1KHW002077 Abb Eter1 R2 Ug

ABB Power Systems
FOX515
ETER1 551
User Manual
User Manual
ETER1 551
Platform FOX515 Release R8
Copyright and confidentiality: Copyright in this document vests in ABB LTD. 

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine scannable form
is not permitted, either in whole or in part. The contents of the manual may not be disclosed
by the recipient to any third party, without the prior written agreement of ABB. 
An exception is the preparation of a backup copy of the software for your own use. For
devices with embedded software, the end-user license agreement on the enclosed CD
applies.
This document may not be used for any purposes except those specifically authorised by
contract or otherwise in writing by ABB.
Disclaimer: ABB has taken reasonable care in compiling this document, however ABB accepts no liability
whatsoever for any error or omission in the information contained herein and gives no other
warranty or undertaking as to its accuracy.
ABB can accept no responsibility for damages, resulting from the use of the network
components or the associated operating software. In addition, we refer to the conditions of
use specified in the license contract.
ABB reserves the right to amend this document at any time without prior notice.
Blank pages: Any blank page present is to accommodate double-sided printing.
Document No.: 1KHW002077




ABB Switzerland Ltd
Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © January 2011 by ABB Switzerland Ltd
CONTENTS
Contents
1 Preface 11
1.1 Precautions and safety 11
1.2 Associated FOX515/512 documents 12
1.3 About this document 13
1.4 Document history 13
1.5 Symbols and notations 13
2 Introduction 14
2.1 Definition of terms 14
2.2 Specification 14
2.2.1 Functions and features overview 14
2.2.2 Physical interfaces 15
2.2.3 Logical interface functions 16
2.2.4 Networking functions 16
2.2.5 Protection 19
2.2.6 Environment 19
2.3 Summary of standards 20
2.3.1 IEEE 20
2.3.2 IETF 20
2.3.3 ETSI 21
2.3.4 IEC 21
2.3.5 EN 21
2.4 Unit view 22
3 Architectural Description 24
3.1 ETER1 architectural block diagram 24
3.1.1 Network processor 24
3.1.2 Fast Ethernet PHYs 24
3.1.3 PBUS access 24
3.1.4 SDRAM 25
3.1.5 Power supply 25
4 Installation 26
4.1 Prerequisites 26
4.1.1 Installation precautions 26
4.1.2 UCST and control unit 26
4.1.3 Unit embedded software (ESW) 26
4.1.4 Ventilation 26
4.2 Slots for the ETER1 unit 27
4.3 Connections and Cables 27
4.3.1 Connectors and signals 27
4.3.2 Ethernet interface cables 29
4.4 Fixing the cables to the cable tray 29
ABB ETER1 551 3

CONTENTS
5 Functional Description 31
5.1 Overview 31
5.2 Ethernet LAN interfaces 31
5.3 TDM WAN interfaces (PBUS connections) 32
5.3.1 PBUS Cross Connections 32
5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s» 33
5.3.3 Protection for TDM WAN links 34
5.4 Bridging functions 34
5.4.1 VLAN MAC transparent bridging 34
5.4.2 IVL based MAC learning 36
5.4.3 RSTP 37
5.4.4 Multiple bridge instances 37
5.4.5 Star topology bridging 38
5.5 Routing functions 39
5.5.1 Static routing 40
5.5.1.1 Connecting an OSPF or a RIP network with ETER1 to other networks 40
5.5.2 OSPF routing 40
5.5.2.1 Static routes and OSPF routing 40
5.5.2.2 OSPF areas 41
5.5.2.3 OSPF neighbours 41
5.5.2.4 OSPF packet authentication 42
5.5.3 RIP routing 42
5.5.3.1 RIP version and authentication 42
5.5.3.2 The split horizon feature 42
5.5.4 Mutual redistribution of routing information 43
5.5.5 VRRP, the virtual router 44
5.5.5.1 Electing the master router 44
5.5.5.2 The virtual router’s MAC address 45
5.5.5.3 Master preemption and address owner 45
5.5.5.4 A common VRRP application with load sharing 45
5.6 Interface stacks 46
5.6.1 Generic stack model 46
5.6.2 MAC/PPP bridged encapsulation 47
5.6.3 MAC bridged encapsulation for DTM-M 47
5.6.4 PPP/HDLC encapsulation & framing 48
5.6.5 Hypothetical applications with bridging 48
5.6.6 Hypothetical applications with routing 51
5.7 Multilink PPP interface 53
5.7.1 Bandwidth considerations for multilink PPP bundles 53
5.7.2 Link quality considerations for multilink PPP bundles 53
5.7.3 Delay considerations for multilink PPP bundles 54
5.7.4 Joining and leaving of link members to and from a multilink PPP bundle 54
5.8 VLAN Interfaces 54
5.8.1 Selective routing per VLAN 55
5.8.2 Inter-VLAN routing 55
5.8.3 Connecting bridged and routed network segments 56
5.9 QoS 56
5.9.1 Frame classification and marking 56
5.9.2 Traffic queueing 57
5.9.3 Priority mapping with profiles 58
4 ETER1 551 ABB

CONTENTS
6 Commissioning 59
6.1 The managed objects tree 59
6.2 Commissioning steps 60
6.2.1 New units in the FOX subrack 60
6.2.2 Setting the configurable parameters 60
7 Operation and Maintenance 61

7.1 General operation recommendations 61
7.2 Status and maintenance 61
7.3 Performance monitoring 61
7.3.1 Setting the scope 63
7.3.2 Selecting the result type and format 63
7.3.3 Interpreting and saving the results 65
7.4 Failures, alarms and notifications 65
7.4.1 Front panel failure indications 65
7.4.2 Failure tables in UCST 66
7.5 Maintenance 66
7.5.1 Inventory data 66
7.5.2 Unit ESW download 66
7.5.3 Upgrades 67
8 UCST GUI Reference 68

8.1 Configuration 68
8.1.1 Board 68
8.1.1.1 Common settings 68
8.1.1.2 QoS 69
8.1.2 Interfaces 70
8.1.2.1 Ethernet phy 70
8.1.2.2 TDM interfaces 71
8.1.2.3 Multilink PPP 72
8.1.2.4 VLAN interfaces 73
8.1.3 Bridges 74
8.1.3.1 Bridges 74
8.1.3.2 Bridge-n IF 75
8.1.4 IPv4 routing 76
8.1.4.1 Interfaces 76
8.1.4.2 Router 80
8.2 Parameter browser 83
8.3 Status/Maintenance 84
8.3.1 Board 84
8.3.1.1 Maintenance 84
8.3.2 Interfaces 85
8.3.2.1 Ethernet Phy 85
8.3.2.2 TDM interface 86
8.3.2.3 Multilink PPP 86
8.3.3 Bridges 87
8.3.3.1 Bridges 87
ABB ETER1 551 5

CONTENTS
8.3.3.2 Bridge-n IF 88
8.3.4 IPv4 routing 89
8.3.4.1 Interfaces 89
8.3.4.2 Router 92
8.4 Alarms 98
8.4.1 General alarm configuration 98
8.4.2 Individual fault cause descriptions 99
8.5 Performance monitoring 100
8.5.1 Location selection tree 100
8.5.2 Counter selection 101
6 ETER1 551 ABB

FIGURES
Figures
Figure 1: Functional block diagram 14

Figure 2: ETER1 unit front view 22
Figure 3: ETER1 unit view 23
Figure 4: ETER1 architectural block diagram 24
Figure 5: ETER1 front view with RJ-45 pin assignment 28
Figure 6: Ethernet link LEDs on the ETER1 unit 28
Figure 7: Side view of the FOX515 cable tray and cable 30
Figure 8: The port based VLAN model (802.1Q, Annex D) 34
Figure 9: Possible inconsistencies in VLAN tagged bridged networks 36
Figure 10: Example bridged network with meshed topography 37
Figure 11: Active tree topology of the same network 37
Figure 12: Example application with multiple bridge instances 38
Figure 13: Example star bridging application 39
Figure 14: Interconnecting networks 40
Figure 15: Redistribution of static routes 41
Figure 16: Redistribution example 43
Figure 17: IP host connected to redundant gateway routers 44
Figure 18: IP host logically connected to a virtual router 44
Figure 19: VRRP application with load sharing 46
Figure 20: Generic stack model 47
Figure 21: Omitted encapsulation type 47
Figure 22: Connection of DTM-M to 3rd party Bridge/Switch 47
Figure 23: Stack details for ETER1 bridging applications 49
Figure 24: Stack details for ETER1 bridging applications (continued) 50
Figure 25: Stack details for ETER1 routing applications 51
Figure 26: Stack details for ETER1 routing applications (continued) 52
Figure 27: Block diagram and stacks for Multilink PPP 53
Figure 28: Connecting Ethernet LAN interfaces to the router 54
Figure 29: Connecting TDM WAN interfaces to the router 54
Figure 30: Selective VLAN routing 55
Figure 31: Inter-VLAN routing 55
Figure 32: The VLAN interface connects between bridging and routing 56
Figure 33: Frame handling for QoS in ETER1 57
Figure 34: Managed objects tree for ETER1 59
Figure 35: «Add Unit» menu 60
Figure 36: Location selection tree for PM 62
Figure 37: Fault indication LEDs on the ETER1 unit 66
ABB ETER1 551 7

FIGURES
8 ETER1 551 ABB

TA B L E S
Tables
Table 1: Electrical interfaces and circuit categories 12

Table 2: Document history 13
Table 3: Ethernet ports on the front panel 15
Table 4: PBUS ports (backplane) 15
Table 5: Parameters, user configurable per interface 16
Table 6: Parameters for virtual interfaces 16
Table 7: OSI layer 2 data forwarding (bridging) 16
Table 8: OSI layer 3 data forwarding (routing) 17
Table 9: OSPF 17
Table 10: RIP 18
Table 11: VRRP; two virtual routers, A and B 18
Table 12: QoS 18
Table 13: Protection 19
Table 14: Power consumption 19
Table 15: Mechanical parameters 19
Table 16: Reliability 19
Table 17: Ethernet media types 29
Table 18: Overview on cross connection modes 32
Table 19: Unit mode characteristics 33
Table 20: Overview on clocking and TDM modes 33
Table 21: Frame classification for QoS 56
Table 22: Default priority mapping for MAC frames 58
Table 23: Default priority mapping for IP packets 58
Table 24: Parameters for the «Common settings» menu 68
Table 25: Parameters for the «QoS» menu 69
Table 26: Parameters for the «Ethernet phy» menu 70
Table 27: Parameters for the «TDM Interfaces» menu 71
Table 28: Parameters for the «Multilink PPP» menu 72
Table 29: Parameters for the «VLAN Interfaces» menu 73
Table 30: Parameters for the «Bridges» menu 74
Table 31: Parameters for the «Bridge-n IF» menu 75
Table 32: Parameters for the «Addressing» menu 76
Table 33: Parameters for the «OSPF» menu 77
Table 34: Parameters for the «RIP» menu 78
Table 35: Parameters for the «VRRP» menu 79
Table 36: Parameters for the «Static Routes» menu 80
Table 37: Parameters for the «OSPF – Areas definition» menu 81
Table 38: Parameters for the «Redistribution» menu 82
Table 39: Parameters for the «Maintenance» menu 84
Table 40: The «Ethernet Phy» status menu 85
Table 41: The «TDM Interface» status menu 86
Table 42: The «Multilink PPP» status menu 86
Table 43: The «Bridges» status menu 87
Table 44: The «Bridge-n IF» status menu 88
ABB ETER1 551 9

TA B L E S
Table 45: Status menu for «General» 89

Table 46: Status menu for «OSPF» 90
Table 47: Status menu for «VRRP» 91
Table 48: Status menu for «Routing Table» 92
Table 49: Status menu for «ARP Table» 93
Table 50: Status menu for «OSPF – Area» 94
Table 51: Status menu for «OSPF – Link State Database» 94
Table 52: Status menu for «OSPF – External Link State Database» 95
Table 53: Status menu for «OSPF – Neighbours Table» 96
Table 54: Status menu for «RIP» 97
Table 55: Status menu for «Ping» 98
Table 56: Status menu for «Traceroute» 98
Table 57: Parameters for the «Alarms - Board» menu 99
Table 58: ETER1 fault causes 99
Table 59: PM counter selection 101
10 ETER1 551 ABB

PRECAUTIONS AND SAFETY
1 Preface
1.1 Precautions and safety

Before you handle any unit of the type ETER1 you must comply with the follow-
ing safety advices:
Please note the following safety precautions:
Hazardous voltages. Risk of electric shock!

Equipment might be connected to high voltages.
→ If a stationary battery is used as local power supply, the charging unit
must have a safety insulation acc. EN 60950-1.
→ If an AC/DC power supply is used instead of a stationary battery, this
must also provide a safety insulation acc. EN 60950-1.
→ Before manipulating anything at the device switch off the power supply.
Hazardous electric currents. Risk of flashover and electric shock!

When interrupting the power supply electric currents can cause a flashover and
an electric shock.
→ The positive (+) terminal of the local power supply must be connected to
earth. The negative (-) terminal of the local power supply must be pro-
tected with a fuse (slow blow). The applicable fuse current rating is speci-
fied in the installation user guide of the FOX515/512 subrack.
→ The subracks must be connected to the local power supply via a circuit
breaker.
Electrostatic discharges. Risk of equipment damage!

To protect your equipment you must discharge any static charge from your per-
son before touching the unit or any components!
→ Wear a grounded, anti-ESD wrist-band when working with the hardware.
Attention to temperature range!

Equipment has a high power dissipation. Insufficient ventilation causes hot
spots and overheating on the equipment. Overheating holds a high risk for dam-
age of the equipment.
→ A sufficient ventilation or cooling and ventilation must be provided by the
operator for the racks or subracks that guarantees for a maximum ambi-
ent temperature of 55° C.
ABB ETER1 551 11

ASSOCIATED FOX515/512 DOCUMENTS
1
Attention to proper earthing!

The subrack must be connected via the rack with the protective earth! The plus
(+) pole of the local power supply must be connected to earth. The minus (-)
pole of the local power supply must be protected with a fuse slow blow). The
subracks may only be connected to a switchable power voltage.
Attention to access control!

Unrestricted access to equipment premises hold a risk of damaged equipment
and disrupted services.
→ The subrack should only be installed in locations with restricted access.
Table 1: Electrical interfaces and circuit categories

Interface Circuit category according Max. rating
to EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC <2A
ITU-T G.703 electrical interfaces SELV <3.3 Vpeak < 10 mA
Electrical Ethernet SELV <3V < 10 mA
10/100Base-TX

For generic information on precautions and safety refer to Precautions and
Safety User Guide.
1.2 Associated FOX515/512 documents

1KHW002000 Precautions and safety User Guide
1KHW002070 FOX UCST Release Note R8C
1KHW002006 FOX System Specification User Guide
1KHW002001 FOX TDM System and Cross Connections User Guide
1KHW002013 COBUX 212, 213 & COBUV 217, 218

COBUX 219, 223 & COBUV 220, 224 
User Guide
1KHW002003 FOX515 Installation Guide
1KHW002059 FOX User Guide
1KHW002004 FOX512 Installation Guide
1KHW002060 UCST/System Operation Basics User Guide
1KHW002007 FOX Network functions User Guide
1KHW002074 FOX515 Open source software declaration
12 ETER1 551 ABB

ABOUT THIS DOCUMENT
1.3 About this document

User Manuals for FOX515/512 units are usually divided into two parts: a Tech-
nical Description and a User Guide.
This FOX515/512 User Guide covers the aspects of the installation, commis-
sioning and operation of the ETER1 unit. It also handles the functional aspects
and technical specification of the unit.
1.4 Document history
Table 2: Document history

ABB Document number Date FOX515/512 Changes since previous version
Release
1KHW002068 09-06-2010 R8C SP1 Documentation corresponding to ESW r1a
1KHW002077 16-02-2011 R8C SP3 Transferred to FM and updated to ESW r2a
1.5 Symbols and notations

This User Guide uses the following symbols:
Please note:
Shows a significant information.
Indicates a possibly hazardous context. The possible hazard is indi-

cated with a symbol and a description.
A further description is added to describe the details of the hazard.
→ Possible actions are given as in this paragraph.
ABB ETER1 551 13

DEFINITION OF TERMS
2
2 Introduction
2.1 Definition of terms

In this document, generic names are used to name functional units:
• ETER1 to name ETER1 551
(initially released with the UCST R8C SP03)
• FOX is used to name the
− FOX515 and the
− FOX512
In this document, the terms “bridging” and “switching” are used as synonyms
and the terms “bridge” and “switch” are used as synonyms accordingly.
2.2 Specification
2.2.1 Functions and features overview
The ETER1 is a versatile networking unit with the main purpose of connecting
Ethernet LANs over TDM links. Therefore the ETER1 supports a variety of pow-
erful functions and features.
router
PBUS (backplane ):
Front ports :
virtual
interfaces
up to 64 P0nc/P12x
4 Ethernet LAN
TDM WAN interfaces,
interfaces
with a total bandwidth
10/100Base-T
of 16 x 2 Mbit/s
bridge
Figure 1: Functional block diagram
• Functions of the Ethernet LAN interfaces

