Вы находитесь на странице: 1из 95

ECN User Guide

EDA 1200
Copyright

Copyright Ericsson AB 2009-2010. 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.

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.

Commons 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 Windows is a registered trademark of Microsoft


Corporation

Solaris Solaris is a registered trademark of Sun Microsystems,


Inc.

Java Java is a trademark of Sun Microsystems, Inc.

Linux Linux is a registered trademark of Linus Torvalds.

1/1553-LZA 101 464-V2 Uen F 2010-01-06


Contents

Contents

1 Introduction 1
1.1 Conventions 1
1.2 Revision Information 2
1.2.1 This Revision (F) 2
1.2.2 Version E 2
1.2.3 Version D 2
1.2.4 Version C 2
1.2.5 Version B 2
1.2.6 Version A 3

2 Introduction to the ECN 5


2.1 EAN Concept 6
2.2 Management of EAN 8
2.2.1 EAN Alarms 9
2.2.2 Alarm forwarding 9
2.2.2.1 Viewing Alarms Locally 9
2.2.2.2 Alarm Filter 10
2.2.3 Fallback State 10
2.2.4 System Log 10

3 Description of the EAN 11


3.1 EAN Node Topology 12
3.1.1 Dynamic Management VLAN 13
3.1.2 Fixed Topology 15
3.1.3 Flexible Topology 16
3.1.3.1 Flexible Blocks with Redundancy 17
3.1.4 Daisy Chaining EANs 18
3.1.5 Link Aggregation 20
3.1.5.1 Static Link aggregation Configuration Between ECN430
and ESN212 20
3.1.5.2 Link Aggregation Between two ESN212 Switches 21
3.1.6 Mixed Topologies 22
3.1.7 Reserved VLANs and Interfaces 22
3.1.8 Disabling EMP Port 23
3.2 EAN in the Network 24
3.2.1 Aggregation of EANs 24
3.2.2 Redundancy with EANs 25
3.2.3 Link Aggregation with EANs 26
3.3 ECN430 28
3.3.1 Fixed Topology 28
3.3.2 Flexible Topology 29
3.3.3 Port Designation 29

1/1553-LZA 101 464-V2 Uen F 2010-01-06


ECN User Guide

3.4 ECN330 29
3.4.1 Fixed Topology 29
3.4.2 Fixed Topology - Supported embedded units 30
3.4.3 Fixed Topology - Daisy Chain Scenario 32
3.4.4 Fixed Topology - Star Scenario 33
3.4.5 Flexible Topology 34
3.4.6 Port Designation 34
3.5 ECN320 34
3.5.1 Fixed Topology 34
3.5.2 Flexible Topology 34
3.5.3 Port Designation 34
3.6 Topology Limitation with Old ECN HW Versions 35
3.6.1 ECN330 up to R1D 35
3.6.2 ECN320 R3B or Higher (128 MB Flash) 35
3.6.3 ECN320 Versions up to R3A (64 MB Flash) 35
3.7 Line and Node Identification 36
3.7.1 Basic Line and Node ID for Fixed Topology 36
3.7.2 Line and Node ID for an Extension Switch 36
3.7.3 Line and Node ID for Flexible Blocks 37
3.7.4 Line and Node ID for EXN104 38
3.8 Security 40
3.8.1 IP Packet Filter 40
3.8.2 SNMPv3 40
3.9 Time Synchronization in the EAN 41

4 User Interface 43
4.1 Ethernet Connections 44
4.1.1 ECN430 44
4.1.1.1 LEDs User Interface 44
4.1.1.2 Power Supply Input Connectors 47
4.1.2 ECN330 47
4.1.2.1 PoE Ports 48
4.1.2.2 LEDs User Interface 49
4.1.2.3 Power Supply Input Connector 50

5 Installation 51

6 Backup, Restore and Factory Defaults 53


6.1 Backup and Restore 53
6.2 Factory Defaults 53

7 Maintenance 55
7.1 Replacing ECN 55
7.1.1 Roll Back the ECN 56
7.2 Replacing a Fuse 57
7.3 Replacing a Fan Tray 57

1/1553-LZA 101 464-V2 Uen F 2010-01-06


ECN User Guide

7.4 Changing SID of Flexible Blocks 59


7.5 Gigabit Media Expansion Module 59

8 Troubleshooting 61
8.1 Diagnose Switch Indicators 61
8.2 Power and Cooling Problems 62
8.3 Embedded units 62
8.4 CLI 64

9 Reference Information 65
9.1 Using a MIB Browser 65
9.2 Backup Using SNMP 69
9.2.1 Specify an FTP Server 70
9.2.2 Create the Backup Job 70
9.2.2.1 Automatic Backup 70
9.2.2.2 Manual Backup 71
9.2.2.3 Scheduled Backup 72
9.2.3 Backup Job Timers 73
9.2.4 Random Start Interval 75
9.2.5 Backup Job Activation 76
9.3 Restore Using SNMP 76
9.4 Built-in Local Configuration 76
9.4.1 Modifying Default Configuration Files 79
9.4.2 Exporting profiles 79
9.4.2.1 Importing profiles 79
9.4.2.2 Creating and Modifying ESN212 Configuration Files 80
9.5 Configuration of VLANs in Star Topology with ESN410 and
ECN330 81
9.5.1 General Configuration 81
9.5.2 VLAN Configuration in Daisy Chained Topology 81
9.5.2.1 Management VLAN Configuration for the First ESN410
Extension Switch 82
9.5.2.2 Configuration of the ECN330 83
9.5.3 VLAN Configuration in Star Topology 84
9.5.3.1 Management VLAN Configuration for the ESN410
Extension Switches 85
9.5.3.2 Configuration of the ECN330 86
9.6 Programs Packages under Open Source Licenses 87
9.6.1 Linux Kernel 88
9.6.2 Linux Applications 88
9.6.3 Linux Libraries 89

1/1553-LZA 101 464-V2 Uen F 2010-01-06


ECN User Guide

1/1553-LZA 101 464-V2 Uen F 2010-01-06


Introduction

1 Introduction

This guide describes the EDA Ethernet Controller Node ECN and is valid for
ECN430, ECN330 and ECN320. The term ECN refers to all variants. The term
ECN330/ECN320 switch refers to ECN320 or ECN330 in switch mode.

The guide describes the concept, the hardware and the functionality.
Furthermore, it provides an overview of software features.

The guide is intended for both operation personnel and system administrators
responsible for operating and maintaining network equipment.

The reader should have a basic knowledge of general Ethernet switch


functionality, the Internet Protocol (IP), and be familiar with general network
terms.

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.

In order to fully understand the function and use of the ECN within the EDA
context, read the System Description.

The guide can be printed on a monochrome printer, but illustrations are easier
to understand if a color printer is used.

1.1 Conventions
The following conventions apply for textual instructions (not screen dumps):
Tools->Options Means: Choose the Tools menu item, choose the Options
menu item.

Bold monospace letters mark text typed by the user (input) in Command
Line Interface (CLI).

Regular monospace letters mark text output in CLI.

<ServerIP> is a parameter (argument) that should be replaced with the actual


value (for example, the IP address of a server). The <> symbols must not
be typed.

[argument] the brackets indicate that this argument is optional and can be
omitted. If used, the brackets must not be typed.

{argument1|argument2} means that either argument1 or argument 2 can be


used as a value for this parameter.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 1


ECN User Guide

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.

1.2.1 This Revision (F)


This revision is made for EDA 1200 4.1 R8A.

Other than editorial changes, this document has been revised as follows:

A description of Dynamic Management VLAN is added in Section 3.1.1


on page 13.

A description of how to daisy chain EANs is added in Section 3.1.4 on


page 18.

1.2.2 Version E
This revision is made for EDA 1200 4.1 R7A.

Other than editorial changes, this document has been revised as follows:

A description of how to configure Link Aggregation is added in Section


3.1.5 on page 20 and Section 3.2.3 on page 26.

1.2.3 Version D
This revision is made for EDA 1200 4.1 R6A.

Other than editorial changes, this document has been revised as follows:

10 G expansion module with four XFP ports added in Section 4.1.1 on


page 44

New DIAG LED states added in Section 8.1 on page 61

1.2.4 Version C

This revision is made for EDA 1200 4.1 R5A,.

Other than editorial changes, this document has been revised as follows:

Section 3.1.5 on page 20 has been rewritten.

1.2.5 Version B
This revision is made for EDA 1200 4.1 R3A.

2 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Introduction

Other than editorial changes, this document has been revised as follows:

Various drawings showing management VLAN show now also Untagged


traffic.

Port number in Figure 26 on page 39 and Figure 27 on page 39 corrected.

1.2.6 Version A

This revision is made for EDA 1200 4.1 R2A. This is the first version of this
document and is based on the ECN User Guide 5/1553-HSC 901 101/2 Uen B.

Other than editorial changes, this document has been revised as follows:

Supported nodes in ECN320 (Section 3.6.3 on page 35) changed.

Link aggregation (Section 3.2.2 on page 25) added.

Reference to factory defaults added in Section 6 on page 53.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 3


ECN User Guide

4 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Introduction to the ECN

2 Introduction to the ECN

The Ethernet Controller Node, referred to as the ECN, is composed of two main
components: The EMP (Ethernet Management Proxy), and the Ethernet switch.
The ECNs are: ECN430, ECN330 and ECN320. When differences between
the ECNs appear in the following this will be explained.

Figure 1 Ethernet Controller Node Architecture

The ECN is a unit that is able to control and aggregate EDA nodes, which are
referred to as embedded units. Together, the ECN and the embedded units
constitute one logical node the Ethernet Access Node (EAN). The EAN is
managed as a single node.

The EAN can be configured in several ways depending on the type and number
of the embedded units connected to the ECN.

The following EDA nodes can be used as embedded units (for further details
refer to Section 3 on page 11):

IP DSLAMs (EDN110, EDN312, and EDN612)

ESN204g, ESN108 and ESN212

1/1553-LZA 101 464-V2 Uen F 2010-01-06 5


ECN User Guide

EXN104 FE to E1/T1 converter

ESN410

ECN320 switch and ESN310

ECN330 switch

EFN324

Other 3rd party unmanaged switches can also be used in the EAN. These are
not considered embedded units.

All embedded elements are Plug and Play, and the EAN elements may be
placed in one cabinet, appearing physically as a single node, or distributed in
different sites on different locations. For information about the ECN430 switch,
refer to ECN430 Switch/EMN120 User Guide.

For information about the ECN330 switch, refer to ECN330-switch User Guide.
For information about the ECN320/ESN310 switch refer to the ESN310 User
Guide. For information about other nodes, please refer to the user guides
for the specific node.

2.1 EAN Concept


The EAN is an autonomous and self-contained node that can be managed
using a Local Craft Tool (LCT) or by an external management system. Figure
2 on page 7 illustrates that the ECN can be used for management and
aggregation (EAN A) or for management only (EAN B).

6 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Introduction to the ECN

Figure 2 EAN Concept

As mentioned before, the EAN can be realized in many ways, using different
embedded units. The EDN288 is an EAN solution, which is, delivered in a
subrack. The EDN288 contains one ECN with 24 EDN312x IP DSLAMs
connected to all downlink ports, and thus supports 288 End-users. For a more
detailed description of this specific EAN, see the EDN288 Installation Guide.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 7


ECN User Guide

Figure 3 EAN Realized as EDN288

The EAN topology is described in more detail in Section 3.1 on page 12.

2.2 Management of EAN


The EAN can be installed and configured and used on its own using the built-in
Local Craft Tool (LCT). The LCT contains a Command Line Interface (CLI),
and a Web interface.

The EAN can also be managed by a management system using an SNMP


interface (Ethernet port).

The LCT can be accessed through the serial connection (console) on the ECN.

The IP address of the ECN is static only, and must be configured using the
Local Craft Tool (LCT).

The different management methods offer different features. Complete


management and monitoring is only available through SNMP. The CLI and
HTTP are used for configuration and monitoring but for example network
settings like spanning tree and link aggregation must be configured using LCT
on the embedded element.

All management options (except visual monitoring) require a User name and
Password before the ECN management can be accessed.

