Ericsson ECN320 User manual

ECN330 and ECN320 User Guide

.

ii

1553-CNH 160 0787 Uen PA2 2005-09-23

Copyright

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 Control-

ler in ECN. The Linux distribution for ECN is based on standard open source

packages widely used in the Linux community. Please refer to the Third Party

License Agreements for the license terms.

Trademark List

Windows®

Windows is a registered trademark of Microsoft

Corporation

Windows NT®

Windows NT is a registered trademark of Microsoft

Corporation

Solaris®

Solaris is a registered trademark of Sun Microsys-

tems, Inc.

.

1553-CNH 160 0787 Uen PA2 2005-09-23 iii

Contents

1 Introduction to this Guide 1

1.1 Conventions 1

1.2 Revision History 2

1.2.1 This Revision 2

1.2.2 Version G 2

1.2.3 Version F 2

1.2.4 Version E 3

1.2.5 Version D 3

1.2.6 Version C 3

1.2.7 Version B 4

1.2.8 Version A 4

2 Introduction to the ECN 5

2.1 Topology of the EAN 6

2.2 Management of EAN 8

3 ECN Functions, Features and HW 9

3.1 Switching Unit Architecture and Features 10

3.1.1 Connections 10

3.1.2 Performance 11

3.1.3 PoE Ports 12

3.1.4 1000BASE-T RJ-45 and SFP Ports 13

3.2 Reserved VLANs, Interfaces and Ports Designation 15

3.3 LEDs User Interface 16

3.4 Power Supply Input Connector 18

3.5 Fan Tray 18

4 Maintenance 20

4.1 Replacing ECN 20

4.2 Replacing a Fuse 20

Error! No text of specified style in document.

iv 1553-CNH 160 0787 Uen A 2005-09-26

4.3 Replacing a Fan Tray 21

5 Management Features Overview 23

5.1 Ethernet Access Node Alarms 24

5.2 Startup Failure 24

5.3 System Log 25

6 Description of the EAN 26

6.1 EAN in the Network 27

6.1.1 EAN Topologies 29

6.2 Line and Node Identification 34

6.3 Installation 38

7 Initial Configuration and Commissioning 39

7.1 The ECN Local Craft Tool 40

7.2 Installation of Software 40

8 Management from PEM 42

8.1 Discovering an EAN 42

8.1.1 Prerequisites 42

9 Web interface 43

9.1 Entering the Web Interface 43

9.2 System 43

9.3 Status 45

9.4 Configuration 51

9.5 Log 53

9.6 Test 55

10 Factory Defaults 57

11 Command Line Interface 58

11.1 Using the Console Connector 59

11.2 Using Telnet 60

Error! No text of specified style in document.

1553-CNH 160 0787 Uen A 2005-09-23

v

11.2.1 Running the ECN as an Switch 61

11.2.1.1 ECN330 Switch 61

11.2.1.2 ECN320/ESN310 Switch 62

11.2.2 Adding Switch Extensions to an EAN 63

11.2.2.1 ECN330 Switch Connected to an ECN 64

11.2.2.2 ECN320/ESN310 Switch Connected to an ECN 65

11.2.3 Adding more Switches to an EAN 66

11.3 Entering Commands 68

11.3.1 Keywords and Arguments 68

11.3.2 Minimum Abbreviation 68

11.3.3 Command Completion 69

11.3.4 Getting Help on Commands 69

11.3.5 Partial Keyword Lookup 70

11.3.6 Using Command History 70

11.3.7 Command Execution 70

11.3.8 Scripts 70

11.3.9 Special Commands 70

11.3.10 CLI Editing Keystrokes 71

11.4 Overview of CLI Commands 72

11.5 General Commands 73

11.5.1 end 73

11.5.2 exit 74

11.5.3 ping 74

11.5.4 rcli 75

11.5.5 restart 76

11.6 config 77

11.6.1 copy-dslport 78

11.6.2 dslport 78

11.6.2.1 alarm-thresholds 79

11.6.2.2 alarms 81

11.6.2.3 channel 81

