Etag1 Um

User Manual
ETAG1
etag1_r2c
Bridging/routing for Ethernet and TDM
XMC20
XMC20
ETAG1 User Manual
Copyright and Confidentiality Copyright in this document vests in KEYMILE. This document contains confi-
dential information which is the property of KEYMILE. It must be held in con-
fidence by the recipient and may not be used for any purposes except those
specifically authorised by contract or otherwise in writing by KEYMILE. This
document may not be copied in whole or in part, or any of its contents dis-
closed by the recipient to any third party, without the prior written agreement
of KEYMILE.
Disclaimer KEYMILE has taken reasonable care in compiling this document, however
KEYMILE 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.
KEYMILE reserves the right to amend this document at any time without
prior notice.
Document PEC EN/LZTBU 372 121/1 RA
Document release XMC20 R6A | 27. April 2015
Published by KEYMILE
http://www.keymile.com
User Manual
ETAG1
Table of Content
1 Preface 7
1.1 Precautions and safety 7
1.2 Symbols and notations 7
1.3 Interfaces and circuit categories 7
1.4 Document history 8
2 Introduction 9
2.1 Functions and features overview 9
2.2 ETAG1 architectural block diagram 11
2.3 Unit view 12
3 Specification 13
3.1 Feature licences 13
3.2 Physical interfaces 13
3.3 Logical interface functions 15
3.4 Networking functions 16
3.5 Protection 18
3.6 Environment 19
3.7 Summary of standards 20
4 Installation 22
4.1 Prerequisites 22
4.2 Slots for the ETAG1 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
© KEYMILE April 2015 page 3 of 163 EN/LZTBU 372 121/1 RA

User Manual
ETAG1
5.3 TDM WAN interfaces (PBUS connections) 29

5.4 Bridging functions 32
5.5 Routing functions 38
5.6 Interface stacks 49
5.7 Multilink PPP interface 54
5.8 VLAN Interfaces 56
5.9 QoS 60
6 Commissioning 68
6.1 Commissioning steps 68
7 Operation and Maintenance 69

7.1 General operation recommendations 69
7.2 Unit optical indicators 70
7.3 Maintenance 71
8 GUI Reference 75
8.1 Introduction 75
8.2 AP: / unit-x 79
8.3 AP: / unit-x / bridges 86
8.4 AP: / unit-x / bridges / bridge-y 87
8.5 AP: / unit-x / loopbackInterface 91
8.6 AP: / unit-x / port-r 97
8.7 AP: / unit-x / router 113
8.8 AP: / unit-x / router / ospf 120
8.9 AP: / unit-x / router / ospf / area-s 122
8.10 AP: / unit-x / router / rip 126
8.11 AP: / unit-x / tdmInterfaces 127
8.12 AP: / unit-x / tdmInterfaces / machdlc-t 130
8.13 AP: / unit-x / tdmInterfaces / mlppp-u 138
8.14 AP: / unit-x / tdmInterfaces / mlppp-u / member-v 143

User Manual
ETAG1
8.15 AP: / unit-x / tdmInterfaces / ppp-w 146

8.16 AP: / unit-x / vlanInterfaces 151
8.17 AP: / unit-x / vlanInterfaces / vif-z 153
8.18 AP: / unit-x / internalPorts 156
8.19 AP: / unit-x / internalPorts / port-1 157
9 Annex 162
9.1 Associated XMC20 documents 162
9.2 Technical support 162
9.3 Product training 163

User Manual
ETAG1
Figures
Figure 1: Functional block diagram 9

Figure 2: ETAG1 architectural block diagram 11
Figure 3: ETAG1 unit view 12
Figure 4: ETAG1 front view with RJ-45 pin assignment 24
Figure 5: Ethernet link LEDs on the ETAG1 unit 25
Figure 6: Side view of the XMC25 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 34
Figure 9: Example bridged network with meshed topography 35
Figure 10: Active tree topology of the same network 35
Figure 11: Example application with multiple bridge instances 36
Figure 12: Example star bridging application 37
Figure 13: Interconnecting networks 39
Figure 14: Redistribution of static routes 40
Figure 15: Redistribution example 43
Figure 16: IP host connected to redundant gateway routers 43
Figure 17: IP host logically connected to a virtual router 44
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 48
Figure 22: Generic stack model 49
Figure 23: Omitted encapsulation type 49
Figure 24: Connection of LineRunner DTM to 3rd party Bridge 50
Figure 25: Stack details for ETAG1 bridging applications 51
Figure 26: Stack details for ETAG1 bridging applications (continued) 52
Figure 27: Stack details for ETAG1 routing applications 53
Figure 28: Block diagram and stacks for Multilink PPP 54
Figure 29: Connecting Ethernet LAN interfaces to the router 56
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 58
Figure 33: The VLAN interface connects between bridging and routing 58
Figure 34: Frame handling for QoS in ETAG1 61
Figure 35: PBUS access with ETAG1 EQP 63
Figure 36: GbE access with ETAG1 EQP 63
Figure 37: Fault indication LEDs on the ETAG1 unit 70
Figure 38: MOM (managed object model) of the ETAG1 unit 76

Preface User Manual
ETAG1
1 Preface
1.1 Precautions and safety
Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety
requirements as defined in EN 60950 (Safety of Information Technology
Equipment).
Please refer to the following document:
[202] Safety Instructions “Precautions and safety”.
1.2 Symbols and notations
This User Manual uses the following symbols:
NOTICE Non-observance could result in minor or moderate injury.

A further description is added to describe the details of the hazard.
→ Possible actions are given as in this paragraph.
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

ETAG1 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

163
Preface User Manual
ETAG1
1.4 Document history
Table 2: Document history

KEYMILE PEC Date XMC20 Changes since previous version
Release
EN/LZTBU 372 121 RD 2015-02-27 R4C First revision for current system release.
EN/LZTBU 372 121/1 RD 2015-03-27 R6A Updated version for the current system release.
Added operation in XMC22.
Internal GbE port reworked.

163
Introduction User Manual
ETAG1
2 Introduction
2.1 Functions and features overview
The ETAG1 is a versatile networking unit with the main purpose of connect-
ing Ethernet LANs over TDM links. Therefore the ETAG1 supports a variety
of powerful functions and features.
1GbE access
Front Connector
2x1 GbE Internal 1 …4
Ethernet
interface 4x10/1
Ethernet
Bridge
interface
virtual
interfaces
PBUS access
1 … 64
16x2 Mbit/s TDM WAN

interface
P0_nc or P12
Router
Host processor
kplane access
Subrack internal Optical

Alarm Alarm ind
communication (2 LEDs)
Figure 1: Functional block diagram
• Functions of the internal port

− 1+1 protected connection to the COGEx 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 8x2Mbit/s or 16x2Mbit/s depending on unit mode
− PPP/HDLC user configurable
− Multilink PPP

163
ETAG1
• Functions of the interface

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

163
ETAG1
2.2 ETAG1 architectural block diagram
GbE star
2x1 GbE GbE Fast
PHYs 4 x Fast
Ethernet
Ethernet
PHYs
Network
Processor
SD
16x2 Mbit/s
PBUS
PBUS
RAM
access
Primary
Power Input
Power Supply
Figure 2: ETAG1 architectural block diagram
• Network processor
The network processor is the heart of the unit. It provides packet forward-
ing for bridging and routing and also handles control protocols and man-
agement 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 2Mbit/s” the ETAG1 behaviour follows the
standard XMC20 PBUS specification. It allows for P0nc connections
(n = 1 … 32) and P12x (transparent) connections.
− For “TDM Access” = “16 x 2Mbit/s” the ETAG1 deserves great care
for the NEs clock synchronisation. For details see paragraph 5.3.2
Unit mode “8 x 2Mbit/s” versus “16 x 2Mbit/s” (on page 29). The con-
nection 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 ETAG1 unit draws its power exclusively from the non stabilized pri-
mary power. The power supply provides the classic +5V and several
lower voltages according to the boards need.
All secondary voltages are ramped up and down in a controlled way.

163
ETAG1
2.3 Unit view
Figure 3: ETAG1 unit view
Figure 3 shows the ETAG1 unit hardware. On the front plate are two LEDs
for the unit- and traffic failure indication. The four Ethernet interfaces use
standard RJ-45 connectors.

163
Specification User Manual
ETAG1
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
FL_Swit Lic ETAG1 Switching MLPPP XMC20 Feature Licence for switching and MLPPP functionality
for ETAG1
FL_Rout Lic ETAG1 OSPF Routing XMC20 Feature Licence for OSPF Routing and VRRP func-
tionality with ETAG1
For more information on features licences please refer to [915] Technical

Bulletin “Feature Licences for XMC20”.
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

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

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

Administrative state enable/disable IEEE 802.3-2005
Speed 10/100 Mbit/s
Port mode half-duplex
full-duplex
Ingress rate limiter enabled/disabled
committed information rate
committed burst size
Ethernet MTU frame size (bridging) max. 1600 bytes
IP MTU frame size (routing) 1500 bytes
Table 6: PBUS ports (backplane)

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
Ethernet MTU frame size (bridging) max. 1600 bytes
IP MTU frame size (routing) 1500 bytes

163
ETAG1
3.3 Logical interface functions
Table 7: Parameters, user configurable per interface

Supported layer 2 protocols for TDM interfaces PPP RFC 1661
Multilink PPP RFC 1990
MAC/PPP RFC1638
MAC/HDLC encapsulation
IP/PPP RFC 1332
Supported IP addressing modes for TDM inter- numbered
faces numbered with peer
Interface assignment, i.e. appropriate interface router
networking function bridge-1 … bridge-8
Table 8: Parameters for virtual interfaces

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

163
ETAG1
3.4 Networking functions
Table 9: OSI layer 2 data forwarding (bridging)

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)

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 interface RFC 3768
(VRRP A and VRRP B)
Dedicated loopback interface valid IP address
Table 11: OSPF

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

163
ETAG1
Table 11: OSPF (continued)

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

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
Table 13: VRRP; two virtual routers, A and B

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

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

163
ETAG1
3.5 Protection
Table 15: Protection

Equipment protection supported
- Switching type 1:1 equipment protection
- Protection mode non revertive
- Switching time MAC/HDLC PBUS or internal GbE port back-
plane connection: 1
< 6s with manual or forced switching
< 9s with removal of the active unit
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
1. Additionally some more time is needed to establish the connection depending on used protocol on layer 2 (PPP, ML-
PPP) and layer 3 (e.g. OSPF, RIP).

163
ETAG1
3.6 Environment
Table 16: Power consumption

Power supply range VBAT refer to [201] System Description “XMC20 R6A”
Maximum current consumption, IVBAT 200 mA
VBAT = -48 V
Maximum power requirement from battery, PTOT 10 W
VBAT = nominal voltage
Table 17: Mechanical parameters

Construction practice 19 inch
Height of unit (1 HU = 44.45 mm) 6 HU
Width of unit (1 HP = 5.08 mm) 4 HP (1 slot)
Size of the PCB (H x D) 233 mm x 220 mm
Weight 440 grams
RoHS Directive 2002/95/EC of the European Parlia-
ment and of the Council of 27.1.2003 on the
Restriction of the use of certain hazardous sub-
stances in electrical and electronic equipment
WEEE Directive 2002/96/EC of the European Parlia-
ment and of the Council of 27.1.2003 on waste
electrical and electronic equipment
Table 18: Reliability

Calculated MTTF at 35 °C 88 years MIL-HDBK-217F
Table 19: Environmental

Emission refer to [201] System Description “XMC20 R6A”
Immunity refer to [201] System Description “XMC20 R6A”
Safety refer to [201] System Description “XMC20 R6A”
Ambient conditions refer to [201] System Description “XMC20 R6A”

163
ETAG1
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

163
ETAG1
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) procedures -
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)

163
Installation User Manual
ETAG1
4 Installation
4.1 Prerequisites
4.1.1 Installation precautions
Before installing an ETAG1 unit take care to follow the safety advice as listed
in [202] Safety Instructions “Precautions and safety”.
NOTICE Electrostatic discharges. Risk of equipment damage!

Keep the ETAG1 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 electrostatic charges.
For the installation of XMC20 HW refer to [301] User Guide “XMC25 Installa-
tion” [310] User Guide “XMC23 Installation” or [322] User Guide “XMC22
Installation”.
4.1.2 Unit embedded software (ESW)
The ETAG1 unit runs on dedicated embedded software (ESW). This ESW is
labelled e.g. etag1_r2c_r2a02.
Valid combinations of hardware (HW) and ESW versions are given in [012]
Release Note “XMC20 System Release R6A”.
The software included in this product contains copyrighted software that is
licensed under the GPL.
For further information and GPL license conditions please refer to [090]
Open Source Software declaration.

163
ETAG1
4.2 Slots for the ETAG1 unit
The ETAG1 unit uses one slot in the XMC20 subrack.

In a XMC20, the ETAG1 unit can be operated in any of the following slots:
• XMC25: 1 … 10, 12 … 21.
• XMC23: 7 … 10, 12 … 14.
• XMC22: 9, 10, 12.
Slot 11 is reserved for the working COGEx unit.
For more information regarding the PBUS access and the cross connections
refer to [314] User Guide “TDM Services and Cross Connections in XMC20”.

163
ETAG1
4.3 Connections and Cables
4.3.1 Connectors and signals
The ETAG1 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.
ETAG1 R1A
47900 xxx
port-4
pin 1
pin 8
port-3
Pin MDI MDI-X

port-2 1 Tx+ Rx+
2 Tx- Rx-
3 Rx+ Tx+
4
5
port-1 6 Rx- Tx-
7
8
Figure 4: ETAG1 front view with RJ-45 pin assignment
Each Ethernet interface provides two LEDs indicating the link state and the
link activity:

163
ETAG1
Activity
Link
Figure 5: Ethernet link LEDs on the ETAG1 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 ETAG1 implement automatic crossover
functionality.
According to the Ethernet link speed, the following cable categories have to
be used:
Table 20: Ethernet media types

IEEE Standard Distance Media Type
10BASE-T 100m Category 3 UTP or better
100BASE-TX 100m Category 5 UTP or better
Please note:
The above cables can be ordered directly from KEYMILE

163
ETAG1
4.4 Fixing the cables to the cable tray
The optical or electrical cables must be attached to the cable tray of the
XMC25 or the corresponding devices of the XMC23/XMC22.
The open cable shields must be in contact with the XMC20 grounding bar
and should be fixed to the cable tray or the corresponding devices in the
XMC23/XMC22.
The figure below shows the cable/cable tray assembly of the XMC25. With
the XMC23/XMC22 the cable tray functionality is implemented differently and
depends on the type of installation (rack-, wall-mounted).
120 mm
xx mm
Figure 6: Side view of the XMC25 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.

163
Functional Description User Manual
ETAG1
5 Functional Description
5.1 Overview
From the interface point of view the ETAG1 is designed to interconnect

Ethernet LANs via TDM links. The two supported interface types on the
physical layer are:
• Ethernet LAN interfaces according to IEEE 802.3 2008;
• TDM WAN interfaces (PBUS connections) according to ITUT G.703 and
ITUT G.704.
The main networking functions of the ETAG1 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 paragraph 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.

163
ETAG1
5.2 Ethernet LAN interfaces
5.2.1 Ethernet front ports
ETAG1 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
− 100Mbit/s full duplex
− 100Mbit/s half duplex
− 10Mbit/s full duplex
− 10Mbit/s half duplex
• Ingress rate limiter
Range 64 kbit/s … 100 Mbit/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 ETAG1 unit is one of the service unit which is only partially integrated in
the chassis switch. It appears in the chassis switch via their internal back-
plane port on the core unit. The internal GbE port connects the ETAG1 to the
chassis switch via the double GbE star on the backplane, i.e. to an internal
Ethernet port on the COGE5 unit. In order to connect both to the working
and to a possible protecting COGE5, 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 switch-over functions are automatically han-
dled by the system.
E.g. a ETAG1 unit plugged in slot-8 of the XMC20 subrack accesses the
internal COGE5 ports at the APs /unit-11/iports/iport-5 (working COGE5 unit)
and /unit-13/iports/iport-8 (protecting COGE5 unit).
For more information related to non fully integrated units and for a detailed
configuration description please refer to [356] User Manual “Ethernet Switch-
ing” and [341] Quick Guide “Ethernet Switching”.