8 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Introduction to the ECN

2.2.1 EAN Alarms

Alarms (SNMP traps or notifications) from embedded units and switching unit
are always sent to the EMP.

2.2.2 Alarm forwarding


Alarms from the EAN are sent to the IP address of the Trap Receiver (several
receivers can be defined). The traps are always sent using the IP address
of the ECN (which is the only address known in the external network) as the
sender address. However, the traps contain the identification of the embedded
unit as a parameter, thus enabling easy and fast identification of the embedded
unit that originated the alarm. The identification of the nodes complies with the
identification concept shown in Figure 23 on page 36.

2.2.2.1 Viewing Alarms Locally

The alarms can also be inspected using the LCT Web. It is possible to see
two alarm views: Active and History. The following figure show the Active
alarm view.

Figure 4 Active Alarms in the LCT

Click details to see all the parameters of the alarm. All alarms are shown in the
alarm history, but only alarms that have a matching clearing alarm are shown in
the Active alarms. When an alarm is cleared (a clearing alarm received) the
original alarm will be removed from the Active alarms. Up to 100 alarms can be
shown in each alarm viewer. The oldest alarm will be deleted If 100 alarms are
shown and a new alarm is received, when there are 100 alarms in the active
view, an alarm will be sent each time a new active alarm is received (as long as
there are still 100 alarms in the view).

1/1553-LZA 101 464-V2 Uen F 2010-01-06 9


ECN User Guide

2.2.2.2 Alarm Filter

The ECN also contains an alarm filter. The filter function is always active, but
by default it is empty, and thus all alarms are allowed. The filter is configured
using the CLI by adding the alarms Object Identifier (OID) to the filter list.
Alarms that are defined in the filter will be discarded. They will not be shown in
the LCT and not sent to any alarm receiver.

For more information about the alarm viewers and alarm filter please refer to
the EMP Web Interface User Guide.

2.2.3 Fallback State


If for some reason the ECN fails to start, it will switch to a Fallback state. The
Fallback state is an emergency application, which contains a limited CLI to
enable diagnostics and reloading of software. When the ECN is in Fallback
state, only the CLI can be used as management interface. Only the console
connector on the ECN or Telnet can be used. Whether Telnet can be used
depends on the reason for the Fallback state.

2.2.4 System Log


The ECN keeps a log of events and errors by using Sys log. There are two
log files, one for errors and one for all events (including errors). Each log file
can be up to 500 KB. When the size of a log file reaches 500 KB, the file is
renamed and a new one is started. The events log file (detailed) is also cleared
on each restart. The log files can be viewed using the CLI if the ECN is in
Fallback state, or using a web browser in normal operation. It might take a
while to display the log.

10 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

3 Description of the EAN

As described in the introduction, the ECN is the key element in the EAN.
Several nodes can be connected to the ECN, see Section 2 on page 5.

The nodes can be combined in various ways to an ECN. Figure 5 on page 11


illustrates the logical structure of the management and End-user traffic in the
EAN, when the ECN is used for aggregation.

The basic topologies supported by the EDA system are described in more
detail in this section.

Figure 5 Ethernet Access Node Structure

The EMP manages all the embedded units. From a management point of view,
the switching unit is also an embedded unit, even though it is located and
integrated in the ECN.

The EMP is the only element communicating directly with a management


system. The EMP forwards the communication to and from the embedded
units. Note that only the management traffic is going through the EMP. The
End-user traffic only passes through the Switching Unit of the ECN.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 11


ECN User Guide

The whole EAN will appear in a management system as one large node with
many End-user lines. All End-user lines are terminated by a Line Termination
Unit (LTU). The LTU can be based on different drop technologies such as DSL,
Fiber or POTS. The traffic can be aggregated through the ECN or by another
Ethernet Switch unit.

The EMP has all the functions necessary to support embedded units like first
level alarm handling, device polling, network topology discovery, fault and
performance management.

The ECN is connected as an Ethernet switch, aggregating the embedded


units, see Figure 6 on page 13 . All the connections between the ECN
and the embedded units are normal Ethernet connections (with or without
PoE). Management traffic between the management system and ECN is
directed to the internal EDA management VLAN. However, the management
traffic between the ECN and the embedded units is directed to the external
management VLAN.

The internal management VLAN of an EAN is (and must be) a different VLAN
than the external management VLAN, in order to separate the two logical
networks. Two different EANs may use the same VLAN for the internal
management traffic. This will have no consequences in terms of security,
since this VLAN is invisible to the rest of the network, outside the EAN. Apart
from the internal management VLAN, other VLANs are reserved for internal
use of the EAN.

End-user traffic must not be directed to any of the reserved VLANs. VLANs are
discussed in more detail in Section 3.1.7 on page 22.

3.1 EAN Node Topology


The topology of the EDA network based on the EAN can be designed in
various ways using the EDA nodes. The status of each embedded unit can be
inspected, including the status and properties of single end-user lines, using
CLI or the Web interface.

In Section 3.1 on page 12 and Section 3.2 on page 24 the concepts and
topologies that are common for the ECN430, ECN330 and ECN320 are
described. Section 3.3 on page 28 describes specific features for ECN430.
Section 3.4 on page 29 describes specific features for ECN330 and Section 3.4
on page 29 describes specific features for ECN320.

Figure 6 on page 13 shows an example of an EAN containing a Fixed Topology


based on ESN108g, ESN212 and a Flexible Block based on ESN212.

12 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 6 Ethernet Access Node in the Network

3.1.1 Dynamic Management VLAN


The Dynamic Management VLAN (DMV) enables the EMP to dynamically
configure the management VLAN ID in all embedded nodes. This is necessary
if the internal management VLAN ID is changed, or if the management VLAN
ID configured in an embedded node is different from the management VLAN
ID used by the EMP.

The DMV concept deploys two VLANs for management. When an EDA node
restarts, it issues a DHCP discovery message. This message notifies any
DHCP server in the network that a node needs the services of the DHCP
server. The message is sent with the VLAN stored in the node. At this point
there are two possible scenarios:

1. The Management VLAN in the network is the same as the VLAN stored
in the node. When this is the case, everything in the network behaves
as usual.

2. The Management VLAN in the network is different from the VLAN stored
in the node. This is where DMV is used. The concept is explained in the
following.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 13


ECN User Guide

The concept incorporates two IP address pools in the EMP: Temporary that is
used only during the VLAN change, and Real that is used when the node is
using the correct VLAN ID during normal operation.

A simplified startup sequence of a node, which has a different Management


VLAN (VLAN246) than the default internal management VLAN (VLAN247) used
by the EMP is shown in Figure 7 on page 14. Please note that not the whole
DHCP sequence is shown.

Figure 7 Dynamic Management Concept

The sequence is as follows:

1. When an EDA 1200 node restarts, it sends a DHCP discover message


using its configured management VLAN (for example 246).

2. If no answer is received after approximately two minutes, the node will


