ABB Power Systems

FOX61x
EPSI1
User Manual
User Manual FOX61x
EPSI1

Release History: Release 1: December 2012

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.: 1KHW002475

ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 2012 by ABB Switzerland Ltd
Table of Contents

1 Preface 7
1.1 Precautions and safety 7
1.2 Interfaces and circuit categories 7
1.3 Document history 7
1.4 Symbols and notations 7
1.5 Definition of terms 8

2 Introduction 9
2.1 Functions and features overview 9
2.2 EPSI1 architectural block diagram 10
2.3 Unit view 12

3 Specification 15
3.1 Feature licences 15
3.2 Physical interfaces 15
3.3 Logical interface functions 16
3.4 Networking functions 17
3.5 Protection 19
3.6 Environment 20
3.7 Summary of standards 21

4 Installation 23
4.1 Prerequisites 23
4.2 Slots for the EPSI1 unit 23
4.3 Connections and Cables 24
4.4 Fixing the cables to the cable tray 26

5 Functional Description 27
5.1 Overview 27
5.2 Ethernet LAN interfaces 28
5.3 TDM WAN interfaces (PBUS connections) 28
5.4 Bridging functions 32
5.5 Routing functions 38
5.6 Interface stacks 48
5.7 Multilink PPP interface 54
5.8 VLAN Interfaces 55
5.9 QoS 58

EPSI1User Manual 3
6 Commissioning 61
6.1 The managed objects tree 61
6.2 Commissioning steps 62

7 Operation and Maintenance 63

7.1 General operation recommendations 63
7.2 Status information and maintenance functions 64
7.3 Performance monitoring 65
7.4 Failures, alarms and notifications 66
7.5 Maintenance 67

8 GUI Reference 69
8.1 Introduction 70
8.2 unit-x: EPSI1 71
8.3 /unit-x/bridges 75
8.4 /unit-x/bridges/bridge-y 75
8.5 /unit-x/InternalPorts 78
8.6 /unit-x/InternalPorts/port-1 78
8.7 /unit-x/loppbackInterface 92
8.8 /unit-x/port-r 96
8.9 /unit-x/router 104
8.10 /unit-x/router/ospf 111
8.11 /unit-x/router/ospf/area-s 113
8.12 /unit-x/router/rip 116
8.13 /unit-x/tdmInterface 117
8.14 /unit-x/tdmInterfaces/machdlc-t 119
8.15 /unit-x/tdmInterface/mlppp-u 126
8.16 /unit-x/tdmInterface/mlppp-u/member-v 130
8.17 /unit-x/tdmInterface/ppp-w 131
8.18 /unit-x/vlanInterfaces 135
8.19 /unit-x/vlanInterfaces/vif-z 137

9 Annex 139
9.1 Associated FOX documents 139

4 EPSI1User Manual
Figures

Figure 1: Functional block diagram 9

Figure 2: EPSI1 architectural block diagram 10
Figure 3: EPSI1 unit view 13
Figure 4: EPSI1 front view with RJ-45 pin assignment 24
Figure 5: Ethernet link LEDs on the EPSI1 unit 25
Figure 6: Side view of the FOX615 cable tray and cable 26
Figure 7: The port based VLAN model (802.1Q, Annex D) 32
Figure 8: Possible inconsistencies in VLAN tagged bridged networks 33
Figure 9: Example bridged network with meshed topography 34
Figure 10: Active tree topology of the same network 34
Figure 11: Example application with multiple bridge instances 35
Figure 12: Example star bridging application 36
Figure 13: Interconnecting networks 38
Figure 14: Redistribution of static routes 39
Figure 15: Redistribution example 42
Figure 16: IP host connected to redundant gateway routers 43
Figure 17: IP host logically connected to a virtual router 43
Figure 18: VRRP application with load sharing 45
Figure 19: Setup for a redundant connection 46
Figure 20: Connectivity test with a broken link 47
Figure 21: Undetected network interruption 47
Figure 22: Generic stack model 48
Figure 23: Omitted encapsulation type 49
Figure 24: Connection of DTM-M to 3rd party bridge 49
Figure 25: Stack details for EPSI1 bridging applications 50
Figure 26: Stack details for EPSI1 bridging applications (continued) 51
Figure 27: Stack details for EPSI1 routing applications 53
Figure 28: Block diagram and stacks for multilink PPP 54
Figure 29: Connecting Ethernet LAN interfaces to the router 55
Figure 30: Connecting TDM WAN interfaces to the router 56
Figure 31: Inter-VLAN routing 57
Figure 32: Selective VLAN routing for tagged and untagged frames 57
Figure 33: The VLAN interface connects between bridging and routing 58
Figure 34: Frame handling for QoS in EPSI1 59
Figure 35: Managed objects tree for EPSI1 61
Figure 36: Status tree 64
Figure 37: Performance management tree 65
Figure 38: Fault indication LEDs on the EPSI1 unit 66
Figure 39: Fault management tree 67

EPSI1User Manual 5
6 EPSI1User Manual
 PREFACE

1 Preface
1.1 Precautions and safety

Before you handle any unit of the type EPSI1 you must comply with the fol-
lowing safety advices. For the applicable safety advices refer to
1KHW002497 FOX61x Precautions and Safety.

1.2 Symbols and notations

This user manual uses the following symbols:

NOTICE Non-observance could result in equipment damage.

A further description is added to describe the details of the hazard.
→ Possible actions are given as in this section.

Please note:
Shows a significant information.

Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
→ Possible actions are given.

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

EPSI1 interface Circuit category according Max. rating
to EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC <2A
ITU-T G.703 electrical inter- SELV <3.3 Vpeak < 10 mA
faces
Electrical Ethernet SELV <3V < 10 mA
10/100Base-TX

EPSI1User Manual 7
PREFACE

1.4 Document history

Table 2: Document history

Date FOX Changes since previous version
Release
December 2012 R1 First release

1.5 Definition of terms

For an explanation of terms used in this document please refer to

"1KHW028514 FOX61x Terms and Abbreviations".

8 EPSI1User Manual
 INTRODUCTION

2 Introduction
2.1 Functions and features overview

The EPSI1 is a versatile networking unit with the main purpose of connecting
Ethernet LANs over TDM links. Therefore the EPSI1 supports a variety of
powerful functions and features.

Internal 1 Gbit/s
Ethernet port
router
CTP (backplane ):

virtual up to 64 P0nc/P12x
4 Front ports :
interfaces TDM WAN interfaces ,
Ethernet LAN with a total bandwidth
interfaces of 16 x 2 Mbit/s
10/100Base-T

bridge

Figure 1: Functional block diagram

• Functions of the internal port

− 1+1 protected connection to the CESMx via backplane
− 1 Gbit/s
• Functions of the external Ethernet LAN interfaces
− Four Ethernet interfaces located on the front panel
− 10/100Base-TX
• Functions of the TDM WAN interfaces
− Up to 64 PBUS individual interfaces
− Total bandwidth 8 x 2 Mbit/s or 16 x 2 Mbit/s depending on unit mode
− PPP/HDLC user configurable
− Multilink PPP
• 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

EPSI1User Manual 9
INTRODUCTION

− VRRP, the virtual router protocol

• QoS functions
− 4 TX queues per interface
− Strict priority scheduling

2.2 EPSI1 architectural block diagram

CESM1 with backplane Ethernet star

EPSI1 GbE PHYs

serial
8 x 2/4Mbit/s
8/16 x
4x Fast 2Mbit/s
Ethernet Network PBUS
processor access PBUS
Fast
Ethernet
PHYs
primary
power
SD input
RAM Power supply

Figure 2: EPSI1 architectural block diagram

• Network processor
The network processor is the heart of the unit. It provides packet for-
warding for bridging and routing and also handles control protocols and
management functions.
• Fast Ethernet PHYs
The physical Ethernet driver chips are responsible for implementing the
CSMA/CD protocol according to the IEEE 802.3 standard.
• GbE PHYs
Circuit adaptation to the NE internal Gigabit Ethernet backplane star.
• 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:
− For «TDM Access» = «8 x 2 Mbit/s» the EPSI1 behaviour follows the
standard FOX PBUS specification. It allows for P0nc connections
(n = 1 … 32) and P12x (transparent) connections.
− For «TDM Access» = «16 x 2 Mbit/s» the EPSI1 deserves great care
for the NEs clock synchronisation. For details see section 5.3.2 Unit

10 EPSI1User Manual
 INTRODUCTION

mode «8 x 2Mbit/s» versus «16 x 2Mbit/s» (on page 29). The connec-
tion types are P0nc (n = 2, 4, 6 … 32) and P12 (Clock master).
• SDRAM
The fast volatile memory serves for the network processor’s own use
and holds all the data queues and various tables for data forwarding.
• Power supply
The EPSI1 unit draws its power exclusively from the un-stabilised pri-
mary power. The power supply provides the classic +5 V and several
lower voltages according to the boards need.
All secondary voltages are ramped up and down in a controlled way.

EPSI1User Manual 11
INTRODUCTION

2.3 Unit view

Fixing screw

EPSI1 R1A Pull-out handle with sticker

Unit LED

Traffic LED

Ethernet 10/100BASE-T port 4

Ethernet 10/100BASE-T port 3

Ethernet 10/100BASE-T port 2

Ethernet 10/100BASE-T port 1

Pull-out handle

Fixing screw

12 EPSI1User Manual
 INTRODUCTION

Figure 3: EPSI1 unit view

EPSI1User Manual 13
INTRODUCTION

14 EPSI1User Manual
 SPECIFICATION

3 Specification
3.1 Feature licences

This unit is subject to one or several feature licences. The following licences
are available for this unit.

Table 3: Functions and features overview relevant for this unit

Licence ID Short Description Description
EPSI1-L3OPT EPSI1 FOX Feature Licence for OSPF Routing functionality with EPSI1

3.2 Physical interfaces

Table 4: Internal Ethernet port (backplane)

Function Description/Range Standard
Not user configurable parameters
Physical mode 1000Mbit/s full duplex
User configurable parameters
Administrative state enable/disable
Ingress rate limiter enabled/disabled
committed information rate
committed burst size

Table 5: Ethernet ports on the front panel

Function Description/Range Standard
Not user configurable parameters
Number of ports 4 IEEE 802.3-2005
Location of ports front panel
Connector type RJ-45
Impedance 100 ± 15 Ohms for the frequency
band from 1 to 100 MHz
Auto negotiation fully supported
User configurable parameters
Administrative state enable/disable IEEE 802.3-2005
Speed 10/100 Mbit/s
Port mode half-duplex
full-duplex

EPSI1User Manual 15
SPECIFICATION

Table 5: Ethernet ports on the front panel (continued)

Function Description/Range Standard
Ingress rate limiter enabled/disabled
committed information rate
committed burst size

Table 6: PBUS ports (backplane)

Function Description/Range Standard
Maximal number of PBUS ports 64
PBUS port types P0nc (Terminated mode) G.704
P12x (Transparent mode)
P12 (Clock Master)
Port speed in P0nc mode 64 kbit/s (n=1) … 1984kbit/s (n=31)
2048 kbit/s (n=32): restricted use
Port speed in P12 mode 2048 kbit/s
Total available bandwidth on the PBUS mode = 8 x 2Mbit/s: 16’384 kbit/s
mode = 16 x 2Mbit/s: 32’768 kbit/s

3.3 Logical interface functions

Table 7: Parameters, user configurable per interface

Function Description/Range Standard
Supported layer 2 protocols for TDM PPP RFC 1661
interfaces Multilink PPP RFC 1990
MAC/PPP RFC1638
MAC/HDLC encapsulation
IP/PPP RFC 1332
Supported IP addressing modes for TDM numbered
interfaces numbered with peer
Interface assignment, i.e. appropriate router
interface networking function bridge-1 ... bridge-8

16 EPSI1User Manual
 SPECIFICATION

Table 8: Parameters for virtual interfaces

Function Description/Range Standard
Interface selection Ethernet interfaces (not assigned to a
bridge instance)
bridge instances 1 ... 8
VLAN ID for frame filtering 1 ... 4094
Administrative state disabled/enabled

3.4 Networking functions

Table 9: OSI layer 2 data forwarding (bridging)

Function Description/Range Standard
Data forwarding technology network processor
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
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
RSTP enable/disable IEEE 802.1w-2001
Path cost computation automatic/manual
Manual path cost 1 … 200’000’000

Table 10: OSI layer 3 data forwarding (routing)

Function Description/Range Standard
Static routing up to 128 static routes
OSPF dynamic routing RFC 2328
RIP v2 dynamic routing RFC 2453
VRRP support of two virtual routers per inter- RFC 3768
face (VRRP A and VRRP B)
Dedicated loopback interface valid IP address

EPSI1User Manual 17
SPECIFICATION

Table 11: OSPF

Function Description/Range Standard
User configurable parameters per AS, area or address range
OSPF Areas up to 8 areas RFC 2328
area link state mode normal
stub
NSSA
area address ranges up to 8 address ranges per
OSPF area
area address range advertise mode advertise address range
hide address range
User configurable parameters per interface
OSPF state enabled/disabled RFC 2328
OSPF mode active
passive
OSPF area backbone (default) RFC 2328
area-2 ... area-8
Interface metric automatic metric
manual metric 1 ... 65535
Router priority (selection of designated router) 0 ... 255
Advanced options
Hello interval 1 ... 65535 s RFC 2328
Dead interval 0 ... 3600 s
Transmit delay 0 ... 3600 s
Retransmit delay 0 ... 3600 s

Table 12: RIP

Function Description/Range Standard
User configurable parameters per interface
RIP state enabled/disabled RFC 2453
RIP mode active
passive
Authentication / Version None / RIPv1
None / RIPv2
None / RIPv1 & v2
Simple / RIPv2
MD5 / RIPv2

18 EPSI1User Manual
 SPECIFICATION

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

Function Description/Range Standard
User configurable parameters per interface (function not available for TDM interfaces)
Virtual router state enable/disable RFC 3768
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 14: QoS

Function Description/Range Standard
Profile for QoS mapping Generic profiles for 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

3.5 Protection

Table 15: Protection