Although the connection on the standby COGEx unit is deactivated the inter-
nal port configuration on active and standby COGEx have to be identical on
the chassis switch configuration and must me done by hand. Additionally
take care to avoid inconsistent networks between the ETAG1 and COGEx
switching functions. For valid configurations please refer to the figures in
section 5.4.1 VLAN MAC transparent bridging (on page 32), 5.4.3 RSTP (on
page 34).

163
ETAG1
5.3 TDM WAN interfaces (PBUS connections)
The PBUS is a XMC20 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 with-
out CAS. For the main characteristics and detailed explanations of the PBUS
please refer to [314] User Guide “TDM Services and Cross Connections in
XMC20”.
ETAG1 supports the following PBUS formats:
• P0nc (with and without CAS)
• P12 (transparent)
• P12 (clock master)
ETAG1 uses the CAS bits for the 1+1 Trail (Path) protection function.
5.3.1 PBUS Cross Connections
ECST is designed to accept valid PBUS cross connections only, but for
ETAG1 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 21: Overview on cross connection modes

ETAG1 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 ETAG1 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 [314]

User Guide “TDM Services and Cross Connections in XMC20”.
5.3.2 Unit mode “8 x 2Mbit/s” versus “16 x 2Mbit/s”
Table 22: Unit mode characteristics

8 x 2Mbit/s 16 x 2Mbit/s
The unit mode 8 x 2Mbit/s is the default mode with a total The unit mode 16 x 2Mbit/s is the high speed option with the
bandwidth of 16 Mbit/s towards the TDM interfaces total bandwidth towards the TDM interfaces doubled to 32
(PBUS). 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 timeslots from n = 1 … 32 may be selected. even numbers of timeslots from n = 2 … 32 may be selected.

163
ETAG1
Table 23: Overview on clocking and TDM modes

TDM mode Framing Available Usable by Clocking Impact in case of unsyn-
in unit the XMC20 chronised Rx/Tx state
mode as 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 XMC20 frame- handled by the G.704 process
16x2Mbit/s work with the local XMC20 clock. and lead to occasional data
loss.
P12 unframed 8x2Mbit/s no The XMC20 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 ETAG1 unit. The even for unsynchronised Rx/
ETAG1 unit extracts the Rx clock Tx state.
from the Rx data stream.
P12 unframed 16x2Mbit/s no The ETAG1 unit uses the UMUX Possible clock differences are
(clock mas- system clock for Rx data streams. handled by the XMC20 frame-
ter) work and lead to occasional
data loss.

Take great care on timing source configuration in XMC20 TDM networks.
Unsynchronised Rx/Tx states should be restricted to transient states during
switch-over 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 paragraph 5.3.1 PBUS
Cross Connections (on page 29).
For details on timing source configuration please refer to [314] User Guide
“TDM Services and Cross Connections in XMC20”.
Please note:
Changing the unit mode may cause a restart of the unit and includes the risk
of inconsistent configurations. KEYMILE therefore recommends deleting an
existing unit whenever the unit mode should be changed.
5.3.3 Protection for TDM WAN links
The XMC20 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 ETAG1 the option “Protected”
must be set to “Yes”, when establishing the cross connection between
ETAG1 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 ETAG1 and TUDA1 enable CAS on both
units and select “Supervised” or “1+1 Revertive” as transport mode on the
TUDA1, provided CAS is supported for the full path.

163
ETAG1
For detailed description of signal protection please refer to [314] User Guide
“TDM Services and Cross Connections in XMC20”.

163
ETAG1
5.4 Bridging functions
5.4.1 VLAN MAC transparent bridging
ETAG1 is a VLAN aware MAC bridge according to IEEE 802.1Q-2003.

ETAG1 uses the port and tag based VLAN concept in order to assign a VID
to received frames.
VLAN A VLAN A
Access port
ETAG1 Access port
Trunk link VLAN aware
VLAN aware
Trunk port Trunk port bridge
Access port bridge 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 ETAG1:
• 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.

163
ETAG1
− 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.
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
Redundant links between two VLAN segments must be of the same link type. Otherwise
the network behaviour will change depending on the active link topography.
trunk link trunk link

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

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

163
ETAG1
Several links from an untagged LAN segment must all use the same VID. Otherwise
connectivity in the network will change depending on the active link topography .

access port with access port with
VLAN ID = 105 VLAN ID = 105
VLAN VLAN
untagged tagged untagged tagged
access port with access port with
VLAN ID = 110 VLAN ID = 105
A) Access port with VLAN ID105 is forwarded

forwarding access port with
VLAN ID = 105
VLAN ID = 110
VLAN VLAN
untagged tagged untagged tagged
VLAN ID = 110
discarding access port with
VLAN ID = 110
B) Access port with VLAN ID110 is forwarded
VLAN ID = 105 discarding
VLAN
untagged tagged
VLAN ID = 110
forwarding
Figure 8: Possible inconsistencies in VLAN tagged bridged networks
5.4.2 IVL based MAC learning
The VLAN standard IEEE 802.1Q-2003 mentions two methods for MAC
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.
ETAG1 implements the IVL approach with tables supporting 8192 learned
MAC addresses per bridge instance.
5.4.3 RSTP
ETAG1 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.

163
ETAG1
Figure 9: Example bridged network with meshed topography
Root
forwarding
forwarding
forwarding
discarding
forwarding
forwarding
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. ETAG1 provides valuable informa-
tion in the status menus for maintaining and debugging bridged networks .
For details see section 8.6.6.1 "AP: / unit-x / port-r, Status - Bridge" (on
page 107).
5.4.4 Multiple bridge instances
ETAG1 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 ETAG1 function set for
bridging without restrictions.

163
ETAG1
Please note:
Traffic isolation between two bridge instances on the same ETAG1 unit is
the same as between two bridges on separate hardware (ETER1 is the
ETAG1 equivalent in the KEYMILE UMUX product family).
ETAG1
ETAG1
PDH/SDH
Network ETER1
3rd party
bridge
ETAG1
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 ETAG1
unit.
5.4.5 Star topology bridging
The star topology bridging feature supported by the ETAG1 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.

163
ETAG1
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”.
ETAG1
ETER1
ETAG1
internal port
via backplane
COGE5
ETAG1 ETER1
ETER1
PDH/SDH
ETAG1 Network
PDH/SDH
Network
TUDA1
TUDA1
ETAG1
LineRunner
DTM
SDSL8
LineRunner
Public bridge interface DTU
Protected bridge interface SDSL8
Figure 12: Example star bridging application
The ETAG1 star bridging function is a purely local bridge function. It is com-
patible with other bridge/switch equipment (ETER1, LAWA4, third party) as
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.

163
ETAG1
5.5 Routing functions
This user guide is not a routing tutorial. The following routing basics and defi-
nitions in this paragraph 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 ETAG1 see paragraph 8.7.3.2 AP: /
unit-x / router, Configuration - StaticRoutes (on page 116).
5.5.1.1 Connecting networks with static routing
The ETAG1 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.

163
ETAG1
specific
default route external route
External
Large Network Destination
OSPF or RIP
ETAG1 ETAG1
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.
Please note:
OSPF external routes are advertised only if “OSPF Redistribute” - “Static” in
the “Router” menu is enabled.

163
ETAG1
Figure 14: Redistribution of static routes
See also paragraph 8.7.3.2 AP: / unit-x / router, Configuration - StaticRoutes

(on page 116).
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 backbone
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.
Please note:
The stub area and NSSA features should be used by OSPF experts only. If
in doubt, please use areas in default mode.

163
ETAG1
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 config-
uration 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.
KEYMILE recommends favouring OSPF routing over RIP, for all cases
where the user has a choice. The ETAG1 unit supports RIP mainly for main-
taining existing RIP networks or to provide interfacing between OSPF and
RIP networks.

163
ETAG1
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 authenti-
cation 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. ETAG1 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 acti-
vating the interface in the corresponding protocol in passive mode, with a
subtle distinction in case of OSPF:
Redistributed connected interfaces are advertised with external LSAs and
can therefore not be summarized via area ranges. Furthermore external
LSAs are not usable by stub areas.
Please note:
Whenever possible prefer configuring interfaces in passive mode over redis-
tribution of connected interfaces. For more information regarding the passive
mode, please refer to paragraph 8.7.3.1 AP: / unit-x / router, Configuration -
Router (on page 114).

163
ETAG1
ETAG1 advertises one or several

static routes corresponding to the
address range of the RIP network
OSPF
RIP
ETAG1
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.
Gateway address =
IP address of Gateway
router A
Gateway router A
IP Network
IP host
Backup gateway router B

with IP address different
from 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.

163
ETAG1
Gateway address =
IP address of the
virtual router
Gateway router A with VRRP
IP Network
IP host
Virtual router Gateway router B 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 ETAG1 VRRP implementation does not use the virtual MAC address.
Instead the MAC address of the corresponding Ethernet interface on the
ETAG1 is used. As a consequence, the virtual router’s MAC address
changes each time a new router becomes master. In order to immediately
reflect this change in all IP host’s MAC tables, a gratuitous ARP is broad-
casted on the LAN by the newly elected master.

163
ETAG1
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 44), we have still two
gateway routers, but this time each is participating in two virtual routers. The
VRRP priorities are selected in order to have different masters for the virtual
routers. Furthermore the IP hosts use different gateway addresses.
IP host x with gateway address =
IP address of the virtual router 1
Gateway router A participates

in virtual router 1 with priority=200 and
in virtual router 2 with priority=100
IP host y with gateway address =

IP address of the virtual router 2 IP Network
Virtual
router 1
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

163
ETAG1
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.
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: ETAG1 Router C: ETAG1
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 IP host C
172.16.1.102/24 Virtual router A Virtual router C 172.16.22.44/24
GW = 172.16.1.221 ID = 221 ID = 221 GW = 172.16.22.221
172.16.1.221/24 172.16.22.221/24
172.16.98.18/30 172.16.98.17/30
24 172 172
.13/ Main TDM link, 2Mb/s 30 .16.2
.16 .1
R-A .16 .6 / R-C 2 .4/
1 72
.9 8
.9 /3 6 .9 8 24
2. 1
0 17
redundant TDM links ,

256 kb/s
VR-A VR-B VR-C VR-D
1 72
172 5/ 30 . 16
.1 6.1 98 . .9 /24
.11 3 . 8 .1 0 2 2.3
/24 .16 /3 0 .16.
17
2 17 2
172.16.98.13/30 172.16.98.14/30
R-B Main TDM link, 2Mb/s R-D
Virtual router B Virtual router D

IP host B ID = 222 ID = 222 IP host D
172.16.1.105/24 172.16.1.222/24 172.16.22.222/24 172.16.22.99/24
GW = 172.16.1.222 GW = 172.16.22.222
Router B: ETAG1 Router D: ETAG1
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 ETAG1 units have OSPF activated in the All ppp over TDM links are configured for
backbone area for all router interfaces 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.

163
ETAG1
Under normal conditions and with no network defects, pinging host D from
host A results in the following trace:
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 upper trail but the return path follows the lower
trail, since host D addresses router D with it’s gateway setting.
The test is repeated with a broken link between host A and router A:
R-A R-C
IP host A IP host C
VR-A VR-B VR-C VR-D
IP host B IP 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:

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:
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 below:

163
ETAG1
R-A
IP host A
VR-A VR-B
IP 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.
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
breakes.
Please note:
KEYMILE 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.

163
ETAG1
5.6 Interface stacks
5.6.1 Generic stack model
The generic stack model reflects the ETAG1 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.
• ETAG1 networking functions
− MAC bridging
− IP routing
• ETAG1 interfaces
− Ethernet
− TDM, i.e. P0nc/P12 via the UMUX internal PBUS
− VLAN interface
• ETAG1 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.
ETAG1
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.
ETAG1 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.

163
ETAG1
5.6.2 MAC/PPP bridged encapsulation
ETAG1 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 LineRunner DTM
ETAG1 supports direct MAC/HDLC encapsulation compatible with LineRun-

ner and TUDA1. With this feature the ETAG1 unit can terminate a LineRun-
ner link and continue the connection with standard PPP.
3rd party Bridge with TDM I/F

MAC Bridging
MAC/PPP RFC3518
PPP RFC1661
PPP/HDLC RFC1662 TDM
TDM interface Network
XMC20 ETAG1
MAC Bridging
MAC/PPP RFC3518 *
MAC/HDLC PPP RFC1661
SDSL8 SELI8
PPP/HDLC RFC1662
P0_nc/P12 P0_nc/P12 P0_nc/P12 P0_nc/P12
SHDSL E1 G.703
LineRunner DTM / DTU

MAC Bridging
MAC/HDLC IEEE 802.3
Ethernet
SHDSL link SHDSL 10/100BASE-T
LAN
* MAC/PPP RFC3518 is compatible with its predecessors RFC1638 and RFC2878
Figure 24: Connection of LineRunner DTM to 3rd party Bridge
5.6.4 PPP / HDLC encapsulation & framing
ETAG1 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).
5.6.5 Hypothetical applications with bridging
The following ETAG1 bridging applications in the figures below are all inter-
connected via a common PDH / SDH network:

163
ETAG1
1 TDM WAN link termination with MAC / PPP

2 Ethernet LAN - TDM WAN connection
3 Traffic aggregation with SDSL8 and LineRunner modem
4 Traffic aggregation with SDSL8 and LineRunner modem plus translation
of TDM WAN link termination from MAC / PPP to MAC / HDLC
5 Traffic aggregation with TUDA1 and serial interface
6 TDM WAN connection to 3rd party bridge with G.703 interface
Bridging application 1:
ETAG1
TDM WAN link termination
with MAC/PPP MAC Bridging
MAC/PPP RFC3518
PPP RFC1661
SELI8 PPP/HDLC RFC1662
P0_nc/P12 P0_nc/P12
E1 G.703
Ethernet LAN - TDM WAN connection ETAG1
ETAG1 MAC Bridging
MAC Bridging IEEE 802.3 3rd party Bridge
TDM
MAC/PPP 10/100BASE-T
Network IEEE 802.3 MAC Bridging
RFC3518
IEEE 802.3
PPP 10/100 Ethernet
RFC1661 BASE-T 10/100BASE-T
LAN
PPP/HDLC
RFC1662 ETAG1
SELI8 P0_nc/P12 IP Routing

IPoE/ARP
IEEE 802.3
10/100BASE-T
ETAG1
Traffic aggregation with SDSL8 and LineRunner modem
MAC Bridging
MAC/PPP MAC/PPP
RFC3518 RFC3518
PPP PPP
RFC1661 RFC1661
PPP/HDLC PPP/HDLC 3rd party Bridge
RFC1662 RFC1662 SDSL8 with TDM I/F
SELI8 P0_nc/P12 P0_nc/P12 P0_nc/P12
MAC Bridging
SHDSL
MAC/PPP
RFC3518
PPP
LineRunner RFC1661
DTM/DTU
PPP/HDLC
P0_nc/P12 RFC1662
TDM TDM
SHDSL link SHDSL
interface interface
Figure 25: Stack details for ETAG1 bridging applications

163
ETAG1
ETAG1 Bridging application 4:

Traffic aggregation with SDSL8 and LineRunner
MAC Bridging modem plus translation of TDM WAN link termination
MAC/PPP from MAC/PPP to MAC/HDLC
TDM RFC3518
Network
PPP MAC/
RFC1661 HDLC
PPP/HDLC SDSL8 3rd party IP host
RFC1662 LineRunner
with Ethernet
DTM/DTU
SELI8 P0_nc/P12 P0_nc/P12 P0_nc/P12 interface
SHDSL MAC Bridging IP
MAC/HDLC IEEE 802.3 IPoE/ARP
P0_nc/P12 10/100 IEEE 802.3
SHDSL link SHDSL BASE-T 10/100BASE-T
ETAG1 Bridging application 5:

Traffic aggregation with TUDA1 and serial interface
MAC Bridging
MAC/PPP MAC/PPP 3rd party Bridge with serial interface
RFC3518 RFC3518
PPP PPP MAC Bridging
RFC1661 RFC1661 MAC/PPP RFC3518
PPP/HDLC PPP/HDLC PPP RFC1661
RFC1662 RFC1662
TUDA1
PPP/HDLC RFC1662
SELI8 P0_nc/P12 P0_nc/P12 P0_nc/P12 P0_nc/P12
Serial interface Serial interface
Bridging application 6: 3rd party Bridge with G.703 interface

TDM WAN connection to 3rd party bridge with G.703 interface
MAC Bridging
MAC/PPP RFC3518
PPP RFC1661
PPP/HDLC RFC1662
P0_nc/P12
E1 G.703
Figure 26: Stack details for ETAG1 bridging applications (continued)
5.6.6 Hypothetical applications with routing
The following ETAG1 routing applications in the figures below are all inter-
connected 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
ETAG1 virtual interface

163
ETAG1
Routing application 1: ETAG1

TDM WAN link termination
with IP/PPP IP Routing
IP/PPP RFC1332
PPP RFC1661
PPP/HDLC RFC1662
P0_nc/P12 P0_nc/P12
E1 G.703
Routing application 2: ETAG1

Ethernet LAN – TDM WAN connection ETAG1
MAC Bridging
ETAG1 IP Routing
IEEE 802.3
IPoE/ARP
IP Routing 10/100BASE-T
TDM IEEE 802.3
Network IP/PPP RFC1332 IPoE/ARP
10/100BASE-T
PPP RFC1661 IEEE 802.3
PPP/HDLC RFC1662 10/100 Ethernet
SELI8 P0_nc/P12 BASE-T LAN
3rd party Router with TDM I/F Routing application 3:

TDM WAN connection to 3rd party router
IP Routing with G.703 interface
IP/PPP RFC1332
PPP RFC1661
PPP/HDLC RFC1662
P0_nc/P12
E1 G.703
Routing application 4:
Interconnection of bridged and routed network segments using the ETAG1 VLAN interface
ETAG1 (a)
IP Routing VLAN MAC Bridging
IP/PPP RFC1332 IPoE/ARP interface MAC/PPP RFC3518
IEEE 802.3
PPP RFC1661 IEEE 802.3 PPP RFC1661
PPP/HDLC RFC1662 10/100 10/100 PPP/HDLC RFC1662
SELI8 P0_nc/P12 BASE-T BASE-T P0_nc/P12
(b) SELI8
ETAG1
Ethernet
MAC Bridging LAN
MAC/PPP RFC3518
PPP RFC1661 There are two alternative ways to interconnect
PPP/HDLC RFC1662 bridged and routed network segments with a
single unit:
P0_nc/P12 SELI8 (a) using the ETAG1 VLAN interface
(b) using an external connection via two
3rd party Bridge with TDM I/F ETAG1 Ethernet ports
MAC Bridging
MAC/PPP RFC3518 TDM
PPP RFC1661 Network
PPP/HDLC RFC1662
E1 G.703
Figure 27: Stack details for ETAG1 routing applications

163
ETAG1
5.7 Multilink PPP interface
ETAG1 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, ETAG1 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.
ETAG1 ETAG1
IP Routing MAC Bridging Termination at the far
Multilink -PPP RFC1990 Multilink -PPP RFC1990 end with Multilink PPP
IP/PPP IP/PPP IP/PPP MAC/PPP MAC/PPP MAC/PPP accordingly
RFC1332 RFC1332 RFC1332 RFC3518 RFC3518 RFC3518 (ETAG1, ETER1 or
PPP PPP PPP PPP PPP PPP third party equipment)
RFC1661 RFC1661 RFC1661 RFC1661 RFC1661 RFC1661
PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC PPP/HDLC
RFC1662 RFC1662 RFC1662 RFC1662 RFC1662 RFC1662
P0_nc/P12 P0_nc/P12 P0_nc/P12 P0_nc/P12 P0_nc/P12 P0_nc/P12
SELI8
P0_nc/P12
TDM
Member links of the ML PPP bundle E1 G.703 Network
- All member links with MAC/PPP, RFC 3518
- Bandwidth per member link up to 2Mbit/s
- Number of member links limited by total
available B/W
P0_nc/P12
Member links of the ML PPP bundle E1 G.703

- All member links with IP/PPP, RFC 1332
- Bandwidth per member link up to 2Mbit/s
- Number of member links limited by total
available B/W
Figure 28: Block diagram and stacks for Multilink PPP
5.7.1 Bandwidth considerations for multilink PPP bundles

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.

163
ETAG1
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).

163
ETAG1
5.8 VLAN Interfaces
The ETAG1 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.
direct assignment (standard case )
TDM WAN
assignment via a bridge
interfaces 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 paragraph 5.6 Interface stacks (on page 49) 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 ETAG1 routing applications (on page 53).

163
ETAG1
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.
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
Gateway Gateway
subnet B Subnets
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
ETAG1 VLAN I/F, VLAN Id = 101
IP addr = 172.16.31.1/24
Subnets VLAN I/F, VLAN Id = 102

A, VLAN Id 101 IP addr = 172.16.32.1/24 Gateway
B, VLAN Id 102 Ethernet
front port VLAN I/F, VLAN Id = 103
C, VLAN Id 103 IP addr = 172.16.33.1/24
D, VLAN Id 104
Interface is assigned to VLAN I/F, VLAN Id = 104
the Bridge as trunk port IP addr = 172.16.34.1/24
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.

163
ETAG1
Ethernet LAN with tagged

and untagged ranges
untagged
Subnet 172.16.1.0/24 ETAG1 Interface assigned to the router,
VLAN A IP addr = 172.16.1.1/24
Subnet 172.16.32.0/24
VLAN-ID = 101 VLAN I/F, VLAN Id = 101
VLAN B IP addr = 172.16.32.1/24 Gateway
Ethernet
Subnet 172.16.33.0/24
front port VLAN I/F, VLAN Id = 102
VLAN-ID = 102
VLAN C IP addr = 172.16.33.1/24
Subnet 172.16.34.0/24
VLAN-ID = 103 VLAN I/F, VLAN Id = 103
VLAN X IP addr = 172.16.34.1/24
VLAN-ID = 168
not routed
Figure 32: Selective VLAN routing for tagged and untagged frames
5.8.3 Connecting bridged and routed network segments
In this application ETAG1 is used for aggregating remote network access

points to a central service point. The network is divided into a bridged part
with LineRunner DTM and a routed part between the ETAG1 units and the
central service point. One or several VLAN interfaces provide the ETAG1
internal connection between bridging and routing.
ETAG1
TDM
VLAN Network
interface (s)
TDM
LineRunner I/F-6
SHDSL link SDSL8 TDM ETAG1
DTM I/F-1
LineRunner SDSL8 TDM

SHDSL link
DTM I/F-2
VLAN
interface(s)
LineRunner TDM
SHDSL link SDSL8
DTM I/F-3
LineRunner TDM
SHDSL link SDSL8
DTM I/F-4
TDM
I/F-5
TDM
Network
Figure 33: The VLAN interface connects between bridging and routing

163
ETAG1
Configuration example for untagged traffic from the LineRunner DTM 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 LineRunner DTM 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.

163
ETAG1
5.9 QoS
QoS for the ETAG1 means forwarding received traffic depending on the traf-
fic 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
5.9.1 Frame classification and marking
Frame classification is depending on the networking function and on the

received frame type.
Table 24: 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
ETAG1 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.

163
ETAG1
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 Frame processing
queue scheduling SW TX queue 3
and forwarding
SW TX queue 4
(network processor )
HW TX queue full *
HW RX
from TDM /I F
Multilink PPP bundle
queue
ML PPP
RX
HW RX
from TDM /I F
queue
HW TX SW TX queue 1
to TDM I/F queue full *
queue ML PPP Queue SW TX queue 2
TX scheduling SW TX queue 3
HW TX
to TDM I/F queue full * SW TX queue 4
queue
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 ETAG1
• Queue scheduling
A scheduling process is responsible to empty a set of queues in a prede-
termined way. The current release of ETAG1 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 25: 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

163
ETAG1
Table 25: Default priority mapping for MAC frames (continued)

802.1p MAC priority TX queue number Priority
6 Voice 4 highest priority
7 Network Control 4 highest priority
Table 26: 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
5.9.4 Equipment protection (EQP)
5.9.4.1 EQP features
To protect the ETAG1 functions against a failure on the ETAG1 unit, XMC20
offers the possibility to equip the subrack with a second ETAG1 unit as a
protecting unit.
EQP protects the main functions switching and routing on the ETAG1 unit
including the backplane interfaces Ethernet and TDM. The Ethernet front
interfaces can’t be protected. When using ETAG1 equipment protection, the
Ethernet traffic from an Ethernet switch is connected to both ETAG1 units via
cables.
In case of a failure on the active (working or protecting) unit the management
and user traffic is rerouted from the failed ETAG1 unit to the standby ETAG1
(protecting or working) unit.
The working and the protecting ETAG1 units can be plugged in any free slot
of the XMC20 subrack.
Management traffic cross-connected over the backplane to the COGEx unit
and user traffic cross-connected to any service unit can be protected.

163
ETAG1
XMC20 active standby
PBUS access PBUS access PBUS access PBUS access
Service Unit
ETAG1 ETAG1
p-1 p-2 p-3 p-4 p-1 p-2 p-3 p-4 p-x
COGE5
SDH/PDH
Local Area access
Network network
p-x = Ethernet port -x
Local Area
Network
Figure 35: PBUS access with ETAG1 EQP
Management traffic over the backplane Gigabit Ethernet star to the COGEx
unit and user traffic to any service unit can be protected.
XMC20 active standby
GbE access GbE access GbE access GbE access
Service Unit ETAG1 ETAG1

p-1 p-2 p-m p-n p-1 p-... p-5 p-1 p-2 p-3 p-4 p-1 p-2 p-3 p-4
Local Area
Network
p-x = Ethernet port -x
Local Area
Network
Figure 36: GbE access with ETAG1 EQP
Please note:
The ports on the standby unit are inactive.
Please note:
The protection switching is non revertive, i.e. after the repair of a failed
ETAG1 unit, the currently active ETAG1 unit remains the active unit irrespec-
tive if it is the working or protecting unit.

163
ETAG1
Please note:
During a protection switch-over the user traffic is interrupted up to 9 s
depending on used protocols and switch-over event. For switching times
please refer to table Protection (on page 18). Additionally some more time is
needed to establish the connection depending on used protocol on layer 2
(e.g. MAC/HDLC, PPP) and layer 3 (e.g. OSPF, RIP).
Please note:
Be careful when using an ETAG1 in a protected routed network. A link
breakdown on an Ethernet front port will leads to a correct rerouting with all
routing protocols. A link breakdown behind the external Ethernet switch in
the local area network will prevent a correct rerouting because the ETAG1
front port admin state is still up.
5.9.4.2 EQP prerequisites
To enable equipment protection for the ETAG1 unit some prerequisites must
be met:
• The protecting ETAG1 unit must be in the unassigned state. Otherwise
the unit will not be selectable in the EQP configuration in AP: /unit-x, Con-
figuration - EQP: Create Group…, EQP Group Creation, Protecting Unit.
• The protecting unit must be hardware compatible with the working unit.
Check the hardware compatibility status after the EQP group configura-
tion in the AP: /unit-x, Status - EQP: Units Status, HW Compatible.
The following requirements must be fulfilled that the two units are stated
as hardware compatible:
− Identical unit function. The unit function is composed of the 5 first
characters of the unit name, e.g. ETAG1. The unit name is available at
the AP:/ Main - Equipment, Unit.
− Identical board identification, e.g. 328. The board identification is avail-
able at the AP:/ Main - Inventory, Board ID.
− Identical hardware variant. The hardware variant is the truncation of
the hardware key divided by 256, e.g. 1/256 = 0. The hardware key is
available at the AP:/ Main - Inventory, Hardware Key.
• The protecting unit must be software compatible with the working unit.
Check the software compatibility status after the EQP group configuration
in the AP: /unit-x, Status - EQP: Units Status, SW Compatible.
The following requirements must be fulfilled that the two units are stated
as software compatible:
− Identical unit function. The unit function is composed of the 5 first
characters of the software name, e.g. etag1. The unit name is availa-
ble at the AP:/ Main - Equipment, Software.
In order to guarantee the full compatibility of all features it is strongly rec-
ommended to use the same software on the working and on the protect-
ing unit.
The compatible software must be installed on the ETAG1 unit before the
EQP group creation.
• The unit configuration of an equipment protection group is always done
on the active unit. The configuration on the standby unit is not possible.

163
ETAG1

The configuration of an equipment protection group must be saved (ECST
NE menu or ECST tool bar: Save to NE).
Otherwise, in case of a protection switch event, the NE will load an outdated
configuration from the internal configuration database and the NE configura-
tion will be corrupted.
5.9.4.3 EQP configuration
The working ETAG1 unit of an EQP group is assigned and configured the
same way as a stand alone ETAG1 unit.
The protecting ETAG1 unit is running with the same ESW as the working
unit and must be in the unassigned state.
The 1+1 equipment protection group is configured on the working unit:
• AP: /unit-x, Configuration - EQP.
− Execute the command “Create Group…”.
− Select the Protecting unit, e.g. /unit-18.
− Execute “OK”.
• Save the NE configuration.
Further on any changes on the ETAG1 configuration must be done on the
active unit. To find out which unit is the active unit check the shelf view, AP
tree or the unit status of the working or protecting ETAG1 unit.

Different configuration on ETAG1 active and standby unit is not possible
because configuration is limited to the active unit only. However the COGEx
bridge (e.g. mode, PVID, ...) and RSTP parameter (e.g. enabled/disabled)
have to match between the ETAG1 and COGEx unit. Additionally with
COGEx redundancy the internal ports bridge and protocol parameters on
both COGEx active and standby unit connected to ETAG1 have to be config-
ured equal too. Inconsistent network configuration using ETAG1 EQP and
COGEx redundancy should be prevented. Please refer to the figures in sec-
tion 5.4.1 VLAN MAC transparent bridging (on page 32) and 5.4.3 RSTP (on
page 34) for valid configuration.
5.9.4.4 EQP status
The unit status of the working and protecting units shows the actual status of
the units belonging to the equipment protection group. The unit status offers
also the commands for the EQP manipulation:
• Manual switch
The currently standby unit is set as active unit and the currently active
unit is set as standby unit. This requires that the currently standby unit is
in operational state, i.e.
− has no failure,
− is not isolated.
A manual switch is possible if it is indicated with the “Manual Switch-Over
Allowed” parameter.
This command can only be activated on the working unit status window.

163
ETAG1
• Forced switch
The currently standby unit is set as active unit, independent of the failure
state of the currently standby unit.
Note that there is a risk that the user traffic will be permanently inter-
rupted if the currently standby unit is in a failure state.
The currently active unit is set as standby unit.
Note that this command can only be activated on the working unit status
window.
• Isolate unit
To be able to perform a maintenance action, e.g. update of the embed-
ded software, on an active unit without activating a protection switch-
over, the working unit can be isolated. This means that the protection
switching state machine is frozen and no protection switch will be done
until the isolation of the unit is removed.
Note that the isolate unit command can only be applied to the working
unit.
• Join unit
Remove the isolation of a previously isolated unit.
Note that the join unit command can only be applied to the working unit.
The table in the EQP status window displays the following items:
• Unit
MO address of the unit belonging to the EQP group.
• EQP unit mode
The working unit is the unit where the protection group has been config-
ured.
The protecting unit is the unit that has been set to the unassigned state
before configuring the protection group.
• Active
Active true means the unit is the active unit, i.e. it is the operational unit.
Active false means the unit is the standby unit, i.e. it is not the operational
unit.
The active state can be changed with the “Manual Switch” and “Forced
Switch” commands.
• Failure
Failure true means the unit is in a failure state.
Failure false means the unit is not in a failure state.
The failure state can not be changed manually.
• Substituted
Substituted true on the working unit means the unit has been substituted
by the protecting unit. A substituted unit is also in the “active false” state.
Substituted false on the working unit means the unit has not been substi-
tuted, i.e. it is the active unit or it has been isolated.
The substituted state of the protecting unit is always false.
• Isolated
Isolated true means the unit has been isolated with the “Isolate Unit”
command.
Isolated false means the unit is not isolated.
The isolation state can be changed with the “Isolate Unit” and “Join Unit”
commands.
The isolated state of the protecting unit is always false.