− All four Ethernet interfaces are located on the front panel
− 10/100Base-TX
− Bridge port type (access/trunk) user configurable
• Functions of the TDM WAN interfaces
− Up to 64 PBUS individual interfaces
− Total bandwidth 8x2Mbit/s or 16x2Mbit/s depending on unit mode
− PPP/HDLC user configurable
− Multilink PPP
− Bridge port type (access/trunk) user configurable
14 ETER1 551 ABB

SPECIFICATION
• Functions of the virtual interface

− Selective routing per VLAN
− Inter-VLAN routing
− Connection between bridged and routed network segments
• Functions of the bridge
− Transparent MAC bridging
− VLAN aware MAC bridging
− RSTP (STP)
− Multiple bridge instances
• Functions of the IP router
− Static routing
− OSPF routing
− RIP routing
− VRRP, the virtual router protocol
• QoS functions
− 4 TX queues per interface
− Strict priority scheduling
2.2.2 Physical interfaces

Table 3: Ethernet ports on the front panel
Function Description/Range Standard ESW release
Not configurable parameters
Number of ports 4 IEEE 802.3-2005 R1
Location of ports front panel
Connector type RJ-45
Impedance 100 ± 15 Ohms for the fre-
quency band from 1 to 100 MHz
Auto negotiation fully supported
User configurable parameters
Administrative state enable/disable IEEE 802.3-2005 R1
Speed 10/100 Mbit/s
Port mode half-duplex
full-duplex
Ingress rate limiter enabled/disabled R2
comitted information rate
comitted burst size
Table 4: PBUS ports (backplane)

Maximal number of PBUS ports 64 R1
PBUS port types P0nc (Terminated mode) G.704
P12x (Transparent mode)
P12 (Clock Master)
Port speed in P0nc mode 64 kbit/s (n=1) … 2048
kbit/s (n=32)
ABB ETER1 551 15

SPECIFICATION
2
Table 4: PBUS ports (backplane) (continued)

Total available bandwidth on the PBUS 8 x 2Mbit/s = 16’384 kbit/s
16 x 2Mbit/s = 32’768 kbit/s
2.2.3 Logical interface functions

Table 5: Parameters, user configurable per interface
Supported layer 2 protocols for TDM interfaces PPP RFC 1661 R1
Multilink PPP RFC 1990
MAC/PPP RFC 1638
MAC/HDLC encapsulation
IP/PPP RFC 1332 R2
Supported IP addressing modes for TDM interfaces numbered R2
numbered with peer
Interface assignment, i.e. appropriate interface net- router R2
working function bridge-1 ... bridge-8 R1
Table 6: Parameters for virtual interfaces

Interface selection Ethernet interfaces (not R2
assigned to a bridge
instance)
bridge instances 1 ... 8
VLAN ID for frame filtering 1 ... 4094
Administrative state disabled/enabled
2.2.4 Networking functions

Table 7: OSI layer 2 data forwarding (bridging)
Data forwarding technology network processor R1
MAC transparent bridging IEEE 802.1D
VLAN MAC transparent bridging IEEE 802.1Q-2003
Frame classifying for VLAN association port- and tag based IEEE 802.1Q-2003
RSTP not VLAN sensitive IEEE 802.1w-2001
RSTP parameters, user configurable per bridge instance
Bridge priority 0 … 61’440 in 16 steps IEEE 802.1w-2001 R1
Hello interval 1 … 10 seconds
Forwarding delay 4 … 30 seconds
Maximum age 6 … 40 seconds
Path cost version 802.1D-1998
802.1t-2001
RSTP parameters, user configurable per interface
16 ETER1 551 ABB

SPECIFICATION
Table 7: OSI layer 2 data forwarding (bridging) (continued)

RSTP enable/disable IEEE 802.1w-2001 R1
Path cost computation automatic/manual
Manual path cost 1 … 200’000’000
Please note:
UCST might limit the ranges of «Hello interval», «Forwarding delay» and «Maxi-
mum age» in order to maintain recommended relationships.
Table 8: OSI layer 3 data forwarding (routing)

Static routing up to 128 static routes R2
OSPF dynamic routing RFC 2328
RIPv2 dynamic routing RFC 2453
VRRP support of two virtual RFC 3768
routers
Dedicated loopback interface
Table 9: OSPF
User configurable parameters per AS, area or address range
OSPF Areas up to 8 areas RFC 2328 R2
Area link state mode normal
stub
NSSA
Area address ranges up to 16 address ranges
per OSPF area
Area address range advertise mode advertise address range
hide address range
User configurable parameters per interface
IP address RFC 2328 R2
Addressing mode numbered
numbered peer
OSPF state enabled/disabled
OSPF mode active
passive
OSPF area backbone (default) RFC 2328 R2
area-2 ... area-8
Interface metric automatic metric
manual metric 1 ... 65535
Router priority (selection of designated router) 0 ... 255
Advanced options
ABB ETER1 551 17

SPECIFICATION
2
Table 9: OSPF (continued)

Hello interval 1 ... 65535 s RFC 2328 R2
Dead interval 0 ... 3600 s
Transmit delay 0 ... 3600 s
Retransmit delay 0 ... 3600 s
Table 10: RIP

RIP state enabled/disabled RFC 2453 R2
RIP mode active
passive
Authentication / Version None / RIPv1
None / RIPv2
None / RIPv1 & v2
Simple / RIPv2
MD5 / RIPv2
Table 11: VRRP; two virtual routers, A and B

Virtual router state enable/disable RFC 3768 R2
Virtual router ID 1 ...255
Virtual router priority 0 ... 255
Virtual router IP address
Virtual router advertise interval 1 ... 255 s
Virtual router preemption state enable/disable
Table 12: QoS

Profile for QoS mapping Generic profiles for R1
equipment with 4 TX
queues
802.1p priority <--> TX queue – mapping priority 0...7 / queue 1...4 IEEE 802.1p
DSCP <--> TX queue – mapping DSCP 0...63 / queue 1...4 RFC 2474 R2
18 ETER1 551 ABB

SPECIFICATION
2.2.5 Protection
Table 13: Protection
Equipment protection not supported
Traffic protection on Ethernet ports supported with RSTP R1
(STP)
Traffic protection on PBUS ports
1+1 SNC/I protection supported for P0nc signals
and P12x signals
1+1 Trail (Path) protection supported for P0nc signals
2.2.6 Environment
Table 14: Power consumption
Power supply range VBAT -39.5 VDC … -72 VDC
Current consumption (typical, with maximum traffic +5 VCC (power rail on
load backplane) = 0 mA
-5 VCC (power rail on
backplane 0 mA
-48 VBAT (direct from bat-
tery) 200 mA
Typical total power requirements from battery with VBAT = -48 V (nominal
voltage) and 80% of power
unit efficiency:
10 W
Table 15: Mechanical parameters

Construction practice 19 inch
Unit height (1 HU = 44.45 mm) 6 HU
Unit width (1 TE = 5.08 mm) 4 TE (1 slot)
PCB size 233 mm x 220 mm
Unit weight 440 g
Table 16: Reliability

Calculated MTTF for all categories of failures (MIL-HDBK-217F)
MTTF @ 35°C ambient temperature 88 year
ABB ETER1 551 19

SUMMARY OF STANDARDS
2
2.3 Summary of standards

2.3.1 IEEE
• IEEE 802.3-2005
CSMA/CD access method and physical specifications
• IEEE 802.1D-2004
Media Access Control Bridges
• IEEE 802.1Q-2003
Virtual Bridged Local Area Networks
• IEEE 802.1w-2001
Media Access Control Bridges Amendment 2: Rapid Reconfiguration
2.3.2 IETF
• RFC 792
ICMP
• RFC 826
ARP
• RFC 1332
IPCP
• RFC 1493
MIB for bridges
• RFC 2328
OSPFv2
• RFC 1661
The Point-to-Point Protocol
• RFC 1662
PPP in HDLC-like framing
• RFC 1724
RIPv2 MIB
• RFC 1850
OSPFv2 MIB
• RFC 1990
The PPP Multilink Protocol
• RFC 2082
RIPv2 MD5 Authentication
• RFC 2453
RIPv2
• RFC 2674
MIB for Bridges, VLAN Extensions
• RFC 2787
MIB for VRRP
• RFC 3518
PPP Bridging Control Protocol (BCP)
• RFC 3768
VRRP
20 ETER1 551 ABB

SUMMARY OF STANDARDS
2.3.3 ETSI
• ES 201468 V1.1.1
Additional EMC Requirements for Telecommunication Equipment for
enhanced availability of service in specific applications
2.3.4 IEC
• IEC EN60950-1
Information Technology Equipment – Safety – Part 1: General Requirements
• ISO/IEC 3309:1191 (E)
Information Technology – Telecommunications and information exchange
between systems – High-level data link control (HDLC) procedures – Frame
structure
2.3.5 EN
• EN 300386 V1.3.1
Telecommunication Network Equipment: EMC Requirements (2001-9)
• EN 55022:1998 + A1
Radiated Emission Class B: Conducted Emission on DC Port Class A
• EN 300 132-2 (2003/01)
Power supply interface at the input to telecommunications equipment; Part 2:
Operated by direct current (dc)
ABB ETER1 551 21

UNIT VIEW
2
2.4 Unit view

Fixing screw
ETER1 R1A Pull-out handle with sticker

ROFBU 367 610/1
Unit LED
Traffic LED
Ethernet 10/100BASE-T port 4
S/N 491xxxxxxx
Pull-out handle with sticker
Fixing screw
Figure 2: ETER1 unit front view
22 ETER1 551 ABB

UNIT VIEW
Figure 3: ETER1 unit view
ABB ETER1 551 23

ETER1 ARCHITECTURAL BLOCK DIAGRAM
3
3 Architectural Description
3.1 ETER1 architectural block diagram
serial
4x Fast
Ethernet
ETER1 8 x 2/4Mbit/s
8/16 x
2Mbit/s
Fast
Ethernet PBUS
PHYs PBUS
access
Network
processor
primary
SD power
RAM Power input
supply
Figure 4: ETER1 architectural block diagram
3.1.1 Network processor

The network processor is the heart of the unit. It provides packet forwarding and
also handles control protocols and management functions.
3.1.2 Fast Ethernet PHYs

The physical Ethernet driver chips are responsible for implementing the CSMA/
CD protocol according to the IEEE 802.3 standard.
3.1.3 PBUS access

The PBUS access block interfaces with the network processor via 8 unit internal
serial links. Doubling the line speed for these links from the usual 2 Mbit/s to
4 Mbit/s enables a maximal PBUS bandwidth of 16 x 2Mbit/s.
On the PBUS side the PBUS access driver behaves slightly different according
to the selected unit mode:
• In unit mode «8 x 2Mbit/s» the ETER1 behaviour follows the standard FOX
PBUS specification. It allows for P0nc connections (n = 1 … 32) and P12x
(transparent) connections.
• In unit mode «16 x 2Mbit/s» the ETER1 deserves great care for the NEs
clock synchronisation.
For details see paragraph 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x
2Mbit/s» (on page 33). The supported connection types are P0nc (n = 2, 4, 6
… 32) and P12 (Clock master).
24 ETER1 551 ABB

ETER1 ARCHITECTURAL BLOCK DIAGRAM
3.1.4 SDRAM
The fast volatile memory serves for the network processor’s own use and holds
all the data queues and various tables.
3.1.5 Power supply

Unlike most FOX boards, the ETER1 unit draws its power from the un-stabilised
primary power. The power supply provides the classic +5V and several lower
voltages according to the boards need.
All secondary voltages are ramped up and down in a controlled way.
ABB ETER1 551 25

PREREQUISITES
4
4 Installation
4.1 Prerequisites
4.1.1 Installation precautions
Electrostatic discharges. Risk of equipment damage!

Keep the ETER1 unit in the ESD protection bag while the unit is not installed in
the subrack. Before taking the unit out of its ESD protection bag, make sure that
you have not accumulated electro-static charges.
4.1.2 UCST and control unit

The operation of the ETER1 551 unit in the FOX requires:
• UCST R8C SP3 or a more recent version.
The ETER1 unit operates with one of the following or more recent COBU<X>
versions:
• COBUX 212, 213, 219 or 223, ESW R5H.
• COBUV 217, 218, 220 or 224, ESW R5H.
For details of the control units refer to "1KHW002013 COBUX 212, 213 &
COBUV 217, 218 COBUX 219, 223 & COBUV 220, 224 User Guide".
For detailed information on the requirements for hardware and software please
refer to "1KHW002070 FOX UCST Release Note R8C".
Please note:
Make sure the COBU<X> is equipped with a 16 MB flash prior to installing an
ETER1 unit, because the ETER1 ESW file is very large (over 7MB).
4.1.3 Unit embedded software (ESW)

The ETER1 unit runs on dedicated ESW. This ESW is labelled
ETER1_R<X>.<Y><zz>, e.g. ETER1_R2.A32.
For the ESW revision prerequisites please refer to "1KHW002070 FOX UCST
Release Note R8C".
The software included in this product contains copyrighted software that is
licensed under the GPL.
For further information and GPL license conditions please refer to
"1KHW002074 FOX515 Open source software declaration".
4.1.4 Ventilation
Operating the ETER1 requires active ventilation of the FOX subrack.
If the FOX subrack is not installed in a rack or cabinet with active ventilation of
the subracks, you must install:
• FOX515 with the FANU5 unit.
• FOX512 with the FANU2 unit.
26 ETER1 551 ABB

SLOTS FOR THE ETER1 UNIT
4.2 Slots for the ETER1 unit

The ETER1 unit uses one slot in the FOX subrack. The used slot must provide
PBUS access, i.e.
• Slots 1 – 10
• Slots 12 – 20
4.3 Connections and Cables

4.3.1 Connectors and signals
The ETER1 has four Ethernet interfaces on the unit front, numbered from bot-
tom up with C1.1 to C4.1
The Ethernet interfaces are equipped with RJ-45 connectors. The interface lay-
out is per default according to the switch layout, but implements automatic
crossover functionality (MDI/MDI-X).
The pin and port assignment of the four front panel connectors is shown in the
figure below.
ABB ETER1 551 27

CONNECTIONS AND CABLES
4
ETER1 R1A
ROFBU 367 610/1
pin 1
C4.1
pin 8
C3.1
Pin MDI MDI-X
1 Tx+ Rx+
2 Tx- Rx-
3 Rx+ Tx+
C2.1
4
5
6 Rx- Tx-
7
C1.1 8
S/N 491xxxxxxx
Figure 5: ETER1 front view with RJ-45 pin assignment
Each Ethernet interface provides two LEDs indicating the link state and the link
activity:
Activity
Link state
Figure 6: Ethernet link LEDs on the ETER1 unit
The activity LED has the following states:

• Yellow blinking: Traffic activity
28 ETER1 551 ABB

FIXING THE CABLES TO THE CABLE TRAY
• Dark: No traffic
The link state LED has the following states:
• Green: 10/100 Mbit/s link up
• Dark: Link down
4.3.2 Ethernet interface cables

1:1 connection and crossover connection cables are available for the Ethernet
interfaces. The cable type can be chosen according to the available cables
since the Ethernet ports on ETER1 implement automatic crossover functionality.
According to the Ethernet link speed, the following cable categories have to be
used:
Table 17: Ethernet media types

IEEE Standard Distance Media Type
10BASE-T 100 m Category 3 SF-UTP or better
100BASE-TX 100 m Category 5 SF-UTP or better
Please note:
The above cables can be ordered directly from ABB
4.4 Fixing the cables to the cable tray

The optical or electrical cables must be attached to the cable tray of the
FOX515 or the corresponding device of the FOX512.
The open cable shields (electrical cables only) must be in contact with the
FOX515/512 grounding bar and should be fixed to the cable tray or the corre-
sponding device of the FOX512.
The figure below shows the cable/cable tray assembly of the FOX515. For addi-
tional information refer to "1KHW002003 FOX515 Installation Guide".
With the FOX512 the cable tray functionality is implemented differently and
depends on the type of installation (rack-, wall-mounted).
For more information on fixing the cables with the FOX512 refer to
"1KHW002004 FOX512 Installation Guide".
ABB ETER1 551 29

FIXING THE CABLES TO THE CABLE TRAY
4
C4.1
C3.1
C2.1
C1.1
C5.1 - C8.1
120 mm
<x> mm
Figure 7: Side view of the FOX515 cable tray and cable
The open cable length <x> between the cable fixing point on the cable tray and
the connector depends on the connected interface.
Please note:
The cable route on the cable tray should follow approximately the projection of
the unit slot on the cable tray.
30 ETER1 551 ABB

OVERVIEW
5 Functional Description
5.1 Overview
From the interface point of view the ETER1 is designed to interconnect Ethernet
LANs via TDM links. The two supported interface types on the physical layer
are:
• "Ethernet LAN interfaces" according to IEEE 802.3 2008;
• "TDM WAN interfaces (PBUS connections)" according to ITUT G.703 and
ITUT G.704.
The main networking functions of the ETER1 is bridging and routing. In addition
there are a variety of sub-functions and ad-on functions for both bridging and
routing.
• "Bridging functions" (OSI layer 2 forwarding)
− "VLAN MAC transparent bridging" according to IEEE 802.1Q-2003
− "IVL based MAC learning"
− "RSTP"
− "Multiple bridge instances"
− Optional "Star topology bridging"
• "Routing functions" (OSI layer 3 forwarding)
− "Static routing"
− "OSPF routing"
− "RIP routing"
− "VRRP, the virtual router"
The "Interface stacks" describe the connection between physical interfaces and
the networking functions, i.e. the interaction between OSI layers 1, 2 and 3.
A special TDM interface type, the "Multilink PPP interface" is supported in order
to enable appropriate bandwidth for LAN–LAN interconnections over WAN links.
The "VLAN Interfaces" is a versatile intermediate function between bridging
and routing.
In the final paragraph "QoS" the focus is on congestion problems typically
occurring when packets must be forwarded from a fast input interface to a far
slower output interface, e.g. from a 100BaseT Ethernet input to a 2 Mbit/s out-
put.
5.2 Ethernet LAN interfaces

ETER1 provides four 10/100BaseT Ethernet interfaces according to the IEEE
802.3 standard.
The Ethernet interfaces are located on the front panel and are user configurable
in respect of:
• Administrative state ON/OFF
• LAN mode selection
− Auto negotiation
ABB ETER1 551 31

T D M WA N I N T E R F A C E S ( P B U S C O N N E C T I O N S )
5
− 100Mbit/s full duplex

− 100Mbit/s half duplex
− 10Mbit/s full duplex
− 10Mbit/s half duplex
• Ingress rate limiter
Range 64 kb/s ... 100 Mb/s
The physical Ethernet driver chips provide automatic RX/TX lines cross over
independently of the LAN mode selection; therefore the Ethernet cabling may
use straight or crossed cabling without restriction.
5.3 TDM WAN interfaces (PBUS connections)

The PBUS is a FOX bus structure for traffic signals of various formats with and
without CAS. The PBUS provides a non-blocking cross connect with the equiva-
lent capacity of 128 x 2 Mbit/s for traffic signals with and without CAS. For the
main characteristics of the PBUS, refer to "1KHW002001 FOX TDM System
and Cross Connections User Guide", paragraph "Bus architectures and imple-
mentations".
ETER1 supports the following PBUS formats:
• P0nc (with and without CAS)
• P12 (transparent)
• P12 (clock master)
ETER1 uses the CAS bits for the 1+1 Trail (Path) protection function.
5.3.1 PBUS Cross Connections

UCST is designed to accept valid PBUS Cross Connections only, but for
ETER1 certain otherwise allowed P12 mode combinations should be avoided.
Do not use any other combinations for P12 mode than those in the table below:
Table 18: Overview on cross connection modes

ETER1 TDM transport unit Remarks
P12 mode CAS P12 mode CAS
Terminated Can be used for the 1+1 path Terminated Must be activated, if If 1+1 path protection is used,
protection function if the peer activated on the make sure the complete link from
unit also supports CAS ETER1 unit end to end is providing CAS
Transparent n.a. Transparent n.a. In unit mode «8x2Mbit/s»
Clock Master n.a. Clock Master n.a. In unit mode «16x2Mbit/s»
For more detailed explanations on Cross Connections please refer to

"1KHW002001 FOX TDM System and Cross Connections User Guide".
32 ETER1 551 ABB

T D M WA N I N T E R F A C E S ( P B U S C O N N E C T I O N S )
5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s»

Table 19: Unit mode characteristics
8 x 2Mbit/s 16 x 2Mbit/s
The unit mode 8 x 2Mbit/s is the default mode with a total The unit mode 16 x 2Mbit/s is the high speed option with the
bandwidth of 16 Mbit/s towards the TDM interfaces total bandwidth towards the TDM interfaces doubled to 32
(PBUS). Available TDM modes are P0nc and P12 (trans- Mbit/s. Available TDM modes are P0nc and P12 (clock mas-
parent). ter).
The granularity for bandwidth selection on a P0nc channel The granularity for bandwidth selection on a P0nc channel (n
(n times 64 kbit/s) is based on one 64 kbit/s time slot, i.e. times 64 kbit/s) is based on two 64 kbit/s time slots, i.e. only
any number of timeslots from n = 1 … 32 may be selected. even numbers of timeslots from n = 2 … 32 may be selected.
Table 20: Overview on clocking and TDM modes

TDM mode Framing Available Usable by Clocking Impact in case of unsynchro-
in unit the FOX as nised Rx/Tx state
mode clock source
P0nc framed 8x2Mbit/s yes The framed G.704 data stream is Possible clock differences are
(n= 1…32) and terminated by the FOX frame- handled by the G.704 process
16x2Mbit/s work with the local FOX clock. and lead to occasional data loss.
P12 unframed 8x2Mbit/s no The FOX framework passes the Clock recovering from received
(transparent) data stream (including its original data streams prevents data loss.
clock) transparently to the TDM
input of the ETER1 unit. The
ETER1 unit extracts the Rx clock
from the Rx data stream.
P12 unframed 16x2Mbit/s no The ETER1 unit uses the FOX Possible clock differences are
(clock mas- system clock for Rx data handled by the FOX framework
ter) streams. and lead to occasional data loss.
Risk of operating trouble!

Take great care on timing source configuration in FOX networks. Unsynchro-
nised Rx/Tx states should be restricted to transient states during switchover of
clock feeding connections.
Prefer the TDM mode P0nc against P12 (clock master) as the framed data
stream can be used to synchronising the TDM network.
For details on Cross Connection, refer to paragraph 5.3.1 PBUS Cross Con-
nections (on page 32).
For details on timing source configuration, refer to "1KHW002001 FOX TDM
System and Cross Connections User Guide".
Please note:
Changing the unit mode may cause a restart of the unit and includes the risk of
inconsistent configurations. ABB therefore recommends deleting an existing unit
whenever the unit mode should be changed.
ABB ETER1 551 33

BRIDGING FUNCTIONS
5
5.3.3 Protection for TDM WAN links

The FOX platform provides both 1+1 SNC/I for P0nc/P12x signals and 1+1 path
protection for P0nc signals with CAS.
In order to configure a protected TDM link for ETER1 the «Protected» option
must be activated, when establishing the cross connection between ETER1 and
the TDM transport unit:
If using the 1+1 path protection for P0nc signals with CAS make sure, the whole
link from end to end is configured for CAS transport and the peer unit is sup-
porting CAS. If a persistent CAS support is not ensured for the full path, CAS
must be disabled on both ends.
For 1+1 path protection between ETER1 and DATAx enable CAS on both units
and select «Supervised» or «1+1 Revertive» as transport mode on the DATAx,
provided CAS is supported for the full path.
For detailed description of signal protection please refer to "1KHW002007 FOX
Network functions User Guide".
5.4 Bridging functions

5.4.1 VLAN MAC transparent bridging
ETER1 is a VLAN aware MAC bridge according to IEEE 802.1Q-2003.
ETER1 uses the port and tag based VLAN concept in order to assign a VID to
received frames.
VLAN A VLAN A
ETER1
Access port Access port
VLAN aware Trunk link VLAN aware
bridge Trunk port Trunk port bridge
Access port Access port
VLAN B VLAN B
Figure 8: The port based VLAN model (802.1Q, Annex D)
34 ETER1 551 ABB

BRIDGING FUNCTIONS
Below a list of rules for the VLAN MAC transparent bridge with port based
VLAN concept as implemented in ETER1:
• General rules
− All received frames have assigned a VLAN membership (after ingress
processing).
− The VLAN membership and the egress port type decide to which ports a
frame may be forwarded to:
a) Forwarding to access ports: only frames with VID = port-VID
b) Forwarding to trunk ports: no limitation
− VLAN aware bridges can receive but not send priority tagged frames –
therefore they send either tagged or untagged frames.
− The port type (access/trunk/trunk with native VLAN) decides, whether a
transmitted frame needs a tag or not (Exception: BPDUs are always
untagged).
• Access port
− The port is a member of exactly one VLAN.
− Received untagged and priority tagged frames are assigned the VLAN
membership as defined by the port’s VLAN id configuration.
− Received VLAN tagged frames are not accepted, even if the VID is the
same as assigned to the corresponding access port.
− TX frames are all sent untagged.
• Trunk port
− The port is a member of every VLAN with VID = 1 … 4094, thus received
VLAN tagged frames with VID = 1 … 4094 are accepted.
− Received untagged and priority tagged frames are discarded.
− TX frames are all sent VLAN tagged.
• Trunk port with native VLAN (hybrid port)
− The port is a member of every VLAN with VID = 1 … 4094, thus received
VLAN tagged frames with VID = 1 … 4094 are accepted.
− Received untagged and priority tagged frames are assigned the VLAN
membership as defined by the port’s VLAN id configuration.
− TX frames are all sent VLAN tagged, except the frames with
VID = port-VID are sent untagged.
Please note:
The VLAN port type (access or trunk) is not dedicated to a physical port type
(Ethernet or TDM) i.e. the VLAN port type is user configurable without restric-
tion.
Take care to avoid inconsistent networks, see figures below.
Consistency problem 1: A link between two VLAN segments must be of the same type on both ends.
Conflicting configuration Correct configurations
trunk trunk
VLAN A VLAN B VLAN A VLAN B
access trunk
access
VLAN A VLAN B
access
ABB ETER1 551 35