Function Description/Range Standard
Equipment protection not supported
Traffic protection on Ethernet ports supported with RSTP (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

EPSI1User Manual 19
SPECIFICATION

3.6 Environment

Table 16: Power consumption

Function Description/Range Standard
Power supply range VBAT -39.5 VDC … -72 VDC
Current consumption (typical, with maximum +5 VCC (power rail on backplane)
traffic load = 0 mA
-5 VCC (power rail on backplane) =
0 mA
-48 VBAT (direct from battery) =
200 mA
Typical total power requirements from battery VBAT = -48 V (nominal voltage)
- +5 VCC: 0 mA x 5.1 V = 0 W
-48 VBAT: 200 mA x 48 V = 10 W

Table 17: Mechanical parameters

Function Description/Range Standard
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 18: Reliability

Function Description/Range Standard
Calculated MTTF for all categories of failures (MIL-HDBK-217F)
MTTF @ 35°C ambient temperature 88 year

20 EPSI1User Manual
 SPECIFICATION

3.7 Summary of standards

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

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

EPSI1User Manual 21
SPECIFICATION

3.7.3 ETSI
• ES 201468 V1.1.1
Additional EMC Requirements for Telecommunication Equipment for
enhanced availability of service in specific applications

3.7.4 IEC
• IEC EN60950-1
Information Technology Equipment – Safety – Part 1: General Require-
ments
• ISO/IEC 3309:1191 (E)
Information Technology – Telecommunications and information
exchange between systems – High-level data link control (HDLC) proce-
dures – Frame structure

3.7.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)

22 EPSI1User Manual
 INSTALLATION

4 Installation
4.1 Prerequisites

4.1.1 Installation precautions

NOTICE Electrostatic discharges. Risk of equipment damage!

Keep the EPSI1 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 Unit embedded software (ESW)

The EPSI1 unit runs on dedicated ESW. This ESW is labelled
EPSI1_r<x>.<y><zz>, e.g. EPSI1_r2.a02.
For the ESW revision prerequisites please refer to FOX61x Release Notes.
The software included in this product contains copyrighted software that is
licensed under the GPL.

4.2 Slots for the EPSI1 unit

The EPSI1 unit uses one slot in the FOX subrack and can be operated in
slots: 1 … 10, 12 … 21 (FOX 615) and slots 7 … 10, 12 … 14 (FOX612).
Slot 11 is always reserved for the CESMx unit.
For more information regarding the PBUS access and the cross connections
please refer to 1KHW002467 FOX61x TDM Services.

EPSI1User Manual 23
INSTALLATION

4.3 Connections and Cables

4.3.1 Connectors and signals

The EPSI1 has four Ethernet interfaces on the unit front panel, numbered
from bottom up with C1.1 to C4.1
The Ethernet interfaces are equipped with RJ-45 connectors. The interface
layout 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.

EPSI1 R1A

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

Figure 4: EPSI1 front view with RJ-45 pin assignment

24 EPSI1User Manual
 INSTALLATION

Each Ethernet interface provides two LEDs indicating the link state and the
link activity:

Activity

Link state

Figure 5: Ethernet link LEDs on the EPSI1 unit

The activity LED has the following states:

• Yellow blinking: Traffic activity
• 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 Ether-
net interfaces. The cable type can be chosen according to the available
cables since the Ethernet ports on EPSI1 implement automatic crossover
functionality.
According to the Ethernet link speed, the following cable categories have to
be used:

Table 19: 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

EPSI1User Manual 25
INSTALLATION

4.4 Fixing the cables to the cable tray

The optical or electrical cables must be attached to the cable tray of the
FOX615 or the corresponding device of the FOX612.
The open cable shields must be in contact with the FOX grounding bar and
should be fixed to the cable tray or the corresponding device in the FOX612.
The figure below shows the cable/cable tray assembly of the FOX615. With
the FOX612 the cable tray functionality is implemented differently and
depends on the type of installation (rack-, wall-mounted).

C4.1

C3.1

C2.1

C1.1

C5.1 - C8.1

120 mm

<x> mm

Figure 6: Side view of the FOX615 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.

26 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5 Functional Description
5.1 Overview

From the interface point of view the EPSI1 is designed to interconnect Ether-
net 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 EPSI1 is bridging and routing. In addi-
tion 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 ... 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 section "QoS" the focus is on congestion problems typically
occurring when packets must be forwarded from a fast input interface to a
slower output interface, e.g. from a 100BaseT Ethernet input to a 2 Mbit/s
output.

EPSI1User Manual 27
FUNCTIONAL DESCRIPTION

5.2 Ethernet LAN interfaces

5.2.1 Ethernet front ports

EPSI1 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 configur-
able in respect of:
• Administrative state ON/OFF
• LAN mode selection
− Auto negotiation
− 100 Mbit/s full duplex
− 100 Mbit/s half duplex
− 10 Mbit/s full duplex
− 10 Mbit/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.2.2 Internal GbE port

The internal GbE port connects to the CESMx unit via backplane. In order to
connect both to the working and to a possible protecting CESMx, the internal
GbE port is implemented in a 1+1 design. Nevertheless the internal port is
presented to the user as a single port and all possible 1+1 switchover func-
tions are automatically handled by the system.

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
equivalent capacity of 128 x 2 Mbit/s for traffic signals with and without CAS.
For the main characteristics and detailed explanations of the PBUS please
refer to 1KHW002466 FOXCST Operation.
EPSI1 supports the following PBUS formats:
• P0nc (with and without CAS)
• P12 (transparent)
• P12 (clock master)
EPSI1 uses the CAS bits for the 1+1 Trail (Path) protection function.

28 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.3.1 PBUS Cross Connections

FOXCST is designed to accept valid PBUS cross connections only, but for
EPSI1 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 20: Overview on cross connection modes

EPSI1 unit Connecting 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 EPSI1 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

1KHW002467 FOX61x TDM Services.

5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s»

Table 21: 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
(PBUS). 32 Mbit/s.
Available TDM modes are P0nc and P12 (transparent). Available TDM modes are P0nc and P12 (clock master).
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 time slots from n = 1 … 32 may be even numbers of time slots from n = 2 … 32 may be
selected. selected.

Table 22: Overview on clocking and TDM modes

TDM mode Framing Available Usable by Clocking Impact in case of unsyn-
in unit the FOX as chronised 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 framework handled by the G.704 process
16x2Mbit/s with the local FOX clock. and lead to occasional data
loss.
P12 unframed 8x2Mbit/s no The FOX framework passes the Clock recovering from
(transparent) data stream (including its original received data streams pre-
clock) transparently to the TDM vents occasional data loss
input of the EPSI1 unit. The EPSI1 even for unsynchronised Rx/
unit extracts the Rx clock from the Tx state.
Rx data stream.
P12 unframed 16x2Mbit/s no The EPSI1 unit uses the FOX sys- Possible clock differences are
(clock master tem clock for Rx data streams. handled by the FOX frame-
work and lead to occasional
data loss.

EPSI1User Manual 29
FUNCTIONAL DESCRIPTION

Risk of operating trouble!

Take great care on timing source configuration in FOX TDM networks.
Unsynchronised 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, please refer to section 5.3.1 PBUS Cross
Connections (on page 29).
For details on timing source configuration please refer to sectio 5.3.1 PBUS
Cross Connections (on page 29).

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 exist-
ing unit whenever the unit mode should be changed.

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 EPSI1 the option «Protected»
must be set to «Yes», when establishing the cross connection between
EPSI1 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 supporting 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 EPSI1 and LEDS1 enable CAS on both
units and select «Supervised» or «1+1 Revertive» as transport mode on the
LEDS1, provided CAS is supported for the full path.

30 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

For detailed description of signal protection please refer to 1KHW002467

FOX61x TDM Services.

5.4 Bridging functions

5.4.1 VLAN MAC transparent bridging

EPSI1 is a VLAN aware MAC bridge according to IEEE 802.1Q-2003.
EPSI1 uses the port and tag based VLAN concept in order to assign a VID to
received frames.

VLAN A VLAN A

EPSI1
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 7: The port based VLAN model (802.1Q, Annex D)

Below a list of rules for the VLAN MAC transparent bridge with port based
VLAN concept as implemented in EPSI1:
• 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.

EPSI1User Manual 31
FUNCTIONAL DESCRIPTION

− 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 front, Ethernet internal or TDM) i.e. the VLAN port type is user con-
figurable without restriction.

32 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

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

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.

Conflicting configuration Correct configurations

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
trunk link discarding
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.
Conflicting configuration Correct configurations
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
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
untagged VLAN tagged
forwarding
VLAN ID = 110

Figure 8: Possible inconsistencies in VLAN tagged bridged networks

EPSI1User Manual 33
FUNCTIONAL DESCRIPTION

5.4.2 IVL based MAC learning

The VLAN standard IEEE 802.1Q-2003 mentions two methods for MAC
learning 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 per VLAN.
• A VLAN aware bridge may implement either SVL only or IVL only or it
may implement both SVL and IVL.
EPSI1 implements the IVL approach with tables supporting 8192 learned
MAC addresses per bridge instance.

5.4.3 RSTP
EPSI1 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
several physical loops. Without breaking up the loops, broadcast frames
would circulate indefinitely, multiplying themselves and thus jam the network
for any unicast user traffic.

Bridge A

Bridge B Bridge C

Figure 9: Example bridged network with meshed topography

Root
Forwarding
Bridge A
Forwarding Forwarding

Forwarding
Discarding
Forwarding

Bridge B Bridge C
Forwarding Discarding

Figure 10: Active tree topology of the same network

In order 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
spanning trees such as STP according to 802.1D. Designing networks with
mixed spanning tree versions should be avoided whenever possible,
because the rapid conversion is then lost. EPSI1 provides valuable informa-
tion in the status menus for maintaining and debugging bridged networks .
For details see section 8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge
(on page 88).

34 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.4.4 Multiple bridge instances

EPSI1 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.
Nevertheless each bridge instance provides the full EPSI1 function set for
bridging without restrictions.

Please note:
Traffic isolation between two bridge instances on the same EPSI1 unit is the
same as between two bridges on separate hardware.

EPSI1

EPSI1

PDH/SDH
network EPSI1

Third party
bridge

EPSI1

Bridge A Bridge B Bridge C Bridge D

Figure 11: Example application with multiple bridge instances

Please note:
BPDUs (the bridge control information for RSTP/STP) are always transmit-
ted without a VLAN tag, i.e. the active tree topology is calculated without
consideration of VLAN borders. Only by using independent bridge instances
it is possible to build multiple independent spanning trees with the EPSI1
unit.

EPSI1User Manual 35
FUNCTIONAL DESCRIPTION

5.4.5 Star topology bridging

The star topology bridging feature supported by the EPSI1 unit can be used
together with VLAN bridging and works as an additional forwarding restric-
tion 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 com-
municate 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 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 inter-
faces only.
• Frame filtering upon the learned MAC address tables is applied in addi-
tion 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».
EPSI1
ETER1
ETER1
Internal port
COGE 1 EPSI1 EPSI1
via backplane
ETER1 PDH/SD
ETER1 network
EPSI1 PDH/SDH
network
EPSI1
PDH/SDH
PDH/SDH
network

network
LEDS1

LEDS1
EPSI1
DTM-M
DATI1
DATI1
DTM-M

Public bridge interface LEDS1

Protected bridge interface

Figure 12: Example star bridging application

The EPSI1 star bridging function is a purely local bridge function. It is com-
patible with other bridge/switch equipment (ETER1, LAWA4, third party) as

36 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

long each bridge with more than two protected interfaces follows the same
forwarding rules as defined above. The function is compatible with the
“Rooted Multipoint EVC type” as described in MEF 10.1.
RSTP does not interfere with the star bridging function, but must be con-
strained to public interfaces only.

5.5 Routing functions

This user manual is not a routing tutorial. The following routing basics and
definitions in this section should help understanding how some important
expressions 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 net-
work 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
interface to an egress interface, using appropriate forwarding infor-
mation.
Forwarding information
− can either be static or dynamic;
− is stored in the routing table;
− is composed of a destination IP address range (network address plus
network mask) and a gateway address.

5.5.1 Static routing

Static routing is a simple and basic function for every router. The corre-
sponding 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 topol-
ogy changes on the network.
For the configuration of static routes in EPSI1 see section 8.9.2.2 /unit-x/
router – Configuration... – StaticRoutes (on page 106).

5.5.1.1 Connecting networks with static routing

The EPSI1 unit uses static routing in order to interconnect between a net-
work with dynamic routing (OSPF or RIP) where it is itself part of and any
external destination.

EPSI1User Manual 37
FUNCTIONAL DESCRIPTION

default route specific

external route

EPSI1 OSPF or RIP external

large network EPSI1 destination
static routing
static routing

static routing or EGRP

Internet

Figure 13: Interconnecting networks

5.5.2 OSPF routing

OSPF is a dynamic routing protocol for IP networks. It uses a link state rout-
ing 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
network 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 cor-
respondingly as an external route. Normally, external routes are distributed
to the whole AS and routers that advertise external routes are considered as
AS boarder routers.

38 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

Please note:
OSPF external routes are advertised only if «OSPF Redistribute» – «Static»
in the «Router»-menu is enabled.

ne: FOX615: Ok

fan: FAMO1: Ok

unit-1: LEDE1 R1A (lede1_r3a05) :

unit-2: LEDE1 R1B (lede1_r3a05) :

unit-7: EPSI 1 P1C (epsi1_r2a02) :

Figure 14: Redistribution of static routes

See also section 8.9.2.2 /unit-x/router – Configuration... – StaticRoutes (on

page 106)

5.5.2.2 OSPF areas

A newly set up OSPF AS is often running in a single area, the backbone

area. But when it grows and it’s size reaches a certain limit, flooding the
whole network information is no longer efficient.
In order to reduce overhead traffic and to save memory resources in the
OSPF routers, 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 all other areas this information is reduced
to one or several summaries. A special role in each AS plays the backbone
area. It must have an ID of «0» and must be of type «Normal». The back-
bone area builds the core of the OSPF network and all other areas (with a
non-zero ID) must physically connect to the backbone (connection on OSI
layer 1, e.g. TDM connection).

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
capabilities, the area topology and the area mode. 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
external routes in a restricted way only.

EPSI1User Manual 39
FUNCTIONAL DESCRIPTION

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 concerning the router instance, some the connecting interfaces.
• The connecting interfaces of two 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.
• The common area of two neighbouring routers must use the same con-
figuration 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
common network properties in the OSPF AS. This router is called the desig-
nated router. The designated router along with a backup designated router is
elected from all OSPF routers in the broadcast network upon the OSPF pri-
ority value.
The two routers of a point-to-point link always form full adjacency, provided
matching area configuration.

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 a 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 ade-
quate.
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

40 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

user has a choice. The EPSI1 unit supports RIP mainly for maintaining exist-
ing 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 authen-
tication is only selectable in conjunction with RIPv2.
• Without authentication the user can select between supporting either
RIPv1 only, RIPv2 only 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
originally been learned from. Counting up to 16 is (in most cases) no longer
necessary and thus speeds up networks convergence.
«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

If a router is located at the border between an OSPF network an a RIP net-
work and if it has active interfaces in both networks, it gathers routing infor-
mation from both the OSPF and the RIP network. The question arises,
whether and how the router should redistribute routing information learned in
one network towards the other network. EPSI1 provides user configurable
redistribution in order to allow individual adaptation.
The following redistribution rules should be followed:
• 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
direction
• Redistribution of connected interfaces has almost the same effect as
activating 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.

EPSI1User Manual 41
FUNCTIONAL DESCRIPTION

Please note:
Whenever possible prefer configuring interfaces in passive mode over redis-
tribution of connected interfaces. For more information regarding the passive
mode, please refer to section 8.9.2.1 /unit-x/router – Configuration... –
Router (on page 104).

ETAG1 advertises one or several

static routes corresponding to the
address range of the RIP network

OSPF RIP
EPSI1

ETAG1 redistributes learned routing

information from OSPF to RIP,
including a possible default route

Figure 15: Redistribution example

5.5.5 VRRP, the virtual router

In order to rise availability, critical network components like gateway routers
should be built redundant. There is no problem to establish a redundant con-
nection 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 gate-
way 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 16: 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 representa-
tion 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
including the IP address. When the IP address of the virtual router is config-
ured as gateway address in the IP host, connectivity to the network is availa-
ble as long as at least one physical member of the virtual router group is up
and running.

42 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

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 17: 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 noth-
ing to do than listening for the master routers advertisements. Missing adver-
tisements from the master router trigger, after a timeout period, a new mas-
ter election.

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 EPSI1 VRRP implementation does not use the virtual MAC address.
Instead the MAC address of the corresponding Ethernet interface on the
EPSI1 is used. As a consequence, the virtual router’s MAC address changes

EPSI1User Manual 43
FUNCTIONAL DESCRIPTION

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

mum. Especially when the participating VRRP routers offer similar path qual-
ity it makes sense to administratively disable preemption. If preemption is
disabled, the currently active master stays master, even if another VRRP
router advertises a higher priority than the current master’s priority. Only an
owner of the virtual 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 consid-
ered as the owner of the address, becomes immediately master and starts
sending advertisements with the highest priority of 255, irrespective from its
actually configured 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 com-
mon and allows load sharing. As in the previous example in Figure 17: IP
host logically connected to a virtual router (on page 43), 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.
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 18: VRRP application with load sharing

Under normal conditions both physical gateway routers are available. Gate-
way 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 gate-
way addresses from virtual router 1 or 2.
The load sharing according to figure 19 above works in transmit direction
only. The return traffic from the IP network finds its way depending on the
routing tables in each router it passes.

44 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.5.6 Establishing a redundant path through a routed network

For a truly redundant connection through an IP routed network two functions
are typically involved: OSPF and VRRP.
The dynamic routing protocol OSPF is responsible to find an alternative
route trough the network in case of a failure in a network node or an inter-
rupted interconnection. The virtual router protocol VRRP is responsible to
switch to an alternative network gateway. Figure 20 below shows a corre-
sponding setup.
Router A: EPSI1 Router C : EPSI1
participates with port -4 participates with port -4
in VR A, priority =110 in VR C, priority =110
in VR B, priority =100 in VR D, priority =100

IP host A Virtual router A Virtual router C IP host C

172.16.1.102/24 ID = 221 ID = 221 172.16.22.44/24
GW = 172.16.1.221 172.16.1.221 /24 172.16.22.221/24 GW = 172.16.22.221

172.16.98.18/30 172.16.98.17/30
24 Main TDM link, R-C 1 72
13/ R-A 17 30 .1 6
. 1. 2. 1 2Mb/s .6/ .22 .
.16 6 .98 .98 4/ 24
17
2 .9/ 2 .16
  30 17  
switch switch
redundant TDM links,
VR-A VR-B 256 kb/s VR-C VR-D

  17  
1 72 /30 2.1
switch .16 8.5 6.9 24 switch
. 1. 1 6.9 8. . 3/
2.1
10 . 22
13/ 2 17
/30 . 16
4 172
Main TDM link, 2Mb/s
R-B R-D
172.16.98.13/30 172.16.98.14/30

IP host B Virtual router B Virtual router D IP host D

172.16.1.105 /24 ID = 222 ID = 222 172.16.22.99/24
GW = 172.16.1.222 172.16.1.222 /24 172.16.22.222/24 GW = 172.16.22.222
Router B: EPSI1 Router D : EPSI1
participates with port -4 participates with port -4
in VR A, priority =100 in VR C, priority =100
in VR B, priority =110 in VR D, priority =110

All EPSI1 units have OSPF activated in All ppp over TDM links are configured
the backbone area for all router interfaces . for automatic OSPF metric .

Figure 19: Setup for a redundant connection

Under normal conditions and with no network defects, pinging host C from
host A results in the following trace:
Reply from 172.16.22.44: bytes=32 time=4ms TTL=252
Route: 172.16.98.18 ->
172.16.22.4 ->
172.16.22.44 ->
172.16.98.17 ->
172.16.1.13

Both forward and return path follow the upper trail.

Under normal conditions and with no network defects, pinging host D from
host A results in the following trace:
Reply from 172.16.22.99: bytes=32 time=4ms TTL=252
Route: 172.16.98.18 ->
172.16.22.4 ->
172.16.22.99 ->
172.16.98.14 ->
172.16.1.113

The forward path follows the uper trail but the return path follows the lower
trail, since host D addresses router D with it’s gateway setting.

EPSI1User Manual 45
FUNCTIONAL DESCRIPTION

The test is repeated with a broken link between host A and router A:

R-A R-C

host A host C
VR-A VR-B VR-C VR-D
host B host D

R-B R-D

Figure 20: Connectivity test with a broken link

Ping test of host C from host A with a broken link:

Reply from 172.16.22.44: bytes=32 time=4ms TTL=251
Route: 172.16.98.13 ->
172.16.22.222 ->
172.16.22.44 ->
172.16.22.4 ->
172.16.98.14 ->
172.16.1.113

Both forward and return path follow the lower trail. An extra hop is added,
because router C must send the return via router D.
Ping test of host D from host A with a broken link:
Reply from 172.16.22.99: bytes=32 time=4ms TTL=252
Route: 172.16.98.13 ->
172.16.22.222 ->
172.16.22.99 ->
172.16.98.14 ->
172.16.1.113

Both forward and return path follow the lower trail. No extra hop is added,
because host D addresses directly router D with it’s gateway address.
Router B is now acting as master for both virtual routers and takes over all
traffic from host A and B. Because router A detects port-4 down, it stops
advertising network 172.16.1.0/24 and as a consequence of this topography
change, router C sends traffic for network 172.16.1.0/24 via router D.
In case of a breakdown of one of the routers, there is a similar corrective
action from the remaining routers performed by OSPF and VRRP.
A problem arises in case of a link failure that can not be detected by the next
router. Let’s assume a setup as in Figure 21: Undetected network interrup-
tion (on page 46) below:

R-A

host A
VR-A VR-B
host B

R-B

Figure 21: Undetected network interruption

VRRP will react correctly on the break between the switches: router B will
become master for both VRs and takes over all traffic from both host A and
B. But the return traffic never arrives back to host A. Router A does not
detect any interface down, thus continues advertising the corresponding IP
network but is unable to deliver received packets to either host A or B.

46 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

Please note:
Keep the network part between hosts and gateway routers with VRRP as
simple as possible, in order to minimise the possibility of undetected breaks.

Please note:
ABB does not recommend configuring VRRP for VLAN interfaces. There is
no status detection for failed interfaces and any network interruption
between a host and the gateway router is not protected. However the VRRP
protection is working in case of a gateway router breakdown.

5.6 Interface stacks

5.6.1 Generic stack model

The generic stack model reflects the EPSI1 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 encapsu-
lation) between the networking function and the physical interface.
• EPSI1 networking functions
− MAC bridging
− IP routing
• EPSI1 interfaces
− Ethernet
− TDM, i.e. P0nc/P12 via the FOX internal PBUS
− VLAN interface
• EPSI1 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.