163
ETAG1
• HW Compatible
HW compatible true means the working HW unit is compatible with the
protecting HW unit.
HW compatible false means the working HW unit is not compatible with
the protecting HW unit. Equipment protection is not possible.
• SW Compatible
SW compatible true means the working unit embedded software (ESW) is
compatible with the protecting unit ESW.
SW compatible false means the working unit ESW is not compatible with
the protecting unit ESW. Equipment protection is not possible.
• DB Saved
DB saved true means the current configuration of the working or protect-
ing unit has been saved to the XMC20 internal database.
DB saved false means the current configuration of the working or protect-
ing unit has not been saved to the XMC20 internal database. A protection
switching event will load an outdated configuration and traffic will be dis-
turbed.

163
Commissioning User Manual
ETAG1
6 Commissioning
6.1 Commissioning steps
6.1.1 New units in the XMC20 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 [355] User Manual
“ECST”.
6.1.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 paragraph 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:
ECST does check numerous dependencies between different parameters, in
order to prevent inconsistent configurations. A warning pops up in case the
entered selection interferes with configuration rules or is not compatible with
previously entered values. However it is not possible for ECST to prevent all
possible inconsistencies or otherwise non-working configurations.

163
Operation and Maintenance User Manual
ETAG1
7 Operation and Maintenance

This section describes the operation functions of the ETAG1 unit. You will
find the following information:
• General operation recommendations for the ETAG1 unit (section 7.1
"General operation recommendations" (on page 69)).
• Optical indicators description found on the ETAG1 unit front (section 7.2
"Unit optical indicators" (on page 70)).
• Generic maintenance functions of the unit (section 7.3 "Maintenance" (on
page 71)).
Please note:
The operation functions described in this section assume a correctly config-
ured and operational ETAG1 unit.
7.1 General operation recommendations
When setting up or debugging an access network using the ETAG1, 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:
− Ping command
The ping command is available at the router status function. Please
refer to section 8.7.4.3 "AP: / unit-x / router, Status - Ping Command"
(on page 118).
− Trace route command
The trace route command is available at the router status function.
Please refer to section 8.7.4.4 "AP: / unit-x / router, Status - Tracer-
oute Command" (on page 118).
• Fault management
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 [302] User Guide “XMC25/XMC23/XMC22”.
For the alarm descriptions please look for the corresponding “Fault Man-
agement” sections in chapter 8 "GUI Reference" (on page 75).
• Performance Monitoring
Performance parameters provide information about the long term stability
and reliability of a link. Furthermore packet statistics provide information
for detailed traffic analysis in the network.
Please note:
Performance monitoring on ETAG1 signals is only available if the signals are
enabled (ports) or cross connections have been configured (internal signals).

163
ETAG1
7.2 Unit optical indicators
LEDs on the front of the ETAG1 unit are used to indicate to the user the
alarm status summary of the unit and of the network traffic signals.
XXXXx R1F
47900242
UNIT TRAFFIC
Figure 37: Fault indication LEDs on the ETAG1 unit
Table 27: LED signalling on ETAG1

LED name Colour State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide the requested function due to
- equipment failure (total breakdown),
- mismatch of HW and SW.
Recovery from this error situation is done usually by replacement
of unit HW or ESW.
Green / Red Booting or Unit has not been taken in service yet or the unit has not been pro-
(blinking 1 Hz) waiting visioned.
Recovery from this situation is done by taking this unit into service
with ECST.
Green Running Unit is up and running, it is ready to provide the required service.
Off Failure System is not powered or outage of power supply on unit or outage
of LED.
TRAFFIC Red Failure One or more active failures on the unit, independent of the sever-
ity.
More detailed information is provided by ECST.
Off Normal Normal (error free) operation.

163
ETAG1
7.3 Maintenance
The following maintenance facilities are available from the management

function “Main” on the NE level:
• Inventory data
• Unit ESW download
• Unit ESW upgrade
7.3.1 Inventory data
It is possible to read inventory data from the ETAG1 unit via the ECST with
the following access point:
AP: /unit-x, Main - Inventory.
7.3.2 Unit ESW download
It is possible to remotely upgrade the ESW (local unit FW) of the ETAG1 via
software download.
Please refer to [355] User Manual “ECST” for a description of the software
download procedure.
7.3.3 Upgrades
You can upgrade an existing ETAG1 with newer functionality as described in

the new ECST 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 XMC20 inventory function. Please refer to [012] Release Note “XMC20
System Release R6A” for the corresponding data in the XMC20 Release
Note.
7.3.3.1 ESW upgrade with EQP
When upgrading the ESW on 1:1 equipment protected ETAG1 units, care
must be taken concerning the traffic interruptions and which unit will finally
be the active unit. At the end of the upgrade procedure the working unit shall
be the active unit.
It is assumed that the working unit is plugged in slot 7 and the protecting unit
is plugged in slot 9 of the XMC25 subrack.
ESW upgrade procedure 1 The following procedure provides the upgrade process with one traffic inter-
ruption of up to 60 s.
Please note:
The ESW upgrade procedure 2 provides shorter interruptions.

163
ETAG1
Isolate the working unit Proceed as follows:

1. Isolate the working ETAG1 unit:
 AP: /unit-7, Status – EQP.
 Execute the “Isolate Unit” command.
 The working ETAG1 unit is isolated, i.e. it will not perform a protection
switch-over.
ESW download and start Proceed as follows:

1. Open the “Software Download” dialogue:
 Menu Tools - Software Download….
2. Configure the ESW file for the working ETAG1 unit:
 Click on the table row with ID “/unit-7”.
 In the “Software to install” column select the new ESW to be
installed.
 In the “Delete unused Software” column tick the selection box.
3. Configure the ESW file for the protecting ETAG1 unit:
 In the “Software to install” column select the new ESW to be
installed.
4. Execute the “Download and Start…” command.
 The “Parameters for command Download and Start” opens.
5. Select the download algorithm:
 Algorithm = Upgrade Units Only.
6. Execute “OK”.
 The new ESW is downloaded and becomes active on the working
and the protecting units.
 Traffic will be interrupted for up to 60s.
 The new ESW is active on the working and the protecting ETAG1 units.
The working ETAG1 unit in slot 7 remains the active unit.
Join the working unit Proceed as follows:

1. Join the working ETAG1 unit:
 AP: /unit-7, Status – EQP.
 Execute the “Join Unit” command.
 The working ETAG1 unit is able again to perform a protection switcho-
ver.
End of instruction
ESW upgrade procedure 2 An alternative procedure requires two shorter interruptions of up to 8 s

instead of one long interruption. Please refer to the note above.
ESW download Proceed as follows:

1. Open the “Software Download” dialogue:
 Menu NE - Software Download….
2. Configure the ESW download for the working ETAG1 unit:
 In the “Software to install” column select the new ESW to be down-
loaded.

163
ETAG1
3. Configure the ESW download for the protecting ETAG1 unit:

 In the “Software to install” column select the new ESW to be down-
loaded.
4. Execute the “Download” command.
 The new ESW is downloaded to the working and the protecting
ETAG1 units
 The ESW download is complete.
ESW upgrade on the protect- Proceed as follows:

ing unit
1. Navigate to the software configuration dialogue:
 AP: /unit-9, Main - Software.
2. Set the parameters in the “Configuration” frame:
 Software = Select the downloaded software.
 Software Installation = Manual Start
 Execute the “Apply” command.
3. Save the configuration:
 Click on the “Save to NE” button.
4. Start the new ESW on the protecting ETAG1 unit:
 Execute the “Start Software” command.
 The new ESW becomes active on the protecting unit. This takes up
to one minute.
 The ESW upgrade on the protecting unit is complete.
Manual switch to protecting 1. Navigate to the EQP status dialogue on the working unit:
unit  AP: /unit-9, Status - EQP.
2. Perform a manual switch-over from the working to the protecting ETAG1
unit:
 Execute the “Manual Switch-Over” command.
 Traffic will be switched to the protecting unit.
 Traffic will be interrupted for up to 8 s.
 The protecting ETAG1 unit is active.
ESW upgrade on the working 1. Navigate to the software configuration dialogue:

unit  AP: /unit-7, Main - Software.
2. Set the parameters in the “Configuration” frame:
 Software = Select the downloaded software.
 Software Installation = Manual Start
 Execute the “Apply” command.
3. Save the configuration:
 Click on the “Save to NE” button.
4. Start the new ESW on the working ETAG1 unit:
 Execute the “Start Software” command.
 The new ESW becomes active on the working unit. This takes up to
one minute.
 The ESW upgrade on the working unit is complete.
Manual switch to working unit 1. Navigate to the EQP status dialogue on the working unit:
 AP: /unit-7, Status - EQP.

163
ETAG1
2. Perform a manual switch-over from the protecting to the working ETAG1

unit:
 Execute the “Manual Switch-Over” command.
 Traffic will be switched to the working unit.
 Traffic will be interrupted for up to 8 s.
 The ESW upgrade is complete and the working ETAG1 unit is active.
End of instruction

