Ericsson EXN401, EXN410 User Manual
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
(i)chip™, SynWatch™m ENTIA™,
PowerSAN™, SlotOptomizer™,
iWARE™, iNAV™, and iSPAN™
-
These are registered trademark of
the Interphase Corporation
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
path: Multi-Service Networks (BMSN), Ethernet DSL Access.
and browse for the product on the following
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 “
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.
Return” at the end of the command line entry is
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
IntroductionContents
Index 165
1553-LZY 214 2655 C 2004-11-24
xiii
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.
Introduction
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 humanreadable 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
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
Introduction
•
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
VC Class
Configuration
Subscriber
Configuration
Interface
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
2.3 Using CLI Commands
The Command Line Interface (CLI) is case-sensitive. •
•
Abbreviated commands: You can abbreviate keywords by entering at
least sufficient leading characters to uniquely identify the desired
keyword.
•
The ? key: Use the ? key at any time to see all the choices you can
enter next. When you enter the ? key, all available choices are
displayed. The system again displays the command you already
entered.
•
The <backspace> key can be used to delete the character immediately
preceding the cursor.
Command Line Interface
•
The <enter> key is used to execute the entered command.
•
The <tab> key and <space> key can be used to complete the current
keyword (if possible). It applies only to well-known keywords and not to
names of entities created by the user.
•
The <up-arrow> key can be used to display the previous command in
history.
•
The <down-arrow> key can be used to display the next command in
history.
•
The <left-arrow> and <right-arrow> keys can be used to move the
cursor back and forth in the command line.
•
The <ESC+B> keys can be used to move the cursor back one word.
•
The <ESC+F> keys can be used to move the cursor forward one word.
•
The <CTRL+A> keys can be used to move the cursor to the beginning
of the command line.
•
The <CTRL+E> keys can be used to move the cursor to the end of the
command line.
•
The <CTRL+C> keys can be used to abort a command line.
•
One <space> character cannot be followed by another <space>
character. The second one is discarded by the CLI.
•
The no keyword: For most configuration commands, the no keyword
can be inserted at the beginning of the command line to negate a
command or to restore its default setting.
•
Names of entities created by the user are alphanumeric strings. They
can contain any character in the sets [a-z], [A-Z], [0-9]. The underscore
character ‘_’ is also accepted. In addition, names of entities of the
same type should be carefully chosen. For example, if an entity named
1553-LZY 214 2655 C 2004-11-24
7
Command Line Interface
thename exists, it will not be possible to define a new entity named
thenam.
2.3.1 Using Help
The system CLI provides a variety of useful context-sensitive help features:
? Lists all keywords applicable to the
•
•
help Displays a brief description of the help
•
partial-keyword?
•
partial-keyword<tab> Completes the partial keyword (if
current command mode
system
Lists the keywords that begin with a
certain character string
possible)
•
command <space>? Lists the set of all valid
2.3.2 Command History
The CLI maintains a command history for each command mode. You can
navigate through command history by using the up and down arrows.
2.3.3 Accessing Command Modes
Table 1 Command Mode Access
Mode
Privileged
EXEC
Global
Configuration
Access
From
User EXEC
Privileged
EXEC
Command Description
enable
configure
next available choices
Access to Privileged EXEC Mode.
To exit this mode:
- disable or exit to return to User EXEC
Access to Global Configuration Mode.
New prompt: (config)
To exit this mode:
- exit or Ctrl+Z to return to Privileged
EXEC
Controller
configuration
Global
Configuration
controller
To configure a SONET interface
New prompt: (config-controll)
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
8 1553-LZY 214 2655 C 2004-11-24
Command Line Interface
Mode
Interface
configuration
ATM VC
class
configuration
Management
configuration
Failover
configuration
Link
aggregation
configuration
Access
From
Global
Configuration
Global
Configuration
Global
Configuration
Global
configuration
Global
configuration
Command Description
interface
vc-class atm
management
failover
link-
aggregation
To modify other types of interfaces
(ATM, FastEthernet, GigabitEthernet)
New prompt: (config-if)
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
To create or modify a set of
preconfigured VC parameters.
New prompt: (config-vc-class)
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
To create or modify a management
entry point.
New prompt: (
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
To create or modify a link aggregation
group.
New prompt: (
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
To create or modify a failover group.
New prompt: (
To exit this mode:
- exit or abort to return to Global
Configuration
- Ctrl+Z to return to Privileged EXEC
config-mngt)
config-link-agg)
config-flvr)
Subscriber
Policy
configuration
Bridge
configuration
1553-LZY 214 2655 C 2004-11-24
Global
Configuration
Global
Configuration
subscriberpolicy
bridge
To create or modify a subscriber policy.
New prompt: (config-bridge)
To exit this mode:
- exit to return to Global Configuration
- Ctrl+Z to return to Privileged EXEC
To create or modify a bridge.
New prompt: (config-bridge)
To exit this mode:
- exit to return to Global Configuration
- Ctrl+Z to return to Privileged EXEC
9
Command Line Interface
2.3.4 Session Time-Out
Since the number of sessions is limited (one session on TTY console and
one telnet session) and the access to Privileged EXEC level is exclusive,
the EXN400 automatically disconnects any session after a period of
inactivity, that is:
For a telnet access, the session is closed. •
• For the TTY console, the session returns to User EXEC level.
The session time-out is 900 seconds by default but can be changed in
Privileged EXEC mode.
10 1553-LZY 214 2655 C 2004-11-24
2.4 User EXEC Mode
2.4.1 enable
Description This command is used to enter into Privileged EXEC mode.
If a password is enabled, user is requested to enter it.
Syntax enable
Default none
Modes User EXEC
Example EXN400$ enable
Command Line Interface
2.4.2 logout
Description This command is used to disconnect a telnet session. This
command is available only for a telnet session.
Syntax logout
Default none
Modes User EXEC, Privileged EXEC
Example EXN400$ logout
2.4.3 disconnect
Description This command is used to force disconnection of a telnet
session. This command is available only for the console session. You can
see if a telnet session is engaged by running the show session comand.
Syntax disconnect
Default none
Modes User EXEC
Example EXN400$ disconnect
1553-LZY 214 2655 C 2004-11-24
11
Command Line Interface
2.5 Privileged EXEC Mode
2.5.1 atm-format
Description This command is used to configure the ATM format between
Network Network Interface (NNI) and User Network Interface (UNI). Once
you change the settings, no further configuration is allowed and you will be
asked to save your configuration and reboot the system. Note that this
parameter is part of the system startup configuration and is not reset by the
clearconf command without the all option.
Syntax atm-format [nni|uni]
nni Selects the NNI format.
uni Selects the UNI format.
If no parmeter is specified, the command displays the current ATM format.
Default NNI
Show show atm-format
Modes Privileged EXEC
Example To configure the ATM format to UNI:
EXN400# atm-format uni
2.5.2 buffers
Description This command is used to configure the system buffer pool.
User can specify the buffer size and the system automatically computes the
number.
The buffers are used to receive and transmit data on any communicating
channel (ATM PVC, Ethernet interface). Each time a new channel is
defined, some buffers are reserved. The number of buffers reserved for
each channel depends on the size of the transmit queue for this channel.
The transmit queue size can be configured by using the tx-queue-size
command.
The buffer size limits the Maximum Transmit Unit (MTU) size. One buffer
must be able to contain the largest MTU and an extra 120-bytes overhead.
12 1553-LZY 214 2655 C 2004-11-24
Command Line Interface
You should keep in mind that increasing the buffer size results in reducing
the number of buffers, and thus, the number of communicating channels
that can be supported.
Once you change the system buffer pool settings, no further configuration
is allowed and you will be asked to save your configuration and reboot the
system. Note that this parameter is part of the system startup configuration
and is not reset by the clearconf command without the all option.
Current settings can be displayed by using the show buffers command.
Syntax buffers {size}
size The new buffer size. It must be a multiple of 256, in the
range [1792-64256]. It must also contain the largest MTU
and an extra 120-bytes overhead.
Default 1792
Show show buffers
Modes Privileged EXEC
Example To configure the buffer size to 2304:
EXN400# buffers 2304
2.5.3 session-timeout
Description This command is used to change the inactivity timeout for
any session.
Syntax [no] session-timeout [value]
value The new assigned timeout in seconds. Value 0 means no
inactivity timeout.
session-timeout value Change the inactivity timeout.
session-timeout Display the current timeout value.
no session-timeout Disable inactivity timeout.
Default 900 seconds
Show session-timeout
Modes Privileged EXEC
Example To configure the session timeout to one hour:
EXN400# session-timeout 3600
1553-LZY 214 2655 C 2004-11-24
13
Command Line Interface
2.5.4 watchdog
Description This command is used to enable or disable the watchdog
mechanism. When the watchdog is enabled, it monitors software activity
and when it detects a failure, it automatically reboots the system.
Syntax [no] watchdog
watchdog Enable watchdog.
no watchdog Display watchdog.
Default Disabled
Show show watchdog
Modes Privileged EXEC
Example To enable watchdog:
EXN400# watchdog
2.5.5 script
Description This command is used to download a script file from the FTP
server and run it. A script file is a text file. Each line is a command as if it
would be entered on the TTY console or Telnet session. Some comment
lines, starting with a pound sign (
script file to improve the readability.
Syntax script {ftp:filename | tftp:filename}
filename Name of the script file on the FTP/TFTP server.
The FTP connection is defined by using:
The FTP username defined using the ip ftp username command
•
(for more information, see “ip ftp username” section 2.6.6 on page 22)
•
The FTP password defined using the ip ftp password command
(for more information, see “ip ftp password” section 2.6.7 on page 22)
•
The FTP server location defined using the ip file server
command (for more information, see “ip file server” section 2.6.8 on
page 23).
#), or blank lines can be inserted in the
The TFTP connection uses the TFTP server location defined using the ip
file server command (for more information, see “ip file server” section
2.6.8 on page 23).
Default None
14 1553-LZY 214 2655 C 2004-11-24
Modes Privileged EXEC
Requirement Need a management entry point since FTP/TFTP is used.
Example To download and run the script file scrconf.txt located in
the directory script on the FTP server:
EXN400# script ftp:script/scrconf.txt
Requirement Need a management entity since FTP is used. This management entity must have an IP address and mask in the same sub-network as
the FTP server.
2.5.6 copy
The copy command in Privileged EXEC mode can be used to:
Command Line Interface
Copy any configuration image to an FTP server •
•
COPY a startup configuration image from an FTP server
•
Copy the running configuration into the startup configuration
•
Restore a backup configuration
Description This command is used to save a configuration to ROM or to
load/copy a configuration from/to an FTP server.
Syntax copy src-config dest-config
src-config and dest-config are one of the following:
backup-config A backup configuration
running-config The current running configuration
startup-config The startup configuration stored in FLASH
ftp:filename filename is the name of the file on the FTP server to
upload or download.
ftp:filename filename is the name of the file on the TFTP server
to upload or download.
The FTP connection is defined by using:
•
The FTP username defined using the ip ftp username command
(for more information, see “ip ftp username” section 2.6.6 on page 22)
•
The FTP password defined using the ip ftp password command
(for more information, see “ip ftp password” section 2.6.7 on page 22)
1553-LZY 214 2655 C 2004-11-24
15
Command Line Interface
The FTP server location defined using the ip file server
•
command (for more information, see “ip file server” section 2.6.8 on
page 23).
The TFTP connection uses the TFTP server location defined using the ip
file server command (for more information, see “ip file server” section
2.6.8 on page 23).
The supported combinations are:
•
copy running-config startup-config
•
copy running-config {ftp:filename | tftp:filename}
•
copy startup-config {ftp:filename | tftp:filename}
•
copy backup-config {ftp:filename | tftp:filename}
•
copy backup-config startup-config
•
copy {ftp:filename | tftp:filename} startup-config
Default None
Modes Privileged EXEC
Requirement Need a management entry point since FTP/TFTP is used.
Example To save running configuration to startup configuration to be
taken into account on next reboot:
EXN400# copy running-config startup-config
Example To save running configuration on an FTP server, in file
named backup located in directory config:
EXN400# copy running-config ftp:config/backup
2.5.7 update
Description This command is used to update the EXN400 internal
software. The EXN400 internal software is supplied by Ericsson as a binary
file. After running this command, the EXN400 is automatically rebooted.
Syntax update {ftp: filename | tftp: filename}
filename Name of the file that contains the new EXN400 internal
software.
16 1553-LZY 214 2655 C 2004-11-24
Loading...