11.6.2.4 line 83

11.6.2.5 performance-data 86

Error! No text of specified style in document.

vi 1553-CNH 160 0787 Uen A 2005-09-26

11.6.2.6 PVC commands 87

11.6.2.7 transmission-mode 97

11.6.3 ecn 98

11.6.3.1 inventory 99

11.6.3.2 link-aggregation 100

11.6.3.3 port 101

11.6.3.4 redundancy 107

11.6.3.5 spanning-tree 108

11.6.3.6 unmanaged-switch 115

11.6.3.7 ip 116

11.6.3.8 switch-extension 117

11.6.3.9 auto-rediscover 120

11.6.4 edn 121

11.6.4.1 link-configuration 121

11.6.5 esn 122

11.6.5.1 link-aggregation 122

11.6.5.2 port 123

11.6.5.3 spanning-tree 124

11.6.5.4 power-on-uplink 124

11.6.6 exn 125

11.6.6.1 line 126

11.6.6.2 packet-distribution 127

11.6.6.3 line-type 127

11.6.7 load-configuration 128

11.6.8 reset-dslports 129

11.6.9 save-configuration 130

11.6.10 system 130

11.6.10.1 aaa 131

11.6.10.2 backup-configuration 132

11.6.10.3 calendar 133

11.6.10.4 cli-autologout 133

11.6.10.5 install 134

11.6.10.6 interface 135

Error! No text of specified style in document.

1553-CNH 160 0787 Uen A 2005-09-23

vii

11.6.10.7 local-management 137

11.6.10.8 ntp 138

11.6.10.9 password 140

11.6.10.10 pem-management 140

11.6.10.11 prompt 141

11.6.10.12 radius-server 142

11.6.10.13 restore-configuration 143

11.6.10.14 service-vlan 144

11.6.10.15 show 145

11.6.10.16 turn 146

11.6.10.17 update 147

11.6.10.18 vlan-unaware 147

11.7 led-test 149

11.7.1 led-test 149

11.8 show 150

11.8.1 dslport 150

11.8.2 ecn 151

11.8.3 edn 152

11.8.4 exn 152

11.8.5 esn 153

11.8.6 system 155

11.9 Fallback State CLI Commands 156

11.9.1 Commands 156

11.9.1.1 calendar 157

11.9.1.2 exit 157

11.9.1.3 interface 157

11.9.1.4 restart 157

11.9.1.5 update 158

11.9.1.6 show 158

11.9.1.7 clear 159

11.9.1.8 ping 160

12 Using a MIB Browser 161

Error! No text of specified style in document.

viii 1553-CNH 160 0787 Uen A 2005-09-26

13 Troubleshooting 166

13.1 Diagnose Switch Indicators 166

13.2 Power and Cooling Problems 167

13.3 Embedded Nodes 167

13.4 CLI 168

14 Specifications and Technical Details 169

15 Programs Packages under the GNU Public License Terms 170

15.1 Kernel 170

15.2 Applications 171

15.3 Libraries 171

Glossary 172

Index 176

Introduction to this Guide

1553-CNH 160 0787 Uen PA2 2005-09-23

1

1 Introduction to this Guide

This guide describes the EDA Ethernet Controller Node ECN and is valid

for both the ECN330 and the ECN320. The term ECN refer to ECN320 and

ECN330. The term ECN switch refer to ECN320 and ECN330 in switch

mode. The term ECN320/ESN310 switch refer to ECN320 in switch mode.

When an ECN is illustrated in a figure, an ECN330 with an uplink port 27 is

used. The appearance of the ECN320 is the same just without this uplink

port.

The guide describes the concept, the hardware and the functionality. Fur-

thermore, it provides an overview of software features, and detailed infor-

mation on how to use the Command Line Interface (CLI) to configure the

ECN.

The guide is intended for both installation personnel and system adminis-

trators responsible for operating and maintaining network equipment.

The reader should have a basic knowledge of general switch functionality,

the Internet Protocol (IP), and Simple Network Management Protocol

(SNMP) in order to understand and utilize the information in the sections