163
GUI Reference User Manual
ETAG1
8 GUI Reference
This section gives a complete reference of the managed objects, properties,
and commands of the ETAG1 service unit as far as these are not covered in
the generic descriptions in [302] User Guide “XMC25/XMC23/XMC22”.
In this section, you will find the following information:
• An introduction (section 8.1 "Introduction" (on page 75)),
• Unit management commands and parameters (section 8.2 "AP: / unit-x"
(on page 79)),
• Bridging management commands and parameters (sections 8.3 "AP: /
unit-x / bridges" (on page 86) and 8.4 "AP: / unit-x / bridges / bridge-y"
(on page 87)),
• Loopback interface management commands and parameters (section 8.5
"AP: / unit-x / loopbackInterface" (on page 91)),
• External and internal Ethernet port management commands and parame-
ters (section 8.6 "AP: / unit-x / port-r" (on page 97), 8.18 "AP: / unit-x /
internalPorts" (on page 156) and 8.19 "AP: / unit-x / internalPorts / port-1"
(on page 157)),
• Routing related management commands and parameters (sections 8.7
"AP: / unit-x / router" (on page 113), 8.7 "AP: / unit-x / router" (on
page 113), 8.8 "AP: / unit-x / router / ospf" (on page 120), 8.9 "AP: / unit-x
/ router / ospf / area-s" (on page 122) and 8.10 "AP: / unit-x / router / rip"
(on page 126)),
• TDM interface related management commands and parameters (sections
8.11 "AP: / unit-x / tdmInterfaces" (on page 127), 8.12 "AP: / unit-x /
tdmInterfaces / machdlc-t" (on page 130), 8.13 "AP: / unit-x / tdmInter-
faces / mlppp-u" (on page 138), 8.14 "AP: / unit-x / tdmInterfaces / mlppp-
u / member-v" (on page 143) and 8.15 "AP: / unit-x / tdmInterfaces / ppp-
w" (on page 146)),
• VLAN interface related management commands and parameters (sec-
tions 8.16 "AP: / unit-x / vlanInterfaces" (on page 151) and 8.17 "AP: /
unit-x / vlanInterfaces / vif-z" (on page 153)).
For a description on how to configure and bring into operation the ETAG1
unit and its main functions, please refer to section 6 "Commissioning" (on
page 68).
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
ETAG1 service unit.
The Figure 38 shows the access point (AP) tree for the ETAG1 unit with its
managed objects.

163
ETAG1
<ap >
XMC20
0...20 <ap >

unit-x: ETAG1
1 <ap>
bridges
8 <ap>
bridge-y
1 <ap >
loopbackInterface
4 <ap>
port-r
1 <ap>
router
1 <ap> 1 <ap>
ospf rip
8 <ap >
area-s
1 <ap>
tdmInterfaces
0 ... 64 <ap> 0 ... 64 <ap> 0 ... 64 <ap>

machdlc-t mlppp-u ppp-w
1 ... 64 <ap>
member-v
1 <ap>
vlanInterfaces
0 ... 32 <ap>
vif-z
1 <ap>
internalPorts
1 <ap>
port-1
Figure 38: MOM (managed object model) of the ETAG1 unit

163
ETAG1
With these managed objects (MOs) the following functions are covered:
Table 28: Managed objects (MOs) for ETAG1

MO Description of the management functions
unit-x: ETAG1 Rxx Restart of the unit, management of the unit ESW, labelling,
(etag1_r2c) indication of equipment status, read of inventory data, access
to logbooks. Configuration of unit parameters and equipment
protection parameters, creating or deleting of data confer-
ences.
bridges Container for the bridge managed objects.
bridge-y Configuration and status of the RSTP bridge parameters.
loopbackInterface Management of the loopback interface related functions, like
the interface assignment and corresponding router configura-
tion.
port-r Management of the Ethernet front port related functions, like
the interface assignment and corresponding bridge or router
configuration.
router Container for the internal ports managed objects.
Configuration of the router usage and handling, addition of
static routes. Router status and maintenance functions.
ospf OSPF status functions.
area-s OSPF area configuration and status functions.
rip Status functions of the RIP router.
tdmInterfaces Container for the TDM interfaces managed objects.
machdlc-t Management of the MAC HDLC TDM interface related func-
tions, like the interface assignment and corresponding bridge
or router configuration.
mlppp-u Management of the multilink PPP TDM interface related func-
tions, like the interface assignment and corresponding bridge
or router configuration.
Create and delete ML PPP members.
member-v Status functions of the multilink PPP member.
ppp-w Management of the PPP TDM interface related functions, like
the interface assignment and corresponding bridge or router
configuration.
vlanInterfaces Container for the VLAN interfaces managed objects.
vif-z Management of the VLAN interface related functions, like the
interface assignment and corresponding router configuration.
internalPorts Container for the internal ports managed objects.
port-1 Management of the Ethernet backplane port related functions,
like the interface assignment and corresponding router configu-
ration.
For each of the managed objects, properties and commands, the GUI “Tree
Views” are given.
This reference section comprises the management functions:
• Overview,
• Main,
• Configuration,
• Fault Management,
• Performance Management, and
• Status.

163
ETAG1
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in
accordance with the APs in the ECST AP tree and the availability of the
management functions of each AP.
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 guide, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter
entry fields of the ECST 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 XMC20
equipment.
Please note:
Please refer to [355] User Manual “ECST” for the description of the ECST
functions.

163
ETAG1
8.2 AP: / unit-x
8.2.1 AP: / unit-x, Overview
For a description of the

− “Overview - Alarms”, and
− “Overview - Cross Connections”
management functions, please refer to [302] User Guide “XMC25/XMC23/
XMC22”.
8.2.2 AP: / unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
XMC22”.

163
ETAG1
8.2.3 AP: / unit-x, Configuration
8.2.3.1 AP: / unit-x, Configuration - General
Table 29: AP: / unit-x, Configuration - General

Operation Name Parameter Name Range Descriptions / Details
Mode TDM Access 8 x 2 Mbit/s Support of P0, P0_nc and P12 Transparent transport
modes.
This is the default unit mode and should be favoured for
all applications not needing the high PBUS bandwidth.
16 x 2 Mbit/s Support of P0_nc (n = 2,4,6, … 32) and P12 Clock Mas-
ter transport modes.
The granularity for bandwidth selection on P0_nc chan-
nels is two 64 kbit/s time slots and not one time slot as
usual, i.e. only even numbers of timeslots from n = 2 …
32 may be selected.
802.1p Mapping MAC tag PRI 0…7 MAC tag PRI 0 … 7 is each mapped to one of the four
TX Queue Q1 … Q4 TX queues
DSCP Mapping DSCP 0 … 63 DSCP 0 … 63 is each mapped to one of the four TX

TX Queue Q1 … Q4 queues
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).

163
ETAG1
8.2.3.2 AP: / unit-x, Configuration - EQP
Table 30: AP: / unit-x, Configuration - EQP

Create EQP Group Open the dialogue for the creation of an equipment pro-
… tection (EQP) group.
A unit must be in the unassigned state to be selectable
as a protecting unit.
EQP Group Crea- Group Type 1:1 Type of the EQP group.
tion Working Unit /unit-x MO address of the working unit, e.g. /unit-6.
In the ECST GUI the working unit MO address is read-
only.
Protecting Unit - List of the MO addresses of all HW compatible units
/unit-y which are not assigned, e.g. /unit-8.
Default is no unit selected.
Delete EQP Group Open the dialogue for the deletion of an existing equip-
ment protection (EQP) group.
Traffic on the protecting unit will be interrupted and ser-
vices will be re-established on the working unit.
The protecting unit will become unassigned.
Please note:
With equipment protection of a ETAG1 unit it is possible to protect all the
switching and routing functions on the unit.
Equipment connected to user ports can not be protected without using an
additional switch.
Please note:
The creation and deletion of an EQP group must be done on the working
unit.
8.2.4 AP: / unit-x, Fault Management
For the a description of the general aspects of the

− “Fault Management - Status”, and
− “Fault Management - Configuration”

163
ETAG1

XMC22”. The following table lists the fault causes of the current AP.
Table 31: AP: / unit-x, 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 Configuration or Cus- Processing  Major An invalid configuration has been accepted
tomization Error Error Alarm by the unit by mistake.
To get rid of the alarm redo the complete con-
figuration or reboot the unit.
If the alarm persists please contact KEY-
MILE.
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.

163
ETAG1
Table 31: AP: / unit-x, Fault Management (continued)

Affecting Severity
EQPUNV EQP Unit Not Available Equipment  Major The standby unit is not available, i.e. not
Alarm plugged in or has an equipment failure.
This alarm is available on the working and the
protecting unit of an EQP group.
EQPHWI EQP Hardware Incom- Equipment  Major The actual hardware is not compatible with
patible With Configura- Alarm the hardware of the protecting unit.
tion This alarm is available on the working unit of
an EQP group only.
EQPSWI EQP Software Incom- Equipment  Major The running software (ESW) is not compati-
patible With Configura- Alarm ble with the software on the protecting unit.
tion This alarm is available on the working unit of
an EQP group only.
EQPNPR EQP Group Not Pro- Equipment  Major The working or the protecting unit is not avail-
tected Alarm able, i.e. not plugged in or has an equipment
failure.
This alarm is available on the working unit of
an EQP group only.
EQPWUI EQP Working Unit Iso- Equipment  Major The working unit has been isolated with the
lated Alarm “Isolate Unit” status command.
No protection is available in this state.
an EQP group only.
EQPUNA EQP Working Unit Not Equipment  Major An automatic protection switch or a “manual
Active Alarm switch” or a “forced switch” to the protecting
unit has been done.
an EQP group only.
8.2.5 AP: / unit-x, Status
8.2.5.1 AP: / unit-x, Status - EQP

163
ETAG1
Table 32: AP: / unit-x, Status - EQP

Operation Name Parameter Name Range Description / Details
EQP Group Manual Switch-Over  Indication that the standby unit, i.e. the working
Allowed or the protecting unit is operational and can take
over the service.
 Indication that the standby unit, i.e. the working
or the protecting unit is not operational due to a
failure or to isolation or that the database has not
been saved. A manual protection switching with
the “Manual Switch-Over” command is not possi-
ble.
EQP Group - Units Unit <MO address> MO address of the unit belonging to the EQP
Status group.
EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.
Working Unit
Protecting Unit
Active  The unit is active (operational).
 The unit is standby (not operational).
Failure  The unit has detected failure(s).

Substituted  The working unit has been substituted by the
 protecting unit.
Isolated  The working unit has been isolated with the “Iso-
 late Unit” command.
HW Compatible  The working unit is hardware compatible with the

 protecting unit in the EQP group.
Please refer to section EQP prerequisites (on
page 64).
SW Compatible  The working unit is embedded software compati-
 ble with the protecting unit in the EQP group.
Please refer to section EQP prerequisites (on
page 64).
DB Saved  The configuration of the unit has been saved.

Manual Switch-Over Manual switch of the unit in the EQP group.
A switch-over is performed only when the other
unit is error free and is not isolated and the data-
base has been saved.
Refer to the “Manual Switch-Over Allowed” prop-
erty above.
Note: For the switching times please refer to
table Protection (on page 18).
Forced Switch-Over Forced switch of the unit in the EQP group.
A switch-over is performed independent of the
error state of the other unit, but the unit must not
be isolated.
Note: For the switching times please refer to
table Protection (on page 18).

163
ETAG1
Table 32: AP: / unit-x, Status - EQP (continued)

Isolate Unit Isolate the working unit from the EQP group.
An isolated working unit will not perform any pro-
tection switch action. The protection switching
state of the unit is frozen.
Join Unit Join the isolated working unit to the EQP group,
i.e. remove the isolation.
Please note:
Automatic, manual and forced protection switching is available from the
working to the protecting unit and vice versa.
→ Please refer to section 5.9.4 "Equipment protection (EQP)" (on
page 62).

163
ETAG1
8.3 AP: / unit-x / bridges
8.3.1 AP: / unit-x / bridges, Overview

− “Overview - Alarms”
management function, please refer to [302] User Guide “XMC25/XMC23/
XMC22”.
8.3.2 AP: / unit-x / bridges, Main

− “Main - General”
XMC22”.

163
ETAG1
8.4 AP: / unit-x / bridges / bridge-y
8.4.1 AP: / unit-x / bridges / bridge-y, Overview

XMC22”.
8.4.2 AP: / unit-x / bridges / bridge-y, Main

XMC22”.
8.4.3 AP: / unit-x / bridges / bridge-y, Configuration
8.4.3.1 AP: / unit-x / bridges / bridge-y, Configuration - RSTP
Table 33: AP: / unit-x / bridges / bridge-y, Configuration - RSTP

RSTP Priority RSTP Priority 0 … 32768 … The bridge with the lowest priority value is chosen as
65535 root bridge in the RSTP negotiations process. Default
value = 32768
RSTP Timer Hello Interval 1 … 1 … 10 1 Time interval in seconds for BPDUs sent on each port
that have RSTP enabled. Default value = 2
Forwarding Delay 4 … 15 … 30 1 Time interval in seconds spent in listening and learning
states. Default value = 15
Maximum Age 6 … 20 … 40 1 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

163
ETAG1
Table 33: AP: / unit-x / bridges / bridge-y, Configuration - RSTP (continued)

RSTP Metric Path Cost Version 802.1t-2001 KEYMILE suggests using the 802.1t path cost version
802.1D-1998 (32 bit).
Only for networks where the majority of the links are
running with speeds of 512 kbit/s or slower the 802.1D
path cost version is recommended (16 bit).
1. ECST 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.4 AP: / unit-x / bridges / bridge-y, Performance Management
For the a description of the general aspects of the performance management

(PM) functions, please refer to [302] User Guide “XMC25/XMC23/XMC22”.
The PM parameters are presented in different groups. The following counter
group is available for the ETAG1 bridges:
• “RSTP Bridge” group, see section AP: / unit-x / bridges / bridge-y, Perfor-
mance Management - RSTP Bridge (on page 88).
The following counter intervals are available:
Table 34: PM counter interval availability

Counter interval RSTP Bridge
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.4.4.1 AP: / unit-x / bridges / bridge-y, Performance Management - RSTP Bridge
Table 35: PM group: RSTP Bridge

PM parameter Description
Nb Topology Changes Number of times the RSTP topology has changed.

163
ETAG1
8.4.5 AP: / unit-x / bridges / bridge-y, Status
8.4.5.1 AP: / unit-x / bridges / bridge-y, Status - RSTP
Table 36: AP: / unit-x / bridges / bridge-y, Status - RSTP

Root Bridge RSTP Priority 0 … 65535 The root bridge can be the local ETAG1 unit, another
MAC Address ETAG1 unit or some third party equipment.
Hello Interval s All RSTP bridges in a contiguous network should use

the same value for the hello interval.
Forwarding Delay s Typically all RSTP bridges in a contiguous network
should use the same value for the forwarding delay.
Newer use a longer forwarding delay than the route
bridge.
Maximum Age s Typically all RSTP bridges in a contiguous 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 chosen as
root bridge in the RSTP negotiations process.
MAC Address The eight bridge instances on the ETAG1 unit all have
their own MAC addresses for unambiguous identifica-
tion.

163
ETAG1
8.4.5.2 AP: / unit-x / bridges / bridge-y, Status - Bridge
Table 37: AP: / unit-x / bridges / bridge-y, Status - Bridge

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

163
ETAG1
8.5 AP: / 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.5.1 AP: / unit-x / loopbackInterface, Overview

XMC22”.
8.5.2 AP: / unit-x / loopbackInterface, Main

XMC22”.
8.5.2.1 AP: / unit-x / loopbackInterface, Main - Admin And Oper Status
Table 38: AP: / unit-x / loopbackInterface, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the loop-
tus Down back interface (RFC 2863).
Operational Status State Up Display of the IETF operational status of the

Down loopback interface (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.5.3 AP: / unit-x / loopbackInterface, Configuration
8.5.3.1 AP: / unit-x / loopbackInterface, Configuration - Interface Assignment
Table 39: AP: / unit-x / loopbackInterface, Configuration - Interface Assignment

Interface Assign- Interface Assign- router The ETAG1 loopback interface is always
ment ment assigned to the router and the assignment is not
user configurable.
8.5.3.2 AP: / unit-x / loopbackInterface, Configuration - Router
Table 40: AP: / unit-x / loopbackInterface, Configuration - Router

Addressing Mode Mode Numbered The loopback interface has its own IPv4 address.
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
address in a non-backbone area, the address should be con-
tained 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”
address mode; not relevant for the loopback interface

163
ETAG1
8.5.3.3 AP: / unit-x / loopbackInterface, Configuration - OSPF
Table 41: AP: / unit-x / loopbackInterface, Configuration - OSPF

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 (0.0.0.0) The loopbackInterface belongs to the selected area.
area-2 … area-8
OSPF Priority Priority 0 … 1 … 255 Parameter not relevant for the loopbackInterface
OSPF Authentica- Key <empty> Parameter not relevant for the loopbackInterface
tion
OSPF Metric Automatic  Parameters not relevant for the loopbackInterface

Manual Metric 0 … 65535
OSPF Timers Hello Interval 1 … 10 … 65535 s Parameters not relevant for the loopbackInterface
Router Dead Inter- 0 … 40 … 3600 s
val
Transmission Delay 0 … 1 … 3600 s
Retransmission 0 … 5 … 3600 s
Delay

163
ETAG1
8.5.3.4 AP: / unit-x / loopbackInterface, Configuration - RIP
Table 42: AP: / unit-x / loopbackInterface, Configuration - RIP

RIP Enabled RIP Enabled  RIP can be enabled or disabled for the loopback inter-
 face.
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 Parameters not relevant for the loopbackInterface
Authentication None / RIPv2
None / RIPv1 And
RIPv2
Simple / RIPv2
MD5 / RIPv2
Key <empty>
Split Horizon Split Horizon  Parameter not relevant for the loopbackInterface

8.5.4 AP: / unit-x / loopbackInterface, Performance Management

group is available for the ETAG1 loopback interface:
• “MIB-2 Interface Table” group, see section AP: / unit-x / loopbackInter-
face, Performance Management - MIB-2 Interface Table (on page 95).

163
ETAG1

Counter interval MIB-2 Interface
Table
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.5.4.1 AP: / unit-x / loopbackInterface, Performance Management - MIB-2 Interface Table
Table 44: PM group: MIB-2 Interface Table

<empty> Currently no PM counters are available.
8.5.5 AP: / unit-x / loopbackInterface, Status
8.5.5.1 AP: / unit-x / loopbackInterface, Status - Router
Table 45: AP: / unit-x / loopbackInterface, Status - Router

Router If Status IP MTU Size Maximal size of transmission unit.
8.5.5.2 AP: / unit-x / loopbackInterface, Status - OSPF

163
ETAG1
Table 46: AP: / unit-x / loopbackInterface, Status - OSPF

OSPF Status Status Designated router This router is advertising the connected Ethernet net-
work
Backup designated This router is elected as backup for the advertising of
router the connected Ethernet network
Other designated This router is neither designated router nor backup des-
router ignated 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 correspond-
ing port
b) the corresponding layer 2 link is down
Designated Router Not applicable for the loopback interface.
Backup Designated Not applicable for the loopback interface.
Router

163
ETAG1
8.6 AP: / unit-x / port-r
These are the Ethernet front ports, with <r> ranging from 1 to 4.
8.6.1 AP: / unit-x / port-r, Overview

XMC22”.
8.6.2 AP: / unit-x / port-r, Main

XMC22”.
8.6.2.1 AP: / unit-x / port-r, Main - Admin And Oper Status
Table 47: AP: / unit-x / port-r, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the port
tus Down (RFC 2863).
Operational Status State Up Display of the IETF operational status of the port
Down (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.6.3 AP: / unit-x / port-r, Configuration
8.6.3.1 AP: / unit-x / port-r, Configuration - Interface Assignment
Table 48: AP: / unit-x / port-r, Configuration - Interface Assignment

Interface Assign- Interface Assign- none The interface is left unassigned.
ment 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.
8.6.3.2 AP: / 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.

163
ETAG1
Table 49: AP: / unit-x / port-r, Configuration - Bridge

VLAN Mode Mode Access Only untagged and priority tagged RX frames are
accepted on an access port and all TX frames are sent
without a tag.
Trunk Only VLAN tagged RX frames with VID = 1 … 4094 are
accepted on trunk ports and all TX frames are sent
VLAN tagged.
Trunk (Native This is the hybrid port with both access and trunk prop-
VLAN) erties:
- Both VLAN tagged and untagged RX frames are
accepted.
- Untagged RX frames get a VLAN tag according to the
“Port VLAN ID” and priority tagged RX frames are
assigned the VLAN membership according to the “Port
VLAN ID”.
- TX frames are sent VLAN tagged, with the exception
of frames with a VLAN ID matching the value of “Port
VLAN ID”, which are sent untagged.
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 filter: only frames with this VLAN ID are
allowed to be transmitted.
Default Priority Default Priority 0…7 Untagged or priority tagged RX frames received on the
port will get this value in the priority field.
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).

163
ETAG1
Table 49: AP: / unit-x / port-r, Configuration - Bridge (continued)

RSTP Path Cost Automatic  By default ETAG1 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 retrieved from the manual
entry.
Manual Cost 1 … 200’000’000 This port path cost value is considered for the RSTP
active topology calculation, if above parameter “Auto-
matic” is set to “false”.
Port path cost adjustments induce the following effects:
- a lower value makes the port more attractive and the
chance to play an active role in the network raises
- a higher value makes the port less attractive and the
chance to play an active role in the network drops
If the path cost version is set to “802.1D-1998”, the

manual cost range is 1 … 65’535)
Accessibility Accessibility Public Controls the port’s behaviour in case “Star topology
Protected bridging” is 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.
8.6.3.3 AP: / 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.

163
ETAG1
Table 50: AP: / unit-x / port-r, Configuration - Router

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
address network design. Whether a certain address / mask com-
IP Mask Any valid IPv4 net- bination is valid for a certain interface is in the responsi-
work mask bility of the user and cannot be checked by the ETAG1
unit or by the ECST.
Peer Address IP Address Any valid IPv4 IP address of peer router in case of “Numbered Peer”
address mode.
8.6.3.4 AP: / 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,
Table 51: AP: / unit-x / port-r, Configuration - OSPF

OSPF Enabled OSPF Enabled  OSPF can be enabled or disabled individually for each
 router port.

163
ETAG1
Table 51: AP: / unit-x / port-r, Configuration - OSPF (continued)

OSPF Mode Mode Active The usual mode to configure a OSPF router interface.
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 advertised to the AS. The passive mode
is typically selected for connected networks with no
OSPF supporting routers.
OSPF Area Area area-1 (0.0.0.0) The corresponding interface belongs to the selected
area-2 … area-8 area.
OSPF Priority Priority 0 … 1 … 255 The priority value is used in the negotiations process in
order 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 Authentica- Key <character string> The configuration of the authentication key for a certain
tion interface is depending on the selection for “Authentica-
tion” for the appropriate area.
Make sure to configure identical keys for all OSPF inter-
faces on a common network segment.
Auth. = none: The parameter is not applicable.
Auth. = Simple: max. 8 characters
Auth. = MD5: max. 16 characters
OSPF Metric Automatic  By default, the metric is calculated automatically from
the specified interface bandwidth:
metric = 100’000 / bandwidth in kbit/s
 The OSPF metric is derived from the configured manual