BRIDGING FUNCTIONS
5
Consistency problem 2: Redundant links between two VLAN segments must be of the same link type.
Otherwise the network behaviour will change depending on the active link
topography.

trunk link trunk link
VLAN A VLAN B VLAN A VLAN B
access link trunk link
A) the forwarding link is an access link

access link
discarding
trunk link
VLAN A VLAN B
access link
VLAN A VLAN B
access link
forwarding
B) the forwarding link is a trunk link

forwarding
trunk link
VLAN A VLAN B
access link
discarding
Consistency problem 3: Several links from an untagged LAN segment must all use the same VID.
Otherwise connectivity in the network will change depending on the active
link topography.
access port with access port with
VLAN ID = 105 VLAN ID = 105
untagged VLAN tagged untagged VLAN tagged
access port with access port with

VLAN ID = 110 VLAN ID = 105
access port with

A) access port with VLAN ID 105 is forwarded VLAN ID = 110
VLAN ID = 105
forwarding
untagged VLAN tagged
discarding
VLAN ID = 110 access port with
VLAN ID = 110
B) access port with VLAN ID 110 is forwarded

VLAN ID = 105
discarding
forwarding
VLAN ID = 110
Figure 9: Possible inconsistencies in VLAN tagged bridged networks
5.4.2 IVL based MAC learning

The VLAN standard IEEE 802.1Q-2003 mentions two methods for MAC learn-
ing and implementation rules:
• Shared VLAN Learning (SVL); the VLAN aware bridge stores the learned
MAC addresses in a common forwarding database for all VLANs.
• Independent VLAN Learning (IVL); the VLAN aware bridge stores the
learned MAC addresses in a separate forwarding database for each VLAN.
• A VLAN aware bridge may implement either SVL only or IVL only or it may
implement both SVL and IVL.
ETER1 implements the IVL approach with tables supporting 8192 learned MAC
addresses per bridge instance.
36 ETER1 551 ABB

BRIDGING FUNCTIONS
5.4.3 RSTP
ETER1 supports the Rapid Spanning Tree Protocol (RSTP) according to IEEE
802.1w.
A spanning tree mechanism is essential in any bridged network with one or sev-
eral physical loops. Without breaking up the loops, broadcast frames would cir-
culate indefinitely, multiplying themselves and thus jam the network for any uni-
cast user traffic.
Bridge A
Bridge B Bridge C
Figure 10: Example bridged network with meshed topography
Root
Forwarding
Bridge A
Forwarding Forwarding
Forwarding
Discarding
Forwarding
Bridge B Bridge C
Forwarding Discarding
Figure 11: Active tree topology of the same network
To prevent loops some bridges place ports in a discarding state and ports that
are participating in the active topology are in the forwarding state.
The RSTP standard requests backward compatibility to older versions of span-
ning trees such as STP according to 802.1D as implemented on the LAWA4/
LEMU6 units. Designing networks with mixed spanning tree versions should be
avoided whenever possible, because the rapid conversion is then lost. ETER1
provides valuable information for maintaining and debugging bridged networks
in the status menus. For details see paragraph 8.3.3 Bridges (on page 87).
5.4.4 Multiple bridge instances

ETER1 supports up to 8 logically independent bridge instances. Multiple bridge
instances provide a simple way for network operators to isolate packet services
over TDM PDH/SDH back haul networks. The multiple bridge instances method
is thus a valid alternative for all cases where VLAN bridging is not available e.g.
in conjunction with older LAWA4/LEMU6 networks.
Nevertheless each bridge instance provides the full ETER1 function set for
bridging without restrictions.
Please note:
Traffic isolation between two bridge instances on the same ETER1 unit is the
same as between two bridges on separate hardware.
ABB ETER1 551 37

BRIDGING FUNCTIONS
5
LAWA4
ETER 1
PDH/SDH
network ETER 1
Third party
bridge
ETER1
Bridge A Bridge B Bridge C Bridge D
Figure 12: Example application with multiple bridge instances
Please note:
BPDUs (the bridge control information for RSTP/STP) are always transmitted
without a VLAN tag, i.e. the active tree topology is calculated without considera-
tion of VLAN borders. Only by using independent bridge instances it is possible
to build multiple independent spanning trees with the ETER1 unit.
5.4.5 Star topology bridging

The star topology bridging feature supported by the ETER1 unit can be used
together with VLAN bridging and works as an additional forwarding restriction
within a VLAN context.
A star topology bridged network (like a tree) consists of a central location (the
root) and peripheral devices (the leaves). All leaves are allowed to communi-
cate with the root, but any traffic between the leaves is inhibited. If VLANS are
used, the whole tree must reside in the same VLAN.
Star topology bridging is compatible with the FOX units LAWA4/LEMU6 and
with the “Rooted Multipoint EVC type” as described in MEF 10.1.
Star topology bridging distinguishes between “public” and “protected” bridge
interfaces and handles frame forwarding according to the following rules:
• Frames received on a public interface are forwarded to all interfaces.
• Frames received on a protected interface are forwarded to public interfaces
only.
• Frame filtering upon the learned MAC address tables is applied in addition to
the star topology bridging.
For the configuration of star topology networks the following rules must be
observed:
• Interfaces towards the tree root are of type «Public».
• Interfaces towards the tree leaves are of type «Protected».
• At least one public interface must be defined on each bridge.
• Star cascades are possible, i.e. the function is recursive.
• RSTP may be activated in order to duplicate uplinks towards the root or to
form a meshed network for the root connection.
• If a bridge in the tree does not support the star topology bridging feature,
then all of its interfaces are of type «Public».
38 ETER1 551 ABB

ROUTING FUNCTIONS
ETER1
Ethernet uplink LAWA4

ROOT with RSTP
ETER1 LAWA4
LAWA4
LAWA4
PDH/SDH
network
ETER1
PDH/SDH
network
DATAx
DATAx
ETER1
DTM-M
STICx
STICx DTM-M
Public bridge interface

Protected bridge interface
Figure 13: Example star bridging application
The ETER1 star bridging function is a purely local bridge function. It is compati-
ble with other bridge/switch equipment (LAWA4, third party) as long each bridge
with more than two protected interfaces follows the same forwarding rules as
defined above.
RSTP/STP does not interfere with the star bridging function, but must be con-
strained to public interfaces only.
5.5 Routing functions

This user guide is not a routing tutorial. The following routing basics and defini-
tions in this paragraph should help understanding how some important expres-
sions are used in this document.
A Router
• works on OSI layer 3 (network layer);
• is sometimes called a layer 3 switch;
• performs the routing function, i.e. connects IP subnets with different network
addresses;
• acts in two planes:
− in the control plane, the forwarding information is collected, main-
tained and stored;
− in the forwarding plane, IP packets are forwarded from an ingress inter-
face to an egress interface, using appropriate forwarding information.
Forwarding information
− can either be static or dynamic;
− is stored in the routing table;
− is composed of a destination IP address range and a gateway address.
ABB ETER1 551 39

ROUTING FUNCTIONS
5
5.5.1 Static routing

Static routing is a simple and basic function for every router. The corresponding
forwarding information is manually entered by the user and is thus part of the
configuration. With static routing very stable networks can be set up, but on the
other hand static routing is unable to react on possible topology changes on the
network.
For the configuration of static routes in ETER1 see paragraph 8.1.4.2 Router
(on page 80).
5.5.1.1 Connecting an OSPF or a RIP network with ETER1 to other networks

The ETER1 unit uses static routing in order to interconnect between a network
with dynamic routing (OSPF or RIP) where it is itself part of and any external
destination.
default route specific

external route
external
large network ETER1 OSPF or RIP destination
static routing static routing

static routing
or EGRP
Internet
Figure 14: Interconnecting networks
In order to get efficient static interconnections between networks it is essential

to have clear allocations of IP addresses, as this can drastically reduce the nec-
essary number of static routes.
5.5.2 OSPF routing

OSPF is a dynamic routing protocol for IP networks. It uses a link state routing
algorithm and falls into the group of interior routing protocols, operating within a
single autonomous system (AS).
All OSPF routers within an AS or alternatively within an area store identical net-
work information in the link state data base (LSDB), which is periodically
updated through flooding within the AS or within the area. From the LSDB each
router calculates the appropriate routes for the routing table with the so called
«shortest path first» algorithm.
OSPF runs in the control plane of a router.
5.5.2.1 Static routes and OSPF routing

