Emp Cli User Guide
Emp Cli User Guide
EDA 1200
Copyright
Ericsson AB 2009-2010. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
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.
Legal Notice
The Linux Core system is the operating system for the Ethernet Node Controller
in ECN. The Linux distribution for ECN is based on standard open source
packages widely used in the Linux community. For more information about the
license refer to Third Party License Agreement.
Common Net Notice Text
This product includes software developed by The Apache Software Foundation
(http://www.apache.org/).
The software is based on the Commons Net software (http://jakarta.apach
e.org/commons/net/).
Only the telnet part and some supporting libraries have been included from the
Commons Net package by Ericsson Denmark.
Please refer to the Third Party License Agreements for the license terms.
Trademark List
Windows
Linux
Contents
Contents
1
Introduction
1.1
Conventions
1.2
Revision Information
2.1
2.2
Entering Commands
2.3
10
2.4
11
13
3.1
Changing Prompt
13
3.2
Changing Password
13
3.3
14
3.4
16
3.5
17
3.6
Ping a Node
18
3.7
CLI Autologout
19
3.8
Restarting Nodes
20
3.9
21
3.10
22
3.11
22
Configuring Interfaces
25
4.1
25
4.2
28
4.3
Backup Configuration
29
4.4
Restore Configuration
30
4.5
31
33
5.1
33
Managing Software
35
6.1
35
6.2
36
6.3
Updating EMP SW
37
6.4
38
6.5
38
Management Configuration
41
7.1
SNMP
41
7.2
Local Management
44
7.3
EM-PEM Management
45
Configuring VLAN
47
8.1
Service VLAN
47
8.2
VLAN Unaware
47
ECN Configuration
49
9.1
External VLAN
49
9.2
Inventory Commands
50
9.3
Port Commands
52
9.4
59
9.5
Link Aggregation
64
9.6
Redundancy
66
9.7
Unmanaged Switch
66
9.8
Unmanaged Node
68
9.9
69
9.10
70
9.11
70
9.12
Switch Extension
72
9.13
Auto Rediscover
79
9.14
79
9.15
Show ECN
80
10
EDN Commands
83
10.1
Uplink Configuration
83
10.2
84
11
85
11.1
85
11.2
88
11.3
94
11.4
PVC Commands
11.5
107
11.6
109
11.7
113
11.8
115
11.9
116
11.10
Alarm Thresholds
117
11.11
118
11.12
119
12
ESN Commands
121
12.1
Link Aggregation
121
12.2
122
13
EXN Commands
125
13.1
125
13.2
125
13.3
126
13.4
127
14
EFN Commands
129
14.1
EFN324 Commands
129
15
Alarms
131
15.1
Alarm Filter
131
15.2
132
15.3
133
15.4
135
16
Security
137
16.1
137
16.2
138
16.3
Configuring Protocols
139
16.4
Radius Server
140
16.5
Tacacs Server
141
16.6
Server Authentication
142
17
145
17.1
145
95
18
149
18.1
149
18.2
149
18.3
150
19
Factory Default
151
20
155
20.1
Linux Kernel
155
20.2
Linux Applications
156
20.3
Linux Libraries
156
Introduction
Introduction
This guide provides detailed information on how to use the Command Line
Interface (CLI) to configure the following Ethernet Controller Nodes (ECN):
ECN320
ECN330
ECN430
The term ECN-switch refers to an ECN running in switch mode. For information
on how to use the Web Interface to configure the ECN, refer to the EMP Web
Interface User Guide.
Although there is a lot of overlap between the Web Interface and the CLI, the
CLI does not include all the functions found in the Web Interface. Similarly,
some CLI functions are not found in the Web Interface.
This guide is intended for both installation personnel and system administrators
responsible for operating and maintaining network equipment. The reader is
expected to have a basic knowledge of general switch functionality, the Internet
Protocol (IP), and Simple Network Management Protocol (SNMP). The guide
does not attempt to give a complete explanation of the various standards, but
rather the implementation of the standards in the ECN. For more information of
the standards, please refer to the standard specifications.
Note:
1.1
Conventions
Typographic conventions used throughout this guide are listed in Table 1 on
page 1.
Table 1
Typographic Conventions
Convention
Description
Example
User Input
A command that
you must enter in
a Command Line
Interface (CLI)
exactly as written.
cd $HOME
Command Variables
Command variables,
the values of which
you must supply.
<home_directory>
Table 1
Typographic Conventions
Convention
Description
Example
[argument1|argument2]
The brackets
indicate that these
arguments are
optional and can
be omitted. The
| indicate that
either argument1 or
argument2 is used.
If used, the brackets
must not be typed.
[disable|enable]
{argument1|argument2}
The brackets
indicate that
argument1 or
argument2 are
required. The
| indicate that
either argument1
or argument2 must
be used as a value
for this parameter.
{lock|unlock}
GUI Objects
Key Combinations
Key combinations.
System Elements
Command and
parameter names,
program names,
path names, URLs,
and directory names
Output Information
Text displayed by
the system
Code Examples
Code examples
(3)
{Jan,Feb}
(1) The plus sign (+) indicates that the keys must be pressed simultaneously.
(2) The use of the forward slash (/) is for Unix systems, Windows systems use the backslash (\).
(3) The back slash (\) is used to show where long lines are split.
1.2
Revision Information
This guide is valid from EDA 1200 4.1 R8A and later. Other product versions,
with functions not described in this guide, may be available.
Introduction
1.2.1
1.2.2
Version B
Other than editorial changes, this document has been revised as follows:
1.2.3
Version (A)
This is the first version of the this guide prepared for EDA 1200 4.1 R7A.
Other than editorial changes, this document has been revised as follows:
New Relay Agent option (TR 101 Flex) added in Section 11.4.1 on page 96
2.1
Set the data format to 8 data bits, 1 stop bit, and no parity.
Note:
When the CLI session has been initiated the following user name and password
has to be given at the login prompt to access the CLI shell:
login:admin
Password:admin (the password will not be shown)
Starting CLI application.
......................
ecn#
2.2
Entering Commands
This section describes how to enter CLI commands.
2.2.1
The commands exit and end, will change the command level, see Section 2.3
on page 10. The CLI is not case sensitive.
2.2.2
Minimum Abbreviation
The CLI will accept a minimum number of characters that uniquely identify a
command. For example, the command config can be entered as co.
If an entry is ambiguous, the system will prompt for further input.
Example:
The command show system calendar can be entered as:
ecn#sho sys cal
2.2.3
Command Completion
If input is terminated by pressing the TAB key, the CLI prints the remaining
characters of a partial keyword or argument up to the point of ambiguity. For
example, typing sh followed by pressing the TAB key will result in printing the
command up to show. If one or more of the previous words are incorrect,
auto-completion does not work. Some detailed examples are shown below.
Examples:
ecn# config dslport 2.3.4 alarms line-initialization-fai
lure e
Pressing the TAB key will result in:
ecn# config dslport 2.3.4 alarms line-initialization-fai
lure enabled
If the value is not uniquely defined, a list of possible options is displayed, that is:
ecn#config dslport 2.3.4 alarms line-initialization-fail
ure
Pressing the TAB key will result in:
line-initialization-failure:
enable, disable
2.2.4
2.2.5
Keystroke
Function
Ctrl + A
Ctrl + B
Ctrl + D
Ctrl + E
Ctrl + F
Ctrl + P
Ctrl + R
Ctrl + U
2.2.6
2.2.7
2.2.8
Command Execution
After a command is executed, the same prompt at the same command level will
appear, indicating that the command has been executed. If there is no error
message, the execution was successful. A new command can be entered
at the same command level.
2.2.9
Scripts
CLI commands can be collected in a script. To play the script, a terminal
program supporting scripts is required as for example the Tera Term (pro).
The commands are copied from the script to the terminal program. This will
activate all the copied commands.
2.3
2.3.1
Go to Root Level
Command Usage:
This command is used to bring the command level to the root level. The
command can be used at all command levels.
Command Level:
Any
Syntax:
end
Arguments:
None
Default Settings:
None
Examples:
ecn(config system)#end
2.3.2
Exit
Command Usage:
This command is used to bring the command level to the previous level. The
command can be used at all command levels. At the root level the CLI is
terminated.
The command end will give the root level, see Section 2.3 on page 10.
Command Level:
Any
Syntax:
exit
Arguments:
None
Default Settings:
None
Examples:
ecn(config system)#exit
10
2.4
Table 3
Level 1
Level 2
config
Handling of configuration
privileges.
copy-dslport
dslport
ecn
Configuration commands
for redundancy and link
aggregation in the ECN.
edn
esn
Commands to configure
embedded switches.
exn
load-configuration
reset-dslports
save-configuration
security
Security configuration.
system
System configuration.
led-test
LED Commands.
test
Testing lines.
Description
11
12
3.1
Changing Prompt
Command Usage:
Use this command to change the command prompt of the CLI in order to make
it easier to identify a node.
Command Level:
ecn(config system)#
Syntax:
prompt [<string>|none]
Arguments:
<string>
none
Default Settings:
None
Examples:
ecn(config system)#prompt ECN430-1
The prompt has now been changed to: ECN430-1#
3.2
Changing Password
Command Usage:
This command is used to change the password for administrators and users of
the ECN switch.
The password for the Web user is not affected. Also use this command to
change or set the minimum length of the password, that is, the minimum
number of characters in the password. The minimum length value can be read
out by using the show command.
Command Level:
ecn(config system)#
Syntax:
password change factorydefault old <password> new
<password>
13
old <password>
new <password>
<length>
Default Settings:
Default minimum length of password is 6.
Examples:
ecn(config system)#password change factorydefault old
admin new 14inimda
ecn(config system)#password change old admin new 14inimda
3.2.1
3.3
14
<message>
{off | interval |
exclusive}
timer <time>
defaulttimer <time>
Default Settings:
Mode: off
For SNMP: exclusive
Timer: 300 s
Examples:
ecn(config)#cma mode interval
ecn(config)#cma timer 100
3.3.1
15
Use this command to display the configured parameters and gives information
about the actual configuration manager.
Command Level:
ecn#
Syntax:
show cma
Arguments:
None
Default Settings:
None
Examples:
ecn#show cma
3.4
When the NTP server is not running, the IP DSLAMs will not be able
to use the remote storage. For more information about the remote
storage function, please refer to the IP DSLAM User Guide.
Command Level:
ecn(config system)#
Syntax:
ntp client {enable|disable}
ntp server-ip <ip-address>
Arguments:
16
{enable | disable}
<ip-address>
Default Settings:
NTP client enabled
IP address: 0.0.0.0
Examples:
ecn(config system)#ntp server-ip 192.168.1.3
ecn(config system)#ntp client enable
3.4.1
3.5
17
Syntax:
calendar date <date> time <time>
Arguments:
argument
Explanation
<date>
<time>
Default Settings:
None
Note:
When the NTP server is not running, the IP DSLAMs will not be able
to use the remote storage. For more information about the remote
storage function, please refer to the IP DSLAM User Guide.
Examples:
ecn(config system)#calendar date 21.10.09 time 15:32:30
ecn(config system)#ntp server-ip 192.168.1.3
3.5.1
3.6
Ping a Node
Command Usage:
This command is almost identical to the ping command from Windows
command prompt. The only difference is that the command parameters cannot
18
be configured. The ping command will always use 56 bytes data packets (64
bytes total), and send the command 5 times.
Command Level:
ecn#
Syntax:
ping <ip-address>
Arguments:
<ip-address>
Default Settings:
None
Examples:
ecn#ping 172.30.38.1
The output will be as follows:
PING 172.30.38.1 (172.30.38.1): 56 data bytes
64 bytes from 172.30.38.1: icmp_seq=0 ttl=255 time=52.1
ms
64 bytes from 172.30.38.1: icmp_seq=1 ttl=255 time=2.0 ms
64 bytes from 172.30.38.1: icmp_seq=2 ttl=255 time=2.0 ms
64 bytes from 172.30.38.1: icmp_seq=3 ttl=255 time=2.0 ms
64 bytes from 172.30.38.1: icmp_seq=4 ttl=255 time=2.2 ms
--- 172.30.38.1 ping statistics --packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.0/12.0/52.1 ms
3.7
CLI Autologout
Command Usage:
Use this command to set an idle interval after which the CLI will logout
automatically. By default the CLI will log out after 5 minutes if there is no user
input. This command is used to set another idle timeout.
Command Level:*
ecn(config system)#
Syntax:
cli-autologout <time>
Arguments:
<time>
19
Default Settings:
5
Examples:
ecn(config system)#cli-autologout 30
3.7.1
3.8
0 minute(s)
Restarting Nodes
Command Usage:
Use this command to restart nodes in the EAN. The EFN324 does not support
reset-on-lan.
Command Level:
ecn#
Syntax:
restart {ecn|switching-unit|enc}
restart reset-on-lan node <node>
restart node {<node>|all}
Arguments:
20
ecn
switching-unit
Arguments:
enc
Default Settings:
None
Examples:
ecn#restart ecn
ecn#restart node all
3.9
<node>
{enable | disable}
21
Default Settings:
None
Examples:
ecn#led-test node 1.0 line enable
3.10
Default Settings:
None
Examples:
ecn(config system)#turn off sbc management-ip-address
172.30.3.1
3.11
22
Syntax:
rcli <node>
Arguments:
<node>
Default Settings:
None
Examples:
ecn#rcli 0.1
23
24
Configuring Interfaces
Configuring Interfaces
This section describes different commands used when installing and configuring
the ECN in the network.
4.1
25
internal
untagged
<vlan-id>
<ip-address>
<subnet-mask>
<prio>
<name>
{add | remove}
activate
Default Settings:
External Interface:
VLAN ID: 246
IP address: 0.0.0.0
Subnet mask: 255.255.255.0
Firewall-acl: none
Internal Interface:
VLAN ID: 247
IP address: 10.0.100.1
Subnet mask: 255.255.0.0
Untagged Interface:
26
Configuring Interfaces
4.1.1
255.255.0.0
255.255.255.0
Default Gateway:
172.31.133.1
27
4.2
4.2.1
Default Settings:
300
Examples:
ecn(config system)#config-autosave-timeout 180
28
Configuring Interfaces
4.2.1.1
4.3
300
Backup Configuration
Command Usage:
Use this command to initiate a backup of the configuration information from
the ECN (EMP) and the embedded elements. To restore the backup file use
the restore command.
The command stores configuration information on a FTP server or if no FTP
server is defined the backup file is placed locally in the directory: /var
Command Level:
ecn(config system)#
Syntax:
backup-configuration {ftp-server <name> filename
<filename>|filename <filename>|terminate}
Arguments:
<name>
29
Arguments:
<filename>
terminate
Default Settings:
None
Examples:
ecn(config system)#backup-configuration ftp-server ftp1
filename eda/backup/conf-backup-file
The command will store the configuration on the ftp1 server in the directory:
eda/backup directory and with the name conf-backup-file.
4.4
Restore Configuration
Command Usage:
Use this command to initiate a restore of the configuration information from the
ECN (EMP) and the embedded elements saved in a backup file. The backup
file is stored on a chosen FTP server or locally on the ECN in the directory:
/var. During the restore the ECN will restart, and the telnet connection to
the ECN will be lost.
Command Level:
ecn(config system)#
Syntax:
restore-configuration {ftp-server <name> filename
<filename>|filename <filename>|terminate}
Arguments:
<name>
30
Configuring Interfaces
Arguments:
<filename>
terminate
Default Settings:
None
Examples:
The following command will restore a configuration file with the name conf-back
up-file located on the ftp1 server in: eda/backup/conf-backup-file.
ecn(config system)#restore-configuration ftp-server ftp1
filename eda/backup/conf-backup-file
The following command will restore a configuration file with the name
conf-backup-file located on the ECN in: /var.
ecn(config system)#restore-configuration filename
conf-backup-file
ecn(config system)#restore-configuration terminate
4.5
Command Level:
ecn(config system)#
31
Syntax:
vmac domain <domain-value> network-element-id
<network-element-id>
vmac disable
Arguments:
<domain-value>
<network-element-id>
Default Settings:
None
Examples:
ecn(config system)#vmac domain 60 network-element-id 135
32
5.1
calendar
config-autosave-timeout
ftp-server
interface
local-management
ntp
password-length
pem-management
radius-server
service-vlans
33
Arguments:
{alarm-receiver |
configuration |
snmpv3-users}
software-versions
vlan-unaware
cli-autologout
vmac
Default Settings:
None
Examples:
ecn#show system calendar
34
Managing Software
Managing Software
The following commands are used in connection with installing and upgrading
software for the ECN and the embedded nodes.
6.1
<ip-address>
<username>
<password>
Default Settings:
None
Examples:
ecn(config system)#ftp-server add name ftp1 server-ip
172.30.30.3 username admin password qwertyui protocol ftp
ecn(config system)#ftp-server delete name ftp1
35
6.1.1
6.2
36
Managing Software
Syntax:
sw-upgrade {ftp-server <name> sw-path <path> control-file
<control-file>}
Arguments:
<name>
<path>
<control-file>
Default Settings:
None
Examples:
The following example will fetch the new.pk.zip control file on the ftp1 server
located in the directory under the root: eansw.
ecn(config system)#sw-upgrade ftp-server ftp1 sw-path
/upgrade/eansw control-file R10A02.zip
6.3
Updating EMP SW
Command Usage:
Use this command to install new software in the EMP. The command should be
executed after the SW has been uploaded to the ECN. The EMP will restart
automatically after the command is executed.
For more information about how to upload SW files please refer to the
installation guides for the ECNs.
Be careful when updating the fallback software. Only update to software that
has been used in the network, as it is important that the fallback software will
work.
Command Level:
ecn(config system)#
Syntax:
update software {enc|fallback}
37
Arguments:
{enc | fallback
Default Settings:
None
Examples:
ecn(config system)#update software enc
ecn(config system)#update software fallback
6.4
6.5
38
Managing Software
Command Level:
ecn(config system)#
Syntax:
clean-up-temporary-storage
Arguments:
None
Default Settings:
None
Examples:
ecn(config system)#clean-up-temporary-storage
39
40
Management Configuration
Management Configuration
Use these commands to configure SNMP management, local management
and EM-PEM management.
7.1
SNMP
Command Usage:
Use this command to configure the followings:
Command Level:
ecn(config system)#
Syntax:
snmp access {administrator|guest|public}{read-only|readwrite}
snmp add {admin-user <admin-username> authentication
{md5|sha} auth-passwd <auth-passwd> priv-passwd
<priv-passwd> | guest-user <guest-username> authentication
{md5|sha} auth-passwd <auth-passwd> | public-user
<pub-username>}
snmp alarm-receiver {add|remove} <ip-address>
snmp alarm-receiver statistics {add|remove} <ip-address>
snmp remove {admin-user|guest-user|public-user} <name>
41
42
{administrator | guest |
public}
{read-only | read-write}
<priv-passwd>
<guest-username>
<public-username>
{admin-user | guest-user |
public-user} <name>
{default | mac-address |
sys-name}
{snmpv2 | snmpv3}
Management Configuration
Arguments:
{none | read-only |
read-write}
{administrator | guest |
public}
Note:
Default Settings:
Table 4
Default Settings
Groups
(Context
name)
Access
Security
Level
Users (Pred
efined)
Password
Administrator
Read-write
User authen
tication and
encryption is
activated
PEM
auth: admini
strator
priv: administ
rator
Guest
Read-only
User authe
ntication is
activated
guest
auth: guesta
uth
Public
Read-only
No security
activated
anonymous
43
7.2
Local Management
Command Usage:
Use this command to control untagged management traffic from and to a port,
and direct traps to a local connected PC. The command enables or disables
untagged management traffic from one of the ports. Used before and after
uploading SW from the PC to the ECN. When lct-receiver is enabled the EMP
will forward SNMP traps to the PC. The type of the traps is defined by the type
argument. To send traps to another trap receiver, use the IP argument. Note
that if the local-trap lct-receiver is disabled and an IP address is defined, traps
will be sent only to the remote trap receiver specified by the IP address.
When local or global management is disabled, the port will be set back to the
default settings specified in Section 9.3 on page 52.
Command Level:
ecn(config system)#
Syntax:
local-management local-traps ip <ip-address>
local-management local-traps lct-receiver {enable|disable}
local-management local-traps local-traps type {1|2|3}
local-management snmp-communities read <string>
local-management snmp-communities set <string>
local-management port {<port>|disable}
Arguments:
44
<ip-address>
{enable | disable}
type {1 | 2 | 3}
read <string>
set <string>
Management Configuration
Default Settings:
port disable
lct-receiver enabled
ip 0.0.0.0
type 3
set : public
read: public
Examples:
ecn(config system)#local-management port 25
ecn(config system)#local-management local-traps
lct-receiver enable
ecn(config system)#local-management local-traps type 2
ecn(config system)#local-management snmp-communities read
public
7.3
EM-PEM Management
Command Usage:
Use this command to set the port for EM-PEM management or to disable
EM-PEM management. If EM-PEM management is enabled on a port, that port
is connected to the public management VLAN for untagged traffic. By default
the ECN does not allow untagged traffic through the uplink ports. VLAN 246
is configured as external management VLAN, so VLAN 246 is configured as
tagged VLAN on all uplink ports.
This means that incoming and outgoing traffic tagged with VLAN ID 246 can
pass these ports. If pem-management is enabled on one uplink port of the
ECN, VLAN 246 is configured as untagged on this port. This means that
untagged traffic running through that port is internally tagged with VLAN 246. A
host connected to this port sending and receiving untagged traffic (like a normal
PC) would appear like being connected to VLAN 246.
This function allows a PC to be connected to a port of the ECN and reach the
EM-PEM management VLAN.
When local or global management is disabled, the port will be set back to the
default settings specified in Section 9.3.1 on page 52.
Command Level:
ecn(config system)#
Syntax:
pem-management port {<port>|disable}
45
Arguments:
{<port> | disable}
Default Settings:
Disabled
Examples:
ecn(config system)#pem-management port disable
46
Configuring VLAN
Configuring VLAN
Use these commands to configure service VLAN and configure RADIUS and
TACACS Servers.
8.1
Service VLAN
Command Usage:
This command may be used to allow the use of the External management VLAN
for End-user traffic. When the command service-vlan use-management-vlan
enable is executed, it is allowed to define a service with the same VLAN ID
as the External Management VLAN.
Stop!
For security reasons it is highly recommended not to enable the External
management VLAN on the downlink ports (default).
Command Level:
ecn(config system)#
Syntax:
service-vlan use-management-vlan {enable|disable}
Arguments:
{enable | disable}
Default Settings:
Disabled
Examples:
ecn(config system)#service-vlan use-management-vlan enable
ecn(config system)#service-vlan use-management-vlan
disable
8.2
VLAN Unaware
Command Usage:
47
Use this command to enable or disable VLAN unaware mode of the switching
unit. When it is enabled, the ECN is transparent for all service and user VLANs.
VLAN tag is still considered for management traffic.
Command Level:
ecn(config system)#
Syntax:
vlan-unaware {enable|disable}
Arguments:
{enable | disable}
Default Settings:
Disabled
Examples:
ecn(config system)#vlan-unaware enable
48
ECN Configuration
ECN Configuration
Ethernet Controller Node commands. . The show command for all ECN
configurations is described in Section 9.15 on page 80.
9.1
External VLAN
Command Usage:
Use this command to add or remove external VLAN IDs and specify which ports
are tagged and untagged traffic. External VLANs can be used by third-party
products or other nodes outsite the EAN, connected to an auxialiary port. Rules
for external VLANs:
Command Level:
ecn(config)#
Syntax:
ecn external-vlan add vlan-id <vlan-id> [tagged-ports
<number>][untagged-ports <number>]
ecn external-vlan remove {vlan-id <id> ports <number>|all}
Arguments:
<vlan-id>
49
Arguments:
<number>
all
Default Settings:
No external VLANs are created.
Examples:
ecn(config)#ecn external-vlan add vlan-id 333 tagged-ports
1-10,18,19 untagged-ports 14,15
ecn(config)#ecn external-vlan remove vlan-id 333 all
9.2
Inventory Commands
Use these command to remove unreachable nodes from the inventory and
configure inventory polling interval.
9.2.1
all
Default Settings:
50
ECN Configuration
None
Examples:
ecn(config)#ecn inventory remove node 1.0
ecn(config)#ecn inventory remove all
9.2.2
<time>
<max-tries>
Default Settings:
interval: 30000
time: 1000
max-tries: 3
Examples:
ecn(config)#ecn inventory polling poll-interval 16000
timeout 800 max-tries 4
51
9.3
Port Commands
The spanning tree interface commands and how to configure a port as uplink,
downlink and auxiliary port are described in this section. The spanning tree
protocol commands are described in Section 9.4 on page 59.
9.3.1
Configuring Port
Command Usage
Use this command to configure the port as an uplink, downlink or auxiliary port.
For the ECN430 the command is used to configure a port as an uplink or a
downlink port. Trying to configure a downlink port on an ECN330 as an uplink
port will give a failure message. The command is used to enable or disable
service VLANs on a port and to withdraw one or more ports from the ordinary
EAN so the port(s) can be used for other purposes without the control from
EMP. An EMP disabled port is called an auxiliary switch port.
In general, all ports on the ECN can be disabled from the EMP. This includes
both uplink and downlink ports. However ports configured to other functions,
can not be disabled, and trying to do so will issue an error message.
The following ports can not be disabled:
The last port on ECN330 node used for (external) management; at least
one uplink port must be kept for management
52
ECN Configuration
{uplink | downlink |
auxiliary}
{default | vlans}
{enable | disable}
.The VLANs for the ECN430 are from factory disabled as shown in Table 5
on page 53.
Table 5
ECN430
ECN330
ECN320
Adm. Use
External
VLAN
Internal
VLAN
Service
VLAN
1 to 23
Downlink
Disabled
Disabled
Disabled
24 to 27
Uplink
Disabled
Disabled
Disabled
1 to 24
Downlink
Disabled
Enabled
Enabled
25 to 27
Uplink
Enabled
Disabled
Enabled
1 to 24
Downlink
Disabled
Enabled
Enabled
25 to 26
Uplink
Enabled
Disabled
Enabled
ECN430
ECN330
Adm. Use
External
VLAN
Internal
VLAN
Service
VLAN
1 to 23
Downlink
Disabled
Enabled
Enabled
24 to 27
Uplink
Enabled
Disabled
Enabled
1 to 24
Downlink
Disabled
Enabled
Enabled
25 to 27
Uplink
Enabled
Disabled
Enabled
53
ECN320
54
Port
Adm. Use
External
VLAN
Internal
VLAN
Service
VLAN
1 to 24
Downlink
Disabled
Enabled
Enabled
25 to 26
Uplink
Enabled
Disabled
Enabled
ECN Configuration
Examples:
ecn(config)#ecn port 27 adm-use uplink vlans external-mgmt
enable servicevlan enable
9.3.2
Spanning-tree Cost
Command Usage:
Use this command to configure the spanning tree path cost for the specified
interface. The command is used by the Spanning Tree Algorithm to determine
the best path between devices. Therefore, lower values should be assigned
to ports attached to faster media, and higher values assigned to ports with
slower media.
Command Level:
ecn(config)#
Syntax:
ecn port <port> spanning-tree cost <cost>
Arguments:
<port>
<cost>
Default Settings:
100.000
Examples
ecn(config)#ecn port 1 spanning-tree cost 20000
9.3.3
55
Command Level:
ecn(config)#
Syntax:
ecn port <port> spanning-tree edge-port {enable|disable}
Arguments:
<port>
{enable | disable}
Default Settings:
Disabled
Examples
ecn(config)#ecn port 1 spanning-tree edge-port disabled
9.3.4
56
ECN Configuration
Arguments:
<port>
{auto | point-to-point |
shared}
Default Settings:
Auto
Examples
ecn(config)#ecn port 1 spanning-tree link-type
point-to-point
9.3.5
{enable | disable}
Default Settings:
Disabled
Examples
57
9.3.6
<priority>
Default Settings:
128
Examples
ecn(config)#ecn port 1 spanning-tree port-priority 0
9.3.7
58
ECN Configuration
Arguments:
<port>
{enable | disable}
Default Settings:
Disabled
Examples
ecn(config)#ecn port 1 spanning-tree protocol-migration
enable
9.4
9.4.1
Default Settings:
15 seconds
Examples
ecn(config)#ecn spanning-tree forward-time 20
59
9.4.2
Default Settings:
2 seconds
Examples
ecn(config)#ecn spanning-tree hello-time 5
9.4.3
60
ECN Configuration
Arguments:
<seconds>
Default Settings:
20 seconds
Examples
ecn(config)#ecn spanning-tree max-age 40
9.4.4
Spanning-tree Mode
Command Usage:
Use this command to select the spanning tree mode for the ECN.
Spanning Tree Protocol
Uses RSTP for the internal state machine but sends only 802.1D BPDUs
(Bridge Protocol Data Units).
Rapid Spanning Tree Protocol
RSTP supports connections to either STP or RSTP nodes by monitoring the
incoming protocol messages and dynamically adjusting the type of protocol
messages the RSTP node transmits, as described below:
STP Mode - If the switch receives an 802.1D BPDU after a ports migration
delay timer expires, the switch assumes it is connected to an 802.1D bridge
and starts using only 802.1D BPDUs
Command Level:
ecn(config)#
Syntax:
ecn spanning-tree mode {rstp|stp}
Arguments:
{rstp | stp}
61
Default Settings:
RSTP
Examples
ecn(config)#ecn spanning-tree mode rstp
9.4.5
Default Settings:
Long
Examples
ecn(config)#ecn spanning-tree path-cost-method long
9.4.6
Spanning-tree Priority
Command Usage:
Use this command to configure the spanning tree priority globally for the ECN.
Bridge priority is used in selecting the root device, root port, and designated
port. The device with the lowest priority becomes the STA root device.
However, if all devices have the same priority, the device with the lowest MAC
address will become the root device.
Command Level:
ecn(config)#
Syntax:
ecn spanning-tree priority <priority>
62
ECN Configuration
Arguments:
<priority>
Default Settings:
32.768
Examples
ecn(config)#ecn spanning-tree priority 16384
9.4.7
Default Settings:
Disabled
Examples
ecn(config)#ecn spanning-tree status disable
9.4.8
63
Syntax:
ecn spanning-tree transmission-limit <seconds>
Arguments:
<seconds>
Default Settings:
3 seconds
Examples
ecn(config)#ecn spanning-tree transmission-limit 4
9.5
Link Aggregation
Command Usage:
Use this command to configure a trunk of several ports that can be used as
a single link.
The command is only used for ECN320 and ECN330.
Link aggregation in ECN430 is configured with the switch CLI (RCLI). For
more information about link aggregation in ECN430 please refer to ECN430
Switch/EMN120 CLI User Guide and the ESN212 and ESN204g CLI User
Guide.
Ports can be statically grouped into an aggregation link (that is a trunk) to
increase the bandwidth of a network connection or to ensure fault recovery. For
example, a trunk consisting of two 1000 Mbps ports can support an aggregated
bandwidth of 2 Gbps when operating at full duplex.
The ECN320 supports up to six active trunks and ECN330 supports up to 13
active trunks.
A port can only join a trunk if the configuration of the port (port settings, VLAN,
QoS) matches the configuration of the trunk.
On uplink ports either the Link Aggregation Control Protocol (LACP, IEEE
802.3ad) can be used to automatically negotiate a trunk link between the ECN
and another network device or a static trunk can be configured. For LACP
trunks, the switches have to comply with LACP. For static trunks the switches
have to comply with the Cisco EtherChannel standard.
When link aggregation is configured on the downlink ports it must be configured
in the EDN312x as well in order to work. The EDN312x is in the Inventory
regarded as connected to the primary port, thus it is edn node a.0 where a is the
primary port number which need to have the link-configuration set to link-aggr.
Command Level:
ecn(config)#
64
ECN Configuration
Syntax:
ecn link-aggregation create-trunk primary <primary>
secondary <secondary>
ecn link-aggregation remove-trunk primary <primary>
ecn link-aggregation uplink {lacp|static} primary <primary>
secondary <secondary>
ecn link-aggregation uplink off
Arguments:
create-trunk
<primary>
<secondary>
remove-trunk
uplink off
Default Settings:
None
Examples:
ecn(config)#ecn link-aggregation create-trunk primary 1
secondary 2
ecn(config)#ecn link-aggregation uplink static primary 26
secondary 27
65
9.6
Redundancy
The EAN redundancy is achieved by using EDN312x (containing two 100
Mbps uplinks) and an expansion kit. The expansion kit contains an extra
ECN. One ECN is configured as Active, while the other ECN is configured
as Standby. During normal operation, all data and management traffic goes
through the active ECN. When either the active ECN, the uplink connecting
it to the network, or the link between the ECN and the EDN312x fails, the
EDN312x will go over to unmanaged state, and all the End-user data will be
directed through the standby ECN.
Note:
Command Level:
ecn(config)#
Syntax:
ecn redundancy work-mode {active|standby}
Arguments:
{active | standby}
Default Settings:
Active
Examples:
ecn(config)#ecn redundancy work-mode standby
9.7
Unmanaged Switch
Command Usage:
Use this command to add or remove an unmanaged switch.
The unmanaged-switch function is used to enable the ECN port for a 3rd party
switch. Valid ECN ports are port 1 to 24.
The 3rd party switch must be configured with the value listed in Table 7 on
page 67. For more detailed information for configuration please refer to the
3rd party switch user guides.
Note:
The configuration must be done through the console port of the 3rd
party switch and the 3rd party switch must comply with RFC1493.
Command Level:
ecn(config)#
Syntax:
66
ECN Configuration
<port>
<ip-address>
Default Settings:
None
Table 7
Parameter
Value
Netmask
255.255.0.0
Gateway
10.0.100.1
Admin VLAN
247
SNMP
Enabled
VLAN Information
VID: 247
All ports must be added as members.
Community String
Public
10.0.100.1
67
Figure 1
9.8
Unmanaged Node
Command Usage:
Use this command to add or remove an unmanaged node connected to an
embedded ESN212 to the inventory of the ECN.
Only RSC96 Power Supply System can be used as an unmanaged node. For
detailed information about this implementation please refer to Adding Power
One RSC96 to EAN guide in the Solution Descriptions folder.
The command configures the ECN to recognize the unmanaged node
connected to a specific port of an embedded ESN212.
Only internal IP address can be used for an unmanaged node.
The IP address must be unique within the EAN, but can be reused in another
EAN.
The unique identification of the unmanaged node is the combination of ECN
IP Address + Node ID in the traps.
68
ECN Configuration
The CLI is the only way to configure (add/remove) and readout, the connection
between ESN212 and the unmanaged node.
The unmanaged node must be configured as described in the guide: Adding
Power One RSC96 to EAN.
Command Level:
ecn(config)#
Syntax:
ecn unmanaged-node add node <a.b> ip <ip-address>
ecn unmanaged-node remove node <a.b>
Arguments:
{add | remove}
<a.b>
<ip-address>
Default Settings:
None
Examples:
Connect unmanaged node with IP-address 10.0.0.55 to port 9 of ESN212 with
ID 1002.
ecn(config)#ecn unmanaged-node add node 1002.9 ip
10.0.0.55
ecn(config)#ecn unmanaged-node remove node 1002.9
9.9
69
Command Level:
ecn(config)#
Syntax:
ecn unmanaged-node polling <oid>
Arguments:
<oid>
Default Settings:
oid = 1.3.6.1.2.1.1.2 (the default sysObjectID OID).
Examples:
ecn(config)#ecn unmanaged-node polling 1.3.6.1.2.1.1.2
9.10
Default Settings:
Version = 1
Examples:
ecn(config)#ecn unmanaged-node snmp-version 1
9.11
70
ECN Configuration
the ECN switch CLI user Guide for more information about how to configure
the switch as IGMP proxy. The IGMP proxy is disabled per default in the
ECN330 and ECN430.
9.11.1
Default Settings:
Enabled
Examples:
ecn(config)#ecn ip igmp snooping querier enable
9.11.2
Default Settings:
71
9.12
Switch Extension
Command Usage:
Use this command to add or remove a switch extension to the inventory of the
ECN (add or remove an ESN310, ECN320 in ESN310 switch, ECN330 switch,
ECN330a switch or ESN410 switch). The command is not used in the ECN430.
This command can also be used to enable or disable service VLAN
configurations on the interconnecting ports (11 and 12) on ESN410 extension
switches.
Executing the command:
1. Adds the switch to the ECN inventory.
2. For the first switch added (node 0.1), the ECN uplink-port status changes
to EMP enabled internal. This applies for all extension switch types,
except 410-uplink, where the port status is changed to EMP enabled
internal-external.
As a consequence of the command execution:
3. All service VLANs from the extension switch(es) are configured on the
uplink ports when these are in use (unless the ecn switch-extension
interconnection-esn410 service-vlan disable command has been used).
4. Internal management VLANs (247 and 248) are configured on the ECN
uplink port.
The switch must be configured with the values listed in Table 8 on page 72.
For more detailed information about configuring the switch refer to section 4 on
page 152 and to the ESN310 User Guide and the ECN User Guide.
Note:
Table 8
72
Parameter
Value
10.0.0.1 to 10.0.0.254
ECN Configuration
Parameter
Value
Netmask
255.255.0.0
Gateway
10.0.100.1
Management VLAN
247 tagged
248 untagged
SNMP
Enabled
VLAN Information
VID: 247
Community String
Public
10.0.100.1
NTP Server
10.0.100.1
Ingress-filtering (ESN410)
Enabled
Command Level:
ecn(config)#
Syntax:
ecn switch-extension add <switch-type> remote-uplink-port
<port> ip <ip-address>
ecn switch-extension remove <node-no>
ecn switch-extension interconnection-esn410 service-vlan
{enable|disable}
Arguments:
{add | remove}
73
Arguments:
<switch-type>
<port>
74
ECN Configuration
Arguments:
<ip-address>
<node-no>
{enable | disable}
Default Settings:
Service VLAN configuration on port 11 and 12 is enabled on ESN410 extension
switches.
Example 1:
Add three daisy chained ESN310 switches, see Figure 2 on page 75.:
Figure 2
75
The switch extension can be added to the ECNs inventory before the
connection between the ECN and the extended switch is established.
However, the extended switch will be unreachable until it is connected.
The connection between the ECN and the extended switch has to be
unreachable before it is possible to remove the switch extension.
If all the extension switches are removed, the uplink port of the ECN330 is
reconfigured to allow traffic only on the external management VLAN.
The second and third switch extensions can also be added without specifying
the port:
ecn(config)# ecn switch-extension add esn310 ip 10.0.0.2
ecn(config)# ecn switch-extension add esn310 ip 10.0.0.3
Example 2:
Add three ESN410 switches and disable service VLANs on the interconnecting
links, see Figure 3 on page 77:
76
ECN Configuration
Figure 3
77
Figure 4
Table 9
78
Exampl
e
First Extension
Switch Type
2 or More
Extension
Switches
Disable Service
VLANs
ESN410
ESN410
No
ESN410
ESN410
Yes
ESN410-uplink
ESN410
No
ECN Configuration
9.13
Exampl
e
First Extension
Switch Type
2 or More
Extension
Switches
Disable Service
VLANs
ESN410-uplink
ESN410
Yes
ESN410-uplink
ESN410
No
Auto Rediscover
Command Usage:
The command is used to configure the automatic rediscovery function. Normally
elements are discovered though an initial DHCP sequence. But under more
special circumstances, for example when an ECN is replaced, elements having
a separate power supply, may not detect this and do a new DHCP-request. The
element will thus not be discovered by ECN and remain unmanaged until next
DHCP renewal (up to 24 hours) although it carries traffic. To circumvent this, a
ping is periodically broadcasted to discover such ghost embedded elements
To discover ghost-elements a ping is broadcasted out on the internal
management VLAN (default 247). If a ping response is received from an
element (IP address) not known in the current inventory in the EMP, a
reset-on-lan is sent, which in turn will make the element restart and run a
normal DHCP-discover sequence that makes it known to the EMP.
Command Level:
ecn(config)#
Syntax:
ecn auto-rediscover state {enable|disable}
ecn auto-rediscover interval <1-60>
Arguments:
{enable | disable}
<1-60>
Default Settings:
State: Enabled
Interval: 5 minutes
Examples:
ecn(config)#ecn auto-rediscover state disable
9.14
79
{<string> | none}
Default Settings:
None
Examples:
ecn(config)#location node 1.0 location Paris
ecn(config)#location node 1.0 location none
9.15
Show ECN
Command Usage:
This command is used to display the different configuration and status in the
ECN.
Command Level:
ecn#
Syntax:
show ecn {external-vlan {tag|vlan-id <id>|port
<port>}|inventory|link-aggregation|polling|port <port> span
ning-tree|redundancy|spanning-tree|ip| switchextension|
switch-ports|auto-rediscover|unmanaged-node| location}
ecn auto-rediscover interval <1-60>
Arguments:
external-vlan tag /
vlan-id <id> / port
<port>
80
ECN Configuration
Arguments:
inventory
link-aggregation
polling
redundancy
spanning-tree
ip
switch-extension
switch-ports
auto-rediscover
Unmanaged-node
location
Default Settings:
None
Interval: 5 minutes
Examples:
ecn#show ecn inventory
ecn#show ecn port 4 spanning-tree
81
82
EDN Commands
10
EDN Commands
Use these commands to configure the uplink of an embedded IP DSLAM.
.
10.1
Uplink Configuration
Command Usage:
The command will configure the IP DSLAM to use link redundancy or link
aggregation.
Command Level:
ecn(config)#
Syntax:
edn <node> link-configuration <secondary>
{single-link|redundancy|link-aggr}
Arguments:
<node>
single-link
redundancy
link-aggr
Default Settings:
None
Examples:
ecn(config)#edn 1.0 link-configuration single-link
83
10.2
Default Settings:
None
Examples:
ecn#show edn 1.0 link-configuration
84
11
11.1
{downstream | upstream}
85
Arguments:
86
data-rate-alarm-threshold
<bitrate>
impulse-noise-protection
min-bit-rate <min-bit-rate>
max-bit-rate <max-bit-rate>
Arguments:
interleave-delay <time>
power-down-mode {enable |
disable}
For more information about the line parameters refer to the EMP Web Interface
User Guide.
Default Settings:
Table 10
Upstream
32 kbps
32 kbps
512 kbps
256 kbps
Interleave delay
20 ms
20 ms
Disabled
87
11.2
88
dmt-carrier-mask
<mask>
delta-psd-annex-1
<delta-psd-annex-1>
delta-psd-annex-m
<delta-psd-annex-1>
delta-psd-normal
<delta-psd-normal>
delta-psd-plus
<delta-psd-plus>
max-snr-margin
<margin>
max-rx-power
<receiver-power>
89
Arguments:
90
upstream max-tx-power
<transmit-power>
delta-psd-plus
<delta-psd-plus>
downstream max-tx-power
<transmit-power>
min-snr-margin
<margin>
min-downshift-margin
<margin>
min-downshift-time
<time>
min-upshift-margin
<margin>
min-upshift-time
<time>
rate-adaption-mode
{fixed | adapt-at-startup |
adapt-at-runtime}
Arguments:
state
{enable | disable}
target-snr-margin
<target-snr-margin>
transmit-psd
{fixed | priority-to-power |
priority-to-rate}
prm-protection
{disable | 12khz | 16khz}
tssi-shape no-of-breakpoints
<no-of-breakpoints>
91
Arguments:
breakpoints
<breakpoints>
auto-configuration
{enable | disable}
tssi-shape adsl2-protocol
<protocol>
92
Arguments:
tx-filter-id
<tx-filter-id>
hs-tx-psd
For more information about the parameters refer to the EMP Web Interface
User Guide.
93
Default Settings:
Table 11
Parameter
Downstream
Upstream
6.0 dB
6.0 dB
6.0 dB
6.0 dB
0.0 dB
0.0 dB
Adapt-at-startup
Adapt-at-startup
Minimum downshift
margin
0 dB
0 dB
0s
0 dB
0 dB
0s
0s
Transmit-psd
Fixed
PRM protection
Disable
Disable
Auto-configuration
Disable
Disable
State
Disable
Disable
Note:
Examples:
ecn(config)#dslport 1.0.1 line downstream dmt-carrier-mask
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFF delta-psd-annex-1 -200
max-snr-margin 1 min-downshift-margin 1 min-downshift-time
1 rate-adaption-mode disable target-snr-margin 1
ecn(config)#dslport 1.0.1 line downstream max-snr-margin
9 min-downshift-margin 1 min-downshift-time 400
min-upshift-margin 6 min-upshift-time 400
ecn(config)#dslport 1.0.1 line downstream transmit-PSD
fixed
11.3
94
The uplink port of the ESN108 can supply the uplink node with power over the
Ethernet cable. The ability to supply a node with power over the Ethernet cable
in the upstream direction can be enabled by the ECN by this command. It
can be disabled or set to auto as well.
Command Level:
ecn(config)#
Syntax:
dslport <dslport> performance-data reset-counters
Arguments:
<dslport>
performance-data
reset-counters
Default Settings:
None
Examples:
ecn(config)#dslport 1.0.1 performance-data reset-counters
11.4
PVC Commands
Use these commands to configure PVC parameters.
Table 12
pvc general
pvc atm
pvc bandwidth
pvc ethernet
pvc ip
Specify IP parameters
95
11.4.1
pvc remove
pvc vlan
96
ta-rate-low-power-state][downstream-maximum-interleave-del
ay][downstream-actual-interleave-delay][upstream-actual-da
ta-rate][upstream-minimum-data-rate][upstream-attainable-d
ata-rate][upstream-maximum-data-rate][upstream-minimum-dat
a-rate-low-power-state][upstream-maximum-interleave-delay
][upstream-actual-interleave-delay]}}]
Arguments:
<dslport>
<variable>
pvc <pvc>
cpe-access-method
<access-method>
97
Arguments:
relay-agent-remoteid-conf
iguration
<method>
relay-agent-circuitid-con
figuration
<method>
relay-agent-remoteid-str
ing
<string>
98
Arguments:
relay-agent-circuitid-st
ring
<string>
relay-agent-options
<string>
Default Settings:
cpe-access-method: DHCP
relay-agent-configuration: Not used
relay-agent-options: None
Examples:
ecn(config)# dslport 1.0.1 pvc 1 general cpe-access-method
dhcp relay-agent-configuration 4 relay-agent-string user1of-netservice relay-agent-options adsl-transmission-system
downstream-actual-data-rate upstream-actual-data-rate
11.4.2
99
Command Level:
ecn(config)#
Syntax:
dslport <dslport> pvc <pvc> atm [atm-service-class <class>]
[upstream-policing {enable|disable}] [vci <vci>] [vpi
<vpi>]
Arguments:
<dslport>
<pvc>
<class>
upstream-policing
{enable | disable}
<vci>
<vpi>
Default Settings:
atm-service-class: UBR
100
upstream-policing: Disabled
vpi: 0
vci: X+31, 32 for PVC 1, 33 for PVC 2, 34 for PVC 3 and so on.
Examples:
ecn(config)# dslport 1.0.1 pvc 1 atm atm-service-class ubr
upstream-policing enable vpi 1 vci 32
11.4.3
bandwidth
{downstream | upstream}
<pvc>
<size>
101
Arguments:
peak-cell-rate
<vci>
sustainable-cell-rate
<speed>
Default Settings:
None.
Examples:
ecn(config)# dslport 1.0.1 pvc 1 bandwidth downstream
max-burst-size 1 peak-cell-rate 32 sustainable-cell-rate
32
11.4.4
If both MAC forced forwarding and local switching are enabled, MAC forced
forwarding has precedence, and local switching will not be used.
Command Level:
ecn(config)#
102
Arguments:
<dslport>
<pvc>
mac-forced-forwarding
{enable | disable}
<mac-address-count-limit>
local-switching
{enable | disable}
Syntax:
dslport <dslport> pvc <pvc> ethernet
[ac-forced-forwarding {enable|disable}]
mac-address-count-limit <mac-address-count-limit>]
[local-switching {enable|disable}]
Default Settings:
mac-forced-forwarding: disabled.
mac-address-count-limit: 0
local-switching: enabled
Examples:
ecn(config)# dslport 1.0.1 pvc 1 ethernet mac-forced-forw
arding enable mac-address-count-limit 10 local-switching
disable
11.4.5
PVC IP Parameters
Command Usage:
Use this command to enable the subscriber to broadcast traffic on the VLAN,
to enable IGMP snooping, to add or remove one or more static IP addresses
and a default gateway.
Command Level:
ecn(config)#
Syntax:
103
<pvc>
broadcast allowed
{enable | disable}
default-gateway
<ip-address>
igmp-snooping
{enable | disable}
static-ip
{add | remove}
<ip-address>
Default Settings:
igmp-snooping: enabled.
broadcast-allowed: disabled
Examples:
ecn(config)# dslport 1.0.1 pvc 1 ip broadcast-allowed
enable default-gateway 192.168.1.1 igmp-snooping enable
static-ip add 192.168.1.3
11.4.6
Removing a PVC
Command Usage:
This command is used to remove a specified PVC.
Command Level:
ecn(config)#
Syntax:
dslport <dslport> pvc <pvc> remove
104
Arguments:
<dslport>
<pvc>
remove
Default Settings:
None
Examples:
ecn(config)# dslport 1.0.1 pvc 1 remove
11.4.7
The VLAN will be configured on all ports of the ECN (both downlink and uplink)
and on all ports of daisy chained switch extensions.
Stop!
Do not use any of the VLAN IDs that are used for management. Apart from the
configurable management VLANs (246, 247, 248, and 249), VLANs 1 and
4093 are used internally in the ECN.
Command Level:
ecn(config)#
Syntax:
dslport <dslport> pvc <pvc> vlan [ethernet-priority
<priority>] vlan-id <vlan-id>
105
Arguments:
<dslport>
<pvc>
<priority>
<vlan-id>
Default Settings:
ethernet-priority: 0
Examples:
ecn(config)# dslport 1.0.1 pvc 1 vlan ethernet-priority 1
vlan-id 3
106
11.5
<mode>
Note:
107
Numbers:
108
Range
Mode
01
AUTODETECT
AUTO ADSL1
AUTO ADSL2
ANSI T1.413
10
11
12
13
14
15
16
18
Auto Annex A
19
20
21
Names:
Range
Name
01
autodetect
auto_adsl1
auto_adsl2
ansi_t1.413
etsi_ts_101_388
itu-t_adsl_over_pots,_g.992.1_annex_a
itu-t_adsl_over_isdn,_g.992.1_annex_b
itu-t_adsl_lite_over_pots,_g.992.2_annex_a
itu-t_adsl2_over_pots,_g.992.3_annex_a
10
itu-t_adsl2_over_isdn,_g.992.3_annex_b
11
itu-t_re-adsl2_over_pots,_g.992.3_annex_a_and_l
12
itu-t_re-narrow_psd_adsl2_over_pots,_g.992.3_annex_a_and_l
13
itu-t_adsl2,_g.992.3_annex_m
14
itu-t_adsl2+_over_pots,_g.992.5_annex_a
15
itu-t_adsl2+_over_isdn,_g.992.5_annex_b
16
itu-t_adsl2+,_g.992.5_annex_m
18
auto_annex_a
19
itu-t_vdsl2,_g.993.2
20
itu-t_adsl2,_g.992.3_annex_j
21
itu-t_adsl2+,_g.992.5_annex_j
Default Settings:
Autodetect
Examples:
ecn(config)#dslport 1.0.1 configurable-auto-transmission
-mode 6 8
11.6
109
basis, except for ADSL over ISDN. If ADSL over ISDN is used, all lines of the
same IP DSLAM are set to ADSL over ISDN.
Choosing AUTO ADSL1 or AUTO ADSL2 will let the IP DSLAM to decide which
access method is appropriate. ADSL1 includes a bunch of ADSL CPE access
methods. ADSL2 includes bunch of ADSL2 and ADSL2+ CPE access methods.
The list of modes defined by this command overwrites any previous allowed
mode. That is, only the modes included in the last entered command will be
allowed.
ITU-T G992.3 Annex J and G.992.3 Annex M cannot be used in the same
command, they exclude each other.
ITU-T G992.5 Annex J and G992.5 Annex M cannot be used in the same
command, they also exclude each other.
If other groups of transmission modes are needed, use the command:
configurable-auto-transmission-mode instead, see Section 11.5 on
page 107.
Note:
Command Level:
ecn(config)#
Syntax:
dslport <dslport> transmission-mode <mode> [<mode>][<mode
>]......[<mode>]
Arguments:
<dslport>
<mode>
Numbers:
110
Range
Mode
01
AUTODETECT
AUTO ADSL1
AUTO ADSL2
ANSI T1.413
Numbers:
Range
Mode
10
11
12
13
14
15
16
18
Auto Annex A
19
20
21
111
Names:
Range
Name
01
autodetect
auto_adsl1
auto_adsl2
ansi_t1.413
etsi_ts_101_388
itu-t_adsl_over_pots,_g.992.1_annex_a
itu-t_adsl_over_isdn,_g.992.1_annex_b
itu-t_adsl_lite_over_pots,_g.992.2_annex_a
itu-t_adsl2_over_pots,_g.992.3_annex_a
10
itu-t_adsl2_over_isdn,_g.992.3_annex_b
11
itu-t_re-adsl2_over_pots,_g.992.3_annex_a_and_l
12
itu-t_re-narrow_psd_adsl2_over_pots,_g.992.3_annex_a_and_l
13
itu-t_adsl2,_g.992.3_annex_m
14
itu-t_adsl2+_over_pots,_g.992.5_annex_a
15
itu-t_adsl2+_over_isdn,_g.992.5_annex_b
16
itu-t_adsl2+,_g.992.5_annex_m
18
auto_annex_a
19
itu-t_vdsl2,_g.993.2
20
itu-t_adsl2,_g.992.3_annex_j
21
itu-t_adsl2+,_g.992.5_annex_j
Arguments, cont.:
<priority>
<vlan-id>
Default Settings:
Autodetect
Examples:
ecn(config)# dslport 1.0.1 transmission-mode 2 3
112
11.7
Command Level:
ecn(config)#
Syntax:
dslport <dslport> vdsl-psd {downstream|upstream}
adv-power-back-off {enabled|disabled}
dslport <dslport> vdsl-psd downstream esel <length> escma
<model> escmb <model> escmc <model> fmax <min-freq> fmin
<max-freq> min-esel <min-esel> mus <min-mask>
dslport <dslport> vdsl-psd upstream power-back-off
{enable us1a <us> us1b <us> us2b <us> us3a <us> us3b <us>
forced-e-length <e-length>}
dslport <dslport> vdsl-psd masks {mib-downstream|mib-upst
ream} {add carrier-index <index> psd-level <level>|delete
carrier-index <index> psd-level <level>|show}
dslport <dslport> vdsl-psd masks carrier-mask {add
start-carrier <integer> stop-carrier <integer>|delete
start-carrier <integer> stop-carrier <integer>|show}
dslport <dslport> vdsl-psd masks notch {add start-carrier
<start-carrier> stop-carrier <stop-carrier>|delete start-car
rier <start-carrier> stop-carrier <stop-carrier>|show}
dslport <dslport> vdsl-psd limit-mask {A_NUS0_PSD|A_EU_32_P
SD|A_EU_36_PSD|A_EU_40_PSD|A_EU_44_PSD|A_EU_48_PSD|A_EU_52
_PSD|A_EU_56_PSD|A_EU_60_PSD|A_EU_64_PSD|EX_ANSI_M1_PSD|EX
_ANSI_M2_PSD|CAB_ANSI_M1_PSD|CAB_ANSI_M2_PSD|EX_ANSI_M1e_P
SD|EX_ANSI_M2e_PSD|CAB_ANSI_M1e_PSD|CAB_ANSI_M2e_PSD|B8_1_
PSD|B8_2_PSD|B8_3_PSD|B8_4_PSD|B8_5_PSD|B8_6_PSD|B8_7_PSD|
B8_8_PSD|B8_9_PSD|B8_10_PSD|B8_11_PSD|B7_1_PSD|B7_2_PSD|
B7_3_PSD|B7_4_PSD|B7_5_PSD|B7_6_PSD}
dslport <dslport> vdsl-psd max-power-down <maximum-power-d
ownstream>
dslport <dslport> vdsl-psd profile-enabling {8a|8b|8c|8d|
12a|12b|17a}
113
Arguments:
All parameters in this command are described in detail in the EMP Web
Interface User Guide. The range for maximum power downstream is -25.6 to
25.6 dBm, though it must not exceed the power defined in the standard for the
selected profile in the profile-enabling parameter. Note that 8a and 8b are not
supported for the EDN612nef although they can be checked without receiving
any failure message.
Note:
Default Settings:
MIN-ESEL: 0
ESEL: 127
ESCMA: -0.90234375
ESCMB: -0.1015625
ESCMC: 1.296875
FMAX: 2992
FMIN: 0
MUS: -11
US1A: -80.0
US1B: -31.0
US2A: 0.0
US2B: 0.0
US3A: 0.0
US3B: 0.0
Forced-e-Length: 120
Power-Back-Off: Enabled
Advanced-Power-Back-Off: Disabled
MIB Mask Downstream:
114
Carrier Index
PSD-Level
125
-25
130
-10
PSD-Level
120
-11
RFI Notches:
Start Carrier
Stop Carrier
125
126
11.8
to {<dslport> all}
Default Settings:
None.
Examples:
ecn(config)#copy-dslport from 1.0.1 to 1.0.2
115
11.9
Default Settings:
None.
Examples:
ecn#test dslport 14.0.2 loop-diagnostic
116
11.10
Alarm Thresholds
Command Usage:
Use this command to set threshold values that will determine when an alarm is
sent telling that a major or critical error affects the system.
Command Level:
ecn(config)#
Syntax:
dslport <dslport> alarm-threshold {downstream|upstream}
{es-15-minutes|ses-15-minutes|uas-15-minutes|es-24-hours|
ses-24-hours|uas-24-hours}
<interval>
Arguments:
<dslport>
{downstream | upstream}
es-15-minutes
ses-15-minutes
uas-15-minutes
es-24-hours
117
Arguments:
ses-24-hours
uas-24-hours
<interval>
Note:
Setting the threshold value to 0 (zero) will disable the alarm. The 15
minutes always start at 0,15, 30 and 45 minutes after the hour (start
time is line initialization). The 24 hours interval start at line initialization,
and is synchronized with the 15 minutes interval.
Default Settings:
None
Examples:
ecn(config)#dslport 1.0.1 alarm-thresholds downstream
es-15-minutes 1 uas-15-minutes 1 ses-15-minutes 1
11.11
118
Arguments:
<dslport>
line-initialization-failure
{enable | disable}
link-up-down {enable |
disable}
Default Settings:
Disabled
Examples:
ecn(config)#dslport 1.0.1 alarms line-initialization
-failure enable link-up-down enable
11.12
alarm
line
119
Arguments:
performance-data
psd line
status line
vdsl-psd
pvc
Default Settings:
None.
Examples:
ecn#show dslport 1.0.1 alarm
ecn#show dslport 1.0.1 pvc 1
120
ESN Commands
12
ESN Commands
Use these commands to configure embedded switches (ESN nodes) including
the built-in ECN switch.
.
12.1
Link Aggregation
Command Usage:
The command is used to configure a link aggregation trunk for the ESN310
switch or the ECN switch. It is available for downlink ports only.
Command Level:
ecn(config)#
Syntax:
esn <node> link-aggregation create-trunk primary <port>
secondary <port>
esn <node> link-aggregation remove-trunk primary <port>
Arguments:
<node>
primary <port>
secondary <port>
Default Settings:
Disabled
Examples:
ecn(config)#esn 0.1 link-aggregation create-trunk primary
8 secondary 12
ecn(config)#esn 0.1 link-aggregation remove-trunk primary
8
121
12.2
12.2.1
<port>
<phy-mode>
Default Settings:
Auto-negotiation
Examples:
ecn(config)#esn 1.0 port 5 phy-mode auto-negotiation
ecn(config)#esn 5.0 port 8 phy-mode 100-mbps-full-duplex
12.2.2
Spanning-tree
The spanning tree port commands are the same as mentioned in Section 9.3
on page 52.
12.2.3
Spanning-tree Protocol
The spanning tree protocol commands are the same as mentioned in Section
9.4 on page 59.
122
ESN Commands
12.2.4
Default Settings:
Disabled
Examples:
ecn(config)#esn 3.0 power-on-uplink enable
123
124
EXN Commands
13
EXN Commands
Use these commands to configure and show EXN104 lines.
.
13.1
<line>
{enable | disable}
{master | slave}
{disable | line-loop}
Default Settings:
None
Examples:
ecn(config)#exn 3.100 line 3 state enable
ecn(config)#exn 3.100 line 3 sync master
ecn(config)#exn 3.100 line 3 test line-loop
13.2
125
Command Level:
ecn(config)#
Syntax:
exn <node> line-type {esf|d4|e1|e1crc|auto-crc}
Arguments:
<node>
{esf | d4 | e1 | e1crc |
auto-crc}
Default Settings:
None
Examples:
ecn(config)#exn 3.100 line-type e1
13.3
{enable | disable}
Default Settings:
None
126
EXN Commands
Examples:
ecn(config)#exn 3.100 packet-distribution enable
13.4
general
line
Default Settings:
None
Examples:
ecn#show exn 3.100 general
ecn#show exn 3.100 line
127
128
EFN Commands
14
EFN Commands
Use these commands to configure EFNs.
14.1
EFN324 Commands
Use these commands to configure and view line state for a port on an
embedded EFN324. The command is only valid for the EFN324.
.
14.1.1
{unlock | lock}
Default Settings:
Unlocked
Examples:
ecn(config)#ethport 1035.0.3 line state lock
14.1.2
129
Command Level:
ecn#
Syntax:
show ethport <portno> {line|performance-data line|status
line}
Arguments:
<portno>
line
performance-data line
status line
Default Settings:
None
Examples:
ecn#show ethport 1035.0.3 line
ecn#show ethport 0.3 performance-data line
130
Alarms
15
Alarms
Use these commands to configure and display alarms from the EAN.
15.1
Alarm Filter
Command Usage:
Use this command to define entries in the alarm filter that will exclude a specific
alarms from being shown in the LCT and from being forwarded to an alarm
receiver (the add option), or to including an alarm that has been excluded (the
remove option).
Alarm oid defined in the filter will not be processed by the ECN. That is they will
be discarded upon arrival to the EMP.
Command Level:
ecn(config)#
Syntax:
alarm filter {add|remove} oid <alarm oid>
Arguments:
{add | remove}
<alarm oid>
Default Settings:
Linkup and linkdown are included in the filter (can be removed). OIDs:
1.3.6.1.6.3.1.1.5.3
1.3.6.1.6.3.1.1.5.4
Examples:
ecn(config)#alarm filter add oid 1.3.6.1.4.1.193.72.300.1
0.2.1.0.1
15.1.1
131
Syntax:
show alarm filter
Arguments:
None
Default Settings:
None
Examples:
ecn#show alarm filter
The output will be:
Alarm Filters:
1.3.6.1.6.3.1.1.5.3
1.3.6.1.6.3.1.1.5.4
15.2
<alarm oid>
Default Settings:
ifLinkup and iflinkdown are included in the filter (can be removed). OIDs:
1.3.6.1.4.1.193.72.600.1.6.0.3
1.3.6.1.4.1.193.72.600.1.6.0.4
Examples:
132
Alarms
15.2.1
15.3
Active Alarms are only synchronized for the following node types:
EDN612
EDN312x
EDN524
Command Level:
ecn(config)#
133
Syntax:
alarm active-alarm-log synchronize {enable|disable}
Arguments:
{enable | disable}
Default Settings:
Disabled
Examples:
ecn(config)#alarm active-alarm-log synchronize enable
15.3.1
134
Port No.
Status
Component
Active Alarm
Status
0.0
Reachable
ECN430
Not Supported
1.0
Reachable
ESN212
Not Supported
1.1
Reachable
EDN312xa
Synchronized
1.3
Reachable
EDN312xe
Synchronized
1.5
Reachable
EDN612p
Synchronized
Alarms
Note:
15.4
all
Default Settings:
None
Examples:
ecn(config)#alarm remove-active-alarm 1
ecn(config)#alarm remove-active-alarm all
15.4.1
Default Settings:
None
Examples:
135
Time
Node
Seq.
OID
2009-07-17
08:48:10
1004.0
4987
1.3.6.1.4.
1.193.72.6
00.1.6.0.3
ecn#
show alarm log history
The output will be similar to the Alarm Active Log, but only the history list
of alarms will be displayed.
136
Security
16
Security
Use these command to configure security settings in the ECN like firewall
access control lists, security users, and net services.
16.1
Command Level:
ecn(config)#
Syntax:
security firewall-acl <firewall-acl name> {create|remove}
security firewall-acl <name> {permit|deny} ip {ipaddress
<ip-address> netmask <subnetmask>|any}[{tcp|udp} port
{telnet|ftp|http|snmp|tftp|any|<portnumber>}][icmp]
{append|insert <sequence-number>|delete}
security firewall-acl <firewall-acl-name> delete
sequence-number <sequence-number>
Arguments:
<firewall-acl-name>
{create | remove}
<sequence-number>
137
Arguments:
{permit | deny}
{<ip-address> netmask
<subnetmask> | any}
{append | insert
<sequence-number> |
delete}
icmp
Default Settings:
None
Examples:
ecn(config)#security firewall-acl fir1 create
ecn(config)#security firewall-acl fir1 permit ip
ip-address 172.30.39.6 netmask 255.255.255.128 append
ecn(config)#security firewall-acl fir1 deny ip any append
ecn(config)#security firewall-acl fir1 delete
sequence-number 2
16.2
138
Security
Syntax:
security user [add username <name> password <password>]|
[remove username <name>]|[modify {usernameold <name> new
<name>}|{password username <name> new <password> password
<password>}|{type username <name> new {admin|cli}}]
Arguments:
{add | modify | type}
<name>
<password>
{admin | cli}
Default Settings:
Type: cli
Examples:
ecn(config)#security user add username peter password
cliandweb
ecn(config)#security user modify type username peter new
cli
16.3
Configuring Protocols
Command Usage:
Use this command to enable or disable servers in the ECN. If https is enabled
http will be automatically disabled. If a user tries to use http towards the ECN it
will be automatically redirected to use https.
Command Level:
ecn(config)#
Syntax:
security net-service https {enable|disable}
Arguments:
{enable}
{disable}
139
Default Settings:
https: enabled
Examples:
ecn(config)#security net-service https enable
16.4
Radius Server
Command Usage:
The command is used to define one or more RADIUS Servers.
A RADIUS Server must be defined when authentication is needed to access an
ECN. Several RADIUS Servers can be defined and they are used in the order
they are defined so that if the connection to the first on the list fails, connection
to the next will be tried. The use of RADIUS authentication must be enabled.
For more information about user authentication refer to System Description.
Command Level:
ecn(config system)#
Syntax:
radius-server enable host <ip-address> [auth-port <port>]
[timeout <seconds>][key <string>]
radius-server disable host <ip-address> [auth-port <port>]
Arguments:
<ip-address>
<port>
<seconds>
<string>
radius-server disable
host
Note:
140
Security
Default Settings:
timeout: 3
authentication-port: 1812
Examples:
ecn(config system)#radius-server enable host 172.1.1.4
timeout 4 key iknowwhatyoudidlastsummer
16.5
Tacacs Server
Command Usage:
Use this command to define one or more TACACS+ Servers.
A TACACS+ Server must be defined when authentication is needed to access
an ECN via the CLI or the Web interface. Several TACACS+ Servers can be
defined and they are used in the order they are defined so that if the connection
to the first on the list fails, connection to the next will be tried. The use of
TACACS+ authentication must be enabled. For more information about user
authentication, refer to the System Description.
Command Level:
ecn(config system)#
Syntax:
tacacs-server {enable|disable} server <ip-address>
tacacs-server {set|unset} secret <string>
Arguments:
<ip-address>
<string>
{enable | disable}
{set | unset}
Default Settings:
None
Examples:
ecn(config system)#tacacs-server enable server 172.1.1.4
141
16.6
Server Authentication
Command Usage:
Use this command to enable or disable RADIUS or TACACS+ authentication
when logging in to CLI and Web interface. In addition, prioritization of
authentication login methods can be enabled or disabled.At least one RADIUS
server must be configured before enabling RADIUS authentication, see Section
16.4 on page 140.
Similarly, at least one TACACS+ server must be configured before enabling
TACACS+ authentication, see Section 16.5 on page 141.
If more than one authentication method is enabled using the prioritize
command, in the event of the first method being unavailable, the second
authentication method will be used. If the second method is unavailable, the
third method will be used. Note that regardless of the prioritized authentication
methods, the root is always able to log in.
If the prioritize function is disabled, LOCAL authentication will be chosen.
To disable a set of login methods, these must previously have been enabled.
Command Level:
ecn(config system)#
Syntax:
aaa authentication login {enable|disable} radius
aaa authentication login {enable|disable} tacacs
aaa authentication login {enable|disable} prioritize
{[local]|[local|tacacs+|tacacs+ local]]|tacacs+
[local|radius|radius local]]}
Arguments:
{enable | disable}
radius
142
Security
Arguments:
{enable | disable}
tacacs+
{enable | disable}
prioritize
Default Settings:
disable radius
disable tacacs+
disable prioritize
enable local
Examples:
ecn(config system)#aaa authentication login enable radius
ecn(config system)#aaa authentication login enable
prioritize radius tacacs+ local
143
144
17
17.1
Keyword
Argument
Command Usage
calendar*
exit
interface
external
internal*
untagged*
default-gatewa
y
restart
enc
update
software
clear*
network
inventory
nodesw
all
ping
show
status
log
*) These commands are supported in releases earlier than EDA 1200 2.0.
Note:
145
17.1.1
Calendar
This command is the same as under normal operation and described in Section
3.5 on page 17. The command is supported in releases before EDA 1200 2.0.
17.1.2
Exit
This command is the same as under normal operation and described in Section
2.3.2 on page 10.
17.1.3
Interface
This command is almost the same as under normal operation. The only
difference is that it is not necessary to save the interface configuration (interface
activate). The activate argument does not exist in the CLI when the ECN is in
fallback state. Restart the ECN to activate the new settings (restart), seeSection
4.1 on page 25. The commands interface internal and interface untagged are
only supported in releases before EDA 1200 2.0.
17.1.4
Restart
This command is almost the same as under normal operation. The only
difference is that it is only possible to use the enc argument (it is only possible
to restart the EMP from the fallback CLI). Refer to Section 3.8 on page 20.
17.1.5
Update
This command is almost the same as under normal operation. The only
difference is that it is only possible to use the enc parameter value (it is only
possible to update the EMP SW from the fallback CLI). Note that the new EMP
SW must be transferred to the ECN before executing the update command.
Refer to Section 6.3 on page 37for more information about the update. For
more information about how to upload SW files, refer to the ECN430 Installation
Guide, the ECN330 Installation Guide or the ECN320 Installation Guide.
17.1.6
Clear
Command Usage:
Use this command to delete configuration or software that is suspected to be
corrupt, and therefore may prevent the ECN from starting up properly. This
command is supported in releases before EDA 1200 2.0.
Command Level:
vty#
Syntax:
clear {network|inventory|nodesw|all}
146
Arguments:
network
inventory
nodesw
all
Default Settings:
None
Examples:
vty#clear network
vty#clear inventory
vty#clear nodesw
vty#clear all
17.1.7
Ping
This command is the same as under normal operation. Refer to Section 3.6
on page 18.
17.1.8
Show
Command Usage:
Use this command to view the status or log file of the ECN. This command is
used for diagnostic purposes in order to identify what went wrong during start
up. Since the log file can be large, specifying the line numbers may be useful.
For more information about log files refer to the EMP Web Interface User Guide.
Command Level:
vty#
Syntax:
show status
show log [<line>][<line>]
147
Arguments:
status
log
Default Settings:
None
Examples:
To show the whole log file:
vty#show status
To show the last 15 lines in the log file:
vty#show log 15
To show line 45 to 75 in the log file:
vty#show log 45 75
148
18
18.1
18.2
149
18.3
150
Factory Default
19
Factory Default
It is possible to reset the ECN to a factory default configuration. Normally the
ECN will start up in normal mode if nothing is selected within 3 seconds. In
some cases the ECN will start up in fallback mode if it fails to start in normal
mode after two attempts, but will never start up in factory default mode unless
selected in the boot menu as explained in the following.
The procedure for resetting the ECN to factory default is described in the
following.
1. Connect a laptop to the console of the ECN. This will enable you to see
the boot menu.
2. Power off the ECN.
3. Power on the ECN.
4. Select reset to factory default in the boot menu.
151
152
Factory Default
153
154
20
20.1
Linux Kernel
Table 14
Linux Kernel
Package
kernel
155
20.2
Linux Applications
Table 15
Linux Applications
Package
bash
busybox
chrony
ethtool
fileutils
grub
Iproute2
strace
sysklogd
sysvinit
tftp
udhcp
util-linux
vsftp
watchdog
iptables
procps
20.3
Linux Libraries
Table 16
Linux Applications
Package
glibc
Linux-PAM
ncurses
Pam-Radius
readline
termcap
uClibc
156