Page is loading ...
Users Guide
EXN401 & EXN410
Users Guide
EXN401 & EXN410
.
Copyright
Ericsson AB - 2003 All Rights Reserved
Disclaimer
No part of this document may be reproduced in any form without the written
permission of the copyright owner.
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Abstract
This document describes the Ethernet DSL Access, and provides and overall
knowledge about the product.
This document is the Users Guide for the EXN401 & EXN410 and describes
the configuration and management of the Ethernet Gateway.
Trademark List
Interphase®, FibreView®, and the
Interphase logo
These are registered trademark of
the Interphase Corporation
(i)chip™, SynWatch™m ENTIA™,
PowerSAN™, SlotOptomizer™,
iWARE™, iNAV™, and iSPAN™
These are trademarks of the
Interphase Corporation
-
All other trademarks are the property
of their own manufacturers.
ii 1553-LZY 214 2655 C 2004-11-24
END-USER LICENSE AGREEMENT
FOR ERICSSON AB SOFTWARE
IMPORTANT NOTICE TO USER–READ CAREFULLY
THIS END-USER LICENSE AGREEMENT FOR ERICSSON AB SOFTWARE (“AGREEMENT”) IS A LEGAL
AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR SINGLE ENTITY) AND ERICSSON AB FOR THE
SOFTWARE PRODUCTS ENCLOSED HEREIN WHICH INCLUDES COMPUTER SOFTWARE AND PRINTED
MATERIALS (“SOFTWARE”). BY INSTALLING, COPYING, OR OTHERWISE USING THE ENCLOSED SOFTWARE,
YOU AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND
CONDITIONS OF THIS AGREEMENT, PROMPTLY RETURN, WITHIN THIRTY DAYS, THE UNUSED SOFTWARE TO
THE PLACE FROM WHICH YOU OBTAINED IT FOR A FULL REFUND.
The Software is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and
treaties. The Software is licensed, not sold.
Grant of License: You are granted a personal license to install and use the Software on a single computer solely for internal use
and to make one copy of the Software in machine readable form solely for backup purposes.
Restrictions on Use: You may not reverse engineer, decompile, or disassemble the Software. You may not distribute copies of
the Software to others or electronically transfer the Software from one computer to another over a network. You may not use the
Software from multiple locations of a multi-user or networked system at any time. You may not use this software on any product
for which it was not intended. You may not use this software on any non-Ericsson product. LICENSEE MAY NOT RENT,
LEASE, LOAN, OR RESELL THE SOFTWARE OR ANY PART THEREOF.
Ownership of Software: Ericsson or its vendors retain all title to the Software, and all copies thereof, and no title to the
Software, or any intellectual property in the Software, is being transferred.
Software Transfer: You may permanently transfer all of your rights under this Agreement, provided you retain no copies, you
transfer all the Software, and the recipient agrees to the terms of this Agreement.
Limitation of Liability: NEITHER ERICSSON NOR ITS LICENSORS SHALL BE LIABLE FOR ANY GENERAL,
INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR OTHER DAMAGES ARISING OUT OF THIS AGREEMENT EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Confidentiality: The Software is copyrighted and contains proprietary and confidential trade secret information of Ericsson and
its vendors. Licensee agrees to maintain the Software in confidence and not to disclose the Software to any third party without
the express written consent of Ericsson. Licensee further agrees to take all reasonable precautions to prevent access to the
Software by unauthorized persons.
Termination: Without prejudice to any other rights, Ericsson may terminate this Agreement if you fail to comply with any term
or condition of the Agreement. In such event you must destroy the Software together with all copies, updates, or modifications
thereof.
Export: You agree to comply with all export and re-export restrictions and regulations of the U.S. Department of Commerce or
other applicable U.S. agency. You must not transfer the Software to a prohibited country or otherwise violate any such
restrictions or regulations.
U.S. Government Restricted Rights: Use, duplication, or disclosure of the Software to or by the U.S. Government is subject to
restrictions as set forth in the applicable U.S. federal procurement regulations covering commercial/restricted rights software.
You are responsible for complying with the notice requirements contained in such regulations.
General: You acknowledge that you have read and understand this Agreement, and by installing and using the
Software you agree to be bound by the terms and conditions herein. You further agree that this is the complete and
exclusive Agreement between Ericsson and yourself. No variation of the terms of this Agreement or any different
terms will be enforceable against Ericsson unless agreed to in writing by Ericsson and yourself. The validity of this
Agreement and the rights, obligations, and relations of the parties hereunder shall be determined under the
substantive laws of the State of Sweeden. If any provision of this Agreement is held invalid, illegal, or
unenforceable, the remaining provisions shall in no way be affected or impaired thereby. All rights in the Software
not specifically granted in this Agreement are reserved by Ericsson.
iii
Assistance
According to the Ericsson Service Agreement made, service and technical
assistance can be obtained accordingly. The consequent possibility for
downloading SW is obtained from
http://dxd.ericsson.se/cgi-bin/eda_authenticate.cgi/centre.html
Documentation updates
Documents are available according to agreement through the local Ericsson
Key Account Manager that can give access to the Customer Product
Information library:
http://cpi.al.sw.ericsson.se/alex
and browse for the product on the following
path: Multi-Service Networks (BMSN), Ethernet DSL Access.
Revision History
This User’s Guide is valid for EXN401 and EXN410 ATM to Ethernet
Converter. Other product versions, which include functions not described in
this manual, may be available.
iv
1553-LZY 214 2655 C 2004-11-24
About this manual
Audience
This manual assumes that its audience has a general understanding of
computing and networking terminology.
Icon Conventions
Icons draw your attention to especially important information:
Note:
The Note icon indicates important points of interest related to the current
subject.
Caution!
The Caution icon brings to your attention those items or steps that, if not
properly followed, could cause problems in your machine’s configuration or
operating system.
Warning!
The Warning icon alerts you to steps or procedures that could be
hazardous to your health, cause permanent damage to the equipment, or
impose unpredictable results on the surrounding environment.
v
Text conventions
The following conventions are used in this manual. Computer-generated text
is shown in typewriter font. Examples of computer-generated text are: program
output (such as the screen display during the software installation procedure),
commands, directory names, file names, variables, prompts, and sections of
program code.
Computer-generated text example
Commands to be entered by the user are printed in bold Courier type. For
example:
cd /usr/tmp
Pressing the return key “
Return” at the end of the command line entry is
assumed, when not explicitly shown. For example:
/bin/su
is the same as:
/bin/su ↵ Return
Required user input, when mixed with program output, is printed in bold
Courier type. References to UNIX programs and manual page entries follow
the standard UNIX conventions.
When a user command, system prompt, or system response is too long to fit
on a single line, it will be shown as
Do you want the new kernel moved into
\ vmunix?[y]
with a backslash at either the beginning of the continued line or at the end of
the previous line.
vi
1553-LZY 214 2655 C 2004-11-24
.
Contents
Assistance iv
Documentation updates iv
Revision History iv
About this manual v
1 Introduction 1
1.1 Overview 1
1.2 Supported standards 1
1.3 Configuration Images 2
1.4 Configuration Methods 2
1.5 Management 3
1.6 Initial Configuration 3
2 Command Line Interface 4
2.1 Overview 4
2.2 Text Conventions 6
2.3 Using CLI Commands 7
2.3.1 Using Help 8
2.3.2 Command History 8
2.3.3 Accessing Command Modes 8
2.3.4 Session Time-Out 10
2.4 User EXEC Mode 11
2.4.1 enable 11
2.4.2 logout 11
2.4.3 disconnect 11
2.5 Privileged EXEC Mode 12
2.5.1 atm-format 12
1553-LZY 214 2655 C 2004-11-24 vii
Introduction
2.5.2 buffers 12
2.5.3 session-timeout 13
2.5.4 watchdog 14
2.5.5 script 14
2.5.6 copy 15
2.5.7 update 16
2.5.8 reload 17
2.5.9 coldboot 17
2.5.10 clearconf 18
2.5.11 configure 18
2.5.12 disable 19
2.6 Global Configuration Mode 20
2.6.1 hostname 20
2.6.2 password 20
2.6.3 enable password 20
2.6.4 date 21
2.6.5 time 21
2.6.6 ip ftp username 22
2.6.7 ip ftp password 22
2.6.8 ip file server 23
2.6.9 ip gateway 23
2.6.10 oam-nodeid 23
2.6.11 lacp 24
2.7 Controller Configuration Mode 25
2.7.1 Entering Mode 25
2.7.2 Commands 25
2.8 Ethernet Interface Configuration Mode 29
2.8.1 Entering Mode 29
2.8.2 Commands 29
2.9 VC Class Configuration Mode 36
2.9.1 Overview 36
2.9.2 Entering Mode 36
2.9.3 Commands 36
viii 1553-LZY 214 2655 C 2004-11-24
IntroductionContents
2.9.4 Removing a VC Class 48
2.10 ATM Interface Configuration Mode 49
2.10.1 Overview 49
2.10.2 Entering Modes 50
2.10.3 ATM Interface Configuration Commands 51
2.10.4 ATM VP Configuration Commands 54
2.10.5 ATM PVC Configuration Commands 57
2.10.6 ATM PVC Range Configuration Commands 61
2.11 Management Configuration Mode 64
2.11.1 Overview 64
2.11.2 Entering Mode 64
2.11.3 Commands 65
2.11.4 Binding an Interface to Management 67
2.11.5 Removing a Management entity 68
2.12 Failover Configuration Mode 69
2.12.1 Overview 69
2.12.2 Entering Mode 69
2.12.3 SONET Specific Commands 70
2.12.4 Gigabit Ethernet Specific Commands 71
2.12.5 Show Commands 72
2.12.6 Other Commands 73
2.12.7 Removing a Failover group 74
2.13 Link Aggregation Configuration Mode 75
2.13.1 Overview 75
2.13.2 Entering Mode 75
2.13.3 Commands 76
2.13.4 Removing a Link Aggregation Group 78
2.14 General Commands 79
2.14.1 ping 79
2.14.2 show 79
3 Bridging 82
3.1 Overview 82
1553-LZY 214 2655 C 2004-11-24
ix
Introduction
3.1.1 What is a Bridge 82
3.1.2 Types of Bridges 82
3.1.3 VLANs 82
3.1.4 Frames Format 83
3.2 EXN400 Bridging Support 86
3.2.1 Supported Interfaces 86
3.2.2 Maximum Number of Bridges 86
3.2.3 Types of Bridge 86
3.2.4 VLAN-Aware Bridge 86
3.2.5 Learning 87
3.2.6 Filtering 87
3.2.7 Force Forwarding 88
3.2.8 Management 88
3.2.9 Bridging process 88
3.2.10 Example: Ethernet-to-ATM – no VLAN – ATM VC Multiplexing 90
3.2.11 Example: ATM-to-Ethernet – no VLAN – ATM LLC/SNAP
Encapsulation 90
3.2.12 Example: Ethernet-to-ATM – VLAN – ATM LLC/SNAP
Encapsulation 91
3.2.13 Example: ATM-to-Ethernet – VLAN – ATM VC Multiplexing 91
3.3 VLAN Priority Mapping 92
3.3.1 Weighted Fair Queueing Mechanism 93
3.4 Command Line Interface 95
3.4.1 Subscriber Policy Configuration Mode 95
3.4.2 Priority Table Configuration Mode 102
3.4.3 ATM PVC Group Configuration Mode 104
3.4.4 PVC Range Group Configuration Mode 108
3.4.5 Bridge Configuration Mode 112
3.5 Configuration Samples 126
3.5.1 Configuring a Transparent MAC Bridge 126
3.5.2 Configuring a VLAN-Aware Bridge 128
4 SNMP Management 130
4.1 Overview 130
x 1553-LZY 214 2655 C 2004-11-24
IntroductionContents
4.2 Configuring SNMP Management 130
4.2.1 Enabling Reception of SNMP Requests 130
4.2.2 Setting the Contact, Name, and Location 131
4.2.3 Configuring a TRAP client 133
4.3 Alarm Notification 134
4.4 Notes on RFC2233 134
4.5 Notes on RFC2737 136
4.6 Notes on RFC1757 136
4.7 Notes on RFC2515 136
4.8 Notes on RFC2558 136
4.9 Notes on RFC2558 136
5 Initial Configuration and Configuration Samples 138
5.1 Initial Configuration 138
5.1.1 Configuring EXN400 Name 138
5.1.2 Setting Date and Time 138
5.1.3 Enabling Privileged EXEC password 139
5.1.4 Configuring ATM format 139
5.1.5 Configuring System Buffer Pool 139
5.2 Configuring Failover 140
5.2.1 Configuring Gigabit Ethernet Failover 140
5.2.2 Configuring SONET Failover 140
5.3 Configuring Management 141
5.3.1 Configuring Management through Fast Ethernet 141
5.3.2 Configuring Management through Fast Ethernet using VLAN 141
5.3.3 Configuring Management on an IP over ATM Channel 142
5.3.4 Configuring Management on an Ethernet over ATM Channel 143
5.4 Configuring FTP Connection 144
6 Command list, description and index 145
6.1 Overview 145
6.2 Global commands 145
6.2.1 Available Commands 145
1553-LZY 214 2655 C 2004-11-24
xi
Introduction
6.3 Quick Reference 151
7 Configuration Guidelines 154
7.1 Schematic Configuration Overview 154
7.2 Accessing the EXN400 154
7.2.1 Default settings for EXN 400 series 155
7.3 Configuration order and examples 156
7.3.1 Clear previous configuration in EXN400 157
7.3.2 Enter the “Global configuration mode” of the EXN400 157
7.3.3 Define "Hostname and Password" for entering this EXN401 157
7.3.4 Create a "Subscriber policy" object 157
7.3.5 Create a "Management" object 157
7.3.6 Define where the ftp file server for software upgrade is incl.
UserID and Password 158
7.3.7 Create a bridge object 158
7.3.8 Initilize the ATM 0 port 158
7.3.9 Initilize the FastEthernet 1 port 158
7.3.10 Connect the management-object and the fastEthernet 1 port to
the bridge-object 158
7.3.11 Define the VC-classes 159
7.3.12 Define the PVC's in the ATM 0 interface, ubr (data1) is set as
the default service class 159
7.3.13 Check how this looks in the connected bridge 160
7.3.14 Define the "virtual ports" in the bridge bridge1 on the
fastEthernet 1 port side 160
7.3.15 Define the "virtual ports" in the bridge bridge1 on the ATM 0
port side 161
7.3.16 Set the sonet interface to “clock source internal” in the EXN400 162
7.3.17 Show all configuration in the EXN400 162
7.3.18 Save configuration in the EXN400 162
7.3.19 Restart the EXN400 162
Acronyms and Abbreviations 163
Reference List 164
xii 1553-LZY 214 2655 C 2004-11-24
Introduction
1 Introduction
1.1 Overview
The EXN400 Ethernet Gateway; see Figure 1 on page 1 is a stand-alone
replaceable unit in a 1U height configuration (pizza box) that provides ATM
to Ethernet processing between various interfaces.
Figure 1 EXN410; Ethernet Gateway
As an off-the-shelf product, the EXN400 is manageable without additional
software add-ons. Management includes configuration and monitoring.
At initial installation, the user can access the EXN400 only through a TTY
console (parameters are 9600 baud, 8 data bits, 1 stop bit, no parity, no
flow control) or via Telnet by using the default settings mentioned in section
7.2.1 on page 155.
After management configuration, the user can also access the EXN400 on
a Telnet session (for more information see Management Configuration
Mode, section 2.11 on page 64 and Configuring Management, 5.3 on page
141).
1.2 Supported standards
IEEE and IETF Standards Compatibility:
IEEE 802.3u Fast Ethernet •
•
•
IEEE 802.3ab 1000BaseT
IEEE 802.1Q-VLAN, IEEE 802.eac
1553-LZY 214 2655 C 2004-11-24
1
Introduction
IEEE 802.3 LAN per 802.3, 802.3ab •
•
•
•
•
•
•
•
•
•
•
•
•
IEEE 802.3ad Link Aggregation
IETF Standards Compatibility:
RFC 2684 Multiprotocol encapsulation over ATM AAL5
ITU Standards Compatibility:
ITU-T I.432.1, I.432.2 B-ISDN user-network interface – Physical layer
specification
ITU-T I.361 B-ISDN ATM layer specification
ITU-T I.363.5 B-ISDN ATM adaptation layer specification: Type 5 AAL
ITU-T I.371 Traffic control and congestion control in B-ISDN
ITU-T I.371.1 Guaranteed frame rate ATM transfer capability
ITU-T I.610 B-ISDN operation and maintenance principles and
functions
1.3 Configuration Images
There are three images of the software configuration:
The running configuration is the configuration currently running. It is
stored in RAM. Therefore any change in configuration will not be taken
into account at next boot unless the running configuration is saved.
The startup configuration is the configuration that is taken into account
at boot time. It is stored in FLASH and can be updated.
The backup configuration is a copy of an operational configuration that
can be reactivated at any time. When configuration is saved in the
startup configuration, the previous startup configuration becomes the
backup configuration.
The software configuration can be downloaded from or saved to a
configuration file on an FTP/TFTP server. This file is not in a human-
readable format and should not be modified by the user.
1.4 Configuration Methods
Configuration is possible by using any of the following methods:
Entering commands on the Command line interface (CLI) through TTY
or remote shell
2 1553-LZY 214 2655 C 2004-11-24
Introduction
Preparing a script file including all the CLI commands, copying it on an
FTP server, and downloading the script file on the EXN400 by running
the script CLI command (for more information on script command,
see “script”, section 2.5.5 on page 14)
•
•
•
•
•
•
•
•
•
•
•
•
•
Downloading a configuration file on the EXN400 from an FTP server by
running the copy CLI command and rebooting to take the new
configuration into account (see “copy”, section 2.5.6 on page 15)
1.5 Management
A management entry point should be configured to:
Perform an FTP/TFTP connection
Run the ping command
Enable a telnet access to the EXN400
Enable SNMP management
Management can be configured through:
A single Ethernet interface or ATM PVC (for more information, see
Management Configuration Mode, section 2.11 on page 64)
A bridge (for more information, see Management Configuration Mode,
section 2.11 on page 64)
For a bridge, management will be available through any interface and/or
ATM PVC bound
to the bridge.
1.6 Initial Configuration
At first use, it is strongly recommended to configure:
The EXN400 name
The date and time
The Privileged EXEC password (if needed)
The ATM format
The system buffer pool
1553-LZY 214 2655 C 2004-11-24
3
Command Line Interface
2 Command Line Interface
2.1 Overview
The Command Line Interface (CLI) is available through either a TTY
console or a Telnet session. Only one Telnet session can be open on an
EXN400 at a given time. To enable telnet access, at least one management
entry point must be configured (for more information, see Management
Configuration Mode, section 2.11 on page 64).
Several access levels are available:
User EXEC level: Only certain commands to view the EXN400 status
are available.
•
•
•
Privileged EXEC level: All the commands to view and configure the
EXN400 are available. A password may be required. Only one session
can enter Privileged EXEC level at a given time.
The EXN400 configuration exists in Global configuration and several
lower level configurations.
To illustrate this, several configuration modes are organized as shown in
Figure 2 on page 5.
4 1553-LZY 214 2655 C 2004-11-24
Command Line Interface
User EXEC
Mode
Privileged
EXEC Mode
Global
Configuration
Controller
Configuration
Management
Configuration
Interface
Configuration
Subscriber
Configuration
VC Class
Configuration
Bridge
Configuration
Policy
Figure 2 Configuration Mode Organization
The command line prompt identifies both the EXN400 name and the
command mode. The last character in the command prompt identifies the
access level, that is,
$ for a User EXEC level and # for a Privileged EXEC
level.
Example:
MyBox(config-if)#
1553-LZY 214 2655 C 2004-11-24
5
Command Line Interface
2.2 Text Conventions
Command descriptions use the following conventions:
boldface font Commands and keywords are in boldface. •
•
•
•
•
•
plain font Parameter values are in plain.
{...} Keywords or variables are required.
[...] Keywords or variables are optional.
x | y Choice between two keywords or variables.
<key> Keyboard character or sequence of characters.
6 1553-LZY 214 2655 C 2004-11-24
/