ACCEED Manual 2202 PDF

ULAF+
ACCEED 2202 Manual Release 6.7

A3118-X652-R67-02
ULAF+ ACCEED 2202 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 2202 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
2202 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 2012

Albisriederstrasse 199
CH-8047 Zrich
Technical modifications possible

Technical specifications and features are binding only insofar as they are specifically and expressly
agreed upon in a written contract.
A3118-X652-R67-02 2 / 297
Contents
1 Notes on product safety ................................................................................................................. 12
1.1 Representation conventions................................................................................................. 13
1.2 Product Safety...................................................................................................................... 14
1.2.1 Notes on protection against laser radiation ..................................................................... 14
1.3 EMC ..................................................................................................................................... 15
1.4 Device handling.................................................................................................................... 16
1.4.1 Electrostatic Sensitive Devices (ESD)............................................................................. 16
1.4.2 Inserting/ removing plug in units ...................................................................................... 16
1.4.3 Stacking the desktop units............................................................................................... 16
1.4.4 Disposal of equipment and units...................................................................................... 17
1.5 Over voltage protection ........................................................................................................ 18
1.5.1 Protection of a network element ...................................................................................... 18
2 Introduction..................................................................................................................................... 19
2.1 ULAF+ documentation structure .......................................................................................... 20
2.2 ACCEED 2202 Manual Structure......................................................................................... 23
2.3 Representation conventions................................................................................................. 24
2.3.1 ACCEED manual naming conventions ............................................................................ 24
2.4 ULAF+ System overview...................................................................................................... 25
2.4.1 Service Interfaces ............................................................................................................ 26
2.4.2 Transmission Interfaces................................................................................................... 26
2.4.3 MEF Carrier Ethernet Services attributes........................................................................ 26
2.4.4 Management Systems ..................................................................................................... 27
2.4.5 ULAF+ Product Range..................................................................................................... 28
3 Application overview....................................................................................................................... 31
3.1 ACCEED 2202 overview ...................................................................................................... 32
3.1.1 Gigabit EFM fiber demarcation, transmission and aggregation unit................................ 32
3.1.2 Technical data.................................................................................................................. 33
3.2 Typical ACCEED 2202 applications..................................................................................... 34
3.2.1 Business Access.............................................................................................................. 34
3.2.2 Wholesale Carrier Ethernet Demarcation........................................................................ 36
3.2.3 Backhaul .......................................................................................................................... 36
3.3 System configurations.......................................................................................................... 37
3.3.1 Mechanics........................................................................................................................ 39
3.3.2 HW options ...................................................................................................................... 39
3.3.3 ACCEED 2202 applications............................................................................................. 39
3.3.4 Uplink interface ................................................................................................................ 40
4 Quick Start Guide ........................................................................................................................... 42
4.1 Introduction .......................................................................................................................... 43
4.2 HW setup.............................................................................................................................. 44
4.2.1 Central Office Setup ........................................................................................................ 44
4.2.2 Remote Terminal Setup................................................................................................... 44
4.2.3 Wiring............................................................................................................................... 44
4.3 EFM link configuration.......................................................................................................... 45
4.3.1 LCT+ installation .............................................................................................................. 45
4.3.2 Remote management configuration ................................................................................ 45
4.3.3 EFM-Link configuration.................................................................................................... 45
5 Installation ...................................................................................................................................... 46
5.1 General requirements/check list .......................................................................................... 47
5.2 Power supply........................................................................................................................ 49
5.2.1 Power supply to the plug in unit....................................................................................... 49
5.2.2 Power supply to the desktop unit..................................................................................... 49
5.3 Grounding concept............................................................................................................... 53
5.4 Interfaces / pinning............................................................................................................... 54
5.4.1 SHDSL interface .............................................................................................................. 55
5.4.2 Ethernet interfaces (10Base-T/100Base-Tx/1000Base-Tx) ............................................ 55
5.4.3 SFP slot interface ............................................................................................................ 55
A3118-X652-R67-02 3 / 297
5.4.4 NMS interface (10/100 Base-T) ....................................................................................... 56

5.4.5 Clock Interface ................................................................................................................. 56
5.4.6 LCT serial interface.......................................................................................................... 58
5.5 DIP switches ........................................................................................................................ 59
5.5.1 DIP switches of Plug in units ........................................................................................... 59
5.5.2 DIP switches of Desktop units ......................................................................................... 59
5.6 Visual indications ................................................................................................................. 60
5.7 LCT+ SW installation............................................................................................................ 62
5.7.1 System requirements....................................................................................................... 62
5.7.2 Installation of the Software .............................................................................................. 62
5.7.3 Uninstalling the Software ................................................................................................. 69
5.8 On site configuration ............................................................................................................ 72
5.8.1 LCT+ ................................................................................................................................ 72
5.8.2 ACCEED 2202 management access .............................................................................. 72
5.8.3 SCC connections ............................................................................................................. 76
5.8.4 EFM link Setup................................................................................................................. 76
5.8.5 Remote Power Supply ..................................................................................................... 76
5.8.6 Power over Ethernet (PoE).............................................................................................. 76
5.8.7 Time settings.................................................................................................................... 78
5.9 Maintenance functions ......................................................................................................... 79
5.9.1 Loopback ......................................................................................................................... 79
5.9.2 BER test........................................................................................................................... 79
5.9.3 Switch port mirroring........................................................................................................ 79
5.9.4 Trap suppression ............................................................................................................. 80
6 Configuration and operation ........................................................................................................... 81
6.1 Management access ............................................................................................................ 82
6.2 LCT+ .................................................................................................................................... 83
6.2.1 Introduction ...................................................................................................................... 83
6.2.2 Starting the LCT+............................................................................................................. 83
6.2.3 The graphical user interface ............................................................................................ 86
6.2.4 Title bar ............................................................................................................................ 87
6.2.5 Menu bar.......................................................................................................................... 88
6.2.6 Status bar......................................................................................................................... 97
6.2.7 The Summary area .......................................................................................................... 98
6.2.8 The View area................................................................................................................ 104
6.2.9 The Tree area ................................................................................................................ 106
6.2.10 The Table area............................................................................................................... 108
7 EFMC Aggregation....................................................................................................................... 117
7.1 EFM Link ............................................................................................................................ 118
8 Ethernet Switch ............................................................................................................................ 119
8.1 Introduction ........................................................................................................................ 120
8.2 ACCEED 2202 switching features at a glance................................................................... 121
8.3 The Building Blocks of the Ethernet switch........................................................................ 123
8.4 Port Control ........................................................................................................................ 125
8.4.1 Global switch port settings............................................................................................. 125
8.4.2 Individual Switch Port Settings ...................................................................................... 127
8.4.3 L2 Control Protocol ........................................................................................................ 133
8.5 Switch Control .................................................................................................................... 135
8.5.1 Forwarding Database .................................................................................................... 135
8.5.2 Aging Time..................................................................................................................... 137
8.5.3 Port isolation .................................................................................................................. 138
8.5.4 Port mirroring ................................................................................................................. 139
8.6 VLAN .................................................................................................................................. 140
8.6.1 VLAN mode.................................................................................................................... 140
8.6.2 VLAN Tag Naming Convention in ACCEED.................................................................. 141
8.6.3 Global VLAN settings..................................................................................................... 142
8.6.4 Port Based VLAN Settings............................................................................................. 154
8.6.5 Tag Protocol Identifier (TPID) list Ingress port ........................................................... 156
8.6.6 Tag Protocol Identifier (TPID) list Egress port ............................................................ 156
A3118-X652-R67-02 4 / 297
8.7 Ethernet Switch Fault Management................................................................................... 157

8.8 Ethernet Switch QoS handling ........................................................................................... 158
8.8.1 Packet Classification...................................................................................................... 158
8.8.2 Policing .......................................................................................................................... 162
8.8.3 Queuing ......................................................................................................................... 170
8.9 EVC Concept ..................................................................................................................... 178
8.10 Statistics and Utilization ..................................................................................................... 179
8.10.1 Introduction .................................................................................................................... 179
8.10.2 Port statistics.................................................................................................................. 182
8.10.3 Policy statistics............................................................................................................... 184
8.10.4 QoS Tx Queue statistics ............................................................................................. 185
8.10.5 Port based metering statistics........................................................................................ 186
8.10.6 EVC statistics................................................................................................................. 187
8.10.7 Utilization ....................................................................................................................... 188
9 Operation and Maintenance......................................................................................................... 191
9.1 Link OAM............................................................................................................................ 192
9.1.1 Link OAM Configuration................................................................................................. 193
9.2 Service OAM ...................................................................................................................... 194
9.2.8 Service OAM Domains and Maintenance Points........................................................ 194
9.2.9 Service OAM Fault Management................................................................................... 203
9.2.10 Service OAM Performance Monitoring .......................................................................... 208
9.3 Service Activation Test (Y.1564)........................................................................................ 225
9.3.1 Measurement Principle .................................................................................................. 226
9.3.2 Measurement Sequence Details.................................................................................... 227
9.3.3 Format of Test Frames .................................................................................................. 229
9.3.4 Test execution................................................................................................................ 230
9.3.5 SAT General configuration ......................................................................................... 231
9.3.6 SAT Configuration of the Test CoS Instances............................................................ 232
9.3.7 Results ........................................................................................................................... 234
9.3.8 Test Report .................................................................................................................... 236
10 CES Circuit Emulation for TDM Services .............................................................................. 238
10.1 Introduction to TDM CES ................................................................................................... 240
10.1.8 What is CES ?................................................................................................................ 240
10.1.9 Motivation to do CES ..................................................................................................... 240
10.1.10 Technical Challenges ................................................................................................ 240
10.1.11 Payload Type and Encapsulation.............................................................................. 241
10.1.12 CES - Functional Components and Interfaces.......................................................... 242
10.1.13 CES operation principle............................................................................................. 244
10.2 CES Applications with ACCEED ........................................................................................ 248
10.2.8 Interworking Scenario .................................................................................................... 250
10.3 Configuring CES ................................................................................................................ 251
10.3.1 Enabling CES and the TDM interface............................................................................ 251
10.3.2 Configuring the CES parameters................................................................................... 251
10.3.3 Configuring the Framer.................................................................................................. 253
10.3.4 CES clock synchronization ............................................................................................ 253
10.4 CES Performance Monitoring and Fault management ...................................................... 254
10.4.1 TDM performance counters ........................................................................................... 254
10.4.2 CES packet and jitter buffer performance ..................................................................... 255
10.4.3 CES Packet Statistics .................................................................................................... 256
10.4.4 CES / TDM Loopback .................................................................................................... 256
10.4.5 CES Alarming ................................................................................................................ 257
10.5 CES Operational Aspects .................................................................................................. 258
10.5.1 Planning CES................................................................................................................. 258
10.5.2 Trouble Shooting CES ................................................................................................... 258
11 General Board settings ............................................................................................................. 260
11.1 Board general system information .................................................................................. 261
11.1.1 System Log .................................................................................................................... 261
11.1.2 Ressources .................................................................................................................... 262
11.1.3 Inventory ........................................................................................................................ 263
A3118-X652-R67-02 5 / 297
11.2 Alarm configuration ............................................................................................................ 264

11.2.1 Severity .......................................................................................................................... 264
11.2.2 Logging .......................................................................................................................... 266
11.3 Local................................................................................................................................... 267
11.3.1 Information ..................................................................................................................... 267
11.3.2 SCC Configuration......................................................................................................... 267
11.3.3 Maintenance .................................................................................................................. 267
11.3.4 Time Setting................................................................................................................... 268
11.3.5 Management Access ..................................................................................................... 268
11.4 Synchronization.................................................................................................................. 269
11.4.1 Introduction .................................................................................................................... 269
11.4.2 ACCEED synchronization overview .............................................................................. 269
11.4.3 Clock sources ................................................................................................................ 270
11.4.4 Synchronization ports .................................................................................................... 270
11.4.5 Clock source selection mechanism ............................................................................... 271
11.4.6 Supported quality and priority values ............................................................................ 271
11.4.7 Synchronisation input selection on LT........................................................................... 272
11.4.8 Synchronization output selection on NT ........................................................................ 272
11.4.9 SSM support .................................................................................................................. 273
11.4.10 Synchronization Fault Management.......................................................................... 273
11.4.11 Synchronization configuration ................................................................................... 273
12 Troubleshooting ........................................................................................................................ 277
12.1 Most common troubles....................................................................................................... 278
12.1.1 SHDSL startup problems ............................................................................................... 278
12.2 LED indications .................................................................................................................. 279
12.2.1 Power LED (1) ............................................................................................................... 279
12.2.2 Alarm LED (1) ................................................................................................................ 279
12.2.3 MAINT LED (1) .............................................................................................................. 280
12.2.4 CLK LED (4)................................................................................................................... 280
12.2.5 NMS green LED (5) ....................................................................................................... 280
12.2.6 ETH Px green LED (6) and (7) ...................................................................................... 280
12.2.7 SFPx LED (8) and (9) .................................................................................................... 280
12.3 Alarm list............................................................................................................................. 281
12.3.1 CES-AIS Alarm .............................................................................................................. 281
12.3.2 CES-ARE Alarm............................................................................................................. 281
12.3.3 CES-LOF Alarm ............................................................................................................. 281
12.3.4 CES-RAI Alarm .............................................................................................................. 281
12.3.5 Clock Not Available Alarm ............................................................................................. 282
12.3.6 Clock Squelched Alarm ................................................................................................. 282
12.3.7 Equipment Alarm ........................................................................................................... 282
12.3.8 ETH No Link Alarm ........................................................................................................ 283
12.3.9 Fan Alarm (desktop only)............................................................................................... 283
12.3.10 LAG-Aggregation Loss .............................................................................................. 283
12.3.11 LAG-Aggregation Mismatch ...................................................................................... 283
12.3.12 LAG-Partial Aggregation Loss................................................................................... 283
12.3.13 LFP Alarm.................................................................................................................. 284
12.3.14 LinkOAM-Critical Event Alarm................................................................................... 284
12.3.15 LinkOAM-Dying Gasp Alarm ..................................................................................... 284
12.3.16 LinkOAM-Invalid Peer Alarm ..................................................................................... 284
12.3.17 LinkOAM-No Peer Alarm........................................................................................... 285
12.3.18 PoE Fault Alarm ........................................................................................................ 286
12.3.19 Power Failure Alarm .................................................................................................. 286
12.3.20 Resource Shortage Alarm ......................................................................................... 286
12.3.21 SOAM-AIS Alarm....................................................................................................... 286
12.3.22 SOAM-Avail Objective ............................................................................................... 287
12.3.23 SOAM-ErrorCCM Alarm ............................................................................................ 287
12.3.24 SOAM-FD Objective .................................................................................................. 287
12.3.25 SOAM-FLR Threshold ............................................................................................... 287
12.3.26 SOAM-IFDV Objective .............................................................................................. 288
A3118-X652-R67-02 6 / 297
12.3.27 SOAM-LCK Alarm ..................................................................................................... 288

12.3.28 SOAM-RDICCM Alarm.............................................................................................. 288
12.3.29 SOAM-RemoteCCM Alarm ....................................................................................... 288
12.3.30 SOAM-XconCCM Alarm............................................................................................ 289
12.3.31 SFP-Incompatible Alarm ........................................................................................... 289
12.3.32 SFP-Missing Alarm.................................................................................................... 289
12.3.33 SFP-Tx Fault Alarm ................................................................................................... 289
12.3.34 TDM-AIS Alarm ......................................................................................................... 290
12.3.35 TDM-BER3 Alarm...................................................................................................... 290
12.3.36 TDM-BER6 Alarm...................................................................................................... 290
12.3.37 TDM-LFA Alarm......................................................................................................... 290
12.3.38 TDM-LOS Alarm ........................................................................................................ 291
12.3.39 TDM-RAI Alarm ......................................................................................................... 291
12.3.40 Temperature Alarm (desktop only)............................................................................ 291
13 References ............................................................................................................................... 292
14 Glossary.................................................................................................................................... 294
A3118-X652-R67-02 7 / 297
Figures
Figure 1-1 ESD symbol ......................................................................................................................... 16