describing the Command Line Interface (CLI) and management.

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 a

more information of the standards, please refer to the standard specifica-

tions.

In order to fully understand the function and use of the ECN, it is recom-

mended to read the System Overview and PEM User Guide.

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 Op-

tions menu item.

OK : A button in a GUI.

Introduction to this Guide

2 1553-CNH 160 0787 Uen PA2 2005-09-23

Bold monospace letters mark text typed by the user (input) in Com-

mand 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.2 Revision History

This guide is valid for EDA 2.2 RA1. Other product version, with functions

not described in this guide may be available.

1.2.1 This Revision

The Command Line Interface (CLI) is updated to reflect the command

structure.

1.2.2 Version G

The following changes were made:

• Minor textual connection added

• Added a section of how to run the ECN as a switch

1.2.3 Version F

The following has been changed:

• The EAN topologies have been revised. The ECN now supports the

FE-E1/T1 converter EXN104 and the ELN220 as embedded nodes.

• The ECN also supports daisy chaining of the optical switch ELN220

and the electrical switch ESN310.

• The ECN supports flexible service access.

Introduction to this Guide

1553-CNH 160 0787 Uen PA2 2005-09-23

3

• The CLI commands have been revised and new commands have been

added in order to support the new topologies (embedded nodes, and

daisy chaining).

• Support of reverting an ECN to an ESN310 and back again.

1.2.4 Version E

The following has been changed:

• Support of ELN220 in an EAN is described

• Support of unaware VLAN in ECN from CLI is described

• Support of ECN auto completion on parameter added

• Change of password through the CLI added

• Correction of the CLI command link-configuration

• Minor corrections of illustrations

1.2.5 Version D

The following has been changed:

• Correction to the CLI command: link-configuration

• Minor textual corrections to sections 2, and 3.

• The section describing installation and upgrading of software has been

revised and moved.

• The sections have been slightly rearranged.

1.2.6 Version C

The following has been changed:

• The ECN has been supplied with dual power input ports

• The rear of the ECN has been supplied with two 20A fuses, one for

each power input

• The ECN has been supplied with an uplink 100 Base-FX option

Introduction to this Guide

4 1553-CNH 160 0787 Uen PA2 2005-09-23

• The web interface has been changed with new layout

• New CLI structure and layout

• New CLI commands have been added

1.2.7 Version B

The following has been changed:

• Upgrading SW description is moved to ECN330 Installation Guide or

ECN320 Installation Guide.

• Replacing ECN added

• Service VLANs are supported and configured by PEM

• No special attention should be paid when connecting ESN108

1.2.8 Version A

The first version of the guide.

Introduction to the ECN

1553-CNH 160 0787 Uen PA2 2005-09-23

5

2 Introduction to the ECN

The ECN is composed of two main components: The Ethernet Node Con-

troller (ENC), and a 24 ports Ethernet switch with Power over Ethernet

(PoE) capabilities. The Ethernet Controller Node (ECN) is a unit that con-

trols and aggregates other EDA nodes (embedded nodes). Together, the

ECN and the embedded nodes constitute a logical node – the Ethernet Ac-

cess 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 nodes connected to the ECN.

The following EDA nodes can be used as embedded nodes (for further de-

tail refer to section

6 on page 26):

• IP DSLAMs (EDN110 and EDN312)

• ESN108 switch,

• Optical ELN220 switch

• EXN104 FE to E1/T1 converter

• ESN310

• ECN320/ESN310 switch

• ECN330 switch

Other 3

rd

party unmanaged switches can also be used in the EAN, but the

following sections primarily focus on the EAN with the EDA nodes listed

above.

The software in the ECN contains the EDA Management Proxy (EMP). The

means that there is no dependency on the Access Domain Server during

start-up or restart. The EAN is completely autonomous and self-sustained,

as the Access Domain Server functions are hosted by the ECN, see

Figure

1 on page

6.

The EAN can be managed without PEM using the Command Line Interface

of the ECN. This is described later in this guide.

