ULAF+

ACCEED 1102/04 Manual

Release 6.12
A3118-X642-R612-01
 ULAF+ ACCEED 1102/04 Manual

Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts can also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950. All equipment connected has to
comply with the safety standards applicable.

Copyright and Licenses

The ACCEED 1102/04 contains both proprietary software and Open Source Software.
The Open Source Software is licensed at no charge under the GNU General Public License (GPL) and
the GNU Lesser General Public License (LGPL). This Open Source Software was written by third
parties and enjoys copyright protection. One is entitled to use this Open Source Software under the
conditions set out in the GPL and LGPL licenses. In the event of conflicts between Albis Technologies´
license conditions and the GPL or LGPL license conditions, the GPL and LGPL conditions shall prevail
with respect to the Open Source portions of the software. The GPL and LGPL conditions for ACCEED
1102/04 are accessible on the Albis Technologies ULAF+ FTP server. The license conditions can also
be found at the following internet websites:
The GPL can be found under the following URL: http://www.gnu.org/copyleft/gpl.html
The LGPL can be found under the following URL: http://www.gnu.org/copyleft/lgpl.html

Copyright (C) Albis Technologies Ltd 2015

Albisriederstrasse 199
CH-8047 Zürich

Technical modifications possible

Technical specifications and features are binding only insofar as they are specifically and expressly
agreed upon in a written contract.

A3118-X642-R612-01 2 / 405
ULAF+ ACCEED 1102/04 Manual

Contents
1 Notes on product safety ................................................................................................................. 13
1.1 Representation conventions ................................................................................................. 14
1.2 Product Safety ...................................................................................................................... 15
Notes on protection against laser radiation ..................................................................... 15
Notes on permitted altitude and use of protection earth .................................................. 15
1.3 EMC ..................................................................................................................................... 16
1.4 Device handling .................................................................................................................... 17
Electrostatic Sensitive Devices (ESD) ............................................................................. 17
Inserting/ removing plug in units ...................................................................................... 17
Stacking the desktop units ............................................................................................... 17
Disposal of equipment and units ...................................................................................... 18
1.5 Over voltage protection ........................................................................................................ 19
Protection of a network element ...................................................................................... 19
2 Introduction ..................................................................................................................................... 20
2.1 ULAF+ documentation structure .......................................................................................... 21
2.2 ACCEED 1102/04 Manual Structure .................................................................................... 24
2.3 Representation conventions ................................................................................................. 25
ACCEED manual naming conventions ............................................................................ 25
2.4 ULAF+ System overview ...................................................................................................... 26
Service Interfaces ............................................................................................................ 27
Transmission Interfaces ................................................................................................... 27
MEF Carrier Ethernet Services attributes ........................................................................ 27
Management Systems ..................................................................................................... 28
ULAF+ Product Range ..................................................................................................... 29
3 Application overview....................................................................................................................... 32
3.1 ACCEED 1102/04 Overview ................................................................................................ 33
2 or 4 wire pairs SHDSL EFM unit ................................................................................... 33
Technical data.................................................................................................................. 35
2 or 4 wire pairs SHDSL EFM CPE ................................................................................. 36
Technical data.................................................................................................................. 36
3.2 Typical ACCEED 1102/04 applications ................................................................................ 38
Business Access .............................................................................................................. 38
Wholesale Carrier Ethernet Demarcation ........................................................................ 40
Utility / Campus ................................................................................................................ 41
3.3 System configurations .......................................................................................................... 42
Mechanics ........................................................................................................................ 43
HW options ...................................................................................................................... 43
ACCEED 1102/04 combinations ...................................................................................... 44
4 Quick Start Guide ........................................................................................................................... 45
4.1 Introduction........................................................................................................................... 46
4.2 HW setup.............................................................................................................................. 47
ACCEED 1102/04 Setup ................................................................................................. 47
Wiring ............................................................................................................................... 47
4.3 EFM link configuration .......................................................................................................... 48
LCT+ installation .............................................................................................................. 48
Management access configuration .................................................................................. 48
EFM-Link configuration .................................................................................................... 48
5 Installation ...................................................................................................................................... 51
5.1 General requirements/check list........................................................................................... 52
5.2 Power supply ........................................................................................................................ 54
Power supply to the plug in unit ....................................................................................... 54
Power supply to the desktop unit ..................................................................................... 54
5.3 Grounding concept ............................................................................................................... 59
5.4 Interfaces / pinning ............................................................................................................... 60
SHDSL interface .............................................................................................................. 61
Ethernet interfaces (10Base-T/100Base-Tx) ................................................................... 61
A3118-X642-R612-01 3 / 405
 ULAF+ ACCEED 1102/04 Manual

SFP slot interface............................................................................................................. 62

NMS interface (10/100 Base-T) ....................................................................................... 62
TDM (G.703) and Clock Interfaces .................................................................................. 62
LCT serial interface .......................................................................................................... 63
5.5 DIP switches......................................................................................................................... 64
5.6 Visual indications ................................................................................................................. 65
5.7 LCT+ SW installation............................................................................................................ 68
System requirements ....................................................................................................... 68
Installation of the Software .............................................................................................. 68
5.8 On site configuration ............................................................................................................ 76
Boot up ............................................................................................................................. 76
ACCEED 1102/04 management interfaces ..................................................................... 76
ACCEED 1102/04 access control of management interfaces ......................................... 81
SCC connections ............................................................................................................. 84
EFM link Setup................................................................................................................. 84
Remote Power Supply ..................................................................................................... 84
Power over Ethernet (PoE) .............................................................................................. 84
Time settings .................................................................................................................... 85
5.9 Maintenance functions ......................................................................................................... 86
Loopback ......................................................................................................................... 86
BER test ........................................................................................................................... 86
Switch port mirroring ........................................................................................................ 87
Trap suppression ............................................................................................................. 87
6 Configuration and operation ........................................................................................................... 88
6.1 Management access ............................................................................................................ 89
Token mechanism............................................................................................................ 89
6.2 LCT+..................................................................................................................................... 90
Introduction ...................................................................................................................... 90
Starting the LCT+ ............................................................................................................. 90
The graphical user interface ............................................................................................ 92
Title bar ............................................................................................................................ 94
Menu bar .......................................................................................................................... 94
Status bar ......................................................................................................................... 97
6.3 LCT+ Control area................................................................................................................ 99
Tree .................................................................................................................................. 99
Connection ..................................................................................................................... 101
User Management ......................................................................................................... 101
Download ....................................................................................................................... 102
6.4 LCT+ View area ................................................................................................................. 103
Ethernet View................................................................................................................. 103
6.5 LCT+ Table area ................................................................................................................ 104
Fault: Alarms .................................................................................................................. 107
Fault: Maintenance ........................................................................................................ 108
Fault: SOAM (Loopbacks) ............................................................................................. 109
Fault: Ping ...................................................................................................................... 110
Configuration: ACCEED 1102/04 .................................................................................. 111
Configuration: Summary ................................................................................................ 112
Performance: Line Parameters ...................................................................................... 113
Performance: Error Counters ......................................................................................... 114
Performance: BER Measurements ................................................................................ 115
Performance: Statistics .................................................................................................. 117
Performance: Utilization ................................................................................................. 117
Performance: Service Activation Testing (SAT) ............................................................ 117
Performance: Circuit Emulation Service (CES) ............................................................. 117
Search ............................................................................................................................ 117
6.6 LCT function blocks ............................................................................................................ 118
Save Configuration ........................................................................................................ 118
Load Configuration......................................................................................................... 120
Preview Mode ................................................................................................................ 121

A3118-X642-R612-01 4 / 405
 ULAF+ ACCEED 1102/04 Manual

Preferences .................................................................................................................... 121

6.7 CLI introduction .................................................................................................................. 125
CLI Modes ...................................................................................................................... 125
CLI Control ..................................................................................................................... 125
CLI Access ..................................................................................................................... 126
Token ............................................................................................................................. 128
User Management ......................................................................................................... 128
CLI Prompt ..................................................................................................................... 129
CLI Navigation ............................................................................................................... 129
Viewing Parameters ....................................................................................................... 131
Setting Parameters ........................................................................................................ 131
CLI configuration commands ......................................................................................... 133
CLI Show Commands .................................................................................................... 141
TFTP Server Setup ........................................................................................................ 148
6.8 Firmware upgrade .............................................................................................................. 150
Local Download ............................................................................................................. 150
Remote Download ......................................................................................................... 152
7 EFMC Aggregation ....................................................................................................................... 153
7.1 EFM Link ............................................................................................................................ 154
EFM Frame distribution ................................................................................................. 154
EFM LT Parameters....................................................................................................... 154
EFM CPE Parameters ................................................................................................... 155
7.2 SHDSL line ......................................................................................................................... 156
Transmission range ....................................................................................................... 156
Cable parameters .......................................................................................................... 157
Payload bit rate .............................................................................................................. 157
Noise level and type ...................................................................................................... 157
Transmission level ......................................................................................................... 157
SHDSL performance (max reach) ................................................................................. 158
SHDSL line Fault Management ..................................................................................... 161
SHDSL line configuration ............................................................................................... 161
SHDSL line performance ............................................................................................... 167
8 Ethernet Switch ............................................................................................................................ 173
8.1 ACCEED 1102/04 switching features at a glance.............................................................. 174
8.2 The Building Blocks of the Ethernet switch ........................................................................ 176
8.3 Port Control ........................................................................................................................ 178
Global switch port settings ............................................................................................. 178
Individual Switch Port Settings ...................................................................................... 180
Ethernet Loopbacks ....................................................................................................... 189
L2 Control Protocols ...................................................................................................... 194
8.4 Switch Control .................................................................................................................... 196
Forwarding Database .................................................................................................... 196
Learning Mode ............................................................................................................... 198
Aging Time ..................................................................................................................... 198
Port isolation .................................................................................................................. 199
Port mirroring ................................................................................................................. 200
L2PT .............................................................................................................................. 201
8.5 VLAN .................................................................................................................................. 205
VLAN mode.................................................................................................................... 205
VLAN Tag Naming Convention in ACCEED .................................................................. 206
Global VLAN settings ..................................................................................................... 207
Port Based VLAN Settings ............................................................................................. 219
Tag Protocol Identifier (TPID) list – Ingress port ........................................................... 220
Tag Protocol Identifier (TPID) list – Egress port ............................................................ 220
VLAN Filters ................................................................................................................... 221
8.6 Ethernet Switch Fault Management ................................................................................... 223
8.7 Ethernet Switch QoS handling ........................................................................................... 224
Packet QoS Attributes Set ............................................................................................. 224
Initial QoS Attribute Assignments .................................................................................. 225

A3118-X642-R612-01 5 / 405
 ULAF+ ACCEED 1102/04 Manual

Policing .......................................................................................................................... 228

Queuing ......................................................................................................................... 245
8.8 EVC Concept...................................................................................................................... 248
8.9 Protection ........................................................................................................................... 249
Linear Protection ............................................................................................................ 249
Ring Protection .............................................................................................................. 257
8.10 Statistics and Utilization ..................................................................................................... 268
Introduction .................................................................................................................... 268
Port statistics .................................................................................................................. 271
Policy statistics............................................................................................................... 273
QoS – Tx Queue statistics ............................................................................................. 274
Port based metering statistics ........................................................................................ 275
EVC statistics ................................................................................................................. 276
Utilization ....................................................................................................................... 277
9 Operation and Maintenance ......................................................................................................... 280
9.1 Link OAM............................................................................................................................ 281
Link OAM Configuration ................................................................................................. 281
Link OAM Fault Management ........................................................................................ 282
9.2 Service OAM ...................................................................................................................... 284
Domains and Maintenance Points ................................................................................. 284
Service OAM Fault Management................................................................................... 291
Service OAM Performance Monitoring .......................................................................... 301
9.3 Service Activation Test (Y.1564) ........................................................................................ 318
Measurement Principle .................................................................................................. 319
Measurement Sequence Details .................................................................................... 320
Format of Test Frames .................................................................................................. 322
SAT – General configuration ......................................................................................... 323
SAT – Configuration of the Test CoS Instances ............................................................ 324
Test execution................................................................................................................ 326
Results ........................................................................................................................... 326
Test Report .................................................................................................................... 328
10 CES – Circuit Emulation for TDM Services .............................................................................. 330
10.1 Introduction to TDM CES ................................................................................................... 332
What is CES ?................................................................................................................ 332
Motivation to do CES ..................................................................................................... 332
Technical Challenges .................................................................................................... 332
Payload Type and Encapsulation .................................................................................. 333
CES - Functional Components and Interfaces .............................................................. 334
CES operation principle ................................................................................................. 338
10.2 CES Applications with ACCEED ........................................................................................ 341
Interworking Scenario .................................................................................................... 342
10.3 Configuring CES ................................................................................................................ 344
Enabling CES and the TDM interface ............................................................................ 344
Configuring the CES parameters ................................................................................... 345
Configuring the Framer .................................................................................................. 347
CES clock synchronization ............................................................................................ 349
10.4 CES Performance Monitoring and Fault management ...................................................... 350
TDM performance counters ........................................................................................... 350
CES packet and jitter buffer performance ..................................................................... 351
CES Packet Statistics .................................................................................................... 352
CES / TDM Loopback .................................................................................................... 353
CES Alarming ................................................................................................................ 353
10.5 CES Operational Aspects .................................................................................................. 355
Planning CES................................................................................................................. 355
Trouble Shooting CES ................................................................................................... 355
11 General Board settings ............................................................................................................. 357
11.1 Board – general system information .................................................................................. 358
System Log .................................................................................................................... 359
Ressources .................................................................................................................... 360

A3118-X642-R612-01 6 / 405
 ULAF+ ACCEED 1102/04 Manual

Inventory ........................................................................................................................ 362

11.2 Alarm configuration ............................................................................................................ 363
Severity .......................................................................................................................... 363
Logging .......................................................................................................................... 364
11.3 Local ................................................................................................................................... 366
Information ..................................................................................................................... 366
SCC Configuration ......................................................................................................... 366
Maintenance .................................................................................................................. 366
Time Settings ................................................................................................................. 367
Management Access ..................................................................................................... 367
11.4 Synchronization .................................................................................................................. 374
Introduction .................................................................................................................... 374
Clock Source Selection .................................................................................................. 374
Supported Quality and Priority Values ........................................................................... 374
Clock Sources ................................................................................................................ 375
Clock Output Interfaces ................................................................................................. 376
Synchronization Fault Management .............................................................................. 377
12 Troubleshooting ........................................................................................................................ 378
12.1 Most common troubles ....................................................................................................... 379
SHDSL startup problems ............................................................................................... 379
Bit errors on the copper line ........................................................................................... 381
12.2 LED indications .................................................................................................................. 382
Power LED (1) ............................................................................................................... 382
Alarm LED (1) ................................................................................................................ 382
MAINT LED (1) .............................................................................................................. 383
PAF LED (1) ................................................................................................................... 383
ETH Px green LED (3), (4), (5) and (6).......................................................................... 383
NMS green LED (8) ....................................................................................................... 383
TDM x LED (9) und (10) ................................................................................................ 383
SHDSL x LED (12) ......................................................................................................... 384
12.3 Alarm list............................................................................................................................. 385
Aggregation Loss Alarm ................................................................................................ 385
APS-Failure Of Protocol Alarm ...................................................................................... 385
Attenuation Threshold Alarm ......................................................................................... 385
CES-AIS Alarm .............................................................................................................. 385
CES-ARE Alarm............................................................................................................. 386
CES-LOF Alarm ............................................................................................................. 386
CES-RAI Alarm .............................................................................................................. 386
Clock Not Available Alarm ............................................................................................. 386
Clock Squelched Alarm ................................................................................................. 386
Equipment Alarm ....................................................................................................... 387
ETH No Link Alarm .................................................................................................... 387
ETH No Path Available Alarm ................................................................................... 387
ETH-Protection Loss Alarm ....................................................................................... 387
ETH-Working Path Not Available Alarm .................................................................... 387
Firmware Type Mismatch Alarm ................................................................................ 388
LAG-Aggregation Loss .............................................................................................. 388
LAG-Aggregation Mismatch ...................................................................................... 388
LAG-Partial Aggregation Loss ................................................................................... 388
LFP Alarm .................................................................................................................. 389
LinkOAM-Critical Event Alarm ................................................................................... 389
LinkOAM-Dying Gasp Alarm ..................................................................................... 389
LinkOAM-Link Fault Alarm ........................................................................................ 389
LinkOAM-No Peer Alarm ........................................................................................... 390
Low Bandwidth Threshold Alarm ............................................................................... 390
Not Aggregated Alarm ............................................................................................... 390
NT Power Failure Alarm ............................................................................................ 391
Partial Aggregation Loss Alarm ................................................................................. 391
Power Failure Alarm .................................................................................................. 392

A3118-X642-R612-01 7 / 405
ULAF+ ACCEED 1102/04 Manual

Resource Shortage Alarm ......................................................................................... 392

SOAM-AIS Alarm ....................................................................................................... 392
SOAM-Avail Objective ............................................................................................... 392
SOAM-ErrorCCM Alarm ............................................................................................ 393
SOAM-FDICSF .......................................................................................................... 393
SOAM-FD Objective .................................................................................................. 393
SOAM-FLR Threshold ............................................................................................... 393
SOAM-IFDV Objective............................................................................................... 394
SOAM-LCK Alarm ..................................................................................................... 394
SOAM-LOSCSF ........................................................................................................ 394
SOAM-RDICCM Alarm .............................................................................................. 395
SOAM-RDICSF ......................................................................................................... 395
SOAM-RemoteCCM Alarm ....................................................................................... 395
SOAM-XconCCM Alarm ............................................................................................ 395
SHDSL-64-65B Alarm ............................................................................................... 396
SHDSL-BER3 Alarm .................................................................................................. 396
SHDSL-BER6 Alarm .................................................................................................. 396
SHDSL-LOS Alarm .................................................................................................... 396
SHDSL-LOSW Alarm ................................................................................................ 397
SNR Margin Aggregation Threshold ......................................................................... 397
TDM-AIS Alarm ......................................................................................................... 397
TDM-BER3 Alarm ...................................................................................................... 397
TDM-BER6 Alarm ...................................................................................................... 398
TDM-LFA Alarm ......................................................................................................... 398
TDM-LOS Alarm ........................................................................................................ 398
TDM-RAI Alarm ......................................................................................................... 398
Temperature Alarm (desktop only) ............................................................................ 399
13 References ............................................................................................................................... 400
14 Glossary .................................................................................................................................... 402

A3118-X642-R612-01 8 / 405
 ULAF+ ACCEED 1102/04 Manual

Figures

Figure 1-1 ESD symbol ......................................................................................................................... 17

Figure 1-2 Disposal of equipment and units .......................................................................................... 18
Figure 1-3 Over voltage protection ........................................................................................................ 19
Figure 2-1 ULAF+ system ..................................................................................................................... 26
Figure 2-2 Typical ULAF+ applications ................................................................................................. 26
Figure 2-3 ULAF+ LCT+ GUI................................................................................................................. 28
Figure 3-1 ACCEED 1102 and 1104 desktop ....................................................................................... 33
Figure 3-2 ACCEED 1102 and 1104 CPE ............................................................................................. 36
Figure 3-3 E-LAN service (multipoint to multipoint EVC) ...................................................................... 38
Figure 3-4 E-Line service (point to point EVC) ...................................................................................... 39
Figure 3-5 E-Tree service (rooted multipoint EVC) ............................................................................... 39
Figure 3-6 ACCEED 1102/04 wholesale application ............................................................................. 40
Figure 3-7 Campus application example ............................................................................................... 41
Figure 3-8 ACCEED 1102/04 configuration examples .......................................................................... 42
Figure 3-9 Line / Link / Service definition .............................................................................................. 42
Figure 4-1 Quick start exemplary configuration ..................................................................................... 46
Figure 4-2 Exemplary configuration wiring ............................................................................................ 47
Figure 4-3 LCT+ installation .................................................................................................................. 48
Figure 5-1 ACCEED 1102/04 ................................................................................................................ 52
Figure 5-2 Location of desktop power supply terminals and selection jumpers .................................... 55
Figure 5-3 AC and DC power supply ..................................................................................................... 56
Figure 5-4 Jumper settings: ACCEED 1102/04 desktop unit local supply; AC or DC ........................... 58
Figure 5-5 Jumper settings: ACCEED 1102/04 desktop unit remotely fed ........................................... 58
Figure 5-6 Rear panel of the ACCEED 1102/04 desktop with main earth terminal for grounding ........ 59
Figure 5-7 ACCEED 1102/04 front panel interfaces and LEDs ............................................................ 60
Figure 5-8 ACCEED 1102/04 CPE front panel interfaces and LEDs .................................................... 60
Figure 5-9 Visual signaling of the ACCEED 1102/04 ............................................................................ 65
Figure 5-10 ACCEED 1102/04 CPE visual signaling ............................................................................ 66
Figure 5-11 ACCEED 1102/04 slow blinking LED................................................................................ 67
Figure 5-12 ACCEED 1102/04 fast blinking LED ................................................................................. 67
Figure 5-13 LCT+ setup program .......................................................................................................... 68
Figure 5-14 LCT+ setup wizard ............................................................................................................. 69
Figure 5-15 LCT+ components to install ............................................................................................... 69
Figure 5-16 Add-on source folder .......................................................................................................... 70
Figure 5-17 Destination folder ............................................................................................................... 70
Figure 5-18 Shortcuts ............................................................................................................................ 71
Figure 5-19 Completing the LCT+ Setup............................................................................................... 71
Figure 5-20 LCT+ setup wizard ............................................................................................................. 72
Figure 5-21 LCT+ previous version detected ........................................................................................ 72
Figure 5-22 LCT+ components to install ............................................................................................... 73
Figure 5-23 Add-on source folder .......................................................................................................... 74
Figure 5-24 Destination folder ............................................................................................................... 74
Figure 5-25 Shortcuts ............................................................................................................................ 75
Figure 5-26 Completing the LCT+ Setup............................................................................................... 75
Figure 5-27 LCT+ connection via RS232 interface ............................................................................... 77
Figure 5-28 Example of ACCEED NMS management connections ...................................................... 78
Figure 6-1 LCT+ Graphical User Interface ............................................................................................ 90
Figure 6-2 LCT+ start dialogue .............................................................................................................. 91
Figure 6-3 LCT+ Login dialogue window ............................................................................................... 92
Figure 6-4 LCT+ GUI ............................................................................................................................. 92
Figure 6-5 LCT+ window header example ............................................................................................ 94
Figure 6-6 File Menu ............................................................................................................................. 95
Figure 6-7 Options Menu ....................................................................................................................... 96
Figure 6-8 Help Menu ............................................................................................................................ 97
Figure 6-9 LCT+ About Window ............................................................................................................ 97
Figure 6-10 LCT+ window bottom detail example ................................................................................. 97

A3118-X642-R612-01 9 / 405
 ULAF+ ACCEED 1102/04 Manual

Figure 6-11 LCT+ progress bar example .............................................................................................. 97

Figure 6-12 LCT+ preview mode active ................................................................................................ 97
Figure 6-13 LCT+ Areas ........................................................................................................................ 99
Figure 6-14 ACCEED 1102/04 Tree view ........................................................................................... 100
Figure 6-15 Connection dialogue ........................................................................................................ 101
Figure 6-16 User Management dialogue ............................................................................................. 101
Figure 6-17 Ethernet view ................................................................................................................... 103
Figure 6-18 Table tabs ........................................................................................................................ 105
Figure 6-19 Table area example ......................................................................................................... 105
Figure 6-20 Configuration example ..................................................................................................... 106
Figure 6-21 Fault / Alarms ................................................................................................................... 107
Figure 6-22 Alarm Log ......................................................................................................................... 107
Figure 6-23 Fault / Maintenance ......................................................................................................... 108
Figure 6-24 Fault / SOAM .................................................................................................................... 109
Figure 6-25 Ping Settings .................................................................................................................... 110
Figure 6-26 Configuration example ACCEED 1102/04 ....................................................................... 111
Figure 6-27 Configuration / Summary ................................................................................................. 112
Figure 6-28 Performance / Line Parameters ....................................................................................... 113
Figure 6-29 Performance / Error Counters .......................................................................................... 114
Figure 6-30 Performance / BER Measurement ................................................................................... 116
Figure 6-31 Save configuration window .............................................................................................. 118
Figure 6-32 Save window .................................................................................................................... 119
Figure 6-33 Open window ................................................................................................................... 120
Figure 6-34 Load configuration window .............................................................................................. 121
Figure 6-35 Connection option ............................................................................................................ 122
Figure 6-36 Confirmation options ........................................................................................................ 122
Figure 6-37 Alarm log clear warning ................................................................................................... 122
Figure 6-38 Logging options ................................................................................................................ 123
Figure 6-39 Trap Log example ............................................................................................................ 123
Figure 6-40 Export ............................................................................................................................... 124
Figure 6-41 Download dialogue........................................................................................................... 150
Figure 6-42 Open download file .......................................................................................................... 151
Figure 6-43 Download OK ................................................................................................................... 151
Figure 6-44 Download progress bar .................................................................................................... 151
Figure 6-45 Download finished ............................................................................................................ 152
Figure 7-1 Bit rate range TC-PAM 16 / TC-PAM 32 ............................................................................ 156
Figure 7-2 max. Reach TC-PAM16 / PE0.4 ........................................................................................ 159
Figure 7-3 max. Reach TC-PAM16 / PE0.8 ....................................................................................... 159
Figure 7-4 max. Reach TC-PAM32 / PE0.4 ........................................................................................ 160
Figure 7-5 max. Reach TC-PAM32 / PE0.8 ........................................................................................ 160
Figure 7-6 SHDSL Loopback............................................................................................................... 161
Figure 8-1 Ethernet switch building blocks .......................................................................................... 176
Figure 8-2 Local and remote switch view with LCT+ ........................................................................... 177
Figure 8-3 Building block – port control ............................................................................................... 178
Figure 8-4 Overview switch ports ACCEED 1102/04 .......................................................................... 178
Figure 8-5 Global switch port settings ................................................................................................. 179
Figure 8-6 Individual switch port settings ............................................................................................ 180
Figure 8-7 Link Failure Propagation example ..................................................................................... 185
Figure 8-8 Aggregation_Ports[] windows ............................................................................................ 186
Figure 8-9 LAG port settings ............................................................................................................... 188
Figure 8-10 LAG configuration ............................................................................................................ 189
Figure 8-11 Building block – switch control ......................................................................................... 196
Figure 8-12 ACCEED - VLAN learning modes .................................................................................... 196
Figure 8-13 ACCEED MAC address Table (VLAN aware mode) ....................................................... 197
Figure 8-14 port isolation ..................................................................................................................... 199
Figure 8-15 port mirroring example ..................................................................................................... 200
Figure 8-16 L2PT example .................................................................................................................. 201
Figure 8-17 Building block – VLAN ..................................................................................................... 205
Figure 8-18 ACCEED 1102/04 VLAN manipulation scenarios ........................................................... 206

A3118-X642-R612-01 10 / 405
 ULAF+ ACCEED 1102/04 Manual

Figure 8-19 Egress Tagging Mode: - (Discard) ................................................................................... 209

Figure 8-20 Egress Tagging Mode: Untagged .................................................................................... 210
Figure 8-21 Egress Tagging Mode: Add Primary Tag ......................................................................... 211
Figure 8-22 Egress Tagging Mode: Primary Tag Only ........................................................................ 212
Figure 8-23 Egress Tagging Mode: Secondary Tag Only ................................................................... 213
Figure 8-24 Egress Tagging Mode: Remove Outer Tag ..................................................................... 214
Figure 8-25 Egress Tagging Mode: Inner Primary, Outer Secondary ................................................. 215
Figure 8-26 Egress Tagging Mode: Inner Secondary, Outer Primary ................................................. 216
Figure 8-27 VLAN DB example ........................................................................................................... 217
Figure 8-28 VLAN filter configuration .................................................................................................. 221
Figure 8-29 Building Block - QoS handling ......................................................................................... 224
Figure 8-30 Ingress CoS profiles ......................................................................................................... 226
Figure 8-31 Ingress CoS profiles ......................................................................................................... 227
Figure 8-32 Ingress DSCP profiles ...................................................................................................... 228
Figure 8-33 Layer 2 packet description ............................................................................................... 229
Figure 8-34 Layer3/4 packet description ............................................................................................. 229
Figure 8-35 Rule configuration ............................................................................................................ 232
Figure 8-36 Color unaware: Single Rate, Three colors ....................................................................... 235
Figure 8-37 Color aware: Single Rate, Three colors ........................................................................... 236
Figure 8-38 Color unaware: Two Rate, Three colors .......................................................................... 236
Figure 8-39 Color aware: Two Rate, Three colors .............................................................................. 237
Figure 8-40 Queue and port shapers .................................................................................................. 247
Figure 8-41 Protection Scenario with ACCEED 1102/4 ...................................................................... 249
Figure 8-42 General Protection Architecture ....................................................................................... 249
Figure 8-43 1+1 Protection Type ......................................................................................................... 250
Figure 8-44 1:1 Protection Type .......................................................................................................... 250
Figure 8-45 APS Protocol and Path Monitoring .................................................................................. 251
Figure 8-46 Linear Protection Example ............................................................................................... 254
Figure 8-47 Ring Protection Scenarios ............................................................................................... 258
Figure 8-48 Ring Protection Principle .................................................................................................. 259
Figure 8-49 Ring Protection Example ................................................................................................. 264
Figure 8-50 Statistics Overview ........................................................................................................... 268
Figure 9-1 Link OAM ........................................................................................................................... 282
Figure 9-2 Link OAM loopback standard behavior .............................................................................. 283
Figure 9-3 Link OAM loopback with forwarding of looped frames....................................................... 283
Figure 9-4 Ethernet OAM Layers ........................................................................................................ 284
Figure 9-5 Service OAM definitions ..................................................................................................... 284
Figure 9-6 Service OAM example ....................................................................................................... 285
Figure 9-7 Service OAM maintenance levels ...................................................................................... 287
Figure 9-8 Service OAM – MEP orientation ........................................................................................ 287
Figure 9-9 AIS example ....................................................................................................................... 294
Figure 9-10 LCK example.................................................................................................................... 295
Figure 9-11 SOAM CSF example ........................................................................................................ 295
Figure 9-12 Service OAM – Linktrace Replies .................................................................................... 300
Figure 9-13 Service OAM – PM session and responder principle ...................................................... 301
Figure 9-14 Service OAM – Round trip delay measurement principle ................................................ 302
Figure 9-15 Service OAM – Inter-frame delay variation measurement principle ................................ 303
Figure 9-16 Service OAM – Delay Measurement Bin ......................................................................... 308
Figure 9-17 Service OAM – Frame loss ratio (FLR) measurement principle ...................................... 310
Figure 9-18 Service OAM – Availability definition ............................................................................... 311
Figure 9-19 Service Activation Test example ...................................................................................... 318
Figure 9-20 Service Activation Test Principle ...................................................................................... 319
Figure 9-21 SAT sequence .................................................................................................................. 320
Figure 9-22 Service Activation Test example ...................................................................................... 323
Figure 9-23 SAT Test CoS Instance ................................................................................................... 324
Figure 9-24 SAT Results ..................................................................................................................... 326
Figure 9-25 SAT Test Report .............................................................................................................. 328
Figure 10-1 CES standards overview .................................................................................................. 331
Figure 10-2 The CES principle ............................................................................................................ 332

A3118-X642-R612-01 11 / 405
 ULAF+ ACCEED 1102/04 Manual

Figure 10-3 Structure of the CES Control Word .................................................................................. 334

Figure 10-4 CES functional components ............................................................................................. 335
Figure 10-5 Format of CESoETH and CESoMPLS frames ................................................................. 338
Figure 10-6 CES operation overview .................................................................................................. 338
Figure 10-7 ACCEED 1102/04 – CES Application Overview .............................................................. 342
Figure 10-8 ACCEED CES Network ................................................................................................... 343
Figure 10-9 CES Alarm locations ........................................................................................................ 354
Figure 11-1 RADIUS functional principle ............................................................................................. 367
Figure 11-2 Flow chart redundant server authentication ..................................................................... 368
Figure 11-3 Authentication databases ................................................................................................. 368
Figure 11-4 Combined authentication modes: Primary RADIUS, secondary local ............................. 369
Figure 11-5 Combined authentication modes: Primary local, secondary RADIUS ............................. 369
Figure 11-6 Zero Touch Provisioning principle .................................................................................... 372
Figure 12-1 Wiring error example ........................................................................................................ 379
Figure 12-2 line equalization and symmetry example ......................................................................... 380
Figure 12-3 bridged taps ..................................................................................................................... 381
Figure 12-4 Impedance mismatch ....................................................................................................... 381
Figure 12-5 ACCEED 1102/04 LEDs .................................................................................................. 382

A3118-X642-R612-01 12 / 405
ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1
Notes on product safety

This chapter contains very important information such as product safety,

EMC, handling of the equipment and over voltage protection.

A3118-X642-R612-01 13 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1.1 Representation conventions

This manual uses different types of indications to make you aware of product safety:

Information

Information gives useful notes which pertain to particular situations and specifically draw
 the reader’s attention to them. Information will be highlighted in the text using an
information symbol.

Warning

Warnings give important information, which it is vital to follow to prevent damage.

! Warnings will be highlighted in the text using a warning symbol.

Other symbols not related to product safety are defined in chapter  2.3.

A3118-X642-R612-01 14 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1.2 Product Safety

It is inevitable that in electrical systems certain parts of the equipment will be powered. During operation
parts of the product may get very hot.

Ignoring this and the warnings given can result in personal injury or in damage to property/ environment.

Before opening the ACCEED desktop unit interrupt the power feed and also disconnect
! all interface connectors. You have to guarantee easy access to the main socket.

All work on the open unit may only be performed by authorized personal (maintenance staff).
Considerable danger (electric shock, fire) for maintenance staff and the user can be harmed with
unauthorized opening of or improper work on the unit.

A prerequisite is that all connected devices also meet these requirements.

Non-adherence to specifications or modifications to setup (for example, the use of SFP modules not
approved for this product) can lead to violation of security provisions. This would invalidate the
Declaration of Conformity. Liability for any associated problems then lies with the person responsible for
the modifications or for non-adherence to specifications.

Notes on protection against laser radiation

Normal operation
Only class1 laser SFPs shall be used

Dangerous fault
The ACCEED unit corresponds to the Laser class 1 for all disturbances.

Notes on permitted altitude and use of protection earth

AC supplied ACCEED devices (Desktops without RPS):

Max. altitude during operation ≤ 2000 m sea level.
Operation above 2000 m sea level (up to 3000 m) is permitted if the equipment
has a reliable connection to a suitable protection earth (PE).

DC supplied ACCEED devices (Plug-in units or Desktops with RPS):

Max. altitude during operation ≤ 3000 m sea level.
In case of using the RPS with remote feeding voltages between 120VDC and 180VDC,
the symbol for identification of class II equipment on the type label must be
changed to invisible (e.g. by covering with adhesive paper).
For remote feeding voltages > 120VDC the equipment must have a reliable
connection to a suitable protection earth (PE).

A3118-X642-R612-01 15 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1.3 EMC
The EC declaration of conformity for the product is met when the installation and cabling is carried out
in compliance with the instructions in the ULAF+ ACCEED 1102/04 Manual ( 5). Where necessary,
project specific documents should be taken into account.

Deviations from the specifications or irregular installation modifications (e.g. the use of cable types with
a lower shielding mass), can lead to violations to the EC protection requirements. In such cases the
declaration of conformity will be invalidated. Responsibilities for any problems that may occur thereafter
then lie with the person responsible for deviating from the specifications.

A3118-X642-R612-01 16 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1.4 Device handling

Electrostatic Sensitive Devices (ESD)

Figure 1-1 ESD symbol

Units that bear the ESD symbol are equipped with electrostatic sensitive units, i.e. the
! appropriate safety precautions must be kept while handling these units.

A wrist band must always be worn when unpacking, packing, touching, removing or inserting units
bearing the ESD symbol, see Figure 1-1. This wrist band must be grounded while working with these
ULAF+ units. This will ensure that components sensitive to electrostatic discharge are not damaged.

Basically the conductor tracks or components on the units may not be touched. The units may only be
held by the edges.

Once they have been removed, place the units in the conductive plastic envelope provided and then
store them or dispatch them special transport cases bearing ESD symbol.

To avoid further damage, defective units are to be handled with as much care as new units.
Units located in an enclosed, unopened housing are always protected.

European Standard EN50082-1 contains information on correct handling of electrostatic sensitive

devices.

Inserting/ removing plug in units

The plug in units can be removed and inserted while the power is on.
To remove units release the screws on the front plate and then remove the unit
To mount plug in units insert the plug in units into the shelf and then tighten the screws on the front
plate.

If neither the ULAF+ desktop unit nor the terminal device is earthed, prevent electrostatic
! discharge by connecting the terminal device before switching on the ULAF+ desktop unit.

Stacking the desktop units

Because of the generated heat you may stack the desktop units only in a room with a
temperature of 20 degrees.
It is recommended using the “subrack 19” for max. 8 desktop units” to accommodate
! multiple desktop models.
This subrack provides space for 8 desktop models included their enclosure. Ordering
number: C107-A124-B106.

A3118-X642-R612-01 17 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

Disposal of equipment and units

Figure 1-2 Disposal of equipment and units

The disposal of all electrical and electronic products should be done separately from the municipal waste
stream via designated collection facilities appointed by the government or the local authorities.

The correct disposal and separate collection of the old equipment will help prevent potential negative
consequences for the environment and human health. It is a precondition for reuse and recycling of
used electrical and electronic equipment.

For more detailed information about disposal of the old equipment, please contact your Albis
Technologies Ltd partner.

A3118-X642-R612-01 18 / 405
 ULAF+ 1 - Notes on product safety ACCEED 1102/04 Manual

1.5 Over voltage protection

Figure 1-3 Over voltage protection

Figure 1-3 shows an example with a SHDSL loop with some inserted BSRUs. Over voltage (2) caused
by i.e. lightning or mains can occur anywhere on the loop. For ACCEED units with fiber interfaces, these
threads do not apply.

Protection of a network element

The over voltage primary protection is mandatory in connection with any ULAF+ network elements (3).
Usually it is a 3-electrode-arrestor with a spark-over voltage of > 130V. When the desktop model is
remote powered by 180V the spark-over voltage has to be > 200V and the desktop model shall be
earthed (4). More information about the grounding concept of the ACCEED can be found in  5.3.

A3118-X642-R612-01 19 / 405
ULAF+ 2 - Introduction ACCEED 1102/04 Manual

2
Introduction

This chapter gives an overview of the ULAF+ system and the product
range.

A3118-X642-R612-01 20 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

2.1 ULAF+ documentation structure

The ULAF+ documentation is composed of the following manuals:

 ACCEED manuals: contain all information relative to a specific ACCEED product: technical
description, installation, configuration, operation and troubleshooting instructions.
- ACCEED 1102/04 Manual
- ACCEED 1404 Manual
- ACCEED 1416 Manual
- ACCEED 2102 Manual
- ACCEED 2104 Manual
- ACCEED 2202 Manual

 ULAF+ system documents:

- Technical Description TED 4.2:
The Technical Description provides an overview of the composition and function of the
system, together with all its components. The descriptions of the subsystems contain
detailed information about the individual submodules and the complete product overview,
together with comprehensive technical data relating to the system.

- Subrack V2 S3105-B128-A210 / -C210 / -C211

- Operating & Maintenance Interface unit OMI SNMP
- SHDSL transmission units: BSTU/QSTU/BSTU4
- SHDSL regenerator BSRU
- Ethernet over TDM inverse-multiplexer GTU4
- Transmission unit BOTU und QOTU for optical transmission
- G.703 converter unit GTU (interface converter)
- Different pluggable modules (e.g. customer interface)
- Technical Description TED 5.1 or newer:
The Technical Description provides an overview of the composition and function of the
system, together with all its components. The descriptions of the subsystems contain
detailed information about the individual submodules and the complete product overview,
together with comprehensive technical data relating to the system.

- Subrack V3 S3118-B628-A210 / -A211

- Compact Shelf, 2 HU, 2+1 slots S3118-B621-A211
- Management & Controller Unit MCU
- Management & Concentrator Unit MCU-S with Ethernet switch
- Management & Concentrator Unit MCU-CES with Ethernet switch and Circuit Emulation
Service functionality
- E1 insertion unit EIU
- SHDSL transmission units: BSTU/QSTU/BSTU4
- SHDSL regenerator BSRU
- Ethernet over TDM inverse-multiplexer GTU4
- Transmission unit BOTU und QOTU for optical transmission
- G.703 converter unit GTU (interface converter)
- Flexible interface converter for Ethernet and data services over E1: BGTU
- Different pluggable modules (e.g. customer interface)
- Installation Manual IMN 4.2:
The Installation Manual contains the assembly instructions for the individual system
components or submodules. The IMN contains tables and illustrations with the contact pin
assignments for the connectors, the settings for the address switches and operating
elements, together with the module-specific alarm tables.

- Subrack V2 S3105-B128-A210 / -C210 / -C211

- Operating & Maintenance Interface unit OMI SNMP
A3118-X642-R612-01 21 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

- SHDSL transmission units: BSTU/QSTU/BSTU4

- SHDSL regenerator BSRU
- Ethernet over TDM inverse-multiplexer GTU4
- Transmission unit BOTU und QOTU for optical transmission
- G.703 converter unit GTU (interface converter)
- Different pluggable modules (e.g. customer interfaces)
- Mounting devices for xDSL regenerators
- Installation Manual IMN 5.1 or newer:
The Installation Manual contains the assembly instructions for the individual system
components or submodules. The IMN contains tables and illustrations with the contact pin
assignments for the connectors, the settings for the address switches and operating
elements, together with the module-specific alarm tables.

- Subrack V3 S3118-B628-A210 / -A211

- Compact Shelf, 2 HU, 2+1 slots S3118-B621-A211
- Management & Controller Unit MCU
- Management & Concentrator Unit MCU-S with Ethernet switch
- Management & Concentrator Unit MCU-CES with Ethernet switch and Circuit Emulation
Service Functionality
- E1 insertion unit EIU
- SHDSL transmission units: BSTU/QSTU/BSTU4
- SHDSL regenerator BSRU / BSRU+
- Ethernet over TDM inverse-multiplexer GTU4
- Transmission unit BOTU und QOTU for optical transmission
- G.703 transmission unit GTU (interface converter)
- Flexible interface converter for Ethernet and data services over E1: BGTU
- Different pluggable modules (e.g. customer interface)
- Mounting steps
- User Manual UMN:
The User Manual describes all the procedures for the LCT which are required for operation
and administration of a fully functioning system. If malfunctions occur, the Manual contains
instructions showing how to restore the system to its normal operating condition.
- User Manual UMN for the Advanced Bridge and Router Module:
The User Manual describes all the procedures for the LCT which are required for operation
and administration of a fully functioning Advanced Bridge and Router Module. If
malfunctions occur, the Manual contains instructions showing how to restore the system to
its normal operating condition.
- CLI Reference Manual for the Advanced Bridge and Router Module
Contains a detailed description of the CLI (Command Line Interface) for the Advanced
Bridge and Router Module.
- CLI Reference Manual for MCU-S / MCU-CES
Contains a detailed description of the CLI (Command Line Interface) of the MCU-S and
MCU-CES.

 AccessIntegrator documents:
Documentation related to the AccessIntegrator (ULAF+ Management System (NMS)).
- Installation Manual (IMN)
The Installation Manual is intended for anyone involved in the installation and configuration
of the AccessIntegrator. It describes the procedures for installation of a new version of the
AccessIntegrator software.
- Administration Manual (ADMN)
The Administration Manual is intended to be used by anyone who configures the
AccessIntegrator for other users. It describes the tasks which must be performed in order
to guarantee trouble-free and reliable management of the network elements using the
AccessIntegrator.
- Operation Manual (OMN)

A3118-X642-R612-01 22 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

Intended for use by anyone who uses AccessIntegrator to monitor and maintain network
elements.

 Download Manager documents:

Documentation related to the Download Manager, a SW application running on a PC capable
of automatically download all units in a Subrack and the corresponding regenerators and NT
devices. The Download Manager is integrated in the AccessIntegrator.
- User Manual UMN:
The User Manual describes how to operate the download manager.

A3118-X642-R612-01 23 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

2.2 ACCEED 1102/04 Manual Structure

Chapter 1 contains very important information such as product safety, EMC, handling of the
equipment and over voltage protection.

Chapter 2 gives an overview of the ULAF+ system and the product family.

Chapter 3 provides an overview of the ACCEED 1102/04 unit, describes typical applications and
system configurations and gives an introduction to the ACCEED 1102/04 architecture.
The aim of this chapter is to show the capabilities of the system and to facilitate network
planning.

Chapter 4 gives step by step instructions to quickly set up a typical EFM link using ACCEED
1102/04 and LCT+. The chapters contain links to other chapters to get specific detailed
information if necessary. The aim of this chapter is to help rapidly set up a first running
configuration and get familiar with ACCEED 1102/04.

Chapter 5 gives detailed information and instructions about ACCEED 1102/04 and LCT+
installation. It contains a description of the mechanic, the power supply options, the
pinning of the different interfaces, the cabling including the management access, the
DIP switches and LEDs, the installation of the LCT+ and instructions about the
necessary on site configurations. The aim of this chapter is to facilitate the installation of
ACCEED 1102/04 for different possible system configurations.

Chapter 6 this chapter gives detailed information and instructions about how to configure and
operate ACCEED 1102/04 and LCT+. It contains a description of both ACCEED
1102/04 and LCT+ features. It shows how to setup the desired configuration with typical
examples. Further it contains a description of all the alarms and performance
management counters. A special section is dedicated to the LCT+. The chapter follows
the structure of the LCT+ dialogues.

Chapter 7 gives an overview of the EFMC capabilities and the configuration and fault management
options

Chapter 8 explains the wide range of the Ethernet switch capabilities based on a building block
model. This covers the switch and port control options and describes the VLAN and
QoS configurations possibilities.
Counter and utilization are explained.

Chapter 9 gives detailed information about the different Operation and Maintenance modes. It
covers Link OAM, Service OAM and Service Activation Testing.

Chapter 10 explains the optional CES Interworking function of the ACCEED 1102/04 unit.

Chapter 11 describes the general information and settings of the ACCEED 1102/04 unit. This
covers inventory and logging information and explains how the alarm configuration is
done. Management access and synchronization options for the ACCEED 1102/04 are
detailed.

Chapter 12 gives some practical help to quickly identify faults and solve them. The chapter contains
a list of all LEDs and alarms, describing possible causes and suggesting possible
solutions. The aim of this chapter is to facilitate trouble shooting.

Chapter 13 contains the complete list of references.

Chapter 14 contains the glossary

A3118-X642-R612-01 24 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

2.3 Representation conventions

This manual uses various different types of indications to highlight the following subjects:

Information

Information gives useful notes which pertain to particular situations and specifically draw
 the reader’s attention to them. Information will be highlighted in the text using an
information symbol.

Warning

Warnings give important information, which it is vital to follow to prevent damage.

! Warnings will be highlighted in the text using a warning symbol.

Operation via LCT+

 This symbol indicates LCT+ specific information about LCT+ usage.

Naming Convention

 This symbol indicates a naming convention used in the manual, i.e. a specification about
a specific terminology used in the manual.

Under Construction

 This symbol indicates that the chapter, paragraph, table or figure is still in progress.

ACCEED manual naming conventions

Within this document to following equivalents are used:

ULAF+ = product family including all ULAF+ products
ACCEED = The ULAF+ Carrier Ethernet product line
ACCEED 1416 = product
 ACCEED 1416 with 180V RPS = product option
Release 6.x = set of features, corresponding to a particular SW (LCT, LCT+,
MetroIntegrator) and FW (ACCEED, MCU (MCU-S/MCU-CES)) version
Packet = Frames
Regenerator = Repeater

A3118-X642-R612-01 25 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

2.4 ULAF+ System overview

Figure 2-1 ULAF+ system

ULAF+ is the «All-in-One Platform» to offer Ethernet and TDM services over packet or TDM networks
exploiting existing copper or fiber access infrastructure.

Figure 2-2 Typical ULAF+ applications

ULAF+ offers the flexibility to provide versatile and comprehensive services out of the same sub rack.
Traditional E1, data (V.35, V.36, X.21) and Ethernet services can share the same subscriber line and
desktop unit.

A3118-X642-R612-01 26 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

Service Interfaces
Ethernet
 10/100/1000Base-T
 SFP’s (electrical or optical, Fast and Gigabit Ethernet)
2Mbit/s E1
 G.703 unstructured, G.704 structured or fractional E1, ISDN PRI
N x 64kBit/s serial data
 X.21, V.35, V.36
Synchronization
 2MHz clock and 2Mbit/s
 Synchronous Ethernet (SyncE)
 PPS and IEEE1588v2

Transmission Interfaces
The system offers copper and fiber interfaces to utilize existing access network infrastructure.
Wire pair bonding allows for fiber like speed, quality and reliability on multi pair copper access links.
Regenerators in a cascading chain and built in remote feeding circuits extend the reach of high bit rate
services to remote locations.

Copper
 ETSI/ITU-T compliant with SHDSL.bis, up to 6.4 Mbps per wire pair
 up to 8 regenerators per wire pair
 bonding of up to 16 wire pairs with line protection
 Spectral compatibility with POTS, ISDN, HDSL, ADSL, VDSL etc.
Fiber
 up to 1Gbit/s two or single fiber systems
 concurrent TDM and Ethernet transmission
 SFP slots allow for flexible choice of optical interfaces
 sub 50ms line protection with LAG

MEF Carrier Ethernet Services attributes

ULAF+ is designed to support the Carrier Ethernet Services defined by the Metro
Ethernet Forum (MEF).

Standardized Services
 E-Line, E-LAN, E-Tree and E-Access Services
 TDM Circuit Emulation Service (CES)
Scalability
 10/100/1000Mbit/s User Network Interfaces (UNI’s)
 per flow bandwidth profiles and SLA enforcement
 up to 64 customers per shelf, thousands of customers per network
Quality of Service
 `Hard`-QoS - guaranteed bandwidth profile per service
 Minimum delay and jitter
Reliability

A3118-X642-R612-01 27 / 405
 ULAF+ 2 - Introduction ACCEED 1102/04 Manual

 Distributed architecture, equipment redundancy

 Sub 50ms line- and path protection
Service Management
 Fast and flexible service provisioning
 Ethernet Link- and Service-OAM

Management Systems
ULAF+ features the following servicing options:

Figure 2-3 ULAF+ LCT+ GUI

Local Craft Terminal (LCT+)

 Intuitive and easy to learn configuration and maintenance
 Windows operating system
MetroIntegrator
 Client / server architecture
 FCAPS based Webinterface
 same look and feel as the LCT / LCT+
 Windows, Linux and Solaris operating systems
CLI
 Command line console, Telnet and SSH
Easy Management Integration, standard protocols and interfaces
 SNMP V1, V2c and V3
 (Element Manager) CORBA northbound interface for umbrella management integration
 Standard MIBs

A3118-X642-R612-01 28 / 405
ULAF+ 2 - Introduction ACCEED 1102/04 Manual

ULAF+ Product Range

Subracks

Subrack V3
19” and ETSI rack suitable 16 + 1 slots
Ethernet and TDM backplane
Clock and Alarm In-/Outputs

Compact Shelf
19” and ETSI rack or desktop use 2+1 slots or 3+0 slots
Ethernet and TDM backplane
Clock and Alarm In-/Outputs

Management and traffic aggregation units

MCU
SNMP Management Unit for
local or remote control of up to
64 access links
Ethernet and serial interfaces

MCU-S
Management and Concentrator Unit with additional Carrier Ethernet
Switch with 2x GbE up-links and 16x FE backplane ports

MCU-CES
Management and Concentrator Unit with Carrier Ethernet Switch and
Circuit Emulation Service for up to 32x E1 services over packet networks

SHDSL transmission units

BSTU
SHDSL Termination Unit for 1x or 2x wire pairs (11.4Mbit/s)
TDM and Ethernet interfaces
Integrated Ethernet switch

QSTU
Quad SHDSL Termination Unit
4 E1 interfaces
1-, 2- or 4-wire pair mode

A3118-X642-R612-01 29 / 405
ULAF+ 2 - Introduction ACCEED 1102/04 Manual

BSTU4
SHDSL Termination Unit for advanced Ethernet services.
4 wire pair bonding (22.8Mbit/s)
4 port Ethernet switch (VLAN, CoS)

BSRU/BSRU+
2 wire pairs SHDSL Regenerator Unit
Up to 8 BSRU cascadable
Remote or local power feeding

ACCEED 1102
EFMC-LR (SHDSL) Ethernet Demarcation Device
1x RJ45 / 2 copper wire pair SHDSL.bis (30.6 Mbit/s)
4x RJ45 10/100Base-T ports, Carrier Ethernet switch
2x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)

ACCEED 1104
EFMC-LR (SHDSL) Ethernet Demarcation Device
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
4x RJ45 10/100Base-T ports, Carrier Ethernet switch
2x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
1x Data Module Slot for X.21, V.35, V.36 (optional)

ACCEED 1102/04 CPE

EFMC-LR (SHDSL) Ethernet Demarcation Device
1x RJ45 / 2 or 4 copper wire pair SHDSL.bis
1x RJ45 10/100Base-T ports, Carrier Ethernet switch

ACCEED 1404
EFMC-LR (SHDSL) Ethernet Demarcation Device with
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)

ACCEED 1416
EFMC-LR (SHDSL) Termination Unit with
Carrier Ethernet switch and bonding of up to 16 wire pairs (102.4 Mbit/s)
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)

Optical transmission units

BOTU
Fiber Optical Termination Unit for Ethernet and TDM services
4x E1, Ethernet switch (VLAN, CoS)
2x SFP module slots

A3118-X642-R612-01 30 / 405
ULAF+ 2 - Introduction ACCEED 1102/04 Manual

ACCEED 2102
EFMF (optical) Termination Unit with Carrier Ethernet switch
2x SFP module slots for protected GbE or FE services
2x RJ45 10/100/1000Base-T ports

ACCEED 2104
EFMF (optical) Termination Unit with Carrier Ethernet switch
4x SFP module slots for protected GbE or FE services
4x RJ45 10/100/1000Base-T ports
4x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
1x BNC PPS 50 Ohm clock output (optional)

ACCEED 2202
EFMF (optical) Termination Unit with Carrier Ethernet switch
2x SFP module slots for protected GbE or FE services
2x RJ45 10/100/1000Base-T ports
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)

Interface converters

BGTU
Flexible interface converter for
Ethernet over E1 or fractional E1 and data over E1 services
1x Dataslot module for X.21, V.35, V.36

GTU4
Inverse multiplexer unit for
Ethernet services over TDM networks. Bundling of up to 4 E1
4 port Ethernet switch

EIU
Quad E1 Insertion Unit for structured or unstructured E1 emulations
services with MCU-CES

Interface Modules
Various Interface Modules
(V.35, V.36, X.21, Ethernet Bridge, Ethernet Router)
Clock and Alarm Module

A3118-X642-R612-01 31 / 405
ULAF+ 3 - Application overview ACCEED 1102/04 Manual

3
Application overview

This chapter provides an overview of the ACCEED 1102/04 unit, describes

typical applications and system configurations and gives an introduction to
the ACCEED 1102/04 architecture. The aim of this chapter is to show the
capabilities of the system and to facilitate network planning.

A3118-X642-R612-01 32 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

3.1 ACCEED 1102/04 Overview

2 or 4 wire pairs SHDSL EFM unit

ACCEED 1102 and ACCEED 1104 supports bonded high speed symmetrical Carrier Ethernet services
on MSAN / DSLAM and ULAF+ platform.
Comprehensive traffic management at the user network interface (UNI) and integrated TDM CES
interworking function enables the implementation of high revenue services on every broadband platform.

Figure 3-1 ACCEED 1102 and 1104 desktop

ACCEED 1102 and 1104 main features

 Ethernet over up to 2 (ACCEED 1102) and 4 (ACCEED 1104) bonded copper wire pairs
 Standard compliant IEEE 802.3ah EFM
 Resilience auto failover and recovery functions
 Rate Adaptive SHDSL
 Network demarcation allowing SLA enforcement
 Ethernet Services with guaranteed bandwidth per flow
 Integrated CES interworking functions
 E1 interfaces and Data Module Slot (DMS) for X.21, V.35 and V.36 to support legacy customer
equipment
 Synchronization with SHDSL symbol clock
 Standard Ethernet Link- and Service-OAM
 Service Assurance and Qualification
 Graphical User Interface
 Zero Touch Provisioning

Copper based Ethernet services with fiber like quality

EFMC-LR is based on established ITU/ETSI SHDSL technology, supporting reliable, spectral
compatible and symmetrical services of 192kbit/s to 15.3Mbit/s per wire pair. Using standard based
EFM-bonding, the ACCEED 1102 can aggregate up to 2 wire pairs providing a maximum data rate of
30.6 Mbit/s and the ACCEED 1104 up to 4 wire pairs at a maximum of 61.2 Mbit/s per customer. EFM

A3118-X642-R612-01 33 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

bonding offers the great flexibility to aggregate wire pairs each with a distinct bit rate with very low
overhead and little latency added.

Compatibility
ACCEED 1102 and 1104 is interoperable with MSAN and DSLAM equipment of major suppliers as well
as ACCEED 1416, 1104 and 1102.

Carrier grade Ethernet services

Traffic aware switching with extended flow management allows providers to address the emerging
market of premium voice and data services over Ethernet.

Support of TDM legacy services

ACCEED 1102 and 1104 features E1 ports and a Data Module Slot (DMS) for X.21, V.35 and V.36
giving the possibility to connect legacy TDM customer equipment. This allows preserving customer
investment and facilitates a successful migration to full Carrier Ethernet services.

Ethernet Service Assurance

ACCEED 1102 and 1104 offer a set of standard based protocols and tools to support providers
managing Ethernet services over their entire Life-Cycle. From provisioning to SLA performance
monitoring and fault localizing ACCEED allows operation staffs to ease their work and increase their
efficiency thus considerably contributing to reducing operating costs.

Provisioning & Turn-up

 Use of configuration files, CLI scripts and Zero Touch Provisioning minimizes the installation effort
by automating the configuration process.
 Built-in service qualification tools allow to cut operational costs for verifying the SLA performance at
service turn-up. No need to dispatch personal and costly test equipment to the customer premises.

Performance Management
 Y.1731 based performance management continuously monitors SLA parameters such as Frame
Loss, Availability, Frame Delay and Frame Delay Variation with microsecond accuracy and
generates alarms if Objective Thresholds are violated, giving providers the possibility to proactively
take actions before the service is seriously degraded.
 Collection of statistics on physical-, packet- and service level as well as real time graphs monitoring
service utilization allows to track the service performance, to analyze network traffic and to certify
SLA conformity.

Fault Management
 EFM multi pair bonding and CCM based hot-/standby protection support the implementation of
resilient services, minimizing the impact of faults on the service.
 Fault propagation (e.g. AIS/RDI, Dying Gasp…), link-, port- and service level-alarms together with
extensive localization tools such as continuity check, linktrace and loopback allow to quickly locate
faults and re-establish the service in case of failures.

Synchronization options
For clock sensitive applications like mobile base station backhaul, synchronization is very important.
ACCEED 1102/04 offers several methods to provide an accurate clock to every customer location:
 Symbol clock delivers a reference clock to customer premises over SHDSL

Mechanics
ACCEED 1102/04 is available as desktop unit and is targeted for customer premises locations.

Management

A3118-X642-R612-01 34 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

ACCEED 1102/04 offers a rich variety of management solutions to fulfill the needs of each customer:
intuitive and easy to operate graphical SW applications; standard-conform protocols; easy to integrate
interfaces; fully automated «Zero Touch Provisioning» solutions.
It provides local management as well as remote Inband- or dedicated DCN access. The set-up of SHDSL
and EFM bonding group is fully managed by the CO equipment according to G.991.2, G.994.1 and
G.998.2.
 CLI console, Telnet and SSH
 Local Craft Terminal LCT+ (GUI)
 CORBA Northbound interface
 Syslog and SNMP traps
 DHCP, TFTP, SCP
 Standard MIBs
 MetroIntegrator Management System

Technical data
Power Supply Input Voltage
Desktop version 48 VDC or 60 VDC (valid range 40 – 72 VDC)
110 VAC or 230 VAC, 50/60 Hz (valid range 95 – 260 VAC)
Maximum Power Consumption
Desktop unit ≤ 11 W
Interfaces
User Network Interface (UNI)
1x or 4x RJ45 10/100Base-T ports
(2x RJ45 G.703 120/75 Ohm port for E1 or Synchronization)
(1x Data Module Slot for X.21, V.35 or V.36
Management
1x RJ45 serial Local Craft Terminal (LCT)
1x RJ45 Ethernet 10/100Base-T DCN
EFM
ACCEED 1102 1x RJ45 / 2 copper wire pairs SHDSL.bis
Line code TC-PAM 4/8/16/32/64/128
ACCEED 1104 1x RJ45 / 4 copper wire pairs SHDSL.bis
Line code TC-PAM 4/8/16/32/64/128
Payload Bitrates 192 to 15300kbit/s per wire pair
ACCEED 1102 up to 30.6 Mbit/s with 2 wire pairs
ACCEED 1104 up to 61.2 Mbit/s with 4 wire pairs
Physical and Environment
Desktop version (W x H x D) (W x H x D) 272 x 47,5 x 175 mm
(wall- and rack-mounting option)
Operating Temperature -5° C to +55° C at 5 to 95 % rel. humidity (non condensing)
Safety EN 60950-1 (2010)
EMC/EMF EN 300386 V1.4.1 (2011)
ES 201468 V1.3.1 (2005)
ITU-T K.20/K.21 (2011)
ITU-T K.45 (2011)
EN 300132-2 V2.1.1 (2003)
EN 62479 (2010)

A3118-X642-R612-01 35 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

2 or 4 wire pairs SHDSL EFM CPE

The ACCEED 1102/04 CPE version has the same functionality as the ACCEED1102/04 with
optimization for the operation with a DSLAM/MSAN. Nevertheless the ACCEED CPE units can also be
operated in the LT/NT mode (reference to chapter where modes are explained). Further details on the
CPE are listed in the technical data chapter below.

Figure 3-2 ACCEED 1102 and 1104 CPE

ACCEED 1102 CPE and 1104 CPE main features

 Ethernet over up to 2 (ACCEED 1102 CPE) and 4 (ACCEED 1104 CPE) bonded copper wire pairs
 Standard compliant IEEE 802.3ah EFM
 Resilience auto failover and recovery functions
 Rate Adaptive SHDSL
 Network demarcation allowing SLA enforcement
 Ethernet Services with guaranteed bandwidth per flow
 Standard Ethernet Link- and Service-OAM
 Service Assurance and Qualification
 Graphical User Interface
 Zero Touch Provisioning

Technical data
Power Supply Input Voltage (AC adapter included)
Desktop version 110 VAC or 230 VAC, 50/60 Hz (valid range 95 – 260 VAC)
Maximum Power Consumption
Desktop unit ≤8W
Interfaces
User Network Interface (UNI)
1x or 4x RJ45 10/100Base-T ports
Management
1x RJ45 Ethernet 10/100Base-T DCN
EFM
ACCEED 1102 CPE 1x RJ45 / 2 copper wire pairs SHDSL.bis
Line code TC-PAM 4/8/16/32/64/128
ACCEED 1104 CPE 1x RJ45 / 4 copper wire pairs SHDSL.bis

A3118-X642-R612-01 36 / 405
ULAF+ 3 - Application overview ACCEED 1102/04 Manual

Line code TC-PAM 4/8/16/32/64/128

Payload Bitrates 192 to 15300kbit/s per wire pair
ACCEED 1102 CPE up to 30.6 Mbit/s with 2 wire pairs
ACCEED 1104 CPE up to 61.2 Mbit/s with 4 wire pairs
Physical and Environment
Desktop version (W x H x D) (W x H x D) 272 x 47,5 x 175 mm
(wall- and rack-mounting option)
Operating Temperature -5° C to +55° C at 5 to 95 % rel. humidity (non condensing)
Safety EN 60950-1 (2013)
EMC/EMF EN 300386 V1.4.1 (2011)
ES 201468 V1.3.1 (2005)
ITU-T K.20/K.21 (2011)
ITU-T K.45 (2011)
EN 300132-2 V2.1.1 (2003)
EN 62479 (2010)

A3118-X642-R612-01 37 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

3.2 Typical ACCEED 1102/04 applications

ACCEED 1102/04 focuses on the following applications:
 High Speed Business Access Ethernet services (E-Line, E-LAN and E-Tree)
 Carrier demarcation for wholesale solutions
 Reliable backhaul of mobile base stations DSLAMs and PWLAN / WiMAX
 All kinds of utility solutions such as public services, railway, energy, industry
Business Access
High Speed Business Access Ethernet services as defined by the Metro Ethernet Forum (MEF) are fully
supported by ACCEED 1102/04 :

1. E-LAN service
 Port based Ethernet private LAN (EP-LAN)
 VLAN based (EVC identified by VLAN-ID) Ethernet virtual private LAN (EVP-LAN)

Figure 3-3 E-LAN service (multipoint to multipoint EVC)

2. E-Line service

A3118-X642-R612-01 38 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

 Port based Ethernet private line (EPL)

 VLAN based (EVC identified by VLAN-ID) Ethernet virtual private line (EVPL)

Figure 3-4 E-Line service (point to point EVC)

3. E-Tree service
 Port based Ethernet private Tree (EP-Tree)
 VLAN based (EVC identified by VLAN-ID) Ethernet virtual private Tree (EVP-Tree)

Figure 3-5 E-Tree service (rooted multipoint EVC)

4. E-Access service
 Port based Ethernet private Tree (EP-ACCESS)
 VLAN based (EVC identified by VLAN-ID) Ethernet virtual private Tree (EVP-ACCESS)

A3118-X642-R612-01 39 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

Wholesale Carrier Ethernet Demarcation

ACCEED 1102/04 best fits in any network demarcation applications thanks to its advanced
functionalities such as in-band management, standard compliant Link- and Service-OAM, extensive
packet counters.

Figure 3-6 ACCEED 1102/04 wholesale application

In wholesales applications ACCEED 1102/04 can be used to provide demarcation and connectivity to a
third party operator over a bonded EFM link allowing to fully monitor and control the service quality at
the NNI interface using the extensive management and OAM functionalities of ACCEED 1102/04.

A3118-X642-R612-01 40 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

Utility / Campus

At locations where copper lines are available, ACCEED 1102/04 can be used to set up high speed
campus connections as indicated in the following example. These Desktops can be used in combination
of ACCEED 1416. Between major sites can be used an optical 1 Gbit/s link, that is protected with multiple
copper wire pairs. This solution can transport Ethernet and Circuit Emulated Services.

Figure 3-7 Campus application example

A3118-X642-R612-01 41 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

3.3 System configurations

The ACCEED 1102/04 architecture can be utilized to implement single copper pair links or bonding
configurations with up to 4 wire pairs.

Figure 3-8 ACCEED 1102/04 configuration examples

 SHDSL Line
An SHDSL connection between the NT (ACCEED 1102/04) and the LT (DSLAM) over a
single copper wire pair

EFM Link
An EFM connection between the NT (ACCEED 1102/04) and the LT (DSLAM) over SHDSL
bonded lines

EVC:
An endpoint Ethernet tunnel that covers a couple of services

Service:
A endpoint to endpoint connection with defined service attributes, like dedicated bandwidth,
priority (QoS) …

Figure 3-9 Line / Link / Service definition

A3118-X642-R612-01 42 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

Mechanics

The desktop units can be used as LT (or COT = Central Office Terminal), as NT (or RT = Remote
Terminal) or as CPE.

HW options

The following HW options of ACCEED 1102 are available:

TDM G.703 E1

Power supply
LT/NT Mode

External AC
SHDSL.bis
CPE Mode

LCT serial
10/100 bT
Ethernet
part number mechanic

S3118-H642-E401 Desktop   2 1 
S3118-H642-D413 Desktop   2 4 2 
S3118-H642-E413 Desktop   2 4 
Table 1 ACCEED 1102 HW options

The following HW options of ACCEED 1104 are available:

TDM G.703 E1

Power Supply
LT/NT Mode

External AC
SHDSL.bis
CPE Mode

LCT serial
10/100 bT
Ethernet

part number mechanic Dataslot

S3118-H643-E401 Desktop   4 1 
S3118-H643-D413 Desktop   4 4 2 
S3118-H643-E413 Desktop   4 4 
S3118-H643-D211 Desktop   4 1 2 1 
Table 2 ACCEED 1104 HW options

Refer to [13] for the complete ULAF+ accessory list.

For operational use of the ACCEED 1102/04 CPE the included (delivered) external AC
power adapter must be used.

A3118-X642-R612-01 43 / 405
 ULAF+ 3 - Application overview ACCEED 1102/04 Manual

ACCEED 1102/04 combinations

This chapter is about how different ACCEED models can be connected together. The following
operational modes are supported by each model:

ACCEED LT NT CO CPE
1416   
1404 
1104   
1102   
1104 CPE   
1102 CPE   

- LT (line termination) is connected to a NT and is the Master of both devices. It remotely configures
the NT. Both devices are configured at the LT.
- NT (network termination) needs a LT
- CO (central office) mode is standalone mode of central office equipment for connecting CPEs.
SHDSL parameters are configured there. All other parameters (e.g. switching, …) are stored in
each device separately
- CPE (customer premises equipment) is standalone equipment, which needs the CO for
connecting via SHDSL, but stores its own configuration locally. The configuration channel is
typically an inband channel in an own VLAN ID.

The following combinations of devices are possible for LT-NT:

The following combinations are possible for CO-CPE:

Note: The BSRU Symbol stands for up to 8 repeater stages. The optional BSRU Repeaters are power
fed by the ACCEED 1416 only or powered locally.

A3118-X642-R612-01 44 / 405
ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

4
Quick Start Guide

This section gives step by step instructions to quickly set up a typical EFM
link using ACCEED 1102/04 and LCT+. The aim of this section is to get
quickly to a first running configuration and familiarize with ACCEED
1102/04. You will also find the links to chapters where you get the detailed
information.

A3118-X642-R612-01 45 / 405
 ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

4.1 Introduction
This chapter demonstrates how to set up an EFM link from scratch using ACCEED 1102/04, with the
help of an exemplary configuration. The exemplary EFM link consists of 2 or 4 bonded SHDSL lines.
One ACCEED 1102/04 desktop unit and a DSLAM with 4 SHDSL port supporting EFM bonding.

Figure 4-1 Quick start exemplary configuration

The following material is necessary to set up the exemplary link:

 1 x ACCEED 1102 desktop S3118-H642-D4xx
or
 1 x ACCEED 1104 desktop S3118-H643-D4xx

 1 x LCT configuration cable C195-A336-A2

 1 x LCT+ CD-ROM P3121-P45-A1
 DSLAM / MSAN with at least 4 SHDSL ports, supporting EFM bonding

Additionally the following infrastructure is necessary:

 1 x Laptop or PC
 Copper cabling

A3118-X642-R612-01 46 / 405
 ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

4.2 HW setup
ACCEED 1102/04 Setup

 No HW settings are needed to prepare the unit for the operation with the DSLAM.
 Connect the desktops to a power source (the green power LED of the desktop unit must turn ON)

ACCEED 1102/04 needs about 1.5 minutes to complete the boot process. During the boot
 phase all LED are flashing to indicate that the boot is in progress. During this time the unit
is not in operation and cannot be managed.

Wiring
Connect the wires as indicated by the picture Figure 4-2

By default all interfaces (EFM, P1...P4, TDM1..2 and NMS) are deactivated, i.e. the alarm
 LEDs are always turned off. To check the correct cabling some on site configuration is
necessary. See chapter  4.3.1.

Figure 4-2 Exemplary configuration wiring

 In case of ACCEED 1102/04 CPE the serial LCT port is missing. The unit is manageable
through the NMS Ethernet port. This NMS port is by default enabled.

A3118-X642-R612-01 47 / 405
 ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

4.3 EFM link configuration

LCT+ installation

In order to perform the configurations necessary to setup the EFM link the LCT+ is required.

Start the LCT+ installer and follow the configuration procedure.

Figure 4-3 LCT+ installation

Further details about the LCT+ installation can be found in  5.7.

Management access configuration

The ACCEED 1102/04 can be managed locally via the serial LCT interface or the NMS Ethernet
interface. Remote inband management is also supported. Please refer to  5.8.2 for the management
access options.
For a first quick start, it is recommended to use the serial LCT interface.

EFM-Link configuration
For ACCEED 1102/04 the set-up of SHDSL and EFM bonding group is fully managed by the DSLAM.
The parameters defined by the DSLAM are:
 line parameters: bandwidth, modulation, power backoff
 bonding configuration (e.g. number of copper pairs in the EFM bond)

On the ACCEED 1102/04 side the following can be set:

 PAF mode
auto: the DSLAM defines the operation mode (single line or EFM bonding)
enable: EFM bonding is enabled
disable: No EFM bonding is possible, single line operation only
 Low bandwidth alarm threshold: raises an alarm, if the available bandwidth goes below the
defined value

A3118-X642-R612-01 48 / 405
 ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

 Enable / disable the SHDSL transceiver for each of the 4 lines

 Attenuation alarm threshold
 SNR margin alarm threshold

The factory default settings are: PAF is set to Auto and all SHDSL lines are enabled.

 The ACCEED 1102/04 EFM link configuration options and information are shown in the
pictures below

A3118-X642-R612-01 49 / 405
 ULAF+ 4 - Quick Start Guide ACCEED 1102/04 Manual

Ethernet Ports
In order to set up an EFM link at least one Ethernet port has to be enabled on the ACCEED 1102/04.
The Ethernet port P1 is enabled by factory default setting.

 The Ethernet ports “enable” command can be found in

Ethernet\Switch Local\LAN Ports\Px (e.g. P1)

A3118-X642-R612-01 50 / 405
ULAF+ 5 - Installation ACCEED 1102/04 Manual

5
Installation

This chapter gives detailed information and instructions about ACCEED

1102/04 and LCT+ installation. It contains a description of the mechanics,
the power supply options, the pinning of the different interfaces, the
cabling including the management access, the DIP switches and LEDs,
the installation of the LCT+ and instructions about the necessary on site
configurations.

The aim of this chapter is to facilitate the installation of ACCEED 1102/04

for a variety of possible system configurations

A3118-X642-R612-01 51 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.1 General requirements/check list

This chapter describes how to install the ACCEED 1102/04 hardware components and the management
software LCT+.

For the installation of other ULAF+ components, such as:

 The 16 + 1 slot Subrack V3 (7 HU)
 The 16 + 1 slot Subrack V2 (8 HU)
 The Compact Shelf (2 HU)
 The Management and traffic concentrator units MCU, MCU-S and MCU-CES
 The Operation and Maintenance unit OMI SNMP
 The SHDSL regenerator BSRU
 And others

Refer to [1] and [2].

The following tasks must be carried out for each system component before/during installation:

 The scope of delivery and installation is complete:

- Check the delivery for completeness using the delivery order.
- Cabling and placement of the shelves must be checked for each individual system component
using the installation instructions.
- The plug in units (if any are used) must be fitted securely.
- Both the external and the internal cabling are correct.
 The hardware is in the as-delivered state:
- Check the hardware-specific settings of the plug in units
- The system voltage is connected and continuously available.
 There is ULAF+ and, if required, AccessIntegrator documentation on site ([9],[10],[11]).
 The LCT+ is installed and operational ( 5.7 and  6.2).

ACCEED 1102/04
ACCEED 1102/04 is the Albis Technologies Ethernet First Mile Copper Long Reach (EFMC LR)
Ethernet Demarcation Device unit for MSAN and DSLAM facilities. It allows the implementation of a
broad variety of applications in the field of carrier grade Ethernet. Please refer to  3.2

ACCEED 1102/04 is available as desktop.

Figure 5-1 ACCEED 1102/04

A3118-X642-R612-01 52 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

LCT+
LCT+ is the Local Craft Terminal used to configure and operate the ULAF+ devices. LCT+ is a Java
based SW application. For more details on the LCT+ please refer to  6.2.

A3118-X642-R612-01 53 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.2 Power supply

Power supply configurations
The ACCEED 1102/04 features the following power supply configurations:

Power configuration Desktop CPE

Local power supply with 110/230 VAC  

Local power supply with 48/60 VDC  -

Remotely fed via SHDSL interface  -

Table 3 power supply modes

Power supply to the plug in unit

Not applicable.

Power supply to the desktop unit

The ACCEED 1102/04 supports the following options for power supply of the desktop unit:

ACCEED 1102/04 CPE units

 Local power supply with 110 VAC or 230 VAC (valid range 95 – 260 VAC) provided through included
AC Adapter
 Remote power supply not available

For operational use of the ACCEED 1102/04 CPE the included (delivered) AC adapter
must be used.

A3118-X642-R612-01 54 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

1 main earth terminal for grounding

2 local power supply terminals
3 jumper settings for local feeding (AC or DC)
4 jumper settings for remotely fed
5 printed circuit board
6 desktop case

Figure 5-2 Location of desktop power supply terminals and selection jumpers

Modifications to the type of supply and grounding may only be made by trained personnel.

A3118-X642-R612-01 55 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.2.2.1 Changing from AC to DC power supply

You can convert the desktop unit from AC to DC supply after it has been installed. To do this, proceed
as follow:

1. Disconnect the power cord and also disconnect all interface cables
2. Release the screws on the bottom of the unit
3. Open the housing by removing the top of the unit
4. Remove the power cord connector or replace the existing power cord with a battery cable
5. Close the housing
6. Screw the screws on the bottom of the unit into the housing

 The input voltage of desktop devices is monitored in order to generate a power fail alarm
in case of power failure. If the input voltage drops below the threshold value (about 100V),
the power fail alarm is raised. Desktops configured as ”NT“ additionally send a so-called
`dying gasp` message to the LT device via transmission interface.
In case of utilization of a DC power source (<100V) the power-fail signaling can be
suppressed using the LCT+.

1 main earth terminal for grounding

2 local power supply terminals (N, L and ground)
3 jumper settings for local feeding (only relevant for ACCEED 1416, 1404, 1104, 1102)
4 jumper settings for feeding from remote (only relevant for ACCEED 1416, 1404, 1104, 1102)
5 printed circuit board
6 desktop case

Figure 5-3 AC and DC power supply

5.2.2.2 Change from local power feeding to remote power feeding

To convert the desktop unit from local supply to remotely fed, proceed as follows:

1. Disconnect the power cord and also disconnect all interface cables
2. Release the screws on the bottom of the unit
3. Open the housing by removing the top of the unit
4. Remove the power cord
A3118-X642-R612-01 56 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5. Change the jumpers as detailed in  5.2.2.3

6. Close the housing
7. Screw the screws on the bottom of the unit into the housing

5.2.2.3 Set the ACCEED 1102/04 power supply source via jumpers

Jumpers are only available on desktop units and are necessary to setup the following configurations:
 Local power supply AC or DC
 Remote power feeding

The housing must be opened to change the jumper settings on the desktop unit. For this action, the
screws on the bottom of the unit must be released.

Before opening the desktop device the power feeding must be interrupted and the
interface connector disconnected. The following settings must only be carried out by
trained personnel.

The jumper must be set as specified by this manual. All other combinations are not allowed
and can lead to danger to the installer or the user (electric shock or fire).

The following instructions only apply if the corresponding jumper sockets are equipped on the ACCEED
1102/04.

Jumper Meaning
3 ACCEED 1102/04 desktop unit local supply; AC or DC
4 ACCEED 1102/04 desktop unit remotely fed
Table 4 Position of jumpers 3 and 4 on the ACCEED 1102/04 desktop units

Desktop unit local supply AC or DC

A3118-X642-R612-01 57 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

1 main earth terminal for grounding

2 local power supply terminals
3 jumper settings for local feeding
4 jumper settings for feeding from remote

Figure 5-4 Jumper settings: ACCEED 1102/04 desktop unit local supply; AC or DC

Desktop unit supplied remotely

1 main earth terminal for grounding

2 local power supply terminals
3 jumper settings for local feeding
4 jumper settings for feeding from remote

Figure 5-5 Jumper settings: ACCEED 1102/04 desktop unit remotely fed

5.2.2.4 Fuses F10, F11

The power supply is protected with fuses. More details are included in Table 5.

Type of fuses Equipped on …

F10: 2AT / 250V all ACCEED 1102/1104 DT models
F11: 2AT / 125V ACCEED 1102/04 CPE DT units
Table 5 Usage of fuse types

The fuses have a protective function and must be replaced by fuses with exactly the same
! electrical specifications.

A3118-X642-R612-01 58 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.3 Grounding concept

The sub rack must always be grounded.
ACCEED desktops must be grounded via a cable with a conductor cross section of at least 0,75mm 2,
if remotely fed with a voltage 120VDC (only applicable for SHDSL units).

The earthing of remotely fed desktop units is mandatory, if the received voltage exceeds
120VDC.

The symbol  located on the type label must also be made invisible (e.g. covering with
adhesive paper).

The grounding of the ACCEED 1102/04 desktop can be made with the main earth
terminal (Figure 5-6, ) on the rear panel of the device or by opening the desktop and
 connecting the ground wire to the local power supply earth terminal (
Figure 5-3, ).

1 main earth terminal for grounding

2 power cord opening
7 alarm output connector (not equipped in all models)
8 air flow openings

Figure 5-6 Rear panel of the ACCEED 1102/04 desktop with main earth terminal for grounding

A3118-X642-R612-01 59 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.4 Interfaces / pinning

Figure 5-7 ACCEED 1102/04 front panel interfaces and LEDs

summary LEDs:
 PAF (red/green)
1  maintenance (yellow) 2 LCT serial RS232 interface
 alarm (red/yellow)
 power (green)
3 10/100bT Ethernet port 1 4 10/100bT Ethernet port 2-4
Network Management System Ethernet
5 Dataslot module 6
interface
7 G.703 Interfaces: TDM1 and TDM2 8 SHDSL connector
9 2 or 4 SHDSL line alarm LEDs

In case of ACCEED 1102/04 CPE:

Figure 5-8 ACCEED 1102/04 CPE front panel interfaces and LEDs

A3118-X642-R612-01 60 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

SHDSL interface

ACCEED 1102/04 has one RJ45 SHDSL connector located on the front panel (SHDSL-U).

Four SHDSL copper pairs (1, 2, 3 and 4) are wired on the SHDSL connector. The Pin assignment is
according to a standard twisted pair LAN cable.

Connector Pin assignment Signal Description

4 SHDSL 1 a
SHDSL interface – wire pair 1
5 SHDSL 1 b
1 SHDSL 2 a
SHDSL interface – wire pair 2
2 SHDSL 2 b
3 SHDSL 3 a
SHDSL interface – wire pair 3
6 SHDSL 3 b
7 SHDSL 4 a
SHDSL interface – wire pair 4
8 SHDSL 4 b
Shield Ground Ground
Table 6 Pin assignment of the SHDSL interface

Note: ACCEED 1102 uses only wire pair 1 and 2.

Ethernet interfaces (10Base-T/100Base-Tx)

ACCEED 1102/04 has 1x or 4x RJ45 Ethernet plugs located on the front panel: P1, P2, P3 and P4.

The pinning corresponds to the 802.3ab standard.

Connector Pin assignment 10/100Base-T

1 Tx +
2 Tx -
3 Rx +
4
5
6 Rx -
7
8
Casing Ground
Table 7 Pin assignment of the Ethernet interfaces (P1, P2, P3 and P4)

 If necessary, send and receive data can be automatically swapped by the Ethernet Port
(Configuration: Auto MDI/MDI-X or fix MDI or fix MDI-X).

A3118-X642-R612-01 61 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

SFP slot interface

Not applicable

NMS interface (10/100 Base-T)

ACCEED 1102/04 has a RJ45 NMS connector located on the front panel (NMS).

Connector Pin assignment 10/100Base-T

1 Tx +
2 Tx -
3 Rx +
4 --
5 --
6 Rx -
7 --
8 --
Casing Ground
Table 8 Pin assignment of the NMS interface

TDM (G.703) and Clock Interfaces

ACCEED 1102/04 front panel interface

ACCEED 1102/04 has one or two RJ45 Clock input/output interface connector located on the front panel
(marked as CLOCK or TDM port). A BNC connector is available using an adapter cable BNC-RJ45.

Each 2 MHz or G.703 clock interface can be configured to 75 or 120 impedance via the NMS.

Connector Pin Signal Description

assignment 120Ω 75Ω
1 TxA TxA
Transmit data
2 TxB Tx_SHIELD
3 Tx_SHIELD Tx_SHIELD Transmit data shield
4 RxA RxA
Receive data
5 RxB Rx_SHIELD
6 Rx_SHIELD Rx_SHIELD Receive data shield
7 - -
8 - -
Shield Shield Shield Overall shield
Table 9 Pin assignment of the TDM/clock interface

The TDM/clock interface can be used as Input and/or Output

 The clock interface is available on ACCEED 1102/04 models with the G703 option only
(see Table 1 and Table 2).

A3118-X642-R612-01 62 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

LCT serial interface

Connector Pin assignment Signal Description

1 -
2 -
3 RxD Receive data
4 TxD Transmit data
5 GND Ground
6 -
7 -
8 -
Table 10 Pin assignment of the LCT serial interface

 The pins 1, 2, 6, 7 and 8 must not be connected

The serial interface parameters:

 115.2 kBaud with
 8 data bits,
 1 start bit,
 1 stop bit,
 no parity and
 no handshake.

A3118-X642-R612-01 63 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.5 DIP switches

Not applicable

A3118-X642-R612-01 64 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.6 Visual indications

ACCEED 1102/04 operating status and monitoring are indicated by LEDs on the front panel.
Additional alarm signaling is provided by LEDs incorporated into some of the RJ45 sockets.

Figure 5-9 Visual signaling of the ACCEED 1102/04

A3118-X642-R612-01 65 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

location LED Visual signaling Status

off PAF has no connection. No Traffic is forwarded
PAF
green PAF discovered and full data traffic established
off Maintenance mode not active
Maintenance function active. See chapter 5.9 for a
yellow on
MAINT detailed list of the maintenance functions.
Firmware on LT and NT are not compatible or
1 yellow blinking
configuration is not supported by NT
off no alarm or `warning`
Alarm red on `critical` or `major` alarm
yellow on `minor` alarm
off no power supply
PWR
green on power supply ok
off no connection
ETH P1..4
on link up
green
blinking traffic (rx/tx)
3&4
off half duplex
ETH P1..4
on full duplex
yellow
blinking collisions
off no connection
NMS green on link up
6 blinking traffic (rx/tx)
off half duplex
NMS yellow
on full duplex
off external clock signal OK or disabled
on LOS clock in (G.704)
TDMx red
7 blink slow Clock not available
blink fast LFA clock in (G.704)
TDMx yellow blink slow Clock output squelched
off no alarm
9 SHDSL 1..4 red on LOS
red blinking LOSW, training
off no alarm
Left (SHDSL 1)
9 red on LOS
Rgt (SHDSL 2)
red blinking LOSW, training
Table 11 ACCEED 1102/04 visual signaling

In case of ACCEED 1102/04 CPE:

Figure 5-10 ACCEED 1102/04 CPE visual signaling

A3118-X642-R612-01 66 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

location LED Visual signaling Status

off PAF has no connection. No Traffic is forwarded
PAF
green PAF discovered and full data traffic established
off Maintenance mode not active
Maintenance function active. See chapter 5.9 for a
yellow on
MAINT detailed list of the maintenance functions.
Firmware on LT and NT are not compatible or
1 yellow blinking
configuration is not supported by NT
off no alarm or `warning`
Alarm red on `critical` or `major` alarm
yellow on `minor` alarm
off no power supply
PWR
green on power supply ok
off no connection
ETH P1..4
on link up
green
blinking traffic (rx/tx)
3
off half duplex
ETH P1..4
on full duplex
yellow
blinking collisions
off no connection
NMS green on link up
6 blinking traffic (rx/tx)
off half duplex
NMS yellow
on full duplex
off no alarm
9 SHDSL 1..4 red on LOS
red blinking LOSW, training
off no alarm
Left (SHDSL 1)
9 red on LOS
Rgt (SHDSL 2)
red blinking LOSW, training
Table 12 ACCEED 1102/04 CPE visual signaling

Figure 5-11 ACCEED 1102/04 slow blinking LED

Figure 5-12 ACCEED 1102/04 fast blinking LED

To get further help in case of installation failures see  12.

A3118-X642-R612-01 67 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.7 LCT+ SW installation

This section describes installation of the LCT+ (Local Craft Terminal) software. LCT+ is a Java based
SW application necessary for the management of ACCEED 1102/04.

ACCEED can also be managed with the network management system MetroIntegrator
 Version 1.0 and higher. Refer to [9] for information regarding the installation of
MetroIntegrator.

System requirements
The following minimum system requirements must be met:

HW:
CPU: Pentium 4 (2 GHz) or Athlon XP (2000+) processor or higher
Memory: 1GB RAM

Operating system:
 Windows 2000
 Windows XP
 Windows Vista
 Windows 7

For all Windows operating systems it is advisable to always use the newest available service pack.

Java Runtime Environment:

 Java RE Version 1.6

Graphics:
 at least 1024x768 resolution

Connectivity:
 Serial Interface or USB with external “serial to USB” converter
 10/100BaseT Interface

Installation of the Software

The LCT+ SW is distributed as setup program that guides the user through the installation procedure.

Setup_LCT+_V3.20.exe

Figure 5-13 LCT+ setup program

The installation and un-installation of the LCT+ SW requires Administrator privileges. It is

 advisable to install the LCT+ SW always with the same user account (e.g. Administrator)
on the same system. This ensures proper de-installation and installation of the LCT+
SW.

A3118-X642-R612-01 68 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.7.2.1 First LCT+ installation

To install the software, proceed as follows:

1 Double click on the setup icon. The following installation dialogue is displayed

Figure 5-14 LCT+ setup wizard

2 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).

Figure 5-15 LCT+ components to install

The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. If LCT+ is
installed, customer specific extensions (Add-ons) can be installed optionally. The selection occurs at
this stage of the installation. The installer window contains the following information:
 list of available components to install (1)
A3118-X642-R612-01 69 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

 A description of the selected component (2)

 The space required for the installation (3)

3 Select which component to install.

4 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).

Figure 5-16 Add-on source folder

If “LCT+ Add-on” has been selected in the previous screen, you can select the source path
5 from where customer specific extensions are copied. Then press `Next >` to continue.
If “LCT+ Add-on” was not selected this screen will not appear

Figure 5-17 Destination folder

A3118-X642-R612-01 70 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

You can choose where to install the program on your computer.

The following folder is suggested for the installation:
6 C:\Program Files\Albis Technologies\LCT
Choose a destination folder and press `Next >` to continue with the upgrade (or `cancel` to
abort the installation).

Figure 5-18 Shortcuts

You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
7 Press `Install` to complete the installation or `Cancel` to abort the operation.

Figure 5-19 Completing the LCT+ Setup

A3118-X642-R612-01 71 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.7.2.2 LCT+ Upgrade (installation of a newer SW version)

If you already have a LCT+ SW installed on your computer and you want to update it with a new version,
proceed as follows:

1 Double click on the setup icon. The Setup Wizard is started

Figure 5-20 LCT+ setup wizard

2 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).

Figure 5-21 LCT+ previous version detected

A3118-X642-R612-01 72 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

The presence of a LCT+ SW has been detected. Before proceeding with the installation the former
installed version has to be removed. It is possible to abort the update procedure and keep the current
LCT+.

3 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).

Figure 5-22 LCT+ components to install

The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. If LCT+ is
installed, customer specific extensions (Add-ons) can be installed optionally. The selection occurs at
this stage of the installation. The installer window contains the following information:
 list of available components to install (1)
 A description of the selected component (2)
 The space required for the installation (3)

4 Select which component to install.

5 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).

A3118-X642-R612-01 73 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

Figure 5-23 Add-on source folder

If “LCT+ Add-on” has been selected in the previous screen, you can select the source path
6 from where customer specific extensions are copied. Then press `Next >` to continue.
If “LCT+ Add-on” was not selected this screen will not appear

Figure 5-24 Destination folder

You can choose where to install the program on your computer.

The following folder is suggested for the installation:
7 C:\Program Files\Albis Technologies\LCT
Choose a destination folder and press `Next >` to continue with the upgrade (or `cancel` to
abort the installation).

A3118-X642-R612-01 74 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

Figure 5-25 Shortcuts

You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
8 Press `Install` to complete the installation or `Cancel` to abort the operation.

Figure 5-26 Completing the LCT+ Setup

A3118-X642-R612-01 75 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8 On site configuration

This section describes configurations, which must be performed on site during the installation, in order
to guarantee a correct installation and cabling.

The aim is to guarantee that once the installation has been completed, the equipment can be
managed remotely and there is no need to return to the equipment location.

These steps include:

1. Configure the remote access (IP address ...) [optional]

2. Configure CES parameters for E1 and Dataslot transport [optional]
3. Configure the time settings [optional]

Boot up

ACCEED 1102/04 needs about 2 minutes to complete the boot process. After power up
 during the boot phase all LED are flashing to indicate the boot activity. During this time
the unit is not in operation and cannot be managed.

ACCEED 1102/04 management interfaces

The following access paths can be used to manage ACCEED 1102/04:

 Serial interface (RS232) on the front panel (not available in ACCEED 1102/04 CPE units)
 NMS Ethernet interface on the front panel
 In-band management

 For on site installation it is recommended to use the serial interface. Please use the serial
cable with the pinning as described in  5.4.6

For ACCEED 1102/04 CPE the NMS port and the in-band NMS port are activated by
default. Remote LCT Access is enabled too.

 Please use a standard Ethernet cable for the external NMS connection. The device will
use the IP 10.0.0.1 on this port.
The in-band NMS will retrieve its IP and Gateway IP from the network DHCP via the
SHDSL connection.

A3118-X642-R612-01 76 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8.2.1 Access via serial interface

Connect the serial cable to the LCT interface and start the LCT+.
In the Connection Tab select `COM` and enter your port number.

Figure 5-27 LCT+ connection via RS232 interface

 The serial interface runs at the speed of 115200 Bit/s. The PC interface is automatically
set up. No manual configuration is necessary.

A3118-X642-R612-01 77 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8.2.2 Access via NMS interface

Figure 5-28 Example of ACCEED NMS management connections

To be able to access the device via NMS port, the port must be enabled and must have a valid IP-
address (with IP-Netmask and Default Gateway).
The IP address configuration can be done either statically in NMS port configuration or dynamically
using DHCP server.
When the configuration is done statically, it is required to configure the IP address and IP-Netmask of
the NMS port and the Default Gateway of the connection.

 The parameters IP-address and IP-net mask are located in

Board\Local\Management Access\NMS Port

A3118-X642-R612-01 78 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

Note: The NMS Port of the ACCEED 1102/04 is capable of 100 BT Full duplex or Autonegotiation.
Collisions will be neither counted nor displayed on the LED

 The Default Gateway parameter is common for the NMS and in-band port and is located in:
Board\Local\Management Access

When the configuration is done dynamically, it is required to configure the DHCP parameters (IP
Configuration and DHCP options).

 The DHCP parameters are located in

Board\Local\Management Access\NMS Port

The DHCP discover will be sent periodically. It can be manually invoked by pressing the DHCP Renew
button.

 LCT connections to the network element via NMS or in-band port utilize a TCP connection
(Port 2101).

A3118-X642-R612-01 79 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8.2.3 Access via Inband Management

To be able to access the device via Inband (management channel is embedded in the data plane) the
following parameters have to be configured:
 Enable in-band management
 Port selection (through which switch ports are in-band management connections allowed)
 IP Address and IP-Netmask or dynamic DHCP IP resolution
 Management VLAN enabling (if checked, a VLAN Tunnel is used for the inband management)
 Management VLAN ID (VID of the Tunnel)
 CoS value (priority) for the management channel (1.p bits of the VID Tag)
 DSCP (optional)
 Transmit Queue (optional)

 The parameters are located in Board\Local\Management Access\Inband

A3118-X642-R612-01 80 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

 The Default Gateway parameter is common for the NMS and inband port and is located in
Board\Local\Management Access

 LCT connections to the network element via NMS or in-band port utilize a TCP connection
(Port 2101).

ACCEED 1102/04 access control of management interfaces

This chapter is about the different access control possibilities of the management.
5.8.3.1 Access control of LCT+
The ACCEED 1102/04 can be accessed via serial or remote access (NMS port and/or Inband
interface). The maximum number of equivalent LCT+ sessions can be restricted.
By default remote access is disabled.

 The parameters are located in Board\Local\Management Access\LCT

5.8.3.2 Access control of CLI

The ACCEED 1102/04 can be accessed via serial, telnet or secure shell (NMS and/or Inband port).
The maximum number of equivalent CLI sessions can be restricted.
By default telnet and SSH are disabled.

A3118-X642-R612-01 81 / 405
ULAF+ 5 - Installation ACCEED 1102/04 Manual

 The parameters are located in Board\Local\Management Access\CLI

A3118-X642-R612-01 82 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8.3.3 Access control of SNMP

The ACCEED 1102/04 can be accessed via SNMP V1, V2c and V3 (NMS and/or Inband port). The
communities are individually configurable. So are the secure parameters of the SNMP V3 protocol.
Up to 8 different trap destinations (IP addresses) are configurable independently.
By default SNMP V1, V2c and V3 are disabled. No trap destinations are defined.

 The parameters are located in Board\Local\Management Access\SNMP

A3118-X642-R612-01 83 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.8.3.4 Syslog
Syslog enables the ACCEED 1102/04 to send all log entries via the syslog protocol to 8 different
Syslog remote hosts. 3 different categories are selectable for each remote host entry.
By default no remote host is defined

 The parameters are located in Board\Local\Management Access\Syslog\Remote Host

5.8.3.5 Authentication
Authentication describes a method to authorize users with centralized authentication database servers
(via e.g. RADIUS). Please see further details in  11.3.5.1.

5.8.3.6 Access control via Access Control Lists (IP)

The management access can be restricted with an IP access control list (ACL) to specific source IP
address ranges.
Please see further details in  11.3.5.3

SCC connections

Not applicable.

EFM link Setup

Not applicable.

Remote Power Supply

Not applicable.

Power over Ethernet (PoE)

Not applicable.

A3118-X642-R612-01 84 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

Time settings
A real time clock is available on ACCEED 1102/04. This can be set automatically via NTP-UNICAST,
MCU system bus time or can be configured manually.

 Time settings are located in Board\Local\Time Settings

`ULAF` mode: the ACCEED 1102/04 plugin requests its time from the central MCU/-S/-
CES or from the LT

`Manual` mode: the button `Set Date and Time` is available. Pressing this button a pop up
dialogues opens, which permits to manually set date and time (note: the pop up dialogue
already contains the current date and time of your PC/Laptop).

`NTP Unicast` mode: the IP address of a Time Server must be configured. The button
`Synchronize with server` is available to force immediate synchronization with the NTP
server.

`PTP` mode: the real time clock is copied from the PTP clock (ACCEED 2104 PTP only)

A3118-X642-R612-01 85 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

5.9 Maintenance functions

ACCEED 1102/04 offers several maintenance tools, which can be used to locate faults and / or ensure
correct operation.

 The yellow maintenance LED and the maintenance field on the LCT+ status bar indicate
the activation of any of the maintenance functions.

Loopback
ACCEED 1102/04 features the following loopbacks:
5.9.1.1 Loopback 1a
Not applicable.

5.9.1.2 Loopback 3a
Loopback 3a is a loopback on ACCEED 1102/04 SHDSL transceiver. SHDSL loopbacks are described
in  7.2.7.

5.9.1.3 Ethernet Loopbacks

The ACCEED 1102/04 is capable of port or VLAN based loopbacks. The port loopback can be
activated on each egress Ethernet port which sends all outgoing frames back into the switch. The
VLAN based loopback can be set on each ingress Ethernet port and loop frames inside the received
traffic stream based on the primary and/or secondary VLAN ID. The loopbacks can handle MAC
swapping. They can be auto turned off after a defined duration.
Ethernet Loopbacks are described in  8.3.3

5.9.1.4 Link OAM Loopbacks

Each ACCEED 1102/04 Ethernet port features a loopback which is controlled by its Link OAM peer.
Each ACCEED 1102/04 Ethernet port features a command to remotely set a loopback on the peer
Ethernet interface.
Link OAM loopbacks are described in  9.1.2.2

5.9.1.5 SOAM Loopbacks

SOAM Loopbacks are a sort of “Ethernet Ping”. A SOAM loopback is started on a MEP; possible targets
are MEPs and MIPs in the same domain (MEG/MA). Destination is either a Unicast- [IEEE, ITU-T] or
Multicast-MAC address [ITU-T].
SOAM loopbacks are described in  9.2.2.4

5.9.1.6 SOAM Link Trace

With SOAM link trace the location of a fault can be determined by sending link trace messages (LTM).
This works analogous to the trace route on the IP layer. When a LTM is sent to a MEP, all intermediate
MIPs respond with a link trace response (LTR) message along the path. The faulty location can be
identified based on the returned LTR messages.
SOAM link trace is described in  9.2.2.5

BER test
ACCEED 1102/04 contains facilities to perform BER test on each SHDSL line separately. BER test
allows to inject a test signal over the SHDSL line and to measure the bit error rate on the line for a
certain period (1 minute to 24 hours in several steps).
The BER Test is described in  6.5.9.

A3118-X642-R612-01 86 / 405
 ULAF+ 5 - Installation ACCEED 1102/04 Manual

Switch port mirroring

Port mirroring allows to duplicate the ingress traffic of a port (mirror port) and to output it on a different
port (analyzer port).
Port mirroring is described in  8.4.5.

Trap suppression
During the execution of maintenance activities it may be necessary to prevent the network management
system from being flooded by alarm information. ACCEED 1102/04 therefore offers the possibility to
disable the generation of traps.
Trap suppression is described in  9.1.

A3118-X642-R612-01 87 / 405
ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6
Configuration and operation

This chapter gives detailed information and instructions about how to

configure and operate ACCEED 1102/04 and LCT+. It contains a
description of both ACCEED 1102/04 and LCT+ features. It shows how to
setup the desired configuration with typical examples. Further it contains
a description of all the alarms and performance management counters. A
special section is dedicated to the LCT+. The chapter follows the structure
of the LCT+ dialogues.

The aim of this chapter is to facilitate the configuration and operation of

ACCEED 1102/04 and LCT+.

A3118-X642-R612-01 88 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.1 Management access

There are different possibilities to access the management plane of the ACCEED device. Users who
like to work with a graphical user interface (GUI) can choose between the local craft terminal (LCT+,
TCP connection at port 2101) and the Network management System (MetroIntegrator, SNMP based).
Users who like command line interface (CLI) for scripting and automation purposes may use TCP/IP
ports for telnet or SSH.

The configuration of the management access is described in the installation chapter. Refer to  5.8.2.

 The OMI SNMP and the MCU have no telnet or SSH client. ACCEED units in such sub
racks can be accessed via in band management

Token mechanism
All ACCEED units are accessible through Remote LCT (TCP 2101), SNMP and CLI (Telnet or SSH).
Some of them are accessible via serial LCT or serial CLI. To prevent inconsistency in the database
only one write access user at a time is allowed. Therefore a write token mechanism is implemented
working as follows:
- If write token is available, the user asking for the token gets write access rights. All following
users asking for the write token get just read access rights
- The user with the write access rights returns the token, when quitting his session.

The behavior of getting write access via the different access methods:
- LCT+ asks for the write token at any user interaction
- LCT+ releases the write token, when the session is disconnected or after 30 minutes without a
user interaction
- CLI asks for the write token, anytime during the active session
- CLI releases the write token, when the CLI session is disconnected or the CLI timeout is
reached (automatic logoff after 1..60 minutes)
- SNMP never asks for a write token, since no configurations are allowed via SNMP

A3118-X642-R612-01 89 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.2 LCT+
Introduction
The Local Craft Terminal (LCT+) is a Java based software application which can be used to manage
the ULAF+ system either locally (via serial interface) or remotely (via a TCP connection over a
dedicated network or in-band).

The LCT+ Graphical User Interface (GUI) has been designed to support the user allowing an intuitive
and easy to learn management of the ULAF+ network elements.

Figure 6-1 LCT+ Graphical User Interface

The following management areas are covered by LCT+

 Fault Management
 Configuration Management
 Performance Management
 Security Management
 SW Management

Starting the LCT+

Make sure that you have installed the LCT+ in accordance with  5.7.

Make sure the LCT+ is connected to the network element. The following options are available:
 Serial interface (RS-232)
 Network Management System (NMS) Ethernet interface
 In band

Refer to  5.8.2 for more information about connectivity.

A3118-X642-R612-01 90 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Start the ULAF+ LCT+ either by double clicking the ULAF+ LCT+ shortcut on the desktop or via the
Start menu item “ULAF+ LCT+” in StartProgramsAlbis TechnologiesLCT.
After the Albis Technologies Splash Screen, the following window will be opened:

Figure 6-2 LCT+ start dialogue

Choose which interface has to be used to establish a connection to the network element:
 COM (serial interface)
o The ‘COM Port’ which is used by LCT+ must be selected from drop-down list
 TCP interface
o A valid IP address of the network element (NE) must be entered
o Options for the connecting to the NE directly or through a Portserver
 `OMI SNMP/MCU/NE`: the LCT+ connects directly to the NE’s IP
 `Portserver`: the LCT+ connects to the portserver’s IP, which is connected to the NE
through the serial interface. For this option the TCP port must be entered.
o Optionally a SOCKS5 proxy can be used, if the TCP port 2101 is blocked, e.g. by a firewall.
The proxy uses the southbound TCP port 2101 and a northbound TCP port, that can be
defined individually, e.g. 1080. The LCT+ communicates via the northbound TCP port with the
proxy and forces it to use the southbound TCP port 2101 through the SOCKS5 protocol.

 The portserver option applies to legacy ULAF+ equipment, without Ethernet connectivity

Click on the button.

A3118-X642-R612-01 91 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

The Login window appears:

Figure 6-3 LCT+ Login dialogue window

The ULAF+ LCT+ allows two different levels of user access:

 Administrator with full access to the entire system
 Maintenance with read permission to monitor the system and with the possibility to apply
maintenance functions (like loopbacks)

Select the relevant ‘Username’ and enter the appropriate password:

Default passwords for MCU / MCU-S / MCU-CES / ACCEED:
 Administrator: UlafPAdm
 Maintenance: UlafPMnt

Default passwords for OMI SNMP / Desktops (except ACCEED):

 Administrator: SAZHigh
 Maintenance: SAZLow

Other usernames may be used if a remote authentication service such as RADIUS is enabled (
11.3.5.1).

The graphical user interface

Figure 6-4 LCT+ GUI

A3118-X642-R612-01 92 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

The title bar is described in  6.2.4, the menu bar is described in  6.2.5 and the status bar is
described in  6.2.6.

The LCT+ work area is divided in to the following 3 parts:

 the control area (see  6.3)
The summary area is located in the upper left corner of the work area and contains the following
dialogues:
- Tree
- Connection
- User Management
- Download
- SCC FW Sync
 the view area (see  6.4)
The view area is located in the upper right corner of the work area and is divided into the following
sub-regions:
- Rack View (if connected to MCU, MCU-S, MCU-CES or OMI-SNMP)
- Ethernet View
- Aggregation View
- Array View
 the table area (see  6.5)
The table area is located in the lower right corner of the work area and is divided into the following
sub-regions:
- Fault
- Alarms
- Maintenance
- SOAM
- Localization
- Ping
- Configuration
- ACCEED 1102/04
- Summary
- Performance
- Line Parameters
- Error Counters
- BER Measurement
- Statistics
- Utilization
- SAT
- CES
- Search

A3118-X642-R612-01 93 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Title bar
The title bar of the LCT+ windows provides the following information:
 Connectivity (COM port or IP address)
 Slot number of the actual unit
 Username(Administrator or Maintenance)
 Version of the LCT+

Figure 6-5 LCT+ window header example

Menu bar
The menu bar contains the following menus:
 File
 Options
 Help
6.2.5.1 File Menu

The File menu is shown in

Figure 6-6 and contains the following commands:

A3118-X642-R612-01 94 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Figure 6-6 File Menu

6.2.5.1.1 Restore Factory Settings and Reboot (Ctrl+R)
This command restores the factory default configuration of the unit.
The command is also available via the control sequence (Ctrl+R)

Since this command will replace all configurations including the management access
 configuration (e.g. the IP address and passwords) with the default values, the remote
connectivity to the network element will be lost.

To restore the default configuration the unit will be rebooted.

To prevent an accidental reset of all device configurations, the user is requested to confirm this
command.

6.2.5.1.2 Clear Configuration (Ctrl+G)

This command clears the complete configuration without a reboot
The command is also available via the control sequence (Ctrl+G)

To prevent an accidental reset of all device configurations, the user is requested to confirm this
command.

6.2.5.1.3 Set Mode

This command sets the operation mode of the ACCEED 1102/04, which is typically done during
installation. Since these units are capable of working with other ULAF+ units (LT-NT) or as stand
alone units (CPE) on a DSLAM, the operation mode is mandatory. By default, the CPE mode is active.

The units are capable of taking the role as LT, NT or CPE. The combinations are found in  3.3.3

After selecting the new mode a warning window appears. All data configured will be lost, when
pressing “OK”

A3118-X642-R612-01 95 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.2.5.1.4 Connect (Ctrl+N)

This command connects LCT+ to the device specified by the connection options (serial interface or
TCP connection).
The command is also available via the control sequence (Ctrl+N)

6.2.5.1.5 Disconnect (Ctrl+D)

This command disconnects LCT+ from current connected device
The command is also available via the control sequence (Ctrl+D)

 LCT+ automatically detects disconnections (e.g. cable pulled out) and notifies the user by
a pop up window.

6.2.5.1.6 Save configuration (Ctrl+S)

The save configuration is described in  6.6.1.

6.2.5.1.7 Load configuration (Ctrl+L)

The load configuration is described in  6.6.2.

6.2.5.1.8 Quit (Ctrl+Q)

This command terminates the LCT+ application.
The command is also available via the control sequence (Ctrl+Q)

6.2.5.2 Options Menu

The options menu is showed in Figure 6-7 and contains the following commands:
 Preview Mode
 Preferences

Figure 6-7 Options Menu

6.2.5.2.1 Preview Mode (Ctrl+P)
The preview menu is described in  6.6.3.

6.2.5.2.2 Reset Window Setting

Restore the original Window proportions of all window sections (factory defaults).

A3118-X642-R612-01 96 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.2.5.2.3 Preferences (Ctrl+E)

The Preferences menu is described in  6.6.4.
6.2.5.3 Help Menu
The Help menu contains the `About` item

Figure 6-8 Help Menu

The `About` item delivers version and copyright information about the LCT+ application

Figure 6-9 LCT+ About Window

Status bar
The LCT+ status bar contains the following information.

Figure 6-10 LCT+ window bottom detail example

1. Progress bar
The progress bar informs about the state of data synchronization between LCT+ and the
connected unit.
`Idle` indicates that currently no data is exchanged/pending between LCT+ and network element.

During data transfer the progress bar indicates the types of data being exchanged as well as a
percent indication of the progress.

Figure 6-11 LCT+ progress bar example

2. Preview
The Preview field indicates whether the LCT+ is in `preview mode` (display of a generic virtual line
model composed of a LT array and a NT array) or not (display of units physically connected to
LCT+). The preview mode is useful to configure devices, which are not yet physically available (for
instance to configure NT Ethernet parameters, before it is connected to the LT). More information
about the preview mode can be found in  6.6.3.
In preview mode the preview field of the status bar turns blue as indicated by the following picture.
A single left click on this field toggles the preview mode like a button.

Figure 6-12 LCT+ preview mode active

A3118-X642-R612-01 97 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

3. Token
The token state indicates whether the LCT+ has the write access permission. Since the system
allows multiple user access to the network elements (for example more than one LCT+ connection
or LCT+ and MetroIntegrator), a mechanism to prevent concurrent write access has been
implemented.
If LCT+ doesn’t have the write permission (token state is red), it is not possible to
change configurations, because another user is connected to the device (via LCT+ or
AccessIntegrator).
The write access will be automatically granted (token state green), as soon as the
concurrent access session is terminated (other user closed the connection to the
network element).
If no user interaction is taken for 30 minutes the LCT+ releases the write token and
change to the yellow token state. Unlike an automatic logout all user changes are still
available, but need the write permission again to be applied.

4. Alarm
The alarm state shows the alarm summary of the connected device. A single left click on this field
shows all alarms in one list (sets the Tree path to the root and the table section to Fault/Alarms).
The color indication corresponds to the alarm LED of the unit in the following way:
 Red alarm state indicates the presence of a critical alarm.
 Orange alarm state indicates the presence of a major alarm.
 Yellow alarm state indicates the presence of a minor alarm.
 Green alarm state indicates the presence of a warning.
 Gray alarm state indicates the absence of alarms.

5. Maintenance
The maintenance state shows the current maintenance state of the connected device. This
indication corresponds to the maintenance LED of the unit. A single left click on this field shows
the origin of the maintenance state (path: Board/Local/Maintenance, Tabs: Fault/Maintenance)
A yellow maintenance state indicates that a maintenance function is currently active. More
information about maintenance indication can be found in  5.6.

A3118-X642-R612-01 98 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.3 LCT+ Control area

Figure 6-13 LCT+ Areas

The (green) control area is located in the upper left corner of the work area and contains the following
dialogues.
It contains 5 tabs:
 Tree
 Connection
 User Management
 Download
 SCC FW Sync

Tree
The tree tab contains the structure of the network elements data model. This is a representation model
of all network element parameters (configurations, inventory, alarms, performance counters …). The
structure is represented as a `tree`. The tree area itself doesn’t contain any parameters but shows the
hierarchical structure of the grouped parameters.
It is possible to navigate the structure expanding and collapsing the groups with the mouse or the
cursor. Selecting a folder in the tree area changes all contents of the table area with the corresponding
parameters. The handling is very similar to the windows explorer: groups are like folders, parameters
like files.

The topmost stage of the structure contains the following groups

A3118-X642-R612-01 99 / 405
 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

 Aggregation
The aggregation is controlled by the DSLAM to which the
ACCEED 1102/04 is connected to.
The ACCEED 1102/04 has one PAF (A) which operation mode
can be configured to work in as aggregated EFM link or single
line mode.
Each of the 4 lines can be enabled or disabled individually and an
alarm threshold for attenuation and SNR margin can be set.
 Ethernet
This group contains layer 2 parameters for the local switch with
the following parameters:
- LAN, SFP ports defining user port attributes
- WAN port defining transmission port attributes
- VLAN, QoS profiles, EVC, Policing, Mirroring, Service
Qualification and Service OAM for logical tasks.
One stage below all parameters for VLAN manipulation, Port
Isolation, protocol detection and handling, link OAM, queue
definition, metering process, rate shaping and many more can be
found.
 CES IWF
This group contains circuit emulation service parameters for the
E1/Clock (TDM) and Data module slot (DMS) interfaces.

 Board
This group contains generic parameters and contains among
others the following groups:
 Alarm Configuration (Severity, Logging)
 Local (Information, Maintenance, Time Settings, Management
Access, Clocking)

Figure 6-14 ACCEED 1102/04 Tree view

To facilitate trouble shooting, alarms are displayed in the tree view as colored circles escalated
hierarchically along the path to the highest instance. The default colors match the following alarms:

red critical alarms

orange major alarms
yellow minor alarms
green warnings

A3118-X642-R612-01 100 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Connection
The connection dialogue is described in  6.2.2.

Figure 6-15 Connection dialogue

User Management
The user management dialogue permits to change the password the two local users (Administrator
and Maintenance).

The default passwords are defined in  6.2.2.

Figure 6-16 User Management dialogue

 With MCU / MCU-S / MCU-CES the passwords must be of at least 8 characters. The
empty password is only allowed if SNMP V3 is not used.

A3118-X642-R612-01 101 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Download
The download dialogue is described in  6.8

The download panel is divided in 4 functions:

 Local Download  6.8.1
 Remote Download  6.8.2

A3118-X642-R612-01 102 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.4 LCT+ View area

The (blue) view area is located in the upper right corner of the work area and contains the following
views.

Ethernet View
The Ethernet view is a representation of ACCEED 1102/04 unit. It shows a logical representation of
the desktop unit. Functional blocks and interfaces are displayed. These are colored depending on
corresponding alarms (green: warning, yellow: minor alarm, orange: major alarm, red: critical alarm).

Figure 6-17 Ethernet view

It is possible to directly jump to the corresponding management area of the tree and
 table areas (see  6.3.1 and  6.5) by clicking on the corresponding functional block or
interface.

A3118-X642-R612-01 103 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.5 LCT+ Table area

The (red) table area is located in the lower right corner of the work area and contains the network
element parameters organized in tab panels. The structure is divided into two levels.

The first level contains Fault, Configuration and Performance management. The second level breaks
down the management areas into further partitions in order to improve clarity. Empty tabs are
automatically set invisible.

A3118-X642-R612-01 104 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Figure 6-18 Table tabs

Figure 6-19 Table area example

Each line of all tables contains a symbol (see Table 1).

Go to parent directory
directory
directory with array view
Alarm
Configuration parameter (editable)
Locked configuration parameter (read-only)
Information (read-only)
Performance counter (read-only)

A3118-X642-R612-01 105 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Table 1 Table area symbols

The table area is linked to the tree area. The parameters displayed in the table panels correspond to
the data structure selected in the tree area as demonstrated by the following example:

Example
To enable Ethernet Port `P1`on the LT device:
 first select the corresponding parameter on the tree view: Ethernet/Switch Local/LAN Ports/P1
(or click on `P1` in the Ethernet view).
 then select the Configuration tab and the ACCEED 1102/04 tab
 enable Port 1
 finally click on `Apply`

Figure 6-20 Configuration example

The tree area allows grouping of parameters and easy access to them by navigating
 through the tree.

By selecting a specific branch or leave in the tree area, the corresponding subset of parameters is
displayed in the table.

A3118-X642-R612-01 106 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Fault: Alarms
The alarm table displays the alarms of the selected structure group / element. For each alarm the
path in the data structure, the alarm location, the alarm state and the alarm severity are shown.

At the bottom of the table an Alarm Filter is present. This can be used to select which alarm
priorities should be displayed. By default the filter is set to `All Alarms`.

Figure 6-21 Fault / Alarms

The following buttons are available:

- Refresh: the data in the table is reloaded from the network element.
- Alarm Log: the Alarm Log window is opened. The Alarm Log contains the last 1’000 alarms
occurred and is stored in the network element.
- Clear Alarm Log: all alarm entries of the Alarm Log stored in the network element are
deleted.

Figure 6-22 Alarm Log

The Alarm Log shows the timestamp of the Alarm change, the severity, the device where the
alarm occurred, the alarm state transition and the path in the tree area.
The Alarm Log can be locally saved as text or pdf file on the PC where the LCT+ is running.

 It is possible to configure, the alarms stored in the Alarm Log. See  11.2.2

 It is possible to change the severity of the alarms. See  11.2.1

A3118-X642-R612-01 107 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Fault: Maintenance
The Maintenance LED and Maintenance State of the LCT+ indicates, that the ACCEED 1102/04 has a
maintenance condition.
By clicking on the yellow maintenance indicator or selecting Board/Maintenance and selecting
FaultMaintenance, the reason for the maintenance condition is displayed (e.g. loop state).

Figure 6-23 Fault / Maintenance

The following locations need to be checked regarding the reason:

- Line Loop Active
Aggregation/EFM Link/[]/Lines/Slot x Port y
Aggregation/EFM Link/[]/Lines/Slot x Port y/Regenerator/Stage z
- Ethernet Port Loopback Active
Ethernet/Switch Local/… Ports/{Port}/VLAN/Ingress/Loopback
Ethernet/Switch Local/… Ports/{Port}/Loopback
Ethernet/Switch EFM-NT/[]/… Ports/{Port}/VLAN/Ingress/Loopback
Ethernet/ Switch EFM-NT/[]/… Ports/{Port}/Loopback
- Link OAM Loop Active
Ethernet/Switch Local/… Ports/{Port}/Link OAM
Ethernet/Switch EFM-NT/[]/… Ports/{Port}/Link OAM
- TDM/DMS Loop Active
CES IWF/Local/TDM/TDM1
CES IWF/Local/TDM/TDM2
CES IWF/Local/DMS/DMS1/Nx64k
 CES IWF/EFM-NT/[]/TDM/TDM1
 CES IWF/EFM-NT/[]/TDM/TDM2
CES IWF/EFM-NT/[]/DMS/DMS1/Nx64k
Note: Loopbacks are described in the following chapters
SHDSL Loopbacks  7.2.7
Ethernet Loopbacks  8.3.3.1
TDM Loopbacks  10.4.4

A3118-X642-R612-01 108 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Fault: SOAM (Loopbacks)

SOAM Loopbacks are a sort of “Ethernet Ping”. A SOAM loopback is started on a MEP; possible
targets are MEPs and MIPs in the same domain (MEG/MA). Destination is either a Unicast- [IEEE,
ITU-T] or Multicast-MAC address [ITU-T].
SOAM loopbacks are described in  9.2.2.4

Figure 6-24 Fault / SOAM

A3118-X642-R612-01 109 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Fault: Ping

Figure 6-25 Ping Settings

A3118-X642-R612-01 110 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Configuration: ACCEED 1102/04

The ACCEED 1102/04 configuration table contains all configuration and inventory parameters of
ACCEED 1102/04. The table contains both editable fields and read only fields.

Figure 6-26 Configuration example ACCEED 1102/04

Configuration parameters changed in the table are marked in blue (as shown in Figure 6-26). The
number of configuration changed in the table is displayed in the `Apply` button (in brackets).

The following buttons are available:

- Apply: the configuration changes are set in the network element.
- Cancel: the changes are discarded.
- Refresh: the data in the table is reloaded from the network element. Possible configuration
changes which have not yet been applied are discarded.
- Set Default: all parameters in the table are set to default. These values are only changed in
the LCT+, to set them in the network element the “Apply” button must be clicked.

A3118-X642-R612-01 111 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Configuration: Summary

The summary configuration table contains a summary of all configuration changes which have not
yet been applied. This allows checking the configuration before it is transferred to the network
element. In particular the summary table can be used together with the `Load Configuration`
function described in  6.6.2. After the configuration has been loaded from a file, the summary
table displays all configuration changes stored in the file. It is easy to get direct access to the
changed parameters in the summary table.
Plausibility Conflicts are shown in the color orange. As long as the conflicts are not resolved
manually, the configuration cannot be applied to the unit.
These plausibility conflicts may also occur, if a new NT is connected that differs from the port
scheme stored in the database. Typically this happens if e.g. an ACCEED 1416 LT was connected
to an ACCEED 1416 and is now connected to an ACCEED 1104 instead (as a replacement). This
conflict can be resolved by clicking on “Match Capabilities”.

Every time the “Apply” button is clicked, the configuration is written to the device and the summary
table is deleted.

Figure 6-27 Configuration / Summary

The following buttons are available:

- Apply: the configuration changes are set in the network element.
- Cancel: the changes are discarded.
- Match Capabilities: conflicting capabilities of LT and NT are tried to be matched

A3118-X642-R612-01 112 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Performance: Line Parameters

The Line Parameters table contains the SHDSL line parameters:

- loop attenuation
- power back off readout
- SNR margin

These parameters are available for each single SHDSL port of the link, i.e. on every SHDSL line
the parameters are measured on both the LT and NT side.
Aggregation/EFM Link/[A]/Lines

Figure 6-28 Performance / Line Parameters

The following button is available:

- Refresh: the data in the table is reloaded from the network element.
- Overview: opens this table in an own window.
- Save As…: opens Save dialog to save table as “.csv” File (character separated values).
The separator is a semicolon.

The option boxes “SNR Margin”, “Loop Attenuation” and “Power Backoff” changes the parameter
display.

A3118-X642-R612-01 113 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Performance: Error Counters

The Error Counters table contains SHDSL CRC6 error counter statistics (see  7.2.9).
Aggregation/EFM Link/[A]/Lines

Figure 6-29 Performance / Error Counters

The following parameters are located at the bottom of the table:

- Interval: data set interval (current, current -1 …). ACCEED features 32 x 15 minutes interval
counters and 7 x 24 hours interval counters for each SHDSL port in the EFM Link (including
NT and regenerators).
- Type: type of error counter (15 minutes or 24 hours counters).

The following buttons are available:

- Refresh: the data in the table is reloaded from the network element.
- Reset: all counters are reset to zero.

A3118-X642-R612-01 114 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Performance: BER Measurements

The BER Measurements table contains the interface to the embedded BER measurement test
facility for the ACCEED 1102/04 SHDSL lines. An individual Bit Error Rate Test generator and
monitor is available for each SHDSL line.
Aggregation/EFM Link/[A]/Lines/Slot xPort y

To perform the BER Test a PRBS (Pseudo Random Bit Sequence) is transmitted over
 the SHDSL line, thus during test execution the line is not available for payload
transmission.

If the SHDSL line on which the BERT is carried out belongs to an established EFM-Link,
 this line temporarily taken out of the aggregation group. A Partial Aggregation Loss Alarm
is raised and remains active for the entire test duration.

To perform the test, a loop-back is automatically activated on the NT side for the duration of the
test and a BER generator / monitor are activated on the LT side as shown in

Figure 6-30.

To test a particular line segment, the loop-back can manually be activated on a regenerator.
The table contains control buttons to start / abort the measurement as well as the measurement
results.

A3118-X642-R612-01 115 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Figure 6-30 Performance / BER Measurement

The following parameter is located at the bottom of the table:

- Interval: Test duration interval. The following options are available: 1 minute, 10 minutes, 1
hour and 24 hours.
The following buttons are available:
- Start: BER measurement is started. While
BERT is service affecting a warning window
pops up as a reminder. It is possible to
deactivate this confirmation window directly or in
the LCT+ Menu
/Options/Preferences/Confirmation/Start BERT
- Abort: the BER measurement is stopped (current results are displayed)
- Refresh: measurement results are reloaded from the network element and displayed

A3118-X642-R612-01 116 / 405

ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Performance: Statistics

The following counter groups are available with ACCEED 1102/04

 Port counters: RMON (and HC-RMON) statistics on MAC level
 Service counters: Packet and Byte counters of ingress and egress port services
 EVC counters: Packet and Byte counters of EVC services
 Bandwidth profile counters: Packets and Byte counters of metering entities
 Tx queue counters: Packet (transmitted and dropped) counters of port transmit queues

For more information please refer to  8.9

Performance: Utilization

Utilization provides information on data rates and utilization of a port or service and displays it in a
graph.

For more information please refer to  8.10.7

Performance: Service Activation Testing (SAT)

The ACCEED built in Service Activation Testing (SAT) feature allows evaluating layer 2 key
performance figures for a service that is planned to be implemented.
For more information please refer to  9.3

Performance: Circuit Emulation Service (CES)

For more information please refer to  10.4.2

Search

A3118-X642-R612-01 117 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.6 LCT function blocks

Save Configuration
The command `Save configuration …` allows to save the configuration (or part of it) of a network element
in a *.ucx file (xml file format).
The command is also available via the control sequence (Ctrl+S).

This command opens the Save Configuration window, which permits to define which parameters will be
stored in the file. The window is vertically divided in two parts:
 The left part of the window corresponds to the current configuration of the network element. The
window contains the data structure of the selected unit in a tree format (the same format used in the
tree area). A green checkmark on a configuration parameter or a configuration node indicates that
the configuration parameter respectively the configuration node will be saved into the configuration
file.
 The right part of the window corresponds to the content of the configuration file. The window
contains the data structure in a tree format (the same format used in the tree area). The configuration
parameters / nodes marked with a green checkmark will be saved into the configuration file and the
grayed out configuration parameters / nodes will not. Green Square ( ) marked parameters /
nodes indicate partial configuration.

Figure 6-31 Save configuration window

Each single configuration parameter / node of the network element can be selected and added to the
configuration file by clicking on the right arrow button ().

Each single configuration parameter / node of the configuration file can be selected and removed by
clicking on the right left arrow button ().

A3118-X642-R612-01 118 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

 To save the entire configuration of the network element, select the upper most directory
(e.g. `ACCEED 1102/04` and click on the right arrow button ().
It is also possible to add / remove items by right clicking on parameters:

The creation of the configuration file can be aborted at any time (`Cancel` button).

The choice of parameters to be transferred to the configuration file can be reset with the `Reset`
button.

The file is created by clicking on the `Save` button, opening the save file dialog. To complete the
creation of the configuration file, a name must be entered in the file name field. Optionally the store
path may be changed.

Figure 6-32 Save window

A3118-X642-R612-01 119 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Load Configuration
The command `Load configuration` allows to transfer the configurations stored in a *.ucx file to a
network element.
The command is also available via the control sequence (Ctrl+L)

First the configuration file needs to be opened. It can be selected by double clicking in the open file
dialog.

Figure 6-33 Open window

Once the configuration file has been selected, the Load Configuration window is opened. This panel
permits to define which parameters of the configuration file will be transferred to the network element.
The window is vertically divided in two parts:
 The left part of the window corresponds to the configuration data stored in the configuration file. The
window contains the data structure of the configuration file in a tree format (the same format used
in the tree area). A green checkmark on a configuration parameter or a configuration node indicates
that the configuration parameter respectively the configuration node will be transferred to the
network element.
 The right part of the window corresponds to the network element. The window contains the data
structure in a tree format (the same format used in the tree area). The configuration parameters /
nodes marked with a green checkmark will be transferred to the configuration file and the grayed
out configurations / nodes remains unchanged.

A3118-X642-R612-01 120 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

110x_End ────────────────────────────────────────────────────────────────────────────────┘
Figure 6-34 Load configuration window

The transfer to the network element can be aborted at any time (`Cancel` button).

The choice of parameters to be transferred to the network element can be reset with the `Reset`
button.

The transfer is initiated by clicking on the `OK` button.

Preview Mode
This command toggles between `Online Mode` (display of units physically connected to LCT+) and
`Preview Mode` (display of a generic virtual line model being under control of the LCT+).
The command is also available via the control sequence (Ctrl+P)

The ACCEED 1102/04 unit is a standalone application being connected to a DSLAM and therefore no
additional ACCEED units are displayed in the preview mode.

The Preview mode is useful to configure devices, which are not yet physically available (for instance to
configure the NT, before it is connected to the LT). This does not apply to the ACCEED 1102/04 unit.

Preferences
This command opens a popup window containing LCT+ preferences and information.
The command is also available as control sequence (Ctrl+E)

The following preferences are available:

A3118-X642-R612-01 121 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

 Connection preferences
- IP Address History
This option allows defining how many IP addresses used to connect to network elements should
be remembered by the LCT+. This avoids annoying re-typing of IP addresses.
The range of remembered addresses goes from 3 up to 15.
The address history can be cleared pressing the `Clear History` button.

Figure 6-35 Connection option

 Confirmation
- Clear Alarm Log
- MAC Table Flush
- Show prohibited parameters in ‘Set To Default’
- Start BERT
- Match Capabilities
- Save MCU-S/MCU-CES Switch Configuration

Figure 6-36 Confirmation options

Some LCT+ operations result in deleting data without any `undo` possibility. These operations therefore
generate popup warnings. The command is only executed once the user confirms the intention to
proceed.

Figure 6-37 Alarm log clear warning

A3118-X642-R612-01 122 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Since these warnings may get annoying for some users, these can be disabled in the `Confirmation`
option dialogue.
Each single warning can be individually disabled.

 Logging

Figure 6-38 Logging options

- Enable Trap Log
`Traps` are spontaneous messages generated by the network element and sent to the
management systems (e.g. AccessIntegrator) to notify about a status change (e.g. alarm state
or performance data ready to be retrieved).

The command `Trap Log` enable / disable adds the tab “Tap Log” to display all generated
traps by the network element in the table view since last login.

The Trap Log is displayed in the table view and can be deleted (`Clear` button) or saved as a
*.csv file (`Save As …` button).

Figure 6-39 Trap Log example

A3118-X642-R612-01 123 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

- LCT+ Log
The LCT+ Log is a system log file containing a trace of the information exchanged between
LCT+ and the network elements. This file has debugging purpose and can be used to analyze
management sessions.
By default the file is located on the user application data directory. A different location can be
defined.

 Export

Figure 6-40 Export

This preference menu includes all pdf export settings:

- Page Size Paper format A4 or Letter
- Page Orientation Paper format Portrait or Landscape
- Font Size 6, 8, 10, 11, 12, 14 or 16 pixel

A3118-X642-R612-01 124 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7 CLI introduction

The Command Line Interface (CLI) is a standard interface to access, monitor and configure the
ACCEED 1102/04. It is text based and mainly used for scripting applications. The look and feel is
designed to be equal to the LCT+.

CLI Modes
The CLI groups its commands to three different modes, to separate tasks. These modes are “Exec“,
“Privileged (Exec)“ and “Configuration“. Each mode supports exclusive commands, which cannot be
executed in the other modes. The CLI Prompt signals the mode entered.
The following table describes the modes and prompts.

Mode User Prompt Description

A small command set to display general system

Exec M ACCEED1102/04> information. For this mode maintenance rights
are sufficient.

Same command set as Exec mode and

Privileged ACCEED1102/04#
A additional write access commands, which needs
(Exec)
administration rights and the write token.

Command set to configure parameters and

Configuration ACCEED1102/04(config)# navigate in the ACCEED tree. By entering the
A
(Top level) configuration mode, the write token is requested.
Write access to parameters is now possible.

Configuration ACCEED1102/04(config- See Configuration mode. Additionally the actual

A abc)#
(Subdir) subdirectory name is displayed

See Configuration mode. But by entering the

Configuration
ACCEED1102/04(RO-config)# configuration mode, the requested write token
(Read-Only, A
was not free. So only read access to parameters
Top level)
is possible.

Configuration ACCEED1102/04(RO-config- See Configuration read only mode. Additionally

(Read-Only, A abc)# the actual subdirectory name is displayed
Subdir)

CLI Control

6.7.2.1 Command History

The ACCEED CLI supports a history of the last commands executed. By pressing cursor up [ ↑ ] and
cursor down [ ↓ ] the navigation through the latests commands is possible.
Alternate to cursor keys, control combinations are supported:
 Cursor up [ ↑ ]  <Ctrl> + P
 Cursor down [ ↓ ]  <Ctrl> + N

A3118-X642-R612-01 125 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.2.2 Command Line Editing

The following table shows all supported shortcuts to edit the command line.
Shortcut Alternate Key Function

<Ctrl> + B Cursor left [ ← ] Moves cursor one character backward

<Ctrl> + F Cursor right [ → ] Moves cursor one character forward
<Ctrl> + A --- Moves cursor to begin of line
<Ctrl> + E --- Moves cursor to end of line
<Tab> --- File and command auto completion
<Ctrl> + H <Backspace> Deletes one character left of cursor and moves the cursor one left
<Ctrl> + D --- Deletes the character the cursor is on
<Ctrl> + K --- Deletes all characters starting from cursor to end of line
<Ctrl> + X --- Deletes all characters from begin of line to character left of cursor
<Ctrl> + W --- Deletes all characters left of cursor to next space leftwards
<Ctrl> + U --- Deletes all characters on the line
<Ctrl> + P Cursor up [↑] Scroll backward through command history
<Ctrl> + N Cursor down [ ↓ ] Scroll forward through command history
<Ctrl> + C --- Breaks actual command line and changes to a new empty line
<Ctrl> + Z --- Leaves configuration mode to privileged mode.

CLI Access
The CLI can be accessed via the following paths:
 Serial interface (115200 baud, data=8, no parity, stop=1)
 Telnet
 SSH V2 (Secure Shell)
 Indirect via MCU-S and MCU-CES

6.7.3.1 CLI Access via serial interface

Start the software Hyper Terminal.
Set the serial communication
parameters to the following settings:

Press Connect

Hit the Key <Enter>. The ACCEED CLI starts

loading its interface

Loading ACCEED CLI...........................

Entering character mode
Escape character is '^]'.

Device: ACCEED 1416

Part Number: S3118-D644-E126-E3
Mode: LT
FW ID: 644
FW Version: 1.80
HW Options: 4wp (Eth+RPS180V+SyncE)
Last Configuration Change: 30.09.2013 - 14:08:07 - UTC

Username:

A3118-X642-R612-01 126 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.3.2 CLI Access via telnet or SSH

Start on a command prompt (e.g. DOS box or shell) the required communication software telnet or
secure shell (SSH) with the Management IP of the ACCEED 1102/04. After the TCP/IP connection
(and the encryption) is established the ACCEED CLI starts up and some basic info is displayed.
C:\>Telnet 10.0.0.1

Loading ACCEED CLI.....................

Device: ACCEED 1416

Part Number: S3118-D644-E126-E3 Example
Mode: LT
FW ID: 644 output of an
FW Version: 1.80 ACCEED
HW Options: 4wp (Eth+RPS180V+SyncE) 1416
Last Configuration Change: 30.09.2013 - 14:18:24 - UTC

Username:

Enter Username , e.g. “Administrator”.

Enter Password (is the Password set for the ACCEED 1102/04). Default for Administrator is
“UlafPAdm”
Username: Administrator
Password:
ACCEED1102/04>

Other usernames than “Administrator” or “Maintenance” may be used if a remote authentication service
such as RADIUS is enabled ( 11.3.5.1).

6.7.3.3 CLI Access via MCU-S and MCU-CES

Alternate to direct access the ACCEED 1102/04 via inband or outband Management, the central
management card can be used to forward the TCP/IP connection. This access path is available for
MCU-S and MCU-CES. It is restricted to the subrack or compact shelf of the management card. RBUS
interface for cascading subracks or compact shelves is not supported.

Start on a command prompt (e.g. DOS box or shell) the required communication software telnet or
secure shell (SSH) with the Management IP of the MCU-S/CES. After the TCP/IP connection (and the
encryption) is established the MCU-S/CES CLI starts up. Enter User Administrator and the
administrator password of the MCU-S/CES (default: UlafPAdm).
(ULAF+ MCU Switching)
User:Administrator
Password:********
(ULAF+ MCU Switching) >

Show all devices inside the subrack that are available for CLI connections:
(ULAF+ MCU Switching) >connect info

Slot 15: ACCEED 1416 LT - FW-ID: 644 - FW: 1.80

Slot 16: ACCEED 1416 LT - FW-ID: 644 - FW: 1.80

(ULAF+ MCU Switching) >

Connect to a slot in the info list:

(ULAF+ MCU Switching) > connect slot 16

(ULAF+ MCU Switching) >

Loading ACCEED CLI......................

Device: ACCEED 1416

Part Number: S3118-D644-E126-E3
Mode: LT
FW ID: 644

A3118-X642-R612-01 127 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

FW Version: 1.80
HW Options: 4wp (Eth+G703+RPS180V+SyncE)
Last Configuration Change: 30.09.2013 - 14:22:10 - UTC

ACCEED1416>

Token
Thus no conflict with other CLI or LCT+ sessions may occur a write token mechanism is implemented.
The ACCEED Firmware is the owner of the token and gives it to the first application requesting it. The
application must release the token, when it has finished its tasks. Here is an overview how the
components of the ULAF+ Management react:

Software Catch Token Release Token

LCT+ When connecting to an ACCEED When disconnecting of an ACCEED
DwlMgr While software download and reboot When finished with these tasks
When the first command is used that When exiting the CLI session on the
CLI Priviledge
need write access ACCEED
When exiting the CLI session on the
CLI Configure When entering the mode
ACCEED

If the write token is requested but not available the following Error message is printed:

ACCEED1416# set session-timeout telnet 60

%_Token not acquired
ACCEED1416#

When entering the configuration mode the write token is requested. If it is not available it enters with
read-only rights. These rights are signaled in the command prompt

Write Token available Write token not available

ACCEED1416# configure terminal ACCEED1416# configure terminal
ACCEED1416(config)# ACCEED1416(RO-config)#

While in configuration mode the CLI tries to catch the token anytime. So if an application like LCT+
releases the write token, the CLI captures the token instantly and is able to perform write actions with
additional commands or mode changes.

User Management
The primary User for login can be Administrator or Maintenance. The Maintenance user is restricted to
the Exec level.

In direct Management access to ACCEED 1102/04:

 Change to privileged level with Administrator password possible for Maintenance Users
 Change of Administrator and Maintenance password possible

If the Management connection is via MCU-S/CES:

 Maintenance Users cannot change their policy
 Local passwords of Administrator and Maintenance cannot be changed

A3118-X642-R612-01 128 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

CLI Prompt
The CLI Prompt can be configured individually at Board\Local\Management Access\CLI\Prompt

The Prompt has up to 200 characters. The first 30 characters are displayed.

CLI Navigation

The ACCEED is based on data models to configure any of the parameters. This structure is equal to
the structure of the LCT+. The navigation paths are the same as are the names of the Parameters.
Please note that the Spaces in the Names of LCT+ parameters are replaced by hyphens, e.g. “Low
Bandwidth Alarm Threshold” = Low-Bandwidth-Alarm-Threshold.
To enter the Configuration mode (Navigation Tree)

ACCEED1102/04# configure terminal

ACCEED1102/04(config)#

The config mode is shown in the prompt with a “(config)” suffix. Get help of the available commands
and parameters by typing “?”. It will create the following output:

ACCEED1102/04(config)# ?
Configure commands:
default Set all parameters in this folder to default
detail Display parameters in this folder
exit Goto to parent folder / Exit from configuration mode
help Description of the interactive help system
logout Terminate current CLI session
match-capabilities Match capabilities on this device
ping Ping a remote host
preview-mode Enable or disable the preview mode
pwdp Print working data model path
root Navigate to the root of the data model
show Show running system information
==============================================================================
/
------------------------------------------------------------------------------
Aggregation / S3118-D644-E126
Ethernet / S3118-D644-E126
CES-IWF / S3118-D644-E126
Board / S3118-D644-E126

The first section shows all commands that are available (ending by the ========= border). The
second section divided in 2-4 parts separated by ------------------.
The first part shows the actual navigation path, e.g. /Aggregation/EFM-Link/[A]
The second shows the subdirectories at this navigation path.
The third shows the available actions at this navigation path. It equals the location dependent Buttons in
the LCT+.

The fourth shows the available Parameters and its description.

Only parts with content are displayed.

A3118-X642-R612-01 129 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Navigate through the tree by typing the Names of the subdirectories and press enter. With the <TAB>
you can auto-complete the Names. The successful change of the path is shown in the prompt by
displaying the new subdirectory in the prompt directly behind the config suffix. The full path of the actual
position in the tree can be printed by using the ‘pwdp’ command.

ACCEED1102/04(config)# Ethernet
ACCEED1102/04(config-Ethernet)# Switch-Local
ACCEED1102/04(config-Switch-Local)# LAN-Ports 1
ACCEED1102/04(config-LAN-Ports/P1)# VLAN
ACCEED1102/04(config-VLAN)# Ingress

ACCEED1102/04(config-Ingress)# pwdp
/Ethernet/Switch-Local/LAN-Ports/P1/VLAN/Ingress

If parameters of a virtual device are displayed, the status [preview] is added to the prompt:

ACCEED1102/04(config)# Ethernet
ACCEED1102/04(config-Ethernet)# Switch-EFM-NT 2
ACCEED1102/04(config-Switch-EFM-NT/[B])[preview]#

This mode equals the preview mode in the LCT+. Its use is to pre-configure remote devices before
attaching them to the network.

The command “exit” moves to the parent directory and in case of the root, it leaves the configure mode.
ACCEED1102/04(config-Switch-EFM-NT/[B])[preview]# exit
ACCEED1102/04(config-Ethernet)# exit
ACCEED1102/04(config)# exit
ACCEED1102/04#

The command “root” moves to the root directory.

ACCEED1102/04(config-Switch-EFM-NT/[B])[preview]# root
ACCEED1102/04(config)#

The following example shows all available sections and parts. The second column of this tabular view is
used for detailed description or attributes. In case of subdirectories it contains “/”, in case of Actions the
signal word “Action”, in case of Parameters the Access rights (RW = modifiable, RO = Read only).

ACCEED1102/04(config)# Ethernet
ACCEED1102/04(config-Ethernet)# Switch-Local
ACCEED1102/04(config-Switch-Local)# ?
Configure commands:
default Set all parameters in this folder to default
detail Display parameters in this folder
CLI commands

exit Goto to parent folder / Exit from configuration mode

help Description of the interactive help system
logout Terminate current CLI session
match-capabilities Match capabilities on this device
ping Ping a remote host
preview-mode Enable or disable the preview mode
pwdp Print working data model path
root Navigate to the root of the data model
show Show running system information
==============================================================================
/Ethernet/Switch-Local Path
------------------------------------------------------------------------------
LAN-Ports /
SFP-Ports /
BPL-Ports /
WAN-Ports /
VLAN / S3118-D644-E126
Folders

QoS / S3118-D644-E126
EVC / S3118-D644-E126
Protection / S3118-D644-E126
Policing / S3118-D644-E126
Mirroring / S3118-D644-E126
SAT / S3118-D644-E126
SOAM / S3118-D644-E126

A3118-X642-R612-01 130 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

------------------------------------------------------------------------------
MAC-Table-Flush Action: Flushes all entries in the MAC table Actions
------------------------------------------------------------------------------
VLAN-Mode RW: Defines the VLAN mode of the switch
Learning-Mode RW: Defines the learning mode of the MAC table
MAC-Table-Aging-Time RW: Timeout for MAC table entries
Number-Of-Allowed-MAC-Addresses RW: Number of allowed MAC addresses in the ...
Maximum-Frame-Size RW: Defines the maximum receive and transmit size...

Parameters
LAN-Ports-Power-Save RW: Automatically reduces the signal amplitude (f...
Random-Early-Discard-(RED) RW: Enables random tail-dropping of frames to av...
Active-LFP-Groups RO: State of all LFP groups
RMON-Counters RO: Defines the counting mode of port RMON counters
Transmit-Queue-Counters RW: Defines the counting mode of port transmit qu...
Ingress-Policy-Counters RW: Defines the counting mode of ingress policy c...
Egress-Policy-Counters RW: Defines the counting mode of egress policy co...
Ingress-Metering-Counters RW: Defines the counting mode of ingress metering...
Egress-Metering-Counters RW: Defines the counting mode of egress metering ...

ACCEED1102/04(config-Switch-Local)#

Viewing Parameters

The command “detail” returns all Parameter Names at the current Navigation Path location and their
values

ACCEED1102/04(config-Switch-Local)#
ACCEED1102/04(config-Switch-Local)# detail
VLAN-Mode Unaware
Learning-Mode Automatic
MAC-Table-Aging-Time 300-s
Number-Of-Allowed-MAC-Addresses 16
Maximum-Frame-Size 1522-Bytes
LAN-Ports-Power-Save false
Random-Early-Discard-(RED) false
Active-LFP-Groups
LFP-Group-A false
LFP-Group-B false
LFP-Group-C false
LFP-Group-D false
LFP-Group-E false
RMON-Counters Bytes-And-Packets
Transmit-Queue-Counters Bytes-And-Packets
Ingress-Policy-Counters Bytes-And-Packets
Egress-Policy-Counters Disabled
Ingress-Metering-Counters Bytes
Egress-Metering-Counters Bytes
ACCEED1102/04(config-Switch-Local)#

Setting Parameters

There are different types of parameters. They are Strings, Integers, Enums and Bit-Arrays.
To find out which Parameters are configurable (e.g. number of characters, Integer range, List of enum
items and Bit patterns) type the parameter name and use the “?”. The created printout shows the

A3118-X642-R612-01 131 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

available parameter commands (default and properties) and below the “-------------------“ line, the
possible input for the selected parameter.

ACCEED1102/04(config-Information)# Description ?
default Reset parameter to default value
properties Display parameter properties String
------------------------------------------------------------------------------
<0..32 Characters> Enter string in quotes

ACCEED1102/04(config-LAN-Ports/P1)# Ingress-Rate-Limit ?
default Reset parameter to default value
properties Display parameter properties Integer
------------------------------------------------------------------------------
<64..100000> Enter an integer value

ACCEED1102/04(config-Switch-Local)# LAN-Ports-Power-Save ?
default Reset parameter to default value
properties Display parameter properties Boolean
------------------------------------------------------------------------------
<true / false> Enter a boolean value

ACCEED1102/04(config-Switch-Local)# VLAN-Mode ?
default Reset parameter to default value
properties Display parameter properties
Lists
------------------------------------------------------------------------------
Unaware
Aware

ACCEED1102/04(config-Inband)# Ports ?
default Reset parameter to default value
properties Display parameter properties
Bit-Arrays
------------------------------------------------------------------------------
P1
P3
BPL1
SFP1
WAN1
WAN2
WAN3
WAN4

The parameter command “default” sets this parameter to the factory default.
The parameter command “properties” or the parameter name without a set parameter shows the
parameter name and its description, the current value of it, the default value and if available the valid
Range.
ACCEED1102/04(config-Information)# Description String
Description Device description
------------------------------------------------------------------------------
Current value "ULAF+ ACCEED 1102/04"
Default value "ULAF+ ACCEED 1102/04"
Range 0..32 Characters

ACCEED1416(config-LAN-Ports/P1)# Ingress-Rate-Limit Integer

Description Ingress rate limit
------------------------------------------------------------------------------
Current value 1000 kbit/s
Default value 1000 kbit/s
Range 64..100000 kbit/s

ACCEED1416(config-Switch-Local)# LAN-Ports-Power-Save
Description Boolean
Automatically reduces the signal amplitude (for cables up to 30m)
------------------------------------------------------------------------------
Current value false
Default value false

ACCEED1416(config-Switch-Local)# VLAN-Mode
Description Defines the VLAN mode of the switch Lists
------------------------------------------------------------------------------
Current value Aware
Default value Unaware

A3118-X642-R612-01 132 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

ACCEED1102/04(config-Inband)# Ports properties

Description Ports enabled for inband management
Set to default Prohibited Bit-Arrays
------------------------------------------------------------------------------
Value Current Default
P1 false true
P3 false true
BPL1 false true
SFP1 true true
WAN1 false true
WAN2 false true
WAN3 false true
WAN4 false true

ACCEED1416(config-Inband)# IP-Address
Description Configured IP address for inband management interface
Set to default Prohibited
------------------------------------------------------------------------------
Current value 10.128.3.99
Default value 10.0.0.1

ACCEED1416(config-Packet)# Destination-MAC-Address
Description MAC address of the remote circuit emulation function
------------------------------------------------------------------------------
Current value 00:1A:D0:00:00:11
Default value 00:00:00:00:00:00

To set a parameter the parameter name followed by the new parameter is used.

ACCEED1102/04(config-Switch-Local)# VLAN-Mode Unaware

ACCEED1102/04(config-Switch-Local)# VLAN-Mode Aware

CLI configuration commands

The following commands are available depending on the operation mode:

Exec Priviledged Navigation Description

clear Clear the configuration or log files  6.7.10.1
configure Enter configuration mode  6.7.10.2
copy Load or save configuration files  6.7.10.3
default Set all parameters in this folder to defaul  6.7.10.4
delete Delete an existing config file  6.7.10.5
detail Display parameters in this folder  6.7.10.6
disable Turn off privileged commands  6.7.10.7
enable Turn on privileged commands  6.7.10.8
erase Erase all files from flash  6.7.10.9
exit exit exit Goto to parent folder / Exit  6.7.10.10
fwsync Firmware sync command  6.7.10.11
fwupdate Firmware download command  6.7.10.12
help help help Description of the interactive help system  6.7.10.13
logout logout logout Terminate current CLI session  6.7.10.14
match-capabilities Match capabilities on this device  6.7.10.15
more Display the content of a file  6.7.10.16
ping ping ping Ping a remote host  6.7.10.17
preview-mode Enable or disable the preview mode  6.7.10.18
pwdp Print working data model path  6.7.10.19
reboot Reboot the system  6.7.10.20
rename Rename an existing config file  6.7.10.21
restore Restore configuration…  6.7.10.22
root Navigate to the root of the data model  6.7.10.23
set set Set a config value  6.7.10.24
show show show Show running system information  6.7.11

A3118-X642-R612-01 133 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.1 Clear
Syntax: clear <list>
Description: Clear the configuration or log files
Options:
ACCEED1102/04# clear ?
alarmlog Clear the alarm log
configuration Clear the configuration
Note: In case of ‘clear configuration’ a confirmation is asked. No reset of the board is
initiated.
ACCEED1102/04# clear configuration
Are you sure? [y|n]: y

6.7.10.2 Configure
Syntax: configure terminal
Description: Enter the configuration mode
Output:
ACCEED1102/04# configure terminal
ACCEED1102/04(config)#
Note: In case of write token unavailable, enter configuration mode read-only
ACCEED1102/04# configure terminal
ACCEED1102/04(RO-config)#

6.7.10.3 Copy
Syntax: copy <source> <destination>
Description: Copy the running-configuration to or from a server
Options: sources
ACCEED1102/04# copy ?
flash:104M_16wp_one_customer.txt Copy from file
flash:22M_4wp_one_customer.txt Copy from file
flash:60M_4wp_one_customer.txt Copy from file
flash:6M_1wp_four_customers.txt Copy from file
help Copy command help
running-config Copy the running-config
scp: Copy from server with SCP (scp:192.168.1.1:/tmp/file.txt)
tftp: Copy from TFTP server (tftp:192.168.1.1/tmp/file.txt)
Options: destinations dependent of the source type
ACCEED1102/04# copy running-config ?
flash: To flash (flash:file.txt)
scp: To server with SCP (scp:192.168.1.1:/tmp/file.txt)
tftp: To TFTP server (tftp:192.168.1.1/tmp/file.txt)

ACCEED1102/04# copy flash:104M_16wp_one_customer.txt ?

running-config To running-config
scp: To server with SCP (scp:192.168.1.1:/tmp/file.txt)
tftp: To TFTP server (tftp:192.168.1.1/tmp/file.txt)

ACCEED1102/04# copy tftp:test ?

flash: To flash (flash:file.txt)
running-config To running-config
Output:
ACCEED1102/04# copy running-config flash:60M_4wp_one_customer.txt
Creating device configuration file......

6.7.10.4 Default
Syntax: default [recursive]
Description: set all parameters in this folder to default values. In case of option “recursive”, all
parameters in all subfolders below this folder are recursively set to default
Output:
ACCEED1102/04(config-Switch-Local)# default
ACCEED1102/04(config-Switch-Local)#
Option: recursive
ACCEED1102/04(config-Switch-Local)# default recursive
Setting parameter values to default.
ACCEED1102/04(config-Switch-Local)#

A3118-X642-R612-01 134 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.5 Delete
Syntax: delete <source>
Description: Delete an existing configuration file
Options:
ACCEED1102/04# delete ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Note: Each deletion action needs to be confirmed
ACCEED1102/04# delete flash:test.abc
Are you sure? [y|n]: Y

6.7.10.6 Detail
Syntax: detail
Description: display all parameters in this folder and their values
Output:
ACCEED1102/04(config-Board)# detail
Last-Configuration-Change 17.01.2013 - 13:38:46
Sample-Device false

ACCEED1102/04(config-Board)#

6.7.10.7 Disable
Syntax: disable
Description: return to exec mode
Output:
ACCEED1102/04# disable
ACCEED1102/04>

6.7.10.8 Enable
Syntax: enable
Description: Enter the privileged mode
Output:
ACCEED1102/04> enable
ACCEED1102/04#

6.7.10.9 Erase
Syntax: erase <source>
Description: Erase all files from flash
Options:
ACCEED1102/04# erase ?
flash: Erase the contents of flash:
Note: erase action needs to be confirmed
ACCEED1102/04# erase flash:
Are you sure? [y|n]: y

6.7.10.10 Exit
Syntax: exit
Description: In privileged mode: Terminate CLI session
In navigation mode root: return to privileged mode
In navigation mode folder: goto parent folder
Output:
ACCEED1102/04(config-Board)# exit
ACCEED1102/04(config)# exit
ACCEED1102/04# exit

Lost connection to host.

A3118-X642-R612-01 135 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

C:\>

6.7.10.11 Fwsync
Not applicable
6.7.10.12 Fwupdate
Syntax: fwupdate <source> [target]
Description: Start local firmware update.
Distribute passive LT Firmware to local-array’s passive firmware bank.
Distribute passive NT Firmware to remote-array-<PAF>’s passive firmware bank.
Options:
ACCEED1102/04# fwupdate ?
abort Abort a currently running remote download
bank:active Remote download source bank:active
bank:passive Remote download source bank:passive
help Fwupdate command help
info Display the version information
scp: Download image with scp
status Show state of currently running updates
tftp: Download image from TFTP address
Output:
ACCEED1102/04# fwupdate tftp:10.128.3.65/ACCEED1102/04/Rel_1.80/ACCEED_1102/04_644_01.80.tgz
Downloading firmware ...........
Firmware download complete
Writing firmware to passive bank.........................................
Written firmware to flash
Awaiting update..........
Done.
ACCEED1102/04#
Output:
ACCEED1102/04# fwupdate info
Active ID: 644/ACCEED 1102/04
Active Version: 1.70
Passive ID: 644/ACCEED 1102/04
Passive Version: 1.80

Output:
ACCEED1102/04# fwupdate bank:active ?
shdsl-nt-port-1 Remote download destination shdsl-nt-port-1
shdsl-nt-port-2 Remote download destination shdsl-nt-port-2
shdsl-nt-port-3 Remote download destination shdsl-nt-port-3
shdsl-nt-port-4 Remote download destination shdsl-nt-port-4
efm-nt-a Remote download destination efm-nt-a
scc-address-12 Remote download destination scc-address-12

ACCEED1102/04# fwupdate bank:passive efm-nt-a

Remote download started: bank:passive -> efm-nt-a
ACCEED1102/04# fwupdate status
Remote update running
target: efm-nt-a
state: Erasing flash
transmitted blocks: 0
ACCEED1102/04# fwupdate status
Remote update running
target: efm-nt-a
state: Running
transmitted blocks: 262
ACCEED1102/04#

A3118-X642-R612-01 136 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.13 Help
Syntax: help
Output:
ACCEED1102/04# help
Please use '?' instead of the keyword 'help'.
There are two possible usages:
a) Show the available commands that start with the already entered
characters e.g. 'c?'
b) Show all possible commands with a parameter description on the
current level e.g. 'show ?'

6.7.10.14 Logout
Syntax: logout
Description: Terminate CLI session
Output:
ACCEED1102/04# logout

Lost connection to host.

C:\>

6.7.10.15 Match-capabilities
Syntax: match-capabilities
Description: Match the capabilities of this device
ACCEED1102/04# match-capabilities
Match capabilities......
ACCEED1102/04#

6.7.10.16 More
Syntax: more <file>
Description: display the content of the selected file
Options:
ACCEED1102/04# more ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Output:
ACCEED1416# more flash:22M_4wp_one_customer.txt
! Current Configuration
! Device: ACCEED 1416
! Part Number: S3118-D644-E126-05
! Mode: LT
! FW ID: 644
! FW Version: 1.80
! HW Options: 4wp (Eth+RPS180V+SyncE)
! Last Configuration Change: 15.01.2013 - 15:51:46 - UTC
!
root
Aggregation
EFM-Link 1
Remote-PAF Slot-1-PAF-A
!
.
.
.
!
root
Board
EFM-NT 4
Management-Access
Inband
Ports P4 false
IP-Configuration Static
ACCEED1416#

A3118-X642-R612-01 137 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.17 Ping
Syntax: ping <ip>
Description: ping a remote host
Options:
ACCEED1102/04# ping ?
xyz.xyz.xyz.xyz Enter a dot separated IP address
Output:
ACCEED1102/04# ping 10.0.0.199
PING 10.0.0.199 (10.0.0.199): 56 data bytes
64 bytes from 10.0.0.199: seq=0 ttl=255 time=0.673 ms

--- 10.0.0.199 ping statistics ---

1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.673/0.673/0.673 ms
ACCEED1102/04#

6.7.10.18 Preview
Syntax: preview-mode [enable/disable]
Description: show status of preview mode or set it
Options:
ACCEED1102/04(config)# preview-mode ?
disable Disable the preview mode
enable Enable the preview mode
Output:
ACCEED1102/04(config)# preview-mode
Preview mode is enabled
ACCEED1102/04(config)# preview-mode enable
ACCEED1102/04(config)# preview-mode disable
ACCEED1102/04(config)#

6.7.10.19 Pwdp
Syntax: pwdp
Description: show path of actual folder
Output:
ACCEED1102/04(config-Tag-Protocol-Identifier)# pwdp
/Ethernet/Switch-Local/LAN-Ports/P1/VLAN/Ingress/Tag-Protocol-Identifier
ACCEED1102/04(config-Tag-Protocol-Identifier)#

6.7.10.20 Reboot
Syntax: reboot <target> [swap]
Description: reboot local system or remote via a channel. If swap is attached, an additional swap of
passive to active firmware bank is forced.
Options:
ACCEED1102/04# reboot ?
refresh update the data
local Reboot target local
shdsl-nt-port-1 Reboot target shdsl-nt-port-1
shdsl-nt-port-2 Reboot target shdsl-nt-port-2
shdsl-nt-port-3 Reboot target shdsl-nt-port-3
shdsl-nt-port-4 Reboot target shdsl-nt-port-4
efm-nt-a Reboot target efm-nt-a
local-array-linecard-2 Reboot target local-array-linecard-2
local-array Reboot target local-array
remote-array-a-linecard-1 Reboot target remote-array-a-linecard-1
remote-array-a Reboot target remote-array-a

A3118-X642-R612-01 138 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.21 Rename
Syntax: rename <file> <new-file>
Description: rename a file in the flash file system
Options:
ACCEED1102/04# rename ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Note: erase action needs to be confirmed
ACCEED1102/04# rename flash:6M_1wp_four_customers.txt 1.txt
Are you sure? [y|n]: y

6.7.10.22 Restore
Syntax: restore <file> [force]
Description: restore a configuration from factory defaults or file in the flash
Options:
ACCEED1416# restore ?
factory-settings Restore factory settings and reboot
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
ACCEED1416# restore factory-settings ?
force Run the command without asking
Output: restored file
ACCEED1416# restore flash: 6M_1wp_four_customers.txt
Are you sure? [y|n]: y
ACCEED1416#
%_Clear configuration done

ACCEED1416#
%_Configuration successfully restored

Lost connection to host.

C:\>
Output: factory defaults
ACCEED1416# restore factory-settings
ACCEED1416# restore factory-settings ?
force Run the command without asking

ACCEED1416# restore factory-settings

Restore factory settings and reboot? [y|n]: y
Rebooting device...

Lost connection to host.

C:\>

6.7.10.23 Root
Syntax: root
Description: change path of actual folder to the top (root) level
Output:
ACCEED1102/04(config-Tag-Protocol-Identifier)# root
ACCEED1102/04(config)#

A3118-X642-R612-01 139 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.10.24 Set
Syntax: set <parameter>
Description: restore a configuration from factory defaults or file in the flash
Options:
ACCEED1102/04# set ?
password Set a new password
session-timeout Set the session timeout
time Set system date and time

Option: Parameter Password

Description: changes the password of the selected user. Is not available, in case of connection
through MCU-S/-CES
ACCEED1102/04# set password ?
Administrator Change the Administrator password
Maintenance Change the Maintenance password
The password may have up to 16 characters
ACCEED1102/04# set password Administrator ?
<0..16 Characters> Enter a new password
The new password is handed over in the command line with quotation marks. For a
successful change the current password is requested. The input of it is hidden with “*”
characters. Note: A double quotation mark means: new password is <Enter> (empty).
ACCEED1102/04# set password Administrator ""
Enter current password: ******
%_Password successfully changed
ACCEED1102/04#

Option: Parameter Session-timeout

Description: changes the timeout minutes of the sessions via serial, ssh and telnet. Each
parameter can be set individually.
ACCEED1102/04# set session-timeout ?
<1..60> Enter session timeout value in minutes
serial session timeout for serial connections
ssh session timeout for SSH connections
telnet session timeout for telnet connections
The set command without a new value shows the actual timeout
ACCEED1102/04# set session-timeout telnet
Current session timeout TELNET: 60 min
ACCEED1102/04#

ACCEED1102/04# set session-timeout telnet ?

<1..60> Enter session timeout value in minutes

ACCEED1102/04# set session-timeout telnet 30

ACCEED1102/04#
Note: A connection through the MCU-S/-CES is a serial link therefore the serial timeout applies, not
the telnet timeout.

Option: Parameter Time

Description: changes the onboard real time clock to the requested time in case of Time Mode is
manual. See Board/Local/Time-Settings
ACCEED1102/04# set time ?
DD.MM.YYYY HH:MM:SS Enter date and time

ACCEED1102/04# set time 15.01.2013 23:18:00

ACCEED1102/04#

A3118-X642-R612-01 140 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

CLI Show Commands

A variety of different show commands is available, that parallel the functionality of LCT+ Buttons.
The following list shows all available commands

ACCEED1102/04# show ?
alarm Display active alarms
flash: Display contents of the flash: directory
mismatch Display all the mismatches on this device
running-config Display current operating configuration
tree Display the datamodel tree below the current folder
version Display system status
alarmlog Dumps a copy of the alarm log
boardinfo Display the content of Board/Local/Information
time Display the content of Board/Local/Time-Settings
mactable Dumps a copy of the current MAC table entries
EVC-Report Displays a report of all EVC configurations
SAT-Report Opens the service activation test report
systemlog Show system log
resources Show system resources
inventory Show inventory list of all connected devices

6.7.11.1 Show alarm

Syntax: show alarm
Description: print the List of the actual Alarms
Output:
ACCEED1102/04# show alarm
Severity Alarm Location Path
--------------------------------------------------------------------------------
Critical Eth-No-Link Port Ethernet/Switch-Local/LAN-Ports/P1
Critical Eth-No-Link Port Ethernet/Switch-EFM-NT/[A]/LAN-Ports/P1
Major Clk-NA Clock-Input Board/Local/Clocking/LAN-Ports/P3
<End of list>

6.7.11.2 Show alarmlog

Syntax: show alarmlog
Description: prints the history of the last 1000 Alarm change entries. The actual time, firmware
version and hardware type is shown. Each Alarm state change has 2 Lines output.
The first line carries:
o 3 digit sequence number
o UTC Time of the Event
o the Serverity of the Alarm occurrence (Critical, Major, Minor, Warning) or clearing (Cleared)
o Device (is always NT in case of CPE)
o Location (Physical Entity) of the Alarm occurance
o Transition of the alarm state (shows the previous and the actual alarm state)
o Path (physical path of the corresponding alarm location)
Output:
ACCEED1102/04(config)# show alarmlog
Downloading Data.

05.01.2013-13:18:56-UTC - FW-ID:654 V1.72 - HW:S3118-K644-E446-A3 - Desktop

Time Severity Device Location Transition

Path

27 05.01.2013-08:53:07-UTC CLEARED NT MEP SOAM-RDICCM->No Alarm

Ethernet/Switch_Local/SOAM/Domains[#1]/MPs[#1]/MEP
26 05.01.2013-08:52:58-UTC MINOR NT MEP No Alarm->SOAM-RDICCM
Ethernet/Switch_Local/SOAM/Domains[#1]/MPs[#1]/MEP
.
.
1 31.12.2012-05:56:22-UTC CRITICAL NT SHDSL Port 2 No Alarm->LOS
Aggregation/EFM_Link[#1]/Lines[#2]/SHDSL
0 31.12.2012-05:56:22-UTC CRITICAL NT SHDSL Port 1 No Alarm->LOS
Aggregation/EFM_Link[#1]/Lines[#1]/SHDSL
<End of list>

A3118-X642-R612-01 141 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.11.3 Show boardinfo

Syntax: show boardinfo
Description: displays the quick info of the actual hardware release and the firmware status.
Additionally the Serial and the CLEI is shown
Output:
ACCEED1102/04# show boardinfo
Description "Slot16" Device description
HW-Part-Number "S3118-K644-E446-A3" Part number of the board
HW-Options "4wp (Eth+G703+RPS180V+SyncE)" Options of the board
Active-FW-Type "654" Type of active firmware
Active-FW-Version "1.80" Version of active firmware
Passive-FW-Type "654" Type of passive firmware
Passive-FW-Version "1.70" Version of passive firmware
Housing Rack-V3 Housing of local device
Slot-Number 16 Slot number in rack (plug-in devices only)
Serial-Number "YLRGQ" Serial number of the board
CLEI "" CLEI code of the board
SCC-ID 00:1A:D0:05:FA:C1 SCC identification number

6.7.11.4 Show EVC-Report

Syntax: show EVC-Report
Description: compact overview of all configured EVC channels
Output:
ACCEED1102/04# show EVC-Report
Downloading Data.

05.01.2013-13:22:20-UTC - FW-ID:654 V1.80 - HW:S3118-K644-E446-A3 - Desktop

Device Description: ULAF+ ACCEED 1404

CoS Identifiers:
--------------------------------------------------------------------------------

Description CoS Mapping CE-VLAN-CoS Values

EVC 1:
--------------------------------------------------------------------------------

Identifier:
Type: Point To Point
VLAN Map:
UNI List:
Port List:

CoS Instances:
----------------------------------------------------------------------------
CoS Identifier Ingress Modifier Egress Modifier
.
.
.
<End of list>

6.7.11.5 Show flash

Syntax: show flash:
Description: print the stored configurations in the flash filesystem
Output:
ACCEED1102/04(config)# show flash:
-rw-r--r-- 93520 Jan 11 17:04 104M_16wp_one_customer.txt
-rw-r--r-- 83441 Jan 11 17:45 22M_4wp_one_customer.txt
-rw-r--r-- 91365 Jan 11 14:58 60M_4wp_one_customer.txt
-rw-r--r-- 88562 Jan 11 16:13 6M_1wp_four_customers.txt

A3118-X642-R612-01 142 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.11.6 Show inventory

Syntax: show inventory
Description: print the list of devices in the ULAF+ Rack System. In case of CPE Application there is
only one NT displayed
Output:
ACCEED1102/04# show inventory
Downloading Data.

12.01.2013-05:08:17-UTC - FW-ID:644 V1.80 - HW:S3118-D644-E126-E3 - Plugin Slot:13

Device Description: Slot 13_Profile 10M

Info NE-Name Partnumber Active FW Passive FW Serial Number

Devices In Aggregation

PAF A S13P1 LT S3118-D644-E126-E3 644 1.80 644 1.70 YBXJK

PAF A S13P1 NT S3118-K644-E146-03 644 1.80 644 1.70 YBXXC
PAF A S13P2 LT S3118-D644-E126-E3 644 1.80 644 1.70 YBXJK
PAF A S13P2 NT S3118-K644-E146-03 644 1.80 644 1.70 YBXXC

Devices In Array/SHDSL/EFM

LT S3118-D644-E126-E3 644 1.80 644 1.70 YBXJK

SHDSL-NT_1 S3118-K644-E146-03 644 1.80 644 1.70 YBXXC
SHDSL-NT_2 S3118-K644-E146-03 644 1.80 644 1.70 YBXXC
LC_12 S3118-D644-E126-05 644 1.80 644 1.70
LC_14 S3118-D644-E126-05 644 1.80 644 1.70
LC_15 S3118-D644-E126-E3 644 1.80 644 1.70
LC_16 S3118-D644-E126-E3 644 1.80 644 1.70
<End of list>
ACCEED1416#

6.7.11.7 Show mactable

Syntax: show mactable
Description: print the actual learned MAC Addresses of the bridge according to the VLAN Table
and ingress Port.
Output:
ACCEED1102/04# show mactable
Downloading Data.

05.01.2013-13:21:42-UTC - FW-ID:654 V1.80 - HW:S3118-K644-E446-A3 - Desktop

Device Description: ULAF+ ACCEED 1404

VLAN MAC Address Port

200 00:1A:D0:17:34:01 WAN1

100 00:1A:D0:17:34:01 WAN1
1 00:1A:D0:05:8F:C1 WAN1

Number of Entries: 3
<End of list>

A3118-X642-R612-01 143 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.11.8 Show mismatch

Syntax: show mismatch
Description: print all mismatching items
Output:
ACCEED1102/04# show mismatch
Creating device mismatch file......
!
root
Ethernet
Switch-Local
LAN-Ports 1
Port-Isolation
Allowed-Egress-Ports P2 true
!
root
Ethernet
Switch-Local
LAN-Ports 3
Port-Isolation
Allowed-Egress-Ports P2 true

ACCEED1102/04#

6.7.11.9 Show resources

Syntax: show resources
Description: print the actual status of the system. Device description (timestamp, HW, FW), Uptime
since last reboot or startup, process list, memory usage and temperature
Output:
ACCEED1404# show resources
Downloading Data.

05.02.2013-13:21:23-UTC - FW-ID:654 V1.80 - HW:S3118-K644-E446-A3 - Desktop

Device Description: ULAF+ ACCEED 1404

== Uptime and system load

13:21:23 up 7:25, load average: 0.00, 0.02, 0.00
== Process list
PID USER VSZ STAT COMMAND
1 root 2904 S init
2 root 0 SW< [kthreadd]
3 root 0 SWN [ksoftirqd/0]
.
.
.
552 root 2908 R ps
== Flash memory usage
/dev/mtdblock5 65.0M 17.3M 47.7M 27% /nvd
/dev/loop0 985.0k 1.0k 984.0k 0% /nvd/configuration

== Temperature and Fan

On-Chip Temperature CPU:71°C FPGA:60°C
Fan Speed:85% PWM:55
<End of list>

A3118-X642-R612-01 144 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.11.10 Show running-config

Syntax: show running-config
Description: print actual configuration (all differences to default values)
Output:
ACCEED1102/04# sh running-config
Creating device configuration file......

! Current Configuration
! Device: ACCEED 1416
! Part Number: S3118-D644-E126-05
! Mode: LT
! FW ID: 644
! FW Version: 118.12
! HW Options: 4wp (Eth+G703+RPS180V+SyncE)
! Last Configuration Change: 13.01.2002 - 19:25:44 - UTC
!
root
Aggregation
EFM-Link 1
Remote-PAF Slot-3-PAF-A
!
.
.
.
!
root
Board
EFM-NT 4
Management-Access
Inband
Ports P4 false
IP-Configuration Static

ACCEED1102/04#

6.7.11.11 Show SAT-Report

Syntax: show SAT-Report
Description: print Service Activation Test Report of the last Service Activation Test.
Output:
ACCEED1102/04# show SAT-Report
Downloading Data.

05.01.2013-13:22:59-UTC - FW-ID:654 V1.80 - HW:S3118-K644-E446-A3 - Desktop

Device Description: ULAF+ ACCEED 1102/04

Test Setup
=============================================================================
Service Configuration Test: Yes
Service Performance Test: No
Color Mode: Color Blind
Color Method: PCP
Test Port: WAN1
Destination MAC Address: 00:1A:D0:17:34:01
Source MAC Address: 00:1A:D0:0F:93:B1
Tunnel VLAN ID: None

Test CoS Instance 1:

--------------------------------------------------------------------------
CIR: 1000 kbit/s
EIR: 25000 kbit/s
M Factor: 10 %
FLR Threshold: 5.000 %
Availability: 95.000 %
FD Threshold: 20000 us
IFDV Threshold: 5000 us
Frame Pattern: EMIX
Frame Size: {64, 128, 256, 1024, 1518} B
VLAN ID: 100
CoS: 0

A3118-X642-R612-01 145 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Service Configuration Test PASS

=============================================================================
Test CoS Instance 1: PASS

CIR Test
--------------------------------------------------------------------------
Duration: 30 s

Test CoS Instance 1: PASS

-----------------------------------------------------------------------
EMIX: {64, 128, 256, 1024, 1518} B
--------------------------------------------------------------------
IR [kbit/s] PASS
Min Avg Max
998.273 1000.000 1000.000

FLR (CIR) [%] PASS

0.000

FD [us] PASS
Min Avg Max
617 1298 2340

IFDV [us] PASS

Min Avg Max
16 643 1718

Throughput Frames
Total Sent Received Lost
6229 6229 0

Delay Frames
Sent Received Lost
30 30 0

Total
Sent CIR Sent Received Lost
6259 6259 6259 0
<End of list>

6.7.11.12 Show systemlog

Syntax: show systemlog
Description: a trace since the last power-up of the last 1000 entries.
Output:
ACCEED1102/04# show systemlog
Downloading Data.

05.02.2013-13:20:33-UTC - FW-ID:654 V1.80 - HW:S3118-K644-E446-A3 - Desktop

Device Description: ULAF+ ACCEED 1102/04

=== NVD entries

=== actual entries
Mar 5 05:55:33 ACCEED syslog.info syslogd started: BusyBox v1.12.2
Mar 5 05:55:33 ACCEED user.notice kernel: klogd started: BusyBox v1.12.2 (2012-06-29
11:39:43 CEST)
Mar 5 05:55:33 ACCEED user.notice kernel: Linux version 2.6.22.18 (aggtpet0@ulafpc22) (gcc
version 4.3.2 (Sourcery G++ Lite 2008q3-41) ) #1 Fri Jun 29 11:43:09 CEST 2012
Mar 5 05:55:33 ACCEED user.warn kernel: CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE),
cr=00053977
Mar 5 05:55:33 ACCEED user.warn kernel: Machine: Feroceon-KW
Mar 5 05:55:33 ACCEED user.warn kernel: Using UBoot passing parameters structure
Mar 5 05:55:33 ACCEED user.warn kernel: BoardID from uboot=10
Mar 5 05:55:33 ACCEED user.warn kernel: Memory policy: ECC disabled, Data cache writeback
Mar 5 05:55:33 ACCEED user.debug kernel: On node 0 totalpages: 63488
<End of list>

A3118-X642-R612-01 146 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.7.11.13 Show time

Syntax: show time
Description: print the battery buffered realtime clock and the timeserver setting for auto time
retrieval from NTP Servers
Output:
ACCEED1102/04# show time
Current-Date-And-Time 05.01.2013 13:19:40 Current system date
(DD.MM.YYYY) Current system time (HH:MM:SS)
Mode Manual Method of time and date
configuration
Active-Time-Server 10.0.0.1 Currently active NTP time
server
Time-Server 10.0.0.1 Configured NTP time server
Server-Port 123 Port of NTP time server

6.7.11.14 Show tree

Syntax: show tree
Description: print path of actual folder and the complete folder structure downwards
Output:
ACCEED1102/04# sh tree
Current Path:
/

Aggregation
EFM-Link[]
...
PME[]
...
Ethernet
Switch-Local
...
Switch-EFM-NT[]
...
CES-IWF
Local
...
EFM-NT[]
...
Board
Alarm-Configuration
...
Local
...
EFM-NT[]
...
Array
Local
SCC[]
SHDSL[]
ACCEED1102/04#

6.7.11.15 Show version

Syntax: show version
Description:
Output:
ACCEED1102/04# sh version
Device: ACCEED 1102/04
Part Number: S3118-D644-E126-E3
Mode: LT
FW ID: 644
FW Version: 1.80
HW Options: 4wp (Eth+G703+RPS180V+SyncE)
Last Configuration Change: 18.01.2013 - 10:38:55 - UTC
Datamodel Version: 0.491.0
CLI.xml Version: 0.13.0 - 0.279.0
ACCEED1102/04#

A3118-X642-R612-01 147 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

TFTP Server Setup

There are different methods for downloading configuration files and firmware updates to the ULAF+
ACCEED System via CLI, e.g. TFTP and SCP. This chapter describes the setup and usage of a TFTP
Server in a Windows environment.

The application tftp32 is often used in networks to

provide Trivial File Transfer Protocol Server
capabilities. This open source application by Ph.
Jounin helps to use TFTP simple, but effective. The
installation file can be downloaded free of charge
from this link:
http://tftpd32.jounin.net/tftpd32_download.html

After installation the icon above is found on the desktop.

When starting the application this main window open:

Enter in the field “current directory”

(marked yellow) the path to the Firmware
or the configuration files. Please use the
assistance of the Browse button to find the
right location.

Additionally insert the IP Address in the

field “server interfaces” (marked cyan) of
this Windows System. The Application
now opens the TCP port 69 and listens to
on it.

Now enter the ACCEED via telnet and

initiate a firmware update. The output may
look like the following screenshot:

C:\>Telnet 10.128.3.27

Loading ACCEED CLI.....................

Device: ACCEED 1102/04

Part Number: S3118-D644-E126-05
Mode: LT
FW ID: 644
FW Version: 1.80
HW Options: 4wp (Eth+RPS180V+SyncE)
Last Configuration Change: 09.01.2013 - 23:18:24 - UTC

Username:
Password :

ACCEED1102/04> enable
ACCEED1102/04# fwupdate tftp:10.128.3.65/ACCEED1102/04/Rel_1.80/ACCEED_1102/04_644_01.80.tgz
Downloading firmware ...........
Firmware download complete
Writing firmware to passive bank.........................................
Written firmware to flash
Awaiting update..........
Done.
ACCEED1102/04#

While connecting the ACCEED TFTP client to the server a transfer file window opens and shows the
progress of the data transfer.

A3118-X642-R612-01 148 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

After the transfer is done you will get an output similar to the this screenshot

A3118-X642-R612-01 149 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

6.8 Firmware upgrade

The ‘Download’ function allows updating the firmware of the network elements.

To reduce the risk of configuration loss when updating the firmware it is recommended
 to always save the configuration to a file before each download.
The load configuration is described in  6.6.2.

Figure 6-41 Download dialogue

All ULAF+ network elements are equipped with 2 program memory banks:
 the active memory bank, containing the code currently running on the NE
 the passive memory bank, which can contain a second FW image

The FW download replaces the image stored in the passive bank.

The download dialogue displays both the active and the passive FW of the network element. These
are characterized by:
 the FW-ID (an identification number unique for each device type)
 the FW version
Local Download

The local download allows upgrading the FW of LT or NT (depending on which network element the
LCT+ is connected to). The local download is performed according to the following procedure:

To initiate a download the file containing the FW (*.dwl file) must be opened. This is done
1
by clicking the ‘Browse’ button.

 The `dwl` file is checked to ensure that only allowed FW can be downloaded.

A3118-X642-R612-01 150 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Figure 6-42 Open download file

2 Start the download by clicking the `Start` button

Figure 6-43 Download OK

Depending on the connection type (e.g. serial management connection) the time needed for the
download procedure to the network varies. The download progress is displayed in the progress bar.

 It is possible to manage the unit (e.g. add/remove lines, change configurations) while
performing the FW download

Figure 6-44 Download progress bar

The download can be aborted at any time. After aborting the passive bank is empty. A new download
can be restarted at any time.

After download completion the checksum of the downloaded FW image is checked.

A3118-X642-R612-01 151 / 405

 ULAF+ 6 - Configuration and operation ACCEED 1102/04 Manual

Figure 6-45 Download finished

To activate the new FW, the `Reboot` button must be pressed and the `Swap` checkbox
3
must be enabled. This will load the downloaded FW in the active bank.

 The service is interrupted during the reboot.

Remote Download
Remote download is the procedure needed to update the FW of the ACCEED 1102/04 unit via the in
band channel.
The in band channel can be very fast, if no rate limiting is applied to in band channel it uses the same
bandwidth as the payload and requires an IP address on the remote ACCEED 1102/04 unit.
The in band download procedure is the same as the procedure for local download.
Please refer to  6.3.4 for more information.

A3118-X642-R612-01 152 / 405

ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7
EFMC Aggregation

This chapter gives an overview of the EFM capabilities, the configuration

and fault management options.

A3118-X642-R612-01 153 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7.1 EFM Link

EFM Frame distribution

- Clustering method
- Cluster sizes
- Overhead

EFM LT Parameters

 EFM configuration:

 Remote PAF
This parameter sets the slot address of the NT unit. If the NT is an ACCEED plug in, this
parameter corresponds to its slot number in the subrack or compact shelf. In case of desktop
units, this parameter is the locally assigned SCC bus address.
 Bandwidth (read-only)
Shows the total configured Bandwidth of the EFM link
 Available Bandwidth (read-only)
Shows the actual available bandwidth within this EFM link. It is the sum of the bandwidth of all
SHDSL lines which are active (not disturbed) in the link
 Low Bandwidth Alarm Threshold
Raise the “Low Bandwidth” Alarm if the available Bandwidth is lower than this configured
bandwidth
 Limit WAN Bandwidth
Sets an egress rate shaper with 90% of the available bandwidth to prevent EFM clustering buffer.
This feature enables the shortest latency and lowest frame delay variation

A3118-X642-R612-01 154 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

EFM CPE Parameters

 EFM configuration:

 Enable (enabled, disabled)

enable – allow SHDSL training
disable – deactivate SHDSL transceiver
 PMMS (enabled, disabled)
enable – allow line probing
disable – prevent line probing

 Alarm Thresholds Source (Central Office (CO), Manual)

Attenuation and Signal Noise Margin Threshold can be defined. If they are hit, a retraining of the
SHDSL line is triggered
Central Office (CO) – Attenuation and SNR Margin will be retrieved from CO side
Manual – Attenuation and SNR Margin are used locally
 Manual Attenuation Alarm Threshold (Off, 0 .. 127 dBl)
Defined Value for the manual Attenuation Alarm Threshold.
 Manual SNR Alarm Threshold (Off, 0 .. 31 dBl)
Defined Value for the manual Attenuation Alarm Threshold.

A3118-X642-R612-01 155 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7.2 SHDSL line

Transmission is via copper wire pairs as defined in ETS 101 524 [15] and ITU-T G.991 [14]. ACCEED
1102/04 supports symmetrical PSD Masks (Power Spectrum Density) with TC-PAM 16 and TC-PAM 32
Modulation (Trellis Coded Pulse Amplitude Modulation).
The extension of the standard ETSI TS 101 524, Annex E, enables significantly higher transmission
rates on the SHDSL interface:
 TC-PAM 16 (192 kbit/s – 3840 kbit/s) or
 TC-PAM 32 (768 kbit/s – 5696 kbit/s)
7-2_01_PAM_Ranges

Figure 7-1 Bit rate range TC-PAM 16 / TC-PAM 32

Beside the above standard compliant modulations ACCEED 1102/04 supports the so-called extended
modulations (EXT-TC-PAM4 / 8 / 16 / 32 / 64 / 128). These can be used to achieve specific results:
 Modulations with fewer symbols (e.g. EXT-TC-PAM4) are more robust to interferers on the line.
These modulations can be used to achieve better reach at lower bit rates.
 Modulations with more symbols (e.g. EXT-TC-PAM128) can be used to achieve a better
throughput at shorter distances.
Extended Bitrates are possible up to 239 TS or 15’296 kbit/s.

The extended bit rates are supported on all ACCEED devices. Please refer to  3.3.3 for the
supported combinations.
If the ACCEED operates in the CPE mode, the DSLAM is defining the bit rate to be established and
therefore the support of the extended bit rates is depending on the capabilities of the SHDSL card in the
DSLAM/MSAN.

 Please respect the rules of your country regarding modulation restrictions. Ask your
regulation authority for the allowed spectrum management rules.

Transmission range
It is not possible to specify a generally-valid value for the usable range of SHDSL systems, because
various cable characteristics, the noise conditions and the modulation type (TC-PAM 16 / TC-PAM 32 /
others) have a critical influence on the transmission range. To enable comparable results, the SHDSL
transmission has been measured by means of a line simulator, on standardized lines with
standardized noise interference. However, the usable ranges which are possible in practice can differ
significantly from the values determined in this way.

The maximum reachable distances are affected by

 the cable parameters (R’, C’, L’, G’)
 the payload bit rate of each wire pair

A3118-X642-R612-01 156 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

 type and level of the surrounding noise

 the level of the transmitted signal (adjustable by the PBO (Power Back Off))
 type of modulation (TC-PAM 16 / TC-PAM 32 / others)
 echo on bridged taps, cable diameter transitions and diverting impedance

Some maximum reach values measured in the lab can be found in  7.2.6.

Cable parameters
The cable parameters are defined, in a first approach, by the diameter of the copper wire and the
insulation material used in the cable. Also the space between the conductors and the wire twisting has
a strong impact on the cable characteristics. The parameters R’, C’, L’, G’ are dependent on the
frequency and temperature. Considering the parameters, one can estimate the attenuation as a
function of the frequency.
The cable parameters for the standardized cables (as simulated in the wire line simulator) are defined
in ITU-T G.991.2 [14] and ETSI ETS 101 524 [15]. In practice, those values can be investigated on the
real cabling by using special cable analyzers.

Payload bit rate

The payload bit rate of each wire pair can be individually adjusted from 192 kbit/s to 15’296 kbit/s in 64
kbit/s steps, according to the application requirements. As a coarse value for orientation, one can
assume that the maximum transmission distance varies inversely with the square root of the payload
bit rate variation.

Example: Lowering the payload bit rate from 2048 kbit/s to 512 kbit/s (4:1) will approximately double
the transmission distance (square root of 4).

Noise level and type

The interference signals that have an influence on the SHDSL signal come from many different sources.
Alongside with far and near end cross talk (FEXT, NEXT) originated by other signals in the same cable
(e.g. POTS, ISDN, HDSL, ADSL, ADSL2, VDSL, VDSL2, etc. or further SHDSL systems), impulsive
noise is frequently present. In order to produce (at laboratory conditions) values comparable to those
ones in real conditions, various noise models have been defined in G.991.2 [14] and ETSI ETS 101 524
[15]; these models reproduce the situations that are possible in practice. For the measurements in
chapter 7.2.5, the noise «Type B» as defined G.991.2 and ETSI ETS 101 524 has been used.
`Type B` noises correspond with a mean value of various interference effects (e.g. several wire pairs)
in a standard cable, in order to receive the most practical test results.
The measurements were carried out with «Type B» noise at 0 dB and 6dB, representing normally and
heavily disturbed surroundings.

Transmission level
The maximum transmission level is defined in G.991.2 and ETSI 101 524.

13,5 dBm for R 2048 kbit/s payload bit rates

with TC-PAM 16
14,5 dBm for 2048  R  3848 kbit/s payload bit rates
13,5 dBm for 768  R < 2688 kbit/s payload bit rates
with TC-PAM 32
14,5 dBm for 2688  R  5696 kbit/s payload bit rates
Table 2 SHDSL transmission levels

The values correspond with the nominal transmission level with the configuration PBO 1 = 0 dB. For
long cables, this default value should be maintained. For shorter cables, the transmission level can be

1 Power Back-Off
A3118-X642-R612-01 157 / 405
 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

reduced through the PBO according to the application requirements, in order to diminish the crosstalk
noise on the other copper pairs.

 In accordance with the standards G.991.2 [14] and ETSI 101 524 [15], the transmission
level must be reduced at line loss 6 dB (or 10 dB at TC-PAM 16 and 8 dB at TC-PAM
32 with ETSI Annex E / ITU-T Annex G). This setting is automatically done in the
‘Automatic' power back off mode or ‘True Attenuation based PBO’ settings.

SHDSL performance (max reach)

The following diagrams contain the maximum reach measured in the lab for different conditions:
 Modulation (TC-PAM 16 / TC-PAM 32)
 Cable diameter (0.4 / 0.8 mm)
 Noise model (6dB ETSI / 0dB)
 Noise source position (Central Office / Remote)

Please note that the diagrams below reflect performance measurements of an ACCEED 1416 to
ACCEED 1416 connection.
The performance between ACCEED 1102/04 and the targeted DSLAM depends on the line conditions
as described above and the SHDSL interoperability (e.g. chipset, analogue front end …) of the two
devices. The performance therefore can differ compared to the diagrams.

A3118-X642-R612-01 158 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

Figure 7-2 max. Reach TC-PAM16 / PE0.4

Figure 7-3 max. Reach TC-PAM16 / PE0.8 2

2 the line simulator is limited to 15500m.

A3118-X642-R612-01 159 / 405
 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

Figure 7-4 max. Reach TC-PAM32 / PE0.4

Figure 7-5 max. Reach TC-PAM32 / PE0.8

A3118-X642-R612-01 160 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

SHDSL line Fault Management

There are two different SHDSL loop types available on the ACCEED 1102/04, the transceiver loop
(3a) and the repeater loop (1a). Both are service affecting, since they interrupt the data transmission
on the selected SHDSL line. Thus the SHDSL line with an active loop will be removed from the EFM
Link (Not Aggregated Alarm) to prevent data reassembly faults.
SHDSL line loops are of the following use:
- BER Test to the SHDSL loop segment (3a and 1a)
- Physical connectivity check to the loop repeater (1a)

SHDSL line loops are set selecting in the Table area the tabs FaultMaintenance and then click on a
loop symbol (View area: Aggregation tab) of a SHDSL port or a Repeater stage.
Aggregation/EFM Link/[]/Lines/Slot x Port y
Aggregation/EFM Link/[]/Lines/Slot x Port y/Regenerator/Stage z

Figure 7-6 SHDSL Loopback

 If a (1a) Loop is set at a certain repeater stage, the (LT initiated) SHDSL training sequence
is started to establish the SHDSL connection to this repeater stage, even if no SHDSL NT
is connected (pilot tone is missing).

All SHDSL line relevant alarms are described in  12.3.

SHDSL line configuration
7.2.8.1 SHDSL line parameters
Each ACCEED 1102/04 SHDSL line (specified by a slot and a port number) presents the following
parameters:

A3118-X642-R612-01 161 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

 Aggregation/EFM Link/[]/Lines/Unassigned

 EFM Link
This is the EFM link to which the SHDSL line is assigned to. This parameter is “read only”. To
assign SHDSL lines to an EFM link see the  5.8.5.
 Assignment
SHDSL lines can be assigned to a certain EFM Link or “unassigned” (i.e. not allocated). It is possible
to add/remove SHDSL lines to/from EFM link without any bit error at any time: at installation or
during operation.
To remove a line from the EFM link, set the Assignment parameter to the “Unassigned” value.
To add a line to the EFM link, select one physical line from the Assignment drop down list. If no
SHDSL line is available in the list, select the Lines node in the parameter tree and press the “Add
Line” button located in the bottom of the table area.
It is possible to remove all lines from the EFM Link, by pressing the button “Remove All” located in
the bottom of the table area, after selecting the Lines node in the parameter tree.
 5.8.5 contains a detailed description about adding SHDSL lines to an EFM Link.

 Line assignment drop down list

 Line ID
Unique ID assigned to this PME among the aggregated lines. This parameter is read only.

A3118-X642-R612-01 162 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

 Status
This parameter indicated the current status of the PME assignment, this parameter is read only.
“Assignment Done And Active” working link
“Assignment Done But Passive” SHDSL bandwidth of this line is lower than 25% of the
fastest line in this EFM link
“Local Assignment Mismatch” SHDSL port already used by another unit
“Remote Assignment Mismatch” Remote PAF assignment already used by another EFM
Link or not available, check Aggregation/EFM Link/[]
“No SHDSL Port Selected” Assignment of SHDSL port is missing
 Bandwidth [kBit/s]
This parameter allows configuring the SHDSL bandwidth of the line in 64 kbit/s steps.

 The range of SHDSL bandwidths depends on the SHDSL Modulation parameter. The
Bandwidth influences the maximum reach of the line. See  7.2.1 and  7.2.5.

 Modulation
ACCEED 1416 features the following SHDSL line modulations:
- TC-PAM16
- TC-PAM32
- EXT-TC-PAM4
- EXT-TC-PAM8
- EXT-TC-PAM16
- EXT-TC-PAM32
- EXT-TC-PAM64
- EXT-TC-PAM128

 Please respect the rules of your country regarding modulation restrictions. Ask your
regulation authority for the allowed spectrum management rules.

 Number of regenerators
This parameter indicates the number of regenerators currently present on the line. This parameter
is `read only` and may take values between zero and 8.
 Attenuation Alarm Threshold [dB]
ACCEED 1102/04 allows to define a line attenuation threshold, so that the equipment generates an
alarm when the line attenuation exceeds the threshold.
 SNR Margin Alarm Threshold [dB]
ACCEED 1102/04 allows to define a SNR Margin threshold, so that the equipment raises an alarm
when the SNR falls below the threshold. This gives the operator the chance to intervene, before the
line fails. A minimum Signal to Noise Margin of 6dB is recommended.
 SNR Margin Aggregation Threshold [dB]
An erroneous SHDSL lines should be removed from the EFM aggregation. The ACCEED 1102/04
allows to remove SHDSL lines from the aggregation, if a configured minimum SNR is not available.
Moreover an alarm with configurable severity is raised.
 SNR Margin Excess Threshold [dB]

A3118-X642-R612-01 163 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7.2.8.2 Rate Optimization

 Rate Optimization configuration:

7.2.8.3 Power back off

The SHDSL transmitter has the ability to reduce its transmitted power in order to reduce crosstalk with
transmission systems operating in the same multi pair cable. The power back off function in upstream
and in downstream direction is the same.

 Power back off configuration:

A3118-X642-R612-01 164 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

Automatic power back off

When `Automatic` is selected, the SHDSL transceivers negotiate the power back off automatically. The
possible values are: 0 dB PBO (meaning NO power back off) up to 6, 8 or 10dB (maximum power back
off in automatic mode). The standard uses the following rule to define the auto power back off:

power back off TC-PAM 16 TC-PAM 32

0 - 6 dB  36 timeslots  48 timeslots
0 - 8 dB - > 48 timeslots
0 - 10 dB > 36 timeslots -
Table 3 automatic power back off

True Attenuation
When `True Attenuation` is selected, the power back off is set according to the line attenuation estimate
calculated by the device. As soon as the line is up (NT or REG with Loop visible), the measured line
attenuation is compared with the estimation. If the difference between the values exceeds +/- 1 dB the
line is restarted with a power back off configuration corresponding to the measured line attenuation.

Manual power back off

When `Manual` (also known as "Forced PBO") is selected, the SHDSL transceivers negotiate the power
back off in the G.handshake procedure according to the configured value from the management system.
The possible values are: 0 dB PBO (maximum signal output) up to 31 dB (signal output is reduced by
31 dB). It is possible to configure each section with its own PBO value.

7.2.8.4 Remote Power Supply

 Remote Power Supply configuration:

A3118-X642-R612-01 165 / 405

ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7.2.8.5 SHDSL local

 Local SHDSL information:

A3118-X642-R612-01 166 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

7.2.8.6 SHDSL-NT

 Remote SHDSL information:

SHDSL line performance

The performance of every single SHDSL line section can be verified by means of:
 Error counters
 Line parameters

Moreover each SHDSL line can be verified using a built-in BERT (Bit Error Rate Test) facility.

For LCT+ specific information see  6.5.7.

7.2.9.1 SHDSL error counters
Payload traffic on the SHDSL line is transmitted in `frames`. Each SHDSL frame contains overhead
information. Among this information a CRC6 checksum is carried in each frame. This allows the
equipment to detect `block errors` occurred during the transmission. A block error corresponds to at

A3118-X642-R612-01 167 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

least one faulty bit within the SHDSL frame. This information allows assessing transmission quality and
debugging faulty lines.

For each single SHDSL line section, the following CRC6 error counters are available:

Elapsed Time
ET
Total of seconds since measurement started
Block Error
BE
Total of errored blocks received
Loss of Sync Word Second
Total of seconds with LOSW alarm condition
LOSWS
By default LOSWS counts even during unavailable state. This can be prevented by
inhibiting the LOSWS counting during UAS. (see  11.2) Board/Alarm Configuration
Errored Seconds
ES
Total of seconds containing at least one BE
Severely Errored Seconds
SES
Total of seconds containing more than 30% errored blocks
Unavailable Seconds
UAS
Total of seconds which the line was not available
Table 4 SHDSL error counters

As indicated in  6.5.8, the following time intervals and types of measurement are available:
 32x intervals of 15 minutes
 7x intervals of 24 hours.

 The error counters are stored in the equipments volatile memory, i.e. the counters are
cancelled on reset or power off.

 The SHDSL line error counters are displayed as shown in the table below.
The counters are stored in 15 minutes and 24 hours interval. The last 32 “15 minutes”
interval and 7 “24 hours” interval can be displayed by selecting the appropriate values in
the pull down menus.
Selecting the SHDSL line of interest in the tree view will display just the counters of the
appropriate line.

SHDSL line parameters

For each SHDSL line the following line parameters are available
A3118-X642-R612-01 168 / 405
 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

SNR Margin estimated SNR Margin (in dB)

Loop Attenuation measured Loop Attenuation (in dB)
Power Back Off Power Back Off value of the SHDSL transmitter (in dB)
Table 5 SHDSL line parameters

 SNR Margin
This parameter indicates Signal-to-Noise Ratio Margin expressed in decibels (dB). It is a measure
of signal strength relative to background noise.

 Loop Attenuation
This parameter indicates the power insertion loss of the copper line. The measured value is given
in dB.

 Power Back Off

Power Back Off reduces the transmit power of the SHDSL transceiver in order to minimize the
crosstalk between copper lines in the same cable bundle.

 For a robust transmission, a minimum Signal to Noise Ratio Margin of 6dB is aimed for a
new installation.

 The SHDSL lines parameters are displayed as shown in the table below.
The table view can be modified to display just the required values. Deselect the tick of the
SNR margin, loop attenuation or power backoff accordingly.
Pressing the Overview button opens a dedicated window with all line parameters.
Selecting the SHDSL line of interest in the tree view will display just the line parameters of
the appropriate line.

7.2.9.2 BERT
The built-in Bit Error Rate Test (BERT) facility allows performing a true Bit Error Rate Measurement on
each SHDSL line.

The test is performed `roundtrip` by the LT unit. During the test a defined bit-pattern (PRBS: 215 -1) is
generated and sent as payload data over the SHDSL line. A loop back is automatically set in the NT
unit. The looped back signal is checked for bit errors in the LT unit.

A3118-X642-R612-01 169 / 405

 ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

To test a particular line segment, the loop-back can manually be activated on a regenerator.

To perform the BER Test a test pattern is transmitted over the SHDSL line, thus during
 test execution the line is not available for payload transmission.

If the SHDSL line on which the BERT is carried out belongs to an established EFM-Link,
 this line temporarily taken out of the aggregation group. A Partial Aggregation Loss
Alarm is raised and remains active for the entire test duration.
BERT delivers more detailed information than the block error rate based on CRC6 error counters (i.e.
the true Bit Error Rate) and is typically used to assess the transmission quality of a line, before putting
it in live service.
The following time intervals are available
 1 minute
 10 minutes
 1 hour
 24 hours.

The following test results are available:

 State
State of the BER measurement (e.g. `Ready to start`, `Searching`, `Running`, `Done` or `Abort`)
 Bit Error Rate
Bit error rate in the following notation 0.000E0
 Errors
Number of bit errors
 Elapsed Seconds
Elapsed time in seconds
 Error Free Seconds
Error free time in seconds
 Pattern Sync Loss Seconds
Sync loss time in seconds

 The BER Test is located in the Aggregation\EFM-Link\[N]\Lines\Slot X Port Y node of the

parameter tree and in the Performance\ BER Measurement tabs (blue circles).
The control of the BER test is located in the bottom of the LCT+ window and allows setting
the duration interval, to start the test, to refresh the displayed test results during execution
and to abort the test (orange circle).
The loopback is automatically set in the EFM NT. The corresponding line is colored in
yellow to signal the presence of a maintenance function (green circle).

A3118-X642-R612-01 170 / 405

ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

BERT is available for each SHDSL line individually. BERTs are independent from each
 other i.e. more BERTs can be started at the same time in parallel.

During BERT the SHDSL line under test is automatically removed from the EFM-
 aggregation. This leads to a reduced total Bandwidth of the EFM-aggregation.

A3118-X642-R612-01 171 / 405

ULAF+ 7 - EFMC Aggregation ACCEED 1102/04 Manual

 To perform a BER Test over a segment of the line, a loopback has to be manually set on
the corresponding regenerator. In the following example, the loopback has been set on
regenerator 8.

A3118-X642-R612-01 172 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8
Ethernet Switch

This chapter describes the powerful feature set of the ACCEED regarding
packet evaluation, manipulation and prioritization for traffic engineering.
Highlights are:
 Highly flexible VLAN manipulation
 Powerful ingress and egress Policy Engines
 Low Latency, low Jitter
 QoS
 Ethernet OAM
 Traffic Shaping
 Traffic Counting
 Protection Mechanisms

A3118-X642-R612-01 173 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.1 ACCEED 1102/04 switching features at

a glance
Port control
 Flow Control, Auto MDI/MDI-X, Mode, Advertised Mode
 Configuration readout incl. Flow control
 Link Failure Propagation (LFP)
 Multicast storm protection
 Broadcast storm protection
 Power over Ethernet
 Synchronous Ethernet
 Port Mirroring (ingress and egress)
 L2CP list with possibility to tunnel/discard/peer
 Port loopback
 Link Aggregation (static LAG and LACP)

Switch control
 Aging enable/disable
 Aging time configurable
 MAC table 16k, self-learning
 MAC table readout
 Limit number of MAC-Addresses learned
 Port isolation

Protection
 Linear Protection G.8031
 Ring Protection G.8032

VLAN
 802.1Q (VLAN)
- 4095 C-VLANs
- Port VID explicit settable
 802.1ad (Provider Bridge)
- Provider/Service VID (S-VID)
- Provider/Service Ethertype (S-TPID)
- Multiple customer services (different C-VLANs to S-VLANs) on same customer port
 TR-101 VLAN manipulations
- Inner/outer swap
- 1:1 translation
- N:1 service multiplexing
- Port-based stacking
- VLAN-based stacking/multiplexing

Classification
 Predefined criteria:
- Ingress Port
- Destination MAC-Address
- Source MAC-Address
- Ethertype (TPID)
- VLAN-ID
- VLAN Priority
- Destination IP-Address
- Source IP-Address
- IP Priority (DSCP)
- IP Datagram Protocol
- TCP/UDP Destination Port
A3118-X642-R612-01 174 / 405
 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

- TCP/UDP Source Port

QoS/Policing
 Prioritization based on:
Ingress port
802.1p (L2)
DSCP (L3)
any other criteria (flow)
 MEF10.2 Ethernet Services Attributes (ingress and egress bandwidth profiles):
Committed Information Rate (CIR)
Excess Information Rate (PIR)
Committed Burst Size (CBS)
Excess Burst Size (EBS)
Peak Burst Size (PBS)
Color mode (CM)
 Metering acc. to RFC2697, 2698 and 3290 with single or two rate three color marking
 8 priority queues per egress port
 Per color queue size
 Hard QoS (guaranteed traffic profile)
 Strict priority (SP)
 Weighted fairness algorithms (WFQ, WRR, SDWRR)
 Per port shaping (rate and burst size)
 Per queue shaping (rate and burst size)
 Random early detection (RED)
 Flexible L2/L3 remarking
 Flexible traffic class assignment

Counters
 Per port packet and byte counters (RMON Etherstats)
 Per ingress and egress service counters (packet or byte / per color)
 Transmit queue counters (packet or byte)
 Per service counters (EVC)
 History for all packet counters

OAM
 Link OAM (802.3ah)
 Service OAM (802.1ag, Y.1731)

A3118-X642-R612-01 175 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.2 The Building Blocks of the Ethernet

switch
This chapter describes the building blocks of the Ethernet switch that can be applied to a packet while
travelling through the ACCEED device.
The simplified figure below show the stages from the ingress side, where the packet is entering
through the ingress port, to the egress side, where the packet is leaving the device via egress port.

Depending on the solution to be implemented, the functions in these building blocks are applied to the
packets.

Figure 8-1 Ethernet switch building blocks

 MAC
This first stage represents the physical port of the ACCEED device connected to the switch. The
Medium Access Control defines the speed and duplex operation of the port. At this stage the packet is
reassembled from its serial form to a full packet stored in a memory buffer. Its FCS is checked.

 Port
In this mandatory stage the packet is analysed regarding the VLAN information and the primary and
secondary VLAN tag assignment is done. The primary and secondary VLAN tag information is further
used as decision criteria in the upcoming stages.
The ports can be configured with port specific VLAN and QoS settings.

 VLAN Translation
The "Primary VLAN translation" is an optional stage and can be performed on the ingress and egress
path (see also stage 7).

 Policing
In addition to the port based configuration settings, traffic can be separated into flows for individual
filtering, metering, VLAN- and QoS manipulation.

 Bridge
The packets entering the bridge are switched to the egress side according to the primary VLAN ID and
the switching criteria defined in the VLAN database. This database defines the VLAN membership of
the physical ports.

 Queuing
On the egress path the packets are enqueued in the transmit queues according to the mapping
scheme that has been assigned on the ingress path. Traffic shaping is possible per queue and per
port.

A3118-X642-R612-01 176 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 VLAN Translation
On the egress path an optional translation of the primary VLAN ID can be applied. This post process
allows the changing of the primary tag.

 Policing
On the egress path, a policing stage is available for flow based filtering, metering, VLAN- and QoS
manipulation.

 Port
Before the packet is leaving the Ethernet switch on the egress port, VLAN and QoS settings can be
changed on the port level according to the requirement for the packet delivery.

 MAC
The leaving packet is prepared for delivery on the egress port. Optionally it can be looped back into
the ingress pipeline of the same port. The Medium Access Control also sets the speed and duplex
operation of the port.

The upcoming chapters describe the functionality in more detail and make reference to the GUI
representation in the LCT+.

The Ethernet Switch settings can be found in the Tree- or the View area of the LCT+.
The graphical representation of the ACCEED LT and NT in the View area is linked to the Tree Area.
By clicking on the descriptions (EVC, PROT, VLAN, etc.) in the graphical view, the respective tree
structure is opened and the Table area with the current settings is shown.
The Ethernet Switch chapter describes the "Switch Local" (LT) configuration. The configuration for the
respective "Switch EFM-NT" has the equal settings.

Figure 8-2 Local and remote switch view with LCT+

A3118-X642-R612-01 177 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.3 Port Control

This chapter explains the configuration settings that can be applied to the ports of the Ethernet switch
in the ACCEED device.
The port control is done based on global settings that are applied to all switch ports and settings that
can be applied individually for each port.

Figure 8-3 Building block – port control

The figure below shows a simplified generic switch model with all possible ports that can be configured
with the ACCEED products. Ports that are not available for configuration for the ACCEED 1102/04 are
greyed out.
Please note that accessible switch ports are P1 – P4 and the SFP1 – SFP4 port. The WAN and BPL
(backplane port) are internal switch ports.

Figure 8-4 Overview switch ports ACCEED 1102/04

Note: the ACCEED 1102/04 unit with data module slot (DMS) has one Ethernet port (P1).

Global switch port settings

The global port settings are applied to all ports as shown in the figure above.
VLAN Mode and MAC Table Aging Time are explained in the Switch Control chapter 8.4
For the global counter settings please refer to chapter 8.10.1

A3118-X642-R612-01 178 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-5 Global switch port settings

 VLAN Mode:  8.5.1
 Learning Mode:  8.4.2
 MAC Table Aging Time:  8.4.3
 Number of allowed MAC Addresses:  8.4.2
 Maximum Frame Size:  8.3.1.1
 LAN Ports Power Save:  8.3.1.2
 Active LFP groups:  8.3.2.2
 … Counters:  8.10.1

8.3.1.1 Maximum Frame Size

The maximum frame size that can be processed with ACCEED 1102/04 is 10240 Bytes.
This setting is applied to all ports of the device.

 Maximum Frame Size values in ACCEED 1102/04: [1522, 2048 or 10240 Bytes]

The maximum frame size on the WAN ports is limited to 2048 Bytes. This limitation is
related to the aggregation function (PAF).
 If the maximum frame size is set to 1522 Bytes, untagged frames up to 1518 Bytes are
processed. This applies to the VLAN Unaware and VLAN Aware mode.

8.3.1.2 LAN Ports Power Save

If this option is enabled, the power output level of all electrical RJ-45 ports is automatically reduced.

 The Power Save mode is applicable only for twisted pair cables up to 30m

A3118-X642-R612-01 179 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Individual Switch Port Settings

The LAN switch ports offer various individual settings which are explained below.
The SFP, the Backplane, the LAG and the WAN switch port offer a subset of these settings.
The picture below shows the default setting for the LAN port P1. The shown MAC address is specific
to this LAN port P1.

Figure 8-6 Individual switch port settings

The following parameters can be configured:

A3118-X642-R612-01 180 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Enable
Enables or shuts down the port
 Mode
Defines port speed and duplex operation
Auto Negotiation port speed and duplex operation is negotiated with peer port
10MBit/s Full Duplex port speed and duplex operation is forced to these values
10MBit/s Half Duplex port speed and duplex operation is forced to these values
100MBit/s Full Duplex port speed and duplex operation is forced to these values
100MBit/s Half Duplex port speed and duplex operation is forced to these values
 Force Full Duplex
If enabled, the MAC transmits with full duplex independently of the auto-negotiation result. This
means, if a device with auto-negotiation disabled is connected to this port, the auto-negotiation will
discover the speed correctly, but the duplex mode cannot be determined and by default would
fallback to half duplex. This duplex result is then ignored by the MAC and forced to full duplex.
 Port Type
RJ45 interface pinout definition
Auto-MDI/MDIX Automatically detects the required cable connection type (straight-through or
crossover) and configures the connection appropriately
MDI Port Medium Dependent Interface port, typically used on the end devices
MDIX Port Medium Dependent Interface Crossover port, typically used on switches

 Description
Individual port description with up to 64 characters, e.g. service name or location.

 Advertised Modes
Restrict port speed and duplex operation combinations for negotiation with the link partner
Only applicable when the Auto Negotiation mode is enabled

 Flow Control
Enables the Flow Control mechanism by sending out "PAUSE" frames (full duplex operation) or
using backpressure (half duplex operation)
Please note that in case of electrical SFPs, flow control is available but the “flow control status” is
void.

 Ingress Rate Limit Enable

The below ingress rate configurations only take effect if enabled here

 Ingress Rate Limit Configuration

The packets with the traffic type(s) selected here are discarded randomly if the defined ingress
rate limit is reached. ( 8.3.2.1)

 Ingress Rate Limit [64 … 1’000 … 100’000 kbit/s, step: 1]

Defines the Ingress rate limit, when packets are discarded randomly. The granularity of the
ingress rate limit is 1 kbit/s.

 LFP Target [A, B, C, D, E]

The LFP target group which will be notified if the link of this port goes down.
The possible LFP target groups are: A, B, C, D and/or E ( 8.3.2.2)

 LFP Sources
All selected LFP sources are monitored. If at least one LFP source is active, this port will be set to
down to signal the counter device on this Ethernet link an LFP alarm. Additionally the “LFP” alarm
is raised.
If all selected LFP sources change to inactive, this Ethernet link will be restored and the “LFP”
alarm cleared.

A3118-X642-R612-01 181 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.3.2.1 Ingress Rate Limit

The ingress rate for the LAN, SFP and Backplane ports can be limited to the defined rate. If this
defined rate limit is exceeded, the arriving packets are discarded randomly to keep the defined rate
limit.

With the "Ingress Rate Limit Configuration" the ingress traffic type is analysed and the packets with the
selected traffic type are discarded in case the ingress rate limit is exceeded.
Traffic Types are recognised based on the destination MAC address of the packets.

Unicast: Specific destination MAC address existing in MAC table

Unknown Unicast: Packets with destination MAC address not existing in the MAC table are sent
to all ports via "unknown unicast"
Multicast: Packets with multicast destination MAC in the range starting at
[01-00-00-00-00-00] up to [01-ff-ff-ff-ff-ff]
Broadcast: Packets with destination MAC address [ff-ff-ff-ff-ff-ff]

 Limiting multicast or broadcast packets can be used to implement storm protection.

A3118-X642-R612-01 182 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.3.2.2 Link Failure Propagation

Link Failure Propagation (LFP) is a proactive way to react to a loss situation on any Ethernet port or
upon connectivity loss of an Ethernet path by shutting down Ethernet ports defined in the targeted LFP
group. Five individual LFP groups can be configured, containing one, several or all Ethernet ports to
be shut down in case a LFP event occurs.
Please note that electrical SFP do not react on LFP alarms and therefore can not be used as LFP
target.
LFP allows devices connected to the Ethernet ports of the ACCEED unit, such as a switch with
spanning tree or link aggregation, to react to a link or path failure.

The sources to trigger an LFP and therefore initiate a forced link down of Ethernet ports are:
 LAN, SFP, BPL and LAG ports (“no link” alarm)
 WAN ports (“aggregation loss” or “partial aggregation loss” alarm)
 SOAM-MEP (“SOAM-RemoteCCM” alarm or reception of SOAM CSF frames,  9.2.1.4)

LFP configuration of the LAN, SFP, BPL and LAG ports

 LFP Target: The targeted LFP group is configured here.

In the example below, LFP group D shall be targeted if the link if port P1 goes down.
LFP Sources: The selected port is assigned to the LFP sources.
In the example P1 is assigned to LFP group B and E.

LFP configuration of the WAN ports

 LFP Trigger: The PAF loss criteria is configured here.

 PAF Aggregation Loss: if all SHDSL links of the PAF failed
 PAF Partial Aggregation Loss: if one or more of the SHDSL links of the PAF failed
LFP Target: The LFP group is selected here.
In the example below, the Ethernet ports assigned to LFP group E are forced down, if the
PAF assigned to the port WAN1 has an aggregation loss. Thus, this service to the
customer is not available any more.

A3118-X642-R612-01 183 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

LFP configuration of SOAM-MEP

 LFP Target: The LFP group configured here is notified if the connectivity on the path
between the MEPs is interrupted and shuts down the Ethernet ports in the selected target
group. The LFP target group is also triggered upon reception of SOAM CSF messages (
9.2.1.4)

A3118-X642-R612-01 184 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

LFP Example:

Figure 8-7 Link Failure Propagation example

The example in the above figure shows an ACCEED unit with the WAN1 interface being the LFP
source. Port P1 and P2 are assigned to the LFP group A.
If a loss is detected on interface WAN1 as indicated with the red cross, the port P1 and P2 are shut
down and report a forced shutdown state accordingly.

8.3.2.3 LAG
LAG (Link Aggregation Group) in ACCEED 1102/04 allows combining up to 4 links to increase the
throughput and provide redundancy in case one link fails.
ACCEED 1102/04 provides two LAG interfaces on which it is possible to aggregate statically (static
LAG) or via LACP (Link Aggregation Control Protocol Active or Passive modes) any SFP interfaces and
any electrical ports P1, P2, …, Px and BPL1.

The LAG is a logical entity that can be configured and used as a physical port. When 1 physical ports is
added to a LAG entity, then all the setting available under the port configuration are not used anymore.
This is true for all the settings but the Flow control, which can be still configured on the port level of the
LAG members.

The WAN port of the ACCEED 1102/04 cannot be part of the LAG. This limitation is
 mainly due to the different physical and electrical characteristic of the SHDSL WAN ports
compared to the Ethernet LAN ports.

Packets sent to the LAG are distributed over the active ports according to the LAG hash algorithm.
The distribution algorithm is based on the combined Layer 2, Layer 3 and Layer 4 packet header
information.

LAG is configured by:

1. Adding the ports to the LAG in Ethernet/Switch_Local/LAG[x]/Aggregation_Ports[]
2. Setting the LACP mode in Ethernet/Switch_Local/LAG[x]/
3. Enabling the LAG function in Ethernet/Switch_Local/LAG[x]/,

A3118-X642-R612-01 185 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The link OAM of all involved ACCEED 1102/04 ports in the LAG are automatically enabled and set to
configuration mode for LAG ports.

8.3.2.3.1 LAG Aggregation port configuration

In Ethernet/Switch Local/LAG/LAG[x]/Aggregation Ports[] it is possible to add ports to the LAG and
check the status of the LACP protocol.

 Ethernet/Switch Local/LAG/LAG1/Aggregation Ports[]

Figure 8-8 Aggregation_Ports[] windows

Any LAN; SFP and Backplane ports can be added to the LAG using the button “Add”, while the
configuration can be checked through the following parameters.

 Index
Index in aggregation list.
 Port
Shows the member port of this link aggregation group.

 Actor Operational System ID

System ID of the actor.
 Actor Operational Key
Operational key of the actor.
 Actor Operational System ID
System ID of the actor.
 Actor Operational State
Operational key of the actor.
- Expired The receive state machine is in the 'expired' state.
- Defaulted The receive state machine is using defaulted operational partner
information, not information recieved in a LACPDU
- Distributing Distributing of outgoing frames is enabled.
- Collecting Collecting of incoming frames is enabled.
- Synchronized The link is allocated to the LAG and is associated to an aggregator.
- Aggregateable This link is considered to be 'aggregateable' for aggregation, and is
not considered an 'individual' link.
- Short Timeout LACP uses the short timeout for this link.
- Active LACP is in active mode.

A3118-X642-R612-01 186 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Partner Operational System ID

System ID of the partner.
 Partner Operational Key
Operational key of the partner.
 Partner Operational System ID
System ID of the partner.
 Partner Operational State
Operational key of the partner.
- Expired The receive state machine is in the 'expired' state.
- Defaulted The receive state machine is using defaulted operational partner
information, not information received in a LACPDU
- Distributing Distributing of outgoing frames is enabled.
- Collecting Collecting of incoming frames is enabled.
- Synchronized The link is allocated to the LAG and is associated to an aggregator.
- Aggregateable This link is considered to be 'aggregateable' for aggregation, and is
not considered an 'individual' link.
- Short Timeout LACP uses the short timeout for this link.
- Active LACP is in active mode

8.3.2.3.2 LAG port configuration

At the location Ethernet/Switch Local/LAG/LAG[x] the LAG port configuration can be set.

 Ethernet/Switch Local/LAG/LAG1

A3118-X642-R612-01 187 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-9 LAG port settings

The following parameters can be configured:

 Enable
Enables or shuts down the port
 Description
Individual port description with up to 64 characters, e.g. service name or location.
 Available Bandwidth
Shows the currently available bandwidth for the LAG port

 LACP Mode
Defines the LACP (Link Aggregation Control Protocol) activity. If LACP is disabled, the ports are
aggregated statically.
Active LACP is enabled and set in Active Mode.
Passive LACP is enabled and set in Passive Mode.
Disabled LACP is disabled. The port works with static LAG.
 Period
Defines the time between the transmission of LACP frames
1s An LACP frame is sent every second (fast LACP)
30s An LACP frame is sent every 30 seconds (slow LACP)
 Aggregator State
The aggregator state is "up" if at least one aggregation port is collecting or both collecting and
distributing, and "down" otherwise

 Ingress Rate Limit Enable

The below ingress rate configurations only take effect if enabled here

 Ingress Rate Limit Configuration

The packets with the traffic type(s) selected here are discarded randomly if the defined ingress
rate limit is reached. ( 8.3.2.1)

 Ingress Rate Limit [64 … 1’000 … 100’000 kbit/s, step: 1]

Defines the Ingress rate limit, when packets are discarded randomly. The granularity of the
ingress rate limit is 1 kbit/s.

 LFP Target [A, B, C, D, E]

The LFP target group which will be notified if the link of this port goes down.
The possible LFP target groups are: A, B, C, D and/or E ( 8.3.2.2)

 LFP Sources
All selected LFP sources are monitored. If at least one LFP source is active, this port will be set to
down to signal the counter device on this Ethernet link an LFP alarm. Additionally the “LFP” alarm
is raised.
If all selected LFP sources change to inactive, this Ethernet link will be restored and the “LFP”
alarm cleared.

 MAC Address
MAC address of this port.

8.3.2.3.3 Configuration example

A3118-X642-R612-01 188 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The figure below shows a LAG configuration between two ACCEED 1102/04 desktop units as it is
presented in the LCT+.

Figure 8-10 LAG configuration

As you can see from the picture, the ports SFP1 and SFP2 belong to the LAG1 interface of the ACCEED
on the left, while the Port P1 and P2 belong to the LAG 1 interface of the ACCEED on the right.

8.3.2.4 Power over Ethernet (PoE)

Not Applicable.
Ethernet Loopbacks
8.3.3.1 Port Loopback
ACCEED 1102/04 offers the possibility to loop the frames that are about to leave the switch at the end
of the egress pipeline back into the ingress pipeline of the same port.
This loopback is configured individually for each port:

A3118-X642-R612-01 189 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/<port>/Loopback
In the Fault / Maintenance tab of the table area, select “Port Loopback Enable”.

An active loopback is indicated with the “Port Loopback State” parameter. Additionally, the
inward facing loopback arrow of the corresponding port turns red in the Ethernet view.

When a port is in loopback mode, it affects all frames that are normally leaving this port. The external
link of a port with active port loopback is forced down.

The port loopback is not available at the WAN1 port of an ACCEED 1102/04 in NT mode, since this
would interrupt the management connection and therefore turn the device inaccessible.

There are four additional parameters that can be configured for the port loopback:

A3118-X642-R612-01 190 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Type (Timed/Permanent)
Timed – The Loop will be active for the time defined in duration or a reboot
Permanent – The Loop will be active till the next reboot
 Duration (1 .. 1440 minutes)
Number of minutes which the port loop is active
 Swap MAC Addresses
Disabled
MAC addresses are not swapped for the looped frames. MAC address learning
should therefore be disabled; otherwise all looped frames will be discarded. VLAN
modifications in the ingress pipeline are possible
Enabled (VLAN Tags Modifiable)
Source and Destination MAC addresses are swapped for all frames and they are
forwarded to the “Redirected Port”. Existing VLAN tags will be tunneled and therefore
preserved, but it is possible to modify the primary VLAN ID in the ingress pipeline, e.g.
to add an additional VLAN tag.
Enabled (VLAN Tags Not Modifiable)
Source and Destination MAC addresses are swapped for all frames and they are
forwarded to the “Redirected Port”. No VLAN modifications or additions are possible.

 Redirected Port
Egress port for the looped frames. This is only relevant if “Swap MAC Addresses” is enabled.

The port loopback is a maintenance function. For this reason, the maintenance LED on
 ACCEED 1102/04 will be on whenever at least one port loopback is active.
After a reboot, all loopbacks will be deactivated, regardless of their state before the reboot.

8.3.3.2 VLAN based Loopback

ACCEED 1102/04 offers the possibility to loop the frames with specific VLAN tags that are about to
enter the switch at the beginning of the ingress pipeline back into the egress pipeline of the same port.
This loopback is configured individually for each port:

A3118-X642-R612-01 191 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/<port>/VLAN/Ingress/Loopback
In the Fault / Maintenance tab of the table area, select “VLAN Loopback Enable”.

An active loopback is indicated with the “VLAN Loopback State” parameter. Additionally,
the outward facing loopback arrow of the corresponding port turns red in the Ethernet view.

When the VLAN loopback mode is active, all frames that are not caught by the loopback method will
be forwarded normally to the bridge.
Frames that are looped are not matched by any ingress policies or VLAN filters.

There are some additional parameters that can be configured for the port loopback:

 Primary VLAN ID (Any, 1 .. 4094)

Specifies a primary VLAN ID defined in the local VLAN Table which shall be looped.
“Any” loops frames with any primary VID.
 Secondary VLAN ID (Any, 1 .. 4094)
Specifies a secondary VLAN ID defined in the local VLAN Table which shall be looped.
“Any” loops frames with any or no secondary VID.
 Type (Timed/Permanent)
Timed – The Loop will be active for the time defined in duration or a reboot
Permanent – The Loop will be active till the next reboot
 Duration (1 .. 1440 minutes)
Number of minutes which the port loop is active

A3118-X642-R612-01 192 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Tunnel VLAN
Optionally the looped frames can be put into a VLAN tunnel (an additional tunnel VLAN tag is
added). The port where the loopback is active must me member of the tunnel VLAN in the VLAN
database.
 Tunnel VLAN ID (1 .. 4094)
VLAN ID used if “Tunnel VLAN” is enabled.
 Swap MAC Addresses
Disable
MAC addresses are not swapped for the looped frames.
Enable
Source and Destination MAC addresses are swapped for all looped frames and these
frames are forwarded to the egress of this port.

The VLAN loopback is a maintenance function. For this reason, the maintenance LED on
 ACCEED 1102/04 will be on whenever at least one VLAN loopback is active.
After a reboot, all loopbacks will be deactivated, regardless of their state before the reboot.

A3118-X642-R612-01 193 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

L2 Control Protocols
The following table shows how ACCEED 1102/04 handles different layer 2 protocols. The behavior is
configurable on a per port basis:
 Tunnel the Ethernet Control Protocol frames are forwarded transparently
 Discard the Ethernet Control Protocol frames are discarded
 Peer the Ethernet Control Protocol frames are terminated / peered in the control
plane
 Tunnel (L2PT) the Ethernet Control Protocol frames are encapsulated using a special MAC
address and send across the network (see  8.4.6 for more details)

Discard
Tunnel

Tunnel
(L2PT)
Types of Ethernet frames / layer 2 control protocols

Peer
MAC-DA: L2PT   
IEEE 802.AB - Link Layer Discovery Protocol (LLDP): 01-80-C2-00-00-0E   
Multicast address: 01-80-C2-00-00-3x (x is between 0 - F)   
IEEE 802.1D und 802.1D-2004 - MAC bridges and Spanning Tree   
Protocol - STP
IEEE 802.1w - Rapid Spanning Tree Protocol (RSTP)   
IEEE 802.1s – Multiple Spanning Tree Protocol (MSTP)   
IEEE 802.1Q - Virtual LANs  
IEEE 802.1Qay  
IEEE 802.1p - Traffic Class Expediting and Dynamic Multicast Filtering  
IEEE 802.1ag - Ethernet Service OAM - Connectivity Fault Management   
(CFM)
ITU-T Y.1731 - OAM Functions and Mechanisms for Ethernet-based   
Networks
IEEE 802.1ah Provider Backbone Bridges (MAC-in-MAC)  
IEEE 802.1X - Port Based Network Access Control  
IEEE 802.3ad - Link Aggregation Control Protocol (LACP)   
IEEE 802.3ah - Ethernet in the First Mile (EFM) / Ethernet Link OAM  
IEEE 802.3x - Flow Control 
Generic Attribute Registration Protocol (GARP)  
Cisco VTP   
CDP   
Table 6 ACCEED 1102/04 Layer 2 Control Protocol handling

A3118-X642-R612-01 194 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/xxx Ports/yyy/L2 Control Protocols

The layer 2 control protocol parameters are set per single protocol to tunnel or discard

The default values are shown in the picture above.

The following parameters cannot be changed:

 Flow control pause frames [Peer]

  Slow protocols subtype 3 (Link OAM)

 Slow protocols subtype 0x0A (ESMC)
[Peer] if enabled, [Discard] if disabled
[Peer] if ACCEED unit with SyncE
[Discard] if ACCEED unit without SyncE

A3118-X642-R612-01 195 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.4 Switch Control

This chapter describes the switch control features.
The picture below shows the respective stages in the reference model.

Figure 8-11 Building block – switch control

Forwarding Database

The ACCEED forwarding database can store up to 16k MAC addresses.

The switch can operate in 2 different VLAN modes, VLAN Unaware and VLAN Aware.
For more information on these two modes please refer to chapter  8.5.1

In VLAN Unaware mode one MAC address table stores the source MAC addresses learned from the
packets received on all ports of the switch. The related VLAN ID is always 1 which is the default VLAN
ID. This MAC address table can store up to 16k MAC addresses. The switching is done solely based
on the MAC address. This behavior is also known as Shared VLAN Learning (SVL).

In VLAN Aware mode, a MAC address table is maintained for each VLAN ID. The sum of all MAC
addresses in these VLAN related MAC address tables can not exceed 16k. The switching is done
based on the MAC address and the related VLAN ID. This behavior is also known as Independent
VLAN Learning (IVL).

Figure 8-12 ACCEED - VLAN learning modes

The ACCEED 1102/04 MAC table can be read out with the LCT+ and saved as text file. It can also be
manually flushed (all entries are deleted).

A3118-X642-R612-01 196 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 The `MAC Table` and `MAC Table Flush` buttons are located in the LCT+ dialogue `Switch
Local` and `Switch EFM-NT`

Figure 8-13 ACCEED MAC address Table (VLAN aware mode)

If the maximal number of 16k MAC addresses in the data base is reached, packets arriving
 with addresses not yet in the MAC address table are flooded to all ports within the same
VLAN.

A3118-X642-R612-01 197 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Learning Mode
There are two learning modes configurable:
 Automatic learning: learning mode=automatic, aging time=10..600
Each source MAC address is stored with its primary VID and ingress port in the forwarding
database. In case there is already an equal entry existing the aging is renewed. If the MAC table
reaches its maximum limit (16k) the source MAC will not be learned, but bridged in its primary VID.
The learning is done in hardware at wire speed.
 Limited learning: learning mode=limited, aging time=10..600, number of allowed MAC=1..128
All new source MAC addresses (not in forwarding database) will be learned by the CPU. If the
maximum number of allowed MAC addresses per switch is reached, the packets will be dropped.
This feature is designed for the NT, CS and CPE, where typically one customer is attached to the
service.
 Disabled learning: aging time=learning disabled
No MAC address will be learned. All frames will be bridged within their primary VLAN group. The
forwarding is done in wire speed.

Aging Time
The MAC Table Aging Time defines how long the learned MAC address is kept in the database if this
MAC address is no longer learned on the corresponding ingress port.

The MAC address learning can be switched off by choosing Learning Disabled as MAC Table Aging
Time. With this setting the switch becomes transparent and acts like a hub.

 The value range for MAC table aging time is [Learning Disabled, 10 … 300 … 600] seconds

A3118-X642-R612-01 198 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Port isolation
To prevent switching between specified ports, these ports can be isolated from other ports.
This is done by restricting the allowed egress ports for frames entering via a specific port.
Typical applications are:
 WAN Isolation (Rooted-Multipoint EVC)
 Multi EPL Mode (LAN1 - WAN1 connection is isolated from LAN2 - WAN2 connection)

The example (Figure 8-14) shows that the traffic of customer 1 (orange) connected on WAN1 using
transmit ports P1 and SFP1 is separated from the traffic of customer 2 (green) connected on WAN2
using transmit ports P2 and P3.

To separate traffic of different customers using the same switch port, VLANs must be used. Please
refer to chapter  8.5.1

Figure 8-14 port isolation

 Ethernet/Switch Local/xxx Ports/1102/04/Port Isolation

Please note that the port isolation must be configured for all ports belonging to the isolated
group.
The example below shows the port isolation configuration for port WAN1 of the orange
customer in the above figure. Port P1 and SFP1 must be configured accordingly to
complete the isolation.

To separate traffic of different customers using the same switch port, VLANs must be used. Please
refer to chapter  8.5.1

A3118-X642-R612-01 199 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 If Link OAM is turned on for a specific port, this port must be enabled in its own port
isolation table to allow a Link OAM loopback.

Port mirroring
Port mirroring allows to duplicate the ingress and/or egress traffic of a port (mirror source port) and to
send it to a different port (mirror analyzer port).

Figure 8-15 port mirroring example

ACCEED supports port based mirroring. All packets without MAC-level errors of the mirror source port
are duplicated and sent to the mirror analyzer port.
ACCEED also supports flow based mirroring. See  8.7.3.5

 Switch Local/Mirroring
Port mirroring can be configured in the LCT+ in the Switch dialogues (local and EFM-NT)

A3118-X642-R612-01 200 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

L2PT
Layer 2 Protocol Tunneling (L2PT) allows to tunnel Layer 2 BPDUs such as STP, LACP, and Cisco
CDP across a network avoiding that intermediate switches can intercept and interpret them. With this
feature a Service Provider can separate its own network from customer networks without blocking the
transmission of the L2 BPDUs.

8.4.6.1 How L2PT works

In order to better understand the basic of L2TP consider Figure 8-16 as example. There are two
customer locations equipped either with ACCEED or 3rd party devices acting as demarcation points. At
each demarcation point L2PT is enabled in order to provide a transparent L2 tunnel between the
customer sites. Each demarcation point does two types of actions:
- Tunnel (L2PT), that consists in manipulating the destination MAC Address of the BPDUs
coming from the UNI and sending them to the NNI interface.
- Peer (L2PT), that consists in restoring the BPDUs destination MAC Address of packets
arriving at the NNI and sending them to the customer UNI interface.
Any port of the ACCEED can act both as Tunnel (L2PT) and as Peer (L2PT).

Figure 8-16 L2PT example

8.4.6.2 L2PT configuration

L2PT configuration is done in three steps:
- Global switch configuration, in order to set parameters such as the MAC Address used for
tunneling or Drop Threshold,
- L2PT Port configuration, in order to configure the Egress port,the Egress VLAN and eventually
the Default VLAN TAG,
- L2CP Port configuration for UNI and NNI, in order to set which BPDUs must be tunneled or
peered respectively.
The three configuration steps are illustrated below.

A3118-X642-R612-01 201 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.4.6.3 Global Switch Configuration

 Ethernet/Switch […]/L2PT

The following parameters can be configured:

 Assigned Cos Value

PCP value of encapsulated and decapsulated L2PT frames when sent VLAN tagged
 Assigned Queue [0 .. 5 .. 7]
Transmit Queue for encapsulated and decapsulated L2PT frames
 Drop Threshold [10, …, 100, …, 300]
Defines the maximum allowed frame rate of L2CP frames to be tunneled

 MAC Address Type

MAC Address type used for L2PT frames
“Albis L2PT” MAC Address standard Albis: 01:1A:D0:00:00:01
“Cisco L2PT” MAC Address standard Cisco: 01:00:0C:CD:CD:D0
“User Defined” User defined MAC Address, specified in the parameter MAC Address
 MAC Address
The MAC address of L2PT tunneled frames will be replaced with this MAC address

In the figure above the Global Switch configuration is set in order to use the Albis standard MAC
address in order as L2PT destination MAC Address. Furthermore the CoS 5 is assigned to L2PT
frames, that cannot be sent with a rate higher than 100 Frame/s.

8.4.6.4 L2PT UNI port configuration

 Ethernet/Switch […]/<port>/ L2PT

A3118-X642-R612-01 202 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The following parameters can be configured:

 Egress Port
Port where L2PT encapsulated and decapsulated frames will be forwarded to
 Tunnel VLAN
If enabled L2PT encapsulated frames will be VLAN tagged
 Tunnel VLAN ID
L2PT encapsulated frames will be tagged and forwarded in this VLAN
 Add Default VLAN
Untagged L2PT encapsulated frames that will additionally get a default VLAN tag
 Remove Default VLAN
The default VLAN tag of L2PT decapsulated frames will be removed
 Default VLAN ID
Untagged L2PT encapsulated frames will be tagged and forwarded in this VLAN

In the figure above the L2 BPDUs entering port P2 are tunneled in the VLAN 4000 and sent to port
SFP1. If the L2 BPDUs are untagged, then the default VLAN tag 8 is added, resulting in a double
tagged BPDU.
On the reverse direction, L2PT BPDUs coming from SFP1 are sent to the customer throughout port P2
removing the Tunnel tag 4000. If the L2PT BPDUs are double tagged and the inner tag is 8 (Default
VLAN ID), than the inner tag is removed and the frame is sent untagged to the customer.

8.4.6.5 L2CP port Configuration

 Ethernet/Switch […]/<port>/L2CP

L2PT BPDU Tunneled

A3118-X642-R612-01 203 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

L2PT BPDU discarded

More information about the L2CP configuration can be found in  8.3.4

The figures above show a typical configuration of L2CP of the Tunnel port and of the Peer port.

A3118-X642-R612-01 204 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.5 VLAN
This chapter describes the VLAN modes and the port based VLAN manipulation options. The
reference model below shows the respective stages that are addressed.

Figure 8-17 Building block – VLAN

VLAN mode
ACCEED can be configured to work in the global modes VLAN unaware or VLAN aware.
The VLAN unaware mode is a transparent mode that can evaluate the VLAN tags, remark .1p bits but
does not change the VLAN ID or TPID information of the packet.
In the VLAN aware mode various VLAN manipulations like tagging, stacking, translation and swapping
can be configured. The port based VLAN manipulation options are explained in this chapter.
The flow (service) based VLAN manipulation options are explained in chapter  8.7.3

8.5.1.1 VLAN unaware mode

In this mode VLAN tags are evaluated, but never changed (except for .1p bits). If present, VLAN tags
are transparently forwarded

 Changing the configuration from “VLAN aware” to “VLAN unaware” does not erase the
VLAN database but all ports are configured to be member of VLAN1.

A3118-X642-R612-01 205 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.5.1.2 VLAN aware mode

In the VLAN aware mode various VLAN manipulations can be applied to the packets on the ingress and
egress paths. The simplified figure below shows possible VLAN manipulation scenarios that can be
realized with ACCEED. The following chapters describe how the global VLAN settings are defined and
the port based VLAN manipulations can be applied.

Figure 8-18 ACCEED 1102/04 VLAN manipulation scenarios

 The VLAN mode can be configured in the LCT+ in the Switch dialogues (local and EFM-
NT)

VLAN Tag Naming Convention in ACCEED

In the VLAN aware mode, ACCEED supports the recognition and modification of the two outermost
VLAN tags of a packet. The packets are identified and further processed based on these two VLAN
tags.
For single tagged packets, only this one tag is accessed accordingly.

 Primary and Secondary VLAN tag

Each packet arriving on the ingress port is assessed and the two outermost VLAN tags
(if existing) are assigned to "Primary" and "Secondary" tag.
The assignment is done based on the TPID(s) and can be configured for each port
individually which provides maximal flexibility for packet processing within the ACCEED
device.

Bridging decisions in ACCEED are always done based on the Primary VLAN tag.

 The existence of a Primary VLAN ID is therefore mandatory.

The Primary and Secondary tag assignment criteria is the EtherType (TPID) or the
configured Port VLAN ID in case of the untagged frames.

A3118-X642-R612-01 206 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Global VLAN settings

8.5.3.1 VLAN database

The VLAN database maintains the configured VLAN IDs with their member ports and tagging
commands.
The VLAN database must be defined for each ACCEED device individually.

The VLAN ID range that can be defined in the database is [1 … 4094]

 VLAN ID 1 is the default value and is always present in the VLAN Database.
VLAN ID 0 will be overwritten with the port VLAN ID without losing the 1.p bits information.
VLAN ID 4095 is reserved according to IEEE 802.1Q and can therefore not be used.

 Ethernet/Switch Local/VLAN/Database[]
VLANs are added to the Database via the Add button by entering the desired VLAN ID.
VLAN IDs or a VLAN ID range can be entered in the same input line (see below).
Additionally, a name can be assigned to each VLAN ID. Please note, that this name has
only local relevance.

A3118-X642-R612-01 207 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Additionally to the VLAN ID definition, the "egress tagging mode" for each port and VLAN ID relation
needs to be set.
Please note that the setting in the LCT+ reflects the modification done to the packets on the egress
port.
The packets leaving on the egress port can have various tagging formats (e.g. untagged, single
tagged, double tagged). These packets are modified according to the egress tagging mode.

 Ethernet/Switch Local/VLAN/Database[]

The default setting for the "egress tagging mode" is "Untagged".

There is one special case: tagging mode "-" (Discard)
A port set to this mode is not member of the corresponding VLAN. That means:
 1) Packets with this Primary VLAN ID are not distributed to this port anymore
2) Packets arriving from that port with the matching Primary VLAN ID are dropped instantly
at the ingress.

The result of the applied "egress tagging mode" are explained in the tables on the next pages.

A3118-X642-R612-01 208 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: - (Discard)

All packets with the respective primary VLAN are discarded on the egress and ingress path of the
respective port.

Figure 8-19 Egress Tagging Mode: - (Discard)

A3118-X642-R612-01 209 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Untagged

All tags recognized in the received packet are removed (primary and/or secondary tag)

Figure 8-20 Egress Tagging Mode: Untagged

A3118-X642-R612-01 210 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Add Primary Tag

The packet is leaving the switch with an added primary tag evaluated on the ingress path.
If the packet already contained a primary and/or secondary tag, these tags are preserved.

Figure 8-21 Egress Tagging Mode: Add Primary Tag

A3118-X642-R612-01 211 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Primary Tag Only

The packet is leaving the switch with the primary tag evaluated on the ingress path.
The secondary tag is removed if present.

Figure 8-22 Egress Tagging Mode: Primary Tag Only

A3118-X642-R612-01 212 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Secondary Tag Only

The packet is leaving the switch with the secondary tag evaluated on the ingress path.
The primary tag is removed if present.

Figure 8-23 Egress Tagging Mode: Secondary Tag Only

A3118-X642-R612-01 213 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Remove Outer Tag

The packet is leaving the switch without the outer tag received on the ingress port.
This is done regardless of the primary or secondary tag information.

Figure 8-24 Egress Tagging Mode: Remove Outer Tag

A3118-X642-R612-01 214 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Inner Primary Tag, Outer Secondary Tag

The packet is leaving the switch with the primary and secondary tag evaluated on the ingress path. If
the outer tag was evaluated as primary and the inner tag as secondary tag – a tag swapping takes
place.

Figure 8-25 Egress Tagging Mode: Inner Primary, Outer Secondary

A3118-X642-R612-01 215 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Egress tagging mode: Inner Secondary Tag, Outer Primary Tag

The packet is leaving the switch with the primary and secondary tag evaluated on the ingress path. If
the inner tag was evaluated as primary and the outer as secondary tag – a tag swapping takes place.

Figure 8-26 Egress Tagging Mode: Inner Secondary, Outer Primary

A3118-X642-R612-01 216 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Example: VLAN DB – Egress Tagging Mode

The following example illustrates the unidirectional flow of an untagged packet arriving at LAN port P3
which shall leave the switch on port WAN1 with a single tag of VLAN ID 10.

Figure 8-27 VLAN DB example

8.5.3.1.1 VLAN ID 0 Secondary Tag

For the two tagging commands “Inner Primary Tag, Outer Secondary Tag” and “Inner Secondary Tag,
Outer Primary Tag”, the situation can occur that a secondary tag is not yet present at the ingress port.
The behavior in such situations is depending on the parameter
Ethernet/Switch […]/VLAN/Transmit VID 0 Secondary Tag
The following settings are possible
 Always
If no secondary tag is present, a secondary tag with VLAN ID 0 is added to the packet.
 Never
If no secondary tag is present, or if the secondary tag has VLAN ID 0, packets are transmitted with
a primary tag only
 Conditionally
If a secondary tag with VLAN ID 0 was already present at the ingress port, it is preserved. If a
secondary tag was not present, packets are transmitted with a primary tag only

A3118-X642-R612-01 217 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.5.3.2 Ingress / Egress Translation Table

The Ingress and Egress Translation Tables globally define the translation of the original primary VLAN
ID of a packet to its new translated primary VLAN ID.
The translation must be applied for each port individually for ingress and egress direction ( 8.5.4)
The example below shows the Ingress Translation Table. The Egress Translation Table can be
defined accordingly.

 Ethernet/Switch Local/VLAN/Ingress Translation Table[]

8.5.3.3 Tag Protocol Identifier List (TPID)

The TPID (also known as VLAN Ethertype) is defined in the first 2 Bytes of the VLAN tag and is used
to indicate which protocol is encapsulated in the payload of an Ethernet frame.
The globally defined list of Tag Protocol Identifiers (TPID) is used to classify the VLAN information of
the packets on the ingress port as primary and secondary tag.
The primary tag information is used as reference for the upcoming VLAN manipulations.

 Ethernet/Switch Local/VLAN/Tag Protocol Identifier List

The TPID List has 4 predefined TPID values and 2 user definable TPID values.

Predefined TPID Values

0x8100 VLAN acc. to IEEE 802.1Q
0x88A8 Stacked VLAN acc. to IEEE 802.1ad (Provider Bridge)
0x9100 Stacked VLAN acc. to IEEE 802.1 Q-in-Q (formally known as IEEE 802.1ad)
0x9200 Non standard value for Q-in-Q

A3118-X642-R612-01 218 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Port Based VLAN Settings

This chapter explains the port based settings that can be applied to define the VLAN tag handling for
the ingress and egress direction.
The Tag Protocol Identifier (TPID) list is used for the primary and secondary tag assignment.

 The port based VLAN settings are only applicable if the VLAN aware mode is enabled.

Ethernet/Switch Local/Port N/VLAN/Ingress

 (Where Port N can be LAN, SFP, Backplane or WAN port)
The following parameter can be defined for the port behaviour in the Ingress direction:

The Egress direction offers a sub set of these parameters only as shown in the picture
below

 Force Port VLAN ID

Enabling overwrites the VLAN ID identified as primary tag with the Port VLAN ID.
 Port VLAN ID [VLAN 1 … VLAN 4094]
Gets the primary VLAN ID, if packets do not contain a primary VLAN ID. E.g. untagged
packets or tunnelling enabled.
all VLAN IDs defined in the VLAN database can be assigned here
 Acceptable Frame Types
[All Frames, Primary Tagged Only, Untagged/Secondary Tagged only]
Defines the frame types that are accepted on this port.
 Translation Enable (Ingress and Egress)
Translation can be applied in Ingress and Egress direction as pictured in the reference model
in stage 3 and stage 7. Enabling this option translates the primary VLAN tag to the VLAN ID
defined in the translation table.
The ingress and egress translation table are defined in the global VLAN settings ( 8.5.3.2)
 Enable VLAN Tunnelling
With port based VLAN tunnelling all frames are treated as untagged and existing VLAN tags
are therefore preserved. Still port and flow based VLAN manipulation can be applied if
tunnelling is applied.
A3118-X642-R612-01 219 / 405
 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Tag Protocol Identifier (TPID) list – Ingress port

The TPID(s) of the packet entering this port are compared with the port specific TPID list.
If the TPID of the outer VLAN tag matches with one of the listed primary TPIDs, this VLAN tag
becomes the primary tag. The inner tag is assigned to the secondary tag accordingly.
For more information on the primary and secondary tag definition, see chapter  8.5.2 (VLAN Tag
Naming Convention in ACCEED)

The global TPID list ( 8.5.3.3) defines the values that are offered to define the primary and
secondary TPIDs for this specific port.

Ethernet/Switch Local/Port N/VLAN/Ingress/Tag Protocol Identifier

 (Where Port N can be LAN, SFP, Backplane or WAN port)

The ingress TPID list contains 4 Primary and 4 Secondary TPID values that can be set
Default value for primary and secondary TPID1 is 0x8100

Tag Protocol Identifier (TPID) list – Egress port

If the packets leaving on the egress port have an assigned primary and/or secondary tag, the TPID
values of these tags are set to the values defined in the table as shown below.

Ethernet/Switch Local/Port N/VLAN/Egress/Tag Protocol Identifier

 (Where Port N can be LAN, SFP, Backplane or WAN port)

The egress TPID list has 1 Primary and 1 Secondary TPID value that can be set
Default value for primary and secondary TPID is 0x8100

 If the egress tagging command for the primary VLAN is “Remove Outer Tag”, the TPID of
the inner tag will not be modified.

A3118-X642-R612-01 220 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

VLAN Filters
It is possible to filter specific traffic flows by their VLAN IDs and CoS values. These traffic flows can
then be either dropped, redirected or explicitly forwarded.

Ethernet/Switch…/ Port N /VLAN/Ingress/Filter

 (where Port N can be a LAN, LAG, SFP, Backplane or WAN port)
press the “Add” Button in the Configuration->ACCEED 1102/04 tab. A window pops up
where you can select an index for the new filter.

The VLAN filter configuration (

Figure 8-28) is divided into two sections, area : criteria selection and area : detailed parameter
configuration. For each of the selected criteria in area , the corresponding parameter is available in
area  for detailed configuration.

Figure 8-28 VLAN filter configuration

 Index [1..32]
Internal unique Filter ID
 Description

A3118-X642-R612-01 221 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Alphanumeric text with up to 32 characters

 Frame Command
“Forward” Forward all matching frames normally along the ingress pipeline
“Drop” Discard all matching packets immediately
“Redirect” Send all matching packets to the “Redirected Port”
“Redirect With MAC Swap” Send all matching packets to the “Redirected Port” and swap source
and destination MAC addresses
 Redirected Port
Destination port for redirected packets

 Criteria
Enable all relevant matching criteria. These are combined by mathematical “and”.

 Primary VLAN Tag Presence

“Present” Match, if the packet is tagged with a TPID defined in the Primary
TPID Group
 Primary VLAN ID [0...4094]
Match the exact value of VLAN ID within the primary VLAN tag
 Primary VLAN Priority (CoS) [0...7]
Match the exact value of the IEEE802.1p priority bits within the primary VLAN tag
 Secondary VLAN Tag Presence
“Present” match, if the packet is SVz or SV0 tagged
 Secondary VLAN ID [0...4094]
Match the exact value of VLAN ID within the secondary VLAN tag
 Secondary VLAN Priority (CoS) [0...7]
Match the exact value of the IEEE802.1p priority bits within the secondary VLAN tag

Up to 32 filters can be configured per port. They are applied in ascending order of their index, i.e. the
filter with the lowest index that matches an incoming packet is applied. If a packet does not match any
of the filters, or if there are no filters configured, the packet follows the ingress pipeline in its orderly
way.

The parameters “Primary VLAN Tag Presence” and “Secondary VLAN Tag Presence”
are both fixed to the value “Present”. This implies that VLAN filters can only be applied
 for double tagged packets. For single tagged and untagged packets, the mechanisms in
chapter  8.7.3 can be used.

The VLAN filter stage comes after the VLAN translation stage (but before the policing
 stage) in the ingress pipeline. Therefore, if VLAN translation is used, the new
(translated) primary VLAN ID has to be used in the VLAN filter.

A3118-X642-R612-01 222 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.6 Ethernet Switch Fault Management

All Ethernet Switch relevant alarms are described in chapter  12.3

A3118-X642-R612-01 223 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7 Ethernet Switch QoS handling

The ACCEED 1102/04 Ethernet switch provides comprehensive flow based QoS handling. QoS
mechanisms can be activated at various stages within the switch. Building blocks with QoS relevant
functionality are highlighted in Figure 8-29.

Figure 8-29 Building Block - QoS handling

At the ingress port , a set of QoS attributes is initialized for each packet. At the ingress policing
stage , traffic flows can be identified and processed independently. Here, those QoS attributes can
be modified, for example based on bandwidth profile conformance of the traffic flows. The same is
possible at the egress policing stage . Between the two policing stages there is the egress queuing
stage  which is responsible for traffic prioritization and shaping.

A detailed description on all involved stages is given throughout this section.

Packet QoS Attributes Set

Each packet that enters the ACCEED switch is immediately associated with a set of QoS attributes.
These attributes define which priority the packet is given internally but also how and if the QoS fields
(e.g. IEEE802.1p priority bits, IP DSCP field) in the packet are modified. The attributes are initialized at
the ingress port ( 8.7.2), but they can be modified at different stages in the switch pipeline.
 Transmit Queue Number
Egress queue which the packet is assigned to. Range 0 (lowest) to 7 (highest priority queue)
 Color
Color classification of the packet, can be green, yellow, or red. This attribute is used for metering
( 8.7.3.4)
 Remark CoS Decision
If “yes”, the corresponding field (.1p bits for CoS) of the packet header is modified (remarked)
according to the corresponding CoS attribute at stage .
 Class of Service (CoS)
IEEE802.1p priority bits that are set in the packet’s primary VLAN tag, if the “CoS remark decision”
attribute is “yes”. Range 0 to 7
 Remark DSCP Decision
If “yes”, the corresponding field (IP DSCP) of the packet header is modified (remarked) according
to the corresponding DSCP attribute at stage .
 DSCP Value
DiffServ Code Points (IP Priority), assigned if the “DSCP remark decision” attribute is “yes”. Range
0 to 63.

A3118-X642-R612-01 224 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Initial QoS Attribute Assignments

The QoS attributes described in the previous section are initialized at the ingress port, based on
information found in the packet headers (trusted mode) or according to the ingress port’s default
settings (untrusted mode).
 Ethernet/Switch […] /<port>/QoS/Ingress


 Trust Mode
“Untrusted” Assign QoS attributes according to port profile ( 8.7.2.1)
“Trust CoS Value Only” Assign QoS attributes according to the packet’s .1p bit value (if
trusted VLAN tag is found) and the global CoS profile ( 8.7.2.2)
“Trust DSCP Value Only” Assign QoS attributes according to the packet’s DSCP field (if it is
an IP packet) and the global DSCP profile ( 8.7.2.3)
“Trust DSCP/CoS Values” The packet’s .1p bit value and DSCP are used for QoS
assignment. If both are available, DSCP is used.
 Trusted VLAN Tag
“Primary VLAN Tag” In “Trust CoS Value” modes, use .1p bits from primary VLAN tag
“Secondary VLAN Tag” In “Trust CoS Value” modes, use .1p bits from secondary VLAN
tag
 Remark CoS [Yes / No] Initial remark decision for the packet’s .1p bits
 Remark DSCP [Yes / No] Initial remark decision for the packet’s DSCP value
 Default CoS [CoS 0 .. CoS 7] Initial CoS, if there is no trusted VLAN tag found in the packet. This
may result from Trust mode=”untrusted” or Primary TPID settings
different to the received ones.

For each of the 3 available trust modes (untrusted mode, CoS trust mode, DSCP trust mode), the
following initial QoS attribute values can be configured:
 Assigned Queue [0 .. 7] Transmit queue in the egress pipeline
 Assigned CoS Value [0 .. 7] IEEE802.1p priority bits that are set in the packet’s primary VLAN
tag. Only relevant if the “Remark CoS” attribute is set.
 Assigned DSCP Value [0 .. 63] DSCP value for IP packets Only relevant if the “Remark DSCP”
attribute is set.
 Assigned Initial Color [green, yellow, red]
Initial color for color aware metering ( 8.7.3.4)

 These are the initial QoS attributes, assigned to each packet. They may be modified in
the policing stages.

In untrusted mode, these attributes are configured in the port profile ( 8.7.2.1).
In CoS trust mode, they are configured in the global CoS profiles ( 8.7.2.2).
In DSCP trust mode, they are configured in the global DSCP profiles ( 8.7.2.3).

A3118-X642-R612-01 225 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7.2.1 Port Profile (Untrusted Mode)

If a port is in untrusted mode, the priotity bits of ingress packets with a valid primary tag ethertype are
stored in the CoS attibutes set. All other packets (e.g. untagged) get the Default CoS. This CoS value
can be addressed by any ingress policy in stage .
By entering the bridge (stage ) this CoS Value is overwritten with the attribute of the port profile. If
“remark CoS” is yes, the CoS will be remarked in the VLAN tag, too.

Figure 8-30 Ingress CoS profiles

 Ethernet/Switch […] /<port>/QoS/Ingress/Port Profile

8.7.2.2 CoS Profiles (CoS Trust Mode)

In CoS trust mode, QoS attributes are assigned according to the global CoS profiles, based on the
incoming packets .1p bits and DEI (drop eligibility indicator).
The mapping table under Ethernet/Switch […]/QoS/Ingress/CoS Profiles defines a QoS attribute set
for each combination of .1p bits and DEI.

In the CoS profiles, the term “CoS Value” stands for the .1p bits of the packet’s VLAN
 tag.

A3118-X642-R612-01 226 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-31 Ingress CoS profiles

8.7.2.3 DSCP Profile (DSCP Trust Mode)

In DSCP trust mode, QoS attributes are assigned according to the global DSCP profiles, based on the
DSCP field of the packet’s IP header.
The mapping table under Ethernet/Switch […]/QoS/Ingress/DSCP Profiles defines a QoS attribute
set for each possible DSCP value (6bit=64 values).

The DCSP profiles can only be applied to IP packets. For non-IP packets, the QoS
 attributes are initialized according to the CoS profiles (if Trust mode=“Trust DSCP/CoS
Values” and the received frame has a primary VLAN Tag), or the port profile.

A3118-X642-R612-01 227 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-32 Ingress DSCP profiles

Policing
As indicated in Figure 8-29, ACCEED 1102/04 features two policing stages, one in the ingress pipeline
and another one in the egress pipeline. In these stages traffic can be processed on a per-flow base.
A flow is a stream of packets that are classified equal with respect to certain user-defined criteria.
These can be attributes like VLAN tags, CoS, ingress or egress ports, specific values in the IP or TCP
headers, or any combination thereof.
A policy in ACCEED consists of a set of rules and a modifier. The rules define a flow that is treated by
the policy, while the modifier defines the action(s) that are performed on the flow. Policies can be
instantiated at any port in either the ingress or egress policing stage.

Flow = series of frames with a common attribute (e.g. VLAN ID, QoS, …)

 Rule
Modifier
= definition of the criteria that define a flow
= actions to be performed on a flow
Policy = treatment / processing of a flow with a modifier

A3118-X642-R612-01 228 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7.3.1 Policing Overview

The configuration of policies in ACCEED 1102/04 involves a number of steps, listed below. The
detailed configurations and parameters are indicated in the following sections.

Step 1: Create Rule(s)  8.7.3.2

 Ethernet/Switch […]/Policing/Rules/

Step 2 (optional): Create Bandwidth Profile  8.7.3.4

Ethernet/Switch […]/Policing/Bandwidth Profiles/

Step 3: Create Modifier  8.7.3.5

Define necessary actions and link the bandwidth profile (if desired)
Ethernet/Switch […]/Policing/Ingress Modifiers/
Ethernet/Switch […]/Policing/Egress Modifiers/

Step 4: Define Policy:  8.7.3.6

Combine one modifier with up to 8 rules
Ethernet/Switch […]/Policing/Ingress Policies/
Ethernet/Switch […]/Policing/Egress Polices/

Step 5: Apply Policy  8.7.3.7

Instantiate policy at the ingress or egress pipeline of a port
Ethernet/Switch […]/<port>/Policing/Ingress/Policy Map[]/
Ethernet/Switch […]/<port>/Policing/Egress/Policy Map[]/

8.7.3.2 Rules
Figure 8-33 shows an example of a typical Ethernet Packet with stacked VLANs, primary VLAN
tagged with ID=1 and secondary VLAN tagged with ID=5:

D S PV1 SV5 DATA X

DST SRC TPID Prio DEI VLAN ID TPID Prio DEI VLAN ID EType DATA FCS
6 byte 6 byte 2 byte 3 bit 1 bit 12 bit 2 byte 3 bit 1 bit 12 bit 2 byte x byte 4 byte
Figure 8-33 Layer 2 packet description

 DST Destination MAC Address

 SRC Source MAC Address
 TPID Tag Protocol Identifier (0x8100, 0x88A8, 0x9100, 0x9200, … user defined)
 Prio [0..7] User priority bits IEEE 802.1p
 DEI [0..1] Drop Eligibility Indicator carries the color of an ingress packet. Green = 0, yellow
& red = 1.
 VLAN ID [0..4094] Identifier of the Virtual LAN
 EType [0..0xFFFF] Ethertype defining the enveloped Protocol, e.g. IP (0x0800)
 DATA PDU
 FCS Frame check sequence

It is also possible to look deeper into the Packet structure, e.g. IP and TCP/UDP streams:

D S PVA SVz EType IP Header TCP / UDP DATA X

0x800 DSCP Proto SRC IP DST IP SRC DST
2 byte 6 bit 1 byte 4 byte 4 byte 2 byte 2 byte
Figure 8-34 Layer3/4 packet description

A3118-X642-R612-01 229 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 DSCP [0..63] DiffServ Code Points (IP Priority)

 Proto [0..255] enveloped IP Protocol like TCP or UDP
 SRC IP Source IP Address
 DST IP Destination IP Address
 SRC TCP/UDP Source Port of TCP/UDP Protocol
 DST TCP/UDP Destination Port of TCP/UDP Protocol

In ACCEED 1102/04, flows are identified by matching incoming packets with rules. These rules define
specific values for the packet fields listed above (or a subset of them).
Rules can be added or removed under Ethernet/Switch […]/Policing/Rules[] with the “Add” and
“Remove” buttons. Up to 200 different rules can be defined. They can then be used in the policy
definition ( 8.7.3.6)

The rule classification parameter section (

Figure 8-35) consists of area : matching criteria selection and area : the detailed parameter
area. By default all criteria in section  are disabled, except “Match All Frames” and section 
is empty. Criteria (e.g. Primary VLAN ID, Primary VLAN Priority) enabled in  get their detailed

A3118-X642-R612-01 230 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

parameters visible in section.

A3118-X642-R612-01 231 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-35 shows all criteria’s and parameters visible. The selected criteria’s are combined with a
logical ‘and’.

Ethernet/Switch […]/Policing/Rules[]

Figure 8-35 Rule configuration

 Rule ID [1..200]
Internal unique Rule ID.
 Description
Alphanumeric rule name with 32 characters. This name is also displayed in the tree view, and in
the policy configuration. It is recommended to use meaningful names for the rules, e.g. “VID=1”.

 Criteria
Select all relevant matching criteria. These are combined by logical “and”.

 Destination MAC Address and Destination MAC Address Mask

Match the range of destination MAC addresses that are described with MAC and mask.
E.g. MAC=00:00:00:00:00:00 and Mask=FF:FF:FF:FF:FF:F0
-> MAC-Range= 00:00:00:00:00:00 … 00:00:00:00:00:0F
 Source MAC Address and Source MAC Address Mask
Match the range of source MAC addresses that are described with MAC and mask.
E.g. MAC=01:00:00:00:00:00 and mask=FF:00:00:00:00:00
-> MAC-Range= 01:00:00:00:00:00 … 01:FF:FF:FF:FF:FF (match all Multicast)

A3118-X642-R612-01 232 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethertype [0x0...0x0800…0xFFFF]
Match the exact value of the Ethertype (describes the content of the Datagram)
 VLAN Tag Presence
“Secondary VLAN Tag or Untagged” match, if packets carry no primary VLAN tag
“Primary VLAN Tag or Priority Tag” match, if packets are PVA or PV0 tagged
 Primary VLAN ID [0...4094]
Match the exact value of VLAN ID within the primary VLAN tag
 Primary VLAN ID Priority [0...7]
Match the exact value of the IEEE802.1p Priority bits within the primary VLAN tag
 Destination IP Address and Destination IP Address Mask
Match the range of Destination IP Addresses that are described with IP and Mask.
E.g. IP=192.168.0.0 and Mask=255.255.0.0 -> IP-Range= 192.168.0.0 … 192.168.255.255
 Source IP Address and Source IP Address Mask
Match the range of Source IP Addresses that are described with IP and Mask.
E.g. IP=10.5.64.0 and Mask=255.255.192.0 -> IP-Range= 10.5.64.0 … 10.5.127.255
 IP Priority (DSCP) [0…63]
Match the exact Diff Serv Code Point (DSCP) value within the IP Packet
 IP Datagram Protocol [0…255]
Match the exact number of the enveloped IP Protocol, e.g. ICMP(1), TCP(6), UDP(17)
 TCP-UDP Destination Port [0…65535]
Match the exact Destination Port number within the IP Packet
 TCP-UDP Source Port [0…65535]
 Match the exact Source Port number within the IP Packet
 SAT Test Frames
Match ACCEED service activation test frames
 Match All Frames
All frames are matched (e.g. if all traffic from one port should be dropped)

8.7.3.3 Service Class Profiles

In the ingress pipeline, flows can optionally be assigned to a service class profile. Such a profile can
be used to modify the QoS attributes that were assigned at the ingress port:
 Assigned Queue [0 .. 7] Transmit queue in the egress pipeline
 Assigned CoS Value [0 .. 7] IEEE802.1p priority bits that are set in the packet’s primary VLAN
tag. Only relevant if the “Remark CoS” attribute is set.
 Assigned DSCP Value [0 .. 63] DSCP value for IP packets. Only relevant if the “Remark DSCP”
attribute is set.
 Assigned Initial Color Initial color for color aware metering ( 8.7.3.4)

A3118-X642-R612-01 233 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch […]/QoS/Ingress/Service Class Profiles

16 different service class profiles can be defined

Service class profiles can be used in ingress modifiers ( 8.7.3.5)

8.7.3.4 Metering / Bandwidth Profiles

Bandwidth profiles ACCEED 1102/04 process and modify the “color” attribute described in  8.7.1.
The application of bandwidth profiles is also called traffic metering and it decides the color of each
packet:

Green = within the guaranteed bandwidth limit (≤CIR).

Yellow = outside the guaranteed, but within the exceeding bandwidth limit (>CIR, ≤PIR).
Red = outside the exceeding bandwidth limit (>PIR).

The relationship between CIR (committed information rate), PIR (peak information rate)
and EIR (excess information rate) is given by:

CIR + EIR = PIR


The same equation applies to CBS (committed burst size), PBS (peak burst size) and
EBS (excess burst size):

CBS + EBS = PBS

With the application of a bandwidth profile to a traffic flow one of the three colors is assigned to each
packet. The packets can then be treated differently according to their color. Green packets are
normally forwarded with high priority, yellow packets are usually seen as best-effort traffic and are
treated with a low priority, while red packets are normally dropped immediately. However, this
behavior can be changed if needed.

Bandwidth profiles in ACCEED 1102/04 can operate in color aware and in color unaware mode.
In color aware mode, the current color attribute of a packet which was assigned at the ingress (and
possibly already modified with a service class profile) is taken into consideration. Packets can not
improve their color with the application of a bandwidth profile, so yellow packet can only be marked
yellow or red by the bandwidth profile, but never green.
In color unaware mode, the initial color attribute is ignored, and all packets are considered green
when entering the bandwidth profile.

A3118-X642-R612-01 234 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Traffic metering is implemented using token bucket algorithms, which use the concept of an imaginary
bucket filled with tokens representing data bytes. The capacity (size) of the bucket thereby represents
the maximum burst size that is allowed for a traffic flow, while the rate at which the bucket is filled
represents the maximum information rate for a traffic flow (CIR or PIR).
Two different types of metering modes can be used in ACCEED 1102/04: Single Rate Three Colors
according to RFC 2697, and Two Rate Three Colors according to RFC 2698. The following examples
illustrate the behavior of the two metering options in both color aware and color unaware mode. For
simplification it is assumed that each packet takes only one token (i.e. the packets are only one byte
long)

8.7.3.4.1 Single Rate, 3 Colors (RFC 2697), Color Unaware

Tokens are filled in the bucket with the rate of the guaranteed
bandwidth (CIR) and, as long as no packets are passing, build up the
green part up the CBS threshold, then the yellow part until the
maximum of CBS + EBS is reached.

Each passing packet takes a color token from the bucket, starting with
the green tokens.
If there are no more green tokens, yellow tokens are used.
If the bucket is empty the packet is colored red.

Figure 8-36 Color unaware: Single Rate, Three colors

The picture shows an example of a 5 packet burst. Let us assume that we do not get additional tokens
during this burst and the bucket is full with tokens. Each packet passing by the bucket will take a token
from it, starting with the green ones and continue with the yellow ones. If no tokens are in the bucket
anymore, the color of the packet gets red.

A3118-X642-R612-01 235 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7.3.4.2 Single Rate, 3 Colors (RFC 2697), Color Aware

Each initial colored green packet stays green as long as there are green tokens available. If not it
takes yellow tokens and gets yellow. If there are no more tokens, its target color is red.
Each initial colored yellow packet takes only yellow tokens and stays yellow. If there are no more
available, the packet gets the color red.

Figure 8-37 Color aware: Single Rate, Three colors

This example demonstrates that a burst with initially colored yellow packets empties the yellow bucket
before the green and leads to red packets with still green available tokens. Compared to the color
blind mode we may now exactly drop the right initially colored packets (3 and 6)

8.7.3.4.3 Two Rates, 3 Colors (RFC 2698), Color Unaware

This mechanism has separate buckets for green and yellow tokens. Both of them are filled at different
rates, the green one with the committed information rate (CIR) and the yellow one with peak
information rate (PIR). Please note: The CIR is always a part of the PIR.

Figure 8-38 Color unaware: Two Rate, Three colors

This picture shows an example of a 5 packet burst. Let us assume that we do not get additional tokens
in any bucket during this burst and the buckets are full. Each packet passing the yellow bucket picks a
yellow token from the yellow bucket. If no token is available anymore the packet gets red. Then the
packet passes the green bucket, picks a green token, if available, and changes its color to green
(yellow color is lost). Note: The CIR is a part of the PIR, that assures, that in case of an empty yellow
bucket the green is also empty. Therefore it will never happen that red packets change their color to
green.

A3118-X642-R612-01 236 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7.3.4.4 Two Rates, 3 Colors (RFC 2698), Color Aware

In this mechanism each initial colored green packet takes a yellow token from the yellow bucket and a
green token from the green bucket. If there are no green tokens it replaces its color with yellow and if
there are no yellow tokens it replaces its color with red.
Each yellow packet only takes yellow tokens from the yellow bucket. If there are no yellow tokens left,
it replaces its color with red.

Figure 8-39 Color aware: Two Rate, Three colors

This example shows a 6 packet burst with different initial colors. As the green bucket get empty the 3rd
packet gets the replace color yellow, because it has already got a yellow token. The 5 th and 6th packet
cannot get any yellow tokens therefore they replace their color with red.

8.7.3.4.5 Metering Yellow / Red Frames Profiles

The metering process does not only change the color attribute of the packets, it can also modify the
other QoS attributes for yellow and red packets. This is done with dedicated metering QoS profiles
which can be selected in the modifiers ( 8.7.3.5) together with the bandwidth profile.
In total there are 8 profiles available to assign new QoS attributes to frames that are
 classified yellow in the ingress metering stage:
Ethernet/Switch […]/QoS/Ingress/Metering Yellow Frames Profiles
Additionally, for the ingress metering stage there is one profile to assign QoS attributes to
red frames, should they not be dropped:
Ethernet/Switch […]/QoS/Ingress/Metering Red Frames Profile
For egress metering, there is one yellow frames profile:
Ethernet/Switch […]/QoS/Egress/Metering Yellow Frames Profile
The egress metering yellow frames profile contains only the CoS and DSCP attributes.
Frames that are classified red in the egress metering are always dropped; therefore there is
no profile for red frames in the egress.

A3118-X642-R612-01 237 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Frames that are classified green in the metering always keep the QoS attributes that were assigned to
them at the ingress port or in the service class profiles.

8.7.3.4.6 Bandwidth Profile Configuration

 Ethernet/Switch […]/Policing/Bandwidth Profiles[]

Bandwidth profiles can be added or removed with the “Add” and “Remove” buttons. Up to
200 different bandwidth profiles can be defined

 Bandwidth Profile ID [1…200] Internal unique Profile ID starting from 1.

 Description Alphanumeric Text with 32 characters.

 Color Mode
“Color blind”: Initial color of packets is ignored
“Color aware”: Initial color of packets is considered
 Metering Mode
“Single Rate, Three Colors”: Single Rate, Three Colors metering according to RFC 2697
“Two Rates, Three Colors”: Two Rates, Three Colors metering according to RFC 2698

 CIR [0 … 10’000 … 1’000’000 kbit/s, step: 1]

Committed Information Rate. This parameter defines a guaranteed bandwidth
 CBS [0 … 10’000 … 500’000 Bytes, step: 1]
Commited Burst Size for the guaranteed bandwidth (green packets)
 EBS [0 … 10’000 … 500’000 Bytes, step: 1]
Excess Burst Size for the exceeding burst matching guaranteed bandwidth (yellow packets)
 PIR [0 … 10’000 … 1’000’000 kbit/s, step: 1]
Peak Information Rate. This parameter defines the total bandwidth of this service
 PBS [0 … 10’000 … 500’000 Bytes, step: 1]
Peak Burst Size for bursts matching the total bandwidth (green and yellow).

8.7.3.4.7 DEI Bit Marking

When a frame leaves at the egress port, its color can optionally be indicated in the VLAN tag with the
Drop Eligibility Indicator (DEI) bit. This bit is set to 0 for green frames and 1 for yellow and red frames.
The DEI bit is located in the primary VLAN tag (see Figure 8-33).

A3118-X642-R612-01 238 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch […]/<port>/QoS/Egress
DEI remarking can be enabled individually for each egress port

8.7.3.5 Modifiers
Modifiers define the actions that are performed on a flow by a policy. Since not all actions are possible
in both the ingress and egress policing stage, ingress and egress modifiers are defined separately.
The following actions are possible in the ingress policing stage:
 Drop the packets
 Modification of QoS attributes using Service Class Profiles
 Application of a bandwidth profile (including QoS attribute remarking of yellow and red
packets)
 Encapsulation into a tunnel VLAN
 Explicit redirection to a given egress port
The following actions are possible in the egress policing stage:
 Drop the packets
 Remarking of DSCP value and .1p bits of outer VLAN tag
 Application of a bandwidth profile (including QoS attribute remarking of yellow packets)
 Modification of outer VLAN ID

8.7.3.5.1 Ingress Modifier Configuration

 Ethernet/Switch […]/Policing/Ingress Modifiers[]

Ingress Modifiers can be added or removed with the “Add” and “Remove” buttons. Up to
200 different Ingress Modifiers can be defined.

A3118-X642-R612-01 239 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ingress Modifier ID [1..200] Internal unique ingress modifier ID

 Description Alphanumeric text with 32 characters.

 Frame Command
“Forward”: Packets will be normally forwarded via the bridge
“Drop”: All packets will be dropped
“Redirect”: Packets redirected to the Redirect Port without bridge lookup
“Redirect with MAC swap”: Packets will be redirected to a port without bridge lookup.
Additionally their source and destination MAC addresses will be
swapped
 Redirect Port Egress port for redirected packets
 Mirror to Analyzer Port A copy of each packet of will be sent to the global ingress mirroring
analyzer port. Ethernet/Switch […]/Mirroring/

 Service Class Profile Modify initial QoS attribute settings according to the selected Service
Class Profile ( 8.7.3.3)
 Remark CoS
“No”: Do not remark the .1p bits in the primary VLAN tag. This setting
overrides the “Remark CoS” configuration done at the ingress port.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
QoS attribute (defined in service class profile, or, if none is
selected, at the ingress port). This setting overrides the “Remark
CoS” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark CoS” configuration done at the ingress
port.
 Remark DSCP
“No”: Do not remark the DSCP bits in IP header. This setting overrides
the “Remark DSCP” configuration done at the ingress port.
“Yes”: Remark the DSCP bits in the IP header with DSCP value QoS
attribute (defined in service class profile, or, if none is selected, at

A3118-X642-R612-01 240 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

the ingress port). This setting overrides the “Remark DSCP”

configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark DSCP” configuration done at the
ingress port.

 Bandwidth Profile Name of the applied bandwidth profile. Metering can be disabled by
selecting “None”. Ethernet/Switch […]/Policing/Bandwidth Profiles
 Dedicated Bandwidth Profile
A dedicated metering instance is created each time a policy with
this modifier is instantiated.
The bandwidth profile is shared among all ingress policies that use
a modifier with the same bandwidth profile.
 Yellow Frames Command
“Transmit unchanged”: Yellow frames are treated like green frames
“Drop”: Discard all packets that are marked yellow
“Assign Yellow Frames QoS Profile”:
Re-assign QoS attributes according to selected Yellow Frames
QoS Profile
 Yellow Frames QoS Profile Yellow Frames Profile ID if command is “Assign Yellow Frames
QoS Profile”: Profiles are configured under
Ethernet/Switch[…]/QoS/Ingress/Metering Yellow Frames
Profile
 Red Frames Command
“Transmit unchanged”: Red frames are treated like green frames
“Drop”: Discard all packets that are marked red
“Assign Red Frames QoS Profile”:
Re-assign QoS attributes according to the Red Frames QoS Profile
Ethernet/Switch […]/QoS/Ingress/Metering Red Frames Profile
 Remark CoS Yellow Red
“No”: Do not remark the .1p bits in the primary VLAN tag for yellow or red
frames. This setting overrides the “Remark CoS” configuration done
at the ingress port.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
defined in the Yellow/Red Frames Profile. This setting overrides the
“Remark CoS” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark CoS” configuration done at the ingress
port. If that decision is “Yes”, remark the .1p bits in the primary
VLAN tag with the CoS value defined in the Yellow/Red Frames
Profile.
 Remark DSCP Yellow Red
“No”: Do not remark the DSCP bits in the IP header for yellow or red
frames. This setting overrides the “Remark DSCP” configuration
done at the ingress port.
“Yes”: Remark the DSCP bits in the IP header with the DSCP value
defined in the Yellow/Red Frames Profile. This setting overrides the
“Remark DSCP” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark DSCP” configuration done at the
ingress port. If that decision is “Yes”, remark the DSCP bits in the
IP header with the DSCP value defined in the Yellow/Red Frames
Profile.

 VLAN Command

A3118-X642-R612-01 241 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

“Force Primary VLAN ID”: Remark the ID of the primary VLAN tag
“Enable VLAN Tunneling”: Add a new VLAN tag to the VLAN stack. This will be the primary
VLAN tag and the ID will be as defined in the Primary VLAN ID
parameter. Already existing VLAN tags are kept unchanged
 Primary VLAN ID [1…4094] Value of the primary VLAN tag ID for force and tunneling
commands

 If VLAN tunneling is enabled, all CoS remarking actions are executed on the new tunnel
VLAN tag.

8.7.3.5.2 Egress Modifier Configuration

 Ethernet/Switch […]/Policing/Egress Modifiers[]

Egress Modifiers can be added or removed with the “Add” and “Remove” buttons.
Up to 200 different Egress Modifiers can be defined.

 Egress Modifier ID [1..200] Internal unique egress modifier ID

 Description Alphanumeric text with 32 characters.

 Frame Command
“Forward”: Packets will be normally forwarded
“Drop”: All packets will be dropped

 Remark CoS Of Outer Tag

“No”: Do not remark the .1p bits in the outer VLAN tag.
“Yes”: Remark the .1p bits in the outer VLAN tag.
 Remarked CoS Value [0..7] remarked CoS value if remarking is selected
 Remark DSCP Of Outer Tag
“No”: Do not remark the DSCP bits in the IP header.
“Yes”: Remark the DSCP bits in the IP header.
 Remarked DSCP Value [0..63]
remarked DSCP value if remarking is selected

A3118-X642-R612-01 242 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Bandwidth Profile Name of the applied bandwidth profile. Metering can be disabled by
selecting “None”. Ethernet/Switch […]/Policing/Bandwidth Profiles
 Dedicated Bandwidth Profile
A dedicated metering instance is created each time a policy with
this modifier is instantiated.
The bandwidth profile is shared among all egress policies that use
a modifier with the same bandwidth profile.
 Yellow Frames Command
“Assign Yellow Frames QoS Profile”:
Re-assign QoS attributes according to the Egress Yellow Frames
QoS Profile.
Ethernet/Switch […]/QoS/Egress/Metering Yellow Frames Profile
This is currently the only option for egress metering.
 Red Frames Command
“Drop”: Discard all packets that are marked red.
 Remark CoS Yellow
“No”: Do not remark the .1p bits in the primary VLAN tag for yellow
frames.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
defined in the Yellow Frames Profile.
 Remark DSCP Yellow Red
“No”: Do not remark the DSCP bits in the IP header for yellow frames.

 VLAN Command
“Force Outer VLAN ID”: Remark the ID of the outer VLAN tag
 Outer VLAN ID [1…4094] Value of the outer VLAN tag ID if forced

CoS (.1p bit) remarking in the ingress policing stage is always executed on the primary
VLAN tag. CoS remarking in the egress policing stage is executed on the outer VLAN
 tag, which could be either the primary or the secondary VLAN tag. The only exception is
the CoS remarking of yellow frames, which is always performed on the primary VLAN
tag.

8.7.3.6 Policy Definition

A policy defines the treatment of a specific traffic flow. In ACCEED 1102/04 policies therefore consist
of a set of rules that specify the flow, and a modifier which defines the actions to be performed on that
flow. Policies for the ingress and egress stage are defined separately. Ingress policies contain 1 to 8
rules and one ingress modifier; egress policies contain 1 to 8 rules and an egress modifier.

 The 8 rules used by a policy are combined with a logical OR, i.e. the policy applies to a
packet as soon as it matches one of the rules.

A3118-X642-R612-01 243 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch […]/Policing/Ingress Policies[]

Ethernet/Switch […]/Policing/Egress Policies[]
Ingress and Egress Policies can be added or removed with the “Add” and “Remove”
buttons.
Up to 200 different Ingress and Egress Policies can be defined.

8.7.3.7 Policy Instantiation

After a policy is defined, it has to be instantiated at a port where it shall take effect. Each port has a list
of ingress and egress policies (called “Policy Map”), that may contain up to 200 policies. All packets
entering a port pass the rules of all ingress policies, starting with the policy with lowest map index. The
first rule that matches the packet the corresponding ingress policy is applied. For packets leaving a
port, the same procedure is executed with egress policies. A packet could match with rules of more
than one policy, but only the first policy is applied. If none of the policies matches, the packet is
forwarded normally.
The same policy can be instantiated at more than one port.

 Ethernet/Switch […]/<port>/Policing/Ingress/Policy Map[]

Ethernet/Switch […]/<port>/Policing/Egress/Policy Map[]
Ingress and Egress Policies can be instantiated at any port in the policy map.
Entries in the policy map can be added or removed using the “Add” and “Remove” buttons.

Entries in the policy map with no selected policy (Policy ID “None”) have no effect.

A3118-X642-R612-01 244 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Queuing
There are traffic situations in Ethernet networks which lead to overload conditions on the interfaces. In
situations where frequent packet drops should be prevented to achieve an optimized throughput
(TCP/IP) large packet buffers may be an appropriate solution. In case of low latency traffic (e.g. VoIP),
buffers should be minimized and this traffic should be prioritized against other services. To solve this
conflict, the best solution is using a flexible queuing mechanism that can be individually configured
according to the customer’s demand.
The packet processor of ACCEED 1102/04 features a flexible queuing engine with 8 egress queues
per port which allows combining strict priority and weighted fairness scheduling on the same port. The
scheduling distribution amongst the queues is done based on bandwidth ratio and not on inaccurate
packet ratio calculations.

Before packet streams are stored in the queues they need to be allocated to a specific queue. This is
done at the ingress port and optionally at the ingress policing stage, where the “egress queue” QoS
attribute ( 8.7.1) for each packet is assigned.

The egress interface is a constant data rate sink limited through the physically or the logically (rate
shaping) defined port capacity. Packet streams from different ingress ports and traffic bursts may lead
to a congestion situation on that interface and will fill the corresponding buffers of the queues.
Each egress port has a shaped deficit weighted round robin (SDWRR) mechanism with 8 independent
queues.
The following parameters can be individually configured per queue:
- Strict priority (SP) or weighted fairness queuing (WFQ) with different weights
- Queue buffer size for low latency (16x256 bytes) or high burst coverage (224x256 bytes) or
steps in between
- Threshold value to early drop yellow and red packets
- Shaper with queue data rate and the maximum burst size

This scheduling mechanism starts from the highest (#7) to the lowest priority (#0) queue and handles
its queued packets in the following manner:
1) “strict priority”
As long as there are packets in this queue and no packets in a higher queue are waiting, this
queue will send its packets until the queue is empty.
2) “WFQ Weight x”
All Queues with mode “WFQ Weight x” share the available bandwidth in the configured
bandwidth ratios.
Example: available bandwidth is 8 Mbit/s. There are 3 queues with different weights 2, 4 and
10. Result: The first queue will get 1MBit/s, the second 2MBit/s and the third 5Mbit/s.

Recommendation: configure the highest priority queues with “strict priority” and the rest in “WFQ”.
Use short queue buffer sizes for strict priority queues to get lowest latency.

A3118-X642-R612-01 245 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.7.4.1 Queue Profile Configuration

Four different transmit queue profiles can be globally configured. For each port it can then be selected
which of the four profiles is used

 Ethernet/Switch […]/QoS/Egress/Queue Profiles/

Configure the four global transmit queue profiles

Select individually for each port which of the four profiles is used
Ethernet/Switch […]/<port>/QoS/Egress/

The following parameters are available for each queue in Queue Profile 1 ... 4:
 Buffer Size [16 … 224 buffer blocks à 256 Bytes, step: 16]
Queue buffer depth of the queue in 256 Byte blocks. Each packet is split in 256
Byte segments.
Packet size ≤ 256 Bytes: 1 buffer block
Packet size > 256 Bytes: n = round up((Packet size) / 256) buffer blocks
 Buffer Threshold [25 … 75 … 100 %, step: 25]
All yellow marked packets exceeding this threshold are dropped immediately
 Scheduling
“Strict Priority” all traffic within this queue is transmitted in case there are no packets in higher
queues scheduled for transmit. This mechanism is preemptive and interrupts
lower priority queues and lower WFQ on packet level
“WFQ Weight x” covers that even in congestion a small “fair” amount of low priority traffic passes
through, where x is the bandwidth weight
8.7.4.2 Shaping
The egress data rate of each queue and each port can be limited. This process is called traffic
shaping. The difference between shaping and the application of bandwidth profiles in policing is that
with shaping, packets are not dropped immediately but kept in a buffer (egress queue) and may be
sent at a later moment, if the queue is not full already.
Each port in ACCEED 1102/04 has 9 independent shapers, one for each queue and one for the whole
port. Queue and port shapers can also be combined and used in a serial configuration (first queue
shaper(s) then port shaper).

A3118-X642-R612-01 246 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Figure 8-40 Queue and port shapers

 Ethernet/Switch […]/<port>/QoS/Egress/Transmit Queues

Queue shaping can be configured independently for each port and queue

Port egress shaping can be configured independently for each port

Ethernet/Switch […]/<port>/QoS/Egress/Shaping

The following parameters can be configured for both queue and port shapers:
 Enable
 Shaping Rate WAN Ports [ 100 … 5’000 … 100’000 kbit/s, step: 1]
all others [1’667 … 5’000 … 1’000’000 kbit/s, step: 1’667]
 Shaping Burst Size [8 … 16 … 128 kByte, step: 8]

A3118-X642-R612-01 247 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.8 EVC Concept

A3118-X642-R612-01 248 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.9 Protection
Linear Protection
Linear protection is utilized to protect services against failures on the path between the two service
end points.
ITU-T G.8031 defines the APS (Automatic Protection Switching) protocol and linear protection
switching mechanisms for point-to-point VLAN-based connection in Ethernet transport networks.
Linear 1+1 and 1:1 protection switching architectures with unidirectional and bidirectional
switching are defined in G.8031.
ACCEED provides linear protection in any combination of the available ports of the unit. The traffic can
be protected based on the port (all traffic) or specific VLANs (services).

Note: The linear protection is an end-2-end service. All intermediate nodes along the working /
protection path are unaware of the protection.

Protection Application
The following figure shows a possible protection scenario with the ACCEED on one side and a 3rd
party device with linear protection functionality on the other end.
The working link on the ACCEED is connected via a microwave link to the edge / aggregation switch in
this example. The protection link is realized with an EFM SHDSL link to the MSAN. The MSAN can be
located in the central office (CO) or a street cabinet at the curb side.

Figure 8-41 Protection Scenario with ACCEED 1102/4

8.9.1.1 General Protection Principle

The figure below illustrates the principle linear protection architecture.
The “Bridge“ is the function that decides on which path(s) the frames are sent. The “Selector“ is the
function that decides from which path the frames are taken.

Figure 8-42 General Protection Architecture

A3118-X642-R612-01 249 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Protection Level
The protection level can be based on port or VLAN.
With port protection, all frames of a port are protected.
With VLAN protection, specific VLANs (services) can be protected either on the same port (“Working
VLAN” scenario) or on port base (“VLAN MAP” scenario).
In the former case the Working and the Protection paths are both active on the same port. For this
reason the protection is achieved using a Protection VLAN id different from the Working VLAN id.
In the latter case the Working and the Protection paths are active on different ports, so the Working
and the Protection VLAN ids are the equal.
The VLAN protection can be used for graded protection switching (highest priority services are
switched to protection based on defined criteria) or load balancing.

Protection Type
The protection type defines the behavior of the selector and the bridge.
“1+1” protection type sends the frames on both paths (working and protection) at the same time. On
the receiving side (selector), the frames are taken from the working path in normal operation.

Figure 8-43 1+1 Protection Type

“1:1” protection sends the frames on the working path only in normal operation and also the selector
takes the frames from the working patch.

Figure 8-44 1:1 Protection Type

Switching Type
The switching type defines whether the selector and bridge work independently or synchronized.
Unidirectional switching works independently on both ends of the protection and consequently no
coordination between the protection instances is required.
Bidirectional switching type is a coordinated switching between the working and protection patch.
Selectors and bridges on both ends are coordinated with the APS protocol (Automatic Protection
Switching). The following combinations of protection and switching types are supported:

selectors on both ends act

Unidirectional APS not required
fully independent
1+1
selectors and bridges on
Bidirectional APS required
both ends are coordinated

A3118-X642-R612-01 250 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

selectors and bridges on

1:1 Bidirectional APS required
both ends are coordinated

If Protection Level is set to “Working VLAN” then the Protection and Switching type can
 be set only to “1:1” and “bidirectional”

 Inband Management and CES services are protected automatically and therefore no
specific protection configuration is required (if linear protection is enabled).

Operation Type
The operation type defines if the services are switched back from the protection path, if the working
path has been restored.
In revertive operation the traffic is switched back after the defined “wait to restore” time.
In non-revertive operation the traffic stays on the protection path.

8.9.1.2 Trigger for Protection Switching

Protection switching is triggered by multiple reasons. The following triggers can be configured with
ACCEED:
 Manual / forced switch by operator control
 Upon detection of a signal failure (SF) condition on SFP ports
 Upon request via APS protocol from the remote switching process (in bidirectional operation)
Triggering can also be done with LFP Groups (Link Failure Propagation) based on
 Link loss of Ethernet port
 PAF (Partial) Aggregation Loss
 SOAM-RemoteCCM / SOAM-RDICCM Alarms
Please refer to chapter  8.3.2.2 for more information about LFP.

8.9.1.3 The APS Protocol

For monitoring the working and protection path CCM (Continuity Check Messages) are sent between
the protection instances. This communication is based on the Service OAM standard as defined in
ITU-T Y.1731 and requires the setup of SOAM domains with MEPs (Maintenance entity group End
Point). Please refer to chapter  0 for more information about S-OAM.

For APS communication, APS PDUs are exchanged between the same MEPs that send CCMs (the
protection path is used)

Figure 8-45 APS Protocol and Path Monitoring

The APS-PDU information consists of the bridge / selector state and the following protection types:
 (A)PS: yes / no
 (B)ridging: 1+1 or 1:1
 (D)irection: uni or bi
 (R)evertive Mode: yes or no

A3118-X642-R612-01 251 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.9.1.4 Configuration of Linear Protection with ACCEED

 Ethernet/Switch Local/Protection/Linear/Instance x
The configuration of the linear protection can be done per instance:

 Enable Enables or disables the protection of this instance (default: disabled)

 Protection Level [Port, VLAN Map, Working VLAN]

 Working Path [any available port]

Port where frames are forwarded and received during signal
failure (SF) condition on working transport entity
 Working Path LFP Source Group [LFP Group A, B, C, D, E]
Please refer to chapter  8.3.2.2 for more information about
LFP
 Working VLAN [any available VLAN]
VLAN ID that is protected by this protection instance

 Protection Path [any available port]

Port where frames are forwarded and received during signal
failure (SF) condition on working transport entity. If the
protection levelis “Port” this parameter must be different from
the Working Path
 Protection Path LFP Source Group [LFP Group A, B, C, D, E]
 Protection VLAN [any available VLAN, unequl to working VLAN]
VLAN ID that is used if the working VLAN ID protected by
this protection instance is interrupted

 Protection State [read only]

 Bridge State [read only]
 Selector State [read only]

 Use APS [Disabled, Enabled]

 Protection Type [1+1, 1:1]
A3118-X642-R612-01 252 / 405
 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Switching Type [Unidirectional, Bidirectional]

 Operation State [Revertive, Non Revertive]

 Hold Off Time [read only]

 Wait To Restore Time [30s, .. 5 Min, .. 12 Min]
 Group Command
None (Clear)
Lock Out (LO): This command prevents a switch to the protection path.
Forced Switch to Protection (FS): Forces the normal traffic signal to be
switched to the protection path (if no signal failure on the protection path exists).
Manual Switch to Protection (MS-P): Forces the normal traffic signal to be
switched to the protection path (if no signal failures on the protection and the
working path exist).
Manual Switch to Working (MS-W): Forces the normal traffic signal to be
switched to the working path (in non-revertive operation and if no signal failures
on the protection and the working path exist).

VLAN Map and APS state

The VLAN Map defines the VLAN (services) which shall be protected when the Protection Level is set
to VLAN Map. The maximal number of protected services per instance is 8.

 Ethernet/Switch Local/Protection/Linear/Instance x/VLAN Map []

The configuration of the VLAN Map can be done per instance by using the Add button:

The APS folder shows the actual status of the last received APS PDU.

A3118-X642-R612-01 253 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.9.1.5 Linear Protection – Alarming

The protection instance(s) have an alarm location called "Protection" with the following alarms:
Path availabilities Revertive mode Non-revertive mode
None Eth-No Path Available Eth-No Path Available
Working path only Eth-Protection Loss Eth-Protection Loss
Protection path only Eth-Working Path Not Available Eth-Protection Loss
Both None None

The differentiation between revertive and non-revertive mode is made to explicitly signal the loss of the
working path in revertive mode. In revertive mode, it is desired that the traffic is taken from the working
path due to better connection or due to traffic engineering purposes. In non-revertive mode, both the
working and protection paths are considered equal.

The protection instance(s) will also have an alarm location called "Protocol" with this alarm:
APS Protocol Alarm
OK None
Not OK APS-Failure of Protocol

The following reasons lead to a protocol alarm:

 A-, B-, D-, R- or T-Bit in received APS frame not equal to local configuration
 No APS frames received for 3.5 intervals (= 17.5 sec)
 APS frames received on wrong path

8.9.1.6 Linear Protection – Configuration Example

The following example illustrates how linear protection is utilized and configured with ACCEED.
Between the sites A and B, carrier Ethernet based services with linear protection are offered to the
customer. The demarcation devices (EDD A und B) are the protection instances which switch defined
services to the protection path in case the working path is interrupted.
All services shall be switched to the protection path in case of failure of the working path, but not the BE
(best effort) service. BE is therefore not available until the working path gets available again.

The configuration required for linear protection for EDD A is described step by step below. Please note
that the configuration for EDD B need to done accordingly.

Figure 8-46 Linear Protection Example

Step 1: Configure the VLAN Database

The VLAN ID of the service frames and the SOAM (CCM, APS) communication must be configured in
the VLAN DB. The source associated VLAN ID of the maintenance domain is 100.
No manipulation of the service VLAN tags are done in this example (tagging command: Primary Tag
Only)

A3118-X642-R612-01 254 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/VLAN/Database[]

Step 2: Configure the LFP trigger and targets

The LFP (Link Failure Propagation) Groups are configured in a next step. This is the LFP group that is
notified if the link of this port goes down or in case of the WAN port, the LFP group is triggered as soon
as the corresponding LFP trigger is active. For EDD A, the port SFP1 (working) and WAN1 (protection)
are configured as shown below. Please note the “Working Path LFP Source Group” is LFP Group A, the
“Protection Path LFP Source Group” is LFP Group B. This is configured in the protection instance as
described in step 4.

 Ethernet/Switch Local/SFP Ports/SFP1

Ethernet/Switch Local/WAN Ports/WAN1

The LFP trigger can be configured for WAN ports: The criteria is
PAF Partial Aggregation Loss - or - PAF Aggregation Loss

Step 3: Configure the SOAM domain and MEP

The SOAM configuration is required for the CCM and APS message communication between the EDD.
Therefore a maintenance domain and the respective MEPs for the ports must be configured. The
communication shall be done in VLAN ID 100 (Source associated VLAN of the domain).

A3118-X642-R612-01 255 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

3.1) Configuration of the source associated VLAN for domain 1 (D1)

 Ethernet/Switch Local/SOAM/Associated VLAN[]/

3.2) Configuration of the domain parameters

Ethernet/Switch Local/SOAM/Domains[]/D1

3.3) Configuration of the maintenance points (MEP) and CCM data base
Ethernet/Switch Local/SOAM/MPs/MP1 and MP2

MP1 CCM Database of MP1

MP2 CCM Database of MP2

4) Configuration of the protection instance

The protection in this example shall be done for all services, except the best effort traffic (BE). The
protection type is 1:1 and the switching type is bidirectional. This implies that the APS protocol is
activated. The trigger in EDD A to switch to the protection path is a link loss on port SFP1 or a SOAM
CCM alarm on the working path.
If the working path gets available again the services shall be switched back to it after a wait-to-restore
(WTR) time of 30 seconds.

A3118-X642-R612-01 256 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

4.1) Configuring the VLAN Map

 Ethernet/Switch Local/Protection/Linear/Instance 1/VLAN Map[]

4.2) Configuring the protection instance

Ethernet/Switch Local/Protection/Linear/Instance 1

Ring Protection

Ethernet Ring Protection Switching (ERPS) provides sub-50ms protection and recovery switching
for Ethernet traffic in a ring topology and at the same time ensures that there are no loops formed at
the Ethernet layer. Ethernet ring protection is defined in ITU-T G.8032 and describes the protection
switching mechanisms and a protocol for Ethernet layer network rings. Ethernet rings can provide
wide-area multipoint connectivity more economically due to their reduced number of links. The
mechanisms and protocol defined in ITU-T G.8032 achieve highly reliable and stable protection.

Each Ethernet Ring Node is connected to adjacent Ethernet Ring Nodes participating in the same
Ethernet Ring, using two independent links. A ring link is bound by two adjacent Ethernet Ring Nodes,
and a port for a ring link is called a ring port.

The fundamentals of this ring protection switching architecture are:

- The principle of loop avoidance
- The utilization of learning, forwarding, and Filtering Database (FDB) mechanisms defined in
the Ethernet flow forwarding function
Loop avoidance in an Ethernet Ring is achieved by guaranteeing that, at any time, traffic may flow on
all but one of the ring links. This particular link is called the Ring Protection Link (RPL), and under
normal conditions this ring link is blocked, i.e. not used for service traffic. One designated Ethernet
Ring Node, the RPL Owner Node, is responsible for blocking traffic at one end of the RPL. Under an
Ethernet ring failure condition, the RPL Owner Node is responsible for unblocking its end of the RPL
(unless the RPL has failed) allowing the RPL to be used for traffic. The other Ethernet Ring Node
adjacent to the RPL, the RPL Neighbor Node, also participates in the blocking or unblocking of its end
of the RPL.

The event of an Ethernet Ring failure results in protection switching of the traffic. This is achieved
under the control of the Ethernet flow forwarding function on all Ethernet Ring Nodes. The R-APS

A3118-X642-R612-01 257 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

(Ring Automatic Protection Switching) protocol is used to coordinate the protection actions over the
ring.

ACCEED provides ring protection based on ITU-T G.8032v2.

Protection Application
The following figure show possible ring protection scenarios where the ring is completely build based
on SHDSL EFM copper connections, or parts of the ring are built with fiber connections or other
transmission media like e.g. microwave technology.

Figure 8-47 Ring Protection Scenarios

8.9.2.1 General Protection Principle

In ERPS there is a central node called RPL Owner Node which blocks one of the ports to ensure that
there is no loop formed for the Ethernet traffic. The link blocked by the RPL owner node is called the
Ring Protection Link or RPL. The node at the other end of the RPL is known as RPL Neighbor Node. It
uses R-APS control messages to coordinate the activities of switching on/off the RPL link.For
monitoring the links in the ring, CCM (Continuity Check Messages) are sent between the protection
instances. This communication is based on the Service OAM standard as defined in ITU-T Y.1731 and
SOAM domains with MEPs (Maintenance entity group End Point) are therefore utilized.
For R-APS communication, R-APS PDUs are exchanged between the MEPs that send CCMs.

Any failure along the ring triggers an R-APS (SF) (R-APS signal fail) message along both directions
from the nodes adjacent to the failed link after these nodes have blocked the port facing the failed link.
On obtaining this message, RPL owner unblocks the RPL port. (Note that a single link failure
anywhere in the ring ensures a loop free topology.)

During the recovery phase when the failed link gets restored the nodes adjacent to the restored link
send R-APS (NR) (R-APS no request) messages. On obtaining this message, the RPL owner block
the RPL port and then sends an R-APS (NR, RB) (R-APS no request, root blocked) message. This will
cause all other nodes other than RPL owner in the ring to unblock all the blocked ports.

This protocol is robust enough to work for unidirectional failure and multiple link failure scenarios in a
ring topology. It includes a mechanism to force switch (FS) or manual switch (MS) which is used in

A3118-X642-R612-01 258 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

field maintenance scenarios.

Figure 8-48 Ring Protection Principle

Protection Level and Instances

The protection level can be based on port or VLAN.
In principle, port Level protection is not foreseen in the standard ITU-T G.8032. With ACCEED, all
VLANs configured in the VLAN DB are protected in case of port level protection and therefore all
services are protected. With the VLAN protection level, specific VLANs (services) can be protected.
This can be used for graded protection switching (highest priority services are switched to protection
based on defined criteria).

ACCEED supports up to 2 logical ring protection instances per device.

Selecting different RPLs per logical ring allows to balance the load in the ring.

Inband Management Protection

Inband Management can be configured for a port, a set of ports or all ports concurrently. The East and
West ports must be included in the inband management port list, for protecting the management
channel.

CES Protection
The CES services are automatically protected by ACCEED device. If the CES egress port is
configured to be one of the protected ports (east or west port) then the CES frames are concurrently
sent out to the opposite side of the ring automatically (east or west port).

SAT Protection
SAT protection works with the same principle as the CES protection. The SAT frames are sent out the
east and west port concurrently if the SAT egress ports is equal to the east or west port of the ring
protection instance.

A3118-X642-R612-01 259 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Source and destination MAC addresses of the SAT frames need to be swapped at the far end loop in
order to be processed at the receiving side of the SAT instance.

Operation Type
The operation type defines if the services are switched back from the protection path, if the working
path has been restored.
In revertive operation the traffic is switched back after the defined “wait to restore” time. In non-
revertive operation, the traffic stays on the protection path.

8.9.2.2 Trigger for protection switching

Protection switching is triggered by multiple reasons. The following triggers can be configured with
ACCEED:
 Manual / forced switch by operator control
 Upon request via R-APS protocol
Triggering can also be done based on signal failure (SF) and with LFP Groups (Link Failure
Propagation)
 Link loss of Ethernet port (SF)
 PAF (Partial) Aggregation Loss
 SOAM-RemoteCCM / SOAM-RDICCM Alarms (No CCM received within 3.5 times the configured
CCM interval)
8.9.2.3 The R-APS protocol
Communication of the ring status is based on the R-APS (Ring Automatic Protection Switching)
protocol which is distributed via SOAM frame
R-APS PDUs are sent in the following situations:

 RPL owner node, periodically in idle state (when PRL blocked)

 If a node detects a signal failure (SF) – 3 fast R-APS are sent out immediately, then
periodically
 If an operator command is applied (manual or forced switch) - 3 fast R-APS are sent out
immediately, then periodically

The R-APS PDU includes the following information:

Request or State
Forced Switch Forces the blocking on the respective ring port with priority over the
SF condition
Signal Fail (SF)
Manual Switch (MS) Forces the blocking on the respective ring port. SF condition has
higher priority
No Request (NR)

Status
RB: RPL Blocked Indicates whether the RPL is blocked or not (valid only, if frames are
from RPL owner node)

DNF: Do Not Flush Indicates whether a MAC table flush is allowed or not

BPR: Blocked Port Reference Indicates whether port 0 (East) or port 1 (West) is blocked

A3118-X642-R612-01 260 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.9.2.4 Configuration of Ring Protection with ACCEED

 Ethernet/Switch Local/Protection/Ring/Instance x
The configuration of the ring protection can be done per instance:

 Enable Enables or disables the protection of this instance (default:

disabled)
 Compatibility Mode ITU-T G.8032v2 is supported (read only value)
 Node Role [Simple, RPL Owner, RPL Neighbor]
 RPL Neighbor Present In Ring [Disabled, Enabled]
 Protection Level [Port, VLAN]
 Operation Type [Revertive, Non Revertive]

 East Port [any available port]

 East Port LFP Source Group [LFP Group A, B, C, D, E]
Please refer to chapter 8.3.2.2 for more information about LFP
 West Port [any available port, unequal to working path]
 West Port LFP Source Group [LFP Group A, B, C, D, E]
Please refer to chapter 8.3.2.2 for more information about LFP
 RPL Port [East Port, West Port] The port facing the RPL

 Node State [read only] Active state of this protection instance

 Active Operator Command [read only] Active operator command
 East Port State [read only] Blocked / Unblocked
 West Port State [read only] Blocked / Unblocked
A3118-X642-R612-01 261 / 405
 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Node ID [read only] The MAC Address of the node

 Service Domain [D1 .. D5]

 Maintenance Port East [MP1 .. MP5]
 Maintenance Port West [MP1, MP2 .. MP5]

 Subring Without R-APS Virtual Channel

[if enabled, R-APS virtual channel is used. Default: Disabled]
 R-APS Control VLAN [VLAN1, any VLAN existing in the VLAN DB]
 Ring ID [1 .. 239], unique for each protection instance

 Hold Off Time [read only]

 Guard Time [50 .. 500 ms .. 2000 ms] Time, while no R-APS messages are processed
 Wait To Restore Time [0 .. 5 Min .. 12 Min] Time until the RPL is blocked again after recovery
 Wait To Block Time [read only]

Operator Command

 Ethernet/Switch Local/Protection/Ring/Instance x
The operator commands can be initiated via the following buttons:
Manual Switch (MS) Forces the blocking on the respective ring port. SF condition has
higher priority
Forced Switch (FS) Forces the blocking on the respective ring port with priority over the
SF condition
Clear Clears the operator command (MS / FS)

VLAN Map and R-APS state

The VLAN Map defines the VLAN (services) which shall be protected for the protection instance in
case the protection level is set to VLAN.
The R-APS folder shows the actual status of the last received R-APS PDU for the East and West port.

A3118-X642-R612-01 262 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/Protection/Ring/Instance x/VLAN Map []

The configuration of the VLAN Map can be done per instance by using the Add button.
The maximal number of protected services per instance is 32.

Ethernet/Switch Local/Protection/Ring/Instance x/R-APS/East Port

8.9.2.5 Ring Protection – Alarming

The protection instance(s) have an alarm location called "Protection" with the following alarms:
Ring Status Alarm Notes
Ok, RPL blocked None -
SF on one link Eth-Protection Loss No detection of more then
one failure in ring possible

The protection instance(s) will also have an alarm location called "Protocol" with this alarm:
APS Protocol Alarm
OK None
Not OK APS-Failure of Protocol

The following reasons lead to a protocol alarm:

 Node ID of received R-APS frame not matching to local configuration

 No R-APS frames received within 17.5 sec
 R-APS frames received on wrong path

8.9.2.6 Ring Protection – Configuration Example

The following example illustrates a ring protection scenario and describes the configuration steps to
realize the protection with ACCEED.
The ring consists of three ring nodes – EDD A, B and C.
Three services (voice, business data and best effort traffic) are running between the head quarter and
the branch offices. Additionally, mobile traffic between the radio base station and the radio network is
transported via the ring.
All services but the best effort service shall be protected in case of a link failure between the ring
nodes. A ring node failure does affect the services in this example because the service end points are
directly connected to the ring nodes.
Please note, this is not an end to end service protection as it can be achieved with linear protection
acc. to ITU-T G.8032.

A3118-X642-R612-01 263 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The configuration required for ring protection for EDD A is described step by step below. Please note
that the configuration for EDD B and C need to be done accordingly.

Figure 8-49 Ring Protection Example

Step 1: Configure the VLAN Database

The VLAN ID of the service frames and the CCM and R-APS communication must be configured in
the VLAN Database. The source associated VLAN ID of the maintenance domain is VID 100.

 Ethernet/Switch Local/VLAN/Database[]

Step 2: Configure the LFP triggers

The LFP (Link Failure Propagation) Groups are configured in a next step. This is the LFP group that is
notified if the link of this port goes down or in case of the WAN port, a PAF partial or aggregation loss
occurs. For EDD A, port WAN1 (West) and WAN3 (East) are configured as shown below. Please note
the “West Port LFP Source Group” is LFP Group A, the “East Port LFP Source Group” is LFP Group B.
This is configured in the protection instance as described in step 4.

A3118-X642-R612-01 264 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/WAN Ports/WAN1

The LFP trigger can be configured for WAN ports: The criteria are
PAF Partial Aggregation Loss - or - PAF Aggregation Loss

Ethernet/Switch Local/WAN Ports/WAN3

Please note, for Ethernet ports LFP targets need to be configured accordingly

Step 3: Configure SOAM domain and MEPs

The SOAM configuration is required for the CCM communication between the EDDs. Therefore a
maintenance domain and the respective MEPs for the ports must be configured. The communication
shall be done in VLAN ID 100 (Source associated VLAN of the domain).

A3118-X642-R612-01 265 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

3.1) Configuration of the source associated VLAN for domain 1 (D1)

 Ethernet/Switch Local/SOAM/Domains/D1/Associated VLAN[]

3.2) Configuration of the domain parameters

Ethernet/Switch Local/SOAM/Domains/D1

Note: the CCM interval defines the time until the protection switching is triggered by the R-
APS protocol (3.5 times the CCM interval)

3.3) Configuration of the maintenance points (MEP) and CCM data base
Ethernet/Switch Local/SOAM/Domains/D1/MPs/MP1 and MP2

MP1 CCM Database of MP1

MP2 CCM Database of MP2

4) Configuration of the protection instance

The protection in this example shall be done for all services, except the best effort traffic (BE).
Therefore the protection level is “VLAN”.
The trigger to initiate a protection switching is a partial aggregation loss on the SHDSL link or a SOAM
CCM alarm.

A3118-X642-R612-01 266 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The settings of the ring protection instance can be found below:

4.1) Configuration of the VLAN Map

 Ethernet/Switch Local/Protection/Ring/Instance 1/VLAN Map[]

4.2) Configuration of the Ring Protection Instance

Ethernet/Switch Local/Protection/Ring/Instance 1

A3118-X642-R612-01 267 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

8.10 Statistics and Utilization

Introduction
Statistics provide information on sent and received packets and bytes on port, service and EVC level.
This information can be used to monitor the quality of a service or for trouble shooting. The statistics
information is available as continuous values or in user definable history intervals.
Utilization provides information on data rates and utilization of a port or service and displays it in a
graph. See  8.10.7 for more information.

The following statistics groups are available:

 Port: RMON (and HC-RMON) statistics on MAC level
 Policy: Ingress and egress service and policing statistics
 QoS - Tx Queue statistics: Packet (transmitted and dropped) of port transmit queues
 Port based metering statistics (UNI): Ingress and egress bandwidth profile statistics
 EVC: Statistics of EVC services

These statistics groups are explained in more detail in the following chapters.
The figure below shows an overview of the port, service and EVC statistics.

Figure 8-50 Statistics Overview

Global counter settings

The statistics and utilization is based on the bytes and packet counters of the ACCEED unit. These
counters can be configured to count bytes and packet or can be disabled. The correct global counter
setting is therefore a first step to get statistics and utilization results.

The RMON port counters are always enabled and presented in bytes and packets (or events).
The “Service Counters” and the “Transmit Queue Counters” must be enabled for counting.
The total number of counter groups that can run in parallel is limited in the ACCEED unit. Therefore
only 2 of the following 3 global counter groups can be enabled in parallel:

 Transmit Queue Counters

 Ingress Policy Counters
 Egress Policy Counters

A3118-X642-R612-01 268 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

When enabled, bytes and packets are counted simultaneously.

The metering counters (ingress and egress) are always enabled, but must be globally configured to
either count bytes or packets.
Please refer to chapter  8.3.1 for more information.

 To define the global counter settings proceed as follow:

Ethernet/Switch Local

 In the tree area, go to Ethernet/Switch Local

Please note that all counter values of all groups are displayed even if the global counter
setting of a given group is set to 'Disabled'. The values for the disabled counters remain 0

 (zero).
If metering counters are globally set to 'Bytes', the metering packet counters remain 0
(zero). If metering counters are globally set to 'Packets', the metering byte counters remain
0 (zero) accordingly.

Continuous and Historic statistics

The statistics can be activated for each port individually. Only if the continuous statistics is activated,
values will be displayed in the statistics groups, else the values are set to “inactive”.
Up to 5 historic statistics can be added by the Add button. Each historic statistics is defined by the
interval duration and the number of intervals.
The continuous statistic can be reset by the user. The historic statistics can not be reset by the user and
are not impacted by the reset of the continuous statistic. All statistics are reset when the unit is rebooted.

 If the Statistics – Current is not active, the performance value are displayed as “Inactive”

A3118-X642-R612-01 269 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/<port>/Statistics/Continuous
To activate the statistics proceed as follow:
 In the tree area, go to Ethernet/Switch Local/<port>/Statistics/Continuous

Ethernet/Switch Local/<port>/Statistics/Historic[]
To add historic statistics proceed as follow:
 In the tree area, go to Ethernet/Switch Local/<port>/Statistics/Historic[]

Interval Duartion: [30 .. 900 .. 3’600] seconds

Number of Infervals: [1 .. 32]
Each historic statistics can be activated individually.

A3118-X642-R612-01 270 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Port statistics
A data network switch permits data communication among a plurality of media stations in a network.
Data packets or packets are transferred between stations by means of data network switch Media
Access Controllers (MACs). The network switch passes data packets received from a transmitting
station to a destination station based on the header information and the received data packet. Packet
transmission events typically are tracked to provide a basis for statistical analysis of network operation
with respect to each data network switch port. For example, the number of transmitted packets,
received packets, transmissions collisions, and the like can be counted and polled periodically. These
significant parameters, called "objects", are collected in a Remote Network Monitoring Management
Information Base (RMON MIB). Through the use of statistical counters, determination can be made of
improper device operations, such as, for example, loss of packets.

ACCEED supports group 1 of the RMON MIB parameters (Ethernet Statistics Group). This group
contains statistics measured by the probe for each monitored Ethernet interface on this device.
Individual RMON statistics are available for each switch port of the ACCEED device. Additionally the
HC-RMON MIB overflow counters (High Capacity) are implemented to cover overflows of the 32 bit
RMON counters.

The content of the Ethernet Statistics Group is listed and described in the etherStatsTable
(see Table 13).

RMON MIB counter Description

The total number of packets (including bad packets,
etherStatsPkts
broadcast packets, and multicast packets) received.
The total number of octets of data (including those in bad
etherStatsOctets packets) received on the network (excluding framing bits but
including FCS octets).
The total number of good packets received that were
etherStatsBroadcastPkts directed to the broadcast address. Note that this does not
include multicast packets.
The total number of good packets received that were
etherStatsMulticastPkts directed to a multicast address. Note that this number does
not include packets directed to the broadcast address.
The total number of packets received that were less than 64
etherStatsUndersizePkts octets long (excluding framing bits, but including FCS
octets) and were otherwise well formed.
The total number of packets received that were longer than
etherStatsOversizePkts 1518 octets (excluding framing bits, but including FCS
octets) and were otherwise well formed.
The total number of packets received that were less than 64
octets in length (excluding framing bits but including FCS
etherStatsFragments octets) and had either a bad Frame Check Sequence (FCS)
with an integral number of octets (FCS Error) or a bad FCS
with a non-integral number of octets (Alignment Error).
The total number of packets received that were longer than
1518* octets (excluding framing bits, but including FCS
octets), and had either a bad Frame Check Sequence
etherStatsJabbers
(FCS) with an integral number of octets (FCS Error) or a
bad FCS with a non-integral number of octets (Alignment
Error).
The total number of packets received that had a length
(excluding framing bits, but including FCS octets) between
64 and 1518 octets, but had either a bad Frame Check
etherStatsCRCAlignErrors
Sequence (FCS) with an integral number of octets (FCS
Error) or a bad FCS with a non-integral number of octets
(Alignment Error).

A3118-X642-R612-01 271 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The best estimate of the total number of collisions on this

etherStatsCollisions
Ethernet segment.
The total number of events in which packets were dropped
by the probe due to lack of resources. Note that this number
etherStatsDropEvents
is not necessarily the number of packets dropped; it is just
the number of times this condition has been detected.
The total number of packets (including bad packets)
etherStatsPkts64Octets received that were 64 octets in length (excluding framing
bits but including FCS octets).
The total number of packets (including bad packets)
etherStatsPkts65to127Octets received that were between 65 and 127 octets in length
inclusive (excluding framing bits but including FCS octets).
The total number of packets (including bad packets)
etherStatsPkts128to255Octets received that were between 128 and 255 octets in length
inclusive (excluding framing bits but including FCS octets).
The total number of packets (including bad packets)
etherStatsPkts256to511Octets received that were between 256 and 511 octets in length
inclusive (excluding framing bits but including FCS octets).
The total number of packets (including bad packets)
etherStatsPkts512to1023Octets received that were between 512 and 1023 octets in length
inclusive (excluding framing bits but including FCS octets).
The total number of packets (including bad packets)
etherStatsPkts1024to1518Octets* received that were between 1024 and 1518* octets in length
inclusive (excluding framing bits but including FCS octets).
Table 13 Ethernet Statistics Group content
* In ACCEED this counter is not limited to 1518 bytes but defined by the globally configured maximum
frame size.

Additionally to the RMON counters listed above, the following counters are available for each port:
"Total Packets Sent"
"Total Octets Sent"
"Total Packets Dropped"

For all switch ports, the above listed packet counters can be displayed also in the LCT+.

A3118-X642-R612-01 272 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 To access the port packet counters proceed as follow:

Ethernet/Switch Local/<port>

 Select the port in the tree area

 Choose the Performance/Statistics tab to display the port statistics

Counter values of the other ports (LAN, WAN, SFP, BPL) are presented in the same way
by choosing the appropriate port in the tree area.

The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.

Additional overflow counters exist for some RMON counters to meet the requirements for
HC-RMON. HC-RMON counters are 64 bits wide, compared to RMON counters, which are

 32 bits wide. So the total number of packets or octets is calculated as a combination of a

counter and it’s appropriate overflow counter. The overflow counters are incremented each
time the corresponding counter wraps around (which is after 232 = 4’294’967’296 packets
or octets).

Policy statistics
The Policy statistics provide information of a specific service for the ingress end egress direction on
the respective port. The policy statistics information consists of:
 The total counted frames or bytes of the service. The classification of the service is defined by the
rule which has been assigned to the policy.
 The frame coloring based on the bandwidth profile configured in the respective modifier of the
policy.

A3118-X642-R612-01 273 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

 Ethernet/Switch Local/<port>/Policing/Ingress/Policy Map[]/Policy x

To access the ingress policy statistics proceed as follow:
 Select the port in the tree area, go to Policing/Ingress/Policy Map[]/Policy x
 Choose the Performance/Statistics tab to display the frames and bytes counter.

For every service the total counted frames and bytes are displayed.
Please note that the global Ingress/Egress Policy Counters must be enabled and
Ingress/Egress Metering counters must be set to Bytes or Packets. If set to Packets, the
Green,Yellow and RED frames are counted, when set to Bytes, the Green, Yellow and Red
Bytes are counted accordingly. please

Counter values of the other ports (LAN, WAN, SFP, BPL) are presented in the same way
by choosing the appropriate port in the tree area.

The figure below shows the continuous egress statistics for Policy 1 of the port WAN1. The
global egress metering counters are set to Bytes.

The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.

QoS – Tx Queue statistics

 Ethernet/Switch Local/<port>/QoS/Egress/Transmit Queues

To access the egress queue packet statistics proceed as follow:
 Select the port in the tree area, go to QoS/Egress/Transmit Queues
 Choose the Performance/Statistics tab

For every transmit queue of a port the total amount of transmitted frames and bytes as well
as the total amount of dropped frames and bytes are displayed.
Counter values of the egress queues of the other ports (LAN, WAN, SFP, BPL) are
presented in the same way by choosing the appropriate port in the parameter tree.

A3118-X642-R612-01 274 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.

Port based metering statistics

Port based metering is applied with a bandwidth profile in ingress and egress direction.

 Ethernet/Switch Local/<port>/UNI/Ingress/Bandwidth Profile

To access the UNI bandwidth profile statistics proceed as follow:
 Select the port in the tree area, go to UNI/Ingress/Bandwidth Profile
 Choose the Performance/Statistics tab to display the frames and bytes counter.
For every service the total counted frames and bytes are displayed.
Please note that the global Ingress/Egress Policy Counters must be enabled and
Ingress/Egress Metering counters must be set to Bytes or Packets. If set to Packets, the
Green, Yellow and Red frames are counted, when set to Bytes, the Green, Yellow and Red
Bytes are counted accordingly.
Counter values of the other ports (LAN, WAN, SFP, BPL) are presented in the same way
by choosing the appropriate port in the tree area.
The figure below shows the continuous ingress bandwidth profile statistics of the port
WAN1. The global ingress metering counters are set to Bytes.

The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)

A3118-X642-R612-01 275 / 405

 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Statistics: Countinuous or the Historic statistics is displayed.

EVC statistics
An EVC can contain up to 8 CoS instances. Each CoS instance can consist of several services,
identified by the CoS value (.1p bit). Please refer to chapter 8.8 for more information on the EVC
concept.
EVC statistics provide the following information:
 Total matched frames or bytes of all CoS instances of an EVC
 Total matched frames or bytes of a specific CoS instance
Additional, the frames or bytes are counted matching the applied metering defined by the bandwidth
profile which is assigned in the modifier of the CoS instance.

 Ethernet/Switch Local/<port>/EVC/EVCs/EVC x
To access the EVC counters proceed as follow:
 Go to Ethernet/Switch Local/EVC/EVCs/EVC x
 Choose the Performance/Packet Counters tab to display packet and byte counters.
For statistics information of the CoS instances:
Go to Ethernet/Switch Local/EVC/EVCs/EVC x/CoS Instances[]/CoS Instance y
Please note that the global Ingress/Egress Policy Counters must be enabled and
Ingress/Egress Metering counters must be set to Bytes or Packets. If set to Packets, the
Green,Yellow and RED frames are counted, when set to Bytes, the Green, Yellow and Red
Bytes are counted accordingly.

The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
A3118-X642-R612-01 276 / 405
 ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Utilization
Utilization provides information on data rates in kbit/s and link or service utilization in percent [%].
The data rates and utilization can be displayed in a real time diagram which is updated regularly. The
data rates and utilization are derived from the counter values.8.8

Utilization information is available for:

 Ports: Rx / Tx bitrate [kbit/s] and utilization [% of port speed]
 Policy: Ingress and egress service. Total, green and yellow bitrate [kbit/s], utilization of green
traffic (compared to CIR), utilization of green and yellow traffic (compared to PIR)
 QoS - Tx Queues: Enqueue bitrate [kbit/s] and utilization [%]
 Port based metering statistics (UNI): Total, green and yellow bitrate [kbit/s], utilization of
green traffic (compared to CIR), utilization of green and yellow traffic (compared to PIR)
 EVC – CoS Instance: Total, green and yellow ingress and egress bitrate [kbit/s], utilization of
green ingress and egress traffic (compared to CIR), utilization of green and yellow ingress and
egress traffic (compared to PIR)

 To access the port utilization proceed as follow:

Ethernet/Switch Local/<port>

 Select the port in the tree area

 Choose the Performance/Utilization tab to display port bit rate and utilization

Utilization information for the other listed points above can be accessed the same way by
selecting the respective point in the tree area.

Refresh computes the actual values and updates them in the GUI.
Diagram… opens the window to select the values to be shown in the graph (see below)

A3118-X642-R612-01 277 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

Ok opens the Realtime Diagram window and starts displaying the selected data (see
below)
Cancel closes this window and returns back to the main utilization window
Clear deselects all selected data

A3118-X642-R612-01 278 / 405

ULAF+ 8 - Ethernet Switch ACCEED 1102/04 Manual

The graphs in the Bitrate and Utilization diagram to be displayed can be selected on the
right side of the diagrams.

Close the realtime diagram window is closed

Reset the displayed diagrams are reset (values are cleared and time axis is set to 0 again).
Save As… opens the dialogue box to save the data in a *.csv format (comma separated
values)
Setup… opens the setup diagram data window to make change on which data should be
displayed. The realtime diagram window runs in the background and the changes made in
the diagram data windows are added when the OK button is applied.

 A maximum of 10 graphs can be displayed concurrently in the bitrate and utilization

diagram. The graphs are updated every 4 seconds.

A3118-X642-R612-01 279 / 405

ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9
Operation and
Maintenance

The OAM chapter provides general information regarding service

features of the ACCEED unit and explains how to configure Service
OAM, Link OAM and service activation testing.

A3118-X642-R612-01 280 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.1 Link OAM

Link OAM (according to IEEE 802.3ah Clause 57) is an Operations, Administration and Maintenance
mechanism defined for a single Ethernet link (single hop).

The OAM entities communicate over a dedicated protocol packets (OAMPDUs) with a rate of one up
to ten packets per second. This means that every second at least one OAMPDU packet containing
information flags is exchanged between OAM entities.

ACCEED supports the following OAMPDUs:

 Information
Information OAMPDUs are used for discovery, fault notification (flags) and "heartbeat"
 Loopback Control (optional)
Loopback Control OAMPDUs allows an active mode entity to activate or deactivate the loop-back
mode on the remote entity.
 Organization-specific (optional):
Organization-specific OAMPDUs can be defined by the equipment vendor. The packets contain
the Organization Unique Identifier (OUI) for differentiation. ACCEED utilizes these packets for the
Embedded Operating Channel (EOC) between ACCEED EFM-LT and ACCEED EFM-NT

 The ACCEED OUI (Organizationally Unique Identifier) field corresponds to 00-1A-D0

The OAMPDUs are terminated by the OAM entities or are discarded if there is no OAM layer
implemented. OAMPDUs are never forwarded to other links.
Link OAM Configuration

 Ethernet/Switch Local/xxx Ports/Py/Link OAM

Link OAM functionality is per default enabled on the WAN ports of LTs and NTs and is configurable
(Enable / Disable) on the LAN ports (default is Link OAM Disabled).

A3118-X642-R612-01 281 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Figure 9-1 Link OAM

An OAM entity can be either in Active or Passive Mode.

Active entities can send and receive OAM messages. Passive entities respond to OAM messages.

The active entity initiates the Link OAM; at least one entity of a link must therefore be active. The other
may be passive, but it can be active as well.
An entity in the active mode detects automatically if the remote entity supports OAM. It discovers also
which specific capabilities are supported.

Capabilities
Among the optional Link OAM capabilities, ACCEED 1102/04 currently supports Remote Loopback. If
the Remote Loopback capability is enabled, the remote peer can initiate a loopback on that port.

For interoperability reasons, the “Variable Retrieval” capability can also be enabled in

 ACCEED 1102/04. This allows for certain 3rd party devices to complete the Link OAM
discovery process. The Variable Retrieval functionality itself is currently not supported by
ACCEED 1102/04, i.e. Variable Requests are not answered.

Link OAM Fault Management

9.1.2.1 Alarms
All Link OAM relevant alarms are described in  12.3

9.1.2.2 Loopbacks

Each OAM entity:

- features a local loopback, controlled by the peer OAM entity via Link OAM
- allows to activate a remote loopback (i.e. a loopback on the peer OAM entity) via Link OAM, if the
local entity is configured in active mode (see below)
- displays the local and peer OAM entity loopback state

A3118-X642-R612-01 282 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 The Link OAM loopbacks control panel can be found in in the Fault/Maintenance Tab under
Ethernet/Switch […]/Port .../Link OAM

The Link OAM standard defines that looped packets from the remote side have to be dropped in the
local entity. Additionally, ACCEED 1102/04 also offers the (non-standard) option to forward looped
packets coming from the remote side

Figure 9-2 Link OAM loopback standard behavior

Figure 9-3 Link OAM loopback with forwarding of looped frames

The Link OAM loopback does not swap MAC addresses of packets. Therefore, if
 forwarding of looped frames is activated, MAC address learning must be disabled in
network elements that are passed by looped packets.

A3118-X642-R612-01 283 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.2 Service OAM

Service OAM describes a set of OAM functions and mechanisms that are not limited to a link, but can
be set up between two or more points in an entire Ethernet network. Service OAM is defined in the
following standards:
IEEE 802.1ag Connectivity Fault Management
ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks

Figure 9-4 Ethernet OAM Layers

Link OAM is described in  9.1.

The following sections describe the Service OAM protocol implementation.

Service OAM is an Operations, Administration and Maintenance mechanism defined for an Ethernet
network (Service OAM Domain). It can generally be divided into Fault Management (FM) and
Performance Management (PM) functions.
Domains and Maintenance Points

Figure 9-5 Service OAM definitions

ME: Maintenance Entity [ITU-T, IEEE]
MEG: ME Group [ITU-T] / MA: Maintenance Association [IEEE].
Designates all MEs in a Maintenance Domain.
MD: Maintenance Domain [IEEE]. The network or the part of the network for which faults
in connectivity can be managed. In ACCEED this is named Domain.
A3118-X642-R612-01 284 / 405
 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

MEP: MEG End Point [ITU-T] or Maintenance association End Point [IEEE]
MIP: MEG Intermediate Point [ITU-T] or Maintenance domain Intermediate Point [IEEE]

9.2.1.1 Service OAM Maintenance Entity Group

Figure 9-6 Service OAM example

A3118-X642-R612-01 285 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

The example in

Figure 9-6 shows a network with 3 endpoints and the 3 possible endpoint-to-endpoint connections.

In the general case of n MEPs there exist n•(n-1)/2 MEs. These MEs constitute a ME Group (MEG)
[ITU-T] respectively a Maintenance Association (MA) [IEEE].

Every MEG / MA has a unique MEG ID [ITU-T] / MAID [IEEE] for differentiation from neighboring
MEGs / MAs

9.2.1.2 Service OAM Maintenance levels

Every MEG / MD is attached to one of eight levels (from 0 on the link level up to 7 on the customer level)

MEGs / MDs on higher levels have to span wider (or at least equally wide) than those on lower levels.
This means that all SOAM traffic from lower levels is terminated at MEPs from higher levels.

MEGs / MDs on the same level must not intersect.

The example in Figure 9-7 illustrates how the level can be used to differentiate the maintenance level:
 Customer or subscriber level
 Service provider level
 Operator level
 Ethernet link level

A3118-X642-R612-01 286 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Figure 9-7 Service OAM maintenance levels

9.2.1.3 MEP Orientation

MEP orientation is referring to the fact that every MEP must be defined acting as Up or Down MEP.
An Up MEP is a MEP that monitors the forwarding path internal in the layer 2 device towards the
bridge. It can also be seen as an inward facing MEP which is implemented on the ingress port of the
ACCEED unit.
The Down MEP is implemented on the egress port of the device and monitors only the forwarding path
external to the ACCEED unit.

The figure below illustrates the MEP orientation option.

Figure 9-8 Service OAM – MEP orientation

9.2.1.4 Service OAM Domain Configuration

ACCEED 1102/04 supports up to 30 SOAM domains.

A3118-X642-R612-01 287 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 Ethernet/Switch […]/SOAM/Domains[]
New domains can be created by pressing the “Add” button.
The following parameters can be configured per domain:

Domain parameters:
 Maintenance Domain Name Format:
[No Maintenance Domain Name Present, Character String]
Maintenance Domain Name is optional. If used, it can be up to 43 characters long, and the
maximum length of the “Short MA Name” is reduced from 45 to 43 characters.
 Maintenance Domain Name: [“Maintenance Domain”, max. length is 43 characters]
Only available if the maintenance domain name format is set to “Character String”
 Short MA Name Format: [Character String, ICC based Format]
 Short MA Name [“SOAM Domain x”, max. length is 45 characters characters or 43 characters in
case a Maintenance Domain Name is used]
 Maintenance Domain Level [0.. 3 .. 7]
Level of Maintenance Domain (MD), higher numbers correspond to domains with greater physical
reaches (e.g. the Customer ME in Figure 9-7)
 Source Associated VLAN [none, any VLAN ID listed in the “Associated VLAN[]” folder]
VLAN ID among the list of associated VLANs in which all Service OAM PDUs (except LMM and
DMM PDUs) generated by Maintenance Points (MP) are to be transmitted.
Note: The corresponding VLAN ID has to be created in the “Associated VLAN[]” folder before it can
be selected.
 MEP Orientation [Down / Up]
Orientation of the Maintenance End Points (MEPs) on this device for this domain
- Down orientation designates a MEP which transmits and receives packets towards the LAN.
- Up orientation means the MEP transmits and receives packets in direction of the Bridge Relay
Entity (“into” the switch).
The MEP orientation doesn’t affect Maintenance Intermediate Points (MIPs) as they do not have
any orientation. Please refer to  9.2.1.3 for additional explanation on MEP orientation.
 Continuity Check Messages [enabled / disabled]
This parameter enables the sending of continuity check messages (CCM) by all MEPs in this
domain ( 9.2.2.1).
 CCM Period [3.33ms, 10ms, 100ms, 1s, 10s. 1min, 10min]
This parameter determines the interval between continuity check messages
 CCM CoS Value [CoS 0 .. CoS 7]
A3118-X642-R612-01 288 / 405
 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

CoS value for CCM, AIS, LCK, APS and CSF frames generated in this domain
 CCM Transmit Queue [Queue 0 .. Queue 7]
Transmit Queue used for CCM, AIS, LCK, APS and CSF frames generated in this domain
 RDI [enabled / disabled]
This parameter enables the sending of Remote Defect Indications (RDI) in the continuity check
messages (CCM). A defect condition exists if the MEP has a RemoteCCM, ErrorCCM, or XconCCM
alarm. A MEP detects the defect condition in receive direction and sets the RDI flag in the CCM
messages in transmit direction if RDI is enabled. Additionally, if RDI is enabled and a CCM with the
RDI flag set is received, then the MEP’s LFP Target Group is triggered (if there is one configured)
and the RDICCM alarm is raised.
 Alarm Indication Signal [enabled / disabled]
Enables the Alarm Indication Signal (AIS) function in this domain (see  9.2.2.2)
 Locked Signal [enabled / disabled]
Enables the Locked Signal (LCK) function in this domain (see  9.2.2.2)
 AIS LCK Period [1s, 1min]
Time period between two AIS or LCK frames
 Client Signal Fail [enabled / disabled]
Enables the Client Signal Fail (CSF) function in this domain (see  9.2.2.3)
 CSF Period [1s, 1min]
Time period between two CSF frames
 CSF LFP Source [LFP Group A .. LFP Group E]
Defines which LFP target group triggers the CSF function in this domain (see  9.2.2.3)

Associated VLAN
Maintenance Domains can be associated with VLANs. A domain can receive packets from multiple
different VLANs (called “Associated VLANs”), but all frames generated by the MPs in a domain will be
sent in the same VLAN (“Source Associated VLAN”). The Source Associated VLAN is selected in the
Domain configuration

 LMM / LMR and DMM / DMR frames can be configured to be sent in an associated VLAN
different from the Domain’s Source Associated VLAN ( 9.2.3.1/  9.2.3.2).

ACCEED devices also support sending and receiving double-tagged SOAM frames. In the device
configuration this is implemented by allowing to configure an optional tunnel VLAN for an associated
VLAN. Therefore, an “Associated VLAN” in ACCCED device configuration describes all VLAN tags (0,
1 or 2 VLAN tags) of a SOAM frame.

A3118-X642-R612-01 289 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 Ethernet/Switch […]/SOAM/Associated VLAN[]

New Associated VLANs can be created by pressing the “Add” button. Up to 30 associated
VLAN can be created.

The following parameters are available:

 Description
Name or description for the VLAN. If not empty, this is also displayed in the tree and in the Source
Associated VLAN selection of the Domains.
 Domain ID [None, D1 .. D30]
 TPID [0x8100, 0x88A8, 0x9100, 0x9200, User Definable TPID #1, User Definable TPID #2]
 VLAN ID [None, any VLAN ID present in the VLAN DB – see  8.5.3.1]
 Tunnel TPID [0x8100, 0x88A8, 0x9100, 0x9200, User Def..TPID #1, User Def. TPID #2]
 Tunnel CoS [CoS0 .. CoS7]
 Tunnel VLAN ID [None, any VLAN ID present in the VLAN DB – see  8.5.3.1]
 Tunnel Ports [port list depends on specific ACCEED type]
Indicates at which ports the tunnel starts and terminates

Each “Associated VLAN” has to be unique and can only be linked to one Domain.
It is also possible to send / receive untagged SOAM frames. There are two ways to achieve this:
- If no “Associated VLAN” is linked to the corresponding Domain
- If an “Associated VLAN” with “VLAN ID”=“Tunnel VLAN ID”=”none” is created and linked to the
corresponding Domain

If tunneling (double tagging) is applied, make sure to configure the following parameters
accordingly:
- VLAN egress tagging commands in the VLAN DB
 - Ingress/Egress TPIDs of the tunnel port(s). Only VLAN tags that are recognized by
the device are considered.
If a tunnel VLAN tag is present at incoming SOAM frames, it has to be the outer and the
primary VLAN tag.

A3118-X642-R612-01 290 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.2.1.5 Service OAM Maintenance Point configuration

An ACCEED unit supports up to 30 local MPs (MEPs or MIPs). Each MP is associated with a Domain.
In the case of Up-MEPs, multiple MEPs may be added to a single Domain.

 Not more than 8 MEPs can be added to Domains with CCM intervals <= 10ms.

 Ethernet/Switch […]/SOAM/MPs

 Domain ID
Enables the Maintenance point and associates it with a Domain. The Domain has to be created
first.
 Locked
Administrative locking of the MP, see  9.2.2.2
 Type [MEP / MIP]
Maintenance point type, either MEP (Maintenance association End Point [IEEE 802.1ag] or
equivalently MEG end point [ITU-T Y.1731]) or MIP (Maintenance domain Intermediate Point
[IEEE 802.1ag] or equivalently MEG Intermediate point [ITU-T Y.1731])
 Associated Port [port list depends on specific ACCEED type]
Port on which the maintenance point should reside
 MEP ID [1... 8’191]
Unique number which identifies the MEP in its Maintenance Domain

Service OAM Fault Management

9.2.2.1 Continuity Check
MEPs periodically exchange Continuity Check OAM messages to detect loss of continuity or incorrect
network connections. A CCM is multicasted to each MEP in a MEG/MA. A flags field is incorporated in
CC Messages. This field includes a bit for Remote Defect Indication (RDI) and an indication of the
period at which CC messages are transmitted. Continuity check can also be used to monitor
redundant paths in G.8031 / G.8032 linear or ring protection scenarios. ACCEED devices support
CCM interval times as fast as 3.3ms to facilitate switchover times below 50ms.

CCM Database
All remote MEPs from which a local MEP expects to receive CCMs have to be entered in the CCM
Database. CCM messages received from unknown MEPs (MEP not present in the CCM database),
raise an XconCCM alarm. Invalid CCM messages (e.g. with unexpected CCM interval) which are
received raise an ErrorCCM alarm.
Lack of messages from MEPs (No CCM message received within 3.5 times the CCM interval) present
in the CCM database, raise a RemoteCCM alarm.

 Remote MEPs are entered in the CCM data base by clicking the Add button and entering
the remote MEP’s ID. Up to 16 remote MEPs can be added per local MEP.

A3118-X642-R612-01 291 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

For each MEP in the CCM Database the following (read-only) information is available:
 MEP ID
ID of the remote MEP
 State
The following states are possible:
- Idle Continuity Check not yet started
- Start Continuity Check starting
- Failed No Continuity Check Messages received from remote MEP
- OK Continuity Check Messages received from remote MEP
 Last State Change
This parameter indicates the time and time at which the remote MEP last entered the Failed or Ok
state or 0 (zero) if it has not yet entered either state.
 MAC Address
MAC address learned for the remote MEP
 RDI
This parameter reports the state of the Remote Defect Indication (RDI) flag in the received Continuity
Check Messages (CCM).
 CSF
Received CSF defect type, if any. See  9.2.2.3
 LFP Target
Defines the LFP target group, which will be notified if connectivity to this MEP has failed or CSF
messages are received. Please refer to  8.3.2.2 for more information on LFP (Link Failure
Propagation)

Each local MEP supports up to 16 remote MEPs. Additionally there is a global limitation on
the number of incoming CCMs. The maximum total number of CCMs received in all

 domains with CCM intervals >10ms is 300 CCMs/second. For domains with CCM intervals
<=10ms the total number is limited to 3000 CCMs/second. The CCM rate depends on the
number of configured remote MEPs and the CCM intervals of each domain. A “Resource
Shortage” alarm is raised when the expected number of received CCMs exceeds the limit.

 In case of connectivity failures (ErrorCCM or XconCCM alarms), there may be some helpful
detail information on the reason of failure in the Fault/SOAM tab. The information displayed
relates to the last defective CCM received by the respective MEP.

A3118-X642-R612-01 292 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.2.2.2 Y.1731 Alarm Indication Signal (AIS) and Locked Signal (LCK)
Client MPs
Client MPs are configured to forward AIS and LCK signal of the domain where a problem occurred, to
the higher level domain MP.

Up to 29 client MPs can be assigned to one MEP whereas the client MPs of a MEP resides always on
the same ACCEED unit as the MEP itself. The client MP can be a MEP or MIP.

 Client MP are entered by clicking the Add button on the Client MP[] level.
For each Client MP, the Service Domain and the corresponding Maintenance Point on that
domain level (can be MEP or MIB) must be assigned.

A3118-X642-R612-01 293 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Alarm Indication Signal (AIS)

Alarm Indication Signal (AIS) suppresses alarms following the detection of defect conditions at the
server layer.
Defect conditions are:
- Signal Fail Condition (XconCCM-Alarm, ErrorCCM-Alarm, RemoteCCM-Alarm)
- AIS condition (the MEP receives an AIS frame)
- LCK condition (the MEP receives an LCK frame)

AIS is initiated if a defect condition on an MEP appears and AIS is enabled on this MEP. This MEP
forwards the AIS to all configured client MPs on the higher MEG levels. The client MPs (MIP) then
send AIS frames in the defined period. AIS frames are only sent in opposite direction of the MEP that
detected the defect condition.
Please refer to  9.2.1.4 for AIS configuration information on the domain level.

The following picture illustrates an AIS example.

Figure 9-9 AIS example

Locked Signal (LCK)

LCK is used to signal administrative locking of a lower domain level MEP that has impact to the
service (e.g. for a maintenance task). LCK is initiated if a MEP is administratively locked (see 
9.2.1.5) and LCK signal is enabled on the domain level (see  9.2.1.4). A MEP in LCK condition
notifies its client MPs, which send out LCK frames. Unlike AIS situations MIPs send LCK frames in

A3118-X642-R612-01 294 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

both directions. A MEP receiving LCK frames will register a defect condition. Therefore, on higher
levels AIS frames are sent. This is illustrated in the following example.

Figure 9-10 LCK example

9.2.2.3 Client Signal Fail (CSF) Function

CSF is used to propagate failure conditions from a MEP to its peer MEPs. CSF covers failure
conditions which are not related to SOAM and are therefore not covered by the AIS and LCK
functions. An example for a Client Signal Failure condition is a physical link at a UNI port that goes
down. The MEP at this UNI port would in this case transmit CSF messages towards all its peer MEPs.
A very typical application for CSF is Link Failure Propagation (LFP) across a network.

Figure 9-11 SOAM CSF example

This is illustrated in Figure 9-11. Normally LFP is used with equipment that does not support
mechanisms like SOAM. LFP will force one ore more UNI ports on a device down if the WAN port
goes down, for example to trigger protection mechanisms like spanning tree or LAG on a router/switch
A3118-X642-R612-01 295 / 405
 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

connected to the LAN port (more info on LFP under  8.3.2.2). Using SOAM CSF, the LFP
functionality can be extended over a Layer 2 network between 2 MEPs. The mechanism works as
follows: If the physical link at the UNI port of MEP A goes down, MEP A starts transmitting CSF
frames. MEP B, upon reception of such frames then forces its UNI port down, to signal a remote
failure condition to the link partner which does not support SOAM.

 In ACCEED, CSF functionality is configured using the LFP Group concept described under
 8.3.2.2
First a port (or MEP) has to be activated as a trigger for an LFP group. For example,
choose LFP Group A as the target group for P1
Ethernet/Switch ../<Port>

In the SOAM domain config, CSF can be enabled and an LFP Group can be selected.
When this group is triggered (in this example because P1 goes down), all MEPs in the
Domain will start transmitting CSF messages.
../SOAM/Domains/Dx

On the remote side, the peer MAP can itself be configured to trigger an LFP group upon
reception of CSF messages
(Remote device) ../SOAM/MPs/MP x/CCM Database/Remote MEP ID y

Finally this LFP Group can then be used to force a port down when triggered by CSF
messages.
(Remote device) Ethernet/Switch ../<Port>

A3118-X642-R612-01 296 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

When a MEP receives CSF frames this is indicated in the CCM database, even if the CSF function is
not enabled.

ACCEED can display the following standardized CSF defect types: LOS (Loss of Signal), FDI
(Forward Defect Indication), RDI (Reverse Defect Indication).
Note: When transmitting CSF messages, ACCEED will always use the LOS defect type.
If ACCEED is receiving CSF messages in a domain where CSF is enabled, it will also raise an alarm
(SOAM-LOSCSF, SOAM-FDICSF or SOAM-RDICSF Alarm).

9.2.2.4 SOAM Loopback

SOAM Loopbacks are a sort of "Ethernet Ping". A SOAM loopback is started on a MEP; possible targets
are MEPs and MIPs (only with unicast messages) in the same domain (MEG/MA).

 SOAM loopbacks are available under the following node, in the Fault/SOAM tab:
../SOAM/Diagnostics/Loopback

A SOAM loopback test is executed by clicking the Start button.

A3118-X642-R612-01 297 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 SOAM Loopbacks are only available on enabled MEPs.

The following parameters can be configured for the loopback:

 Maintenance Point [MP1 .. MP30]
Source MEP from which the loopback should be executed
 Multicast Loopback [enabled / disabled]
If enabled loopback messages are sent to all MEPs in the Maintenance Domain at the same
Maintenance Domain Level. Otherwise the messages are sent only to the Maintenance Point with
the specified MAC address.
 Use MEP ID / Target MEP ID
Enables and defines the target MEP ID. If enabled, Multicast Loopback and Target MAC address
are not available.
 Target MEP MAC Address
Read-only value, only relevant if “Use MEP ID” is selected, and “Multicast Loopback” is disabled.
MAC address of the remote MEP or MIP, automatically taken from the source MEP’s remote MEP
database.
 Target MAC Address
Only relevant if “Use MEP ID” is not selected, and “Multicast Loopback” is disabled. MAC address
of the destination MEP or MIP.
 Number Of Messages [0 .. 3 .. 3600]
Number of messages that will be sent, 0 (zero) means that the messages will be continuously sent
until the transmission is explicitly aborted.
 Time Period between Messages [0.. 1 .. 60 sec]
Time (in seconds) to wait between the reception of the last reply message and the sending of the
next request
 Message Size [64…1’500 Bytes]
Size of the loopback messages in bytes
 CoS Value
Defines the VLAN priority (CoS) of the LBM frame
 Transmit Queue
Defines the transmit queue the LBM frames are assigned to

9.2.2.5 SOAM Linktrace

Linktrace is an on-demand Service OAM function which is used for path discovery between an
initiating MEP and a remote maintenance point. Fault locations can be determined by sending a LTM
(Link Trace Message) and the analysis of the LTRs (Link Trace Reply). This works analogous to the IP
traceroute function.

 SOAM Linktrace is available under the following node, in the Fault/SOAM tab:
../SOAM/Diagnostics/Linktrace

A3118-X642-R612-01 298 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

A Linktrace is initiated by clicking the Start button

 SOAM Linktrace is only available on enabled MEPs.

The following parameters are available:

 Maintenance Point [MP1 .. MP30]
Source MEP from which the linktrace should be executed
 Use MEP ID / Target MEP ID
Enables and defines the target MEP ID. If enabled, Target MAC address is not available.
 Target MEP MAC Address
Read-only value, only relevant if “Use MEP ID” is selected. MAC address of the remote MEP or
MIP, automatically taken from the source MEP’s remote MEP database.
 Target MAC Address
Only relevant if “Use MEP ID” is not selected. MAC address of the destination MEP or MIP.
 TTL [1 .. 64 .. 255]
Time To Live value indicates the maximum hops a LTM frame is forwarded by a MP.
 Use FDB Only [enable / disable]
If set, only MAC addresses learned in the filtering DB of the switch are used to determine the egress
port of an LTM frame. Otherwise, information saved in the optional CCM databases of the traversed
MIPs may be also used to determine the egress port.
 CoS Value [CoS0 .. CoS7]
Defines the VLAN priority (CoS value) of the LTM frames to be transmitted.
 Transmit Queue [Queue #0 .. Queue #7]
Defines the transmit queue the LTM and LTR frames are assigned.
 State
Indicates the state of the linktrace [Running / Idle / Error]
 LTM Transaction Identifier
Random number generated by the initiating unit.

Linktrace replies are automatically presented in a window that opens when the trace has been finished.
It can also be read out and displayed by clicking the “Read Linktrace Replies” button.

The Linktrace replies window presents the following information:

LTMtransID: Transaction Identifier of linktrace messages.

A3118-X642-R612-01 299 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Target MAC Adress: of remote MEP

Starting Time: of the linktace

TTL: TTL value after being decremented each time the LTM frame has been forwarded
by a MP. Starting from the configured TTL value
hwOnly: if 1, the filtering database (MAC table) of the switch is used only to determine the
egress port of the LTM frame (this applies to each forwarding MP on the route from
initiating MEP to the target MP). Otherwise, the optional MIP CCM database can
additionally be used to determine the egress port of the LTM frame.
fwdYes: the FwdYes flag is set if a modified LTM is forwarded
terminalMep: the TerminalMEP flag is set, if the MP in the reply egress TLV (or reply ingress TLV
if the egress TLV is not present) is a MEP
lastEgressId: The implementation in ACCEED is based on Y.1731 where the EgressID is defined
as 8 Byte value. The first 2 Bytes are ZEROs and the following 6 Bytes are the MAC
address of the last LTM-responder.
nextEgressId: The implementation in ACCEED is based on Y.1731 where the EgressID is defined
as 8 Byte value. The first 2 Bytes are ZEROs and the following 6 Bytes are the MAC
address of the actual LTM-responder.
relayAction: RlyHit: The MPs MAC address matches the target MAC address of the LTM frame.
RlyFDB: The egress port was determined using the filtering database/MAC table
RlyMPDB: The egress port was determined using the MIP CCM database
ingressAction: IngOK or empty = unknown
ingressAddress: MAC address of the associated port of the ingress MP
egressAction: EgrOK or empty = unknown
egressAddress: MAC address of the associated port of the egress MP

Figure 9-12 Service OAM – Linktrace Replies

A3118-X642-R612-01 300 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Service OAM Performance Monitoring

The purpose of Service OAM performance monitoring is to verify that SLAs are met in terms of the
contracted performance attributes. With ACCEED devices, the following attributes can be specified for
a service:

Delay Measurement (DM)

 Frame Delay (FD)
 Inter-Frame Delay Variation (IFDV)
Loss Measurement (LM)
 Frame Loss Ratio (FLR)
 Availability

The protocols and mechanisms required for the measurements are defined in ITU-T Y.1731 [17]
ACCEED supports:

 Single-ended delay measurement with DMM/DMR frames

 Dual-ended loss measurement with CCM frames
 Single-ended loss measurement with LMM/LMR frames
 Dual-ended synthetic loss measurement with 1SL frames
 Single-ended synthetic loss measurement with SLM/SLR frames

The measurement protocols always run between two MEPs. If the measurement is “dual-ended”, both
MEPs can gather results. If it is “single-ended”, only the initiating MEP gathers results.
Independently from the type of measurement (single-/dual-ended), IFDV, FLR, and Availability results
can be calculated separately for forward and backward direction (one-way), while FD measurement
using DMMs gives round-trip (two-way) results.

On ACCEED devices, an instance that executes DM or LM measurements and collects corresponding

statistics is called DM / LM “Session”. An instance that just listens and answers DMM and LMM frames
(in the case of single-ended measurements) is called DM / LM “Responder”. A responder does not
collect any statistics. Sessions and responders can be configured independently.

Figure 9-13 Service OAM – PM session and responder principle

A3118-X642-R612-01 301 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.2.3.1 Frame Delay (FD) Measurements

Frame delay measurement is performed by transmitting Delay Measurement Messages (DMM) and
Delay Measurement Replies (DMR) between two MEPs according to ITU-T Y.1731.
Timestamps are added to the frames at reception and transmission of both DMM and DMR in order to
measure the frame delay and filter out the processing time at the remote MEP.
The picture below illustrates the two way (round-trip) delay measurement realized in ACCEED.

Figure 9-14 Service OAM – Round trip delay measurement principle

The measurement of inter-frame delay variation can be performed using the same DMM and DMR
messages that are used for delay measurement.
The delay of the last completed measurement is compared with the delay of the current completed
measurement in forward and backward direction. The picture below illustrates the measurement
principle.

A3118-X642-R612-01 302 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Figure 9-15 Service OAM – Inter-frame delay variation measurement principle

9.2.3.1.1 DM Session configuration

Up to 30 delay measurement sessions per ACCEED unit can be configured. Each session performs
frame delay measurement (FD) and inter-frame delay variation measurement (IFDV).

A3118-X642-R612-01 303 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 ../SOAM/Performance/DM Sessions/Session x

The following parameters are available:

 Enable
Enable the session, starts the measurements, immediately when applied.
 Maintenance Point [MP1 .. MP30]
Maintenance point the session is running from
 Version [0 .. 1]
Version of generated DMM PDUs
 Fame Length [64 .. 2’048 Bytes]
As this is a synthetic testing, the frame length, VLAN ID and CoS parameters should be
configured to be the same or similar as the expected customer service frames.
 Period [100ms, 1s, 10s]
Interval between transmitted DMM frames
 Use MEP ID / Target MEP ID
Enables and defines the target MEP ID. If enabled, Target MAC address can not be set.
 Target MAC Address
If the remote MEP is not addressed by MEP ID (“Use MEP ID” disabled), the remote MEP’s MAC
address can be specified manually.
 DM VLAN
Defines the VLAN that is used for DMM/DMR frames. Entries among the list of associated VLAN
can be selected.
Attention: The DM VLAN can be different from the domain “source associated VLAN ID”.
 CoS Value [CoS 0 .. CoS 7]
 Transmit Queue [Queue#0 .. Queue#7]
 Accepted CoS Values
DMRs with the selected CoS values are accepted for this DM session.

In most cases DMRs should have the same CoS value as the corresponding DMMs. DMR
 CoS values that differ from the configured DMM CoS value should only be selected if CoS
values are translated at some point within the network.

9.2.3.1.2 DM Responder configuration

A3118-X642-R612-01 304 / 405
 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Up to 60 responders can be configured. The configuration information of the responder must match
the domain and VLAN / CoS settings of the respective DM session. A responder must be enabled in
order to reply to the DM session with DMR frames.

 ..\SOAM\Performance\DM Responders\
Responders can be created by clicking the Add button

The following parameters are available:

 Enable
 Maintenance Point [MP1 .. MP30]
Maintenance point the responder is attached to
 DM VLAN
Defines the VLAN that is used for DMM/DMR frames. Entries among the list of associated VLAN
can be selected.
Attention: The DM VLAN can be different from the domain “source associated VLAN ID”.
 CoS Value [Incoming CoS]
DMRs are always sent back with the same CoS value as the received DMM
 Transmit Queue [Queue#7]
 Accepted CoS Values
DMMs with the selected CoS values are accepted for this DM session.

9.2.3.1.3 DM Session Statistics

In order to see any DM values, statistics must be enabled. All measurements are aggregated for
interval with configurable durations. Default value is 15 min.
The possible range is from 1 minute to 1’440 minutes.
Additionally, the device can be configured to store to 32 historic intervals.

A3118-X642-R612-01 305 / 405

ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 The statistics settings can be configured under

 ,,/SOAM/Performance/DM Sessions/Session x/Statistics/Current

One historic data set can be added and enabled for up to 32 past intervals. The interval
duration is taken from the current statistics setting.
History settings can be enabled under
 ../SOAM/Performance/DM Sessions/Session x/Statistics/Historic[]

 Statistics configuration is effective for both FD and IFDV measurements.

If the Statistics – Current is not active, all performance values are displayed as “Inactive”

A3118-X642-R612-01 306 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 FD and IFDV results can be accessed in the Performance tab under

 ../SOAM/Performance/DM Sessions/Session x/FD
 ../SOAM/Performance/DM Sessions/Session x/IFDV
If historic statistics is configured and enabled, these values can be seen by selecting the
respective interval in the Statistic pull down menu as shown at the bottom in the picture
below.

IFDV values are presented accordingly in the IFDV folder

Three counters are provided for all intervals:

 Initiated Measurements: Number of DM messages (DMM or CCM) transmitted
 Completed Measurements: Number of DM responses (DMR or CCM) received
 Valid Measurements: Number of measurements where the result was between 0 and 5s

If measurement values are “unknown” and/or completed and valid measurements are
zero, then a possible communication problem between the DM session and responder
might cause the failure. Verify the session and responder settings and the communication
 path in-between.
If the value is showing “Inactive”, this indicates that the current statistics counter is not
enabled. To enable the statistics counter go to
 ../SOAM/Performance/DM Sessions/Session x/FD/Statistics/Current

Every delay measurement result is assigned to one of maximum 10 intervals called bins, whose
corresponding counter is increased.
The range of bin x is defined by the lower threshold (thld) assigned to bin x and the lower threshold
assigned to bin (x+1).
Measurements with a delay greater than 5 sec are not considered and therefore discarded. The
threshold of Bin 1 should always be set to zero. In the figure below an example with 5 Bins is shown.

A3118-X642-R612-01 307 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Figure 9-16 Service OAM – Delay Measurement Bin

Up to 10 Bins can be configured for each DM session (individually for roundtrip FD, forward and
backward IFDV), whereas the threshold of Bin 1 is a permanent list entry. Bins 2 to 10 can be added
with the respective Add button.

 ../SOAM/Performance/DM Sessions/Session x/FD/Round-Trip Bins[]

../SOAM/Performance/DM Sessions/Session x/IFDV/Forward Bins[]
../SOAM/Performance/DM Sessions/Session x/IFDV/Backward Bins[]
Bind can be added using the Add button
Range of the Threshold values [0 .. 5’000’000 micro seconds]

 To change bin settings, the corresponding DM session has to be disabled

 Bin counters can be accessed in the Performance tab under

 ../SOAM/Performance/DM Sessions/Session x/FD/Round-Trip Bins[]
 ../SOAM/Performance/DM Sessions/Session x/IFDV/Forward Bins[]
 ../SOAM/Performance/DM Sessions/Session x/IFDV/Backward Bins[]

A3118-X642-R612-01 308 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

If historic statistics is configured and enabled, these values can be seen by selecting the
respective interval in the Statistic pull down menu as shown at the bottom in the picture
below.

ACCEED devices can be configured to generate an alarm if FD or IFDV measurements exceed a

defined limit during a measurement interval.
The limit is set by configuring “Objective” and “Percentile” values. “SOAM-FD Objective” or “SOAM-
IFDV Objective” alarms are raised if less than “Percentile” of all measurements fall below the
“Objective” values.

 Alarm thresholds can be set under

../SOAM/Performance/DM Sessions/Session x/FD
../SOAM/Performance/DM Sessions/Session x/IFDV
The Objective value is defined by the lower threshold of the selected Bin. Default value:
None (meaning no alarm threshold is active)
The Percentile value ranges from 0 to 100%. Default value: 95%

IFDV thresholds are configured accordingly under the IFDV folder

9.2.3.2 Loss Measurement (LM)

Like DM, LM is always performed between two MEPs. The ITU-T standard Y.1731 defines the
following options to do frame loss measurement.
 Dual-ended LM using CCM
Frame counters can be inserted in the CCMs transmitted between the MEPs. This way, both
end points can gather frame loss results for both directions. Frame counters based on real
customer traffic can be used, but this method does not support individual LM sessions for
different service classes in Multi-CoS EVCs.
 Single-ended LM using LMM / LMR
Dedicated Loss Measurement Messages / Replies (LMM / LMR) containing frame counters
are transmitted between MEPs. Frame counters based on real customer traffic can be used.

A3118-X642-R612-01 309 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Only one end point gathers results for both directions. Multi-CoS setups are supported, but not
multi-point EVCs (LAN scenarios).
 Dual-ended synthetic LM using 1SL
Dedicated Synthetic Loss Measurement Messages (1SL) are transmitted by a MEP. A
receiving MEP can calculate frame loss statistics for one traffic direction based on the loss
rates of these 1SL. This method supports multi-point scenarios.
 Single-ended synthetic LM using SLM / SLR
Dedicated Synthetic Loss Measurement Messages / Replies (SLM / SLR) are transmitted
between MEPs. Frame loss statistics are calculated based only on loss rates of these SLM /
SLR. This method supports multi-point scenarios.
ACCEED devices support all mentioned loss measurement methods

Two LM metrics are evaluated, Frame Loss Ratio (FLR) and Availability.

Frame Loss Ratio (FLR) measurement is performed by exchanging local transmit (TxFC) and receive
service frame counters (RxFC) between MEPs. For CCM and LMM based measurements, real service
traffic is counted, while synthetic measurement uses the count of transmitted and received SLM / SLR
/ 1SL.
If there is no traffic (e.g. ΔTxFwd = 0) or the previous counters are zero/unknown, then the FLR is
unknown (and the measurement is considered as completed, but not valid).

Figure 9-17 Service OAM – Frame loss ratio (FLR) measurement principle

Availability is defined by the frame loss ratio during a sequence of consecutive short time FLR
measurements (availability indicators) and the last availability state.
A single availability indicator is evaluated over a time interval ∆t = k * LM Frame Period. The number
of LM PDUs (k) that are used to calculate a single availability indicator is configurable. For LM based
on real customer traffic, k is typically set to 1, while for synthetic LM, k should be set to a value of at

A3118-X642-R612-01 310 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

least 10. This means that depending on the LM frame period, a single availability indicator covers a
time period (∆t) between 100ms up to a few seconds. Depending on the FLR in that time period
compared to a predefined threshold, there are two possible values a single availability indicator can
have, “high FLR” or “low FLR”.
“Availability” is then assessed over sliding window of size n = {1, …, 10} availability indicators. Its state
changes only if all availability indicators in the sliding window have the same value (see

Figure 9-18).

Figure 9-18 Service OAM – Availability definition

9.2.3.2.1 LM Session configuration

Up to 30 loss measurement sessions per ACCEED unit can be configured. Each session can perform
Frame Loss Ratio (FLR) and Availability measurement.

A3118-X642-R612-01 311 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 ../SOAM/Performance/LM Sessions/Session x

The following parameters are available:

 Enable
 Maintenance Point [MP1 .. MP30]
 LM Type [LMM, CCM, SLM, 1SL]
Defines the used loss measurement message type
 Version [0, 1]
Version of generated LMM PDUs. Not relevant for LM types other than “LMM”.
 Frame Size [64 .. 2048]
Frame size of transmitted 1SL / SLM frames. Only relevant for LM types “SLM” and ”1SL”
 Test ID [0 .. 232-1]
Test ID automatically assigned based in LM Session Index and MEP ID. Only relevant for LM
types “SLM” and ”1SL”
 Remote Test ID [0 .. 232-1]
1SL frames with this test ID are considered for 1SL sessions. Only relevant for LM type “1SL”.
 1SL Initiator [true, false]
Enables the transmission of 1SL frames. If not activated, the session only acts as a
1SL sink, generating LM statistics based on received 1SL frames. Only relevant for LM type “1SL”.
 Period [100ms, 1s, 10s]
Period between LM frames
 Ingress Policy
Policy used for counting Tx frames in case of Up-MEP or Rx frames in case of Down-MEP. The
index refers to the index in the ingress policy map of the port where the selected MEP resides.
Only relevant for LM types “LMM” and “CCM”.
 Egress Policy
Policy used for counting Tx frames in case of Down-MEP or Rx frames in case of Up-MEP. The
index refers to the index in the egress policy map of the port where the selected MEP resides.
Only relevant for LM types “LMM” and “CCM”.
 Applications (L2PT)

A3118-X642-R612-01 312 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Frames sent and received by the selected special applications are counted with this LM session.
Only relevant for LM types “LMM” and “CCM”.
 Use MEP ID / Target MEP ID
Enables and defines the target MEP ID. If enabled, Target MAC address cannot be set.
 Target MAC Address
If the remote MEP is not addressed by MEP ID (“Use MEP ID” disabled), the remote MEP’s MAC
address can be specified manually.
 LM VLAN
Defines the VLAN that is used for LM frames. Entries among the list of associated VLAN can be
selected. Not relevant if LM Type is “CCM”.
Attention: The LM VLAN can be different from the domain “source associated VLAN ID”.
 CoS Value [CoS 0 .. CoS 7]
Not relevant if LM Type is “CCM”.
 Transmit Queue [Queue#0 .. Queue#7]
Not relevant if LM Type is “CCM”.
 Accepted CoS Values
LMRs with the selected CoS values are accepted for this LM session. Not relevant if LM Type is
“CCM”.

Ingress / Egress Policy

The FLR and Availability measurement using LMM/LMR or CCM is based on the evaluation of the
frames counted in ingress and egress direction of a specific service. Based on these counter values,
the FLR and availability is calculated.
In order to count the frames belonging to a specific service, an ingress and egress policy needs to be
set up and assigned to the port where the frames should be counted. Additionally, these policies need
to be assigned in the LM session.
For more information on policing, please refer to  8.7.3

 The used policies needs to apply a bandwidth profile, and only frames marked as green
by the bandwidth profile are considered for the FLR and Availability measurement.
Global counter setting
If LM is done using LMM/LMR or CCM, metering counters need to be set to packets according to the
picture below.
These settings are done on switch level and therefore apply to all ports.

A3118-X642-R612-01 313 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 Ethernet/Switch […]/

Only Ingress and Egress Metering Counters need to be set to “Packets” to use LM. Ingress
and Egress Policy Counters are not relevant for LM

Dual-ended frame loss measurements are based on the LM type CCM or 1SL and
therefore an LM session needs to be configured on each end.
 Single-ended frame loss measurements are based on the LM type LMM or SLM. These
configurations consist of a LM Session on the initiating MEP and a LM Responder on the
other MEP.

9.2.3.2.2 LM Responder configuration

LM responders are required for single-ended loss measurement, i.e. when LM type LMM or SLM is
used.
Up to 60 loss measurement responders per ACCEED unit can be configured.

 Responders can be added using the Add button.

../SOAM/Performance/LM Responders/

The following parameters are available:

 Enable
 Maintenance Point [MP1 .. MP30]
 Ingress Policy

A3118-X642-R612-01 314 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Policy used for counting Tx frames in case of Up-MEP or Rx frames in case of Down-MEP. The
index refers to the index in the ingress policy map of the port where the selected MEP resides
 Egress Policy
Policy used for counting Tx frames in case of Down-MEP or Rx frames in case of Up-MEP. The
index refers to the index in the egress policy map of the port where the selected MEP resides
 Applications (L2PT)
Frames sent and received by the selected special applications are counted with this LM session.
 LM VLAN
Defines the VLAN that is used for LMM/LMR frames. Entries among the list of associated VLAN can
be selected.
Attention: The LM VLAN can be different from the domain “source associated VLAN ID”.
 CoS Value [Incoming CoS]
LMRs are always sent back with the same CoS value as the received LMM.
 Transmit Queue [Queue#7]
 Accepted CoS Values
LMMs with the selected CoS values are accepted for this LM session.
9.2.3.2.3 LM Session Statistics
LM session statistics and history are configured the same way as DM session statistics with the
following exceptions:
- FLR and Availability statistics can be configured independently whereas statistics
configuration for FD and IFDV is combined. This allows to have different statistics interval
durations for FLR and Availability
- Larger interval duration range for FLR and Availability [1..525’600min (1year)]
Please refer to  9.2.3.1.3 for information on how to configure the statistics and history section.

A threshold can be defined on the average FLR to raise an alarm in case of high FLR. The alarm is
raised if the average FLR threshold is exceeded after completion of a statistics interval. After that the
alarm remains active until a statistics interval is completed with an average FLR below the threshold.

A3118-X642-R612-01 315 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 ../SOAM/Performance/LM Sessions/Session x/FLR

Thresholds can only be changed when the LM Session is not enabled.

FLR results are available in the Performance tab (for current and historic intervals) under
../SOAM/Performance/LM Sessions/Session x/FLR

Note: In case of dual-ended synthetic LM using 1SL, only backward results are available.
The current Availability is evaluated immediately after each single FLR measurement. The size of the
sliding window (n) as well as the FLR threshold (C) between high and low FLR are configurable.
Availability Alarms also exist. Unlike for FLR alarms, Availability alarms are not only raised after
conclusion of a statistics interval, but immediately when the ratio of single measurements in the
current interval with an “Unavailable” result exceeds the configured Unavailability threshold.

A3118-X642-R612-01 316 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 ../SOAM/Performance/LM Sessions/Session x/Availability

Thresholds can only be changed when the LM Session is not enabled.

Availability results are available in the Performance tab (for current and historic intervals)
under
../SOAM/Performance/LM Sessions/Session x/Availability

Note: In case of dual-ended synthetic LM using 1SL, only backward results are available.

A3118-X642-R612-01 317 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

9.3 Service Activation Test (Y.1564)

The ACCEED built in Service Activation Test (SAT) allows evaluation of layer 2 key performance
parameters for a service that is newly implemented.

SAT can be performed prior to deploying the "live service” for verifying the quality requirements of a
MEF service. These requirements are:
 Committed Information Rate (CIR)
 Excess Information Rate (EIR)
 Frame Loss Ratio (FLR)
 Availability
 Frame Delay (FD) (Round-trip based, i.e. fd = measured round-trip delay / 2)
 Inter-Frame Delay Variation (IFDV) (Round-trip based, i.e. ifdv = abs(fd_t2 – fd_t1)

At the end of the measurement, a report is generated with the results, and PASS/FAIL is indicated.

The qualification measurement can also be performed in service, in parallel with running traffic
belonging to previously installed services on the ACCEED unit. No additional equipment is required to
perform SAT measurements with ACCEED. Traffic generator and analyzer are built in functions of the
ACCEED unit.

Up to 4 different customer traffic flows (Test CoS Instances) are emulated on the ACCEED unit, sent
out through the defined testport to the destination network element. The destination network element
has looped back activated which sent back these traffic flows with swapped source and destination
MAC addresses. At arrival on the SAT flow injecting ACCEED the flows are terminated and evaluated.
The necessary layer 2 loopback with MAC swapping can be performed with an ACCEED unit or any
capable 3rd party equipment. Note: A loopback without MAC swapping would also work, but may lead
to unpredictable traffic conditions (e.g. Port locks due to STP or overload conditions of MAC learning
events on old switching devices)

Figure 9-19 Service Activation Test example

This methodology of measuring traffic during the activation phase of a service is based on the Y.1564
standard (formerly known as Y.156sam).
It closes the gap between RFC2544 method and the today’s service demand, by
 Testing services along the network and not the maximum limit of just one network element
 Verifying CIR and EIR profiles
 Doing recurring frame delay and frame delay variation measurements
 Measuring frame loss and availability
This advanced set of actions enables the network planners and service teams to bring up services
quickly and to troubleshoot in case of Service Level Agreement violations.

A3118-X642-R612-01 318 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Y.1564 is separated in 2 phases: the Service Configuration Test, verifying the configuration of the
bandwidth profile parameters, and the Service Performance Test, proving the long term stability of the
new service.

Measurement Principle
The ACCEED acts like a 100 Mbit/s Ethernet traffic generator and detector. The traffic is injected into
the existing service through the generator ingress policy.

Figure 9-20 Service Activation Test Principle

This test traffic is then forwarded via the WAN interface (or any other configured test port) to Carrier
Ethernet network to the remote Ethernet demarcation unit. This unit must be capable of swapping the
Source with the Destination MAC and loop the packets back to the local EDD.

On its way the test packets pass the egress policy of the local WAN, the ingress policy of the remote
WAN, the egress policy of the remote WAN and before passing the ingress policy of the local WAN
they are trapped to the analyzer.
In most cases services are defined by ingress policies. Therefore, by default only the ingress policy of
the remote ingress is tested with SAT. If the ingress policy of the service at the local EDD should be
tested, the ACCEED has the ability to use the same ingress policy of the LAN port. This is done by
applying the corresponding ingress modifier of the LAN port to the SAT/Test CoS Instance/Applied
Modifier.

Always take all ingress and egress bandwidth profiles along the SAT stream into account.
They may influence your measurement by additional bandwidth restrictions (smallest
information rate wins) or burst sequence cuts (smallest burst size wins)
 For trustful measurements it is recommended to start with one bandwidth profile, the one
with the highest CIR/PIR values and to measure the throughput. Then add step by step the
other bandwidth profiles in decreasing bandwidth order and measure each time.

In principle initiating SAT measurements from both sides provide the most accurate results.

The test stream consists of performance packets for evaluating the maximum bandwidth based on CIR
and EIR, which is accumulated in “color blind” mode to one PIR, and timing packets for measuring the
roundtrip delay.
The format of the test frames is described in  9.3.3

A3118-X642-R612-01 319 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Measurement Sequence Details

The SAT is a sequence of measurements evaluating the different service parameters, which are
CIR: prove the transmission of CIR
CIR+EIR: prove that CIR is granted and EIR possible
Traffic policing: prove the limitation capabilities of the used bandwidth profiles
Service Performance: prove long term stability of the CIR Test

Figure 9-21 SAT sequence

The performance parameters FLR, Availability, frame delay, inter-frame delay variation are based on
measurements of CIR frames only.

9.3.2.1 CIR Test

This test case creates a throughput and delay stream for each of the configured Test CoS Instances
with the bandwidth configured in the CIR field and transmits it to the SAT test port. The received data
rate (rxRate) is not allowed to be above the CIR. The frame loss ratio (FLR), frame delay (FD) and
inter frame delay variation (IFDV) need to be below the configured thresholds too.

This test will PASS, if the following parameters are matched for each instance

CIR  (1  FLRThreshold)  rxRate  CIR

rxFLR  FLRThreshold
rxFD  FDThreshold
rxIFDV  IFDVThreshold

9.3.2.2 CIR+EIR Test

This Test case creates for each of the configured Test CoS Instances a throughput and delay stream
with the sum bandwidth configured in the CIR and EIR field (PIR) and transmits it to the SAT test port.
The received data rate (rxRate) is not allowed to be above the sum of CIR and EIR and the frame loss
ratio (FLR) of the CIR stream is not allowed to be greater than the configured one. The configured
thresholds for frame delay (FD) and inter frame delay variation (IFDV) need to be covered too.

This test will PASS, if the following parameters are matched for each instance

CIR  (1  FLRThreshold)  rxRate  (CIR  EIR)

rxFLR  FLRThreshold
rxFD  FDThreshold

A3118-X642-R612-01 320 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

rxIFDV  IFDVThreshold

The sum of all txRates shall not exceed 100 Mbit/s. This allows the maximum for this test case of
Σ(CIR+EIR) = 100 Mbit/s.
9.3.2.3 Traffic Policing Test
Goal of this test case is to overshoot (by up to 25%) the throughput service limits and test the limitation
capabilities of the bandwidth profile rules. For each of the configured Test CoS Instance a throughput
and delay stream is created. The transmit rate depends on the ratio between CIR and EIR:

If CIR  (5  EIR ) (true for most 2 rate three colour bandwidth profiles)
txRate  CIR  ( EIR  125 %)
Else (true for most single rate three colour bandwidth profiles)
txRate  (CIR  125 %)  EIR

The sum of all txRates shall not exceed 100 Mbit/s. This allows the maximum for this test case of
Σ(CIR+EIR) = 80 Mbit/s.

This test is especially designed to get into congestion of the bandwidth profile under test. Therefore
not only the bandwidth parameters (CIR and EIR) need to be taken into account, but also the burst
buffer sizes (CBS and EBS). They define how many traffic bursts are allowed, before the bandwidth
profile starts dropping traffic.

Therefore the Y.1564 introduced a correction factor called MFactor adjusting the upper bandwidth limit.
Its range is between 0% and 25% and it depends on the burst buffer size, the test duration and the
txRate. The default value of the MFactor on the ACCEED is 10%. It can be roughly calculated with the
following formula, where the CBS&EBS are in [Bytes] and CIR&EIR in [kbit/s] for the Bandwidth profile
under test:
 CBS  EBS 1 8
M Factor      %
 CIR  EIR SingleTestDuration 10 
The maximum received data rate shall not exceed the sum of CIR and EIR corrected by the M Factor and
its lower limit is the CIR with its allowed frame loss ratio. The configured thresholds for frame delay
(FD) and inter frame delay variation (IFDV) need to be matched, too.

This test will PASS, if the following parameters are matched for each instance

CIR  (1  FLRThreshold)  rxRate  (CIR  EIR)  (1  M )

rxFLR  FLRThreshold
rxFD  FDThreshold
rxIFDV  IFDVThreshold

9.3.2.4 Service Performance Test

This test equals the CIR test ( 9.3.2.1), but with a much longer measurement period.
Additionally the Availability of the Service is validated.

This test will PASS, if the following parameters are covered for each instance

CIR  (1  FLR )  rxRate  CIR

rxFLR  FLRThreshold
rxFD  FDThreshold

A3118-X642-R612-01 321 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

rxIFDV  IFDVThreshold
rxAvailability  AvailabilityThreshold

Format of Test Frames

The test frames of the SAT test have the following format:

MAC DA 6 Bytes
MAC Header
MAC SA 6 Bytes
Tunnel sTag Primary TPID 2 Bytes
(optional) .1p bits + VLAN ID 2 Bytes
TPID = 0x8100 (fix) 2 Bytes
VLAN cTag (optional)
.1p bits + VLAN ID 2 Bytes
Ethertype 0x88’B7 2 Bytes
Albis OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier
Albis Ethertype (0x00’11) 2 Bytes
Sequenznummer 4 Bytes
Payload
Padding (0x00) variable
FCS 4 Bytes
Table 14 Format of Test Frames for throughput measurement

MAC DA 6 Bytes
MAC Header
MAC SA 6 Bytes
Primary TPID 2 Bytes
Tunnel sTag (optional)
.1p bits + VLAN ID 2 Bytes
TPID = 0x8100 (fix) 2 Bytes
VLAN cTag (optional)
.1p bits + VLAN ID 2 Bytes
Ethertype 0x88’B7 2 Bytes
OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier Albis Ethertype 2 Bytes
(0x00’90, 0x00’91, 0x00’92)
TxTimeStampf 8 Bytes
(like DMM)
Payload RxTimeStampf 8 Bytes
(like DMM)
Padding (0x00) variable
FCS 4 Bytes
Table 15 Format of delay measurement frames

Frame Length Albis Ethertype

EMIX: 64 Bytes 0x00’10
EMIX: 128 Bytes 0x00’11
EMIX: 256 Bytes 0x00’12
EMIX: 512 Bytes 0x00’13
EMIX: 1024 Bytes 0x00’14
EMIX: 1280 Bytes 0x00’15
EMIX: 1518 Bytes 0x00’16
EMIX: 2040 Bytes 0x00’17
Fixed Size: 64..2048 Bytes 0x00’1F
Table 16 Albis Ethertypes

A3118-X642-R612-01 322 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

SAT – General configuration

►Ethernet/Switch […]/SAT

Figure 9-22 Service Activation Test example

The following parameters can be configured:

 Service Configuration Test
Includes all defined Service Configuration Tests in the test report
 Service Configuration Setup
CIR Test
CIR EIR Test
Traffic Policing Test
 Service Performance Test
Includes Service Performance Test in test cycle and test report
 Detailed Test Report
A detailed test report includes the results of each single EMIX frame size
 Color Mode
“Color Blind” is the only option in this release. It describes, that the generator is injecting packets
without any pre-coloring (e.g. DEI bit)
 Color Method
only valid for “color aware” color mode. It describes which parameter identifies the color of the
returned SAT stream, if the opposite device remarks its color decision into each frame of the
stream. Possible methods are PCP (.1p), DEI-Bit, DSCP-Values, VID, …
“PCP” is the only option in this release.
 Single Test Duration [10 .. 600 seconds]
Defines the runtime of each single test in the Service Configuration section
 Test Duration [1 .. 1440 minutes]
Defines the runtime of the Service Performance test
 Test Port
Defines the transmit and receive port of the SAT traffic, e.g. P1, P2, P3, SFP1, BPL, WAN1, …
 Destination MAC Address
Sets the target MAC Address of the Destination. Typically it is the MAC of the Loopback device

A3118-X642-R612-01 323 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 Tunnel VLAN
Defines if a tunnel VLAN is added (common to all CoS Instances)
 Tunnel VLAN ID
Sets the S-Tag VLAN ID in case of an VLAN tunnel

Additionally the following information is available:

 Source MAC Address
Views the Source MAC of the Test port
 Delay Measurement Frame Period
Views the delay period of concatenated Delay Measurement Frames
 State
Views the state of the test, “Idle” for no SAT test running, “Running” for SAT tests are active, and
“Failed” if the SAT is wrong configured (i.e. no enabled tests or instances, maximal bit rate is
exceeded)
 Elapsed Time
Displays the number minutes elapsed of the service performance test
 Remaining Time
Displays the remaining time to finish the service performance test

SAT – Configuration of the Test CoS Instances

Figure 9-23 SAT Test CoS Instance

The following parameters can be configured:

A3118-X642-R612-01 324 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

 Enable
enables this test traffic instance with the following parameters
 Description
this description is printed into the test report after the “Test CoS Instance x:” label
 CIR [0, 64 .. 100000 kbit/s]
Committed information rate of the test traffic
 EIR [0 .. 100000 kbit/s]
Excess information rate of the test traffic
 Measurements
For each of the measurement parameters FLR, Availability, FD and IFDV it can be defined
whether or not the results are included in the final test report. If one of the parameters is not
selected, the corresponding threshold is not relevant, and the measurement result for that
parameter is not a PASS / FAIL criterion for the test.
 M Factor [0 .. 25 %]
Correction factor added on CIR+EIR threshold to compensate the start up effects of the burst
buffer settings (CBS and EBS)
 FLR Threshold [0 .. 100.000 %]
Maximum Frame Loss Ratio Threshold to detect a PASS
 Availability Threshold [0 .. 100.000 %]
Minimum Availability Threshold to detect a PASS
 Availability Consecutive Measurements [1 .. 10]
Number of successful Availability Measurements necessary to get an accountable result
 Availability FLR Threshold [0 .. 100.000 %]
This setting defines valid availability intervals in dependency of the FLR. If the Frame Loss Ratio is
below this threshold, the availability is accounted. See  9.2.3.2
 FD Threshold [0 .. 5000000 us]
Maximum Frame Delay acceptable for a PASS
 IFDV Threshold [0 .. 5000000 us]
Maximum inter frame delay variation acceptable for a PASS
 VLAN Tagged
enabled: a VLAN Tag is attached to all test frames configured in this Test CoS Instance.
“enabled” is the default setting for Instance 2, 3 and 4.
disabled: test frames are untagged
 Assigned VLAN ID [1 .. 4094]
This VLAN ID value is always attached to the VLAN Tag in case VLAN tagging is enabled,
otherwise for untagged frames it defines the internally assigned VLAN ID
 Assigned CoS Value [0 .. 7]
This .1p value is always attached to the VLAN Tag in case VLAN tagging enabled
 Accepted CoS Value
Outgoing CoS: Received SAT frames are only accepted by this CoS instance if their CoS value
is identical to the CoS value of frames transmitted by this CoS instance. Normally,
the Outgoing corresponds to the Assigned CoS Value, but the Applied Modifier
could force an Outgoing CoS Value which is different from the originally Assigned
CoS Value (if no VLAN tunnel is present). “Outgoing CoS” is the default
configuration.
Any: This CoS instance accepts received frames with any CoS value. Note: In this
case, no other CoS instance must be activated with the same VLAN ID.
CoS 0 .. Cos 7: This CoS instance only accepts received frames with this specific CoS value
 Accepted Tunnel CoS Value
Outgoing CoS: Received SAT frames are only accepted by this CoS instance if their tunnel CoS
value is identical to the tunnel CoS value of frames transmitted by this CoS
instance. Normally, the Outgoing corresponds to the Assigned CoS Value, but the
Applied Modifier could force an Outgoing CoS Value which is different from the
originally Assigned CoS Value. “Outgoing CoS” is the default configuration.

A3118-X642-R612-01 325 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Any: This CoS instance accepts received frames with any tunnel CoS value.
CoS 0 .. Cos 7: This CoS instance only accepts received frames with this specific tunnel CoS
value
 Applied Modifier
To verify correct configuration of an ingress policy, an ingress modifier can be applied to SAT
frames. For example, if an ingress policy is applied at a UNI port, the modifier of that policy can
also be applied to SAT frames.
 Frame Pattern
“Fixed Size”: All test frames do have the same length
“EMIX”: Frames are sent in a repeating sequence of configurable frames with sizes 64B, 128B,
256B, 512B, 1024B, 1280B, 1518B or 2048B
 EMIX Frame Sizes
Selectable frame sizes 64B, 128B, 256B, 512B, 1024B, 1280B, 1518B or 2048B
 Frame Size [64 .. 2048 bytes]
Sets the frame length of all test frames, if frame pattern is “Fixed size”

The “Frame Command” and “Redirected Port” parameters of the Applied Modifier have no
influence on SAT frames. Also, if a tunnel VLAN is set in the general SAT configuration (
9.3.4), the “VLAN Command” and “Primary VLAN ID” of the Applied Modifier are ignored. If
 no tunnel VLAN is set in the general SAT configuration, the “VLAN Command” of the
Applied Modifier should be set to its default value for correct operation.
All other parameters of the Applied Modifier (like Bandwidth Profile, QoS attribute
manipulations) are also relevant for SAT frames

Test execution
The SAT can be executed by pressing the “Start” button in the Configuration tab under
Ethernet/Switch […]/SAT. It can be terminated any time during the test phase by pressing the “Abort”
button.
The test report can be displayed anytime during the tests showing the current status of the test cases
by pressing the “Test Report …” button.
At the end of the test the test report automatically pops up with the final results. It can be stored as a
text or pdf file by pressing the “Save As…” button on the bottom of the test report window.

Results

Figure 9-24 SAT Results

A3118-X642-R612-01 326 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Additionally the following information is available:

 Test
Name of the current test in operation (CIR, CIR EIR, Traffic Policing or Service Performance)
 Minimum Information Rate
Minimum received data rate since start of test
 Average Information Rate
Average received data rate since start of test
 Maximum Information Rate
Maximum received data rate since start of test
 Frame Loss Ratio
Ratio of lost frames vs sent frames in the Class CIR
 Availability
Availability since start of the actual test
 Minimum Frame Delay
Minimum roundtrip delay of the delay measurement frames
 Average Frame Delay
Average roundtrip delay of the delay measurement frames
 Maximum Frame Delay
Maximum roundtrip delay of the delay measurement frames
 Minimum Inter-Frame Delay Variation
Minimum roundtrip delay variation between two consecutive delay measurement frames
 Average Inter-Frame Delay Variation
Average roundtrip delay variation between two consecutive delay measurement frames
 Maximum Inter-Frame Delay Variation
Maximum roundtrip delay variation between two consecutive delay measurement frames
 Total Throughput Frames Sent
Complete number of test frames sent for throughput measurement
 Throughput Frames Received
Number of test frames received that are corresponding to the throughput measurement
 Throughput Frames Lost
Number of frames dropped from the throughput test stream
 Delay Frames Sent
Number of transmitted delay measurement frames
 Delay Frames Received
Number of correctly received delay measurement frames
 Delay Frames Lost
Number of lost delay measurement frames
 Total CIR Frames Sent
Number of test frames sent within the configured CIR traffic parameters

A3118-X642-R612-01 327 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Test Report
The test report has two sections: First the setup parameters and second the measurement results.

Figure 9-25 SAT Test Report

In the first section the basic configuration of the System (Date and Time, Firmware Version, Hardware
ID and Slot number) and the test port (Test groups enabled, color mode, color method, port name,
MACs and Tunnel VID) are printed. It is followed by the configuration of each Test CoS Instance that
is enabled (CIR, EIR, M, Pattern, Size, VID and CoS, as well as FLR, Availability, FD and IFDV
thresholds, if the corresponding measurement parameters are enabled).

The second section contains the results of each single test parameter that is selected in the Test CoS
Instance configuration. The headline of each test section (service configuration test or service
performance test) shows the overall result.
A FAIL of one of the test parameters leads to a FAIL of the whole Test Cos Instance and is shown in
the headline. This FAIL leads then to a FAIL of the whole test section.

Additionally, the results for each single EMIX frame size are displayed if the detailed test reports are
enabled. The results are not assessed with a “FAIL/PASS”.

A3118-X642-R612-01 328 / 405

 ULAF+ 9 - Operation and Maintenance ACCEED 1102/04 Manual

Parameters displayed and controlled in the Test CoS Instances are:

 Information Rate (Minimum, Average and Maximum rxRate) in kbit/s

 Frame Loss Ration of CIR in %
 Availability (service performance test only) in %
 Frame Delay (Minimum, Average and Maximum) in μsec.
 Inter Frame Delay Variation (Minimum, Average and Maximum) in μsec.

Parameters just displayed in the Test CoS Instances are:

 Throughput Frames (Sent, Received and Lost) in number of frames

 Delay Frames (Sent, Received and Lost) in number of frames
 Total Frames (Sent, CIR Sent, Received, and Lost)

At the end of the test, the test report automatically pops up with the final results. It can be stored as a
text or pdf file by pressing the “Save As…” button.

The default filename for the test report is generated from the unit’s Management IP and its slot
position number, e.g. “Test_Report_192.168.1.1_S13”

A3118-X642-R612-01 329 / 405

ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10
CES – Circuit
Emulation for TDM
Services

This chapter starts with a general introduction to CES. This is followed by

the description of the CES application options with ACCEED. In the third
part, the CES configurations, performance and alarm management
capabilities are explained.
The last section covers the operational aspects of CES.

A3118-X642-R612-01 330 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Reference to CES Standards

The list gives an overview of the available standards and recommendations for TDM CES with the
supported encapsulation and payload types. The figure below shows all possible CES solutions and
what is realized with the ACCEED in the red frame.

 MEF – Metro Ethernet Forum

MEF 8 - Implementation Agreement for the Emulation of PDH Circuits over Metro
Ethernet Networks [CESoETH]
Encapsulation: Ethernet
Payload Type: CESoPSN and SAToP

 ITU – International Telecommunication Union

Y.1413 - TDM-MPLS network interworking – User plane interworking
Encapsulation: MPLS
Payload Type: CESoPSN and SAToP

 Broadband Forum (IP/MPLS Forum)

IA 8.0.0 - Implementation Agreement- Emulation of TDM Circuits over MPLS Using Raw
Encapsulation – a.k.a. [CESoMPLS]
Encapsulation: MPLS
Payload Type: CESoPSN and SAToP

 IETF – Internet Engineering Task Force

RFC 4553
Structure-Agnostic Time Division Multiplexing (TDM) over Packet [SAToP]
Encapsulation: MPLS, IP
Payload Type: SAToP
RFC 5086
Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet
Switched Network [CESoPSN]
Encapsulation: MPLS, IP
Payload Type: CESoPSN

Figure 10-1 CES standards overview

A3118-X642-R612-01 331 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.1 Introduction to TDM CES

What is CES ?
CES stands for Circuit Emulation Services and describes the emulation of a TDM circuit over a packet
network.
The packet network is invisible to the TDM source and destination equipment.
The main differences between the conventional TDM transmission compared to CES are:
 Fix data rate (time slots) compared to statistical packet multiplexing
 Strict clocking compared to clock recovery
 Continuous time slots compared to out of sequence packets

Figure 10-2 The CES principle

Motivation to do CES
The motivation to introduce CES is mainly based on the fact, that the traditional TDM or ATM networks
are being accompanied or even replaced by more scalable and more economical packet networks.
CES therefore allows a smooth phase out of the legacy networks.

The following points list further motivations to introduce CES

 Continue to provide high margin legacy TDM services
 No need to replace customer equipment or interfaces
 Single solution to offer TDM and Ethernet services from the same EFM platform
 Reduce cost and risks to operate legacy networks by phasing them out

Technical Challenges
The different approach of transporting the TDM service with CES compared to the traditional TDM way
implies some technical challenges which need to be carefully looked at when considering an
introduction of CES.
The challenges are:
 Clock recovery and synchronization
With a packet network, the connection between the ingress and egress frequency is broken,
since packets are discontinuous in time
 Delay and Jitter
Packetization and jitter buffer adding delay which are crucial to some applications (e.g. voice,
mobile, backhauling)
 Frame Loss and Reordering
Packets can be dropped in the packet network or packets may not arrive in the order they
have been sent out.
The answers to these challenges are addressed by the ACCEED CES solution and are explained in
the following chapters.

A3118-X642-R612-01 332 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Payload Type and Encapsulation

Payload Type
TDM signals can be divided in structured and unstructured signals.
Structured (structure aware) TDM consists of a framing with time slots as defined in ITU-T G.704
where as unstructured (structure agnostic) TDM is a bit stream with no framing information.

The TDM payload type therefore needs to be defined in the CES IWF (Inter-Working Function).
Structure aware TDM payload is referred to as
 CESoPSN Circuit Emulation Service over Packet Switched Network

With CESoPSN the configured subscriber rate (nx64kbit/s) is transmitted by the CES IWF.
Time slot zero is not transported over the packet network. The time slot zero is generated at the
far end IWF and added to the TDM frame. The maximum subscriber rate with CESoPSN is 31 TS
or 1’984 kbit/s (time slot 1 ..32).
Example: A service with 512 kbit/s (8 TS) should be transmitted via CESoPSN. The TDM service
must arrive in timeslot 1-9 at the ACCEED. All information in TS0 (e.g. SA-Bits) are not forwarded.

Unstructured TDM payload is known as

 SAToP Structure Agnostic Time Division Multiplexing (TDM) over Packet

With SAToP the complete TDM (32 TS) bit stream is transmitted and the data rate is 2’048kbit/s.

ACCEED supports both payload types, CESoPSN and SAToP.

Encapsulation
The encapsulation defines the network layer protocol and adaption function used to transport the
TDM payload.

The
Figure 10-1 gives an overview of the network layer and adaption function options.
ACCEED supports Ethernet and MPLS encapsulation as indicated by the red frame below.
The adaption function consists of a service ID, a control word and an optional RTP part.

The 4 Byte service ID is the ECID (Emulated Circuit Identifier) in case of Ethernet encapsulation and
the pseudo wire label in case if MPLS encapsulation to identify the CES service (the pseudo wire).
The service ID must be configured for both directions – source and destination CES IWF.

A3118-X642-R612-01 333 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

The 32 Bit ECID consists of a 20 Bit user definable value followed by the last 12 Bit which are
reserved and are set to “0x102” in order to interwork with an MPLS-based circuit emulation service.
The Emulated circuit identifiers have local significance only, and are associated with the source MAC
address of the CES stream.
The 32 Bit MPLS pseudo wire ID has also a 20 Bit user definable value, followed by the S-Bit, 3 bit for
the traffic class (Experimental Bit – EXP) and the 8 Bit Time to Live (TTL) value.

The 4 Byte long control word allows detecting packet loss and wrong packet order by the sequence
number. It also contains defect indication information coded in the L, R and M bit..Please see also the
CES control word structure in the figure below.
The control word is automatically generated by the CES IWF.

Figure 10-3 Structure of the CES Control Word

L and M bit
The local TDM failure indicates a TDM defect impacting the TDM data.
When the L bit is set, the payload of the CES packet is set to 1 (one).
The M bit is set to supplement the meaning of the L bit.
The following local TDM failure indication are mapped to the L- and M-bit with ACCEED:
L M
Interpretation
Bit 4 Bit 6 Bit 7
0 0 0 Indicates no local TDM defect detected.
0 1 0 Reports the receipt of RAI or RDI at the local TDM interface in case the
framer is set to termination or monitoring. CES-RAI is raised at the remote
IWF.
1 0 0 Indicates a local TDM defect that triggers CES-AIS generation at the
remote CES IWF.
Local TDM defect is LOS in case the framer is set to transparent operation
and LOS, AIS, or LFA in case the framer is set to termination or
monitoring.

R bit
When the R bit is received, it indicates that the remote IWF did not receive the CES frame and
consequently has raised a LOF alarm. AIS is sent the TDM interface.
Thus the setting of the R bit indicates failure of the connection in the opposite direction. This indicates
congestion or other network related faults.

The fragmentation bits (FRG) are not used with ACCEED and are set to 0 (zero).

CES - Functional Components and Interfaces

Simplified, the CES feature can be divided in 2 components as shown in Figure 10-4, the CES IWF
and the optional Framer. It has an interface to the TDM and packet side.
Both interfaces are explained below.

Circuit Emulation Service Inter-Working Function (CES IWF)

The CES IWF is responsible for all functions required for the emulated service. This includes the
following:
 Encapsulation and decapsulation
 Payload formation and extraction
 Synchronization

A3118-X642-R612-01 334 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

 Carriage of TDM signaling and alarms

 Error Response and Defect Behaviour
 TDM performance monitoring

Framer
The Framer is an optional component that operates on the TDM interface and produces the service
(e.g. G.704 or n*64 kbit) that is emulated across the packet network.

In case of ACCEED the framer can be configured to operate the following modes:
Transparent: signal passes unchanged
Monitoring: signal passes unchanged, framing and CRC4 errors are evaluated
Termination: frame is regenerated, CRC4 section is terminated

Figure 10-4 CES functional components

A3118-X642-R612-01 335 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

There are two basic interfaces in the TDM domain. These are indicated in the

Figure 10-5 as TDM Interface and CES TDM Interface.

The following functionality is provided on these service interfaces:

TDM Interface
At this interface the actual TDM service is handed off to the customer or TDM network operator. It
therefore provides a physical connector. In case of ACCEED it is a RJ-45 connector for the E1 service.
The TDM service can be transported in two ways, structure-agnostic or structure-aware. See also 
10.1.4.

DMS Interface
Additionally to the E1 TDM interfaces, an ACCEED unit with optional data module slot (DMS) is
available. The data module slot can be deployed with an X.21, V.35 or V.36 data modules.
Two E1 TDM interfaces and one TDM E1 and one data module can operate concurrently.
For more information on the data modules, please refer to the ULAF+ system documentation (TED
and IMN) as refered to in  2.1

CES TDM Interface

The actual circuit service that is emulated between interworking functions through the packet network.
In case of ACCEED the following CES TDM interface types are supported:
 E1 at 2.048 Mbit/s as defined in ITU-T Recommendations [G.702] and [G.704]
 N x 64kbit/s data (i.e. 64 kbit/s, 128 kbit/s, 192 kbit/s) such as defined in ITU-T
Recommendation [I.231.1]

The following functionality is provided on the transport interface:

Ethernet Interface

A3118-X642-R612-01 336 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

The Ethernet interface is the transport interface where the CES packets are sent to and received from.
The CES frame format is shown in

Figure 10-5.
The Ethernet interface in ACCEED is referred to as Egress Port and can be configured as any switch
port of the ACCEED unit (Px, SFPx and WANx).

A3118-X642-R612-01 337 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

CES frame format

The frame format of the CESoETH and CESoMPLS are similar.
The differences are:
 The EtherType
 The CES circuit identifier: ECID for CESoETH, MPLS tunnel- and pseudo wire label for
CESoMPLS

Figure 10-5 Format of CESoETH and CESoMPLS frames

CES operation principle

Figure 10-6 illustrates the principle of CES operation. Please note that only one direction of the traffic
is shown in the figure. The TDM traffic shown on the left side enters the CES IFW (Inter Working
Function) and is being packetized.
The CES IWF sends then the resulting packets into the packet network. They are transported through
the packet network where they are received on the far end CES IWF. The packets may get different
delays (jitter) travelling through the packet network or changed packet ordering when they arrive. The
different colours of the packets indicate their transmit and receive order.
The jitter buffer compensates the delay variation (jitter) that the packets have experienced in the
packet network.
The larger (deeper) the jitter buffer, the more packet delay variation (PDV) can be compensated.
Payload size (TDM payload size per packet) and jitter buffer are configurable in the ACCEED unit and
influence the end to end delay accordingly. Additionally to the delay introduced by the CES
packetization and jitter buffer function, the network propagation delay caused by the packet network
adds to the end to end overall delay.

Figure 10-6 CES operation overview

A3118-X642-R612-01 338 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Packetization
The size of TDM payload per packet influences the following parameter:

 Bandwidth Efficiency
The larger the payload per CES packet, the lower the overhead ratio. Larger packets therefore
result in better bandwidth efficiency.
PayloadSize [ Bytes ]
BandwidthEffciencyCESoEth[%] 
30  PayloadSize [ Bytes ]
PayloadSize [ Bytes ]
BandwidthEffciencyCESoMPLS [%] 
34  PayloadSize [ Bytes ]

SubscriberRate[kBits / s ] *100
TotalBandwidth[kBit / s ] 
BandwidthEffciency[%]

 Packetization Delay
The packetization delay is dependant on the choosen payload size per packet and the TDM
subscriber rate.

PayloadSize [ Bytes]
PacketizationDelay [ms ] 
8 * SubscriberRate[TS ]
Note: in case of SAToP payload type, the subscriber rate is always equal to 32 time slots [TS]

The optimal compromise between bandwidth efficiency and packetization delay is depending on the
operators requirements.
Example:
The default CES packet payload size in ACCEED is 256 Bytes which results in a packetization delay
of 1ms for a subscriber rate of 32TS (2’048 kBit/s). The resulting Bandwidth Efficiency is 89.5% for
CESoEth and 88.3% for CESoMPLS. This equals 2’288 kBit/s and 2’320 kBit/s respectively on the
Ethernet transmission interface.
Jitter Buffer
When packets arrive at the far end CES IWF, they can be out of sequence or arrive too early to be
delivered to the TDM interface. The jitter buffer allows the reordering of the packets to compensate the
packet delay variation (PDV) to a certain extent, depending on the chosen jitter buffer size.

The reordering of the packet is based on the sequence number contained in the control word of each
CES packet. When a packet is received, the sequence number is verified and reordering is done if
applicable.

The jitter buffer is initialized to work at a fill grade of 50%. This leads to an initial delay caused by the
jitter buffer of 50% of the maximum delay variation that can be compensated by the jitter buffer.
The amount of delay and PDV can change dynamically in the packet network depending on e.g. the
load in the network elements.
To compensate this effect, ACCEED applies an algorithm which automatically adjusts the delay of
each packet to achieve a constant delivery of CES packets to CES IWF. This automatic adjustment of
the jitter buffer delay does not change the maximal size of the jitter buffer.
Note: In case of increased packet delay, the compensation of the packet delay variation is smaller
than in case of decreased packet delay.

Dimensioning the Jitter Buffer Size

A jitter buffer that is over dimensioned adds unnecessary delay, a jitter buffer that is too small will lead
to dropped packets in case of high packet delay variations.

The optimal jitter buffer size can only be set, if the maximum PDV is known. Since the PDV is
dynamic, the max. PDV need to be monitored over a period of time.

A3118-X642-R612-01 339 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Refer to  10.4.2 for information on how to read out the max. PDV with the LCT+
Knowing the maximal PDV, the jitter buffer size can be set to compensate this maximum jitter.

The jitter buffer size can be calculated according to the following formula:

PDVmax [ms ]  SubscriberRate[kbit / s]

JitterBuffer[ Bytes] 
8
For SAToP the following simplification can be done:
JitterBufferSAToP[ Bytes]  PDVmax [ms ]  256[ Bytes / ms ]

Example:
According to MEF 5, the CES IWF should be capable of compensating a frame delay variation (PDV)
of up to 10 ms. That means the maximum PDV is 10 ms.
The subscriber rate is 512 kbit/s with CESoPSN payload type.
The calculated jitter buffer size is:
10[ms ]  512[kbit / s ]
JitterBuffer[ Bytes ]   640 Bytes
8

The minimal Jitter Buffer size must be at least 2 times the configured payload size.

Please note that packets with large MTU size being transported over a low speed SHDSL

 link can add high jitter and therefore can be critical for a correct operation of the CES
service. A packet with MTU = 1500Bytes being transported over a single copper wire pair
at SHDSL data rate of 1Mbit/s, introduces a jitter of 12ms to the CES packets.
Therefore carefully plan the jitter buffer size in context of all traffic being sent over the
SHDSL link. In-band Management and OAM traffic also need to be taken into account.

Operator Hint:
Since the maximum PDV is normally not know when configuring the CES IWF for ACCEED, the
following procedure could be followed to define the jitter buffer size:
1. Establish the CES service with the default jitter buffer size of 4’096 Bytes.
Read out the measured maximum PDV after the value has reached the maximum as
described in  10.4.2.
2. Calculate the jitter buffer with the formula below. The
2 * max .PDV [ms ]  SubscriberRate[kbit / s ]
JitterBuffer[ Bytes ] 
8
3. Round up the calculated jitter buffer size to the next multiple of the payload size and enter the
jitter buffer size in the packet settings.
Example: the calculated value is 591 Bytes. The configured payload size is 256 Bytes.
The recommended jitter buffer size therefore is 768 Bytes.
4. Monitor the CES performance if there are any jitter buffer overflows or under runs.
5. In case of overflows/under runs, increase the jitter buffer size by multiples of the payload size.

Actual values of the packetization- and jitter buffer delay are provided by the ACCEED unit. For more
information please refer to  10.3.2 for packetization delay and  10.4.2 for jitter buffer delay.

A3118-X642-R612-01 340 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.2 CES Applications with ACCEED

The ACCEED CES solution can be deployed in various network scenarios to establish a TDM service.
Typical CES applications are shortly described and also reflected in the figure below.

Mobile Backhauling
CES can be deployed where no TDM network access is available or the TDM network will be
dismantled. In addition to the E1 traffic, the Ethernet traffic can also be transported on the same
access link. By this way, a hybrid mobile backhaul access solution can be realized.

TDM PBX
Many voice services today are still transported over TDM leased line services from the PBX at the
customer site to the central voice switch location.
Alternatively to these costly leased lines, CES can replace the leased lines by still providing the same
TDM interface towards the customer (PBX).
A migration from the TDM voice to VoIP at a later point is supported by the very same ACCEED unit.
This is achieved by using the Ethernet instead of the TDM/CES interface.

Router with TDM interface

Router interfaces based on E1 are still deployed in many customer sites. TDM leased lines provide
costly connectivity between the sites.
Replacing these leased lines by a CES solution can provide a cost efficient alternative to the leased
lines deployed today. Furthermore, any legacy service interface based on E1 can be replaced by the
CES solution with ACCEED (e.g. Frame Relay)
The migration to an Ethernet based service at a later point can be achieved with the same ACCEED
unit.

Router with Data Interface

In many locations transport interfaces based on X.21, V.35 or V.36 in the customer’s router equipment
are still in use. ACCEED provides a solution based on CES providing these data services, without the
need to further operate the TDM network between the sites.
The migration to an Ethernet based service at a later point can be achieved with the same ACCEED
unit.

The ACCEED 1102 and 1104 provide 2 E1 TDM interfaces that can be utilized for CES services. The
ACCEED 1104 provides the option to additionally utilize a data interface (X.21 or V.35/36).

A3118-X642-R612-01 341 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Figure 10-7 ACCEED 1102/04 – CES Application Overview

Interworking Scenario
To further enlarge the possible deployment scenarios, ACCEED CES is designed to interwork with the
ULAF+ MCU-CES solution and 3rd party equipment like CES gateways.
The Figure 10-8 shows 4 different interworking scenarios.
Interworking of the various CES solutions is depending on the implementation of the CES and TDM
parameters. Main parameters are defined in the payload type and CES adaption function and the

A3118-X642-R612-01 342 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

encapsulation. Please refer to  10.3 for more information on the ACCEED 1102/04 CES
configuration options.

Figure 10-8 ACCEED CES Network

A3118-X642-R612-01 343 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.3 Configuring CES

Enabling CES and the TDM interface

 The ACCEED 1102 and 1104 provide 2 E1 TDM interfaces which are represented as
TDM1 and TDM2 in the LCT+ view as shown in the figure below.
Optionally the ACCEED 1104 provides X.21 or V.35/36 data interfaces, represented as
DMS1.

 Enabling the CES function and the TDM interface can be done here:
CES IWF/Local/TDM/TDM1/2

 Mode [Clock, TDM] Clock: 2 MBit or 2048 kHz clock, see  11.4.2
TDM: 2 MBit/s clock
 Impedance [120, 75 Ohm] Impedance of TDM interface
 Description Individual interface description with up to 64 characters, e.g. Service
Name or Location

A3118-X642-R612-01 344 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

 Enabling the DMS1 interface can be done here:

CES IWF/Local/DMS/DMS1

Configuring the CES parameters

The CES parameters for TDM2 and DMS1 are identical as for TDM1 but need to be configured to with
different ECID or pseudowire labels respectively.

 The CES parameters are configured here:

CES IWF/Local/TDM/TDMx/Packet

Please refer to  10.1.6 for more information on jitter buffer- and payload size.

 Encapsulation [Ethernet, MPLS]

A3118-X642-R612-01 345 / 405
 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

 Payload Format [SAToP, CESoPSN]

 Egress Port [ any Ethernet port]
Defines the Ethernet port that sends and receives the CES stream

 Addressing Mode [Ethernet, IP], please refer to  10.3.2.1 for more information
 Destination MAC Address [00:00:00:00:00:00, destination MAC address], relevant only
in Ethernet addressing mode
 Destination IP Address [0.0.0.0, destination IP address], relevant only in IP addressing
mode
 Resolved Destination Address [read only]

Relevant only if Encapsulation = Ethernet

 Destination ECID [1 .. 1’048’575] destination ECID
 Source ECID [1 .. 1’048’575] source ECID
Note: the local Source ECID must match with the Destination ECID of the remote unit.

Relevant only if Encapsulation = MPLS

 Tunnel Ingress Label [1 .. 1’000 .. 1’048’575]
 Tunnel Egress Label [1 .. 1’000 .. 1’048’575]
 Tunnel Egress EXP Value [0 .. 7], Experimental Bit of tunnel egress label, typically used
for CoS.
 Tunnel Egress TTL Value [1 .. 255], Time To Live value of tunnel egress label

Relevant only if Encapsulation = MPLS

 Pseudowire Inress Label [1 .. 100 .. 1’048’575]
 Pseudowire Egress Label [1 .. 100 .. 1’048’575]
Note: the TTL value of the egress pseudowire label is set to 2 as defined in ITU-T Y.1413 since
the CES service is a point 2 point application. The TTL value can not be changed by the user.

 Pseudowire VLAN Defines if a VLAN tag is added to CES data (payload) AND control
traffic
 Pseudowire VLAN ID [1 .. 4094] VLAN ID that is assigned to CES data and control traffic
of this pseudowire
 CoS Value [0 .. 7] CoS value that is assigned to CES data traffic of this pseudowire
 Transmit Queue [0 .. 7], Transmit queue at egress port that is assigned to CES data
traffic of this pseudo wire

 Jitter Buffer Size [2 ..4’096 .. 8’192] Please refer to  10.1.6 for more information
 Maximum PDV Compensation The maximal possible PDV compensation based on the
configured jitter buffer size. This value is calculated and
therefore read only.
 Payload Size [1 .. 256 .. 1’023] Please refer to  10.1.6 for more information
 Packetization Latency Delay caused by the packetization. This value is calculated
and therefore read only.

 The assigned VLAN ID and CoS value must be the same in the local and remote packet
configuration of the IWF.

A3118-X642-R612-01 346 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.3.2.1 Addressing Mode

The Addressing Mode is referring to the method that is used to set the destination MAC address of the
remote circuit emulation function. This MAC address is used to send the CES packets to the remote
CES function.
The two methods are called Ethernet and IP addressing mode.

With the Ethernet addressing mode, the MAC address of the remote CES function must be known
and is entered in the field named “Destination MAC Address”. The local MAC address of the CES
function is displayed in the LCT+ under CES IWF/Local.

With the IP addressing mode, the destination MAC address is resolved based on the ARP process
and is therefore set in the “Resolved Destination MAC Address” field automatically.
In order to do so, the local and remote CES functions must be configured with appropriate IP
addresses, netmask and gateway information. Additionally, CoS value and transmit queue can be
configured for the CES control packets. The tagging configuration of the CES control packets is done
in the CES packet configuration section for each pseudo wire individually and is equal to the tagging
and VLAN ID of the CES data traffic (payload). Please refer to  10.3.2 for more information on the
CES packet configuration.
If the MAC address cannot be resolved a CES-ARE (Address Resolution Alarm) alarm is raised.
Please refer to  10.5.2 for more information on trouble shooting CES.

 The configuration of the IP addressing and control traffic for the CES function can be done
here:
CES IWF/Local

 IP Address [0.0.0.0, valid IP address]

 IP Netmask [0.0.0.0, valid netmask]
 Default Gateway [0.0.0.0, valid IP address]

 CoS Value [CoS 0 .. CoS 7]

 Transmit Queue [Queue #0 .. Queue #7]

 MAC Address MAC Address of the CES function. Read only value

 The Addressing configuration must be done on both ends of the pseudo wire and must
match the remote information. E.g. the MAC or IP addresses respectively must match.

Configuring the Framer

The framer can be configured independently from the payload type.

A3118-X642-R612-01 347 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

This can lead to invalid configurations in combination with the customer TDM signal.
Example: the customer signal is unframed and the framer is set to termination. This will generate an
alarm because the framer expects a framed signal but received the unframed bit-stream. The framer
will raise a loss of frame alignment alarm (TDM-LFA).
The following combinations are invalid and will raise a TDM-LFA alarm:
The customer signal is an unframed bit-stream according to G.703.
1) The payload type is SAToP and the framer is set to Monitoring or Termination
2) The payload type is CESoPSN. (All framer settings: Transparent, Monitoring or Termination)

 The configuration of the E1 framer can be done here:

CES IWF/Local/TDM/TDM1/E1 Framer

 Framing Mode of the E1 framer

Transparent signal passes unchanged
Monitoring signal passes unchanged, framing and CRC4 errors are evaluated
Termination CRC4 section is terminated, a new frame is generated
 Subscriber Bitrate [64, 128 .. 2’048 kbit/s], 1 to 32 time slots (TS)
Note: in case of a framed signal according to G.704, the maximal
possible subscriber rate is 1’984kbit/s or 31 time slots (TS). Time slot 0
(zero) terminated in the CES IWF.
 AIS Recognition [disabled, enabled]
In transparent mode by default AIS is not recognized. With this
parameter AIS recognition can be enabled in transparent mode. In
Monitoring and Termination mode AIS Recognition is always enabled.
When AIS is recognized, the AIS signal is also regenerated with the
device’s internal clock in case of an AIS condition.
 CRC4-TDM [disabled, enabled]
 CRC4-CES [disabled, enabled]

 The configuration of the data traffic can be done here:

CES IWF/Local/DMS/DMS1/Nx64k
Please note, the data of the data module are mapped transparently into the packets acc.
to RFC5086 Clause 5.2, known as Basic NxDS0 service.

 Bitrate [64Kbit/s (1TS) .. 2’048kBit/s (32TS)]

A3118-X642-R612-01 348 / 405
 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

 Control Circuits 106 [Auto / On]

107 [Auto / On]
109 [Auto / On]
141 [Auto / Off]

CES clock synchronization

Only synchronous clock applications are supported with ACCEED.
The clock for the IWF is derived from the active clock source in ACCEED.
The following clock sources are available:
 TDM interface (Frontpanel)
 SHDSL (SHDSL symbol clock)
 Internal clock
└110x_1404_1416_2104_2202_End

Please refer to  11.4.2 for information on the clocking options.

A3118-X642-R612-01 349 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.4 CES Performance Monitoring and

Fault management
TDM performance counters
The TDM counters are based on CRC4 errors.
The performance counter in ACCEED are defined according to ITU-T G.826

 The TDM performance of the TDM interface is displayed here:

CES IWF/Local/TDM

The TDM performance of the framer is displayed here:

 CES IWF/Local/TDM/TDM1/E1 Framer

 ET Elapsed Time
 BE Block Errors (A block in which one or more bits are in error)
 BBE Background Block Error (An errored block not occurring as part of a SES)
 ES Errored Seconds (A one-second period with one or more errored blocks or at
least one defect
 SES Severely Errored Seconds (A one-second period which contains ≥30% BE or at least
one defect)
 UAS Unavailable Seconds (counts if more than 10 seconds SES occurred)

A3118-X642-R612-01 350 / 405

ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

CES packet and jitter buffer performance

 The CES IWF packet performance is consisting of the packet statistic counters and the
CES jitter buffer performance.
The Packet Statistics can be displayed as a continuous counter and as history counter with
definable interval duration and stored number of intervals.
Up to 5 history counters can be added. Refer to  10.4.3 for the activation and
configuration of the packet statistics.
The packet and jitter buffer performance can be found here:
CES IWF/Local/TDM/TDM1/Packet

Please note, that the statistics view can be switched between “Continuous” and the defined
historic counters.

A3118-X642-R612-01 351 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

CES Packet Statistics

By default statistics are disabled and the performance values are displayed as “Inactive”. In order to
see any values, statistics must be enabled
Additionally, up to 5 historic counters can be configured here with defined interval duration and
number of intervals to be stored.

 The statistics settings can be accessed under:

 CES IWF/Local/TDM/TDM1/Packet/Statistics/Continuous

 CES IWF/Local/TDM/TDM1/Packet/Statistics/Historic[]

History settings can be accessed under:

 SOAM/DM Sessions/Session x/Statistics/Historic[]
Up to 5 Historic counters can be added and enabled for up to 32 intervals.
Interval duration: [30 .. 900 .. 3’600]
Number of Intervals: [1 .. 32]
Please note that the historic counters must be activated in order to be effective.

A3118-X642-R612-01 352 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

CES / TDM Loopback

ACCEED provides loopbacks to the CES and TDM interface that can be set via LCT+ or CLI.

 To set the loopbacks go to:

CES IWF/Local/TDM/TDM1

└110x_1404_1416_2104_2202_End

 To set the loopbacks on DMS go to:

CES IWF/Local/DMS/DMS1

CES Alarming
The CES alarming can be divided in TDM and CES related alarms. The available alarms are shown in
Figure 10-9 for the three alarm locations at the TDM, CES TDM and Ethernet interface. For each of
these alarms, the severity can be set and the logging can be enabled or disabled. TDM BER3 and
BER6 are based on the CRC4 counter.

TDM-LOS Loss of signal at TDM interface detected

TDM-AIS Alarm indication signal at TDM interface detected
TDM-LFA Loss of frame alignment at TDM interface detected
TDM-BER3 Bit Error Rate of 10E-3 at TDM interface detected
TDM-BER6 Bit Error Rate of 10E-6 at TDM interface detected
TDM-RAI Remote alarm indication at TDM interface detected

CES-LOF Loss of frame at CES interface detected

CES-AIS Alarm indication signal at CES interface detected
CES-RAI Remote alarm indication at CES interface detected
CES-ARE Address Resolution alarm at CES interface detected

The alarms are only seen in the system when they are present and cleared when the problem is
resolved. Please refer to the Alarm Log to see the alarm history.

A3118-X642-R612-01 353 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

Figure 10-9 CES Alarm locations

A3118-X642-R612-01 354 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

10.5 CES Operational Aspects

Planning CES
The following points need to be considered when planning to deploy CES.
 What are the critical parameters of the TDM service that need to be emulated.
- Maximum acceptable end to end delay
- Availability of performance- and fault management information (e.g. to fulfill the SLA)
- Structure of the TDM signal to be emulated (unframed, framed, specific signaling ?)
 How is the clock delivered to the ACCEED unit?
Please note that only synchronous clock applications are supported with ACCEED.
 Is the SHDSL data rate sufficient to deliver the TDM service and additional Ethernet services if
applicable?
 Is the QoS concept well defined to ensure error-free CES operation?
- Prioritization of packets against other traffic
- Queueing and Scheduling

Trouble Shooting CES

This chapter describes possible approaches to find problems related to CES.

The alarms presented by the ACCEED unit provide a good entry point for CES trouble shooting.
See  10.4.4 for all alarms related to CES and TDM.

If TDM alarms are present:

 Verify if the physical connection is correct (TDM LOS)
 The framer is configured appropriately (TDM LFA)
 Clocking is properly applied to both ends of the CES IWF devices (TDM LFA)
 The local and remote end customer TDM interface is working correctly (TDM AIS, RDI)
 Verify if the customer TDM signal is error free (TDM BER3, BER6)
If TDM framing with CRC4 is present in the customer signal, verify the TDM counters as
described in  10.4.1
Use the loopback to CES and TDM interface to narrow down the problem. Please refer to  10.4.4.

For the CES alarms (CES LOF), various problems might be present.
 SHDSL data rate is not sufficient (CES LOF).
See utilization of CES egress port. Refer to  8.10.7 for port utilization
 The Packet configuration (Encapsulation and Payload Type) must match between both CES
IWF. Example: VID=22, CoS=7, CESoPSN, Payload Size=256
 The Configured VLAN ID in the packet section must be existing in the VLAN DB and the
tagging command must be set to “Primary Tag Only” for the respective CES egress port.
 Verify CES packet and jitter buffer performance, see  10.4.2
Statistics: are the lost, early or late frames counted?
CES: are jitter buffer overflows, under runs counted?
Adjust the jitter buffer size accordingly, see  10.1.6
 Verify that the CES packets are sent to the correct egress queue and no packets are dropped
in this egress queue.
 The CES-ARE alarm indicates a connectivity problem, preventing the automatic MAC
exchange between the CES IWF. The connectivity between the CES IWF on the IP layer can
be tested based on ping messages as shown in the figure below:

A3118-X642-R612-01 355 / 405

 ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 1102/04 Manual

 The ping initiated by the CES IWF IP can be done as follows:

 Board/Local
Please note that if the Count is set to “0”, the ping requests are sent continuously until the
request is aborted.

The CES stream generated by the IWF is directly sent to the egress queue of the egress
port configured in the packet section. Egress modifiers therefore do not apply to the CES
packets. In the ingress direction, the CES stream is directly linked to the CES IWF before
any ingress modifier can be applied. Consequently, statistics and utilization which base on

 modifiers do never show the CES packets.

Please note that the port configurations like VLAN tunneling and force port VLAN ID are
applied before the CES stream is sent to the CES IWF and can cause problems in
detecting the CES stream.

The mirroring function can be applied to the CES stream.

└110x_1404_1416_2104_2202_End

A3118-X642-R612-01 356 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11
General Board
settings

The board chapter provides general information of the ACCEED unit and
explains how to configure equipment specific settings like clocking, alarm
configuration, time settings and management access.

A3118-X642-R612-01 357 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11.1 Board – general system information

Board/Local/Information
Board/EFM-NT/[x]/Information
The Board section provides general system information on the inventory, system resource
situation and a system log for the LT and the NTs.
This information is accessible for the LT and the NTx. By selecting the respective buttons
marked yellow in the screen shot below windows with the required information will pop up.
The information is further explained in the following chapters.

A3118-X642-R612-01 358 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

System Log

Board/Local/Information
Board/EFM-NT/[x]/Information
System Log lists the events on the ACCEED and can be used as source for trouble
shooting.
Entries listed under “NVD entries” are critical events stored to a non volatile memory since
the first start of the ACCEED unit.
“actual entries” lists all events since the last startup of the ACCEED device.
The events are listed in chronological order with the most recent at the button of the list.
The example below shows a System Log excerpt of an ACCEED 1416 unit.

Save As… saves the system log list in a text or pdf file
Cancel closes this window
Refresh updates the System Log window

A3118-X642-R612-01 359 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Ressources
Board/Local/Information
Board/EFM-NT/[x]/Information
The resource information provides insight in the ACCEED units for trouble shooting
purposes. Up time and system load a process list and memory usage are displayed.
In case of the ACCEED desktop units, temperature of the CPU and the FPGA, and fan
speed information are displayed additionally.

Save As… saves the resource information in a text or pdf file

Cancel closes this window
Refresh updates the Resources window

A3118-X642-R612-01 360 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

The resources information window also indicates percentage usage of certain system resources such
as policy rules, counters, etc…
Additionally in case of shortage of system resources (resource shortage alarm  12.3.29), the
reasons are stated here:
 “Too many EVC, PTP or Inband Management resources used”. Solution: reduce number of EVC
or CoS Instances
 “Too many policy rules used” Solution: reduce the number of policy rules
 “Too many policy ingress/egress metering entities used”. Solution: reduce number of
ingress/egress bandwidth profiles
 “Too many transmit buffer resources used”: Queue profiles attached to active Ethernet ports
assign more buffers than available in the buffer pool. Additional packet drops due to buffer under
run may occur in heavy overload conditions. Solution: reduce number of active (enabled) ports
and/or reduce the number of buffer blocks in the queue profiles
 “Too many Service OAM resources used”. Solution: reduce number of CCM or performance
measurement instances. Reducing the number of associated VLANs, or using Down MEPs
instead of Up MEPs may also help.
 “Too many remote MEP resources used”. Solution: reduce number of configured remote MEPs or
reduce CCM intervals
 “Too many performance statistic resources used”. Solution: reduce number of enabled historic
statistics.

A3118-X642-R612-01 361 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Inventory
Board/Local/Information
Board/EFM-NT/[x]/Information
The inventory lists all devices in the aggregation and the array respectively.
The information listed under Inventory is depending on the ACCEED unit and application.
The example below shows an ACCEED 1416 plug in (LT) to desktop (NT) application with 4
SHDSL ports being aggregated and assigned to PAF A. In the Aggregation section you see
the 2 SHDSL links and the connected NT devices. All of them end on the same NT device,
because the serial number of all NT links is the same. The Text “S13Px” describes here that
all used SHDSL are connected in Slot 13. In the Array section shows that via the SCC bus
are connected 4 more LT are connected (Slot 12, 14-16). The top LT in the list is the local one
which is connected to NTs via SHDSL and logically to the EFM-NT A. The difference of the
EFM-NT_A to the SHDSL lines (serial number) signals, that the EFM-NT_A is not on the
same NT as the SHDSL lines are terminated, but in a device connected to the SCC ring of
them.

Save As… saves the inventory information in a text or pdf file

Cancel closes this window
Refresh updates the Inventory window

A3118-X642-R612-01 362 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11.2 Alarm configuration

The Alarm log lists all raised alarms.
Alarm configuration allows to define the severity of each alarm and if the individual alarm shall be
logged and therefore being displayed in the alarm log.

The alarm configuration is accessible under Board/Alarm Configuration


Suppress Power Failure if enabled, no alarm is raised in case of a DC power failure
Minimum Trap Level when an alarm is raised and the defined severity of this alarm
is equal or above the trap level, a respective alarm trap is
generated. The trap level is applied to the whole ACCEED
unit.
Inhibit LOSWS During UAS if enabled, LOSWS counter stops counting during
Unavailable State (this method is mainly used by DSLAMs).
LOSWS equals then the number of retraining seconds and
heavy error conditions.

Severity

The severity values are accessible under Board/Alarm Configuration/Severity

The severity of all alarms can be configured individually. The severity values are:
Warning: lowest severity, alarms are marked with the color green
Minor: second lowest severity, alarms are marked with color yellow
 Major: second highest severity: alarms are marked with the color orange
Critical: highest severity, alarms are marked with the color red
The table below the default severity values for all ACCEED 1102/04 alarms.
For more information on the individual alarm please refer to the alarm list in  12.3

A3118-X642-R612-01 363 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Logging
The logging of alarms can be configured individually. Per default all alarms are logged.
Please note that an alarm trap is only generated, if the logging for the respective alarm is enabled.
Disable logging of alarms not being of importance for fault management help reduce the size of the
alarm log.

A3118-X642-R612-01 364 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

The logging values are accessible under Board/Alarm Configuration/Logging

A3118-X642-R612-01 365 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11.3 Local

Information
The board information are accessible under Board/Local/Information
The values of the active and passive FW version reflect the actual FW loaded on the
ACCEED unit.
The housing is depending on the ACCEED unit variant, being a desktop or plug in module.
The CLEI (Common Language Equipment Identification) code is individual for each ACCEED
unit type and allows to identify and track the network equipment.
The example blow represents an ACCEED 1416 plug in unit.

SCC Configuration
Not applicable.

Maintenance
Possible maintenance reasons for ACCEED 1102/04 are:
 Link OAM Loop Active: local or remote loopback is active
 Service OAM Loop Active: SOAM Loop activated from remote side
 Service OAM Ethernet Locked: Lock messages are sent from remote side
 Ethernet Port Loopback Active: All transmitted frames are looped back to port
 Ethernet Port Mirroring Active: Port mirroring on one of the Ethernet ports is active
 Traps Disabled
 Trap Level Low
 MAC Table Aging Disabled
 ZeroTouch Provisioning Active
 Writing Configuration To Flash: flash writing is in progress
 TDM/DMS Loop Active: Loopback enabled on TDM interface, on CES interworking function, on
data interface 3c or 2b

A3118-X642-R612-01 366 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

The maintenance information are accessible under Board/Local/Maintenance

Select the Fault folder to see the actual maintenance reasons.
An active maintenance state is also indicated by the yellow maintenance box in the lower
right corner of the LCT+ window.
The example below indicates that a line loop and a BER measurement are active.

Time Settings
For the time setting configuration please refer to  5.8.8

Management Access
For the management access options please refer to  5.8.2

11.3.5.1 Authentication (via RADIUS)

For user logins to ACCEED devices, centralized user authentication can optionally be used.
RADIUS (Remote Authentication Dial In User Service) is a protocol for central user authentication and
authorization, defined by the IETF in RFC 2865. RADIUS also offers accounting functionalities; however,
ACCEED devices do currently not use them.

11.3.5.1.1 Functional Principle

RADIUS is a client – server protocol. A RADIUS client is located on ACCEED devices. If a user wants
to log in to the device, he or she has to provide his or her user name and password to the RADIUS
client, which then sends an “access request” message to the RADIUS server. The server tries to
authenticate the user and responds with an “access accept” or “access reject” message. Depending on
this answer from the server, the user is allowed to log into the device, or access is denied for the user.

Figure 11-1 RADIUS functional principle

11.3.5.1.2 Authorization
Additionally, the server informs the client of the access privileges attached to the user (authorization).
Currently two access privilege levels are supported, Administrator (full access) and Maintenance (read-
only access and maintenance functions). The server can communicate this authorization information
with RADIUS attribute value pairs (AVP) carried in the access accept messages.
ACCEED uses the “Service-Type” attribute. If ACCEED receives an access accept message with the
“Service-Type” attribute set to the value “Administrative” (value 6), the corresponding user is granted

A3118-X642-R612-01 367 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Administrator privileges. If the “Service-Type” AVP has a different value or is missing, the user is set to
Maintenance rights.

11.3.5.1.3 Redundant servers

Up to 3 different RADIUS servers can be configured in order to increase resilience. If the first server is
not answering within the configured timeout period the request is retried till the maximum retry value is
reached, an authentication request is sent to the second server, and then to the third. Depending on the
configured number of retries per server and timeout period, this procedure can take a considerable
amount of time.

Figure 11-2 Flow chart redundant server authentication

11.3.5.1.4 Order of Authentication Modes

RADIUS authentication can be combined with conventional authentication by the device itself using the
two locally available users “Administrator” and “Maintenance”. A primary and secondary authentication
method can be configured to be either “Local” or “RADIUS”. In case only the primary method shall be
used, the secondary authentication method can also be set to “None”.
The default setting is local authentication only.

Figure 11-3 Authentication databases

The procedures for a combined use of local and RADIUS authentication methods are described in the
following two flow charts.

A3118-X642-R612-01 368 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Figure 11-4 Combined authentication modes: Primary RADIUS, secondary local

Figure 11-5 Combined authentication modes: Primary local, secondary RADIUS

11.3.5.1.5 Configuration

A3118-X642-R612-01 369 / 405

ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Board/Local/Management Access/Authentication

Authentication Method 1 [Local, RADIUS]

The primary authentication method can be RADIUS or Local.
Authentication Method 2 [None, Local, RADIUS]
The secondary authentication method can be RADIUS or Local, or None, if no
secondary authentication should be used. The secondary authentication method
must be different from the primary method.
RADIUS Retransmits [1 .. 4 .. 15]
Number of retries for each configured RADIUS server, in case a timeout occurs.
RADIUS Timeout [1 .. 5 .. 30s]
Timeout used in communication with RADIUS servers.

Up to 3 RADIUS servers can be added with the “Add” button under

Board/Local/Management Access/Authentication/RADIUS Server

Authentication Protocol [PAP]

Authentication Protocol to be used with this RADIUS server. Currently only PAP
is supported.
Message Authenticator [enable, disable]
Select if the message authenticator attribute shall be used.
To provide protection from spoofed Access-Request messages and RADIUS
message tampering, each RADIUS message can be additionally protected with
the RADIUS Message Authenticator attribute, which is described in RFC 2869,
"RADIUS Extensions."
The RADIUS Message Authenticator attribute is a Message Digest 5 (MD5) hash
of the entire RADIUS message. The shared secret is used as the key. If the
RADIUS Message Authenticator attribute is present, it is verified. If it fails
verification, the RADIUS message is discarded. If the client settings require the
Message Authenticator attribute and it is not present, the RADIUS message is
discarded.
Shared Secret [up to 16 characters]
Shared secret defined for this RADIUS server. Note: this parameter is not saved
in config files.

A3118-X642-R612-01 370 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11.3.5.2 Zero Touch Provisioning

With Zero Touch Provisioning the ACCEED CPE can be delivered from the stock to the end customer
without any customer specific configuration. The customer just physically connects the device to the
power and the WAN interface (e.g. copper or fiber). The provisioning of the device is then done
automatically, without customer interaction or any manual task in the network operation center. There
is obviously no need for a skilled technician to travel to the customer site.

Zero Touch Provisioning is available for all ACCEED units running in CPE mode. For the LT /NT
mode, the configuration is distributed to the NT(s) via the LT.
The mechanism is based on standard protocols which allow an integration of the provisioning process
into the customer environment. The communication for the provisioning process is done via the inband
management interface.

The CPE can request the following parameters via DHCP during the initial provisioning phase,
depending on the settings in the ACCEED unit.
 Management IP, Netmask and Default Gateway
 Management VLAN ID
 Management VLAN CoS
 NTP Server
 Bootfile
 TFTP Server Address
 Specific ACCEED device configuration (cfg file)

Step by step
1. ACCEED requests an IP address, net mask and default gateway from the DHCP server
2. If required,
a) the VLAN configuration can be changed
b) the IP address, net mask and default gateway is requested again, now in the configured
VLAN
3. Request of boot file which contains further provisioning information
4. If applicable, the firmware is updated
5. If applicable, a configuration file is received from a tftp server and applied to the ACCEED unit.

A3118-X642-R612-01 371 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

These steps are further illustrated in the diagrams A to E below.

Figure 11-6 Zero Touch Provisioning principle

The following parameter can be set in ACCEED for zero touch provisioning
Board/Local/Management Access

Board/Local/Management Access/Inband

A3118-X642-R612-01 372 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

 Please note, the ACCEED CPEs are prepared to support the zero touch provisioning
process, but integration in the specific environment is always required.

11.3.5.3 Access Control

The access to the ACCEED 1102/04 can be limited by defining a white list of IP address ranges (IP
and net mask). There can be up to 32 different IP ranges.
By default ACL access is disabled. No ACL are defined.

The access control list can be activated and configured here

Board/Local/Management Access/Access Control
Access Control need to be enabled to control the management access with the ACL

 Up to 32 entries can be added and configured in the ACL.

A3118-X642-R612-01 373 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

11.4 Synchronization

Introduction
ACCEED 1102/04 is an Ethernet device. Due to Ethernet’s asynchronous packet character there is no
need for synchronization for basic data transmission services. However, timing critical applications like
mobile backhaul or CES require accurate synchronization on remote locations. This is why ACCEED
offers a comprehensive feature set to provide high quality timing to customer locations.
ACCEED’s internal high-quality PLL (phase locked loop) can be synchronized to one of several possible
clock sources: SHDSL symbol clock and external reference inputs (HDB3 or 2MHz). The selection of
the input is done automatically, based on a configurable priority list. The active reference clock can then
be forwarded to different output interfaces.

Clock Source Selection

Two criteria (Quality and Priority) are used for determining from which source the ACCEED’s system
clock shall be synchronized. The clock quality value can be assigned manually to each potential clock
source. The quality level of the front panel clock input can be obtained automatically from
Synchronization Status Messages (SSM) coded in the TDM SA bits, if the interface is in 2 Mbit/s mode.
Among all enabled and available clock sources, ACCEED synchronizes its system clock to the one with
the highest quality level.
For the case that two eligible clock sources have the same quality level, a priority value can be assigned
to each potential clock source (lowest value wins).
If both quality and priority are equal, sources are used in the following pre-programmed order:
 TDM (Frontpanel)
 SHDSL (NT & CPE)
 Internal

The currently active clock source is shown in Board\Local\Clocking

Supported Quality and Priority Values

Quality
Supported clock quality values are the levels defined in Option 1 of ITU-T G.781. Other quality levels
received at the input interface are treated as DNU (0x0F).

HEX Dec (Name) Priority

 0x02 2 (QL PRC) Highest quality level
 0x04 4 (QL SSU-A) ↑
 0x08 8 (QL SSU-B) ↓
 0x0B 11 (QL SEC) Lowest quality level
 0x0F 15 (QL DNU/Do not use) Should not be used for synchronization

The DNU (Do Not Use) quality level is also sent out on interfaces that are currently used as active clock
source, in order to prevent timing loops.
A3118-X642-R612-01 374 / 405
 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Priority
Clock priority can be configured to the following values:
 Range: 0..255
 0 defines the highest priority
 255 represents the lowest priority

Clock Sources
The following section shows the configuration of the different possible clock sources. Not all interfaces
shown in the screenshots may be available on a specific device.

11.4.4.1 TDM Interface

A 2 MHz or 2 Mbit/s G.703 signal provided to the frontpanel Clock / TDM interface(s) can be used as
synchronization source.
Note: 2 MHz input is only possible if the interface is not used for CES. If CES is active, the
corresponding 2 Mbit/s G.703 signal can be as synchronization source.
Board\Local\Clocking\Frontpanel

The “Trust SSM” parameter enables automatic configuration of the clock quality via received
SSM. The “Send SSM” parameter enables sending of SSMs with the quality of the currently
active clock source. Both parameters are only relevant if Clock Type is set to “2 Mbps”.

11.4.4.2 SHDSL
SHDSL symbol clock can be used as a reference for devices in NT/CPE mode. Because SHDSL
synchronization is always provided from LT/CO towards NT/CPE side, SHDSL cannot act as a clock
source at LT/CO devices.

A3118-X642-R612-01 375 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Board\Local\Clocking\SHDSL


The Screenshot shows a device in CPE mode. In LT-NT connections, clock quality and priority
are always automatically forwarded from LT to NT.
In CPE mode, the “Trust SSM” parameter enables automatic configuration of the clock quality
via received SSM.

11.4.4.3 Internal Clock

If none of the external clock sources are active, ACCEED uses its internal oscillator.

Board\Local\Clocking\Internal

Clock Output Interfaces

11.4.5.1 Frontpanel
A 2 MHz or 2 Mbit/s G.703 signal output can be activated at the frontpanel clock / TDM interface.
Frontpanel clock output can be squelched if the currently active system clock quality level falls below a
configurable “Output Squelsh Threshold”
Note: 2 MHz output is only possible if the interface is not used for CES. CES output signals are always
synchronized to the currently active clock source.
11.4.5.2 SHDSL
SHDSL synchronization is always provided from LT/CO towards NT/CPE side.
In LT/CO mode, the currently active reference clock is automatically used as SHDSL symbol clock and
forwarded to the NT/CPE side. It is therefore not necessary to explicitly enable SHDSL clock output on
LT/CO mode devices. NT/CPE cannot transmit a clock signal to SHDSL lines

A3118-X642-R612-01 376 / 405

 ULAF+ 11 - General Board settings ACCEED 1102/04 Manual

Synchronization Fault Management

A “Clock not Available” alarm is raised if an interface is configured as clock source but does not
receive a valid clock signal. A “Clock Squelched” alarm is raised if the frontpanel clock output is
enabled but the currently active system clock quality is below the squelch threshold.
The synchronization relevant alarms are also described in  12.3.

A3118-X642-R612-01 377 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

12
Troubleshooting

This chapter gives some practical help to quickly identify faults and solve
problems. The chapter contains a list of all alarms, describing possible
causes and suggesting possible solutions.

The aim of this chapter is to facilitate trouble shooting.

A3118-X642-R612-01 378 / 405

 ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

12.1 Most common troubles

SHDSL startup problems
Depending on the bit rate and on the presence of regenerators, the SHDSL line may require some
minutes to complete the startup process and training.

Table 17 contains some startup times measured in the lab. These should be considered examples.

Line type modulation bit-rate startup time

LT – NT PAM32 5696 kBit/s 25 sec
LT- regenerator – NT PAM32 5696 kBit/s 45 sec
LT – NT PAM16 192 kBit/s 35 sec
LT- regenerator – NT PAM16 192 kBit/s 75 sec
Table 17 SHDSL line startup time examples

If after several minutes the line didn’t reach synchronization, there might be a problem to solve. The
most common causes are:

12.1.1.1 Device not connected / not powered

If the LT, one of the regenerators (if applicable) or the NT is not properly connected to the copper line
or is not powered, the line will not start and the LOS alarm will persist.

If the RED SHDSL LED starts blinking, the handshake protocol between LT and NT has
 been successfully completed, meaning that a physical connection exists between LT and
NT.

 Check the LT and NT power supply

 In case of regenerators or remotely fed NT device, make sure that the remote power supply is ON
and check the jumper settings on the NT and DIP-switch configurations on the regenerators.
 Check the copper line connection; make sure the RJ45 connector is properly inserted in the board.

12.1.1.2 Wiring error

In case of wiring errors (e.g. the connected wires do not belong to the same wire pair as showed in

Figure 12-1) the SHDSL will not start and the LOSW alarm (RED SHDSL LED blinking) will persist.

Figure 12-1 Wiring error example

A3118-X642-R612-01 379 / 405

 ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

 If the RED SHDSL LED starts blinking, the handshake protocol between LT and NT has
successfully completed, meaning that a physical connection exists between LT and NT.

 Check the copper line wiring

12.1.1.3 Copper line equalization and symmetry

All elements used for equalization and symmetry like inductance (Pupin) coils or capacitors must be
removed before SHDSL is applied in the cable section

Figure 12-2 line equalization and symmetry example

 Check the copper line

 Remove the inductances / capacitors

12.1.1.4 Over voltage protection

As described in chapter 1.5 the unit must be protected from over voltages at the SHDSL interface. If
the remote power supply (180V) is used, the ignition voltage of the gas arrestor has to be > 200 V,
otherwise the protection element can get active and the RPS will turn off, inhibiting the start up
procedure.

 The RPS will shut down because of Overcurrent alarm, each time it tries to power the line.
This happens every two minutes.

 Check the alarm log (presence of RPS alarm every 2 minutes)

 Use an over voltage protection >200V.
12.1.1.5 SHDSL performance
As described in  7.2, the reach of a SHDSL line depends on the bit rate and on the parameters. If the
copper line is too long, for the used cable and the configured bit rate, the line will continuously retrain
and never reach synchronization. The LOSW alarm will persist.

 Check the line attenuation and the SNR margin

 If possible reduce line speed to increase line reach
 If possible add regenerators to the line

 A minimum noise margin of 6dB is recommended to operate a line.

12.1.1.6 Bridged taps

Bridged taps are (sometimes forgotten) lines at MDF which cause undesirable reflections and can distort
the high-frequency SHDSL signals. Bridged taps reduce the expected distance

A3118-X642-R612-01 380 / 405

 ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

Figure 12-3 bridged taps

12.1.1.7 Impedance mismatch

If the complete cable section consists of several sub-sections with different cable types the expected
length cannot be reached due to the reflections (impedance mismatch!)

Figure 12-4 Impedance mismatch

Bit errors on the copper line

Sporadic bit errors may occur on copper lines, e.g. because of impulse noise.
If the error frequently occurs or persists, the cause should be investigated.

The following built-in debugging tools can be used to analyze the errors:
 SHDSL line parameters enables to check line attenuation and SNR
 Alarm Log: the alarm log can be used to check, if the bit errors is related to some alarm
 SHDSL performance counters: the counters can be used to find out, when the errors occurred

A likely cause of disturbances is an impaired transmission line. Check the line performance parameters
(line attenuation / signal to noise ratio margin) and the cable installation (e.g. that the connector is
properly inserted).

Reliable grounding the equipment (LT and NT units) often helps to eliminate disturbances.

A3118-X642-R612-01 381 / 405

 ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

12.2 LED indications

Figure 12-5 ACCEED 1102/04 LEDs

Power LED (1)

OFF A turned off power LED indicated a problem with power supply or heat.

The power supply has to be checked:

- Are the power supply cable correctly installed?
- Are the power setting correct? Check  5.2.
- If the ACCEED 1404 unit is supposed to be fed over the copper wires, check
the RPS alarms on the LT unit.

If the green PWR LED is OFF and the red Alarm is ON then the device is in a
"forced shutdown" condition because of over temperature condition. This mode
prevents the equipment to be permanently damaged.
Possible causes could be:
- Too high environment temperature
- FAN failure

Suggested recovery procedure:

1. Power off the equipment
2. Wait until devices cooled
3. Try to power on and check the FAN alarm state.

Alarm LED (1)

RED or A red alarm LED indicates the presence of a critical or major alarm
YELLOW A yellow LED indicates the presence of a minor alarm

To find out the exact alarm cause the LCT+ must be utilized. Information about
debugging with LCT+ can be found in  12.3.

A3118-X642-R612-01 382 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

 Alarms configured as Warnings are not indicated on the alarm LED.

MAINT LED (1)

ON This indicates that a maintenance function has been activated.
Data transmission may be affected by this (temporary) configuration.

Possible maintenance functions are:

- SHDSL loop 1a active on regenerator
- BER measurement running
- Link OAM remote loopback active
- Link OAM local loopback active
- Service OAM locked signal is active
- Traps suppressed

BLINK 2x FAST Zero Touch Provisioning mode

PAF LED (1)

ON This indication signals the Aggregation Loss alarm.
See  12.3.1.

BLINKING This indication signals the Partial Aggregation Loss alarm.

SLOW See  12.3.27.

ETH Px green LED (3), (4), (5) and (6)

OFF This indication signals "no link" on the P1, P2 or P3 interface.
Possible cause are:
- Wiring error (interface is not connected)
- Configuration error (interface shut down)

NMS green LED (8)

OFF This indication signals "no link" on the NMS interface.
Possible cause are:
- Wiring error (interface is not connected)
- Configuration error (interface shut down)

TDM x LED (9) und (10)

RED Indicates fault of clock input
See  0.
YELLOW Indicates AIS on the E1 Interface

A3118-X642-R612-01 383 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SHDSL x LED (12)

ON This indication signals the SHDSL-LOS alarm.
See  12.3.46.

BLINKING This indication signals the SHDSL-LOSW alarm.

SLOW See  12.3.47.

BLINKING This indication signals the SHDSL-64-65B alarm.

FAST See  12.3.43.

A3118-X642-R612-01 384 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

12.3 Alarm list

Aggregation Loss Alarm

Description Remote aggregation card (EFM-NT) is not reachable
alarm location PAF
defect location PAF
default severity Critical
default logging log
LED signaling RED PAF LED ON
debug hints This alarm indicates that the EFM link cannot be aggregated:
 the SHDSL wiring is wrong
 all SHDSL connection belonging to the link are broken (see SHDSL
alarms)
 No PAF has been configured on the NT device

APS-Failure Of Protocol Alarm

Description The APS information received from-tail-end is incompatible or invalid
alarm location Protection
defect location Protection
default severity Critical
default logging log
LED signaling ---
debug hints Check that the APS protocol must be configured on both ends and that the
configuration is coherent.

Attenuation Threshold Alarm

Description Line attenuation above threshold
alarm location PME
defect location PME
default severity Minor
default logging log
LED signaling none
debug hints The line attenuation of the cable may vary over time. It is possible to
define a threshold, so that the equipment generates an alarm when the
line attenuation exceeds a certain threshold.

CES-AIS Alarm
description Alarm Indication Signal at CES interface detected
alarm location CES
defect location CES IWF
default severity Minor
default logging Log
LED signaling None
debug hints Check the TDM interface at the remote IWF

A3118-X642-R612-01 385 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

CES-ARE Alarm
description Adress Resolution Error at CES interface detected
alarm location CES
defect location CES IWF
default severity Critical
default logging Log
LED signaling None
debug hints Check the local and remote CES configuration

CES-LOF Alarm
description Loss of Frames at CES interface detected
alarm location CES
defect location CES IWF
default severity Critical
default logging Log
LED signaling None
debug hints Check the connectivity between the two CES IWF

CES-RAI Alarm
description Remote Alarm Indication at CES interface detected
alarm location CES
defect location CES IWF
default severity Minor
default logging Log
LED signaling None
debug hints Check the TDM interface at the remote IWF

Clock Not Available Alarm

description Clock source is not available
alarm location Clock input
defect location Clock
default severity Critical
default logging log
LED signaling RED CLOCK LED ON
debug hints This alarm is raised under the following circumstances:
- An interface is configured as clock input, but there is no input signal
- An interface is configured as clock input, but the input signal cannot
be used for synchronization (e.g. due to frequency offset or high jitter)
- An interface is configured to receive clock quality information via SSM
(“Trust SSM” parameter is enabled), but does not receive SSMs

Clock Squelched Alarm

description Clock output is squelched due to low quality
alarm location Clock output
defect location Clock
default severity Minor
default logging log
LED signaling YELLOW CLOCK LED ON
debug hints This alarm is raised when the quality of the available clock source is lower
than the configured quality threshold. The clock output signal is consequently
suppressed.
The reference clock source should be checked

A3118-X642-R612-01 386 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

Equipment Alarm
description Equipment failure
alarm location Equipment
defect location Equipment
default severity Critical
default logging log
LED signaling none
debug hints The HW is damaged. Replace the unit.

ETH No Link Alarm

description No link on Ethernet port
alarm location ETH Port
defect location ETH Port
default severity Critical
default logging log
LED signaling none
debug hints  Ethernet port not connected / Cable broken
 Configuration error (e.g. interface shut down)

ETH No Path Available Alarm

description All paths of a protection instance are unavailable
alarm location Protection
defect location Protection
default severity Critical
default logging log
LED signaling ---
debug hints The alarm indicates that all the path of the protection instance are unavailable.
The connections belonging the protection should be checked and restored.

ETH-Protection Loss Alarm

description The traffic of a protection instance is not protected
alarm location Protection
defect location Protection
default severity Critical
default logging log
LED signaling ---
debug hints The link used for protecting an instance is down. The connection on the
protection path must be verified.

ETH-Working Path Not Available Alarm

description The working path of a protection instance is not available (in revertive operation
only)
alarm location Protection
defect location Protection
default severity Critical
default logging log
LED signaling ---
debug hints The link working path of a protected instance is down. The connection on
the working path must be verified.

A3118-X642-R612-01 387 / 405

 ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

──────────────────────────────────────────────────────────────────────┐

Firmware Type Mismatch Alarm

description Remote FW type incompatible
alarm location PME/SCC
defect location PME/SCC
default severity Critical
default logging log
LED signaling YELLOW MAINT LED Blink-Slow
debug hints The alarm may have two different causes:
 indicates the FW of the NT unit is not compatible with the one of the LT.
A FW update is necessary.
 All ACCEED units in the array must have the same FW version. At least
one unit has a different FW version. A FW update is necessary.

LAG-Aggregation Loss
description All members ports of the LAG port are down
alarm location Aggregation
defect location ……………..…
default severity Critical
default logging log
LED signaling ……………..…
debug hints ……………..…

LAG-Aggregation Mismatch
description Link Aggregation is not set up properly
alarm location Aggregation
defect location ……………..…
default severity Critical
default logging log
LED signaling ……………..…
debug hints ……………..…

LAG-Partial Aggregation Loss

description A member port of the LAG port is down, protection is no more available
alarm location Aggregation
defect location ……………..…
default severity Critical
default logging log
LED signaling ……………..…
debug hints ……………..…

A3118-X642-R612-01 388 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

LFP Alarm
description Link failure propagation (link forced down due to PAF alarm)
alarm location ETH Port
defect location ETH Port
default severity Critical
default logging log
LED signaling none
debug hints Possible causes are
 Aggregation Loss (configurable)
 Partial Aggregation Loss (configurable)
 Configuration error

Check the PAF / SHDSL line alarms and the LFP configuration

LinkOAM-Critical Event Alarm

description Link OAM peer reports a Critical Alarm
alarm location Link OAM
defect location Link OAM
default severity Minor
default logging log
LED signaling none
debug hints The peer unit has an equipment alarm

LinkOAM-Dying Gasp Alarm

description Link OAM peer reported a dying gasp (caused by power fail or an
unexpected reboot)
alarm location Link OAM
defect location Link OAM
default severity Critical
default logging log
LED signaling none
debug hints The peer unit has power loss condition

LinkOAM-Link Fault Alarm

description Link OAM peer reported a link fault (caused by unidirectional link interruption)
alarm location Link OAM
defect location Link OAM
default severity Critical
default logging log
LED signaling none
debug hints The peer notifies that there is an unidirectional connection.

A3118-X642-R612-01 389 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

LinkOAM-No Peer Alarm

description No Link OAM no peer discovered
alarm location Link OAM
defect location Link OAM
default severity Critical
default logging log
LED signaling none
debug hints  The peer unit LinkOAM is disabled
 The peer unit is not present (SHDSL respectively Ethernet no link alarm
are also active)
 Configuration error

Low Bandwidth Threshold Alarm

description Available bandwidth is below the configured threshold
alarm location PAF
defect location PAF
default severity Critical
default logging log
LED signaling PAFx RED Blink-Fast
debug hints If the aggregated available bandwidth of the PAF falls below the
configured "Low Bandwidth Alarm Threshold" value, this alarm is raised.
Verify that the PAF is without error and the defined threshold is set to a
value below the PAF available bandwidth

Not Aggregated Alarm

description PME resource is already assigned or not available
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling none
debug hints Possible defects are:
 PME not reachable
 PME already assigned
This alarm usually signals a configuration error:
 a SHDSL link has been requested, which has already been allocated
for a different EFM link
 resources have been requested on a device, which is not available
(e.g. not yet inserted in the Subrack or SCC connection is not
available)

A3118-X642-R612-01 390 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

NT Power Failure Alarm

description Power loss on NT
alarm location NT Power Supply
defect location NT Power Supply
default severity Critical
default logging log
LED signaling none
debug hints The input voltage of the NT device is monitored in order to send a power
fail alarm in case of NT power failure. If the input voltage drops below the
threshold value (about 100V), a dying gasp message is sent to the LT
device via transmission interface.
In case of utilization of a DC power source (<100V) the power-fail
signaling can be suppressed using the LCT+. For further information see
 9.1.

Partial Aggregation Loss Alarm

description One or more lines of aggregation are not available
alarm location PAF
defect location PME
default severity Critical
default logging log
LED signaling RED PAF LED Blink-Slow
debug hints This alarm indicates a layer 1 problem in one or more aggregated lines.
To spot the faulty line(s), refer to the SHDSL alarms:
 SHDSL_LOS
 SHDSL-LOSW
 SHDSL-64-65B

A3118-X642-R612-01 391 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

Power Failure Alarm

description Power supply voltage below threshold
alarm location Power Supply
defect location Power Supply
default severity Minor
default logging log
LED signaling none
debug hints The input voltage of the device is monitored in order to send a power fail
alarm in case of power failure. If the input voltage drops below the
threshold value (about 100V), the power failure alarm is raised.
In case of utilization of a DC power source (<100V) the power-fail
signaling can be suppressed using the LCT+. For further information see
 9.1.

Resource Shortage Alarm

description Not enough resources available
alarm location Equipment
defect location Resources
default severity Critical
default logging log
LED signaling none
debug hints Cleaning up unused rules and service configurations may help to solve
the resource shortage problem. See  11.1.2

SOAM-AIS Alarm
description AIS messages received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling None
possible causes Check for possible loss of continuity on lower layer

SOAM-Avail Objective
description Availability objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging Log
LED signaling None
defect(s)
possible causes ……………………….

A3118-X642-R612-01 392 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SOAM-ErrorCCM Alarm
description Invalid CCM received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling None
defect(s)
possible causes A service OAM MEP is receiving invalid CCM packets
 Packets are not compatible (e.g. interval configuration)
 Malformed packets
Service OAM debug information is available via LCT+. See  9.2.1.5, in
the section Last CCM Failure parameters.

SOAM-FDICSF
description Client Signal Fail (Forward Defect Indication)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with FDI flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.

SOAM-FD Objective
description Frame delay objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….

SOAM-FLR Threshold
description Average Frame loss ratio has exceeded the configured threshold
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….

A3118-X642-R612-01 393 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SOAM-IFDV Objective
description Inter-Frame delay variation objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….

SOAM-LCK Alarm
description LCK messages received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging log
LED signaling none
possible causes Intended Maintenance Mode (not a defect)

SOAM-LOSCSF
description Client Signal Fail (Loss of Signal)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with LOS flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.

A3118-X642-R612-01 394 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SOAM-RDICCM Alarm
description Remote defect indication
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling none
debug hints A MEP in the domain has loss of continuity
Service OAM debug information is available via LCT+. See  9.2.1.5, in
the section Last CCM Failure parameters.

SOAM-RDICSF
description Client Signal Fail (Reverse Defect Indication)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with RDI flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.

SOAM-RemoteCCM Alarm
description CCMs missing
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging log
LED signaling none
debug hints Loss of continuity: at least 3 subsequent CCM packets have been lost (or
received too late). Loss of continuity may be caused by:
 Interruption in the connection
 Configuration error

SOAM-XconCCM Alarm
description Cross connect error
alarm location MEP
defect location MEP
default severity Critical
default logging log
LED signaling none
debug hints This alarm indicates, that a service OAM MEP is receiving alien CCM
packets
 CCM packets from a different domain (CCM leak)
 CCM packets from a lower CCM layer (configuration error CCM in lower
layer not terminated)
Service OAM debug information is available via LCT+. See  9.2.1.5, in
the section Last CCM Failure parameters.

A3118-X642-R612-01 395 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SHDSL-64-65B Alarm
description 64/65B not synchronized
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling RED SHDSL-U LED Blink-Fast
debug hints This alarm indicates a 64/65B encapsulation coding error. This alarm can
occur as a transient at SHDSL startup or in case of interoperability error
(possible in case of devices from different vendors).

SHDSL-BER3 Alarm
description Bit error rate > 10-3
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling none
debug hints The Bit Error Ratio 10-3 alarm on one of the wires of the transmission
interface indicates that the received signal has a bit error rate that
exceeds 10-3. A cause for this is most likely an impaired transmission line.
Check the line performance parameters (line attenuation / signal to noise
ratio margin) and the cable installation.

SHDSL-BER6 Alarm
description Bit error rate > 10-6
alarm location PME
defect location PME
default severity Minor
default logging log
LED signaling none
debug hints The Bit Error Ratio 10-6 alarm on one of the wires of the transmission
interface indicates that the received signal has a bit error rate that
exceeds 10-6 (one bit out of a million is wrong). Sporadic bit errors may
occur on copper lines, e.g. because of impulse noise.
If the error frequently occurs or persists, the cause should be investigated.
A likely cause of disturbances is an impaired transmission line. Check the
line performance parameters (line attenuation / signal to noise ratio
margin) and the cable installation.
Reliable grounding the equipment often helps to eliminate disturbances.

SHDSL-LOS Alarm
description Loss of signal
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling RED SHDSL-U LED ON
defect(s) Loss of signal
possible causes  wiring error
 remote device is not connected
 the copper wire is broken

A3118-X642-R612-01 396 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

SHDSL-LOSW Alarm
description Loss of synchronization word
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling RED SHDSL-U LED Blink-Slow
debug hints The wire pair is in the training state, i.e. is trying to establish the SHDSL
link. This state is normally transitory (typically about 30 seconds). This
state indicates that the electrical connection between LT and NT /
regenerator is ok.
If the state persists (some minutes), the copper wire may have a reach
problem and it could be necessary to reduce the line speed.

SNR Margin Aggregation Threshold

description SNR margin below aggregation threshold
alarm location PME
defect location PME
default severity Critical
default logging log
LED signaling none
debug hints Lines with insufficient SNR margin may cause disturbances which can
affect the entire aggregated link. Therefore the option to remove lines which
fall below a so-called "aggregation threshold" is available.
If the signal to Noise margin of the line has fallen below the configured SNR
aggregation threshold, the line is removed from the aggregation and the
"SNR Margin Aggregation Threshold Alarm" is raised.

TDM-AIS Alarm
description Loss of Frame Alignment at TDM/Clock interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Critical
default logging Log
LED signaling CLOCK RED Blinking-Fast
debug hints Check the TDM device connected to ACCEED

TDM-BER3 Alarm
description Bit Error Rate of 10E-3 at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Critical
default logging Log
LED signaling none
debug hints Check the TDM device connected to ACCEED

A3118-X642-R612-01 397 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

TDM-BER6 Alarm
description Bit Error Rate of 10E-6 at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Minor
default logging Log
LED signaling None
debug hints Check the TDM device connected to ACCEED

TDM-LFA Alarm
description Alarm Indication Signal at TDM interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Minor
default logging Log
LED signaling CLOCK YELLOW ON
debug hints Check the TDM device connected to ACCEED

TDM-LOS Alarm
description Loss of Signal at TDM/Clock interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Critical
default logging log
LED signaling CLOCK RED ON
debug hints Check the TDM connection and input signal

TDM-RAI Alarm
description Remote Alarm Indication at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Minor
default logging Log
LED signaling none
debug hints Check the TDM device connected to ACCEED

A3118-X642-R612-01 398 / 405

ULAF+ 12 - Troubleshooting ACCEED 1102/04 Manual

Temperature Alarm (desktop only)

description Temperature above critical value
alarm location Equipment
defect location Equipment
default severity Critical
default logging log
LED signaling none
debug hints The desktops inner temperature is measured and supervised.
If the inner temperature exceeds a threshold, indicating that the device is
approaching a critical value, the temperature alarm is raised.
If the inner temperature continues to rise, then the device is forced to a
shutdown mode before the equipment gets permanently damaged.
Possible causes could be:
 Too high environment temperature
 Fan failure
Suggested recovery procedure:
 Power off the equipment
 Wait until devices cooled
 Try to power on and check the fan alarm state

If the fan is in operation, the temperature alarm is raised at about 65°C environment
temperature and the device is shut down at about 80°C.
 If the fan is out of order the temperature alarm will likely occur at any environment
temperature and the device is shut down at about 20°C.

The device is specified up to 55°C environment temperature and must never be used at
higher temperatures

A3118-X642-R612-01 399 / 405

ULAF+ 13 - References ACCEED 1102/04 Manual

13
References

[1] ULAF+ Installation Manual (IMN) V4.2

Albis Technologies Ltd
A3118-X300-H100-*-76D1

[2] ULAF+ Installation Manual (IMN) V5.1

Albis Technologies Ltd
A3118-X300-H100-*-7618

[3] ULAF+ Technical Description (TED) V4.2

Albis Technologies Ltd
A3118-X300-H100-*-7618

[4] ULAF+ Technical Description (TED) V5.1

Albis Technologies Ltd
A3118-X300-H100-*-7618

[5] ULAF+ User Manual (UMN)

Albis Technologies Ltd
A3118-X300-H100-*-7619

[6] ULAF+ User Manual (UMN) for the Advanced Bridge and Router Module
Albis Technologies Ltd
A3118-X300-H100-*-7619

[7] Advanced bridge and router module CLI Reference Manual

Albis Technologies Ltd
A3118-X359-A2-2-7619

[8] MCU-S CLI Reference Manual

Albis Technologies Ltd
A3118-X359-A1-3-7619

A3118-X642-R612-01 400 / 405

ULAF+ 13 - References ACCEED 1102/04 Manual

[9] AccessIntegrator Installation Manual(IMN)

Albis Technologies Ltd
A50010-T3-U100-*-76D1

[10] AccessIntegrator System Administration Manual(ADMN)

Albis Technologies Ltd
A50010-T3-U100-*-7671

[11] AccessIntegrator Operation Manual (OMN)

Albis Technologies Ltd
A50010-T3-U100-*-7619

[12] Download Manager User Manual (UMN)

Albis Technologies Ltd
A3118-X300-H110-*-0019

[13] Ordering Information for ULAF+ access platform

Albis Technologies Ltd
Data sheets and product news

[14] ITU-T Recommendation G.991.2 - Single-Pair High-Speed Digital Subscriber Line

(SHDSL) Transceivers

[15] ETSI TS 101 524 - Symmetric single pair high bit rate digital subscriber line (SDSL)
transmission system on metallic local lines

[16] MEF 10.2 - Ethernet Services Attributes Phase 2

http://metroethernetforum.org/PDF_Documents/technical-specifications/MEF10.2.pdf

[17] ITU-T Recommendation Y.1731 - OAM functions and mechanisms for Ethernet based
networks

A3118-X642-R612-01 401 / 405

ULAF+ 14 - Glossary ACCEED 1102/04 Manual

14
Glossary

A3118-X642-R612-01 402 / 405

ULAF+ 14 - Glossary ACCEED 1102/04 Manual

Term Explanation
AcI Access Integrator the ULAF+ Network Management System
BER Bit Error Rate
BERT Bit Error Rate Test
BiDi Bidirectional transmission over a single fiber
The Bundling service attribute enables two or more VLAN IDs to be
mapped to a single EVC at a UNI. With bundling, the provider and
subscriber must agree on the VLAN IDs used at the UNI and the
Bundling mapping between each VLAN ID and a specific EVC.
A special case of bundling is where every VLAN ID at the UNI
interface maps to a single EVC. This service attribute is called all-to-
one bundling.
Committed Burst Size, CBS is a bandwidth profile parameter. It
CBS limits the maximum number of bytes available for a burst of service
packets sent at the UNI speed to remain CIR-conformant.
CCM Continuity Check Message (Service OAM)
CE Customer Edge, Equipment on the Subscriber side of the UNI.
CES Circuit Emulation Service
CF is a bandwidth profile parameter. The Coupling Flag allows the
CF choice between two modes of operation of the rate enforcement
algorithm.
Committed Information Rate, CIR is a bandwidth profile parameter.
It defines the average rate in bits/s of service packets up to which
CIR
the network delivers service packets and meets the performance
objectives de-fined by the CoS Service Attribute.
A set of service packets that have a commitment from the Service
Class of Service
Provider to receive a particular level of performance.
Information derivable from a) the EVC to which the service packet is
mapped, b) the combination of the EVC to which the service packet
is mapped and a set of one or more CE-VLAN CoS values, c) the
Class of Service Identifier combination of the EVC to which the service packet is mapped and
a set of one or more DSCP values, or d) the combination of the EVC
to which the service packet is mapped and a set of one or more
tunneled Layer 2 Control Protocols.
Color Mode, CM is a bandwidth profile parameter. The color mode
CM parameter indicates whether the color-aware or color-blind property
is employed by the bandwidth profile
CFM Continuity Fault Management
A Bandwidth Profile property where a pre-determined level of
Bandwidth Profile compliance for each service packet is taken into
Color-aware
account when determining the level of compliance for each service
packet.
A bandwidth profile property where a pre-determined level of
bandwidth profile compliance for each service packet, if present, is
Color-blind
ignored when determining the level of compliance for each service
packet.
CoS Class of service, corresponds to IEEE 802.1p priorities
DNU Do Not Use (for synchronization)
DSCP Diffserv Codepoints, extended priority field in IPv4 header
Extended Burst Size, EBS is a bandwidth profile parameter. It limits
the maximum number of bytes available for a burst of service
EBS
packets sent at the UNI speed which are colored yellow. This setting
is only available in single rate policing mode
EFM Ethernet in the First Mile, IEEE 802.1ah
Egress Outbound direction
EOC Embedded Operating Channel
EPL Ethernet Private Line, P2P connection via one EVC

A3118-X642-R612-01 403 / 405

ULAF+ 14 - Glossary ACCEED 1102/04 Manual

E-Service Ethernet-Service (transmission of Ethernet packets)

ESMC Ethernet Synchronization Message Channel
Ethernet OAM Ethernet Operation Administration and Maintenance
EVC Ethernet Virtual Channel/Circuit
EVPL Ethernet Virtual Private Line, P2P connection via several EVCs
FD Full Duplex
FE Fast Ethernet – 100 Mbit/s
GbE Gigabit Ethernet – 1’000 Mbit/s
IETF Internet Engineering Task Force
Ingress Inbound direction
INV Invalid
IP Internet Protocol
Layer 2 Control Protocol, a service packet that is used for Layer 2
L2CP
control, e.g., Spanning Tree Protocol.
LAN Local Area Network
ULAF+ Local Craft Terminal (Element manager for both local and
LCT+
remote management of ULAF+ equipment)
LSP Label Switched Path (MPLS)
LSR Label Switching Router (Router with MPLS functionality)
LT Line Termination
MAC Media Access Controller
MCU Management and Concentrator Unit
Management and Concentrator Unit with Carrier Grade Ethernet
MCU-S
Switch and GbE uplink
Management and Concentrator Unit with Carrier Grade Ethernet
MCU-CES
Switch, GbE uplink and Circuit Emulation Service functionality
MDF Main Distribution Frame
MIB Management Information Base
Multipoint-to-Multipoint EVC, an EVC with two or more UNIs. A
Multipoint-to-Multipoint EVC with two UNIs is different from a Point-
MP2MP EVC
to-Point EVC because one or more additional UNIs can be added to
it.
MPLS Multi-Protocol Label Switching
MSTP Multiple Spanning Tree Protocol
Network Element (from management system perspective, a generic
NE
manageable device).
NMS Network Management System
NT Network Termination
OSI Open Systems Interconnection
P2P EVC An EVC with exactly 2 UNIs.
PAF PME (Physical Medium Entities) Aggregation Function
PBB Provider Backbone Bridging
PBB-TE Provider Backbone Bridging - Traffic Engineering
Peak Burst Size, PBS is a bandwidth profile parameter. It limits the
PBS maximum number of bytes available for a burst of service packets
sent at the UNI speed to remain PIR-conformant.
Policy Control List, defines a list with lookup keys and actions, used
PCL
for classifying traffic
Peak Information Rate, PIR is a bandwidth profile parameter. It
defines the average rate in bits/s of service packets up to which the
PIR
network may deliver service packets but without any performance
objectives.
PME Physical Medium Entity
PRC Primary Reference Clock
Implies that subsequent mechanisms (switch pipeline stages) may
Precedence Hard
not override the current assignment

A3118-X642-R612-01 404 / 405

ULAF+ 14 - Glossary ACCEED 1102/04 Manual

Implies that subsequent mechanisms (switch pipeline stages) may

Precedence Soft
override the current assignment
PTP Precision Time Protocol
RMON Remote Network Monitoring
QL Quality Level
QoS Quality Of Service
A multipoint EVC in which each UNI is designated as either a Root
or a Leaf. Ingress service packets at a Root UNI can be delivered to
Rooted-Multipoint EVC one or more of any of the other UNIs in the EVC. Ingress service
packets at a Leaf UNI can only be delivered to one or more Root
UNIs in the EVC.
RSTP Rapid Spanning Tree Protocol
System Cross Connect. Connection between ACCEED units in an
SCC
array.
SEC SDH Equipment Clock
An Ethernet packet transmitted across the UNI toward the Service
Service Packet Provider or an Ethernet packet transmitted across the UNI toward
the Subscriber.
Service multiplexing is used to support multiple instances of EVCs
Service Multiplexing on the same physical connection. This allows the same customer to
have different services with the same Ethernet wire.
Service Provider The organization providing Ethernet Service(s).
SFP Small Form factor Pluggable
SHDSL Single-Pair High-speed Digital Subscriber Line
SLA Service Level Agreement
SNMP Simple Network Management Protocol
According to ITU-T G.781: an action that cuts-off (i.e. shuts down)
an output signal. For some signals (e.g. 2 Mbit/s) squelching may be
Squelch
realized by means of inserting AIS, instead of shutting down the
signal.
SrTcm Single Rate Two Color Mode
Synchronization Status Message / Synchronization Status
SSM
Messaging
SSU Synchronization Supply Unit
SSU-A Primary Level SSU
SSU-B Second Level SSU
STP Spanning Tree Protocol
Subscriber The organization purchasing and/or using Ethernet Services.
SyncE Synchronous Ethernet
TLS Transparent LAN Service
TOS Type Of Service, Priority field in IPv4 Header
Tag Protocol Identifier, corresponds to the Ethertype of the VLAN
TPID
tag
TrTcm Two Rates Three Color Mode
User Network Interface, The physical demarcation point between
UNI the responsibility of the Service Provider and the responsibility of
the Subscriber
WAN Wide Area Network

A3118-X642-R612-01 405 / 405