send a new DHCP discover message. This time the message is sent as
untagged. The switching unit tags the message with VLAN 248 ("Untagged
VLAN") and forwards it to the EMP.

3. The EMP will send a reply tagged with VLAN 248 containing IP address
from the temporary IP range and the Management VLAN. The VLAN tag
is stripped by the switching unit before sending it back to the node as
untagged traffic.

4. The node does not use the IP address but stores the new Management
VLAN ID.

14 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

5. A new DHCP discover message is issued tagged with the new VLAN ID
(246).

6. After verifying that the request came from VLAN 246, the EMP assigns a
real IP address to the node.

3.1.2 Fixed Topology

In order to extend the number of line terminations per EAN, it is possible to add
switches to the EAN. These switches can be either embedded switches in a
fixed topology or flexible block switches in a flexible topology.

In a Fixed Topology the embedded switch is connected to a primary downlink


port (port on the ECN switch). Figure 8 on page 15 illustrates a fixed topology
where several switches are added.

The identification of the nodes is based on the physical port connection to


the ECN.

The inventory (embedded units) is automatically discovered by the EMP when


a node sends a DHCP request to the ECN. In a Fixed Topology the ECN
inspects the MAC address of the connected switches, including the switching
unit in the ECN. The MAC addresses display exact information about how
the node is connected to the ECN.

Figure 8 Fixed Topology Node Identification

1/1553-LZA 101 464-V2 Uen F 2010-01-06 15


ECN User Guide

3.1.3 Flexible Topology

A Flexible Block may be connected anywhere in the network, as long as there


is layer 2 transparency for the internal management VLAN, service VLANs and
untagged traffic to the ECN. The untagged traffic may be tunneled through a
VLAN in the aggregation network instead of being sent untagged, but the tunnel
must end before the ECN and the flexible block. The ECN and flexible block
must be able to send and receive untagged traffic to each other.

In the Flexible Topology the ECN identifies the Flexible Block by the Switch ID
of the Flexible Block switch (ESN212, ESN204g) or EFN324. The Flexible
Blocks are automatically recognized by the ECN by their DHCP request. The
Flexible Block switch intercepts the DHCP requests of the underlying nodes
and inserts its own Switch ID as DHCP option 60. When the ECN assigns an IP
address to the node, this IP address is also entered into the inventory table of
the ECN. This enables the ECN to communicate and recognize all embedded
units in the Flexible Blocks. Note that if there is already an SID in a DHCP
request (for example, when two Flexible Block switches are daisy chained), the
switch will not intercept the request.

Figure 9 on page 17 depicts three Flexible Blocks managed by an ECN. Two


are daisy chained. The daisy chained link or the uplink may be link aggregated.
This is configured with the ESN212 CLI. In a daisy chained scenario an
ESN212 can aggregated by an EFN324 but an EFN324 can not aggregated
by an ESN212. Refer to the EFN324 User Guide for a complete list of the
restrictions that apply to an EFN324 in both flexible and daisy chained topology.

16 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 9 Flexible Blocks

The two uplinks depicted in Figure 9 on page 17 may be on the same interface
and link.

The Flexible Block can also be connected to a downlink of an extension switch.


It will still be perceived as a Flexible Block.

The SID must be unique under one ECN in order for the node to act and be
recognized as a flexible block. Range of the SID: 1-254.

A Flexible Block may only contain one of the following:

One ESN212 and the EDNs connected to it

One ESN204g and the EDNs connected to it

One EFN324

The SID must be set in the ESN212, ESN204g using DIP switches or EFN324
using the CLI. EDN612 IP DSLAMs connected to ESN212 (or ESN204g) are
identified using the SID of the ESN212 (or ESN204g) that the IP DSLAMs
are connected to.

3.1.3.1 Flexible Blocks with Redundancy

Redundancy for a Flexible Block level can only be used with the ESN212. The
following is an example of a supported scenario:

1/1553-LZA 101 464-V2 Uen F 2010-01-06 17


ECN User Guide

Figure 10 Flexible Blocks with Ring Structure

RSTP is set using the CLI by doing the following:

ECN:

Configure the switching unit ports (using RCLI) for Link aggregation according
to the ECN Switch CLI Guide. This is only relevant when the Flexible block is
connected directly to the ECN.

ESN212:

Configure the ESN212 using RCLI or console for RSTP according to the
ESN212 CLI User Guide.

3.1.4 Daisy Chaining EANs


It is possible to daisy chain EANs as illustrated in Figure 11 on page 19. The
service VLANs for both uplink and downlink ports must be configured manually
so that the traffic can flow in both directions between all daisy chained EANs.
Configuration is done in the CLI of the ECNs using the command: external-vlan,
see the ECN LCT User Guide for details about the command.

The VLANs for the daisy chained EANS must be setup to ensure that:

18 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Service traffic can flow in both direction in VLAN A, B, C, D and E in the


first EAN.

Service traffic can flow in both directions in VLAN A, B, C, D and E in the


second EAN.

Service traffic can flow in both directions in VLAN A, D and E in the third
EAN.

As illustrated End-user traffic from the third EAN through VLAN A, D and E.
The uplink and downlink ports of the second EAN must there be manually
configured with VLAN A, D and E otherwise only traffic through service VLAN
B and C would be allowed.

For the same reasons the downlink ports of the first EAN have to be configured
with service VLAN A, B, C, D and E.

The uplink ports of the first EAN thus have to be manually configured with
service VLAN C, D and E. If End-users using A or B in the first switch in the
chain are removed, the VLAN will dissapear as well, therefore it is relevant to
consider configuring all service VLANs in the upper switch manually.

Figure 11 Daisy Chained EANS

1/1553-LZA 101 464-V2 Uen F 2010-01-06 19


ECN User Guide

3.1.5 Link Aggregation

Link aggregation on a Flexible Block level can only be used with ESN212.
The following scenarios are supported:

Figure 12 Flexible Blocks with Link Aggregation

Service VLANS need not be configured manually. The EMP will configure the
Service VLANs in the aggregated links automatically.

3.1.5.1 Static Link aggregation Configuration Between ECN430 and ESN212

Static Link aggregation is set using CLI, by doing the following (the example
shows aggregated links between ports 3-4 on the ECN430 and 11-12 on the
ESN212 with flexible block id 43):

ECN430 Configuration

Start a terminal emulator (for example telnet) and login to the ECN430 with the
user name: admin and password: admin

Log into the switching unit

ecn#rcli 0.0

In switching unit create link aggregation (channel group number 1 is used)

switch# configure terminal


switch#interface ge1/3
switch# static-channel-group 1

20 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

switch#exit
switch#interface ge1/4
switch# static-channel-group 1
switch#exit
switch#exit
switch#exit

ESN212 Configuration

Start a terminal emulator (for example telnet) and login to the ECN430 with the
user name: admin and password: admin

Log into the ESN212 unit

ecn#rcli 1043.0

In the ESN212 create a link aggregation group (channel group number 77


is used)

switch#configure terminal
switch#set port-channel enable
switch#interface port-channel 77
switch#no shutdown
switch#exit

In ESN212 connect ports to link aggregation group (channel group number 77


is used)

switch#interface gigabitethernet 0/11


switch#channel-group 77 mode on
switch#exit
switch#interface gigabitethernet 0/12
switch#channel-group 77 mode on
switch#exit

Connect internal management VLAN to all ports and link aggregation group
(channel group number 77 is used)

switch#vlan 247
switch#ports gigabitethernet 0/1-10 port-channel 77
switch#exit
switch#exit
switch#exit

3.1.5.2 Link Aggregation Between two ESN212 Switches

Both static and dynamic link aggregation can be used using the RCLI towards
each ESN212. For detailed information about how to configure link aggregation
please refer to command descriptions and example in the ESN212, ESN204g
CLI User Guide.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 21


ECN User Guide

3.1.6 Mixed Topologies

The ECN supports mixing any fixed and any flexible topology on node basis.
But it is not possible to mix different topologies per ECN port.

Figure 13 Fixed and Flexible Topologies Combined

3.1.7 Reserved VLANs and Interfaces


The ECN acts as a Network Address Translator (NAT) for management
traffic. The embedded units are therefore hidden from the Access Domain
Management System. Different interfaces that are configured independently
are thus used:

Internal Interface This interface is the gateway for the embedded


units. It has an internal IP address of the ECN, and uses the internal
management VLAN.

External Interface This interface represents the EAN to the outside


network. It has the IP Address of the ECN, and uses the management
VLAN used in the EDA network.

Internal Interface Untagged This interface is used by Dynamic


Management VLAN (DMV). This feature ensures that embedded units are
reconfigured automatically if their configured management VLAN is not the
same as the internal VLAN in the EAN.

22 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

For example, if an EDN using VLAN ID 246 is connected as an embedded


unit in the EAN using VLAN ID 247. DMV will reconfigure the EDN to
use VLAN ID 247. For more information about the DMV, refer to the
Management VLAN Configuration Guide. Note that the ECN does not
have to be configured for the DMV. It automatically supports the DMV for
all embedded units.

Note: EFN324 does not support Dynamic Management VLAN (DMV).


If the internal management VLAN has to be changed, it must be
changed manually in the EFN324 before changing the internal
management VLAN in the EMP.

Apart from the mentioned VLANs, the EAN VLAN ID 4093-4095 are used
internally.

Thus VLAN IDs that can be used as Service VLAN IDs (with default
management VLANs) are:

2 245, 249 4092.

3.1.8 Disabling EMP Port


A port on an ECN can be EMP disabled using the CLI. When a port is EMP
disabled, the EMP will remove the internal management VLAN (default 247)
and ignore that port. It will not be configured with service VLANs, and any
connected nodes will not appear in the inventory. Any configuration on this port
must be done manually using the Switch CLI (or possibly by a management
system). An EMP disabled port is called an auxiliary switch port and can be
used to aggregate non-EDA equipment.

It is not possible to disable an EMP port on an extension or embedded switch.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 23


ECN User Guide

Figure 14 EMP Disabled Port

3.2 EAN in the Network

3.2.1 Aggregation of EANs


When several EANs are connected in a network, it is crucial that the internal
management VLAN as well as untagged broadcast domain of one EAN is
separated from another EANs.

Figure 15 on page 25 illustrates two EANs aggregated in a switch, and how


VLANs are configured in order to ensure separation of the internal management
domain. In the illustration the default management VLANs are used (external
management: 246, internal management: 247).

24 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 15 Aggregation of EANs

3.2.2 Redundancy with EANs


It is possible to use redundancy when several EANs are connected in a ring
structure. If a link fails, the traffic can flow in the other direction.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 25


ECN User Guide

Figure 16 Redundancy

Figure 16 on page 26 illustrates an example of a ring structure where all the


ports used are uplink ports.

In the ring structure, spanning tree must be used (configured using CLI) to
avoid loops in the network.

In each ECN the service VLANs from the other EANs must be configured using
a management system. The system does not set a limit to the number of
EANs that can be connected in a ring. However, other considerations such as
bandwidth or spanning tree size limit the practical size. The same scenario is
also valid for daisy chaining several EANs. In practice, because of the spanning
tree, this scenario is a daisy chain that changes the traffic direction if a link fails.

3.2.3 Link Aggregation with EANs

It is possible to use link aggregation with EANs. Static link aggregation is used.

26 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 17 Link Aggregation

Static Link aggregation is set using CLI, by doing the following (the example
shows aggregated links between ports 10-12 on the ECN430 and 25-27 on the
ECN330, and configure Service VLAN 7):

ECN430 Configuration

Start a terminal emulator (for example telnet) and login to the ECN430 with the
user name: admin and password: admin

Configure auxiliary ports for external management VLAN to be used towards


the daisy chained ECN330:

ecn#config ecn port 10 admin-use auxiliary vlans


external-mgmt enable
ecn#config ecn port 11 admin-use auxiliary vlans
external-mgmt enable
ecn#config ecn port 12 admin-use auxiliary vlans
external-mgmt enable

Log into the switching unit

ecn#rcli 0.0

In the switching unit create link aggregation on the uplink.

switch#configure terminal
switch#interface ge1/22
switch#static-channel-group 1
switch#exit

1/1553-LZA 101 464-V2 Uen F 2010-01-06 27


ECN User Guide

switch#interface ge1/23
switch# static-channel-group 1
switch#exit
switch#exit

In the switching unit create link aggregation on auxiliary ports towards ECN330.

switch#configure terminal
switch#interface ge1/10
switch#static-channel-group 2
switch#exit
switch#interface ge1/11
switch# static-channel-group 2
switch#exit
switch#interface ge1/12
switch# static-channel-group 2
switch#exit
switch#exit

Configure service VLANs used in daisy chained ECN330

Configure link aggregated ports

switch#config ecn external-vlan add vlan-id 7 tagged-ports


10-12

Configure uplink ports

switch#config ecn external-vlan add vlan-id 7 tagged-ports


22-23

ECN330 Configuration

Start a terminal emulator (for example telnet) and login to the ECN330 with the
user name: admin and password: admin

ecn#config ecn link-aggregation uplink static primary 25


secondary 26-27

3.3 ECN430

3.3.1 Fixed Topology

For a description of how the ECN430 is used in a fixed topology, see Section
3.1.2 on page 15.

The following figure shows the supported embedded units in EAN with Fixed
Topology using ECN430.

28 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 18 Supported Fixed Topologies with ECN430

3.3.2 Flexible Topology


Flexible blocks are connected to any port of the ECN430 and not necessarily
directly.

For a description of how the ECN430 is used in a flexible topology, see Section
3.1.3 on page 16.

3.3.3 Port Designation


In ECN430 the ports has no default classification as Uplink and Downlink ports.
They must be configured during installation using CLI and when Service VLANs
are configured for end-users EMP will automatically configure these VLANs on
the necessary ports in the embedded switches managed by EMP.

3.4 ECN330

3.4.1 Fixed Topology

For a description of how the ECN330 is used in a fixed topology, see Section
3.1.2 on page 15. Additionally it is possible to expand the number of line
terminations in an EAN by adding extension switches when a ECN330 is used
in a topology.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 29


ECN User Guide

Extension Switches

An extension switch is connected to one of the uplink ports (not necessarily


directly) of the ECN330, see Figure 19 on page 30. The extension switch adds
more primary ports to the EAN. More embedded switches and nodes can be
connected in this way.

The ECN can be used for control of the extension switches with or without
aggregating the End-user traffic coming from these nodes. The management
VLAN and IP settings are configured manually in the extension switches using
the CLI. The ECN recognizes the extension switches by their IP address. The
EMP CLI is used to add the extension switches to the ECN. Refer to Section
9.1 on page 65 for detailed information about how to configure the ECN and
extension switches for the scenarios described in this section.

Figure 19 ECN330 - Embedded Switches and Extension Switch

While embedded units are always fully managed by the ECN, the degree of
management on extension switches can vary depending on the extension
switch type. The following switches are supported as extension switches:

ECN320-switch, ECN330-Switch (ECN downgraded to switch)

ESN310

ESN410

3.4.2 Fixed Topology - Supported embedded units


Figure 20 on page 31 and illustrates possible internal topologies of nodes under
the ECN. All 6 combinations can be connected to any of the downlink ports on
the ECN330 and the switch extension.

30 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

It is also possible to use ECN330 Switch (ECN acting as a switch only after
downgrading it from the CLI) or a third party switch. When an unmanaged
switch is used, all VLANs including internal management VLAN must be
manually configured in the switch with whichever tool that is available for the
specific switch. Up to 8 unmanaged switches can be connected to any of the
downlink ports. The only embedded unit that can be connected under an
unmanaged switch is EDN312.

The EXN104 converter on the remote site will in some cases (3, 4 and 6) need
a power node to supply the necessary power. When the ESN108 switch is
used to aggregate the EXN104 converter (combination 6) can supply both
the upstream and downstream converters with power through the Ethernet
cables. As indicated, the ESN108 is connected to the uplink EXN104 through
the electrical port 8, which must be configured in the ESN108 in order to
supply power through the uplink port 8. The configuration is done through the
command line interface of the EMP.

Note that the ECN330 has a 16K MAC table. The performance will be affected
if the maximum number of all nodes it forwards traffic to (including End-user
devices) exceeds 16,000.

Note: When daisy chaining Switch extensions, all extension switches must
be of the same type (for example, all extension switches are ECN330
switch).

Figure 20 ECN330 with ECN330 Switches as Extension Switches

1/1553-LZA 101 464-V2 Uen F 2010-01-06 31


ECN User Guide

3.4.3 Fixed Topology - Daisy Chain Scenario

In Figure 21 on page 32 and Figure 22 on page 33 the topologies based on


ESN410 are illustrated using default management VLANs. Both topologies are
based on the 12-port optical switch ESN410. Up to seven ESN410 can be
managed by one ECN330. However the system is limited to the support of
approximately 200 embedded units due to performance limitations.

The IP DSLAM can be connected through an ESN212 or ESN108, which is


connected to a Gigabit fiber port (port 1-8) of the ESN410.

Figure 21 Daisy Chained Traffic and Management Separation Scenario

In the daisy-chained scenario, the first ESN410 must be connected to one of


the optical ports 25 or 26 of the ECN330, and the following ESN410 switches
must be connected to either port 11 or 12 of the previous ESN410. Thus port
11 12 of the ESN410 are used for daisy-chaining and port 9 10 can be used
for uplink. Any necessary spanning tree settings must be configured manually.
Port 11 and 12 must be configured manually for both management VLAN.

For information about how to configure the VLAN settings, see Section 9.5
on page 81.

The first ESN410 is denoted Extension switch 1, the second Extension Switch
2 and so on. It is not possible to remove a lower extension switch from the
inventory, while a higher one exists (for example, one cannot remove extension
switch 2, while extension switch 3 is still in the inventory).

32 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

When the ESN410 extension switches are created (using the CLI), they must
be created as a switch extension with type esn410-uplink, so that the EMP
configures both internal and external management VLANs on the ECN ports.

3.4.4 Fixed Topology - Star Scenario

Figure 22 Star Traffic and Management Separation Scenario

In the Star-topology the ECN330 is connected to the extension switches


through an aggregation switch unknown to EMP. That is, the EMP is not aware
of the aggregation switch, and it is not shown in the inventory of the ECN.

When the ESN410 extension switches are created (using the CLI), they must
be created as a switch extension with type esn410-uplink, so that the EMP
configures both internal and external management VLANs on the ECN port.

ECN330 must be connected to the aggregation switch using one of the optical
ports 25 or 26 of the ECN. One or more of the ports 9 12 of the extension
ESN410s must be connected to the aggregation switch. Note that even though
the extension switches are not daisy chained, they are configured in the ECN
as if they are. Therefore, the same rule applies also for star topology: it is
not possible to remove a lower extension switch from the inventory, while a
higher one exists.

Note: If two star topology EANs has to be connected it must be done through
a third aggregation switch to ensure a separation of the internal
management VLANs of the two EANs.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 33


ECN User Guide

3.4.5 Flexible Topology

The Gigabit Ethernet ports (25, 26 and 27) of the ECN330 must be used to
connect a flexible block.

Note that a Flexible Block can be connected to a downlink of an extension


switch. It will still be perceived as a Flexible Block and not as part of the Fixed
Topology under the extension switch.

For a description of how the ECN330 is used in a fixed topology, Section 3.1.2
on page 15.

3.4.6 Port Designation

ECN330 has two types of ports: Uplink ports (25, 26, 27) and Downlink ports
(1-24):

Uplink ports are configured automatically with the External management


VLAN ID (default 246). Any untagged traffic entering an uplink port is
tagged with VLAN ID 1 and discarded, since the data will not be forwarded
to any port.

Downlink ports are configured automatically with the Internal management


VLAN ID (default 247). Any untagged traffic entering a downlink port is
tagged with the defined Untagged VLAN ID (default 248).

3.5 ECN320

3.5.1 Fixed Topology


For a description of how the ECN320 is used in a fixed topology, Section 3.1.2
on page 15 and Section 3.4 on page 29. Note the limitations mentioned in
Section 3.6 on page 35.

3.5.2 Flexible Topology


Flexible block are not supported for ECN320.

3.5.3 Port Designation

ECN320 has two types of ports: Uplink ports (25 and 26) and Downlink ports
(1-24):

Uplink ports are configured automatically with the External management


VLAN ID (default 246). Any untagged traffic entering an uplink port is
tagged with VLAN ID 1 and discarded, since the data will not be forwarded
to any port.

34 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Downlink ports are configured automatically with the Internal management


VLAN ID (default 247). Any untagged traffic entering a downlink port is
tagged with the defined Untagged VLAN ID (default 248).

3.6 Topology Limitation with Old ECN HW Versions


Due to the size of the SW packages of new nodes, there are some limitations
on old HW versions regarding which types of embedded units can be used
under the same ECN.

3.6.1 ECN330 up to R1D


The following node packages can be used under the same ECN:

Table 1 Possible embedded units Under the Same ECN


Option 1 Option 2 Option 3 Option 4
EDN612 EDN312 EDN612 EDN312
EDN312x EDN312x EFN324 EDN312x
ESN108 ESN108 ESN212 EFN324
ESN212 ESN212 ESN410 ESN108
ESN410 ESN310 ESN212
ESN410 ESN410
EXN104

3.6.2 ECN320 R3B or Higher (128 MB Flash)


The following node packages can be used under the same ECN:

EDN312, EDN312x, ESN108, ESN310, EXN104, ESN410

3.6.3 ECN320 Versions up to R3A (64 MB Flash)


The following nodes can be used under the same ECN:

Option 1: EDN312x, ESN108, ESN310, EXN104

Option 2: EDN312, ESN108, ESN310, EXN104

1/1553-LZA 101 464-V2 Uen F 2010-01-06 35


ECN User Guide

3.7 Line and Node Identification


The identification of a node uses the name of the ECN (or IP address) together
with the Ethernet ports. The identification number is used in various CLI
configurations. In the following figures the ECN430 is used but the principles
are the same for all ECNs.

3.7.1 Basic Line and Node ID for Fixed Topology


Figure 23 on page 36 illustrates the concept of the embedded unit identification.

The ECN is identified with 0 and the ECN switch with 0.0.

Figure 23 Embedded unit Identification

The lines on the IP DSLAM are designated as follows:

ECN Port Number.Switch Port Number.EDN Port Number.

If the EDN is connected directly to the ECN the ESN Port Number is 0.

The nodes are identified in the same way as the lines, except that the last
number is always 0.

3.7.2 Line and Node ID for an Extension Switch


Figure 24 on page 37, identification of the embedded units is shown using the
ESN410 switch in the EAN. The extension switch is always connected to the

36 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

uplink port 25, 26 or 27 on the ECN. The extension switch ports (ESN410) are
numbered according to the port number. Port 1 is numbered 101, port 2 is
numbered 102 and so on up to number 108. As a consequence the ports on
the IP DSLAM will be designated as follows:

Extension Port Number.Switch Port Number.EDN Port Number.

Figure 24 Embedded unit Identification with an Extension Switch

The EAN can be extended with up to 7 switches, which are daisy chained or
star connected. The node number of the next switches will be Node 0.2, 0.3
0.4 and so on. The ports of the switches (ESN410) will be numbered from
201 to 212 and 301 to 312 and so on.

3.7.3 Line and Node ID for Flexible Blocks


The line and node ID for Flexible Blocks are illustrated in Figure 25 on page 38.
The designation is as follows:

Line ID: 1000+SID.Flexible Block Switch port. EDN port number

Flexible Block Switch ID: 1000+SID.0

EDN: 1000+SID.Flexible Block Switch port.0

Note that for the EFN324, the Flexible Block Switch port is 0.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 37


ECN User Guide

Figure 25 Line and Node ID with Flexible Blocks

3.7.4 Line and Node ID for EXN104


Figure 26 on page 39 and Figure 27 on page 39, the identification of the nodes
is illustrated, using the EXN104 FE to E1/T1 converter in different combinations.

As illustrated in Figure 26 on page 39, EXN104 converters, when inserted for


example between the ECN and the IP DSLAM, will not affect the line numbering.

EXN104 converters inserted between the ECN and the ESN108 are identified
by the node numbers 100 (central) and 200 (remote) and EXN104 converters
inserted between an ESN108 and an IP DSLAM, are identified by the node
number 101 (central) and 102 (remote), see Figure 26 on page 39.

38 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

Figure 26 Node Identification for an Embedded EXN104 converter

Figure 27 Node Identification for an Embedded EXN104

1/1553-LZA 101 464-V2 Uen F 2010-01-06 39


ECN User Guide

3.8 Security
Different features are implemented in the ECN to ensure security in the network
management system.

3.8.1 IP Packet Filter

An IP packet filter (firewall) mechanism is implemented in the ECN. Using


the CLI, firewall access control lists (ACL) can be configured to control the
access to the management functions of the EAN. A list of IP addresses can be
specified so that only traffic from these IP addresses is allowed access to the
management part of the EAN, that is, the EMP (Ethernet Management Proxy).
Different rules can be specified for different kind of traffic. For example, the
rules can specify which IP addresses that are allowed to send SNMP requests,
log in to the web interface or telnet to the ECN.

The firewall access control lists can be applied on the external management
interface (default VLAN 246) on the ECN. Applying access control lists makes it
possible to check all incoming traffic by the source IP address, the protocol and
the destination port number. All protocols and port numbers relevant for the
ECN can be included in rules in the firewall access lists.

A similar access control list is also implemented in the switch unit. For more
information refer to the ECN430 Switch/EMN120 User Guide.

3.8.2 SNMPv3

SNMPv3 provides security in the network management system by providing


encryption and authentication including verification of user rights. The following
features are provided by SNMPv3:

Authentication Verify the identity of the source of the data including


verification of user rights.

Privacy Ensure that data is transmitted from source to destination


without undetected modification (integrity) and protected from unauthorized
disclosure (encryption).

Access Control Determines whether access to a managed object is


allowed.

3 different groups (Context names) are defined with access to different MIBs,
and a user must belong to one of these groups. Access rights (read-only
and read-write) and a security level (no authentication, authentication
or authentication and encryption) are defined for each group. For more
information, refer to the System Description.

40 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Description of the EAN

3.9 Time Synchronization in the EAN


A central NTP server is used by the embedded units in the network for setting
time and date. The IP address of the central NTP server is set in the ECN by a
management system or using the CLI command ntp. When the IP address is
set, the following takes place:

The NTP client in the ECN is enabled.

The NTP client synchronizes with the central NTP server.

The local NTP server in the EMP synchronizes with the NTP client.

All embedded units synchronize with the local NTP server.

If a central NTP server is not used the CLI command calendar is used to set
time and date in the local NTP server of the ECN. See EMP CLI User Guide for
more information about the commands calendar and ntp.

Figure 28 Time Synchronization

1/1553-LZA 101 464-V2 Uen F 2010-01-06 41


ECN User Guide

42 1/1553-LZA 101 464-V2 Uen F 2010-01-06


User Interface

4 User Interface

All connectors and LED indicators for ECN430, ECN330 and ECN320 are
located in the front panels.

Figure 29 ECN430 Front Panel

Note: The Release button is not used.

Figure 30 ECN330 Front and Rear Panels

1/1553-LZA 101 464-V2 Uen F 2010-01-06 43


ECN User Guide

4.1 Ethernet Connections

4.1.1 ECN430
The ECN430 has the following Ethernet connections:

20 10/100/1000BASE-T RJ-45 combo Gigabit RJ45 ports with shared Small


Form Factor Pluggable (SFP) transceiver slots (Ports 1 20). In its default
configuration, if an SFP transceiver (purchased separately) is installed in a
slot and has a valid link on its port, the associated RJ45 port is disabled
and cannot be used. The ports support automatic MDI/MDI-X.

3 independent 1000BASE-T RJ45 ports (Ports 21-23). The ports support


automatic MDI/MDI-X.

Optional 10 Gigabit media expansion module, which is available in two


variants:

0 10G Module, 2*XFP and 2*elec: with two XFP (10G Small Form
Factor Pluggable) transceiver slots (optical), and two built-in Infiniband
X4 transceivers (electrical). The Infiniband X4 transceiver uses IEEE
802.3ak 10GBASE CX4 signals over Infiniband cable. The maximum
approved length of the cable for the ECN430 is 3m.

0 10G Module 4*XFP ports: with four XFP (10G Small Form Factor
Pluggable) transceiver slots (optical).

The ECN430 automatically detects the type of XFP module plugged in.

4.1.1.1 LEDs User Interface

The unit also includes a display panel for key system and port indications that
simplify installation and network troubleshooting. The LEDs for the base unit,
which are located on the front panel for easy viewing, are shown in Figure 31
on page 44.

Figure 31 System and Ports Status LEDs

44 1/1553-LZA 101 464-V2 Uen F 2010-01-06


User Interface

Table 2 System and Ports Status LEDs


LED Condition Status
System Status
PWR Steady Green The units internal power supply is
operating normally.
Off The unit has no power connected, or
the internal power supply has failed.
DIAG Steady Green The system diagnostic test has
completed successfully.
Flashing Green The system diagnostic test is in
progress.
Steady Red The system diagnostic test has
detected a fault in the Switching unit.
FAN Steady Red One or both cooling fans have failed.
Off The units cooling fans are operating
normally.
CTRL Flashing Green ENC self test and boot in progress
(fast) (during start).
Steady Green ENC in normal operation.
Steady Red Error in ENC (Fallback state and when
booting), or if the ECN430 is running
in switch-mode.
Off ENC not present.
Gigabit Combo Ports (1~20)
E (RJ45) Steady or Port has established a valid 10 or 100
Flashing Amber Mbps network connection. Flashing
indicates activity.
Steady or Port has established a valid 1000 Mbps
Flashing Green network connection. Flashing indicates
activity.
Off There is no valid link on the port.
O (SFP) Steady or Port has established a valid 1000 Mbps
Flashing Green network connection. Flashing indicates
activity.
Off There is no valid link on the port.
10/100/1000 Mbps Ports (21~23)

1/1553-LZA 101 464-V2 Uen F 2010-01-06 45


ECN User Guide

(Link/Activity) Steady or Port has established a valid 10 or 100


Flashing Amber Mbps network connection. Flashing
indicates activity.
Steady or Port has established a valid 1000 Mbps
Flashing Green network connection. Flashing indicates
activity.
Off There is no valid link on the port.

The optional 10 Gigabit slide-in module includes its own integrated LED
indicators on the modules front panel, as shown in Figure 32 on page 46 and
described in Table 3 on page 46.

Figure 32 Gigabit Module Status

Table 3 10 Gigabit Port and Module Status LEDs


LED Condition Status
Ports 24-27 Stady or Flashing Port has established a valid 10
Green Gbps network connection. Flashing
indicates activity.

46 1/1553-LZA 101 464-V2 Uen F 2010-01-06


User Interface

MODULE Flashing Green Begins flashing once the module


Release button is pressed, and
continues flashing until the system is
ready to release the module.
Steady Green The module can now be removed from
the chassis.
DIAG Flashing Green The system diagnostic test is in
progress.
Steady Green The system diagnostic test has
completed successfully.
Red The system diagnostic has detected a
fault with the 10G module.

4.1.1.2 Power Supply Input Connectors

The dual power supply input connectors are located on the front panel of the
ECN430. The standard power supply for the ECN430 is -48 VDC, and includes
protection through a disposable fuse (located beneath a plastic cover in the
top left corner of the front panel). Power redundancy can be established by
connecting both power inputs. If for some reason one of the power supplies
is out of order the other supply will automatically take over without any
disturbances.

Figure 33 Power supply Input Connector and Fuses

4.1.2 ECN330

The ECN330 has the following Ethernet connections:

24 10BASE-T/100BASE-TX RJ-45 downlink ports. These support


automatic MDI/MDI-X. All 10/100 RJ-45 ports support Power-over-Ethernet
(PoE).

1/1553-LZA 101 464-V2 Uen F 2010-01-06 47


ECN User Guide

Two uplink combo 1000BASE-T/SFP ports on the front panel. Optional


slide-in SFP transceivers can provide 100 Mpbs (100BASE-FX) and 1000
Mbps (1000BASE-SX, 1000BASE-LX, 1000BASE-LH) fiber links to remote
devices.

One uplink 10/100/1000BASE-T Gigabit Ethernet port.

4.1.2.1 PoE Ports

All of the 24 10BASE-T/100BASE-TX RJ-45 ports support PoE capability and


can supply up to 23.1 W of power to connected EDA nodes.

The PoE enables DC power to be supplied to the connected nodes through the
Ethernet cable. IP DSLAMs attached to a port can draw power directly from the
ECN over the Ethernet cable without requiring a separate power source. The
ECN automatically detects an EDA node by its authenticated PoE signature
and senses its required load before turning on DC power to the port. An electric
port of ESN108 (which is also a PoE node) can also be connected to the ECN.
The sense circuit in both nodes (ECN and ESN108) will sense that no power is
required. This detection mechanism also prevents damage to other network
equipment that is not an EDA node.

The ECN delivers power to the IP DSLAM using the two wire pairs in UTP or
STP CAT 5 cable that are not used for 10BASE-T/100BASE-TX connections
(for details, see ECN330-switch Users Guide). Each line is individually
controlled with an auto-detect circuit that opens up if a load within the
EDA-specified range is detected, and shuts down if the load exceeds the limit of
23.1 W. Each line is filtered for surge currents and has a 4 ms backup reservoir,
should short voltage drop outs occur.

The ECN can provide up to 600 mA continuously on each 10/100 Mbps port, or
up to 23.1 W of power. However, taking into account some power loss over
the cable, the amount of power that can be delivered to an EDA node is about
21 W. If a device draws more than 625 mA from a port, an overload condition
occurs and the port turns off the power.

These ports also support automatic MDI/MDI-X operation, so straight-through


cables can be used for all network connections to PCs or servers, or to other
switches or hubs.

The ports also support auto-negotiation, so the optimal transmission mode (half
or full duplex), and data rate (10 or 100 Mbps) can be selected automatically,
if this feature is also supported by the attached device. If a device connected
to one of these ports does not support auto-negotiation, the correct speed
will be sensed by the port, but the transmission mode will by default be half
duplex. Each port also supports auto-negotiation of flow control, so the ECN
can automatically prevent port buffers from becoming saturated.

The ECN controls the power and data on a port independently. Power can be
requested from a device that already has a data link to the ECN. In addition, the
ECN can supply power to a device even if the ports data connection has been

48 1/1553-LZA 101 464-V2 Uen F 2010-01-06


User Interface

disabled. The power on a port is continuously monitored by the ECN and it will
be turned off as soon as a device connection is removed.

4.1.2.2 LEDs User Interface

The unit also includes a display panel for key system and port indications that
simplify installation and network troubleshooting. The LEDs, which are located
on the front panel for easy viewing, are shown in Figure 34 on page 49 and
described in Table 4 on page 49.

Figure 34 System and Ports Status LEDs

Table 4 System and Ports Status LEDs


LED Condition Status
System Status
PWR On Green The units internal power supply is
operating normally.
Off The unit has no power connected.
DIAG On Green The system diagnostic test has been
completed successfully.
Flashing Green The system diagnostic test is in progress.
On Red The system diagnostic test has detected
a fault in the Switching unit.
FAN On Red One or both cooling fans have failed.
Off The units cooling fans are operating
normally.
CTRL Flashing Green ENC self test and boot in progress
(fast) (during start).
On Green ENC in normal operation.
On Red Error in ENC (Fallback state and when
booting), or if the ECN is running in
switch-mode.
Off ENC not present.
10/100 Mbps Ports

1/1553-LZA 101 464-V2 Uen F 2010-01-06 49


ECN User Guide

1 ~24 (Link/Ac On or Flashing Port has established a valid 10 or 100


tivity) Green Mbps network connection. Flashing
indicates activity.
Flashing Red Port has detected a power overload
or short circuit and has shut down the
power on the port.
Off There is no valid link on the port.
100/1000 Mbps Combo Ports
25, 26 (E - On or Flashing Port has established a valid 10, 100, or
RJ-45), (O - Green 1000 Mbps network connection. Flashing
SFP) indicates activity.
Off There is no valid link on the port.
100/1000 Mbps Combo Ports
Port 27 On or Flashing Port has established a valid 10, 100, or
(Link/Activity) Green 1000 Mbps network connection. Flashing
indicates activity.
Off There is no valid link on the port.

4.1.2.3 Power Supply Input Connector

The ECN has a dual power input with the purpose of achieving redundancy.
The power will be supplied by both power inputs.

If for some reason one of the power supplies is out of order the other supply will
automatically take over without any disturbances.

The power supply input connector is located on the front panel of the ECN.

The standard power supply for the ECN is -48 V DC, which includes protection
through a disposable fuse (located on the rear panel).

Figure 35 Power Supply Input Connector and Fuse

50 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Installation

5 Installation

The ECN is configured with the initial parameters using the ECN Local Craft
Tool, see ECN430 Installation Guide and ECN330 Installation Guide for more
information. The configuration includes some basic configuration parameters
such as IP address, subnet mask and SNMP parameters.

Configuration and line provisioning can be done without a management system


using the web interface or the Command Line Interface of the EMP.

The embedded units are configured automatically. When the nodes are
connected to the ECN, the Ethernet Management Proxy (EMP) recognizes the
new embedded unit and supplies it with all the necessary SW and configuration
parameters. For extensions switches configuration must be done manually.

Any embedded unit can be replaced at any given time, without the need of
registration. If the new node is the same type of node as the old one (for
example by replacing an EDN312 with another EDN312), all the configuration
of the old node including line provisioning will be configured automatically in
the new node. The line provisioning must be redone when changing to a new
type of node (for example, an EDN312x instead of an EDN312),. Special
requirements apply to the replacement of an ESN204g, see the EDA 1200
Generic User Guide for more information.

SW for the embedded units is installed on the ECN using management system,
CLI or the Web interface connecting to a FTP server.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 51


ECN User Guide

52 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Backup, Restore and Factory Defaults

6 Backup, Restore and Factory Defaults

This section describes the backup, restore and factory defaults functions in
the ECN.

6.1 Backup and Restore


In general the ECN configuration files can be backed up and restored using
either the web interface, the CLI or SNMP.

The following three types of backups can be done:

Manual backup, which can be done using either the web interface, the
CLI or SNMP.

Scheduled backup, which can be done only using SNMP. A scheduled


backup starts at a specified time, runs again after a specified time period,
and runs a specified number of times.

Automatic backup runs automatically when a configuration change has


been made.

How to perform a manual backup and restore of the configuration using the
Web or CLI interface is described in the EMP CLI User Guide (CLI) and EMP
Web Interface User Guide (Web).

Using SNMP to setup a manual, a scheduled, or an automatic backup is


described in section Section 9.2 on page 69.

6.2 Factory Defaults


It is possible to set the ECN (including the switching unit) back to factory
defaults using the console port on the ECN. Please refer to the EMP CLI User
Guide for detailed instructions.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 53


ECN User Guide

54 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Maintenance

7 Maintenance

7.1 Replacing ECN


When replacing an ECN make sure that a registration in a management system
is reestablished if necessary. The following procedure is a plug and play
procedure that is only valid when a node is replaced with another node of the
same type. For example ECN330 is replaced with another ECN330. Using this
procedure only the initial configuration is needed to be configured manually.

ECN320 can be replaced with ECN330 without reprovisioning provided that the
same ports are used.

When an ECN320 or ECN330 is replaced with ECN430, the End-users need to


be reprovisioned with the management system used. That is, the new node is
regarded as a new node and not a replacement of the old one.

To replace an ECN with the another ECN of the same type or ECN320 with
ECN330 using the same ports:

1. If there is no recent backup, and if it is possible, make a backup of the ECN,


using one of the methods described in Section 6 on page 53.

2. Disconnect the power and Ethernet connections from the ECN. The
Ethernet connections must be marked, so they can be reconnected to the
same port number in the new HW.

3. Dismount the old ECN.

4. Mount the new ECN and connect the uplink connection.

5. Connect the power and perform the basic configuration according to the
instructions in the ECN430 Installation Guide or the ECN330 Installation
Guide. Note that the IP address of the new node must be the same as
the old one.

6. Update the software if necessary. Note that this update should include
the EMP software as well as the software for all the embedded units. If
possible, use the EAN package to perform this update.

7. If possible, restore the configuration information from a backup file.

8. Connect the Ethernet connections to the downlink ports and any daisy
chained connections.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 55


ECN User Guide

Note: When replacing an ECN with embedded units that do not use
Power over Ethernet (ESN108, ESN204g, ESN212 and EFN324),
the embedded unit must be restarted to be registered in inventory
of the ECN.

If a node is not restarted, it will be registered when it next sends


a DHCP request. Registration is required for communication
between the ECN and the node.

9. If PEM or ServiceOn PEM is used, make a Forced Synchronization in PEM


(use the Network Configuration Manager, select the EAN properties, and
click the Synchronize button). This will update the PEM database with
the MAC address of the new node, and download the configuration to all
the embedded units.

10. If multicast is used and the new element is an ECN, the proxy query
address should be configured in the new ECN switch for the corresponding
service VLANs. For example:

Vty-0(config)# ip igmp snooping vlan 4 proxy-query-ad


dress 172.30.39.158.

11. The replacement is complete.

7.1.1 Roll Back the ECN


If the replacement of the ECN (as described above) fails for some reason, the
original ECN has to be remounted, and a rollback must be performed as follows:

1. The Ethernet connections must be marked, if not already done, so that they
can be reconnected to the same port number. Disconnect the power and
Ethernet connections from the ECN.

2. Dismount the ECN that failed.

3. Remount the original ECN.

4. Connect the power. No new basic configuration should be needed, because


this should be already saved and available as .startup configuration when
performing the hot swap.

5. Connect the Ethernet cables to the ECN.

Note: When replacing an ECN with embedded units that do not use
Power over Ethernet (in other words, ESN108, ESN204g, ESN212
and EFN324), the embedded unit must be restarted to be
registered in inventory of the ECN. If a node is not restarted, it will
be registered when it next sends a DHCP request. Registration is
required for communication between the ECN and the node.

6. If PEM or ServiceOn PEM is used, make a Forced Synchronization in PEM


(use the Network Configuration Manager, select the EAN properties, and
click the Synchronize button). This will update the PEM database with

56 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Maintenance

the MAC address of the new node, and download the configuration to all
the embedded units.

7. The roll back of the ECN has been completed.

7.2 Replacing a Fuse


The fuse protecting the DC power supply of the ECN is disposable. If the fuse
has blown, replace it with a new 20 A, 250 V type T fuse for ECN320/30 or a
new 10 A, 250 V type T fuse for ECN430.

Warning!
Power off the ECN before replacing a DC power supply fuse.

To replace a fuse, follow these steps:

1. Remove the -48 V DC power source from the ECN.

2. Unscrew the fuse holder counter-clockwise from its socket. Pull out the
blown fuse and discard it.

3. Insert a new 20 A, 250 V type T fuse into the fuse holder and screw the
holder clockwise back into the fuse socket.

4. Reconnect the -48 V DC power source to the ECN.

7.3 Replacing a Fan Tray


The fan tray should be replaced if the FAN status LED turns red (a cooling
fan in the fan tray has failed).

To ensure proper cooling of the ECN, both fans must be operational. If one
fan fails the ECN will continue to run, but the fan tray should be replaced as
soon as possible.

The fan tray of the ECN can be completely removed without powering off the
unit. To replace a fan tray, follow these steps:

1. Remove the fan tray plastic access cover on the right side of the front panel
by pulling it open from the right.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 57


ECN User Guide

2. Unscrew the fan trays screw.

3. Grasp the fan trays handle and pull it outward to disconnect it from the
ECN. Carefully slide the fan tray out of the ECN.

Do!
The new fan tray must be inserted immediately after the old one is removed.

4. Install a new fan tray in the ECN by sliding it into the empty slot. Push firmly
so that the fan trays connector is fully engaged with the ECN.

5. Screw and tighten the fan trays screw.

6. Check that the FAN status LED on the ECN front panel is off and that both
new fans are running.

7. Replace the fan tray plastic access cover on the ECN front panel by
pushing the covers right edge in until it snaps into place.

58 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Maintenance

7.4 Changing SID of Flexible Blocks


If the SID of a flexible block (for example ESN204g, EFN324 or ESN212) for
some reason needs to be changed, the node and all the underlying connected
nodes will have to be restarted afterwards.

As a consequence of changing the SID, the configuration of the lines, including


profiles and services, will be lost and must be configured again.

7.5 Gigabit Media Expansion Module


The ECN430 must be powered off before installing or removing a 10 Gigabit
media expansion module. For more information see ECN430 Installation
Guide. In order for EMP to discover the insertion or removal of the module, the
operator must manually force EMP to discover this, using the EMP CLI. EMP
will not automatically poll for the presence of the module.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 59


ECN User Guide

60 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Troubleshooting

8 Troubleshooting

8.1 Diagnose Switch Indicators


Table 5 Troubleshooting Chart
Symptom Cause Action
PWR LED is DC power is Check if the DC power supply is connected
off disconnected to the ECN. Check connections between
the ECN, the power cables, and the DC
power circuit. Check the ECNs fuse
condition. Replace the fuse, if necessary.
DIAG LED is The switch has Power cycle the ECN to see if the condition
on red detected a fault is cleared. If the condition persists, contact
Ericsson.
DIAG LED is The ECN430 The ECN430 has detected a mismatch
flashing red has detected between the startup configuration file and
fast (5 times a a mismatched the hardware. This LED will change to
second) startup configu steady green after the system changes
ration file automatically to the default configuration
file for the current software.
DIAG LED is The ECN430 The ECN430 has detected an unsupported
flashing red has detected 10G module plugged in. Update the switch
slow (1 time a an unsupporte SW to a version that supports that specific
second) d 10G module 10G module.
FAN LED is One or both Replace the fan tray.
on red cooling fans
have a fault
CTRL LED is ENC not Contact Ericsson
off present
CTRL LED is Error in the Log in to the CLI, check if the ECN is
on red ENC or the in Fallback state. Check the log file for
ECN is in errors. Check the interface configuration.
switch mode
If the ECN is not in Fallback state, contact
Ericsson.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 61


ECN User Guide

A port status There is no Verify that the ECN and attached device
LED is off valid link on the are powered on.
port
Be sure the cable is plugged into both the
ECN and corresponding device.
Verify that the proper cable type is used
and its length does not exceed specified
limits.
Check the adapter on the attached
device and cable connections for possible
defects. Replace the defective adapter or
cable if necessary.
A port status There is a Remove the connection to the port.
LED is flashing power overload
red or short circuit Check the connection cable and
on the port connectors for defects and possible short
circuits. Replace the network cable if
necessary.
If the network cable is verified to be OK,
replace the EDA device.

8.2 Power and Cooling Problems


If the power indicator does not turn on when the power cord is plugged in, there
may be a problem with the DC power circuit, power cord, or internal power
supply. However, if the unit powers off after running for a while, check for loose
power connections, power losses or surges from the DC source, and verify that
the units cooling fans are unobstructed and running prior to shutdown. If the
problem still cannot be isolated, the internal power supply may be defective.

8.3 Embedded units


Verify that all system components have been properly installed. If one or more
components appear to be malfunctioning (such as the power cord or network
cabling), test them in another environment where all the other components are
functioning properly.

62 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Troubleshooting

Table 6 Troubleshooting Chart


Symptom Cause Action
Embedded The VMAC domain Either disable the VMAC domain,
unit will not has been set through or use only the allowed topology.
start the CLI, and a node
is connected not
according to the
allowed topology.
When a new
embedded unit is
installed with a wrong
management VLAN
it will take some time
before this is corrected
by the EMP.
ESN108 will The ESN108 HW Check from the Inventory in the
not start revision is not Web Interface, or in CLI that the HW
recognized by the revision of the ESN108 appears in
ECN. the Known HW/SW relations. If not,
upgrade the EAN SW with SW that
supports the ESN108 HW revision.
IP DSLAM will The IP DSLAM Check from the Inventory in the
not start HW revision is not Web Interface, that the HW revision
recognized by the of the IP DSLAM appears in the
ECN. Known HW/SW relations. If not,
upgrade the EAN SW with SW
that supports the IP DSLAM HW
revision.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 63


ECN User Guide

8.4 CLI
Table 7 Troubleshooting Chart
Symptom Action
Cannot connect Be sure the agent is configured with a valid IP address,
using Telnet or subnet mask and default gateway.
SNMP software
If trying to connect to the agent using the IP address for
a tagged VLAN group, the management station must
include the appropriate tag in its transmitted frames.
Check that there is a valid network connection to the
switch and that the port being used has not been disabled.
Check network cabling between the management station
and the switch.
If a Telnet session cannot connect, the switch may have
exceeded the maximum number of concurrent Telnet
sessions permitted. Try connecting again at a later time.
Cannot access Be sure the terminal emulator program is set to VT100
the on-board compatible, 8 data bits, 1 stop bit, no parity and 9600 bps.
configuration Check that the null-modem serial cable conforms to the
program through pin-out connections, see ECN330 Installation Guide or
a serial port ECN320 Installation Guide.
connection
Cannot connect If a connection using SSH fails, the maximum number
using Secure of concurrent SSH sessions permitted may have been
Shell exceeded. Try connecting again at a later time.
Be sure the SSH server is enabled and its control
parameters properly configured on the ECN430-switch,
and that the SSH client software is properly configured
on the management station.
Be sure a public key has been generated on the
ECN430-switch and this key exported to the SSH client.
Be sure an account has been set up on the ECN430-switch
for each SSH user, including user name, authentication
level, and password.
Be sure the clients public key has been imported to the
ECN430-switch (if public key authentication is used).

64 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

9 Reference Information

This section gives some additional information that is not needed for daily
operation.

9.1 Using a MIB Browser


It is possible to use a standard MIB browser to read a limited number of MIB
parameters from the embedded units. For further information see ECN430 MIP
Overview or ECN330 and ECN320 EMP MIB Overview. Note that the SNMP
GET NEXT and SNMP GET BULK operation is not supported.

Stop!
Do not set MIB parameters using a MIB browser if PEM is used. Use the
Advanced Node configuration if needed.

In order to reach the embedded unit (which is concealed from the


rest of the network) the embedded unit must be identified through the
instance part of the SNMP Object Identifier (OID). The embedded unit
is identified by a six to nine digit integer (the leading zeroes may be
omitted). The identifier is constructed according to the following scheme:

Since leading zeroes may be omitted, the digits are always counted from the
right. The following table explains the identifiers.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 65


ECN User Guide

Table 8 Identifiers
Identifier Fixed Topology Flexible Topology
ECN Port or Switch ID Port no. on the ECN or Switch ID + 1000
(5 digits) extension switch :
ECN: 0+port No.
Switch ext. 1: 100+port
No.
Switch ext. 2: 200+port
No.
*
Switch ext. 7: 700+port
No.
Aggregation Switch Port Port No. Port No.
(2 digits)
For IP DSLAM For IP DSLAM
connected directly to connected directly to
the ECN/ext switch or the ECN/ext switch or
for EFN324, always 00. for EFN324, always 00.
OID type (1 digit) 0 : Line OID 0 : Line OID
1: Channel 0 OID (DSL 1: Channel 0 OID (DSL)
only)
2: Channel 1 OID (DSL)
2: Channel 1 OID (DSL
only)
Line No (2 digits) Line number on the Line number on the
node node

Table 9 Examples
ECN Port or Port on OID type Line No Identifier
Switch ID Aggregation
Switch
Port 1 on 3 Line 4 103004
ECN
Port 3 on ext. None Channel 0 10 20300110
switch 2
Switch ID = None Line 19 103500019
35
Switch ID = 4 Channel 1 12 112404212
124

66 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Figure 36 on page 67 illustrates how the Line Identifier is used in the instance.
Note that not all OIDs have a PVC as an instance, in which case, only the Line
Identifier is added to the OID.

Figure 36 OID to an Embedded unit

In the following examples, the integrated MIB Browser of HP OpenView is used.


It is always a good idea to start by checking the inventory of the EAN.

This is done by querying the empInventoryProductNumber parameter, see


Figure 37 on page 68. Note that the port number in the result is given as for
example 3.0, which is an EDN connected directly to port 3.

This query is performed toward the ECN and therefore no line identifier is
needed.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 67


ECN User Guide

Figure 37 EAN Inventory

Figure 38 on page 69 shows an example of how to retrieve the line type


parameter, which is part of the standard ADSL MIB. The only instance is the
Line identification, which is given as 500001 (port one of an EDN connected
directly to port five of the ECN). The result of the query is four (fast or
Interleaved).

68 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Figure 38 Querying ADSL Line Type

9.2 Backup Using SNMP


All the operations related to backup and restore by using SNMP are done by
setting parameters in the private MIB: peaSwm. The MIB contains two groups
relevant for backup and restore:

peaSwmFtpServerDataTable, which is used to define the FTP servers.

peaSwmBRJobTable, which is used to define the backup or restore job.

Refer to the ECN430 MIB Overview, the ECN430 MIB Description, the ECN330
and ECN320 MIB Overview and the ECN330 and ECN320 MIB Description for
detailed information about the MIBs.

Note that it is possible to configure multiple backups (also of automatic type). It


is thus possible to configure two automatic backups, each to a different FTP
server. The backup is initiated by setting MIB parameters in the ECN:

1/1553-LZA 101 464-V2 Uen F 2010-01-06 69


ECN User Guide

Specify an FTP server. This includes specifying the name of the FTP
server, the IP address, the user name and the password of the FTP server.
Furthermore it is necessary to specify the file name and the path to the
directory where the backup file will be stored. It is possible to specify
several servers.

Create a backup job. This includes specifying the type of backup: manual,
scheduled or automatic. The name of the backup file and the path to the
directory where it will be stored needs to be specified as well.

Define timers for the backup job (optional). Timers are used for all SNMP
configured backups. For more information please refer to Section 9.2.3
on page 73.

Define random start interval for the job (optional). For more information
please refer to Section 9.2.4 on page 75.

Activate the backup job. For more information please refer to Section 9.2.5
on page 76.

9.2.1 Specify an FTP Server

In the following it is explained how to specify an FTP server in the ECN.

The FTP server is defined in the table: peaSwmFtpServerDataTable. For more


detailed information about each parameter please refer to the ECN330 MIB
Description. The following parameters are defined:

Status: Select an index that is not used, for example, 1.

Server name: Select a name for the FTP server (optional)

IP address: Specify the IP address of the FTP server.

User name: Define the user name for accessing the server.

Password: Specify the password for the user of the FTP server.

9.2.2 Create the Backup Job

9.2.2.1 Automatic Backup

A manual backup is defined in the table: peaSwmBRJobTable.

The following parameters are set in the MIB tables:

Status: Select an index that is not used, for example, 1.

Name: Select a name for the backup job (optional)

Action: Select backup(1)

70 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Timers: Set MinWait and MaxWait (both optional)

Action type: Select automatic(1)

FTP server: This is the index that defines the FTP server to be used.

FTP server name: The name of the FTP server specified when it was created.
Either the index or the name or both can be used to specify the FTP server.
If no server is specified, the backup file will be placed locally on the ECN in
the directory: /var/backuptmp/.

Path: Specify the path to the directory on the FTP server where the backup file
is going to be stored (optional). If not specified the backup file will be stored in
the home directory of the user. Please note that Windows and Solaris servers
have different ways of specifying directories.

File name: The name of the backup file.

The name of the backup file can be extended. The following values can be
used:

Table 10 Values used for specifying the extension of a backup file


Value File Extension
0 Nothing added
1 Date is added
2 A number 1-10 is added
3 A number 1-20 is added
4 A number 1-100 is added

Example: If the name of the backup file is fullbackup, setting the extension
value to 1 will add the date to the file name. The backup file will thus be
renamed to fullbackup20061005. If the value 2 is set, the name of the file
will be fullbackup1, the next backup will have the name fullbackup2 and
so on. Note that if the file extension is set to two for example, then after ten
backups, the new backup file will again have number 1 appended.

9.2.2.2 Manual Backup

A manual backup is defined in the table: peaSwmBRJobTable.

The following parameters are set in the MIB tables:

Status: Select an index that is not used, for example, 1.

Name: Select a name for the backup job (optional)

Action: Select backup(1)

1/1553-LZA 101 464-V2 Uen F 2010-01-06 71


ECN User Guide

Timers: Set MinWait and MaxWait (both optional). Per default MaxWait is set
to zero and the backup will be executed immediately.

Action type: Select manual(3)

FTP server: This is the index that defines the FTP server to be used.

FTP server name: The name of the FTP server specified when it was created.
Either the index or the name or both can be used to specify the FTP server. If
no server is specified, the backup file will be placed locally on the ECN in the
directory: /var/backuptmp/

Path: Specify the path to the directory on the FTP server where the backup file
is going to be stored (optional). If not specified the backup file will be stored in
the home directory of the user. Please note that Windows and Solaris servers
have different ways of specifying directories.

File name: The name of the backup file.

The name of the backup file can be extended. The following values can be
used:

Table 11 Values used for specifying the extension of a backup file


Value File Extension
0 Nothing added
1 Date is added
2 A number 1-10 is added
3 A number 1-20 is added
4 A number 1-100 is added

9.2.2.3 Scheduled Backup

A scheduled backup is a backup job that will start running at a specified time.
The job can be configured to run a number of times at a specified interval.

The parameters are almost the same as described for a manual backup in
Section 9.2.4 on page 75 and the same MIB table is used.

The parameters specific for the scheduled backup is listed in the following. The
other parameters are set as for the manual backup.

Action type: Select periodic(2)

Timers: Set MinWait and MaxWait (both optional). Per default MaxWait is set
to zero and the backup will be executed immediately.

Start: Specify the time when the backup will start. The time is the local time
on the ECN and must be specified in bytes. The two first bytes specify the

72 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

year, followed by month, day, hours, minutes and seconds all specified by one
byte each. The values must be converted to hexadecimal. Example: The date
2006-09-26 21:30:00 is specified as (2006 is 07D6): # 0x07 0xD6 0x09 0x1A
0x15 0x1E 0x00. The start time must be a time in the future.

Period: Specify the period between periodic backups. If the value is set to 0,
the backup will be run only once. The time must be specified in bytes in the
same way as for the start. Example: A period of one week can be specified as:
# 0x00 0x00 0x00 0x07 0x00 0x00 0x00.

Number of times: Specify the number of times the periodic backup will run. If
the value 0 is specified, the backup job will run after each period (interval) as
long as the backup job is not deleted.

9.2.3 Backup Job Timers


There are two timers that are used in connection with any backup job configured
by SNMP (not CLI or Web):

MinWait a global parameter for all back jobs (default 1 hour). This timer
restarts every time a configuration change occurs.

MaxWait a specific parameter that can be set explicitly for each backup
job. This timer starts when there is a backup request. The default value for
this timer depends on the job type:

0 Automatic backup: 1 hour

0 Manual or scheduled backup: zero

These timers are mostly effective when automatic backup is used. However,
they are active in all jobs initiated through SNMP. As long as the MaxWait is
zero, the timers will not have any effect, but by keeping them active, there is a
possibility to use them also in the manual or scheduled backup. The purpose
of the timers is to avoid initiation of a backup during a series of configuration
commands. The following figure illustrates what will happen if there are no
timers and the ECN is configured with multiple parameters (backup is set to
auto):

Figure 39 Auto Backup without Timers

1/1553-LZA 101 464-V2 Uen F 2010-01-06 73


ECN User Guide

As can be seen from Figure 39 on page 73, three backup jobs will be initiated,
causing a lot of traffic on the links and load on the ECN processor. By
introducing some delay (timers) it is possible to wait until the configuration is
finished and then make one backup that includes all the new parameters. In
order to do that, the two timers are used. It is the timers that initiate the backup
job upon expiry, and the configuration (or activation of a backup through SNMP)
is a backup request that activates the timers.

Figure 40 on page 74 illustrates the same situation when timer MinWait is


introduced.

Figure 40 Auto Backup with MinWait Timer

As illustrated, if MinWait timer has a reasonable value, only one backup will be
made when the configuration is finished. However, as long as the node is being
configured, no backup will be taken. In order to ensure that a backup will be
taken at some point, MaxWait timer is used.

74 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Figure 41 Auto Backup with Both Timers

A backup will be initiated when any of the timers expires. Note that the MaxWait
timer is not restarted by new backup requests after it is started. For both
MinWait and MaxWait, the action to take when they expire can be defined. The
possible actions are:

Run job: Execute the backup job (default).

Trap: Send a trap indicating that the timer expired.

None: Do nothing.

A start interval can be specified in hours indicating when a new job may start
after it is first created and ready to start. A random start time within an interval
may prevent bottleneck problems at the FTP server. If set to zero, the job
must start as soon as it is activated.

9.2.4 Random Start Interval


Random start interval (DateStartInterval) can be used to prevent traffic storms
due to scheduled backups in multiple nodes. It is not recommended to use it for
any other type of back up. The random start interval is given in hours, and will
delay the start of a backup with a random time interval from within the given
time. If the value is set to zero (default) no delay will be introduced.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 75


ECN User Guide

9.2.5 Backup Job Activation

Set the RowStatus parameter to initiate the backup job.

Start the backup job by setting the status to active(1). If the status after the
backup has been done has the value backupSuccess(4), the backup was done
successfully. When the status of the backup job has been read, the backup job
can be deleted by setting the status to destroy(6).

9.3 Restore Using SNMP


Restoring the configuration is almost the same as creating a backup.

During a restore, the EMP will be restarted, so that the operator needs to
reconnect to the ECN. A restore must be defined as a manual job that will start
immediately after it is defined, and only run once. It cannot be scheduled. The
restore process will restore the configuration files saved in the backup file. The
restore will only succeed if the following conditions are fulfilled:

All the necessary software must be installed.

The hardware configuration must be the same as when the backup was
made (that is the same type of embedded elements must be connected).

The EMP must be configured with the same external and internal
management IP-Address and VLAN and the same uplink and downlink
ports must be used.

The same EMP software version must be running.

As for the backup procedure an FTP server must be created first, as described
in Section 9.2.1 on page 70.

If the FTP server is not specified, the restore job will look for the backup file in
the local directory: /var/backuptmp/on the ECN.

A status parameter for the restore job indicates whether the job is running or
completed. The status will be in the state of completed when the restore job
has finished. The restore job will fetch the specified backup file, and the result
is kept until the restore job is deleted.

9.4 Built-in Local Configuration


It is possible to configure lines and provide services in all embedded units
(except the EFN324) by using the LCT.

The configuration is done using profiles, which can be created and edited in
the LCT. A profile is a collection of configuration parameters. It has a name
and an index, and by assigning it to a line, the line is configured with the values
defined in the profile. The ECN can contain multiple profiles for the same profile

76 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

type. It is possible to create new profiles and edit existing profiles. A profile
cannot be edited while in use (assigned to a line).

When the ECN boots for the first time, it will automatically generate the
following default profile files:

Table 12 Auto Generated Profile Files


File Description
DslAlarmProfile.1 Default alarm configuration for any line. Valid for
both EDN312x and EDN612. ADSL and VDSL.
AdslLineProfile.2 Default line profile parameter settings for any ADSL
line in both EDN312x and EDN612.
VdslLineProfile.1 Default line profile parameter settings for any VDSL
line.
VdslPsdProfile.1 Default PSD settings for any VDSL line
AdslPsdProfile.1 Default PSD settings for any ADSL line

When an IP DSLAM is discovered, a configuration file for that specific IP


DSLAM is created by the ECN. When a line is later configured by assigning
profiles to it from the LCT, the configuration parameters defined in the profiles
are saved in the configuration file. Any changes made for any of the lines of a
specific IP DSLAM will result in an update (change) of this configuration file.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 77


ECN User Guide

Figure 42 IP DSLAM Configuration Files

As illustrated in Figure 42 on page 78, there can be several profile files of each
type. Each of these files has an index number. If a line is not configured with a
specific profile, then according to the node type, the following profiles are used:

EDN612 Line profile 1 (VDSL line profile), VDSL PSD profile 1, ADSL
PSD profile 1, Alarm profile 1

EDN312x Line profile 2 (ADSL line profile), ADSL PSD profile 1, Alarm
profile1

If a specific configuration for a specific ESN212 (based on the port to which it is


connected to) is desired, it is possible to add the port number to the file name.
For example, the file named ESN212_DefConfig_101_0 will automatically be
loaded to the ESN212 connected to port one of the first extension switch. The
file named ESN212_DefConfig_203_0 will be automatically loaded to the
ESN212 connected to port three of the second extension switch, and so on. For
ESN212 in Flexible blocks, add 1000 to the SID. For example the file named
ESN212_DefConfig_1035_0 will be automatically loaded to the ESN212 with
SID=35. The ECN will always use a port specific ESN212 default configuration
file before using the general default configuration file.

As mentioned before, the default configuration files are only loaded when
a node is first discovered by the ECN. If it is desired to load a new default
configuration file, the node must be disconnected and removed from the ECN

78 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

inventory. When it is reconnected, it will be treated as a new node and the


default configuration loaded to it.

9.4.1 Modifying Default Configuration Files


All default files can be modified. The profiles can be modified in the LCT and
then exported or imported. The ESN212 files are a backup of a configured
ESN212.

9.4.2 Exporting profiles

1. Create the profiles using the WEB LCT.

2. Create an FTP session (username = root and password = secret) to the


ECN.

3. Export of the profiles can be performed by downloading the profiles to an


external location/directory. The profiles are stored persistently as files in
the following directories of the ECN:

Table 13 Directories and Files


ECN Directory Files
/var/cfgProfileStorage/ala Alarm profiles
rmProfiles
/var/cfgProfileStorage/line Line profiles, both ADSL and VDSL
Profiles
/var/cfgProfileStorage/vdsl VDSL PSD profiles
PsdProfiles

9.4.2.1 Importing profiles

1. Create an FTP session (username = root and password =


secret) to the ECN. 2. /var/cfgProfileStorage/alarmProfiles
/var/cfgProfileStorage/lineProfiles /var/cfgProfileStorage/vdslPsdProfiles
3. Restart the EMP using the CLI command restart enc.

2. The profiles can be imported by uploading the profiles to the following


directories of the ECN:

/var/cfgProfileStorage/alarmProfiles

/var/cfgProfileStorage/lineProfiles

/var/cfgProfileStorage/vdslPsdProfiles

3. Restart the EMP using the CLI command restart enc.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 79


ECN User Guide

9.4.2.2 Creating and Modifying ESN212 Configuration Files

An ESN212 must be used in order to create a configuration file. The


configuration file is a backup of a running ESN212. Note that it is not possible
to edit an existing backup file. The file contains hidden characters and syntax
rules that make editing impossible.

To create a configuration file:

1. Configure the ESN212 to the desired functionality using the ESN212 CLI
(please refer to the ESN212 and ESN204g CLI User Guide).

2. Backup the running configuration using the ESN212 CLI: esn212# write
startup-config.

3. Upload the configuration files for the ESN212 to /var/tftpboot/MPCon


figFiles/ on the FTP server on the ECN using the following file name

convention:

For example:

esn212# copy startup-config tftp://10.0.100.1/MPConfigF


iles/ESN212_DefConfig_101_0

4. Repeat for all the necessary files.

Restore the configuration file:

1. Find the IP address of the ESN212 using the EMP CLI and locate the node
according to the Port No.:

emp-cli# show ecn inventory


Port No. Status Component HW IP address MAC ***
*
*
102.0 Reachable ESN212 P1A 10.0.1.8 00:01:EC:CF:9F:75

2. Log on the ESN212 CLI and execute the following commands:

esn212# copy tftp://10.0.100.1/MPConfigFiles/102.0_10.0


.1.8 startup-config

80 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

esn212# restart

If the restore is made for a backup file created by the ECN use the file
name: 102.0_10.0.1.8_back.startup.conf (102.0_10.0.1.8 is the
node identification according to the file naming convention described in
this section). For example:

esn212# copy tftp://10.0.100.1/MPConfigFiles/102.0_10.0


.1.8_back.startup.conf startup-config

esn212# restart

Note that the ESN212 must be restarted after the restore in order to run
with the new configuration.

9.5 Configuration of VLANs in Star Topology with ESN410


and ECN330
This section describes how to configure the VLANs on ESN410 extension
switches in a star topology. The extension switches connection to the ECN can
be either daisy chain, or through an aggregation switch (star topology).

Examples of the commands needed to configure the extension switches and


the ECN are given for each case.

9.5.1 General Configuration

In both daisy chain topology and star topology, the ESN410 must be defined as
a switch-extension in the EMP using the EMP CLI interface.

In the ESN410 extension switches configuration of internal management VLAN


configuration, IP address, internal management VLAN, SNMP alarm receiver,
alarm type, and NTP server has to be done manually. The ECN will configure
all the service VLANs automatically.

When the first extension switch is added, using the add esn410-uplink
command, the VLAN configuration of the specified uplink port on the ECN330
switch will be changed in order to allow traffic on both the internal and external
management VLAN, instead of the external management VLAN only.

Note: All configuration of the EMP unmanaged aggregation switch (the star
center) must be done manually.

9.5.2 VLAN Configuration in Daisy Chained Topology


Figure 43 on page 82 shows an example of the VLAN configuration for a
daisy-chained topology. Possible port numbers for the daisy chain links, as well
as IP addresses for the extension switches, are also indicated.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 81


ECN User Guide

All VLAN configurations on the unmanaged aggregation switch must be done


manually. For the extension switches, only the management VLANs need to be
configured manually.

Figure 43 VLAN Configuration Example for Daisy Chained Topology

9.5.2.1 Management VLAN Configuration for the First ESN410 Extension Switch

This configuration must be done using CLI. Connect to the first ESN410 switch
using a console connection. The following sequence of commands must be
entered to change the VLAN settings for the ESN410 extension switch:

Console# conf

Console(config)#vlan database

Console(config-vlan)# vlan 247 name intmgm media ethernet


state active

Console(config-vlan)# vlan 248 name dynmgm media ethernet


state active

Console(config-vlan)# exit

Console# interface ethernet 1/1-8

82 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Console(config-if)# switchport allowed vlan add 247 tagged

Console(config-if)# switchport allowed vlan remove 246

Console(config-if)# switchport allowed vlan add 248


untagged

Console(config-if)# switchport native vlan 248

Console(config-if)# exit

Console(config-if)# interface ethernet 1/11-12

Console(config-if)# switchport allowed vlan add 247 tagged

Console(config-if)# switchport allowed vlan add 248


untagged

Console(config-if)# switchport native vlan 248

Console(config-if)# exit

Console(config-if)# interface ethernet 1/11

Console(config-if)# switchport allowed vlan remove 246

Console(config-if)# exit

The IP address assigned to the ESN410 must be within the range 10.0.0.1 to
10.0.0.254. In the example, the IP address 10.0.0.37 is used.

Console# configure

Console(config)# management vlan 247

Console(config)# management vlan default-gateway 10.0.100.1

Console(config)# interface vlan 247

Console(config)# ip address 10.0.0.37 255.255.0.0

Console(config)# exit

The following command is used to copy the configuration to the start up file,
to be used at restart of the switch. This will end the configuration of the
ESN410 switch. When the command is executed accept the default name:
esn410configuration.cfg.
Console# copy running-config startup-config

9.5.2.2 Configuration of the ECN330

Each ESN410 in the chain must be configured using the switch-extension


command:

1/1553-LZA 101 464-V2 Uen F 2010-01-06 83


ECN User Guide

For the first ESN410 extension switch use the following command example:

ecn330 config)# ecn switch-extension add esn410-uplink