Figure 1-2 Disposal of equipment and units.......................................................................................... 17
Figure 1-3 Over voltage protection........................................................................................................ 18
Figure 2-1 ULAF+ system ..................................................................................................................... 25
Figure 2-2 Typical ULAF+ applications ................................................................................................. 25
Figure 2-3 ULAF+ LCT+ GUI ................................................................................................................ 27
Figure 3-1 ACCEED 2202 plug in and desktop..................................................................................... 32
Figure 3-2 E-LAN service (multipoint to multipoint EVC) ...................................................................... 34
Figure 3-3 E-Line service (point to point EVC)...................................................................................... 35
Figure 3-4 E-Tree service (rooted multipoint EVC) ............................................................................... 35
Figure 3-5 ACCEED 2202 wholesale application.................................................................................. 36
Figure 3-6 Mobile Backhaul example .................................................................................................... 36
Figure 3-7 ACCEED 2202 configuration examples ............................................................................... 37
Figure 3-8 Line / Link / Service definition .............................................................................................. 38
Figure 3-9 ACCEED 2202 applications ................................................................................................. 40
Figure 3-10 Uplink traffic concentration via MCU-S .............................................................................. 41
Figure 4-1 Quick start exemplary configuration .................................................................................... 43
Figure 4-2 Exemplary configuration wiring ............................................................................................ 44
Figure 4-3 LCT+ installation .................................................................................................................. 45
Figure 5-1 ACCEED 2202 plug in unit................................................................................................... 48
Figure 5-2 ACCEED 2202 desktop unit................................................................................................. 48
Figure 5-3 Location of desktop power supply terminals and selection jumpers.................................... 50
Figure 5-4 AC and DC power supply..................................................................................................... 51
Figure 5-5 ACCEED 2202 plug in and desktop front panel interfaces and LEDs ................................. 54
Figure 5-6 Subrack clock in interfaces (75 and 120 Ohm).................................................................... 57
Figure 5-7 Visual signaling of the ACCEED 2202................................................................................. 60
Figure 5-8 ACCEED 2202 slow blinking LED....................................................................................... 61
Figure 5-9 ACCEED 2202 fast blinking LED ........................................................................................ 61
Figure 5-10 LCT+ setup program .......................................................................................................... 62
Figure 5-11 LCT+ Setup Wizard............................................................................................................ 63
Figure 5-12 LCT+ components to install .............................................................................................. 63
Figure 5-13 Destination folder ............................................................................................................... 64
Figure 5-14 Shortcuts ............................................................................................................................ 65
Figure 5-15 Completing the LCT+ Setup .............................................................................................. 65
Figure 5-16 LCT+ Setup Wizard............................................................................................................ 66
Figure 5-17 LCT+ previous version detected ........................................................................................ 66
Figure 5-18 LCT+ components to install .............................................................................................. 67
Figure 5-19 Destination folder ............................................................................................................... 68
Figure 5-20 Shortcuts ............................................................................................................................ 68
Figure 5-21 Completing the LCT+ Setup .............................................................................................. 69
Figure 5-22 LCT+ ùninstaller` .............................................................................................................. 69
Figure 5-23 Uninstall the LCT+ SW....................................................................................................... 70
Figure 5-24 Uninstall options................................................................................................................. 70
Figure 5-25 Uninstall complete.............................................................................................................. 71
Figure 5-26 LCT+ connection via RS232 interface ............................................................................... 73
Figure 5-27 example of ACCEED NMS management connections ...................................................... 74
Figure 5-28 Powering of CE (Customer Equipment) via PoE ............................................................... 77
Figure 6-1 LCT+ Graphical User Interface ............................................................................................ 83
Figure 6-2 LCT+ start dialogue.............................................................................................................. 84
Figure 6-3 LCT+ Login dialogue window............................................................................................... 85
Figure 6-4 LCT+ GUI ............................................................................................................................. 86
Figure 6-5 LCT+ window header example ............................................................................................ 87
Figure 6-6 File Menu ............................................................................................................................. 88
Figure 6-7 File Menu ............................................................................................................................. 88
Figure 6-8 Save configuration window .................................................................................................. 89
Figure 6-9 Save window ........................................................................................................................ 90
A3118-X652-R67-02 8 / 297
Figure 6-10 Open window ..................................................................................................................... 91

Figure 6-11 Load configuration window ................................................................................................ 92
Figure 6-12 Options Menu..................................................................................................................... 92
Figure 6-13 Preview mode .................................................................................................................... 93
Figure 6-14 LCT+ Preview mode .......................................................................................................... 94
Figure 6-15 Connection option .............................................................................................................. 94
Figure 6-16 Confirmation options .......................................................................................................... 95
Figure 6-17 Alarm log clear warning ..................................................................................................... 95
Figure 6-18 Logging options.................................................................................................................. 95
Figure 6-19 Trap Log example .............................................................................................................. 96
Figure 6-20 Export................................................................................................................................. 96
Figure 6-21 Help Menu.......................................................................................................................... 97
Figure 6-22 LCT+ About Window .......................................................................................................... 97
Figure 6-23 LCT+ window bottom detail example................................................................................. 97
Figure 6-24 LCT+ progress bar example .............................................................................................. 97
Figure 6-25 LCT+ preview mode active ................................................................................................ 97
Figure 6-26 LCT+ Areas........................................................................................................................ 98
Figure 6-27 Connection dialogue .......................................................................................................... 99
Figure 6-28 User Management dialogue............................................................................................... 99
Figure 6-29 Download dialogue .......................................................................................................... 100
Figure 6-30 Open download file .......................................................................................................... 101
Figure 6-31 Download OK ................................................................................................................... 101
Figure 6-32 Download progress bar.................................................................................................... 101
Figure 6-33 Download finished............................................................................................................ 102
Figure 6-34 Remote download dialogue ............................................................................................. 102
Figure 6-35 Rack view......................................................................................................................... 104
Figure 6-36 Ethernet view ................................................................................................................... 106
Figure 6-37 ACCEED 2202 Tree view ................................................................................................ 107
Figure 6-38 Table tabs ........................................................................................................................ 108
Figure 6-39 Table area example ......................................................................................................... 109
Figure 6-40 Configuration example ..................................................................................................... 110
Figure 6-41 Fault / Alarms ................................................................................................................... 111
Figure 6-42 Alarm Log......................................................................................................................... 111
Figure 6-43 Fault / Maintenance ......................................................................................................... 112
Figure 6-44 Fault / SOAM.................................................................................................................... 113
Figure 6-45 Configuration example ACCEED 2202............................................................................ 114
Figure 6-46 Configuration / Summary ................................................................................................. 115
Figure 8-1 Ethernet switch building blocks.......................................................................................... 123
Figure 8-2 Local and remote switch view with LCT+........................................................................... 124
Figure 8-3 Building block port control............................................................................................... 125
Figure 8-4 Overview switch ports ACCEED 2202 CM (plug-in) and CS (desktop) device ................. 125
Figure 8-5 Global switch port settings ................................................................................................. 126
Figure 8-6 Individual switch port settings ............................................................................................ 127
Figure 8-7 Link Failure Propagation example ..................................................................................... 131
Figure 8-8 LAG configuration .............................................................................................................. 132
Figure 8-9 Building block switch control ........................................................................................... 135
Figure 8-10 ACCEED - VLAN learning modes.................................................................................... 135
Figure 8-11 ACCEED MAC address Table (VLAN aware mode) ....................................................... 136
Figure 8-12 port isolation..................................................................................................................... 138
Figure 8-13 port mirroring example ..................................................................................................... 139
Figure 8-14 Building block VLAN ..................................................................................................... 140
Figure 8-15 ACCEED 2202 VLAN manipulation scenarios................................................................ 141
Figure 8-16 Egress Tagging Mode: - (Discard) ................................................................................... 144
Figure 8-17 Egress Tagging Mode: Untagged .................................................................................... 145
Figure 8-18 Egress Tagging Mode: Add Primary Tag......................................................................... 146
Figure 8-19 Egress Tagging Mode: Primary Tag Only........................................................................ 147
Figure 8-20 Egress Tagging Mode: Secondary Tag Only................................................................... 148
Figure 8-21 Egress Tagging Mode: Remove Outer Tag ..................................................................... 149
Figure 8-22 Egress Tagging Mode: Inner Primary, Outer Secondary................................................. 150
A3118-X652-R67-02 9 / 297
Figure 8-23 Egress Tagging Mode: Inner Secondary, Outer Primary................................................. 151
Figure 8-24 VLAN DB example ........................................................................................................... 152
Figure 8-25 Packet flow process: Service/Queuing ............................................................................ 158
Figure 8-26 Layer2 packet description ................................................................................................ 158
Figure 8-27 Layer3/4 packet description ............................................................................................. 159
Figure 8-28 Rules: Packet Classification............................................................................................. 160
Figure 8-29 color unaware: Single Rate, Three colors........................................................................ 163
Figure 8-30 color unaware: Two Rate, Three colors ........................................................................... 163
Figure 8-31 color aware: Single Rate, Three colors............................................................................ 164
Figure 8-32 color aware: Two Rate, Three colors ............................................................................... 164
Figure 8-33 Bandwidth Profile ............................................................................................................. 165
Figure 8-34 Ingress Service ................................................................................................................ 166
Figure 8-35 Ingress Port Service Assignment..................................................................................... 168
Figure 8-36 Egress Service ................................................................................................................. 168
Figure 8-37 Egress Port Service Assignment ..................................................................................... 170
Figure 8-38 Trust mode, port CoS and port remark defaults .............................................................. 172
Figure 8-39 QoS port profile ................................................................................................................ 172
Figure 8-40 Ingress CoS profiles......................................................................................................... 173
Figure 8-41 Ingress DSCP profiles...................................................................................................... 174
Figure 8-42 Ingress service profiles .................................................................................................... 175
Figure 8-43 Ingress yellow frame profiles ........................................................................................... 175
Figure 8-44 Egress queue parameter profile....................................................................................... 176
Figure 8-45 Egress queue profile and DEI remark.............................................................................. 176
Figure 8-46 Egress queue parameters................................................................................................ 177
Figure 8-47 Egress port shaping ......................................................................................................... 177
Figure 8-48 Statistics Overview........................................................................................................... 179
Figure 9-1: Ethernet OAM Layers ....................................................................................................... 194
Figure 9-2 Service OAM definitions..................................................................................................... 194
Figure 9-3 Service OAM example ....................................................................................................... 195
Figure 9-4 Service OAM maintenance levels ...................................................................................... 196
Figure 9-5 Service OAM MEP orientation ........................................................................................ 196
Figure 9-6 Service OAM Linktrace Replies ...................................................................................... 207
Figure 9-7 Two-way vs. one-way measurement ................................................................................. 208
Figure 9-8 Service OAM PM session and responder principle ........................................................ 209
Figure 9-9 Service OAM Round trip delay measurement principle .................................................. 211
Figure 9-10 Service OAM Delay Measurement Bin ......................................................................... 212
Figure 9-11 Service OAM Inter-frame delay variation measurement principle ................................ 214
Figure 9-12 Service OAM Frame loss ratio (FLR) measurement principle ...................................... 221
Figure 9-13 Service OAM Availability definition ............................................................................... 223
Figure 9-14 Service Activation Test example...................................................................................... 225
Figure 9-15 Service Activation Test Principle...................................................................................... 226
Figure 9-16 SAT sequence.................................................................................................................. 227
Figure 9-17 Service Activation Test example...................................................................................... 231
Figure 9-18 SAT Test CoS Instance ................................................................................................... 232
Figure 9-19 SAT Results ..................................................................................................................... 234
Figure 9-20 SAT Test Report .............................................................................................................. 236
Figure 10-1 CES standards overview.................................................................................................. 239
Figure 10-2 The CES principle ............................................................................................................ 240
Figure 10-3 Structure of the CES Control Word.................................................................................. 242
Figure 10-4 CES functional components............................................................................................. 243
Figure 10-5 Format of CESoETH and CESoMPLS frames................................................................. 244
Figure 10-6 CES operation overview .................................................................................................. 245
Figure 10-7 ACCEED 2202 CES Application Overview................................................................... 249
Figure 10-8 ACCEED CES Network ................................................................................................... 250
Figure 10-9 CES Alarm locations ........................................................................................................ 257
Figure 11-1 Clock sources example.................................................................................................... 270
Figure 11-2 LT Synchronization .......................................................................................................... 272
Figure 11-3 NT Synchronization.......................................................................................................... 272
Figure 11-4 Synchronization configuration model............................................................................... 273
A3118-X652-R67-02 10 / 297
Figure 12-1 ACCEED 2202 LEDs ....................................................................................................... 279
A3118-X652-R67-02 11 / 297
ULAF+ 1 - Notes on product safety ACCEED 2202 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-X652-R67-02 12 / 297
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 readers 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-X652-R67-02 13 / 297
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.
1.2.1 Notes on protection against laser radiation
Normal operation
Only class1 SFPs shall be used
Dangerous fault
The ACCEED unit corresponds to the Laser class 1 for all disturbances.
A3118-X652-R67-02 14 / 297
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 2202 Manual (chapter 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-X652-R67-02 15 / 297
1.4 Device handling

1.4.1 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.
1.4.2 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.
1.4.3 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-X652-R67-02 16 / 297
1.4.4 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-X652-R67-02 17 / 297
1.5 Over voltage protection
BSRU BSRU ACCEED
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.
1.5.1 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 chapter
5.3.
A3118-X652-R67-02 18 / 297
ULAF+ 2 - Introduction ACCEED 2202 Manual
2
Introduction
This chapter gives an overview of the ULAF+ system and the product
range.
A3118-X652-R67-02 19 / 297
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 1416 Manual
- ACCEED 1102/04 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
- Flexible interface converter for Ethernet and data services over E1: BGTU
- 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-X652-R67-02 20 / 297

- 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 regenerator BSRU / BSRU+
- G.703 transmission unit GTU (interface converter)
- Flexible interface converter for Ethernet and data services over E1: BGTU
- 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)
Intended for use by anyone who uses AccessIntegrator to monitor and maintain network
elements.
A3118-X652-R67-02 21 / 297
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-X652-R67-02 22 / 297
2.2 ACCEED 2202 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 2202 unit, describes typical applications and
system configurations and gives an introduction to the ACCEED 2202 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 2202
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 2202.
Chapter 5 gives detailed information and instructions about ACCEED 2202 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 2202
for different possible system configurations.
Chapter 6 this chapter gives detailed information and instructions about how to configure and
operate ACCEED 2202 and LCT+. It contains a description of both ACCEED 2202 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 2202 unit.
Chapter 11 describes the general information and settings of the ACCEED 2202 unit. This covers
inventory and logging information and explains how the alarm configuration is done.
Management access and synchronization options for the ACCEED 2202 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-X652-R67-02 23 / 297
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 readers 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.
2.3.1 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.7 = set of features, corresponding to a particular SW (LCT, LCT+, AcI) and FW
(ACCEED, MCU (MCU-S/MCU-CES) version
Packet = Frames
Regenerator = Repeater
A3118-X652-R67-02 24 / 297
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-X652-R67-02 25 / 297
2.4.1 Service Interfaces

Ethernet
10/100/1000Base-T
SFPs (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)
2.4.2 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
2.4.3 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 and E-Tree Services
TDM Circuit Emulation Service (CES)
Scalability
10/100/1000Mbit/s User Network Interfaces (UNIs)
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-X652-R67-02 26 / 297
Distributed architecture, equipment redundancy

Sub 50ms line- and path protection
Service Management
Fast and flexible service provisioning
Ethernet Link- and Service-OAM
2.4.4 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
Element Manager for AccessIntegrator

Client / server architecture
same look and feel as the LCT / LCT+
Windows and Solaris operating systems
Cross Domain Manager (CDM) for AccessIntegrator supported
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-X652-R67-02 27 / 297
2.4.5 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-X652-R67-02 28 / 297
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 (optional)
ACCEED 1104
EFMC-LR (SHDSL) Ethernet Demarcation Device
4x RJ45 10/100Base-T ports, Carrier Ethernet switch
1x Data Module Slot for X.21, V.35, V.36 (optional)
ACCEED 1404
EFMC-LR (SHDSL) Ethernet Demarcation Device with
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
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)
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
Optical transmission units
BOTU
Fiber Optical Termination Unit for Ethernet and TDM services
4x E1, Ethernet switch (VLAN, CoS)
2x SFP module slots
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 refence clock in/out (optional)
A3118-X652-R67-02 29 / 297
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-X652-R67-02 30 / 297
ULAF+ 3 - Application overview ACCEED 2202 Manual
3
Application overview
This chapter provides an overview of the ACCEED 2202 unit, describes

typical applications and system configurations and gives an introduction
to the ACCEED 2202 architecture. The aim of this chapter is to show the
capabilities of the system and to facilitate network planning.
A3118-X652-R67-02 31 / 297
3.1 ACCEED 2202 overview
3.1.1 Gigabit EFM fiber demarcation, transmission and aggregation unit

ACCEED 2202 supports Carrier Ethernet Services allowing the implementation of a broad variety of
crucial applications on fiber lines.
As Carrier Ethernet Network Interface Device (NID), ACCEED 2202 provides comprehensive service
demarcation.
Figure 3-1 ACCEED 2202 plug in and desktop
ACCEED line card and desktop units allow the implementation of a broad variety of crucial
applications in the promising field of carrier grade Ethernet.
Following the successful ULAF+ product philosophy, the ACCEED EFM family has been designed to
be fully compatible with the installed ULAF+ base preserving customer investment and pave the way
for successful migration to Carrier Ethernet services.
The desktop unit can also be deployed as standalone device connected to an aggregation- or edge
switch.
ACCEED 2202 main features

Ethernet over up to 2 fiber links (bi- or unidirectional transmission)
Resilience auto failover and recovery functions
Flexible mapping of user traffic to Ethernet flows
Carrier grade Ethernet Services with guaranteed bandwidth per flow
Synchronization with SHDSL symbol clock, SyncE and 1588v2
Gigabit Ethernet interfaces
MSA compliant SFP slot
Standard compliant 802.3ah
Standard Ethernet OAM
MEF standards compliant
Simple provisioning by means of predefined configuration files
A3118-X652-R67-02 32 / 297
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.
ACCEED features a managed Gigabit Ethernet switch with up to 3 Ethernet customer ports per unit
supporting E-Line, E-LAN and E-Tree services according to MEF scenarios and per flow bandwidth
profiles according to MEF10.
Network Synchronization
For clock sensitive applications like mobile base station backhaul, synchronization is very important.
ACCEED 2202 offers several methods to provide an accurate clock to every customer location:
Synchronous Ethernet deliver accurate timing over packet based networks
2MHz clock in - and output allow to connect to legacy BITS (Building Integrated Timing Supply)
Automatic selection of the best available clock source, based on SSM (Synchronization Status
Message)
2MHz SyncE conversion and vice versa
Mechanics
The ACCEED 2202 is available as plug in for the ULAF+ Subrack and Compact Shelf or as desktop
unit. ACCEED 2202 fits in any location: central offices, customer premises, street cabinets and many
others.
Management
ACCEED 2202 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. Local access as well as remote
Inband- or dedicated DCN access.
3.1.2 Technical data

Power Supply
Input Voltage
Plug in version 40 to 72 VDC
Desktop version 40 to 72 VDC
95 to 260 VAC
Power Consumption
Desktop unit (without PoE) 12 W
Plug in card (without PoE) 12 W
Interfaces
User Network Interface (UNI/NNI)
2x RJ45 10/100/1000Base-T ports
1x SFP slot for FE/GbE optical or electrical
(1x RJ45 G.703 120/75 Ohm port for E1 or Synchronization)
Management
1x RJ45 serial RS232 Local Craft Terminal (LCT)
1x RJ45 Ethernet 10/100Base-T DCN
Physical and Environment
Plug in version Double Eurocard size
Desktop version (W x H x D) 272 x 47.5 x 175 mm (wall-mounting possible)
Operating Temperature -5 C to +55 C at 5 to 95 % rel. humidity
Safety EN 60950-1 (2011)
EMC/EMF EN 300386 V1.5.1 (2010)
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-X652-R67-02 33 / 297
3.2 Typical ACCEED 2202 applications

ACCEED 2202 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
3.2.1 Business Access
High Speed Business Access Ethernet services as defined by the Metro Ethernet Forum (MEF) are
fully supported by ACCEED 2202 :
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-2 E-LAN service (multipoint to multipoint EVC)
A3118-X652-R67-02 34 / 297
2. E-Line service
Port based
Ethernet private line (EPL)
Ethernet virtual private line (EVPL)
Figure 3-3 E-Line service (point to point EVC)
3. E-Tree service
Port based
Ethernet private Tree (EP-Tree)
Ethernet virtual private Tree (EVP-Tree)
Figure 3-4 E-Tree service (rooted multipoint EVC)
A3118-X652-R67-02 35 / 297
3.2.2 Wholesale Carrier Ethernet Demarcation
ACCEED 2202 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-5 ACCEED 2202 wholesale application
In wholesales applications ACCEED 2202 can be used to provide connectivity to a third party operator
(OLO) over an optical fiber allowing to fully monitor and control the service quality at the NNI interface
using the extensive management and OAM functionalities of ACCEED 2202.
3.2.3 Backhaul
ACCEED 2202 allows implementing reliable backhaul solutions with Gigabit Ethernet speed over
optical fibers with the possibility to protect the optical fiber link with a second fiber connection.
The following picture shows the backhaul of a NodeB via an active and protection link..
Figure 3-6 Mobile Backhaul example
A3118-X652-R67-02 36 / 297
3.3 System configurations

The flexible ACCEED 2202 architecture can be utilized to implement a wide variety of configurations
as shown by the following picture:
Subrack to desktop (point to point with protection option, aggregation)
Desktop to desktop (point to point with protection option as well as aggregation of 2 desktop units)
Direct connection to aggregation network (3rd party edge device)
Figure 3-7 ACCEED 2202 configuration examples
Optical Line
A optical connection between LT and NT over single or dual fiber
EFM Link
A EFM connection between LT and NT over optical fiber
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)
A3118-X652-R67-02 37 / 297
Figure 3-8 Line / Link / Service definition
A3118-X652-R67-02 38 / 297
3.3.1 Mechanics
Both the plug in and the desktop units can be used as LT (or CM = Connection Master) and as NT (or
CS = Connection Slave).
3.3.2 HW options
The following HW options of ACCEED 2202 are available:
Synchronous
Ethernet (P1)
Power over
part number mechanic
Ethernet
S3118-J652-E413 Plug in Ethernet

S3118-J652-E446 Plug in
S3118-H652-E413 Desktop
S3118-H652-E446 Desktop
Table 1 ACCEED 2202 HW options
The following ACCEED 2202 accessories are available:
part number Description

V3708-Z67-X17 SFP 1000 Base-SX optical 850 nm (550 m), multimode - two fibres
V3708-Z67-X27 SFP 1000 Base-LX optical 1310 nm (10 km), singlemode - two fibres
V3708-Z67-X37 SFP 1000 Base-T electrical (100 m)
Table 2 ACCEED 2202 accessories
Refer to [13] for the complete ULAF+ accessory list.
3.3.3 ACCEED 2202 applications

ACCEED 2202 can be used to realize various application. This can be a connection between
ACCEED 2202 units (desktop or plug-in) or an ACCEED 2202 and 3rd party devices.
The following applications can be realized with ACCEED 2202:

Point to Point (PTP)
Protected Point to Point (PPTP)
Point to Multipoint (PTMP)
Standalone (PTP or PPTP) connection to a 3rd party device
ACCEED 2202 can be configured via the front panel DIP-switch to work as Configuration Master
(CM) or Configuration Slave (CS). The CM controls the slave unit and provides the management
access to the CS. In the standalone application the ACCEED 2202 unit must be configured as CM.
A3118-X652-R67-02 39 / 297
For the link OAM configuration please refer to chapter Fehler! Verweisquelle konnte nicht gefunden
werden.
The following figure shows possible configurations:
Figure 3-9 ACCEED 2202 applications
Link Aggregation Group (LAG)

Link aggregation of the 2 SFP ports and the LAN ports (P1 and P2) can be utilized to double the
throughput. Additionally, LAG provides redundancy if one link fails. This is utilized in the PPTP
application.
In case of such a link failure, the traffic transported over the remaining available link. For more
information on LAG please refer to chapter 8.4.2.3
3.3.4 Uplink interface

There are different ways to connect the Ethernet flows of a Subrack to the carrier network in the
central office:
Connect each Ethernet interface to an external device
Use the capabilities of ACCEED to concentrate uplink Ethernet traffic
Use the MCU-S / MCU-CES unit to concentrate uplink Ethernet traffic
Uplink via ACCEED

With the ACCEED 2202 unit the uplink can be realized by utilizing different physical interfaces (P1..P3
or SFP1) or concentrate the entire traffic over a single interface allowing a single uplink connection.
A3118-X652-R67-02 40 / 297
Uplink via MCU-S / MCU-CES

The MCU-S / MCU-CES boards are designed to concentrate Ethernet traffic of the Subrack V3 via the
backplane, eliminating the need for external cabling. The Subrack V3 has an Ethernet star topology in
the backplane providing a 100Mbit/s connection between the central controller unit MCU-S / MCU-
CES and each of the line card slots. The MCU-S / MCU-CES unit and the Subrack V3 are described in
detail in [4].
Figure 3-10 Uplink traffic concentration via MCU-S
The above example shows a Subrack V3 equipped with a MCU-S and three ACCEED 2202 units. The
MCU-S unit concentrates the traffic of the three 100bT Subrack V3 interfaces.
A3118-X652-R67-02 41 / 297
ULAF+ 4 - Quick Start Guide ACCEED 2202 Manual
4
Quick Start Guide
This section gives step by step instructions to quickly set up a typical

EFM link using ACCEED 2202 and LCT+. The aim of this section is to
get quickly to a first running configuration and familiarize with ACCEED
2202. You will also find the links to chapters where you get the detailed
information.
A3118-X652-R67-02 42 / 297
4.1 Introduction
This chapter demonstrates how to set up an EFM link from scratch using ACCEED 2202, with the help
of an exemplary configuration.
The exemplary EFM link consists of 2 ACCCED 2202 desktop units connected via optical fiber.
Figure 4-1 Quick start exemplary configuration
The following material is necessary to set up the exemplary link:

2 x ACCEED 2202 desktop S3118-H652-E446
1 x LCT configuration cable C195-A336-A2
1 x LCT+ CD-ROM P3121-P45-A1
2 x SFP 1000 Base-LX (10 km V3708-Z67-X27
optical 1310 nm), single mode - two fibres
Additionally the following infrastructure is necessary:

1 x Laptop or PC
Optical cable (two fibers)
A3118-X652-R67-02 43 / 297
4.2 HW setup
4.2.1 Central Office Setup
Setup the sub rack according to the ULAF+ Installation Manual ([2]).
Equip the ACCEED 2202 plug in unit in the sub rack, and make sure that the DIP switch is set to the CM
position (connection master)
Securely fit the plug in unit in the sub rack
Connect the sub rack to ground
Connect the sub rack to a power source
Power up the sub rack (the green power LED the ACCEED unit must be ON)
4.2.2 Remote Terminal Setup

Ensure the DIP switch of the desktop unit is set in the CS position (connection slave)
Connect the desktops to a power source (the green power LED of both desktop units must be ON)
ACCEED 2202 needs about 2 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.
4.2.3 Wiring
Connect the wires as indicated by the picture Figure 4-2
By default the all interfaces (P1...P3, SFP, NMS and Sync) 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
A3118-X652-R67-02 44 / 297
4.3 EFM link configuration
4.3.1 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 chapter 5.7.
4.3.2 Remote management configuration

As indicated in chapter 5.8.2 the exemplary set up allows the remote configuration and alarming of the
ACCEED 2202 CS (connection slave) via LCT or NMS port of the ACCEED 2202 plug in (CM).
For a first quick start, it is recommended to use the serial LCT interface.
4.3.3 EFM-Link configuration

The NNI port SFP1 of the ACCEED 2202 is enabled by default.
Ethernet Ports
In order to set up an EFM link at least one UNI port has to be enabled on the CM side and one on the
CS side.
The Ethernet ports P1 is enabled on the ACCEED 2202 units by factory default.
A3118-X652-R67-02 45 / 297
ULAF+ 5 - Installation ACCEED 2202 Manual
5
Installation
This chapter gives detailed information and instructions about ACCEED

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

for a variety of possible system configurations
A3118-X652-R67-02 46 / 297
5.1 General requirements/check list

This chapter describes how to install the ACCEED 2202 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 (chapter 5.7 and 6.2).
ACCEED 2202 is the Gigabit Ethernet First Mile Fibber (EFMF) demarcation, transmission and
aggregation unit of the ULAF+ system for active fiber Carrier Ethernet Access applications. Please
refer to chapter 3.2
ACCEED 2202 is available as plug in for use in 16 + 1 Subracks and in the Compact Shelf as well as
desktop.
A3118-X652-R67-02 47 / 297
Figure 5-1 ACCEED 2202 plug in unit
Figure 5-2 ACCEED 2202 desktop unit
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 chapter 6.2.
A3118-X652-R67-02 48 / 297
5.2 Power supply

Power supply configurations
Table 3 shows the various ACCEED 2202 power supply configurations:
Power configuration Plug in Desktop
Local power supply with 110/230 VAC -
Local power supply with 48/60 VDC

Table 3 power supply modes
5.2.1 Power supply to the plug in unit
Power is supplied to the plug in unit via the Subrack backplane. The input voltage is nominal 48 VDC or
60 VDC (valid range 40 - 72 VDC).
5.2.1.1 Fuses F1-F8; F10; F11

The power supply is protected with fuses. More details are included in Table 4.
Type of fuse Comment
F11: 1AT / 125V Plug in model with PoE
F10: 2AT / 125V
F1-F8: 1. 25AT / 125V
Table 4 Usage of fuse types
The fuses have a protective function and must be replaced by fuses with exactly the same
electrical specifications.
5.2.2 Power supply to the desktop unit

The following options are available for power supply to the desktop unit:
Local power supply with 110 VAC or 230 VAC (valid range 95 260 VAC)
Local power supply with 48 VDC or 60 VDC (valid range 40 72 VDC)
A3118-X652-R67-02 49 / 297
A local power supply terminals

B jumper settings for local feeding (AC or DC)
C jumper settings for remotely fed (only relevant for ACCEED 1416)
D main earth terminal for grounding
E printed circuit board
F desktop case
Figure 5-3 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-X652-R67-02 50 / 297
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+.
A local power supply terminals

B jumper settings for local feeding
C jumper settings for feeding from remote
D main earth terminal for grounding
E printed circuit board
F desktop case
Figure 5-4 AC and DC power supply
5.2.2.2 Change from local power feeding to remote power feeding
Not applicable
5.2.2.3 Set the ACCEED 2202 power supply via jumpers

Not applicable
A3118-X652-R67-02 51 / 297
5.2.2.4 Fuses F10; F11

The power supply is protected with fuses. More details are included in Table 5.
Type of fuse Equipped on
F10: 1AT / 125V Desktop unit with PoE
F11: 2AT / 250V Desktop unit
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-X652-R67-02 52 / 297
5.3 Grounding concept

The sub rack must always be grounded.
ACCEED desktops must be grounded via a cable of at least 0,75mm2, if remotely fed with a voltage
120VDC (only applicable for SHDSL units).
Grounding is done over the main earth terminal

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).
A3118-X652-R67-02 53 / 297
5.4 Interfaces / pinning
1 3 5 7 9
2 4 6 8
Figure 5-5 ACCEED 2202 plug in and desktop front panel interfaces and LEDs
summary LEDs: DIP switches:

power (green) CS (Configuration Master) / CS
1 alarm (red/yellow) 2 (Configuration Slave)
maintenance (yellow) LCT (Plug in only): LCT interface
enable / disable
3 LCT serial RS232 interface 4 2MHz/2Mbit Clock interface
Network Management System Ethernet 10/100/1000bT Ethernet port 1
5 6
interface
7 10/100/1000Base-T Ethernet port 2 8 SFP 1 port
9 SFP 2 port
A3118-X652-R67-02 54 / 297
5.4.1 SHDSL interface
Not applicable
5.4.2 Ethernet interfaces (10Base-T/100Base-Tx/1000Base-Tx)
ACCEED 2202 has 2x RJ45 Ethernet plugs located on the front panel: P1 and P2. Depending on the
HW option only one or both of these front panel interfaces are usable:
Ethernet port 1 Ethernet port 2

Plug in front panel backplane
Desktop front panel front panel
Table 6 ACCEED 2202 Ethernet interfaces
The front connector P2 of Plug In units has no function, because this switch port is used
as backplane port. Through this interface the Ethernet traffic of the Subrack V3 (or the
Compact Shelf) can be aggregated by the MCU-S unit. The backplane interface cannot be
used in the Subrack V2.
The signals of the Ethernet interfaces depend on the interface configuration (10/100Base-T or
1000Base-T). The pinning corresponds to the 802.3ab standard.
Connector Pin assignment 1000Base-T 10/100Base-T PoE option (P1)

1 BI_DA + Tx + PoE +
2 BI_DA - Tx - PoE +
3 BI_DB + Rx + PoE -
4 BI_DC +
5 BI_DC -
6 BI_DB - Rx - PoE -
7 BI_DD +
8 BI_DD -
Casing Ground Ground
Table 7 Pin assignment of the Ethernet interfaces (P1 and P2)
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).
5.4.3 SFP slot interface
A3118-X652-R67-02 55 / 297
ACCEED 2202 is equipped with two MSA compliant SFP slots on the front panel.
There are plenty of possibilities of different Ethernet SFPs that can be used:
- FE and GbE Ethernet are supported
- BiDi and triple rate SFPs are supported
- SFPs with extended data block (Temperature, Rx Power, )
5.4.4 NMS interface (10/100 Base-T)

ACCEED 2202 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
5.4.5 Clock Interface

ACCEED 2202 has two clock interfaces available:
The front panel clock in / out interface
The Subrack clock in interface (backplane)
The following table shows how these interfaces are used depending on the system configuration:
clock in clock out

Plug in Subrack and front panel front panel
Desktop front panel front panel
Table 9 clock in / out interface
A3118-X652-R67-02 56 / 297
Figure 5-6 Subrack clock in interfaces (75 and 120 Ohm)
ACCEED 2202 front panel interface

ACCEED 2202 has one or two RJ45 Clock input/output interface connector located on the front panel
(CLOCK or TDM). A BNC connector is available using an adapter cable BNC-RJ45.
Each 2 MHz or G.704 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 10 Pin assignment of the clock interface
The clock interface can be used as Input and/or Output
The clock interface is available on ACCEED 2202 models with the SyncE option only (see
Table 1).
A3118-X652-R67-02 57 / 297
5.4.6 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 11 Pin assignment of the LCT serial interface
The pins 1, 2, 6, 7 and 8 must not be connected
The serial interface runs at the speed of 115.2 kBaud with 8 data bits, 1 start, 1 stop bit and with
neither parity nor handshake.
A3118-X652-R67-02 58 / 297
5.5 DIP switches

5.5.1 DIP switches of Plug in units
CS/CM Switch
The upper switch (CS/CM) determines the mode of the unit:
right position CM Configuration Master, through this unit it is possible to fully manage the
remote device/devices (default)
left position CS Configuration Slave.
By default the switch is in the right CM position.
LCT Switch
The lower switch (LCT) determines the interface used for local configuration:
right position LCT Local management via LCT over serial interface on front panel
Management access via backplane interface (respectively MCU/OMI
left position
SNMP) (default)
By default the switch is in the left position (Management via MCU/OMI SNMP).
5.5.2 DIP switches of Desktop units
CS/CM Switch
The switch (COT/RT) determines the mode of the unit:
upper position COT Configuration Master, through this unit it is possible to
fully manage the remote device/devices
lower position RT Configuration Slave. (default)
By default the switch is in the CM position.
A3118-X652-R67-02 59 / 297
5.6 Visual indications

ACCEED 2202 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.
1 3 5 7 9
2 4 6 8
Figure 5-7 Visual signaling of the ACCEED 2202
location LED Visual signaling Status

off no power supply
PWR
green on power supply ok
off no alarm or `warning`
Alarm red on `critical` or `major` alarm
yellow on `minor` alarm
1 off Maintenance mode not active
Maintenance function active. See chapter 5.9 for a
yellow on
MAINT detailed list of the maintenance functions.
Firmware (all members of the array) on LT and NT
yellow blinking are not compatible or configuration is not supported
by NT/Array
off external clock signal OK or disabled
on LOS clock in (G.704)
Clock red
4 blink slow Clock not available
blink fast LFA clock in (G.704)
Clock yellow blink slow Clock output squelched
off no connection
NMS green on link up
5 blinking traffic (rx/tx)
off half duplex
NMS yellow
on full duplex
off no connection
ETH P1..3
green on link up
blinking traffic (rx/tx)
6,7
off half duplex
ETH P1..3
yellow on full duplex
blinking collisions
8,9 SFP1 green off no connection
A3118-X652-R67-02 60 / 297
on link up
blinking traffic (rx/tx)
off SFP port disabled
SFP1
yellow/red yellow on full duplex
red on SFP not inserted (interface enabled)
Table 12 ACCEED 2202 visual signaling
1 sec.
on
off
1 sec.
Figure 5-8 ACCEED 2202 slow blinking LED
200 ms
on
off
200 ms
Figure 5-9 ACCEED 2202 fast blinking LED
To get further help in case of installation failures see chapter 12.
A3118-X652-R67-02 61 / 297
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 2202.
ACCEED can also be managed with AccessIntegrator Version 5.0 and higher. Refer to [9]
for information regarding the installation of AccessIntegrator.
5.7.1 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.5
Graphics:
at least 1024x768 resolution
Connectivity:
Serial Interface or USB with external serial to USB converter
10/100BaseT Interface
5.7.2 Installation of the Software

The LCT+ SW is distributed as setup program that guides the user through the installation procedure.
Figure 5-10 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-X652-R67-02 62 / 297
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-11 LCT+ Setup Wizard
2 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).
Figure 5-12 LCT+ components to install
A3118-X652-R67-02 63 / 297
The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. 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)
3 Select which component to install.

Figure 5-13 Destination folder
You can choose where to install the program on your computer.

The following folder is suggested for the installation:
5 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-X652-R67-02 64 / 297
Figure 5-14 Shortcuts
You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
6 Press Ìnstall` to complete the installation or `Cancel` to abort the operation.
Figure 5-15 Completing the LCT+ Setup
A3118-X652-R67-02 65 / 297
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-16 LCT+ Setup Wizard
Figure 5-17 LCT+ previous version detected
A3118-X652-R67-02 66 / 297
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+.
Figure 5-18 LCT+ components to install
The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. 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.