EPSI1
Networking function

Encapsulation Encapsulation

Physical interface Physical interface

Figure 22: 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.

EPSI1User Manual 47
FUNCTIONAL DESCRIPTION

EPSI1 or 3rd party equipment

Networking function

Encapsulation
Encapsulation and
Physical interface interface omitted

Figure 23: Omitted encapsulation type

How the generic stack model can be used is shown by the hypothetical
application examples below.

5.6.2 MAC/PPP bridged encapsulation

EPSI1 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

EPSI1 supports direct MAC/HDLC encapsulation compatible with DTM-M
and LEDS1. With this feature the EPSI1 unit can terminate a DTM-M link
and continue the connection with standard PPP.
EPSI1 DTM-M
MAC Bridging MAC Bridging
MAC/PPP DATI1
RFC 3518 * MAC/HDLC MAC/HDLC IEEE 802.3
PPP P0nc/P12x
P0nc /P12x PBUS PBUS DSL DSL link DSL 10/100 Base-T
RFC 1661
PPP/HDLC
LEDE1 RFC 1662
E1 HDB3 PBUS
PBUS
P0nc/P12x P0nc/P12x

Ethernet
3rd party Bridge with serial I /F LAN
MAC Bridging
MAC/PPP
RFC 3518
PPP MAC bridging IP routing
RFC 1661
PPP/HDLC IEEE 802.3
PDH/SDH PHY Ethernet IPoE/ARP
RFC 1662
network IEEE 802.3
serial interface 10/100Base-T
G.703 MAC framing
IEEE 802.3
PHY Ethernet
10/100Base-T

Figure 24: Connection of DTM-M to 3rd party bridge

5.6.4 PPP/HDLC encapsulation & framing

EPSI1 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
synchronous serial bit streams (e.g. with X.21, V.35 or G.703 interfaces).

48 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.6.5 Hypothetical applications with bridging

The following EPSI1 bridging applications in the figures below are all inter-
connected via a common PDH/SDH network:
1 TDM WAN link termination with MAC/PPP
2 Ethernet LAN – TDM WAN connection
3 Traffic aggregation with DATI1 and DTM-M modem
4 Traffic aggregation with DATI1 and DTM-M modem plus translation of
TDM WAN link termination from MAC/PPP to MAC/HDLC
5 Traffic aggregation with LEDS1 and serial interface
6 TDM WAN connection to 3rd party bridge with G.703 interface

Bridging application 1: EPSI1

TDM WAN link termination
with MAC/PPP MAC Bridging
MAC/PPP
RFC 3518*
PPP
RFC 1661
PPP/HDLC
LEDE1 RFC 1662
E1 HDB3 PBUS
PDH/SDH PBUS
network P0nc/P12x P0nc/P12x

Bridging application 2: EPSI1

Ethernet LAN – TDM WAN connection
IP routing

IPoE/ARP

IEEE 802.3
EPSI1
MAC Bridging 10/100 Base-T
MAC/PPP
IEEE 802.3 EPSI1
RFC 3518
PPP 10/100 Base-T MAC Bridging
RFC 1661 Ethernet LAN
PPP/HDLC
RFC 1662 IEEE 802.3

LEDE1 PBUS
10/100 Base-T
P0nc /P12x

3rd party Bridge

MAC Bridging

IEEE 802.3
10/100 Base-T
Gb Ethernet

Bridging application 3:
Traffic aggregation with DATI 1 and DTM-M

EPSI1 3rd party Bridge with serial I /F

MAC Bridging MAC Bridging
MAC/PPP MAC/PPP MAC/PPP
RFC 3518 RFC 3518 RFC 3518
PPP PPP PPP
RFC 1661 RFC 1661 RFC 1661
DATI1 DTM-M
PPP/HDLC PPP/HDLC PPP/HDLC
RFC 1662 RFC 1662 RFC 1662
P0nc/P12x
LEDE1 PBUS PBUS DSL link DSL serial serial interface
P0nc/P12x P0nc/P12x PBUS DSL G.703
interface

Figure 25: Stack details for EPSI1 bridging applications

EPSI1User Manual 49
FUNCTIONAL DESCRIPTION

PDH/SDH
network

Bridging application 4:
Traffic aggregation with DATI 1 and DTM -M plus translation of 3rd party IP host
TDM WAN link termination from MAC /PPP to MAC/HDLC with Ethernet I /F
DTM-M
EPSI1 IP

MAC Bridging MAC Bridging IPoE/ARP

MAC/PPP DATI1
RFC 3518 MAC/HDLC MAC/HDLC IEEE 802.3 IEEE 802.3
PPP P0nc /P12x P0nc/P12x 10/100 Base-T
PBUS DSL DSL link DSL 10/100Base-T
RFC 1661 PBUS Gb Ethernet
PPP/HDLC
RFC 1662
LEDE1 PBUS
P0nc/P12x

Bridging application 5:
Traffic aggregation with TUDA 1 and serial interface

EPSI1 3rd party Bridge with serial I /F

MAC Bridging MAC Bridging
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 LEDS1 PPP/HDLC
RFC 1662 RFC 1662 RFC 1662
PBUS PBUS P0nc/P12x serial interface
LEDE1 PBUS serial
P0nc/P12x P0nc/P12x interface G.703

Bridging application 6:
TDM WAN connection to 3rd party bridge with G .703 interface

3rd party Bridge with serial I /F

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 RFC 2878

Figure 26: Stack details for EPSI1 bridging applications (continued)

50 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.6.6 Hypothetical applications with routing

The following EPSI1 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 3rd party router with G.703 interface
4 Interconnection of bridged and routed network segments using the EPSI1
virtual interface

EPSI1User Manual 51
FUNCTIONAL DESCRIPTION

Routing application 1: EPSI1

TDM WAN link termination with IP /PPP IP routing
IP/PPP
RFC 1332
PPP
RFC 1661
PPP/HDLC
LEDE1 RFC 1662
PDH/SDH E1 HDB3 PBUS
network PBUS
P0nc/P12x P0nc/P12x

Routing application 2: EPSI1

Ethernet LAN – TDM WAN connection IP routing
IPoE/ARP
EPSI1 IEEE 802.3
IP routing 10/100Base-T
IP/PPP EPSI1
IPoE/ARP
RFC 1332
PPP MAC Bridging
IEEE 802.3
RFC 1661 IEEE 802.3
PPP/HDLC Ethernet LAN
RFC 1662 10/100Base-T 10/100Base-T

LEDE1 PBUS 3rd party Bridge

P0nc/P12x
MAC Bridging
IEEE 802.3
Ethernet

Routing application 3:
TDM WAN connection to 3rd party router with G.703 interface
3rd party router with serial I /F
IP routing
IP/PPP
RFC 1332
PPP
RFC 1661
PPP/HDLC
RFC 1662
serial interface
G.703

Routing application 4:
Interconnection of bridged and routed network segments using the EPSI 1 VLAN interface

EPSI1
IP routing MAC Bridging
VLAN
IP/PPP interface MAC/PPP
RFC 1332 IPoE/ARP IPoE/ARP IEEE 802.3 RFC 3518
PPP PPP
IEEE 802.3 10/100 Base-T
RFC 1661 (a) RFC 1661
PPP/HDLC 10/100Base-T PPP/HDLC
RFC 1662 RFC 1662
LEDEx PBUS PBUS
P0nc /P12x Ethernet Ethernet P0nc/P12x
front port front port
3rd party Bridge with serial I /F (b) There are two alternative ways to
MAC Bridging interconnect bridged and routed
MAC/PPP network segments with a single unit :
RFC 3518 (a) using the EPSI1 VLAN interface
PPP Ethernet LAN
(b) using an external connection via
RFC 1661
PPP/HDLC two EPSI1 Ethernet ports
RFC 1662
serial interface
G.703

EPSI1
MAC Bridging LEDE1
MAC/PPP PDH/SDH E1 HDB3
RFC 3518 network PBUS
PPP P0nc/P12x
RFC 1661
PPP/HDLC
RFC 1662 LEDE1
PBUS P0nc/P12x
PBUS
P0nc/P12x E1 HDB3

Figure 27: Stack details for EPSI1 routing applications

52 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.7 Multilink PPP interface

EPSI1 supports Multilink PPP 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 multiple
independent links between a fixed pair of systems, providing a virtual link
with greater bandwidth than any of the constituent members. With Multilink
PPP, EPSI1 can provide an aggregate link bandwidth of up to 32 Mbit/s.
ML PPP is not depending on the corresponding networking function, i.e. it
works with both bridging and routing.
EPSI1 EPSI1
MAC Bridging IP routing

Multilink -PPP, RFC1990 Multilink-PPP, RFC1990

Termination at
the far side with MAC/PPP MAC/PPP MAC/PPP IP/PPP IP/PPP IP/PPP
Multilink PPP RFC 3518 RFC 3518 RFC 3518 RFC 1332 RFC 1332 RFC 1332
accordingly PPP PPP PPP PPP PPP PPP
RFC 1661 RFC 1661 RFC 1661 RFC 1661 RFC 1661 RFC 1661
(EPSI1, ETER1 PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC
or third party RFC 1662 RFC 1662 RFC 1662 RFC 1662 RFC 1662 RFC 1662
equipment ) PBUS PBUS PBUS PBUS PBUS PBUS
P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x P0nc/P12x

LEDE1
E1 HDB3
PBUS
P0nc/P12x
PDH/SDH
network LEDE1
E1 HDB3
PBUS
P0nc/P12x

Member links of the ML PPP bundle Member links of the ML PPP 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 28: 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
bandwidth, it is strongly recommended to use member links of the same
bandwidth in ML PPP 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 frag-
ments on fast and slow member links exceeds a certain limit.

EPSI1User Manual 53
FUNCTIONAL DESCRIPTION

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 seg-
ments (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 man-
ual reconfiguration.

5.7.3 Delay considerations for multilink PPP bundles

For delay calculations on multilink PPP bundles the aggregated total band-
width 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
member link numbers (e.g. interruptions in the communication network or
configuration changes).

5.8 VLAN Interfaces

The EPSI1 unit provides different ways of connecting Ethernet LAN inter-
faces 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 29: Connecting Ethernet LAN interfaces to the router

Accordingly, there is a choice for connecting TDM WAN interfaces to the

router.

54 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

direct assignment (standard case )

TDM WAN
interfaces assignment via a bridge
instance and a VLAN interface
VLAN
interface

Figure 30: 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 possible choices are not cross
compatible. See section 5.6 Interface stacks (on page 47) for stack details.
The virtual LAN interface is a versatile function mainly for:
− inter-VLAN routing;
− selective routing per VLAN;
− 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 please refer to Figure 27:
Stack details for EPSI1 routing applications (on page 52).

5.8.1 Inter-VLAN routing

An example application for 1000 IP hosts uses four IP subnets of 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 provides IP connectivity between the subnets and furthermore acts
as gateway for all subnets. This requirements can be achieved in different
ways:
1 In the classic solution there is a port reserved on the router per IP subnet
and the subnets are physically isolated.
2 Only one port is needed on the router device if the four class C subnets
are supernetted with a /22-mask. Drawback: Overhead traffic rises with
the bigger broadcast domain and a non-default network mask has to be
established in each participating IP host.
3 As in solution 2), only one port is needed on the router device in the
VLAN solution and the IP subnet size is still limited to a default /24-mask,
in order to maintain a reasonable size for the broadcast domain.

EPSI1User Manual 55
FUNCTIONAL DESCRIPTION

1) Solution with a port per IP subnet 2) Solution with one single port and a
(/24-mask) and an IP address per port 4 times bigger IP subnet (/22-mask)

subnet A
subnet B Gateway Subnets Gateway
subnet C A, B, C, D

subnet D

3) VLAN solution with one single port and a VLAN interface per
subnet (/ 24-mask), each with a unique VLAN ID and IP address
VLAN I/F, VLAN Id = 101 EPSI1
Subnets IP addr = 172 .16.31.1/24
A, VLAN Id 101 VLAN I/F, VLAN Id = 102
B, VLAN Id 102 Ethernet IP addr = 172 .16.32.1/24 Gateway
C, VLAN Id 103 front port
VLAN I/F, VLAN Id = 103
Eth-1 IP addr = 172 .16.33.1/24
D, VLAN Id 104
VLAN I/F, VLAN Id = 104
IP addr = 172 .16.34.1/24
Interface is assigned to
the Bridge as trunk port

Figure 31: Inter-VLAN routing

5.8.2 Routing of tagged and untagged traffic

In the example application below both tagged and untagged frames must be
routed over the same interface.

Ethernet LAN with tagged Interface assigned to the router , EPSI1

and untagged ranges IP addr = 172 .16.1.1/24

VLAN X untagged VLAN I/F, VLAN Id = 101

VLAN-ID = 168 Subnet 172.16.1.0/24 IP addr = 172.16.32.1/24
not routed by Eth-1 Ethernet
VLAN I/F, VLAN Id = 102 Gateway
VLAN C VLAN A front port IP addr = 172.16.33.1/24
Subnet 172.16.34.0/24
Subnet172.16.32.0/24 Eth-1
VLAN-ID = 101 VLAN I/F, VLAN Id = 103
VLAN-ID = 103 VLAN B
Subnet172.16.33.0/24 IP addr = 172.16.34.1/24
VLAN-ID = 102

Figure 32: Selective VLAN routing for tagged and untagged frames

56 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

5.8.3 Connecting bridged and routed network segments

In this application EPSI1 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 EPSI1 units and the central ser-
vice point. One or several VLAN interfaces provide the EPSI1 internal con-
nection between bridging and routing.
EPSI1
VLAN TDM
interface network

  DTM-M DSL link TDM