From the OSPF AS point of view, a static route points to a destination some-
where outside the AS, i.e. it is considered as an external destination and corre-
spondingly as an external route. Normally, external routes are distributed to the
whole AS and routers that advertise external routes are considered as AS bor-
der routers. Exceptions to this rule are described in the paragraph below.
40 ETER1 551 ABB

ROUTING FUNCTIONS
Please note:
OSPF external routes are advertised only if «Redistribution» of static sources is
enabled.
Figure 15: Redistribution of static routes
5.5.2.2 OSPF areas

In order to reduce overhead traffic and save memory resources in medium and
large OSPF ASs, an AS can be divided into areas. It is then differentiated
between intra area routing (routing within an area) and inter area routing. The
detailed network information down to the single router and network is distributed
within an area only. For other areas this information is reduced to a summary. A
special role in each AS plays the backbone area. It is mandatory for each AS,
must have an ID of «0» and must be of type «Normal». The backbone area
builds the core of the OSPF network and all other areas (with a non-zero ID)
must physically connect to the backbone.
Please note:
There is no hard limit for an allowed number of routers per area, as this is
depending on the number of interfaces per router, the routers hardware capabil-
ities, the area topology, the area mode and other indicators. However, as a
defensive rule of thumb, a network should perform stable with up to about 50
routers per area. Keep in mind, that the most loaded routers are the area border
routers, since they have to store the LSAs of more than one area.
Areas can be of type «Normal», «Stub» or «NSSA».
Stub areas and NSSA can help reducing overhead traffic, but support AS exter-
nal routes in a restricted way only.
Please note:
The stub area and NSSA features should be used by OSPF experts only. If in
doubt, please use areas in default mode.
5.5.2.3 OSPF neighbours

Two or more OSPF routers in the same broadcast domain or at each end of a
point-to-point link form an adjacency when they have detected each other. But
before the adjacency is built, a few conditions must be met, some of them con-
cerning the router instance, some the connecting interfaces.
• The connecting interfaces of the neighbouring routers must
− belong to the same area;
− use the same authentication key (if authentication is used);
− use the same timing parameters for hello- and dead-interval.
ABB ETER1 551 41

ROUTING FUNCTIONS
5
• The common area of the neighbouring routers must use the same configura-
tion for
− area mode (normal, stub, NSSA),
− OSPF packet authentication (none, simple, MD5).
It is not necessary for OSPF routers in a broadcast network to become fully
adjacent to each other router in the same network, as this would multiply the
traffic for OSPF internal data exchange. Instead one router advertises the com-
mon network properties in the OSPF AS. This router is called the designated
router. The designated router along with a backup designated router is elected
from all OSPF routers in the broadcast network upon the highest priority value.
The two routers of a point-to-point link always form full adjacency.
5.5.2.4 OSPF packet authentication

Authentication helps in maintaining a network stable and safe. Let’s take the
case, where an AS border router is by mistake configured to run OSPF on the
interface that connects to the neighbouring network external to the AS. It would
then collect unwanted routing information from the „foreign“ network and inject it
into his native AS, with potential damage to the proper routing in the network.
The use of authentication reduces the danger of routers mistakenly taking part
of an OSPF AS and for this use case a simple authentication is adequate.
Another use case is to prevent installing a router in the AS with vicious inten-
tion. In this case MD5 cryptographic authentication should be used.
5.5.3 RIP routing

The Routing Information Protocol, commonly called RIP, is a distance-vector
routing protocol, which employs the hop count as a routing metric. Despite its
obvious shortages and drawbacks, RIP is one of the most enduring of all routing
protocols. The maximum number of hops allowed for RIP is 15, which in fact
makes clear, that RIP is intended for smaller networks only. ABB recommends
favouring OSPF routing over RIP, for all cases where the user has a choice.
The ETER1 unit supports RIP mainly for maintaining existing RIP networks or to
provide interfacing between OSPF and RIP networks.
5.5.3.1 RIP version and authentication

Support of RIP versions 1 and 2 is associated with the support of authentica-
tion:
• RIPv1 does not support authentication, therefore simple or MD5 authentica-
tion is only selectable together with RIPv2.
• Together with RIPv1 the user can select between supporting either RIPv1,
RIPv2 or both versions.
For the decision whether to use authentication or not and the choice between
simple and MD5 authentication, the same considerations as for OSPF apply to
a RIP network.
5.5.3.2 The split horizon feature

A major drawback of RIP is its slow conversion in case of a link failure. In the
original version (RIPv1) a recursive process had to count up to the maximum
hop count of 16 in order to detect an obsolete route. The split horizon feature
inhibits sending route information back to a neighbour router where it had origi-
nally been learned from. Counting up to 16 is (in most cases) no longer neces-
sary and thus speeds up networks convergence.
42 ETER1 551 ABB

ROUTING FUNCTIONS
«Split horizon» is activated by default and should not be deactivated without

strong need of a dedicated application.
5.5.4 Mutual redistribution of routing information

A router is located at the border between an OSPF network an a RIP network
and has active interfaces in both networks. It therefore gathers routing informa-
tion from both the OSPF and the RIP network. The question arises, whether
and how the router should redistribute routing information gathered in one net-
work towards the other network.
The following rules should be followed for this situation:
• Never redistribute in both directions OSPF –> RIP and RIP –> OSPF
• If redistribution from OSPF into RIP is selected, use static routing from RIP
into OSPF (redistribution example below)
• If redistribution from RIP into OSPF is selected, use static routing from
OSPF into RIP
• Redistribution from OSPF into RIP is more common than in the other direc-
tion
• Redistribution of connected interfaces has almost the same effect as activat-
ing the interface in the corresponding protocol in passive mode, with a subtle
distinction in case of OSPF:
Redistributed connected interfaces are advertised with external LSAs and
can therefore not be summarized via area ranges. Furthermore external
LSAs are not usable by stub areas.
Please note:
Whenever possible prefer configuring interfaces in passive mode over redistri-
bution of connected interfaces. For more information regarding the passive
mode, refer to Table 33: Parameters for the «OSPF» menu (on page 77).
Figure 16: Redistribution example
ABB ETER1 551 43

ROUTING FUNCTIONS
5
5.5.5 VRRP, the virtual router

In order to increase availability, critical network components like gateway rout-
ers should be built redundant. There is no problem to establish a redundant
connection on the Ethernet layer from an IP host to both a main and a backup
gateway router. But a problem remains on the IP layer: the configured gateway
address in the IP host points to one of the two gateway routers and in case of
failure a manual reconfiguration action is needed.
Backup gateway router B with IP address

Gateway address different from gateway router A
= IP address of
Gateway router A
switch IP network
IP host Gateway router A
Figure 17: IP host connected to redundant gateway routers
The Virtual Router Redundancy Protocol (VRRP) efficiently solves this single
point of failure inherent in static default routed environments. This increased
reliability is achieved by advertising a virtual router, an abstract representation
of master and backup routers acting as a group. From the IP host’s point of
view, the behaviour of the virtual router is the same as a physical router includ-
ing the IP address. When the IP address of the virtual router is configured as
gateway address in the IP host, connectivity to the network is available as long
as at least one physical member of the virtual router group is up and running.
Gateway address
= IP address of gateway router B with VRRP
the virtual router
switch
IP network
IP host
virtual
router
gateway router A with VRRP

Figure 18: IP host logically connected to a virtual router
5.5.5.1 Electing the master router

VRRP specifies an election protocol that dynamically assigns responsibility for a
virtual router among a set of participating redundant routers. The elected router
is called the master and is responsible for the following tasks:
• respond to ARP requests for the virtual router’s IP address;
• forward packets that are sent to the virtual router’s IP address;
• periodically send advertisements with its properties as current master;
• check received advertisements on higher priority than the own priority;
• transit to the backup state if received priority is higher than the own and
preemption is enabled.
All other participating VRRP routers are in the backup state and have nothing to
do than listening for the master routers advertisements. Missing advertisements
from the master router trigger, after a timeout period, a new master election.
44 ETER1 551 ABB

ROUTING FUNCTIONS
Please note:
This description is simplified and does not contain all possible cases and sub
cases as stated in the VRRP standard (RFC 3768).
5.5.5.2 The virtual router’s MAC address

The VRRP standard defines a reserved range of IEEE 802 MAC addresses that
should be used by the VRRP master in response to ARP requests and as
source address for packets sent by the master. This virtual MAC address may
only be used by the master and has the following value:
00-00-5E-00-01-{VRID}, where VRID is an 8 bit value with the virtual router’s ID.
Please note:
The ETER1 VRRP implementation does not use the virtual MAC address.
Instead the MAC address of the corresponding Ethernet interface on the ETER1
is used. As a consequence, the virtual router’s MAC address changes each
time a new router becomes master. In order to immediately reflect this change
in all IP host’s MAC tables, a gratuitous ARP is broadcasted on the LAN by the
newly elected master.
5.5.5.3 Master preemption and address owner

It is often desirable to keep switching of current master to an absolute minimum.
Especially when the participating VRRP routers offer similar path quality it
makes sense to administratively disable preemption. If preemption is disabled,
the currently active master stays master, even if another VRRP router adver-
tises a higher priority than the current master’s priority. Only an owner of the vir-
tual router’s address can override the disabled preemption status and becomes
immediately master when it is up and running.
Each router that participates in a virtual router still has its own IP address in the
same subnet as the virtual router’s IP address. If a router is configured with its
own IP address matching the virtual router’s IP address it is considered as the
owner of the address, becomes immediately master and starts sending adver-
tisements with the highest priority of 255, irrespective from its actually config-
ured VRRP priority.
5.5.5.4 A common VRRP application with load sharing

Applications with just one virtual router fulfil the demand for gateway router
redundancy, but all packet forwarding is solely performed by the master and all
backup routers run idle. The application in the figure below is quite common and
allows load sharing. As in the previous example in Figure 18: IP host logically
connected to a virtual router (on page 44), we have still two gateway routers,
but this time each is participating in two virtual routers. The VRRP priorities are
selected in order to have different masters for the virtual routers. Furthermore
the IP hosts use different gateway addresses.
ABB ETER1 551 45

INTERFACE STACKS
5
Gateway router A participates

IP host x with in virtual router 1 with priority=200 and
gateway address in virtual router 2 with priority=100
= IP address of
virtual router 1
switch
IP network
IP host y with Virtual
gateway address router 1
= IP address of
virtual router 2 Gateway router B participates
Virtual in virtual router 1 with priority=100 and
router 2 in virtual router 2 with priority=200
Figure 19: VRRP application with load sharing
Under normal conditions both physical gateway routers are available. Gateway
router A will be master of virtual router 1 and gateway router B will be master of
virtual router 2. IP host x sends all its traffic to the virtual router 1 (gateway
address) and IP host y sends all its traffic to the virtual router 2. In case of a
gateway router failure, the remaining one will become master of both virtual
routers and handles all the traffic for all IP hosts that use gateway addresses
from virtual router 1 or 2.
5.6 Interface stacks

5.6.1 Generic stack model
The generic stack model reflects the ETER1 unit’s full capabilities in respect of
networking functions and in respect of interface functions. The stack model also
shows the interface depending signal treatment (packet encapsulation) between
the networking function and the physical interface.
• ETER1 networking functions
− MAC bridging
− IP routing
• ETER1 interfaces
− Ethernet
− TDM, i.e. P0nc/P12 via the FOX internal PBUS
− VLAN interface
• ETER1 encapsulations
− IEEE 802.3 (Ethernet/bridging)
− IPoE/ARP (Ethernet/routing)
− MAC/PPP (TDM/bridging)
− MAC/HDLC (TDM/bridging)
− IP/PPP (TDM/routing)
− PPP/HDLC (Standard WAN encapsulation)
The generic stack model allows graphical connection of two interfaces with the
corresponding encapsulation.
46 ETER1 551 ABB

INTERFACE STACKS
ETER1
Networking function
Encapsulation Encapsulation
Physical interface Physical interface
Figure 20: Generic stack model
Sometimes the encapsulation and the physical interface is omitted for one side.
In this case, the blank side is not essential for the application and could be of
any type.
ETER1 or 3rd party equipment

Networking function
Encapsulation Encapsulation and

interface omitted
Physical interface
Figure 21: Omitted encapsulation type
How the generic stack model can be used is shown by the hypothetical applica-
tion examples below.
5.6.2 MAC/PPP bridged encapsulation

ETER1 supports the MAC/PPP framing and the BCP protocol defined by RFC
1638 and additional features defined by the updated specifications RFC 2878
and RFC 3518.
5.6.3 MAC bridged encapsulation for DTM-M

ETER1 supports direct MAC/HDLC encapsulation compatible with DTM-M and
DATAx. With this feature the ETER1 unit can terminate a DTM-M link and con-
tinue the connection with standard PPP.
ETER1 DTM-M
MAC Bridging MAC Bridging
MAC/PPP STICx
RFC 3518* MAC/HDLC MAC/HDLC IEEE 802.3
PPP P0nc/P12x
P0nc/P12x PBUS PBUS DSL DSL link DSL 10/100Base-T
RFC 1661
PPP/HDLC
LOMIx RFC 1662
E1 HDB3 PBUS
PBUS
P0nc/P12x P0nc/P12x
Ethernet
3rd party Bridge/Switch with serial I/F LAN
MAC Bridging
MAC/PPP
RFC 3518
PPP
RFC 1661
PPP/HDLC
PDH/SDH RFC 1662
network
serial interface
G.703
Figure 22: Connection of DTM-M to 3rd party Bridge/Switch
ABB ETER1 551 47

INTERFACE STACKS
5
5.6.4 PPP/HDLC encapsulation & framing

ETER1 supports the standard Point-to-Point Protocol (PPP according to
RFC1661) combined with the HDLC-like framing for PPP encapsulated packets
according to RFC1662.
This is a widely used standard to transport data of various protocols over syn-
chronous serial bit streams (e.g. with X.21, V.35 or G.703 interfaces).
5.6.5 Hypothetical applications with bridging

The following ETER1 bridging applications in the figures below are all intercon-
nected via a common PDH/SDH network:
1 TDM WAN link termination with MAC/PPP
2 Ethernet LAN – TDM WAN connection
3 Traffic aggregation with STICx and DTM-M modem
4 Traffic aggregation with STICx and DTM-M modem plus translation of TDM
WAN link termination from MAC/PPP to MAC/HDLC
5 Traffic aggregation with DATAx and LAN interface
6 Traffic aggregation with DATAx and serial interface
7 TDM WAN connection to LAWA4/LEMU6
8 TDM WAN connection to 3rd party bridge with G.703 interface
48 ETER1 551 ABB

INTERFACE STACKS
Bridging application 1: ETER1

TDM WAN link termination
with MAC/PPP MAC Bridging
MAC/PPP
RFC 3518*
PPP
RFC 1661
PPP/HDLC
LOMIx RFC 1662
PDH/SDH E1 HDB3 PBUS
PBUS
network P0nc/P12x P0nc/P12x
Bridging application 2: ETER1

Ethernet LAN – TDM WAN connection
IP routing
IPoE/ARP
IEEE 802.3
ETER1
MAC Bridging 10/100Base-T
MAC/PPP
RFC 3518 IEEE 802.3 ETER1
PPP 10/100Base-T MAC Bridging
RFC 1661 Ethernet LAN
PPP/HDLC IEEE 802.3
RFC 1662
LOMIx PBUS
P0nc/P12x 10/100Base-T
3rd party Bridge

MAC Bridging
IEEE 802.3
10/100Base-T
Gb Ethernet
Bridging application 3:
Traffic aggregation with STICx and DTM-M modem
ETER1 3rd party Bridge with serial I/F

MAC/PPP MAC/PPP MAC/PPP
RFC 3518 RFC 3518 RFC 3518
PPP PPP PPP
RFC 1661 RFC 1661 RFC 1661
PPP/HDLC PPP/HDLC STICx DTM-M PPP/HDLC
RFC 1662 RFC 1662 RFC 1662
PBUS PBUS P0nc/P12x serial interface
LOMIx PBUS DSL link DSL serial
P0nc/P12x P0nc/P12x DSL interface G.703
Traffic aggregation with STICx and DTM-M modem plus 3rd party IP host
translation of TDM WAN link termination from MAC/PPP to MAC/HDLC with Ethernet I/F
DTM-M IP
ETER1
MAC Bridging MAC Bridging IPoE/ARP
MAC/PPP MAC/HDLC STICx MAC/HDLC IEEE 802.3 IEEE 802.3
RFC 3518
PPP P0nc/P12x P0nc/P12x 10/100Base-T
PBUS DSL DSL link DSL 10/100Base-T
RFC 1661 PBUS Gb Ethernet
PPP/HDLC
RFC 1662
LOMIx PBUS
P0nc/P12x
Figure 23: Stack details for ETER1 bridging applications
ABB ETER1 551 49

INTERFACE STACKS
5
PDH/SDH
network
Bridging application 5: 3rd party IP host

Traffic aggregation with DATAx and LAN interface with Ethernet I/F
ETER1 DATAx IP
MAC Bridging MAC Bridging IPoE/ARP