A3118-X652-R67-02 67 / 297
Figure 5-19 Destination folder
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-20 Shortcuts
You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
7 Press Ìnstall` to complete the installation or `Cancel` to abort the operation.
A3118-X652-R67-02 68 / 297
Figure 5-21 Completing the LCT+ Setup
5.7.3 Uninstalling the Software

If necessary the LCT+ SW can be uninstalled manually. To do this look for the uninstall program on
your computer. This can be found in the folder where the LCT+ has been installed (e.g. C:\Program
Files\Albis Technologies\LCT)
Figure 5-22 LCT+ ùninstaller`
To uninstall the software, proceed as follows:
1 Double click on uninstall. The following dialogue will display:
A3118-X652-R67-02 69 / 297
Figure 5-23 Uninstall the LCT+ SW
2 Press `Next >` to continue uninstalling or `cancel` to abort
Figure 5-24 Uninstall options
3 Select uninstall options and press `Next >` to continue (or `cancel` to abort)
A3118-X652-R67-02 70 / 297
Figure 5-25 Uninstall complete
A3118-X652-R67-02 71 / 297
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. Enable the optical interface(s)

2. Configure the remote access (IP address ...) [optional]
3. Configure Power Over Ethernet [optional]
4. Configure the time settings [optional]
5.8.1 LCT+
ACCEED 2202 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.
5.8.2 ACCEED 2202 management access

The following access paths can be used to manage ACCEED 2202:
Serial interface (RS232) on the ACCEED board (plug in and desktop)
Serial interface of the management card OMI SNMP / MCU / MCU-S or MCU-CES (plug in only)
NMS Ethernet interface on the ACCEED board (plug in and desktop)
NMS Ethernet interface of the management card OMI SNMP / MCU / MCU-S or MCU-CES (plug
in only)
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
Information about access via OMI SNMP management card can be found in [1], [3] and [5].
Information about access via MCU / MCU-S / MCU-CES management card can be found in [2], [4]
and [5].
A3118-X652-R67-02 72 / 297
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-26 LCT+ connection via RS232 interface
The serial interface runs at the speed of 115200 Bit/s on MCU, MCU-S, MCU-CES and
ACCEED, at 9600 Bit/s on OMI SNMP. The PC interface is automatically set up. No
manual configuration is necessary.
A3118-X652-R67-02 73 / 297
5.8.2.2 Access via NMS interface
Figure 5-27 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 parameters IP-address and IP-net mask are located in

Board\Local\Management Access\NMS Port:
A3118-X652-R67-02 74 / 297
The Default Gateway parameter is common for the NMS and in-band 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).
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 port is in-band management allowed)
IP Address and IP-Netmask
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-X652-R67-02 75 / 297
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).
5.8.3 SCC connections
Not applicable.
5.8.4 EFM link Setup
Not applicable.
5.8.5 Remote Power Supply
Not applicable.
5.8.6 Power over Ethernet (PoE)
A3118-X652-R67-02 76 / 297
For both ACCEED 2202 plug in and desktop units a HW option supporting power over Ethernet
according to 802.3af is available.
ACCEED 2202 is designed as endpoint PSE (Power Sourcing Equipment) Alternative A, Class 0
The power is available on Ethernet port P1 and provides:
Maximum power 15,4W

Output Voltage 44 to 57VDC
Output Current max 350mA
Figure 5-28 Powering of CE (Customer Equipment) via PoE
To use Power over Ethernet please order an ACCEED 2202 version that supports this
feature.
Power over Ethernet is not available on desktops with 48VDC power supply!
PoE can be activated via LCT+. The configuration is located in

Switch Local\LAN Ports\P1\Power Over Ethernet
Switch EFM-NT\[A]\LAN Ports\P1\Power Over Ethernet
A3118-X652-R67-02 77 / 297
5.8.7 Time settings

A real time clock is available on ACCEED 2202. This can be set automatically via NTP-UNICAST or
can be configured manually.
Time settings are located in Board\Local\Time Settings
In `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
contains the current date and time).
In `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.
A3118-X652-R67-02 78 / 297
5.9 Maintenance functions

ACCEED 2202 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.
5.9.1 Loopback
ACCEED 2202 features the following loopbacks:
5.9.1.1 Loopback 1a
Not applicable.
5.9.1.2 Loopback 3a
Not applicable.
5.9.1.3 Link OAM Loopbacks

Each ACCEED 2202 Ethernet port features a loopback, controlled by the Link OAM of the peer.
Each ACCEED 2202 Ethernet port features a command to remotely set a loopback on the peer
Ethernet interface.
Link OAM loopbacks are described in chapter 9.1
.
5.9.1.4 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 chapter 9.2.9
5.9.1.5 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 respond (LTR) message along the path. The faulty
location can be identified based on the returned LTR messages.
SOAM link trace is described in chapter 9.2.9
5.9.2 BER test
Not applicable.
5.9.3 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 chapter 8.5.4.
A3118-X652-R67-02 79 / 297
5.9.4 Trap suppression

During the execution of maintenance activities it maybe necessary to prevent the network
management system from being flooded by alarm information. ACCEED 2202 therefore offers the
possibility to disable the generation of traps.
Trap suppression is described in chapter 9.1.
A3118-X652-R67-02 80 / 297
ULAF+ 6 - Configuration and operation ACCEED 2202 Manual
6
Configuration and operation
This chapter gives detailed information and instructions about how to

configure and operate ACCEED 2202 and LCT+. It contains a
description of both ACCEED 2202 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 2202 and LCT+.
A3118-X652-R67-02 81 / 297
6.1 Management access

There are different possibilities to access the management plane of the ACCEED device. One is the
local craft terminal (LCT) to support users who like to work with a graphical user interface (GUI) and a
command line interface (CLI) for scripting and automation purposes.
The configuration of the management access is described in the installation chapter. Refer to chapter
5.8.2.
A3118-X652-R67-02 82 / 297
6.2 LCT+
6.2.1 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
6.2.2 Starting the LCT+

Make sure that you have installed the LCT+ in accordance with chapter 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 chapter 5.8.2 for more information about connectivity.
A3118-X652-R67-02 83 / 297
Start the ULAF+ LCT+ either by double clicking the ULAF+ LCT+ shortcut on the desktop or via the
Start menu item ULAF+ LCT+ in StartProgramsAlbis TechnologiesLCT.
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)
TCP interface
If `COM` is selected, The COM Port which is used by LCT+ must be selected.
For a `TCP` connection the IP address of the network element must be entered.
Furthermore one of the following options must be selected:

ÒMI SNMP/MCU/NE`: the LCT+ is directly connected to a ULAF+ devices with IP connectivity
`Portserver`: the LCT+ is connected to a ULAF+ NE with serial interface via portserver. For this
option the port address must be entered.
Optionally a SOCKS5 proxy can be used, if the TCP port 2101 cannot be used by the LCT+, e.g. a
Firewall blocks it. The proxy uses the southbound TCP port 2101 and a northbound TCP port, that can
be defined individually, e.g. 1080. The LCT+ communicates then via this TCP port with the proxy.
The portserver option applies to legacy ULAF+ equipment, without Ethernet connectivity
Click on the `Connect` button.
The Login window appears:
A3118-X652-R67-02 84 / 297
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 password for MCU / MCU-S / MCU-CES / ACCEED:

Administrator: UlafPAdm
Maintenance: UlafPMnt
Default password for OMI SNMP / Desktops (except ACCEED):

Administrator: SAZHigh
Maintenance: SAZLow
A3118-X652-R67-02 85 / 297
6.2.3 The graphical user interface
Figure 6-4 LCT+ GUI
The title bar is described in chapter 6.2.4, the menu bar is described in chapter 6.2.5 and the status
bar is described in chapter 6.2.6.
The LCT+ work area is divided in to the following 4 parts:

the summary area (see chapter 6.2.7)
The summary area is located in the upper left corner of the work area and contains the following
dialogues:
Connection
User Management
Download
SCC FW Sync
the view area (see chapter 6.2.8)
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 tree area (see chapter 6.2.9)
The tree area is located in the lower left corner of the work area and contains the data structure of
the selected unit in a tree format. This area does not contain any configuration, fault or
performance data. These are located in the `table area`.
A3118-X652-R67-02 86 / 297
the table area (see chapter 6.2.10)

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 Loopbacks
Configuration
ACCEED 2202
Summary
Performance
Packet Counters
Error Counters
BER Measurement
Line Parameters
Service Qualification
6.2.4 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
A3118-X652-R67-02 87 / 297
6.2.5 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:
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.
Figure 6-7 File Menu
6.2.5.1.2 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.3 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.
A3118-X652-R67-02 88 / 297
6.2.5.1.4 Save configuration (Ctrl+S)

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-8 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 ().
To save the entire configuration of the network element, select the upper most directory
(e.g. ÀCCEED 2202` and click on the right arrow button ().
A3118-X652-R67-02 89 / 297
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-9 Save window
A3118-X652-R67-02 90 / 297
6.2.5.1.5 Load configuration (Ctrl+L)

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-10 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 left 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-X652-R67-02 91 / 297
Figure 6-11 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 ÒK` button.
6.2.5.1.6 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-12 and contains the following commands:
Preview Mode
Preferences
Figure 6-12 Options Menu
A3118-X652-R67-02 92 / 297
6.2.5.2.1 Preview Mode (Ctrl+P)

This command toggles between Ònline Mode` (display of units physically connected to LCT+) and
`Preview Mode` (display of a generic virtual line model composed of the possible CS being connected
to the CM).
The command is also available via the control sequence (Ctrl+P)
The CS need to be connected to the LCT+ in Preview mode.
Figure 6-13 Preview mode
The Preview mode is useful to configure devices, which are not yet physically available (for instance to
configure the CS, before it is connected to the CM).
To enter the Preview mode the LCT+ must be connected to one CM device. After setting the
connection to `Preview`, the LCT+ makes the virtual line model available.
As depicted in Figure 6-14 the Preview mode (Online / Preview) is displayed:

in the status bar (1)
in the Options menu (2)
in the background of the view area (blue in case of Preview) (3)
A3118-X652-R67-02 93 / 297
Figure 6-14 LCT+ Preview mode
6.2.5.2.2 Reset Window Setting