DATI1 TDM
I/F-1
EPSI1 I/F-6
  TDM
DTM-M DSL link DATI1
I/F-2
VLAN interface(s)
  DTM-M DSL link TDM
DATI1
I/F-3
TDM
  TDM
DTM-M DSL link DATI1 I/F-5
I/F-4

TDM
network

Figure 33: The VLAN interface connects between bridging and routing

Configuration example for untagged traffic from the DTM-M and a single
VLAN interface, i.e. all IP hosts in a common subnet:
• TDM I/F-1 ... 4: assigned to bridge-1 as access port with VLAN-ID =1
• one single VLAN interface with VLAN-ID =1 and connected to bridge-1
Configuration example for untagged traffic from the DTM-M and an IP subnet
per TDM interface:
• TDM I/F-1: assigned to bridge-1 as access port with VLAN-ID = 101
• TDM I/F-2 ... 4: assigned to bridge-1 as access port with VLAN-ID = 102
... 104 accordingly
• VLAN interface vif-1 with VLAN-ID = 101 and connected to bridge-1
• VLAN interface vif-2 ... 4 with VLAN-ID = 102 ... 104, all on bridge-1
Configure TDM interfaces as «Trunk» for tagged traffic on the DSL links.

5.9 QoS

QoS for the EPSI1 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 pro-
cesses are involved in the QoS function:
• Traffic classification
• Traffic queueing
• Priority mapping to queues

EPSI1User Manual 57
FUNCTIONAL DESCRIPTION

5.9.1 Frame classification and marking

Frame classification is depending on the networking function and on the
received frame type.

Table 23: 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 The frame priority is derived field in the IPv4 header
derived from the frame tag from the ingress port priority

5.9.2 Traffic queueing

EPSI1 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 Ethernet I/F
queue scheduling 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
Multilink PPP bundle

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 34: Frame handling for QoS in EPSI1

58 EPSI1User Manual
 FUNCTIONAL DESCRIPTION

• Queue scheduling
A scheduling process is responsible to empty a set of queues in a prede-
termined way. The current release of EPSI1 uses strict priority schedul-
ing.
• Forwarding service fairness
Ingress frames from the active interfaces are served and forwarded in a
round robin way.

5.9.3 Priority maps

The relation between traffic priority and transmit queues is controlled with
separate mapping tables for MAC frames and IP packets.

Table 24: 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 25: 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

EPSI1User Manual 59
FUNCTIONAL DESCRIPTION

60 EPSI1User Manual
 COMMISSIONING

6 Commissioning
6.1 The managed objects tree

All user configurable parameters of the EPSI1 unit, i.e. the managed objects
are arranged in a tree. The structure of the tree follows the various interface
types.

FOX NE

unit-1 unit-x: EPSI1 unit-21

bridges vlanInterfaces

bridge-1
Bridge-2
Bridge-3 VLAN
Bridge-4
Bridge-5
Bridge-6 tdmInterfaces (create/delete vif-1...32
Bridge-7
Bridge-8 VLAN Interface)

Interface
RSTP Assignment
machdlc-1...64 mlppp-1…8 ppp-1...64
TDM Router
(create/delete
machdlc- OSPF
loopback -
internalPorts Interface portport
-1port
-2port
-3 -4
mlppp- RIP
ppp- Interface MLPPP Interface
interfaces) Assignment (create/delete member-1...64 Assignment VRRP A
member)
Bridge Bridge VRRP B
port-1 Interface
Router Assignment TDM Router
Router Interface CTP
Assignment OSPF Bridge OSPF
Interface OSPF
Assignment Bridge Router RIP Router RIP
RIP
Bridge Router TDM OSPF TDM

Router OSPF CTP RIP CTP

OSPF RIP Router OSPF RIP

RIP VRRP A Static Legend :

Routes
VRRP A VRRP B area-1 tdmInterfaces node in the AP tree
VRRP B (backbone)
Ingress Rate area-2
Limiter area-3
area-4
area-5
area-6
area-7 tree leafs are accessed with
Ingress Rate area-8
Limiter PHY TDM
Interface-1 «Configuration ...» from the
PHY OSPF corresponding AP

Figure 35: Managed objects tree for EPSI1

EPSI1User Manual 61
COMMISSIONING

Please note:
The other management domains (Main, Fault Management, Performance
Management and Status) follow the same tree structure.

6.2 Commissioning steps

6.2.1 New units in the FOX subrack

Units must be physically present in the subrack before they can be config-
ured. Should a unit have no ESW, it will start up in the bootloader. In this
case the user must download the appropriate software before he can con-
tinue with the configuration process.
For a description of ESW download please refer to 1KHW002466 FOXCST
Operation.

6.2.2 Setting the configurable parameters

Though the configuration order for the numerous parameters is not generally
crucial, the parameter «Mode» under the tag «General» must be set in the
very first step, as it can not be changed after any TDM interfaces have been
configured. See also section 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x
2Mbit/s» (on page 29) for details.
Special care is needed for the arrangement of TDM interfaces, especially in
bandwidth demanding applications. Make sure to start with the broad links
and always configure possible multilink PPP first.

Please note:
FOXCST does check numerous dependencies between different parame-
ters, in order to prevent inconsistent configurations. A warning pops up in
case the entered selection interferes with configuration rules or is not com-
patible with previously entered values. However it is not possible for
FOXCST to prevent all possible inconsistencies or otherwise non-working
configurations.

62 EPSI1User Manual
 OPERATION AND MAINTENANCE

7 Operation and Maintenance

7.1 General operation recommendations

When setting up or debugging an access network using the EPSI1, the task
is facilitated by using the implemented operation, alarm and maintenance
features:
• Status information and maintenance functions
Status indications provide a detailed view for all interfaces on both physi-
cal and logical layers. In addition a number of interactive test functions
are provided.
• Performance Monitoring
Performance parameters provide information about the long term stabil-
ity and reliability of a link. Furthermore packet statistics provide informa-
tion for detailed traffic analysis in the network.
• Fault management

EPSI1User Manual 63
OPERATION AND MAINTENANCE

7.2 Status information and maintenance functions

FOX NE
unit-1 unit-21

EQP
unit-x: EPSI1

bridges vlanInterfaces

vif-1...32
bridge-1
Bridge-2
Bridge-3
Bridge-4
Bridge-5
Bridge-6
Bridge-7
Bridge-8 OSPF
RSTP tdmInterfaces VRRP A
VRRP B
Bridge

machdlc-1...64 mlppp-1…8 ppp-1...64

loopback -
internalPorts Interface portport
-1port
-2port
-3 -4 Bridge Bridge Bridge
member-1...64
Router Router
port-1 Router Bridge Link Router
OSPF
Router Link OSPF
OSPF Router Link
Bridge ARP Table CTP Link
CTP OSPF
OSPF
Router Routing Table
CTP
VRRP A
OSPF Ping Command
VRRP B
VRRP A Traceroute
PHY OSPF RIP Legend :
Command
VRRP B node in the
Interface tdmInterfaces
RIP State AP tree
Link State
area-1
External Link
area-2 Bridge
tree leafs are
State (backbone)
area-3
area-4
area-5 accessed with
area-6
area-7
area-8
Neighbour « Status... » from the
Table Link State corresponding AP

Figure 36: Status tree

Above diagram shows an overview on the available status information for the
EPSI1 unit. Practically every node in the tree provides a menu with one or
several status items. For detailed information about the displayed values or
supported functions please refer to the corresponding section in chapter 8
«GUI Reference».

64 EPSI1User Manual
 OPERATION AND MAINTENANCE

7.3 Performance monitoring

The EPSI1 unit provides performance monitoring data for all types of inter-
faces and for the bridge instances. These test points, i.e. locations where the
various counters collect their information, are allocated in a tree.

unit-x: EPSI1
bridges vlanInterfaces

bridge-1
Bridge-2
Bridge-3 vif-1...32
Bridge-4
Bridge-5
Bridge-6
Bridge-7
Bridge-8
PM groups:
PM groups: - MIB-2 Interface Table
- RSTP Bridge tdmInterfaces

internal loopback - machdlc-1...64 mlppp-1…8 ppp-1...64

Ports Interface
port-1
port -2-3-4
port
port PM groups:
- RSTP Interface
port-1 PM groups: PM groups: - MIB-2 Interface Table
- MIB-2 Interface PM groups: - RSTP Interface
- RSTP Interface - Protection
Table - MIB-2 Interface
- MIB-2 Interface Table Table
PM groups: PM groups: - Protection
- RSTP Interface member-1...64
- RSTP Interface
- MIB-2 Interface Table - MIB-2 Interface
Table
PM groups:
- MIB-2 Interface Table
- Protection

Legend : tree leafs are accessed with

port-1 … 4 node in the AP tree PM groups: «Performance Management ... »
- ….
from the corresponding AP

Figure 37: Performance management tree

The EPSI1 performance monitoring provides three different counter groups:

• RSTP Bridge
• RSTP Interface
• MIB-2 Interface Table
• Protection
Above figure 35 shows, which counter group is available on which AP node.
Each counter group supports the following counter types:
• 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)

Please note:
The performance monitoring is always running. It is not traffic disturbing.

EPSI1User Manual 65
OPERATION AND MAINTENANCE

Please note:
Performance monitoring on EPSI1 signals is only available if the signals are
enabled (ports) or cross connections have been configured (internal signals).
For the definition of terms and a detailed description of the generic aspects
of the FOX performance monitoring, please refer to 1KHW002466 FOXCST
Operation.

7.4 Failures, alarms and notifications

7.4.1 Front panel failure indications

The EPSI1 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 sig-
nals.
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 blinking, 1 Hz: Waiting
The unit has not been taken into service or has not been provisioned.
• Green: Running
The unit is up and running and is ready to provide the required service.
• Off: 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
severity.
• Off: Normal
Error free operation.

EPSI1 R1A

Unit Traffic

Figure 38: Fault indication LEDs on the EPSI1 unit

66 EPSI1User Manual
 OPERATION AND MAINTENANCE

7.4.2 Failure tables in FOXCST

Most alarms on the EPSI1 unit are located on the NE level and in addition
some alarms are provided for the Ethernet and TDM interfaces, as illustrated
in Figure 37 below:

FOX NE
unit-1 unit-21
unit-x: EPSI1

SWM
SSWNA tdmInterfaces
Legend : SWIN
PRC
node in the CCE portport
-1port
-2port
port-1 … 4 -3 -4 machdlc-1...64 mlppp-1…8 ppp-1...64
AP tree HWIC
SWIC
GSW member-1...64
tree leafs are MFA
LOS
accessed with UNAV
«Fault NSW
Management ...» UNAS LOS LOS LOS
LOS
from the UIC LOS TSF TSF TSF
PWRSVE BAR
corresponding AP RTSF RTSF RTSF
EQM

Figure 39: Fault management tree

Depending on the unit’s alarm configuration the active failures generate

entries in the NE active alarms list and in the NE alarm log book. For details
please refer to 1KHW002466 FOXCST Operation.
For the alarm descriptions please look for the corresponding «Fault Manage-
ment...» sections in chapter 8 GUI Reference (on page 69).

7.5 Maintenance

The following maintenance facilities are available from the managemnt func-
tion «Main» on the NE level:
• Inventory data
• Unit ESW download
• Unit ESW upgrade

7.5.1 Unit ESW download

It is possible to remotely upgrade the ESW (local unit FW) of the EPSI1 via
software download.
Please refer to 1KHW002466 FOXCST Operation for a description of the
software download procedure.

EPSI1User Manual 67
OPERATION AND MAINTENANCE

7.5.2 Upgrades
You can upgrade an existing EPSI1 with newer functionality as described in
the new FOXCST release, if the new functional unit is compatible with your
hardware and you have the corresponding software licence.
You can check the compatibility between your hardware and the ESW via
the FOX inventory function. Please refer to 1KHW002459 FOX61x Release
Notes for the corresponding data in the FOX Release Note.

68 EPSI1User Manual
 GUI REFERENCE