metric value.
Manual Metric 0 … 65’535 The OSPF routing table calculations can be affected
with manual OSPF metrics. This feature should how-
ever be used by OSPF experts only.
OSPF Timers Hello Interval 1 … 10 … 65535 s Time interval for sending of hello packets on that inter-
face. All OSPF routers that are attached to the same
network must agree on the same hello interval.
Router Dead Inter- 0 … 40 … 3600 s The time before a neighbouring router is declared down
val after missing the hello packets.
Transmission Delay 0 … 1 … 3600 s The time it takes to transmit a link state update packet
over this interface. LSAs contained in the update packet
must have their age incremented by this amount before
transmission.
Retransmission 0 … 5 … 3600 s Time interval between LSA retransmissions for adjacen-
Delay cies belonging to this interface. Also used when retrans-
mitting database description and link state request
packets.
8.6.3.5 AP: / 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.

163
ETAG1
Table 52: AP: / unit-x / port-r, Configuration - RIP

RIP Enabled RIP Enabled  RIP can be enabled or disabled individually for each
 router port.
RIP Mode Mode Active The usual mode to configure a RIP router interface.
Passive No RIP protocol packets are sent or received on this
interface, but the network that is connected to the inter-
face is still advertised 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
Authentication support
None / RIPv2 Support of RIPv2 only, without authentication support
None / RIPv1 And Support of both RIPv1 and RIPv2, without authentica-
RIPv2 tion support
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
character 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.
8.6.3.6 AP: / 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.
The ETAG1 can participate on one or two virtual routers over the same inter-
face. Therefore two parameter sets “VRRP A” and “VRRP B” are provided.

163
ETAG1
Descriptions in this paragraph are correspondingly applicable for “VRRP A”

and “VRRP B”.
Table 53: AP: / unit-x / port-r, Configuration - VRRP A/B

VRRP Enabled VRRP Enabled  The ETAG1 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 same
LAN, each virtual router entity is identified with the vir-
tual router ID.
Priority Priority 0 …100 … 255 The router with the highest priority is selected as 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 (same
the corresponding virtual router ID) must use the same virtual IP address.
interface
Advertise Interval Advertise Interval 1 … 255 s The time interval in seconds each virtual router member
sends advertisements. A virtual router member is con-
sidered as down after 3 missing advertisements.
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.

163
ETAG1
8.6.3.7 AP: / unit-x / port-r, Configuration - Ingress Rate Limiter
Table 54: AP: / unit-x / port-r, Configuration - Ingress Rate Limiter

Rate Limiter Rate Limiter Ena-  By default the ingress rate limiter is disabled, i.e. the
bled  corresponding input bandwidth for the Ethernet front
ports is 100 Mbit/s.
Committed Informa- 64 … 100’000 kbit/s The Committed Information Rate (CIR) when limiting is
tion Rate enabled.
Committed Burst 1 … 256 kB The Committed Burst Size (CBS) for the limitation pro-
Size cess, 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.
8.6.3.8 AP: / unit-x / port-r, Configuration - PHY

163
ETAG1
Table 55: AP: / unit-x / port-r, Configuration - PHY

PHY Mode PHY Mode Autonegotiation With the LAN mode configuration an Ethernet port
10 Mbit/s Full Duplex can be forced to work in a specific operation mode
or allowing the port to select the best mode automat-
10 Mbit/s Half Duplex ically by negotiating with the appropriate peer entity.
100 Mbit/s Full Duplex By default the LAN mode is set to “Auto Negotia-
tion”.
100 Mbit/s Half Duplex
8.6.4 AP: / unit-x / port-r, Fault Management

Table 56: AP: / unit-x / port-r, Fault Management

Affecting Severity
LOS Loss Of Signal Communication Alarm  Major No input signal detected on the port
8.6.5 AP: / unit-x / port-r, Performance Management

groups are available for the ETAG1 Ethernet ports:
• “RSTP Interface” group, see section AP: / unit-x / port-r, Performance
Management - RSTP Interface (on page 107).
• “MIB-2 Interface Table” group, see section AP: / unit-x / port-r, Perfor-
mance Management - MIB-2 Interface Table (on page 107).

Counter interval RSTP Interface MIB-2 Interface
Table
User Counter yes yes
History 15min yes yes
History 24h yes yes
Alarm 15min no no
Alarm 24h no no

163
ETAG1
8.6.5.1 AP: / unit-x / port-r, Performance Management - RSTP Interface
Table 58: PM group: RSTP Interface

In BPDUs Number of incoming Bridge Protocol Data Units.
Out BPDUs Number of outgoing Bridge Protocol Data Units.
Invalid BPDUs Number of invalid incoming Bridge Protocol Data
Units.
Forward Transitions Number of port state transitions from Discarding or
Learning to Forwarding.
8.6.5.2 AP: / unit-x / port-r, Performance Management - MIB-2 Interface Table

In Octets Number of ingress octets.
In Packets Number of ingress packets.
In Discards Number of ingress discarded packets.
In Errors Number of ingress errors.
Out Octets Number of egress octets.
Out Packets Number of egress packets.
Out Discards Number of egress discarded packets.
Out Errors Number of egress errors.
8.6.6 AP: / unit-x / port-r, Status
8.6.6.1 AP: / unit-x / port-r, Status - Bridge
Please note:
The bridge status for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to one of the eight bridge instances.

163
ETAG1
Table 60: AP: / unit-x / port-r, Status - Bridge

RSTP RSTP Enabled  RSTP is enabled on the internal port
 RSTP is disabled on the internal port
1
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 1 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 forwarded on the port
Designated Bridge, The RSTP Designated Bridge in respect to a port
Priority denotes the bridge on the other side of the point-to-point
Designated Bridge, link or the designated bridge on the LAN segment.
MAC Address
Edge Port  No RSTP peer bridge attached on this port

Point to Point  The port is connected by a point-to-point LAN segment
 to exactly one other bridge.
Effective Port Path The port path cost is calculated from the port bandwidth
Cost and is dependent on the configured path cost version. In
case of manual port path cost, this value is equal to the
configured value.
1. 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.

163
ETAG1
8.6.6.2 AP: / unit-x / port-r, Status - Router
Please note:
The router status for the corresponding Ethernet front port is only meaning-
ful, if the port is assigned to the router.
Table 61: AP: / unit-x / port-r, Status - Router

Router If Status IP MTU Size Maximal size of transmission unit
8.6.6.3 AP: / unit-x / port-r, Status - OSPF
Please note:
The OSPF status for the corresponding Ethernet front port is only meaning-

163
ETAG1
Table 62: AP: / unit-x / port-r, Status - OSPF

OSPF Status Status Designated router This router is advertising the connected Ethernet net-
work
Backup designated This router is elected as backup for the advertising of
router the connected Ethernet network
Other designated This router is neither designated router nor backup des-
router ignated 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 correspond-
ing port
b) the corresponding layer 2 link is down
Designated Router The currently active designated router on the connected
network (for Ethernet ports and VLAN interfaces only)
Backup Designated The currently active backup designated router on the
Router network (for Ethernet ports and VLAN interfaces only)
8.6.6.4 AP: / unit-x / port-r, Status - VRRP A/B
Please note:
The VRRP status for the corresponding Ethernet front port is only meaning-
The ETAG1 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 paragraph are correspondingly applicable for
“VRRP A” and “VRRP B”.

163
ETAG1
Table 63: AP: / unit-x / port-r, Status - VRRP A/B

VRRP Status Virtual MAC MAC address of the virtual router if this interface is the
Address VRRP master. If this interface is VRRP backup, the dis-
played value is meaningless.
Status Master The ETAG1 unit acts as master for the corresponding
virtual router.
Backup The ETAG1 unit acts as backup for the corresponding
virtual router.
Initialize Transient state
Up Time s Time in seconds since the corresponding virtual router
is up.
8.6.6.5 AP: / unit-x / port-r, Status - PHY
Table 64: AP: / unit-x / port-r, Status - PHY

PHY State Speed 10 Mbit/s The currently active interface speed. Can be the result
100 Mbit/s of an automatic negotiation process or user configured.
Duplex Half Duplex The currently active interface mode. Can be the result of
Full Duplex an automatic negotiation process or user configured.
IEEE802.3 Flow Flow control is not supported by ETAG1.

Control

163
ETAG1
8.6.6.6 AP: / unit-x / port-r, Status - Interface
Table 65: AP: / unit-x / port-r, Status - Interface

MAC Address MAC Address Each Ethernet front port has its own unique MAC
address.

163
ETAG1
8.7 AP: / unit-x / router
8.7.1 AP: / unit-x / router, Overview

XMC22”.
8.7.2 AP: / unit-x / router, Main

XMC22”.

163
ETAG1
8.7.3 AP: / unit-x / router, Configuration
8.7.3.1 AP: / unit-x / router, Configuration - Router

163
ETAG1
Table 66: AP: / unit-x / router, Configuration - Router

OSPF Redistribute Connected, Con-  Route information for a network that is directly con-
nected nected but not enabled for OSPF is advertised to the
OSPF AS.
 Route information for a network that is directly con-
nected but not enabled for OSPF is not advertised to
the OSPF AS.
Connected, Metric 0 … 65535 Corresponding metric for directly connected networks
Static, Static  Static routes that are defined on the local router are dis-
tributed to the OSPF AS (default)
 Static routes from the local router are not distributed
Static, Metric 0 … 65535 Corresponding metric for static routes
Default Information  A default route redistributed by another router is
Originate, Default adopted by OSPF.
 A default route redistributed by another router is not
adopted by OSPF.
Default Information  If there is no default route available OSPF distributes a
Originate, Always summary default route.
 If there is no default route available OSPF distributes no
default route.
RIP, RIP  Route information that has been learned from a con-
nected RIP network is distributed to the OSPF AS.
 No route information from RIP networks is distributed in
the OSPF AS.
RIP, Metric 0 … 65535 Corresponding metric for route information from RIP
networks
RIP Redistribute Connected, Con-  Route information for a network that is directly con-
nected nected but not enabled for RIP is exchanged on active
RIP interfaces.
 Route information for a network that is directly con-
nected but not enabled for RIP is not exchanged on
active RIP interfaces.
Connected, Metric 0 … 15 Corresponding metric for directly connected networks
Static, 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
Static, Metric 0 … 15 Corresponding metric for static routes
Default Information  A default route redistributed by another router is
Originate, Default adopted by RIP.
 A default route redistributed by another router is not
adopted by RIP.
OSPF, OSPF  Route information that has been learned from a con-
nected OSPF AS is exchanged on active RIP inter-
faces.
 No route information from a possible OSPF AS is
exchanged.
OSPF, Metric 0 … 15 Corresponding metric for route information from OSPF
AS

163
ETAG1
8.7.3.2 AP: / unit-x / router, Configuration - StaticRoutes
Table 67: AP: / unit-x / router, Configuration - StaticRoutes

Static Route Table IP Address Any valid IP net- The destination / mask pair unambiguously identifies an
IP Mask work address / net- IP address range, where the corresponding static route
work mask is pointing to. The default destination 0.0.0.0 / 0.0.0.0
combination contains the whole IP address range.
Gateway IP valid IP address Any IP address in a directly connected network can be
Address 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
8.7.4 AP: / unit-x / router, Status
8.7.4.1 AP: / unit-x / router, Status - ARP Table

163
ETAG1
Table 68: AP: / unit-x / router, Status - ARP Table

ARP Table IP Address The IP address / MAC address relation is the result of
MAC Address an ARP request and is valid for the LAN segment con-
nected by the corresponding interface.
Interface On this interface the IP address / MAC address relation
has been learned.
8.7.4.2 AP: / unit-x / router, Status - Routing Table
Table 69: AP: / unit-x / router, Status - Routing Table

Routing Table Destination Address The destination address / mask pair unambiguously
Destination Mask identifies an IP address range.
Gateway Address The address, where the packets for the corresponding
destination are sent to.
Interface physical router The destination network is connected either to an Ether-
interface net front port or to a TDM interface.
VLAN interface The destination network is connected to a VLAN inter-
face
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

163
ETAG1
8.7.4.3 AP: / unit-x / router, Status - Ping Command
Table 70: AP: / unit-x / router, Status - Ping Command

Ping Command Destination Address IPv4 address of the ping target
Number Of 1 … 10 Number of ping requests to be executed
Requests
Packet Size 28 … 100 … 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
8.7.4.4 AP: / unit-x / router, Status - Traceroute Command

163
ETAG1
Table 71: AP: / unit-x / router, Status - Traceroute Command

Trace Route Com- Destination Address IPv4 address of the traceroute target
mand

163
ETAG1
8.8 AP: / unit-x / router / ospf
8.8.1 AP: / unit-x / router / ospf, Overview

XMC22”.
8.8.2 AP: / unit-x / router / ospf, Main

XMC22”.
8.8.3 AP: / unit-x / router / ospf, Status
8.8.3.1 AP: / unit-x / router / ospf, Status - Link State
Table 72: AP: / unit-x / router / ospf, Status - Link State

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

163
ETAG1
8.8.3.2 AP: / unit-x / router / ospf, Status - External Link State
Table 73: AP: / unit-x / router / ospf, Status - External Link State
OSPF 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.8.3.3 AP: / unit-x / router / ospf, Status - Neighbour Table
Table 74: AP: / unit-x / router / ospf, Status - Neighbour Table

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 bidirec-
tional communication 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 desig-
nated router it will establish full adjacency to all OSPF
routers on the Ethernet subnet.
Source The router’s IP address on the corresponding interface

163
ETAG1
8.9 AP: / unit-x / router / ospf / area-s
Though the OSPF standard does not limit the number of areas, the ETAG1
implementation supports 8 areas, with <s> ranging from 1 to 8.
8.9.1 AP: / unit-x / router / ospf / area-s, Overview

XMC22”.
8.9.2 AP: / unit-x / router / ospf / area-s, Main

XMC22”.

163
ETAG1
8.9.3 AP: / unit-x / router / ospf / area-s, Configuration
8.9.3.1 AP: / unit-x / router / ospf / area-s, Configuration - OSPF
Table 75: AP: / unit-x / router / ospf / area-s, Configuration - OSPF

OSPF Area Ena- OSPF Area Ena-  Administrative control for the corresponding area
bled 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 configured area address range, e.g. the net-
work address of the first address range.

163
ETAG1
Table 75: AP: / unit-x / router / ospf / area-s, Configuration - OSPF (continued)
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 0 … 4’294’967’295 If the stub area has more than one area border router,
Cost the route calculation of all routers in the stub areas can
be guided with the advertised stub cost. Meaningful for
border routers only.
OSPF Area Authen- Authentication None No authentication is used in OSPF hello- and LSA-
tication Mode packets
Simple Authentication with a plain text string is used in OSPF
hello- and LSA-packets
MD5 Authentication with a MD5 hash is used in OSPF hello-
and LSA-packets.
OSPF Area Ranges Enabled  Administrative control for the corresponding area
 address range
IP Address Any valid IP net- The address / mask pair unambiguously identifies an IP
IP Mask work address / net- address range. The specified address ranges must not
work mask overlap.
combination
Advertise  The corresponding address range is advertised
throughout the AS.
 The corresponding address range is not advertised, it is
therefore a hidden address range.

163
ETAG1
8.9.4 AP: / unit-x / router / ospf / area-s, Status
8.9.4.1 AP: / unit-x / router / ospf / area-s, Status - Link State
Table 76: AP: / unit-x / router / ospf / area-s, Status - Link State
OSPF Area State Area Border Rout- Number of border routers in the corresponding area
ers
AS Routers Total number of routers in the OSPF AS
Link State Adver- Number of entries in the OSPF link state data base
tisements
Area LSA Check-
sum