Restore the original Window proportions of all window sections (factory defaults).
6.2.5.2.3 Preferences (Ctrl+E)
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:
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-15 Connection option
A3118-X652-R67-02 94 / 297
Confirmation
- Clear Alarm Log
- Show prohibited parameters
- MAC Table Flush
Figure 6-16 Confirmation options
Some LCT+ operations result in deleting data without any ùndo` possibility. These operations
therefore generate popup warnings. The command is only executed once the user confirms the
intention to proceed.
Figure 6-17 Alarm log clear warning
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
C:\ \
Figure 6-18 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).
A3118-X652-R67-02 95 / 297
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-19 Trap Log example
- System Log
The System Log is a 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-20 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-X652-R67-02 96 / 297
6.2.5.3 Help Menu

The Help menu contains the Àbout` item
Figure 6-21 Help Menu
The Àbout` item delivers version and copyright information about the LCT+ application
Figure 6-22 LCT+ About Window
6.2.6 Status bar

The LCT+ status bar contains the following information.
Figure 6-23 LCT+ window bottom detail example
1. Progress bar
The progress bar informs about the state of data synchronization between LCT+ and the
connected unit.
Ìdle` 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-24 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 chapter 6.2.5.
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-25 LCT+ preview mode active
A3118-X652-R67-02 97 / 297
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 AccessIntegrator), a mechanism to prevent concurrent write access has been
implemented. If LCT+ doesnt 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).
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 chapter 5.6.
6.2.7 The Summary area
Figure 6-26 LCT+ Areas
The (yellow) summary area is located in the upper left corner of the work area and contains the
following dialogues.
A3118-X652-R67-02 98 / 297
6.2.7.1 Connection
The connection dialogue is described in chapter 6.2.2.
Figure 6-27 Connection dialogue
6.2.7.2 User Management

The user management dialogue permits to change the password of both the Administrator and the
Maintenance access.
The default passwords are defined in chapter 6.2.2.
Figure 6-28 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-X652-R67-02 99 / 297
6.2.7.3 Download
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.
Figure 6-29 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 by
1
clicking the Browse button.
The `dwl` file is checked to ensure that only allowed FW can be downloaded.
A3118-X652-R67-02 100 / 297

Figure 6-30 Open download file
2 Start the download by clicking the `Start` button
Figure 6-31 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-32 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-X652-R67-02 101 / 297

Figure 6-33 Download finished
To activate the new FW, the `Reboot` button must be pressed and the `Swap` checkbox must
3
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 2202 CS device (if the
LCT+ is not directly attached to it, but via a CM device)
The following channels are available to perform a remote download:

Link OAM
The Link OAM is a communication channel between the CM and the CS. The Link OAM channel
has a minimal impact on the payload bit rate (approx. 300kbit/s) during download.
In band
The download of CS unit can be performed via in band management. This 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 device. In band is recommended to upgrade FW during
installation. The in band download procedure is the same as the procedure for local download.
Figure 6-34 Remote download dialogue
The remote download dialogue displays active and passive FW type and version.
A3118-X652-R67-02 102 / 297

The remote download is performed in the following steps:

(1) If needed, transfer the suitable FW from the PC into the passive bank of the local unit
(2) Transfer the suitable FW from the CM active bank to the target device
(3) Reboot with swap
NT remote download
To remotely download a CS unit perform the following steps:
1 Select NT / CS as target device in the download dialogue

2 Select CS A or B (if available) as target unit in the dropdown list for downloading
3 Select the source FW for the download
The following options are available:

local active FW
local passive FW
4 Start the download by clicking the `Start` button
Progress is displayed in the progress bar.
It is possible to manage the device (e.g. change configurations) while performing the FW
download. After starting the download, it runs in the background without any support or
need of the management system.
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.
To activate the new FW, the Reboot button must be pressed and the Swap checkbox must be
5
enabled. This will load the downloaded FW in the active bank.
The service is interrupted during the reboot.
A3118-X652-R67-02 103 / 297

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

The rack view is a representation of the Subrack. It gives indication about the equipped units and
allows starting the element manager application of a unit by double clicking the corresponding front
panel.
The Rack view is only available if connected via a management card, i.e. OMI SNMP,
MCU, MCU-S or MCU-CES.
Figure 6-35 Rack view
A3118-X652-R67-02 104 / 297

The `Rack view` contains the following information:
Sub rack image

This image shows:
the sub rack equipping (empty slots are grey / equipped slots are white)
the name of the equipped unit
the state of the of the plug in units shown by symbolic LED
green: no alarm or warning,
yellow: minor alarm,
red: major or critical alarm
the unit type (MGMT = Management, LT = Line Termination, NT = Network Termination, CM =
Configuration Master or CS =Configuration Slave)
The slot number
The MCU / MCU-S / MCU-CES management units are located in the middle of the rack,
but have the slot number zero.
Rack
The Rack area allows selecting the sub rack to be accessed. This configuration is needed in case of
sub rack cascading and / or extended slot addresses. See the sub rack installation manual [1] and [2]
for more information.
Slot Info
This field provides the following information for the selected slot (blue colored unit):
(HW) part number
active FW-ID and FW Version
passive FW-ID and FW Version
Device Description (Board/Local/Information) or User Data (older plug in units, e.g. BSTU)
6.2.8.2 Ethernet View

The Ethernet view is a representation of the EFM link. It shows a logical representation of the EFM-LT
and (if applicable) the EFM-NT unit. Functional blocks and interfaces of both the LT and NT are
displayed. These are colored depending on corresponding alarms (green: warning, yellow: minor
alarm, orange: major alarm, red: critical alarm).
A3118-X652-R67-02 105 / 297

Figure 6-36 Ethernet view
It is possible to directly jump to the corresponding management area of the tree and table
areas (see chapters 6.2.9 and 6.2.10) by clicking on the corresponding functional block or
interface.
6.2.9 The Tree area
The (green) tree area is located in the lower left corner of the work area and 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 doesnt 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-X652-R67-02 106 / 297

Ethernet
This group contains layer 2 parameters for the local switch and if
applicable for the remote switch (Switch CS). Both contain the
following subgroups:
- LAN, SFP and Backplane (for plug in only) ports defining user
port attributes
- WAN ports 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) interface.
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)
CS (Information, Management Access, Clocking).
Figure 6-37 ACCEED 2202 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-X652-R67-02 107 / 297

6.2.10 The 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.
Figure 6-38 Table tabs
A3118-X652-R67-02 108 / 297

Figure 6-39 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)
Table 1 Table area symbols
A3118-X652-R67-02 109 / 297

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òn 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 2202 tab
enable Port 1
finally click on Àpply`
Figure 6-40 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-X652-R67-02 110 / 297

6.2.10.1 Fault Management

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 Àll Alarms`.
Figure 6-41 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 1000 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-42 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 *.txt file on the PC where the LCT+ is running.
It is possible to configure, the alarms stored in the Alarm Log. See chapter 11.2.2
It is possible to change the severity of the alarms. See chapter 11.2.1

A3118-X652-R67-02 111 / 297
Maintenance
The maintenance table contains the maintenance functions (Loopbacks, ) of the selected
structure group / element. The table contains editable fields (e.g. set loop) and read only
parameters (e.g. loop state).
Figure 6-43 Fault / Maintenance
Maintenance parameters changed in the table are marked in blue (as shown in Figure 6-45). The
number of parameters changed in the table is displayed in the Àpply` button (in brackets).

- Apply: the changes are configured in the network element.
- Cancel: the changes are discarded.
- Refresh: the data in the table is reloaded from the network element. Possible changes which
have not yet been applied are discarded.
A3118-X652-R67-02 112 / 297

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 chapter 9.2.9
Figure 6-44 Fault / SOAM
A3118-X652-R67-02 113 / 297

6.2.10.2 Configuration Management

ACCEED 2202
The ACCEED 2202 configuration table contains all configuration and inventory parameters of
ACCEED 2202. The table contains both editable fields and read only fields.
Figure 6-45 Configuration example ACCEED 2202
Configuration parameters changed in the table are marked in blue (as shown in Figure 6-45). The
number of configuration changed in the table is displayed in the Àpply` button (in brackets).

- Apply: the configuration changes are set in the network element.
- 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-X652-R67-02 114 / 297

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 chapter 6.2.5.1.5. 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.
Every time the Apply button is clicked, the configuration is written to the device and the summary
table is deleted.
Figure 6-46 Configuration / Summary

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

Packet Counters
The following counter group are available with ACCEED 2202

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 chapter 8.9
Utilzation
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 chapter 8.10.7

A3118-X652-R67-02 115 / 297
Service Activation Testing (SAT)
The ACCEED built in Service Activation Testing (SAT) feature allows to evaluate layer 2 key
performance figures for a service that is planned to be implemented.
For more information please refer to chapter 8.10
SOAM
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
For more information please refer to chapter 8.11.2
A3118-X652-R67-02 116 / 297

ULAF+ 7 - EFMC Aggregation ACCEED 2202 Manual
7
EFMC Aggregation
This chapter gives an overview of the EFM capabilities, the configuration

and fault management options.
A3118-X652-R67-02 117 / 297

ULAF+ 7 - EFMC Aggregation ACCEED 2202 Manual
7.1 EFM Link

The EFM chapter is not applicable to ACCEED 2202.
A3118-X652-R67-02 118 / 297

ULAF+ 8 - Ethernet Switch ACCEED 2202 Manual
8
Ethernet Switch
A3118-X652-R67-02 119 / 297

8.1 Introduction
The ACCEED uses a powerful packet processor that fits for access and aggregation applications.
The built in feature highlights are:
Highly flexible VLAN manipulation
Powerful ingress and egress Policy Engines
Low Latency, low Jitter
QoS
Ethernet OAM
Traffic Shaping
Traffic Counting
A3118-X652-R67-02 120 / 297

8.2 ACCEED 2202 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
Link Aggregation (LAG)
Switch control
Aging enable/disable
Aging time configurable
MAC table 16k, self-learning
MAC table readout
Port isolation
VLAN
802.1Q (VLAN)
- 4095 C-VLANs
- Port VID explicit settable
802.1ad (Provider Bridge)
- Provider VID
- Provider Ethertype
- Multiple customer services (different C-VLANs to P-VLANs) on same customer port
TR-101 VLAN manipulations
- Inner/outer swap
- 1:1 translation
- Port-based stacking
- VLAN-based stacking
Classification
Predefined criteria:
- Ingress Port
- Destination MAC-Address
- Source MAC-Address
- Ethertype
- VLAN-ID
- VLAN Priority
- Destination IP-Address
- Source IP-Address
- IP Priority (DSCP)
- IP Datagram Protocol
- TCP/UDP Destination Port
- TCP/UDP Source Port
Flows identified by any criteria in the first 128 bytes of the packet
A3118-X652-R67-02 121 / 297

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 with
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
Transmit queue counters
Per service counters (EVC)
History for all packet counters
OAM
Link OAM (802.3ah)
Service OAM (802.1ag, Y.1731)
A3118-X652-R67-02 122 / 297

8.3 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 trough 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 devise 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).
Service
In addition to the port based configuration settings, each packet flow can be assigned to an ingress
service. The service assignment is done via packet matching rules.
The ingress services can be applied for 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
A3118-X652-R67-02 123 / 297

On the egress path the packets are enqueued in the transmit queues according to the mapping
scheme that has been applied on the ingress path. Shaping of the egress transmit queues are
configured in the port settings.
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.
Service
On the egress path, an egress service can be assigned to the ports applying filtering, metering, VLAN
manipulation and QoS manipulation. The service assignment is done via packet matching rules.
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. The Medium Access Control therefore
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 (Switch, 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.
Tree area View area

Figure 8-2 Local and remote switch view with LCT+
A3118-X652-R67-02 124 / 297

8.4 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 2202 are
greyed out.
Please note that accessible switch ports are P1, P2, P3 and the SFP1 and SFP2 port. The WAN and
BPL (backplane port) are internal switch ports.
Figure 8-4 Overview switch ports ACCEED 2202 CM (plug-in) and CS (desktop) device
8.4.1 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.5
For the global counter settings please refer to chapter 8.10.1
A3118-X652-R67-02 125 / 297

Figure 8-5 Global switch port settings
8.4.1.1 Maximum Frame Size

The maximum frame size that can be processed with ACCEED 2202 is 10240 Bytes.
This setting is applied to all ports of the device.
Maximum Frame Size values in ACCEED 2202: [1522, 2048 or 10240 Bytes]
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.4.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-X652-R67-02 126 / 297

8.4.2 Individual Switch Port Settings

The LAN switch ports offer various individual settings which are explained below.
The SFP and Backplane and 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
A3118-X652-R67-02 127 / 297

The following parameters can be configured:
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
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
Port description with up to 64 characters (where is this description used SNMP ?)
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.
GbE Clocking Mode

Defined the clocking mode resolution for 1000Base-T operation
Auto (Prefere Slave)

Manual (Master)
Manual (Slave)
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.4.2.1)
Ingress Rate Limit [64 1000 100000 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
The LFP target group which will be notified if the link of this port goes down.
The possible LFP target groups are: [none, A, B, C, D, E] ( 8.4.2.2)
A3118-X652-R67-02 128 / 297

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.
8.4.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.
8.4.2.2 Link Failure Propagation

Link Failure Propagation (LFP) is a proactive way to react to a loss situation on LAN, WAN ports or
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.
8.4.2.2
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)
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.
A3118-X652-R67-02 129 / 297

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.
LFP Example:
A3118-X652-R67-02 130 / 297

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.4.2.3 LAG
LAG (Link Aggregation Group) in ACCEED 2202 allows to combine 2 links to increase the throughput
and provide redundancy in case one link fails.
ACCEED 2202 provides LAG on the two SFP interfaces and the electrical ports P1 and P2 on the
desktop.
The LAG is a logical entity and all switch settings are done on the LAG level. The members of the LAG
therefore have no switch port settings. Flow control is the only parameter that can be configured on
the port level of the LAG members.
Packets sent to the LAG are distributed over the 2 ports according to the LAG hash algorithm.
The distribution algorithm is based on the combined L2/L2/L4 packet header information. The
algorithm can not be configured by the user but is defined in the ACCEED system.
LAG is configured by enabling the LAG function on both ends of the link at the same time. The link
OAM of all involved ACCEED 2202 ports in the LAG are automatically enabled and set to
configuration mode.
Note: It can take up to 3 Minutes until the LAG is visible in the LCT+.
The figure below shows a LAG configuration between two ACCEED 2202 desktop units as it is
presented in the LCT+
A3118-X652-R67-02 131 / 297

Figure 8-8 LAG configuration
A3118-X652-R67-02 132 / 297

8.4.3 L2 Control Protocol

The following table shows how ACCEED 2202 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
Discard
tunnel
peer
Types of Ethernet frames / layer 2 control protocols
Multicast frames
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)
IEEE 802.1ag - Ethertype 0x8902
ITU-T Y.1731 - OAM Functions and Mechanisms for Ethernet-based Networks
IEEE 802.1ah Provider Backbone Bridges (MAC-in-MAC)
IEEE 802.1ad Provider Bridges (Q-in-Q, VLAN Stacking) 1
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 2 ACCEED 2202 Layer 2 Control Protocol handling
1
VLAN aware mode
A3118-X652-R67-02 133 / 297
The layer 2 protocol parameters are located in:

Ethernet/Switch Local/xxx Ports/yyy/L2 Control Protocols
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
8.4.3.1 Power over Ethernet (PoE)

ACCEED units can be ordered with the option of Power over Ethernet on LAN port P1. Please refer to
chapter 5.8.6 for more information on the PoE specifications.
Enabling PoE is done on the respective P1 LAN port as shown in the picture below.
The Power over Ethernet (PoE) control panel can be found in:
Ethernet/Switch Local/xxx Ports/P1/Power Over Ethernet
A3118-X652-R67-02 134 / 297

8.5 Switch Control

This chapter describes the switch control features.
The picture below shows the respective stages in the reference model.
Figure 8-9 Building block switch control
8.5.1 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 the VLAN Aware.
For more information on these two switch modes please refer to chapter 8.6.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, for each VLAN ID that is defined, a MAC address table is maintained. The sum
of all MAC addresses in these VLAN related MAC address tables can not exceed the 16k. The
switching is done based on the MAC address and the related VLAN ID. This behavior is also known
Independent VLAN Learning (IVL).
Figure 8-10 ACCEED - VLAN learning modes
The ACCEED 2202 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-X652-R67-02 135 / 297

The `MAC Table` and `MAC Table Flush` buttons are located in the LCT+ dialogue `Switch
Local` and `Switch EFM-NT`
Figure 8-11 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-X652-R67-02 136 / 297

8.5.2 Aging Time

The MAC Table Aging Time defines the how long the learned MAC address is kept in the data base if
this source 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-X652-R67-02 137 / 297

8.5.3 Port isolation

To prevent switching between specified ports, these ports can be isolated from traffic of other ports.
This is done by selecting at each ingress port the allowed / isolated egress ports.
Typical applications are:
WAN Isolation (Rooted-Multipoint EVC)
Multi EPL Mode (LAN1 - WAN1 connection is isolated from LAN2 - WAN2 connection)
The example (Figure 8-12) 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.6.1
Figure 8-12 port isolation
Port isolation can be configured per port in the LCT+ found at Ethernet/Switch Local/xxx
Ports/2202/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.
A3118-X652-R67-02 138 / 297

To separate traffic of different customers using the same switch port, VLANs must be used. Please
refer to chapter 8.6.1
If Link OAM is turned on for a specific port, this port must be enabled in its own port isolation
table.
8.5.4 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-13 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.
Port mirroring can be configured in the LCT+ in the Switch dialogues (local and EFM-NT)
Switch Local/Mirroring
A3118-X652-R67-02 139 / 297

8.6 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-14 Building block VLAN
8.6.1 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.8
8.6.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-X652-R67-02 140 / 297

8.6.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-15 ACCEED 2202 VLAN manipulation scenarios
The VLAN mode can be configured in the LCT+ in the Switch dialogues (local and EFM-NT)
8.6.2 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 rule can be defined 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 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 primary tag.
A3118-X652-R67-02 141 / 297

8.6.3 Global VLAN settings
8.6.3.1 VLAN database

The VLAN database reflects the membership of the physical ports (LAN, WAN) to the defined VLANs
existing in the ACCEED device.
The VLAN database must be defined for each ACCEED device individually.
The existence of the VLAN ID in the database is a prerequisite that the switch can handle packets with
the matching Primary VLAN IDs.
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 loosing the 1.p bits information.
VLAN ID 4095 is reserved according to IEEE 802.1Q and can therefore not be used.
The VLAN Database can be found in: 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).
The entered VLAN ID is automatically associated to the matching primary VLAN ID.
Additionally, a name can be assigned to each VLAN ID. Please note, that this name has only
local relevance.
A3118-X652-R67-02 142 / 297

Additionally to the VLAN ID definition, the "egress tagging mode" for each port and VLAN 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 arriving 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.
The VLAN Database can be found in: 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 part of the VLAN Membership anymore. That means:
1) Packets with the VLAN ID are not distributed to this port anymore
2) Packets arriving from that port with the matching VLAN ID are dropped instantly at the
ingress.
The result of the applied "egress tagging mode" to the possible tagging formats of the packets arriving
on the egress port are explained in the tables on the next pages.
A3118-X652-R67-02 143 / 297

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-16 Egress Tagging Mode: - (Discard)
A3118-X652-R67-02 144 / 297

Egress tagging mode: Untagged

All tags recognized in the received packet are removed (primary and/or secondary tag)
Figure 8-17 Egress Tagging Mode: Untagged
A3118-X652-R67-02 145 / 297

Egress tagging mode: Add Primary Tag

The packet is leaving the switch with the primary tag evaluated on the ingress path.
If the packet contains a primary and/or secondary tag, these tags are preserved.
Figure 8-18 Egress Tagging Mode: Add Primary Tag
A3118-X652-R67-02 146 / 297

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-19 Egress Tagging Mode: Primary Tag Only
A3118-X652-R67-02 147 / 297

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-20 Egress Tagging Mode: Secondary Tag Only
A3118-X652-R67-02 148 / 297

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-21 Egress Tagging Mode: Remove Outer Tag
A3118-X652-R67-02 149 / 297

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-22 Egress Tagging Mode: Inner Primary, Outer Secondary
A3118-X652-R67-02 150 / 297

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-23 Egress Tagging Mode: Inner Secondary, Outer Primary
A3118-X652-R67-02 151 / 297

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-24 VLAN DB example
A3118-X652-R67-02 152 / 297

8.6.3.2 Ingress / Egress Translation Table

The Ingress and Egress Translation Table globally defines 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.6.4)
The example below shows the Ingress Translation Table. The egress translation table can be defined
accordingly.
The Ingress Translation Table can be found in:

Ethernet/Switch Local/VLAN/Ingress Translation Table[]
8.6.3.3 Tag Protocol Identifier List (TPID)

The TPID also known as 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.
The Tag Protocol Identification List can be found in:

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-X652-R67-02 153 / 297

8.6.4 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 to make the primary and secondary tag assignment.
The port based VLAN settings are only applicable if the VLAN aware mode is enabled.
The Port VLAN setting for ingress can be found in:

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 all VLAN IDs defined in the VLAN database can be assigned]
Acceptable Frame Types

Defines the frame types that are accepted on this port. Possible settings are:
[All Frames / Primary Tagged Only / Untagged / Secondary Tagged only]
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.6.3.2)
A3118-X652-R67-02 154 / 297

Enable VLAN Tunneling

With port based VLAN tunneling all frames are treated as untagged and existing VLAN tags
are therefore preserved. Port and flow based VLAN manipulation can be applied if tunneling is
applied.
A3118-X652-R67-02 155 / 297

8.6.5 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.6.2 (VLAN Tag
Naming Convention in ACCEED)
The global TPID list ( 8.6.3.3) defines the values that are offered to define the primary and
secondary TPIDs for this specific port.
The Port TPID list for ingress can be found in:

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
8.6.6 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.
The Port TPID list for egress can be found in:
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
A3118-X652-R67-02 156 / 297

8.7 Ethernet Switch Fault Management

All Ethernet Switch relevant alarms are described in chapter 12.3
A3118-X652-R67-02 157 / 297

8.8 Ethernet Switch QoS handling