8 GUI Reference
This chapter provides a complete reference of the managed objects, proper-
ties, and commands of the EPSI1 functional unit.
This chapter contains the following information:
• An introduction (next section below),
• Management commands and parameters for all available access points
(AP), starting with the unit AP (section 8.2 unit-x: EPSI1 (on page 71)

Table 26: Overview on EPSI1 management

unit-x
cfgm: section 8.2.2, fm: section 8.2.3, status: section 8.3
bridge-y internal loopback Ethernet router tdmInterfaces vlanInter-
cfgm: Port Interface port-r cfgm: section 8.9.2 cfgm: section 8.13.2 faces
section cfgm: cfgm: sec- cfgm: status: section 8.9.3 cfgm: sec-
8.4.2 section tion 8.7.2 section tion 8.18.2
pm: sec- 8.6.2 pm: sec- 8.8.2 fm:
tion 8.4.3 pm: sec- tion 8.7.3 section
status: tion status: 8.8.3
section 8.6.3 section pm: sec-
8.4.4 status: 8.7.4 tion 8.8.4
section status:
8.6.4 section
8.8.5
OSPF RIP machdlc-t mlppp-u ppp-w vif-z
status: status: cfgm: sec- cfgm: section cfgm: sec- cfgm: sec-
section section tion 8.14.2 8.15.2 tion 8.17.2 tion 8.19.2
8.10.2 8.12.2 fm: sec- fm: section 8.15.3 fm: section pm: sec-
tion 8.14.3 pm: section 8.15.4 8.17.3 tion 8.19.3
pm: sec- status: section pm: sec- status: sec-
tion 8.14.4 8.15.5 tion 8.17.4 tion 8.19.4
area-s status: member-v status: sec-
section tion 8.17.5
cfgm: cfgm: section
8.14.4
section 8.16.2
8.11.2 fm: section 8.16.3
status: pm: section 8.16.4
section status: section
8.11.3 8.16.5

The corresponding management domains for «Main» are not included in

Table 26 above, because this is FOX generic. For details regarding the man-
agement function «Main», please refer to 1KHW002466 FOXCST Operation.

EPSI1User Manual 69
GUI REFERENCE

8.1 Introduction

Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the
EPSI1 functional unit.
The descriptions provide screen views and descriptions for the FOXCST
GUI.
The order of appearance of the management functions in this reference is in
accordance with the context menu order for each of the APs in the FOXCST
AP tree.
A full context menu may look as follows:
:

Most of the APs only offer a part of the menu items shown above since each
AP provides an individual set of management functions out of the ones
shown above.
This reference section comprises the management functions:
• “Main“,
• “Configuration“,
• “Fault Management“, and
• “Status“.
In the tables of the sections below, the parameter default values for proper-
ties are underlined.

Please note:
For better legibility of numbers in this user manual, inverted commas are
used when the number’s size exceeds three digits (e.g. 40’000). In parame-
ter entry fields of the FOXCST GUI, these inverted commas must not be
entered. Instead, the numbers are entered without these inverted commas
(e.g. 40000).

Please note:
Screenshots presented in this reference may show configurations or data
that may not correspond to the GUI you see when managing your FOX
equipment.

Please note:
Please rrefer to 1KHW002466 FOXCST Operation for the description of the
FOXCST functions and refer to 1KHW002464 FOX61x System Description.

70 EPSI1User Manual
 GUI REFERENCE

8.2 unit-x: EPSI1

8.2.1 unit-x: EPSI1 – Main

For the
− «Main – General»,
− «Main – Equipment»,
− «Main – Inventory»,
− «Main – Logbooks», and
− «Main – Software»
management functions description, please refer to 1KHW002466 FOXCST
Operation.

EPSI1User Manual 71
GUI REFERENCE

8.2.2 unit-x: EPSI1 – Configuration

8.2.2.1 unit-x: EPSI1 – Configuration – General

72 EPSI1User Manual
 GUI REFERENCE

Table 27: Parameters for menu unit-x: EPSI1 – Configuration –

General
Operation Name Parameter Name Range Descriptions / Details
Mode TDM Access 8 x 2Mbit/s» (Sup- This is the default unit mode and should be favoured for all
port of P0, P0nc applications not needing the high PBUS bandwidth.
and P12 Trans-
parent
16 x 2Mbit/s» The granularity for bandwidth selection on P0nc channels is
(Support of P0nc two 64kbit/s time slots and not one time slot as usual, i.e. only
(n = 2,4,6, … 32) even numbers of time slots from n = 2 … 32 may be selected.
and P12 Clock
Master)

For details about relations between unit modes, TDM modes and timing con-
figuration see 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/s» (on
page 29).

Table 28: Parameters for the «QoS» menu

Column name Range Descriptions / Details
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 ... Q4 MAC tag PRI 0 ... 7 is each mapped to one of the four TX
queues
DSCP Mapping – DSCP Q1 ... Q4 DSCP 0 ... 63 is each mapped to one of the four TX queues

Any mapping profile other than the default profile must first be created in the
«NE Configuration» menu before it can be used for the EPSI1 unit.

EPSI1User Manual 73
GUI REFERENCE

8.2.3 unit-x: EPSI1 – Fault management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation section 8.4. The following table
lists the fault causes of the AP on unit level.

Table 29: Parameters for menu unit-x: EPSI1 – Fault management...

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWM Software Mismatch Equipment  Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment  Minor The ESW that is scheduled for installation is
Not Available Alarm not available on the unit. Make sure that the
ESW is downloaded to the unit.
SWIN Software Incompatible Equipment  Major The running ESW is not compatible with the
With Network Element Alarm version required by the NE type or version.
PRC PBUS Resource Con- Processing  Major The PBUS access circuit of another TDM unit
flict Error Alarm in the subrack is defective.
Remove or unassign the other TDM units in
the subrack one by one until the alarm is
cleared. Replace the defective unit.
CCE Configurazion or Cus- Equipment  Major
tomization Error Alarm
HWIC Hardware Incompatible Equipment  Major The plugged HW is not compatible with the
With Configuration Alarm unit configuration HW stored in the database.
You may need to change the HW or re-create
the configuration for the unit.
SWIC Software Incompatible Equipment  Major The ESW running on the unit is not compati-
With Configuration Alarm ble with the unit configuration stored in the
database. You may need to upgrade, or
downgrade the ESW, or re-create the config-
uration with the currently running ESW.
GSW General Software Equipment  Major An ESW internal error has been detected that
Alarm Alarm might inhibit the ESW from running correctly.
MFA Maintenance Function Communica-  Warning A maintenance function has been activated
Active tion Alarm by the operator.
E.g. the synchronisation condition has been
manually changed in the timing sources sta-
tus.
UNAV Unit Not Available Equipment  Critical The unit that is configured is either not
Alarm plugged or not recognized due to a failure.
NSW No Application Soft- Equipment  Major There is no application ESW installed on the
ware Alarm unit, or the application ESW has not yet fin-
ished its boot process.
UNAS Unit Not Assigned Equipment  Warning The unit is not assigned and cannot be con-
Alarm figured. To assign the unit, execute the
“Assign” command in the “Main” function of
the unit.
UIC Unit Incompatible Equipment  Major The inserted unit is not compatible with the
Alarm assigned unit.
PWRSVE Battery Power Saving Equipment  Critical Power saving is active on the unit, i.e. it is
Alarm kept in the “reset” state during battery power
backup.
EQM Equipment Malfunction Equipment  Critical
Alarm

74 EPSI1User Manual
 GUI REFERENCE

8.3 /unit-x/bridges

8.3.1 /unit-x/bridges – Main

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation, section 10.1, “Management function
«Main»“.

8.4 /unit-x/bridges/bridge-y

8.4.1 /unit-x/bridges/bridge-y – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.4.2 /unit-x/bridges/bridge-y – Configuration...

8.4.2.1 /unit-x/bridges/bridge-y – Configuration... – RSTP

Table 30: Parameters for menu unit-x: EPSI1 – Configuration –

General
Operation Parameter Range Descriptions / Details
Name Name
RSTP Priority RSTP Priority 0 ... 65535 The bridge with the lowest priority value is choosen as root
bridge in the RSTP negotiations process. Default value =
32768
RSTP Timer Hello Interval 1 ... 10 * Time interval in seconds for BPDUs sent on each port that
have RSTP enabled. Default value = 2
Forwarding Delay 4 ... 30 * Time interval in seconds spent in listening and learning states.
Default value = 15
Maximum Age 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

EPSI1User Manual 75
GUI REFERENCE

Table 30: Parameters for menu unit-x: EPSI1 – Configuration – Gen-

eral (continued)
Operation Parameter Range Descriptions / Details
Name Name
RSTP Metric Path Cost Version 802.1t (32 bits) ABB suggests using the 802.1t path cost version (default).
802.1D 1998 (16 Only for networks where the majority of the links are running
bits) with speeds of 512 kbit/s or slower the 802.1D path cost ver-
sion is recommended.

* FOXCST 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.

8.4.3 /unit-x/bridges/bridge-y – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following group is available on this AP:
• RSTP Bridge
This group contains counters:
− Nb of Topology Changes

8.4.4 /unit-x/bridges/bridge-y – Status...

8.4.4.1 /unit-x/bridges/bridge-y – Status... – RSTP

Table 31: Parameters for menu unit-x/bridges/bridge-y – Status –

RSTP
Operation Parameter Range Descriptions / Details
Name Name
Root Bridge RSTP Priority 0 ... 65535 The root bridge can be the local EPSI1 unit, another EPSI1 unit or
MAC Address some third party equipment.

76 EPSI1User Manual
 GUI REFERENCE

Table 31: Parameters for menu unit-x/bridges/bridge-y – Status –

RSTP (continued)
Operation Parameter Range Descriptions / Details
Name Name
Hello Interval All RSTP bridges in a contigous network should use the same
value for the hello interval.
Forwarding Delay Typically all RSTP bridges in a contigous network should use the
same value for the forwarding delay. Newer use a longer forward-
ing delay than the route bridge.
Maximum Age 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.
Path Cost cost from the local bridge to the root bridge
Local Bridge RSTP Priority 0 ... 61’440 The bridge with the lowest priority value is choosen as root bridge
in the RSTP negotiations process.
MAC Address The eight bridge instances on the EPSI1 unit all have their own
MAC addresses for unambiguous identification.

8.4.4.2 /unit-x/bridges/bridge-y – Status... – Bridge

Table 32: Parameters for menu unit-x/bridges/bridge-y – Status –

Bridge
Operation Parameter Range Descriptions / Details
Name Name
MAC Table 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
Ingress Interface Port, where the corresponding MAC frame was received

EPSI1User Manual 77
GUI REFERENCE

8.5 /unit-x/InternalPorts

8.5.1 /unit-x/InternalPorts – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.6 /unit-x/InternalPorts/port-1

8.6.1 /unit-x/InternalPorts/port-1 – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.6.2 /unit-x/InternalPorts/port-1 – Configuration...

8.6.2.1 /unit-x/InternalPorts/port-1 – Configuration... – Interface Assignment

Table 33: Parameters for menu /unit-x/internalports/port-1 – Configuration – Interface Assignment

Operation Parameter Range Descriptions / Details
Name Name
Interface Interface Assign- none The interface is left unassigned (default).
Assignment ment bridge-1 ... bridge-8 The interface is assigned to one of the eight available bridge
instances. The number of interfaces assigned to the same
bridge is not limited.
router The interface is assigned to the router.

78 EPSI1User Manual
 GUI REFERENCE

8.6.2.2 /unit-x/InternalPorts/port-1 – Configuration... – Bridge

Please note:
Bridge configuration for the internal port is only meaningful, if the internal
port is assigned to one of the eight bridge instances. For any other internal
port assignment, these parameters are ignored.
:

Table 34: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – Bridge
Operation Parameter Range Descriptions / Details
Name Name
VLAN Mode Mode Access Only untagged and priority tagged RX frames are accepted on an
(default) 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 This is the hybrid port with both access and trunk properties:
VLAN) - 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 mem-
bership 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.
Default VLAN ID Default 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 fil-
ter: only frames with this VLAN ID are allowed to be transmitted.
Deafault Priority Deafault Priority 0 ... 7 Untagged or priority tagged RX frames received on the port will get
this value in the priority field.

EPSI1User Manual 79
GUI REFERENCE

Table 34: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – Bridge (continued)
Operation Parameter Range Descriptions / Details
Name Name
RSTP Enabled RSTP Enabled  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 34).
RSTP Path Cost Automatic  By default EPSI1 automatically calculates port path cost from the
configured bandwidth.
Some example port path values for 802.1t-2001:
- for Ethernet port 100 Mbit/s, path cost = 200’000
- for TDM port 2 Mbit/s, path cost = 10’000’000
- for TDM port 1 Mbit/s, path cost = 20’000’000
- for TDM port 100 kbit/s, path cost = 200’000’000
 The value for path cost is retreived from the manual entry.
RSTP Path Cost ManualCost 1 ... This port path cost value is considered for the RSTP active topology
200’000’000 calculation, if above parameter «Automatic» is set to «true».
Port path cost adjustments induce the following effects:
(if the path cost - a lower value makes the port more attractive and the chance to
version is set to play an active role in the network raises
«802.1D- - a higher value makes the port less attractive and the chance to
1998», this play an active role in the network drops
range is
1 ... 65535)
Accessibility 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 36).

Please note:
For manual path cost configuration, the setting for «Path Cost Version» must
always be considered.

80 EPSI1User Manual
 GUI REFERENCE

8.6.2.3 /unit-x/InternalPorts/port-1 – Configuration... – Router

Please note:
Router configuration for the internal port is only meaningful, if the internal
port is assigned to the router. For any other internal port assignment, these
parameters are ignored.
:

Table 35: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – Router
Operation Parameter Range Descriptions / Details
Name Name
Addressing Mode Mode Numbered The internal port has its own IPv4 address.
Numbered Peer Used for PPP interfaces with no IP address exchange.
Please do not select for the internal port.
Address IP Address Any valid IPv4 Both address and mask values are subject of correct IP net-
address work design. Whether a certain address/mask combination is
IP Mask Any valid IPv4 net- valid for a certain interface is in the responsibility of the user
work mask and cannot be checked by the EPSI1 unit or by the FOXCST.

Peer Address IP Address Any valid IPv4 IP address of peer router in case of «Numbered Peer» mode.
address Not relevant for the internal port.

EPSI1User Manual 81
GUI REFERENCE

8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF

Please note:
OSPF configuration for the internal port is only meaningful, if the internal port
is assigned to the router. For any other internal port assignment, these
parameters are ignored.

Table 36: Parameters for menu /unit-x/port-1 – Configuration – OSPF

Operation Parameter Range Descriptions / Details
Name Name
OSPF Enabled OSPF Enabled  OSPF can be enabled or disabled individually for each router
 port (Default = disabled).

OSPF Mode Mode Active The usual mode to configure a OSPF router interface (default)
Passive No hello packets or LSA packets are sent or received on this
interface and no adjacencies can be built over this interface,
but the network that is connected to the interface is still adver-
tised to the AS.The passive mode is typically selected for con-
nected networks with no OSPF supporting routers.
OSPF Area Area area-1 (Backbone) The corresponding interface belongs to the selected area.
area-2 ... area-8

82 EPSI1User Manual
 GUI REFERENCE

Table 36: Parameters for menu /unit-x/port-1 – Configuration – OSPF

Operation Parameter Range Descriptions / Details
Name Name
OSPF Priority Priority 0 ... 255 The priority value is used in the negotiations process in order
Default = 128 the 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.
OSPF Authenti- Key Auth. = none: The configuration of the authentication key for a certain inter-
cation parameter n.a. face is depending on the selection for «Authentication» for the
Auth. = Simple: appropriate area.
max. 8 characters Make sure to configure identical keys for all OSPF interfaces
on a common network segment.
Auth. = MD5: max.
16 characters
OSPF Metric Automatic  By default, the metric is calculated automatically from the spec-
ified interface bandwidth: metric = 100’000 / bandwidth in kbit/s
 The OSPF metric is derived from the configured manual metric
value.
Manual Metric 1 ... 65535 The OSPF routing table calculations can be affected with man-
ual OSPF metrics. This feature should however be used by
OSPF experts only.
OSPF Timers Hello Interval 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.
Router Dead 0 ... 3600 The time before a neighbouring router is declared down after
Interval Default = 40 missing the hello packets.
Transmission 0 ... 3600 The time it takes to transmit a link state update packet over this
Delay Default = 1 interface. LSAs contained in the update packet must have
their age incremented by this amount before transmission.
Retransmission 0 ... 3600 Time interval between LSA retransmissions for adjacencies
Delay Default = 5 belonging to this interface. Also used when retransmitting
database description and link state request packets.

8.6.2.5 /unit-x/InternalPorts/port-1 – Configuration... – RIP

Please note:
RIP configuration for the internal port is only meaningful, if the internal port is
assigned to the router. For any other internal port assignment, these param-
eters are ignored.

EPSI1User Manual 83
GUI REFERENCE

Table 37: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – RIP
Operation Parameter Range Descriptions / Details
Name Name
RIP Enabled RIP Enabled  RIP can be enabled or disabled individually for each router port
 (Default = disabled).

RIP Mode Mode Active The usual mode to configure a RIP router interface (default).
Passive No RIP protocol packets are sent or received on this interface,
but the network that is connected to the interface is still adver-
tised on active interfaces.
The passive mode is typically selected for networks with no
RIP supporting routers.
RIP Metric Default Metric 0 ... 15
RIP Version And Mode None/RIPv1 Support of RIPv1 only, which implies no authentication support
Authentication None/RIPv2 Support of RIPv2 only, without authentication support
None/RIPv1 And Support of both RIPv1 and RIPv2, without authentication sup-
RIPv2 port
Simple/RIPv2 Support of RIPv2 only, authentication with plain text string
MD5/RIPv2 Support of RIPv2 only, authentication with MD5 hash
Key 0 ... 16 characters User editable text string for authentication. Any printable char-
acter is allowed. By default the string is empty.
Split Horizon Split Horizon  Split horizon inhibits sending route information back to routers,
 where it had previously been learned from (default = enabled).

84 EPSI1User Manual
 GUI REFERENCE

8.6.2.6 /unit-x/InternalPorts/port-1 – Configuration... – VRRP A/B

The EPSI1 can participate on one or two virtual routers over the same inter-
face. Therefore two parameter sets «VRRP A» and «VRRP B» are provided.
Descriptions in this section are correspondingly applicable for «VRRP A»
and «VRRP B».

Please note:
VRRP A/B configuration for the internal port is only meaningful, if the internal
port is assigned to the router. For any other internal port assignment, these
parameters are ignored.
:

Table 38: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – VRRP A/B
Operation Name Parameter Name Range Descriptions / Details
VRRP Enabled VRRP Enabled  The EPSI1 router participates over the internal port
on a virtual router.
 The VRRP function is inactive on the internal port.
Virtual Router ID Virtual Router ID 1 ... 255 Since several virtual routers can be active on the
default = 1 same LAN, each virtual router entity is identified
with the virtual router ID.
Priority Priority 0 ... 255 The router with the highest priority is selected as
default = 100 master router from all active members of a virtual
router entity.
Virtual IP Address Virtual IP Address IP address in the The virtual IP address of the virtual router entity. All
network range of router members in the same virtual router entity
the corresponding (same virtual router ID) must use the same virtual
interface IP address.
Advertise Interval Advertise Interval 1 ... 255 The time interval in seconds each virtual router
default = 1 member sends advertisements. A virtual router
member is considered as down after 3 missing
advertisements.

EPSI1User Manual 85
GUI REFERENCE

Table 38: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – VRRP A/B (continued)
Operation Name Parameter Name Range Descriptions / Details
Preemption Mode Preemption Mode  A higher priority backup router may preempt this
router as master.
 Once elected as master, this router keeps running
as master, even if a higher priority backup router is
up and running again. Only a virtual router address
owner may still overrun disabled preemption.

8.6.2.7 /unit-x/InternalPorts/port-1 – Configuration... – Ingress Rate Limiter

Table 39: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – Ingress Rate Limiter
Operation Parameter Range Descriptions / Details
Name Name
Rate Limiter Rate Limiter Ena-  By default the ingress rate limiter is disabled, i.e. the corre-
bled  sponding input bandwidth for the internal port is 1Gbit/s.

CommittedInfor- 64 kbit/s ... 100 The Commited Information Rate (CIR) when limiting is enabled
mationRate Mbit/s
CommittedBurst- 1 kB ... 256 kB The Committed Burst Size (CBS) for the limitation process,
Size 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.

86 EPSI1User Manual
 GUI REFERENCE

8.6.2.8 /unit-x/InternalPorts/port-1 – Configuration... – PHY

Table 40: Parameters for menu /unit-x/internalports/port-1 – Configu-

ration – PHY
Operation Parameter Range Descriptions / Details
Name Name
PHY Mode PHY Mode The internal port is 1Gbit/s full duplex and is not user configur-
able

8.6.3 /unit-x/InternalPorts/port-1 – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• RSTP Interface
This group contains counters:
− Out BPDUs
− In BPDUs
− Invalid BPDUs
− Forward Transitions
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors

EPSI1User Manual 87
GUI REFERENCE

8.6.4 /unit-x/InternalPorts/port-1 – Status...

8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge

Please note:
Bridge status for the internal port is only meaningful, if the port is assigned to
one of the eight bridge instances.
:

Table 41: Parameters for menu /unit-x/internalports/port-1 – Status –

Bridge
Operation Parameter Range Descriptions / Details
Name Name
RSTP RSTP Enabled  RSTP is enabled on the internal port
 RSTP is disabled on the internal port
State * Learning Transient state during topology changes for root ports and designated
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»
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