MAC/PPP MAC/PPP MAC/PPP IEEE 802.3 IEEE 802.3
RFC 3518* RFC 3518* RFC 1638
PPP PPP PPP 10/100Base-T
RFC 1661 RFC 1661 RFC 1661 10Base-T Gb Ethernet
PPP/HDLC PPP/HDLC PPP/HDLC
RFC 1662 RFC 1662 RFC 1662
LOMIx PBUS PBUS serial interface
P0nc/P12x P0nc/P12x G.703
Traffic aggregation with DATAx and serial interface
ETER1 3rd party Bridge with serial /IF

MAC/PPP MAC/PPP MAC/PPP
RFC 3518* RFC 3518* RFC 3518
PPP PPP PPP
RFC 1661 RFC 1661 RFC 1661
PPP/HDLC PPP/HDLC PPP/HDLC
RFC 1662 RFC 1662 DATAx RFC 1662
PBUS PBUS P0nc/P12x serial interface
LOMIx PBUS serial
P0nc/P12x P0nc/P12x interface G.703
TDM WAN connection to LAWA 4/LEMU6
LAWA4 / LEMU6
MAC bridging
MAC/PPP
RFC 1638
PPP
RFC 1661
PPP/HDLC
RFC 1662
LOMIx PBUS
P0nc/P12x
TDM WAN connection to 3rd party bridge with G .703 interface
3rd party Bridge with serial /IF

MAC Bridging
MAC/PPP
RFC 3518
PPP
RFC 1661
PPP/HDLC
RFC 1662
serial interface
G.703
* MAC/PPP RFC3518 is compatible with its predecessors RFC1638 and RFC2878
Figure 24: Stack details for ETER1 bridging applications (continued)
50 ETER1 551 ABB

INTERFACE STACKS
5.6.6 Hypothetical applications with routing

The following ETER1 routing applications in the figures below are all intercon-
nected via a common PDH/SDH network:
1 TDM WAN link termination with IP/PPP
2 Ethernet LAN – TDM WAN connection
3 TDM WAN connection to LAWA4/LEMU6
4 TDM WAN connection to 3rd party router with G.703 interface
5 Interconnection of bridged and routed network segments using the ETER1
virtual interface
Routing application 1: ETER1

TDM WAN link termination with IP /PPP
IP routing
IP/PPP
RFC 1332
PPP
RFC 1661
PPP/HDLC
LOMIx RFC 1662
PDH/SDH E1 HDB3 PBUS
network PBUS
P0nc/P12x P0nc/P12x
Routing application 2: ETER1

Ethernet LAN – TDM WAN connection
IP routing
IPoE/ARP
IEEE 802.3
ETER1
IP routing 10/100Base-T
IP/PPP IPoE/ARP
RFC 1332 ETER1
PPP
RFC 1661 IEEE 802.3 MAC Bridging
PPP/HDLC 10/100Base-T IEEE 802.3
RFC 1662 Ethernet LAN
LOMIx PBUS 10/100Base-T
P0nc/P12x
3rd party Bridge

MAC Bridging
IEEE 802.3
10/100Base-T
Gb Ethernet
Routing application 3:
TDM WAN connection to LAWA 4/LEMU6
LAWA4/LEMU6
IP routing
IP/PPP
RFC 1332
PPP
RFC 1661
PPP/HDLC
RFC 1662
LOMIx PBUS
P0nc/P12x
Figure 25: Stack details for ETER1 routing applications
ABB ETER1 551 51

INTERFACE STACKS
5
PDH/SDH
network
TDM WAN connection to 3rd party router with G.703 interface
3rd party router with serial /IF

IP routing
IP/PPP
RFC 1332
PPP
RFC 1661
PPP/HDLC
RFC 1662
serial interface
G.703
Interconnection of bridged and routed network
segments using the ETER 1 VLAN interface
ETER1
IP routing MAC Bridging
VLAN
IP/PPP interface MAC/PPP
IPoE/ARP IPoE/ARP IEEE 802.3
RFC 1332 RFC 3518
PPP IEEE 802.3 10/100Base-T PPP
RFC 1661 RFC 1661
PPP/HDLC PPP/HDLC
RFC 1662 10/100Base-T RFC 1662
LOMIx PBUS PBUS
P0nc/P12x P0nc/P12x
Ethernet
ETER1 LAN
MAC Bridging
MAC/PPP
RFC 3518
PPP
RFC 1661
PPP/HDLC
RFC 1662 LOMIx LOMIx
PBUS P0nc/P12x PDH/SDH E1 HDB3
PBUS network PBUS
P0nc/P12x E1 HDB3 P0nc/P12x
3rd party Bridge with serial /IF

MAC Bridging
MAC/PPP
RFC 3518
PPP
RFC 1661
PPP/HDLC
RFC 1662
serial interface
G.703
Figure 26: Stack details for ETER1 routing applications (continued)
52 ETER1 551 ABB

MULTILINK PPP INTERFACE
5.7 Multilink PPP interface

ETER1 supports Multilink PPP (MLPPP) according to RFC1990, which is a
standard method for splitting, recombining and sequencing datagrams across
multiple logical data links. The goal of multilink operation is to coordinate multi-
ple independent links between a fixed pair of systems, providing a virtual link
with greater bandwidth than any of the constituent members. With Multilink
PPP, ETER1 can provide an aggregate link bandwidth of up to 32 Mbit/s.
MLPPP is not depending on the corresponding networking function, i.e. it works
with both bridging and routing.
ETER1 ETER1
MAC Bridging IP routing
Multilink -PPP, RFC1990 Multilink -PPP, RFC1990

Termination at MAC/PPP MAC/PPP MAC/PPP IP/PPP IP/PPP IP/PPP
the far side with RFC 3518 RFC 3518 RFC 3518 RFC 1332 RFC 1332 RFC 1332
Multilink PPP PPP PPP PPP PPP PPP PPP
accordingly RFC 1661 RFC 1661 RFC 1661 RFC 1661 RFC 1661 RFC 1661
(ETER1 or third PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC
RFC 1662 RFC 1662 RFC 1662 RFC 1662 RFC 1662 RFC 1662
party equipment)
PBUS PBUS PBUS PBUS PBUS PBUS
P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x
LOMIx
E1 HDB3
PBUS
P0nc/P12x
PDH/SDH
network LOMIx
E1 HDB3
PBUS
P0nc/P12x
Member links of the MLPPP bundle Member links of the MLPPP bundle
- All member links with MAC/PPP, RFC 3518 - All member links with IP /PPP, RFC 1332
- Bandwidth per member link up to 2Mbit/s - Bandwidth per member link up to 2Mbit/s
- Number of member links limited by total - Number of member links limited by total
available B/W available B/W
Figure 27: Block diagram and stacks for Multilink PPP
5.7.1 Bandwidth considerations for multilink PPP bundles
Risk of operating trouble!

Although multilink PPP allows combining of member links with different band-
width, it is strongly recommended to use member links of the same bandwidth
in MLPPP bundles.
Non-observance of this rule can result in excessive packet loss, as the reas-
sembly process discards packets when the delay difference for the fragments
on fast and slow member links exceeds a certain limit.
5.7.2 Link quality considerations for multilink PPP bundles

Member links of multilink PPP bundles should consist of similar link quality. Due
to the process of splitting up packets in segments at the transmit side and
recombining the segments at the receive side, it is obvious that bad segments
(from one bad link) can degrade the quality of the whole bundle. Therefore it
could have a positive effect on the throughput of the multilink PPP bundle when
a bad member link is excluded from the bundle by a manual reconfiguration.
ABB ETER1 551 53

VLAN INTERFACES
5
5.7.3 Delay considerations for multilink PPP bundles

For delay calculations on multilink PPP bundles the aggregated total bandwidth
may not be used, but the single link bandwidth must be considered instead.
5.7.4 Joining and leaving of link members to and from a multilink

PPP bundle
All member links handle their PPP LCP individually including link up and link
down procedures. The multilink PPP stays in operation, as long as one member
link is up and running.
Changes in the number of member links will always lead to an interruption of
the corresponding multilink bundle in the range of 30 seconds up to several
minutes. This behaviour is independent from the reason for the change in mem-
ber link numbers (interruptions in the communication network or configuration
changes).
5.8 VLAN Interfaces

The ETER1 unit provides different ways of connecting Ethernet LAN interfaces
to the router.
direct assignment (standard case)
assignment via a VLAN interface

Ethernet
VLAN
LAN interface
interfaces
assignment via a bridge
instance and a VLAN interface
VLAN
interface
Figure 28: Connecting Ethernet LAN interfaces to the router
Accordingly, there is a choice for connecting TDM WAN interfaces to the router.
direct assignment (standard case )
TDM WAN
interfaces assignment via a bridge
instance and a VLAN interface
VLAN
interface
Figure 29: Connecting TDM WAN interfaces to the router
Please note:
The configuration of the peer device on the WAN link must be observed, since
the packet encapsulation for the two choices are not cross compatible. See par-
agraph 5.6 Interface stacks (on page 46) for stack details.
The virtual LAN interface is a versatile function mainly for:
− selective routing per VLAN;
54 ETER1 551 ABB

VLAN INTERFACES
− inter-VLAN routing;
− connection between bridged and routed network segments.
From the router’s point of view a VLAN interface is handled the same way as
any other numbered interface. For the stack details of a VLAN interface see
paragraph 5.6.6 Hypothetical applications with routing (on page 51).
5.8.1 Selective routing per VLAN

An application uses four IP subnets in class C size:
• Subnet A, IP address 172.16.31.0/24
• Subnet B, IP address 172.16.32.0/24
• Subnet C, IP address 172.16.33.0/24
• Subnet D, IP address 172.16.34.0/24
A router acts as gateway for all subnets and furthermore provides IP connectiv-
ity between the subnets.
In the classic solution there is a port on the router reserved per IP subnet and
the subnets are physically isolated. In the VLAN solution the physical LAN setup
is decoupled from the logical setup.
Solution with router port per IP subnet VLAN solution with decoupled physical and logical setup
VLAN I/F, VLAN Id = 101 ETER1

subnets A + B
subnet A VLAN Id 101/102 IP addr = 172.16.31.1/24
VLAN I/F, VLAN Id = 102
subnet B Gateway IP addr = 172.16.32.1/24 Gateway
subnets A + C
VLAN Id 101/103 VLAN I/F, VLAN Id = 103
subnet C
IP addr = 172.16.33.1/24
subnet D subnets A + B + D VLAN I/F, VLAN Id = 104
VLAN Id 101/102 /104 IP addr = 172.16.34.1/24
Figure 30: Selective VLAN routing
5.8.2 Inter-VLAN routing

Ethernet LANs grow bigger and bigger but there are good reasons to keep IP
subnets down to a reasonable size. In practice, the class C size subnet with 254
IP host addresses is a typical subnet size. By using VLANs, we can build appli-
cations, where several IP subnets run on the same physical Ethernet LAN. In
order to provide IP connectivity between the subnets, we need IP routing
between the corresponding VLANs. The solution as shown in the figure below is
also known as a «router on a stick».
Ethernet LAN with tagged

and untagged ranges
VLAN X untagged VLAN I/F, VLAN Id = 101 ETER1
VLAN -ID = 168 not routed by Eth -1 IP addr = 172.16.32.1/24
not routed by Eth -1 Ethernet
VLAN I/F, VLAN Id = 102
VLAN C VLAN A front port IP addr = 172.16.33.1/24
IP-addr = 172.16.34.0/24 IP-addr = 172 .16.32.0/24 Eth-1
VLAN -ID = 103 VLAN -ID = 101 VLAN I/F, VLAN Id = 103
VLAN B
IP-addr = 172 .16.33.0/24 IP addr = 172.16.34.1/24
VLAN -ID = 102
Figure 31: Inter-VLAN routing
ABB ETER1 551 55

QOS
5
5.8.3 Connecting bridged and routed network segments

In this application ETER1 is used for aggregating remote network access points
to a central service point. The network is divided into a bridged part with DTM-M
and a routed part between the ETER1 units and the central service point. The
VLAN interface provides the ETER1 internal connection between bridging and
routing.
DTM-M
DTM-M
DTM-M
DTM-M
DTM-M
Figure 32: The VLAN interface connects between bridging and routing
5.9 QoS
QoS for the ETER1 means forwarding received traffic depending on the traffic
priority. This function becomes essential when fast ingress traffic (from Ethernet
ports) is destined for slower egress ports (TDM ports). Several processes are
involved in the QoS function:
• Traffic classification
• Traffic queueing
• Priority mapping to queues
5.9.1 Frame classification and marking

Frame classification is depending on the networking function and on the
received frame type.
Table 21: Frame classification for QoS

MAC bridging IP routing
VLAN tagged or priority untagged frame The packet priority is
tagged frame derived from the DSCP
The frame priority is derived The frame priority is derived field in the IPv4 header
from the frame tag from the ingress port priority
56 ETER1 551 ABB

QOS
5.9.2 Traffic queueing

ETER1 provides queuing facilities in order to handle user traffic according to its
proper priority.
• Input queuing (HW RX queue)
The input queue must absorb ingress line speed bursts.
• Output queuing (HW/SW TX queue)
Output queues must absorb bursts from the frame forwarding process. This
is particularly the case, if data streams from fast Ethernet inputs feed TDM
outputs. It also occurs, if several input streams feed a single output stream of
the same bandwidth.
HW RX
from Ethernet I/F
queue
SW TX queue 1
HW TX Queue SW TX queue 2
to E the rnet I/F scheduling
queue SW TX queue 3
SW TX queue 4
HW TX queue full *
HW RX
from TDM I/F
queue
SW TX queue 1
HW TX Queue SW TX queue 2
to TDM I/F scheduling
queue SW TX queue 3 Frame processing
SW TX queue 4
and forwarding
HW TX queue full * (network
processor)
HW RX
from TDM I/F
queue ML PPP
Mul tilin k PPP bun dle
HW RX Rx
from TDM I/F
queue
HW TX
to TDM I/F
queue SW TX queue 1
queue full * Queue
ML PPP SW TX queue 2
schedu-
HW TX Tx SW TX queue 3
to TDM I/F ling
queue SW TX queue 4
queue full *
HW TX queue full *
* no SW TX queue is filled up as long the HW TX queue is not full
Figure 33: Frame handling for QoS in ETER1
• Queue scheduling
A scheduling process is responsible to empty a set of queues in a predeter-
mined way. The current release of ETER1 uses strict priority scheduling.
• Forwarding service fairness
Ingress frames from the active interfaces are served and forwarded in a
round robin way.
ABB ETER1 551 57

QOS
5
5.9.3 Priority mapping with profiles

The generic FOX profile feature is used in order to define priority maps. A
default QoS mapping profile «QoS_Default» is always available in the UCST
with mapping characteristics as shown in the table below.
Table 22: Default priority mapping for MAC frames

802.1p MAC priority TX queue number Priority
1 Background 1 lowest priority
2 Spare 1 lowest priority
0 Best Effort [DEFAULT] 2 low priority
3 Excellent Effort 2 low priority
4 Controlled Load 3 high priority
5 Video 3 high priority
6 Voice 4 highest priority
7 Network Control 4 highest priority
Table 23: Default priority mapping for IP packets

DSCP value TX queue number Priority
0 ... 15 1 lowest priority
16 ... 31 2 low priority
32 ... 47 3 high priority
48 ... 63 4 highest priority
58 ETER1 551 ABB

THE MANAGED OBJECTS TREE
6 Commissioning
6.1 The managed objects tree

All user configurable parameters of the ETER1 unit, i.e. the managed objects
are arranged in a tree. The tree root corresponds to the slot in the UCST main
menu, the branches are tags in the first menu and the leafs contain the actual
parameter settings, mostly static tables and some dynamic tables.
ETER1_R2
Board Interfaces Bridges IPv4 Routing
Common Bridge-1 IF
Settings QoS Bridges Bridge -2 IF Router
Bridge-3 IF
Unit Mode Mapping Bridge-1 Bridge-4 IF
Profile Bridge-5 IF
Bridge-6 IF
Bridge -7 IF
Bridge-8 Bridge-8 IF Static
Routes OSPF RIP Redistribution
Dynamic list Dynamic Auto Direction

of bridge list of static Backbone
summary RIP  OSPF
interfaces routes
Ethernet TDM Multilink VLAN
Phy Interfaces PPP Interfaces Dynamic list of Direction
areas 2 … 7 OSPF  RIP
Eth-1 TDM Multilink VLAN
Interface -1 PPP-1 interface -1
Eth-2
Dynamic list of area
Eth-3 address ranges
Interfaces
TDM Multilink VLAN
Eth-4
Interface -64 PPP-8 interface -32
Addressing OSPF RIP VRRP
ETER1_R2 tree root Dynamic list Dynamic list Dynamic list Dynamic list of
of router of router of router routed LAN interfaces
interfaces interfaces interfaces (Ethernet and VLAN )
Interfaces tree branch (node)
TDM
Interface -1
tree leaf
Figure 34: Managed objects tree for ETER1
ABB ETER1 551 59

COMMISSIONING STEPS
6
6.2 Commissioning steps

6.2.1 New units in the FOX subrack
A new unit must be created by the user with the «Add Unit» menu. Double click-
ing in an empty slot opens the menu.
Figure 35: «Add Unit» menu
The units are automatically initialised when power is switched on (i.e. when the
unit is plugged into the subrack). The unit obtains the configuration data from
the COBU<X>.
6.2.2 Setting the configurable parameters