The ACCEEDs Packet Processor has a powerful integrated flow metering engine. It is able to police
Ethernet traffic on a per flow basis. Additionally it is possible to shape the egress traffic to a target
bitrate. To understand the whole packet flow process take a detailed look on the Packet
Classification, the Policing with Service Profiles and the Queuing Mechanism.
All ingress flows (streams of Ethernet packets with a set of equal criteria, e.g. VLAN ID or traffic class)
of a MAC port pass through the service profiles attached to it. In case these flows match any criteria
(named matching rules) defined in the service profiles, the corresponding bandwidth metering
mechanism is applied and this flow is policed (Packet colors green, yellow and red are assigned
related to the traffic situation).
Ingress Egress
1 2 3 4 5 6 7 8 9 10
VLAN translation
VLAN translation
Port Service Queuing Service Port

Bridge
MAC
MAC
Scheduler
Shaper
VLAN
Policy
Policy
VLAN
VLAN
VLAN
QoS
QoS
QoS
QoS
Figure 8-25 Packet flow process: Service/Queuing
To get to the first flow metering process you need to define a packet classification rule
and a bandwidth profile. Attach both to a new created Ingress Service and assign this
service to at least one ingress port. If necessary adjust the Queue mechanism at the
egress port.
How is a packet flow processed from QoS point of view?
At the ingress port each arriving packet is analysed separately and gets an individual assignment
of the transmit queue number, the packet color, the CoS and DSCP value. These four parameters can
be modified with the help of Ingress Policing Services. This gives the possibility to pre-define the
importance of different streams. Those streams are then ordered, prioritized and shaped in the
queuing engine. For post-processing it is possible to use Egress Policing Services to assign new
CoS and DSCP values or drop out unqualified flows. At the egress port the remarking of CoS and
DSCP bits is done.
8.8.1 Packet Classification

Packet Classification is also used as Rule within this context. The rule is a list of parameters that
need to be fulfilled. If all selected parameters are within the defined parameter ranges, the rule returns
its result as rule is matching. All selected parameters are used as logical AND operation.
Before describing each parameter here a short summary of the typical Ethernet Packet with stacked
VLANs, with PVA (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-26 Layer2 packet description
A3118-X652-R67-02 158 / 297

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..4095] Identifier of the Virtual LAN
EType [0..0xFFFF] Ethertype defining the enveloped Protocol, e.g. IP (0x0800)
DATA PDU
X/FCS Packet 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-27 Layer3/4 packet description
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
A Rule has an ID, this is it internal number, and optional a name assigned in the description field. If no
rule name is applied, the name Rule ID #<IDnum> is used. The corresponding Service Configuration
uses a dropdown box that shows all available rules. We recommend using rule names, which describe
the matching parameters. E.g. a rule that matches on IEEE802.1p Priority bits with COS value 4 could
be described dot1p=4.
Create a new Rule by navigating to Switch/Policing/Rules and press Add Button in the
Configuration->ACCEED 2202 tab
Now the new rule template is created and ready to be filled with your demands
Flows = series of frames with a common attribute (e.g. VLAN ID, QoS, )
Service = treatment of a flow
A3118-X652-R67-02 159 / 297

8.8.1.1 Configuration Settings: Rule Classification

The rule classification parameter section (Figure 8-28) consists of area : matching criteria selection
and area : the detailed parameter area. By default all criteria in section are disabled and section
is empty. Criteria (e.g. Primary VLAN ID, Primary VLAN Priority) enabled in get their detailed
parameters visible in . Figure 8-28 shows all criterias and parameters visible.
Note: This is an example to show all criteria.
Figure 8-28 Rules: Packet Classification
Rule ID [1..32] Internal unique Rule ID.

Description Alphanumeric Text with 32 characters.
Criteria Enable all relevant matching criteria. These are combined by mathematical 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:01 and Mask=FF:FF:FF:FF:FF:F0
-> MAC-Range= 00:00:00:00:00:01 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=00:FF:FF:FF:FF:FF
-> MAC-Range= 01:00:00:00:00:00 01:FF:FF:FF:FF:FF (match all Multicast)
Ethertype [0x0...0xFFFF]
Match the exact value of the Ethertype (describes the content of the Datagram)
A3118-X652-R67-02 160 / 297
VLAN Tag Presence

Secondary VLAN Tag or Untagged match, if packets are untagged or only with SVz
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) [063]
Match the exact the Diff Serv Code Points (DSCP) within the IP Packet
IP Datagram Protocol [0255]
Match the exact number of the enveloped IP Protocol, e.g. ICMP(1), TCP(6), UDP(17)
TCP-UDP Destination Port [065535]
Match the exact Destination Port number within the IP Packet
TCP-UDP Source Port [065535]
Match the exact Source Port number within the IP Packet
Match All Frames
Match all packets (e.g. if all traffic from one port should be dropped)
A3118-X652-R67-02 161 / 297

8.8.2 Policing
Policing is a mechanism that identifies e.g. the bandwidth of a traffic flows and defines the treatment of
traffic exceeding this bandwidth. To each flow a traffic profile can be attached within the corresponding
service. This traffic profile consists of a guaranteed and a peak bandwidth that can be shared with
other services.
Each packet within this policed stream is taken into account for the calculation of the used bandwidth.
The mechanism results in different colors that are attached to each packet of the stream:
Green = within the guaranteed bandwidth limit (CIR)
Yellow = outside the guaranteed, but within the exceeding bandwidth limit (PIR)
Red = outside the exceeding bandwidth limit
Later on it can be decided to transmit/change/drop/mirror the packets based on their color.
8.8.2.1 Color decision process
There are two different modes of color dependent policing: color aware and color blind. These
modes describe, if the incoming packets already carries information about the color (within the VLAN
tag or the IP/DSCP bits) or not.
The Color Mode can be set in the Bandwith Profile which is assigned to the Ingress Service.
Possible colors are:

- green (should be transmitted and drops prevented)
- yellow (maybe transmitted and drops allowed)
- red (probably dropped)
The color selection is done in 3 steps.

Step 1 sets at the ingress port the initial packet color in the QoS Port Profile. The initial packet color
is assigned in case the trusted criterion is not applicable (e.g. trust DSCP, but no IP packets
are received). If the mode is untrusted or the packets are not within the services, the default
port color is used.
Step 2 does the initial coloring based on the assigned Class of Service Profile attached to the trust
level. There are none, which always lead to the initial color, CoS based, which selects the
color based on .1p and DEI bit decision in the VLAN Tag, DSCP based, which selects the
color based on the DSCP bits within the IP packet and DSCP/CoS based which selects IP
packets with DSCP then VLAN packets with .1p and DEI. Untagged non-IP packets are done
with the initial color.
Step 3 is final coloring based on MEF 10 traffic parameters. To cover traffic burst with lowest latency,
tokens are filled in buckets (green & yellow) with different token rates (CIR & PIR). The tokens
within the bucket represent the maximum packet burst that can be covered at this specific
time. Each packet passing by the buckets needs to take out a token. If no token is available,
the packet replaces its color with yellow or red according to the color mechanism. Please
find the description and examples in Chapter 8.8.2.2 and 8.8.2.3.
Based on this color result you decide in the service policy command how to treat the packets (e.g.
transmit in a different queue or drop packets)
Initial colored green packets take green tokens. If not available yellow and then red
tokens. Initial colored yellow packets take only yellow tokens, red if no yellowed are
available.
In color blind mode Step 1 and Step 2 are skipped. Each packet is assumed to have the initial color
green
A3118-X652-R67-02 162 / 297

8.8.2.2 Color decision: (ingress) color blind
Single Rate, 3 Colors: (RFC 2697)

This mechanism is used to assign colors to packets allocated by
bandwidth. Tokens are filled in the bucket with the rate of the
guaranteed bandwidth (CIR) and, as long as no packets are
received, build up the green buffer until the CBS Threshold, then
the yellow buffer until the maximum of CBS+EBS is reached.
Each packet received 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 receive packet color gets red.
Figure 8-29 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 yellows. If no tokens are in the bucket
anymore, the color of the packet gets red.
Two Rates, 3 Colors: (RFC 2698)

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-30 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-X652-R67-02 163 / 297
8.8.2.3 Color decision: (ingress) color aware
Single Rate, 3 Colors: (RFC 2697)

This mechanism works like this: 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-31 color aware: Single Rate, Three colors
This example demonstrates that a burst with initial 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 initial colored packets (3 and 6)
Two Rates, 3 Colors: (RFC 2698)

This mechanism work like the following: 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-32 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 5th and 6th packet
cannot get any yellow tokens therefore they replace their color with red.
A3118-X652-R67-02 164 / 297

8.8.2.4 Configuration Settings: Bandwidth Profile

Each identified stream (8.8.1) can be attached to a Bandwidth Profile (according to MEF10). These
Bandwidth Profiles can be attached to a port or an EVC as ingress or egress service. Each Bandwidth
Profile can be assigned multiple times to different services.
The Bandwidth Profiles are located in: Switch/Policing/Bandwidth Profiles
Figure 8-33 Bandwidth Profile
Bandwidth Profile ID [116] Internal unique Profile ID starting from 1.

Color Mode
Color blind: color decision is done according to chapter 8.8.2.2
Color aware: initial color information is transported within the packets ( 8.8.2.3)
Metering Mode
Single Rate, Three Colors: one guaranteed bit rate (CIR) with a covered burst (CBS) colored in
green and an exceeding burst (EBS) colored in yellow
Two Rates, Three Colors: two separate bit rates, one for guaranteed (CIR) and one for
maximum (PIR) bit rate. Burst sizes are divert, too (CBS and PBS)
CIR [0 10000 1000000 kbit/s, step: 1]

Committed Information Rate. This parameter defines a guaranteed bandwidth
CBS [0 10000 500000 Bytes, step: 1]
Maximum Burst Buffer Size for the guaranteed bandwidth (green packets)
EBS [0 10000 500000 Bytes, step: 1]
Maximum Excess Burst Buffer Size for the exceeding burst matching guaranteed bandwidth
(yellow packets)
PIR [0 10000 1000000 kbit/s, step: 1]
Peak Information Rate. This parameter defines the total bandwidth of this service. It always
includes the CIR. Excess information rate is EIR = PIR - CIR
PBS [0 10000 500000 Bytes, step: 1]
Maximum Peak Burst Buffer Size for bursts matching the total bandwidth (green and yellow). CBS
is a subset of PBS.
A3118-X652-R67-02 165 / 297

8.8.2.5 Configuration Settings: Ingress Service

An ingress service consists of up to 4x rules to identify flows, 1x bandwidth profile and the packet
commands that are executed based on the color decision or the flow identification. E.g. drop red
packets, redirect a packet back to its origin with an additional swap of the Source and Destination
MAC address Services can be assigned to Ethernet ports or EVCs.
Figure 8-34 Ingress Service
Ingress Service ID [1..16] Internal unique ingress service ID

Description Alphanumeric text with 32 characters.
Frame Command
Forward: All packets matching one of the Rules will be forwarded via the bridge
Drop: All packets matching one of the Rules will be dropped
Redirect: All packets matching one of the Rules will be moved to redirect port
Redirect with MAC swap: All packets matching one of the Rules will be redirected to redirect
port and their source and destination MAC will be swapped
Redirect Port defines destination port to redirect packets
Mirror to Analyzer Port A copy of each packet of this ingress service will be additionally sent
to global ingress mirroring analyzer port Switch/Mirroring
Service QoS Profile Service profile ID #1#16 defining queue assignment, CoS & DSCP
value and packet color Switch/QoS/Ingress/Service Profiles
If None is selected, the queue assignment and the initial packet color
is used from the ingress port <port>/QoS/Ingress/Port Profile
Remark CoS
No: do nothing
Yes: remark the priority bits (.1p) of the primary VLAN tag with the assigned
CoS value of service QoS profile
Switch/QoS/Ingress/Service Profiles
Keep Port Remark Decision: CoS remark decision has higher priority than the ingress service
A3118-X652-R67-02 166 / 297

<port>/QoS/Ingress/Port Profile
Remark DSCP
No: do nothing
Yes: remark the DSCP bits of the IP Header with the Assigned DSCP Value of Service QoS
Profile Switch/QoS/Ingress/Service Profiles
Keep Port Remark Decision: DSCP remark decision has higher priority than the Ingress Service
Bandwidth Profile Name of the bandwidth profile (Color Mode, Metering Mode, CIR, CBS,
PIR, PBS) used for the matching packets of this Ingress Service.
Switch/Policing/Bandwidth Profiles
Dedicated Bandwidth Profile
An instance of the selected bandwidth profile is created and attached to this service. This
bandwidth profile runs independently of other services
Share bandwidth profile with all Services that refer the same Bandwidth Profile ID
Yellow Frames Command
Transmit unchanged: no change to the packet transmission process
Drop: Discard all packets that are marked yellow
Assign Yellow Frames QoS Profile: Queue assignment, CoS / DSCP value
Switch/QoS/Ingress/Metering Yellow Frames Profiles
Yellow Frames QoS Profile Yellow Frames Profile ID #1#16 defining Queue Assignment,
CoS & DSCP value
Switch/QoS/Ingress/ Metering Yellow Frames Profiles
Red Frames Command
Transmit unchanged: transmit anyway
Drop: Discard all packets that are marked red
Assign Red Frames QoS Profile: Queue assignment, CoS / DSCP value
Switch/QoS/Ingress/Metering Red Frames Profiles
Remark CoS Yellow Red
No: do nothing
Yes: remark the priority bits (.1p) of the primary VLAN tag with the
assigned CoS value of metering Yellow Frame Profile
Keep Port Remark Decision: CoS remark decision has higher priority than the ingress service
Remark DSCP Yellow Red
No: do nothing
Yes: remark the DSCP bits of the IP packets with the assigned CoS value
of metering Yellow Frame Profile
Keep Port Remark Decision: DSCP remark decision of the ingress port has higher priority than
the ingress service
VLAN Command All matching packets of this ingress service will have
Force Primary VLAN ID: VLAN ID of the primary tag remarked by value of primary VLAN ID
Enable VLAN Tunneling: added outer tag with VLAN ID of primary VLAN ID
Primary VLAN ID [14094] Value of the primary VLAN ID tag for force and tunneling rules
Rule #1 #4 Select up to 4 ingress matching rules from rules pool. Rule #1 has the highest
priority. The first match leads to the execution of this Ingress Service
A3118-X652-R67-02 167 / 297

8.8.2.6 Configuration Settings: Port Ingress Service Assignment
Figure 8-35 Ingress Port Service Assignment
Service #1 #8 Assigns up to 8 ingress services to the physical port. Each ingress packet on
that port will run through the assigned services till it gets a match. The
corresponding service is then executed and all following services are skipped
for this ingress packet.
8.8.2.7 Configuration Settings: Egress Service
Figure 8-36 Egress Service
A3118-X652-R67-02 168 / 297

Egress Service ID [1..16] Internal unique Egress Service ID

Frame Command
Forward: All packets matching one of the Rules will be forwarded via the Bridge
Drop: All packets matching one of the Rules will be dropped
Remark CoS of Outer Tag

No: do nothing
Yes: remark the priority bits (.1p) of the outer VLAN Tag with the Remarked CoS Value
Remarked CoS Value [0..7] .1p bits of the outer tag
Remark DSCP
No: do nothing
Yes: remark the DSCP bits of the IP Header with the Remarked DSCP Value
Remarked DSCP Value [0..63] DSCP bits of the egress IP packet
Bandwidth Profile Name of the bandwidth profile (Color Mode, Metering Mode, CIR, CBS,
PIR, PBS) used for the matching packets of this Ingress Service.
Switch/Policing/Bandwidth Profiles
Dedicated Bandwidth Profile
An instance of the selected Bandwidth Profile is created and attached to this Service. This
bandwidth profile runs independently of other services
Share bandwidth profile with all Services that refer the same Bandwidth Profile ID
Yellow Frames Command Assign Yellow Frames QoS Profile: CoS and DSCP Value
Switch/QoS/Egress/Metering Yellow Frames Profiles
Red Frames Command Drop
Remark CoS Yellow
No: do nothing
Yes: remark the priority bits (.1p) of the outer VLAN Tag with the Remarked CoS Value
Remark DSCP Yellow
No: do nothing
Yes: remark the DSCP bits of the IP Header with the Remarked DSCP Value
VLAN Command All matching packets of this ingress service will have
Force Outer VLAN ID: VLAN ID of the outer tag remarked by the value of Outer VLAN ID
Outer VLAN ID [14094] Value of the Outer VLAN ID tag for Force and Tunneling rules
Rule #1 #4 Select up to 4 ingress matching rules from rules pool. Rule #1 has the highest
priority. The first match leads to the execution of this Ingress Service
A3118-X652-R67-02 169 / 297

8.8.2.8 Configuration Settings: Port Egress Service Assignment
Figure 8-37 Egress Port Service Assignment
Service #1 #4 Assigns up to 4 egress services to this physical port. Each egress packet on
that port will run through the assigned services till it gets a match. The
corresponding service is then executed and all following services are skipped
for this egress packet.
8.8.3 Queuing
There are many traffic situations in modern Ethernet networks which lead to overload conditions of the
traffic interfaces. In situations where traffic drops should be prevented to get a high throughput
(TCP/IP) large packet buffers are a good solution. In case of low latency traffic (e.g. VoIP, Video)
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 for
the customer demand.
The packet processor of the ACCEED 2202 has an integrated a flexible queuing engine. Compared to
standard switches you can combine strict priority and weighted fairness on the same port and the
scheduling distribution amongst the queues is done on bandwidth ratio and not on inaccurate packet
ratio.
Before packet streams are stored in the queues they need to be assigned to the selected queue. This
can be done through Class of Service profiles (802.1p prio bits + DEI bit and/or DiffServ Code Points
DSCP within the IP) or within policing services.
The egress interface is a constant data rate sink limited through the physically (UNI) 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 link 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)
- 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 with the following manner:
1) strict priority
As long as there are packets in this queue and no packets in a higher queue are processed,
this queue will send its packets until the queue is empty.
A3118-X652-R67-02 170 / 297

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-X652-R67-02 171 / 297

8.8.3.1 Configuration Settings: Trust mode / QoS

Each packet uses internally a set of four Quality of Service (QoS) parameters (Queue number, CoS
value, DSCP value and packet color) to process the egress transmit mechanism.
Figure 8-38 Trust mode, port CoS and port remark defaults
Trust Mode select the profile parameter set for QoS for this ingress port
Untrusted: use Port Profile parameter set
Trust CoS Values only: use the CoS Profiles
Switch/QoS/Ingress/CoS Profiles
Trust DSCP Values only: use the DSCP Profiles
Switch/QoS/Ingress/DSCP Profiles
Trust DSCP/CoS Values: use the DSCP Profiles for IP Packets, then the CoS Profiles for
tagged packets
Switch/QoS/Ingress/DSCP Profiles
Switch/QoS/Ingress/CoS Profiles
Trusted VLAN Tag CoS and DEI value for the CoS Service Profile selection is taken from
Primary VLAN Tag:
Secondary VLAN Tag:
Remark CoS
No: do nothing
Yes: remark the priority bits (.1p) of the primary VLAN Tag with the value of the profile
Remark DSCP
No: do nothing
Yes: remark the DSCP bits of the IP Header with the value of the profile
Default CoS CoS value for untagged packets
8.8.3.2 Configuration Settings: QoS Assignment with the port profile (Untrusted
Mode)
Figure 8-39 QoS port profile

Any ingress packet received on this port and trust mode is untrusted gets the following attribute set:
A3118-X652-R67-02 172 / 297

Assigned Queue assign transmit queue number for any egress ports
Assigned CoS Value set CoS value for remarking or rule matching
Assigned DSCP Value set DSCP value for remarking or rule matching
Assigned Initial Color set initial ingress packet color
8.8.3.3 Configuration Settings: QoS Assignment with CoS profiles (Trust CoS Values
only)
Figure 8-40 Ingress CoS profiles
Each ingress packet that is tagged has a CoS value and a DEI bit. All 16 possibilities are covered with
this profile list. According to CoS and DEI bit of the primary tag the following attributes are set:
Assigned Queue assign transmit queue number for the egress ports
Assigned Initial Color set initial ingress packet color (typically DEI=0 green, DEI=1 yellow)
A3118-X652-R67-02 173 / 297

8.8.3.3.1 Configuration Settings: QoS Assignment with DSCP profiles (Trust DSCP
Values only)
Figure 8-41 Ingress DSCP profiles
Each ingress packet that is an IP packet has a DSCP value. All 64 possibilities are covered with this
profile list. According to the six DSCP bit of the IP header the following attributes are set:
Assigned Initial Color set initial ingress packet color (typically all green)
A3118-X652-R67-02 174 / 297

8.8.3.4 Configuration Settings: QoS Assignment with Service profiles
Figure 8-42 Ingress service profiles
Each packet that matches an ingress service and is within the policing range of green (CIR/CBS) may
override the existing QoS set. There are 16 individually defined Service Profiles attribute sets
available. Each of them with the QoS set:
Assigned CoS Value set CoS value for remarking
Assigned DSCP Value set DSCP value for remarking
Assigned Color set packet color (typically green)
8.8.3.5 Configuration Settings: QoS Assignment with Yellow Frames profiles

In this section up to 16 individual QoS profiles are defined for yellow packets. A yellow packet profile
can be attached to ingress and egress services.
Figure 8-43 Ingress yellow frame profiles

Each packet that matches an ingress service and is within the policing range of yellow (EBS or
PIR/PBS) may override the existing QoS set. There are 16 individually defined Yellow Frame Profiles
attribute sets available. Each of them with the QoS set:
Assigned CoS Value set CoS value for remarking
Assigned DSCP Value set DSCP value for remarking
Assigned Color packet color is set to yellow (read only)
A3118-X652-R67-02 175 / 297
8.8.3.6 Configuration Settings: Queue Profile Configuration
Figure 8-44 Egress queue parameter profile
The following parameters are available for Queue Profile 1 ... 4:

Queue #0 #7 number of the modified queue
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.8.3.7 Configuration Settings: port queue profile assignment & DEI bit Remark at
Egress
This section defines the queue profile that should be attached to this physical port. Additionally the
Drop Eligibility Indicator located in the VLAN tag of the primary tag maybe remarked. If remark is
enabled, the DEI bit carries then the color information based on the policing process: 0 = green, 1 =
yellow.
Figure 8-45 Egress queue profile and DEI remark
Transmit Queue Profile Assigns one of the 4x predefined queue profiles to the egress port for
the parameter selection queue number, buffer size, threshold and
scheduling
Remark DEI Bit Remarks Drop Eligibility Indicator with packet color (green=0, yellow=1).
This indicator transports the packet color information from this network
instance to another one. The DEI bit is located in the primary VLAN tag
(Figure 8-26)
A3118-X652-R67-02 176 / 297

8.8.3.8 Configuration Settings: Queue Configuration
Figure 8-46 Egress queue parameters
The following parameters are available:

Shaping Enable
Each queue may have an independent rate shaper
Shaping Rate WAN Ports [ 100 5000 100000 kbit/s, step: 1]
Px, SFP1, BPL [1667 5000 1000000 kbit/s, step: 1667]
Shaping rate per queue
Shaping Burst Size [8 16 128 kByte, step: 8]
Maximum burst size that can be used to shape the traffic
Calculate the maximum shaping delay with the selected parameters:
MaximumShapingDelay[ms]
ShapingBurstSize[kByte]
8 10 3
ShapingRate[kbit / s ]
8.8.3.9 Configuration Settings: Port Egress Rate Shaping
Figure 8-47 Egress port shaping
Enable enables/disables the egress shaper for this port

Shaping Rate WAN Ports [ 100 5000 100000 kbit/s, step: 1]
all others [1667 5000 1000000 kbit/s, step: 1667]
Target bit rate of the egress port
Shaping Burst Size [8 16 128 kByte, step: 8]
Maximum burst size that can be used to shape the traffic
A3118-X652-R67-02 177 / 297

8.9 EVC Concept
A3118-X652-R67-02 178 / 297

8.10 Statistics and Utilization

8.10.1 Introduction
Statistics provide information on sent/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 histories..
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-48 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-X652-R67-02 179 / 297

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.4.1 for more information.
To define the global counter settings proceed as follow:

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-X652-R67-02 180 / 297

To activate the statistics proceed as follow:

In the tree area, go to Ethernet/Switch Local/xy Ports/yz/Statistics/Continuous
To add historic statistics proceed as follow:

In the tree area, go to Ethernet/Switch Local/xy Ports/yz/Statistics/Historic[]
Interval Duartion: [30 .. 900 .. 3600] seconds

Number of Infervals: [1 .. 32]
Each historic statistics can be activated individually.
A3118-X652-R67-02 181 / 297

8.10.2 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 LT and NT (LAN-Ports
and WAN Ports). 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 directed
etherStatsMulticastPkts 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
etherStatsJabbers 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 had a length
(excluding framing bits, but including FCS octets) between 64
etherStatsCRCAlignErrors and 1518 octets, but 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
A3118-X652-R67-02 182 / 297

(Alignment Error).
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) received
etherStatsPkts64Octets that were 64 octets in length (excluding framing bits but
including FCS octets).
etherStatsPkts65to127Octets that were between 65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets).
etherStatsPkts1024to1518Octets* that were between 1024 and 1518* octets in length inclusive
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-X652-R67-02 183 / 297

To access the port packet counters proceed as follow:

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
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 its appropriate overflow counter. The overflow counters are incremented each
time the corresponding counter wraps around (which is after 232 = 4294967296 packets or
octets).
8.10.3 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-X652-R67-02 184 / 297

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
The figure below shows the continuous egress statistics for Policy 1 of the port WAN1. The
global egress metering counters are set to Bytes.
8.10.4 QoS Tx Queue statistics
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-X652-R67-02 185 / 297

8.10.5 Port based metering statistics

Port based metering is applied with a bandwidth profile in ingress and egress direction.
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.
Bytes are counted accordingly.
The figure below shows the continuous ingress bandwidth profile statistics of the port WAN1.
The global ingress metering counters are set to Bytes.
A3118-X652-R67-02 186 / 297

8.10.6 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.9 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.
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
Bytes are counted accordingly.
A3118-X652-R67-02 187 / 297

8.10.7 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.9
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:

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-X652-R67-02 188 / 297

Ok opens the Realtime Diagram window and starts displaying the selected data (see below)
Cancel closes this windows and returns back to the main utilization window
Clear deselect all selected data
A3118-X652-R67-02 189 / 297

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 windows and changes can be made (select/deselect
data). 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.
Maximal 10 graphs can be displayed concurrently in the bitrate and utilization diagram. The
graphs are updated every 4 seconds.
A3118-X652-R67-02 190 / 297

ULAF+ 9 - Operation and Maintenance ACCEED 2202 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-X652-R67-02 191 / 297

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 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 Fault Management

Alarms:
All Link OAM relevant alarms are described in chapter 12.3
Loopbacks:
Each OAM entity:

- features a local loop-back, controlled by the peer OAM entity via Link OAM
- allows to activate a remote loop-back (i.e. a loop-back on the peer OAM entity) via Link OAM,
if the local entity is configured in active mode (see below)
- displays the state of the peer OAM entity loop-back state
The Link OAM loop-backs control panel can be found in:

Ethernet\Switch Local\xxx Ports\Py\Link OAM
A3118-X652-R67-02 192 / 297

9.1.1 Link OAM Configuration
The Link OAM parameters can be found in: Ethernet\Switch Local\xxx Ports\Py\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 also.
An entity in the active mode detects automatically if the remote entity supports OAM. It discovers also
which specific capabilities are supported.
The management communication between ACCEED 2202 CM and CS is realized trough the link OAM
channel.
ACCEED 2202 therefore has a proprietary Link OAM mode named Configuration Mode. This mode
must be set in every CM CS configuration to allow management communication. The management
communication is required to e.g. see the CS via LCT+ or to perform a FW download.
Capabilities
If the Remote Loopback capability is enabled, the remote peer can initiate a loopback on that port.
The ACCEED OUI (Organizationally Unique Identifier) field corresponds to 00-1A-D0
A3118-X652-R67-02 193 / 297

9.2 Service OAM

9.2.8 Service OAM Domains and Maintenance Points
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
Service OAM
Services
(Y.1731, 802.1ag)
Bridged Network OAM / Connectivity Layer

Network
(802.1ag, Y.1731)
Ethernet Link MPLS SDH/SONET Other

Transport
OAM (802.3ah) OAM OAM OAM
Figure 9-1: Ethernet OAM Layers
The Link OAM is described in chapter 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).
Figure 9-2 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.
MEP: MEG End Point [ITU-T] or Maintenance association End Point [IEEE]
MIP: MEG Intermediate Point [ITU-T] or Maintenance domain Intermediate Point [IEEE]
A3118-X652-R67-02 194 / 297

9.2.8.1 Service OAM Maintenance Entity Group
Figure 9-3 Service OAM example
The example in Figure 9-3 shows a network with 3 endpoints and the 3 possible endpoint-to-endpoint
connections.
In the general case of n MEPs there exist n x (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.8.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 are larger (or at least equal) than those on the lower levels.
MEGs / MDs on the same level must not intersect.
The example in Figure 9-4 illustrates how the level can be used to differentiate the maintenance level:
Customer level
Service provider level
Operator level
Ethernet link level
A3118-X652-R67-02 195 / 297

Customer Customer
Operator A Operator B
Equipment Equipment
Provider domain
Customer OAM Level
Provider OAM Level
Operator OAM Level Operator OAM Level
Link OAM
Figure 9-4 Service OAM maintenance levels
9.2.8.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 illustrated the MEP orientation option.
Figure 9-5 Service OAM MEP orientation

A3118-X652-R67-02 196 / 297
9.2.8.4 ACCEED Service OAM implementation

The Service OAM implementation in ACCEED is divided in 3 main parts which is reflected in the tree
view of the LCT+ GUI. This chapter gives a short overview of the Service OAM implementation in
ACCEED. The detailed explanation can be found in the following chapters starting with 9.2.8.5
1) Domains
In this section the domain configurations are set up. This includes the definition of the maintenance
points (MEP or MIP) and the assigned client maintenance points (CMP).
Additionally, the fault management functions can be configured and performed. This includes CCM,
AIS, LCK and also loopback and linktrace.
2) Delay Measurement
The delay measurement section consists of the frame delay measurement (FD) and the inter frame
delay variation (IFDV) measurement.
To set up a delay measurement a respective session is configured on the local unit and the
corresponding responder on the remote device. Thresholds for each session can be defined to raise
an alarm, when the defined criterias are met. The results can be stored in up to 32 user definable
intervals and can be displayed in a table.
3) Loss Measurement
The loss measurement section consists of the frame loss ratio (FLR) measurement and the Availability
measurement.
Single- or dual ended loss measurement sessions can be set up.
Single ended loss measurement sessions are based on the exchange of LMM (Loss Measurement
Message) sent out by the initiating session and LMR (Loss Measurement Reply) sent by the
responder.
Dual ended loss measurement sessions are based on CCMs (Continuity Check Message) messages.
Two corresponding sessions are therefore set up.
To set up a loss measurement, a respective session is configured on the local unit and the
corresponding responder on the remote device.
Single-Ended with LMM/LMRs session and corresponding responder,
Dual-Ended with CCMs two corresponding sessions, no responders
Thresholds for each session can be defined to raise an alarm when the defined criteria are met. The
results can be stored in up to 32 user definable intervals and can be displayed in a table.
A3118-X652-R67-02 197 / 297

9.2.8.5 Service OAM Domain Configuration

ACCEED 2202 provides 5 SOAM domains. 9.2.8.5
The domain configuration is located in Ethernet\Switch Local\SOAM and the

Ethernet\Switch EFM-NT or Ethernet\Switch CS.
MEGs / MDs can be associated with one or more VLANs

Messages are received from all associated VLANs
Messages are sent only in one dedicated VLAN (Source Associated VLAN)
Domain parameters:
Maintenance Domain Name Format:
[No Maintenance Domain Name Present, Character String]
If the format is set to NO, then only the Short MA Name can be configured with up to 45
characters.
If the format is set to Character String, then the Maintenance Domain Name can be set with up
to 43 characters. Additionally the Short MA Name can be set but the field length of 43 is reduced
by the length of the configured Maintenance Domain Name.
Short MA Name Format: [Character String, ICC based Format]
The Maintenance Domain Name Length is automatically determined. (read only value)
Short MA Name [SOAM Domain x, max. length is 45 characters]
Maintenance Domain Name: [Maintenance Domain x, max. length is 43 characters]
Only available, if the maintenance domain name format is set to Character String
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-4)
Source Associated VLAN [none, any VLAN ID listed in the associated VLAN[] folder
VLAN ID among the list of associated VLANS on which all Service OAM PDUs (except the LMM
and DMM PDUs) are generated by Maintenance Points (MP) are to be transmitted. This VLAN
corresponds to the Primary VLAN ID as defined in IEEE 802.1ag.
A3118-X652-R67-02 198 / 297
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 (the inner of the switch).
The MEP orientation doesnt affect Maintenance Intermediate Points (MIPs) as they do not have
any orientation. Please refer to 9.2.8.3 for more additional explanation on MEP orientation.
Continuity Check Messages [enabled / disabled]
This parameter enables the sending of continuity check messages (CCM) in this domain.
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
CCM Interval [100ms, 1s, 10s. 1min, 10min]
This parameter determines the interval between continuity check messages
RDI [enabled / disabled]
This parameter enables the sending of Remote Defect Indications (RDI) in the continuity check
messages (CCM). A MEP detects the LOC (Loss of Continuity) fault condition in receive direction
and sets the RDI flag in the CCM messages in transmit direction if RDI is enabled
Associated VLAN [ ]
Before a Source Associated VLAN can be assigned to the maintenance domain, the respective
VLAN need to be defined in the Associated VLAN table.
VLAN double-tagging (tunnel VLAN tag and domain associated source VLAN tag) is supported for
the frames of the following SOAM protocols:
- Ethernet Continuity Check (CCM)
- Ethernet Loopback (LBM, LBR)
- Ethernet Linktrace (LTM, LTR)
- Ethernet Alarm Indication Signal (AIS)
- Ethernet Locked Signal (LCK)
- Ethernet Loss Measurement (LMM, LMR)
The SOAM VLAN double-tagging is only supported under certain constraints for Ethernet Delay
Measurement (DMM, DMR).
The following scenarios are supported:
- Adding and removing a tunnel VLAN tag to a delay frame between the initiating and
responding MEP.
- Starting and terminating a tunnel in the device processing the delay frames, but the
ingress/egress port is not a tunnel port
The tunnel VLAN tag has to be the outer and the primary VLAN tag.
For each of the 5 Service OAM Domains, VLANs can be associated.

Associated VLANs can be added by clicking the Add button of the Associated_VLAN[] list.
(NOTE: the VLAN ID must exist on the ACCEED VLAN database)
Associated VLANs can be removed by clicking the Remove or the Remove All button.
A3118-X652-R67-02 199 / 297


Description
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 also 8.6.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 also 8.6.3.1]
Tunnel Ports [P1, P2, P3, SFP1, WAN1]
Indicates at which ports the tunnel starts and terminates
If tunnelling is applied, make sure the to configure the following parameters accordingly:
- Ingress policies
- VLAN egress tagging commands in the VLAN DB
- Ingress/Egress TPIDs of the tunnel port
A3118-X652-R67-02 200 / 297

9.2.8.6 Service OAM Maintenance Point configuration

Every domain configured on the ACCEED unit supports up to 5 maintenance points (MP) configured
as MEP or one MP configured as MIP.
Enabled [enabled / disabled]

Enables the Maintenance point
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 [P1 / P2 / P3 / WAN1 / WAN2 / WAN3 / WAN4 / BPL1 / SFP1]
Port on which the maintenance point should reside
MEP ID [1... 8191]
Unique number which identifies the MEP in this Maintenance Domain
CCM Database parameters:

CCM Database parameters are relevant for MEP only (these parameters do not exist for MIPs).
For each measurement end point the expected remote MEPs must 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, also raise a RemoteCCM alarm.
MEPs are entered in the CCM data base by clicking the Add button and entering a valid MEP-
ID.
MEPs are removed from the CCM database by clicking the Remove or Remove All button.
A3118-X652-R67-02 201 / 297

For each MEP in the CCM Database the following (read-only) information are 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 of the remote MEP
RDI
This parameter reports the state of the Remote Defect Indication (RDI) flag in the received
Continuity Check Messages (CCM).
LFP Target
Defines the LFP target group, which will be notified if the connectivity to this MEP has failed (3
consecutive CCM have been lost)
The ports defined in this LFP group are forced down accordingly.
Please refer to 8.4.2.2 for more information on LFP (Link Failure Propagation)
Client MP parameters:
Client MPs are configured to forward AIS and LCK signal of the domain the problem occurred, to the
higher level domain MP.
Up to 4 client MPs can be assigned to one MEP where as 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.
Please refer to the AIS and LCK chapter in the Service OAM fault management chapter 9.2.9 for client
MP examples.
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-X652-R67-02 202 / 297

9.2.9 Service OAM Fault Management
9.2.9.1 Y.1731 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.
Please refer to chapter 9.2.8.5 for AIS configuration information on the domain level.
Client MP configuration is explained in chapter 9.2.8.6.
The following picture illustrates an AIS example.
A3118-X652-R67-02 203 / 297

9.2.9.2 Y.1731 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 LCK is enabled on a MEP and the LCK
signal is enabled on the domain level.
Note:
Domains[Y]/Locked_Signal Enables the transmission of LCK frames and the forwarding of the LCK
signal to a client maintenance point)
MP[x]/Locked If true, then MEP is administratively locked and initiates LCK
9.2.9.3 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 on Switch Local in the following node:

SOAM\Domains\D X\MPs\MP Y\Loopback
SOAM Loopbacks are only available on enabled MEPs.
A3118-X652-R67-02 204 / 297

The following parameters can be configured for the loopback:

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 MEP with the specified
MAC address. See also Destination 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.
Destination MAC Address
MAC address of a specified remote MEP, see also Multicast Loopback.
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 [641500 Bytes]
Size of the loopback messages in bytes
LBM CoS
Defines the VLAN priority (CoS) of the LBM frame
LBM Queue
Defines the transmit queue the LBM frames are assigned to
9.2.9.4 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 are available on Switch Local, Switch EFM-NT and Switch CS in the
following node:
SOAM\Domains\Domain X\MPs\MP Y\Linktrace
A3118-X652-R67-02 205 / 297

SOAM Linktrace is only available on enabled MEPs.

Use MEP ID [enabled / disabled]
If enabled, the target MEP ID is used to indicate the remote MEP
Target MAC Adress
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.
LTM CoS [CoS0 .. CoS7]
Defines the VLAN priority (CoS value) of the LTM and LTR frames to be transmitted.
LTM 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]
LTM Transaction Identifier
Random number generated by the ACCEED unit.
The 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.
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
A3118-X652-R67-02 206 / 297

Figure 9-6 Service OAM Linktrace Replies
A3118-X652-R67-02 207 / 297

9.2.10 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. According to Section 6.9 EVC Related Performance Service
Attributes of MEF 10.2 [16] the following attributes can be specified for a service:
Frame Delay (FD)

Inter-Frame Delay Variation (IFDV)
Frame Loss Ratio (FLR)
Availability
The protocols and mechanisms required for the measurements are defined in ITU-T Y.1731 [17].
These are:
Two-way delay measurement with DMM/DMR frames

Dual-ended loss measurement with CCM frames
Single-ended loss measurement with LMM/LMR frames
The loss measurements are used for both FLR and availability performance. The definition of
availability is thereby left out of scope of the Y.1731 Recommendation.
Also the delay measurements are used for both FD and IFDV performance.
The measurement protocols always run between two MEPs. If the measurement is dual-ended it
means that both MEPs can gather results. If it is single-ended only the initiating MEP can gather
results. A one-way measurement is similar to dual-ended measurement while two-way is akin to
single-ended. However it is also possible to get (at least approximate) one-way results from two-
way measurement. They are then known as forward and backward, see Figure. The details are
explained later on.
Two-way measurement
Forward1
MEP A MEP B
Backward1
Round-trip
One-way measurement
MEP A MEP B
1
As seen from MEP A
Figure 9-7 Two-way vs. one-way measurement
A3118-X652-R67-02 208 / 297

The performance monitoring functions in ACCEED are grouped in two parts the delay measurement
(DM) and the loss management (LM).
Delay Measurement (DM)

Frame Delay performance (FD)
Inter-Frame Delay Variation performance (IFDV)
Loss Measurement (LM)

Frame Loss Ratio performance (FLR)
Availability
Before the actual delay or loss measurement can be started, a measurement session and responder
need to be configured on the respective devices.
Up to eight sessions and responders can be defined per ACCEED unit for delay and loss
measurement.
Each of the sessions requires a responder on the far end MEP to be configured. The responder adds
the required measurement information and makes sure the data is sent back towards the MEP where
the session was started.
All performance measurements are specific to a domain and consist of a session and a responder.
The picture below illustrates the session and responder principal.
Figure 9-8 Service OAM PM session and responder principle
9.2.10.1 DM Session configuration

Up to eight delay measurement sessions per ACCEED unit can be configured. Each session consists
of a frame delay measurement (FD) and an inter-frame delay variation measurement (IFDV).
Starting a DM session always performs a FD and IFDV measurement.
Delay measurement sessions are available under:

SOAM\Domains\DM Sessions\Session x
A3118-X652-R67-02 209 / 297