remote-uplink-port 25 ip 10.0.0.37

(25 refers to the port that the first extension switch is connected to on the
ECN330, while 10.0.0.37 is the IP address of the first ESN410 extension
switch.)

For the second to seventh ESN410 extension switch use the following
command example (changing the IP address as required):

ecn330(config)# ecn switch-extension add esn410-uplink


remote-uplink-port 11 ip 10.0.0.38

(11 refers to the port that the extension switch is connected to on the previous
extension switch.)

Finally, to prevent service traffic between the daisy chained ESN410s, use
the following command:

ecn330(config)#ecn switch-extension interconnection-esn410


service-vlan disable

9.5.3 VLAN Configuration in Star Topology


Figure 44 on page 85 shows an example of the VLAN configuration for Star
topology. The figure indicates whether the VLANs are tagged (t) or untagged
(u). Possible port numbers for the ESN410 uplinks, as well as IP addresses for
extension switches, are also indicated.

84 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

Figure 44 VLAN Configuration Example for Star Topology

In the ESN410 aggregation switch, the port connected to the ECN330 must
have both the external and internal management VLANs configured, but no
Service VLANs should be configured on this port.

For each ESN410 switch, the internal management VLAN and Service VLANs
must be configured on the uplink port used to connect to the aggregation
ESN410 switch.