88 EPSI1User Manual
 GUI REFERENCE

Table 41: Parameters for menu /unit-x/internalports/port-1 – Status –

Bridge (continued)
Operation Parameter Range Descriptions / Details
Name Name
RSTP Designated The RSTP Designated Bridge in respect to a port denotes the bridge
Bridge Priority on the other side of the point-to-point link or the designated bridge on
Designated 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.
Effective Port The port path cost is calculated from the port bandwidth and is
Path Cost dependent on the configured path cost version. In case of manual port
path cost, this valu is equal to the configured value.

* 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
alternate port and backup port is in discarding state.

8.6.4.2 /unit-x/InternalPorts/port-1 – Status... – Router

Please note:
Router status for the internal port is only meaningful, if the port is assigned to
the router.
:

Table 42: Parameters for menu /unit-x/internalports/port-1 – Status –

Router
Operation Parameter Range Descriptions / Details
Name Name
Router If Status IP MTU Size Maximal size of transmission unit

EPSI1User Manual 89
GUI REFERENCE

8.6.4.3 /unit-x/InternalPorts/port-1 – Status... – OSPF

Please note:
The OSPF status for the internal port is only meaningful, if the port is
assigned to the router.
:

Table 43: Parameters for menu /unit-x/internalports/port-1 – Status –

OSPF
Operation Parameter Range Descriptions / Details
Name Name
OSPF Status Status Designated router This router is advertising the connected Ethernet network
Backup desig- This router is elected as backup for the advertising of the con-
nated router nected Ethernet network
Other designated This router is neither designated router nor backup designated
router router
Point-to-point There is no designated router on point-to-point links (TDM I/F)
Loopback There is no status information for the loopback I/F
Down a) OSPF is administratively disabled on the corresponding port
b) the corresponding layer 2 link is down
Designated The currently active designated router on the connected network
Router (for Ethernet ports and VLAN interfaces only)
Backup Desig- The currently active backup designated router on the network
nated Router (for Ethernet ports and VLAN interfaces only)

90 EPSI1User Manual
 GUI REFERENCE

8.6.4.4 /unit-x/InternalPorts/port-1 – Status... – VRRP A/B

The EPSI1 can participate on one or two virtual routers over the same inter-
face. Therefore two individual status menus for «VRRP A» and «VRRP B»
are provided. Descriptions in this section are correspondingly applicable for
«VRRP A» and «VRRP B».

Please note:
VRRP status for the internal port is only meaningful, if the internal port is
assigned to the router.
:

Table 44: Parameters for menu /unit-x/internalports/port-1 – Status –

VRRP A/B
Operation Parameter Range Descriptions / Details
Name Name
VRRP Status Virtual MAC MAC address of the virtual router if this interface is the VRRP
Address master. If this interface is VRRP backup, the displayed value is
meaningless.
Status Master The EPSI1 unit acts as master for the corresponding virtual
router
Backup The EPSI1 unit acts as backup for the corresponding virtual
router
Initialize Transient state
Up Time Time in seconds since the corresponding virtual router is up

EPSI1User Manual 91
GUI REFERENCE

8.7 /unit-x/loopbackInterface

The loopback interface allows the user to assign an IP address to the unit
itself, rather than to a real interface. The loopback address is used as router
ID for OSPF.

8.7.1 /unit-x/loopbackInterface – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.7.2 /unit-x/loopbackInterface – Configuration...

8.7.2.1 /unit-x/loopbackInterface – Configuration... – Interface Assignment

The EPSI1 loopback interface is always assigned to the router and the
assignment is not user configurable.

8.7.2.2 /unit-x/loopbackInterface – Configuration... – Router

Table 45: Parameters for menu /unit-x/loopbackInterface – Configura-

tion – Router
Operation Parameter Range Descriptions / Details
Name Name
Addressing Mode Numbered The loopback interface has its own IPv4 address.
Mode Numbered Peer Used for PPP interfaces with no IP address exchange.
Please do not select for the loopback interface.
Address IP Address Any valid IPv4 Any valid IP address is accepted. If the router is located in a
address non-backbone area, the address should be contained in the
configured area address range.
IP Mask Any valid IPv4 net- Typically a host mask is used for the loopback interface,
work mask though any valid network mask is accepted.
Peer Address IP Address Any valid IPv4 IP address of peer router in case of «Numbered Peer» mode;
address not relevant for the loopback interface

92 EPSI1User Manual
 GUI REFERENCE

8.7.2.3 /unit-x/loopbackInterface – Configuration... – OSPF

Table 46: Parameters for menu /unit-x/loopbackInterface – Configura-

tion – OSPF
Operation Parameter Name Range Descriptions / Details
Name
OSPF Enabled OSPF Enabled  OSPF can be enabled or disabled for the loopback
 interface (Default = disabled).

OSPF Mode Mode Active Parameter not relevant for the loopbackInterface
Passive
OSPF Area Area area-1 (Backbone) The loopbackInterface belongs to the selected area.
area-2 ... area-8
OSPF Priority Priority 0 ... 255 Parameter not relevant for the loopbackInterface
Default = 128
OSPF Authenti- Key Auth. = none: Parameter not relevant for the loopbackInterface
cation parameter n.a.
Auth. = Simple:
max. 8 characters
Auth. = MD5: max.
16 characters

EPSI1User Manual 93
GUI REFERENCE

Table 46: Parameters for menu /unit-x/loopbackInterface – Configura-

tion – OSPF (continued)
Operation Parameter Name Range Descriptions / Details
Name
OSPF Metric Automatic  Parameter not relevant for the loopbackInterface

Manual Metric 1 ... 65535
ManualMetric
OSPF Timers Hello Interval 1 ... 65535 Parameter not relevant for the loopbackInterface
Default = 10
Router Dead Interval 0 ... 3600
Default = 40
Transmission Delay 0 ... 3600
Default = 1
Retransmission Delay 0 ... 3600
Default = 5

8.7.2.4 /unit-x/loopbackInterface – Configuration... – RIP

94 EPSI1User Manual
 GUI REFERENCE

Table 47: Parameters for menu /unit-x/loopbackInterface – Configura-

tion – RIP
Operation Parameter Range Descriptions / Details
Name Name
RIP Enabled RIP Enabled  RIP can be enabled or disabled for the loopback interface
 (Default = disabled).

RIP Mode Mode Active Parameter not relevant for the loopbackInterface
Passive
RIP Metric Default Metric 0 ... 15 Parameter not relevant for the loopbackInterface
RIP Version And Mode None/RIPv1 Parameter not relevant for the loopbackInterface
Authentication None/RIPv2
None/RIPv1 And
RIPv2
Simple/RIPv2
MD5/RIPv2
Key 0 ... 16 characters Parameter not relevant for the loopbackInterface
Split Horizon Split Horizon  Parameter not relevant for the loopbackInterface


8.7.3 /unit-x/loopbackInterface – Performance Management...

N.A.

8.7.4 /unit-x/loopbackInterface – Status...

8.7.4.1 /unit-x/loopbackInterface – Status... – Router

The status menu for «Router» is the same for all interfaces. Please refer to
8.6.4.2 /unit-x/InternalPorts/port-1 – Status... – Router (on page 89).

8.7.4.2 /unit-x/loopbackInterface – Status... – OSPF

N.A.

EPSI1User Manual 95
GUI REFERENCE

8.8 /unit-x/port-r

These are the Ethernet front ports, with <r> ranging from 1 to 4.

8.8.1 /unit-x/port-r – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.8.2 /unit-x/port-r – Configuration...

8.8.2.1 /unit-x/port-r – Configuration... – Interface Assignment

Interface assignment is the same for all interfaces. Please refer to section
8.6.2.1 /unit-x/InternalPorts/port-1 – Configuration... – Interface Assignment
(on page 78).

8.8.2.2 /unit-x/port-r – Configuration... – Bridge

Please note:
Bridge configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to one of the eight bridge instances. For any
other port assignment, these parameters are ignored.
Bridge configuration is the same for all interfaces. Please refer to section
8.6.2.2 /unit-x/InternalPorts/port-1 – Configuration... – Bridge (on page 79).

96 EPSI1User Manual
 GUI REFERENCE

8.8.2.3 /unit-x/port-r – Configuration... – Router

Please note:
Router configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
:

Table 48: Parameters for menu /unit-x/port-1 – Configuration –

Router
Operation Parameter Range Descriptions / Details
Name Name
Addressing Mode Mode Numbered Each port that is assigned to the router has its own IPv4
address.
Numbered Peer Used for PPP interfaces with no IP address exchange
Address IP Address Any valid IPv4 Both address and mask values are subject of correct IP net-
address work design. Whether a certain address/mask combination is
IP Mask Any valid IPv4 net- valid for a certain interface is in the responsibility of the user
work mask and cannot be checked by the EPSI1 unit or by the FOXCST.

Peer Address IP Address Any valid IPv4 IP address of peer router in case of «Numbered Peer» mode
address

8.8.2.4 /unit-x/port-r – Configuration... – OSPF

Please note:
OSPF configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
OSPF configuration is the same for all interfaces. Please refer to section
8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF (on page 82).

EPSI1User Manual 97
GUI REFERENCE

8.8.2.5 /unit-x/port-r – Configuration... – RIP

Please note:
RIP configuration for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to the router. For any other port assignment, these
parameters are ignored.
RIP configuration is the same for all interfaces. Please refer to section
8.6.2.5 /unit-x/InternalPorts/port-1 – Configuration... – RIP (on page 83).

8.8.2.6 /unit-x/port-r – Configuration... – VRRP A/B

Please note:
VRRP A/B configuration for the corresponding Ethernet front port is only
meaningful, if the port is assigned to the router. For any other port assign-
ment, these parameters are ignored.
VRRP A/B configuration is the same for Ethernet front ports as for the inter-
nal port. Please refer to section 8.6.2.6 /unit-x/InternalPorts/port-1 – Configu-
ration... – VRRP A/B (on page 85).

98 EPSI1User Manual
 GUI REFERENCE

8.8.2.7 /unit-x/port-r – Configuration... – Ingress Rate Limiter

Table 49: Parameters for menu /unit-x/port-r – Configuration –

Ingress Rate Limiter
Operation Parameter Range Descriptions / Details
Name Name
Rate Limiter Rate Limiter Ena-  By default the ingress rate limiter is disabled, i.e. the corre-
bled  sponding input bandwidth for the Ethernet front ports is 100
Mbit/s.
CommittedInfor- 64 kbit/s ... 100 The Commited Information Rate when limiting is enabled
mationRate Mbit/s
CommittedBurst- 1 kB ... 256 kB The Committed Burst Size for the limitation process, which is
Size 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.

EPSI1User Manual 99
GUI REFERENCE

8.8.2.8 /unit-x/port-r – Configuration... – PHY

Table 50: Parameters for menu /unit-x/port-r – Configuration – PHY

Operation Parameter Range Descriptions / Details
Name Name
PHY Mode PHY Mode Autonegotiation With the LAN mode configuration an Ethernet port can be
PHYConfig PHYMode 10MbitsFullDuplex forced to work in a specific operation mode or allowing the
port to select the best mode automatically by negotiating with
10MbitsHalfDuplex the appropriate peer entity. By default the LAN mode is set to
100MbitsFullDuplex «Auto Negotiation».
100MbitsHalfDuplex

8.8.3 /unit-x/port-r – Fault Management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation. The following table lists the fault
causes for the Ethernet front ports.

Table 51: Parameters for menu unit-x/port-r – Fault management...

ID Fault Cause Event Type Traffic Moni- Default Description
Affecting tored Severity
LOS Loss Of Signal Communication Alarm   Major No input signal detected on the port

100 EPSI1User Manual

 GUI REFERENCE

8.8.4 /unit-x/port-r – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• RSTP Interface
This group contains counters:
− Out BPDUs
− In BPDUs
− Invalid BPDUs
− Forward Transitions
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors

8.8.5 /unit-x/port-r – Status...

8.8.5.1 /unit-x/port-r – Status... – Bridge

Please note:
Bridge status for the corresponding Ethernet front port is only meaningful, if
the port is assigned to one of the eight bridge instances.
The status menu for «Bridge» is the same for all interfaces. Please refer to
section 8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge (on page 88).

8.8.5.2 /unit-x/port-r – Status... – Router

Please note:
Router status for the corresponding Ethernet front port is only meaningful, if
the port is assigned to the router.
The status menu for «Router» is the same for all interfaces. Please refer to
8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF (on page 82).

EPSI1User Manual 101

GUI REFERENCE

8.8.5.3 /unit-x/port-r – Status... – OSPF

Please note:
OSPF status for the corresponding Ethernet front port is only meaningful, if
the port is assigned to the router.
The status menu for «OSPF» is the same for all Ethernet interfaces. Please
refer to 8.6.4.3 /unit-x/InternalPorts/port-1 – Status... – OSPF (on page 90).

8.8.5.4 /unit-x/port-r – Status... – VRRP A/B

Please note:
VRRP status for the corresponding Ethernet front port is only meaningful, if
the port is assigned to the router.
The status menu for «VRRP A/B» is the same for all interfaces. Please refer
to 8.6.4.4 /unit-x/InternalPorts/port-1 – Status... – VRRP A/B (on page 91).

8.8.5.5 /unit-x/port-r – Status... – PHY

Table 52: Parameters for menu /unit-x/port-r/ – Status – PHY

Operation Parameter Range Descriptions / Details
Name Name
PhyState Speed 10 Mbit/s The currently active interface speed. Can be the result of an
100 Mbit/s automatic negotiation process or user configured.

Duplex Half Duplex The currently active interface mode. Can be the result of an
Full Duplex automatic negotiation process or user configured.

IEEE802.3 Flow Flow control is not supported by EPSI1.

Control

102 EPSI1User Manual

 GUI REFERENCE

8.8.5.6 /unit-x/port-r – Status... – Interface

Table 53: Parameters for menu /unit-x// – Status – Interface

Operation Parameter Range Descriptions / Details
Name Name
MAC Address Each Ethernet front port has its own unique MAC address

EPSI1User Manual 103

GUI REFERENCE

8.9 /unit-x/router

8.9.1 /unit-x/router – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.9.2 /unit-x/router – Configuration...

8.9.2.1 /unit-x/router – Configuration... – Router

104 EPSI1User Manual

 GUI REFERENCE

Table 54: Parameters for menu /unit-x/router – Configuration –

Router
Operation Name Parameter Range Descriptions / Details
Name
OSPF Redistribute Connected  Route information for a network that is directly connected but
not enabled for OSPF is advertised to the OSPF AS.
 Route information for a network that is directly connected but
not enabled for OSPF is not advertised to the OSPF AS.
Metric 0 ... 65535 Corresponding metric for directly connected networks
Static  Static routes that are defined on the local router are distrib-
uted to the OSPF AS (default)
 Static routes from the local router are not distributed
Metric 0 ... 65535 Corresponding metric for static routes
RIP  Route information that has been learned from a connected
RIP network is distributed to the OSPF AS.
 No route information from RIP networks is distributed in the
OSPF AS.
Metric 0 ... 65535 Corresponding metric for route information from RIP networks
RIP Redistribute Connected  Route information for a network that is directly connected but
not enabled for RIP is exchanged on active RIP interfaces.
 Route information for a network that is directly connected but
not enabled for RIP is not exchanged on active RIP inter-
faces.
Metric 0 ... 15 Corresponding metric for directly connected networks
Static  Static routes that are defined on the local router are
exchanged on active RIP interfaces.
 Static routes from the local router are not exchanged
Metric 0 ... 15 Corresponding metric for static routes
OSPF  Route information that has been learned from a connected
OSPF AS is exchanged on active RIP interfaces.
 No route information from a possible OSPF AS is exchanged.
Metric 0 ... 15 Corresponding metric for route information from OSPF AS

EPSI1User Manual 105

GUI REFERENCE

8.9.2.2 /unit-x/router – Configuration... – StaticRoutes

Table 55: Parameters for menu /unit-x/router – Configuration –

StaticRoutes
Operation Name Parameter Name Range Descriptions / Details
Static Route Table IP Address Any valid IP net- The destination/mask pair unambiguously identifies an IP
IP Mask work address/net- address range, where the corresponding static route is
work mask pointing to. The default destination 0.0.0.0/0.0.0.0 con-
combination tains the whole IP address range.
Gateway IP Address valid IP address Any IP address in a directly connected network can be
specified as gateway address for a static route.
Add... Add a new item to the static route table
Remove Delete an entry from the static route table

106 EPSI1User Manual

 GUI REFERENCE

8.9.3 /unit-x/router – Status...

8.9.3.1 /unit-x/router – Status... – ARP Table

Table 56: Parameters for menu /unit-x/router/ – Status – ARP Table

Operation Parameter Range Descriptions / Details
Name Name
ARP Table IP Address The IP address/MAC address relation is the result of an ARP
MAC Address request and is valid for the LAN segment connected by the cor-
responding interface.
Interface On this interface the IP address/MAC address relation has
been learned.