Enable
Enable the session, starts the measurements, immediately when applied.
Service Domain [D1 ..D5]
Maintenance Point [MP1 .. MP5]
Fame Length [64 .. 2048 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]
Enables and defines the target MEP ID. If enabled, Target MAC address can not be set.
DMM VID
Any VID defined in the VLAN DB can be selected here and therefore can be different then the
domain source associated VLAN ID
Attention: The DMM VID can be different than the domain source associated VLAN ID and
must be additionally configured in the Associated VLAN list of the respective domain if it is
not yet contained.
DMM CoS [CoS 0 .. CoS 7]
DMM Queue [Queue#0 .. Queue#7]
9.2.10.2 DM Responder configuration

DM responder is configured on the ACCEED where the remote MEP is located. Up to eight
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.
Delay measurement responders are available on Switch Local, Switch EFM-NT and Switch
CS in the following node:
SOAM\Domains\DM Responders\Responder x
A3118-X652-R67-02 210 / 297


Enable
Service Domain [D1 .. D5]
DMR VID
Any VID defined in the VLAN DB can be selected here and therefore can be different then the
domain source associated VLAN ID. The DMR VID must be the same as configured for DMM
frames.
Attention: The DMR VID can be different than the domain source associated VLAN ID and
must be additionally configured in the Associated VLAN list of the respective domain if it
is not yet contained.
DMR CoS [CoS 0 .. CoS 7]
DMR Queue [Queue#0 .. Queue#7]
9.2.10.3 Frame Delay (FD)

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 (07/2011).
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-9 Service OAM Round trip delay measurement principle
A3118-X652-R67-02 211 / 297

Every delay measurement results is assigned to one of maximal 5 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 then 5 sec are not considered and therefore discarded.
Figure 9-10 Service OAM Delay Measurement Bin
Up to 5 Round-Trip Bins can be configured for each DM session, whereas the threshold of Bin 1 is a
permanent list entry. Bins 2 to 5 can be added with the respective Add button.
SOAM/DM Sessions/Session x/FD/Round-Trip Bins[]

Range of the Threshold values [0 .. 5000000 micro seconds]
In order to supervise the delay of a service and generate an alarm if a defined limit is exceeded within
a measurement interval, for each DM session an Objective Round-Trip delay and a Percentile Round-
Trip delay can be configured.
An SOAM-FD Objective Alarm is raised if less percent of the measurements defined by the
Percentile Round-Trip are below the round trip delay defined by the Objective Round-Trip.
The Objective Round-Trip is defined by choosing the respective Bin. Default value: None
The Percentile Round-Trip range is from 0 to 100%. Default value: 95%
The Round-Trip parameters can be configured under SOAM\DM Sessions\Session x\FD
A3118-X652-R67-02 212 / 297

Delay measurement in ACCEED provides the frame delay measurement information of the current
interval and the past up to 32 intervals in a history. The interval duration is configurable in the range of
1 to 1440 minutes.
The frame delay measurement results of the respective interval are accessed via the
Performance tab and the following path SOAM\DM Sessions\Session x\FD
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.
If the Round-trip values show unknown and the 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\DM Sessions\Session x\FD\Statistics\Current
Every frame delay measurement is assigned to the respective Bin and counted there. The Bin
counters can be accessed via the Performance tab and the following path:
SOAM\DM Sessions\Session x\FD\Round-Trip Bins[]
A3118-X652-R67-02 213 / 297

below.
9.2.10.4 Inter-Frame Delay Variation (IFDV)

The measurement of inter-frame delay variation can be performed using the same mechanism as
used for frame delay measurement by exchanging DMM and DMR messages and evaluating the time
stamps.
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.
Figure 9-11 Service OAM Inter-frame delay variation measurement principle
A3118-X652-R67-02 214 / 297

Every IFDV measurement results is assigned to one of maximal 5 intervals called bins, whose
corresponding counter is increased. This is performed in forward and backward direction accordingly.
For more information on the Bin principle please refer to chapter 9.2.10.3
Up to 5 Forward and 5 Backward Bins can be configured for each DM session, whereas Bin 1 is a
permanent list entry. Bins 2 to 5 can be added with the respective Add button.
SOAM/DM Sessions/Session x/IFDV/Forward Bins[]

Range of the Threshold values [0 .. 5000000 micro seconds]
In order to supervise the inter-frame delay variation of a service and generate an alarm if a defined
limit is exceeded within a measurement interval, for each DM session objectives and percentiles for
forward and backward inter-frame delay variation can be configured.
An SOAM-IFDV Objective Alarm is raised if less percent of the measurements defined by the
Percentile Forward / Backward are below the inter-frame delay variation defined by the Objective
Forward- and Backward parameter.
The Objective Forward and Backward is defined by choosing the respective Bin. Default
value: None
The Percentile Forward and Backward range is from 0 to 100%. Default value: 95%
These parameters can be configured under SOAM\DM Sessions\Session x\IFDV
A3118-X652-R67-02 215 / 297

Inter-frame delay variation measurement in ACCEED provides the measurement information of the
current interval and the past up to 32 intervals in a history. The interval duration is configurable in the
range of 1 to 1440 minutes.
The inter-frame delay variation measurement results of the respective interval are accessed
via the Performance tab and the following path SOAM\DM Sessions\Session x\IFDV
below.
Every inter-frame delay variation measurement is assigned to the respective Bin and
counted there. The Bin counters can be accessed via the Performance tab and the
following path:
SOAM\DM Sessions\Session x\IFDV\Forward Bins[] and \Backward Bins[]
below.
A3118-X652-R67-02 216 / 297

9.2.10.5 DM Session Statistics

In order to see any DM values, statistics must be enabled. Additionally, the interval duration for the
measurement can be set. Default value is 15 min. The possible range is from 1 min to 1440 min.
The measured values can be stored in the history for up to 32 intervals.
The statistics settings can be accessed under:

SOAM/DM Sessions/Session x/Statistics/Current
One History can be added and enabled for up to 32 intervals. The interval duration is taken
from the current statistics setting.
History settings can be accessed under:
SOAM/DM Sessions/Session x/Statistics/Historic[]
If the Statistics Current is not active, the performance value are displayed as Inactive
A3118-X652-R67-02 217 / 297

9.2.10.6 Loss Measurement (LM)

The measurement of the frame loss is implemented using dual-ended (using CCMs) and single-ended
(using LMMs) loss measurement according to ITU-T Y.1731 (07/2011).
In the performance monitoring instance the method of measurement can be determined by the LM
Type parameter (Value: CCM or LMM). In terms of quality of the results both methods are equivalent.
However there are some advantages and disadvantages for either variant as shown in the table
below.
Method Pro Con
CCM based No additional frames inserted Only one instance per MEP possible
(dual-ended) (if CCMs are already used) Configuration on both ends required
Calculation of results is
possible on both ends
LMM based No configuration on other end Extra frames inserted
(single-ended) required (better suited for on- Calculation of results is only possible
demand measurement) on the initiating end
Measurement of multiple
services on the same MEP
Table 3 Pros and cons of CCM and LMM based frame loss measurement
Dual-ended frame loss measurements are based on the LM type CCM and therefore on
each end a LM session need to be configured.
Single-ended frame loss measurements are based on the LM type LMM. These
configurations consist of a LM Session on the initiating MEP and a LM Responder on the
other MEP.
Common limitation of the loss measurement is that it does not support point-to-multipoint
connections.
If there is no customer traffic on the service to be monitored, the loss measurement does
not deliver any results.
9.2.10.7 LM Session configuration

Up to eight loss measurement sessions per ACCEED unit can be configured. Each session consists of
a frame loss ratio (FLR) and an Availability section.
Delay LM sessions are available under:

SOAM\Domains\LM Sessions\Session x
A3118-X652-R67-02 218 / 297


Enable
LM Type [LMM, CCM]
Defines the loss measurement meassage type. See 9.2.10.6 for more information.
Period [100ms, 1s, 10s]
Ingress Policy
Policy used for counting Tx frames in case of Up-MEP or Rx frames in case of Down-MEP
Egress Policy
Policy used for counting Tx frames in case of Down-MEP or Rx frames in case of Up-MEP
Enables and defines the target MEP ID. If enabled, Target MAC address can not be set.
LMM VID
Any VID defined in the VLAN DB can be selected here and therefore can be different than the
domain source associated VLAN ID. The LMM VID must be the same as configured for LMR
frames.
Attention: The LMM VID can be different than the domain source associated VLAN ID and
must be configured additionally in the Associated VLAN list of the respective domain if it is
not yet contained.
LMM CoS [CoS 0 .. CoS 7]
LMM Queue [Queue#0 .. Queue#7]
Ingress / Egress Policy

The FLR and Availability measurement 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.8.2
A3118-X652-R67-02 219 / 297

Only frames marked as green are considered for the FLR and Availability measurement.
Global counter setting

The metering counters need to be set to packets. Please refer to the picture below with the part
highlighted in yellow.
These settings are done on the switch level and therefore apply to all ports.
The global counter settings are available under:

Ethernet/Switch Local
Only the Ingress and Egress Metering Counters need to be set to Packets for LM sessions. The
Ingress and Egress Policy Counters can be configured independently of the LM sessions!!
9.2.10.8 LM Responder configuration

LM responders are required for the single-ended loss measurement, using the LM type: LMM.
Up to eight loss measurement responders per ACCEED unit can be configured.
Delay LM sessions are available under:

SOAM\Domains\LM Sessions\Session x

Enable
Ingress Policy
Policy used for counting Tx frames in case of Up-MEP or Rx frames in case of Down-MEP
Egress Policy
Policy used for counting Tx frames in case of Down-MEP or Rx frames in case of Up-MEP
LMM VID
A3118-X652-R67-02 220 / 297

Any VID defined in the VLAN DB can be selected here and therefore can be different than the
domain source associated VLAN ID. The LMR VID must be the same as configured for LMM
frames.
Attention: The LMR VID can be different than the domain source associated VLAN ID and
must be configured additionally in the Associated VLAN list of the respective domain if it is
not yet contained.
LMR CoS [CoS 0 .. CoS 7]
LMR Queue [Queue#0 .. Queue#7]
9.2.10.9 Frame Loss Ratio (FLR)

Frame Loss Ratio (FLR) measurement is performed by exchanging local transmit (TxFC) and receive
service frame counters (RxFC) of a MEP.
Two measurement types are possible. Single-ended (only the initiating MEP gathers results) using
loss measurement messages (LMM) and loss measurement replies (LMR)
Dual-ended (both MEPs gather results) using continuity check messages (CCM)
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).
The picture below illustrates the measurement principle.
Figure 9-12 Service OAM Frame loss ratio (FLR) measurement principle
FLR Configuration
FLR configuration parameters are available under:

SOAM\LM Sessions\Session x\FLR in the Configuration tab
A3118-X652-R67-02 221 / 297


Average FLR Forward Threshold [0% .. 5% ..100%]
The average frame loss ratio threshold (%) are compared at the end of a measurement interval
against the current value. If this value exceeds the threshold a FLR threshold alarm is generated
(lasting until the end of the measurement interval)
Average FLR Backward Threshold [0% .. 5% ..100%]
the same as above for the backward measurement direction.
FLR results are available under:

SOAM\LM Sessions\Session x\FLR in the Performance tab
A3118-X652-R67-02 222 / 297

9.2.10.10 Availability
The Availability is defined by the frame loss ratio during a sequence of consecutive time intervals (n)
and the last availability state.
A sliding window of size n = {1, , 10} contains the information concerning the FLR compared to the
FLR-threshold C of the last n consecutive time intervals.
Figure 9-13 Service OAM Availability definition
Availability configuration parameters are available under:

SOAM/LM Sessions/Session x/Availability in the Configuration tab

Consecutive Measurements [1 ..10]
FLR Threshold [0% .. 50% .. 100%]
Unavailability Threshold Forward [0% .. 5% .. 100%]
Unavailability Threshold Backward [0% .. 5% .. 100%]
Availability results are available under:

SOAM\LM Sessions\Session x\Availability in the Performance tab
A3118-X652-R67-02 223 / 297

9.2.10.11 LM Session Statistics
LM session statistics are configured the same way as DM session statistics with the following
exceptions:
- FLR and Availability can be configured independently where as the FD and IFDV is a
combined configuration.
- Interval duration range is larger in case of FLR and Availability [1..525600 min]
Please refer to 9.2.10.5 for information on how to configure the statistics and history section.
A3118-X652-R67-02 224 / 297

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
rd
capable 3 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-14 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 todays 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-X652-R67-02 225 / 297

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.
9.3.1 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-15 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 analyser.
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-X652-R67-02 226 / 297

9.3.2 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-16 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.
CIR (1 FLRThreshold ) rxRate (CIR EIR)

rxFLR FLRThreshold
rxFD FDThreshold
A3118-X652-R67-02 227 / 297

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 MFactor 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.
CIR (1 FLRThreshold ) rxRate (CIR EIR) (1 M )

rxFLR FLRThreshold
rxFD FDThreshold
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-X652-R67-02 228 / 297

rxAvailability AvailabilityThreshold
9.3.3 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 0x88B7 2 Bytes
Albis OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier
Albis Ethertype (0x0011) 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)
TPID = 0x8100 (fix) 2 Bytes
VLAN cTag (optional)
Ethertype 0x88B7 2 Bytes
OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier Albis Ethertype 2 Bytes
(0x0090, 0x0091, 0x0092)
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 0x0010
Fixed Size: 64..2048 Bytes 0x001F
Table 16 Albis Ethertypes
A3118-X652-R67-02 229 / 297

9.3.4 Test execution

Ethernet/Switch Local/SAT
The SAT can be executed by pressing the Start button. 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.
A3118-X652-R67-02 230 / 297

9.3.5 SAT General configuration
Figure 9-17 Service Activation Test example

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,
A3118-X652-R67-02 231 / 297

Destination MAC Address

Sets the target MAC Address of the Destination. Typically it is the MAC of the Loopback device
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
9.3.6 SAT Configuration of the Test CoS Instances
Figure 9-18 SAT Test CoS Instance

A3118-X652-R67-02 232 / 297
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
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.10.10
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
Applied Modifier
To test the ingress modifier of the local LAN port, the same modifier policy of this LAN port can be
selected from the dropdown menu
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
A3118-X652-R67-02 233 / 297

9.3.7 Results
Figure 9-19 SAT Results
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 to 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
A3118-X652-R67-02 234 / 297

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-X652-R67-02 235 / 297

9.3.8 Test Report

The test report has two sections: First the setup parameters and second the measurement results.
Figure 9-20 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, FLR, Availability, FD, IFDV, Pattern, Size, VID and CoS).
The second section contains the results of each single test parameter. 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 he 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-X652-R67-02 236 / 297

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 file by pressing the Save As button.
A3118-X652-R67-02 237 / 297

ULAF+ 10 - CES Circuit Emulation for ACCEED 2202 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-X652-R67-02 238 / 297

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
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
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-X652-R67-02 239 / 297

10.1 Introduction to TDM CES

10.1.8 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
10.1.9 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
10.1.10 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:
A3118-X652-R67-02 240 / 297

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.
10.1.11 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 1984 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 2048kbit/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.
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.
A3118-X652-R67-02 241 / 297

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
Bit 4 Bit 6 Bit 7 Interpretation
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).
10.1.12 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
Carriage of TDM signalling 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.
A3118-X652-R67-02 242 / 297

In case of ACCEED the framer can be configured to operate the following modes:
Transparent: frames pass unchanged (LOS, AIS)
Monitoring: frames pass unchanged, CRC4 errors are evaluated (BER, LFA, RDI)
Termination: frame is regenerated, CRC4 section is terminated (alarms per section)
Figure 10-4 CES functional components
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 chapter 10.1.11.
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
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.
A3118-X652-R67-02 243 / 297

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).
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
10.1.13 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
A3118-X652-R67-02 244 / 297

adds to the end to end overall delay.
Figure 10-6 CES operation overview
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. The maximum Bandwidth Efficiency is 100% (without
overhead).
PayloadSize [ Bytes]
BandwidthEffciencyCESoEth [%]
30 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.
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 (2048 kBit/s). The resulting Bandwidth Efficiency is 89.5% for
CESoEth and 88.3% for CESoMPLS. This equals 2288 kBit/s and 2320 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
A3118-X652-R67-02 245 / 297

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. Refer to chapter 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 4096 Bytes.
Read out the measured maximum PDV after the value has reached the maximum as
described in chapter 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.
A3118-X652-R67-02 246 / 297
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 chapter 10.3.2 for packetization delay and chapter 10.4.2 for jitter buffer
delay.
A3118-X652-R67-02 247 / 297

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.
A3118-X652-R67-02 248 / 297

Figure 10-7 ACCEED 2202 CES Application Overview
A3118-X652-R67-02 249 / 297

10.2.8 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
encapsulation. Please refer to chapter 10.3 for more information on the ACCEED 2202 CES
configuration options.
Figure 10-8 ACCEED CES Network
A3118-X652-R67-02 250 / 297

10.3 Configuring CES

10.3.1 Enabling CES and the TDM interface
Enabling the CES function and the TDM interface can be done here:
CES IWF/Local/TDM/TDM1
Mode [Clock, TDM] Clock: 2 MBit or 2048 kHz clock, see chapter 11.4.5
TDM: 2 MBit/s clock
Impedance [120, 75 Ohm] Impedance of TDM interface
10.3.2 Configuring the CES parameters
The CES parameters are configured here:

CES IWF/Local/TDM/TDM1/Packet
Please refer to chapter 10.1.13 for more information on jitter buffer- and payload size.
A3118-X652-R67-02 251 / 297

Encapsulation [Ethernet, MPLS]

Payload Format [SAToP, CESoPSN]
Egress Port [all available Ethernet ports]
Defines the Ethernet port that sends and receives the CES stream
Destination MAC The MAC address of the destination (remote) CES function
Source MAC Displays the MAC address of the CES function that is assigned to the physical
port (egress port). Source MAC address is read only.
Note: The source MAC address is specific to the selected egress port. If the
egress port is changed, the destination MAC address of the remote CES IWF
need to be updated accordingly.
Relevant only if Encapsulation = Ethernet

Destination ECID [1 .. 1048575] destination ECID
Source ECID [1 .. 1048575] 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 .. 1000 .. 1048575]
Tunnel Egress Label [1 .. 1000 .. 1048575]
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 .. 1048575]
Pseudowire Egress Label [1 .. 100 .. 1048575]
Note: the TTL value of the egress pseudowire label is set to 2 (Y.1413) since the CES service is
a point 2 point application. The TTL value can not be changed by the user.
Assigned VLAN ID [1, list of all defined VLANs in the VLAN database]
Assigned CoS Value [0 .. 7]
Assigned Queue [0 .. 7], assigned egress transmit queue
Jitter Buffer Size [2 ..4096 .. 8192] Please refer to 10.1.13 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 .. 1023] Please refer to 10.1.13 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 same in the local and remote packet
configuration of the IWF.
A3118-X652-R67-02 252 / 297

10.3.3 Configuring the Framer

The framer can be configured independently from the payload type.
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 frames pass unchanged (LOS, AIS)
Monitoring frames pass unchanged, CRC4 errors are evaluated (BER, LFA, RDI)
Termination CRC4 section is terminated, a new frame is generated
Subscriber Bitrate [64, 128 .. 2048 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 1984kbit/s or 31 time slots (TS). Time slot
0 (zero) terminated in the CES IWF.
CRC4-TDM [disabled, enabled]
CRC4-CES [disabled, enabled]
If the clock for the CES function is provided via front panel clock input, the framing must be
set to termination and CRC4 TDM must be activated.
10.3.4 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)
Ethernet Ports (SyncE)
Internal clock
Please refer to chapter 11.4.5 for information on the clocking options.
A3118-X652-R67-02 253 / 297

10.4 CES Performance Monitoring and

Fault management
10.4.1 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-X652-R67-02 254 / 297

10.4.2 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 chapter 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-X652-R67-02 255 / 297

10.4.3 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 .. 3600]
Number of Intervals: [1 .. 32]
Please note that the historic counters must be activated in order to be effective.
10.4.4 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
A3118-X652-R67-02 256 / 297

10.4.5 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
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.
Figure 10-9 CES Alarm locations
A3118-X652-R67-02 257 / 297

10.5 CES Operational Aspects

10.5.1 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
10.5.2 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 chapter 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 chapter 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 chapter 8.10.7 for port utilization
A3118-X652-R67-02 258 / 297

The Packet configuration (Encapsulation and Payload Type) must match between both CES
IWF. Example: VID=22, CoS=7, CESoPSN, Payload Size=256
Verify CES packet and jitter buffer performance, see chapter 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 chapter 10.1.13
Verify that the CES packets are sent to the correct egress queue and no packets are dropped
in this egress queue.
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.On 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.
A3118-X652-R67-02 259 / 297

ULAF+ 11 - General Board settings ACCEED 2202 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-X652-R67-02 260 / 297

11.1 Board general system information

The Board section provides on the top level general system information on the inventory,
system resource situation and a system log.
This information is accessible under Board/ by selecting the respective buttons marked
yellow in the screen shot below. The information is further explained in the following
chapters.
11.1.1 System Log
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-X652-R67-02 261 / 297

11.1.2 Ressources
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 and fan information are displayed
additionally
Save As saves the resource information in a text or pdf file

Refresh updates the Resources window
A3118-X652-R67-02 262 / 297

11.1.3 Inventory
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.
Save As saves the inventory information in a text or pdf file

Refresh updates the Inventory window
A3118-X652-R67-02 263 / 297

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 when 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.
11.2.1 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 2202 alarms.
For more information on the individual alarm please refer to the alarm list in chapter 12.3
A3118-X652-R67-02 264 / 297

A3118-X652-R67-02 265 / 297

11.2.2 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. 11.4
The logging values are accessible under Board/Alarm Configuration/Logging
A3118-X652-R67-02 266 / 297

11.3 Local
11.3.1 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.
11.3.2 SCC Configuration

Not applicable.
11.3.3 Maintenance
Possible maintenance reasons for ACCEED 2202 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
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 is active.
A3118-X652-R67-02 267 / 297

11.3.4 Time Setting

For the time setting configuration please refer to chapter 5.8.7
11.3.5 Management Access

For the management access options please refer to chapter 5.8.2
A3118-X652-R67-02 268 / 297

11.4 Synchronization
11.4.1 Introduction
ACCEED 2202 is an Ethernet device. Due to Ethernets asynchronous packet character there is no
need for synchronization for basic data transmission service. However timing critical applications like
mobile or DSLAM backhaul require accurate synchronization on remote location. This is why the
ACCEED offers a comprehensive feature set to provide high quality timing to customer locations.
Network synchronization can be derived from 2MHz or SyncE physical reference clocks
Synchronous Ethernet (SyncE)

Due to the new services transmitted over packet networks it may be necessary to transport high
quality frequency synchronization across the entire network.
For example, time division multiplexing (TDM) services such as T1/E1 and SONET/SDH require
synchronized clocks at both the source and destination nodes. Similarly, wireless base stations
require synchronization to a common clock to ensure a smooth handover between adjacent cells.
While there are several ways to achieve synchronization over Ethernet, one gaining momentum is
Synchronous Ethernet (SyncE). SyncE is a PHY-Level frequency distribution that is achieved through
the Ethernet port. This method requires a primary Reference Clock (PRC) feeding the Ethernet
Network. At each node a timing recovery unit will recondition the clock, clean it, and use it as the
transmit clock to the next node. Thus the timing is passed from node to node in the same way timing is
passed in SONET/SDH or T1/E1.
Synchronous Ethernet (SyncE) applications:
Wireless Backhaul:
- For GSM systems; the timing reference has been T1 or E1-based. Bandwidth of these links is
saturated due to the new 3G services.
- LTE next generation wireless protocol.
- Current GPS based systems moving to SyncE for frequency reference
Metro and Carrier Ethernet:
- Circuit Emulation Services
- Digital Video Broadcasting
11.4.2 ACCEED synchronization overview

ACCEED NT features a hybrid "SETS" function to provide 2MHz, HDB3 and SyncE clock outputs
Acts as a converter for different types of clock sources and formats
The ACCEEDs internal clock source has EEC1 (SEC) quality
A3118-X652-R67-02 269 / 297

11.4.3 Clock sources
Figure 11-1 Clock sources example
11.4.4 Synchronization ports

G.703 2MHz Bit Clock
Input: - Plug in units LT from sub rack backplane
- Desktop units LT from 2MHz clock front side connector
Output: - Plug in and desktop units NT at 2MHz clock front side connector
Synchronous Ethernet Ports