Generally the tags in the ETER1 UCST configuration menu are arranged in the
same order as the parameters should be entered:
The parameter «Unit Mode» under the «Board» tag needs special attention, as
it should not be changed after the TDM interfaces have been configured. See
also paragraph 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s» (on
page 33) for details.
Before bridging and routing functions can be configured, the necessary inter-
faces must be activated. Special care is needed for the arrangement of TDM
interfaces, especially in bandwidth demanding applications. Make sure to start
with the broad links and configure multilink PPP first.
Please note:
UCST does checks numerous dependencies between different parameters, in
order to prevent inconsistent configurations. A warning pops up in case the
entered selection interferes with configuration rules or is not compatible with
previously entered values.
However it is not possible for UCST to prevent all possible inconsistencies or
otherwise non-working configurations.
60 ETER1 551 ABB

GENERAL OPERATION RECOMMENDATIONS
7 Operation and Maintenance
7.1 General operation recommendations

When setting up or debugging an access network using the ETER1, the task is
facilitated by using the implemented operation, alarm and maintenance fea-
tures:
• Alarms and status indications
Alarms and status indications provide a detailed view for both the physical
layer and the link layer.
• Performance Monitoring
Performance parameters give information about the long term stability and
reliability of a link. Furthermore packet statistics provide information for
detailed traffic analysis in the network.
7.2 Status and maintenance

To access the status and maintenance functions of a unit in FOX, click on the
unit and select the menu entry «Unit Configuration» – «Status/Maintenance….»,
then select the appropriate layer and function tag.
For a more detailed description of the Status/Maintenance menus see para-
graph 8.3 Status/Maintenance (on page 84).
7.3 Performance monitoring

The ETER1 unit provides performance monitoring data for all types of interfaces
and for the bridge instances. These test points, i.e. locations where the various
counters collect their information, are allocated in a tree.
ABB ETER1 551 61

PERFORMANCE MONITORING
7
«Board» layer
available counter groups : MIB-2 Statistics
RSTP available types : «Counter»
Unfiltered Events
RSTP Bridge Counters
«Ethernet Phy» layer
available counter groups : MIB-2 Statistics available types : «Counter»
RSTP
Individual Ethernet interface layers available types : «PM 15 min»

available counter groups : MIB-2 Statistics «PM 24h»
RSTP «Counter»
«TDM Interfaces» layer
RSTP
Unfiltered Events
Individual TDM interface layers available types : «PM 15 min»

RSTP
«Counter»
Unfiltered Events
«Multilink PPP» layer

RSTP
Individual Multilink PPP interface layers available types : «PM 15 min»

RSTP «Counter»
«Bridges» layer
available types : «Counter»
available counter group : RSTP Bridge Counters
Individual Bridge layers available types : «PM 15 min»

available counter group : RSTP Bridge Counters «PM 24h»
«Counter»
«RouterIF» layer and «Loopback» layer
available counter group : MIB-2 Statistics available types : «Counter»
«VLAN Interfaces» layer

available counter group : MIB-2 Statistics available types : «Counter»
Individual VLAN interface layers available types : «PM 15 min»

available counter group : MIB-2 Statistics «PM 24h»
«Counter»
Figure 36: Location selection tree for PM
The ETER1 performance monitoring provides four different counter groups:

• MIB-2 Statistics,
• RSTP,
• Unfiltered events,
• RSTP Bridge Counters.
Depending on the traffic signal layer, a selection of the above counter groups is
available.
On a single traffic interface layer the following counter types are available:
• PM 15min (up to 96 15 minutes intervals)
• PM 24h (up to 7 24 hours intervals)
• Counter (user counter with infinite duration, can be reset by the user)
On all upper traffic layers, only the user counter is available.
Please note:
The performance monitoring is always running. It is not traffic disturbing.
62 ETER1 551 ABB

Please note:
PM data is not available unless the real time clock has been set in the network
element (menu «NE Configuration» – «Set Time…»).
Please note:
Performance monitoring on ETER1 signals is only available if the signals are
enabled (ports) or cross connections have been configured (internal signals).
For a description of the individual PM menus see paragraph 8.5 Performance
monitoring (on page 100).
For the definition of terms and a detailed description of the generic aspects of
the FOX performance monitoring, refer to "1KHW002007 FOX Network func-
tions User Guide".
7.3.1 Setting the scope

The performance monitoring information is evaluated and stored in the unit itself
and therefore it is required to upload this information to get the counter values.
Select the UCST menu «Unit Configuration» – «Performance Monitoring…» to
access the performance monitoring information.
The PM dialogue opens as an empty window.
• In a first step click on the «Get Tree» button to display the available layers in
the «Location Selection Tree» field.
• Access the required layer by clicking on the layer name or the «+» sign in
front of the layer name. Clicking on the «+» sign displays all available subu-
nits of the corresponding layer.
• Select the required subunit by clicking on it.
• Any node in the tree, including the tree root (i.e. the unit’s name and slot)
can be selected.
• The «Location» field shows now the selected location. The location cannot
be changed in the «Location» field.
7.3.2 Selecting the result type and format

For the previously selected location the counter group, counter type, the interval
and the presentation format have to be selected.
• Groups
Select one of the available counter groups for the selected PM location.
• Type
According to the selected group select one of the available counter types:
− PM 15 minutes
Performance monitoring data with 15 minutes measuring intervals. Up to
96 intervals are available (= 24 hours). The results of the latest 96 inter-
vals are kept in the memory, the results of previous intervals are can-
celled.
The PM 15min data are available on subunit level only.
The PM counts and ratios cannot be reset.
− PM 24 hours
Performance monitoring data with 24 hours measuring intervals. Up to 7
intervals are available (= 1 week). The results of the latest 7 intervals are
kept in memory; the results of previous intervals are cancelled.
ABB ETER1 551 63

7
The PM 24h data are available on subunit level only.

The PM counts and ratios cannot be reset.
− Counter
Continuous sum of the performance monitoring parameters without using
an interval.
The PM counts and ratios can be reset. The «Elapsed Time» column
shows the time of the current measurement (since the last reset).
• Intervals
Select the PM interval to be displayed:
− n intervals (n = 1 to 96) for the PM 15 minutes type
Show the PM data of the n latest intervals before the current interval.
− n intervals (n = 1 to 7) for the PM 24 hours type
Show the PM data of the n latest intervals before the current interval.
− Current
Show the PM data of the current interval (this selection is not available
with «Counter»).
− All
Show the PM data of all available intervals.
• Presentation
The ETER1 unit presents PM values in the «Events» format. The «Ratio»
format is not practical for packet oriented connections and thus not sup-
ported.
Ratio formatted PM results are however available for the underlying physical
TDM links from the corresponding transmission units, e.g. LOMIF.
64 ETER1 551 ABB

FAILURES, ALARMS AND NOTIFICATIONS
7.3.3 Interpreting and saving the results

The PM results for the selected location, group, type, interval and presentation
format are displayed in the «Counts» field after clicking on the «Get» button.
The «Start Time» is
• the start of the measuring period with «PM 15min» and «PM 24h» types, or
• the time of the last reset with the «Counter» type.
The «Elapsed Time» is
• the time from the start of the measuring period (the start time) to the actual
time with «PM 15min» and «PM 24h» types, or
• the time from the last reset (the start time) to the actual time with the «Coun-
ter» type.
The counters of type «Counter» can be reset by clicking on the «Reset» button.
Only the currently displayed results are reset.
The displayed results can be saved in an Excel-compatible file with .csv
(comma separated value) format by clicking on the «Save …» button.
Type the desired file name in the «File» – «Name» field, select the «;» or the
«TAB» as separator and then click on the «Save» button.
7.4 Failures, alarms and notifications

7.4.1 Front panel failure indications
The FOX alarm system processes failures. The failures are locally indicated via
the front panel LEDs of the unit and the alarm LEDs of the COBUX/COBUV (if
applicable).
The ETER1 provides LED indicators on the front panel. The LEDs are used to
indicate to the user the alarm status of the unit and of the network traffic signals.
The unit LED has the following states:
• Red: Failure
The unit is not in service due to an equipment failure or a mismatch between
hardware and software.
• Red/green blinking, 4 Hz: Booting
The unit embedded SW is starting up.
• Red/green blinking, 2 Hz: ESW reconfiguration
A new unit embedded SW is starting up.
• Red blinking, 1 Hz: Waiting
The unit has not been taken into service or has not been provisioned.
• Green: Running or reconfiguration
The unit is up and running and is ready to provide the required service, or
the unit is reconfigured.
• Dark: Failure
The unit is not powered.
The traffic LED has the following states:
• Red: Failure
One or more traffic failures are active on the unit, independent of the sever-
ity.
• Dark: Normal
Error free operation
ABB ETER1 551 65