EPSI1User Manual 107

GUI REFERENCE

8.9.3.2 /unit-x/router – Status... – Routing Table

Table 57: Parameters for menu /unit-x/router/ – Status – Routing

Table
Operation Parameter Name Range Descriptions / Details
Name
Routing Table Destination Address The destination address/mask pair unambiguously identifies
Destination Mask an IP address range.

Gateway Address The address, where the packets for the corresponding des-
tination are sent to.
Interface physical router The destination network is connected either to an Ethernet
interface front port or to a TDM interface.
VLAN interface The destination network is connected to a VLAN interface
loopback interface N.A.
Source connected The route is derived from the user configuration
OSPF The route is calculated from the OSPF link state data base
static The route is derived from a user configured static route

108 EPSI1User Manual

 GUI REFERENCE

8.9.3.3 /unit-x/router – Status... – Ping Command

Table 58: Parameters for menu /unit-x/router/ – Status – Ping

Command
Operation Parameter Name Range Descriptions / Details
Name
Ping Command Destination Address IPv4 address of the 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 in bytes
Do Not Fragment  The do not fragment bit in the IP header is set
 The do not fragment bit in the IP header is cleared

EPSI1User Manual 109

GUI REFERENCE

8.9.3.4 /unit-x/router – Status... – Traceroute Command

Table 59: Parameters for menu /unit-x/router/ – Status – Traceroute

Command
Operation Parameter Range Descriptions / Details
Name Name
Trace Route Destination IPv4 address of the traceroute target
Command Address
:

110 EPSI1User Manual

 GUI REFERENCE

8.10 /unit-x/router/ospf

8.10.1 /unit-x/router/ospf – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.10.2 /unit-x/router/ospf – Status...

8.10.2.1 /unit-x/router/ospf – Status... – Link State

Table 60: Parameters for menu /unit-x/router/osp – Status – Link

State
Operation Parameter Range Descriptions / Details
Name Name
OSPF Link State Area ID ID of the area, where the link state is originated
Type Router link The collected states of a router's interfaces
Network link Describe the set of routers attached to the network
Summary link 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
Age Age of the corresponding advertisement in seconds
Checksum The checksum can be used to quickly detect LSA changes

EPSI1User Manual 111

GUI REFERENCE

8.10.2.2 /unit-x/router/ospf – Status... – External Link State

Table 61: Parameters for menu /unit-x/router/ospf – Status – External

Link State
Operation Parameter Range Descriptions / Details
Name Name
External Link- Link ID Network address of the corresponding destination
State
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
cHECKSUM The checksum can be used to quickly detect LSA changes

8.10.2.3 /unit-x/router/ospf – Status... – Neighbour Table

112 EPSI1User Manual

 GUI REFERENCE

Table 62: Parameters for menu /unit-x/router/ospf – Status – Neigh-

bour Table
Operation Parameter Range Descriptions / Details
Name Name
OSPF Neighbour Neighbour ID The neighbour’s router OSPF Id
Table Priority Priority used for the designated router election
State Init Hello packets received from the neighbour, but bidirectional commu-
nication 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 designated
nor backup designated router on the corresponding Ethernet subnet.
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

8.11 /unit-x/router/ospf/area-s

Though the OSPF standard does not limit the number of areas, the EPSI1
implementation supports 8 areas, with <s> ranging from 1 to 8.

8.11.1 /unit-x/router/ospf/area-s – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

EPSI1User Manual 113

GUI REFERENCE

8.11.2 /unit-x/router/ospf/area-s – Configuration...

8.11.2.1 /unit-x/router/ospf/area-s – Configuration... – OSPF

114 EPSI1User Manual

 GUI REFERENCE

Table 63: Parameters for menu /unit-x/router/ospf/area-s – Configura-

tion – OSPF
Operation Name Parameter Range Descriptions / Details
Name
OSPF Area Enabled OSPF Area Ena-  Administrative control for the corresponding area
bled  Area-1 (backbone) is mandatory for an OSPF AS and must not
be disabled.
OSPF Area ID Area ID 0.0.0.0 For area-1 (backbone) no other ID is accepted
IPv4 address For area-2 ... area-8 any IP address value is accepted. Though
it is a standard practice to using an address that fits in the con-
figured area address range, e.g. the network address of the
first address range.
OSPF Area Type Area Type Standard 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 type 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 type instead.
Please note: All OSPF routers in the same area must agree on the same area type
OSPF Area Stub Stub Cost If the stub area has more than one area border router, the route
Cost calculation of all routers in the stub areas can be manuald with
the advertised stub cost. Meaningful for border routers only.
OSPF Area Authen- Authentication None No authentication is used in OSPF hello- and LSA-packets
tication Mode 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.
OSPF Area Ranges Enabled  Administrative control for the corresponding area address
 range

IP Address Any valid IP The address/mask pair unambiguously identifies an IP address

IP Mask network range. The specified address ranges must not overlap.
address/net-
work mask
combination
Advertise  The corresponding address range is advertised throughout the
AS.
 The corresponding address range is not advertised, it is there-
fore a hidden address range.

EPSI1User Manual 115

GUI REFERENCE

8.11.3 /unit-x/router/ospf/area-s – Status...

8.11.3.1 /unit-x/router/ospf/area-s – Status... – Link State

Table 64: Parameters for menu /unit-x/router/ospf/area-1/ – Status –

OSPF Area State
Operation Parameter Name Range Descriptions / Details
Name
OSPFAreaState Area Border Routers Number of border routers in the corresponding area
AS Routers Total number of routers in the OSPF AS
Link State Advertisements Number of entries in the OSPF link state data base
Area LSA Checksum

8.12 /unit-x/router/rip

8.12.1 /unit-x/router/rip – Main...

Please refer to 1KHW002466 FOXCST Operation.

8.12.2 /unit-x/router/rip – Status...

8.12.2.1 /unit-x/router/rip – Status... – Rip State

116 EPSI1User Manual

 GUI REFERENCE

Table 65: Parameters for menu /unit-x/router/rip – Status – RIP State

Operation Parameter Range Descriptions / Details
Name Name
Rip State Address Any valid IP address/ This IP address range as specification for a learned
Mask mask combination route information

Metric 1 ... 15 standard RIP metric range; 16 = end of network

Origin Directly Connected The network is connected to the local RIP router
<IP address value> IP address of next hop router

8.13 /unit-x/tdmInterface

8.13.1 /unit-x/tdmInterfaces – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

EPSI1User Manual 117

GUI REFERENCE

8.13.2 /unit-x/tdmInterfaces – Configuration...

8.13.2.1 /unit-x/tdmInterfaces – Configuration... – TDM

Table 66: Parameters for menu /tdmInterface – Configuration – TDM

Operation Name Parameter Name Range Descriptions / Details
Available TDM Available TDM 0 ... 64 Up to 64 TDM interfaces can be created, the allocation
Interfaces Interfaces between MACHDLC, PPP and MLPPP is up to the users
(read only) demand
Largest Available n=0 ... 32 The largest available bandwidth is oriented on the capacity
Bandwidth of an E1 link. N=32 (2048kbit/s) is usable with a P12 (trans-
parent) link. G.704 structured links offer bandwidth in the
range of n= 1... 31 (n=1 ... 30 with CAS).
Total Free Bandwidth 0 ... 16’384 kbit/s Bandwidth quote for TDM Access = 8x2 Mbit/s
0 ... 32’768 kbit/s Bandwidth quote for TDM Access = 16x2 Mbit/s
Create MAC HDLC Bandwidth P12 (Transpar- Please be aware of the different P12 handling depending
Interface ent) on the TDM access 8x2 Mbit/s or 16x2 Mbit/s. See also
section 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x 2Mbit/
s» (on page 29).
n=1 ... n=32 Bandwidth selection for TDM access = 8x2 Mbit/s
in steps of 1
n=2 ... n=32 Bandwidth selection for TDM access = 16x2 Mbit/s
in steps of 2
MAC HDLC Interface machdlc-1 ... Only unused interfaces are offered for selection
machdlc-64

118 EPSI1User Manual

 GUI REFERENCE

Table 66: Parameters for menu /tdmInterface – Configuration – TDM

Operation Name Parameter Name Range Descriptions / Details
Create PPP Inter- Bandwidth Same as for MAC HDLC interface creation
face PPP Interface ppp-1 ... ppp-64
Create MLPPP Bandwidth Same as for MAC HDLC interface creation
Interface MLPPP Interface mlppp-1 ...
mlppp-64
No Of Members 2 ... 8 Up to 8 identical ppp links can be arranged in a mlppp bun-
dle.
Delete MACHDLC MACHDLC Interface Existing MAC- The selected interface is not deleted, unless the user positi-
Interface HDLC interfaces tively acknowledges the corresponding warning message:
Delete PPP Inter- PPP Interface Existing PPP
face interfaces
Delete MLPPP MLPPP Interface Existing MLPPP
Interface interfaces

8.14 /unit-x/tdmInterfaces/machdlc-t

8.14.1 /unit-x/tdmInterface/machdlc-t – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.14.2 /unit-x/tdmInterface/machdlc-t – Configuration...

8.14.2.1 /unit-x/tdmInterface/machdlc-t – Configuration... – Interface Assignment

Interface assignment is the same for all interfaces. Please refer to section
8.6.2.1 /unit-x/InternalPorts/port-1 – Configuration... – Interface Assignment
(on page 78)).

8.14.2.2 /unit-x/tdmInterface/machdlc-t – Configuration... – Bridge

Please note:
Bridge configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to one of the eight bridge instances. For any
other port assignment, these parameters are ignored.
Bridge configuration is the same for all interfaces. Please refer to section
8.6.2.2 /unit-x/InternalPorts/port-1 – Configuration... – Bridge (on page 79).

EPSI1User Manual 119

GUI REFERENCE

8.14.2.3 /unit-x/tdmInterface/machdlc-t – Configuration... – Router

Please note:
Router configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
Router configuration is the same for all interfaces. Please refer to section
8.6.2.3 /unit-x/InternalPorts/port-1 – Configuration... – Router (on page 81).

8.14.2.4 /unit-x/tdmInterface/machdlc-t – Configuration... – OSPF

Please note:
OSPF configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
OSPF configuration is the same for all interfaces. Please refer to section
8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF (on page 82).

8.14.2.5 /unit-x/tdmInterface/machdlc-t – Configuration... – RIP

Please note:
RIP configuration for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to the router. For any other port assignment, these
parameters are ignored.
RIP configuration is the same for all interfaces. Please refer to section
8.6.2.5 /unit-x/InternalPorts/port-1 – Configuration... – RIP (on page 83).

8.14.2.6 /unit-x/tdmInterface/machdlc-t – Configuration... – TDM

Table 67: Parameters for menu /unit-x/tdmInterface/machdlc-t – Con-

figuration... – TDM
Operation Parameter Range Descriptions / Details
Name Name
Bandwidth Bandwidth 64kbit/s ... 2048 kbit/s The configured bandwidth on the interface
(read only)

120 EPSI1User Manual

 GUI REFERENCE

8.14.2.7 /unit-x/tdmInterface/machdlc-t – Configuration... – CTP

Table 68: Parameters for menu /unit-x/tdmInterface/machdlc-t – Con-

figuration... – TDM
Operation Name Parameter Name Range Descriptions / Details
CtpConfiguration Layer Rate (P0_nc | P12)
(Readonly) n 1 ... 32
Timeslot(s)
z-End Configura- RevertiveProtectionS- 
tion witching 
CAS AIS Supervision 

Switch-Over Logging 


8.14.3 /unit-x/tdmInterface/machdlc-t – Fault Management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation.

Table 69: Parameters for menu unit-x/tdmInterface/machdlc-t – fault

management...
ID Fault Cause Event Type Traffic Moni- Default Description
Affecting tored Severity
TSF Trail Signal Fail- Communication Alarm   Major The working path of a 1+1 protected link
ure is down
RTSF Redundant Trail Communication Alarm   Minor The protecting path of a 1+1 protected
Signal Failure link is down

8.14.4 /unit-x/tdmInterface/machdlc-t – Performance Management...

For detailed explanation refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• RSTP Interface

EPSI1User Manual 121

GUI REFERENCE

This group contains counters:

− Out BPDUs
− In BPDUs
− Invalid BPDUs
− Forward Transitions
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors
• Unfiltered Events
This group contains counters:
− Protection Switches

122 EPSI1User Manual

 GUI REFERENCE

8.14.5 /unit-x/tdmInterface/machdlc-t – Status...

8.14.5.1 /unit-x/tdmInterface/machdlc-t – Status... – Bridge

Please note:
Bridge status for the corresponding MAC HDLC port is only meaningful, if
the port is assigned to one of the eight bridge instances.
The status menu for «Bridge» is the same for all interfaces. Please refer to
8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge (on page 88)

8.14.5.2 /unit-x/tdmInterface/machdlc-t – Status... – Router

Please note:
Router status for the corresponding MAC HDLC port is only meaningful, if
the port is assigned to the router.
The status menu for «Router» is the same for all interfaces. Please refer to
8.6.4.2 /unit-x/InternalPorts/port-1 – Status... – Router (on page 89).

8.14.5.3 /unit-x/tdmInterface/machdlc-t – Status... – OSPF

Please note:
OSPF status for the corresponding MAC HDLC port is only meaningful, if the
port is assigned to the router.
The status menu for «Bridge» is the same for all interfaces. Please refer to
8.6.4.3 /unit-x/InternalPorts/port-1 – Status... – OSPF (on page 90).

8.14.5.4 /unit-x/tdmInterface/machdlc-t – Status... – Link

Table 70: Parameters for menu /unit-x/tdmInterface/machdlc-t – Sta-

tus – Link State
Operation Parameter Range Descriptions / Details
Name Name
Link State State Up The layer 2 protocol is up and operational
Down The layer 2 protocol is down
Unknown No state information for the layer 2 protocol available

EPSI1User Manual 123

GUI REFERENCE

8.14.5.5 /unit-x/tdmInterface/machdlc-t – Status... – CTP

Please note:
TDM cross connection is generic for all TDM service units. For more infor-
mation refer to 1KHW002467 FOX61x TDM Services.

124 EPSI1User Manual

 GUI REFERENCE

Table 71: Parameters for menu /unit-x/tdminterfaces/machdlc-t/ –

Status – CTP
Operation Parameter Range Descriptions / Details
Name Name
Trail Status Working Trail, Managed object address of the a-End Working CTP
Remote CTP
Working Trail, OK No failure on the received signal
Status SF Signal Fail status on the received signal
CAS AIS CAS AIS status in the received signal, i.e. an all ‘1’ signal
SD Signal Degraded status on the received signal
Not Available The status of the received signal is not available, e.g. when the
CTPs role is a-end in a unidirectional connection.
Protecting Trail, Managed object address of the a-End Protecting CTP
Remote CTP
Protecting Trail, OK No failure on the received signal
Status SF Signal Fail status on the received signal
CAS AIS CAS AIS status in the received signal, i.e. an all ‘1’ signal
SD Signal Degraded status on the received signal
Not Available The status of the received signal is not available, e.g. when the
CTPs role is a-end in a unidirectional connection.
Active Trail Working The trail from the a-End Working remote CTP has been selected.
Protecting The trail from the a-End Protecting remote CTP has been
selected.
Not Available There is no active trail.
External Request Request Release Automatic trail selection
Force Working Force the selector to use the trail from the a-End Working remote
CTP
Force Protecting Force the selector to use the trail from the a-End Protecting
remote CTP
Manual Working Prefer the trail from the a-End Working remote CTP - use this
trail only if the fault status is not worse than the fault status of the
protecting trail
Manual Protect- Prefer the trail from the a-End Protecting remote CTP - use this
ing trail only if the fault status is not worse than the fault status of the
working trail

EPSI1User Manual 125

GUI REFERENCE

8.15 /unit-x/tdmInterface/mlppp-u

8.15.1 /unit-x/tdmInterface/mlppp-u – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.15.2 /unit-x/tdmInterface/mlppp-u – Configuration...

8.15.2.1 /unit-x/tdmInterface/mlppp-u – Configuration... – MLPPP

Table 72: Parameters for menu /unit-x/tdmInterface/mlppp-u – Con-

figuration... – MLPPP
Operation Parameter Name Range Descriptions / Details
Name
Create Member Bandwidth P12 (Transpar- Please be aware of the different P12 handling depending
ent) on the TDM access 8x2 Mbit/s or 16x2 Mbit/s. See also
section 5.3.2 Unit mode «8 x 2Mbit/s» versus «16 x
2Mbit/s» (on page 29).
n=1 ... n=32 Bandwidth selection for TDM access = 8x2 Mbit/s
in steps of 1
n=2 ... n=32 Bandwidth selection for TDM access = 16x2 Mbit/s
in steps of 2
Unused MLPPP Members member-1 ... Selection list of all unused MLPPP members
member-64
Delete Member Used Members Selection list of all currently configured MLPPP members