All embedded elements are Plug and Play, with automatic registration in

PEM. The EAN elements may be placed in one cabinet, appearing physi-

cally as a single node, or distributed in different sites on different locations.

Introduction to the ECN

6 1553-CNH 160 0787 Uen PA2 2005-09-23

For Information about the ECN330-switch refer to ECN330-switch User’s

Guide. For Information about the ECN320/ESN310 switch refer to ECN320

User Guide

2.1 Topology of the EAN

Depending on how the topology of the EAN is designed, based on the

nodes described above, the supported number of end-users may vary.

Below in

Figure 1 on page 6 an example of how the topology of an EAN

can be designed is shown with IP DSLAMs connected either directly to the

ECN or through the 8-port switch ESN108.

Fully extended with ESN108 switches on all 24 ports of the ECN and eight

12-ports IP DSLAMs on all ports of the ESN108 will enable the EAN to

support 2304 end-users.

Another realization of the EAN is the EDN288, which is a pre-cabled solu-

tion, delivered in a subrack. The EDN288 contains one ECN with the 12-

line IP DSLAM (EDN312) connected to all 24 ports, and thus supports 288

end-users. For a more detailed description of this specific EAN please see

the EDN288 User Guide and the EDN288 Installation Guide.

PEM

Ethernet Access Node

ESN108

(optional)

EDNXXX

ECN

Alarm

DHCP

FTP

TFTP

SNTP

ConfigSW

Ethernet

Management

Proxy

Towards

broadband

backbone

Figure 1 The EAN with ESN108 and IP DSLAMs

Introduction to the ECN

1553-CNH 160 0787 Uen PA2 2005-09-23

7

The EAN topology is described in more details in section 6.1 on page 27,

where examples using the ELN220 optical switch, the ESN310 switch and

the EXN104 FE to E1 converter are discussed.

Introduction to the ECN

8 1553-CNH 160 0787 Uen PA2 2005-09-23

2.2 Management of EAN

The EAN can be installed and configured for site verification without con-

nection to PEM.

During normal operation, if the connection from PEM to the EAN is lost,

traffic to and from the end-users will continue, and it will only be possible to

change the end-user parameters as for example the line speed. The EAN

will continue to run in local mode, which means that the ECN starts acting

as a stand-alone Domain Server using the last valid configuration and SW

in order to continue operation.

If any configuration changes (for the EAN) are made in PEM while the EAN

is not reachable, the EAN will have to be synchronized manually from PEM

when the connection is restored.

The Command Line Interface (CLI) of the ECN makes it possible to run the

EAN without connection to PEM, that is, use the CLI for management, con-

figuration and for DSL line provisioning. For full management configuration

PEM must be used.

ECN Functions, Features and HW

1553-CNH 160 0787 Uen PA2 2005-09-23

9

3 ECN Functions, Features and HW

The following sections describe the ECN functions, features and hardware.

The ECN is used as the first and second level aggregation switch in the

EDA network, while also supplying directly connected IP DSLAMs with DC

power over the Ethernet connections.

As well as its Power-over-Ethernet capabilities, the ECN provides compre-

hensive network management features, such as multicast switching, virtual

LANs, and Layer 2 Quality of Services (QoS), which provide reliability and

consistent performance for network traffic.

Figure 2 on page 9 shows the

front and rear panels of the ECN (ECN330).

Figure 2 ECN330 Front and Rear Panels

ECN Functions, Features and HW

10 1553-CNH 160 0787 Uen PA2 2005-09-23

3.1 Switching Unit Architecture and Features

The ECN employs a wire-speed, non-blocking switching fabric.

This permits simultaneous wire-speed transport of multiple packets at low

latency on all ports. The ECN also features full-duplex capability on all

ports, which effectively doubles the bandwidth of each connection.

Auto-negotiation is used to select the optimal transmission speed and

communication mode for each connection. With store-and-forward switch-

ing and flow control, maximum data integrity is always maintained, even

when the loading is heavy.

3.1.1 Connections

The ECN includes 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. This is utilized in the ELN220 scenario described in