163
ETAG1
8.10 AP: / unit-x / router / rip
8.10.1 AP: / unit-x / router / rip, Overview

XMC22”.
8.10.2 AP: / unit-x / router / rip, Status
8.10.2.1 AP: / unit-x / router / rip, Status - Rip State
Table 77: AP: / unit-x / router / rip, Status - Rip State

Rip State Address Any valid IP This IP address range as specification for a learned
Mask address / mask route information
combination
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

163
ETAG1
8.11 AP: / unit-x / tdmInterfaces
8.11.1 AP: / unit-x / tdmInterfaces, Overview

XMC22”.
8.11.2 AP: / unit-x / tdmInterfaces, Main

XMC22”.

163
ETAG1
8.11.3 AP: / unit-x / tdmInterfaces, Configuration
8.11.3.1 AP: / unit-x / tdmInterfaces, Configuration - TDM
Delete TDM interfaces dialogues:

163
ETAG1
Table 78: AP: / unit-x / tdmInterfaces, Configuration - TDM

Available TDM Available TDM 0 … 64 Up to 64 TDM interfaces can be created, the allocation
Interfaces Interfaces between MAC HDLC, PPP and MLPPP is up to the
(read only) users demand.
Largest Available n=0 … 32 The largest available bandwidth is oriented on the
Bandwidth capacity of an E1 link. N=32 (2048 kbit/s) is usable with
a P12 (transparent) link. G.704 structured links offer
bandwidth in the range of n = 1 … 31 (n = 1 … 30 with
CAS).
Total Free Band- 0 … 16’384 kbit/s Bandwidth quote for TDM Access = 8x2 Mbit/s
width 0 … 32’768 kbit/s Bandwidth quote for TDM Access = 16x2 Mbit/s
Create MAC HDLC Bandwidth P12 (Transparent) Please be aware of the different P12 handling depend-
Interface … ing on the TDM access 8x2 Mbit/s or 16x2 Mbit/s. See
also paragraph 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
in steps of 2
MAC HDLC Inter- machdlc-1 … Only unused interfaces are offered for selection
face machdlc-64
Create PPP Inter- Bandwidth Same as for MAC HDLC interface creation
face … PPP Interface ppp-1 … ppp-64
Create MLPPP No Of Members 1…8 Up to 8 identical ppp links can be arranged in a mlppp
Interface … bundle.
Bandwidth For Each Same as for MAC HDLC interface creation
Member
MLPPP Interface mlppp-1 …
mlppp-64
Delete MAC HDLC MAC HDLC Inter- Existing MAC HDLC The selected interface is not deleted, unless the user
Interface … face interfaces positively acknowledges the corresponding warning
Delete PPP Inter- PPP Interface Existing PPP inter- message:
face … faces
Delete MLPPP MLPPP Interface Existing MLPPP
Interface … interfaces

163
ETAG1
8.12 AP: / unit-x / tdmInterfaces / machdlc-t
8.12.1 AP: / unit-x / tdmInterfaces / machdlc-t, Overview

XMC22”.
− “Overview - CTP”
management function, please refer to [314] User Guide “TDM Services and
Cross Connections in XMC20”.
8.12.2 AP: / unit-x / tdmInterfaces / machdlc-t, Main

XMC22”.
8.12.2.1 AP: / unit-x / tdmInterfaces / machdlc-t, Main - Admin And Oper Status
Table 79: AP: / unit-x / tdmInterfaces / machdlc-t, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the TDM
tus Down interface (RFC 2863).

Down TDM interface (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.12.3 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration
8.12.3.1 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - Interface Assignment
The interface assignment is the same for all interfaces. Please refer to sec-
tion 8.6.3.1 "AP: / unit-x / port-r, Configuration - Interface Assignment" (on
page 98).
8.12.3.2 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - Bridge
Please note:
The bridge configuration for the corresponding interface is only meaningful, if
it is assigned to one of the eight bridge instances. For any other assignment,
The bridge configuration is the same for all interfaces. Please refer to section
8.6.3.2 "AP: / unit-x / port-r, Configuration - Bridge" (on page 98).
8.12.3.3 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - Router
Please note:
The router configuration for the corresponding interface is only meaningful, if
it is assigned to the router. For any other assignment, these parameters are
ignored.
The router configuration is the same for all interfaces. Please refer to section
8.6.3.3 "AP: / unit-x / port-r, Configuration - Router" (on page 100).
8.12.3.4 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - OSPF
Please note:
The OSPF configuration for the corresponding interface is only meaningful, if
ignored.
The OSPF configuration is the same for all interfaces. Please refer to section
8.6.3.4 "AP: / unit-x / port-r, Configuration - OSPF" (on page 101).
8.12.3.5 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - RIP
Please note:
The RIP configuration for the corresponding interface is only meaningful, if it
is assigned to the router. For any other assignment, these parameters are
ignored.
The RIP configuration is the same for all interfaces. Please refer to section
8.6.3.5 "AP: / unit-x / port-r, Configuration - RIP" (on page 102).

163
ETAG1
8.12.3.6 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - TDM
Table 80: AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - TDM

Bandwidth Bandwidth 64 … 2048 kbit/s The configured bandwidth on the interface (read only).
The bandwidth is configured when the interface is cre-
ated.
8.12.3.7 AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - CTP
Table 81: AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - CTP

CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is P0_nc,
P12 i.e. n x 64 kbit/s or P12, i.e. 2048 kbit/s.
n 1 … 32 Number of timeslots in case of P0_nc. The possible

range is from 1 to 32.
Timeslot(s) The timeslot(s) property of a ETAG1 TDM interface is
empty.
Connected to CTPs Remote CTP <MO address> Address string of a connections remote end. Without a
connection the parameter is empty

163
ETAG1
Table 81: AP: / unit-x / tdmInterfaces / machdlc-t, Configuration - CTP (continued)

Connection Index 0 … 65’535 Index of a connection assigned to the interface. Without
a connection the parameter is empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The interface is the ending point of a connection.
Please refer to [314] User Guide “TDM Services and
a-End Working The interface is the working starting point of a protected
or unprotected connection.
a-End Protecting The interface is the protecting starting point of a pro-
tected connection.
Remote Role z-End The CTP at the connections remote end is the ending
point of a connection.
Please refer to [314] User Guide “TDM Services and
a-End Working The CTP at the connections remote end is the working
starting point of a protected or unprotected connection.
a-End Protecting The CTP at the connections remote end is the protect-
ing starting point of a protected connection.
z-End Configuration Revertive Protection  Enable revertive protection switching.
Switching  The z-End will preferably select the working a-End.
Non-revertive protection switching is only available for
participants with the number of timeslots n=1.
Non-revertive protection switching for n>1 will be availa-
ble in a future release,
CAS AIS Supervi-  Use CAS AIS as protection switching criterion.
sion 
Switch-Over Log-  Enable the logging of the protection switch-over events.
ging 
8.12.4 AP: / unit-x / tdmInterfaces / machdlc-t, Fault Management

Table 82: AP: / unit-x / tdmInterfaces / machdlc-t, Fault Management

ID Fault Event Type Traffic Default Description
Cause Affecting Severity
TSF Trail Signal Communication Alarm  Major Trail signal fail (TSF) from the P12 transport
Failure unit is active, or
CAS AIS active (only available if CAS AIS
supervision is enabled).
In a protected connection the working AND
the protecting path have failed.

163
ETAG1
Table 82: AP: / unit-x / tdmInterfaces / machdlc-t, Fault Management (continued)

RTSF Redundant Communication Alarm  Minor Trail signal fail (TSF) from the P12 transport
Trail Signal unit is active, or
Failure CAS AIS active (only available if CAS AIS
In a protected connection the working OR the
protecting path has failed.
In an unprotected connection this fault cause
is not applicable.
8.12.5 AP: / unit-x / tdmInterfaces / machdlc-t, Performance Management

groups are available for the ETAG1 MAC HDLC interfaces:
• “RSTP Interface” group, see section AP: / unit-x / tdmInterfaces / mach-
dlc-t, Performance Management - RSTP Interface (on page 134).
• “MIB-2 Interface Table” group, see section AP: / unit-x / tdmInterfaces /
machdlc-t, Performance Management - MIB-2 Interface Table (on
page 134).
• “Protection” group, see section AP: / unit-x / tdmInterfaces / machdlc-t,
Performance Management - Protection (on page 135).

Counter interval RSTP Interface MIB-2 Interface Protection
Table
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no no no
Alarm 24h no no no
8.12.5.1 AP: / unit-x / tdmInterfaces / machdlc-t, Performance Management - RSTP Interface

8.12.5.2 AP: / unit-x / tdmInterfaces / machdlc-t, Performance Management - MIB-2 Interface

Table


163
ETAG1
8.12.5.3 AP: / unit-x / tdmInterfaces / machdlc-t, Performance Management - Protection
Table 86: PM group: Protection

8.12.6 AP: / unit-x / tdmInterfaces / machdlc-t, Status
8.12.6.1 AP: / unit-x / tdmInterfaces / machdlc-t, Status - Bridge
Please note:
The bridge status for the corresponding interface is only meaningful, if it is
assigned to one of the eight bridge instances.
The bridge status is the same for all interfaces. Please refer to section
8.6.6.1 AP: / unit-x / port-r, Status - Bridge (on page 107).
8.12.6.2 AP: / unit-x / tdmInterfaces / machdlc-t, Status - Router
Please note:
The router status for the corresponding interface is only meaningful, if it is
assigned to the router.
The router status is the same for all interfaces. Please refer to section
8.6.6.2 AP: / unit-x / port-r, Status - Router (on page 109).
8.12.6.3 AP: / unit-x / tdmInterfaces / machdlc-t, Status - OSPF
Please note:
The OSPF status for the corresponding interface is only meaningful, if it is
The OSPF status is the same for all interfaces. Please refer to section
8.6.6.3 AP: / unit-x / port-r, Status - OSPF (on page 109).
8.12.6.4 AP: / unit-x / tdmInterfaces / machdlc-t, Status - Link

163
ETAG1
Table 87: AP: / unit-x / tdmInterfaces / machdlc-t, Status - Link

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
8.12.6.5 AP: / unit-x / tdmInterfaces / machdlc-t, Status - CTP
Please note:
TDM cross connection is generic for all TDM service units. For more infor-
mation refer to [314] User Guide “TDM Services and Cross Connections in
XMC20”.

163
ETAG1
Table 88: AP: / unit-x / tdmInterfaces / machdlc-t, Status - CTP

Trail Status Working Trail, Managed object address of the a-End Working CTP
Remote CTP
Working Trail, Sta- OK No failure on the received signal
tus SF Signal Fail status on the received signal
CAS AIS CAS AIS status in the received signal, i.e. an all ‘1’ sig-
nal
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 connec-
tion.
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’ sig-
nal
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 connec-
tion.
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 Work-
ing remote CTP
Force Protecting Force the selector to use the trail from the a-End Pro-
tecting 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 Protecting Prefer the trail from the a-End Protecting remote CTP -
use this trail only if the fault status is not worse than the
fault status of the working trail

163
ETAG1
8.13 AP: / unit-x / tdmInterfaces / mlppp-u
8.13.1 AP: / unit-x / tdmInterfaces / mlppp-u, Overview

XMC22”.
8.13.2 AP: / unit-x / tdmInterfaces / mlppp-u, Main

XMC22”.
8.13.2.1 AP: / unit-x / tdmInterfaces / mlppp-u, Main - Admin And Oper Status
Table 89: AP: / unit-x / tdmInterfaces / mlppp-u, Main - Admin And Oper Status

Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.13.3 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration
8.13.3.1 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - MLPPP
Table 90: AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - MLPPP

Create Member … Bandwidth P12 (Transparent) Please be aware of the different P12 handling depend-
ing on the TDM access 8x2 Mbit/s or 16x2 Mbit/s. See
also paragraph 5.3.2 Unit mode “8 x 2Mbit/s” versus “16
x 2Mbit/s” (on page 29).
in steps of 1
in steps of 2
Unused MLPPP member-1 … mem- Selection list of all unused MLPPP members
Members ber-64
Delete Member … Used Members Selection list of all currently configured MLPPP mem-
bers
8.13.3.2 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - Interface Assignment
page 98).
8.13.3.3 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - Bridge
Please note:

163
ETAG1
8.13.3.4 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - Router
Please note:
ignored.
8.13.3.5 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - OSPF
Please note:
ignored.
8.13.3.6 AP: / unit-x / tdmInterfaces / mlppp-u, Configuration - RIP
Please note:
ignored.
8.13.4 AP: / unit-x / tdmInterfaces / mlppp-u, Fault Management

Table 91: AP: / unit-x / tdmInterfaces / mlppp-u, Fault Management

Affecting 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

163
ETAG1
8.13.5 AP: / unit-x / tdmInterfaces / mlppp-u, Performance Management

groups are available for the ETAG1 MLPPP interfaces:
• “RSTP Interface” group, see section AP: / unit-x / tdmInterfaces / mlppp-
u, Performance Management - RSTP Interface (on page 141).
mlppp-u, Performance Management - MIB-2 Interface Table (on
page 141).

Table
History 24h yes yes
Alarm 15min no no
Alarm 24h no no
8.13.5.1 AP: / unit-x / tdmInterfaces / mlppp-u, Performance Management - RSTP Interface

8.13.5.2 AP: / unit-x / tdmInterfaces / mlppp-u, Performance Management - MIB-2 Interface

Table

8.13.6 AP: / unit-x / tdmInterfaces / mlppp-u, Status
8.13.6.1 AP: / unit-x / tdmInterfaces / mlppp-u, Status - Bridge
Please note:

163
ETAG1
8.13.6.2 AP: / unit-x / tdmInterfaces / mlppp-u, Status - Link
Table 95: AP: / unit-x / tdmInterfaces / mlppp-u, Status - Link

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 Number of members that are currently up and running
Up
Maximum Recon- Maximum IP packet size on octets after the fragment
structed Receive reconstruction process.
Unit Note that a client packet is split into fragments if the
packet size is larger than the IP MTU size.
8.13.6.3 AP: / unit-x / tdmInterfaces / mlppp-u, Status - Router
Please note:
8.13.6.4 AP: / unit-x / tdmInterfaces / mlppp-u, Status - OSPF
Please note:

163
ETAG1
8.14 AP: / unit-x / tdmInterfaces / mlppp-u / member-v
8.14.1 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Overview

XMC22”.
8.14.2 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Main

XMC22”.
8.14.2.1 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Main - Admin And Oper Status
Table 96: AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Main - Admin And Oper Status

Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.14.3 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Configuration
8.14.3.1 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Configuration - TDM
The TDM configuration is the same for all TDM interfaces. Please refer to
section 8.12.3.6 "AP: / unit-x / tdmInterfaces / machdlc-t, Configuration -
TDM" (on page 132).
8.14.3.2 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Configuration - CTP
The CTP configuration is the same for all TDM interfaces. Please refer to
CTP" (on page 132).
8.14.4 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Fault Management

Table 97: AP: / unit-x / tdmInterfaces / machdlc-t, Fault Management

LOS Loss Of Sig- Communication Alarm  Major ML PPP member link down
nal
is not applicable.
8.14.5 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Performance

Management

groups are available for the ETAG1 ML PPP members:

163
ETAG1

mlppp-u / member-v, Performance Management - MIB-2 Interface Table
(on page 145).
• “Protection” group, see section AP: / unit-x / tdmInterfaces / mlppp-u /
member-v, Performance Management - Protection (on page 145).

Counter interval MIB-2 Interface Protection
Table
History 24h yes yes
Alarm 15min no no
Alarm 24h no no
8.14.5.1 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Performance Management - MIB-2

Interface Table

8.14.5.2 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Performance Management -

Protection

8.14.6 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Status
8.14.6.1 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Status - Link
The Link status is the same for all TDM interfaces. Please refer to section
8.12.6.4 AP: / unit-x / tdmInterfaces / machdlc-t, Status - Link (on page 135).
8.14.6.2 AP: / unit-x / tdmInterfaces / mlppp-u / member-v, Status - CTP
The CTP status is the same for all TDM interfaces. Please refer to section
8.12.6.5 AP: / unit-x / tdmInterfaces / machdlc-t, Status - CTP (on page 136).

163
ETAG1
8.15 AP: / unit-x / tdmInterfaces / ppp-w
8.15.1 AP: / unit-x / tdmInterfaces / ppp-w, Overview

XMC22”.
8.15.2 AP: / unit-x / tdmInterfaces / ppp-w, Main

XMC22”.
8.15.2.1 AP: / unit-x / tdmInterfaces / ppp-w, Main - Admin And Oper Status
Table 101: AP: / unit-x / tdmInterfaces / ppp-w, Main - Admin And Oper Status

Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.15.3 AP: / unit-x / tdmInterfaces / ppp-w, Configuration
8.15.3.1 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - Interface Assignment
page 98).
8.15.3.2 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - Bridge
Please note:
8.15.3.3 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - Router
Please note:
ignored.
8.15.3.4 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - OSPF
Please note:
ignored.
8.15.3.5 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - RIP
Please note:
ignored.