MAINTENANCE
7
ETER1 R1A
ROFBU 367 610/1
Unit Traffic
Figure 37: Fault indication LEDs on the ETER1 unit
Please refer to "1KHW002059 FOX User Guide" (paragraph «Diagnostics,

Fault and Alarm Handling» for the definition of terms (Defects, Fault Causes,
Failures etc.) and details of the FOX fault handling and alarm system.
7.4.2 Failure tables in UCST

Depending the unit’s alarm configuration the active failures generate entries in
the NE fault list and in NE fault log book. For details see paragraph 8.4 Alarms
(on page 98).
7.5 Maintenance
There is no need to access any components on the ETER1 unit for mainte-
nance.
The following maintenance facilities are available (operation via the UCST/FOX-
MAN-UN):
• Inventory data
• Unit SW download
• Unit SW upgrade
7.5.1 Inventory data

It is possible to read inventory data from the ETER1 modules via the UCST/
FOXMAN-UN. For a description of the inventory function, refer to
"1KHW002059 FOX User Guide".
7.5.2 Unit ESW download

It is possible to remotely upgrade the ESW (local FW) of the ETER1 via soft-
ware download.
For the requirements and installation of the ESW on your PC/computer, refer to
"1KHW002060 UCST/System Operation Basics User Guide". Please refer to
"1KHW002059 FOX User Guide" for the description of the software download
procedure.
66 ETER1 551 ABB

MAINTENANCE
Please note:
Make sure the COBU<X> is equipped with a 16 MB flash prior to installing an
ETER1 unit, because the ETER1 ESW file is very large (> 7MB). Due to the
large ESW file, the upgrading of an ETER1 unit to a new ESW state takes
aproximately 10 minutes for the download and a similar amount of time for the
distribution from the COBUX unit to the ETER1 unit.
7.5.3 Upgrades
You can upgrade an existing ETER1 with newer functionality as described in
the new UCST release, if the new functional unit is compatible with your hard-
ware and you have the corresponding software licence. You can check the
compatibility between your hardware and the ESW via the FOX inventory func-
tion. Please refer to "1KHW002059 FOX User Guide" and for the correspond-
ing data in the FOX Release Notes refer to "1KHW002070 FOX UCST Release
Note R8C".
For detailed information on the upgrade procedures for the FOX control units
and traffic units, refer to "1KHW002059 FOX User Guide".
ABB ETER1 551 67

CONFIGURATION
8
8 UCST GUI Reference
8.1 Configuration
8.1.1 Board
8.1.1.1 Common settings
Table 24: Parameters for the «Common settings» menu

Column name Range Descriptions / Details
Mode 8 x 2Mbit/s» (Support of P0, P0nc This is the default unit mode and should be favoured for all
and P12 Transparent applications not needing the high PBUS bandwidth.
16 x 2Mbit/s» (Support of P0nc (n = The granularity for bandwidth selection on P0nc channels is two
2,4,6, … 32) and P12 Clock Master) 64kbit/s time slots and not one time slot as usual, i.e. only even
numbers of timeslots from n = 2 … 32 may be selected.
For details about relations between unit modes, TDM modes and timing config-
uration see 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s» (on page 33)
68 ETER1 551 ABB

CONFIGURATION
8.1.1.2 QoS
Table 25: Parameters for the «QoS» menu

Name QoS_Default The default mapping profile is always available from UCST
User defined profiles The user can create own mapping profiles in the «NE Con-
figuration» menu.
View...
802.1p Mapping – MAC tag PRI Q1 (lowest priority) MAC tag PRI 0 ... 7 is each mapped to one of the four TX
Q2 (low priority) queues
Q3 (high priority)
Q4 (highest priority)
DSCP Mapping – DSCP Q1 (lowest priority) DSCP 0 ... 63 is each mapped to one of the four TX queues
Q2 (lowest priority)
Q3 (high priority)
Q4 (highest priority)
Any mapping profile other than the default profile must first be created in the
«NE Configuration» menu before it can be used for the ETER1 unit.
For ETER1 specific QoS please refer to paragraph 5.9 QoS (on page 56)
For FOX515/512 profile handling please refer to "1KHW002059 FOX User
Guide".
ABB ETER1 551 69

CONFIGURATION
8
8.1.2 Interfaces
8.1.2.1 Ethernet phy
Table 26: Parameters for the «Ethernet phy» menu

Sbu Name «Eth-1» ... «Eth-4» Pre-defined by the system
Name 0 ... 16 characters User editable name for the port. Any printable character is
allowed. By default the name is empty.
State enabled/disabled Administrative state of the port, disabled by default. Disabled links
are not checked for alarms.
Assignment «Bridge-1» … «Bridge-8» Ethernet physical interfaces can be assigned to one of the eight
«Router» available bridge instances, to the router or can be left unassigned.
By default the assignment is set to «None», i.e. the interface is
«None» unassigned.
An unassigned Ethernet interface can still be used as physical
interface for a VLAN interface; see also paragraph 5.8 VLAN
Interfaces (on page 54).
LAN Mode «Auto Negotiation» With the LAN mode configuration an Ethernet port can be forced
«10Mbit/s Half Duplex» to work in a specific operation mode or allowing the port to select
the best mode automatically by negotiating with the appropriate
«10Mbit/s Full Duplex» peer entity. By default the LAN mode is set to «Auto Negotiation».
«100Mbit/s Half Duplex»
«100Mbit/s Full Duplex»
Ingress Rate Limiter enabled/disabled By default the ingress rate limiter is disabled, i.e. the correspond-
ing input bandwidth is 10Mbit/s or 100Mbit/s.
CIR Ingress [kbit/s] 64 kbit/s ... 100 Mbit/s The Commited Information Rate when limiting is enabled
CBS Ingress [kByte] 1 kB ... 256 kB The Committed Burst Size for the limitation process, which is
implemented as a token bucket rate policer. Received packets
with MTU size > CBS can not be forwarded and are dropped. 2 kB
is therefore the lowest value that should ever be set.
The ETER1 unit does not support flow control on its Ethernet interfaces.
70 ETER1 551 ABB

CONFIGURATION
8.1.2.2 TDM interfaces
Table 27: Parameters for the «TDM Interfaces» menu

Sbu Name «TDM Interface-1» ... Pre-defined by the system (static table)
«TDM Interface-64»
Protocol Port not used The port is not active (default)
Multilink PPP The port is a member link of a multilink bundle
PPP The standard WAN protocol for OSI layer 2 (link layer)
MAC/HDLC WAN protocol with direct MAC frame into HDLC encapsulation;
must be supported by the terminating peer entity
User Data Rate 64 kbit/s ... 2048 kbit/s The noted data rate in kbit/s corresponds to 1 ... 32 in numbers of
G.704 time slots. For «Unit Mode» = 8 x 2 Mbit/s the granularity for
selection is 64 kbit/s, for «Unit Mode» = 16x 2 Mbit/s the granular-
ity for selection is 128 kbit/s.
P12 (Transparent) Possible selection for «Unit Mode» = 8 x 2 Mbit/s
P12 (Clock Master) Possible selection for «Unit Mode» = 16 x 2 Mbit/s
Assignment «Bridge-1» … «Bridge-8» TDM interfaces can be assigned to one of the eight available
«Router» bridge instances, to the router or can be left unassigned. By
default the assignment is set to «None», i.e. the interface is unas-
«None» signed.
Multilink PPP Bundle «MLPPP-1» … The MLPPP member links must be assigned to one of the eight
«MLPPP-8» pre-defined multilink bundles.
Please be aware of the fact that the member links of MLPPP bun-
dles should be of the same bandwidth; see also paragraph 5.7.1
Bandwidth considerations for multilink PPP bundles (on page 53)
CAS AIS Supervision enabled/disabled AIS supervision is used as failure indication for the 1+1 Trail
(Path) protection function.
For a detailed description of signal protection please refer to 5.3.3
Protection for TDM WAN links (on page 34)
ABB ETER1 551 71

CONFIGURATION
8
8.1.2.3 Multilink PPP
Table 28: Parameters for the «Multilink PPP» menu

Sbu Name «Multilink PPP-1» ... Pre-defined by the system (static table)
«Multilink PPP-8»
Assignment «Bridge-1» … «Bridge-8» Multilink PPP interfaces can be assigned to one of the eight avail-
«Router» able bridge instances, to the router or can be left unassigned. By
default the assignment is set to «None», i.e. the interface is unas-
«None» signed.
Members List of all PPP links in the This menu item is intended for information only. Use the «TDM
MLPPP bundle Interfaces» menu in order to configure the MLPPP members.
72 ETER1 551 ABB

CONFIGURATION
8.1.2.4 VLAN interfaces
Table 29: Parameters for the «VLAN Interfaces» menu

Sbu Name «VLAN Interface-1» ... Pre-defined by the system (static table)
«VLAN Interface-32»
Interface Not in use The virtual interface is not used
«Eth-1» ... «Eth-4» The virtual interface is directly connected to an Ethernet port.
Physical Ethernet ports must be enabled and must not be con-
nected to a bridge in order to be available for VLAN interface con-
nection. The same Ethernet port can be connected to several
VLAN interfaces, each with a different VLAN ID.
«Bridge-1» … «Bridge-8» The virtual interface is connected to one of the bridge instances.
The same bridge instance can be connected to several VLAN
interfaces, each with a different VLAN ID.
VLAN ID 1 ... 4094 Only frames that match the configured VLAN ID are routed over
this interface.
Assignment «Router» Virtual interfaces are always assigned to the router. This column is
therefore included for informational purpose only.
For more information regarding the use of virtual interfaces see 5.8 VLAN Inter-
faces (on page 54)
ABB ETER1 551 73

CONFIGURATION
8
8.1.3 Bridges
8.1.3.1 Bridges
Table 30: Parameters for the «Bridges» menu

Sbu Name «Bridge-1» ... «Bridge-8» Pre-defined by the system (static table)
Name 0 ... 16 characters User editable name for the bridge. Any printable character is
Bridge Priority 0 ... 61440 selectable in The bridge with the lowest priority value is choosen as root bridge
multiples of 4096 in the RSTP negotiations process. Default value = 32768
Hello interval [s] 1 ... 10 * Time interval in seconds for BPDUs sent on each port that have
RSTP enabled. Default value = 2
Forwarding Delay [s] 4 ... 30 * Time interval in seconds spent in listening and learning states.
Default value = 15
Maximum Age [s] 6 ... 40 * The maximum lifetime controls the time (and range) that BPDU
information can be used for. This may need to be adjusted for
large networks. Default value = 20
Path Cost Version 802.1t (32 bits) ABB suggests using the 802.1t path cost version (default). Only
802.1D 1998 (16 for networks where the majority of the links are running with
speeds of 512 kbit/s or slower the 802.1D path cost version is rec-
ommended.
* UCST can restrict these ranges in order to maintain save relationships for
hello interval, forwarding delay and maximum age according to the IEEE
802.1w standard.
74 ETER1 551 ABB

CONFIGURATION
8.1.3.2 Bridge-n IF
Table 31: Parameters for the «Bridge-n IF» menu

Sbu Name Subunit names of The subunit names are composed of the corresponding interface’s
assigned bridge ports subunit name and the interface’s user editable name.
Port Type Access (default) Only untagged and priority tagged RX frames are accepted on an
access port and all TX frames are sent without a tag.
Trunk Only VLAN tagged RX frames with VID = 1 … 4094 are accepted
on trunk ports and all TX frames are sent VLAN tagged.
Trunk (Native VLAN) This is the hybrid port with both access and trunk properties:
- Both VLAN tagged and untagged RX frames are accepted.
- Untagged RX frames get a VLAN tag according to the «Port
VLAN ID» and priority tagged RX frames are assigned the VLAN
membership according to the «Port VLAN ID».
- TX frames are sent VLAN tagged, with the exception of frames
with a VLAN ID matching the value of «Port VLAN ID», which are
sent untagged.
Port VLAN ID 1 ... 4094 This parameter is not applicable for trunk ports.
Untagged or priority tagged RX frames received on the port will
get a VLAN tag with this VLAN ID. Default =1
For TX frames destined for access ports this parameter acts as a
filter: only frames with this VLAN ID are allowed to be transmitted.
Port Priority 0 ... 7 Untagged or priority tagged RX frames received on the port will
get this value in the priority field.
RSTP enabled/disabled RSTP can be enabled or disabled individually for each port.
Default = enabled. For a description of the RSTP functionality see
5.4.3 RSTP (on page 37).
Automatic Port Path Cost enabled/disabled By default ETER1 automatically calculates port path cost from the
Computation configured bandwidth, i.e. default = enabled.
Port Path Cost 1 ... 200’000’000 Port path cost can be entered here if above parameter is set to
manual entry.
Accessibility Public (default) Controls the port’s behaviour in case «Star topology bridging» is
Protected enabled, see 5.4.5 Star topology bridging (on page 38).
ABB ETER1 551 75

CONFIGURATION
8
8.1.4 IPv4 routing

8.1.4.1 Interfaces
8.1.4.1.1 Addressing
Table 32: Parameters for the «Addressing» menu

assigned router ports subunit name and the interface’s user editable name.
Mode Numbered The corresponding router interface has its own IPv4 address. The
«Numbered» selection is available for all interface types.
Numbered Peer * Used for PPP interfaces with no IP address exchange.
This selection is available for TDM WAN interfaces only.
IPv4 Address Any valid IPv4 address Both address and mask values are subject of correct IP network
IPv4 Mask Any valid IPv4 mask design. Whether a certain address/mask combination is valid for a
certain interface is in the responsibility of the user and cannot be
checked by the ETER1 unit or by the UCST.
IPv4 Peer Address Any valid IPv4 address IP address of peer router in case of «Numbered Peer» mode.
* This addressing mode must be used for TDM links between ETER1 and
LAWA4/LEMU6. Configure the addressing mode on the LAWA4 or LEMU6 as
«Numbered».
76 ETER1 551 ABB

CONFIGURATION
8.1.4.1.2 OSPF
Table 33: Parameters for the «OSPF» menu

Sbu Name Subunit names of assigned The subunit names are composed of the corresponding interface’s
router ports subunit name and the interface’s user editable name.
OSPF State enabled/disabled OSPF can be enabled or disabled individually for each router port.
Default = disabled
Mode Active (default) The usual mode to configure a OSPF router interface.
Passive No hello packets or LSA packets are sent or received on this inter-
face and no adjacencies can be built over this interface, but the
network that is connected to the interface is still advertised to the
AS.The passive mode is typically selected for connected networks
with no OSPF supporting routers.
Area Backbone The corresponding interface belongs to the selected area.
The backbone area is mandatory for an OSPF AS and is always
selectable.
Area-2 ... Area-7 Non-backbone areas are only selectable if they have previously
been created.
If the router has no connection to the backbone area, it must not
connect to more than one area.
Automatic Metric enabled/disabled By default, the metric is calculated automatically from the specified
interface bandwidth: metric = 100’000 / bandwidth in kbit/s
Interface Metric 1 ... 65535 The OSPF routing table calculations can be affected with manual
interface metrics. This feature should however be used by OSPF
experts only.
ABB ETER1 551 77

CONFIGURATION
8
Table 33: Parameters for the «OSPF» menu (continued)

Priority 0 ... 255 The priority value is used in the negotiations process in order the
Default = 128 select the designated router and the backup designated router.
With a priority value of «0», the router is ineligible to ever become
designated router on the attached network.
This parameter has no relevance for TDM interfaces.
Advanced Options
Authentication key Auth. = none: parameter n.a. The configuration of the authentication key for a certain interface
Auth. = Simple: max. 8 char. is depending on the selection for «Authentication» for the appro-
priate area.
Auth. = MD5: max. 16 char.
Hello interval [s] 1 ... 65535 Time interval for sending of hello packets on that interface. All
Default = 10 OSPF routers that are attached to the same network must agree
on the same hello interval.
Dead interval [s] 0 ... 3600 The time before a neighbouring router is declared down after after
Default = 40 missing the hello packets.
Transmit delay [s] 0 ... 3600 The time it takes to transmit a link state update packet over this
Default = 1 interface. LSAs contained in the update packet must have their
age incremented by this amount before transmission.
Retransmit delay [s] 0 ... 3600 Time interval between LSA retransmissions for adjacencies
Default = 5 belonging to this interface. Also used when retransmitting data-
base description and link state request packets.
8.1.4.1.3 RIP
Table 34: Parameters for the «RIP» menu

assigned router ports subunit name and the interface’s user editable name.
78 ETER1 551 ABB

CONFIGURATION
Table 34: Parameters for the «RIP» menu (continued)

RIP State enabled/disabled RIP can be enabled or disabled individually for each router port.
Default = disabled
Mode Active (default) The usual mode to configure a RIP router interface.
Passive No RIP protocol packets are sent or received on this interface, but
the network that is connected to the interface is still advertised on
active interfaces.
The passive mode is typically selected for networks with no RIP
supporting routers.
Authentication/Version None/RIPv1 Support of RIPv1 only, which implies no authentication support
None/RIPv2 Support of RIPv2 only, without authentication support
None/RIPv1&v2 Support of both RIPv1 and RIPv2, without authentication support
Simple/RIPv2 Support of RIPv2 only, authentication with plain text string
MD5/RIPv2 Support of RIPv2 only, authentication with MD5 hash
Authentication key 0 ... 16 characters User editable text string for authentication. Any printable character
is allowed. By default the string is empty.
Split horizon enabled/disabled Split horizon inhibits sending route information back to routers
from which it had previously been learned (default = enabled).
8.1.4.1.4 VRRP
Table 35: Parameters for the «VRRP» menu

Sbu Name All interfaces that sup- In order to support the virtual router function, the interface must be
port VRRP enabled, assigned to the router and must be either an Ethernet IF
or a VLAN IF that is connected to a bridge.
Parameter set A and B
<parameter> A The ETER1 can participate on one or two virtual routers over the
<parameter> B same interface. Therefore two identical parameter sets are provided
for each interface that supports VRRP.
VRRP State A enabled The ETER1 router participates over the corresponding interface on
a virtual router.
disabled The VRRP function is inactive on the corresponding interface.
ABB ETER1 551 79

CONFIGURATION
8
Table 35: Parameters for the «VRRP» menu (continued)

VRRP State B enabled The ETER1 router participates over the corresponding interface on
a second virtual router.
disabled The second virtual router is inactive on the corresponding interface
Virt. Router ID A/B 1 ... 255 Since several virtual routers can be active on the same LAN, each
default = 1 virtual router entity is identified with the virtual router ID.
Priority A/B 0 ... 255 The router with the highest priority is selected as master router from
default = 100 all active members of a virtual router entity.
Virt. IP Addr. A/B IP address in the net- The virtual IP address of the virtual router entity. All router members
work range of the corre- in the same virtual router entity (same virtual router ID) must use
sponding interface the same virtual IP address.
Advertise Interval A/B [s] 1 ... 255 The time interval in seconds each virtual router member sends
default = 1 advertisements. A virtual router member is considered as down
after 3 missing advertisements.
Preempt A/B enabled A higher priority backup router may preempt this router as master.
disabled Once elected as master, this router keeps running as master, even
a higher priority backup router is up and running again. Only a vir-
tual router address owner may still overrun disabled preemption.
8.1.4.2 Router
8.1.4.2.1 Static routes
Table 36: Parameters for the «Static Routes» menu

Index 1 ... 128 This value is automatically created by the system and identifies
the route entry in the dynamic list.
Destination Any valid IP network The destination/mask pair unambiguously identifies an IP address
Mask address/network mask range, where the corresponding static route is pointing to. The
combination default destination 0.0.0.0/0.0.0.0 contains the whole IP address
range.
Gateway valid IP address Any IP address in a directly connected network can be specified
as gateway address for a static route.
80 ETER1 551 ABB

CONFIGURATION
8.1.4.2.2 OSPF
Table 37: Parameters for the «OSPF – Areas definition» menu

Areas definition
Index 1 ... 8 This value is automatically created by the system and identifies the
area entry in the dynamic list.
Area Name «Backbone» The backbone area is mandatory for an OSPF AS. The area with
index = 1, area name = backbone, areaID = 0.0.0.0 and mode =
normal is created by the system and can not be edited by the user.
0 ... 16 characters User editable text string for areas 2 ... 8. Any printable character is
allowed. By default the strings are set to «Area-2» ... «Area-8».
AreaID The full IP address range The standard practise is using the area’s lowest network address as
area ID, but in fact the ID is selectable without relation to real
addresses.
Mode normal (default) The standard OSPF area type without restrictions
Stub OSPF AS external routes are not distributed to stub areas; these
destinations can be reached upon a default route via an area border
router. Stub areas must therefore not contain AS external routes.
If in doubt about the exact behaviour of a stub area please don’t use
this feature and use the default area mode instead.
NSSA As for stub areas, AS external destinations can only be reached
using a summary route via an area border router. But unlike stub
areas, NSSA areas may contain AS external routes.
If in doubt about the exact behaviour of a the NSSA please don’t
use this feature and use the default area mode instead.
All OSPF routers in an area must agree on the same area mode
Stub Cost If the stub area has more than one area border router, the route cal-
culation of all routers in the stub areas can be guided with the
advertised stub cost. Meaningful for border routers only.
ABB ETER1 551 81

CONFIGURATION
8
Table 37: Parameters for the «OSPF – Areas definition» menu (continued)
Authentication none No authentication is used in OSPF hello- and LSA-packets
simple Authentication with a plain text string is used in OSPF hello- and
LSA-packets
MD5 Authentication with a MD5 hash is used in OSPF hello- and LSA-
packets.
All OSPF routers in an area must agree on the same authentication mode
Area address ranges
Index 1 ... 16 This value is automatically created by the system and identifies the
address range entry in the dynamic list.
Address Any valid IP network The address/mask pair unambiguously identifies an IP address
Mask address/network mask range. The specified address ranges must not overlap.
combination
Advertising enabled The corresponding address range is advertised throughout the AS.
disabled The corresponding address range is not advertised, it is therefore a
hidden address range.
8.1.4.2.3 Redistribution
Table 38: Parameters for the «Redistribution» menu

OSPF (Direction RIP --> OSPF)
Source Connected A network is directly connected via a router interface, but the connect-
ing interface is not enabled for OSPF
Static All static routes that are defined on the router
RIP All routes that the router has learned from RIP
State enabled The corresponding route information is advertised to the OSPF AS
disabled The corresponding route information is not advertised
Import metric 0 ... 65535 Value used as metric in the LSA for advertising the corresponding
route information
82 ETER1 551 ABB

PARAMETER BROWSER
Table 38: Parameters for the «Redistribution» menu (continued)

RIP (Direction OSPF --> RIP)
Source Connected A network is directly connected via a router interface, but the connect-
ing interface is not enabled for RIP
Static All static routes that are defined on the router
OSPF All routes that the router has learned from OSPF
State enabled The corresponding route information is advertised to the RIP neigh-
bours
disabled The corresponding route information is not advertised
Import metric 0 ... 15 Value used as metric for the corresponding destinations
8.2 Parameter browser

The UCST parameter browser allows for a quick parameter view on a config-
ured unit. Identical parameter values are displayed as in the configuration
menu, but in a view only manner and with a different layout.
ABB ETER1 551 83

STATUS/MAINTENANCE
8
8.3 Status/Maintenance
8.3.1 Board
8.3.1.1 Maintenance
Table 39: Parameters for the «Maintenance» menu

Group name Column name Range Descriptions / Details
Logbooks... Get logbooks Command button for displaying the logbook selection
Available logbooks Unit alert/error log: The logbooks are included mainly for debug purposes
Unit console trace log: in case of possible operating problems. In such situa-
tions it permits ABB’s customer support a deep view
Syslog(/var/log/mes- into the ETER1 unit by analysing collected contents of
sages) logbooks.
Kernel log (dmesg)
Get Read the corresponding logbook data from the unit in
the contents buffer
Clear Erase the contents buffer and window
Print The contents buffer is printed. The print sub-menu
allows for printer selection and configuration.
Please note the file output option as a convenient way
of making logbook contents remotely available for
ABB’s customer support.
Close The unit logbook window is closed
Restart The ETER1 unit is restarted when the issued warning is
acknowledged with «Yes».
CLI... The CLI option is intended for internal use only.
84 ETER1 551 ABB

STATUS/MAINTENANCE
8.3.2 Interfaces
8.3.2.1 Ethernet Phy
Table 40: The «Ethernet Phy» status menu

SbU name The pre-defined name plus the user editable string
State enabled/disabled The administrative interface state; no further status information is
displayed for disabled interfaces.
Link state Up The interface is logically up and running
Down The interface is logically down or disconnected
LAN mode «10Mbit/s Half Duplex» The state of the active Ethernet interface (Link state = up) either as
«10Mbit/s Full Duplex» a result of the auto negotiation process or from the explicit user con-
figuration
«100Mbit/s Half Duplex»
«100Mbit/s Full Duplex»
«Unknown» LAN mode in case the link state is down
MAC address The MAC address that is allocated to the physical interface
ABB ETER1 551 85

STATUS/MAINTENANCE
8
8.3.2.2 TDM interface
Table 41: The «TDM Interface» status menu

SbU name TDM Interface-1 ... TDM The pre-defined subunit name plus the user editable string
Interface-64 All rows for subunits configured as «Port Not Used» are empty.
State enabled/disabled The administrative interface state
Down The interface is logically down or disconnected (layer 2)
8.3.2.3 Multilink PPP
Table 42: The «Multilink PPP» status menu

SbU name TDM Interface-1 ... TDM The pre-defined subunit name plus the user editable string
Interface-64 All rows for subunits configured as «Port Not Used» are empty.
State enabled/disabled The administrative interface state
Down The interface is logically down or disconnected (layer 2)
86 ETER1 551 ABB

STATUS/MAINTENANCE
Table 42: The «Multilink PPP» status menu (continued)

Up/Total Members This column displays both the number of active members and the
number of totally configured members for the corresponding multi-
link PPP interface.
8.3.3 Bridges
8.3.3.1 Bridges
Table 43: The «Bridges» status menu

Column name Range / Case Descriptions / Details
SbU Name Bridge-1 ... Bridge-8 The pre-defined subunit name plus the user editable string
Local Bridge Priority 0 ... 61’440 The bridge with the lowest priority value is choosen as root
bridge in the RSTP negotiations process.
Local Bridge MAC Address The eight bridge instances on the ETER1 unit all have their
own MAC address for unambiguous identification.
Root Bridge Priority 0 ... 65535 The root bridge can be the local ETER1 unit, another ETER1
Root Bridge MAC Address unit or some third party equipment
Root Bridge Hello Interval [s] All RSTP bridges in a contigous network should use the same
value for the hello interval.
Root Bridge Forwarding Delay [s] Typically all RSTP bridges in a contigous network should use
the same value for the forwarding delay. Newer use a longer
forwarding delay than the route bridge.
Root Bridge Maximum Age [s] Typically all RSTP bridges in a contigous network should use
the same value for the maximum age. Newer use a bigger
maximum age than the route bridge.
Root Path Cost cost from the local bridge to the root bridge
MAC Addresses
MAC Address This MAC address was detected as source address in a
received frame
VLAN ID Access port The configured port VLAN ID
Trunk port The VLAN ID in the received frame
ABB ETER1 551 87

STATUS/MAINTENANCE
8
Table 43: The «Bridges» status menu (continued)

Column name Range / Case Descriptions / Details
Ingress Port Port, where the corresponding MAC frame was received
8.3.3.2 Bridge-n IF
Table 44: The «Bridge-n IF» status menu

SbU Name Eth-1 ... -4 Any Ethernet interface that is assigned to the corresponding bridge
TDM Interface-1 ... -64 Any TDM interface that is assigned to the corresponding bridge
Multilink PPP-1 ... -8 Any MLPPP interface that is assigned to the corresponding bridge
RSTP enabled RSTP is enabled on the corresponding port
disabled RSTP is disabled on the corresponding port
RSTP Oper State * Learning Transient state during topology changes for root ports and desig-
nated ports; no user traffic forwarding
Forwarding This port is part of the active topology and forwards user traffic in
both directions
Blocking This port is not part of the active topology and blocks user traffic in
both directions; this state is also called «discarding»
RSTP Role * Root This port has the best connection (in terms of path cost) to the root
bridge
Designated A forwarding port that connects to a LAN segment down from the
root
Alternate An alternative connection to the root bridge
Backup An alternative connection to a LAN segment, where another port (in
role «Designated») already connects to
Disabled Transient state during the initialization process; no user data is for-
warded on the port
RSTP Designated The RSTP Designated Bridge in respect to a port denotes the
Bridge Priority bridge on the other side of the point-to-point link or the designated
RSTP designated bridge on the LAN segment.
Bridge MAC Address
Edge Port No RSTP peer bridge attached on this port
Point to Point Link The port is connected by a point-to-point LAN segment to exactly
one other bridge.
88 ETER1 551 ABB

STATUS/MAINTENANCE
Table 44: The «Bridge-n IF» status menu (continued)

Effective Port Path Cost The port path cost is calculated from the port bandwidth and is
dependent on the configured path cost version.
* In a bridged LAN whose RSTP information has been completely distributed

and is stable, i.e., consistent port roles have been assigned throughout the
LAN, every root port and designated port is in forwarding state and every alter-
nate port and backup port is in discarding state.
8.3.4 IPv4 routing

8.3.4.1 Interfaces
8.3.4.1.1 General
Table 45: Status menu for «General»

SbU Name Eth-1 ... -4 Any Ethernet interface that is assigned to the router
TDM Interface-1 ... -64 Any TDM interface that is assigned to the router
Multilink PPP-1 ... -8 Any MLPPP interface that is assigned to the router
VLAN Interface-1 ... -32 Any VLAN interface (VLAN I/Fs are always assigned to the router)
Loopback The routers identification
IP MTU Maximal size of transmission unit
IP Address IP address as configured on the unit
Operational State Up/Down This status corresponds to the «Link State» in the «Interfaces»
menu
ABB ETER1 551 89

STATUS/MAINTENANCE
8
8.3.4.1.2 OSPF
Table 46: Status menu for «OSPF»

SbU Name Eth-1 ... -4 Any interface that is assigned to the router and is activated for
TDM Interface-1 ... -64 the OSPF function
Multilink PPP-1 ... -8

VLAN Interface-1 ... -32
Loopback
OSPF Status Designated router This router is advertising the connected Ethernet network
Backup designated router This router is elected as backup for the advertising of the con-
nected Ethernet network
Other designated router This router is neither designated router nor backup designated
router
Point-to-point There is no designated router on point-to-point links (TDM I/F)
Loopback No status information for the loopback I/F
Down OSPF status is «Down» when the layer 2 link is down
OSPF Des. Router The currently active designated router on the connected network
OSPF Backup Des. Router The currently active backup designated router on the network
90 ETER1 551 ABB

STATUS/MAINTENANCE
8.3.4.1.3 VRRP
Table 47: Status menu for «VRRP»

SbU Name Eth-1 ... -4 Any Ethernet interface that is assigned to the router
VLAN Interface-1 ... -32
Loopback There is no VRRP status information for the loopback I/F
Virt. MAC Addr. A MAC address of the virtual router if this interface is the VRRP master.
If this interface is VRRP backup, the displayed value is meaningless.
Oper. State A Master The ETER1 unit acts as master for the corresponding virtual router
Backup The ETER1 unit acts as backup for the corresponding virtual router
Up Time A [s] Time in seconds since the corresponding virtual router is up
Virt. MAC Addr. B The ETER1 unit can participate on two virtual routers, VR A and VR B.
Oper. State B All status information is therefore available for both VR A and VR B.
Up Time B[s]
ABB ETER1 551 91

STATUS/MAINTENANCE
8
8.3.4.2 Router
8.3.4.2.1 Routing Table
Table 48: Status menu for «Routing Table»

Destination Any valid IP network The destination/mask pair unambiguously identifies an IP address
Mask address/network mask range, where the corresponding route is pointing to.
combination
Gateway Valid IP address IP address of the next router’s interface. This is the address, where
all packets for the destination in the corresponding table entry are
sent to.
Router Interface Any local router interface Interface, over which a network is connected to, in case of
in operational up state «Source» = «Connected»
Source Connected The route information is derived from a directly connected interface.
Static The route information is derived from a static route entry on the
local router.
OSPF Any route information that is calculated from the OSPF link state
database and the OSPF external link state database
RIP Any route information that is learned from RIP neighbours
92 ETER1 551 ABB

STATUS/MAINTENANCE
8.3.4.2.2 ARP Table
Table 49: Status menu for «ARP Table»

IPv4 Address IP address in the corre- An IP address of a device that is directly connected via Ethernet
sponding subnet to the local router
MAC Address Any valid MAC address MAC address that belongs to the IP address in the corresponding
table entry
Router Interface Any local router interface The IPv4/MAC address pair is connected over this interface
in operational up state
8.3.4.2.3 OSPF – Area
ABB ETER1 551 93

STATUS/MAINTENANCE
8
Table 50: Status menu for «OSPF – Area»

SbU Name Backbone The area name
User defined name
Nb of Area Border Routers Routers in the area that connect to other areas in the AS
Nb of AS Routers Total number of AS border routers, i.e. routers that connect to
external destinations.
Nb of Link State Advertise- Corresponding to the number of entries in the Link State Data-
ments base (see table below)
Area LSA Checksum The checksum can be used to quickly detect LSA changes
8.3.4.2.4 OSPF – Link State Database
Table 51: Status menu for «OSPF – Link State Database»

Are Id ID of one of the active areas in the AS
LSA Type Router The collected states of a router's interfaces
Network Describe the set of routers attached to the network
Summary Summaries are advertised by area border routers and describe
inter-area routes.
Link Id either a router identifier or an IP route in the AS
Router Id ID of the OSPF router that has advertised the list item
Sequence Continuously counting up, in order to prevent listing the same item
twice
94 ETER1 551 ABB

STATUS/MAINTENANCE
Table 51: Status menu for «OSPF – Link State Database» (continued)
Age Age of the corresponding advertisement in seconds
Checksum The checksum can be used to quickly detect LSA changes
8.3.4.2.5 OSPF – External Link State Database
Table 52: Status menu for «OSPF – External Link State Database»
Link Id Network address of the corresponding destination
Router Id ID of the OSPF router that is advertising the external destination
Sequence Continuously counting up, in order to prevent listing the same item
twice
Age Age of the corresponding advertisement in seconds
Gateway How the external destination can be reached
Router Interface
ABB ETER1 551 95

STATUS/MAINTENANCE
8
8.3.4.2.6 OSPF – Neighbours Table
Table 53: Status menu for «OSPF – Neighbours Table»

Neighbour Id The neighbour’s router OSPF Id
Priority Priority used for the designated router election
State Init Hello packets received from the neighbour, but bidirectional com-
munication has not yet been established
Two ways Communication with the neighbour has fully been established, but
no adjacency has been built. Obviously the local router is not desig-
nated nor backup designated router on the corresponding Ethernet
subnet. See also 8.3.4.1.2 OSPF (on page 90)
This state should never appear on TDM interfaces.
Full If the router is elected as designated or backup designated router it
will establish full adjacency to all OSPF routers on the Ethernet sub-
net.
Source The router’s IP address on the corresponding interface
96 ETER1 551 ABB

STATUS/MAINTENANCE
8.3.4.2.7 RIP
Table 54: Status menu for «RIP»

Network Any valid IP network This IP address range as specification for a learned route informa-
Mask address/network mask tion
combination
Metric 1 ... 15 standard RIP metric range; 16 = end of network
From Directly Connected The network is connected to the local RIP router
<IP address value> IP address of next hop router
8.3.4.2.8 Ping
ABB ETER1 551 97

ALARMS
8
Table 55: Status menu for «Ping»

Request
Destination IPv4 Address Ping target
Number of requests 1 ... 10 Number of ping requests to be executed
Packet size 28 ... 65535 IP datagram packet size for the ping request
Fragmenting enabled The do-not-fragment bit is cleared in the IP header
disabled The do-not-fragment bit is set in the IP header
Response
Result of the ping request
8.3.4.2.9 Traceroute
Table 56: Status menu for «Traceroute»

Request/Destination Target IP address
IPv4 Address
Response Trace result
8.4 Alarms
8.4.1 General alarm configuration
The ETER1 unit supports alarms on various layers:
• Board
• Interfaces
− Ethernet physical interfaces
− TDM interfaces
− Multilink ppp interfaces
Though each layer contains different fault causes, the configurable parameters
are the same for all layers. The screenshot below is from the TDM interfaces
menu, but the descriptions are valid for all alarm layers.
98 ETER1 551 ABB

ALARMS
Table 57: Parameters for the «Alarms - Board» menu

Fault Cause See individual alarm layer descriptions below
Report Option Monitored The corresponding alarm is contained in the units faults list
Not monitored The corresponding alarm is not contained in the units faults list
Severity Urgent (UA) The corresponding alarm is considered as urgent
Non Urgent (NA) The corresponding alarm is considered as not urgent
Log Book Only The corresponding alarm is contained in the alarm log book but
not in the faults list
Persist Time [s] Trapped Even very short occurrences of the corresponding fault will gener-
ate an entry in the alarm log book
0.1 second ... 30 seconds Alarm durations below the configured value will not trigger the cor-
responding alarm and are thus filtered
Absent Time [s] 0.2 second ... 30 seconds The alarm condition is cleared after the corresponding fault is
absent for the configured time
Subunit All The configured parameters are valid for all subunits of the corre-
sponding interface type
Static list of subunits The configured parameters are valid for the selected subunit only
These buttons serve for the same function as the above described
«Report Option» but they are valid for all fault causes of the
selected layer or the selected subunit.
8.4.2 Individual fault cause descriptions

Table 58: ETER1 fault causes
Layer Fault cause Descriptions / Details
Board Unit Not Available The unit is not plugged or does not respond the polls from the con-
(no sublayer, no subunits) trol unit. Furthermore the unit can itself activate this alarm with the
built in self test or by detecting a HW/SW mismatch.
Equipment failure A hardware failure has been detected by the control unit
Router Configuration The current router or bridge configuration is not persistent – any
Error networking function is thus ceased
Interfaces
Sublayer: Ethernet Phy Link down This alarm is a summary for both OSI layers 1 and 2.
Subunits: 1 ... 4
ABB ETER1 551 99

8
Table 58: ETER1 fault causes (continued)

Layer Fault cause Descriptions / Details
Sublayer: TDM Interfaces PPP Link Down The ppp link is not established (OSI layer 2)
Subunits: 1 ... 64 Working Signal Failure The working path of a TDM link with 1+1 protection is down
Protecting Signal Failure The protecting path of a TDM link with 1+1 protection is down
Sublayer: Multilink PPP MLPPP Link Down The multilink ppp is not established (OSI layer 2)
Subunits: 1 ... 8 MLPPP Reduced Capac- The multilink ppp is up, but not all configured member links are
ity available
8.5 Performance monitoring

The ETER1 unit supports the standard FOX performance monitoring:
8.5.1 Location selection tree

The location selection tree serves as navigation map trough the physical and
logical interface structure of the unit. The PM counters are located at the tree
leafs and at the tree nodes. See also Figure 36: Location selection tree for PM
(on page 62) for an overview of counter locations.
100 ETER1 551 ABB

8.5.2 Counter selection
Table 59:PM counter selection

Menu Name Descriptions / Details
Groups The selection choice is depending of the selected loca-
tion.
Type On tree nodes, only the user counter «Counter» is
available and on tree leafs PM data in interval struc-
tured format is available with «PM 15min» and «PM
24h»
Intervals Allows selective display of intervals of interest.
Presentation The current ETER1 release supports presentation in
«Events» format only.
After the counter selection the «Get» button must be activated in order to fetch
the PM data from the unit and display it on the UCST screen.
ABB ETER1 551 101

8
102 ETER1 551 ABB

Contact us
Printed in Switzerland (1102-0000-0)

ABB Switzerland Ltd
Power Systems
Bruggerstrasse 72
5400 Baden
Tel.: +41 58 585 77 44
+41 58 585 55 77
E-mail: utility.communication@ch.abb.com
www.abb.com/utilitycommunication

1KHW002077 Abb Eter1 R2 Ug

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1KHW002077 Abb Eter1 R2 Ug

Uploaded by

Copyright:

Available Formats

ABB Power Systems

Copyright and confidentiality: Copyright in this document vests in ABB LTD. 

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHW002077

ABB ETER1 551 3

4 ETER1 551 ABB

7 Operation and Maintenance 61

8 UCST GUI Reference 68

ABB ETER1 551 5

6 ETER1 551 ABB

Figure 1: Functional block diagram 14

ABB ETER1 551 7

8 ETER1 551 ABB

Table 1: Electrical interfaces and circuit categories 12

ABB ETER1 551 9

Table 45: Status menu for «General» 89

10 ETER1 551 ABB

1.1 Precautions and safety

Hazardous voltages. Risk of electric shock!

Hazardous electric currents. Risk of flashover and electric shock!

Electrostatic discharges. Risk of equipment damage!

Attention to temperature range!

ABB ETER1 551 11

Attention to proper earthing!

Attention to access control!

Table 1: Electrical interfaces and circuit categories

1.2 Associated FOX515/512 documents

1KHW002070 FOX UCST Release Note R8C

1KHW002006 FOX System Specification User Guide

1KHW002001 FOX TDM System and Cross Connections User Guide

1KHW002013 COBUX 212, 213 & COBUV 217, 218

1KHW002003 FOX515 Installation Guide

1KHW002059 FOX User Guide

1KHW002004 FOX512 Installation Guide

1KHW002060 UCST/System Operation Basics User Guide

1KHW002007 FOX Network functions User Guide

1KHW002074 FOX515 Open source software declaration

12 ETER1 551 ABB

1.3 About this document

1.4 Document history

Table 2: Document history

1.5 Symbols and notations

Indicates a possibly hazardous context. The possible hazard is indi-

ABB ETER1 551 13

2.1 Definition of terms

Figure 1: Functional block diagram

• Functions of the Ethernet LAN interfaces

14 ETER1 551 ABB

• Functions of the virtual interface

2.2.2 Physical interfaces

Table 4: PBUS ports (backplane)

ABB ETER1 551 15

Table 4: PBUS ports (backplane) (continued)

2.2.3 Logical interface functions

Table 6: Parameters for virtual interfaces

2.2.4 Networking functions

16 ETER1 551 ABB

Table 7: OSI layer 2 data forwarding (bridging) (continued)

Table 8: OSI layer 3 data forwarding (routing)

ABB ETER1 551 17

Table 9: OSPF (continued)

Table 10: RIP

Table 11: VRRP; two virtual routers, A and B