In the ESN410 extension switches, the internal management VLAN (on all
ports), IP address, internal management VLAN, SNMP alarm receiver, alarm
type, and NTP server configuration has to be done manually. The ECN will
configure all the service VLANs automatically.

9.5.3.1 Management VLAN Configuration for the ESN410 Extension Switches

The uplink ports on the ESN410 extension switches must allow VLAN 247
and VLAN 248. VLAN 246 must be removed from all switch ports. This
configuration must be done using CLI. Connect to each the switch using a
console connection. The following sequence of commands must be entered to
change the VLAN settings:

Console# conf

1/1553-LZA 101 464-V2 Uen F 2010-01-06 85


ECN User Guide

Console(config)# vlan database

Console(config-vlan)# vlan 247 name intmgm media ethernet


state active

Console(config-vlan)# vlan 248 name dynmgm media ethernet


state active

Console(config-vlan)#exit

Console(config)#interface ethernet 1/1-12

Console(config-if)# switchport allowed vlan add 247 tagged

Console(config-if)# switchport allowed vlan add 248


untagged

Console(config-if)# switchport native vlan 248

Console(config-if)# switchport allowed vlan remove 246

Console(config-if)# switchport allowed vlan remove 1

Console(config-if)# exit

The IP address assigned to the ESN410 switch must be within the range of
10.0.0.1 to 10.0.0.254. In the example, the IP address 10.0.0.37 is used