163
ETAG1
8.15.3.6 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - TDM
The TDM configuration is the same for all TDM interfaces. Please refer to
TDM" (on page 132).
8.15.3.7 AP: / unit-x / tdmInterfaces / ppp-w, Configuration - CTP
The CTP configuration is the same for all TDM interfaces. Please refer to
CTP" (on page 132).
8.15.4 AP: / unit-x / tdmInterfaces / ppp-w, Fault Management

Table 102: AP: / unit-x / tdmInterfaces / ppp-w, Fault Management

LOS Loss Of Sig- Communication Alarm  Major The PPP link is down.
nal
is not applicable.
8.15.5 AP: / unit-x / tdmInterfaces / ppp-w, Performance Management

groups are available for the ETAG1 PPP interfaces:
• “RSTP Interface” group, see section AP: / unit-x / tdmInterfaces / ppp-w,
Performance Management - RSTP Interface (on page 149).
ppp-w, Performance Management - MIB-2 Interface Table (on page 149).

163
ETAG1
• “Protection” group, see section AP: / unit-x / tdmInterfaces / ppp-w, Per-

formance Management - Protection (on page 149).

Counter interval RSTP Interface MIB-2 Interface Protection
Table
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no no no
Alarm 24h no no no
8.15.5.1 AP: / unit-x / tdmInterfaces / ppp-w, Performance Management - RSTP Interface

Units.
8.15.5.2 AP: / unit-x / tdmInterfaces / ppp-w, Performance Management - MIB-2 Interface Table

8.15.5.3 AP: / unit-x / tdmInterfaces / ppp-w, Performance Management - Protection

Switch-Over Number of protection switch-over events.

163
ETAG1
8.15.6 AP: / unit-x / tdmInterfaces / ppp-w, Status
8.15.6.1 AP: / unit-x / tdmInterfaces / ppp-w, Status - Bridge
Please note:
8.15.6.2 AP: / unit-x / tdmInterfaces / ppp-w, Status - Router
Please note:
8.15.6.3 AP: / unit-x / tdmInterfaces / ppp-w, Status - OSPF
Please note:
8.15.6.4 AP: / unit-x / tdmInterfaces / ppp-w, Status - Link
The Link status is the same for all TDM interfaces. Please refer to section
8.12.6.4 AP: / unit-x / tdmInterfaces / machdlc-t, Status - Link (on page 135).
8.15.6.5 AP: / unit-x / tdmInterfaces / ppp-w, Status - CTP
The CTP status is the same for all TDM interfaces. Please refer to section
8.12.6.5 AP: / unit-x / tdmInterfaces / machdlc-t, Status - CTP (on page 136).

163
ETAG1
8.16 AP: / unit-x / vlanInterfaces
8.16.1 AP: / unit-x / vlanInterfaces, Overview

XMC22”.
8.16.2 AP: / unit-x / vlanInterfaces, Main

XMC22”.
8.16.3 AP: / unit-x / vlanInterfaces, Configuration
8.16.3.1 AP: / unit-x / vlanInterfaces, Configuration - VLAN

163
ETAG1
Table 107: Parameters for menu /vlanInterfaces - Configuration - VLAN

Create VLAN Inter- VLAN Device port-1 … port-4 Ethernet front ports:
face … - ports that are not assigned may be connected to a
VLAN interface
- ports that are assigned to the router may be con-
nected to a VLAN interface
- ports that are assigned to a bridge must NOT be con-
nected to a VLAN interface
bridge-1 … bridge-8 Bridge instances may always be connected to a VLAN
interface.
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.
Delete VLAN Inter- VLAN Interface currently config- The selected VLAN interface is not deleted, unless the
face … ured VLAN inter- user positively acknowledges the corresponding warn-
faces ing message:

163
ETAG1
8.17 AP: / unit-x / vlanInterfaces / vif-z
8.17.1 AP: / unit-x / vlanInterfaces / vif-z, Overview

XMC22”.
8.17.2 AP: / unit-x / vlanInterfaces / vif-z, Main

XMC22”.
8.17.2.1 AP: / unit-x / vlanInterfaces / vif-z, Main - Admin And Oper Status
Table 108: AP: / unit-x / tdmInterfaces / ppp-w, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the VLAN

Down VLAN interface (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.17.3 AP: / unit-x / vlanInterfaces / vif-z, Configuration
8.17.3.1 AP: / unit-x / vlanInterfaces / vif-z, Configuration - Interface Assignment
page 98).
8.17.3.2 AP: / unit-x / vlanInterfaces / vif-z, Configuration - Router
8.17.3.3 AP: / unit-x / vlanInterfaces / vif-z, Configuration - OSPF
8.17.3.4 AP: / unit-x / vlanInterfaces / vif-z, Configuration - RIP
8.17.3.5 AP: / unit-x / vlanInterfaces / vif-z, Configuration - VRRP A/B
The VRRP A/B configuration for a VLAN interface is the same as for an
Ethernet interface. Please refer to section 8.6.3.6 AP: / unit-x / port-r, Config-
uration - VRRP A/B (on page 103).
8.17.4 AP: / unit-x / vlanInterfaces / vif-z, Performance Management

group is available for the ETAG1 VLAN interfaces:
• “MIB-2 Interface Table” group, see section AP: / unit-x / vlanInterfaces /
vif-z, Performance Management - MIB-2 Interface Table (on page 155).

Counter interval MIB-2 Interface
Table
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no

163
ETAG1
8.17.4.1 AP: / unit-x / vlanInterfaces / vif-z, Performance Management - MIB-2 Interface Table

8.17.5 AP: / unit-x / vlanInterfaces / vif-z, Status
8.17.5.1 AP: / unit-x / vlanInterfaces / vif-z, Status - OSPF
8.17.5.2 AP: / unit-x / vlanInterfaces / vif-z, Status - VRRP A/B
The VRRP A/B status is the same for the VLAN interfaces as for the Ether-
net interfaces. Please refer to section 8.6.6.4 AP: / unit-x / port-r, Status -
VRRP A/B (on page 110).
8.17.5.3 AP: / unit-x / vlanInterfaces / vif-z, Status - Interface
The Interface status is the same for the VLAN interfaces as for the Ethernet
interfaces. Please refer to section 8.6.6.6 AP: / unit-x / port-r, Status - Inter-
face (on page 112).

163
ETAG1
8.18 AP: / unit-x / internalPorts
8.18.1 AP: / unit-x / internalPorts, Overview

XMC22”.
8.18.2 AP: / unit-x / internalPorts, Main

XMC22”.

163
ETAG1
8.19 AP: / unit-x / internalPorts / port-1
8.19.1 AP: / unit-x / internalPorts / port-1, Overview

XMC22”.
8.19.2 AP: / unit-x / internalPorts / port-1, Main

XMC22”.
8.19.2.1 AP: / unit-x / internalPorts / port-1, Main - Admin And Oper Status
Table 111: AP: / unit-x / internalPorts / port-1, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the internal
tus Down port (RFC 2863).

Down internal port (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down

163
ETAG1
8.19.3 AP: / unit-x / internalPorts / port-1, Configuration
8.19.3.1 AP: / unit-x / internalPorts / port-1, Configuration - Interface Assignment
page 98).
8.19.3.2 AP: / unit-x / internalPorts / port-1, Configuration - Bridge
Please note:
8.19.3.3 AP: / unit-x / internalPorts / port-1, Configuration - Router
Please note:
ignored.
8.19.3.4 AP: / unit-x / internalPorts / port-1, Configuration - OSPF
Please note:
ignored.
8.19.3.5 AP: / unit-x / internalPorts / port-1, Configuration - RIP
Please note:
ignored.

163
ETAG1
8.19.3.6 AP: / unit-x / internalPorts / port-1, Configuration - VRRP A/B
Please note:
The 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,
The VRRP A/B configuration for the internal port is the same as for an Ether-
net interface. Please refer to section 8.6.3.6 AP: / unit-x / port-r, Configura-
tion - VRRP A/B (on page 103).
8.19.3.7 AP: / unit-x / internalPorts / port-1, Configuration - Ingress Rate Limiter
The Ingress Rate Limiter configuration for the internal port is the same as for
an Ethernet interface. Please refer to section 8.6.3.7 AP: / unit-x / port-r,
Configuration - Ingress Rate Limiter (on page 105).
8.19.3.8 AP: / unit-x / internalPorts / port-1, Configuration - PHY
Table 112: AP: / unit-x / internalPorts / port-1, Configuration - PHY

PHY Mode PHY Mode 1000 Mbit/s Full Duplex The internal port is 1 Gbit/s full duplex and is not
user configurable
8.19.4 AP: / unit-x / internalPorts / port-1, Performance Management

groups are available for the ETAG1 internal port:
• “RSTP Interface” group, see section AP: / unit-x / internalPorts / port-1,
Performance Management - RSTP Interface (on page 160).
• “MIB-2 Interface Table” group, see section AP: / unit-x / internalPorts /
port-1, Performance Management - MIB-2 Interface Table (on page 160).

163
ETAG1

Table
History 24h yes yes
Alarm 15min no no
Alarm 24h no no
8.19.4.1 AP: / unit-x / internalPorts / port-1, Performance Management - RSTP Interface

Units.
8.19.4.2 AP: / unit-x / internalPorts / port-1, Performance Management - MIB-2 Interface Table

8.19.5 AP: / unit-x / internalPorts / port-1, Status
8.19.5.1 AP: / unit-x / internalPorts / port-1, Status - Bridge
Please note:
The bridge status for the internal port is only meaningful, if it is assigned to
one of the eight bridge instances.

163
ETAG1
8.19.5.2 AP: / unit-x / internalPorts / port-1, Status - Router
Please note:
The router status for the internal port is only meaningful, if it is assigned to
the router.
8.19.5.3 AP: / unit-x / internalPorts / port-1, Status - OSPF
Please note:
The OSPF status for the internal port is only meaningful, if it is assigned to
the router.
8.19.5.4 AP: / unit-x / internalPorts / port-1, Status - VRRP A/B
Please note:
The VRRP status for the internal port is only meaningful, if it is assigned to
the router.
The VRRP A/B status is the same for the internal port as for the Ethernet
interfaces. Please refer to section 8.6.6.4 AP: / unit-x / port-r, Status - VRRP
A/B (on page 110).
8.19.5.5 AP: / unit-x / internalPorts / port-1, Status - PHY
The PHY status is the same for the internal port as for the Ethernet inter-
faces. Please refer to section 8.6.6.5 AP: / unit-x / port-r, Status - PHY (on
page 111).
Please note:
The internal port speed is fixed to 1 Gbit/s and full duplex.
8.19.5.6 AP: / unit-x / internalPorts / port-1, Status - Interface
The Interface status is the same for the internal port as for the Ethernet inter-
faces. Please refer to section 8.6.6.6 AP: / unit-x / port-r, Status - Interface
(on page 112).

163
Annex User Manual
ETAG1
9 Annex
9.1 Associated XMC20 documents
Any version(s) and/or release(s) indicated with the below listed document
titles identify the specific state of the software and/or feature set at the crea-
tion time of the present document. If the present document is published as
part of a document collection, the hyperlinks might open a document valid for
a newer version/release. That updated version is valid in the context of all
units and features described in the document collection.
[012] Release Note “XMC20 System Release R6A”
[090] Open Source Software declaration
[201] System Description “XMC20 R6A”
[202] Safety Instructions “Precautions and safety”
[301] User Guide “XMC25 Installation”
[302] User Guide “XMC25/XMC23/XMC22”
[314] User Guide “TDM Services and Cross Connections in XMC20”
[341] Quick Guide “Ethernet Switching”
[355] User Manual “ECST”
[356] User Manual “Ethernet Switching”
[915] Technical Bulletin “Feature Licences for XMC20”
9.2 Technical support
Please refer to the KEYMILE Extranet (via http://www.keymile.com) for sup-

port contact information.

163
Annex User Manual
ETAG1
9.3 Product training
Training courses are available for a wide range of KEYMILE products and
applications.
For contact information, course descriptions, locations and dates, refer to the
Website: http://www.keymile.com, then select “Services - Training” from the
menu.

163

Etag1 Um

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Etag1 Um

Enviado por

Direitos autorais:

Formatos disponíveis

User Manual

Bridging/routing for Ethernet and TDM

Document PEC EN/LZTBU 372 121/1 RA

Document release XMC20 R6A | 27. April 2015

© KEYMILE April 2015 page 3 of 163 EN/LZTBU 372 121/1 RA

5.3 TDM WAN interfaces (PBUS connections) 29

7 Operation and Maintenance 69

© KEYMILE April 2015 page 4 of 163 EN/LZTBU 372 121/1 RA

8.15 AP: / unit-x / tdmInterfaces / ppp-w 146

© KEYMILE April 2015 page 5 of 163 EN/LZTBU 372 121/1 RA

Figure 1: Functional block diagram 9

© KEYMILE April 2015 page 6 of 163 EN/LZTBU 372 121/1 RA

1.1 Precautions and safety

1.2 Symbols and notations

This User Manual uses the following symbols:

NOTICE Non-observance could result in minor or moderate injury.

Risk of operating trouble!

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

© KEYMILE April 2015 page 7 of 163 EN/LZTBU 372 121/1 RA

1.4 Document history

Table 2: Document history

© KEYMILE April 2015 page 8 of 163 EN/LZTBU 372 121/1 RA

2.1 Functions and features overview

16x2 Mbit/s TDM WAN

Subrack internal Optical

Figure 1: Functional block diagram

• Functions of the internal port

© KEYMILE April 2015 page 9 of 163 EN/LZTBU 372 121/1 RA

• Functions of the interface

© KEYMILE April 2015 page 10 of 163 EN/LZTBU 372 121/1 RA

2.2 ETAG1 architectural block diagram

Figure 2: ETAG1 architectural block diagram

© KEYMILE April 2015 page 11 of 163 EN/LZTBU 372 121/1 RA

2.3 Unit view

Figure 3: ETAG1 unit view

© KEYMILE April 2015 page 12 of 163 EN/LZTBU 372 121/1 RA

3.1 Feature licences

Table 3: Functions and features overview relevant for this unit

For more information on features licences please refer to [915] Technical

3.2 Physical interfaces

Table 4: Internal Ethernet port (backplane)

Table 5: Ethernet ports on the front panel

© KEYMILE April 2015 page 13 of 163 EN/LZTBU 372 121/1 RA

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

Table 6: PBUS ports (backplane)

© KEYMILE April 2015 page 14 of 163 EN/LZTBU 372 121/1 RA

3.3 Logical interface functions

Table 7: Parameters, user configurable per interface

Table 8: Parameters for virtual interfaces

© KEYMILE April 2015 page 15 of 163 EN/LZTBU 372 121/1 RA

3.4 Networking functions

Table 9: OSI layer 2 data forwarding (bridging)

Table 10: OSI layer 3 data forwarding (routing)

Table 11: OSPF

© KEYMILE April 2015 page 16 of 163 EN/LZTBU 372 121/1 RA

Table 11: OSPF (continued)

Table 12: RIP

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

Table 14: QoS

© KEYMILE April 2015 page 17 of 163 EN/LZTBU 372 121/1 RA

Table 15: Protection

© KEYMILE April 2015 page 18 of 163 EN/LZTBU 372 121/1 RA