Total Access 5000

deployment guide
Matter
Total Access 5000

Business Services
Deployment Guide
System Release: 5.1.0
Document Number: 65K510DEP08-1A

April 2010
Total Access 5000 Business Services Deployment Guide
Trademarks
Any brand names and product names included in this document are
trademarks, registered trademarks, or trade names of their respective holders.
To the Holder of this Document

The contents of this document are current as of the date of publication. ADTRAN® reserves
the right to change the contents without prior notice.
In no event will ADTRAN be liable for any special, incidental, or consequential damages or
for commercial losses even if ADTRAN has been advised thereof as a result of issue of this
document.
About this Document

This document supports Total Access 5000 System Release 5.1. Deployment Guides provide
quick start installation and turn up information for the Total Access 5000 system deploying a
specific network application. The intended audience for this information is the craft person
responsible for the initial system installation. This guide provides configuration steps needed
to achieve traffic flow‐through, diagrams, descriptions of functionality, and configuration
examples.
For detailed installation, provisioning, and user interface information for each individual
system component, refer to the Installation and Maintenance Guide for each applicable
common, access, and line module.
901 Explorer Boulevard
P.O. Box 140000
Huntsville, AL 35814‐4000
United States
(256) 963‐8000
©2010 ADTRAN, Inc.
All Rights Reserved.
ii 65K510DEP08-1A
Copyrights
Copyright © 1998 Todd C. Miller
strlcat() is copyright as follows:
Copyright © 1998 Todd C. Miller <Todd.Miller@courtesan.com>
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of condi‐
tions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT‐
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright © 1990, 1993 The Regents of the University of California
daemon() and getusershell() is copyright as follows:
Copyright © 1990, 1993 The Regents of the University of California.
3. Neither the name of the University nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
65K510DEP08-1A iii
Modifications for Dropbear to getusershell() are by Paul Marinceu
Copyright © 1982, 1985, 1986, 1988, 1993, 1994 The Regents of the University of California,
Copyright © 1995, 1996, 1997, and 1998 WIDE Project.
3. Neither the name of the project nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS “AS IS” AND
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS
Copyright © 1982, 1985, 1986, 1988, 1993, 1994 The Regents of the University of California.
3. All advertising materials mentioning features or use of this software must display the
following acknowledgement:
4. This product includes software developed by the University of California, Berkeley and
its contributors.
5. Neither the name of the University nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS”ʹ AND
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
iv 65K510DEP08-1A
@(#)socket.h8.6 (Berkeley) 5/3/95
Revision History
Revision Date Description
A April 2010 Initial release. This document supports Total Access 5000 System
Release 5.1.0 and Carrier Ethernet.
Conventions
The following typographical conventions are used in this document:
This font indicates a cross‐reference link.
This font indicates screen menus, fields, and parameters.
THIS FONT indicates keyboard keys (ENTER, ESC, ALT). Keys that are to be pressed simultaneously
are shown with a plus sign (ALT+X indicates that the ALT key and X key should be pressed at the
same time).
This font indicates references to other documentation and is also used for emphasis.
This font indicates on‐screen messages and prompts.
This font indicates text to be typed exactly as shown.
This font indicates silk‐screen labels or other system label items.
This font is used for strong emphasis.
65K510DEP08-1A v
Hazard Classifications
The following hazard classifications are used in this document:
! DANGER
DANGER indicates a hazard with a high level of risk which, if not avoided,
will result in death or serious injury.
! WARNING
WARNING indicates a hazard with a medium level of risk which, if not
avoided, could result in death or serious injury.
! CAUTION
CAUTION indicates a hazard with a low level of risk which, if not avoided,
could result in minor or moderate injury. CAUTION can also be used to alert
against unsafe practices associated with events that could lead to personal
injury.
NOTICE
Notice call‐outs indicate a potentially hazardous situation not related to
personal injury, such as messages related to property damage only.
NOTE
Notes inform the user of additional, but essential, information or features.
Metric Conversion
The Total Access 5000 is designed to fit standard 19‐inch and 23‐inch racks, occupying 2U or
6U of vertical space. 1U equals 1 rack unit of vertical height, which equals 1.75 inches or 44.5
millimeters. The following metric conversions apply:
• 19 inches = 482 millimeters
• 23 inches = 584 millimeters
• 9U (15.75 inches) = 400 millimeters
Other measurements are listed in metric and standard notations, where applicable.
vi 65K510DEP08-1A
Icons
The following icons are used throughout the ADTRAN document suite:
jobAid
installation guide
deployment guide
application guide
reference guide
diagnostic guide
safety and regulatory
engineering guide
release notes
upgrade guide
user guide
Training
ADTRAN offers training courses on our products. These courses include overviews on
product features and functions while covering applications of ADTRAN product lines.
ADTRAN provides a variety of training options, including customized training and courses
taught at our facilities or at customer sites.
For inquiries concerning training, contact ADTRAN:
Training Phone: 800‐615‐1176, ext. 6303
Training Fax: 256‐963‐6217
Training Email:training@adtran.com
65K510DEP08-1A vii
viii 65K510DEP08-1A
Contents
Introduction
Scope of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1
In this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2
Section 1
Business Services Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Scope of this Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Ethernet over Copper Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ethernet over Copper Components List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Business Services Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Business Services Migration Components List . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Ethernet over TDM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Ethernet over TDM Components List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Ethernet over Fiber Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Ethernet over Fiber Components List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
CLI Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
CLI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
CLI Input Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
65K510DEP08-1A ix
Section 2
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Tools Required for Chassis Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Install the SMIO3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
SMIO3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Install the Fan Module and Fan Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Fan Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Mount the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Ground the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Connect the Power Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Install and Connect the Rear Panel Components . . . . . . . . . . . . . . . . . . . 2-11
Connect the SMIO3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
AMIO1 Blank Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Install the AMIO1 Blank Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
AMIO2-CH50P Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
AMIO2-CH64P Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
LMIO2-CH64B Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
LMIO2-CH50D Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
LMIO2 HD DS1 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
LMIO2 High-Speed Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
LMIO2 DS3 BNC Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Installing a DS3 BNC Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Install the Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Install the Front Panel Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
SCM Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
SCM, Second Generation Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Bridging SCM Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Ethernet 2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Install the SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
GigE SM Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Install the GigE SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Install the SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
32-Port SHDSL EFM Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
EFM Bonding Protection Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Install the EFM Bonding Protection Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
CH DS3 PPP/MLPPP 3-Port Line Module Description . . . . . . . . . . . . . . . . . . . . 2-20
PPP T1 Link to Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
DS3 EFM 4-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
DS3 EFM 3-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
x 65K510DEP08-1A
Contents
T1 8-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

GE 4-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
RPR Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Gigabit Ethernet 8-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . 2-23
DS1 PPP/MLPPP 32-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . 2-23
Install the Access and Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Apply Power and Verify the Self-Test Passes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Install the NetVanta 800/80000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
NetVanta 814 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
NetVanta 8044 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Section 3
Common Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Log On to the Total Access 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Set the Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Provision the SNMP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Set the TID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Provision the Node Number and Network Name. . . . . . . . . . . . . . . . . . . . . 3-5
Provision the GigE SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Provision the GigE SM Administration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Provision the Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Provision the Network Port Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Network Port Mode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Port Mode Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Example #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Example #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Example #3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Example #4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Provision the Gigabit-Ethernet Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Provision the LACP Switchover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Provision LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Provision the Timing Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Configure SCM Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
VLAN Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Provisioning the IP Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Provision the Inband Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
65K510DEP08-1A xi
Provisioning the Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Provision the Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Provision the S-tag Tag Protocol Identifier (TPID) . . . . . . . . . . . . . . . . . . 3-16
Provision the Class of Service (CoS) Map . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
SNTP Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Provision SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Disable SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
View SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Provision Authentication, Authorization, and Accounting (AAA) . . . . . . 3-19
Configure TACACS+ Server(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Configure Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Authentication Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Configure TACACS+ Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Configure User Activity Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Accounting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Configure Local User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Create a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Modify an Existing User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Delete an Existing User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Configure the Password Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Section 4
EoCu Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
EoCu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Provisioning Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Provision the 32-Port SHDSL EFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Provision the 32-Port SHDSL EFM Administration Status . . . . . . . . . . . . . . . . . . . 4-4
Provision the EFM Bonding Protection Module Administration State . . . 4-6
Create an EFM Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Bonding Group Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Provisioning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Verify Bonding Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
EFM Bonding Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Configure EFM Bonding Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . 4-9
Modify an Existing Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Modify a Bonding Group with EZ-EFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Modify a Bonding Group Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Auto-Provision the SHDSL Pairs Using EZ-EFM . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
EFM Bonding Overhead Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
xii 65K510DEP08-1A
Contents
Create an EVC Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
EVC Cross Connect Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Provisioning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
ELAN Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Enable EFM Bonding Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
EFM Bonding Protection Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Log On to the NetVanta 838 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
CRAFT Port Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Remote Access Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Create an EVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
EVC Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Configure the EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
EVC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Create an EVC Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Map Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Map Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Configure the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Provision Policers in the NetVanta 838 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Policer Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Policer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Provision MAC Address Limiting and Aging . . . . . . . . . . . . . . . . . . . . . . . 4-30
Disable Unused NetVanta 838 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Disable the SHDSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Disable Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Disable the Gigabit-Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Disable Power Feed Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Clear the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Save the NetVanta 838 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
65K510DEP08-1A xiii
Section 5
BSM Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
BSM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Provision the Line Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Provision the CH DS3 PPP/MLPPP 3-Port Line Module Administration Status . . 5-4
Provision the DS1 PPP/MLPPP 32-Port Line Module Administration Status . . . . 5-6
Create a Point-To-Point Protocol Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
PPP Group Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Delete a PPP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
PPP Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Add a Link to the PPP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Delete a Link from the PPP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
EVC Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
EVC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Create an EVC Map on the Total Access 5000 . . . . . . . . . . . . . . . . . . . . . 5-15
Map and DSCP Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Map Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
EVC Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Section 6
EoTDM Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
In this Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
EoTDM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Provision the Line Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Provision the Line Module Administration Status . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Create an EFM Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Bonding Group Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Verify Bonding Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
EFM Bonding Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
xiv 65K510DEP08-1A
Contents
Configure EFM Bonding Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . 6-9

Modify an Existing Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Modify a Bonding Group with EZ-EFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Modify a Bonding Group Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
EFM Bonding Overhead Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
EVC Cross Connect Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
CRAFT Port Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Remote Access Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Create an EVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
EVC Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
EVC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Create an EVC Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Map Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Map Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Modify an Existing EFM Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Remove an Existing Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Provision Policers in the NetVanta 800 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Policer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Disable Unused NetVanta 800 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Disable the DS1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Disable Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Disable Power Feed Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
Save the NetVanta 800 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
65K510DEP08-1A xv
Section 7
EoF Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
EoF Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Provision the GE 8-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Configure Subtended Host Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Create an EVC Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
EVC Cross Connect Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
ELAN Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Provisioning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
CRAFT Port Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Remote Access Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Create an EVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
EVC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
EVC Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
EVC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Create an EVC Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Map Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Map Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Provision Policers in the NetVanta 8044 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Policer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Disable Unused NetVanta 8044 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Save the NetVanta 8044 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
xvi 65K510DEP08-1A
Contents
Appendix A
Link Aggregation Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Link Aggregation Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Disable LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Enable Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Create a Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Enable LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Configure Default Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Configure EVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Redirect EVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Remove Link Aggregation Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Provision Default Network Interface to None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Redirect EVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Remove a Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Provision Default Network Interface to SM A, Net 1 . . . . . . . . . . . . . . . . . . . . . . . A-7
Disable Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Appendix B
SHDSL Rate Reach Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
49-Self Reach on AWG24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Realistic Deployment Reach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Bonded 49-self Reach for a Minimum Rate of 10Mbps . . . . . . . . . . . . . . . . . . . . . . B-3
Bonded 49-self Reach for a Maximum Rate of 10Mbps. . . . . . . . . . . . . . . . . . . . . . B-3
Appendix C
Ethernet OAM Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Ethernet Operation, Administration, and Management . . . . . . . . . . . . . . . . . . . . . . C-2
Ethernet OAM Carrier Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Ethernet OAM for Business Service Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Ethernet OAM on the NetVanta 800/8000 Series NCTE . . . . . . . . . . . . . . . . . . . . . . C-4
NetVanta 800/8000 Series NCTE Configuration Procedure . . . . . . . . . . . . . . . . . C-5
Create a MEP and Enable CCMs per MEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
NCTE Ethernet OAM Example Using Component 1 . . . . . . . . . . . . . . . . . . . . . . . C-8
65K510DEP08-1A xvii
NCTE A Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

NCTE B Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
NCTE Ethernet OAM Example Using Component 2 . . . . . . . . . . . . . . . . . . . . . . . C-9
NCTE A Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
NCTE B Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Ethernet OAM on the MSAP (Total Access 5000) . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Enable Ethernet OAM on the Total Access 5000 . . . . . . . . . . . . . . . . . . . . . . . . C-11
Create the Maintenance Domain and Association . . . . . . . . . . . . . . . . . . . . . . . . C-11
Create a MIP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
MIP Creation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Create a Gigabit-Ethernet MEP on the Total Access 5000 . . . . . . . . . . . . . . . . . C-12
MEP Creation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Appendix D
TWAMP Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
TWAMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
TWAMP Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
TWAMP Connection Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
TWAMP Test Session Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
TWAMP Active Test Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
TWAMP Test Session End and PM Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
TWAMP Configuration on the NCTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Current TWAMP Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Appendix E
Dynamic Counters Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Configure or Modify the Counter Profile for the Counter . . . . . . . . . . . . . . . . . . . . E-2
Shut the Counter Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
xviii 65K510DEP08-1A
Contents
Appendix F
NetVanta Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Rules for Provisioning EVCs, EVC Maps, and Policers . . . . . . . . . . . . . . . . . . . . . F-2
EVCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
EVC Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
Admin State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
MEN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
S-tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
List of Connected EVC Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
CE-VLAN Preservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
EVC Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
EVC Map Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
Destination EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
Admin State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8
UNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8
CE-VLAN-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8
CE-VLAN-Pri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8
DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
Untagged and Priority Tagged Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
MEN-Pri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
Men-Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
MAC Type - Broadcast/Multicast/Unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
L2CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
Example #1: Two CE-VLANs Mapped to Two EVCs . . . . . . . . . . . . . . . . . . . . . . F-10
Example #2: Two CE-VLANs Mapped to One EVC . . . . . . . . . . . . . . . . . . . . . . F-11
Example #3: EVC Map Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-12
Bandwidth Policer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-14
Bandwidth Policer Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-14
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-14
Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-14
Admin State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
UNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
List of EVC-maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
CIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
CBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-16
65K510DEP08-1A xix
EIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-16
EBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-16
Example #1: Ingress Bandwidth Policer per UNI . . . . . . . . . . . . . . . . . . . . . . . . . F-16
Example #2: Ingress Bandwidth Policer per EVC . . . . . . . . . . . . . . . . . . . . . . . . F-16
Example #3: Ingress Bandwidth Policer per Custom . . . . . . . . . . . . . . . . . . . . . . F-17
NetVanta 800/8000 Series Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-19
Configuration for LTU #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-19
Configuration for LTU #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-22
Configuration for NTU #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-23
Appendix G
BSM DS3/DS1 Layer 1 Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Loopback Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Line Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
DS3 Test Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
Remote Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4
Test Administrative Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4
Local Line Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4
BERT Test Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4
DS1 Test Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5
Remote Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5
Test Administrative Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6
Local Line Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6
BERT Test Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6
Appendix H
Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-2
Default Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-2
T3 Alarm Severity Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-2
T1 Alarm Severity Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-3
xx 65K510DEP08-1A
Contents
Appendix I
5.1 Provisioning Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Total Access 5000 Provisioning Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-2
NetVanta 80/8000 Provisioning Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-21
Appendix J
GigE Star Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1
Central Office Terminal (COT) Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-2
Provision the GE 4-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-2
Provision the GE 4-Port Line Module Administration Status . . . . . . . . . . . . . . J-2
Provision the Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-3
Provision the Ethernet Star . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-3
Provision for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-4
Provision the DS3 Unchannelized EFM 4-Port Line Module . . . . . . . . . . . . . . . . . J-4
Provision the DS3 Unchannelized EFM 4-Port Line Module
Administration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-4
Provision the Uplink Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-5
Provision the Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-6
Provision the T1 8-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-6
T1 8-Port Line Module Provisioning Defaults . . . . . . . . . . . . . . . . . . . . . . . . . J-6
Access the T1 8-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-8
Provision the T1 8-Port Line Module Service State . . . . . . . . . . . . . . . . . . . . J-8
Provision the T1 8-Port Line Module DS1 Interface Service State . . . . . . . . . J-8
Provision the Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-8
Provision the Uplink Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-9
Provision the DS1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-9
Remote Terminal (RT) Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-10
Provision the GigE SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-10
Provision the Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-10
Provision the GE 4-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-11
Provision the GE 4-Port Line Module Administration Status . . . . . . . . . . . . . J-11
Provision the Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-12
Provision the Ethernet Star . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-12
Provision for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-12
Provision the DS3 Unchannelized EFM 4-Port Line Module . . . . . . . . . . . . . . . . J-13
Provision the DS3 Unchannelized EFM 4-Port Line Module Administration Status
J-13
Provision the Uplink Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-14
65K510DEP08-1A xxi
Provision the T1 8-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-15

Provision the Uplink Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-15
Appendix K
GigE Linear Chain Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-1
Central Office Terminal (COT) Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-2
Remote Terminal (RT) Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-2
Appendix L
RPR Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1
Basic RPR Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1
Ethernet Ring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-2
Central Office Terminal (COT) Node Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . L-3
Provision the RPR Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-3
RPR Line Module Provisioning Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-3
Access the RPR Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-4
Provision the RPR Line Module Service State . . . . . . . . . . . . . . . . . . . . . . . . L-5
Provision the Hub/Spoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-6
Provision the Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-7
Provision the IGMP Multicast VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-7
Remote Terminal (RT) Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-8
Provision the GigE SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-8
Provision the Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-8
Provision the Hop Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-8
Provision the RPR Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-9
Provision the Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-9
Provision the Hub/Spoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-9
Provision the IGMP Multicast VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-10
xxii 65K510DEP08-1A
Contents
Appendix M
Add/Remove Node from RPR Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-1
Perform a Manual or Forced Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-2
Add Node to a Complete Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-4
Remove a Node from a Complete Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-6
Appendix N
ERPS Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-1
ERPS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-2
ERPS Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-2
ERPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-2
Ring Interface Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-3
New Remote Terminal Addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-4
System Timing Configuration for Central Office Node . . . . . . . . . . . . . . . . . . . . . . N-4
System Timing Configuration for Remote Terminal Node . . . . . . . . . . . . . . . . . . . N-5
Appendix O
Loopback Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-1
Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-1
In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-1
Loopback Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-2
Line Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-2
Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-3
Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-4
65K510DEP08-1A xxiii
Figures
Figure 1-1. EoCu General Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 1-2. Business Service Migration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Figure 1-3. BSM and EoCu Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Figure 1-4. EoTDM DS3 4-Port General Application Diagram . . . . . . . . . . . . . . . . . . . . . 1-8
Figure 1-5. EoTDM DS3 3-Port General Application Diagram . . . . . . . . . . . . . . . . . . . . . 1-9
Figure 1-6. EoF General Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Figure 2-1. Installing the SMIO3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Figure 2-2. 23-Inch Fan Module Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Figure 2-3. 23-Inch Fan Filter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-4. Mounting Bracket Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-5. Chassis Rear View, Ground Lug Location . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Figure 2-6. Power Connection Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-7. Installing the Transmit and Receive DS3 Cables . . . . . . . . . . . . . . . . . . . . . 2-14
Figure 2-8. Installing the Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Figure 2-9. Module Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Figure 4-1. EoCu Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Figure 4-2. Bucket Alogrithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Figure 5-1. BSM Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Figure 6-1. EoTDM (Clear Channel) Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Figure 6-2. EoTDM (Channelized) Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Figure 7-1. EoF Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Figure B-1. Single Pair Theoretical 49–self Reach on AWG24 . . . . . . . . . . . . . . . . . . . .B-2
Figure B-2. Single Pair Realistic Deployment Reach on AWG24 . . . . . . . . . . . . . . . . . . .B-2
Figure B-3. Bonded Multi-pair Deployment Reach on AWG24 (rates >10Mbps) . . . . . . .B-3
Figure B-4. Bonded Multi-pair Deployment Reach on AWG24 (rates <10Mbps) . . . . . . .B-3
Figure C-1. Ethernet OAM (Carrier Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2
Figure C-2. Ethernet OAM (BSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3
Figure F-1. E-Line Service - EVC per CE-VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11
Figure F-2. Detailed Mapping of Two Point-to-Point EVCs . . . . . . . . . . . . . . . . . . . . . . F-11
Figure F-3. E-Line Service - EVC per Multiple CE-VLANs . . . . . . . . . . . . . . . . . . . . . . . F-12
Figure F-4. Detailed Mapping of a Point-to-Point EVC . . . . . . . . . . . . . . . . . . . . . . . . . . F-12
Figure F-5. Typical NetVanta 800/8000 Series Applications . . . . . . . . . . . . . . . . . . . . . F-19
Figure G-1. Line Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Figure G-2. Payload Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
Figure G-3. Remote Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
Figure L-1. RPR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-2
Figure L-2. Two RPR Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-2
Figure L-3. RPR Line Module Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-5
Figure L-4. RPR Line Module Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-6
65K510DEP08-1A xxiv
Figure M-1. RPR Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-2
Figure M-2. Current Protection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-3
Figure M-3. Add/Remove Node Illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-4
Figure M-4. Current West Protection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-5
Figure M-5. Protection Command: Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-5
Figure O-1. Line Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-2
Figure O-2. Payload Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-3
Figure O-3. Remote Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-4
xxv 65K510DEP08-1A
Tables
Table Intro-1. Topic List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1

Table Intro-2. Related System Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2
Table 1-1. Section 1 Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Table 1-2. Deployment Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Table 1-3. Deployment Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Table 1-4. Deployment Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Table 1-5. Deployment Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Table 1-6. Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Table 1-7. CLI Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Table 1-8. Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Table 1-9. Input Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Table 2-2. Rear Panel Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table 2-3. LED Self-test Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Table 3-2. GigE SM Administration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Table 3-3. GigE SM Network Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Table 3-4. Network Port Service State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Table 3-5. LACP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Table 3-6. CoS Map Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Table 3-7. Password Complexity Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Table 4-2. 32-Port SHDSL EFM Administration States . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-3. 32-Port SHDSL EFM Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Table 4-4. EFM Bonding Protection Module Administration States . . . . . . . . . . . . . . . . 4-6
Table 4-5. EFM Bonding Group Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Table 4-6. Available S-tag Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Table 4-7. EFM Bonding Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Table 5-2. Line Module Administration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Table 5-3. DS1 Administration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Table 5-4. PPP Group Connecting Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Table 5-5. PPP Link Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Table 5-7. PPP Group Connecting Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Table 6-2. DS3 EFM 4-Port and DS3 EFM 3-Port Administration States . . . . . . . . . . . . 6-4
Table 6-3. EFM Bonding Group Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table 7-2. GE 8-Port Line Module Administration States . . . . . . . . . . . . . . . . . . . . . . . . 7-4
65K510DEP08-1A xxvi
Table 7-3. Available S-tag Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Table A-1. Appendix A Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Table B-1. Appendix B Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
Table C-1. Appendix C Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1
Table D-1. Appendix D Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1
Table D-2. Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-6
Table E-1. Appendix E Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-1
Table F-1. Appendix F Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Table F-2. EVC Map Forwarding Order of Precedence . . . . . . . . . . . . . . . . . . . . . . . . . F-3
Table F-3. EVC Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
Table F-4. EVC State Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
Table F-5. CE-VLAN Preservation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-6
Table F-6. EVC Map Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7
Table F-7. Map State Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8
Table F-8. Untagged and Priority Tagged Frame Options . . . . . . . . . . . . . . . . . . . . . . . F-9
Table F-9. MAC Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
Table F-10. L2CP Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
Table F-11. Policer Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-14
Table F-12. Policer State Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
Table F-13. Mode Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15
Table G-1. Appendix G Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Table H-1. Appendix H Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H-1
Table H-2. Default Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H-2
Table H-3. T3 Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H-3
Table H-4. T1 Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H-3
Table I-1. Appendix I Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Table I-2. Authentication, Authorization, and Accounting (AAA) Defaults . . . . . . . . . . . I-2
Table I-3. Auto-Upgrade Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-2
Table I-4. SCA Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-3
Table I-5. Security Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-4
Table I-6. System Privilege Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-4
Table I-7. Username Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-5
Table I-8. Ethernet CFM Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-6
Table I-9. Node Number and Network Name Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . I-6
Table I-10. Fan Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-6
Table I-11. Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-7
Table I-12. Gigabit-Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-7
Table I-13. SDHSL Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-8
Table I-14. T1 Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-8
Table I-15. T3 Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-9
Table I-16. EFM Group Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-10
Table I-17. EFM Link Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-11
Table I-18. System Management EVC Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12
Table I-19. Redundancy Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12
Table I-20. QOS COS-Map Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12
Table I-21. Queue EFM Group Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12
Table I-22. System Timing Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-13
xxvii 65K510DEP08-1A
Tables
Table I-23. Event Log Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-13

Table I-24. IP Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-13
Table I-25. Power Shedding Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-15
Table I-26. System Alarm Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-15
Table I-27. TL1 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-19
Table I-28. SNMP Host Parameters Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-19
Table I-29. Ethernet CFM Default-Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-19
Table I-30. Line Admin 0 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-20
Table I-31. Line Console 0 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-20
Table I-32. Line Network 0 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-20
Table I-33. Operational Modes Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-21
Table I-34. AAA Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-21
Table I-35. SHDSL Timeout Training Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-21
Table I-36. TACACS+ Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-22
Table I-37. RADIUS Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-22
Table I-38. Security Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-22
Table I-39. Username Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-22
Table I-40. Ethernet CFM Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-23
Table I-41. Probe Responder TWAMP Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-23
Table I-42. Queue Time-Constant Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-23
Table I-43. QOS COS-Map Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-24
Table I-44. Temperature-Sensor Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-24
Table I-45. SHDSL Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-24
Table I-46. Gigabit-Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-25
Table I-47. EFM Group Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-26
Table I-48. EFM Link Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-26
Table I-49. Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-26
Table I-50. Gigabit-Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-27
Table I-51. Queue Ethernet Interface Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-28
Table I-52. Queue EFM Group Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-29
Table I-53. System Management EVC Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-29
Table I-54. Counter Profile Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-29
Table I-55. System Alarm Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-29
Table I-56. SNMP Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-30
Table I-57. Line Console Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-30
Table J-1. Appendix J Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1
Table J-2. GE 4-Port Line Module Administration States . . . . . . . . . . . . . . . . . . . . . . . . J-2
Table J-3. DS3 Unchannelized EFM 4-Port Module Administration States . . . . . . . . . . J-4
Table J-4. T1 8-Port Line Module Provisioning Defaults . . . . . . . . . . . . . . . . . . . . . . . . . J-7
Table J-5. GE 4-Port Line Module Administration States . . . . . . . . . . . . . . . . . . . . . . . J-11
Table J-6. DS3 Unchannelized EFM 4-Port Module Administration States . . . . . . . . . J-13
Table K-1. Appendix K Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .K-1
Table L-1. Appendix L Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1
Table L-2. Default Provisioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-3
Table M-1. Appendix M Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-1
Table N-1. Appendix N Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .N-1
Table O-1. Appendix O Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O-1
65K510DEP08-1A xxviii
Introduction
Scope of this Guide

This guide provides the minimum configuration steps needed for the Ethernet over Copper
(EoCu), Business Service Migration (BSM), Ethernet over TDM (EoTDM), and Ethernet over
Fiber (EoF) deployments.
In this Guide
This guide contains the topics listed in Table Intro‐1.
Table Intro-1. Topic List
Section Topic
Section 1 Business Services Overview
Section 2 Installation
Section 3 Common Provisioning
Section 4 EoCu Provisioning
Section 5 BSM Provisioning
Section 6 EoTDM Provisioning
Section 7 EoF Provisioning
Appendix A Link Aggregation Guide
Appendix B SHDSL Rate Reach Information
Appendix C Ethernet OAM Provisioning
Appendix D TWAMP Provisioning
Appendix E Dynamic Counters Provisioning
Appendix F NetVanta Examples
Appendix G BSM DS3/DS1 Layer 1 Tests
Appendix H Alarm Severities
Appendix I 5.1 Provisioning Defaults
65K510DEP08-1A Intro-1
Table Intro-1. Topic List
Section Topic
Appendix J GigE Star Provisioning
Appendix K GigE Linear Chain Provisioning
Appendix L RPR Provisioning
Appendix M Add/Remove Node from RPR Ring
Appendix N ERPS Provisioning
Appendix O Loopback Provisioning
Related Documentation
Refer to Table Intro‐2 for additional, detailed system information concerning the Business
Services deployment. For detailed component information, refer to the applicable Installation
and Maintenance Guides and Job Aids for the individual component product.
Table Intro-2. Related System Documentation
Title Part Number
Total Access/NetVanta Carrier CLI Dictionary 6TANV510CLI‐35
Total Access 5000/5006 Engineering and Ordering Guide System Release 5.1 65K510ENG‐1
Total Access 5000 I/O Module Configuration Job Aid 65K510XMIO‐22
Total Access 5000/5006 Load Calculation Guidelines Job Aid 65KLOADCALC‐22
Broadband SFP/XFP Matrix Application Note 61442000G1‐49
Intro-2 65K510DEP08-1A
Section 1
Business Services Overview
Scope of this Section

This section provides an overview of the Ethernet over Copper (EoCu), Business Services
Migration (BSM), Ethernet over TDM (EoTDM), and Ethernet over Fiber (EoF) applications. In
addition, the section also provides a Command Line Interface (CLI) overview.
In this Section
This section contains the following topics:
Table 1-1. Section 1 Topics
Topic See Page
Ethernet over Copper Overview 1‐2
Business Services Migration Overview 1‐5
Ethernet over TDM Overview 1‐8
Ethernet over Fiber Overview 1‐12
Command Line Interface Overview 1‐14
65K510DEP08-1A 1-1
Ethernet over Copper Overview

The Total Access 5000 is a carrier class multi‐service access and aggregation platform. It
supports Internet Protocol Television (IPTV) and Voice over IP (VoIP) across both copper and
fiber interfaces while simultaneously supporting legacy services. These services include basic
Plain Old Telephone Service (POTS) and Digital Subscriber Line (DSL).
The end to end EoCu solution (Figure 1‐1) encompasses the latest Metro Ethernet Forum
(MEF) certified Ethernet in the First Mile (EFM) over copper network termination units
(NTU), which leverages existing copper facilities to offer extended reach Carrier Ethernet up
to 45Mbps.
The EoCu solution offers the following features:
• Consistent Operations, Administration and Maintenance (OAM)
• Traffic management and flow‐through provisioning
• Resiliency through dynamic circuit removal and restoration
• Electrical and Optical Ethernet connections to the customer
Total Access 5000

SHDSL
(x8) EoCu
General
Central Office Application Diagram
SHDSL
SHDSL
Pairs (x8)
Router
Customer Site
NetVanta 838
Figure 1-1. EoCu General Application Diagram
1-2 65K510DEP08-1A
Section 1, Business Services Overview - Ethernet over Copper Overview
Ethernet over Copper Components List

Table 1‐2 lists the products needed for the EoCu deployment.
Table 1-2. Deployment Part Numbers
Part Number Description CLEI
Total Access 5000 Components
1187001L1 23‐Inch Chassis BVM2V10G_ _
1187010L1 System Controller Module (SCM) BVCUD0YM_ _
1187010G2 SCM, Second Generation BVC1AA6E_ _
1187011G1 Bridging SCM BVC1ABGE_ _
1187020G1 Switch Module 2 Gigabit, no Ring Generator BVL2N0NC_ _
1187020G2 Switch Module 2 Gigabit, w/Ring Generator BVL2N0PC_ _
1187025G1 Switch Module 2‐10G/2‐1 Gigabit, no Ring Generator BVL3AE4D_ _
1187025G2 Switch Module 2‐10G/2‐1 Gigabit, w/Ring Generator BVL3AE5D_ _
1187030G1 Switch Module 5, 2‐10G/2‐1/2.5 Gigabit, no Ring Generator BVL3AE6D_ _
1187051L1/G1 Switch Module I/O 3 (SMIO3) BVL2PT0C_ _
1187180L1 32‐Port SHDSL EFM Access Module BVL3ABED_ _
1187260G1 DS3 Unchannelized EFM 4‐Port Line Module BVL3ADAD_ _
1187300L1 T1 8‐Port Line Module BVL250CC_ _
1187520E1 RPR Line Module BVC1AAWE_ _
1187550E1 Gigabit Ethernet 4‐Port (GE 4‐Port) Line Module BVL2270C_ _
1187400G1 Line Module Input/Output Dual Champ 64‐Pin Bridged Rear BVL260DC_ _

Panel (LMIO2‐CH64B)
1187401G1 Line Module Input/Output Dual Champ 50‐Pin Divided Rear BVL2X10C_ _

Panel (LMIO2‐CH50D)
1187410G1 Access Module Input/Output Dual Champ 50‐Pin Push‐ BVPQADHM_ _

Through Panel (AMIO2‐CH50P)
1187411G1 Access Module Input/Output Triple Champ 50‐Pin Push‐ BVPQAD2M_ _

1187450G1 Access Module Input/Output Dual Champ 64‐Pin Push‐ BVPQADJM_ _

1187460E1 LMIO2 High‐Speed Line Module Rear Panel BVM6E00A_ _
1187925G1 AMIO1 Blank Panel N/A
1187080L1 23‐Inch Fan Module BVPQADGM_ _
1187081L1 23‐Inch Fan Filter N/A
65K510DEP08-1A 1-3
Table 1-2. Deployment Part Numbers (Continued)
1187250G1 EFM Bonding Protection Module BVL3ACUD_ _

1187925L1/G1 AMIO1 Blank Panel N/A
Other Components
1200633G4 NetVanta 838 SIM5K10B_ _
1172839G1 NetVanta 838 EFM NTE Enhanced Protection VAMLC00B_ _
! CAUTION
Due to compliance certification requirements, only SFPs supplied by
ADTRAN are to be used with the Total Access 5000 modules. ADTRAN
cannot certify system integrity when non ADTRAN supplied SFPs are used.
1-4 65K510DEP08-1A
Section 1, Business Services Overview - Business Services Migration Overview
Business Services Migration Overview

The Business Services Migration (BSM) application applies to legacy customer routers or
integrated access devices already using a variety of link layer protocols to carry IP traffic over
DS1. Figure 1‐2 displays legacy customer routers connected through a SONET and TDM infra‐
structure that can be migrated to an Ethernet infrastructure through the use of the Total
Access 5000.
Customer
Site DS1
Router
SONET SONET
Central Office #1 Core

Central Office
DCS DCS DCS DS1 over

Channelized
Optical
Interface
DS1
Customer
Site Channelized
DS3
DS1 Total Access

Router 5000
GigE GigE
WAN
IP Router
Network
DS1
Figure 1-2. Business Service Migration Example
Figure 1‐3 displays a mixed serives diagram of the BSM and EoCu applications.
65K510DEP08-1A 1-5
Routers
2G LAG with LACP

Internet Access, for Redundancy
Local LAN
Total Access 5000
PPP T1 To Customer
(Future Availability)
Netvanta 873 (x2)
Ch. DS3 to M13
Routers
SHDSL
PPP T1
To Customer
M13 MUX
Business Service
Migration and Ethernet Internet Access,
over Copper Mixed Services Local LAN
Figure 1-3. BSM and EoCu Application Diagram
1-6 65K510DEP08-1A
Section 1, Business Services Overview - Business Services Migration Overview
Business Services Migration Components List

Table 1‐3 lists the products needed for the Business Service Migration deployment.
1187051L1/G1 Switch Module I/O 3 (SMIO3) BVL2PT0C_ _
1187220G1 CH DS3 PPP/MLPPP 3‐Port Line Module BVL3AFND _ _

Panel
1187402G1 Line Module Input/Output Dual HD DS1 Divided Pair Rear BVL3ADRD_ _

Panel
1187442E1 Line Module Input/Output (LMIO2) DS3 8NR (Non‐Redun‐ BVM6C00A_ _

dant)
1187443L1 Line Module Input/Output (LMIO2) DS3 BNC 4R (Redundant) BVM6D00A_ _
1187803G2 DS1 PPP/MLPPP 32‐Port Line Module BVL3AHRD_ _
1187080L1 23‐Inch Fan Module BVPQADGM_ _
1187081L1 23‐Inch Fan Filter N/A
! CAUTION
65K510DEP08-1A 1-7
Ethernet over TDM Overview

The end to end Ethernet over TDM (EoTDM) solution (Figure 1‐4 and Figure 1‐5) encom‐
passes the latest Metro Ethernet Forum (MEF) certified Ethernet in the First Mile (EFM) over
Time Division Multiplexed (TDM) Network Termination Units (NTU), which leverages
existing TDM/SDH/SONET facilities to offer extended reach Carrier Ethernet up to 135Mbps.
The EoTDM offers the following features:
• Consistent Operations, Administration, and Maintenance (OAM)
• Traffic management and flow‐through provisioning
• Resiliency through dynamic circuit removal and restoration
• Electrical and Optical Ethernet connections to the customer
Total Access 5000

EoTDM
SONET
Multiplexer
(Central Office)
General
DS3s
Router
Customer Site
NetVanta 873
SONET
Multiplexer
(Customer Side)
Figure 1-4. EoTDM DS3 4-Port General Application Diagram
1-8 65K510DEP08-1A
Section 1, Business Services Overview - Ethernet over TDM Overview
EoTDM
Channelized Application
Total Access 5000 Customer Site

Router
SONET
Multiplexer
(Central Office) NetVanta 818
Central Office DS1s
DS3s
Customer Site
Router
DS1s NetVanta 818
NetVanta 818
Customer Site
Router
Figure 1-5. EoTDM DS3 3-Port General Application Diagram
65K510DEP08-1A 1-9
Ethernet over TDM Components List

Table 1‐2 lists the products needed for the EoTDM deployment.
1187020E1 Switch Module 2 Gigabit Ethernet BVL2NSMC_ _
1187260G1 DS3 Unchannelized EFM 4‐Port Line Module (DS3 EFM 4‐Port) BVL3ADAD_ _
1187443L1 Line Module Input/Output (LMIO) DS3 BNC 4R (Redundant) BVM6D00A_ _
1187810G1 DS3 Channelized EFM 3‐Port Line Module (DS3 EFM 3‐Port) BVL3ADSD_ _
1187520E1 RPR Line Module BVC1AAWE_ _
1187550E1 Gigabit Ethernet 4‐Port (GE 4‐Port) Line Module BVL2270C_ _

Panel (LMIO2‐CH64B)
1187401G1 Line Module Input/Output Dual Champ 50‐Pin Divided Rear BVL2X10C_ _

Panel (LMIO2‐CH50D)
1187410G1 Access Module Input/Output Dual Champ 50‐Pin Push‐ BVPQADHM_ _

1187411G1 Access Module Input/Output Triple Champ 50‐Pin Push‐ BVPQAD2M_ _


1187460E1 LMIO2 High‐Speed Line Module Rear Panel BVM6E00A_ _
1187925G1 AMIO1 Blank Panel N/A
1-10 65K510DEP08-1A
Section 1, Business Services Overview - Ethernet over TDM Overview
Table 1-4. Deployment Part Numbers (Continued)
Other Components
1200637G4 NetVanta 814 T1/E1 EFM NTE SIM5700B_ _
1200639G1 NetVanta 873 EFM NTE SIM6J00A_ _
1200637G2 NetVanta 818 T1/E1 EFM NTE SIM5800B_ _
! CAUTION
65K510DEP08-1A 1-11
Ethernet over Fiber Overview

Enhancing the Total Access 5000 to support Ethernet services aggregation is achieved by the
addition of the Gigabit Ethernet 8‐Port Line Module (GE 8‐Port LM). The GE 8‐Port LM can
terminate up to 8 GigE facilities, allowing a single Total Access 5000 shelf to terminate
multiple 10Mbps, 100Mbps, and/or 1 Gbps access facilities. The GE 8‐Port LM can be used in
conjunction with the existing EoCu and/or EoTDM services, allowing multiple business
service delivery methods to be provided from a single Total Access 5000 shelf.
In addition to sub‐aggregating existing Ethernet over Fiber (EoF) facilities, the Total Access
5000 and associated GE 8‐Port LM is capable of delivering new Ethernet services directly to
customer locations with fiber connectivity; supporting scalable service rates of up to 1 Gbps.
Further, Service Providers who have already deployed the Total Access 5000 for delivering
EoCu and/or EoTDM, new EoF services delivery can be added to the solution portfolio
without a lengthy and expensive standardization process thus improving the solutions time to
market. The NetVanta 8000 family of Etherent over Fiber NTU would be sub‐tended from the
Total Access 5000 via this new GE 8‐Port LM to deliver the Ethernet service to the customer
premises.
Total Access 5000

GigE EoF
General
GE Optical
Fiber
GigE
Router
Customer Site
NetVanta 8044
Figure 1-6. EoF General Application Diagram
1-12 65K510DEP08-1A
Section 1, Business Services Overview - Ethernet over Fiber Overview
Ethernet over Fiber Components List

Table 1‐5 lists the products needed for the EoF deployment.
1187020E1 Switch Module 2 Gigabit Ethernet BVL2NSMC_ _
1187460E1 Line Module Input/Output Dual High‐Speed Rear Panel BVM6E00A_ _
1187552G1 Gigabit Ethernet 8‐Port Line Module BVL3AHDD_ _
Other Components
1172804G1 NetVanta 8044 Fiber Network Termination Equipment BVM8600E_ _
! CAUTION
65K510DEP08-1A 1-13
Command Line Interface Overview

This section details the following information:
• Command Modes
• CLI Shortcuts
• CLI Error Messages
• CLI Input Descriptions
Command Modes
The Total Access 5000 CLI has three command modes, Basic, Application, and Enable. Each
mode supports a specific set of commands. For example, all interface configuration
commands are accessible only through the Enable mode. Table 1‐6 shows a brief description of
each command mode.
Table 1-6. Command Modes
Mode Access by... Prompt With this mode...
Basic Beginning a session > Display system information and

show status or statistics
Enable Entering Enable mode while # Manage running configurations,

in the Basic mode as follows: enter any configuration modes, and
>enable view security settings
Application Performing a common func‐ # Copy system provisioning and exe‐

tion with a reduced set of cute standard test procedures
commands
CLI Shortcuts
Use the CLI shortcuts to help configure the product. Table 1‐7 provides a list of the CLI
shortcuts.
1-14 65K510DEP08-1A
Section 1, Business Services Overview - Command Line Interface Overview
Table 1-7. CLI Shortcuts
Shortcut Description
Up arrow or CTRL + P Use the up arrow to re‐display a previously entered command. The up
arrow can cycle through all commands entered starting with the most
recent command.
TAB After entering a partial, but unique, command, press the TAB to complete
the command. The command displays on the command prompt and waits
for input.
? Use the ? for any of the following:
• Display a list of all subcommands in the current mode.
• Display a list of available commands beginning with certain letter(s).
• Obtain syntax help for a specific command by entering the command, a
space, and then a question mark (?). The CLI displays the range of
values and a brief description of the next parameter expected for that
particular command.
CTRL + A Use CTRL + A to jump to the beginning of the displayed command line.
CTRL + E Use CTRL + E to jump to the end of the displayed command line.
CTRL + U Use CTRL + U to clear the current displayed command line.
Auto finish Enter enough letters to identify a command as unique. For example, enter‐
ing int eth 1 at the Global Configuration prompt provides access to
the configuration parameters for the specified Ethernet interface.
CLI Error Messages

Table 1‐8 lists and defines some of the more common error messages given in the CLI.
Table 1-8. Error Messages
Message Helpful Hints
%Ambiguous command This message occurs when multiple commands can be derived
from the input. Try using the “?” command to determine the
error. Refer to “CLI Shortcuts” on page 1‐14 for more informa‐
tion.
%Unrecognized command This message occurs when a single command is entered that fails
to match any supported commands. Try using the “?” command
to determine the error. Refer to “CLI Shortcuts” on page 1‐14 for
more information.
%Invalid or incomplete com‐ This message occurs when the command is not properly finished.
mand Try using the “?” command to determine the error. Refer to “CLI
Shortcuts” on page 1‐14 for more information.
%Invalid input detected at “^” The error in command entry is located where the caret (^) mark
marker appears. Enter a question mark at the prompt. The system dis‐
plays a list of applicable commands or gives syntax information
for the entry.
65K510DEP08-1A 1-15
CLI Input Descriptions

Table 1‐9 lists and defines the inputs used throughout the CLI.
Table 1-9. Input Descriptions
Input Syntax Input Example Description
<x-y> ‐2‐4000 Use this input to enter a range by entering the x and y

variables. The x and y variables are numeric and can be
negative.
<x-n> 1‐n Use this input to enter an infinite range by entering the

x variable. The x variable is numeric and can be nega‐
tive.
<x> 0 Use this input to enter a single number.
<x,y-z,a> ‐1,4‐10,20‐22 Use this input to enter a comma delimited numeric list

without spaces. This input can include ranges.
<HH:MM:SS> 12:30:01 Use this input to enter the time in hour‐minute‐second

format.
<HH:MM> 12:30 Use this input to enter the time in hour‐minute format.
MONTH MAR Use this input to enter the month. Use the full month

name or the 3‐letter abbreviation. This input is not case
sensitive.
HHH 010 Use this input to enter a numeric hex. The number of

“H”s designates the number of hex digits allowed.
WORD MAP_1 Use this input to enter a string without spaces. This

input is case sensitive.
LINE MAP 2 Use this input to enter a string allowing spaces. This

input is case sensitive.
LIST 1,3‐7,9,10 Use this input to enter a comma delimited numeric list

without spaces. This input can include ranges.
<character> A Use this input to enter any single alpha character.
A.B.C.D Use this input to enter an IP address.
xx:xx:xx:xx:xx:x Use this input to enter a MAC address.
x
<shelf/slot/ 1/1/1 Use this input to enter the shelf, slot, and port.

port>
<shelf/slot/ 1/1/MAP Use this input to enter the shelf, slot, and WORD.

WORD>
<shelf/slot> 1/S Use this input to enter the shelf and slot.
<shelf/WORD> 1/DEFAULT Use this input to enter the shelf and WORD.
<shelf> 1 Use this input to enter the shelf number. Only shelf 1 is
supported.
1-16 65K510DEP08-1A
Section 1, Business Services Overview - Command Line Interface Overview
Table 1-9. Input Descriptions (Continued)
Input Syntax Input Example Description
<slot/port> 1/1 Use this input to enter the slot and port.
<slot> 1 Use this input to enter the slot. Valid inputs are 0 ‐ 22 for
module slots, A for SM A, B for SM B, S for the SCU,
and F for the fan module.
<port> 1 Use this input to enter the port number.
65K510DEP08-1A 1-17
1-18 65K510DEP08-1A
Section 2
Installation

This section provides installation information for the Total Access 5000 Chassis, Fan Module,
Access Modules, and SMIO3.
In this Section
Topic See Page
Tools Required for Chassis Installation 2‐2
Install the SMIO3 2‐3
Install the Fan Module and Fan Filter 2‐5
Mount the Chassis 2‐7
Ground the Chassis 2‐8
Connect the Power Terminal 2‐9
Install and Connect the Rear Panel Components 2‐11
Install the Front Panel Modules 2‐16
Install the NetVanta 800/80000 2‐27
65K510DEP08-1A 2-1
Tools Required for Chassis Installation

The tools required to install the chassis are as follows:
• A #2 phillips‐head screwdriver
• Crimping tool for power lugs
• Wire strippers
• Wire‐wrap tool
• Side cutters
• Torque wrench with a range from 2 to 37 inch/pounds
• Ohmmeter
The items required to install the chassis are as follows:
• Screws for mounting the chassis to the Central Office (CO) racks
• Insulated wire, stranded, copper, (2 AWG to 6 AWG) that is at least equal to the same size
of the power wire for grounding the chassis to the frame
• Data cables terminated for the Total Access 5000 50‐pin or 64‐pin connections
• Insulated wire for power connections
! WARNING
To prevent electrical shock, do not install equipment in a wet location or
during a lightning storm.
NOTICE
Electrostatic Discharge (ESD) can damage electronic modules. Before
handling modules, wear an antistatic discharge wrist strap to prevent
damage to electronic components. Place modules in antistatic packing
material when transporting or storing. When working on modules, always
place them on an approved antistatic mat that is electrically grounded.
2-2 65K510DEP08-1A
Section 2, Installation - Install the SMIO3
Install the SMIO3

This subsection details the following information:
• SMIO3 Description
• Installation Steps
SMIO3 Description
The Switch Module Input/Output 3 (SMIO3) supports one System Controller Module (SCM)
and two Switch Modules (SM).
The SMIO3 provides the following:
• Physical interface (3 slots) to the Total Access 5000 backplane for the SCM and two SMs
• Physical communication paths between the SCM and the SMs
• Communication interface ports to the SCM that enable management of the Total Access
5000 system
• Wire‐wrap terminals for external clocks, alarm I/O, testing, and voltage
• Control signals and a power path to the Fan Module
Installation Steps
The SMIO3 attaches to the back of the Total Access 5000 chassis. To install the SMIO3,
complete the following:
! CAUTION
If the chassis is rack mounted, be sure that the chassis is square and not
distorted by the rack frame before installing the SMIO3. To aid installation,
loosen the chassis mounting bolts to allow the chassis to become square.
NOTE
Before installing the chassis, install the SMIO3. Installing the SMIO3 ensures
the relay rack, if not square, will not warp the chassis. If not done properly,
the SMIO3 mounting screws will not mate with the chassis. For installation
instructions, refer to the Total Access 5000 Switch Module I/O3 (SMIO3) Job Aid
(P/N 61187051L1‐22).
1. Align the SMIO3 across slots labeled 12/SCM, SM A, and SM B (labeled in the front of the

chassis). Seat the SMIO3 onto the installation pegs of the chassis so that it rests firmly
against the chassis frame.
2. Attach the module to the chassis using the four phillips screws and three stand‐offs
provided (see Figure 2‐1).
3. Using a #1 phillips‐head screwdriver, attach the guard to the chassis using the two
screws to secure the guard.
65K510DEP08-1A 2-3
3/8” Screws
Stand-offs
SMIO3
3/4” Screws
Figure 2-1. Installing the SMIO3
NOTE
Before installing the chassis in a CO frame, the paint must be removed from
the surface of the CO frame where the mounting brackets come in contact
with that frame. Antioxidants must be applied to these areas after the paint
has been removed.
2-4 65K510DEP08-1A
Section 2, Installation - Install the Fan Module and Fan Filter
Install the Fan Module and Fan Filter

• Description of the Fan Module
• Installation steps for installing the Fan Module and Fan Filter
Fan Module Description

The Fan Module consists of a sheet metal tray that holds four fans rated at a nominal –48 VDC.
The Fan Module is mounted from the front of the rack and is installed into the top slot of the
Total Access 5000 Chassis. The Fan Module is designed to provide forced air ventilation to
cool a fully populated Total Access 5000 Chassis.
Power is supplied to the Fan Module through two independent circuits that are controlled as a
group. Each circuit supplies power to two fans, which are connected in parallel. When fully
inserted, the Fan Module connects to the SMIO3. The SMIO3 routes power and serial commu‐
nications from the switch module to the Fan Module. The fan microprocessor samples the
speed of each fan and reports an alarm condition for fan failure or eminent fan failure.
Installation Steps
To install the Fan Module, complete the following:
1. Push the Fan Module firmly into the top slot of the chassis (see Figure 2‐2).
Figure 2-2. 23-Inch Fan Module Installation
2. Use the two thumb‐screws on the lower left and right side of the Fan Module to secure
the module to the chassis.
65K510DEP08-1A 2-5
NOTE
The Fan Filter is located at the bottom of the Total Access 5000 chassis and is
accessed from the front of the chassis (see Figure 2‐3).
3. Insert the fan filter at the bottom of the chassis with the springs oriented toward the back
of the chassis and the aluminum filter mesh facing upward.
4. Gently push the filter in and up until it engages with the chassis.
Figure 2-3. 23-Inch Fan Filter Installation
2-6 65K510DEP08-1A
Section 2, Installation - Mount the Chassis
Mount the Chassis

NOTE
When mounting the chassis, leave the mounting screws loose until the SMIO3
and fan module have been installed.
The chassis is shipped with two mounting brackets that are used to install the chassis with
either a 2‐inch, 3.3‐inch, 4.1‐inch or 5‐inch front projection. Each bracket is attached with five
screws, which are supplied with the chassis. Refer to Figure 2‐4 for mounting locations and
mounting bracket orientations.
2-Inch Front
Projection
5-Inch Front
Projection
3.3-Inch Front
Projection
4.1-Inch Front
Projection
Figure 2-4. Mounting Bracket Locations
65K510DEP08-1A 2-7
Ground the Chassis

The frame ground lug can accommodate from 2 AWG to 6 AWG copper, stranded wire. When
connecting the frame ground, use a wire gauge that is at least as large a gauge as the power
connections (see Figure 2‐5).
To make the ground connection to the chassis, complete the following:
1. Ensure that the power is disconnected at the source.
2. Remove the connection hardware from both chassis ground bolts.
3. Clean the surface of the chassis grounding area and apply an appropriate antioxidant.
4. Strip the ground wire 5/8 of an inch and crimp the chassis ground lug to the wire.
5. Connect the ground wire to the chassis ground bolts.
6. Install the lock washers and hex nuts.
7. Torque the hex nuts to 24 inch/pounds.
8. Secure the other end of the ground wire to a suitable rack ground according to local
Central Office (CO) practices.
Ground
Figure 2-5. Chassis Rear View, Ground Lug Location
2-8 65K510DEP08-1A
Section 2, Installation - Connect the Power Terminal
Connect the Power Terminal

The chassis provides redundant power terminal inputs. Two sources of –48 VDC must be
provided to use the redundant power feature. The two power inputs are labeled –48V A and
–48V B and are located on the back of the chassis (see Figure 2‐6).
NOTE
A readily accessible disconnect device such as a rackmount fuse and alarm
panel that is suitably approved and rated, should be incorporated in the fixed
wiring.
NOTICE
The Total Access 5000 System is designed for a reliably grounded ‐48V
nominal DC supply. This requires the positive terminal to be referenced to
earth ground. Make this reference connection at either the source (rectifier or
battery) or at the frame. Powering by any other means may void the warranty
of the product.
To connect power to the chassis, complete the following:
1. Determine which fuse pairs are to supply power to the Total Access 5000 shelf and
remove the fuses from the A and B slots for the pair.
2. Ensure the power is disconnected at the source.
3. Open the plastic power terminal doors on the rear of the chassis to access the power
terminals.
4. Cut four lengths of appropriately sized wire to reach from the terminals on the fuse and
alarm panel to the power terminals on the Total Access 5000 Chassis. Leave enough slack
in the wires to allow for dressing the wires to the rack according to local practice.
5. Strip 5/8 of an inch from the power and return wires, and using a crimping tool, connect
an appropriate lug to each end of the wires.
6. Connect the ends of one wire between the “A‐Side” CO –48 VDC supply and the “A‐
Side”
–48V A terminal on the Total Access 5000 Chassis.
7. Connect three more power wires as follows:
• “A‐Side” CO –48 VDC return to chassis “A‐Side” RTN
• “B‐Side” CO –48 VDC supply to chassis “B‐Side” –48V B
• “B‐Side” CO –48 VDC return to chassis “B‐Side” RTN
8. Ensure all power connections are tight.
9. Close the plastic power terminal doors.
65K510DEP08-1A 2-9
Power Terminal
Figure 2-6. Power Connection Location
2-10 65K510DEP08-1A
Section 2, Installation - Install and Connect the Rear Panel Components
Install and Connect the Rear Panel Components

This subsection details the connection and installation of the Total Access 5000 rear panels.
Connect the SMIO3

The plastic guard that covers the wire‐wrap terminals on the SMIO3 is a safety feature that
prevents personnel and equipment from contacting exposed voltages.
NOTE
The SMIO3 is already installed but must be connected.
To remove the guard, complete the following procedure:
1. Using a #1 phillips‐head screwdriver, remove the three screws that secure the guard.
2. Carefully remove the guard by pulling it straight from the SMIO3.
To reinstall the guard, reverse the previous procedures.
Input and output connectors on the SMIO3 consist of the following:
• Communications Interface Ports – Physical interfaces to the SCM, consisting of RS‐232‐
compatible ports for Admin and Network Management functions, and an Ethernet LAN
for Management functions
• Terminal Block Connections – Labeled blocks of wire‐wrap terminals for alarms, alarm
cut off, external voltage, clock functions, test bus, and shelf linking functions
NOTE
Refer to the Total Access 5000 Switch Module I/O 3 (SMIO3) Installation and
Maintenance Practice (P/N 61187051G1‐5) for detailed information.
AMIO1 Blank Panel

The AMIO1 covers one module slot on the rear of the Total Access 5000 Chassis.
Install the AMIO1 Blank Panel

To install the AMIO1 Blank Panel, complete the following procedure:
1. Position the AMIO1 Blank on the rear alignment pins on the back of the chassis over the
appropriate slot.
1. Using the Captive Panel Screws, secure the AMIO1 Blank to the rear of the chassis.
AMIO2-CH50P Rear Panel

The AMIO2‐CH50P covers two module slots on the rear of the chassis. The AMIO2‐CH50P is
designed to hold two standard entry 50‐pin male champ connector cables. For standard entry,
the cable exits the 90° connector hood on the pin 1 end of the male champ connector.
65K510DEP08-1A 2-11
NOTE
The AMIO2‐CH50P supports the COMBO A2+ 24‐Port and RPOTS 24‐Port
Access Modules.
AMIO2-CH64P Rear Panel

The AMIO2‐CH64P covers two module slots on the rear of the Total Access 5000 Chassis. The
AMIO2‐CH64P is designed to hold two standard entry 64‐pin male champ connector cables.
For standard entry, the cable exits the 90° connector hood on the pin 1 end of the male champ
connector.
NOTE
Push‐through panels are provided with four Captive Champ Screws for
installation of two connectors to the panel. Use two screws for each connector,
one for the mounting bracket, the second to secure the connector to the panel.
The Captive Champ Screw provided with the cable must be replaced if it is
not a 0.35 inch screw.
LMIO2-CH64B Rear Panel

The LMIO2‐CH64B is an interconnect for two line module slots on the rear of the chassis. The
LMIO2‐CH64B module provides metallic access to 32 four‐wire circuits per access module
installed for a maximum of 32 four‐wire circuits. Two 64‐pin male 90° champ connectors
attach to the LMIO2‐CH64B, and provide connection and stabilization between modules in
the Total Access 5000 Chassis and external cable connections that use 64‐pin connectors. For
standard entry, the cable exits the 90° connector hood on the pin 1 end of the male champ
connector.
LMIO2-CH50D Rear Panel

The LMIO2‐CH50D is an interconnect for two line module slots on the rear of the Total Access
5000 Chassis. The LMIO2‐CH50D provides metallic access to 8 four‐wire circuits per access
module installed for a maximum of 16 four‐wire circuits. Two 50‐pin male 90° champ
connectors attach to the LMIO2‐CH50D, and provide connection and stabilization between
modules in the Total Access 5000 Chassis and external cable connections that use 50‐pin
connectors. For standard entry, the cable exits the 90° connector hood on the pin 1 end of the
male champ connector.
LMIO2 HD DS1 Rear Panel

The LMIO2 HD DS1 Rear Panel is an interconnect for two line module slots on the rear of the
Total Access 5000 Chassis. The LMIO2 HD DS1 provides metallic access to 32 four‐wire
circuits per access module. Four 2 mm connectors provide access to the DSX loops. The upper
connectors provide the transmit pair, and the lower connectors provide the receive pair.
2-12 65K510DEP08-1A
LMIO2 High-Speed Rear Panel

The LMIO2 High Speed Rear Panel provides a high‐speed data path from a front panel SFP to
an adjacent GE 4‐Port, GE 8‐Port, or RPR Line Module.
In a packet ring configuration, the LMIO2 High‐Speed Rear Panel is used to provide a high
speed data link and handshake communications between two Total Access 5000 RPR Line
Modules. Both applications can also be used for automatic protection switching (APS).
LMIO2 DS3 BNC Rear Panel

The LMIO2 DS3 BNC Rear Panel is a series of I/O modules for the ATM DS3 Line Modules on
the rear of the Total Access 5000 chassis. The LMIO2 DS3 BNC Rear Panel provides Tx (out)
and Rx (in) BNC connectors for the ATM DS3.
NOTE
The LMIO2 DS3 BNC Rear Panel only supports the DS3 ATM Line Module.
Installing a DS3 BNC Rear Panel

To install the DS3 BNC Rear Panel, complete the following:
1. If installed, remove the rear blank panel.
2. Position the DS3 BNC Rear Panel on the rear alignment pins on the back of the Total
Access 5000 Chassis.
3. Using the 0.335 inch screws on the top and the 0.725 inch Captive Panel screw on the
bottom, secure the DS3 BNC Rear Panel to the chassis.
4. Install the transmit and receive DS3 cables.
! WARNING
To meet NEBS Level 3 and provide proper airflow and filtration, the
applicable rear panel must be installed in any occupied slot, and a front and
rear panel blank must be installed in any empty slots.
65K510DEP08-1A 2-13
DS3 8NR
1187442E1
Transmit
TX1 RX1
Receive
E
V TX2 RX2
E
N
S
L
O TX3 RX3
T
1187440L1
Redundant BNC Rear Panel
TX4 RX4
DS
32
B NR
11 N C
TX1 RX1
87
44
1L1
O TX2 RX2
D
Transmit D
S
L
Receive O TX3 RX3
T
Transmit
TX4 RX4
Receive
1187441L1
Non-Redundant BNC Rear Panel
Figure 2-7. Installing the Transmit and Receive DS3 Cables
2-14 65K510DEP08-1A
Install the Rear Panels

To install the push‐through panels, complete the following procedure (see Figure 2‐8 and
Table 2‐2):
1. 2. 3.
Figure 2-8. Installing the Rear Panels
Table 2-2. Rear Panel Installation Steps
Step Description
1 Position the rear panel on the back of the chassis so that the middle notch on the panel aligns
with the chassis alignment pin. The rear panel is provided with a set of captive screws.
These screws insert into the chassis’ screw mounting holes. Use a Phillips screwdriver to
tighten the captive screws, securing the panel to the chassis.
2 Install the Champ Mounting Bracket to the bottom of the 90° male champ connector using
one #4‐40 x 0.35 inch Captive Screw. The rear panel is provided with a set of #4‐40 x 0.35 inch
Captive Screws for installation of two connectors to the panel. Use two screws for each con‐
nector, one for the mounting bracket, the second to secure the connector to the panel (see
Step 3). Replace the Captive Screw provided with the cable if it is not a 0.35 inch screw.
3 Install the 90° male champ connector to the rear panel by sliding the mounting bracket down
into the panel slot, and securing with a #4‐40 x 0.35 inch Captive Screw at the top of the
champ connector.
! WARNING
To meet NEBS Level 3 and provide proper airflow and filtration, the
applicable rear panel must be installed in any occupied slot, and a front and
rear blank panel must be installed in any empty slots.
65K510DEP08-1A 2-15
Install the Front Panel Modules

This subsection details the description and installation of the Total Access 5000 front panel
modules.
SCM Description
The System Controller Module (SCM) provides a logical user interface to the entire system.
The SCM enables the provisioning of modules, alarm status monitoring, querying of perfor‐
mance data, and initiation of tests for any module in the shelf. The SCM provides various
interfaces for both local and remote management of the Total Access 5000 system. It supports
Simple Network Management Protocol (SNMP), Command Line Interface (CLI), Transaction
Language 1 (TL1), Telnet, and local craft access for the entire Total Access 5000 system.
SCM, Second Generation Description

The SCM, Second Generation (SCM G2) provides a logical user interface to the entire system.
The SCM G2 enables the provisioning of modules, alarm status monitoring, the querying of
performance data, and the initiation of tests for any module in the shelf. The SCM G2 provides
various interfaces for both local and remote management of the Total Access 5000 system,
including a secondary Ethernet port on the front panel with auto cross‐over correction that
supports a DHCP server. The SCM G2 supports SNMP, CLI, TL1, Telnet, SSHv2, and local
craft access for the entire Total Access 5000 system.
Bridging SCM Description

The Bridging SCM provides a logical user interface to the entire system. The Bridging SCM
enables the provisioning of modules, alarm status monitoring, the querying of performance
data, and the initiation of tests for any module in the shelf. The Bridging SCM provides
various interfaces for both local and remote management of the Total Access 5000 system. The
SCM supports SNMP, CLI, TL1, Telnet, SSHv2, and local craft access for the entire Total Access
5000 system. The SCM also supports Ethernet bridging between an Ethernet port and an
Inband Network interface.
Ethernet 2 Interface
The Ethernet port (ENET 2) on the front panel is a 10/100Base‐T port with auto cross‐over
connections that supports a DHCP server. This port can be used in a similar fashion as the rear
Ethernet port is traditionally used from a management perspective.
2-16 65K510DEP08-1A
Section 2, Installation - Install the Front Panel Modules
Install the SCM

To install the SCM, complete the following procedure:
NOTE
The SMIO3 must be installed before installing the SCM.
1. Pull the ejector latches, located on the upper and lower left‐hand side of the SCM front
panel, from the closed positions.
2. Hold the SCM by the front panel while supporting the bottom edge of the module with
the ejector latches opened to engage the chassis edges.
3. Align the module edges to fit in the lower and upper guide grooves for the slot labeled
12/SCM.
4. Slide the module into the module slot. Apply simultaneous thumb pressure at the top
and bottom of the module (to the right of the ejector latches) to ensure that the module is
firmly seated against the backplane of the chassis.
5. Secure the SCM in place by rotating the ejector latches into the locked positions.
GigE SM Description
The GigE Switch Module (SM) provides network data aggregation for the Total Access 5000
system. The GigE SM switches Ethernet traffic from the SFP inputs to the Access Module slots.
The GigE SM controls common system functions and communication between access modules
and the SCM. The GigE SM interfaces to the high speed backplane through the SMIO3.
Install the GigE SM

To install the GigE SM, complete the following:
NOTE
The SMIO3 must be installed prior to installing the GigE SM.
1. Pull the ejector latches, located on the upper and lower left‐hand side of the GigE SM
front panel, from the closed positions.
2. Hold the GigE SM by the front panel while supporting the bottom edge of the module
with the ejector latches opened to engage the chassis edges.
3. Align the module edges to fit in the lower and upper guide grooves of the Switch
Module slot labeled SM A or SM B.
4. Slide the GigE SM approximately halfway into the module slot and insert the copper or
optical cable into the SFP module.
5. Continue sliding the GigE SM into the chassis, applying simultaneous pressure at the top
and bottom of the module (to the right of the ejector latches) to ensure that the module is
firmly seated against the backplane of the chassis.
6. Secure the GigE SM in place by rotating the ejector latches into the locked positions.
7. Connect the copper or optical cables with the appropriate connector that matches the
SFP.
65K510DEP08-1A 2-17
8. Route the copper or optical cable to the cable tray located at the bottom of the module
slots and dress with appropriate ties.
Install the SFPs

! CAUTION
To install an SFP into an appropriate module, complete the following:
1. Inspect the SFP for damage. If damaged, file a claim with the carrier and then contact
ADTRAN Customer Service.
2. Insert the SFP into the SFP cage on the switch module, with the label from the
manufacturer facing to the right. Slide the SFP all the way into the cage until it clicks into
place.
3. Remove the safety cap from the optical connectors of the SFP.
4. Insert the fiber connector into the SFP until it clicks into place.
! CAUTION
Do not attempt to remove the SFP with the fiber installed.
32-Port SHDSL EFM Description

The 32‐Port SHDSL EFM provides 32 SHDSL links that can be bonded with Ethernet in the
first mile (EFM). Each SHDSL link is capable of data rates from 192 kbps to 5.7 Mbps in 64
kbps increments. For proper functionality, the 32‐Port SHDSL EFM must be installed in a Total
Access 5000 shelf that has a SM installed.
2-18 65K510DEP08-1A
EFM Bonding Protection Module Description

The EFM Protect Access Module provides EFM bonding engine protection for any EFM
SHDSL or DS1 EFM (1187802L1) access module installed in a Total Access 5000 system
beginning with System Release 3.2. These modules must support EFM bonding and have been
cross‐slot provisioned.
Install the EFM Bonding Protection Module
NOTE
ADTRAN recommends installing the EFM Protect Access Module in slot 11
or 21 of the Total Access 5000 chassis.
To install the EFM Protect Access Module, complete the following steps:
1. Pull the ejector latches on the EFM Protect Access Module, located on the upper and
lower left‐hand side of the EFM Bonding Protection Module front panel, from the closed
positions.
2. Hold the EFM Protect Access Module by the front panel while supporting the bottom
edge of the module with the ejector latches opened to engage the chassis.
3. Align the EFM Protect Access Module edges to fit in the lower and upper guide grooves
of the module slot.
4. Slide the EFM Protect Access Module into the module slot. Apply simultaneous thumb
pressure at the top and bottom of the module (to the right of the ejector latches) to ensure
that the module is firmly seated against the backplane.
5. Secure the EFM Protect Access Module in place by rotating the ejector latches into the
locked positions.
6. Install one of the following AMIO1 Blank Panels on the rear of the Total Access 5000
Chassis directly behind the EFM Protect Access Module:
• P/N 1187925L1 is used with the Total Access 5000 non‐shielded chassis (1187001L1)
• P/N 1187925G1 is used with the Total Access 5000 shielded chassis (1187001G1)
After installation is complete, the EFM Protect Access Module performs a series of initial‐
ization and self‐tests. Once the series of self‐tests are completed, the front panel LEDs reflect
the true state of the hardware.
65K510DEP08-1A 2-19
CH DS3 PPP/MLPPP 3-Port Line Module Description

The CH DS3 PPP/MLPPP 3‐Port Line Module provides channelized Point‐to‐Point Protocol
(PPP) and Multi‐Link Point‐to‐Point Protocol (MLPPP) network connectivity to a Total Access
5000 system by way of three channelized DS3 interfaces. Each channelized interface provides
connectivity for 28 DS1 channels.
PPP T1 Link to Ethernet

PPP operates at the data link layer and provides end‐to‐end connectivity for devices across a
point‐to‐point link. PPP is made up of a suite of protocols, including LCP, authentication, and
NCP (IPCP only), used to establish and maintain connectivity. The CH DS3 PPP/MLPPP 3‐
Port Line Module will forward frames from a T1 channel with PPP encapsulation to the
Ethernet uplink with a single S‐tag.
MLPPP groups can contain a maximum of eight T1 channels.
DS3 EFM 4-Port Line Module Description

The DS3 EFM 4‐Port provides four DS3 interfaces to the Total Access 5000 shelf. The DS3 EFM
4‐Port is designed for use as an end Ethernet First Mile (EFM) bonding interface that provides
aggregate Ethernet connectivity to additional Total Access 5000 Chassis or to NetVanta DS3
EFM Network Circuit Terminating Equipment (NCTE).
The DS3 EFM 4‐Port provides four DS3 signals consisting of digital data transmitted at 44.736
Mbps each.
NOTE
• The LMIO DS3 BNC Rear Panel must be installed prior to insertion of the
DS3 EFM 4‐Port into the chassis. In a 1:1 redundant configuration, the DS3
EFM 4‐Port modules must be installed in consecutive odd‐even slots.
• The LMIO DS3 BNC Rear Panel occupies two slots. Slot 11 cannot be used
since slot 12/SCM, SM A, and SM B slots are already occupied by the SMIO3
rear panel.
2-20 65K510DEP08-1A
DS3 EFM 3-Port Line Module Description

The DS3 EFM 3‐Port provides three DS3 interfaces to the Total Access 5000 shelf. The DS3
EFM 3‐Port is designed for use as an end EFM bonding interface that provides aggregate
Ethernet connectivity to additional Total Access 5000 Chassis or to NetVanta DS3 EFM NTE.
The DS3 EFM 3‐Port provides 3 DS3 ports that can support bonding up to 84 DS1s to form up
to a maximum of 42 EFM groups.
NOTE
• The LMIO DS3 BNC Rear Panel must be installed prior to insertion of the
DS3 EFM 4‐Port into the chassis. In a 1:1 redundant configuration, the DS3
EFM 4‐Port modules must be installed in consecutive odd‐even slots.
• The LMIO DS3 BNC Rear Panel occupies two slots. Slot 11 cannot be used
since slot 12/SCM, SM A, and SM B slots are already occupied by the SMIO3
rear panel.
T1 8-Port Line Module Description

The T1 8‐Port Line Module provides eight independent outside plant conventional T1 inter‐
faces to a customer or between Total Access 5000 systems with or without span power. Each
interface consists of a four‐wire T1 interface between a Time Division Multiplex (TDM)
network and an IP network.
The T1 8‐Port Line Module converts Ethernet packets to a TDM stream. The T1 interfaces are
used to transport the Ethernet packets from one Total Access 5000 shelf to another. The
module implements the Ethernet First Mile (EFM) protocol to fragment and defragment the
packets into bonded T1 channels of various bandwidths.
With a span supply daughter board, each T1 can supply –130 VDC or ±130 VDC (260 VDC
effective) to power conventional T1 repeaters. Each supply circuit is limited to 60 mA and
includes a Ground Fault Interrupt (GFI). The span supply can be configured as open, source,
or loopback for the span supply current.
The T1 8‐Port Line Module can operate in redundant mode where the left‐most module in the
chassis is the primary and the module to the right is the secondary.
NOTE
An LMIO2‐CH50D must be installed prior to the insertion of the T1 8‐Port
Line Module.
GE 4-Port Line Module Description

The GE 4‐Port Line Module interfaces to the Total Access 5000 shelf through individual
1‐Gbps backplane connections to each Total Access 5000 Switch Module. The GE 4‐Port Line
Module may be deployed in a redundant or non‐redundant configuration. A redundant
configuration is obtained through the use of the LMIO2 High‐Speed Line Module Rear Panel
(P/N 1187460E1). This module provides a control path between the redundant module pair. In
a non‐redundant configuration, the Total Access 5000 I/O Blank Panel (P/N 1187923L1) is
required.
The GE 4‐Port Line Module can also be used as a network extender for Ethernet traffic to
multiple Total Access 5000 shelves. In this configuration, the GE 4‐Port Line Module interfaces
65K510DEP08-1A 2-21
to a Total Access 5000 Switch Module. Small Form‐factor Pluggable (SFP) cages are provided
for inputs on the front panel of each module for maximum flexibility of the interfaces.
! CAUTION
ADTRAN can be used with the GE 4‐Port Line Module. ADTRAN cannot
certify system integrity with other SFPs.
NOTE
• A LMIO2‐CH64B must be installed prior to installing the GE 4‐Port Line
Module.
• For redundant configuration, the Total Access 5000 LMIO2 Rear Panel must
be installed prior to installing the GE 4‐Port Line Module. In a non‐
redundant configuration, the Total Access 5000 I/O Blank Panel must be
installed prior to installing the GE 4‐Port Line Module.
RPR Line Module Description

The RPR Line Module provides an optical ring transport option for the Total Access 5000.
The RPR Line Module provides uplink and downlink connectivity for the Total Access 5000
by way of a fiber ring. An RPR ring provides the same type of Class of Service (CoS)‐aware
connectivity as other uplink and downlink ports in the Total Access 5000 network, and
supports transport of all Total Access 5000 services, signaling, and timing to other Total Access
5000s stationed on the ring.
The RPR Line Modules work in pairs, with each Line Module providing either an East or a
West span interface. The pair of RPR Line Modules should be in adjacent slots of the chassis,
with the lower, odd numbered slot providing the West interface, and the higher, even
numbered slot providing the East interface.
! CAUTION
Due to compliance certification requirements, only 3.125 Gbps SFPs supplied
by ADTRAN are to be used with the RPR Line Module. ADTRAN cannot
certify system integrity with other SFPs.
NOTE
The LMIO2 Rear Panel must be installed in the slots on the back of the Total
Access 5000 Chassis that correspond to the slots in which the RPR Line
Modules will be installed; the LMIO2 must be installed prior to installing any
RPR Line Module.
Prior to installing the RPR Line Module, install an ADTRAN approved optical SFP module
into the required SFP port. The SFP must be capable of running at 3.125 Gbps line rate to
support a 2.5 Gbps data rate.
2-22 65K510DEP08-1A
NOTE
The RPR Line Module in the higher numbered slot is designated as the East
interface and the lower numbered slot is designated as the West interface.
Gigabit Ethernet 8-Port Line Module Description

The Gigabit Ethernet 8‐Port Line Module (GE 8‐Port LM) provides the EoF solutions similar to
the EoCu and EoTDM . The GE 8 Port LM allows subtending of network channel termination
equipment (NCTE) to provide Business Ethernet services. The GE 8 Port LM interfaces to the
SM GigE on the Total Access 5000 shelf backplane to provide 1G, 2.5G and 5G bandwidth.
The GE 8 Port LM can be deployed in a redundant configuration through the use of a Total
Access 5000 LMIO2 High Speed Rear Panel. The LMIO2 panel provides a control path
between the redundant modules.
When the GE 8Port LM is used for redundant applications, the GE 8]Port LMs must be
installed in adjacent slots with the left most GE 8 Port LM in an odd numbered slot (e.g., 1 and
2, 21 and 22).
The GE 8 Port LM has eight front panel SFP cages that provide inputs for maximum interface
flexibility.
The GE 8 Port LM can receive timing from the SM GigE via the backplane, and transmit this
timing out of any of the eight faceplate ports using the Sync E format. The module will not
receive timing on any of its faceplate ports.
NOTE
When using the GE 8‐Port LM to route data to an adjacent GE 8‐Port LM, an
LMIO2 High Speed Rear Panel must be installed prior to insertion of the GE
8‐Port LM into the Total Access 5000 Chassis.
DS1 PPP/MLPPP 32-Port Line Module Description

The DS1 PPP/MLPPP 32‐Port Line Module (DS1 PPP/MLPPP 32‐Port) provides 32 DS1 lines
and supports Point‐to‐Point and Multi‐Link Point‐to‐Point protocols. The 32 DS1s are
intended for in‐plant use and have no fuse or lightning protection.
NOTE
• The DS1 PPP/MLPPP 32‐Port can be installed in any slot (excluding slots
labeled 11, 12/SCM, SM A, and SM B) of the Total Access 5000 Chassis. If
installing only one DS1 PPP/MLPPP, it is recommended that it be installed
in an odd slot.
• Prior to installing the DS1 PPP/MLPPP 32‐Port, install a Line Module
Input/Output Dual HD DS1 Divided Pair Rear Panel or a Line Module
Input/Output Dual Champ 64‐Pin Bridged Rear Panel.
65K510DEP08-1A 2-23
Install the Access and Line Modules

Remove the Access Module Blank from the appropriate slot of the Total Access 5000 Chassis,
if present.
To install the module, reference Figure 2‐9.
Latches in open
position
Align with
guide grooves,
slide in until
seated
Latches in
closed position
Figure 2-9. Module Installation Steps
2-24 65K510DEP08-1A
Apply Power and Verify the Self-Test Passes

The Total Access 5000 SMIO3 delivers two –48 VDC buses to the SCM. The SCM operates
with both or either –48 VDC buses active.
All power, ground, and administrative wiring should now be completed on the Total Access
5000 shelf, and an SCM should be installed in slot 12/SCM of the shelf. To apply power,
complete the following procedure:
1. Insert a fuse into the fuse and alarm panel. The fuse should be selected with an amperage
appropriate for the intended use of the Total Access 5000 shelf.
2. Verify that the power‐on self‐test routine has completed successfully for each
component.
When power is applied, each component performs a series of initialization self‐tests.
Once completed, the front panel LEDs reflect the true state of the hardware. Refer to
Table 2‐3 to verify the self‐test LED indications.
Table 2-3. LED Self-test Indications
Label Status Description
SCM
PWR { Off No power to unit

z Green Power and initialization OK
z Red Power, temp, or boot failure
GigE SM

SHDSL EFM

z Yellow Power and out of service
EFM Bonding Protection Module

CH DS3 PPP/MLPPP 3‐Port

65K510DEP08-1A 2-25
DS3 EFM

DS3 EFM 4‐Port

z Green DS3 EFM 4‐Port passed self‐test and is set to In Service
4 Green Flashing DS3 EFM 4‐Port In Service and being accessed via menu
z Yellow Out of Service‐Unassigned or Out of Service‐Maintenance
4 Yellow Flash‐ Out of Service‐Unassigned or Out of Service‐Maintenance and
ing being accessed via menu
z Red DS3 EFM 4‐Port failed self‐test or initialization
DS3 EFM 3‐Port
PWR { Off No power is present

z Green DS3 EFM 3‐Port passed self‐test and is set to In Service
4 Green Flashing DS3 EFM 3‐Port In Service and being accessed via menu
z Yellow DS3 EFM 3‐Port Out of Service‐Unassigned or Out of Service‐
Maintenance
4 Yellow Flash‐ DS3 EFM 3‐Port Out of Service‐Unassigned or Out of Service‐
ing Maintenance and being accessed via menu
z Red DS3 EFM 3‐Port failed self‐test or initialization
T1 8‐Port

z Green Card Service State is set to In Service
4 Green Flashing Card Service State is set to In Service and an active menu session
is in progress
z Yellow Card Service State is Out of Service
z Red Power, temperature, or boot failure
GE 4‐Port

4 Green Flashing Card Service State is set to In Service and an active menu session
is in progress
RPR

2-26 65K510DEP08-1A
Section 2, Installation - Install the NetVanta 800/80000
Fan Module

z Red Major Alarm ‐ Multiple Fan Failure or Eminent Failure Detected
z Orange Minor Alarm ‐ Single Fan Failure or Eminent Failure Detected
Install the NetVanta 800/80000

• NetVanta 814 Description
• Installing the NetVanta 800/8000
NetVanta 814 Description

The NetVanta 814 T1/E1 Ethernet in the First Mile (EFM) is a Metro‐Ethernet Forum (MEF)
compliant, EFM bonded NTU designed for cost‐effective deployment of voice and data
services to small and medium size businesses supporting up to four four‐wire T1/E1 loops.
The NetVanta 814 accepts T1 or E1 network interfaces and delivers 10/100Base‐T Ethernet for
customer LAN extension. The NetVanta 814 terminates the T1/E1 loops in an RJ‐21 connector
and supports an aggregate data rate up to 6 Mbps (T1) or 8 Mbps (E1) over a single EFM
bonding group.

The NetVanta 818 T1/E1 Ethernet in the First Mile (EFM) is a MEF compliant, EFM bonded
NTU designed for cost‐effective deployment of voice and data services to small and medium
size businesses supporting up to eight four‐wire T1/E1 loops. The NetVanta 818 accepts T1 or
E1 network interfaces and delivers 10/100Base‐T Ethernet for customer LAN extension. The
NetVanta 818 terminates the T1/E1 loops in an RJ‐21 connector and supports an aggregate
data rate up to 12 Mbps (T1) or 16 Mbps (E1) over a single EFM bonding group.

The NetVanta 838 SHDSL EFM is a Metro‐Ethernet Forum (MEF) compliant, EFM bonded
NTU designed for cost‐effective deployment of data services to small and medium size
businesses supporting up to eight two‐wire SHDSL loops. The NetVanta 838 accepts SHDSL
or eSHDSL and delivers 10/100Base‐T Ethernet for customer LAN extension. The NetVanta
838 terminates the SHDSL loops in an RJ‐21 connector and supports data rates from 192 kbps
to 5.7 Mbps per copper pair. The NetVanta 838 provides an aggregate data rate up to 45.6
Mbps over a single EFM bonding group.
65K510DEP08-1A 2-27

The NetVanta 873 DS3 EFM is a MEF compliant, EFM bonded NTU designed for cost‐effective
deployment of data services to small and medium size businesses supporting up to three
DS3s. The NetVanta 873 accepts unchannelized DS3s and delivers 10/100Base‐T Ethernet, as
well as a Gigabit Ethernet SFP port for customer LAN extension. The DS3s are terminated in
BNC connectors and operate at the standard 44.736 Mbps data rate. The NetVanta 873
provides an aggregate data rate up to 134.208 Mbps over a single EFM bonding group.

The NetVanta 8044 Business Services (NTE) is a Gigabit‐Ethernet NTE or Ethernet Access
Device (EAD) that supports point to point deployment for Gigabit‐Ethernet services from the
Total Access 5000 platform or any other Ethernet‐service platform that supports standard‐
based Ethernet over Fiber (EoF) implementations. The ADTRAN EoF solution is a MEF
compliant solution supporting familiar operation tools based on Connectivity Fault
Management (CFM) and Performance Monitoring (PM) Ethernet OAM standards, as well as,
leading authentication standards such as RADIUS and TACACS+.
Installation Steps
To wallmount or rackmount the NetVanta 800, complete the following procedure:
1. Attach mounting brackets to the side of the NetVanta 800 in the correct orientation for
either rackmount or wallmount using the two screws provided for each bracket.
• To rackmount the unit, use the appropriate rack‐type screws to mount the NetVanta
800 into the rack.
• To wallmount the unit, secure the NetVanta 800 to the wall with appropriate screws.
2. Connect the frame ground from the frame ground lug on the upper right rear panel of
the NetVanta 800 to the equipment rack grounding screw or other appropriate
grounding connection.
3. Make power connections to the NetVanta 800.
NOTE
• A readily accessible disconnect device, such as a rackmount fuse and alarm
panel that is suitably approved and rated, should be incorporated into the
fixed wiring
• Connect to a reliably grounded ±48 VDC or ±24 VDC source that is
electrically isolated from the AC source
• The branch circuit overcurrent protection should be a slow‐blow fuse or
circuit breaker
a. Determine which fuse pairs are to supply power to the NetVanta 800.
b. Remove the fuses from the A and B slots for the pair.
c. Connect RET A, PWR A, RET B, and PWR B to the power connector. PWR refers to
respective ±48 VDC or ±24 VDC power sources; RET refers to respective returns.
4. Apply power and check voltages.
2-28 65K510DEP08-1A
Section 2, Installation - Install the NetVanta 800/80000
! WARNING
Installing fuses in the fuse and alarm panel at this stage will provide power to
the NetVanta 800. There will be power to pins and connectors on the rear
panel and inside the NetVanta 800. Exercise caution to avoid electrical shock.
a. Install appropriate fuses in the slots in the fuse and alarm panel that serves the
NetVanta 800.
b. Using a voltmeter, verify that the operating voltage is within the specifications for A
or B power feeds. For more information, refer to Specifications on the back.
c. Remove the fuses from the A and B slots for the pair.
5. If the customer site is equipped with local alarm capability, connect the CRIT (critical),
MAJOR, and MINOR alarm leads from the on‐site alarm equipment to the Common (C),
Normally Open (NO), or Normally Closed (NC) wire‐wrap terminals on the NetVanta 800
rear panel.
These connections will enable audible and/or visual indicators from the on‐site alarm
equipment.
65K510DEP08-1A 2-29
2-30 65K510DEP08-1A
Section 3
Common Provisioning

This section details the common provisioning for a Total Access 5000 System. It contains
general information for provisioning the System Controller Module (SCM) and GigE Switch
Module (GigE SM).
In this Section
Topic See Page
Log On to the Total Access 5000 3‐2
Set the Date and Time 3‐3
Provision the SNMP Interface 3‐3
Set the TID 3‐4
Provision the Node Number and Network Name 3‐6
Provision the GigE SM 3‐6
Provision the Timing Source 3‐6
SNTP Provisioning 3‐18
Configure Local User Accounts 3‐24
65K510DEP08-1A 3-1
Log On to the Total Access 5000

For initial deployment, only craft access is available. A serial cable with a male DB‐9 connector
on the Total Access 5000 end is required.
To log on to the Total Access 5000 command line interface, complete the following:
1. Set the parameters of the VT100 terminal to the following settings:
• 9600 baud rate
• 8‐data bits
• No parity
• 1‐stop bit
• No flow control
2. Plug the male end of the data cable into the Total Access 5000 . Make a connection to the
VT100 terminal or a PC running emulation software as appropriate for the equipment.
3. After completing the prerequisite procedures above, pressing any key displays the logon
prompt.
The Total Access 5000 System Logon prompt displays the following information:
User Access Verification
Username:
NOTE
The account name and password are case sensitive.
Default accounts are ADMIN, READONLY, READWRITE, and TEST. The
default password for each of these accounts is PASSWORD. The privilege to
change passwords, account names, and privileges are included in the
ADMIN account.At the Username field, input the Username (ADMIN), and
press ENTER.
4. At the Password field, input the Password (PASSWORD), and press ENTER.
5. Upon entering the correct password, the Total Access 5000 CLI introduction banner
displays the following information:
User Access Verification
Username:ADMIN
Password:********
Last Login Date : Nov 10 2008 10:19:17
Last Login Type : IP Session(CLI) - 192.168.1.3
Login Failures : 0 (Since Last Login)
: 14 (Total for Account)
TA5000>
6. Type enable, and press ENTER to enable the privileged commands.
The Total Access 5000 system displays the following information:
TA5000>enable
TA5000#
3-2 65K510DEP08-1A
Section 3, Common Provisioning - Set the Date and Time
NOTE
The privileged commands (Enable prompt) are designated by the # prompt.
Set the Date and Time

To set the date and time, complete the following:
1. From the Enable prompt, type config term, and press ENTER.
2. From the Global Configuration prompt, type clock set <HH:MM:SS> <1-31> WORD
<2000-2036>, and press ENTER.
3. Type exit, and press ENTER to return to the Enable prompt.
Provision the SNMP Interface

The SNMP interface is configured to provide almost all items accessible through the Total
Access 5000 CLI. Status and performance monitoring parameters are read‐only elements,
whereas configuration items are read‐write. The only items that may not be changed through
SNMP are network management elements that would interfere with proper operation of the
Ethernet or Inband interfaces, such as IP addresses, default routes, etc.
NOTE
The SNMP information is required in order for the Total Access EMS to
interface with the Total Access 5000.
To provision the SNMP information, complete the following:
1. From the Enable prompt, type config term and press ENTER to access the Global Con‐
figuration prompt.
2. From the Global Configuration prompt, type snmp-server host A.B.C.D, and press
ENTER to add an SNMP server entry to the Total Access 5000.
3. From the Global Configuration prompt, type snmp-server chassis-id WORD to set
the System Name, and press ENTER.
NOTE
The chassis name is entered using up to 55 alpha‐numeric characters
beginning with a letter character with no spaces allowed.
4. From the Global Configuration prompt, type snmp-server location WORD to set the

System Location to the desired location name, and press ENTER.
NOTE
The SNMP server location allows spaces, special characters, and upper and
lower case characters. The SNMP server location is limited to 55 alpha‐
numeric characters.
65K510DEP08-1A 3-3
5. If desired, type snmp-server chassis-id-tid-sync to enable TID/SysName Sync,
and press ENTER.
NOTE
• The TID/SysName Sync provisioning is a setting that forces the TL1 TID
and SNMP System Name to be identical. If Sync is enabled, a change to one
of these settings forces the other to be changed as well.
• If the TID/SysName Sync is enabled, it converts the system name to all caps
and the only special character allowed is “_”.
Set the TID

To set the Target Identifier (TID), complete the following procedure:
1. From the Global Configuration prompt, type tl1, and press ENTER to access the TL1 Con‐
figuration prompt.
2. From the TL1 Configuration prompt, type tid WORD, and press ENTER to set the TID.
NOTE
The TID name is entered using up to 20 alpha‐numeric characters beginning
with a letter character. The TID name must be unique and not duplicate the
Network Name.
3. Type end, and press ENTER to return to the Enable prompt.
3-4 65K510DEP08-1A
Section 3, Common Provisioning - Provision the Node Number and Network Name
Provision the Node Number and Network Name

The default Total Access 5000 Node number is 0. When the Node number is 0, the SCM does
not recognize any other modules in the shelf.
To set the Node number, complete the following procedure:
1. From the Enable prompt, type configure terminal, and press ENTER to access the Glo‐
bal Configuration prompt.
! CAUTION
The factory default setting for Network is Node 0. For single‐node
applications (EoCu, EoTDM, BSM, etc.), the node number is set to 1.
2. From the Global Configuration prompt, set the node number by typing node-number
3. From the Global Configuration prompt, set the network name by typing network-name
WORD, and press ENTER.
NOTICE
The Network Name must not duplicate the TID/chassis‐id. If using Total
Access EMS the Network Name must be a unique name for node discovery.
65K510DEP08-1A 3-5
Provision the GigE SM

• Provision the GigE SM administration state
• Provision the network ports
• Provision the network port modes
• Provision the LACP switchover mode
• Provision for Link Aggregation Control Protocol (LACP)
• Provision the timing source
Provision the GigE SM Administration Status

For traffic to pass, the GigE SM module must be enabled.
Table 3‐2 displays the three administration states and the equivalent service states from prior
releases.
Table 3-2. GigE SM Administration States
Command Previous Description
no shutdown In Service In the no shutdown state, traffic passes

and alarms are generated.
shutdown maintenance Out of Service, In the shutdown maintenance state,

Maintenance traffic passes but no alarms are generated.
Alarms are suppressed and no evidence of
the alarm is shown.
shutdown Out of Service, In the shutdown state, no traffic passes

Unassigned and no alarms are generated.
To set the module administration state, complete the following procedure:
2. From the Global Configuration prompt, provision the module administration state by
entering one of the following commands:
• Type no slot shutdown <shelf/slot>, and press ENTER to take a card In Service
NOTE
• If connected to the shelf where the module resides, the shelf number is
typically 1.
• This is the slot of the module being configured. Valid values for the Switch
Modules are A and B.
• Type slot shutdown maintenance <shelf/slot>, and press ENTER to take a

card Out of Service, Maintenance
• Type slot shutdown <shelf/slot>, and press ENTER to take a card Out of Service,
Unassigned
3-6 65K510DEP08-1A
Section 3, Common Provisioning - Provision the GigE SM
3. Type end, and press Enter to return to the Enable prompt.
Provision the Network Ports

To configure the network port administration states, complete the following procedure:
NOTE
This is a single node setup, therefore Network Port 2 will be set to the Out of
Service‐Unassigned state. This prevents any unnecessary alarms for the
unused network port.
2. From the Global Configuration prompt, type interface gigabit-ethernet 1/A/1,
and press ENTER to access the slot A, Net 1 Configuration prompt.
3. Type no shutdown, and press ENTER to set the port to In Service.
4. Type interface gigabit-ethernet 1/A/2, and press ENTER to access the slot A Net 2
Configuration prompt.
5. Type shutdown, and press ENTER to set the port to Out of Service, Unassigned.
6. Type exit, and press ENTER to return to the Global Configuration prompt.
7. Type interface gigabit-ethernet 1/B/1, and press ENTER to access the slot B, Net 1
9. Type interface gigabit-ethernet 1/B/2, and press ENTER to access the slot B, Net 2
10. Type shutdown, and press ENTER to set the port to Out of Service, Unassigned.
NOTE
The GigE SM NET 1 LED should be green. If not, perform physical layer
diagnostics.
65K510DEP08-1A 3-7
Provision the Network Port Modes

• Provision the network port modes
• Provision the gigabit‐ethernet speed
Network Port Mode Descriptions

In the Total Access 5000 System Release 5.1, a Switch Module Gigabit‐Ethernet network
interface can operate in four modes. Refer to Table 3‐3 for the GigE SM Network Operation
modes.
Table 3-3. GigE SM Network Operation Modes
Mode Description
Network Interface If a port is designated as the Ethernet default interface and the network
node is set to 1, it is automatically placed in Network Interface mode and
is not designated as downlink.
Unused If a port is not designated as the Ethernet default interface or set as a
downlink, it is unused.
Uplink If a port is designated as the Ethernet default interface and the network
node is greater than 1, it is automatically placed in Uplink mode and is
not designated as downlink. Equivalent to enabling Upstream Chaining
in prior Total Access 5000 releases.
Downlink A port is set in downlink as follows:
1. From the Enable prompt, type configure terminal, and press
ENTER to access the Global Configuration prompt.
2. From the Global Configuration prompt, type interface
gigabit-ethernet <shelf/slot/port>. and press ENTER.
3. From the Gigabit Ethernet Interface Configuration prompt, type
downlink, and press ENTER to set the port to downlink.
Equivalent to enabling Downstream Chaining in prior Total Access 5000
releases. This is the only mode that is not a result of Ethernet default
interface and node number provisioning. It must be explicitly set.
Table 3‐4 displays the Total Access 5000 network port system defaults.
Table 3-4. Network Port Service State
Module and Port System Default
SM A, Net 1 Ethernet default interface
SM A, Net 2 Disabled
SM B, Net 1 Ethernet default interface
SM B, Net 2 Disabled
3-8 65K510DEP08-1A
Once the node number is provisioned, the network ports are configured as follows:
• If the node is set to 1, then Net 1 is in Network Interface mode, and Net 2 is unused
• If the node is greater than 1, then Net 1 is in Uplink mode, and Net 2 is unused
To designate Net 2 as the default interface, complete the following procedure:
2. From the Global Configuration prompt, type ethernet default interface
gigabit-ethernet 1/A/2. and press ENTER.
NOTE
• If Net 2 is designated as the default Ethernet interface, then Net 1 becomes
unused.
• If it is to be used, LACP still needs to be enabled on the active ports.
Port Mode Configuration Examples

This section displays a list of port mode configuration examples.
Example #1
The steps to turn up a system with Net 1 as the Network Interface and Net 2 as Unused (from
the defaults) are:
#configure terminal
(config)#node number 1
(config)#exit
#
Example #2
The steps to turn up a system with Net 1 as the Network Interface and Net 2 as a Downlink
are:
#configure terminal
(config)#interface gigabit-ethernet 1/A/2
(config gig-eth 1/A/2)# downlink
(config gig-eth 1/A/2)# exit
(config)#exit
#
Example #3
The steps to turn up a system with Net 1 as Uplink and Net 2 as Unused are:
#configure terminal
(config)#exit
#
65K510DEP08-1A 3-9
Example #4
The steps to turn up a system with Net 1 as Uplink and Net 2 as Downlink are:
#configure terminal
(config)#interface gigabit-ethernet 1/A/2
(config gig‐eth 1/A/2)# downlink
(config gig‐eth 1/A/2)# exit
(config)#exit
#
Provision the Gigabit-Ethernet Speed

To provision the Gigabit‐Ethernet speed, complete the following:
and press ENTER to access the GigE SM in slot A and the Net 1 Configuration prompt.
NOTE
If slot B is the active SM, use 1/B/1 for the <shelf/slot/port> syntax.
3. Provision the Gigabit‐Ethernet speed by performing one of the following commands:
• Type speed 1000, and press ENTER to configure the gigabit ethernet for 1000 Mbps
operation
• Type speed auto, and press ENTER to enable the auto‐negotiation of speed
NOTE
• The default Gigabit‐Ethernet speed is auto.
• The Auto Negotiation setting on the Total Access 5000 should be consistent
with the associated upstream switch port’s Auto Negotiation setting.
• For more information on LACP, refer to “Appendix A, Link Aggregation
Guide”.
3-10 65K510DEP08-1A
Provision the LACP Switchover Mode

A difference in the way that Cisco and Juniper switches handle LACP messaging requires a
provisioning option, called lacp grammar standby‐aggregation. To set this option, complete
the following:
and press ENTER to access the Gigabit‐Ethernet prompt for the active SM, network port 1.
NOTE
If slot B is the active SM, use 1/B/1 for the <shelf/slot/port> designator.
3. Depending on the switch, perform one of the following:
• If the Total Access 5000 is connected to a Cisco switch, type no lacp grammar
standby-aggregation, and press ENTER.
NOTE
The no version of the lacp grammar command is the default value.
• If the Total Access 5000 is connected to a Juniper switch, type lacp grammar
standby-aggregation, and press ENTER.
65K510DEP08-1A 3-11
Provision LACP
When connecting the GigE SM to the provider network interface element (normally a switch
or a router), multiple configuration options can be used. The current BSM application
connects to the external switch with a single Switch Module port (NET 1) from each Switch
Module, using Link Aggregation Control Protocol (LACP) to convey Active/Standby status of
each GigE SM port.
NOTE
The maximum data rate for the network interface is still 1 Gbps. The use of
LACP is independent of using link aggregation to obtain greater than 1 Gbps
network connection. This LACP use is often called hot‐standby LACP.
Table 3‐5 displays the three LACP modes.
Table 3-5. LACP Modes
Command Description
lacp mode active The GigE SM always sends LACP packets along the configured links.
lacp mode passive The GigE SM will not send LACP packets until it has first received an

LACP packet.
no lacp mode LACP is disabled for this port.
To provision for LACP, complete the following procedure:
and press ENTER to access the GigE SM in slot A and the Net 1 Configuration prompt.
NOTE
If slot B is the active SM, use 1/B/1 for the <shelf/slot/port> syntax.
3. Provision the LACP Mode by performing one of the following commands:
• Type lacp mode active, and press ENTER to set the port LACP mode to active
• Type lacp mode passive, and press ENTER to set the port LACP mode to passive
• Type no lacp mode, and press ENTER to set the port LACP mode to disabled
3-12 65K510DEP08-1A
Section 3, Common Provisioning - Provision the Timing Source
Provision the Timing Source

To set the timing sources (primary and secondary) to BITS, complete the following procedure:
NOTE
The primary and secondary timing sources can be different depending on the
configuration.
2. From the Global Configuration prompt, type system-timing <shelf>, and press ENTER
to access the System Timing Configuration prompt.
NOTE
<shelf> is the node number of the shelf being provisioned, typically 1.
3. From the System Timing Configuration prompt, set the primary timing source to Ext A
by typing source primary external primary, and press ENTER.
4. From the System Timing Configuration prompt, set the secondary timing source to Ext B
by typing source secondary external secondary, and press ENTER.
65K510DEP08-1A 3-13
Configure SCM Management

• Definition of VLAN
• Provision the IP address for the SCM
VLAN Definition
A virtual local area network (VLAN) is a group of hosts with a common set of requirements
that communicate as if they were attached to the same wire, even though they may actually
physically be connected to different segments of a LAN.
The Inband Management VLAN is used to handle all management traffic, such as SNMP and
telnet traffic to the Total Access 5000.
Provisioning the IP Network Interface

The IP Network Interface parameters that must be entered are dependent on the interface
type.
• Inband Interface
• Ethernet Interface
Provision the Inband Interface

To set the Inband Interface for the shelf, complete the following procedure:
2. From the Global Configuration prompt, type system-management-evc, and press ENTER
to access the System Management EVC Interface Configuration prompt.
3. From the System Management EVC Interface Configuration prompt, type s-tag <1-
4094>, and press ENTER to set the system management VLAN to the desired ID.
4. From the System Management EVC Configuration prompt, type men-pri <0-7>, and
press ENTER to set the system management VLAN priority to the desired priority.
Use the men‐pri <0‐7> command to set the priority given to frames sourced by the
system. The priority value appears as the P‐bit in the VLAN tag of the frame.
5. From the System Management EVC Configuration prompt, type ip address A.B.C.D
A.B.C.D, and press Enter to configure the Inband IP address and subnet mask.
6. From the System Management EVC Configuration prompt, type no shutdown, and
press ENTER to enable the system management EVC.
7. Type exit, and press Enter to return to the Global Configuration prompt.
8. From the Global Configuration prompt, type ip route A.B.C.D A.B.C.D A.B.C.D,
and press Enter to set the gateway for the inband interface, where the first value is the IP
address of the Inband interface, the second value is the subnet mask, and the third value
is the gateway IP address for the inband interface.
3-14 65K510DEP08-1A
Section 3, Common Provisioning - Configure SCM Management
NOTE
The gateway should be the router to which the interface is connected, or the
first routing hop outside of the Total Access 5000 for the interface. A static
entry for the gateway is added to the route table when the gateway is
configured, and that IP address is used as the first hop for routing on that
interface.
9. Type exit, and press ENTER to return to the Enable prompt.
Provisioning the Ethernet Interface

To set the Ethernet interface for the shelf, complete the following procedure:
2. From the Global Configuration prompt, type interface ethernet 1/S/1, and press
ENTER to access the Ethernet Interface Configuration prompt.
3. From the Ethernet Interface Configuration prompt, type ip address A.B.C.D
A.B.C.D, and press ENTER to configure the Ethernet interface IP address and subnet
mask.
4. From the Ethernet Configuration prompt, type no shutdown, and press ENTER to return
to enable the Ethernet Interface Configuration prompt.
6. From the Global Configuration prompt, type ip route A.B.C.D A.B.C.D A.B.C.D,
and press Enter to set the gateway for the Ethernet interface, where the first value is the
IP address of the Ethernet interface, the second value is the subnet mask, and the third
value is the gateway IP address for the Ethernet interface.
NOTE
The gateway should be the router to which the interface is connected, or the
first routing hop outside of the Total Access 5000 for the interface. A static
entry for the gateway is added to the route table when the gateway is
configured, and that IP address is used as the first hop for routing on that
interface.
NOTE
If both the Inband and Ethernet interface IP addresses are provisioned and
enabled, they must be on different subnets.
65K510DEP08-1A 3-15
Provision the Default Gateway

To provision the default gateway, complete the following procedure:
2. From the Global Configuration prompt, type ip default-gateway A.B.C.D, and
press ENTER to set the system default gateway.
NOTE
The default gateway must match the gateway address of either the Inband or
Ethernet interface, which is typically the router to which the interface is
connected.
Provision the S-tag Tag Protocol Identifier (TPID)

The S‐tag TPID is typically a function of the type of external switch or router that is connected
to the GigE SM. If not set, set the S‐tag TPID to the desired value. The S‐tag TPID indicates the
Ethertype used to identify the S‐VLAN tags. To change the S‐tag TPID, complete the following
procedure:
2. From the Global Configuration prompt, type ethernet s-tag-tpid HHHH, and press
ENTER to set the S‐tag TPID to HHHH, where HHHH is in hexadecimal.
NOTE
• The valid TPID ranges are 0x8000‐0xFFFF using 4 hexadecimal digits.
• The default TPID value is 0x8100.
3-16 65K510DEP08-1A
Section 3, Common Provisioning - Provision the Class of Service (CoS) Map
Provision the Class of Service (CoS) Map

Each layer 2 interface in the Total Access 5000 (Gigabit‐Ethernet, Ethernet, EFM bonding
group, etc.) has four quality of service (QoS) priority queues for traffic egressing the interface.
Traffic is assigned to these queues based upon a Total Access 5000 system‐wide configurable
option. The Total Access 5000 uses the outer 802.1Q VLAN p‐bits to determine to which
queue each Ethernet frame should be assigned. The p‐bits‐to‐queue mapping is done using
the qos cos‐map command. Complete the following procedure:
1. From the Enable prompt, type configure terminal, and press ENTER to get to the Glo‐
2. From the Global Configuration prompt, type qos cos-map <queue_number> <L2 COS
#1> <L2 COS #2> ..., and press ENTER.
Table 3‐6 displays the CoS map syntax.
Table 3-6. CoS Map Syntax
Syntax Definition
queue_number The Total Access 5000 queue number (0‐3) to which the L2 CoS
value(s) should be assigned. 0 holds the lowest priority queue, and 3
holds the highest.
L2 COS #n All 8 possible values can be specified. This list of CoS/PCP values can
be mapped to the specified QoS queue level.
NOTE
For EoCu services, the Total Access 5000 system pushes the CoS mapping
down to any subtended NetVanta 800 series, so that the mapping applies
uniformily.
65K510DEP08-1A 3-17
SNTP Provisioning
This section details the following information related to the Simple Network Timing Protocol
(SNTP) as used on the Total Access 5000 shelf:
• Provision SNTP
• Disable SNTP
• View SNTP Status
Provision SNTP
If desired, an SNTP server can be used by the Total Access 5000 to get its date and time. Out of
the box, SNTP is disabled. It is automatically enabled once an SNTP server is defined (i.e. it
attempts to connect to the server and use it). Setting up SNTP has two steps:
• Defining the SNTP server(s)
• Defining the MSAP local offset from GMT
To provision SNTP, complete the following steps:
2. From the Global Configuration prompt, type clock timezone WORD <-23-23> <0-
59>, and press ENTER to set the clock timezone.
Use the clock timezone WORD <‐23‐23> <0‐59> command to set the name of the time
zone, the hours offset, and the minutes offset from the UTC.
NOTE
The WORD input designates the time zone. This is only useful for human
readability.
3. From the Global Configuration prompt, type ip sntp server A.B.C.D, and press

ENTER to define an SNTP server. If no server was previously defined, this command also
enables SNTP.
4. Type exit, and press ENTER to return to the enable prompt.
Disable SNTP
To disable SNTP, complete the following steps:
2. From the Global Configuration prompt, type no ip sntp server A.B.C.D, and press
ENTER to delete all SNTP servers and, thus, disable SNTP.
NOTE
The IP address (A.B.C.D) is optional in this command since there is only one
SNTP server defined per Total Access 5000.
3. Type exit and press ENTER to return to the Enable prompt.
3-18 65K510DEP08-1A
Section 3, Common Provisioning - Provision Authentication, Authorization, and Accounting (AAA)
View SNTP
From the Enable prompt, type show sntp, and press ENTER to view the SNTP status.
Provision Authentication, Authorization, and Accounting

(AAA)
AAA contains the following three elements:
• Authentication is the process of logging into the network element. Upon entering a
username and password, the local account database or the TACACS+ and/or RADIUS
servers determine if the log on attempt is successful for the given user.
• Command Authorization provides a process to allow a TACACS+ server to grant or deny
access to a user on a per‐command basis. When a user enters a CLI command, but before
the command is executed, a TACACS+ server is queried to determine if the command can
be executed by that user.
• Command Accounting is the process of notifying a TACACS+ server when the user enters
a CLI command. It allows the TACACS+ server to maintain logs of CLI command activity
for each user.
If using TACACS+ for authentication, then authorization and/or accounting can optionally be
enabled or disabled. The executable CLI commands depend on whether command authori‐
zation is enabled or disabled.
For authentication, both RADIUS and TACACS+ can return a response that requests more
information from the user (such as a challenge question), in which case the product displays
the message from the server to the user, and awaits input from the user. Multiple challenge
transactions can be made during an authentication request.
Authentication also occurs when the user enters enable from the Enable prompt. If
TACACS+ is contained in the authentication login method list, then upon entering enable
from the Enable prompt, the product transmits another authentication request to the
TACACS+ server. As with login, the server can respond with a message requesting more infor‐
mation, such as a password. Successful authentication in this process results in the user being
escalated in privilege level, and granted access to the Enable prompt.
When a user attempts to access the Total Access 5000, the Total Access 5000 connects to the
TACACS+ or RADIUS server to verify the user and what the user can do. The Total Access
5000 must be configured to talk to the correct server, along with the actions to take if the server
cannot be contacted.
Configure TACACS+ Server(s)

To use a TACACS+ server, the server parameters must be configured in the Total Access 5000
so that the Total Access 5000 can communicate with the server.
The Total Access 5000 supports up to 4 TACACS+ servers configured in a single default group.
The servers contain a sequence number that governs the order in which communication is
attempted. When a server is added to the system, it is entered into the default TACACS+
server list as the next available server after any existing servers. A server’s sequence number
can be modified. A server having a sequence number of zero is never queried.
To configure a TACACS+ server, complete the following procedure:
65K510DEP08-1A 3-19
2. From the Global Configuration prompt, type tacacs-server host A.B.C.D key

WORD port <1-65535> timeout <1-30>, and press ENTER to configure the TACACS+
server.
NOTE
• Any combination of shared_key, port_num, and timeout_secs can be
specified, including listing none of them at all. Only the parameters
specified will be changed from the global TACACS+ default values (or
whatever their current values are).
• If the IP address is that of a new TACACS+ server, a new server will be
added to the TACACS+ server list. All server parameters will be defaulted
to the global TACACS+ value, and then overwritten with whichever
parameters are specified after the IP address. If the server is an existing
server, the parameters specified will be modified.
3. Type tacacs-server host A.B.C.D name WORD, and press ENTER to set the TACACS+

server hostname.
4. To set the server sequence number (or priority), type tacacs-server host A.B.C.D
sequence-number <0-4>, and press ENTER, where priority = 1 (primary server), 2,
(secondary server), and so on up to 4.
NOTE
Only 0 can have mulitple servers. Sequence numbers 1 ‐ 4 can only have one
server for each sequence number at any given time. To swap the sequence
number of two servers, temporarily set the sequence number of one server to
0, change the other server’s sequence number, and then change the sequence
number of the first server from 0 to the new desired number.
If the sequence number is not specified, the system automatically orders the servers
(from primary on down) as they are entered, so the specification of the sequence number
is only necessary if the priority order needs to be changed. A server with a sequence
number of zero is effectively disabled.
5. To delete a TACACS+ server from the server list, type no tacacs-server host
A.B.C.D, and press ENTER.
3-20 65K510DEP08-1A
Configure Authentication Method

The Total Access 5000 uses the following priority of authentication methods:
1. If enabled, the Total Access 5000 attempts to authenticate the user via Emergency Entry
Port (EEP). If EEP is not enabled or the username supplied is not a supported EEP user‐
name, the Total Access 5000 proceeds to the next step.
The EEP is a local authentication method that can be employed in scenarios where all
other authentication methods are unsuccessful. When EEP is enabled, the user can enter
a predetermined username CHALLENGE to gain access to the system. The user is then
presented a challenge key. The correct response to this challenge key can be acquired
from ADTRAN Technical Support. If the correct response is issued, then the user is
logged in with local Admin privileges.
When EEP is enabled and the CHALLENGE username is entered at the login prompt, the
network element presents the challenge key immediately, and does not request a
password. This is true regardless of how the authentication login method list is
configured.
NOTE
Use caution when disabling EEP. Prior to disabling EEP, considerations must
be given to options for recovery during conditions when all other
authentication methods deny access.
2. If enabled, the Total Access 5000 attempts to authenticate the user using the configured
TACACS+ server(s). If TACACS+ is not enabled or the Total Access 5000 is unable to
connect to a TACACS+ server, the Total Access 5000 proceeds to the next step.
3. If enabled, the Total Access 5000 attempts to authenticate the user using the configured
RADIUS server(s). If RADIUS is not enabled or the Total Access 5000 is unable to connect
to a RADIUS server, the Total Access 5000 proceeds to the next step.
4. If enabled, the Total Access 5000 authenticates the user using the locally programmed
user accounts. If local authentication is not enabled, the Total Access 5000 rejects the
login attempt.
NOTE
If the Total Access 5000 connects to a TACACS+ server or, then, a RADIUS
server, and the server rejects the login attempt, the Total Access 5000 does not
proceed to the next authentication method. It rejects the login attempt. A
fallback to the next method occurs only if a timeout occurs on all servers of a
given protocol (TACACS+ or RADIUS).
To configure the authentication method(s) to be used, complete the following procedure:
2. From the Global Configuration prompt, type aaa authentication login default
group tacacs+ [group radius|local], and press ENTER.
65K510DEP08-1A 3-21
NOTE
The methods group radius, group tacacs+, and local are all optional,
but at least one method must be specified. Only the methods listed are used.
Authentication Examples
The following example enables TACACS+ and local authentication, but disables RADIUS
authentication.
TA5000#configure terminal
TA5000(config)#aaa authentication login default group tacacs+ local
TA5000(config)#exit
TA5000#
The following example only enables local authentication, disabling all remote authentication
methods.
TA5000(config)#aaa authentication login default local
TA5000(config)#exit
TA5000#
Configure TACACS+ Authorization

If per‐command authorization is enabled for a group of commands, the Total Access 5000
connects with the TACACS+ server each time a command is entered to verify that the user has
permission to execute the command.
NOTE
TACACS+ authorization only occurs when TACACS+ authentication is used.
Commands are grouped as follows:
• Level 0 commands: The only level 0 commands are enable, disable, end, exit, and
logoff. These commands are not subject to remote command authorization.
• Level 1 commands: All commands that are native to the Root prompt (prior to the enable
command being issued) are Level 1 commands. These include most show commands.
• Level 15 commands: All remaining commands not designated as Level 0 or Level 1. This
includes all application commands, all commands native to the Enable prompt (not also
present at the Root prompt prior to the enable command being used), and all commands
at and beyond the Global Configuration prompt.
• Level 15 configuration commands: These commands are at or beyond the Global
To configure the authorization for a level, complete the following procedure:
2. From the Global Configuration prompt, type aaa authorization commands <1,15>
default group tacacs+, and press ENTER to enable TACACS+ authorization for a
command level.
3-22 65K510DEP08-1A
NOTE
Either of the following commands disable TACACS+ authorization for a
command level:
• aaa authorization commands <1,15> default none

• no aaa authorization commands <1,15>
After any of the above commands are issued to enable or disable remote authorization of all
level 15 commands, command authorization for commands at and beyond the Global Config‐
uration prompt can be separately enabled or disabled via the following:
• aaa authorization config-command
• no aaa authorization config-command
The following command sequence enables TACACS+ authorization for all level 15 commands
except for those at or beyond the Configure Terminal prompt:
• aaa authorization command 15 default group tacacs+
• no aaa authorization config-command
NOTE
Although no authorization is performed for commands at or beyond the
configuration prompt, the configure terminal command does undergo
TACACS+ authorization.
The following command sequence enables TACACS+ authorization for all level 15 commands
except for those prior to the Configure Terminal prompt:
• aaa authorization command 15 default none
• aaa authorization config-command
Configure User Activity Accounting

Command accounting is configured similarly to command authorization. The commands are
grouped in the same manner as authorization.
The following rules apply:
NOTE
TACACS+ accounting only occurs when TACACS+ authentication is used.
• Level 0 commands: Not subject to remote accounting
• Level 15 config commands: There is no config‐command accounting command. These
follow level 15 rules
To configure accounting for a level, perform the following:
• From the Global Configuration prompt, type aaa accounting commands <1,15>
default stop-only group tacacs+, and press ENTER to enable TACACS+ accounting
for a command level.
65K510DEP08-1A 3-23
Accounting Example
In the following example, level 1 and 15 command accounting is enabled.
TA5000(config)#aaa accounting commands 1 default stop-only group
tacacs+
TA5000(config)#aaa accounting commands 15 default stop-only group
tacacs+
Configure Local User Accounts

• Create a new user account
• Modify an existing user account
• Delete an existing user account
• Configure the password complexity
Create a New User Account

To create a new local user to the Total Access 5000, complete the following procedure:
2. From the Global Configuration prompt, type security, and press ENTER to access the
Security Configuration prompt.
3. From the Security Configuration prompt, type username WORD, and press ENTER to create
a new user and access the User Configuration prompt.
4. From the User Configuration prompt, type password, and press ENTER to access the
Password Entry prompt.
5. From the Password Entry prompt, type the password for the user, and press ENTER.
6. From the User Configuration prompt, type privilege [admin|config|read-
only|read-write|test], and press ENTER to set the user privilege level.
The default value when a new user is created is read‐only.
7. From the User Configuration prompt, type no disable to enable the username.
Modify an Existing User Account

To modify an existing user account on the Total Access 5000, complete the following
procedure:
3. From the Security Configuration prompt, type username WORD, and press ENTER to access
an existing user account and access the User Configuration prompt.
3-24 65K510DEP08-1A
Section 3, Common Provisioning - Configure Local User Accounts
NOTE
If no change to the password is required, steps 4 ‐ 5 are optional.
4. From the User Configuration prompt, type password, and press ENTER to access the
Password Entry prompt.
5. From the Password Entry prompt, type the new password for the user, and press ENTER.
NOTE
If no change to the privilege level is required, step 6 is optional.
6. From the User Configuration prompt, type privilege [admin|config|read-
only|read-write|test], and press ENTER to set the user privilege level.
7. From the User Configuration prompt, by performing one of the following commands:
• Type no disable, and press ENTER to enable the username
• Type disable, and press ENTER to disable the username
Delete an Existing User Account

To delete an existing user account on the Total Access 5000, complete the following procedure:
3. From the Security Configuration prompt, type no username WORD, and press ENTER to
delete the account.
65K510DEP08-1A 3-25
Configure the Password Complexity

Password complexity provides options that increase or decrease the level of password security
by adjusting specific local password requirements. By default, password complexity is
disabled, placing no restrictions on passwords created for local accounts. To enable password
complexity, complete the following procedure:
3. From the Security Configuration prompt, type password complexity, and press ENTER.
Once completed, the following options can be enabled or disabled. To enable, simply enter the
command as shown. To disable, type no password complexity from the Security Configu‐
ration prompt.
The options listed in Table 3‐7 are enabled or disabled at the Security Configuration prompt.
Table 3-7. Password Complexity Options
CLI Command Description
case-sensitive If enabled, all usernames and passwords are case sensitive.
password digit If enabled, it requires all passwords to contain at least one numeric

character.
password length Sets the minimum length of the password.

<min_length>
password lowercase If enabled, it requires all passwords to have at least one upper‐case

alphabet character.
password no-digit- If enabled, passwords cannot start or end with a numeric character.

start-end
password special If enabled, it requires all passwords to have at least one upper‐case

alphabet character.
password uppercase If enabled, it requires all passwords to have at least one upper‐case

alphabet character.
3-26 65K510DEP08-1A
Section 4
EoCu Provisioning

This section details the steps needed to provision EoCu using the SHDSL Ethernet in the First
Mile (EFM) Access Module and the NetVanta 838. This section provides the minimum config‐
uration for traffic to pass from the GigE SM port to an Ethernet port on the NetVanta 838.
In this Section
Topic See Page
EoCu Overview 4‐2
Provisioning Summary 4‐3
Provision the 32‐Port SHDSL EFM 4‐4
Provision the EFM Bonding Protection Module Administration State 4‐6
Create an EFM Bonding Group 4‐7
Create an EVC Cross Connect 4‐14
Enable EFM Bonding Protection 4‐17
Log On to the NetVanta 838 4‐20
Create an EVC 4‐21
Create an EVC Map 4‐24
Provision Policers in the NetVanta 838 4‐27
Provision MAC Address Limiting and Aging 4‐30
Disable Unused NetVanta 838 Interfaces 4‐31
Save the NetVanta 838 Provisioning 4‐34
65K510DEP08-1A 4-1
EoCu Overview
Figure 4‐1 displays an overview of the EoCu deployment.
3 NetVanta 838 Entities/Commands 4 NetVanta 838 Entities/Commands

1 Total Access 5000 “Cross Connect”
EVC EVC-2010 EVC EVC-2020
• End Point 1→ PORT, NET 1
MEN- PORT EFM-Group 1 MEN- PORT EFM-Group 1
• End Point 2→ Bridge, Bridge Group 1
S-tag 201 S-tag 2020
• S-tag = 2010
2 Total Access 5000 “Cross Connect” 5 NetVanta 838 Entities/Commands 6 NetVanta 838 Entities/Commands
• End Point 1→ PORT, NET 1 EVC-MAP MAP-2010 EVC-MAP MAP-2020
• End Point 2→ Bridge, Bridge Group 1 UNI ETH 1 UNI ETH 3
• S-tag = 2020 Connect-EVC EVC-2010 Connect-EVC EVC-2020
Total Access 5000

SHDSL Available EVC’s and
PORT 1 SHDSL #1
Management VLAN
Pushed Down by
SHDSL
PORT 2 SHDSL #2 Total Access 5000
Bridge Group #1
Bridge SHDSL
EP2 PORT 3 SHDSL #3 5 ETH 1
EP1 Group #1 VLAN
3 MAP 2010 2010
SHDSL
PORT 4 SHDSL #4
1 ETH 2
NET 1
2 SHDSL
PORT 5 SHDSL #5 EFM 4 MAP 2020
Group #1 6 ETH 3
VLAN
EVC 2020
SHDSL 2020
EP1 PORT 6 SHDSL #6
EP2
ETH 4
SHDSL SHDSL #7
PORT 7
GigE VLAN
NetVanta 838
2010 +2020 SHDSL SHDSL #8
PORT 8
Management
VLAN 2048
Metro
Ethernet
Network
Bridge Group
“Phycical Links” EoCu
System Diagram
Figure 4-1. EoCu Diagram
4-2 65K510DEP08-1A
Section 4, EoCu Provisioning - Provisioning Summary
Provisioning Summary
To create a data path from the GigE SM port on the Total Access 5000 to an Ethernet port on
the NetVanta 838, complete the following procedure:
1. Provision the 32‐Port SHDSL EFM Access Module.
For more information, refer to “Provision the 32‐Port SHDSL EFM” on page 4‐4.
2. Provision the EFM Bonding Protection Module.
For more information, refer to “Provision the EFM Bonding Protection Module
Administration State” on page 4‐6.
NOTE
EFM Bonding Protection is optional.
3. Create an EFM bonding group at the GigE SM that bonds a set of SHDSL ports of the
module together.
The bonding group acts as the data flow access point to the NetVanta 838 and is the path
down which the management configuration is pushed.
For more information, refer to “Create an EFM Bonding Group” on page 4‐7.
4. Create an Ethernet Virtual Circuit (EVC) at the Total Access 5000 that connects the EFM
group to the Gigabit Ethernet port of the GigE SM.
This creates the mapping of the S‐tagged data. This accomplishes the following:
• The GigE SM knows where to send the tagged traffic coming in from the gigabit
network port
• The GigE SM pushes the available tags to each EFM bonding group and to each
NetVanta 838 for the local NetVanta 838 provisioning
For more information, refer to “Create an EVC Cross Connect” on page 4‐14.
5. Enable EFM Bonding Protection.
NOTE
EFM Bonding Protection is optional.
For more information, refer to “Enable EFM Bonding Protection” on page 4‐17.
6. Log on to the NetVanta 838.
For more information, refer to “Log On to the NetVanta 838” on page 4‐20.
7. Create the EVC at the NetVanta 838.
The EVC is a logical connection point into the EFM group.
NOTE
• Multiple EVCs can be created for a given EFM group.
• For the NetVanta, the shelf is always 1 and the slot is always zero.
For more information, refer to “Create an EVC” on page 4‐21.
65K510DEP08-1A 4-3
8. Create a map at the NetVanta 838 that informs the unit to switch data from a given User
to Network Interface (UNI), at a minimum, to a particular EVC, and vice versa.
For more information, refer to “Create an EVC Map” on page 4‐24.
9. Provision policers in the NetVanta 800.
10. For more information, refer to “Provision Policers in the NetVanta 838” on page 4‐27.
11. Provision MAC Address Limiting and Aging.
For for more information, refer to “Provision MAC Address Limiting and Aging” on
page 4‐30.
12. Disable any unused interfaces.
For more information, refer to “Disable Unused NetVanta 838 Interfaces” on page 4‐31.
Provision the 32-Port SHDSL EFM

This subsection details provisioning the 32‐Port SHDSL EFM service state.
Provision the 32-Port SHDSL EFM Administration Status

The 32‐Port SHDSL EFM card service state must be set to In Service or Out of Service, Mainte‐
nance.
NOTE
If the card service state is set to Out of Service, Maintenance, normal
operation occurs but alarms are not reported.
For traffic to pass, the 32‐Port SHDSL EFM module must be enabled.
Table 4‐2 displays the three administration states and shows the equivalent Service State from
prior releases.
Table 4-2. 32-Port SHDSL EFM Administration States

shutdown maintenance Out of Service, In the shutdown maintenance state, traf‐

Maintenance fic passes but no alarms are generated.

To set the module administration and port administration states, complete the following
procedure:
4-4 65K510DEP08-1A
Section 4, EoCu Provisioning - Provision the 32-Port SHDSL EFM
NOTE
If connected to the shelf where the module resides, the shelf number is
typically 1.
performing one of the following commands:
• Type no slot shutdown <shelf/slot>, and press ENTER to take the slot In Service
• Type slot shutdown maintenance <shelf/slot>, and press ENTER to take the
slot Out of Service Maintenance
• Type slot shutdown <shelf/slot>, and press ENTER to take the slot Out of
Service, Unassigned
3. From the Global Configuration prompt, type interface shdsl <shelf/slot/port>,
and press ENTER.
4. To configure the Circuit ID, type description LINE, and press ENTER.
5. Provision the SHDSL port administration state by performing one of the following
commands:
• Type no shutdown, and press ENTER to take the port In Service
• Type shutdown maintenance, and press ENTER to take the port Out of Service,
Maintenance
• Type shutdown, and press ENTER to take the port Out of Service, Unassigned
6. To set the alarm thresholds, type thresholds [cvc|es|losws|ses|uas] [15
minute|24 hour] <0-2147483647>, and press ENTER.
Table 4‐3 provides the syntax and alarm threshold definitions for arg_1 and arg_2.
Table 4-3. 32-Port SHDSL EFM Alarm Thresholds
Syntax Definition
arg_1 Select the threshold to configure the following:
• cvc ‐ Code Violation Count
• es ‐ Errored Seconds
• losws ‐ Loss of Sync Word Seconds
• ses ‐ Severely Errored Seconds
• uas ‐ Unavailable Seconds
arg_2 Enter the second alarm threshold to one of the following:
• 15‐minute ‐ This reports any violations within a 15‐minute time
frame. Valid values are 0‐2147483647.
• 24‐hour ‐ This reports any violations within a 24‐hour time frame.
Valid values are 0‐2147483647.
7. Repeat steps 3‐8 for each SHDSL port that needs to be provisioned.
65K510DEP08-1A 4-5
Provision the EFM Bonding Protection Module

Administration State
For traffic to be protected in the event of an EFM bonding engine failure, the EFM Bonding
Protection Module card service state must be set to IS or OOS‐MA. The default service state
for the 32‐Port SHDSL EFM EFM is OOS‐MA.
NOTE
If the card service state is set to OOS‐MA, normal operation occurs but alarms
are not reported.
To set the card service state, complete the following procedure:
Table 4‐4 displays the three administration states.
Table 4-4. EFM Bonding Protection Module Administration States

and alarms are generated.This is the
default value.
shutdown maintenance Out of Service, In the shutdown maintenance state,

Maintenance traffic passes but no alarms are generated.

2. From the Global Configuration prompt, provision the administration state by
NOTE
• If connected to the shelf where the module resides, the shelf number is
typically 1.
• This is the slot of the module being configured. Valid values are
1 – 11 and 13 – 22.

slot Out of Service, Maintenance
Service, Unassigned
3. Type end, and press Enter to return to the Enable prompt.
4-6 65K510DEP08-1A
Section 4, EoCu Provisioning - Create an EFM Bonding Group
Create an EFM Bonding Group

• Definition of an EFM bonding group
• Steps for configuring the EFM bonding management
• Steps for modifying an existing bridge
• Auto‐Provision the SHDSL pairs using EZ‐EFM
• EFM bonding overhead description
Bonding Group Definition

A bonding group is defined as “a group of switch interfaces assigned to a singular bridge unit
and network interface.”
The EFM bonding group bundles multiple SHDSL lines together to provide bandwidth equal
to the sum of the SHDSLs bonded. This process provides the necessary bandwidth for service.
For example, eight SHDSLs bonded together provide eight times the speed of 1 SHDSL (8 x
5.696 = 45.568 Mbps of bandwidth) to transport ethernet traffic.
Provisioning Steps
This procedure creates an EFM bonding group at the GigE SM that bonds the physical layer
ports (SHDSL) of the access module(s) together.
To create a new bonding group, complete the following procedure:
1. From the Enable prompt, type application, and press ENTER to access the Application
Configuraton prompt.
2. From the Application Configuration prompt, type ez-efm <shelf>, and press ENTER to
start the EZ Ethernet application.
3. From the EFM Configuration prompt, type create WORD link <EFM links>
upstream <0-250000> downstream <0-250000> active-links-minimum <1-n>,
and press ENTER to create an EFM Bonding Group.
Table 4‐5 displays the list of variables for the EFM bonding group.
65K510DEP08-1A 4-7
Table 4-5. EFM Bonding Group Variables
Syntax Description
WORD Enter the name (up to 50 alphanumeric characters with no spaces or spe‐
cial characters) of the bonding group.
EFM links Enter the EFM links to add to the bonding group. Each link must be in the

slot/port format and separated by commas.
active-links-min- Enter the number of links in the group required to provide the upstream
imum and downstream rates. Any additional links will be hot standby links.
upstream/down- The values after the upstream and downstream keywords are the
stream upstream and downstream rates for the bonding group.
4. From the EFM Configuration prompt, type exit, and press ENTER to return to the
Application Configuration prompt.
Verify Bonding Group Creation

To verify that the bonding group was created, and determine the slot and group ID assigned
to the group, perform one of the following:
• From the Enable prompt, type show interfaces efm-group, and press ENTER to view
all EFM bonding groups in the Total Access 5000
• From the Enable prompt, type show table interfaces efm-group, and press ENTER
to view a table (with limited EFM group information)
• From the Enable prompt, type show efm-group 1, and press ENTER to see the links
assigned to all groups in the shelf along with the provisioned group rates
EFM Bonding Group Example

The example below creates a bonding group which includes slot 1, ports 3 and 5, then displays
the group status.
NOTE
If there is a problem with the creation of the group, an error message will
follow the create command. Otherwise, it is successful if no error message
follows the command.
TA5000# application
TA5000(app)# ez-efm 1
TA5000(app-ez-efm 1)# create my_bonding_group link 1/3,1/5 upstream 5000
downstream 5000 active-links-minimum 1
TA5000(app-ez-efm 1)# exit
TA5000(app)# exit
TA5000# show interfaces efm-group
EFM Group 1/1/2 {MY_BONDING_GROUP} is ENABLED and UP
Provisioned Links : 1/3,1/5
Active Links : 1/3,1/5
Inhibited Links : None
UpStream Data Rate : 5120
DownStream Data Rate : 5120
4-8 65K510DEP08-1A
Loopback : Disabled
XCV Threshold : 1e-7
XCV Link Removal : Enabled
TA5000#
Configure EFM Bonding Management Provisioning

The NetVanta 838 Inband Management configuration is tied to the EFM bonding group.
Thus, when a NetVanta is replaced, the remote management configuration is pushed down so
that the NetVanta is immediately remote accessible when at least one SHDSL link synchro‐
nizes.
NOTE
• If provisioning the NetVanta 838 locally, the Total Access 5000 overwrites
the Inband management provisioning when the SHDSL ports synchronize
with the SHDSL EFM access module.
• The Inband management of the NetVanta 838 is configured at the Total
Access 5000, and pus hed down to the NetVanta 838 as soon as
synchronization is achieved on one of the links of the bonded group.
To configure the EFM bonding group management provisioning, complete the following
procedure:
2. From the Global Configuration prompt, type interface efm-group <shelf/slot/
group>, and press ENTER to access the EFM Bonding Group Configuration prompt.
3. From the EFM Group Interface Configuration prompt, type subtended-host ip
address A.B.C.D E.F.G.H, and press ENTER to provision the NetVanta Management
IP address (A.B.C.D) and subnet mask (E.F.G.H).
4. From the EFM Group Interface Configuration prompt, type subtended-host s-tag
<1-4094>, and press ENTER to provision the NetVanta Management VLAN.
default-gateway A.B.C.D, and press ENTER to provision the NetVanta Management
Gateway.
file-server default host A.B.C.D, and press ENTER to provision the NetVanta 838
Management TFTP server.
7. From the EFM Group Interface Configuration prompt, type subtended-host snmp-
server chassis-id WORD, and press ENTER to provision the NetVanta SNMP system
name.
server community read-only WORD, and press ENTER to provision the read‐only
SNMP community.
server community read-write WORD, and press ENTER to provision the read‐write
SNMP community.
10. From the EFM Group Interface Configuration prompt, type end, and press ENTER to
return to the Enable prompt.
65K510DEP08-1A 4-9
NOTE
This information is sent to the NetVanta 838 by way of an overhead
management channel.
Once completed and if the management VLANs of the GigE SM and the NetVanta 838 are
equivalent, the NetVanta 838 Command Line Interface (CLI) can be accessed via the Inband
Management VLAN.
Modify an Existing Bridge

There are two ways to modify an existing EFM bonding group. The EZ‐EFM application
allows the user to add or remove a link to/from a bonding group while simultaneously speci‐
fying the bonding group upstream and downstream data rates. The EZ‐EFM application
automatically re‐provisions all links in the group to the necessary link rates, whether the rate
is increased or decreased. The links retain and provide the provisioned data rate.
The second way to add or remove a link to/from a group is by directly modifying the EFM
bonding group in the EFM Bonding Group Configuration prompt. This method does not
result in a re‐provisioning of the links in the group, but can result in the links not being set to
the optimum rates; the group not providing the specified data rate if links are removed.
Modify a Bonding Group with EZ-EFM

To modify a bonding group using the EZ‐EFM application, complete the following procedure:
1. From the Enable prompt, type application and press ENTER to access the application
CLI prompt.
2. From the Application Configuration prompt, type ez-efm 1 and press ENTER to start the
EZ Ethernet application.
3. From the EFM Configuration prompt, type modify <group_name> link <slot/
port> upstream <0-250000> downstream <0-250000> active-links-minimum
<1-n>, and press ENTER to modify an existing EFM Bonding Group.
Refer to Table 4‐5 for the list of variables for the EFM bonding group.
4. From the EFM Configuration prompt, type modify <group_name> no-link <slot/
port> upstream <0-250000> downstream <0250000> active-links-minimum
<1-n>, and press ENTER to remove links from an existing EFM Bonding Group.
NOTE
For the modify command, all parameters must be specified, even if a
particular value is not being changed.
Refer to Table 4‐5 for the list of variables for the EFM bonding group.
4-10 65K510DEP08-1A
Modify a Bonding Group Directly

To modify a bonding group directly, complete the following procedure:
3. If required, modify the active‐links‐minimum or modify the upstream and downstream
rates from the EFM Configuration prompt, type modify <group_name> link <slot/
port> upstream <0-250000> downstream <0-250000> active-links-minimum
<1-n>, and press ENTER to modify an existing EFM Bonding Group.
4. From the Enable prompt, type configure terminal, and press ENTER to access the
Global Configuration prompt.
5. From the Global Configuration prompt, type interface efm-group <group_name>,
and press ENTER to access the EFM Bonding Group Configuration prompt.
6. From the EFM Group Interface Configuration prompt, type one of the following
commands to add or remove a link to the EFM bonding group.
• From the EFM Group Interface Configuration prompt, type link <slot/port>,
and press ENTER to add a link to the EFM bonding group
• From the EFM Group Interface Configuration prompt, type no link <slot/port>,
and press ENTER to remove a link from the EFM bonding group
7. From the EFM Group Interface Configuration prompt, type exit and press ENTER to
return to the Application Configuration prompt.
65K510DEP08-1A 4-11
Auto-Provision the SHDSL Pairs Using EZ-EFM

The EZ‐EFM feature automatically provisions the maximum and minimum rates of each
SHDSL pair in the bonding group, as follows:
• SHDSL maximum rate = (upstream_rate) / (mimimum_links)
• SHDSL minimum rate = ( (upstream_rate) / (minimum_links) ) / 4
NOTE
For fixed rate mode, the minimum rate is set equal to the maximum rate.
The SHDSL Training Mode (fixed, worst‐case rate adaptive, or current‐case rate adaptive)
must be modified directly (per SHDSL pair in the CLI, and per EFM Group in the EMS).
The SHDSL Worst Case Margin must also be modified directly (per SHDSL pair in the CLI or
EMS).
Of the items listed above, only the SHDSL Training Mode and Worst Case Margin are passed
down to the NetVanta 838. The minimum and maximum rates pushed down from the EZ EFM
to the SHDSL Total Access 5000 pairs are not pushed down to the NetVanta. This results in the
NetVanta ranges remaining at the minimum and maximum values (3 and 89), rather than
matching those of the Total Access 5000. The training attempt succeeds despite this difference
in provisioning. The SHDSL rate adaptive training algorithm requires that each SHDSL trans‐
ceiver determines at which rate it can train, and then passes that information to the other
transceiver. The NetVanta 838 SHDSL interface determines the maximum rate at which it can
train, and then notifies the Total Access 5000 interface that it can train up to that rate. As long
as the NetVanta can train at the minimum rate provisioned at the Total Access 5000 (group
rate divided by active‐links‐minimum, then divided again by 4), the train succeeds. If the
NetVanta cannot achieve that training rate, the train fails, and training attempts will continue.
EFM Bonding Overhead Description

Before being transported over the physical layer (SHDSL, T1, etc.), the EFM bonding engine
first encapsulates Ethernet frames into EFM fragments. EFM Fragment payload can vary from
64 to 512 bytes depending on the Ethernet packet size. If an Ethernet Frame is 512 bytes or
smaller, it is placed into one EFM fragment. If the frame is between 513 and 1024 bytes, it is
split between two EFM fragments. If the frame is 1025 bytes or greater, it is split between three
EFM fragments.
Each EFM fragment has the following overhead:
• There are 2 bytes of overhead per fragment that are the same for all fragments: a start byte
and Ck byte (an EOF designator)
• The frame check sequence (FCS): the size of this depends on technology
• There are 2 additional overhead bonding header bytes
For SHDSL, this comes out to 8 overhead bytes per fragment. In addition, as part of the 64/65
EFM framing, there are code words that are 64 payload bytes and 1 sync byte.
Using this information, the following equations can be used to determine the effective
percentage of the EFM bonding group that is available for customer Ethernet transport (for
SHDSL):
• Ethernet frames 512 bytes or smaller:
% Utilization = (Frame Size) / (Frame Size + 8)x (64/65)
4-12 65K510DEP08-1A
• Ethernet frames between 513 and 1024 bytes, inclusive:
% Utilization = (Frame Size) / (Frame Size + 16) x (64/65)
• Ethernet frames 1025 bytes or larger:
The equations above assume that the NetVanta is not adding an extra tag to the customer
traffic (ie. when the customer traffic is tagged, and the customer edge tag is not being
preserved). In any case where the customer tag is preserved (the most likely scenario), and the
NetVanta 838 is simply stacking the provisioned service provider tag (s‐tag) to the customer
tag (if present), the calculation must account for the additional 4 bytes for the s‐tag, as follows:
• For Ethernet frames 512 bytes or smaller:
• For Ethernet frames between 513 and 1024 bytes, inclusive:
To determine the EFM bonding group bandwidth that needs to be provisioned so that the
customerʹs commissioned rate is provided, divide the customer rate by this percentage:
Required EFM Group Rate = (Customer Commissioned Rate) / (% Utilization.
Following are example calculations for customer throughput percentage, given a fixed frame
size, assuming the NetVanta 838 is adding a VLAN tag:
• For 64 byte Ethernet frames (worst case scenario):
% Utilization = (64) / (64 + 12) x (64/65) = 82.9%
• For an 8 Mbps bonding group, the actual throughput would be:
8 Mbps x .829 = 6.632 Mbps
• If a customer is sold a 4 Mbps service, the required EFM group size calculation would be:
(4 Mbps) / (.829) = 4.825 Mbps
• For 1500 byte Ethernet frames:
% Utilization = (1500) / (1500 + 28) x (64/65) = 96.7%
8 Mbps x .967 = 7.736 Mbps
(4 Mbps) / (.967) = 4.137 Mbps
Another point of reference is the EFM bonding group utilization percentage that is seen
assuming uniform distribution of frame sizes, from 64 to 1518 bytes. This value is 96.0%
assuming the service provider VLAN tag is being added to the customer traffic. Assuming
uniform traffic size, the EFM group would need to be a factor of 1.042 greater than the
commissioned customer rate to provide the full customer rate.
The service provider is best suited to decide what traffic model it wants to use for network
planning, but the tools above should allow them to suitably determine the EFM Group
bandwidth needed to provide the customerʹs full traffic rate.
65K510DEP08-1A 4-13
Create an EVC Cross Connect

• Definition of an EVC
• Guidelines for creating an EVC
• Steps for creating an EVC
EVC Definition
An EVC is a logical entity that provides a means for connecting two endpoints in the Total
Access 5000 and provides a path for Ethernet frames with a particular VLAN ID within the
Total Access 5000. The EVC cross‐connects two endpoints and provides the mechanism by
which an S‐tag path is created in the system. The S‐tag corresponds to the VLAN ID. For
example, in the EoCu application an EVC cross‐connect is created between a physical network
port and a logical EFM bonding group. Traffic entering the network port on the selected S‐tag
is sent by the GigE SM to the 32‐Port SHDSL EFM containing the bonding group and then
forwarded to the bonding group by the module.
In the Total Access 5000, customer traffic switches throughout the system via S‐tags
(outermost VLAN tag on an Ethernet packet). Downstream traffic enters the system through
the network ports on the GigE SM and is S‐tag switched to the appropriate slot. The 32‐Port
SHDSL EFM then decides how to send that traffic to the customer. Upstream traffic is
switched to the network in a similar manner.
NOTE
If the NetVanta 838 management VLAN differs from the GigE SM
management VLAN, create a cross connect for the GigE SM to pass the
NetVanta 838 management traffic. When creating a cross connect, set up the
cross connect with an S‐tag equal to the NetVanta 838 management VLAN,
pointing to the appropriate EFM Group.
EVC Cross Connect Guidelines

When creating a cross‐connect, enforce the following guidelines:
• An EVC cannot be part of another cross‐connect
• Each EVC must have a unique S‐tag
Table 4‐6 displays the available S‐tags in the Total Access 5000.
Table 4-6. Available S-tag Range
S-tag Function
0, 1, 4095 Reserved
2 – 4094 EVPLs and Inband Management VLAN
3072 Internal Management VLAN (Default)
4-14 65K510DEP08-1A
Section 4, EoCu Provisioning - Create an EVC Cross Connect
Provisioning Steps
This process establishes a connection between the physical port and the virtual network.
To create the EVC, complete the following procedure:
2. From the Global Configuration prompt, type evc <evc_name>, and press ENTER.
3. From the EVC Interface Configuration prompt, type s-tag <1-4094>, and press ENTER
to set the S‐tag of the EVC.
4. From the EVC Interface Configuration prompt, type connect men-port gigabit-
ethernet 1/A/1, and press ENTER to connect the active SM Net 1 interface to the EVC.
NOTE
The connect men‐port gigabit‐ethernet command entry applies to the active
GigE SM, independent of which GigE SM is actually specified, in an Active/
Standby configuration.
5. From the EVC Interface Configuration prompt, type connect men-port efm-group

<shelf/slot/group>, and press ENTER to connect the EFM bonding group to the EVC.
NOTE
The EFM bonding group name can be used in lieu of the shelf/slot/group
designation.
6. From the EVC Interface Configuration prompt, type no shutdown and press ENTER to
enable the EVC.
7. From the EVC Interface Configuration prompt, type end and press ENTER to return to the
Enable prompt.
65K510DEP08-1A 4-15
ELAN Definition
An Emulated Local Area Network (ELAN) is a single shelf application that supports single
tagged MEPs for Ethernet OAM. Double tagged MEPs for Ethernet OAM when doing ELAN
are not supported. An ELAN EVC can be provisioned with endpoints accessed from any
EoCu access module. Mixed access ELAN EVCs are also possible.
Provisioning Steps
To provision an ELAN, complete the following:
2. From the Global Configuration prompt, type evc WORD, and press ENTER.
ethernet <shelf/slot/port>, and press ENTER.
Use this command to configure which GigE 8‐Port LM port the selected EVC is applied
to.
4. From the EVC Interface Configuration prompt, type mac-switched, and press ENTER to
enable MAC Switching.
Enable prompt.
4-16 65K510DEP08-1A
Section 4, EoCu Provisioning - Enable EFM Bonding Protection
Enable EFM Bonding Protection

• Definition of EFM Bonding Protection
• Steps for enabling EFM Bonding Protection
EFM Bonding Protection Definition

EFM Bonding Protection is a Layer 2 application used to protect traffic carried by those access
modules that include an EFM Bonding Engine as part of their feature set. EFM Bonding
Protection will not work for access modules that do not have this feature. The purpose of EFM
Bonding is the protection of traffic going to and from a particular slot, and not the access
module in that slot.
In an EFM Bonding Protection configuration, the Total Access 5000 EFM Protect Module is
installed in a Total Access 5000 shelf. Once the module is installed, it must be configured so it
can protect traffic going to and from a module in a specific slot. By creating an EFM Bonding
Group, traffic to and from a group of slots/access modules can also be protected. As an added
feature, EFM Bonding Protection also allows each of these groups and/or access modules
within a group to have a priority assigned to the traffic going to and from that access module
or group. For example, assume that all the access modules are being protected by the EFM
Protect Module in slot 11. The access modules in slot 1 to 8 have their priority set to 1 (priority
levels range from 1 to 32 where 32 is the highest priority), and those access modules in slots 17
to 21 have a priority level of 10. If one of the access modules in slots 1 to 8 goes offline, their
traffic will switch over to the EFM Protect Module. The traffic will continue to pass through
the EFM Protect Module until the access module that went offline comes back online, or an
access module in slots 17 to 21 goes offline. If that occurs, the EFM Protect Module will switch
to the slot/access module with the higher priority.
An example of how this configuration could be used is displayed in Table 4‐7.
Table 4-7. EFM Bonding Protection
SLOT 1 SLOT 2 SLOT 3 SLOT 4 SLOT 5 SLOT 6 SLOT 7 SLOT 8 BG

Location
Ports Ports Ports Ports Ports Ports Ports Ports NCTE

1‐27 1‐27 1‐27 1‐27 1‐27 1‐27 1‐27 1‐27 1‐27
BG 1 1 1 1 1 1 1 1 NCTE1 Slot 1
2 BG 2 2 2 2 2 2 2 NCTE2 Slot 2
3 3 BG 3 3 3 3 3 3 NCTE3 Slot 3
4 4 4 BG 4 4 4 4 4 NCTE4 Slot 4
5 5 5 5 BG 5 5 5 5 NCTE5 Slot 5
6 6 6 6 6 BG 6 6 6 NCTE6 Slot 6
7 7 7 7 7 7 BG 7 7 NCTE7 Slot 7
8 8 8 8 8 8 8 BG 8 NCTE8 Slot 8
BG9 9 9 9 9 9 9 9 NCTE9 Slot 1
10 BG10 10 10 10 10 10 10 NCTE10 Slot 2
11 11 BG11 11 11 11 11 11 NCTE11 Slot 3
65K510DEP08-1A 4-17
Table 4-7. EFM Bonding Protection (Continued)
SLOT 1 SLOT 2 SLOT 3 SLOT 4 SLOT 5 SLOT 6 SLOT 7 SLOT 8 BG

Location
12 12 12 BG12 12 12 12 12 NCTE12 Slot 4
13 13 13 13 BG13 13 13 13 NCTE13 Slot 5
14 14 14 14 14 BG14 14 14 NCTE14 Slot 6
15 15 15 15 15 15 BG15 15 NCTE15 Slot 7
16 16 16 16 16 16 16 BG16 NCTE16 Slot 8
BG17 17 17 17 17 17 17 17 NCTE17 Slot 1
18 BG18 18 18 18 18 18 18 NCTE18 Slot 2
19 19 BG19 19 19 19 19 19 NCTE19 Slot 3
20 20 20 BG20 20 20 20 20 NCTE20 Slot 4
21 21 21 21 BG21 21 21 21 NCTE21 Slot 5
22 22 22 22 22 BG22 22 22 NCTE22 Slot 6
23 23 23 23 23 23 BG23 23 NCTE23 Slot 7
24 24 24 24 24 24 24 BG24 NCTE24 Slot 8
BG25 25 25 25 25 25 25 25 NCTE25 Slot 1
26 BG26 26 26 26 26 26 26 NCTE26 Slot 2
27 27 BG27 27 27 27 27 27 NCTE27 Slot 3
This table is an example of how EFM Protection Bonding could be configured to protect traffic
going to multiple Network Channel Termination Equipment (NCTEs). Each NCTE could be
an individual port or entire device at a customer location.
In the example, each card in Slots 1 to 8 have EFM Protection Bonding. In the example, there
are only three to four Bonding Groups (BG) per slot, but there could be as many as 8. Each BG
(also known as a Bridge) is described below:
• BG 1 is shown in Yellow and the Bonding Engine is located in Slot 1. Every group of
Yellow Slots and related Ports are part of this BG 1. These slots and ports have been
“Bridged’ together to form a BG. This BG is transmitting data to customer NCTE1/Slot 1,
NCTE9/Slot1, NCTE17/Slot 1 and NCTE25/Slot 1.
• BG 2 is shown in Red and the Bonding Engine is located in Slot 2. Every group of Red Slots
and related Ports are part of this BG 2. This BG is transmitting data to customer NCTE2/
Slot 2, NCTE10/Slot 2, NCTE18/Slot 2 and NCTE26/Slot 2.
• BG 3 is shown in Blue and the Bonding Engine is located in Slot 3. Every group of Blue
Slots and related Ports are part of this BG 3. This BG is transmitting data to customer
NCTE3/Slot 3, NCTE11/Slot 3, NCTE19/Slot 3 and NCTE27/Slot 3.
In this example, if the Bonding Engine in Slot 1 went offline, the EFM Protect Module would
take over the traffic going to and from the bonding groups associated with that Bonding
Engine. As a result, there would be no loss or reduced bandwidth going to the customer’s
NCTEs. The EFM Protection Module will continue this protection until the Bonding Engine is
returned to service. It is important to remember that the Bonding Engine is physically located
in an access module. Correcting this situation may require replacement of that access module.
4-18 65K510DEP08-1A
Section 4, EoCu Provisioning - Enable EFM Bonding Protection
One of the advantages of configuring the Bonding Groups as depicted in this example is
related to “traffic prioritization”. Traffic prioritization is used to establish different priority
levels for traffic going to different bonding groups. If BG 1 has an assigned priority of “5”, and
goes offline, the EFM Protection Module will take over the traffic for that module. If however,
BG 2 has a priority of “10” and it goes offline, the EFM Protection Module will switch to that
bonding group and drop traffic going to BG1. When this happens, only 1/4th of the data going
to the customer’s NCTEs would be lost.
Provisioning Steps
To enable EFM Bonding Protection, complete the following procedure:
2. From the Global Configuration prompt, type protection-group <shelf/group>,
and press ENTER to access the Protection Group Configuration prompt. If it is a new
group, it is created. If it is an existing group, it can now be modified.
3. From the Protection‐Group Configuration prompt, type add protect-module
<slot>, and press ENTER to assign the EFM Protection Module to the protection group.
4. From the Protection‐Group Configuration prompt, type add working-module
<slot>, and press ENTER to assign a working access module slot to the protection group.
5. Repeat step 4 to add all needed slots to the protection group.
6. By default, all slots in the group are at level 0, the lowest priority in the group. The first
slot that fails will be protected until it can have control restored. Other slots will be
blocked. To give a slot precedence within the group, type priority <slot> <1-n>,
and press ENTER. 32 is the highest priority, followed by 31, and so on.
7. From the Protection‐Group Configuration prompt, type wait-to-restore auto-
switch <1-20>, and press ENTER to set the wait to restore time.
This option is used to set the amount of time that the EFM Protection module will
continue to protect traffic after an access module that was down has been returned to
service. Once the access module is back in service for the time indicated (1 to 20 minutes),
and the revertive setting is enabled, the EFM Protection module relinquishes the traffic
back to the access module.
8. From the Protection‐Group Configuration prompt, type end and press ENTER to return to
the Enable prompt.
65K510DEP08-1A 4-19
Log On to the NetVanta 838

Access the management and provisioning features for the NetVanta 838 products by
Command Line Interface (CLI) using a standard DB‐9 serial cable to connect to the console
port located on the unit. The CLI may also be accessed via Telnet over the Inband
Management VLAN.
CRAFT Port Login

To establish CLI communication with the product, complete the following procedure:
1. Connect to the craft interface using a VT100 terminal or PC with VT100 emulation soft‐
ware configured with the following parameters:
• Any baud rate from the list of 9600, 19200, 38400, 57600, or 115200
• 8 data bits
• No parity
• 1 stop bit
• No flow control
2. Once connected, press ENTER several times to access the CLI.
NOTE
The account name and password are case sensitive. Default accounts are
ADMIN, READONLY, READWRITE, and TEST. The default password for
each of these accounts is PASSWORD. The privilege to change passwords,
account names, and privileges are included in the ADMIN account.
Remote Access Login

To remotely access the NetVanta 838, open a telnet session to the IP address configured in the
bridge group.
4-20 65K510DEP08-1A
Section 4, EoCu Provisioning - Create an EVC
Create an EVC
• EVC guidelines
• Steps for configuring an EVC
• EVC example
EVC Definition
The Metro Ethernet Forum (MEF) defines an EVC as “an association of two or more UNIs,”
where a UNI is a standard 10/100/1000 Ethernet interface that is the point of demarcation
between the Customer Equipment (CE) and the Metro Ethernet Network (MEN) of the service
provider. In simple terms, an EVC performs two functions.
• Connects two or more subscriber sites (UNIs) enabling the transfer of Ethernet service
frames
• Prevents data transfer between the subscriber sites that are not part of the same EVC
This capability enables an EVC to provide data privacy and security similar to a Frame
Relay or ATM Permanent Virtual Circuit (PVC).
Multiple EVCs can reside on a common bonding group or Ethernet port. Each EVC typically
has an associated EVC VLAN tag whose VLAN ID is unique among other EVCs in the MEN.
The EVC VLAN tag allows the EVC to be identified and separated from other EVCs.
At a minimum, two items must be set up for the EVC: the MEN interface it will use and the S‐
tag it will use.
NOTE
The S‐tag must match the EVCs configured at the Total Access 5000.
EVC Guidelines
To ensure valid provisioning, enforce the following guidelines when creating an EVC:
• An EVC is applied only if the status is Running (as indicated in the show evc output),
which indicates that the conditions are valid
• Two EVCs are considered to be duplicate if they both have the same values for the
following attributes:
– MEN port
– S‐tag
• No two EVCs can have the same name
• If the system is managed through a VLAN on a designated bonding group or Ethernet
port, the S‐tag value for the EVC cannot equal the management VLAN ID
65K510DEP08-1A 4-21
Provisioning Steps
To create an EVC, complete the following procedure:
2. From the Global Configuration prompt, type evc WORD, and press ENTER to create an
EVC.
The WORD attribute is an arbitrary string that is used to identify the EVC within the
MEN. The value must be unique across all EVCs defined in the NetVanta 838, and is
intended for management and control purposes. The value is not carried in any field in
the Ethernet frame.
This creates the EVC and enables the EVC Configuration prompt.
Configure the EVC

The MEN port and S‐tag must be configured for the EVC. To configure the Metro Ethernet
Network and S‐tag, complete the following procedure:
1. From the EVC Configuration prompt, type connect men-port efm-group 1/0/1, and
press ENTER to set the MEN‐port as an EFM bonding group of the NetVanta 838.
This attribute is the logical interface connected to the MEN. The possible options consist
of the Ethernet port(s) and bonding group(s) available on the NetVanta 838. In typical
configurations, the MEN port is specified as a bonding group.
2. From the EVC Configuration prompt, set the S‐tag by typing s-tag <2-4094>, and
press ENTER.
This attribute is the VLAN ID associated with the EVC tag.
NOTE
The NetVanta 838 S‐tag must match the S‐tag provisioned in the Total Access
5000 for this bonding group. If the S‐tag is not configured at the Total Access
5000, the EVC will not go running.
3. By default, CE VLAN Preservation is enabled. To disable,type no preserve-ce-vlan,
and press ENTER.
If CE VLAN Preservation is enabled, the NetVanta preserves the customer’s VLAN tag
for traffic entering the NetVanta. It stacks the service provider tag on top of the customer
tag. If it is disabled, the customer VLAN tag is stripped before the service provider tag is
added to the traffic.
If CE VLAN Preservation is disabled, the customer tag is added back onto traffic
egressing to the customer.
4. By default, the new EVC is disabled. Enable the new EVC by typing no shutdown, and
press ENTER.
5. Type exit and press ENTER to return to the Global Configuration prompt.
7. To save the changes in non‐volatile memory, type write, and press ENTER.
8. View the new EVC by typing show evc WORD, and press ENTER.
4-22 65K510DEP08-1A
Section 4, EoCu Provisioning - Create an EVC
NOTE
If creating an EVC with the same S‐tag as the management traffic, the conflict
is noted in the status of the EVC.
EVC Example
The following is a sample output of the show interfaces EVC command for evc2010.
MyNV838>show evc evc2010
EVC evc2010
S-TAG : 2010
Admin State : Enabled
EVC Status : Running - Enabled
MEN-port : EFM-Group 1/0/1
CE-VLAN Preservation : Disabled
MyNV838#
65K510DEP08-1A 4-23
Create an EVC Map

• Definition of a map
• Steps for creating a map
• Steps for configuring a map
• Map example
Map Definition
Define the association of customer traffic on a UNI port with an EVC by defining an entity
called an EVC‐map. Each EVC‐map is typically associated with a single customer and
specifies parameters including the customer VLAN ID and Class of Service (CoS) behavior of
the traffic from the customer. Use a map to classify traffic for use by an EVC for forwarding
and for use by a policer for rate limiting.
Map Guidelines
To ensure valid provisioning, enforce the following guidelines when creating a map:
• A map is applied only if the EVC map’s status is Running (as indicated in the show evc‐
map output), which indicates that the conditions are valid
• Two maps are considered to be duplicate if they both have the same values for the
– UNI port
– CE‐VLAN‐ID
– Overlapping range for CE‐VLAN‐Pri
– Differentiated Services Code Point (DSCP) value
– Untagged priority tagged frames
• No two maps can have the same name
port, the management VID value cannot equal the CE‐VLAN‐ID value of the map
• If the CE‐VLAN‐ID preservation attribute of an EVC is disabled, all of the maps connected
to the EVC must have the same value of the CE‐VLAN‐ID attribute which can include not
specifying this attribute which allows means the EVC‐map does not consider VLAN‐ID
in its match criteria
• When multiple maps are applied to a single EVC, each map must have the same UNI.
Multiple UNIs cannot be mapped to a single EVC
• If two or more maps have either the same UNI or the same associated EVC, only one of
the maps can be provisioned to allow untagged and priority tagged frames
4-24 65K510DEP08-1A
Section 4, EoCu Provisioning - Create an EVC Map
Provisioning Steps
To create the map, complete the following procedure:
2. From the Global Configuration prompt, type evc-map WORD, and press ENTER to create
the map and enter the map configuration mode.
This attribute is an arbitrary string that is used to identify the map. The value must be
unique across all maps defined in the product and is intended for management and
control purposes. The value is not carried in any field in the Ethernet frame.
Configure the Map

The User to Network Interface (UNI) and the EVC must be configured for the map. A map
binds the UNI traffic to the EVC. To configure the map, complete the following procedure:
1. From the EVC‐Map Configuration prompt, set the UNI by typing either connect uni
ethernet or connect uni gigabit-ethernet followed by the port number in 1/0/
port format, and press ENTER.
2. From the EVC‐Map Configuration prompt, connect the new map to the EVC by typing
connect evc WORD, and press ENTER.
This attribute is the name of the EVC associated with the map and must be specified.
3. In addition, the following attributes for the map can be set:
a. If desired, type match broadcast, match multicast, and/or match unicast.
To remove an attribute type no match broadcast, no match multicast, or no
match unicast.
b. CE VLAN ID: This adds the customer edge VLAN ID to the match criteria of the
map. To set this value, type match ce-vlan-id <0-4094>. To remove this
attribute from the match criteria, type no match ce-vlan-id.
c. CE VLAN Priority: This adds the customer edge VLAN priority to the match
criteria of the map. To set this value, type match ce-vlan-pri <0-7>. To remove
this attribute from the match criteria, type no match ce-vlan-pri. A range of
values can be specified as part of this command.
d. Discard: If this value is set, the NetVanta discards all traffic that matches the maps
match criteria. To enable discarding traffic, type connect discard. To disable,
type no connect discard. This connection takes the place of the connection to
the EVC.
NOTE
If the map was previously connected to an EVC, it will have to be reconnected
after the no connect discard command is used.
e. Differentiated Services Code Point (DSCP): This adds the Internet Protocol DSCP of
the customer traffic to the match criteria of the map. To set this value, type match
dscp <0-63>. To remove this attribute from the match criteria, type no match
dscp. A range of DSCP values can be entered for this command.
65K510DEP08-1A 4-25
f. L2CP: This configures the map to pass only layer 2 control protocol traffic. To
enable, type match l2cp. To remove this from the match criteria, type no match
l2cp.
4. From the EVC‐Map Configuration prompt, enable the map by typing no shutdown, and
press ENTER.
7. To save the changes to non‐volatile memory, type write, and press ENTER.
8. From the Enable prompt, view the new map by typing show evc-map WORD, and press
ENTER.
This command also displays the EVC and UNI that the map is attached to.
Once this process is completed, data can be run through the system.
Map Example
The following is a sample output of the show interfaces map command for map‐2010.
MyNV838#show evc-map my_test_map
EVC-map Status : Running - Enabled
Connected EVC : evc2010
Policer : None
Connected UNI : Ethernet 1/0/1
Match Traffic Type : Broadcast
Match Traffic Type : Multicast
MyNV838#
4-26 65K510DEP08-1A
Section 4, EoCu Provisioning - Provision Policers in the NetVanta 838
Provision Policers in the NetVanta 838

• Definition of Policers
• Steps for configuring Policers
• Policer example
Policer Definition
Policing is a rate based admission control function utilizing a leaky bucket alogrithm (see
Figure 4‐2). A policer keeps non‐conformant traffic from entering the network and degrading
other customers and/or services.
INGRESS
Dropped
CBS
EBS
EIR
CIR
Figure 4-2. Bucket Alogrithm
The Committed Information Rate (CIR) equals the rate guaranteed to the user. All traffic flow
below this rate is considered “green”.
The Excess Information Rate (EIR) equals the rate above and beyond the CIR that is allowed to
pass through the policer. This traffic is marked “yellow” by setting the DEI/CFI bit on the
802.1q VLAN tag. If set to zero, the policer is considered a one rate policer (green only, no
yellow). If set to non‐zero, the policer is considered a two rate policer.
65K510DEP08-1A 4-27
The Committed Burst Size (CBS) equals the amount of bytes the traffic is allowed to burst
above and beyond the CIR before it falls into the EIR “bucket”. The traffic is still left as green
and is unmarked.
The Excess Burst Size (EBS) equals the amount of bytes the traffic is allowed to burst above
and beyond the EIR before it is marked as red and discarded. This traffic is marked as yellow.
NOTE
If a two rate policer is used, such that traffic is marked yellow, the DEI/CFI bit
is used to mark the traffic. In the this application, the bit is being used to mark
the traffic as discard eligible. It is not being used as a CFI bit. Ensure that
other switching hardware in the network can handle this differentation, or the
traffic will be dropped by the hardware because the CFI usuage will render
the traffic invalid.
Configuration of DEI marking can be performed per interface using the
s-tag-dei command to enable marking or no s-tag-dei command
which forces all frames to have the bit set to 0 for CFI compatability mode.
The NetVanta 800s default to have this enabled for the EFM‐Groups and
disabled for the ethernet and gigabit ethernet interfaces.
Provisioning Steps
Policers can be mapped per EVC, EVC‐Map, Ethernet port, Gigabit‐Ethernet port, or EFM
bonding group. To create a policer and assign it to a traffic flow, complete the following
procedure:
1. From the Global Configuration prompt, type policer <policer_name>, and press
Enter to create the policer.
2. From the Policer Configuration prompt, type cir <cir_rate>, and press ENTER to set
the committed information rate, in kbps.
3. From the Policer Configuration prompt, type eir <eir_rate>, and press ENTER to set
the excess information rate, in kbps.
4. From the Policer Configuration prompt, type cbs <cbs_bytes>, and press ENTER to set
the committed burst size, in bytes.
5. From the Policer Configuration prompt, type ebs <ebs_bytes>, and press ENTER to set
the excess burst size, in bytes.
6. From the Policer Configuration prompt, type one of the following and press ENTER to
assign the policer to the desired element:
per custom evc-map <EvcMapName>
per evc <EvcName>
per uni efm-group 1/0/1
per uni ethernet 1/0/<ethernet_port>
per uni gigabit-ethernet 1/0/1
7. From the Policer Configuration prompt, type no shutdown, and press ENTER to enable
the policer.
8. From the Policer Configuration prompt, type end, and press ENTER to return to the Enable
prompt.
4-28 65K510DEP08-1A
Section 4, EoCu Provisioning - Provision Policers in the NetVanta 838
9. From the Enable prompt, type show policer, and press ENTER to view a list of policers
and the status of each.
Policer Example
The following is a sample output of the show policers command for map‐2010.
MyNV838#show policer my-policer
Policer Status : Running
Configured CIR : 10000 kbps
Actual CIR : 10024 kbps
Configured EIR : 20000 kbps
Actual EIR : 20049 kbps
Configured CBS : 3125 bytes
Actual CBS : 3126 bytes
Configured EBS : 12500 bytes
Actual EBS : 12503 bytes
Mode : Custom
Qualified EVC-maps:
Name Policed Status UNI
-----------------------------------------------------------------------
pubs Map Not Running Ethernet 1/0/1
Performance Total Discards
------------------------------------------------------------------------
Ingress Green Frames 0 0
Ingress Green Bytes 0 0
Ingress Yellow Frames 0 0
Ingress Yellow Bytes 0 0
Ingress Red Frames 0
Ingress Red Bytes 0
65K510DEP08-1A 4-29
Provision MAC Address Limiting and Aging

To prevent MAC Address storms at the customer Ethernet/Gigabit‐Ethernet ports, the
NetVanta 800 series supports MAC Address Limiting. The NetVanta learns MAC addresses
from traffic ingressing the customer interface; once the NetVanta learns the provisioned limit,
it does not allow any additional MAC addresses to pass toward the network. The MAC
Address limit can be set to any value from 1 to 100. MAC Address Limiting can also be
disabled. By default, NetVanta has MAC Address Limiting disabled.
If enabled, MAC Address aging can be used. By default, the MAC Aging timeout is 5
minutes. The MAC Aging Timeout can be set to any value from 1 to 3600 seconds. If set to
zero, MAC Aging is disabled, and learned MAC addresses are locked.
To set the MAC Address Limit count and aging values, complete the following steps:
2. From the Global Configuration prompt, access the Ethernet Configuration prompt or the
Gigabit‐Ethernet Configuration prompt by completing one of the following:
• Type interface ethernet 1/0/port, and press ENTER to access the Ethernet
Configuration prompt, where port is any value from 1 to 4
• Type interface gigabit-ethernet 1/0/1, and press ENTER to access the Gigabit‐
Ethernet Configuration prompt
3. Type mac limit <# of MAC addresses>, and press ENTER to set the maximum number
of MAC Addresses allowed on the selected interface, from 1 to 100 addresses.
NOTE
To disable MAC limiting, type no mac limit, and press ENTER.
4. Type mac aging-time <timeout_value>, and press ENTER to set the MAC Address

Aging Timeout value for the selected interface, where timeout_value is the new timeout
value in seconds, between 0 (MAC aging is disabled) and 3600 seconds.
4-30 65K510DEP08-1A
Section 4, EoCu Provisioning - Disable Unused NetVanta 838 Interfaces
Disable Unused NetVanta 838 Interfaces

The NetVanta 838 declares alarms for all unused interfaces (SHDSL, EFM, Ethernet, and
Power Feed). To clear these alarms once the 838 is turned up, the appropriate interfaces must
be shut down.
This subsection details the following information
• Disable the SHDSL interfaces
• Disable the Ethernet interfaces
• Disable the Gigabit‐Ethernet interface
• Disable the power feed alarms
• Clear the alarm log
Disable the SHDSL Interfaces

For each unused SHDSL port in the EFM Bonding Group, complete the following procedure:
NOTE
This must be done to clear the SHDSL loss of signal and EFM near end sync
alarms.
2. From the Global Configuration prompt, access the unused SHDSL portʹs configuration
prompt by typing interface shdsl 1/0/<port>, and press ENTER.
3. From the SHDSL Interface Configuration prompt, shut the SHDSL port down by typing
shutdown, and press ENTER.
4. Repeat steps 2 to 3 for the remaining unused SHDSL ports.
5. From the SHDSL Interface Configuration prompt, type exit, and press ENTER to return to
the Global Configuration prompt.
6. From the Global Configuration prompt, type interface efm-group 1/0/1, and press
ENTER to access the EFM Bonding Group Configuration prompt.
7. Remove the SHDSL port from the bonding group by typing no link <slot/port>,
and press ENTER. For NetVanta products, the slot is always zero.
8. Repeat step 7 to remove all unused ports from the EFM bonding group.
Once all unused SHDSL interfaces have been disabled, all SHDSL and EFM bonding group
alarms should be cleared in the alarm log, and the EFM LED should be lit solid green, if there
are no other issues. Also, the partial EFM group alarm should clear.
65K510DEP08-1A 4-31
Disable Ethernet Interfaces

For each Ethernet port that is not in use for customer services, complete the following
procedure:
NOTE
This must be done to clear the Ethernet link down alarms.
2. From the Global Configuration prompt, access the unused Ethernet Port Configuration
prompt by typing interface ethernet 1/0/<port>, and press ENTER.
3. Disable the Ethernet port down by typing shutdown, and press ENTER.
The Ethernet link down alarm should now be cleared for this port in the alarm log, and
the portʹs LED should be off.
4. Repeat steps 2 and 3 for the remaining unused Ethernet ports.
Once all unused Ethernet ports have been disabled, all Ethernet alarms should be cleared
in the alarm log.
Disable the Gigabit-Ethernet Interface

To disable the Gigabit‐Ethernet port, complete the following procedure:
NOTE
A port must be placed out of service, regardless of SFP presence, to remove
the alarms.
If the port is enabled and no SFP is present, there will be an alarm for no SFP
being present.
2. From the Global Configuration prompt, access the Gigabit‐Ethernet Port Configuration
prompt by typing interface gigabit-ethernet 1/0/1, and press ENTER.
3. Disable the Gigabit‐Ethernet port down by typing shutdown, and press ENTER.
The Gigabit‐Ethernet link down alarm should now be cleared in the alarm log, and the portʹs
LED should be off.
4-32 65K510DEP08-1A
Section 4, EoCu Provisioning - Disable Unused NetVanta 838 Interfaces
Disable Power Feed Alarms

To disable the power feed alarms, complete the following procedure:
NOTE
A power feed input cannot be disabled, but if both interfaces are not being
sourced with ±48 VDC or ±24 VDC powering, there is a power fail alarm
active for the unused input.
2. From the Global Configuration prompt, access the system alarm prompt by typing
system-alarm, and press ENTER.
3. If power feed A is unused, disable the power feed A alarm by typing no alarm enable
power-fail dc a, and press ENTER.
4. If power feed B is unused, disable the power feed B alarm by typing no alarm enable
power-fail dc b, and press ENTER.
The power A or B fail alarm should be cleared in the alarm log.
Once all unused interfaces are disabled, the alarms for these interfaces should now be cleared.
If all in‐use interfaces (SHDSL, Ethernet, Gigabit‐Ethernet, and power) are in non‐alarmed
states, then the Alarm LED on the NetVanta 838 should now be lit solid green.
Clear the Alarm Log

Before clearing the Alarm Log, the alarms must first be acknowledged.
To clear the Alarm Log, complete the following procedure:
1. From the Enable prompt, type force alarm acknowledge, and press ENTER.
2. Clear the alarm log by typing force alarm clear and pressing ENTER.
3. Verify there are no alarms by typing show alarm log and pressing ENTER.
65K510DEP08-1A 4-33
Save the NetVanta 838 Provisioning

After any changes are made, whether new services or port configuration, the user should
always save provisioning to non‐volatile memory in order to maintain those attributes during
power loss. From the Enable prompt, save provisioning by typing copy running-configu-
ration startup-configuration, and press ENTER.
The save completes within 5‐seconds and returns to the user prompt immediately. Once the
user prompt returns, the NetVanta has saved its configuration to non‐volatile memory.
4-34 65K510DEP08-1A
Section 5
BSM Provisioning

This section details the steps needed to provision a BSM application using the CH DS3 PPP/
MLPPP 3‐Port Line Module or the DS1 PPP/MLPPP 32‐Port Line Module.
In this Section
Topic See Page
BSM Overview 5‐2
Provision the Line Module 5‐4
Create a Point‐To‐Point Protocol Group 5‐7
Create an EVC Map on the Total Access 5000 5‐15
65K510DEP08-1A 5-1
BSM Overview
Figure 5‐1 displays an overview of the BSM deployment.
Edge
Router
IP
MSAP
Switch
Access Module
IPoE
Customer Module
Router
IP PPP
S-tag
S-tag S-tag
PPP GigE
DS1
GigE
Total Access
5000
Figure 5-1. BSM Diagram
In the upstream direction, customer IP data arrives at the access module encapsulated within
a Point‐to‐Point Protocol (PPP) group. T1s transport the PPP traffic, while the Network
Control Protocol (NCP) within the Link Control Protocol (LCP) initiated session manages the
operation of the PPP. The Interworking Function de‐encapsulates the customer IP from the
PPP and re‐encapsulates the customer IP in Ethernet. DSCP values from the PPP IP traffic map
directly to p‐bits to set the priority of the Ethernet frames, which then travel to the switch
module’s cross‐connect as a designated bridge. The switch module cross‐connects the bridge
to the appropriate S‐tagged VLAN on the GigE network ports designated for the upstream
edge router.
In the downstream direction, the switch module switches on the outer VLAN VID to the
appropriate bridge of an access module’s customer data flow. At the access module, the Inter‐
working Function de‐encapsulates the customer IP traffic from each Ethernet flow and re‐
encapsulates it in PPP, delivering it to one of four egress queues based on the Ethernet frame
p‐bit values.
5-2 65K510DEP08-1A
Section 5, BSM Provisioning - Provisioning Summary
To provision for BSM, complete the following procedure:
1. Provision the Line Module.
For more information, refer to “Provision the Line Module” on page 5‐4.
2. Create a Point‐to‐Point Protocol (PPP) group consisting of T1 interfaces, and assign the IP
address of the subtended device, the IP address of the Edge router, and any DNS
addresses to the created PPP group.
The IP address and the DNS addresses are pushed down to the customer router
subtended off the Total Access 5000.
For more information, refer to “Create a Point‐To‐Point Protocol Group” on page 5‐7.
3. Create an EVC to connect the PPP group to a VLAN going out the Gigabit Ethernet port,
to the Edge router.
4. Create an EVC map to define the DSCP‐to‐priority bit mapping and to create the EVC‐to‐
PPP group mapping.
For more information, refer to “Create an EVC Map on the Total Access 5000” on page 5‐
15.
65K510DEP08-1A 5-3
Provision the Line Module

This section details provisioning for the following modules:
• CH DS3 PPP/MLPPP 3‐Port Line Module
• DS1 PPP/MLPPP 32‐Port Line Module
Provision the CH DS3 PPP/MLPPP 3-Port Line Module

Administration Status
The CH DS3 PPP/MLPPP 3‐Port Line Module card service state must be set to In Service, Out
of Service, or Out of Service‐Maintenance.
NOTE
• If the card service state is set to Out of Service‐Maintenance, normal
• Line code and line buildout cannot be provisioned for either the DS3 or
DS1.
For traffic to pass, the CH DS3 PPP/MLPPP 3‐Port Line Module must be enabled.
prior releases.
Table 5-2. Line Module Administration States

shutdown maintenance Out of Service, In the no shutdown state, traffic passes

Maintenance but no alarms are generated. Alarms are
suppressed and no evidence of the alarm
is shown.
shutdown Out of Service, In the no shutdown state, no traffic

Unassigned passes and no alarms are generated.
procedure:
NOTE
typically 1.
5-4 65K510DEP08-1A
Section 5, BSM Provisioning - Provision the Line Module
• Type no slot shutdown <shelf/slot>, and press ENTER to take a slot In Service
• Type slot shutdown maintenance <shelf/slot>, and press ENTER to take a slot
Out of Service Maintenance
• Type slot shutdown <shelf/slot>, and press ENTER to take a slot Out of Service,
Unassigned
3. From the Global Configuration prompt, type interface t3 <shelf/slot/
port:channel>, and press ENTER.
4. From the T3 Interface Configuration prompt, type description LINE, and press ENTER
to configure the Circuit ID.
5. From the T3 Interface Configuration prompt, type framing [cbit|m23], and press
ENTER to select the framing mode.
6. From the T3 Interface Configuration prompt, provision the T3 port administration state
by performing one of the following commands:
• Type no shutdown, and press ENTER to take a port In Service
• Type shutdown maintenance, and press ENTER to take a port Out of Service‐Mainte‐
nance
• Type shutdown, and press ENTER to take a port Out of Service‐Unassigned
7. Repeat steps 3‐6 for each DS3 port that needs to be provisioned.
8. From the T3 Interface Configuration prompt, type exit, and press ENTER to return to the
9. From the Global Configuration prompt, type interface t1 <shelf/slot/port>, and
press ENTER.
11. From the T1 Interface Configuration prompt, type framing [d4|esf], and press ENTER
to select the framing mode.
• Type shutdown maintenance, and press ENTER to take a port Out of Service, Mainte‐
nance
• Type shutdown, and press ENTER to take a port Out of Service, Unassigned
65K510DEP08-1A 5-5
Provision the DS1 PPP/MLPPP 32-Port Line Module Adminis-

tration Status
The DS1 PPP/MLPPP 32‐Port Line Module card service state must be set to In Service, Out of
Service, or Out of Service‐Maintenance.
NOTE
• If the card service state is set to Out of Service‐Maintenance, normal
• Line code and line buildout cannot be provisioned for DS1.
For traffic to pass, the DS1 PPP/MLPPP 32‐Port Line Module must be enabled.
prior releases.
Table 5-3. DS1 Administration States

shutdown maintenance Out of Service, In the no shutdown state, traffic passes

Maintenance but no alarms are generated. Alarms are
suppressed and no evidence of the alarm
is shown.
shutdown Out of Service, In the no shutdown state, no traffic

Unassigned passes and no alarms are generated.
procedure:
NOTE
typically 1.
Out of Service Maintenance
Unassigned
press ENTER.
5-6 65K510DEP08-1A
Section 5, BSM Provisioning - Create a Point-To-Point Protocol Group
5. From the T1 Interface Configuration prompt, type framing [d4|esf], and press ENTER
to select the framing mode.
nance
Create a Point-To-Point Protocol Group

• Definition of a PPP group
• Steps for creating and configuring the PPP group
• PPP example
• Steps for adding a link to the PPP group
PPP Group Definition

Creating a PPP group provides a way to bond, or join, several physical links, such as multiple
T1s, into a single group. As part of the creation, a peer IP address, default gateway, and DNS
addresses are assigned to the group.
PPP is used in networking and is a data link protocol that transports data packets between
two networking nodes via a simultaneous, bi‐directional connection over synchronous and
ansynchronous circuits. The data packets are delivered in order and can be used over a variety
of hosts, or network layer protocols.
PPP depends on two separate protocols for operation: LCP and NCP. LCP is necessary to
verify, configure, and test the link connections. NCP is an assembly of protocols used to verify
and configure the variety of network layer protocols over which PPP can be used. PPP is also
capable of being used over such physical networks as serial cable, phone line, and trunk line.
PPP is used by Internet Service Providers (ISPs), which use encapsulated forms of PPP to
access Digital Subscriber Line (DSL) internet, which are Point‐to‐Point Protocol over Ethernet
(PPPoE) and Point‐to‐Point Protocol over ATM (PPPoA).
65K510DEP08-1A 5-7
Provisioning Steps
This procedure creates a PPP group at the CH DS3 PPP/MLPPP 3‐Port or DS1 PPP/MLPPP 32‐
Port Line Module that bonds the DS1 channels passing within the physical layer ports of the
access module together into a PPP group. The DS1 PPP/MLPPP 32‐Port Line Modules uses
unchannelized DS1s.
To create a new PPP group, complete the following procedure:
bal Configuraton prompt.
2. From the Global Configuration prompt, type interface ppp-group <shelf/slot/
group>, and press ENTER to create the PPP group and access the PPP Group
Table 5‐4 displays the list of variables for connecting the PPP group.
Table 5-4. PPP Group Connecting Variables
Syntax Description
shelf Enter the shelf number. If provisioning a single‐node configuration, enter 1.
slot Enter the slot number of the DS3 module.
group Enter the unique group number of the new PPP group.
3. From the PPP Group Configuration prompt, type alias WORD, and press ENTER to specify
a text string alias that can be used to reference the PPP group, where WORD is the name
of the alias.
NOTE
If creating a name with spaces, quotes must be used. For example, alias
“PPP Group A”.
4. From the PPP Group prompt, type one of the following commands:
• To provision the CH DS3 PPP/MLPPP 3‐Port Line Module, type link <slot/
port:channel>, and press ENTER to add a DS1 channel to the PPP group
• To provision the DS1 PPP/MLPPP 32‐Port Line Module, type link <slot/port>,
and press Enter to add a DS1 to the PPP group
Repeat this step to add additional DS1 channels to the PPP group.
Table 5‐5 displays the list of variables for the PPP link.
Table 5-5. PPP Link Variables
Syntax Description
slot Enter the slot number of the selected module.
port Enter the port number of the selected interface.
channel* Enter the DS1 channel number within the specified DS3 interface.
* ‐ Channel is only used for the CH DS3 PPP/MLPPP 3‐Port Line Module
5-8 65K510DEP08-1A
5. From the PPP Group prompt, type peer default ip address A.B.C.D, and press

Enter to set the PPP group peer IP address.
NOTE
A.B.C.D is the IP address of the subtended device.
6. From the PPP Group prompt, type peer default ip default-gateway A.B.C.D,

and press ENTER to set the PPP group peer default gateway address.
NOTE
A.B.C.D is the IP address of the default gateway.
7. From the PPP Group prompt, type peer default ip dns A.B.C.D E.F.G.H, and

press ENTER to set the PPP group peer DNS addresses.
NOTE
A.B.C.D is the IP address of the primary DNS and E.F.G.H is the IP address of
the secondary DNS. Specifying the secondary DNS is optional.
8. From the PPP Group prompt, type no shutdown, and press ENTER to activate the PPP
group.
9. From the PPP Group prompt, type end, and press ENTER to return to the Enable prompt.
The PPP group is now created.
10. From the Enable prompt, type show interfaces ppp-group <shelf/slot/group>,
and press ENTER to view the PPP group configuration and status.
Delete a PPP Group

To delete a PPP group, complete the following steps:
2. From the Global Configuration prompt, type no interface ppp-group <shelf/
slot/group>, and press ENTER to delete the specified PPP group.
3. From the Global Configuration prompt, type end, and press ENTER to return to the Enable
prompt.
65K510DEP08-1A 5-9
PPP Group Example

The following example creates a PPP group that includes slot 3, DS3 #2, and DS1 port 17. It
assigns the subtended device of the IP address, 192.168.1.2, with a default gateway of
192.168.1.254. It also sets the primary DNS as 192.167.2.13. This example is for the CH DS3
PPP/MLPPP 3‐Port Line Module.
PPP Group 1/3/5 {} is ENABLED and DOWN
Interface Status:
Active Slot : 3
Available Links : 3/2:17
LCP State : REQSENT
NCP State : INITIAL
IP Address Configuration : Static IP
Peer IP Address : 192.168.1.2
Peer IP Gateway : 192.168.1.254
Peer IP Primary DNS : 192.167.2.13
Peer IP Secondary DNS : 0.0.0.0
Multilink : rejected
Number of Active Links : 1
Fragment : rejected
Local/Remote MRRU : 0/0
N2F-F2N Small Seq #s : rejected-rejected
Local ED : Not Available
Remote ED : Not Available
Local/Remote MRU : 1500/1500
Running Totals:
Tx L3 Packets : 4196
Tx Packets : 16346
Tx Octets : 411059
Tx Discard Count : 0
Tx Error Count : 0
Rx L3 Packets : 4282
Rx Packets : 16431
Rx Octets : 405541
Rx Discard Count : 8
Rx Error Count : 0
TA5000#
5-10 65K510DEP08-1A
Add a Link to the PPP Group

To add a link to the PPP group, complete the following steps:
1. From the Enable prompt, type show interfaces ppp-group, and press ENTER to view
all PPP groups in the Total Access 5000.
NOTE
As an alternative, type show ppp-group <shelf> or show ppp-group
<shelf/slot> to see an abbreviated list of ppp‐groups/links on the shelf or
the slot.
group>, and press ENTER to access PPP Group Interface Configuration prompt.
4. If adding a second link, Multilink PPP must be enabled. From the PPP Group Interface
Configuration prompt, type ppp multilink, and press ENTER.
5. From the PPP Group Interface Configuration prompt, type one of the following
commands:
• To provision the CH DS3 PPP/MLPPP 3‐Port Line Module, type link <slot/
port:channel>, and press ENTER to add a link to the group
• To provision the DS1 PPP/MLPPP 32‐Port Line Module, type link <slot/port>,
and press ENTER to add a link to the group
Delete a Link from the PPP Group

To remove a link from the PPP group, complete the following steps:
group>, and press ENTER to access PPP Group Interface Configuration prompt.
3. From the PPP Group Interface Configuration prompt, type one of the following
commands:
• To provision the CH DS3 PPP/MLPPP 3‐Port Line Module, type no link <slot/
port:channel>, and press ENTER to remove a link to the group
• To provision the DS1 PPP/MLPPP 32‐Port Line Module, type no link <slot/
port>, and press ENTER to remove a link to the group
65K510DEP08-1A 5-11

EVC Definition
which an S‐tag path is created in the system. The S‐tag corresponds to the VLAN ID.
the network ports on the GigE SM and is S‐tag switched to the appropriate slot and PPP
group.
frames
Each EVC typically has an associated EVC VLAN tag whose VLAN ID is unique among other
EVCs in the MEN. The EVC VLAN tag allows the EVC to be identified and separated from
other EVCs.
At a minimum, two items must be set up for the EVC: the MEN interface it will use and the
S‐tag it will use.
The EVC specifies to which service provider VLAN the new PPP group interface is tied. It also
specifies the following:
• The upstream Metro Ethernet Network (MEN) ports: a Gigabit‐Ethernet port on the GigE
SM, or a Gig‐E link aggregation group
• The service provider VLAN (s‐tag)
5-12 65K510DEP08-1A
Section 5, BSM Provisioning - Create an EVC Cross Connect
EVC Guidelines
To ensure valid provisioning, observe the following guidelines when creating an EVC:
• Two EVCs are considered to be duplicate if they both have the same values for the S‐tag.
• The S‐tag value for the EVC cannot equal the management VLAN ID
S-tag Function
0, 1, 4095 Reserved
Provisioning Steps
This process establishes a connection between the physical port (Gigabit‐Ethernet port on the
GigE SM) and the virtual network (the PPP group connected to the customer router).
NOTE
The connect men-port gigabit-ethernet command entry applies to the
active GigE SM, independent of which GigE SM is actually specified, in an
Active/Standby configuration.
enable the EVC.
Enable prompt.
The EVC is now created.
7. From the Enable prompt, type show evc <evc_name>, and press ENTER to view the new
EVC status.
The PPP group and EVC has been created and enabled.
65K510DEP08-1A 5-13
EVC Example
The following example creates the EVC my_evc_123. Then the EVC maps VLAN 1951 from
Gigabit‐Ethernet port 1 to PPP group 1/3/5.
TA5000(config)# evc my_evc_123
TA5000(config-evc my_evc_123)# s-tag 1951
TA5000(config-evc my_evc_123)# connect men-port gigabit-ethernet <1/A/1>
TA5000(config-evc my_evc_123)# no shutdown
TA5000(config-evc my_evc_123)# end
TA5000# show evc my_evc_123
EVC my_evc_123
S-TAG : 1951
Admin Status : Enabled
Interfaces : GIG-E 1/ A/ 1
: PPP 1/ 3/ 5
MAC Learning Mode : Off
MAC Aging Time : 0
TA5000#
5-14 65K510DEP08-1A
Section 5, BSM Provisioning - Create an EVC Map on the Total Access 5000
Create an EVC Map on the Total Access 5000

• Definition of a map and DSCP
• Guidelines for creating a map
• EVC map example
Map and DSCP Definition

called a map. Each map is associated with a single customer and specifies the Class of Service
(CoS) behavior of the traffic from the customer.
The EVC map sets up the mapping of customer Differentiated Services Code Point (DSCP)
value (in the IP packet) to MEN priority bit value (in the Ethernet frame). For example, the
DSCP value 60 of traffic coming from the customer could be mapped to service provider
VLAN priority level 4.
DSCP is the marker used to display as a header field in the packet classification of IP packets.
The DSCP serves the purpose of initiating network routers to employ differentiated grades of
service to several packet streams.
Map Guidelines
To ensure valid provisioning, observe the following guidelines when creating a map:
– UNI port/PPP‐group
• When multiple maps are applied to a common EVC, each map must contain the same
PPP‐group. Multiple PPP‐groups cannot be mapped to a common EVC
NOTE
If the user does not specify the DSCP match criteria or MEN priority value for
the map and chooses to use the default values, the map is still required to
complete the creation of the BSM service.
65K510DEP08-1A 5-15
Provisioning Steps
To create the EVC map on the Total Access 5000, complete the following steps:
2. From the Global Configuration prompt, type evc-map WORD <shelf/slot>, and press
ENTER to create an EVC map in the specified shelf and slot, where WORD is the name of
the new EVC map.
NOTE
If creating a name with spaces, quotes must be used. For example, evc-map
“test map” 1/21.
3. From the EVC Map Interface Configuration prompt, type connect evc WORD, and press

ENTER to connect the EVC map to the EVC, where WORD is the alias of the EVC.
4. From the EVC Map Interface Configuration prompt, type connect uni ppp-group
<shelf/slot/group>, and press ENTER to connect the EVC map to the PPP group.
Table 5‐7 displays the list of variables for connecting the PPP group.
Table 5-7. PPP Group Connecting Variables
Syntax Description
shelf Enter the shelf number. If provisioning a single‐node configuration,
enter 1.
slot Enter the slot number of the DS3 module.
group Enter the a unique group number of the new PPP group.
5. From the EVC Map Interface Configuration prompt, type match dscp <0-63>, and

press ENTER.
The match dscp <0‐63> command specifies the DSCP to match for traffic received from
the customer (PPP group).
NOTE
• Multiple DSCP values can be listed, so that several maps can be mapped to
a MEN priority value in one step rather than several. For example, the
command, match dscp 5,12,24-37, would be valid
• Provisioning of the DSCP matching criteria is optional. If a DSCP matching
criteria is not specified for an EVC map, then all traffic coming from the
PPP group matches the given EVC map, and that map is used instead. If,
for a particular PPP group, there are maps that specify the DSCP and one
that does not, the EVC map without a DSCP specifier receives any traffic
that does not match the other EVC maps
• If DSCP traffic received from the customer that does not match a
configured map, it is still passed onto the EVC VLAN, with priority zero.
6. From the EVC Map Interface Configuration prompt, type men-pri <0-7>, and press

ENTER.
5-16 65K510DEP08-1A
Section 5, BSM Provisioning - Create an EVC Map on the Total Access 5000
The men‐pri <0‐7> command specifies the p‐bit value to map the traffic to in the
upstream direction.
NOTE
The EVC map default is men‐pri 0.
7. From the EVC Map Interface Configuration prompt, type no shutdown, and press ENTER
to enable the EVC map.
The EVC map is now created.
8. From the EVC Map Interface Configuration prompt, type end, and press ENTER to return
to the Enable prompt.
9. From the Enable prompt, type show evc-map WORD <shelf/slot>, and press ENTER to
view the EVC map configuration and status.
Upon completing the PPP group, EVC, and EVC map provisioning, the BSM service provi‐
sioning is complete. IP traffic from the customer, arriving encapsulated in PPP frames, will be
extracted from the PPP traffic, and re‐encapsulated into Ethernet frames with VLAN and p‐bit
values dictated by the EVC and EVC map settings. Ethernet traffic from the network will have
its IP contents extracted and re‐encapuslated into PPP frames for passage down the PPP
group to the customer router.
EVC Map Example

The following example creates the EVC map test_map.
TA5000(config)# evc-map test_map 1/21
TA5000(config-evc test_map)# connect evc test_evc_100
TA5000(config-evc test_map)# connect uni ppp-group 1/3/5
TA5000(config-evc test_map)# match dscp 41
TA5000(config-evc test_map)# men-pri 5
TA5000(config-evc test_map)# no shutdown
TA5000(config-evc test_map)# end
TA5000# show evc test_map 1/21
Name State Status
----------------------------------------------------------------------------
test_map 1/21 Enabled Running
Match Criteria Destination

--------------------------------------------------------------------------
UNI: ppp-group 1/3/5 EVC: A_803_evc1 (501)
DSCP: 41 MEN-Pri: 5
TA5000#
65K510DEP08-1A 5-17
5-18 65K510DEP08-1A
Section 6
EoTDM Provisioning

The DS3 Unchannelized EFM 4‐Port Line Module (DS3 EFM 4‐Port) interoperates with the
NetVanta 873 by using three DS3s and delivering over 100 Mbps over a capable link like
SONET or radio. The NetVanta 873 and DS3 EFM 4‐Port, when combined, provide a complete
end‐to‐end packet transport under one umbrella and same network management system.
The DS3 Channelized EFM 3‐Port Line Module (DS3 EFM 3‐Port) interoperates with the
NetVanta 818 by using three DS3s and delivering over 100 Mbps over a capable link like
SONET or radio. The NetVanta 818 and DS3 EFM 3‐Port, when combined, provide a complete
end‐to‐end packet transport under one umbrella and same network management system.
In this Section
Topic See Page
EoTDM Overview 6‐2
Provision the Line Module 6‐4
Create an EFM Bonding Group 6‐6
Create an EVC 6‐17
65K510DEP08-1A 6-1
EoTDM Overview
This subsection details the steps needed to provision EoTDM using the DS3 Ethernet in the
First Mile (EFM) Access Module and the NetVanta 800. This section provides the following
information:
• Inband management configuration for the SCM and the NetVanta 800 Network Circuit
Terminating Equipment (NCTE)
• Minimum configuration for traffic to pass from the GigE SM port to an Ethernet port on
the NetVanta 800
Figure 6‐1 and Figure 6‐2 display an overview of the EoTDM deployment.
Total Access 5000 NetVanta 873

EoTDM Available EVC’s and
Management VLAN
System Diagram Pushed Down by
Total Access 5000
Bridge Group #1
EFM
Bridge DS3 Group #1
EP2 PORT 1 DS3 #1 5 ETH 1
VLAN
EP1 Group #1 3 MAP 2010 2010
DS3
1 PORT 2 DS3 #2 ETH 2
NET 1
2 DS3 4 MAP 2020
PORT 3 DS3 #3
6 ETH 3
VLAN
EVC 2020
2020
EP1 PORT 4
EP2 ETH 4
Bridge Group
“Phycical Links”
GigE VLAN
2010 +2020
Management
VLAN 2048
Metro
Ethernet
Network
• End Point 1→ PORT, NET 1 EVC EVC-2010 EVC EVC-2020
• End Point 2→ Bridge, Bridge Group 1 MEN- PORT EFM-Group 1 MEN- PORT EFM-Group 1
• S-tag = 2010 S-TAG 2010 S-TAG 2020
• End Point 2→ Bridge, Bridge Group 1 UNI ETH 1 UNI ETH 3
Figure 6-1. EoTDM (Clear Channel) Diagram
Total Access 5000 NetVanta 818

EoTDM Available EVC’s
System Diagram Pushed Down by

Total Access 5000
Bridge Group #1
EFM
Bridge Group #1
EP2 PORT 1 DS1 #1 5 ETH 1
VLAN
EP1 Group #1 3 MAP 2010 2010
DS3s DS1s
1 PORT 2 DS1 #2 ETH 2
NET 1
2 4 MAP 2020
PORT 3 DS1 #3
6 ETH 3
MUX VLAN
EVC 2020
2020
EP1
EP2 ETH 4
Bridge Group
“Phycical Links”
GigE Q VLAN
2010 +2020
Metro
Ethernet
Network
• End Point 1→ PORT, NET 1 EVC EVC-2010 EVC EVC-2020
• End Point 2→ Bridge, Bridge Group 1 MEN- PORT EFM-Group 1 MEN- PORT EFM-Group 1
• S-tag = 2010 S-TAG 2010 S-TAG 2020
• End Point 2→ Bridge, Bridge Group 1 UNI ETH 0/1 UNI ETH 0/3
Figure 6-2. EoTDM (Channelized) Diagram
6-2 65K510DEP08-1A
Section 6, EoTDM Provisioning - Provisioning Summary
the NetVanta 800, complete the following:
1. Provision the DS3 EFM 4‐Port or DS3 EFM 3‐Port Line Module.
For more information, refer to “Provision the Line Module” on page 6‐4.
2. Create an EFM bonding group at the GigE SM that bonds a set of DS3 ports on the DS3
EFM line module together.
The bonding group acts as the data flow access point to the NetVanta 800 and is the path
down which the management configuration is pushed.
For more information, refer to “Create an EFM Bonding Group” on page 6‐6.
3. Create an Ethernet Virtual Circuit (EVC) at the Total Access 5000 that connects the EFM
group to the Gigabit Ethernet port of the GigE SM.
• The GigE SM knows where to send the tagged traffic coming in from the gigabit
network port
• The GigE SM pushes the available tags to each EFM bonding group and to each
NetVanta 800 for the local NetVanta 800 provisioning
The EVC is a logical connection point into the EFM group.
NOTE
• Multiple EVCs can be created for a given EFM group.
• For the NetVanta, the shelf is always 1 and the slot is always zero.
page 6‐27.
65K510DEP08-1A 6-3
Provision the Line Module

This section details provisioning the Line Module service state.
Provision the Line Module Administration Status

The DS3 EFM 4‐Port or DS3 EFM 3‐Port card service state must be set to IS or Out of Service,
Maintenance.
NOTE
If the card service state is set to Out of Service, Maintenance, normal
For traffic to pass, the DS3 EFM 4‐Port or DS3 EFM 3‐Port module must be enabled.
prior releases.
Table 6-2. DS3 EFM 4-Port and DS3 EFM 3-Port Administration States

shutdown maintenance Out of Service, In the shutdown maintenance state, traf‐

Maintenance fic passes but no alarms are generated.

To set the module administration and port administration states, complete the following:
NOTE
typically 1.
slot Out of Service Maintenance
Service, Unassigned
3. From the Global Configuration prompt, type one of the following commands:
6-4 65K510DEP08-1A
Section 6, EoTDM Provisioning - Provision the Line Module
• To access the DS3 EFM 4‐Port, type interface t3 <shelf/slot/port>, and
press ENTER.
• To access the DS3 EFM 3‐Port, type interface t3 <shelf/slot/
port:channel>, and press Enter.
4. To configure the Circuit ID, type description LINE, and press ENTER.
5. Provision the DS3 port administration state by performing one of the following
commands:
• Type no shutdown, and press ENTER to take the port In Service
• Type shutdown maintenance, and press ENTER to take the port Out of Service,
Maintenance
• Type shutdown, and press ENTER to take the port Out of Service, Unassigned
6. To set the alarm thresholds, type thresholds [cvc-p|cv-l|cvp-p|
escp-p|es|esp-p|sefs-p|sescp-p|uas-p] [15 minute|24 hour]
7. Repeat steps 3‐8 for each DS3 port that needs to be provisioned.
65K510DEP08-1A 6-5
Create an EFM Bonding Group

• Definition of an EFM bonding group
• Steps for configuring the EFM bonding management
• Steps for modifying an existing bridge
• Auto‐Provision the DS3 pairs using EZ‐EFM
• EFM bonding overhead description
Bonding Group Definition

A bonding (bridge) group is defined as “Virtual LAN terminology for a group of switch inter‐
faces assigned to a singular bridge unit and network interface.”
The EFM bonding (bridge) group bundles multiple DS3 lines together to provide bandwidth
equal to the sum of the DS3s bonded. This process provides the necessary bandwidth for
service. For example, three DS3s bonded together provide three times the speed of 1 DS3
(3 x 44.736 = 134.208 Mbps of bandwidth) to transport ethernet traffic.
Provisioning Steps
This procedure creates an EFM bonding group at the GigE SM that bonds the physical layer
ports (DS3) of the access module(s) together.
To create a new bonding group, complete the following:
Configuraton prompt.
2. From the Application Configuration prompt, type ez-efm <shelf>, and press ENTER to
start the EZ Ethernet application.
3. From the EFM Configuration prompt, type one of the following commands to create an
EFM Bonding Group:
• To provision the DS3 EFM 4‐Port, type create WORD <EFM links> <slot/port>
upstream <0-250000> downstream <0-250000> active-links-minimum
<1-n>, and press ENTER.
• To provision the DS3 EFM 3‐Port, type create WORD <EFM links> <slot/
port:channel> upstream <0-250000> downstream <0-250000> active-
links-minimum <1-n>, and press ENTER.
6-6 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EFM Bonding Group
Table 6‐3 displays the list of variables for the EFM bonding group.
Table 6-3. EFM Bonding Group Variables
Syntax Description
WORD Enter the name (up to 50 alphanumeric characters with no spaces or spe‐
cial characters) of the bonding group.
EFM links Enter the EFM links to add to the bonding group. Each link must be in the
slot/port:channel format.
active‐links‐minimum Enter the number of links in the group required to provide the upstream
and downstream rates. Any additional links will be hot standby links.
upstream/downstream The values after the upstream and downstream keywords are the
upstream and downstream rates for the bonding group.
Verify Bonding Group Creation

To verify that the bonding group was created, and determine the slot and group ID assigned
to the group, perform one of the following:
• From the Enable prompt, type show interfaces efm-group, and press ENTER to view
all EFM bonding groups in the Total Access 5000
• From the Enable prompt, type show table interfaces efm-group, and press ENTER
to view a table (with limited EFM group information)
• From the Enable prompt, type show efm-group 1, and press ENTER to see the links
assigned to all groups in the shelf along with the provisioned group rates
65K510DEP08-1A 6-7
EFM Bonding Group Example

The example below creates a bonding group on the DS3 EFM 3‐Port which includes slot 1,
ports 3 and 5, then displays the group status.
NOTE
If there is a problem with the creation of the group, an error message will
follow the create command. Otherwise, it is successful if no error message
follows the command.
TA5000# application
TA5000(app)# ez-efm 1
TA5000(app-ez-efm 1)# create my_bonding_group link 16/3:1-3:8
upstream 5000 downstream 5000 active-links-minimum 1
Done
TA5000(app-ez-efm 1)# exit
TA5000(app)# exit
TA5000# show interfaces efm-group
EFM Group 1/1/2 {MY_BONDING_GROUP} is ENABLED and UP
Provisioned Links : 1/3,1/5
Active Links : 1/3,1/5
Inhibited Links : None
UpStream Data Rate : 5120
DownStream Data Rate : 5120
Loopback : Disabled
XCV Threshold : 1e-7
XCV Link Removal : Enabled
TA5000#
6-8 65K510DEP08-1A
Configure EFM Bonding Management Provisioning

The NetVanta 800 Inband Management configuration is tied to the EFM bonding group.
Thus, when a NetVanta is replaced, the remote management configuration is pushed down so
that the NetVanta is immediately remote accessible when at least one DS3 link synchronizes.
NOTE
• If provisioning the NetVanta 800 locally, the Total Access 5000 overwrites
the Inband management provisioning when the DS3 ports synchronize
with the DS3 EFM access module.
• The Inband management of the NetVanta 800 is configured at the Total
Access 5000, and pus hed down to the NetVanta 800 as soon as
synchronization is achieved on one of the links of the bonded group.
To configure the EFM bonding group management provisioning, complete the following:
2. From the Global Configuration prompt, type interface efm-group <shelf/slot/
group>, and press ENTER to access the EFM Bonding Group Configuration prompt.
address A.B.C.D E.F.G.H, and press ENTER to provision the NetVanta Management
IP address (A.B.C.D) and subnet mask (E.F.G.H).
4. From the EFM Group Interface Configuration prompt, type subtended-host s-tag
<1-4094>, and press ENTER to provision the NetVanta Management VLAN.
default-gateway A.B.C.D, and press ENTER to provision the NetVanta Management
Gateway.
file-server default host A.B.C.D, and press ENTER to provision the NetVanta 800
Management TFTP server.
server chassis-id WORD, and press ENTER to provision the NetVanta SNMP system
name.
server community read-only WORD, and press ENTER to provision the read‐only
SNMP community.
server community read-write WORD, and press ENTER to provision the read‐write
SNMP community.
10. From the EFM Group Interface Configuration prompt, type end, and press ENTER to
NOTE
This information is sent to the NetVanta 800 by way of an overhead
management channel.
65K510DEP08-1A 6-9
Once completed and if the management VLANs of the GigE SM and the NetVanta 800 are
equivalent, the NetVanta 800 Command Line Interface (CLI) can be accessed via the Inband
Management VLAN.
Modify an Existing Bridge

There are two ways to modify an existing EFM bonding group. The EZ‐EFM application
allows the user to add or remove a link to/from a bonding group while simultaneously speci‐
fying the bonding group upstream and downstream data rates. The EZ‐EFM application
automatically re‐provisions all links in the group to the necessary link rates, whether the rate
is increased or decreased. The links retain and provide the provisioned data rate.
The second way to add or remove a link to/from a group is by directly modifying the EFM
bonding group in the EFM Bonding Group Configuration prompt. This method does not
result in a re‐provisioning of the links in the group, but can result in the links not being set to
the optimum rates, or even in the group not providing the specified data rate if links are
removed.
Modify a Bonding Group with EZ-EFM

To modify a bonding group using the EZ‐EFM application, complete the following:
3. From the EFM Configuration prompt, type one of the following commands to modify an
existing EFM Bonding Group:
• To provision the DS3 EFM 4‐Port, type modify <group_name> link <slot/
port> upstream <0-250000> downstream <0-250000> active-links-
minimum <1-n>, and press ENTER.
• To provision the DS3 EFM 3‐Port, type modify <group_name> link <slot/
Refer to Table 6‐3 on page 6‐7 for the list of variables for the EFM bonding group.
4. From the EFM Configuration prompt, type one of the following commands to remove
links from an existing EFM Bonding Group:
• To provision the DS3 EFM 4‐Port, type modify <group_name> no-link <slot/
port> upstream <0-250000> downstream <0-250000> active-links-
minimum <1-n>, and press ENTER.
• To provision the DS3 EFM 3‐Port, type modify <group_name> no-link <slot/
NOTE
For the modify command, all parameters must be specified, even if a
particular value is not being changed.
6-10 65K510DEP08-1A
Refer to Table 6‐3 on page 6‐7 for the list of variables for the EFM bonding group.

Modify a Bonding Group Directly

To modify a bonding group directly, complete the following:
2. From the Global Configuration prompt,type interface efm-group <group_name>,
and press ENTER to access the EFM Bonding Group Configuration prompt.
commands to add a link to the EFM Bonding Group:
• To provision the DS3 EFM 4‐Port, type link <slot/port>, and press ENTER.
• To provision the DS3 EFM 3‐Port, type link <slot/port:channel>, and press
ENTER.
commands to remove a link to the EFM Bonding Group:
• To provision the DS3 EFM 4‐Port, type no link <slot/port>, and press ENTER.
• To provision the DS3 EFM 3‐Port, type no link <slot/port:channel>, and press
ENTER.
5. From the EFM Group Interface Configuration prompt, type exit and press ENTER to
return to the Application Configuration prompt.
65K510DEP08-1A 6-11
EFM Bonding Overhead Description

Before being transported over the physical layer (DS3, T1, etc.), the EFM bonding engine first
encapsulates Ethernet frames into EFM fragments. EFM Fragment payloads can vary from 64
to 512 bytes depending on the Ethernet packet size. If an Ethernet Frame is 512 bytes or
smaller, it is placed into one EFM fragment. If the frame is between 513 and 1024 bytes, it is
split between two EFM fragments. If the frame is 1025 bytes or greater, it is split between three
EFM fragments.
Each EFM fragment has the following overhead:
• There are 2 bytes of overhead per fragment that are the same for all fragments: a start byte
and Ck byte (an EOF designator)
• The frame check sequence (FCS): The size of this depends on technology
• There are 2 additional overhead bonding header bytes
For DS3, this comes out to 8 overhead bytes per fragment. In addition, as part of the 64/65
EFM framing, there are codewords that are 64 payload bytes and 1 sync byte.
Using this information, the following equations can be used to determine the effective
percentage of the EFM bonding group that is available for customer Ethernet transport (for
DS3):
• Ethernet frames 512 bytes or smaller:
% Utilization = (Frame Size) / (Frame Size + 8)x (64/65)
• Ethernet frames between 513 and 1024 bytes, inclusive:
The equations above assume that the NetVanta is not adding an extra tag to the customer
traffic (ie. when the customer traffic is tagged, and the customer edge tag is not being
preserved). In any case where the customer tag is preserved (the most likely scenario), and the
NetVanta 800 is simply stacking the provisioned service provider tag (s‐tag) to the customer
tag (if present), the calculation must account for the additional 4 bytes for the s‐tag, as follows:
• For Ethernet frames 512 bytes or smaller:
• For Ethernet frames between 513 and 1024 bytes, inclusive:
To determine the EFM bonding group bandwidth that needs to be provisioned so that the
customerʹs commissioned rate is provided, divide the customer rate by this percentage:
Required EFM Group Rate = (Customer Commissioned Rate) / (% Utilization.
Following are example calculations for customer throughput percentage, given a fixed frame
size, assuming the NetVanta 800 is adding a VLAN tag:
• For 64 byte Ethernet frames (worst case scenario):
% Utilization = (64) / (64 + 12) x (64/65) = 82.9%
8 Mbps x .829 = 6.632 Mbps
(4 Mbps) / (.829) = 4.825 Mbps
6-12 65K510DEP08-1A
• For 1500 byte Ethernet frames:
% Utilization = (1500) / (1500 + 28) x (64/65) = 96.7%
8 Mbps x .967 = 7.736 Mbps
(4 Mbps) / (.967) = 4.137 Mbps
Another point of reference is the EFM bonding group utilization percentage that is seen
assuming uniform distribution of frame sizes, from 64 to 1518 bytes. This value is 96.0%
assuming the service provider VLAN tag is being added to the customer traffic. Assuming
uniform traffic size, the EFM group would need to be a factor of 1.042 greater than the
commissioned customer rate to provide the full customer rate.
The service provider is best suited to decide what traffic model it wants to use for network
planning, but the tools above should allow them to suitably determine the EFM Group
bandwidth needed to provide the customerʹs full traffic rate.
65K510DEP08-1A 6-13

EVC Definition
which an S‐tag path is created in the system. The S‐tag corresponds to the VLAN ID. For
example, in the EoTDM application an EVC cross‐connect is created between a physical
network port and a logical EFM bonding group. Traffic entering the network port on the
selected S‐tag is sent by the GigE SM to the DS3 EFM 4‐Port containing the bonding group and
then forwarded to the bonding group by the module.
the network ports on the GigE SM and is S‐tag switched to the appropriate slot. The DS3 EFM
4‐Port then decides how to send that traffic to the customer. Upstream traffic is switched to the
network in a similar manner.
NOTE
management VLAN, create a cross connect for the GigE SM to pass the
NetVanta 800 management traffic. When creating a cross connect, set up the
cross connect with an S‐tag equal to the NetVanta 800 management VLAN,
pointing to the appropriate EFM Group.

NOTE
When deployed in a Multi‐Node network, each EoTDM customer still
requires a unique S‐tag. The Total Access 5000 can not alert users if VLANs
are already in use on another Node.
6-14 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EVC Cross Connect
S-tag Function
0, 1, 4095 Reserved
Provisioning Steps
To create the EVC, complete the following:
NOTE

NOTE
The EFM bonding group name can be used in lieu of the shelf/slot/group
designation.
enable the EVC.
Enable prompt.
65K510DEP08-1A 6-15

Management VLAN.
CRAFT Port Login

To establish CLI communication with the product, complete the following:
• Any baud rate from the list of 9600, 19200, 38400, 57600, or 115200
• 8 data bits
• No parity
• 1 stop bit
• No flow control
NOTE
Remote Access Login

To remotely access the NetVanta 800, open a telnet session to the IP address configured in the
bridge group.
6-16 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EVC
Create an EVC
• EVC guidelines
• EVC example
EVC Definition
frames
This capability enables an EVC to provide data privacy and security similar to a Frame Relay
or ATM Permanent Virtual Circuit (PVC).
At a minimum, two items must be set up for the EVC: the MEN port it will use and the S‐tag it
will use.
NOTE
EVC Guidelines
– MEN port
– S‐tag
port, the S‐tag value for the EVC cannot equal the management VLAN ID
65K510DEP08-1A 6-17
Provisioning Steps
To create an EVC, complete the following:
EVC.
the Ethernet frame.
Configure the EVC

port and S‐tag, complete the following:
1. From the EVC Configuration prompt, type connect men-port efm-group 1/0/1, and
press ENTER to set the MEN‐port as an EFM bonding group of the NetVanta 800.
This attribute is the logical interface connected to the MEN. The possible options consist
of the Ethernet port(s) and bonding group(s) available on the NetVanta 800. In typical
configurations, the MEN port is specified as a bonding group.
press ENTER.
NOTE
5000 for this bonding group.
and press ENTER.
press ENTER.
7. To save the changes in non‐volatile memory, type write, and press ENTER.
6-18 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EVC
NOTE
If creating an EVC with the same S‐tag as the management traffic, the
NetVanta 800 will report a conflict.
EVC Example
EVC evc2010
S-TAG : 2010
MyNV800#
65K510DEP08-1A 6-19
Create an EVC Map

• Map example
Map Definition
called an EVC‐map. Each EVC‐map is typically associated with a single customer and
specifies parameters including the customer VLAN ID and Class of Service (CoS) behavior of
the traffic from the customer. Use a map to classify traffic for use by an EVC for forwarding
and for use by a policer for rate limiting.
Map Guidelines
– UNI port
– CE‐VLAN‐ID
port, the management VID value cannot equal the CE‐VLAN‐ID value of the map
to the EVC must have the same value of the CE‐VLAN‐ID attribute
• When multiple maps are applied to a single EVC, each map must have the same UNI.
Multiple UNIs cannot be mapped to a single EVC
6-20 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EVC Map
Provisioning Steps
To create the map, complete the following:
Configure the Map

binds the UNI traffic to the EVC. To configure the map, complete the following:
1. From the EVC‐Map Configuration prompt, set the UNI by typing either connect uni
ethernet or connect uni gigabit-ethernet followed by the ethernet port number
in 1/0/port format, and press ENTER.
The WORD attribute is the physical interface connected to the customer equipment. The
possible options consist of the Ethernet port(s) and bonding group(s) available on the
NetVanta 800. In typical configurations, the specified option is an Ethernet port.
3. In addition, the following attributes for the map can be set:
a. If desired, type match broadcast, match multicast, and/or match unicast.
To remove an attribute type no match broadcast, no match multicast, or no
match unicast.
b. CE VLAN ID: This adds the customer edge VLAN ID to the match criteria of the
map. To set this value, type match ce-vlan-id <0-4094>. To remove this
attribute from the match criteria, type no match ce-vlan-id.
c. CE VLAN Priority: This adds the customer edge VLAN priority to the match
criteria of the map. To set this value, type match ce-vlan-pri <0-7>. To remove
this attribute from the match criteria, type no match ce-vlan-pri. A range of
values can be specified as part of this command.
d. Discard: If this value is set, the NetVanta discards all traffic that matches the maps
match criteria. To enable discarding traffic, type connect discard. To disable,
type no connect discard. This connection takes the place of the connection to
the EVC.
NOTE
If the map was previously connected to an EVC, it will have to be reconnected
after the no connect discard command is used.
e. Differentiated Services Code Point (DSCP): This adds the Internet Protocol DSCP of
the customer traffic to the match criteria of the map. To set this value, type match
65K510DEP08-1A 6-21
dscp <0-63>. To remove this attribute from the match criteria, type no match

dscp. A range of DSCP values can be entered for this command.
f. L2CP: This configures the map to pass only layer 2 control protocol traffic. To
enable, type match l2cp. To remove this from the match criteria, type no match
l2cp.
press ENTER.
5. From the EVC‐Map Configuration prompt, type end, and press ENTER to return to the
Enable prompt.
6. To save the changes to non‐volatile memory, type write, and press ENTER.
ENTER.
This command also displays the EVC and UNI that the map is attached.
Once this process is completed, data can be run through the system. If untagged data is
sent into the NetVanta 800, the GigE SM Ethernet port transmits data tagged with the
appropriate S‐tag.
Map Example
MyNV800#show evc-map my_test_map
EVC-map Status : Running - Enabled
Connected EVC : evc2010
Policer : None
Connected UNI : Ethernet 1/0/1
Match Traffic Type : Broadcast
Match Traffic Type : Multicast
MyNV800#
6-22 65K510DEP08-1A
Section 6, EoTDM Provisioning - Create an EVC Map
Modify an Existing EFM Group

To add a link to the EFM group at the NetVanta 800, complete the following:
1. From the Enable prompt, type configure terminal, and press Enter to access the Global
2. From the Global Configuration prompt, access the DS1 port’s configuration prompt by
typing no shutdown, and press ENTER.
3. From the SHDSL Interface Configuration prompt, enable the down DS1 ports by typing
no shutdown, and press ENTER.
4. Repeat steps 2 to 3 for the remaining DS1 ports to be added to the EFM group.
7. Add the DS1 port to the bonding group by typing link 0/<port>, and press ENTER.
8. Repeat step 7 to add all desired ports to the EFM bonding group.
Remove an Existing Link

To remove a link from the EFM group at the NetVanta 800, complete the following:
2. From the Global Configuration prompt, access the DS1 port’s configuration prompt by
typing interface t1 1/0/<port>, and press ENTER.
3. From the T1 Interface Configuration prompt, shut the DS1 port down by typing
4. Repeat steps 2 to 3 for the remaining DS1 ports to be removed from the EFM group.
7. Remove the DS1 port from the bonding group by typing no link 0/<port>, and press
ENTER.
8. Repeat step 7 to remove all desired ports from the EFM bonding group.
65K510DEP08-1A 6-23

• Policer example
Policer Definition
INGRESS
Dropped
CBS
EBS
EIR
CIR
6-24 65K510DEP08-1A
Section 6, EoTDM Provisioning - Provision Policers in the NetVanta 800
and is unmarked.
NOTE
procedure:
per evc <EvcName>
the policer.
prompt.
65K510DEP08-1A 6-25
Policer Example
Mode : Custom
Qualified EVC-maps:
-----------------------------------------------------------------------
------------------------------------------------------------------------
Ingress Red Bytes 0
MyNV800#
6-26 65K510DEP08-1A
Section 6, EoTDM Provisioning - Provision MAC Address Limiting and Aging

it does not allow any additional MAC addresses to pass toward the network. The MAC
Address limit can be set to any value from 1 to 100. MAC Address Limiting can also be
disabled. By default, the NetVanta limits the customer to 100 learned MAC Addresses.
2. From the Global Configuration prompt, access the Ethernet Configuration prompt or the
Gigabit‐Ethernet Configuration prompt by completing one of the following:
• Type interface ethernet 1/0/port, and press ENTER to access the Ethernet
Configuration prompt, where port is any value from 1 to 4
• Type interface gigabit-ethernet 1/0/1, and press ENTER to access the Gigabit‐
Ethernet Configuration prompt
NOTE

65K510DEP08-1A 6-27

The NetVanta 800 declares alarms for all unused interfaces (DS3, EFM, Ethernet, and Power
Feed). To clear these alarms once the 800 is turned up, the appropriate interfaces must be shut
down.
This section details the following information
• Disable the DS3 interfaces
• Disable the Ethernet interfaces
• Disable the power feed alarms
Disable the DS1 Interfaces

For each unused DS1 port in the EFM Bonding Group, complete the following:
NOTE
This must be done to clear the DS1 loss of signal and EFM near end sync
alarms.
2. From the Global Configuration prompt, access the unused DS3 portʹs configuration
prompt by typing interface t3 1/0/<port>, and press ENTER.
3. From the T3 Interface Configuration prompt, shut the DS3 port down by typing
4. Repeat steps 2 to 3 for the remaining unused DS3 ports.
7. Remove the DS3 port from the bonding group by typing no link <slot/port>, and
press ENTER. For NetVanta products, the slot is always zero.
8. Repeat step 7 to remove all unused ports from the EFM bonding group.
Once all unused DS3 interfaces have been disabled, all DS3 and EFM bonding group alarms
should be cleared in the alarm log, and the EFM LED should be lit solid green, if there are no
other issues. Also, the partial EFM group alarm should clear.
6-28 65K510DEP08-1A
Section 6, EoTDM Provisioning - Disable Unused NetVanta 800 Interfaces
Disable Ethernet Interfaces

For each Ethernet port that is not in use for customer services, complete the following:
NOTE
This must be done to clear the Ethernet link down alarms.
2. From the Global Configuration prompt, access the unused Ethernet Port Configuration
prompt by typing interface ethernet 1/0/<port>, and press ENTER.
3. Disable the Ethernet port down by typing shutdown, and press ENTER.
The Ethernet link down alarm should now be cleared for this port in the alarm log, and
the portʹs LED should be off.
4. Repeat steps 2 and 3 for the remaining unused Ethernet ports.
Once all unused Ethernet ports have been disabled, all Ethernet alarms should be cleared
in the alarm log.

To disable the Gigabit‐Ethernet port, complete the following:
NOTE
the alarms.
being present.
3. Disable the Gigabit‐Ethernet port by typing shutdown, and press ENTER.
LED should be off.
65K510DEP08-1A 6-29
Disable Power Feed Alarms

To disable the power feed alarms, complete the following:
NOTE
A power feed input cannot be disabled, but if both interfaces are not being
sourced with ±48 VDC or ±24 VDC powering, there is a power fail alarm
active for the unused input.
2. From the Global Configuration prompt, access the system alarm prompt by typing
system-alarm, and press ENTER.
3. If power feed A is unused, disable the power feed A alarm by typing no alarm enable
power-fail dc a, and press ENTER.
4. If power feed B is unused, disable the power feed B alarm by typing no alarm enable
power-fail dc b, and press ENTER.
The power A or B fail alarm should be cleared in the alarm log.
Once all unused interfaces are disabled, the alarms for these interfaces should now be cleared.
If all in‐use interfaces (DS3, Ethernet, Gigabit‐Ethernet, and power) are in non‐alarmed states,
then the Alarm LED on the NetVanta 800 should now be lit solid green.
Clear the Alarm Log

To clear the Alarm Log, complete the following:

6-30 65K510DEP08-1A
Section 7
EoF Provisioning

This section details the steps needed to provision an EoF application using the Total Access
5000 8‐Port Gigabit Ethernet(GE 8‐Port) Line Module and the NetVanta 8044 Fiber Network
Termination Equipment.
In this Section
Topic See Page
EoF Overview 7‐2
Provision the GE 8‐Port Line Module 7‐4
Configure Subtended Host Information 7‐5
Create an EVC 7‐9
Provision Policers in the NetVanta 8044 7‐14
65K510DEP08-1A 7-1
EoF Overview
The EoF application provides the option to deliver Gigabit service speeds to customers over
optical facilities. Initial network termination units will support point to point deployment or
delivery from any Ethernet facility.
Figure 7‐1 displays an overview of the EoF deployment.
3 NetVanta 8044 Entities/Commands 4 NetVanta 8044 Entities/Commands

1 Total Access 5000 “Cross Connect”
EVC EVC-2010 EVC EVC-2020
• End Point 1→ PORT, NET 1
GigE Port #2 GigE Port #8
• End Point 2→ GigE Port
S-TAG 2010 S-TAG 2020
• S-tag = 2010
• End Point 2→ GigE Port UNI ETH 1 UNI ETH 3
Total Access 5000

Octal GigE Fiber Available EVC’s and
GigE #1 GigE #1 Management VLAN
Pushed Down by
GigE #2 GigE #2 Total Access 5000
GigE #1
GigE #3 GigE #3 5 GigE #2

EP1 EP2 VLAN
3 2010 2010
GigE #4 GigE #4
1 GigE #3-7
NET 1
2
GigE #5 GigE #5 4 2020
6 GigE #8
VLAN
EVC 2020
2020
EP1 EP2 GigE #6 GigE #6
GigE #7 GigE #7
GigE VLAN
NetVanta 8044
2010 +2020 GigE #8 GigE #8
Management
VLAN 2048
Metro
Ethernet
Network EoF
System Diagram
Figure 7-1. EoF Diagram
7-2 65K510DEP08-1A
Section 7, EoF Provisioning - Provisioning Summary
the NetVanta 8044, complete the following procedure:
1. Provision the GE 8‐Port Line Module.
For more information, refer to “Provision the GE 8‐Port Line Module” on page 7‐4.
2. Configure the subtended host information.
For more information, refer to “Configure Subtended Host Information” on page 7‐5.
3. Create an Ethernet Virtual Circuit (EVC) at the Total Access 5000 that connects the
Gigabit Ethernet port of the default ethernet interface.
• The GigE SM knows where to send the tagged traffic coming in from the default
ethernet interface
• The GigE SM pushes the available tags to each GE 8‐Port LM and to each NetVanta
8044 for the local NetVanta 8044 provisioning
The EVC is a connection between two physical ports.
7. Provision policers in the NetVanta 8044.
For more information, refer to “Provision Policers in the NetVanta 8044” on page 7‐14.
page 7‐17.
65K510DEP08-1A 7-3
Provision the GE 8-Port Line Module

prior releases.
Table 7-2. GE 8-Port Line Module Administration States
no shutdown In Service In the no shutdown state, traffic

passes and alarms are generated.
shutdown maintenance Out of Service, Main‐ In the shutdown maintenance

tenance state, traffic passes but no alarms are
generated.
shutdown Out of Service, Unas‐ In the shutdown state, no traffic

signed passes and no alarms are generated.
Out of Service, Maintenance
Unassigned
2. From the Global Configuration prompt, type interface gigabit-ethernet
<shelf/slot/port>, and press ENTER.
3. Provision the port administration state by performing one of the following commands:
nance
7-4 65K510DEP08-1A
Section 7, EoF Provisioning - Configure Subtended Host Information
Configure Subtended Host Information

To configure the subtended host information, complete the following:
3. From the Gigabit‐Ethernet Interface Configuration prompt, type subtended-host ip
address A.B.C.D E.F.G.H, and press ENTER.
default-gateway A.B.C.D, and press ENTER.
file-server default host A.B.C.D, and press ENTER.
6. From the Gigabit‐Ethernet Interface Configuration prompt, type subtended-host
mode, and press ENTER.
7. From the Gigabit‐Ethernet Interface Configuration prompt, type subtended-host s-
tag <1-4094>, and press ENTER.
s-tag-priority, and press ENTER.
snmp-server chassis-id, and press ENTER.
snmp-server community read-only, and press ENTER.
snmp-server community read-write, and press ENTER.
65K510DEP08-1A 7-5

EVC Definition
Total Access 5000. The EVC cross‐connects two or more endpoints and provides the
mechanism by which an S‐tag path is created in the system. The S‐tag corresponds to the
VLAN ID.
the network ports on the GigE SM and is S‐tag switched to the appropriate slot. The GE 8‐Port
LM then decides how to send that traffic to the customer. Upstream traffic is switched to the
network in a similar manner.
NOTE
management VLAN, create an EVC for the GigE SM to pass the NetVanta
8044 management traffic. When creating a cross connect, set up the cross
connect with an S‐tag equal to the NetVanta 8044 management VLAN,
pointing to the appropriate appropriate GigE 8‐Port LM port.

S-tag Function
0, 1, 4095 Reserved
7-6 65K510DEP08-1A
Section 7, EoF Provisioning - Create an EVC Cross Connect
Provisioning Steps
4. From the EVC Interface Configuration prompt, type connect men-port default
ethernet interface 1/A/1, and press ENTER to connect the active SM Net 1 interface
to the EVC.
NOTE

ethernet <shelf/slot/group>, and press ENTER to connect the GE 8‐Port to the EVC.
enable the EVC.
Enable prompt.
ELAN Definition
An Emulated Local Area Network (ELAN) is a single shelf application that supports single
tagged MEPs for Ethernet OAM. Double tagged MEPs for Ethernet OAM when doing ELAN
are not supported. An ELAN EVC can be provisioned with endpoints accessed from any EoF
access module. Mixed access ELAN EVCs are also possible.
Provisioning Steps
To provision an ELAN, complete the following:
2. From the Global Configuration prompt, type evc WORD, and press ENTER.
ethernet <shelf/slot/port>, and press ENTER.
Use this command to configure which GigE 8‐Port LM port the selected EVC is applied
to.
4. From the EVC Interface Configuration prompt, type mac-switched, and press ENTER to
enable MAC Switching.
Enable prompt.
65K510DEP08-1A 7-7

Management VLAN.
CRAFT Port Login

To establish CLI communication with the product, complete the following procedure:
• Any baud rate
• 8 data bits
• No parity
• 1 stop bit
• No flow control
NOTE
Remote Access Login

To remotely access the NetVanta 8044, open a telnet in the management VLAN that was set up
in the subtended host configuration.
7-8 65K510DEP08-1A
Section 7, EoF Provisioning - Create an EVC
Create an EVC
• EVC guidelines
• EVC example
EVC Definition
frames
At a minimum, two items must be set up for the EVC: the MEN interface it will use and the S‐
tag it will use.
NOTE
EVC Guidelines
– MEN port
– S‐tag
• If the system is managed through a VLAN on a designated Ethernet port, the S‐tag value
for the EVC cannot equal the management VLAN ID
65K510DEP08-1A 7-9
Provisioning Steps
To create an EVC, complete the following procedure:
EVC.
the Ethernet frame.
Configure the EVC

port and S‐tag, complete the following procedure:
1. From the EVC Configuration prompt, type connect men-port gigabit-ethernet 1/
0/1, and press ENTER to set the MEN‐port as the Gigabit Ethernet port as the uplink of the
NetVanta 8044.
This attribute is the interface connected to the MEN. The possible options consist of all of
the Ethernet port(s) available on the NetVanta 8044.
press ENTER.
NOTE
5000 for this EVC or EoF circuit.
and press ENTER.
press ENTER.
7. To save the changes in non‐volatile memory, type copy running-config startup-
config, and press ENTER.
7-10 65K510DEP08-1A
Section 7, EoF Provisioning - Create an EVC
NOTE
If creating an EVC with the same S‐tag as the management traffic, the
NetVanta 8044 will report a conflict.
EVC Example
EVC evc2010
S-TAG : 1200
MyNV8044#
65K510DEP08-1A 7-11
Create an EVC Map

• Map example
Map Definition
called a EVC‐map. Each EVC‐map is typically associated with a single customer and specifies
parameters including the customer VLAN ID and Class of Service (CoS) behavior of the traffic
from the customer. Use a map to classify traffic for use by an EVC for forwarding and for use
by a policer for rate limiting.
Map Guidelines
– UNI port
– CE‐VLAN‐ID
• If the system is managed through a VLAN on a designated Ethernet port, the
management VID value cannot equal the CE‐VLAN‐ID value of the map
to the EVC must have the same value of the CE‐VLAN‐ID attribute
7-12 65K510DEP08-1A
Section 7, EoF Provisioning - Create an EVC Map
Provisioning Steps
To create the map, complete the following procedure:
Configure the Map

binds the UNI traffic to the EVC. To configure the map, complete the following procedure:
1. From the EVC‐Map Interface Configuration prompt, set the UNI by typing connect uni
gigabit-ethernet followed by the ethernet port number in 1/0/port format, and
press ENTER.
NOTE
For the NetVanta, the shelf is always 1 and the slot is always zero.
press ENTER.
4. From the EVC‐Map Configuration prompt, type end, and press ENTER to return to the
Enable prompt.
5. To save the changes to non‐volatile memory, type copy running-config startup-
config, and press ENTER.
ENTER.
This command also displays the EVC and UNI that the map is attached to.
Once this process is completed, data can be run through the system.
Map Example
MyNV8044show evc-map map100
EVC-map map100
EVC-map Status : Running
Connected EVC : evc1100 (1200)
65K510DEP08-1A 7-13
Policer : evc1100
Connected UNI : Gigabit-Ethernet 1/0/6
Match CE-VLAN-ID : 100

• Policer example
Policer Definition
INGRESS
Dropped
CBS
EBS
EIR
CIR
7-14 65K510DEP08-1A
Section 7, EoF Provisioning - Provision Policers in the NetVanta 8044
and is unmarked.
NOTE
procedure:
per evc <EvcName>
the policer.
prompt.
65K510DEP08-1A 7-15
Policer Example
Mode : Custom
Qualified EVC-maps:
-----------------------------------------------------------------------
------------------------------------------------------------------------
Ingress Red Bytes 0
MyNV8044#
7-16 65K510DEP08-1A
Section 7, EoF Provisioning - Provision MAC Address Limiting and Aging

it does not allow any additional MAC addresses to pass toward the network. MAC Address
Limiting can also be disabled. By default, NetVanta has MAC Address Limiting disabled.
2. From the Global Configuration prompt, access the Gigabit‐Ethernet Configuration
prompt by typing interface gigabit-ethernet 1/0/1, and press ENTER to access the
Gigabit‐Ethernet Configuration prompt.
NOTE

65K510DEP08-1A 7-17

The NetVanta 8044 declares alarms for all unused Gigabit‐Ethernet interfaces. To clear these
alarms once the 8044 is turned up, the appropriate interfaces must be shut down.
This subsection details the following information

To disable the Gigabit‐Ethernet port, complete the following procedure:
NOTE
the alarms.
being present.
3. Disable the Gigabit‐Ethernet port down by typing shutdown, and press ENTER.
LED should be off.
Clear the Alarm Log

To clear the Alarm Log, complete the following procedure:

7-18 65K510DEP08-1A
Appendix A
Link Aggregation Guide
Scope of this Appendix

This appendix details the steps needed to provision/remove link aggregation. Net 1 and Net 2
of the GigE SM can be combined to provide a 2 Gbps connection to upstream network
equipment.
NOTE
• A link aggregation group cannot be connected in the downstream direction
to any subtended nodes.
• Ensure all front panel ports on the Active and Standby switch modules are
physically connected to the upstream networking equipment.
In this Appendix
This appendix contains the following topics:
Table A-1. Appendix A Topics
Topic See Page
Link Aggregation Provisioning A‐2
Remove Link Aggregation Provisioning A‐6
65K510DEP08-1A A-1
Link Aggregation Provisioning

To provision for link aggregation, complete the following procedure:
NOTICE
To add cross connects to the aggregation bridge, reprovisioning is required.
1. Disable LACP.
LACP messages must be temporarily disabled while setting up the link aggregation
group. For more information, refer to “Disable LACP” on page A‐2.
2. If needed, enable additional Gigabit‐Ethernet interfaces.
For more information, refer to “Enable Network Interfaces” on page A‐3.
3. Create a Link Aggregation group and add Gigabit‐Ethernet physical interfaces.
For more information, refer to “Create a Link Aggregation Group” on page A‐3.
4. Enable LACP.
For more information, refer to “Enable LACP” on page A‐3.
5. Configure the default network interface to the newly created link aggregation group.
For more information, refer to “Configure Default Network Interface” on page A‐4.
6. Create an EVC and link it to the link aggregation group.
For more information, refer to “Configure EVCs” on page A‐4.
7. Redirect any created EVCs to a link aggregation group.
For more information, refer to “Redirect EVCs” on page A‐5.
Disable LACP
To disable LACP for all active gigabit‐ethernet ports, complete the following procedure:
2. From the Gigabit Ethernet Interface Configuration prompt, type interface gigabit-
ethernet 1/A/1, and press ENTER to access the Gigabit Ethernet Interface Configuration
prompt.
3. From the Gigabit Ethernet Interface Configuration prompt, type no lacp mode, and
press ENTER to disable LACP for the gigabit‐ethernet interface.
4. Repeat steps 2 to 3 to disable LACP for all active gigabit‐ethernet interfaces
5. From the Gigabit Ethernet Interface Configuration prompt, type end, and press ENTER to
A-2 65K510DEP08-1A
Appendix A, Link Aggregation Guide - Link Aggregation Provisioning
Enable Network Interfaces

To enable any SM Gigabit‐Ethernet ports:
1. From the Enable prompt, type configure terminal and press ENTER to access the Glo‐
<shelf/slot/port>, and press ENTER to access the Gigabit Ethernet Interface
3. From the Gigabit Ethernet Interface Configuration prompt, type no shutdown, and
press ENTER to set the interface to In Service.
4. Repeat steps 2 to 3 to enable additional gigabit‐ethernet interfaces
Create a Link Aggregation Group

To create a link aggregation group and assign physical interfaces, complete the following
procedure:
2. From the Global Configuration prompt, type interface lag-group 1/A/1, and press
ENTER to create the link aggregation group and access the lag group configuration prompt.
3. From the Link Aggregation Group Interface Configuration prompt, type active-
links-minimum <1-n>, and press ENTER to set the minimum number of active links for
the group.
4. From the Link Aggregation Group Interface Configuration prompt, type link
gigabit-ethernet <shelf/slot/port>, and press ENTER to add a gigabit‐ethernet
interface to the group.
5. Repeat step 4 to add all needed interfaces to the group.
6. From the Link Aggregation Group Interface Configuration prompt, type no shutdown
and press ENTER to enable the link aggregation group.
7. From the Link Aggregation Group Interface Configuration prompt, type end and press
ENTER to return to the Enable prompt.
8. From the Enable prompt, type show lag-group 1, and press ENTER to see the link
aggregation groups in the system.
Enable LACP
To enable LACP for all active gigabit‐ethernet ports, complete the following procedure:
2. From the Global Configuration prompt, type interface gigabit-ethernet <1/
slot/port>, and press ENTER to access the Gigabit Ethernet Interface Configuration
prompt.
65K510DEP08-1A A-3
3. From the Gigabit Ethernet Interface Configuration prompt, type lacp mode active or

lacp mode passive, and press ENTER to configure the interface for the desired LACP
mode.
4. Repeat steps 2 to 3 to enable LACP for all active gigabit‐ethernet interfaces in the link
aggregation group.
Configure Default Network Interface

To configure the default network interface, complete the following procedure:
2. From the Global Configuration prompt, type ethernet default interface lag-
group 1/A/1, and press ENTER to set the default network interface to the newly created
link aggregation group.
3. From the Global Configuration prompt, type end and press ENTER to return to the Enable
prompt.
Configure EVCs
Once a link aggregation group is created, it can be included in the Total Access 5000 cross
connects. To create an EVC and connect it to a link aggregation group, complete the following
procedure:
2. From the Global Configuration prompt, type evc WORD, and press ENTER to create an EVC
with name evc_name.
4. From the EVC Interface Configuration prompt, type connect men-port lag-group
<1/slot/port>, and press ENTER to connect the desired link aggregation group to the
EVC.
NOTE
This command entry applies to the active GigE SM, independent of which
GigE SM is actually specified, in an Active/Standby configuration.

NOTE
The EFM bonding group shelf/slot/group designation can be used in lieu of
the group name.
A-4 65K510DEP08-1A
Appendix A, Link Aggregation Guide - Link Aggregation Provisioning
6. From the EVC Interface Configuration prompt, type no shutdown, and press ENTER to
enable the EVC.
7. From the EVC Interface Configuration prompt, type end, and press ENTER to return to the
Enable prompt.
Redirect EVCs
When a link aggregation is created and enabled, any service EVCs previously connected to the
Gigabit‐Ethernet port must be redirected to the newly created link aggregation group.
NOTICE
If not redirected to the Gigabit‐Ethernet port, the EVCs will be left hanging.
To redirect the EVCs to a link aggregation group, complete the following procedure:
1. From the root prompt, type show evc, and press ENTER to display all EVCs in the Total
Access 5000.
For any EVCs that are connected to the Gigabit‐Ethernet port, perform the following
steps to disconnect them from the GE port and connect them to the LAG group.
3. From the Global Configuration prompt, type evc <shelf/slot/index>, and press
ENTER to access the EVC Interface Configuration prompt.
4. From the EVC Interface Configuration prompt, type no connect men-port
gigabit-ethernet 1/a/1, and press ENTER to disconnect the EVC from the GE port.
5. From the EVC Interface Configuration prompt, type connect men-port lag-group
1/C/1, and press ENTER to connect the EVC to the newly created LAG group.
7. Repeat steps 3‐6 as necessary.
65K510DEP08-1A A-5
Remove Link Aggregation Provisioning

To remove the link aggregation provisioning, complete the following procedure:
NOTICE
To remove cross connects from the aggregation bridge, reprovisioning is
required.
1. Disable LACP.
For more information, refer to “Disable LACP” on page A‐2.
2. Provision the default network interface to none.
For more information, refer to “Provision Default Network Interface to None” on
page A‐6.
3. Redirect any created EVCs to the Network Gigabit‐Ethernet port.
For more information, refer to “Redirect EVCs” on page A‐6.
4. Remove the Link Aggregation group.
For more information, refer to “Remove a Link Aggregation Group” on page A‐7.
5. Provision the default network interface to the SM A, Net 1.
For more information, refer to ʺ“Provision Default Network Interface to SM A, Net 1” on
page A‐7.
6. Disable unused network interfaces.
For more information, refer to “Disable Network Interfaces” on page A‐8.
7. Enable LACP.
For more information, refer to “Enable LACP” on page A‐3.
Provision Default Network Interface to None

2. From the Global Configuration prompt, type no ethernet default interface, and
press ENTER to set the default network interface to None.
prompt.
Redirect EVCs
When a link aggregation group is disabled or removed, any service EVCs previously
connected to the link aggregation group must be redirected to the network Gigabit‐Ethernet
port.
NOTICE
If not redirected to the link aggregation group, the EVCs will be left hanging.
A-6 65K510DEP08-1A
Appendix A, Link Aggregation Guide - Remove Link Aggregation Provisioning
To redirect the EVCs to a Gigabit‐Ethernet port, complete the following procedure:
1. From the root prompt, type show evc, and press ENTER to display all EVCs in the Total
Access 5000.
For any EVCs that are connected to the Gigabit‐Ethernet port, perform the following
steps to disconnect them from the GE port and connect them to the LAG group.
3. From the Global Configuration prompt, type evc <shelf/slot/index>, and press
ENTER to access the EVC Interface Configuration prompt.
4. From the EVC Interface Configuration prompt, type no connect men-port lag-
group 1/a/1, and press ENTER to disconnect the EVC from the LAG group.
ethernet 1/a/1, and press ENTER to connect the EVC to the newly created LAG group.
7. Repeat steps 3‐6 as necessary.
Remove a Link Aggregation Group

To create a link aggregation group and assign physical interfaces, complete the following
procedure:
2. From the Global Configuration prompt, type no interface lag-group 1/A/1, and
press ENTER to delete the link aggregation group.
3. From the Global Configuration prompt, type end, and press ENTER to return to the Enable
prompt.
Provision Default Network Interface to SM A, Net 1

2. From the Global Configuration prompt, type ethernet default interface
gigabit-ethernet 1/A/1, and press ENTER to set the default network interface to SM
A, Net 1.
prompt.
65K510DEP08-1A A-7
Disable Network Interfaces

To disable any unused SM Gigabit‐Ethernet ports:
<shelf/slot/port>, and press ENTER to access the lag group configuration prompt.
3. From the Gigabit Ethernet Interface Configuration prompt, type shutdown, and press
ENTER to set the interface to Out of Service, Unassigned.
4. Repeat steps 2 to 3 to disable additional gigabit‐ethernet interfaces
A-8 65K510DEP08-1A
Appendix B
SHDSL Rate Reach Information

This appendix displays the rate reach information for single pair and multi‐pair SHDSLs.
In this Appendix
Table B-1. Appendix B Topics
Topic See Page
49‐Self Reach on AWG24 B‐2
Realistic Deployment Reach B‐2
Bonded 49‐self Reach for a Minimum Rate of 10Mbps B‐3
Bonded 49‐self Reach for a Maximum Rate of 10Mbps B‐3
65K510DEP08-1A B-1
49-Self Reach on AWG24

Figure B‐1 displays the e‐SHDSL reach for a 49‐self noise on AWG24.
e-SHDSL Reach: 49-self Noise on AWG24

6000
e-SHDSL 32-TCPAM
5000
4000
Rate (kbps)
e-SHDSL 16-TCPAM
3000 3dB bandwidth:
SHDSL 32-TCPAM-> Data Rate/8
16-TCPAM-> Data Rate/6
2000
1000
0
0 3 6 9 12 15 18 21
Reach (kft of AWG24)
Figure B-1. Single Pair Theoretical 49–self Reach on AWG24
Realistic Deployment Reach

Figure B‐2 displays a single pair realistic deployment reach for AWG24.
SHDSL/e-SHDSL Realistic Deployment Reach

6000
49 disturbers
12 disturbers
5000
SpM limits
4000
Rate (kbps)
3000
2000
1000
0
0 3 6 9 12 15 18 21 24
Figure B-2. Single Pair Realistic Deployment Reach on AWG24
B-2 65K510DEP08-1A
Appendix B, SHDSL Rate Reach Information - Bonded 49-self Reach for a Minimum Rate of 10Mbps
Bonded 49-self Reach for a Minimum Rate of 10Mbps

Figure B‐3 displays a bonded multi‐pair deployment reach on AWG24 (rates >10Mbps).
Bonded 49-self reach for a min. rate of 10Mbps
45 2-pairs
4-pairs
40 6-pairs
8-pairs
35
Rate (Mbps)
30
25
20
15
10
0 3 6 9
Figure B-3. Bonded Multi-pair Deployment Reach on AWG24 (rates >10Mbps)
Bonded 49-self Reach for a Maximum Rate of 10Mbps

Figure B‐4 displays a bonded multi‐pair deployment reach on AWG24 (rates <10Mbps).
Bonded 49-self reach for a max. rate of 10Mbps

10
8
Rate (Mbps)
2-pairs
2 4-pairs
6-pairs
8-pairs
0
0 3 6 9 12 15 18 21
Figure B-4. Bonded Multi-pair Deployment Reach on AWG24 (rates <10Mbps)
65K510DEP08-1A B-3
B-4 65K510DEP08-1A
Appendix C
Ethernet OAM Provisioning

This appendix defines Ethernet OAM and describes Ethernet OAM provisioning for the
NetVanta 800/8000 series NCTE and the Total Access 5000.
In this Appendix
This appendix contains the following:
Table C-1. Appendix C Topics
Topic See Page
Ethernet Operation, Administration, and Management C‐2
Ethernet OAM on the NetVanta 800/8000 Series NCTE C‐4
Ethernet OAM on the MSAP (Total Access 5000) C‐11
65K510DEP08-1A C-1
Ethernet Operation, Administration, and Management

Two types of Ethernet Operation, Administration, and Management (OAM) are supported.
One type is Ethernet Link OAM defined by the IEEE 802.3ah standard. Ethernet Link OAM
operates over a single point‐to‐point Ethernet link. The other type is Ethernet Connectivity
Fault Management (CFM) defined by the IEEE 802.1ag standard. Ethernet CFM is used to
verify connectivity between endpoints across an Ethernet‐based network of any number of
links, and as faults occur, the device causing the failure can be determined through the use of
linktrace and loopback/ping messages.
Ethernet OAM Carrier Ethernet

Figure C‐1 shows a typical Total Access 5000 E‐Line deployment. Ethernet OAM is used in
this application to verify the entire Ethernet path between NetVanta #1 and NetVanta #2. If a
failure occurs at any point in the network, one (or both) NetVanta units will no longer receive
continuity check messages (CCMs) and will be able to raise an alarm. Once an alarm is
received, linktrace can be used to determine which devices can be seen along the path or to
target specific devices along the path. Using the layered capabilities of Ethernet OAM,
Ethernet OAM connections can exist between the two Total Access 5000 units or between the
two CPE routers; however, these would need to operate at different Maintenance Domain
(MD) levels.
Demarcation Demarcation
Customer Customer
Site Site
Total Access 5000 #1 Total Access 5000 #2
NetVanta #1 NetVanta #2
CPE Router CPE Router
Network
Link OAM 802.3ah
End to End OAM or multi-hop OAM 802.1ag/Y.1731
Figure C-1. Ethernet OAM (Carrier Ethernet)
The NetVanta 800/8000 supports creating Maintenance Association End Points (MEP) with the
following configurable attributes:
• Interface ‐ Any interface transporting Ethernet services.
• Direction ‐ Up or Down
–Down MEP ‐ Active side is further away from MAC relay/Switch than its passive
side. A Down MEP transmits CFM messages from the interface it is on out to the
physical link.
–Up MEP ‐ Active side is further away from the interface it is on than its passive side.
An Up MEP transmits CFM messages from the interface is on in towards the MAC
relay of the bridge.
• Component ‐ Provider or Customer
–Provider Component (S‐Component) ‐ A flow that is switched by s‐tag and defined
by an EVC.
C-2 65K510DEP08-1A
Appendix C, Ethernet OAM Provisioning - Ethernet Operation, Administration, and Management
–Customer Component (C‐Component) ‐ A flow that is switched by c‐tag, defined
by an EVC‐map, and classified onto an EVC by the EVC‐map’s matching criteria.
• Primary Vid ‐ None, 1‐4094
• Level ‐ 0‐7
The NetVanta 8000 supports creation of Maintenance Association Intermediate Points (MIP)
with the following configurable attributes:
• Interface ‐ Any interface transporting Ethernet services. The interface must also be
operating as a MEN‐port
• Component ‐ Provider only
• Primary VID ‐ 2‐4094
• Level ‐ 0‐7
Ethernet OAM for Business Service Migration

Figure C‐2 shows a typical Total Access 5000 BSM deployment. Use Ethernet OAM to verify
Ethernet connectivity between the PPP group/Ethernet interface in the Total Access 5000 #1
and the PPP group/Ethernet interface in the Total Access 5000 #2.
The Total Access 5000 supports the following features for Ethernet OAM:
• Network‐facing Down MEPs and MIPs only on tag‐switched EVCs at the GigE SM
interface
• Network‐facing Up MEPs at the PPP group interface (BSM only)
Demarcation Demarcation
Customer Customer
Site Site
Total Access 5000 #2
PPP Group Total Access 5000 #1 PPP Group
CPE Router CPE Router
Network
End to End OAM or multi-hop OAM 802.1ag
Figure C-2. Ethernet OAM (BSM)
65K510DEP08-1A C-3
Ethernet OAM on the NetVanta 800/8000 Series NCTE

To configure Ethernet OAM on the NetVanta 800/8000 Series NCTE, complete the following
procedure:
1. Enable Ethernet OAM on the NetVanta 800/8000 Series NCTE.
2. Create the Ethernet OAM MD.
The MD contains the following attributes:
• Name
• Domain Level
3. Within the newly created MD, create one or more Ethernet OAM Maintenance
Associations (MA).
The MA contains the following attributes:
• Name
• Component
• Component’s Primary VID
• CCM Interval
• Associated Remote MEPs
4. Create Maintenance End Points (MEP) and enable CCMs per MEP.
The MEP contains the following attributes:
• MEPID
• Direction
• Interface
• Priority
• CCM Transmission State
5. On products that support MIPs, edit the Default MD.
The Default MD contains the following attributes:
• Default MIP Creation Rule
• Default MIP Level
• Component
• Component’s Primary VID
• Component’s MIP Creation Rule
• Component’s MIP Level
C-4 65K510DEP08-1A
Appendix C, Ethernet OAM Provisioning - Ethernet OAM on the NetVanta 800/8000 Series NCTE
NetVanta 800/8000 Series NCTE Configuration Procedure

Create the MD, MA, and a MEP on the Netvanta 800/8000 Series NCTE #1 (example at the
end):
2. From the Global Configuration prompt, enable the Ethernet OAM subsystem by typing
ethernet cfm, and press ENTER.
3. From the Global Configuration prompt, create the Ethernet OAM MD by typing
ethernet cfm domain char-string WORD level <0-7>, and press ENTER
Use the name of the MD in place of the WORD field and specify the level of MD after the
level argument.
4. From the MD Configuration, type association char-string WORD to create the MA
(or edit an existing MA).
5. From the MA Configuration prompt, type ccm interval [1-minute|1-second|10-
minutes|10-seconds|100-milliseconds] to set the CCM interval (default is 1
second):
Use 100‐milliseconds, 1‐second, 10‐seconds, 1‐minute, or 10‐minutes for the CCM
interval.
6. The NetVanta supports remote MEP auto‐discovery and auto‐learning within a MA.
Auto‐discovery lets a local MEP discover its peers without committing them to a state
where they can cause RemoteCCM defects/alarms. Other alarms for invalid CCI,
MACstatus, or Xconnect will still be raised. Discovery does not commit any of the
discovered RMEPs to provisioning and if a Discovered entry fails, it will be removed
from the system after aging out. Learning allows the user to immediately learn all peers,
transition them to Static entries, and place their values in provisioning so they will be
persisten upon a restore.
There are seveal items that compose the MEP database and control how it operates.
• MEP Database ‐ Each MA manages its own MEP database. The MEP database
contains all Remote MEPs and also configures how Remote MEPs can be added.
• Connectivity Failure Interval ‐ This value cannot be directly configured by a user but
is based off of the user‐configurable CCM interval. The Connectivity Failure Interval
is 3.5 times the CCM Interval. It is often used as the timeframe during which certain
events are expected to occur within. One example is if a local MEP receives a CCM
from a RMEP and doesn’t receive subsequent CCM from it within this time frame,
then the RMEP’s state is set to ‘Fail’. For a Maintenance Association using a 1‐second
CCM Interval, if a local MEP receives a CCM from a RMEP and does not receive
another within 3.5‐seconds, the RMEP has failed.
• Remote‐MEP ‐ Remote MEPs (RMEP) are defined by their MEPID which must be
unique across the MA. The valid range for a MEPID is 1‐8191. A RMEP can operate
in one of two modes. It can be a ‘Static’ RMEP or a ‘Discovered’ RMEP. The
operation mode of a RMEP is dictated by the MEP database rule of the Maintenance
Association.
–Static ‐ A Static RMEP raises the Remote CCM defect condition if it transitions from
the Ok state to the Fail state. A Static RMEP will also be stored in provisioning after
a write and will be restored following a subsequent reload.
–Discovered ‐ A Discovered RMEP does not raise the Remote CCM defect condition
if it transitions from the Ok state to the Fail state. After Discovered RMEP remains
65K510DEP08-1A C-5
in the Fail state for 100‐minutes it will be removed from the MA’s MEP database. A
Discovered RMEP will not be stored in provisioning and will need to be redis‐
covered after a system reload. A Discovered RMEP is detonated by an asterisk
preceding the MEPID.
• MEP Database Rules ‐ The following are the two supported rules for a MA’s MEP
database:
–auto‐discovery ‐ If a local MEP receives a CCM from a RMEP that has not been
previously configured, it creates a RMEP whose operation mode will be
Discovered.
–auto‐learning ‐ If a local MEP receives a CCM from a RMEP that has not been previ‐
ously configured, it creates a RMEP whose operation mode will be Static.
• MEP Database Actions ‐ The following are actions that can be performed on RMEPs
in the MEP Database:
–Lock ‐ If in the auto‐discovery state, Discovered RMEPs can transition to operate as
Static by being locked.
–Clear ‐ If a Discovered peer fails, it can be manually removed or cleared. If a
Discovered peer has not failed, it can still be cleared but it will be re‐discovered on
the next received CCM from that RMEP.
• MEP Database Rule Transitions ‐ When changing the MA rule from an auto‐
discovery state to an auto‐learning state, all Discovered entries are made Static.
When transitioning from an auto‐discovery state to configured‐only state, all
Discovered entries are removed.
To configure the remote MEP database learning rule, type one of the following
commands:
• Type mep-database configured-only, and press ENTER to set the rule to
configured‐only learning. This is the default
• Type mep-database auto-discovery , and press ENTER to set the rule to auto‐
discovery learning
• Type mep-database auto-discovery auto-learn, and press ENTER to set the
rule to auto‐learning
7. If needed, from the MA Configuration prompt, type remote-mep <1-8191>, and press
ENTER to create a RMEP that operates as a Static entry in the MEP‐database.
This step can be repeated to add more than one remote‐MEP to the association.
8. From the MA Configuration prompt, type component [1|2] vlan [<1-4094>|none]
to associate a VLAN with the maintenance association:
For Component 1 Down and Up MEPs, use the VLAN ID of the EVC with which the MA
is operating on.
For Component 2 Down and Up MEPs, use a customer VLAN ID that is being mapped to
an EVC by an EVC‐map.
If none is specified, untagged CFM messages will be sent.
A Component needs to be created in the Maintenance Association to define the realm of
the MA and the VLAN of the MA. A MA can operate either on c‐tag or s‐tag.
• A Component ID of 1 indicates the Maintenance Association operates on the s‐tag
• A Component ID of 2 indicates the Maintenance Association operates on the c‐tag
A MD and MA can be terminated on an NCTE in various ways depending on the
architecture of the CFM deployment across the network.
C-6 65K510DEP08-1A
Single‐tag CFM service for s‐tag 100:
• Component 1 VLAN 100 Down MEP on the MEN‐port
• Component 1 VLAN 100 Up MEP on the UNI defined by an EVC‐map connected to
the EVC with s‐tag 100
Single‐tag CFM service for c‐tag 20 towards customer:
• Component 2 VLAN 20 Down MEP on the UNI‐port for customer CFM service
operability.
Double‐tag CFM service for s‐tag 100, c‐tag 20 destined for a Provider network:
• Component 2 VLAN 20 Up MEP on the UNI‐port defined by an EVC‐map connected
to the EVC with s‐tag 100
9. Type exit, and press ENTER to return to the MD prompt.
11. A MIP can be created on a specific VID and specific MD level by entering the Default
MD. The MIP will be created on all MEN‐ports with that VID so long that a Down MEP
on the same VID doesn’t exist at a equal or higher level.
12. From the Global Configuration prompt, enter the Ethernet CFM Default MD by typing
ethernet cfm default-domain, and press ENTER.
13. From the Default‐MD Component prompt, type component 1 vlan <2-4094>, and
press ENTER to configure the MIP creation settings for the specified Provider VLAN.
A prerequisite for editing a Default‐MD Component is that the VLAN must already be
defined by a EVC using the same s‐tag and in the Running state. If no such EVC exists,
then the MIP rules cannot be accessed for that Default‐MD Component VID.
14. From the Default‐MD Component prompt, type level <0-7>, and press ENTER. The MIP
creation will be attempted at the specified MD level for this Provider VID.
15. From the Default‐MD Component prompt, type mip-allowed any, and press ENTER to
allow MIPs to be created on this Provider VID.
65K510DEP08-1A C-7
Create a MEP and Enable CCMs per MEP

The NetVanta NCTE allows MEPs to be created on the following interfaces: EFM‐group,
Ethernet, and Gigabit‐Ethernet. To create a MEP, type the appropriate command at the Global
Configuration prompt:
• interface efm-group 1/0/1
• interface ethernet 1/0/x (for ethernet port x)
NOTE
More than one EFM‐group can exist, but not against the Total Access 5000.
• interface gigabit-ethernet 1/0/1
NOTE
Gigabit‐ports are not present on all NetVanta 800‐series products.
To create a MEP and enable the CCMs per the MEP, complete the following procedure:
NOTE
EFM‐group MEPs should only be created with Component 1 MAs. Ethernet
and Gigabit‐Ethernet MEPs should only be created with Component 2 MAs.
1. From the Interface prompt, a MEP can be created or edited if previously created by typ‐
ing ethernet cfm mep <MEPID> <MD_name> <MA_name> [up|down], and press
ENTER.
Use the MEPID of the local MEP, the MD Name, and the MA Name it is to operate in.
2. Enable continuity check messages (CCMs) for the MEP by typing ccm-enabled, and
press ENTER.
3. Enable the MEP by typing no shutdown, and press ENTER.
NCTE Ethernet OAM Example Using Component 1

In the following example, the user is creating a level 5 MD between two endpoints (NCTE A
and NCTE B) and a single MA operating on the Provider VID 1010. NCTE A has a MEP with
a MEPID of 2000 and NCTE B has a MEP with a MEPID of 2001. The CCM interval is not
explicitly configured so the default CCM interval of 1‐second will be used.
NCTE A Configuration
ethernet cfm
ethernet cfm domain char-string MD_5 level 5
association char-string MA_1010
remote-mep 2001
C-8 65K510DEP08-1A
component 1 vlan 1010

exit
exit
exit
interface efm-group 1
ethernet cfm mep 2000 MD_5 MA_1010 down
ccm-enabled
no shutdown
exit
NCTE B Configuration
ethernet cfm
remote-mep 2000
exit
exit
exit
interface efm-group 1
ethernet cfm mep 2001 MD_5 MA_1010 down
ccm-enabled
no shutdown
exit
NCTE Ethernet OAM Example Using Component 2

In the following example, the user is creating a level 6 MD in the customer network which is
encapsulated by an s‐tag and is transparent across the provider network. Up MEPs will
transmit/receive CFM messages with the c‐tag defined by Component 2 of the Maintenance
Association. Due to the rules of the EVC and EVC‐map, these messages will have the s‐tag
stacked before egressing the MEN‐port. For the Up MEPs to become active, the EVC‐map
matching on CE‐VLAN‐ID 200 must be in the Running state. The MA has two endpoints
(NCTE A and NCTE B). The user is creating a single MA with VLAN 200. NCTE A has a MEP
with a MEPID of 600 and NCTE B has a MEP with a MEPID of 601. The CCM interval is not
explicitly configured so the default CCM interval of 1‐second will be used.
NCTE A Configuration
evc evc1010
s-tag 1010
connect men-port efm-group 1/0/1
no shutdown
65K510DEP08-1A C-9
evc-map map200
match ce-vlan-id 200
connect uni ethernet 1/0/1
connect evc evc1010
no shutdown
ethernet cfm
remote-mep 601
interface ethernet 1/0/1
ethernet cfm mep 600 MD_6 MA_200 up
ccm-enabled
no shutdown
NCTE B Configuration
evc evc1010
s-tag 1010
connect men-port efm-group 1/0/1
no shutdown
evc-map map200
match ce-vlan-id 200
connect uni ethernet 1/0/1
connect evc evc1010
no shutdown
ethernet cfm
remote-mep 600
interface ethernet 1/0/1
ethernet cfm mep 601 MD_6 MA_200 up
ccm-enabled
no shutdown
C-10 65K510DEP08-1A
Appendix C, Ethernet OAM Provisioning - Ethernet OAM on the MSAP (Total Access 5000)
Ethernet OAM on the MSAP (Total Access 5000)

To configure Ethernet OAM on the Total Access 5000, complete the following:
1. Enable Ethernet OAM on the Total Access 5000.
2. Create the MD and MA.
The MD contains the following attributes:
• Domain name
• Domain level
• Association name
• Component VLAN number
3. Create a MIP on a VLAN.
4. Create a MEP on the Total Access 5000.
Enable Ethernet OAM on the Total Access 5000

To enable Ethernet OAM on the Total Access 5000, complete the following:
2. From the Global Configuration prompt, type ethernet cfm, and press ENTER to enable
CFM subsystem on the Total Access 5000.
Create the Maintenance Domain and Association

To create an MD and association, and to associate a VLAN with the association, complete the
following:
2. From the Global Configuration prompt, type ethernet cfm domain char-string
WORD level <0-7> to create the ethernet MD at level domain_level.
3. From the Ethernet OAM Domain Configuration prompt, type association char-
string WORD to create the maintenance association.
4. From the Ethernet OAM Association Configuration prompt, type component 1 vlan
<1-4094> to add (associate) the VLAN to the MA/MD.
5. Type exit, then press ENTER, to exit the Association Configuration prompt.
6. Type exit, then press ENTER, to exit the Domain prompt.
65K510DEP08-1A C-11
Create a MIP on a VLAN

MIPs are created in the default domain per the MIP rules set per VLAN. For a VLAN to be
added to the default domain, the EVC for the VLAN should be created before the following
steps are performed.
Once the VLAN has been added to the default domain, create the MIP by performing the
following steps:
1. From the Global Configuration prompt, type ethernet cfm default-domain to enter
the Default Domain Configuration prompt.
2. From the Ethernet OAM Default Domain Configuration prompt, type component 1
vlan <1-4094> to enter the Component Configuration prompt.
3. From the Ethernet OAM Default Domain Component Configuration prompt, type level
<0-7> to set the default level of the component.
4. Type mip-allowed any to allow MIPs to be created on the VLAN.
NOTE
The MIP is created at the lowest level between the level at which the domain
was created and the default domain level. The example commands above
created the domain at level 6, and the default domain was set to level 4, thus,
the MIP is created at level 4.
MIP Creation Example

The following example displays an additional MIP created on VLAN 200.
Switch(config)#ethernet cfm default-domain
Switch(config-ecfm-def-domain)#component 1 vlan 200
Switch(config-ecfm-def-comp)#level 4
Switch(config-ecfm-def-comp)#mip-allowed any
Create a Gigabit-Ethernet MEP on the Total Access 5000

To create a network‐facing MEP at the Gigabit‐Ethernet network interface of the Total Access
5000, complete the following (assumes the MD and MA has been created):
1. From the Global Configuration prompt, type interface gigabit 1/<active_SM>/1
to enter the Gigabit‐Ethernet Interface configuration.
2. From the Gigabit Ethernet Interface Configuration prompt, type ethernet cfm mep
<mepid> <domain_name> <domain_association> down to create the MEP.
3. From the Ethernet OAM MEP Configuration prompt, type no mep-shutdown to enable
the MEP.
4. From the Ethernet OAM MEP Configuration prompt, type exit, and press ENTER to
return to the Gigabit Ethernet Interface Configuration prompt.
5. From the Gigabit Ethernet Interface Configuration prompt, type exit, and press ENTER to
return to the Global Configuration prompt.
C-12 65K510DEP08-1A
Appendix C, Ethernet OAM Provisioning - Ethernet OAM on the MSAP (Total Access 5000)
MEP Creation Example

The following example displays the creation of an MEP.
Switch(config-giga-eth b/1)#ethernet cfm mep 1 MD6 MA6_100 down
Switch(config-ecfm-mep1)#no mep-shutdown
Switch(config-ecfm-mep1)#exit
Switch(config-giga-eth b/1-mep)#
Switch(config-giga-eth b/1-mep)#exit
Switch(config-giga-eth B/1)#exit
65K510DEP08-1A C-13
C-14 65K510DEP08-1A
Appendix D
TWAMP Provisioning

This appendix gives an overview of TWAMP, describes the steps required to configure
TWAMP (Two‐way Active Measurement Protocol) on the NCTE (NetVanta), and describes the
steps to view the current TWAMP status.
In this Appendix
This appendix contains the following:
Table D-1. Appendix D Topics
Topic See Page
TWAMP Overview D‐2
TWAMP Provisioning D‐2
TWAMP Configuration on the NCTE D‐4
Current TWAMP Status D‐5
65K510DEP08-1A D-1
TWAMP Overview
TWAMP is a mechanism by which IP performance metrics and packet loss can be obtained
across the Metro Ethernet. These types of metrics verify that a certain service level is being met
across the network that was agreed upon between the customer and the service provider.
TWAMP allows a unit in the Metro Ethernet to set up and send IP packets to a destination unit
in the Metro Ethernet. The destination unit receives the packet and transmits it right back to
the sending unit. The packet contains timestamps inserted by the sending and destination
units that indicate sending time, time received and re‐transmitted at the destination unit, and
the time received back at the sending unit. With this information, the sending unit can
calculate the following statistics: packet loss, two‐way latency, and directional/one‐way jitter.
NOTE
The NCTE only supports reflector mode.
TWAMP Provisioning
In TWAMP terminology, the source node or sender is called the ʺsession‐senderʺ and the
reflector is simply called the ʺsession‐reflectorʺ. In addition, the source node usually has the
responsibility of initially requesting a TWAMP session to commence. In TWAMP terminology
this is called the ʺControl‐Clientʺ ‐ sometimes just abbreviated to client. The reflector node
also has another role of being the TWAMP ʺserverʺ. The ʺserverʺ is responsible for accepting
the TWAMP requests from the source node.
The TWAMP protocol can be divided up into the 4 logical states. Each phase commences
sequentially in time in a normal TWAMP probe exchange:
• The connection setup phase (run over TCP)
• The test session setup phase (run over TCP)
• The active test session phase (run over UDP)
• The test session end and pm retrieval phase (run over TCP)
NOTE
The active test session phase runs over UDP, whereas the other 3 phases all
run over a single TCP connection.
TWAMP Connection Setup

The host that initiates the tcp connection takes the role of control‐client and session sender.
The host that acknowledges the TCP connection is the session‐reflector.
TWAMP Test Session Setup

The session‐reflector does NOT process incoming test packets for PM metrics and does not
care about the send schedule. Consequently, the number of scheduled slots and number of
packets in the request‐session command must be set to 0.
Sender UDP port is the UDP port used for sender transmission. Receiver UDP port is the UDP
port used for reflector transmission.
D-2 65K510DEP08-1A
Appendix D, TWAMP Provisioning - TWAMP Provisioning
If the sender and receiver addresses are set to 0, then the IP addresses used in the IP packet
that encapsulates the request‐session command shall be used in the test packets.
The timeout in the request‐session command shall be used by the session‐reflector as the
amount of time that the reflector must wait after receiving a stop‐sessions message. The
reflector shall keep reflecting packets until this amount of time passes. After this, the reflector
stops reflecting packets.
The type‐P descriptor was used to set the DSCP or PHB in the message from the sender. The
reflector should use these same values in the reflected packet.
The send schedule for test packets is NOT used in TWAMP. The sender should autonomously
decide the send schedule.
TWAMP Active Test Session

At this point, a switch is made from using TCP to using the UDP protocol. With TWAMP, the
session‐reflector sends out test packets in response to each test packet it receives.
The send schedule is not communicated to the session‐reflector. As such, there is no need for
a standardized computation of packet timing. The sender, though, should have its best
approximation of its real time placed into the departure timestamp field.
The TWAMP session‐reflector timestamps the received packet, copies the packet sequence
number in the corresponding reflected packet field, transmits the reflected packet, and ignores
packets received after the ʺstop‐session command + timeoutʺ.
The TWAMP test packet from the reflector consists of the following parameters:
• Sequence number ‐ is the sequence number of the test packet according to its arrival time
at the session‐reflector. This value should start with zero and increment by one for each
subsequent packet. This is independent from the sequence number of the arriving
packets.
• Timestamp ‐ the session reflectorʹs transmit timestamp. Format is same as used in
OWAMP.
• Error estimate ‐ the time error estimate in the session reflectorʹs transmit timestamp.
Format is the same as used in OWAMP.
• Receive timestamp ‐ the session reflectorʹs receive timestamp. Format is same as used in
OWAMP. The difference between timestamp and receive timestamp is the amount of
time the packet was in transition at the session‐reflector. The error estimate associated
with timestamp also applies here.
• ʺSender Sequence Number ‐ an exact copy of the sequence number from the session
sender test packet.
• Sender Timestamp ‐ an exact copy of the timestamp from the session‐sender test packet
• Sender Error Estimate ‐ an exact copy of the error estimate from the session‐sender test
packet
• Packet padding ‐ an exact copy of the packet padding from the session‐sender test packet
65K510DEP08-1A D-3
TWAMP Test Session End and PM Retrieval

The official end of the active TWAMP test session phase is declared when the sender sends a
ʺstop‐sessionsʺ control message. This is the same message and format as OWAMP with the
following exceptions:
• The next seqno must be set to zero
• The number of skip ranges must be set to 0.
• The message must not contain any session descriptor records or skip ranges.
TWAMP does not use the fetch‐session command used in OWAMP and does not rely upon
any metrics collected at the session‐reflector. All PM statistics are collected at the session‐
sender.
TWAMP Configuration on the NCTE

Configuring TWAMP on the NCTE involves the following steps:
• Optionally changing the maximum number of sessions allowed at the TWAMP responder
• Enabling the TWAMP responder
– Optionally changing the test session timeout default
– Optionally changing the control session timeout default
– Optionally changing the control session TCP port
A 1:1 test‐session to control‐session relationship is supported. Once TWAMP is configured, it
is possible to view its current status.
Configuration Steps
To configure the maximum number of sessions and to enable the TWAMP responder,
complete the following steps:
1. From the Global Configuration prompt, type probe responder twamp and press ENTER
to access the TWAMP Responder Configuration prompt.
2. From the TWAMP Responder Configuration prompt, type max-sessions <1-n>, then
press ENTER to set the number of maximum TWAMP sessions allowed at the NCTE.
The default value is 6.
3. From the TWAMP Responder Configuration prompt, type control source-port
<port_val>, and press ENTER to set the source control TCP port to port_val.
4. From the TWAMP Responder Configuration prompt, type test timeout <1-65535>,
then press ENTER to set the test session responder timeout in seconds.
The NCTE test session timeout is the amount of time during an active TWAMP test
session that the NCTE will wait on another test session packet before timing out and
closing the test session portion of the TWAMP protocol. The test session phase uses the
UDP protocol.
D-4 65K510DEP08-1A
Appendix D, TWAMP Provisioning - Current TWAMP Status
NOTE
If the start of the test session is never reached, only the control timeout is
used.
5. From the TWAMP Responder Configuration prompt, type control timeout <1-
65535>, and press ENTER to set the control session responder timeout in seconds.
The control timeout is similar to the test session timeout, but the control timeout applies
to the control session phase of TWAMP. The control sesion phase uses the TCP protocol.
6. From the TWAMP Responder Configuration prompt, enable the TWAMP responder, by
typing no shutdown, then press ENTER.
7. Type exit and press ENTER to exit to the Global Configuration prompt.
Current TWAMP Status

To view the current TWAMP status, complete the following:
From the Enable prompt, type show probe responder twamp to see the current TWAMP
status:
NetVanta800/8000#show probe responder twamp
TWAMP Reflector status
State: Enabled
Control Port: 862
Timeouts
Control: 900 seconds
Test: 900 seconds
Test Packets
Received: 745
Sent: 745
Sessions
Active: 3 of 6
Opened: 15
Closed: 12
Rejected: 13
Table D‐2 contains a description of the statistics listed in the example above:
65K510DEP08-1A D-5
Table D-2. Statistics
Statistic Description
Test Packets
Received This statistic provides the accumulation of the number of test‐session packets
received by active test‐session reflectors on the NCTE.
Sent This statistic provides the accumulation of the number of test‐session packets
sent by active test‐session reflectors on the NCTE.
Sessions
Active This statistic is expressed as X of Y. X is the number of currently active test
sessions on the NCTE. Y is the maximum number of test sessions allowed on
the NCTE.
Opened This statistic provides the accumulation of the number of test sessions that
have been opened on the NCTE.
Closed This statistic provides the accumulation of the number of test sessions that
have been closed on the NCTE.
Rejected This statistic provides the accumulation of the number of test sessions that
have been rejected on the NCTE. A rejection occurs when trying to exceed
the number of maximum sessions allowed.
D-6 65K510DEP08-1A
Appendix E
Dynamic Counters Provisioning

This appendix defines dynamic counters and describes the provisioning of dynamic counters.
In this Appendix
Table E-1. Appendix E Topics
Topic See Page
Introduction E‐2
Configure or Modify the Counter Profile for the Counter E‐2
65K510DEP08-1A E-1
Introduction
The Total Access 5000 provides the ability to view counts of various traffic types throughout
the system that is not generally available by way of the normal performance monitoring
buckets or counters. Dynamic counters allow the user to set up a counter monitoring traffic as
it is transmitted to, or received from, any interface in the Total Access 5000 or NetVanta. This
includes backplane, EFM group, Ethernet, Gigabit‐Ethernet, and Link Aggregation interfaces.
In addition to the interface to be monitored, the VLAN, VLAN p‐bit, and color of the traffic
can be specified.
A user could choose to monitor any green traffic being received on a particular VLAN from a
specified EFM bonding group. Or, a user could choose to monitor red traffic on a particular
VLAN being thrown away by the policer. Only one of each filter can be specified. For
example, two VLANs cannot be specified for a single dynamic counter.
Configure or Modify the Counter Profile for the Counter

Profiles can be edited to change any saved criteria.To configure or modifty a counter profile,
complete the following procedure:
2. From the Global Configuration prompt, set up one more counter profiles or an enter an
existing counter profile by typing counter-profile <shelf/slot/index>, and press
ENTER.
Counter profiles are not global. Each profile belongs to a shelf/slot. Profiles are used to
specify various filters for the counter.
3. As desired, type each of the following to configure the type of traffic to be specified by
the counter profile. Create the filter for the traffic type to be monitored:
• Type color <color>, and press Enter to specify a traffic color type. Valid values are
green, yellow, and red
• Type pbit <p_bit_value>, and press Enter to specify the S‐tag priority bit value. Valid
values are 0‐7
• Type vlan <VLAN>, and press Enter to specify the S‐tag value to be monitored
The profile is complete at this point.
5. From the Global Configuration prompt, type dynamic-counter <shelf/slot/
index>, and press ENTER to access the Dynamic‐Counter Configuration prompt.
6. From the Dynamic‐Counter Configuration prompt, type set counter-profile
<shelf/slot/index> [exclude|include], and press ENTER to specify the counter‐
profile to be used by the dynamic counter.
Use include to count packets that match the counter‐profile. Use exclude to count packets
that do not match the counter‐profile.
7. From the Dynamic‐Counter Configuration prompt, assign an interface to the counter by
typing set interface <interface_type> <shelf/slot/port> <traffic
direction>, and press ENTER.
Valid interface types are backplane, efm‐group, ethernet, gigabit‐ethernet, and lag‐
group. The traffic direction specifies whether the dynamic counter should be monitoring
traffic being transmitted to (tx) or received from (rx) the interface.
E-2 65K510DEP08-1A
Appendix E, Dynamic Counters Provisioning - Configure or Modify the Counter Profile for the Counter
8. From the Dynamic‐Counter Configuration prompt, type no shutdown, and press ENTER
enable the counter.
Shut the Counter Down

There are two methods to shut down an existing counter.
The first method is to type no dynamic-counter <shelf/slot/index>, and press ENTER.
The second method to delete an existing counter is described in the following procedure:
2. From the Global Configuration prompt, enter an existing counter profile by typing
counter-profile <shelf/slot/index>, and press ENTER.
3. From the Counter‐Profile Configuration prompt, type shutdown, and press Enter.
65K510DEP08-1A E-3
E-4 65K510DEP08-1A
Appendix F
NetVanta Examples

This appendix details a variety of different uses for the NetVanta products.
In this Appendix
Table F-1. Appendix F Topics
Topic See Page
Rules for Provisioning EVCs, EVC Maps, and Policers F‐2
EVCs F‐4
EVC Maps F‐7
Bandwidth Policer F‐14
NetVanta 800/8000 Series Applications F‐19
65K510DEP08-1A F-1
Rules for Provisioning EVCs, EVC Maps, and Policers

To ensure valid provisioning, the rules below are enforced for EVCs, EVC maps, and policers.
In most cases the value of the status attribute for an entity provides a brief description of the
condition.
1. An EVC, EVC map, or policer is applied only if the respective status is running, which
indicates that the conditions are valid.
2. Two EVC maps are considered to be duplicate if they both have the same values for the
• UNI port
• CE‐VLAN‐ID
• Overlapping range for CE‐VLAN‐Pri
• DSCP value
• Untagged/Priority‐tagged frames
3. Two EVCs are considered to be duplicate if they both have the same values for the
following attribute:
• S‐tag
4. Two Policers are considered to be duplicate if they both have the same values for the
• Mode
• UNI
• EVC
5. No EVC maps can have the same name.
6. No two EVCs can have the same name.
7. No two policers can have the same name.
8. If the network element is managed through a VLAN on a designated EFM bonding
group or Ethernet port for a port connected to by the system management EVC as a MEN
port, the following applies.
• Any EVC connected to the same MEN port with an s‐tag VID value equal to the
management VID value is invalid.
• If no EVCs are connected to the port, any EVC map sharing the same port but
connected to it as a UNI is made invalid if the EVC map is matching on a CE‐VLAN‐
ID equal to the VID of the system management EVC.
If a port is connected to the system management EVC as a UNI, it cannot be used by any
EVCs or EVC maps.
9. If the CE‐VLAN‐ID preservation attribute of an EVC is disabled, all of the associated
EVC maps must have the same value of the CE‐VLAN‐ID attribute.
10. When multiple EVC maps are applied to a common EVC, each EVC map must have the
same UNI. Multiple UNIs cannot be mapped to a common EVC.
11. If two EVC maps have the same UNI, only one of the EVC maps can be provisioned to
allow untagged and priority tagged frames.
12. No one Ethernet frame can be governed by more than one policer.
F-2 65K510DEP08-1A
Appendix F, NetVanta Examples - Rules for Provisioning EVCs, EVC Maps, and Policers
13. When two or more EVC maps have overlapping criteria and an incoming packet matches
two or more of the criteria for the EVC maps, the EVC map that has provisioning options
higher in the order of precedence, as shown in Table F‐2, is used to forward traffic.
Table F-2. EVC Map Forwarding Order of Precedence
Precedence Provisioning Options
1 12cp, ce‐vlan‐id, ce‐vlan‐pri
2 12cp, ce‐vlan‐pri
3 12cp, ce‐vlan‐id
4 12cp
5 unicast/multicast/broadcast, ce‐vlan‐id, ce‐vlan‐pri
6 unicast/multicast/broadcast, ce‐vlan‐pri
7 unicast/multicast/broadcast, ce‐vlan‐id
8 unicast/multicast/broadcast
9 untagged
10 dscp, ce‐vlan‐id
11 ce‐vlan‐id, ce‐vlan‐pri
12 ce‐vlan‐id
13 dscp
14 ce‐vlan‐pri
15 no match criteria options configured (only uni port is defined)
65K510DEP08-1A F-3
EVCs
The MEF defines an EVC as “an association of two or more UNIs,” where a UNI is a standard
10/100/1000 Ethernet interface that is the point of demarcation between the CE and the MEN
of the service provider. In simple terms, an EVC performs two functions.
frames
• Prevents data transfer between subscriber sites that are not part of the same EVC
Multiple EVCs can reside on a common bonding group or Ethernet port. Each EVC has an
associated EVC whose VLAN ID is unique among other EVCs in the MEN. The EVC s‐tag
allows the EVC to be identified and separated from other EVCs within the MEN. The EVC s‐
tag exists only within the MEN and is not transmitted from or received at the CE.
The MEF defines Ethernet Line (E‐Line) services as a service that provides a point‐to‐point
EVC that connects exactly two UNIs.
EVC Attributes
The attributes of an EVC are described in the following paragraphs.
Name
This attribute is an arbitrary string that is used to identify the EVC within the MEN. The value
must be unique across all EVCs defined in the network element, and is intended for
management and control purposes. The value is not carried in any field in the Ethernet frame.
As an example, the Acme Service Provider can use “EVC‐0001898‐ACME‐MEGAMART” to
represent the 1898th EVC in the MEN. In this example, the customer for the EVC is MegaMart.
Configuration Status
This read‐only attribute indicates the current status of the EVC. The EVC can be administra‐
tively enabled, but can not be in the functional state if it is not fully configured or if a conflict
exists. If the EVC is not applied due to the configuration or a conflict, refer to Table F‐3 for a
lists of the possible values.
Table F-3. EVC Status Values
Possible Values Definition
Running Conditions are okay and the EVC provisioning is applied.
Missing Connection The EVC is not connected to enough active interfaces. The mini‐
mum required is two. The active interface can be directly con‐
nected by MEN‐port or mapped UNI.
Tag Conflict Another EVC is administratively enabled and configured to use
the same s‐tag.
Disabled The State value of the EVC is provisioned as disabled.
System‐management‐evc Con‐ The EVC s‐tag is in use by the system management EVC.
flict
F-4 65K510DEP08-1A
Appendix F, NetVanta Examples - EVCs
Admin State
This attribute is the user‐configurable state of the EVC. Table F‐4 lists the available options.
Table F-4. EVC State Options

Option Definition
Enabled The EVC is in service, and the provisioning is applied if the con‐
ditions are valid.
Disabled The EVC is not in service, and the provisioning is not applied.
MEN Port
This attribute is the physical interface connected to the MEN. The possible options consist of
the Ethernet port(s) and bonding group(s) available on the specific product. In typical config‐
urations, the MEN port is specified as a bonding group. One or more MEN ports can be
directly connected to an EVC. A connected MEN port has an associated status that determines
if it can be used by the EVC to transmit/receive traffic. This status is read‐only to an EVC and
is controlled by external processes (for example, LinkOAM or EVC Advertisement). Ports
disallowed by external processes cannot be used during the validation of the configuration of
an EVC.
S-tag
This attribute is the VLAN ID associated with the EVC s‐tag. The EVC VID is set using the s‐
tag command. If the alias specified during creation is numeric, the s‐tag will default to match.
List of Connected EVC Maps

This attribute lists all EVC maps connected to the EVC, each with an associated status. EVC
maps listed as “Running” can transmit/receive EVC traffic.
NOTE
Not all EVC maps are required to be in the “Running” state for the EVC to be
successfully transporting traffic.
CE-VLAN Preservation
This attribute controls whether to preserve the CE‐VLAN tag within the EVC. This option
must be enabled if multiple CE‐VLANs are forwarded to the EVC (Refer to Rule 9 on page F‐
2). Table F‐5 lists the available options.
65K510DEP08-1A F-5
Table F-5. CE-VLAN Preservation Options

Option Definition
Enabled When this attribute is set to enabled, the following occurs.
• In the UNI‐to‐MEN direction, the frame is encapsulated and
transported by the EVC as is.
• In the MEN‐to‐UNI direction, the frame is unencapsulated
and egresses the UNI.
Disabled When this attribute is set to disabled, the following occurs.
• In the UNI‐to‐MEN direction, the CE‐VLAN tag is stripped if
present and the frame is then encapsulated and transported by
the EVC. Depending on the MEN‐Pri attribute of the
associated EVC map(s), the P‐bit value of the EVC is either set
explicitly or is inherited from the stripped CE‐VLAN tag.
• In the MEN‐to‐UNI direction, if the connected EVC maps are
matching on a single CE‐VLAN‐ID and not matching
untagged/priority tagged, then the frame is unencapsulated
and the CE‐VLAN‐ID of the EVC map is added. Depending on
the MEN‐Pri attribute of the connected EVC map(s), the P‐bit
value of the added CE‐VLAN tag is either set explicitly or is
inherited from the EVC s‐tag.
• If the connected EVC maps are matching on a single CE‐
VLAN‐ID and matching untagged/priority tagged, then the
frame is unencapsulated and the CE‐VLAN‐ID of the EVC
map is not added.
F-6 65K510DEP08-1A
Appendix F, NetVanta Examples - EVC Maps
EVC Maps
An EVC map classifies traffic ingressing a UNI into an EVC given configured match criteria. It
uniquely identifies a subscriber traffic flow within an EVC and provides the mechanism for
VLAN tag manipulation, Ingress Bandwidth Policing, forwarding, and queuing.
EVC Map Attributes

The attributes of a EVC Map are described in the following sections.
Destination EVC
This attribute defines the name of the EVC that the EVC map is fowarding traffic to and
receiving from. This attribute can also be used to discard traffic matched by the EVC map. An
EVC map is limited to a single EVC connection.
Name
This attribute is an arbitrary string that is used to identify the EVC map. The value must be
unique across all EVC maps defined in the network element and is intended for management
and control purposes. The value is not carried in any field in the Ethernet frame. As an
example, the service provider might use “SCPOP1‐Node3‐Slot2‐Port1” to signify port 1 in slot
2 of node 3 in Santa Clara POP1.
This attribute indicates the current status of the EVC map. The EVC map can be administra‐
tively enabled, but it can not be in a functional state if it is not fully configured or if there is a
conflict. Table F‐6 lists the possible values.
Table F-6. EVC Map Status Values
Possible Value Definition
Running Conditions are okay and the EVC map provisioning is applied.
Missing Connection to EVC The EVC map is not connected to an EVC or the EVC does not
exist.
EVC not running The connected EVC is not in the “Running” state.
Invalid UNI The EVC map is not connected to a UNI, the connected UNI does
not exist, or the EVC map is not available for Ethernet services.
Disabled The EVC map administrative state is disabled.
Duplicate EVC‐map Another EVC map exists having a conflicting ingress criteria.
Refer to Rule 2 on page F‐2.
65K510DEP08-1A F-7
Table F-6. EVC Map Status Values (Continued)
Overlaps System‐management‐ The CE‐VLAN‐ID conflicts with the VID that is actively used for
evc managing the system and the two are sharing the same port..
Preserve conflict The EVC is not preserving CE‐VLAN‐ID and has at least two
EVC maps connected to it with different values for the CE‐
VLAN‐ID attribute. For an EVC forwarding traffic in the MEN‐
to‐UNI direction, the switch uses the CE‐VLAN‐ID value of the
EVC map. There is no way for the switch to determine what
value to apply if the values vary across connected EVC maps.
Overlaps EVC The UNI of the EVC map is used by a MEN‐port of an enabled
EVC.
Admin State
This attribute is the user‐configurable state of the EVC map. Table F‐7 lists the available
options.
Table F-7. Map State Options

Option Definition
Enabled The EVC map is in service, and the provisioning is applied if the
conditions are valid.
Disabled The EVC map is not in service, and the provisioning is not
applied.
UNI
This attribute is the physical interface connected to the Customer Equipment (CE) or
subscriber. It is the demarcation point of Adtran equipment to the subscriber premises and is
the gateway into the EVC. The protection of the EVC is performed at the UNI so that assump‐
tions can be made within the EVC.
CE-VLAN-ID
This attribute is the VLAN ID of the outermost VLAN tag of the Ethernet frame received at the
UNI port. If the value is unspecified, then the EVC map applies to the remainder of customer
frames received that are not affected by other EVC maps on the same UNI port.
CE-VLAN-Pri
This attribute is a range of P‐bit values of the outermost VLAN tag of the Ethernet frame
received at the UNI port. This attribute can only be specified if the DSCP attribute is not
specified. The value is entered as a character string of the allowable P‐bit values.
F-8 65K510DEP08-1A
DSCP
This attribute is the DSCP value of the Ethernet frame received at the UNI port. This attribute
can only be specified if the CE‐VLAN P‐bit attribute is not specified.
Untagged and Priority Tagged Frames

This attribute controls whether untagged and priority tagged frames are allowed to ingress
the UNI port in addition to frames tagged with the specified CE‐VLAN‐ID. Table F‐8 lists the
available options.
Table F-8. Untagged and Priority Tagged Frame Options

Option Definition
Enabled Untagged and priority‐tagged frames are allowed at the UNI
port.
Disabled Untagged and priority‐tagged frames are discarded at the UNI
port.
A priority tag is a frame that is tagged with a CE VLAN ID of zero. If the untagged attribute is
specified with no other attributes except the UNI port, then the EVC map only forwards
untagged and priority tagged frames to the EVC. If other attributes are specified for the EVC
map in addition to the untagged attribute, then the untagged and priority tagged attribute
indicates that untagged and priority tagged frames are forwarded to the EVC in addition to
the frames that are characterized by the other EVC map attributes.
MEN-Pri
This attribute controls how frames classified by the EVC map populate the p‐bit of the s‐tag
added by the EVC. This attribute can be explicitly set to a priority value in the range of 0 to 7
or it can be set to inherit. If this attribute is set to inherit, the top VLAN tag p‐bit value of the
classified frames is used to populate the EVC s‐tag p‐bit field. If the classified frame does not
contain a VLAN tag, the p‐bit value used can be derived from a system level setting. If the
attribute is explicity set to a value, all classified frames by the EVC map add the EVC service
tag with a p‐bit equal to the explicity configured value.
Men-Queue
This attribute controls how frames admitted by the EVC map are mapped to queues. If the
MEN queue attribute is explicity set, the traffic enters the desired queue regardless of the
system level provisioned p‐bit to queue mapping from the network element. When set to
inherit, it follows the system level provisioned mapping.
The CoS mapping can be changed from the default 802.1Q‐2005 mapping by using the qos
cos‐map <queue> <class> command.
Policer
This attribute displays the policer, if any, that is applied to the EVC map.
65K510DEP08-1A F-9
MAC Type - Broadcast/Multicast/Unicast

This attribute matches the MAC address type of traffic to be admitted to the EVC map. If one
or more of these attributes are set, frames are admitted into the connected EVC if it matches
any of the types configured. By default, an EVC map ignores MAC type in the classification.
Table F‐9 lists the MAC types.
Table F-9. MAC Type
Type MAC DA Description MAC DA Example
Broadcast All 1s FF:FF:FF:FF:FF:FF
Multicast First octet LSB is 1 01:00:00:00:00:00
Unicast First octet LSB is not a 1 0A:C8:2C:DD:DD:DD
L2CP
This attribute matches traffic based on a group of Layer 2 Control Protocols (L2CP) desti‐
nation MAC addresses. If this attribute is enabled, all L2CP frames listed in Table F‐10 are
classifed by the EVC map.
Table F-10. L2CP Frames
Control Protocol MAC Destination Address
STP/RSTP/MSTP 01 80 C2 00 00 00
Pause 01 80 C2 00 00 01
LACP/EFM OAM/LLDP/Slow 01 80 C2 00 00 02
Protocol
802.1x 01 80 C2 00 00 03
Undefined Bridge Addresses 01 80 C2 00 00 04‐0E
All Bridges 01 80 C2 00 00 10
GMRP 01 80 C2 00 00 20
GVRP 01 80 C2 00 00 21
Example #1: Two CE-VLANs Mapped to Two EVCs

Figure F‐1 illustrates an example of two customer VLANs that ingress the network element on
a common UNI port and map to two different EVCs. Customer VLAN 1 is mapped to the EVC
with SVID 101, and customer VLAN 2 is mapped to the EVC with SVID 102. Both EVCs can
reside on the same physical interface (for example, bonding group), or both EVCs can reside
on two different interfaces.
F-10 65K510DEP08-1A
MEN
CE VLAN 1 EVC #1, SVID = 101 CE VLAN 1
UNI UNI
CE VLAN 2 EVC #2, SVID = 102 CE VLAN 2
Figure F-1. E-Line Service - EVC per CE-VLAN
Figure F‐2 provides a more detailed view of the mapping of the customer VLANs into the
EVCs in the UNI‐to‐MEN direction. For this example, both EVCs reside on the same bonding
group, and the CoS for each received customer frame is inherited from the P‐bit value of the
outermost customer VLAN tag. The following provisioning applies on each system.
• EVC #1: MEN Port = EFM‐Group 1/0/1, S‐tag = 101, CE‐VLAN‐ID Preservation = Enabled
• EVC Map #1: UNI = Ethernet 1/0/1, CE‐VLAN‐ID = 1, EVC = 1, MEN‐Pri = Inherit
• EVC Map #2: UNI = Ethernet 1/0/1, CE‐VLAN‐ID = 2, EVC = 2, MEN‐Pri = Inherit
Link #1
P-bit 7 P-bit 7
EVC #1 Link #2
CE VLAN ID 1 P-bit 6 P-bit 6
VID 101
Link #3
UNI Bonding
Group
P-bit 7 P-bit 7
EVC #2
CE VLAN ID 2 P-bit 6 P-bit 6
VID 102
Link #n
Customer Metro Ethernet

Interface Network Interface
Figure F-2. Detailed Mapping of Two Point-to-Point EVCs
Example #2: Two CE-VLANs Mapped to One EVC

Figure F‐3 illustrates an example of two customer VLANs that ingress the network element on
a common UNI port and map to a common EVC. Customer VLANs 1 and 2 are mapped to an
EVC with SVID 101.
65K510DEP08-1A F-11
MEN
CE VLAN 1 CE VLAN 1
UNI EVC #1, SVID = 101 UNI
CE VLAN 2 CE VLAN 2
Figure F-3. E-Line Service - EVC per Multiple CE-VLANs
Figure F‐4 provides a more detailed view of the mapping of the customer VLANs into the
EVC in the UNI‐to‐MEN direction. For this example, the CoS for each received customer
frame is inherited from the P‐bit value of the outermost customer VLAN tag. The following
provisioning would apply on each system.
• EVC‐map #1: UNI = Ethernet 1/0/1, CE‐VLAN‐ID = 1, EVC = 1, MEN‐Pri = Inherit
• EVC‐map #2: UNI = Ethernet 1/0/1, CE‐VLAN‐ID = 2, EVC = 1, MEN‐Pri = Inherit
Link #1
P-bit 7
Link #2
CE VLAN ID 1 P-bit 6
P-bit 7
Link #3
EVC #1
UNI P-bit 6 Bonding
SVID 101
Group
P-bit 7
CE VLAN ID 2 P-bit 6
Link #n
Customer Metro Ethernet

Interface Network Interface
Figure F-4. Detailed Mapping of a Point-to-Point EVC
Example #3: EVC Map Forwarding

When two or more EVC maps have overlapping criteria and an incoming packet matches two
or more of the criteria for the EVC maps, the EVC map that has provisioning options higher in
the order of precedence (refer to Rule 13 on page F‐3) is used to forward traffic.
An example in which three EVC maps are configured on the NCTE is defined as follows:
evc-map 1
connect uni eth 1/0/1
match l2cp
match ce-vlan-id 1
match ce-vlan-pri 5
F-12 65K510DEP08-1A
connect evc 1
no shutdown
evc-map 2
match unicast
match ce-vlan-id 1
match ce-vlan-pri 5
connect eVc 2
no shutdown
evc-map 3
match ce-vlan-id 1
match ce-vlan-pri 5
connect evc 3
no shutdown
If a packet arrives at Ethernet 1/0/1 UNI port containing a valid L2CP address, a VLAN ID of
1, and a VLAN priority of 5, the packet matches criteria in both EVC‐map #1 and EVC‐map #3,
but the packet gets forwarded by EVC‐map #1 to EVC 1 because EVC‐map #1 has a higher
order of precedence than the criteria for EVC‐map #3. If another packet arrives at Ethernet 1/0/
1 UNI port containing a unicast destination address, a VLAN ID of 1, and a VLAN priority of
5, the packet matches criteria in both EVC‐map #2 and EVC‐map #3, but the packet gets
forwarded by EVC‐map #2 to EVC 2 because EVC‐map #2 has a higher order of precedence
than the criteria for EVC‐map #3. Finally, if a third packet arrives at the Ethernet 1/0/1 UNI
port containing a broadcast destination address, a VLAN ID of 1, and a VLAN priority of 5,
the packet matches only the criteria in EVC‐map #3 and gets forwarded to EVC 3.
65K510DEP08-1A F-13
Bandwidth Policer
A bandwidth policer is a method of characterizing service frames for the purpose of rate
enforcement. A bandwidth policer can be applied in one of the following ways:
• Ingress bandwidth policer per ingress UNI
• Ingress bandwidth policer per EVC
• Ingress bandwidth policer per custom
In typical applications, the bandwidth available on the EVC is less than the bandwidth
available at the UNI port. The bandwidth bottleneck is typically only in the UNI‐to‐MEN
direction; therefore, all bandwidth policers are applied only for traffic conducted in the UNI‐
to‐MEN direction. Policers are not applied to the traffic conducted in the MEN‐to‐UNI
direction.
Bandwidth Policer Attributes

The attributes of a bandwidth policer are described in the following paragraphs.
Name
This attribute is an arbitrary string that is used to identify the policer. The value must be
unique across all policers defined in the product, and is intended for management and control
purposes. The value is not carried in any field in the Ethernet frame.
This attribute is a read‐only status identifier of the policer. The policer can be administratively
enabled, but it can not be in functional state if it is not fully configured or if there is a conflict.
Table F‐11 lists the possible values.
Table F-11. Policer Status Values
Running The policer is running and applying ingress a bandwidth profile
to any matching EVC maps.
Disabled The administrative state of the policer is provisioned as Disabled.
Duplicate policer An enabled policer with equal precedence and equal value exists.
Refer to Rule 4 on page F‐2.
Invalid rate(s) The values for CIR and/or EIR conflict in relation to the rate cou‐
pling value.
No Mode The mode attribute of the policer is not set.
Unknown UNI The mode is per UNI and the UNI can not be found.
Unknown EVC The mode per EVC and the EVC can not be found.
Unknown EVC‐map The mode per Custom and the EVC map can not be found.
F-14 65K510DEP08-1A
Appendix F, NetVanta Examples - Bandwidth Policer
Admin State
This attribute is the user‐configurable state of the policer. Table F‐12 lists the available options.
Table F-12. Policer State Options
Option Definition
Enabled The policer is in service, and the provisioning is applied if the
conditions are valid.
Disabled The policer is not in service, and the provisioning is not applied.
Mode
This attribute controls how the policer is applied. A policer can be applied to multiple EVC
maps simultaneously and the list of EVC maps it applies to is determined by the mode that it
is configured in. Table F‐13 lists the available modes.
Table F-13. Mode Options
Option Definition
Not Applied The policer is not applied.
Per UNI The policer is applied to all EVC maps of a specific UNI port.
Per EVC The policer is applied to all EVC maps associated with a specific
EVC.
Custom The policer is applied to one or more EVC maps.
UNI
This attribute is available and meaningful only if the mode is per UNI. The policer is applied
to all EVC maps connected to a specific UNI.
EVC
This attribute is available and meaningful only if the mode is per EVC. The value is the name
of the associated EVC. The policer is applied to EVC maps connected to the same UNI and
connected to a specific EVC. It can be worded as “Per EVC per UNI.”
List of EVC-maps
Each policer entry lists the EVC maps that match the criteria and a policing status for each
EVC map. An EVC map entry with a status of “Applied” indicates all traffic matched by the
EVC map is subject to the bandwidth profile of the policer.
CIR
The CIR defines the average rate in kilobit per second (kbps) of service frames up to which the
network delivers service frames and meets the performance objectives of the service. Service
frames admitted by the CIR are colored green.
65K510DEP08-1A F-15
CBS
The CBS is the maximum available bytes for a burst of ingress traffic sent at the UNI speed
while still conforming to the CIR.
EIR
The EIR defines the average rate in kilobit per second (kbps) of service frames up to which the
network can deliver service frames but without an performance objectives. Service frames
allowed by the EIR are colored yellow.
EBS
The EBS is the maximum available bytes for a burst of ingress traffic sent at the UNI speed
while still conforming to the EIR.
Example #1: Ingress Bandwidth Policer per UNI

A single bandwidth policer can be applied to all ingress frames at a designated UNI. This type
of policer manages bandwidth non‐discriminately for all EVCs that are associated with the
UNI. Depending on the configuration and traffic conditions during periods of congestion,
some EVCs get more bandwidth while others get less bandwidth if multiple EVCs are
associated with the UNI.
Consider the conditions of “Example #1: Two CE‐VLANs Mapped to Two EVCs” on page F‐
10, where traffic for two customer VLANs is received at the same UNI port and mapped to
two different EVCs.
The following policer would collectively apply to all frames that ingress at Ethernet 1/0/1 (for
example, the two customer VLANs). The policer would give a total of 5Mbps with 2Mbps
considered green and 3Mbps considered yellow.
Policer #1:
• CIR/EIR Coupling = Disabled
• Committed Information Rate (CIR) = 2000 kbps
• Excess Information Rate (EIR) = 3000 kbps
• Committed Burst Size (CBS) = 3125 bytes
• Excess Burst Size (EBS) = 12500 bytes
• Mode = Per UNI
• UNI = Ethernet 1/0/1
Policer #1 is applied to ingress traffic of both EVC‐map #1 and EVC‐map #2 because these EVC
maps have Ethernet 1/0/1 defined as the UNI port.
Example #2: Ingress Bandwidth Policer per EVC

A single bandwidth policer can be applied to all ingress frames that are mapped to a desig‐
nated EVC. If traffic is mapped from a UNI to two EVCs, then one policer can be defined for
each EVC.
Consider the conditions of “Example #1: Two CE‐VLANs Mapped to Two EVCs” on page F‐
10, where two customer VLANs are received at the same UNI port and mapped to two
different EVCs.
F-16 65K510DEP08-1A
Appendix F, NetVanta Examples - Bandwidth Policer
The following policers would apply to the respective EVC.
Policer #1:
• CIR = 1000 kbps
• EIR = 2000 kbps
• CBS = 3125 bytes
• EBS = 12500 bytes
• Mode = Per EVC
• EVC = #1
Policer #2:
• CIR = 2000 kbps
• EIR = 3000 kbps
• Mode = Per EVC
• EVC = #2
Policer #1 is applied to ingress traffic of EVC‐map #1, because all egress traffic into the MEN
from EVC #1 is in the EVC‐map #1 criteria.
Policer #2 is applied to ingress traffic of EVC‐map #2, because all egress traffic into the MEN
from EVC #2 is in the EVC‐map #2 criteria.
Example #3: Ingress Bandwidth Policer per Custom

A single bandwidth policer can be applied to ingress frames of a particular EVC map or set of
EVC maps. Use this application of the bandwidth policer to limit traffic on ingress frames
without having to specify the UNI or EVC. The custom policer makes it possible to limit traffic
on EVC maps that have CE‐VLANs as the criteria. It also allows implementing different
policers on EVC maps that have a common connected to an EVC but are not duplicate EVC
maps.
Consider the conditions of “Example #2: Two CE‐VLANs Mapped to One EVC” on page F‐11
where two CE‐VLANs are received at the same UNI port and mapped to the same EVC. In
order to enforce a different bandwidth policer for each CE‐VLAN, apply separate custom
policers to each EVC map.
The following policers can apply to the respective EVC maps.
Policer #1
• CIR = 1000 kbps
• EIR = 2000 kbps
• Mode = Custom
65K510DEP08-1A F-17
• Connected = EVC‐map #1
Policer #2
• CIR = 2000 kbps
• EIR = 3000 kbps
• Mode = Custom
• Connected = EVC‐map #2
Policer #1 is applied to the ingress traffic of EVC‐map #1, which is CE‐VLAN 1.
Policer #2 is applied to the ingress traffic of EVC‐map #2, which is CE‐VLAN 2.
F-18 65K510DEP08-1A
Appendix F, NetVanta Examples - NetVanta 800/8000 Series Applications
NetVanta 800/8000 Series Applications

Figure F‐5 displays several, typical applications of the NetVanta 800 Series products. NTU #1
carries traffic from four different customers, each on an individual CE‐VLAN. NTU #2 carries
untagged traffic from a single customer. NTU #3 is subtended off of LTU #2 and carries only
certain priority traffic from individual customers and sends the priority traffic through
separate EVCs to LTU #2. LTU #2 picks up one more additional customer utilizing a certain
DSCP level. NTU #1, #2, and LTU #2 send traffic through EVCs to LTU #1, which serves as an
aggregator before mapping all traffic to EVCs that traverse the Gigabit‐Ethernet port to and
from the MEN. LTU #1 picks up the untagged traffic of another local customer. Refer to the
following script for the values to configure each NTU and LTU shown in this application.
EVC 1101
EVC 1102
EVC 1103
EVC 1104 CE-VLAN 101
CE-VLAN 102
10/100
NTU #1 ETH 10/100
10/100
1
Group 1
XDSL
Group 2 Group 1
LTU #1
EFM
EFM
GE
GE
MEN Gig 1 ETH

2
10/100
10/100
10/100
XDSL
CE-VLAN 103
EFM
EVC 4000 ETH 1 CE-VLAN 104
Group 1
EFM
10/100
ETH 2
UNTAGGED
EVC 2201 ETH 10/100

1
CE-VLAN 305 NTU #2
UNTAGGED
10/100
DSCP=35
GE
CE-VLAN 302 PRI=5-7

ETH 1 Gig 1 10/100
CE-VLAN 301 PRI=6
ETH
Group 1
Group 1
XDSL
10/100 10/100
1
EFM
EVC 3305 EFM

ETH 10/100 10/100
2
LTU #2 Gig ETH
10/100 10/100
NTU #3 1 3
CE-VLAN 303 PRI=3
GE
EVC 3301
EVC 3302
EVC 3303 UNTAGGED
EVC 3304
Figure F-5. Typical NetVanta 800/8000 Series Applications
Configuration for LTU #1

The following script corresponds to the configuration shown in Figure F‐5 for LTU #1.
NV800(config)#evc-map customer1
NV800(config-evc-map customer1 1/0)#match ce-vlan-id 1101
NV800(config-evc-map customer1 1/0)#connect evc 1101
NV800(config-evc-map customer1 1/0)#connect uni efm-group 1/0/1
NV800(config-evc-map customer1 1/0)#no shutdown
NV800(config-evc-map customer10 1/0)#connect uni ethernet 1/0/1
65K510DEP08-1A F-19

NV800(config)#evc 1101
NV800(config-evc 1101)#connect men-port gigabit-ethernet 1/0/1
NV800(config-evc 1101)#no preserve-ce-vlan
NV800(config-evc 1101)#no shutdown
F-20 65K510DEP08-1A

65K510DEP08-1A F-21
Configuration for LTU #2

The following script corresponds to the configuration shown in Figure F‐5 for LTU #2.
NV800(config-evc-map customer10 1/0)#match dscp 35
NV800(config-evc-map customer10 1/0)#connect uni gigabit-ethernet 1/
0/1
NV800(config-evc 3301)#connect men-port ethernet 1/0/1
F-22 65K510DEP08-1A
Configuration for NTU #1

The following script corresponds to the configuration shown in Figure F‐5 for NTU #1.
NV800(config-evc 1101)#connect men-port efm-group 1/0/1
NV800(config-evc 1104)#men-port efm-group 1/0/1

65K510DEP08-1A F-23

NV800(config-evc-map customer6 1/0)#match ce-vlan-pri 6
NV800(config-evc-map customer7 1/0)#match ce-vlan-pri 5-7
NV800(config-evc-map customer8 1/0)#match ce-vlan-pri 3
NV800(config-evc-map customer9 1/0)#connect uni gigabit-ethernet 1/0/
1
F-24 65K510DEP08-1A
Appendix G
BSM DS3/DS1 Layer 1 Tests

The Total Access 5000 System Release 5.1supports DS3 and DS1 test capabilities.
In this Appendix
Table G-1. Appendix G Topics
Topic See Page
Loopback Definition G‐2
Line Loopback G‐2
Payload Loopback G‐2
Remote Loopback G‐3
DS3 Test Configuration G‐3
DS1 Test Configuration G‐5
65K510DEP08-1A G-1
Loopback Definition
A loopback and Bit Error Rate Test (BERT) provide the ability to insert a known traffic pattern
and verify the error‐free performance of the circuit at given points in the system.
Line Loopback
A line loopback (see Figure G‐1) loops all of the received data back toward the network (DS3
payload and DS3 data). The transmitted data is the identical data that is received and is not
reframed or regenerated. This tests right up to the DS3 interface of the module.
The line loopback can be local to the access module.
Line Loopback
DS3 Interface
DS-3 Facility Framer
Figure G-1. Line Loopback Diagram
Payload Loopback
A payload loopback (see Figure G‐2) performs the same functionality as the line loopback,
except the payload loopback sends the received data through the framer, where it is reframed
and regenerated, prior to being transmitted back out towards the network. This test also
verifies the internal hardware of the module.
The payload loopback is locally initiated.
NOTE
The DS3 does not support a payload loopback.
G-2 65K510DEP08-1A
Appendix G, BSM DS3/DS1 Layer 1 Tests - Remote Loopback
Payload Loopback
DS3 Interface
Figure G-2. Payload Loopback Diagram
Remote Loopback
A remote loopback (see Figure G‐3)transmits a Far End Loop‐up code via the FEAC channel in
the DS3 module to the customer equipment, which responds by setting‐up a line loopback
towards the DS3 card in the Total Access 5000. After the customer equipment DS3 port is
looped‐up, BERT patterns can be sent from the DS3 card to test the integrity of the DS3 circuit.
NOTE
DS3 BERT patterns can be sent from external test equipment. For example,
the integrated BERT in the DS3 EFM module.
The Remote Loopback request only works in the C‐Bit framing mode.
Remote Loopback
NetVanta 873 Total Access 5000
DS-3 Facility DS-3 Facility
Framer Framer
Figure G-3. Remote Loopback Diagram
DS3 Test Configuration

• Remote loopback configuration
• Test administrative functions
• Local line loopback configuration
• BERT test configuration
65K510DEP08-1A G-3
Remote Loopback Configuration

To configure the unit to respond to (enable) or to ignore (disable) to remote loopback
commands, complete the following steps:
press ENTER to access the T3 Interface Configuration prompt.
3. From the T3 Interface Configuration prompt, perform one of the following:
• Type remote-loopback, and press ENTER to provision the port to respond to remote
loopback commands.
• Type no remote-loopback, and press ENTER to provision the port to ignore remote
loopback commands.
4. From the T3 Interface Configuration prompt, type end, and press ENTER to return to the
Enable prompt.
Test Administrative Functions

The Total Access 5000 CLI Application prompt, controls both the local loopback and BERT
functions. While in the Application prompt, the following commands can be issued:
• View the current test status of the DS3 interface by typing show test interface t3
<shelf/slot/port>, and press ENTER
• Clear the test statistics of the DS3 interface by typing test interface t3
<shelf/slot/port> clear, and press ENTER
• Stop any test in progress (loopback or BERT) by typing no test interface t3
Local Line Loopback Configuration

To configure local DS3 loopbacks, complete the following steps:
prompt.
2. From the Application prompt, type test interface t3 <shelf/slot/port> local
loopback line timeout <0-9999>, and press ENTER to start a DS3 line loopback.
NOTE
• The loopback timeout is optional and can be left off the loopback command
NOTE
• The DS3 line loopback can be stopped by typing no test interface t3
BERT Test Configuration

The Channelized DS3 Multi‐Service 3‐Port performs BERT generation and testing at the DS3
interfaces. To configure the DS3 BERT, complete the following steps:
G-4 65K510DEP08-1A
Appendix G, BSM DS3/DS1 Layer 1 Tests - DS1 Test Configuration
prompt.
2. From the Application prompt, start the BERT by performing one of the following
commands:
• Type test interface t3 <shelf/slot/port> remote pattern
<pattern_type>, and press ENTER.
• Type test interface t3 <shelf/slot/port> remote pattern
<pattern_type> loopback line timeout <0-9999>, and press ENTER to start a
DS3 BERT test and request a remote loopback (at the customer equipment toward
the Total Access 5000) of the DS3.
NOTE
Valid <pattern_type> values are p215, p220, and p223.
3. From the Application prompt, type test interface t3 <shelf/slot/port>

insert-error, and press ENTER to inject a bit error into the pattern.
NOTE
• Injecting a bit error into the pattern is optional
NOTE
• The DS3 BERT test can be stopped by typing no test interface t3
DS1 Test Configuration

• Remote loopback configuration
• Test administrative functions
• Local line loopback configuration
• BERT test configuration
Remote Loopback Configuration

To configure the unit to respond to (enable) or to ignore (disable) to remote loopback
commands, complete the following steps:
port:channel>, and press ENTER to access the T1 Interface Configuration prompt.
3. From the T1 Interface Configuration prompt, perform one of the following:
• Type remote-loopback <command_type>, and press ENTER to provision the port
to respond to remote loopback commands.
65K510DEP08-1A G-5
NOTE
Valid <command_type> values are csu, fdl, and feac.
• Type no remote-loopback, and press ENTER to provision the port to ignore remote
loopback commands.
NOTE
Valid <command_type> values are csu, fdl, and feac.
4. From the T1 Interface Configuration prompt, type end, and press ENTER to return to the
Enable prompt.
Test Administrative Functions

The Total Access 5000 CLI Application prompt, controls both the local loopback and BERT
functions. While in the Application prompt, the following commands can be issued:
• View the current test status of the DS3 interface by typing show test interface t1
<shelf/slot/port:channel>, and press ENTER
• Clear the test statistics of the DS3 interface by typing test interface t1
<shelf/slot/port:channel> clear, and press ENTER
• Stop any test in progress (loopback or BERT) by typing no test interface t1
Local Line Loopback Configuration

To configure local DS3 loopbacks, complete the following steps:
prompt.
2. From the Application prompt, type test interface t1 <shelf/slot/
port:channel> local loopback line timeout <0-9999>, and press ENTER to start
a DS1 line loopback.
NOTE
• The loopback timeout is optional and can be left off the loopback command
NOTE
• The DS3 line loopback can be stopped by typing no test interface t1
BERT Test Configuration

The Channelized DS3 Multi‐Service 3‐Port performs BERT generation and testing at the DS3
interfaces. To configure the DS3 BERT, complete the following steps:
prompt.
G-6 65K510DEP08-1A
Appendix G, BSM DS3/DS1 Layer 1 Tests - DS1 Test Configuration
2. From the Application prompt, start the BERT by performing one of the following
commands:
• Type test interface t1 <shelf/slot/port:channel> remote pattern
<pattern_type>, and press ENTER.
• Type test interface t1 <shelf/slot/port:channel> remote pattern
<pattern_type> loopback <lpbk_req_type> timeout <0-9999>, and press
ENTER to start a DS1 BERT test and request a remote loopback (at the customer
equipment toward the Total Access 5000) of the DS1.
NOTE
• Valid <pattern_type> values are 1in8, all0s, all1s, and qrss
NOTE
• Valid <lpbk_req_type> values are csu, fdl, feac, and niu
3. From the Application prompt, type test interface t1 <shelf/slot/

port:channel> insert-error, and press ENTER to inject a bit error into the pattern.
NOTE
• Injecting a bit error into the pattern is optional
NOTE
• The DS3 BERT test can be stopped by typing no test interface t1
65K510DEP08-1A G-7
G-8 65K510DEP08-1A
Appendix H
Alarm Severities

This appendix defines the T1 and T3 alarm severities and provides provisioning guidance for
the alarms.
In this Appendix
Table H-1. Appendix H Topics
Topic See Page
Introduction H‐2
Default Severities H‐2
T3 Alarm Severity Level H‐2
T1 Alarm Severity Level H‐3
65K510DEP08-1A H-1
Introduction
Total Access System Release 4.5 allows the user to configure the alarm severity level for all T3
and T1 fault alarms, along with being able to enable or disable all alarms. The alarm severities
are provisioned on a per‐slot basis.
Default Severities
Table H‐2 displays the T3 and T1 alarms and their default severities.
Table H-2. Default Severities
Alarm Default
T3 Alarm Defaults
LOS Major
LOF Major
RAI Minor
AIS Major
T1 Alarm Defaults
LOF Major
RAI Minor
AIS Major
T3 Alarm Severity Level

To set the alarm severity level for a T3 alarm, complete the following steps:
press ENTER to access the T3 Configuration prompt.
3. From the T3 Configuration prompt, type alarm level <alarm_name>
<alarm_level>, and press ENTER to set the alarm severity level. Refer to Table E‐2 for
valid alarm_name and alarm_level values.
4. From the T3 Configuration prompt, provision the alarm status by performing one of the
following commands:
• Type no alarm enable <alarm_name>, and press ENTER to disable the specified
alarm
• Type alarm enable <alarm_name>, and press ENTER to enable the specified alarm
5. From the T3 Configuration prompt, type end, and press ENTER to return to the Enable
prompt.
Table H‐3 displays the T3 Parameter Values.
H-2 65K510DEP08-1A
Appendix H, Alarm Severities - T1 Alarm Severity Level
Table H-3. T3 Parameter Values
alarm_name alarm_level
LOS Critical
LOF Major
RAI Minor
AIS Alert
Information
T1 Alarm Severity Level

To set the alarm severity level for a T3 alarm, complete the following steps:
port:channel>, and press ENTER to access the T1 Configuration prompt.
3. From the T1 Configuration prompt, type alarm level <alarm_name>
<alarm_level>, and press ENTER to set the alarm severity level. Refer to Table H‐4 for
valid alarm_name and alarm_level values.
Table H‐4 displays the T3 Parameter Values.
Table H-4. T1 Parameter Values
alarm_name alarm_level
LOF Critical
RAI Major
AIS Minor
Alert
Information
4. From the T1 Configuration prompt, provision the alarm status by performing one of the
following commands:
• Type no alarm enable <alarm_name>, and press ENTER to disable the specified
alarm
• Type alarm enable <alarm_name>, and press ENTER to enable the specified alarm
5. From the T1 Configuration prompt, type end, and press ENTER to return to the Enable
prompt.
65K510DEP08-1A H-3
H-4 65K510DEP08-1A
Appendix I
5.1 Provisioning Defaults

This appendix details the provisioning defaults for the Total Access 5000 and NetVanta 800.
In this Appendix
Table I-1. Appendix I Topics
Topic See Page
Total Access 5000 Provisioning Defaults I‐2
NetVanta 80/8000 Provisioning Defaults I‐21
65K510DEP08-1A I-1
Total Access 5000 Provisioning Defaults

To view the current provisioning settings, complete the following steps:
1. From the Total Access 5000 Root prompt, type enable to access the Enable prompt, and
press ENTER.
2. From the Enable prompt, type show run config to display the list of current
provisioning settings, and press ENTER.
3. Refer to the tables below to view the factory provisioning defaults.
Table I-2. Authentication, Authorization, and Accounting (AAA) Defaults
Provisioning Option Default Setting
aaa accounting commands 1 default none None
aaa accounting commands 15 default none None
aaa accounting exec None
aaa accounting update periodic 5
aaa authentication eep Enabled
aaa authentication login Local
aaa authorization commands 1 default none None
aaa authorization commands 15 default none None
aaa authorization config‐command Disabled
aaa authorization exec None
auto‐provisioning controller Enabled
auto‐provisioning module Enabled
Table I-3. Auto-Upgrade Defaults
alarm enable complete Disabled
alarm enable failed Enabled
alarm enable file bad Enabled
alarm enable file changed Disabled
alarm enable software‐version‐error Enabled
alarm enable started Disabled
alarm enable unknown‐module Enabled
alarm level software‐version‐error Minor
mode Manual
refresh‐interval 0
I-2 65K510DEP08-1A
Appendix I, 5.1 Provisioning Defaults - Total Access 5000 Provisioning Defaults
Table I-3. Auto-Upgrade Defaults (Continued)
release None
retries 0
scr Disabled
Table I-4. SCA Defaults
autosave Disabled
max‐instances 1
permit‐restore controller Disabled
permit‐restore controller network general Disabled
permit‐restore controller network interface Disabled
permit‐restore controller sca Disabled
permit‐restore controller security Disabled
permit‐restore controller snmp Disabled
permit‐restore modules empty‐slots Disabled
permit‐restore modules in‐service Disabled
prefix “ “
retries 5
schedule Disabled
suffix “.sca”
update‐only Enabled
permit‐restore modules Disabled
radius‐server auth‐port 1812
radius‐server retransmit 3
radius‐server timeout 1
tacacs‐server port 49
tacacs‐server timeout 1
65K510DEP08-1A I-3
Table I-5. Security Defaults
account‐expiration Disabled
advisory‐warning message Disabled
alarm enable account‐expiration Enabled
alarm enable lock‐out Enabled
alarm enable login console Enabled
alarm level login console Info
case‐sensitive Enabled
lock‐out indefinite Disabled
multiple‐logins Enabled
advisory‐warning tl1 Disabled
lock‐out duration 1
lock‐out failures 5
notification 7
user‐lock‐out Disabled
password complexity Disabled
password digit Enabled
password expiration Disabled
password length 8
password lowercase Enabled
password no‐digit‐start‐end Disabled
password not‐last Disabled
password special Enabled
password uppercase Enabled
snmp‐access Disabled
Table I-6. System Privilege Defaults
ADMIN
account‐expiration 90
password‐expiration 60
CONFIG
I-4 65K510DEP08-1A
Table I-6. System Privilege Defaults (Continued)
READ‐ONLY
READ‐WRITE
TEST
Table I-7. Username Defaults
ADMIN
account‐expiration Enable
disable Enabled
lock‐out Disabled
password‐expiration Enable
privilege Admin
READONLY
disable Enabled
lock‐out Disabled
privilege Read‐Only
READWRITE
65K510DEP08-1A I-5
Table I-7. Username Defaults (Continued)
disable Enabled
lock‐out Disabled
privilege Read‐Write
TEST
disable Enabled
lock‐out Disabled
privilege Test
Table I-8. Ethernet CFM Defaults
ethernet cfm Disabled
ethernet cfm traceroute cache hold‐time 100
ethernet cfm traceroute cache size 100
ethernet s‐tag‐tpid 8100
Table I-9. Node Number and Network Name Defaults
node‐number 0
network‐name Total Access 5000 Network
Table I-10. Fan Defaults
alarm enable single‐fan Enabled
alarm enable multiple‐fan Enabled
speed Max
I-6 65K510DEP08-1A
Table I-11. Ethernet Interface Defaults
ip address 10.100.1.32
subnet mask 255.255.255.0
shutdown Enabled ‐ In Service
Table I-12. Gigabit-Ethernet Interface Defaults
description “ “
speed Auto
lacp mode Disabled
lacp grammar standby‐aggregation Disabled
downlink Disabled
alarm enable link‐down Enabled
subtended‐host mode Disabled
subtended‐host snmp‐server chassis‐id “ “
subtended‐host snmp‐server community read‐only Public
subtended‐host snmp‐server community read‐write Private
subtended‐host ip file‐server default host 0.0.0.0
subtended‐host ip address 0.0.0.0 0.0.0.0
subtended‐host ip default‐gateway 0.0.0.0
subtended‐host s‐tag 4096
subtended‐host s‐tag‐priority 7
alarm enable unknown‐pluggable Enabled
alarm enable pluggable‐fault Enabled
alarm enable heartbeat‐loss Enabled
alarm enable lacp‐timeout Enabled
alarm enable port‐mode Enabled
alarm enable downstream‐fault Enabled
alarm enable upstream‐node Enabled
65K510DEP08-1A I-7
Table I-13. SDHSL Interface Defaults
description “ “
thresholds es 15‐minute 0
thresholds ses 15‐minute 0
thresholds uas 15‐minute 0
thresholds cvc 15‐minute 0
thresholds losws 15‐minute 0
thresholds es 24‐hour 0
thresholds ses 24‐hour 0
thresholds uas 24‐hour 0
thresholds cvc 24‐hour 0
thresholds losws 24‐hour 0
thresholds snr‐margin 0
thresholds loop‐attenuation 0
annex A or B
linerate Mode ‐ Adaptive;
Minimum Rate ‐ 3;
Maximum Rate ‐ 89;
Target Margin ‐ 3;
Adaptive Mode ‐ Worstcase Condition
constellation crossover‐rate 60
power‐back‐off Auto
diagnostics splice‐detect distance‐type Feet
shutdown Disabled ‐ Out of Service Unassigned
Table I-14. T1 Interface Defaults
description “ “
framing ESF
thresholds es‐p 15‐minute 0
thresholds ses‐p 15‐minute 0
thresholds uas‐p 15‐minute 0
thresholds cv‐p 15‐minute 0
thresholds es‐p 24‐hour 0
I-8 65K510DEP08-1A
Table I-14. T1 Interface Defaults (Continued)
thresholds ses‐p 24‐hour 0
thresholds uas‐p 24‐hour 0
thresholds cv‐p 24‐hour 0
test timeout 1440
test timeout remaining 0
test‐pattern QRSS
test‐pattern no sync Enabled
loopback local line Enabled
remote‐loopback CSU Enabled
remote‐loopback FDL Enabled
Table I-15. T3 Interface Defaults
description “ “
framing C‐Bit
loopback local line Enabled
loopback remote Disabled
remote‐loopback Enabled
test‐pattern P223
timeout loopback 1440
thresholds es‐l 15‐minute 0
thersholds cv‐l 15‐minute 0
thresholds esp‐p 15‐minute 0
thresholds cvp‐p 15‐minute 0
thresholds sescp‐p 15‐minute 0
thresholds cvcp‐p 15‐minute 0
thresholds sas‐p 15‐minute 0
thresholds uasp‐p 15‐minute 0
thresholds es‐l 24‐hour 0
thersholds cv‐l 24‐hour 0
thresholds esp‐p 24‐hour 0
65K510DEP08-1A I-9
Table I-15. T3 Interface Defaults (Continued)
thresholds cvp‐p 24‐hour 0
thresholds sescp‐p 24‐hour 0
thresholds cvcp‐p 24‐hour 0
thresholds sas‐p 24‐hour 0
thresholds uasp‐p 24‐hour 0
alarm enable los Enabled
alarm enable lof Enabled
alarm enable rai Enabled
alarm enable ais Enabled
alarm trap los Enabled
alarm trap lof Enabled
alarm trap rai Enabled
alarm trap ais Enabled
alarm level los Major
alarm level lof Major
alarm level rai Minor
alarm level ais Major
Table I-16. EFM Group Defaults
alias “EFM BRIDGE slot/#”
active‐links‐minimum 1
rate‐control Enabled
rate‐control upstream X downstream X 0 0
loopback remote Disabled
loopback timeout 0
thresholds xcv 1e‐7
xcv‐link‐removal Enabled
thresholds bad‐fragments 15‐minute 0
thresholds lost‐fragments 15‐minute 0
thresholds lost‐starts 15‐minute 0
thresholds lost‐ends 15‐minute 0
I-10 65K510DEP08-1A
Table I-16. EFM Group Defaults (Continued)
thresholds bad‐fragments 24‐hour 0
thresholds lost‐fragments 24‐hour 0
thresholds lost‐starts 24‐hour 0
thresholds lost‐ends 24‐hour 0
subtended‐host ip address 0.0.0.0.0.0.0.0
subtended‐host snmp‐server community read‐only “public”
subtended‐host snmp‐server community read‐ “private”
write
Table I-17. EFM Link Defaults
thresholds errored‐fragments 15‐minute 0
thresholds small‐fragments 15‐minute 0
thresholds large‐fragments 15‐minute 0
thresholds discarded‐fragments 15‐minute 0
thresholds fcs‐errors 15‐minute 0
thresholds coding‐errors 15‐minute 0
thresholds errored‐fragments 24‐hour 0
thresholds small‐fragments 24‐hour 0
thresholds large‐fragments 24‐hour 0
thresholds discarded‐fragments 24‐hour 0
thresholds fcs‐errors 24‐hour 0
thresholds coding‐errors 24‐hour 0
65K510DEP08-1A I-11
Table I-18. System Management EVC Defaults
s‐tag 3002
men‐pri 7
ip address 10.100.11.138
Table I-19. Redundancy Defaults
wait‐to‐restore Disabled
revertive Disabled
alarm enable protection‐unavailable Enabled
alarm enable switch‐to‐protect Enabled
alarm enable card‐active Enabled
alarm‐enable peer‐version Enabled
alarm‐enable database‐sync Enabled
alarm enable peer‐mirror Enabled
Table I-20. QOS COS-Map Defaults
qos cos‐map 0 0 1
qos cos‐map 1 2 3
qos cos‐map 2 4 5
qos cos‐map 3 6 7
Table I-21. Queue EFM Group Defaults
max‐depth 31
cos Queue Number
I-12 65K510DEP08-1A
Table I-22. System Timing Defaults
alarm enable source primary‐failed Enabled
alarm enable source secondary‐failed Enabled
revertive Enabled
source primary Internal
source secondary Internal
external primary type Bits‐D4
external primary quality Do Not Use
external primary priority 0
external secondary type Bits‐D4
external secondary quality Do Not Use
external secondary priority 0
Table I-23. Event Log Defaults
alarm enable system‐log failure Enabled
alarm enable system‐log full Disabled
mode Capacity
prefix “ ”
retries 0
schedule Every 30 days at 23:45
suffix “ “
update‐only Enabled
Table I-24. IP Defaults
ip default‐gateway 10.100.1.32
ip domain‐lookup Disabled
ip domain‐name‐list “test.adtran.com adtran.com”
ip file‐server auto‐upgrade filename “ “
ip file‐server auto‐upgrade path “ “
ip file‐server default filename “ “
ip file‐server default path “ “
65K510DEP08-1A I-13
Table I-24. IP Defaults (Continued)
ip file‐server download‐cache expire 480
ip file‐server event‐log‐export path “ “
ip file‐server general‐export path “ “
ip file‐server general‐export retries 0
ip file‐server sca filename “ “
ip forwarding Disabled
ip raw‐tl1 server 2001
ip raw‐tl1 tcp‐dead‐client Enabled
ip route 10.100.1.32 255.255.255.0 0.0.0.0
ip route (2) 10.100.11.138 255.255.255.0 0.0.0.0
ip sntp server Disabled;
IP Address ‐ 0.0.0.0
ip ssh key size 1024
ip ssh server 2009
ip ssh tunnels Enabled
ip ssh‐tl1 server 2006
ip ssh‐tl1‐secondary server 2007
ip syslog Disabled
ip telnet dead‐client Disabled
ip telnet server 2008
ip telnet‐secondary server 2002
ip telnet‐tl1 server 2000
ip terminal‐server telnet admin security Disabled
ip terminal‐server telnet admin server 2004
ip terminal‐server telnet network security Disabled
ip terminal‐server telnet network server 2003
line‐timeout 30
clock dst‐auto‐adjust Disabled
ip file‐server default protocol TFTP
snmp‐server alarm enable authenticate‐failure Enabled
I-14 65K510DEP08-1A
Table I-25. Power Shedding Defaults
activation‐delay 5
alarm External‐input 1
deactivation‐delay 1
scr mode Auto
scr schedule Disabled
snmp‐server alarm enable Authenticate‐failure
snmp‐server chassis‐id ʺTA5000ʺ
snmp‐server community read‐only ʺPublicʺ
snmp‐server community read‐write ʺPrivateʺ
snmp‐server contact ʺwww.adtran.comʺ
snmp‐server enable traps Enabled
snmp‐server location ʺSysLocation not setʺ
snmp‐server non‐vol‐card‐status Disabled
alarm enable ring‐generator Enabled
alarm enable downstream‐node Enabled
alarm enable bandwidth‐unavailable Enabled
alarm enable internal‐system‐s‐tag Enabled
alarm enable node‐number Enabled
alarm enable duplicate‐node‐number Enabled
alarm enable power‐limit Enabled
alarm enable duplicate‐scm‐ip Enabled
Table I-26. System Alarm Defaults
alarm aid external‐input 1 1
65K510DEP08-1A I-15
Table I-26. System Alarm Defaults (Continued)
alarm aid power‐fail ac 19
alarm aid power‐fail dc a 17
alarm aid power‐fail dc b 18
alarm condition‐code external‐input 1 ʺEXT‐IN‐1ʺ
alarm condition‐code power‐fail ac ʺPOWERʺ
alarm condition‐code power‐fail dc a ʺPWRA‐1ʺ
alarm condition‐code power‐fail dc b ʺPWRB‐1ʺ
alarm description external‐input 1 ʺExt Alm Input 1ʺ
I-16 65K510DEP08-1A
alarm description power‐fail ac ʺAC Power Failʺ
alarm enable external‐input 1 Enabled
65K510DEP08-1A I-17
alarm enable module comm‐failure Enabled
alarm enable module removed Enabled
alarm enable module restart Enabled
alarm enable power‐fail dc a Enabled
alarm enable power‐fail dc b Enabled
alarm enable service‐state get‐fail Enabled
alarm enable service‐state set‐fail Enabled
alarm enable test audible‐relay critical Enabled
alarm enable test audible‐relay major Enabled
alarm enable test audible‐relay minor Enabled
alarm enable test visual‐relay critical Enabled
alarm enable test visual‐relay major Enabled
alarm enable test visual‐relay minor Enabled
alarm level external‐input 1 Minor
alarm level module removed Major
alarm level power‐fail ac Major
I-18 65K510DEP08-1A
alarm level power‐fail dc a Major
alarm level power‐fail dc b Major
chronology Ascending
Table I-27. TL1 Defaults
equipment‐id 0
chassis‐id‐tid‐sync Enabled
echo Disabled
log‐max 25
tid “TA5000”
Table I-28. SNMP Host Parameters Defaults
mode Under Creation
retry‐limit 0
timeout 3
version 2c
Table I-29. Ethernet CFM Default-Domains
mip‐level‐default 0
mip‐allowed‐default None
mip‐sender‐id‐default None
level Defer
mip‐allowed Defer
mip‐sender‐id Defer
65K510DEP08-1A I-19
Table I-30. Line Admin 0 Defaults
dcd Disabled
dtr Disabled
flow‐control Disabled
mode Menus
speed 9600
Table I-31. Line Console 0 Defaults
dtr Disabled
speed 9600
Table I-32. Line Network 0 Defaults
mode Menus
speed 9600
I-20 65K510DEP08-1A
Appendix I, 5.1 Provisioning Defaults - NetVanta 80/8000 Provisioning Defaults
NetVanta 80/8000 Provisioning Defaults

To view the current provisioning settings for System Release 5.1, complete the following steps:
1. From the NetVanta 838 Root prompt, type enable to access the Enable prompt, and
press ENTER.
2. From the Enable prompt, type show run config to display the list of current
provisioning settings, and press ENTER.
3. Refer to the tables below to view the factory provisioning defaults.
Table I-33. Operational Modes Defaults
Provisioning Option Default Settings
shdsl mode NTU
ds3 mode NTU
ip default‐gateway 0.0.0.0
ip file‐server default host 0.0.0.0
ip file‐server default filename “ “
line timeout 15
clock timezone Name ‐ “ “;
Hours Offset ‐ 0:
Minutes Offset ‐ 0
Table I-34. AAA Defaults
aaa authentication login default Local
aaa authentication eep Enabled
aaa authorization commands 1 default None
aaa authorization commands 15 default None
aaa authorization config‐command Enabled
aaa authorization exec default None
aaa accounting commands 1 default None
aaa accounting commands 15 default None
aaa accounting exec default None
aaa accounting update periodic 5
Table I-35. SHDSL Timeout Training Default
shdsl timeout training 60
65K510DEP08-1A I-21
Table I-36. TACACS+ Defaults
tacacs‐server port 49
tacacs‐server timeout 5
Table I-37. RADIUS Defaults
radius‐server default‐privilege Admin
radius‐server auth‐port 1812
radius‐server timeout 5
radius‐server retransmit 3
Table I-38. Security Defaults
alarm enable login success Enabled
alarm level login success Info
alarm enable login failure Enabled
alarm level login failure Info
Table I-39. Username Defaults
Username ‐ ADMIN
password ʺPASSWORDʺ
privilege Admin
disable Enabled
Username ‐ READONLY
privilege Read‐only
disable Enabled
I-22 65K510DEP08-1A
Table I-39. Username Defaults (Continued)
Username ‐ READWRITE
privilege Read‐write
disable Enabled
Username ‐ TEST
privilege Test
disable Enabled
Table I-40. Ethernet CFM Defaults
ethernet s‐tag‐tpid 8100
ethernet cfm Disabled
ethernet cfm traceroute chache hold‐time 100
ethernet cfm traceroute chache size 100
Table I-41. Probe Responder TWAMP Defaults
control source‐port 862
control timeout 900
test timeout 900
max‐sessions 6
shutdown Disabled
Table I-42. Queue Time-Constant Default
queue time‐constant wred 16
65K510DEP08-1A I-23
Table I-43. QOS COS-Map Defaults
qos cos‐map 0 1
qos cos‐map 1 0
qos cos‐map 2 2
qos cos‐map 3 3
qos cos‐map 4 4
qos cos‐map 5 5
qos cos‐map 6 6
qos cos‐map 7 7
qos untagged 0
Table I-44. Temperature-Sensor Defaults
thresholds over‐temperature celsius 65
thresholds over‐temperature fahrenheit 149
Table I-45. SHDSL Interface Defaults
description “SHDSL Port #”
annex A or B
linerate Mode ‐ Fixed;
Minimum Rate ‐ 3;
Maximum Rate ‐ 89
power‐back‐off Auto
diagnostics splice‐detect distance‐type Feet
thresholds snr‐margin 0
thresholds loop‐attenuation 0
thresholds es 15‐minute 0
thresholds ses 15‐minute 0
thresholds uas 15‐minute 0
thresholds cvc 15‐minute 0
thresholds losws 15‐minute 0
thresholds es 24‐hour 0
I-24 65K510DEP08-1A
Table I-45. SHDSL Interface Defaults (Continued)
thresholds ses 24‐hour 0
thresholds uas 24‐hour 0
thresholds cvc 24‐hour 0
thresholds losws 24‐hour 0
description “ “
speed auto
thresholds errors 15‐minute 0
thresholds runts 15‐minute 0
thresholds giants 15‐minute 0
thresholds discards 15‐minute 0
thresholds multicasts 15‐minute 0
thresholds broadcasts 15‐minute 0
thresholds errors 24‐hour 0
thresholds runts 24‐hour 0
thresholds giants 24‐hour 0
thresholds discards 24‐hour 0
thresholds multicasts 24‐hour 0
thresholds broadcasts 24‐hour 0
subtended‐host mode Disabled
subtended‐host snmp‐server community read‐only Public
subtended‐host snmp‐server community read‐write Private
subtended‐host ip address 0.0.0.0 0.0.0.0
65K510DEP08-1A I-25
Table I-47. EFM Group Defaults
description “Bonding Group #”
xcv‐link‐removal Enabled
thresholds xcv 1e‐7
thresholds bad‐fragments 15‐minute 0
thresholds lost‐fragments 15‐minute 0
thresholds lost‐starts 15‐minute 0
thresholds lost‐ends 15‐minute 0
thresholds bad‐fragments 24‐hour 0
thresholds lost‐fragments 24‐hour 0
thresholds lost‐starts 24‐hour 0
thresholds lost‐ends 24‐hour 0
Table I-48. EFM Link Defaults
thresholds errored‐fragments 15‐minute 0
thresholds small‐fragments 15‐minute 0
thresholds large‐fragments 15‐minute 0
thresholds discarded‐fragments 15‐minute 0
thresholds fcs‐errors 15‐minute 0
thresholds coding‐errors 15‐minute 0
thresholds errored‐fragments 24‐hour 0
thresholds small‐fragments 24‐hour 0
thresholds large‐fragments 24‐hour 0
thresholds discarded‐fragments 24‐hour 0
thresholds fcs‐errors 24‐hour 0
thresholds coding‐errors 24‐hour 0
Table I-49. Ethernet Interface Defaults
crossover Auto
speed Auto
I-26 65K510DEP08-1A
Table I-49. Ethernet Interface Defaults (Continued)
link‐state‐awareness Disabled
description “Eth Port #”
thresholds collisions 15‐minute 0
thresholds invalid‐vlan 15‐minute 0
thresholds peak‐mac‐entries 15‐minute 0
thresholds collisions 24‐hour 0
thresholds invalid‐vlan 24‐hour 0
thresholds peak‐mac‐entries 24‐hour 0
mac limit Disabled
mac aging‐time 300
link‐state‐awareness Disabled
description “GigEth Port #”
speed 1000
65K510DEP08-1A I-27
Table I-50. Gigabit-Ethernet Interface Defaults (Continued)
thresholds invalid‐vlan 15‐minute 0
thresholds peak‐mac‐entries 15‐minute 0
thresholds invalid‐vlan 24‐hour 0
thresholds peak‐mac‐entries 24‐hour 0
mac limit Disabled
mac aging‐time 300
Table I-51. Queue Ethernet Interface Defaults
max‐depth 255
algorithm Disabled
drop‐probability green 10
drop‐probability yellow 10
thresholds wred green maximum 25
thresholds wred green minimum 15
thresholds wred yellow maximum 15
thresholds wred yellow minimum 5
weight Dynamic
cos Queue Number
I-28 65K510DEP08-1A
Table I-52. Queue EFM Group Defaults
max depth 255
algorithm Disabled
drop‐probability green 10
drop‐probability yellow 10
thresholds wred green maximum 25
thresholds wred green minimum 15
thresholds wred yellow maximum 15
thresholds wred yellow minimum 6
weight Dynamic
cos Queue Number
Table I-53. System Management EVC Defaults
s‐tag 1
connect men‐port efm‐group 1/0/1
ip address 0.0.0.0
men‐pri 7
shutdown Enabled
Table I-54. Counter Profile Defaults
vlan Disabled
pbit Disabled
color Disabled
Table I-55. System Alarm Defaults
alarm enable power‐fail dc a Enabled
alarm level power‐fail dc a Minor
alarm enable power‐fail dc b Enabled
65K510DEP08-1A I-29
alarm level power‐fail dc b Minor
alarm enable power‐fail ac Enabled
alarm level power‐fail ac Critical
Table I-56. SNMP Defaults
snmp‐server community read‐write “Private”
snmp‐server community read‐only “Public”
snmp‐server contact “www.adtran.com”
snmp‐server chassis‐id “NetVanta838”
snmp‐server location “NotSet”
snmp‐server enable traps Disabled
Table I-57. Line Console Default
baud Auto
I-30 65K510DEP08-1A
Appendix J
GigE Star Provisioning

This appendix details the steps to provision the Total Access 5000 network in a GigE Star
configuration.
In this Appendix
Table J-1. Appendix J Topics
Topic See Page
Central Office Terminal (COT) Provisioning J‐2
Remote Terminal (RT) Provisioning J‐10
65K510DEP08-1A J-1
Central Office Terminal (COT) Provisioning

To provision the COT Node, complete the following:
• Provision the GE 4‐Port Line Module
For more information, refer to “Provision the GE 4‐Port Line Module” on page J‐2.
• Provision the DS3 Unchanelized EFM 4‐Port Line Module
For more information, refer to “Provision the DS3 Unchannelized EFM 4‐Port Line
Module” on page J‐4.
• Provision the T1 8‐Port Line Module
For more information, refer to “Provision the T1 8‐Port Line Module” on page J‐6.

• Provision the GE 4‐Port Line Module Service State
• Provision the Network Ports
• Provision the Ethernet Star
• Provision for Redundancy
Provision the GE 4-Port Line Module Administration Status

Table J‐2 displays the three administration states and shows the equivalent Service State from
prior releases.
Table J-2. GE 4-Port Line Module Administration States



generated.

To set the module administration state, complete the following:
1. From the Total Access 5000 Main menu, select System CLI, and press ENTER.
2. From the CLI menu, select CLI Command Entry, and press ENTER.
The following response id displayed:
Use EXIT to exit CLI session.
3. Select Y to enter the CLI command interface.
4. Log in again using the default ADMIN and PASSWORD options. The CLI prompt is
displayed.
J-2 65K510DEP08-1A
Appendix J, GigE Star Provisioning - Central Office Terminal (COT) Provisioning
6. From the Enable prompt, type configure terminal, and press ENTER.
Unassigned
nance

To configure the network port administration states, complete the following:
<shelf/slot/port>, and press ENTER to access the Ethernet Interface Configuration
prompt.
4. Repeat steps 2 and 3 for each port being used.
Provision the Ethernet Star

To configure the Total Access 5000 for a Gigabit Ethernet Star, complete the following:
prompt.
3. From the Ethernet Interface Configuration prompt, type downlink, and press ENTER.
The downlink command enables downstream tree networking on the selected interface.
65K510DEP08-1A J-3
Provision for Redundancy

To provision for redundancy, complete the following:
NOTE
To make the GE 4‐Port Line Module in the odd slot the active module,
provision it first.

2. From the Global Configuration prompt, type redundancy <shelf/slot>. and press
ENTER.
3. From the Redundancy Configuration prompt, type no shutdown, and press ENTER.
NOTE
Redundancy is not fully enabled until the even slot is also In Service.
4. Repeat steps 2 and 3 for the GE 4‐Port Line Module in the even slot.

• Provision the DS3 Unchannelized EFM 4‐Port Line Module
• Provision the Uplink Identifer
• Provision the Timing Source

prior releases.
Table J-3. DS3 Unchannelized EFM 4-Port Module Administration States



generated.

J-4 65K510DEP08-1A
The following response is displayed:
displayed.
Unassigned
press ENTER.
nance
Provision the Uplink Identifier

To provision the uplink identifier, complete the following:
2. From the Global Configuration prompt, type ethernet default interface efm-
group WORD, and press ENTER.
NOTE
Use the WORD input to enter a string without spaces. This input is case
sensitive.
WORD is the group name assigned when configuring the EFM group using EZ‐EFM.
65K510DEP08-1A J-5

To provision the timing source, complete the following:
2. From the Global Configuration prompt, type system-timing <shelf>, and press
ENTER.
3. From the System‐Timing Configuration prompt, type source primary loop-a
interface t3 <shelf/slot/port>, and press ENTER.
4. From the System‐Timing Configuration prompt, type source secondary loop-b
NOTE
ADTRAN recommends having the primary and secondary timing sources on
different DS3 ports and adjacent redundant slots.
Provision the T1 8-Port Line Module

• T1 8‐Port Line Module Provisioning Defaults
• Access the T1 8‐Port Line Module
• Provision the T1 8‐Port Line Module Service State
• Provision the T1 8‐Port Access Line Module DS1 Interface Service State
• Provision the Uplink Identifier
• Provision the DS1 Interface
T1 8-Port Line Module Provisioning Defaults

When the T1 8‐Port Line Module is installed in a Total Access 5000 shelf, the SCM queries the
system (local and clustered shelves) to synchronize its database. No user intervention is
required for this process. Provisioning is handled without user entry if Auto‐Provisioning is
enabled. Otherwise, provisioning must be accomplished manually through the SCM menu
system.
Table J‐4 shows the minimum list of factory defaults and values that are loaded after instal‐
lation and self‐test. These defaults and values provide the minimum configuration for turn up
of the T1 8‐Port Line Module.
J-6 65K510DEP08-1A
Table J-4. T1 8-Port Line Module Provisioning Defaults

Option Settings Default
Provisioning
Card Service State In Service; OOS‐Maintenance
Out of Service‐Unassigned;
Out of Service‐Maintenance
Card Mode
EFM/PWE3 EFM (Network Mode); EFM (Network
PWE3 (Pseudowire) Mode)
DS1 Interfaces
Service State In Service; OOS‐Unassigned
Out of Service‐Unassigned;
Out of Service‐Maintenance
Output LBO 0‐133 ft; 0‐133 ft
133‐266 ft;
266‐399 ft;
399‐533 ft;
533‐655 ft;
9 dB;
0 dB;
–7.5 dB;
–15 dB;
–22.5 dB
Line Code B8Zs; B8ZS
AMI
Line Type ESF; Unframed
D4;
Unframed
Span Voltage Disabled; Disabled
–130 VDC;
(260 VDC) ±130 VDC;
Loopback
EFM Settings
Uplink Identifier System; System
Select EFM Group
Timing
LoopA Timing None; None
DS1‐1
LoopB Timing None; None
DS1‐1
65K510DEP08-1A J-7
Access the T1 8-Port Line Module

To access the T1 8‐Port Line Module, complete the following:
1. From the Total Access 5000 Main menu, select Module Menus, and press ENTER.
2. From the Module Menus menu, select T1 8‐Port, and press ENTER.
Provision the T1 8-Port Line Module Service State

The card service state must be set to IS or OOS‐MA.
NOTE
If the card service state is set to OOS‐MA, normal operation occurs but alarms
are not reported.
To set the card service state, perform the following procedure:
1. From the T1 8‐Port Line Module menu, select Provisioning, and press ENTER.
2. From the Provisioning menu, select Card Service State, and press ENTER.
3. From the Card Service State menu, select the appropriate service state, and press ENTER.
Provision the T1 8-Port Line Module DS1 Interface Service State

For each DS1 port being used, the service state must be set to IS.
To set the DS1 port service state, perform the following procedure:
1. From the Provisioning menu, select DS1 Port Interfaces, and press ENTER.
2. From the DS1 Port Provisioning menu, select Service State, and press ENTER.
3. From the Service State menu, select the service state of the DS1 Port, and press ENTER.

To provision the T1 8‐Port timing source, complete the following:
1. From the Provisioning menu, select EFM Setting, and press ENTER.
2. From the EFM Settings menu, select Timing, and press ENTER.
3. From the Timing menu, select LoopA Timing Source, and press ENTER.
4. From the LoopA Timing Source menu, select the required option, and press Enter.
This menu contains the following options:
• Select DS1: This setting allows the entry of the DS1 timing source. The valid settings
are from 1–8.
• None: When selected, this option does not set the timing source to the DS1. Timing
defaults to the timing set in the GigE SM.
5. From the Timing menu, select LoopB Timing Source, and press ENTER.
6. From the LoopB Timing Source menu, select the required option, and press Enter.
are from 1–8.
J-8 65K510DEP08-1A

The uplink identifier settings are depdendant on the Nodes connection through the EFM card.
To set the uplink identifier for the COT, complete the following:
2. From the EFM Settings menu, select Uplink Identifier, and press ENTER.
3. From the Uplink Identifier System menu, select System, and press ENTER.
Provision the DS1 Interface

To provision the DS1 Interfaces, complete the following:
1. From the T1 8‐Port Main menu, select Provisioning, and press ENTER.
2. From the Provisioning menu, select DS1 Interfaces, and press ENTER.
3. From the DS1 Interface menu, select the required DS1, and press ENTER.
4. From the DS1 Port Provisioning menu, select Service State, and press ENTER.
5. From the Service State menu, select In Service, and press ENTER.
6. From the DS1 Port Provisioning menu, select Line Buildout, and press ENTER.
This options used for provisioning both the cable length (in feet) and the transmit pulse
shape and attenuation applied to the transmit signal. Using the 0 dB setting provides for
the longest circuit length. The valid options are:
• 0 – 133 ft
• 133 – 266 ft
• 266 – 399 ft
• 399 – 533 ft
• 533 – 655 ft
• 0 dB
• –7.5 dB
• –15 dB
• –22.5 dB
7. From the Output LBO menu, set the line buildout, and press ENTER.
9. From the EFM Setting menu, select DS1 Bonding, and press ENTER.
65K510DEP08-1A J-9
Remote Terminal (RT) Provisioning

To provision the RT, complete the following:
• Provision the GigE SM
For more information, refer to “Provision the GigE SM” on page J‐10.
• Provision the GE 4‐Port Line Module
For more information, refer to “Provision the GE 4‐Port Line Module” on page J‐11.
• Provision the DS3 Unchanelized EFM 4‐Port Line Module
For more information, refer to “Provision the DS3 Unchannelized EFM 4‐Port Line
Module” on page J‐13.
• Provision the T1 8‐Port Line Module
For more information, refer to “Provision the T1 8‐Port Line Module” on page J‐15.


To set the timing sources (primary and secondary) to BITS, complete the following:
NOTE
The primary and secondary timing sources can be different depending on the
configuration.
1. From the Switch Module menu, select Provisioning, and press ENTER.
2. From the Provisioning menu, select Timing, and press ENTER.
3. From the Timing menu, select Primary Source, and press ENTER.
The Primary Source provisions the local input for the primary clock generation.
4. From the Primary Timing Source menu, select Net 1, and press ENTER.
5. From the Timing menu, select Secondary Source, and press ENTER.
The Secondary Source provisions the local input for the secondary clock generation.
6. From the Secondary Timing Source menu, select Local, and press ENTER.
J-10 65K510DEP08-1A
Appendix J, GigE Star Provisioning - Remote Terminal (RT) Provisioning

• Provision the GE 4‐Port Line Module Service State
• Provision the Network Ports
• Provision the Ethernet Star
• Provision for Redundancy
Provision the GE 4-Port Line Module Administration Status

prior releases.
Table J-5. GE 4-Port Line Module Administration States



generated.

displayed.
6. From the Enable prompt, type configure terminal, and press ENTER.
Unassigned
65K510DEP08-1A J-11
• Type shutdown maintenance, and press ENTER to take a port Out of Service,
Unassigned

To configure the network port administration states, complete the following:
prompt.
4. Repeat steps 2 and 3 for each port being used.
Provision the Ethernet Star

To configure the Total Access 5000 for a Gigabit Ethernet Star, complete the following:
prompt.
3. From the Ethernet Interface Configuration prompt, type downlink, and press ENTER.
The downlink command enables downstream tree networking on the selected interface.
Provision for Redundancy

To provision for redundancy, complete the following:
NOTE
To make the GE 4‐Port Line Module in the odd slot as the active module,
provision it first.
2. From the Global Configuration prompt, type redundancy <shelf/slot>. and press
ENTER.
3. From the Redundancy Configuration prompt, type no shutdown, and press ENTER.
NOTE
Redundancy is not fully enabled until the even slot is also In Service.
J-12 65K510DEP08-1A
4. Repeat steps 2 and 3 for the GE 4‐Port Line Module in the even slot.

• Provision the DS3 Unchannelized EFM 4‐Port Line Module
• Provision the Uplink Identifer

prior releases.
Table J-6. DS3 Unchannelized EFM 4-Port Module Administration States



generated.

displayed.
6. From the Enable prompt, type configure terminal, and press ENTER. to access the
65K510DEP08-1A J-13
Unassigned
press ENTER.
nance

To provision the uplink identifier, complete the following:
2. From the Global Configuration prompt, type ethernet default interface efm-
group WORD, and press ENTER.
NOTE
Use the WORD input to enter a string without spaces. This input is case
sensitive.
WORD is the group name assigned when configuring the EFM group using EZ‐EFM.

To provision the timing source, complete the following:
2. From the Global Configuration prompt, type system-timing <shelf>, and press
ENTER.
3. From the System‐Timing Configuration prompt, type source primary loop-a
4. From the System‐Timing Configuration prompt, type source secondary loop-b
NOTE
ADTRAN recommends having the primary and secondary timing sources be
on different DS3 ports and adjacent redundant slots.
J-14 65K510DEP08-1A
Provision the T1 8-Port Line Module

• Provision the Uplink Identifier

To provision the T1 8‐Port timing source, complete the following:
2. From the EFM Settings menu, select Timing, and press ENTER.
3. From the Timing menu, select LoopA Timing Source, and press ENTER.
4. From the LoopA Timing Source menu, select the required option, and press Enter.
are from 1–8.
5. From the Timing menu, select LoopB Timing Source, and press ENTER.
6. From the LoopB Timing Source menu, select the required option, and press Enter.
are from 1–8.

The uplink identifier settings depend on if the Nodes are being connected by way of the EFM
card.
To set the uplink identifier for RT Node, complete the following:
2. From the EFM Setting menu, select Uplink Identifier, and press ENTER.
3. From the Uplink Identifier System menu, select Select EFM Group, and press ENTER.
4. From the Select EFM Group menu, enter the selected EFM group, and press ENTER.
65K510DEP08-1A J-15
J-16 65K510DEP08-1A
Appendix K
GigE Linear Chain Provisioning

This appendix details the steps to provision the Total Access 5000 network in a GigE Linear
Chain configuration.
In this Appendix
Table K-1. Appendix K Topics
Topic See Page
Central Office Terminal (COT) Provisioning K‐2
Remote Terminal (RT) Provisioning K‐2
65K510DEP08-1A K-1
Central Office Terminal (COT) Provisioning

Provisioning the COT Node consists of setting the network ports on the COT GigE SM.
To set the network ports, complete the following:
2. From the Provisioning menu, select Network Ports, and press ENTER.
3. From the Network Port 1 Provisioning menu, select Service State, and press ENTER.
This option enables provisioning of the service state of Net 1.
4. From the Network Port 1 Operation State menu, select In Service, and press ENTER.
5. Press N to move to the Network Port 2 Provisioning menu.
8. From the Network Port 2 Provisioning menu, select Port Mode, and press ENTER.
9. From the Port Mode menu, select Downlink, and press ENTER.

Provisioning the RT Node consists of setting the network ports on the RT GigE SM.
To set the network ports, complete the following:
2. From the Provisioning menu, select Network Ports, and press ENTER.
5. Press N to move to the Network Port 2 Provisioning menu.
8. From the Network Port 2 Provisioning menu, select Port Mode, and press ENTER.
9. From the Port Mode menu, select Downlink, and press ENTER.
K-2 65K510DEP08-1A
Appendix L
RPR Provisioning

This appendix details the steps to provision the Total Access 5000 network in a Resilient
Packet Ring (RPR) configuration.
In this Appendix
Table L-1. Appendix L Topics
Topic See Page
Basic RPR Rules L‐1
Ethernet Ring Diagrams L‐2
Central Office Terminal (COT) Node Provisioning L‐3
Remote Terminal (RT) Provisioning L‐8
Basic RPR Rules

When provisioning RPR, the following rules must apply:
• RPR Rings can originate from the COT Node or a RT Node. If the Ring originates at an RT
node, then that RPR card must be configured as a Hub
• Ring Speed is 2.5G with Add/Drop of 1G per span
• The same VLAN cannot be configured on Multiple nodes within a Ring. If done, the
Active RPR Line Module raises a VLAN Mis Config alarm on the COT Node
• Ensure the S‐tag TPID in the Switch Module is set to 0x8100
• RPR is supported with a pair of cards in adjacent slots (odd/even pairs). Each card
provides one of the Node’s links on the ring
65K510DEP08-1A L-1
Ethernet Ring Diagrams

The following diagrams display two different RPR configurations.
Figure L‐1 displays an RPR ring. The COT Node acts as the Hub Node for the RPR ring.
COT
RT RT
RPR
RT
Figure L-1. RPR Ring
Figure L‐2 displays two RPR rings. The COT Node acts as the Hub Node for the RPR ring, and
one RT Node also acts as the Hub Node for the second RPR ring.
COT
RT RT
RPR
RT
RT RT
RPR
Figure L-2. Two RPR Rings
L-2 65K510DEP08-1A
Appendix L, RPR Provisioning - Central Office Terminal (COT) Node Provisioning
Central Office Terminal (COT) Node Provisioning

The COT Node is provisioned by setting the provisioning on the RPR Line Module.
NOTE
The GigE SM in the COT Node requires no provisioning for the timing source
or the Hop Count.
Provision the RPR Line Module

• RPR Line Module Provisioning Defaults
• Access the RPR Line Module
• Provision the RPR Line Module Service State
• Provision the Hub/Spoke
• Provision the Timing
• Provision IGMP Multicast VLAN
RPR Line Module Provisioning Defaults

When the RPR Line Module is installed in a Total Access 5000 shelf, the SCM queries the
system (local and clustered shelves) to synchronize its database. No user intervention is
required for this process. Provisioning is handled without user entry if Auto‐Provisioning is
enabled. Otherwise, provisioning must be accomplished manually through the SCM menu
system.
Table L‐2 shows the minimum list of factory defaults and values that are loaded after instal‐
lation and self‐test. These defaults and values provide the minimum configuration for turn up
of the RPR Line Module.
Table L-2. Default Provisioning Options

Provisioning Option Available Options Default Setting
Card Service State
Card Service State IS (In Service); OOS‐MA

OOS‐UAS (Out of Service ‐ Unas‐
signed);
OOS‐MA (Out of Service ‐ Mainte‐
nance)
Redundancy
Revertive Revertive; Non Revertive (dis‐

Non Revertive able)
Revertive Timeout 15–65535 seconds 15 s
RPR Provisioning
Keepalive Timeout (ms) 2–200 milliseconds 5 ms
65K510DEP08-1A L-3
Table L-2. Default Provisioning Options (Continued)

Provisioning Option Available Options Default Setting
Wait to Restore Time (s) 0–1140 seconds 10 s
Protection Holdoff Time (ms) 0–500 milliseconds 0 s
Protection Command Force Switch; Idle

Manual Switch;
Idle
Fairness Weight 1; 1
2;
4;
8;
16;
32;
64;
128
Allow Any SFP
Allow Any SFP Yes; No
No
System Timing
Timing None; None

Set Timing to Loop A;
Set Timing to Loop B
Multicast VLAN Provisioning
Multicast VLAN Value 1–4094 0
Multicast VLAN Enable Yes; No
No
Hub/Spoke Mode
Hub/Spoke Mode Hub; Hub

Spoke
Access the RPR Line Module

To access the RPR Line Module, complete the following:
1. From the Total Access 5000 Main menu, select Module Menus, and press ENTER.
2. From the Module Menus menu, select RPR LM, and press ENTER.
Figure L‐3 displays the RPR Line Module Main menu.
L-4 65K510DEP08-1A
TID: HSV00001 Total Access 5000 System MM/DD/YY HH:MM

Unacknowledged Alarms: None Unit Number: 1
RPR Line Module: Active
1. Configuration
2. Provisioning
3. Status
4. Test
5. Alarms
6. Performance Monitoring
7. Event Log
Selection :
'?' - System Help Screen
Figure L-3. RPR Line Module Main Menu
Provision the RPR Line Module Service State

The card service state must be set to IS.
NOTE
The RPR Line Modules work in a Master/Slave relationship. The active
(Master) must be IS, and the standby (Slave) must in the IS, Standby‐Hot (IS,
S‐H) state. If the modules are Out‐of‐Service, the span should be down and
the card should not participate in any redundancy or ring operation, nor
should it participate in database mirroring.
1. From the RPR Line Module menu, select Provisioning, and press ENTER.
Figure L‐4 displays the RPR Line Module Provisioning menu.
65K510DEP08-1A L-5
TID: HSV00001 Total Access 5000 System MM/DD/YY HH:MM

Unacknowledged Alarms: None Unit Number: 1
RPR LM Provisioning
1. Card Service State : In Service

2. Redundancy
3. RPR Provisioning
4. Allow Any SFP : no
5. Timing : Loop A / Loop B
6. Software Update
7. Restore Factory Defaults
8. Multicast VLAN : Disabled
9. Hub/Spoke Mode : Hub/Spoke
Selection :
Figure L-4. RPR Line Module Provisioning Menu
2. From the Provisioning menu, select Card Service State, and press ENTER.

3. From the Card Service State menu, select the appropriate service state, and press ENTER.
Provision the Hub/Spoke

Rings originating at a COT Node require no provisioning.
NOTE
• If an RPR ring originates at a Remote Terminal, then the Hub/Spoke Mode
must be set to Hub on the originating Node.
• The COT Node automatically sets to Hub Mode.
To provision the Hub/Spoke, complete the following:
2. From the Provisioning menu, select Hub/Spoke Mode, and press ENTER.
3. From the Hub/Spoke menu, select the required option, and press ENTER.
L-6 65K510DEP08-1A
Provision the Timing

The RPR Line Module in the COT receives timing from the GigE SM and automatically
transmits timing onto the ring.
Provision the IGMP Multicast VLAN
NOTE
If enabled, the RPR Line Module on the Hub Node must enable the Multicast
VLAN.
The Multicast VLAN, disabled by default, is configured on the COT Node RPR Line Module.
When an IGMP VLAN is enabled and configured on the GigE SM, the Multicast VLAN must
be enabled on the RPR Line Module. The IGMP VLAN must be enabled and configured on the
GigE SM of the COT as well as the RT Nodes. If disabled on the RPR Line Module, the
Multicast downstream traffic will not work as the RPR Line Module by default does not flood
the traffic.
To provision IGMP Multicast VLAN, complete the following:
2. From the Provisioning menu, select Multicast VLAN, and press ENTER.
3. From the Multicast VLAN, select the required setting, and press ENTER.
65K510DEP08-1A L-7

To deploy multiple nodes, complete the following:
• Provision the GigE SM
For more information, refer to “Provision the GigE SM” on page L‐8.
• Provision the RPR Line Module
For more information, refer to “Provision the RPR Line Module” on page L‐9.

• Provision the Hop Count

Primary and secondary sources must be configured to receive timing from LoopA and LoopB
where LoopA is the lower numbered (odd or West) RPR Line Module and LoopB is the higher
numbered (even or East) RPR Line Module. To set the timing, complete the following:
3. From the Timing menu, select Primary Source, and press ENTER.
The Primary Source provisions the local input for the primary clock generation.
4. From the Primary Timing Source menu, select Source, and press ENTER.
5. From the Source menu, select LoopA, and press ENTER.
6. From the LoopA menu, select the appropriate slot, and press ENTER.
7. From the Timing menu, select Secondary Source, and press ENTER.
The Secondary Source provisions the local input for the secondary clock generation.
8. From the Secondary Timing Source menu, select Source, and press ENTER.
9. From the Source menu, select LoopB, and press ENTER.
10. From the LoopB menu, select the appropriate slot, and press ENTER.
Provision the Hop Count

Hop Count must be enabled. To enable Hop Count, complete the following:
3. From the Timing menu, select Hop Count, and press ENTER.
4. From the Hop Count menu, select Enabled, and press ENTER.
L-8 65K510DEP08-1A
Appendix L, RPR Provisioning - Remote Terminal (RT) Provisioning
Provision the RPR Line Module

Once the RT GigE SM is provisioned, the following features of the RPR Line Module must be
set:
• Provision the Timing
• Provision the Hub/Spoke
• Provision IGMP Multicast VLAN
Provision the Timing

The active RPR Line Module must be provisioned with LoopA being West and LoopB being
East. To provision the RPR timing, complete the following:
3. From the Timing Configuration menu, press E.
4. From the Timing Configuration menu, select Set Timing to Loop B, and press ENTER.
5. From the Timing Configuration menu, press W.
6. From the Timing Configuration menu, select Set Timing to Loop A, and press ENTER.
Provision the Hub/Spoke

Rings originating at a COT Node require no provisioning.
NOTE
• If an RPR ring originates at a Remote Terminal, then the Hub/Spoke Mode
must be set to Hub on the originating Node.
• The COT Node automatically sets to Hub Mode.
65K510DEP08-1A L-9
Provision the IGMP Multicast VLAN
NOTE
If enabled, the RPR Line Module on the Hub Node must enable the Multicast
VLAN.
The Multicast VLAN, disabled by default, is configured on the COT Node RPR Line Module.
When an IGMP VLAN is enabled and configured on the GigE SM, the Multicast VLAN must
be enabled on the RPR Line Module. The IGMP VLAN must be enabled and configured on the
GigE SM of the COT as well as the RT Nodes. If disabled on the RPR Line Module, the
Multicast downstream traffic will not work as the RPR Line Module by default does not flood
the traffic.
To provision IGMP Multicast VLAN, complete the following:
2. From the Provisioning menu, select Multicast VLAN, and press ENTER.
3. From the Multicast VLAN, select the required setting, and press ENTER.
L-10 65K510DEP08-1A
Appendix M
Add/Remove Node from RPR Ring

This appendix details how to add and remove a node or replace fiber using Manual Switch or
Forced Switch.
In this Appendix
Table M-1. Appendix M Topics
Topic See Page
Perform a Manual or Forced Switch M‐2
Add Node to a Complete Ring M‐4
Remove a Node from a Complete Ring M‐6
65K510DEP08-1A M-1
Perform a Manual or Forced Switch

To perform a Forced or Manual Switch, complete the following:
2. From the Provisioning menu, select RPR Provisioning, and press ENTER.
Figure M‐1 displays the RPR Provisioning menu.
TID: TA5000 Total Access 5000 System MM/DD/YY hh:mm

Unacknowledged Alarms: None Node: 1
RPR Provisioning
1. Keepalive Timeout (ms) : 5

2. Wait to Restore Time (s) : 10
West East
3. Protection Holdoff Time (ms): 0 0
4. Protection Command : Idle Idle
5. Fairness Weight : 1 1
6. Reset Watermarks
Selection :

.
Figure M-1. RPR Provisioning Menu
3. From the RPR Provisioning menu, select Protection Command, and press ENTER.
Figure M‐2 displays the Current Protection menu.
M-2 65K510DEP08-1A
Appendix M, Add/Remove Node from RPR Ring - Perform a Manual or Forced Switch

Current West Protection: Idle
1. Force Switch
2. Manual Switch
3. Idle
Selection : 2
W-West E-East
Figure M-2. Current Protection Menu
4. From the Current Protection menu, press E or W to change the direction to East or West.
5. From the Current Protection menu, select the appropriate switch, and press ENTER.
The following options are available:
• Force Switch: This selection forces traffic away from the span, regardless of the ring
state
• Manual Switch: This selection forces traffic away from the span, only when the ring
is closed, with no errors
65K510DEP08-1A M-3
Add Node to a Complete Ring

NOTE
Mark the fibers before removing any fibers. Identify new fibers and mark
accordingly. Perform an OTDR to make sure the fiber span is clean and note
any TX and RX values.
Figure M‐3 assumes that a three‐node ring exists. A fourth node (D) is being added to the ring.
Total Access
5000 (Node B)
10.0.80.20
RX
RX TX
TX
Total Access
RX 5000 to be
RX TX Added (Node D)
TX 10.0.80.10
Total Access
5000 Host
(Node A) RX
10.0.80.10 RX TX
TX Total Access
5000 (Node C)
10.0.80.30
RX
TX RX
TX
West East
Figure M-3. Add/Remove Node Illustration
To add a Node to a complete ring, complete the following:
NOTE
• This process assumes that a three‐node ring exists and that a fourth node is
being added. The first node will be identified as A, the second node as B,
the third node as C, and the new node as D.
• For more information on performing a Manual or Forced Switch, refer to
“Perform a Manual or Forced Switch” on page M‐2.
1. Log on to Node C and perform a Manual Switch on the East Interface.
A Manual Switch checks if any faults exist on the ring. If any faults exist on the ring, the
Manual Switch is rejected.
Figure M‐4 displays the Current West Protection menu.
M-4 65K510DEP08-1A
Appendix M, Add/Remove Node from RPR Ring - Add Node to a Complete Ring

Current West Protection: Idle
1. Force Switch
2. Manual Switch
3. Idle
Selection : 2
W-West E-East
Figure M-4. Current West Protection Menu
Figure M‐5 displays an example of a Manual Switch.

RPR Provisioning
1. Keepalive Timeout (ms) : 5

2. Wait to Restore Time (s) : 10
West East
3. Protection Holdoff Time (ms): 0 0
4. Protection Command : Manual Switch Idle
5. Fairness Weight : 1 1
6. Reset Watermarks
Selection :
Figure M-5. Protection Command: Manual
2. Once the Manual Switch completes, go back to the Idle condition. Allow 10 seconds to
pass, and perform a Forced Switch on the East Interface.
3. Log on to Node B and perform a Forced Switch on the West Interface.
4. Disconnect the fibers between Node B and C.
65K510DEP08-1A M-5
Disconnect both RX and TX on the West Interface on Node B and both RX and TX on the
East Interface on Node C.
5. Connect fibers between Nodes B through D and Nodes D through C.
Connect the East TX of Node C to the West TX/RX of Node D. Connect the East TX of
Node C to the West RX of Node D.
Connect the West RX of Node B to the East TX of Node D. Connect the West TX of Node
B to the East RX of Node D.
6. Verify the topology sees Node D.
7. Log on to Node C and remove the Forced Switch on the East Interface.
8. Log on to Node B and remove the Forced Switch on the West Interface.
Remove a Node from a Complete Ring

NOTE
• Mark the fibers before removing any fibers. Identify new fibers and mark
accordingly. Perform an OTDR to make sure the fiber span is clean and
note any TX and RX values.
• This process assumes that a four‐node ring exists and that the fourth node
is being removed. The first node will be identified as A, the second node as
B, the third node as C, and the fourth node as D.
• For more information on performing a Manual or Forced Switch, refer to
“Perform a Manual or Forced Switch” on page M‐2.
To remove Node D from the Node Ring, complete the following:
1. Verify that No Services are configured on the rest of the Nodes to the Node that is being
removed. If any services exist, remove or delete the services.
2. Log on to Node C and perform a Manual Switch on the East Interface.
3. Perform a Forced Switch on the East Interface.
4. Log on to Node B and perform a Forced Switch on the West Interface.
5. Disconnect the fibers to both the TX and RX on the East Interface on Node C. Disconnect
the fibers to both the TX and RX on the West Interface on Node B.
6. Connect the East RX of Node C to the West TX of Node B. Connect the East TX of Node C
to the West RX of Node B.
7. Verify the topology sees a complete ring with Node C and B now being neighbors.
8. Log on to Node C and remove the Forced Switch on the East Interface.
9. Log on to Node B and remove the Forced Switch on the West Interface.
M-6 65K510DEP08-1A
Appendix N
ERPS Provisioning

This appendix details the provisioning of the Switch Module 2‐10G/2‐1 Gigabit, w/Ring
Generator to support Ethernet Ring Protection Switching.
In this Appendix
Table N-1. Appendix N Topics
Topic See Page
ERPS Overview N‐2
ERPS Guidelines N‐2
ERPS Configuration N‐2
65K510DEP08-1A N-1
ERPS Overview
ERPS provides carrier class protection for Ethernet traffic in a ring topology.
ERPS Guidelines
When provisioning ERPS, observe the following guidelines:
• The ERPS ring can only support up to 24 Nodes per ring
• The ERPS ring cannot subtend other ERPS rings, but can support subtended RPR rings
• Only provisioned Inband, internal, and mutlicast VLANs can be shared. VLANs cannot
be shared accross Nodes
NOTE
Only the Switch Module 2‐10G/2‐1 Gigabit, w/Ring Generator
(P/N 1187025G1/G2) currently supports ERPS provisioning.
ERPS Configuration
To configure ERPS, complete the following:
1. Ensure a physical ring exists on the selected Total Access 5000 network.
NOTE
The physical ring consists of fiber connections to the 10 GigE ports. Select the
ports on the nodes going from SM A to SM B in a chaining order until reaching
the original source node.
2. Select the GigE ports being used for ERPS.
NOTE
Remove any previously configured uplinks on the network port.
3. Configure ERPS ring interface on all the nodes.
For more information, refer to “Ring Interface Creation” on page N‐3.
N-2 65K510DEP08-1A
Appendix N, ERPS Provisioning - ERPS Configuration
Ring Interface Creation

To configure the ring interface, complete the following:
1. After establishing a connection with the SCM, pressing any key displays the Total Access
5000 System logon screen.
NOTE
The account name and password fields are case‐sensitive.
The default account name is “ADMIN” and the password is “PASSWORD.”
Other default accounts are: READONLY, READWRITE, and TEST. An
account with ADMIN privileges is required to change the account name and
password.
2. Type the default account name, ADMIN (or the configured account name with System
Administrator privileges), and press ENTER.
3. Type the default password, PASSWORD (or the configured password), and press ENTER.
4. The Total Access 5000 Main Menu is displayed.
5. From the Main Menu, select System CLI and press ENTER.
6. On the CLI menu, verify that the Telnet Port is 2008. This is the default telnet designation.
If this is not displayed, select CLI Telnet Port option and set the port to 2008. Press the ESC
key to return to the CLI menu.
7. From the CLI menu, select CLI Command Entry and press ENTER.
8. The following response is displayed: Use EXIT to exit CLI session.
9. Select “Y” to enter the CLI command interface.
10. Type enable, and press ENTER to enable privileged commands.
12. From the Global Configuration prompt, type interface erps 1/A/1, and press ENTER.
NOTE
If SM‐B is active on the Node, the command changes to interface erps 1/B/1.
13. From the ERPS Interface Configuration prompt, type west interface

ten-gigabit-ethernet 1/A/2, and press ENTER.
14. From the ERPS Interface Configuration prompt, type east interface
ten-gigabit-ethernet 1/B/2, and press ENTER.
15. From the ERPS Interface Configuration prompt, type no shut, and press ENTER to set the
port In Service.
16. From the ERPS Interface Configuration prompt, type exit, and press ENTER.
17. From the Global Configuration prompt, type ethernet default interface erps 1/
B/1, and press ENTER.
65K510DEP08-1A N-3
NOTE
Step 17 should only be performed on RT nodes.
New Remote Terminal Addition

To add a new Remote Terminal to the ERPS ring, complete the following:
NOTICE
These steps must be performed in this order. If not, traffic will be lost on the
ring.
1. Log on to the Remote Terminal Node.
2. Configure the ERPS interface on the new Remote Terminal.
For more information, refer to “Ring Interface Creation” on page N‐3.
3. From the Global Configuration prompt, type ethernet default interface erps 1/
B/1, and press ENTER.
This command configures the uplink on the Remote Terminal Node.
4. Put a Manual Switch (MS) followed by a Forced Switch (FS) on one end of the span
where the Remote Terminal Node will be inserted. Use the following commands to
complete this step:
a. From the Global Configuration prompt, type force manual-switch erps east
1/B/1, and press ENTER.
b. From the ERPS Interface Configuration prompt, type force-switch east, and
press ENTER.
5. Put a FS on the other end of the span.
6. Physically connect the new Remote Terminal Node to the ring.
7. Remove the FS on both nodes. From the ERPS Interface Configuration prompt, type no
force-switch east, and press ENTER.
System Timing Configuration for Central Office Node

To configure the system timing for the Central Office Node, complete the following:
2. From the Global Configuration prompt, type system-timing 1, and press ENTER.
3. From the System‐Timing Configuration prompt, type external primary hop-count
0, and press ENTER.
4. From the System‐Timing Configuration prompt, type external primary priority
0, and press ENTER.
5. From the System‐Timing Configuration prompt, type external primary type bits-
d4, and press ENTER.
6. From the System‐Timing Configuration prompt, type external primary quality
stratum 1, and press ENTER.
N-4 65K510DEP08-1A
Appendix N, ERPS Provisioning - ERPS Configuration
7. From the System‐Timing Configuration prompt, type source primary external

primary, and press ENTER.
8. From the System‐Timing Configuration prompt, type exit, and press ENTER.
9. If necessary, repeat steps 3 ‐ 6, replacing primary with secondary, for a secondary
external source.
System Timing Configuration for Remote Terminal Node

To configure the system timing for the Remote Terminal Node, complete the following:
1. Log on to the Remote Terminal Node.
3. From the Global Configuration prompt, type system-timing 1, and press ENTER.
4. From the System‐Timing Configuration prompt, type source primary interface
ten-gigabit-ethernet 1/A/2 fixed, and press ENTER.
5. From the System‐Timing Configuration prompt, type source secondary interface
ten-gigabit-ethernet 1/B/2 fixed, and press ENTER.
6. From the System‐Timing Configuration prompt, type revertive hop-count, and
press ENTER.
7. From the System‐Timing Configuration prompt, type exit, and press ENTER.
65K510DEP08-1A N-5
N-6 65K510DEP08-1A
Appendix O
Loopback Provisioning

This appendix details the different loopbacks available for the DS3.
In this Appendix
Table O-1. Appendix O Topics
Topic See Page
Loopback Definition O‐2
Line Loopback O‐2
Payload Loopback O‐3
Remote Loopback O‐4
65K510DEP08-1A O-1
Loopback Definition
A loopback and Bit Error Rate Test (BERT) provide the ability to insert a known traffic pattern
and verify the error‐free performance of the circuit at given points in the system.
Line Loopback
A line loopback loops all of the received data back toward the network (DS3 payload and DS3
data). The transmitted data is the identical data that is received and is not reframed or regen‐
erated. This tests right up to the DS3 interface of the module.
The line loopback can be local to the access module and can be initiated by the 873’s request
for a far end loop back.
Line Loopback
DS3 Interface
Figure O-1. Line Loopback Diagram
O-2 65K510DEP08-1A
Appendix O, Loopback Provisioning - Payload Loopback
Payload Loopback
A payload loopback performs the same functionality as the line loopback, except the payload
loopback sends the received data through the framer, where it is reframed and regenerated,
prior to being transmitted back out towards the network. This test also verifies the internal
hardware of the module.
The payload loopback is locally initiated.
Payload Loopback
DS3 Interface
Figure O-2. Payload Loopback Diagram
65K510DEP08-1A O-3
Remote Loopback
A remote loopback transmits a Far End Loop‐up code via the FEAC channel in the DS3
module to the NetVanta 873, which responds by setting‐up a line loopback towards the DS3
card in the Total Access 5000. After the NetVanta 873 DS3 port is looped‐up, Bit Error Rate
Test (BERT) patterns can be sent from the DS3 card to test the integrity of the DS3 circuit.
NOTE
DS3 BERT patterns can be sent from external test equipment. For example,
the integrated BERT in the DS3 EFM module or the NetVanta 873 can be used
in place of an external DS3 test set.
The Remote Loopback request only works in the C‐Bit framing mode.
Remote Loopback
NetVanta 873 Total Access 5000
DS-3 Facility DS-3 Facility
Framer Framer
Figure O-3. Remote Loopback Diagram
O-4 65K510DEP08-1A
Appendix O, Loopback Provisioning - Remote Loopback
65K510DEP08-1A O-5
Carrier Networks Division
901 Explorer Blvd.
Huntsville, AL 35806
U.S.A.
http://www.adtran.com
deployment guide
ADTRAN CUSTOMER CARE
From within the U.S. 1.800.726.8663
From outside the U.S. +1 256.963.8716
PRICING AND AVAILABILITY

1.800.827.0807

Total Access 5000

Uploaded by

Copyright:

Available Formats

You might also like

Total Access 5000

Uploaded by

Document Information

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

Total Access 5000

Uploaded by

Copyright:

Available Formats

deployment guide

Total Access 5000

Document Number: 65K510DEP08-1A

To the Holder of this Document

About this Document

Revision Date Description

safety and regulatory

T1 8-Port Line Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Provisioning the Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Create an EVC Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Configure EFM Bonding Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . 6-9

NCTE A Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

Provision the T1 8-Port Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-15

Figure 1-1. EoCu General Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table Intro-1. Topic List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1

Table 7-3. Available S-tag Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Table I-23. Event Log Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-13

Scope of this Guide

Table Intro-1. Topic List

Table Intro-1. Topic List

Table Intro-2. Related System Documentation

Title Part Number

Scope of this Section

Table 1-1. Section 1 Topics

Topic See Page

Ethernet over Copper Overview

Total Access 5000

Figure 1-1. EoCu General Application Diagram

Ethernet over Copper Components List

Table 1-2. Deployment Part Numbers

Part Number Description CLEI

1187001L1 23‐Inch Chassis BVM2V10G_ _

1187010L1 System Controller Module (SCM) BVCUD0YM_ _

1187010G2 SCM, Second Generation BVC1AA6E_ _

1187011G1 Bridging SCM BVC1ABGE_ _

1187020G1 Switch Module 2 Gigabit, no Ring Generator BVL2N0NC_ _

1187020G2 Switch Module 2 Gigabit, w/Ring Generator BVL2N0PC_ _

1187025G1 Switch Module 2‐10G/2‐1 Gigabit, no Ring Generator BVL3AE4D_ _

1187025G2 Switch Module 2‐10G/2‐1 Gigabit, w/Ring Generator BVL3AE5D_ _

1187030G1 Switch Module 5, 2‐10G/2‐1/2.5 Gigabit, no Ring Generator BVL3AE6D_ _

1187051L1/G1 Switch Module I/O 3 (SMIO3) BVL2PT0C_ _

1187180L1 32‐Port SHDSL EFM Access Module BVL3ABED_ _

1187260G1 DS3 Unchannelized EFM 4‐Port Line Module BVL3ADAD_ _

1187300L1 T1 8‐Port Line Module BVL250CC_ _

1187520E1 RPR Line Module BVC1AAWE_ _

1187550E1 Gigabit Ethernet 4‐Port (GE 4‐Port) Line Module BVL2270C_ _

1187300L1 T1 8‐Port Line Module BVL250CC_ _

1187400G1 Line Module Input/Output Dual Champ 64‐Pin Bridged Rear BVL260DC_ _

1187401G1 Line Module Input/Output Dual Champ 50‐Pin Divided Rear BVL2X10C_ _

1187410G1 Access Module Input/Output Dual Champ 50‐Pin Push‐ BVPQADHM_ _

1187411G1 Access Module Input/Output Triple Champ 50‐Pin Push‐ BVPQAD2M_ _

1187450G1 Access Module Input/Output Dual Champ 64‐Pin Push‐ BVPQADJM_ _

1187460E1 LMIO2 High‐Speed Line Module Rear Panel BVM6E00A_ _

1187925G1 AMIO1 Blank Panel N/A

1187080L1 23‐Inch Fan Module BVPQADGM_ _

1187081L1 23‐Inch Fan Filter N/A

Table 1-2. Deployment Part Numbers (Continued)

Part Number Description CLEI

1187250G1 EFM Bonding Protection Module BVL3ACUD_ _