Console# configure

Console(config)# management vlan 247

Console(config)# management vlan default-gateway 10.0.100.1

Console(config)# interface vlan 247

Console(config-if)# ip address 10.0.0.37 255.255.0.0

Console(config-if)# exit.

The following command is used to copy the configuration to the start up file
to be used at restart of the switch. This will end the configuration of the
ESN410 switch. When the command is executed accept the default name:
esn410configuration.cfg.

Console# copy running-config startup-config

9.5.3.2 Configuration of the ECN330

Each extension ESN410 switch must be configured in the ECN330 using the
switch-extension command.

For the first ESN410 extension switch use the following command example:

86 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

ecn330 (config)# ecn switch-extension add esn410-uplink


remote-uplink-port 25 ip 10.0.0.37

(25 refers to the port that the first extension switch is connected to on the
ECN330, while 10.0.0.37 is the IP address of the first ESN410 extension
switch.)

Note: In star topology, the first extension switch refers to the switch
connected first chronologically, in other words, at a time before the
connection of the other extension switches. (Unlike for daisy-chain
topology, in star topology, there is no physical configuration limitation
on which extension switch is first.) The other extension switches are
also registered in the time order in which they are connected.

For the second to seventh ESN410 extension switches use the following
command example (changing the IP address as required):

ecn330 (config)# ecn switch-extension add esn410-uplink