126 EPSI1User Manual

 GUI REFERENCE

8.15.2.2 /unit-x/tdmInterface/mlppp-u – Configuration... – Interface Assignment

Interface assignment is the same for all interfaces. Please refer to section
8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge (on page 88).

8.15.2.3 /unit-x/tdmInterface/mlppp-u – Configuration... – Bridge

Please note:
Bridge configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to one of the eight bridge instances. For any
other port assignment, these parameters are ignored.
Bridge configuration is the same for all interfaces. Please refer to section
8.6.2.2 /unit-x/InternalPorts/port-1 – Configuration... – Bridge (on page 79).

8.15.2.4 /unit-x/tdmInterface/mlppp-u – Configuration... – Router

Please note:
Router configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
Router configuration is the same for all interfaces. Please refer to section
8.6.2.3 /unit-x/InternalPorts/port-1 – Configuration... – Router (on page 81).

8.15.2.5 /unit-x/tdmInterface/mlppp-u – Configuration... – OSPF

Please note:
OSPF configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
OSPF configuration is the same for all interfaces. Please refer to section
8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF (on page 82).

8.15.2.6 /unit-x/tdmInterface/mlppp-u – Configuration... – RIP

Please note:
RIP configuration for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to the router. For any other port assignment, these
parameters are ignored.
RIP configuration is the same for all interfaces. Please refer to section
8.6.2.5 /unit-x/InternalPorts/port-1 – Configuration... – RIP (on page 83).

8.15.3 /unit-x/tdmInterface/mlppp-u – Fault Management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation. The following table lists the fault
causes for the ML PPP ports.

EPSI1User Manual 127

GUI REFERENCE

Table 73: Parameters for menu unit-x/tdmInterface/mlppp-u – Fault

management...
ID Fault Cause Event Type Traffic Moni- Default Description
Affecting tored Severity
LOS Loss Of Signal Communication Alarm   Major ML PPP link down
BAR Bandwidth Quality Of Service   Warning One or several ML PPP member links
Reduced Alarm down

8.15.4 /unit-x/tdmInterface/mlppp-u – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• RSTP Interface
This group contains counters:
− Out BPDUs
− In BPDUs
− Invalid BPDUs
− Forward Transitions
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors

8.15.5 /unit-x/tdmInterface/mlppp-u – Status...

8.15.5.1 /unit-x/tdmInterface/mlppp-u – Status... – Bridge

Please note:
Bridge status for the corresponding MLPPP port is only meaningful, if the
port is assigned to one of the eight bridge instances.
The status menu for «Bridge» is the same for all interfaces. Please refer to
8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge (on page 88).

128 EPSI1User Manual

 GUI REFERENCE

8.15.5.2 /unit-x/tdmInterface/mlppp-u – Status... – Link

Table 74: Parameters for menu /unit-x/tdminterfaces/mlppp-u/ – Sta-

tus – Bundle State
Operation Parameter Name Range Descriptions / Details
Name
Bundle State Link State Up The layer 2 protocol is up and operational
Down The layer 2 protocol is down
Unknown No state information for he layer 2 protocol available
Members Number of members according to the user configuration
Members Currently Up Number of members that are currently up and running
Maximum Recon-
structed ReceiveUnit

8.15.5.3 /unit-x/tdmInterface/mlppp-u – Status... – Router

Please note:
Router status for the corresponding MLPPP port is only meaningful, if the
port is assigned to the router.
The status menu for «Router» is the same for all interfaces. Please refer to
8.6.4.2 /unit-x/InternalPorts/port-1 – Status... – Router (on page 89).

8.15.5.4 /unit-x/tdmInterface/mlppp-u – Status... – OSPF

Please note:
OSPF status for the corresponding MLPPP port is only meaningful, if the
port is assigned to the router.
The status menu for «Router» is the same for all interfaces. Please refer to
8.6.4.3 /unit-x/InternalPorts/port-1 – Status... – OSPF (on page 90).

EPSI1User Manual 129

GUI REFERENCE

8.16 /unit-x/tdmInterface/mlppp-u/member-v

8.16.1 /unit-x/tdmInterface/mlppp-u/member-v – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.16.2 /unit-x/tdmInterface/mlppp-u/member-v – Configuration...

8.16.2.1 /unit-x/tdmInterface/mlppp-u/member-v – Configuration... – TDM

TDM configuration is the same for all TDM interfaces. Please refer to section
8.14.2.6 /unit-x/tdmInterface/machdlc-t – Configuration... – TDM (on
page 120).

8.16.2.2 /unit-x/tdmInterface/machdlc-t – Configuration... – CTP

CTP configuration is the same for all CTP interfaces. Please refer to section
8.14.2.7 /unit-x/tdmInterface/machdlc-t – Configuration... – CTP (on
page 121).

8.16.3 /unit-x/tdmInterface/mlppp-u/member-v – Fault Management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation. The following table lists the fault
causes for the ML PPP ports.

Table 75: Parameters for menu unit-x/tdmInterface/mlppp-u/member-

v – Fault management...
ID Fault Cause Event Type Traffic Moni- Default Description
Affecting tored Severity
LOS Loss Of Signal Communication Alarm   Major ML PPP member link down
TSF Trail Signal Communication Alarm   Major The working path of a 1+1 protected
Failure link is down
RTSF Redundant Communication Alarm   Minor The protecting path of a 1+1 protected
Trail Signal link is down
Failure

130 EPSI1User Manual

 GUI REFERENCE

8.16.4 /unit-x/tdmInterface/mlppp-u/member-v – Performance

Management...
For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors
• Unfiltered Events
This group contains counters:
− Protection Switches

8.16.5 /unit-x/tdmInterface/mlppp-u/member-v – Status...

8.16.5.1 /unit-x/tdmInterface/mlppp-u/member-v – Status... – Link

Link state is the same for all TDM interfaces. Please refer to section 8.14.5.4
/unit-x/tdmInterface/machdlc-t – Status... – Link (on page 123).

8.16.5.2 /unit-x/tdmInterface/mlppp-u/member-v – Status... – CTP

CTP state is the same for all TDM interfaces. Please refer to section
8.14.5.5 /unit-x/tdmInterface/machdlc-t – Status... – CTP (on page 124).

8.17 /unit-x/tdmInterface/ppp-w

8.17.1 /unit-x/tdmInterface/ppp-w – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.17.2 /unit-x/tdmInterface/ppp-w – Configuration...

8.17.2.1 /unit-x/tdmInterface/ppp-w – Configuration... – Interface Assignment

Interface assignment is the same for all interfaces. Please refer to section
8.6.2.1 /unit-x/InternalPorts/port-1 – Configuration... – Interface Assignment
(on page 78).

EPSI1User Manual 131

GUI REFERENCE

8.17.2.2 /unit-x/tdmInterface/ppp-w – Configuration... – Bridge

Please note:
Bridge configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to one of the eight bridge instances. For any
other port assignment, these parameters are ignored.
Bridge configuration is the same for all interfaces. Please refer to section
8.6.2.2 /unit-x/InternalPorts/port-1 – Configuration... – Bridge (on page 79).

8.17.2.3 /unit-x/tdmInterface/ppp-w – Configuration... – Router

Please note:
Router configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
Router configuration is the same for all interfaces. Please refer to section 8
8.6.2.3 /unit-x/InternalPorts/port-1 – Configuration... – Router (on page 81).

8.17.2.4 /unit-x/tdmInterface/ppp-w– Configuration... – OSPF

Please note:
OSPF configuration for the corresponding Ethernet front port is only mean-
ingful, if the port is assigned to the router. For any other port assignment,
these parameters are ignored.
OSPF configuration is the same for all interfaces. Please refer to section
8.6.2.4 /unit-x/InternalPorts/port-1 – Configuration... – OSPF (on page 82).

8.17.2.5 /unit-x/tdmInterface/ppp-w – Configuration... – RIP

Please note:
RIP configuration for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to the router. For any other port assignment, these
parameters are ignored.
RIP configuration is the same for all interfaces. Please refer to section
8.6.2.5 /unit-x/InternalPorts/port-1 – Configuration... – RIP (on page 83).

8.17.2.6 /unit-x/tdmInterface/ppp-w – Configuration... – TDM

TDM configuration is the same for all TDM interfaces. Please refer to section
8.14.2.6 /unit-x/tdmInterface/machdlc-t – Configuration... – TDM (on
page 120).

8.17.2.7 /unit-x/tdmInterface/ppp-w – Configuration... – CTP

CTP configuration is the same for all CTP interfaces. Please refer to section
8.14.2.7 /unit-x/tdmInterface/machdlc-t – Configuration... – CTP (on
page 121).

132 EPSI1User Manual

 GUI REFERENCE

8.17.3 /unit-x/tdmInterface/ppp-w – Fault Management...

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation. The following table lists the fault
causes for PPP ports.

Table 76: Parameters for menu unit-x/tdmInterface/ppp-w – Fault

management...
ID Fault Cause Event Type Traffic Moni- Default Description
Affecting tored Severity
LOS Loss Of Signal Communication Alarm   Major ML PPP member link down
TSF Trail Signal Communication Alarm   Major The working path of a 1+1 protected
Failure link is down
RTSF Redundant Communication Alarm   Minor The protecting path of a 1+1 protected
Trail Signal link is down
Failure

8.17.4 /unit-x/tdmInterface/ppp-w – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• RSTP Interface
This group contains counters:
− Out BPDUs
− In BPDUs
− Invalid BPDUs
− Forward Transitions
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors
• Unfiltered Events
This group contains counters:
− Protection Switches

EPSI1User Manual 133

GUI REFERENCE

8.17.5 /unit-x/tdmInterface/ppp-w – Status...

8.17.5.1 /unit-x/tdmInterface/ppp-w – Status... – Bridge

Please note:
Bridge status for the corresponding PPP port is only meaningful, if the port is
assigned to one of the eight bridge instances.
The status menu for «Bridge» is the same for all interfaces. Please refer to
8.6.4.1 /unit-x/InternalPorts/port-1 – Status... – Bridge (on page 88).

8.17.5.2 /unit-x/tdmInterface/ppp-w – Status... – Router

Please note:
Router status for the corresponding PPP port is only meaningful, if the port is
assigned to the router.
The status menu for «Router» is the same for all interfaces. Please refer to
8.6.4.2 /unit-x/InternalPorts/port-1 – Status... – Router (on page 89).

8.17.5.3 /unit-x/tdmInterface/ppp-w – Status... – OSPF

Please note:
OSPF status for the corresponding PPP port is only meaningful, if the port is
assigned to the router.
The status menu for «OSPF» is the same for all interfaces. Please refer to
8.6.4.3 /unit-x/InternalPorts/port-1 – Status... – OSPF (on page 90).

8.17.5.4 /unit-x/tdmInterface/ppp-w – Status... – Link

Link state is the same for all TDM interfaces. Please refer to section
8.14.5.4 /unit-x/tdmInterface/machdlc-t – Status... – Link (on page 123).

8.17.5.5 /unit-x/tdmInterface/ppp-w – Status... – CTP

CTP state is the same for all TDM interfaces. Please refer to section 8.14.5.5
/unit-x/tdmInterface/machdlc-t – Status... – CTP (on page 124).

134 EPSI1User Manual

 GUI REFERENCE

8.18 /unit-x/vlanInterfaces

8.18.1 /unit-x/vlanInterfaces – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.18.2 /unit-x/vlanInterfaces – Configuration...

8.18.2.1 /unit-x/vlanInterfaces – Configuration... – VLAN

Table 77: Parameters for menu /vlaninterfaces – Configuration... –

VLAN
Operation Parameter Range Descriptions / Details
Name Name
Create VLAN VLAN Device port-1 ... port-4 Ethernet front ports:
Interface - ports that are not assigned may be connected to a VLAN
interface
- ports that are assigned to the router may be connected to a
VLAN interface
- ports that are assigned to a bridge must NOT be connected
to a VLAN interface
bridge-1 ... bridge-8 Bridge instances may always be connected to a VLAN inter-
face.
VLAN ID 1 ... 4094 RX frames for the VLAN interface come from the router and
are always untagged. They get a VLAN tag with this VLAN ID
(Default =1).
Only TX frames with a matching VLAN ID are destined for that
VLAN interface and forwarded to the router.
VLAN Interface vif-1 ... vif-32 Up to 32 VLAN interfaces can be configured.

EPSI1User Manual 135

GUI REFERENCE

Table 77: Parameters for menu /vlaninterfaces – Configuration... –

VLAN (continued)
Operation Parameter Range Descriptions / Details
Name Name
DeleteVLANIn- VLAN Interface currently config- The selected VLAN interface is not deleted, unless the user
terface VLANInter- ured VLAN inter- posititively acknowledges the corresponding warning message:
DeleteV- face faces
LANInter-
face

136 EPSI1User Manual

 GUI REFERENCE

8.19 /unit-x/vlanInterfaces/vif-z

8.19.1 /unit-x/vlanInterfaces/vif-z – Main...

For the «Main» management function description, please refer to
1KHW002466 FOXCST Operation.

8.19.2 /unit-x/vlanInterfaces/vif-z – Configuration...

8.19.2.1 /unit-x/vlanInterfaces/vif-z – Configuration... – Interface Assignment

Interface assignment is the same for all interfaces. Please refer to section
8.6.2.1 /unit-x/InternalPorts/port-1 – Configuration... – Interface Assignment
(on page 78).

8.19.2.2 /unit-x/vlanInterfaces/vif-z – Configuration... – Router

Router configuration for a VLAN interface is the same as for an Ethernet

interface. Please refer to section 8.6.2.3 /unit-x/InternalPorts/port-1 – Config-
uration... – Router (on page 81).

8.19.2.3 /unit-x/vlanInterfaces/vif-z – Configuration... – OSPF

OSPF configuration for a VLAN interface is the same as for an Ethernet

interface. Please refer to section 8.6.2.4 /unit-x/InternalPorts/port-1 – Config-
uration... – OSPF (on page 82).

8.19.2.4 /unit-x/vlanInterfaces/vif-z – Configuration... – RIP

RIP configuration for a VLAN interface is the same as for an Ethernet inter-
face. Please refer to section 8.6.2.5 /unit-x/InternalPorts/port-1 – Configura-
tion... – RIP (on page 83).

8.19.2.5 /unit-x/vlanInterfaces/vif-z – Configuration... – VRRP A/B

VRRP A/B configuration for a VLAN interface is the same as for an Ethernet
interface. Please refer to section 8.6.2.6 /unit-x/InternalPorts/port-1 – Config-
uration... – VRRP A/B (on page 85).

EPSI1User Manual 137

GUI REFERENCE

8.19.3 /unit-x/vlanInterfaces/vif-z – Performance Management...

For a detailed explanation of the FOXCST PM commands and properties
please refer to 1KHW002466 FOXCST Operation.
The following groups are available on this AP:
• MIB-2 Interface Table
This group contains counters:
− In Octets
− In Packets
− In Discards
− In Errors
− Out Octets
− Out Packets
− Out Discards
− Out Errors

8.19.4 /unit-x/vlanInterfaces/vif-z – Status

8.19.4.1 /unit-x/vlanInterfaces/vif-z – Status – OSPF

The status menu for «OSPF» is the same for the VLAN interfaces as for the
Ethernet interfaces. Please refer to /unit-x/InternalPorts/port-1 – Status... –
OSPF.

8.19.4.2 /unit-x/vlanInterfaces/vif-z – Status – VRRP A/B

The status menu for «VRRP A/B» is the same for the VLAN interfaces as for
the Ethernet interfaces. Please refer to 8.6.4.4 /unit-x/InternalPorts/port-1 –
Status... – VRRP A/B (on page 91).

138 EPSI1User Manual

 ANNEX

9 Annex
9.1 Associated documents

1KHW028514 FOX61x Terms and Abbreviations

1KHW002497 FOX61x Precautions and Safety
1KHW002459 FOX61x Release Notes
1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002463 FOX61x Lightning Protection
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002467 FOX61x TDM Services
1KHW002468 FOX61x Ethernet Services
1KHW002469 FOX61x CESM1
1KHW002470 FOX61x LESU1
1KHW002471 FOX61x ETOP1
1KHW002472 FOX61x ELET1
1KHW002473 FOX61x LEDE1
1KHW002474 FOX61x DATI1
1KHW002475 FOX61x EPSI1
1KHW002476 FOX61x SAMO1
1KHW002477 FOX61x SAMO2
1KHW002478 FOX61x LEDS1
1KHW002479 FOX61x LEDA1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1
1KHW002498 FOX61x Electrical Cables

EPSI1User Manual 139

ANNEX

140 EPSI1User Manual

Contact us

ABB Switzerland Ltd

1KHW002475 © Copyright 2012 ABB. All rights reserved.

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: utility.communication@ch.abb.com

www.abb.com/utilitycommunication