the introduction of this guide.

The ECN330 also contains one independent 1000BASE-T RJ45 port (Port

27) that operates at 10 Mbps or 100 Mbps, half or full duplex, or at 1000

Mbps, full duplex.

The ECN has 24 10BASE-T/100BASE-TX RJ-45 ports. The features of the

ports are summarized below:

• 24 dual-speed ports for 10 or 100 Mbps Ethernet connections, with

support for automatic MDI/MDI-X. All 10/100 RJ-45 ports support

Power-over-Ethernet (PoE)

• Two Gigabit combo ports—use either 10/100/1000BASE-T RJ-45 or

Small Form Factor Pluggable (SFP) transceiver slot (100 Mbps and

1000 Mbps)

• One independent 10/100/1000BASE-T Gigabit Ethernet port

• Auto-negotiation enables each RJ-45 port to automatically select the

optimum communication mode (half or full duplex) for the attached de-

vice

• Unshielded (UTP) cable supported on all RJ-45 ports: Category 3 or

better for 10 Mbps connections, Category 5 or better for 100 Mbps

connections, and Category 5, 5e, or 6 for 1000 Mbps connections

• IEEE 802.3u, IEEE 802.3z, and IEEE 802.3ab compliant

ECN Functions, Features and HW

1553-CNH 160 0787 Uen PA2 2005-09-23

11

3.1.2 Performance

• Transparent bridging – The ECN supports IEEE 802.1D transparent

bridging. The address table facilitates data switching by learning ad-

dresses, and then filtering or forwarding traffic based on this informa-

tion. The address table supports up to 8K and 16K addresses

(ECN320/ECN330).

• Store-and-Forward Switching – The ECN copies each frame into its

memory before forwarding them to another port. This ensures that all

frames have a standard Ethernet size and have been verified for accu-

racy with the cyclic redundancy check (CRC), thus preventing bad

frames from entering the network and wasting bandwidth. To avoid

dropping frames on congested ports, the ECN provides 32 Mbytes for

frame buffering. This buffer can queue packets awaiting transmission

on congested networks.

• Aggregate bandwidth up to 8.8 Gbps for ECN320 and 10.8 GBPS for

ECN330.

• Packet capacity 8.9 Mpps (million packets per second)

• Filtering and forwarding at line speed

• Broadcast storm control - Broadcast suppression prevents broadcast

traffic from overwhelming the network. When enabled on a port, the

level of broadcast traffic passing through the port is restricted. If broad-

cast traffic rises above a predefined threshold, it will be throttled down

until the level falls back beneath the threshold.

• The ECN supports up to 4094/250 (ECN330/ECN320) tagged Service

VLANs (VLANs used for End-user traffic) based on the IEEE 802.1Q

standard. Service VLANs can be assigned using CLI and PEM. As-

signing a VLAN from the CLI configures the VLAN on all ports.

• Quality of Service (QoS) supports four levels of priority. The ECN priori-

tizes each packet based on the required level of service, using four pri-

ority queues with strict priority and using IEEE 802.1p and 802.1Q tags

to prioritize incoming traffic. These functions can be used to provide in-

dependent priorities for delay-sensitive data and best-effort data.

• Multicast Switching based on IGMP Snooping

• Link redundancy supported by utilizing Rapid Spanning Tree (RSTP).

• Link aggregation by utilizing LACP

ECN Functions, Features and HW

12 1553-CNH 160 0787 Uen PA2 2005-09-23

3.1.3 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 directly draw power

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 electrical 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 connec-

tions (for details see ECN330-switch User’s 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 res-

ervoir, should short voltage dropouts 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 auto-

matically, 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 cor-

rect speed will be sensed by the port, but the transmission mode will by de-

fault be half duplex. Each port also supports auto-negotiation of flow con-

trol, so the ECN can automatically prevent port buffers from becoming satu-

rated.

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 addi-

tion, the ECN can supply power to a device even if the port’s data connec-

tion has been 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

Page is loading ...

Ericsson ECN320, ECN330 User manual

Related papers

Other documents