remote-uplink-port 11 ip 10.0.0.38

9.6 Programs Packages under Open Source Licenses


This section gives an overview of the open source licenses on which the ECN
is based. These are the GNU Public License Terms, the Apache 2.0 License,
the Apache 1.1 license and the LGPL 2.1 license.

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.

These programs are free software; you can redistribute them and/or modify
them under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your option)
any later version.

See the GNU General Public License in the Third Party License Agreement
for more details.

The EMP application contains standard open source packages from Jakarta
Commons Net.

The programs are distributed in the hope that they will be useful, but WITHOUT
ANY WARRANTY.

This Product includes software developed by the Apache Software Foundation


(http://www.apache.org).

The EMP application contains open source code from Enterprise Edt, called
edtFTPj. This is available for distribution under an LGPL license and should
not be modified.

1/1553-LZA 101 464-V2 Uen F 2010-01-06 87


ECN User Guide

The programs packages are available for download at:

ftp-hotel.Ericsson.net

Login: eda-gpl

Password: q5prst

9.6.1 Linux Kernel


Table 14 Linux Kernel
Package
kemel

9.6.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

88 1/1553-LZA 101 464-V2 Uen F 2010-01-06


Reference Information

9.6.3 Linux Libraries

Table 16 Linux Libraries


Package
glibc
Linux-PAM
ncurses
Pam-Radius
readline
termcap
uClibc

1/1553-LZA 101 464-V2 Uen F 2010-01-06 89

Вам также может понравиться