Input: - Any 100/1000 Ethernet port (P1P3 or SFP) on ACCEED LT
Please note, electrical SFP do not support SyncE properly and can not be used as
input port for SyncE.
Output: - All 100/1000 Ethernet ports (P1P3 and SFP) on ACCEED NT
- Ethernet ports not used as synchronization inputs on ACCEED LT
Others
Input: - SHDSL to transmit the clock from LT to NT (with symbol clock).
Selection of available SHDSL interfaces is done automatically.
- SCC to get synchronization form other ACCEEDs in the array
Output: - SCC to transmit synchronization to other ACCEEDs in the array
A3118-X652-R67-02 270 / 297

11.4.5 Clock source selection mechanism

Two criteria (Quality and Priority) are used for determining which clock source the ACCEED shall
apply to obtain its system clock. Both, quality and priority information has to be assigned to every
clock source.
Clock source quality information is assigned by configuration or a prior knowledge (e.g. internal clock
= SEC).
In case of SyncE data (Ethernet ports P1...P3, SFP) the quality can be defined by the Ethernet
Synchronization Messaging Channel (ESMC). The messages in the ESMC are equal to the messages
of the TDM Synchronization Status Message (SSM). the SyncE clock quality is also configurable via
LCT+.
Clock source priority is assigned by configuration. The priorities determine which clock sources are
allowed for the clock extraction and in what order, if several sources have the same clock quality.
ACCEED selects and forwards the clock source with best quality available. If sources with equal
quality are available, clock selection is based on priority.
If both the quality and the priority are equal, the following pre-programmed succession is applied:
Clock input
Ethernet
SHDSL
SCC
internal
If one source fails an automatic switch over to the next clock source with the best quality and the
highest priority is implemented.
If there is no external source available, the internal oscillator changes to the mode holdover. In this
mode the ACCEED retains the clock frequency of the source to which it had been synchronized before
the failure. The holdover mode is revertive. Once the original clock source with the previously highest
priority will work correctly the ACCEED synchronizes after a wait to restore time back to the original
clock source.
11.4.6 Supported quality and priority values

Quality
Supported clock quality levels correspond to the levels defined in Option 1 of ITU-T G.781. Other
quality levels are displayed at the input interface but treated as DNU (0x0F).
0x02 (QL PRC) Highest quality level

0x04 (QL SSU-A)
0x08 (QL SSU-B)
0x0B (QL SEC) Lowest quality level
0x0F (QL Do not use) Should not be used for synchronization
Priority
Clock priorities configured via the NMS correspond to the following values:
Range: 0..255
0 defines the highest priority
255 represents the lowest priority
A3118-X652-R67-02 271 / 297

11.4.7 Synchronisation input selection on LT
Figure 11-2 LT Synchronization
Clock source can be selected among 2MHz, Eth, SCC or Internal

Quality and Priority have to be assigned to each source
The Ethernet Port selected as input sends "Do not use" information in opposite direction to
prevent a clock loop
Inspection and transmitting of the SSM at the Ethernet ports (using ESMC) can be disabled
Quality of Ethernet source can be SSM (ESMC) or set manually
Q/P and SSM are transmitted to outputs
11.4.8 Synchronization output selection on NT

ACCEED 1416 NT
Ethernet SSM
Q/P
SCC SCC Q/P
Q/P Clock
SHDSL 1...4 Q / P of the
Source
selected
Selection
Q/P clock source 2 MHz clock out Q/P
Internal /
Holdover
Figure 11-3 NT Synchronization
Clock source is selected among SHDSL, SCC or Internal

Each clock source has a quality and priority (assigned by LT)
Selection of SHDSL-Port (14) is done automatically (based on availability, quality and priority)
Selection of SCC Port (East or West) is done automatically (based on availability, quality and
priority)
Transmitting of the SSM at the Ethernet ports (using ESMC) can be configured
A3118-X652-R67-02 272 / 297

Clock output is squelched if clock quality falls below a configurable threshold

11.4.9 SSM support
If an Ethernet port is selected as clock source on the EFM-LT and if "Use SSM" is selected, the QL
value will be extracted from the received SSM packet. If no or invalid SSM packets are received, the
clock is considered invalid and gets the QL value "Do not use" (0x0F).
In case of 100FD or 1000FD operation, the SSM packets are transmitted periodically on all Ethernet
ports (LT and NT) except on LT port configured as input. The quality corresponds to the assigned QL
value of the current active clock source.
11.4.10 Synchronization Fault Management

All Synchronization relevant alarms are described in chapter 12.3.
11.4.11 Synchronization configuration

As indicated in the previous chapters several parameters can be configured to define the clock source
selection of the ACCEED 2202 clock synchronization.
The next sections show the different LCT+ configurations and information (read only values) based on
the following ACCEED 2202 configuration:
Figure 11-4 Synchronization configuration model
A3118-X652-R67-02 273 / 297

11.4.11.1 LT configuration
Clocking
Clocking can be found in Board\Local
In this folder you can find the currently active clock source as well as the according quality
and priority levels displayed as read only values.
This area is also used to configure the SSM handling for the SyncE ports.
Trust SSM
Send SSM
The settings are global (for all SycE Ports)
Note: Picture shows default settings
Internal
Internal can be found in Board\Local\Clocking
This area presents status messages concerning the internal clock. All parameters are read only.
A3118-X652-R67-02 274 / 297

Clock-In
Clock-In can be found in Board\Local\Clocking
This area is used to configure settings relating to the incoming clock.
Quality
Priority
Impedance 2
2
Only available on ACCEED desktop units
A3118-X652-R67-02 275 / 297
Ethernet
Ethernet can be found in Board\Local\Clocking
This area is used to configure settings relating to the incoming clock on Ethernet interfaces.
Source Port
(in the example below P1 is selected as Source Port. It means that P1 is a clock input)
Quality (Quality level assigned to that input port manually)
Quality Reported By SSM (Quality level assigned to this clock source using SSM)
Priority (Priority assigned to this clock source)
11.4.11.2 Configuration on NT side

Clocking
Clocking can be found in Board\EFM-NT
In this folder you can find the currently active clock source as well as the according quality and
priority levels displayed as read only values.
This area is also used to enable the SSM generation and to define the minimum quality level to
transmit to transmit the clock.
Send SSM
Output Squelch Threshold
A3118-X652-R67-02 276 / 297

ULAF+ 12 - Troubleshooting ACCEED 2202 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-X652-R67-02 277 / 297

12.1 Most common troubles

12.1.1 SHDSL startup problems
Not applicable.
A3118-X652-R67-02 278 / 297

12.2 LED indications
1 3 5 7 9
2 4 6 8
Figure 12-1 ACCEED 2202 LEDs
12.2.1 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 chapter 5.2.
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.
12.2.2 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 chapter 12.3.
Alarms configured as Warnings are not indicated on the alarm LED.
A3118-X652-R67-02 279 / 297

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

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
12.2.4 CLK LED (4)

RED Indicates fault of clock input
See chapter 0.
12.2.5 NMS green LED (5)
OFF This indication signals "no connection" or "no traffic" on the NMS interface.
Possible cause are:
- Wiring error (interface is not connected)
- Configuration error (interface shut down)
12.2.6 ETH Px green LED (6) and (7)

OFF This indication signals "no connection" or "no traffic" on the P1, P2 or P3
interface.
Possible cause are:
12.2.7 SFPx LED (8) and (9)

green OFF This indication signals "no connection" or "no traffic" on SFP interface.
Possible cause are:
red ON This indication signals the SFP-Missing alarm.

See chapter 12.3.32.
red BLINKING This indication signals the SFP-Incompatible alarm.

SLOW See chapter 12.3.31.
A3118-X652-R67-02 280 / 297

12.3 Alarm list
12.3.1 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
12.3.2 CES-ARE Alarm

description Adress Resolution Error at CES interface detected
alarm location CES
default severity Critical
default logging Log
LED signaling None
debug hints Check the local and remote CES configuration
12.3.3 CES-LOF Alarm

description Loss of Frames at CES interface detected
alarm location CES
default logging Log
LED signaling None
debug hints Check the connectivity between the two CES IWF
12.3.4 CES-RAI Alarm

description Remote Alarm Indication at CES interface detected
alarm location CES
default logging Log
LED signaling None
debug hints Check the TDM interface at the remote IWF
A3118-X652-R67-02 281 / 297

12.3.5 Clock Not Available Alarm

description No valid source clock available
alarm location Clock
defect location Clock
default logging log
LED signaling RED CLOCK LED ON
debug hints This alarm exists only on units configured as LT.
This alarm is raised, when the active clock source fails. No alarm is raised if
a backup clock fails.
Example:
Priority sequence (from top priority): clock-in, SyncE
If clock-in fails -> Clock Not Available alarm is raised
If SyncE fails -> Clock Not Available alarm is not raised.
Possible causes are:

- wiring error:
Remember that for plug in units the Subrack interface must be used
instead of the interface on the front panel!
- No signal present, check the clock device
12.3.6 Clock Squelched Alarm

description Clock output is squelched due to low quality
alarm location Clock
defect location Clock
default logging log
LED signaling YELLOW CLOCK LED ON
debug hints This alarm exists only on units configured as NT.
This alarm is raised, when the quality of the available clock source is poorer
than the configured quality threshold. The clock output signal is consequently
suppressed.
The reference clock source should be checked
12.3.7 Equipment Alarm

description Equipment failure
alarm location Equipment
defect location Equipment
default logging log
LED signaling none
debug hints The HW is damaged. Replace the unit.
A3118-X652-R67-02 282 / 297

12.3.8 ETH No Link Alarm

description No link on Ethernet port
alarm location ETH Port
defect location ETH Port
default logging log
LED signaling none
debug hints Ethernet port not connected / Cable broken
Configuration error (e.g. interface shut down)
12.3.9 Fan Alarm (desktop only)

description Fan defect or RPMs below threshold
alarm location Fan
defect location Fan
default logging log
LED signaling none
debug hints The alarm indicates that the turning speed of the fan in the desktop unit is
below a certain threshold value, indicating mechanic deterioration due to
aging or complete failure. The fan should be replaced before the fan
completely fails.
12.3.10 LAG-Aggregation Loss

description All members ports of the LAG port are down
alarm location Aggregation
defect location ..
default logging log
LED signaling ..
debug hints ..
12.3.11 LAG-Aggregation Mismatch

description Link Aggregation is not set up properly
defect location ..
default logging log
LED signaling ..
debug hints ..
12.3.12 LAG-Partial Aggregation Loss

description A member port of the LAG port is down, protection is no more available
defect location ..
default logging log
LED signaling ..
debug hints ..
A3118-X652-R67-02 283 / 297

12.3.13 LFP Alarm

description Link failure propagation (link forced down due to PAF alarm)
alarm location ETH Port
defect location ETH Port
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
12.3.14 LinkOAM-Critical Event Alarm

description Link OAM peer reports a Critical Alarm
alarm location Link OAM
defect location Link OAM
default logging log
LED signaling none
debug hints The peer unit has an equipment alarm
12.3.15 LinkOAM-Dying Gasp Alarm

description Link OAM peer reported a dying gasp (caused by power fail or an
unexpected reboot)
default logging log
LED signaling none
debug hints The peer unit has power loss condition
12.3.16 LinkOAM-Invalid Peer Alarm

Description ......................................
default logging log
LED signaling none
debug hints
A3118-X652-R67-02 284 / 297

12.3.17 LinkOAM-No Peer Alarm

description No Link OAM no peer discovered
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
A3118-X652-R67-02 285 / 297

12.3.18 PoE Fault Alarm

description Non-powered device, device with invalid signature or faulty device
connected
alarm location PoE
defect location PoE
default logging log
LED signaling none
debug hints No device connected
Non-powered device connected
Low Signature Detected
High Signature Detected
Overload
12.3.19 Power Failure Alarm

description Power supply voltage below threshold
alarm location Power Supply
defect location Power Supply
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 chapter 9.1.
12.3.20 Resource Shortage Alarm

description Not enough resources available
defect location Resources
default logging log
LED signaling none
debug hints Cleaning up unused rules and service configurations may help to solve the
resource shortage problem.
12.3.21 SOAM-AIS Alarm

description AIS messages received
alarm location MEP
defect location Remote MEP (CCM Database)
default logging Log
LED signaling None
possible causes Check for possible loss of continuity on lower layer
A3118-X652-R67-02 286 / 297

12.3.22 SOAM-Avail Objective

description Availability objective has been exceeded
alarm location MEP
default logging Log
LED signaling None
defect(s)
possible causes .
12.3.23 SOAM-ErrorCCM Alarm

description Invalid CCM received
alarm location MEP
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 chapter 9.2.1.5,
in the section Last CCM Failure parameters.
12.3.24 SOAM-FD Objective

description Frame delay objective has been exceeded
alarm location MEP
default logging log
LED signaling none
defect(s)
possible causes .
12.3.25 SOAM-FLR Threshold

description Average Frame loss ratio has exceeded the configured threshold
alarm location MEP
default logging log
LED signaling none
defect(s)
possible causes .
A3118-X652-R67-02 287 / 297

12.3.26 SOAM-IFDV Objective

description Inter-Frame delay variation objective has been exceeded
alarm location MEP
default logging log
LED signaling none
defect(s)
possible causes .
12.3.27 SOAM-LCK Alarm

description LCK messages received
alarm location MEP
default logging log
LED signaling none
possible causes Intended Maintenance Mode (not a defect)
12.3.28 SOAM-RDICCM Alarm

description Remote defect indication
alarm location MEP
default logging Log
LED signaling none
debug hints A MEP in the domain has loss of continuity
12.3.29 SOAM-RemoteCCM Alarm

description CCMs missing
alarm location MEP
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
A3118-X652-R67-02 288 / 297

12.3.30 SOAM-XconCCM Alarm

description Cross connect error
alarm location MEP
defect location MEP
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)
12.3.31 SFP-Incompatible Alarm

description SFP module is incompatible
alarm location SFP
defect location SFP
default logging log
LED signaling RED SFP LED Blink-Slow
debug hints The equipped SFP module type is not supported.
Following SFP types are supported:

100Base-FX
1000Base-SX
1000Base-CX
1000Base-LX
1000Base-T
12.3.32 SFP-Missing Alarm

description SFP module missing
alarm location SFP
defect location SFP
default logging log
LED signaling RED SFP LED ON
debug hints The interface SFP1 is enabled but the SFP module is not inserted into the
SFP slot.
12.3.33 SFP-Tx Fault Alarm

Description The SFP module raised a SFP-Tx Fault alarm
alarm location SFP
defect location SFP
default logging log
LED signaling none
debug hints SFP-TX Fault indicates a laser fault of some kind.
A3118-X652-R67-02 289 / 297

12.3.34 TDM-AIS Alarm

description Loss of Frame Alignment at TDM/Clock interface detected
alarm location TDM / G.703
defect location TDM interface
default logging Log
LED signaling CLOCK RED Blinking-Fast
debug hints Check the TDM device connected to ACCEED
12.3.35 TDM-BER3 Alarm

description Bit Error Rate of 10E-3 at TDM interface detected
alarm location TDM
default logging Log
LED signaling none
12.3.36 TDM-BER6 Alarm

description Bit Error Rate of 10E-6 at TDM interface detected
alarm location TDM
default logging Log
LED signaling None
12.3.37 TDM-LFA Alarm

description Alarm Indication Signal at TDM interface detected
default logging Log
LED signaling CLOCK YELLOW ON
A3118-X652-R67-02 290 / 297

12.3.38 TDM-LOS Alarm

description Loss of Signal at TDM/Clock interface detected
default logging log
LED signaling CLOCK RED ON
debug hints Check the TDM connection and input signal
12.3.39 TDM-RAI Alarm

description Remote Alarm Indication at TDM interface detected
alarm location TDM
default logging Log
LED signaling none
12.3.40 Temperature Alarm (desktop only)

description Temperature above critical value
defect location Equipment
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 65C environment
temperature and the device is shut down at about 80C.
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 20C.
The device is specified up to 55C environment temperature and must never be used at
higher temperatures
A3118-X652-R67-02 291 / 297

ULAF+ 13 - References ACCEED 2202 Manual
13
References
[1] ULAF+ Installation Manual (IMN) V4.2

Albis Technologies Ltd
A3118-X300-H100-*-76D1
[2] ULAF+ Installation Manual (IMN) V5.1

A3118-X300-H100-*-7618
[3] ULAF+ Technical Description (TED) V4.2

A3118-X300-H100-*-7618
[4] ULAF+ Technical Description (TED) V5.1

A3118-X300-H100-*-7618
[5] ULAF+ User Manual (UMN)

A3118-X300-H100-*-7619
[6] ULAF+ User Manual (UMN) for the Advanced Bridge and Router Module
A3118-X300-H100-*-7619
[7] Advanced bridge and router module CLI Reference Manual

A3118-X359-A2-2-7619
[8] MCU-S CLI Reference Manual

A3118-X359-A1-3-7619
A3118-X652-R67-02 292 / 297

ULAF+ 13 - References ACCEED 2202 Manual
[9] AccessIntegrator Installation Manual(IMN)

A50010-T3-U100-*-76D1
[10] AccessIntegrator System Administration Manual(ADMN)

A50010-T3-U100-*-7671
[11] AccessIntegrator Operation Manual (OMN)

A50010-T3-U100-*-7619
[12] Download Manager User Manual (UMN)

A3118-X300-H110-*-0019
[13] Ordering Information for ULAF+ access platform

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-X652-R67-02 293 / 297

ULAF+ 14 - Glossary ACCEED 2202 Manual
14
Glossary
A3118-X652-R67-02 294 / 297

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 limits the
CBS 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 the
CIR
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
Color-aware Profile compliance for each service packet is taken into account when
determining the level of compliance for each service packet.
A bandwidth profile property where a pre-determined level of bandwidth
Color-blind profile compliance for each service packet, if present, is 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 packets sent
EBS
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
E-Service Ethernet-Service (transmission of Ethernet packets)
ESMC Ethernet Synchronization Message Channel
A3118-X652-R67-02 295 / 297

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 1000 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 remote
LCT+
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 Switch
MCU-S
and GbE uplink
Management and Concentrator Unit with Carrier Grade Ethernet Switch,
MCU-CES
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
MP2MP EVC Multipoint-to-Multipoint EVC with two UNIs is different from a Point-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 for
PCL
classifying traffic
Peak Information Rate, PIR is a bandwidth profile parameter. It defines
PIR the average rate in bits/s of service packets up to which the 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 not
Precedence Hard
override the current assignment
Implies that subsequent mechanisms (switch pipeline stages) may
Precedence Soft
override the current assignment
PTP Precision Time Protocol
RMON Remote Network Monitoring
A3118-X652-R67-02 296 / 297

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 one or
Rooted-Multipoint EVC
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
SCC System Cross Connect. Connection between ACCEED units in an 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 on the
Service Multiplexing 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
Squelch output signal. For some signals (e.g. 2 Mbit/s) squelching may be
realized by means of inserting AIS, instead of shutting down the signal.
SrTcm Single Rate Two Color Mode
SSM Synchronization Status Message / Synchronization Status 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
TPID Tag Protocol Identifier, corresponds to the Ethertype of the VLAN tag
TrTcm Two Rates Three Color Mode
User Network Interface, The physical demarcation point between the
UNI responsibility of the Service Provider and the responsibility of the
Subscriber
WAN Wide Area Network
A3118-X652-R67-02 297 / 297

ACCEED Manual 2202 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACCEED Manual 2202 PDF

Uploaded by

Copyright:

Available Formats

ULAF+

ACCEED 2202 Manual Release 6.7

Important Notice on Product Safety

Copyright and Licenses

Copyright (C) Albis Technologies Ltd 2012

Technical modifications possible

5.4.4 NMS interface (10/100 Base-T) ....................................................................................... 56

8.7 Ethernet Switch Fault Management................................................................................... 157

11.2 Alarm configuration ............................................................................................................ 264

12.3.27 SOAM-LCK Alarm ..................................................................................................... 288

Figure 1-1 ESD symbol ......................................................................................................................... 16

Figure 6-10 Open window ..................................................................................................................... 91

Figure 12-1 ACCEED 2202 LEDs ....................................................................................................... 279

This chapter contains very important information such as product safety,

1.1 Representation conventions

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

1.2 Product Safety

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

1.2.1 Notes on protection against laser radiation

1.4 Device handling

Figure 1-1 ESD symbol

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

1.4.2 Inserting/ removing plug in units

1.4.3 Stacking the desktop units

1.4.4 Disposal of equipment and units

Figure 1-2 Disposal of equipment and units

1.5 Over voltage protection

BSRU BSRU ACCEED

Figure 1-3 Over voltage protection

1.5.1 Protection of a network element

2.1 ULAF+ documentation structure

ULAF+ system documents:

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

- Subrack V3 S3118-B628-A210 / -A211

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

- Ethernet over TDM inverse-multiplexer GTU4

- Subrack V3 S3118-B628-A210 / -A211

Download Manager documents:

2.2 ACCEED 2202 Manual Structure

Chapter 13 contains the complete list of references.

Chapter 14 contains the glossary

2.3 Representation conventions

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

Operation via LCT+

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

2.3.1 ACCEED manual naming conventions

Within this document to following equivalents are used:

2.4 ULAF+ System overview

Figure 2-1 ULAF+ system

Figure 2-2 Typical ULAF+ applications

2.4.1 Service Interfaces

N x 64kBit/s serial data

2.4.2 Transmission Interfaces

2.4.3 MEF Carrier Ethernet Services attributes

Distributed architecture, equipment redundancy

2.4.4 Management Systems

Figure 2-3 ULAF+ LCT+ GUI

Local Craft Terminal (LCT+)

Element Manager for AccessIntegrator

Easy Management Integration, standard protocols and interfaces

2.4.5 ULAF+ Product Range

Management and traffic aggregation units

SHDSL transmission units