Академический Документы
Профессиональный Документы
Культура Документы
A3118-X654-R620-01 2 / 398
ULAF+ ACCEED 2104 Manual
Contents
1 Notes on product safety ................................................................................................................. 13
1.1 Representation conventions ................................................................................................. 14
1.2 Product Safety ...................................................................................................................... 15
Notes on protection against laser radiation ..................................................................... 15
Notes on permitted altitude and use of protection earth .................................................. 15
1.3 EMC ..................................................................................................................................... 16
1.4 Device handling .................................................................................................................... 17
Electrostatic Sensitive Devices (ESD) ............................................................................. 17
Inserting/ removing plug in units ...................................................................................... 17
Stacking the desktop units ............................................................................................... 17
Disposal of equipment and units ...................................................................................... 18
1.5 Over voltage protection ........................................................................................................ 19
Protection of a network element ...................................................................................... 19
2 Introduction ..................................................................................................................................... 20
2.1 ULAF+ documentation structure .......................................................................................... 21
2.2 ACCEED 2104 Manual Structure ......................................................................................... 24
2.3 Representation conventions ................................................................................................. 25
ACCEED manual naming conventions ............................................................................ 25
2.4 ULAF+ System overview ...................................................................................................... 26
Service Interfaces ............................................................................................................ 27
Transmission Interfaces ................................................................................................... 27
MEF Carrier Ethernet Services attributes ........................................................................ 27
Management Systems ..................................................................................................... 28
ULAF+ Product Range ..................................................................................................... 29
3 Application overview....................................................................................................................... 32
3.1 ACCEED 2104 Overview ..................................................................................................... 33
Gigabit EFM fiber demarcation, transmission and aggregation unit ................................ 33
Technical data.................................................................................................................. 35
3.2 Typical ACCEED 2104 applications ..................................................................................... 37
Business Access .............................................................................................................. 37
Wholesale Carrier Ethernet Demarcation ........................................................................ 39
Backhaul .......................................................................................................................... 40
Utility / Campus ................................................................................................................ 41
3.3 System configurations .......................................................................................................... 42
Mechanics ........................................................................................................................ 44
HW options ...................................................................................................................... 44
4 Quick Start Guide ........................................................................................................................... 45
4.1 Introduction........................................................................................................................... 46
4.2 HW setup.............................................................................................................................. 47
ACCEED 2104 Setup ...................................................................................................... 47
Wiring ............................................................................................................................... 47
4.3 EFM link configuration .......................................................................................................... 48
LCT+ installation .............................................................................................................. 48
5 Installation ...................................................................................................................................... 49
5.1 General requirements/check list........................................................................................... 50
5.2 Power supply ........................................................................................................................ 52
Power supply to the plug in unit ....................................................................................... 52
Power supply to the desktop unit S3118-H654-E413 ...................................................... 52
Desktop unit S3118-H654-F416 with redundant Power supply ....................................... 55
5.3 Grounding concept ............................................................................................................... 57
Protective earth grounding for desktop unit S3118-H654-E413 ...................................... 57
Functional earth grounding for desktop unit S3118-H654-F416 ..................................... 57
5.4 Interfaces / pinning ............................................................................................................... 58
SHDSL interface .............................................................................................................. 58
Ethernet interfaces (10Base-T/100Base-Tx/1000Base-Tx) ............................................ 58
SFP slot interface............................................................................................................. 59
A3118-X654-R620-01 3 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 4 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 5 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 6 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 7 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 8 / 398
ULAF+ ACCEED 2104 Manual
Figures
A3118-X654-R620-01 9 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 10 / 398
ULAF+ ACCEED 2104 Manual
A3118-X654-R620-01 11 / 398
ULAF+ ACCEED 2104 Manual
Figure 11-5 Combined authentication modes: Primary local, secondary RADIUS ............................. 361
Figure 11-6 Zero Touch Provisioning principle .................................................................................... 364
Figure 12-1 ACCEED 2104 LEDs ....................................................................................................... 379
A3118-X654-R620-01 12 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
1
Notes on product safety
A3118-X654-R620-01 13 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
Information
Information gives useful notes which pertain to particular situations and specifically draw
the reader’s attention to them. Information will be highlighted in the text using an
information symbol.
Warning
Other symbols not related to product safety are defined in chapter 2.3.
A3118-X654-R620-01 14 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
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.
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.
Normal operation
Only class1 laser SFPs shall be used
Dangerous fault
The ACCEED unit corresponds to the Laser class 1 for all disturbances.
A3118-X654-R620-01 15 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
1.3 EMC
The EC declaration of conformity for the product is met when the installation and cabling is carried out
in compliance with the instructions in the ULAF+ ACCEED 2104 Manual ( 5). Where necessary,
project specific documents should be taken into account.
Deviations from the specifications or irregular installation modifications (e.g. the use of cable types with
a lower shielding mass), can lead to violations to the EC protection requirements. In such cases the
declaration of conformity will be invalidated. Responsibilities for any problems that may occur thereafter
then lie with the person responsible for deviating from the specifications.
A3118-X654-R620-01 16 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
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.
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.
A3118-X654-R620-01 17 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
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-X654-R620-01 18 / 398
ULAF+ 1 - Notes on product safety ACCEED 2104 Manual
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.
A3118-X654-R620-01 19 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
2
Introduction
This chapter gives an overview of the ULAF+ system and the product
range.
A3118-X654-R620-01 20 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
ACCEED manuals: contain all information relative to a specific ACCEED product: technical
description, installation, configuration, operation and troubleshooting instructions.
- ACCEED 1102/04 Manual
- ACCEED 1404 Manual
- ACCEED 1416 Manual
- ACCEED 2102 Manual
- ACCEED 2104 Manual
- ACCEED 2202 Manual
AccessIntegrator documents:
Documentation related to the AccessIntegrator (ULAF+ Management System (NMS)).
- Installation Manual (IMN)
The Installation Manual is intended for anyone involved in the installation and configuration
of the AccessIntegrator. It describes the procedures for installation of a new version of the
AccessIntegrator software.
- Administration Manual (ADMN)
The Administration Manual is intended to be used by anyone who configures the
AccessIntegrator for other users. It describes the tasks which must be performed in order
to guarantee trouble-free and reliable management of the network elements using the
AccessIntegrator.
- Operation Manual (OMN)
A3118-X654-R620-01 22 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
Intended for use by anyone who uses AccessIntegrator to monitor and maintain network
elements.
A3118-X654-R620-01 23 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
Chapter 2 gives an overview of the ULAF+ system and the product family.
Chapter 3 provides an overview of the ACCEED 2104 unit, describes typical applications and
system configurations and gives an introduction to the ACCEED 2104 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 2104
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 2104.
Chapter 5 gives detailed information and instructions about ACCEED 2104 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 2104
for different possible system configurations.
Chapter 6 this chapter gives detailed information and instructions about how to configure and
operate ACCEED 2104 and LCT+. It contains a description of both ACCEED 2104 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 2104 unit.
Chapter 11 describes the general information and settings of the ACCEED 2104 unit. This covers
inventory and logging information and explains how the alarm configuration is done.
Management access and synchronization options for the ACCEED 2104 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.
A3118-X654-R620-01 24 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
Information
Information gives useful notes which pertain to particular situations and specifically draw
the reader’s attention to them. Information will be highlighted in the text using an
information symbol.
Warning
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.
A3118-X654-R620-01 25 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
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.
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-X654-R620-01 26 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
Service Interfaces
Ethernet
10/100/1000Base-T
SFP’s (electrical or optical, Fast and Gigabit Ethernet)
2Mbit/s E1
G.703 unstructured, G.704 structured or fractional E1, ISDN PRI
N x 64kBit/s serial data
X.21, V.35, V.36
Synchronization
2MHz clock and 2Mbit/s
Synchronous Ethernet (SyncE)
PPS and IEEE1588v2
Transmission Interfaces
The system offers copper and fiber interfaces to utilize existing access network infrastructure.
Wire pair bonding allows for fiber like speed, quality and reliability on multi pair copper access links.
Regenerators in a cascading chain and built in remote feeding circuits extend the reach of high bit rate
services to remote locations.
Copper
ETSI/ITU-T compliant with SHDSL.bis, up to 6.4 Mbps per wire pair
up to 8 regenerators per wire pair
bonding of up to 16 wire pairs with line protection
Spectral compatibility with POTS, ISDN, HDSL, ADSL, VDSL etc.
Fiber
up to 1Gbit/s two or single fiber systems
concurrent TDM and Ethernet transmission
SFP slots allow for flexible choice of optical interfaces
sub 50ms line protection with LAG
Standardized Services
E-Line, E-LAN, E-Tree and E-Access Services
TDM Circuit Emulation Service (CES)
Scalability
10/100/1000Mbit/s User Network Interfaces (UNI’s)
per flow bandwidth profiles and SLA enforcement
up to 64 customers per shelf, thousands of customers per network
Quality of Service
`Hard`-QoS - guaranteed bandwidth profile per service
Minimum delay and jitter
Reliability
A3118-X654-R620-01 27 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
Management Systems
ULAF+ features the following servicing options:
A3118-X654-R620-01 28 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
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
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
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-X654-R620-01 29 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
BSTU4
SHDSL Termination Unit for advanced Ethernet services.
4 wire pair bonding (22.8Mbit/s)
4 port Ethernet switch (VLAN, CoS)
BSRU/BSRU+
2 wire pairs SHDSL Regenerator Unit
Up to 8 BSRU cascadable
Remote or local power feeding
ACCEED 1102
EFMC-LR (SHDSL) Ethernet Demarcation Device
1x RJ45 / 2 copper wire pair SHDSL.bis (30.6 Mbit/s)
4x RJ45 10/100Base-T ports, Carrier Ethernet switch
2x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
ACCEED 1104
EFMC-LR (SHDSL) Ethernet Demarcation Device
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
4x RJ45 10/100Base-T ports, Carrier Ethernet switch
2x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
1x Data Module Slot for X.21, V.35, V.36 (optional)
ACCEED 1404
EFMC-LR (SHDSL) Ethernet Demarcation Device with
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)
ACCEED 1416
EFMC-LR (SHDSL) Termination Unit with
Carrier Ethernet switch and bonding of up to 16 wire pairs (102.4 Mbit/s)
1x RJ45 / 4 copper wire pair SHDSL.bis (61.2 Mbit/s)
3x RJ45 10/100/1000Base-T ports, 1x SFP, Carrier Ethernet switch
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)
BOTU
Fiber Optical Termination Unit for Ethernet and TDM services
4x E1, Ethernet switch (VLAN, CoS)
2x SFP module slots
A3118-X654-R620-01 30 / 398
ULAF+ 2 - Introduction ACCEED 2104 Manual
ACCEED 2102
EFMF (optical) Termination Unit with Carrier Ethernet switch
2x SFP module slots for protected GbE or FE services
2x RJ45 10/100/1000Base-T ports
ACCEED 2104
EFMF (optical) Termination Unit with Carrier Ethernet switch
4x SFP module slots for protected GbE or FE services
4x RJ45 10/100/1000Base-T ports
4x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
1x BNC PPS 50 Ohm clock output (optional)
ACCEED 2202
EFMF (optical) Termination Unit with Carrier Ethernet switch
2x SFP module slots for protected GbE or FE services
2x RJ45 10/100/1000Base-T ports
1x RJ45 G.703 120/75 Ohm port for E1 or reference clock in/out (option)
Power over Ethernet (optional)
Interface converters
BGTU
Flexible interface converter for
Ethernet over E1 or fractional E1 and data over E1 services
1x Dataslot module for X.21, V.35, V.36
GTU4
Inverse multiplexer unit for
Ethernet services over TDM networks. Bundling of up to 4 E1
4 port Ethernet switch
EIU
Quad E1 Insertion Unit for structured or unstructured E1 emulations
services with MCU-CES
Interface Modules
Various Interface Modules
(V.35, V.36, X.21, Ethernet Bridge, Ethernet Router)
Clock and Alarm Module
A3118-X654-R620-01 31 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
3
Application overview
A3118-X654-R620-01 32 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
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.
Performance Management
Y.1731 based performance management continuously monitors SLA parameters such as Frame
Loss, Availability, Frame Delay and Frame Delay Variation with microsecond accuracy and
generates alarms if Objective Thresholds are violated, giving providers the possibility to proactively
take actions before the service is seriously degraded.
Collection of statistics on physical-, packet- and service level as well as real time graphs monitoring
service utilization allows to track the service performance, to analyze network traffic and to certify
SLA conformity.
Fault Management
Ethernet ring and linear protection as well as Link Aggregation (LAG) allow the implementation of
resilient architectures minimizing the impact of faults on the service.
Fault propagation (including AIS/RDI and Dying Gasp), link, port and service level alarms together
with extensive localization tools such as continuity check, link-trace and loopback allow to quickly
locate faults and re-establish the service in case of failures.
Synchronization options
A3118-X654-R620-01 34 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
For clock sensitive applications like mobile base station backhaul, synchronization is very important.
ACCEED 2104 offers several methods to provide an accurate clock to every customer location:
IEEE 1588v2 Precision Timing Protocol delivers protocol based clock and phase over packet based
networks
Synchronous Ethernet delivers highly accurate physical layer timing over packet based networks
2048 kbit/s / 2048 kHz 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)
SyncE / IEEE 1588v2 to 2048 kbit/s / 2048 kHz conversion
Pulse per second (PPS) input and output for phase synchronization
Management
ACCEED 2104 offers a rich variety of management solutions to fulfill the needs of each customer:
intuitive and easy to operate graphical SW applications
standard compliant protocols
easy to integrate into 3rd party solutions
fully automated Zero Touch Provisioning
The management access can be local and from remote via inband or dedicated DCN connection:
CLI console, Telnet and SSH
Local Craft Terminal LCT+ (GUI)
SNMP (Standard MIBs and private ACCEED MIB)
NETCONF
DHCP, TFTP, SCP
Syslog
MetroIntegrator NMS (with SOAP / REST Northbound Interface)
Technical data
S3118-H654-E413 (Eth)
S3118-H654-F416 (Eth+G703+PTP+SyncE)
Power Consumption
Desktop version 15W (typical)
(Eth)
Interfaces
Network Interface (UNI/NNI)
4x SFP slot for FE/GbE
4x RJ45 10/100/1000Base-T
TDM (optional)
A3118-X654-R620-01 35 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
A3118-X654-R620-01 36 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
1. E-LAN service
Port based Ethernet private LAN (EP-LAN)
VLAN based (EVC identified by VLAN-ID) Ethernet virtual private LAN (EVP-LAN)
2. E-Line service
A3118-X654-R620-01 37 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
3. E-Tree service
Port based Ethernet private Tree (EP-Tree)
VLAN based (EVC identified by VLAN-ID) Ethernet virtual private Tree (EVP-Tree)
4. E-Access service
Port based Ethernet private Access Service (EP-ACCESS)
VLAN based (EVC identified by VLAN-ID) Ethernet virtual Access Service (EVP-ACCESS)
A3118-X654-R620-01 38 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
ACCEED 2104 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.
In wholesales applications ACCEED 2104 can be used to provide demarcation and 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 2104.
A3118-X654-R620-01 39 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
Backhaul
ACCEED 2104 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..
A3118-X654-R620-01 40 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
Utility / Campus
At locations where fiber links are available, ACCEED 2104 can be used to set up high speed campus
connections as indicated in the following example. These units can be used at for different types of
protection. It is possible to reach up to 2 Gbit/s with Link aggregation or 1:1 linear protection path. The
quickest 1+1 protection can be used, too. This solution can transport Ethernet and Circuit Emulated
Services.
A3118-X654-R620-01 41 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
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
A3118-X654-R620-01 42 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
Service:
A endpoint to endpoint connection with defined service attributes, like dedicated bandwidth,
priority (QoS) …
A3118-X654-R620-01 43 / 398
ULAF+ 3 - Application overview ACCEED 2104 Manual
Mechanics
HW options
10/100/1000 bT
TDM G.703 E1
IEEE 1588
Ethernet
Ethernet
part number mechanic
PTP,
S3118-H654-E413 Desktop 4 4
S3118-H654-F416 Desktop 4 4 4
Table 1 ACCEED 2104 HW options
The following ACCEED 2104 accessories are available: (All fiber connectors are LC)
A3118-X654-R620-01 44 / 398
ULAF+ 4 - Quick Start Guide ACCEED 2104 Manual
4
Quick Start Guide
This section gives step by step instructions to quickly set up a typical EFM
link using ACCEED 2104 and LCT+. The aim of this section is to get
quickly to a first running configuration and familiarize with ACCEED 2104.
You will also find the links to chapters where you get the detailed
information.
A3118-X654-R620-01 45 / 398
ULAF+ 4 - Quick Start Guide ACCEED 2104 Manual
4.1 Introduction
This chapter demonstrates how to set up an EFM link from scratch using ACCEED 2104, with the help
of an exemplary configuration.
The exemplary EFM link consists of 2 ACCCED 2104 desktop units connected via optical fiber.
A3118-X654-R620-01 46 / 398
ULAF+ 4 - Quick Start Guide ACCEED 2104 Manual
4.2 HW setup
ACCEED 2104 Setup
Connect the desktops to a power source (the green power LED of the desktop unit must turn ON)
ACCEED 2104 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.
Wiring
Connect the wires as indicated by the picture Figure 4-2
By default all interfaces (P1...P4, SFP1…SFP4 and NMS) are deactivated, i.e. the alarm
LEDs are always turned off. To check the correct cabling some on site configuration is
necessary. See chapter 4.3.1.
A3118-X654-R620-01 47 / 398
ULAF+ 4 - Quick Start Guide ACCEED 2104 Manual
LCT+ installation
In order to perform the configurations necessary to setup the EFM link the LCT+ is required.
A3118-X654-R620-01 48 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
5
Installation
The aim of this chapter is to facilitate the installation of ACCEED 2104 for
a variety of possible system configurations
A3118-X654-R620-01 49 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The following tasks must be carried out for each system component before/during installation:
ACCEED 2104 is the Gigabit Ethernet First Mile Fiber (EFMF) demarcation, transmission and
aggregation unit of the ULAF+ system for active fiber Carrier Ethernet Access applications. Please refer
to 3.2
Figure 5-2 ACCEED 2104 desktop unit with TDM & IEEE1588v2
LCT+
LCT+ is the Local Craft Terminal used to configure and operate the ULAF+ devices. LCT+ is a Java
based SW application. For more details on the LCT+ please refer to 6.2.
A3118-X654-R620-01 51 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Redundant local
Local power
supply with
supply with
48/60 VDC
Part number Version Mechanic
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-X654-R620-01 52 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Modifications to the type of supply and grounding may only be made by trained personnel.
A3118-X654-R620-01 53 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
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.
In case of utilization of a DC power source (<100V) the power-fail signaling can be
suppressed using the LCT+.
Not applicable
5.2.2.3 Set the ACCEED 2104 power supply source via jumpers
Not applicable
A3118-X654-R620-01 54 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
5.2.2.4 Fuse F3
The power supply is protected with fuses. More details are included in Table 4.
The fuses have a protective function and must be replaced by fuses with exactly the same
! electrical specifications.
Power supply connection is via a terminal blocks connector. The conductor cross section of the wire
must be at least 0.75 mm2.
Power 1 and Power 2 can be connected in parallel to the same source so that the ACCEED 2104
does not trigger an alarm. You can optionally disable the power supply monitoring function for the
unused power connection in the LCT.
A loss of power or dropping below of a threshold of about 36 VDC triggers an "Alarm".
The fuses have a protective function and must be replaced by fuses with exactly the
! same electrical specifications.
A3118-X654-R620-01 56 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The ACCEED 2104 unit (S3118-H654-E413) must be grounded if it operates with AC power supply
and the altitude above sea level is >2000m. The conductor cross section of the grounding cable must
be at least 0.75 mm2.
This symbol, located on the type label must also be made invisible (e.g. covering with
adhesive paper).
The grounding of the ACCEED 2104 desktop can be made with the main earth terminal
(Figure 5-5, ) on the rear panel of the device or by opening the desktop and
connecting the ground wire to the local power supply earth terminal (
Figure 5-4, ).
Figure 5-5 Rear panel of the ACCEED 2104 with main terminal for protective earth grounding
Functional earth grounding for desktop unit S3118-H654-F416
The rear panel of the ACCEED 2104 unit (S3118-H654-F416), including redundant power supply is
reported below. The terminal blocks PWR1 and PWR2 include a ground terminal. It is recommended
to use this terminal for a functional earth grounding. The conductor cross section of the grounding
cable must be at least 0.75 mm2.
Figure 5-6 Rear panel of the ACCEED 2104 with terminal for power and functional earth grounding
A3118-X654-R620-01 57 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Figure 5-7 ACCEED 2104 desktop front panel interfaces and LEDs
summary LEDs:
power (green)
1 2 LCT serial RS232 interface
alarm (red/yellow)
maintenance (yellow)
Network Management System Ethernet
3 4 4x G.703 Interface
interface
5 1 PPS clock in/out (backside) 6 4x 10/100/1000Base-T Ethernet port
7 4x SFP port 8 Alarm interface - 2x in, 2x out (backside)
9 1x ToD in/out (backside)
SHDSL interface
Not applicable
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.
A3118-X654-R620-01 58 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
If necessary, send and receive data can be automatically swapped by the Ethernet Port
(Configuration: Auto MDI/MDI-X or fix MDI or fix MDI-X).
A3118-X654-R620-01 59 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Each 2 MHz or G.703 clock interface can be configured to 75 or 120 impedance via the NMS.
The clock interface is available on ACCEED 2104 models with the SyncE option only
(see Table 1).
A3118-X654-R620-01 60 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Alarm interface
The ACCEED 2104 unit (S3118_H654-F416) is equipped with a RJ45 connector, providing an Alarm
interface for 2 inputs and 2 outputs. The RJ45 connector is located on the backside.
Pin
Connector Contact name Description
assignment
1 OutCon_1a Alarm output 1 / Pin a (current-free closed)
2 OutCon_1b Alarm output 1 / Pin b (current-free closed)
3 OutCon_2a Alarm output 2 / Pin a (current-free open)
4 OutCon_2b Alarm output 2 / Pin b (current-free open)
5 InCon_1a Alarm input 1 / Pin a
6 InCon_1b Alarm input 1 / Pin b
7 InCon_2a Alarm input 2 / Pin a
8 InCon_2b Alarm input 2 / Pin b
CASE Ground Common shield
Table 11 Pin assignment of the Alarm interface
ToD interface
The ACCEED 2104 unit (S3118_H654-F416) is equipped with a RJ45 connector, providing a Time of
Day serial signal and an 1 PPS pulse signal. Both signals can be input or output. The PPS pulse
signals the rising edge of the clock. The ToD serial signal contains a timestamp. The pinning is
according to G.703 Amd.1. The RJ45 connector is located on the backside.
A3118-X654-R620-01 61 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Pin
Connector Contact name Description
assignment
1 Reserved
2 Reserved
3 1PPS_io_a 1 packet per second signal in/out pin -
4 GND Ground
5 -
6 1PPS_io_b 1 packet per second signal in/out pin +
7 TOD_io_a Time of day signal in/out pin -
8 TOD_io_b Time of day signal in/out pin +
CASE Ground Common shield
Table 13 Pin assignment of the ToD interface
Pin
Connector Contact name Description
assignment
A3118-X654-R620-01 62 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 63 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 64 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 65 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
ACCEED can also be managed with the network management system MetroIntegrator
Version 1.0 and higher. Refer to [9] for information regarding the installation of
MetroIntegrator.
System requirements
The following minimum system requirements must be met:
HW:
CPU: Pentium 4 (2 GHz) or Athlon XP (2000+) processor or higher
Memory: 1GB RAM
Operating system:
Windows 2000
Windows XP
Windows Vista
Windows 7
For all Windows operating systems it is advisable to always use the newest available service pack.
Graphics:
at least 1024x768 resolution
Connectivity:
Serial Interface or USB with external “serial to USB” converter
10/100BaseT Interface
Setup_LCT+_V3.20.exe
A3118-X654-R620-01 66 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
1 Double click on the setup icon. The following installation dialogue is displayed
2 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).
The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. If LCT+ is
installed, customer specific extensions (Add-ons) can be installed optionally. The selection occurs at
this stage of the installation. The installer window contains the following information:
list of available components to install (1)
A3118-X654-R620-01 67 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
If “LCT+ Add-on” has been selected in the previous screen, you can select the source path
5 from where customer specific extensions are copied. Then press `Next >` to continue.
If “LCT+ Add-on” was not selected this screen will not appear
A3118-X654-R620-01 68 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
7 Press `Install` to complete the installation or `Cancel` to abort the operation.
A3118-X654-R620-01 69 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
2 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).
A3118-X654-R620-01 70 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The presence of a LCT+ SW has been detected. Before proceeding with the installation the former
installed version has to be removed. It is possible to abort the update procedure and keep the current
LCT+.
3 Press `Next >` to continue with the upgrade (or `cancel` to abort the installation).
The installer allows to setup both the LCT+ and the legacy equipment LCT or just the LCT. If LCT+ is
installed, customer specific extensions (Add-ons) can be installed optionally. The selection occurs at
this stage of the installation. The installer window contains the following information:
list of available components to install (1)
A description of the selected component (2)
The space required for the installation (3)
A3118-X654-R620-01 71 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
If “LCT+ Add-on” has been selected in the previous screen, you can select the source path
6 from where customer specific extensions are copied. Then press `Next >` to continue.
If “LCT+ Add-on” was not selected this screen will not appear
A3118-X654-R620-01 72 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
You can choose if shortcuts for LCT+ and/or LCT should be created on your desktop.
8 Press `Install` to complete the installation or `Cancel` to abort the operation.
A3118-X654-R620-01 73 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
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.
Boot up
ACCEED 2104 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.
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
A3118-X654-R620-01 74 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The serial interface runs at the speed of 115200 Bit/s. The PC interface is automatically
set up. No manual configuration is necessary.
A3118-X654-R620-01 75 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
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). Both IPv4 and IPv6 are supported for the NMS
interface.
The IP address configuration can be done either statically in NMS port configuration or dynamically
using DHCP server. Please note that DHCP is only supported for IPv4.
When the configuration is done statically, it is required to configure the IP address and netmask (prefix
length) of the NMS port and the Default Gateway of the connection.
For IPv6 addresses, notation in 8 groups of 4 hexadecimal digits separated by colons ( : ) according to
RFC 5952 is supported. Leading zeroes in a group can be omitted, multiple groups of zeroes can be
replaced by two colons. Example: 2001:db8:0:0:aaaa::1 .
A3118-X654-R620-01 76 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The Default Gateway parameter is common for the NMS and in-band port and is located in:
Board\Local\Management Access
When the configuration is done dynamically, it is required to configure the DHCP parameters (IP
Configuration and DHCP options).
A3118-X654-R620-01 77 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The DHCP discover will be sent periodically. It can be manually invoked by pressing the DHCP Renew
button.
LCT connections to the network element via NMS port or in-band port utilize a TCP
connection (Port 2101).
A3118-X654-R620-01 78 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 79 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
VLAN tagging for the management channel can be different for each switch port.
“-“ means management access is not allowed through the corresponding port.
“Untagged” means there is no VLAN tag for inband management on that port,
“Management VLAN” is a single VLAN tag (according to config in the “Inband” folder)
“Management VLAN And Tunnel VLAN” is double tagged inband management.
Please note that if VLAN tags are used, they have to be configured in the VLAN database.
In the double tagged case, the tunnel VLAN is the primary VLAN in which the
corresponding port has to be member.
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 port or in-band port utilize a TCP
connection (Port 2101).
A3118-X654-R620-01 80 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The configuration of Host Name and Domain is optional and not necessary for DNS to
work. Host name is used for example in Syslog messages.
A3118-X654-R620-01 81 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 82 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
A3118-X654-R620-01 83 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
5.8.3.5 Syslog
Syslog enables the ACCEED 2104 to send all log entries via the syslog protocol to 8 different Syslog
remote hosts. 3 different categories are selectable for each remote host entry.
5.8.3.6 Authentication
Authentication describes a method to authorize users with centralized authentication database servers
(via e.g. RADIUS). Please see further details in 11.3.5.1.
SCC connections
Not applicable.
Not applicable.
Not applicable.
A3118-X654-R620-01 84 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
Time settings
A real time clock is available on ACCEED 2104. This can be set automatically via NTP-UNICAST, MCU
system bus time or can be configured manually.
`ULAF` mode: the ACCEED 2104 plugin requests its time from the central MCU/-S/-CES
or from the LT
`Manual` mode: the button `Set Date and Time` is available. Pressing this button a pop up
dialogues opens, which permits to manually set date and time (note: the pop up dialogue
already contains the current date and time of your PC/Laptop).
`NTP Unicast` mode: the IP address of a Time Server must be configured. The button
`Synchronize with server` is available to force immediate synchronization with the NTP
server.
`PTP` mode: the real time clock is copied from the PTP clock (ACCEED 2104 PTP only)
A3118-X654-R620-01 85 / 398
ULAF+ 5 - Installation ACCEED 2104 Manual
The yellow maintenance LED and the maintenance field on the LCT+ status bar indicate
the activation of any of the maintenance functions.
Loopback
ACCEED 2104 features the following loopbacks:
5.9.1.1 Loopback 1a
Not applicable.
5.9.1.2 Loopback 3a
Not applicable.
BER test
Not applicable.
Trap suppression
During the execution of maintenance activities it may be necessary to prevent the network management
system from being flooded by alarm information. ACCEED 2104 therefore offers the possibility to disable
the generation of traps.
Trap suppression is described in 9.1.
A3118-X654-R620-01 87 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
6
Configuration and operation
A3118-X654-R620-01 88 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
The configuration of the management access is described in the installation chapter. Refer to 5.8.2.
The OMI SNMP and the MCU have no telnet or SSH client. ACCEED units in such sub
racks can be accessed via in band management
Token mechanism
All ACCEED units are accessible through Remote LCT (TCP 2101), SNMP, NETCONF (SSH), and
CLI (Telnet or SSH). Some of them are accessible via serial LCT or serial CLI. To prevent
inconsistency in the database only one write access user at a time is allowed. Therefore a write token
mechanism is implemented working as follows:
- If write token is available, the user asking for the token gets write access rights. All following
users asking for the write token get just read access rights
- The user with the write access rights returns the token, when quitting his session.
The behavior of getting write access via the different access methods:
- LCT+ asks for the write token at any user interaction
- LCT+ releases the write token, when the session is disconnected or after 30 minutes without a
user interaction
- CLI asks for the write token, anytime during the active session
- CLI releases the write token, when the CLI session is disconnected or the CLI timeout is
reached (automatic logoff after 1..60 minutes)
- SNMP and NETCONF sessions do not ask for a write token
A3118-X654-R620-01 89 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
6.2 LCT+
Introduction
The Local Craft Terminal (LCT+) is a Java based software application which can be used to manage
the ULAF+ system either locally (via serial interface) or remotely (via a TCP connection over a
dedicated network or in-band).
The LCT+ Graphical User Interface (GUI) has been designed to support the user allowing an intuitive
and easy to learn management of the ULAF+ network elements.
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
A3118-X654-R620-01 90 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
Start the ULAF+ LCT+ either by double clicking the ULAF+ LCT+ shortcut on the desktop or via the
Start menu item “ULAF+ LCT+” in StartProgramsAlbis TechnologiesLCT.
After the Albis Technologies Splash Screen, the following window will be opened:
Choose which interface has to be used to establish a connection to the network element:
COM (serial interface)
o The ‘COM Port’ which is used by LCT+ must be selected from drop-down list
TCP interface
o A valid IPv4 or IPv6 address of the network element (NE) must be entered. For IPv6
addresses, notation in 8 groups of 4 hexadecimal digits separated by colons ( : ) according to
RFC 5952 is supported. Leading zeroes in a group can be omitted, multiple groups of zeroes
can be replaced by two colons. Example: 2001:db8:0:0:aaaa::1 .
o Options for the connecting to the NE directly or through a Portserver
`OMI SNMP/MCU/NE`: the LCT+ connects directly to the NE’s IP
`Portserver`: the LCT+ connects to the portserver’s IP, which is connected to the NE
through the serial interface. For this option the TCP port must be entered.
o Optionally a SOCKS5 proxy can be used, if the TCP port 2101 is blocked, e.g. by a firewall.
The proxy uses the southbound TCP port 2101 and a northbound TCP port, that can be
defined individually, e.g. 1080. The LCT+ communicates via the northbound TCP port with the
proxy and forces it to use the southbound TCP port 2101 through the SOCKS5 protocol.
The portserver option applies to legacy ULAF+ equipment, without Ethernet connectivity
A3118-X654-R620-01 91 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
Other usernames may be used if a remote authentication service such as RADIUS is enabled (
11.3.5.1).
A3118-X654-R620-01 92 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
The title bar is described in 6.2.4, the menu bar is described in 6.2.5 and the status bar is
described in 6.2.6.
A3118-X654-R620-01 93 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
Title bar
The title bar of the LCT+ windows provides the following information:
Connectivity (COM port or IP address)
Slot number of the actual unit
Username(Administrator or Maintenance)
Version of the LCT+
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:
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 prevent an accidental reset of all device configurations, the user is requested to confirm this
command.
To prevent an accidental reset of all device configurations, the user is requested to confirm this
command.
LCT+ automatically detects disconnections (e.g. cable pulled out) and notifies the user by
a pop up window.
A3118-X654-R620-01 95 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
The `About` item delivers version and copyright information about the LCT+ application
Status bar
The LCT+ status bar contains the following information.
A3118-X654-R620-01 96 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
1. Progress bar
The progress bar informs about the state of data synchronization between LCT+ and the
connected unit.
`Idle` indicates that currently no data is exchanged/pending between LCT+ and network element.
During data transfer the progress bar indicates the types of data being exchanged as well as a
percent indication of the progress.
2. Preview
The Preview field indicates whether the LCT+ is in `preview mode` (display of a generic virtual line
model composed of a LT array and a NT array) or not (display of units physically connected to
LCT+). The preview mode is useful to configure devices, which are not yet physically available (for
instance to configure NT Ethernet parameters, before it is connected to the LT). More information
about the preview mode can be found in 6.6.3.
In preview mode the preview field of the status bar turns blue as indicated by the following picture.
A single left click on this field toggles the preview mode like a button.
3. Token
The token state indicates whether the LCT+ has the write access permission. Since the system
allows multiple user access to the network elements (for example more than one LCT+ connection
or LCT+ and MetroIntegrator), a mechanism to prevent concurrent write access has been
implemented.
If LCT+ doesn’t have the write permission (token state is red), it is not possible to
change configurations, because another user is connected to the device (via LCT+ or
AccessIntegrator).
The write access will be automatically granted (token state green), as soon as the
concurrent access session is terminated (other user closed the connection to the
network element).
If no user interaction is taken for 30 minutes the LCT+ releases the write token and
change to the yellow token state. Unlike an automatic logout all user changes are still
available, but need the write permission again to be applied.
4. Alarm
The alarm state shows the alarm summary of the connected device. A single left click on this field
shows all alarms in one list (sets the Tree path to the root and the table section to Fault/Alarms).
The color indication corresponds to the alarm LED of the unit in the following way:
Red alarm state indicates the presence of a critical alarm.
Orange alarm state indicates the presence of a major alarm.
Yellow alarm state indicates the presence of a minor alarm.
Green alarm state indicates the presence of a warning.
Gray alarm state indicates the absence of alarms.
5. Maintenance
A3118-X654-R620-01 97 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
The maintenance state shows the current maintenance state of the connected device. This
indication corresponds to the maintenance LED of the unit. A single left click on this field shows
the origin of the maintenance state (path: Board/Local/Maintenance, Tabs: Fault/Maintenance)
A yellow maintenance state indicates that a maintenance function is currently active. More
information about maintenance indication can be found in 5.6.
A3118-X654-R620-01 98 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
The (green) control area is located in the upper left corner of the work area and contains the following
dialogues.
It contains 5 tabs:
Tree
Connection
User Management
Download
SCC FW Sync
Tree
The tree tab contains the structure of the network elements data model. This is a representation model
of all network element parameters (configurations, inventory, alarms, performance counters …). The
structure is represented as a `tree`. The tree area itself doesn’t contain any parameters but shows the
hierarchical structure of the grouped parameters.
It is possible to navigate the structure expanding and collapsing the groups with the mouse or the
cursor. Selecting a folder in the tree area changes all contents of the table area with the corresponding
parameters. The handling is very similar to the windows explorer: groups are like folders, parameters
like files.
A3118-X654-R620-01 99 / 398
ULAF+ 6 - Configuration and operation ACCEED 2104 Manual
Ethernet
This group contains layer 2 parameters for the local switch with 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)
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:
Connection
The connection dialogue is described in 6.2.2.
User Management
The user management dialogue permits to change the password the two local users (Administrator
and Maintenance).
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.
Download
The download dialogue is described in 6.8
The (blue) view area is located in the upper right corner of the work area and contains the following
views.
Ethernet View
The Ethernet view is a representation of the EFM link. It shows a logical representation of the EFM
unit. Functional blocks and interfaces of the unit are displayed. These are colored depending on
corresponding alarms (green: warning, yellow: minor alarm, orange: major alarm, red: critical alarm).
It is possible to directly jump to the corresponding management area of the tree and
table areas (see 6.3.1 and 6.5) by clicking on the corresponding functional block or
interface.
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.
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)
The table area is linked to the tree area. The parameters displayed in the table panels correspond to
the data structure selected in the tree area as demonstrated by the following example:
Example
To enable Ethernet Port `P1`on the LT device:
first select the corresponding parameter on the tree view: Ethernet/Switch Local/LAN Ports/P1
(or click on `P1` in the Ethernet view).
then select the Configuration tab and the ACCEED 2104 tab
enable Port 1
finally click on `Apply`
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.
Fault: Alarms
The alarm table displays the alarms of the selected structure group / element. For each alarm the
path in the data structure, the alarm location, the alarm state and the alarm severity are shown.
At the bottom of the table an Alarm Filter is present. This can be used to select which alarm
priorities should be displayed. By default the filter is set to `All Alarms`.
The Alarm Log shows the timestamp of the Alarm change, the severity, the device where the
alarm occurred, the alarm state transition and the path in the tree area.
The Alarm Log can be locally saved as text or pdf file on the PC where the LCT+ is running.
It is possible to configure, the alarms stored in the Alarm Log. See 11.2.2
Fault: Maintenance
The Maintenance LED and Maintenance State of the LCT+ indicates, that the ACCEED 2104 has a
maintenance condition.
By clicking on the yellow maintenance indicator or selecting Board/Maintenance and selecting
FaultMaintenance, the reason for the maintenance condition is displayed (e.g. loop state).
Fault: Ping
The ACCEED 2104 configuration table contains all configuration and inventory parameters of
ACCEED 2104. The table contains both editable fields and read only fields.
Configuration parameters changed in the table are marked in blue (as shown in Figure 6-26). The
number of configuration changed in the table is displayed in the `Apply` button (in brackets).
Configuration: Summary
The summary configuration table contains a summary of all configuration changes which have not
yet been applied. This allows checking the configuration before it is transferred to the network
element. In particular the summary table can be used together with the `Load Configuration`
function described in 6.6.2. After the configuration has been loaded from a file, the summary
table displays all configuration changes stored in the file. It is easy to get direct access to the
changed parameters in the summary table.
Plausibility Conflicts are shown in the color orange. As long as the conflicts are not resolved
manually, the configuration cannot be applied to the unit.
These plausibility conflicts may also occur, if a new NT is connected that differs from the port
scheme stored in the database. Typically this happens if e.g. an ACCEED 1416 LT was connected
to an ACCEED 1416 and is now connected to an ACCEED 1104 instead (as a replacement). This
conflict can be resolved by clicking on “Match Capabilities”.
Every time the “Apply” button is clicked, the configuration is written to the device and the summary
table is deleted.
Performance: Statistics
Performance: Utilization
Utilization provides information on data rates and utilization of a port or service and displays it in a
graph.
The ACCEED built in Service Activation Testing (SAT) feature allows evaluating layer 2 key
performance figures for a service that is planned to be implemented.
For more information please refer to 9.3
Search
The LCT+ Search function can be helpful to search for parameter locations in a tree. All parameters
and parameter descriptions are searched for a given keyword. From the search results it’s possible to
jump directly to the corresponding location in the tree.
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.
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. `ACCEED 2104` and click on the right arrow button ().
It is also possible to add / remove items by right clicking on parameters:
The creation of the configuration file can be aborted at any time (`Cancel` button).
The choice of parameters to be transferred to the configuration file can be reset with the `Reset`
button.
The file is created by clicking on the `Save` button, opening the save file dialog. To complete the
creation of the configuration file, a name must be entered in the file name field. Optionally the store
path may be changed.
Load Configuration
The command `Load configuration` allows to transfer the configurations stored in a *.ucx file to a
network element.
The command is also available via the control sequence (Ctrl+L)
First the configuration file needs to be opened. It can be selected by double clicking in the open file
dialog.
Once the configuration file has been selected, the Load Configuration window is opened. This panel
permits to define which parameters of the configuration file will be transferred to the network element.
The window is vertically divided in two parts:
The left part of the window corresponds to the configuration data stored in the configuration file. The
window contains the data structure of the configuration file in a tree format (the same format used
in the tree area). A green checkmark on a configuration parameter or a configuration node indicates
that the configuration parameter respectively the configuration node will be transferred to the
network element.
The right part of the window corresponds to the network element. The window contains the data
structure in a tree format (the same format used in the tree area). The configuration parameters /
nodes marked with a green checkmark will be transferred to the configuration file and the grayed
out configurations / nodes remains unchanged.
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.
Preview Mode
Not applicable.
Preferences
This command opens a popup window containing LCT+ preferences and information.
The command is also available as control sequence (Ctrl+E)
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.
Confirmation
- Clear Alarm Log
- MAC Table Flush
- Show prohibited parameters in ‘Set To Default’
- Start BERT
- Match Capabilities
- Save MCU-S/MCU-CES Switch Configuration
Some LCT+ operations result in deleting data without any `undo` possibility. These operations therefore
generate popup warnings. The command is only executed once the user confirms the intention to
proceed.
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
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).
- LCT+ Log
The LCT+ Log is a system log file containing a trace of the information exchanged between
LCT+ and the network elements. This file has debugging purpose and can be used to analyze
management sessions.
By default the file is located on the user application data directory. A different location can be
defined.
Export
CLI Modes
The CLI groups its commands to three different modes, to separate tasks. These modes are “Exec“,
“Privileged (Exec)“ and “Configuration“. Each mode supports exclusive commands, which cannot be
executed in the other modes. The CLI Prompt signals the mode entered.
The following table describes the modes and prompts.
CLI Control
CLI Access
The CLI can be accessed via the following paths:
Serial interface (115200 baud, data=8, no parity, stop=1)
Telnet
SSH V2 (Secure Shell)
Indirect via MCU-S and MCU-CES
Press Connect
Username:
Username:
Other usernames than “Administrator” or “Maintenance” may be used if a remote authentication service
such as RADIUS is enabled ( 11.3.5.1).
Start on a command prompt (e.g. DOS box or shell) the required communication software telnet or
secure shell (SSH) with the Management IP of the MCU-S/CES. After the TCP/IP connection (and the
encryption) is established the MCU-S/CES CLI starts up. Enter User Administrator and the
administrator password of the MCU-S/CES (default: UlafPAdm).
(ULAF+ MCU Switching)
User:Administrator
Password:********
(ULAF+ MCU Switching) >
Show all devices inside the subrack that are available for CLI connections:
(ULAF+ MCU Switching) >connect info
ACCEED1416>
Token
Thus no conflict with other CLI or LCT+ sessions may occur a write token mechanism is implemented.
The ACCEED Firmware is the owner of the token and gives it to the first application requesting it. The
application must release the token, when it has finished its tasks. Here is an overview how the
components of the ULAF+ Management react:
If the write token is requested but not available the following Error message is printed:
When entering the configuration mode the write token is requested. If it is not available it enters with
read-only rights. These rights are signaled in the command prompt
While in configuration mode the CLI tries to catch the token anytime. So if an application like LCT+
releases the write token, the CLI captures the token instantly and is able to perform write actions with
additional commands or mode changes.
User Management
The primary User for login can be Administrator or Maintenance. The Maintenance user is restricted to
the Exec level.
CLI Prompt
The CLI Prompt can be configured individually at Board\Local\Management Access\CLI\Prompt
The Prompt has up to 200 characters. The first 30 characters are displayed.
CLI Navigation
The ACCEED is based on data models to configure any of the parameters. This structure is equal to
the structure of the LCT+. The navigation paths are the same as are the names of the Parameters.
Please note that the Spaces in the Names of LCT+ parameters are replaced by hyphens, e.g. “Low
Bandwidth Alarm Threshold” = Low-Bandwidth-Alarm-Threshold.
To enter the Configuration mode (Navigation Tree)
The config mode is shown in the prompt with a “(config)” suffix. Get help of the available commands
and parameters by typing “?”. It will create the following output:
ACCEED2104(config)# ?
Configure commands:
default Set all parameters in this folder to default
detail Display parameters in this folder
exit Goto to parent folder / Exit from configuration mode
help Description of the interactive help system
logout Terminate current CLI session
match-capabilities Match capabilities on this device
ping Ping a remote host
preview-mode Enable or disable the preview mode
pwdp Print working data model path
root Navigate to the root of the data model
show Show running system information
==============================================================================
/
------------------------------------------------------------------------------
Aggregation / S3118-D644-E126
Ethernet / S3118-D644-E126
CES-IWF / S3118-D644-E126
Board / S3118-D644-E126
The first section shows all commands that are available (ending by the ========= border). The
second section divided in 2-4 parts separated by ------------------.
The first part shows the actual navigation path, e.g. /Aggregation/EFM-Link/[A]
The second shows the subdirectories at this navigation path.
The third shows the available actions at this navigation path. It equals the location dependent Buttons in
the LCT+.
Navigate through the tree by typing the Names of the subdirectories and press enter. With the <TAB>
you can auto-complete the Names. The successful change of the path is shown in the prompt by
displaying the new subdirectory in the prompt directly behind the config suffix. The full path of the actual
position in the tree can be printed by using the ‘pwdp’ command.
ACCEED2104(config)# Ethernet
ACCEED2104(config-Ethernet)# Switch-Local
ACCEED2104(config-Switch-Local)# LAN-Ports 1
ACCEED2104(config-LAN-Ports/P1)# VLAN
ACCEED2104(config-VLAN)# Ingress
ACCEED2104(config-Ingress)# pwdp
/Ethernet/Switch-Local/LAN-Ports/P1/VLAN/Ingress
If parameters of a virtual device are displayed, the status [preview] is added to the prompt:
ACCEED2104(config)# Ethernet
ACCEED2104(config-Ethernet)# Switch-EFM-NT 2
ACCEED2104(config-Switch-EFM-NT/[B])[preview]#
This mode equals the preview mode in the LCT+. Its use is to pre-configure remote devices before
attaching them to the network.
The command “exit” moves to the parent directory and in case of the root, it leaves the configure mode.
ACCEED2104(config-Switch-EFM-NT/[B])[preview]# exit
ACCEED2104(config-Ethernet)# exit
ACCEED2104(config)# exit
ACCEED2104#
The following example shows all available sections and parts. The second column of this tabular view is
used for detailed description or attributes. In case of subdirectories it contains “/”, in case of Actions the
signal word “Action”, in case of Parameters the Access rights (RW = modifiable, RO = Read only).
ACCEED2104(config)# Ethernet
ACCEED2104(config-Ethernet)# Switch-Local
ACCEED2104(config-Switch-Local)# ?
Configure commands:
default Set all parameters in this folder to default
detail Display parameters in this folder
CLI commands
QoS / S3118-D644-E126
EVC / S3118-D644-E126
Protection / S3118-D644-E126
Policing / S3118-D644-E126
Mirroring / S3118-D644-E126
SAT / S3118-D644-E126
SOAM / S3118-D644-E126
------------------------------------------------------------------------------
MAC-Table-Flush Action: Flushes all entries in the MAC table Actions
------------------------------------------------------------------------------
VLAN-Mode RW: Defines the VLAN mode of the switch
Learning-Mode RW: Defines the learning mode of the MAC table
MAC-Table-Aging-Time RW: Timeout for MAC table entries
Number-Of-Allowed-MAC-Addresses RW: Number of allowed MAC addresses in the ...
Maximum-Frame-Size RW: Defines the maximum receive and transmit size...
Parameters
LAN-Ports-Power-Save RW: Automatically reduces the signal amplitude (f...
Random-Early-Discard-(RED) RW: Enables random tail-dropping of frames to av...
Active-LFP-Groups RO: State of all LFP groups
RMON-Counters RO: Defines the counting mode of port RMON counters
Transmit-Queue-Counters RW: Defines the counting mode of port transmit qu...
Ingress-Policy-Counters RW: Defines the counting mode of ingress policy c...
Egress-Policy-Counters RW: Defines the counting mode of egress policy co...
Ingress-Metering-Counters RW: Defines the counting mode of ingress metering...
Egress-Metering-Counters RW: Defines the counting mode of egress metering ...
ACCEED2104(config-Switch-Local)#
Viewing Parameters
The command “detail” returns all Parameter Names at the current Navigation Path location and their
values
ACCEED2104(config-Switch-Local)#
ACCEED2104(config-Switch-Local)# detail
VLAN-Mode Unaware
Learning-Mode Automatic
MAC-Table-Aging-Time 300-s
Number-Of-Allowed-MAC-Addresses 16
Maximum-Frame-Size 1522-Bytes
LAN-Ports-Power-Save false
Random-Early-Discard-(RED) false
Active-LFP-Groups
LFP-Group-A false
LFP-Group-B false
LFP-Group-C false
LFP-Group-D false
LFP-Group-E false
RMON-Counters Bytes-And-Packets
Transmit-Queue-Counters Bytes-And-Packets
Ingress-Policy-Counters Bytes-And-Packets
Egress-Policy-Counters Disabled
Ingress-Metering-Counters Bytes
Egress-Metering-Counters Bytes
ACCEED2104(config-Switch-Local)#
Setting Parameters
There are different types of parameters. They are Strings, Integers, Enums and Bit-Arrays.
To find out which Parameters are configurable (e.g. number of characters, Integer range, List of enum
items and Bit patterns) type the parameter name and use the “?”. The created printout shows the
available parameter commands (default and properties) and below the “-------------------“ line, the
possible input for the selected parameter.
ACCEED2104(config-Information)# Description ?
default Reset parameter to default value
properties Display parameter properties String
------------------------------------------------------------------------------
<0..32 Characters> Enter string in quotes
ACCEED2104(config-LAN-Ports/P1)# Ingress-Rate-Limit ?
default Reset parameter to default value
properties Display parameter properties Integer
------------------------------------------------------------------------------
<64..100000> Enter an integer value
ACCEED2104(config-Switch-Local)# LAN-Ports-Power-Save ?
default Reset parameter to default value
properties Display parameter properties Boolean
------------------------------------------------------------------------------
<true / false> Enter a boolean value
ACCEED2104(config-Switch-Local)# VLAN-Mode ?
default Reset parameter to default value
properties Display parameter properties
Lists
------------------------------------------------------------------------------
Unaware
Aware
ACCEED2104(config-Inband)# Ports ?
default Reset parameter to default value
properties Display parameter properties
Bit-Arrays
------------------------------------------------------------------------------
P1
P3
BPL1
SFP1
WAN1
WAN2
WAN3
WAN4
The parameter command “default” sets this parameter to the factory default.
The parameter command “properties” or the parameter name without a set parameter shows the
parameter name and its description, the current value of it, the default value and if available the valid
Range.
ACCEED2104(config-Information)# Description String
Description Device description
------------------------------------------------------------------------------
Current value "ULAF+ ACCEED 2104"
Default value "ULAF+ ACCEED 2104"
Range 0..32 Characters
ACCEED1416(config-Switch-Local)# LAN-Ports-Power-Save
Description Boolean
Automatically reduces the signal amplitude (for cables up to 30m)
------------------------------------------------------------------------------
Current value false
Default value false
ACCEED1416(config-Switch-Local)# VLAN-Mode
Description Defines the VLAN mode of the switch Lists
------------------------------------------------------------------------------
Current value Aware
Default value Unaware
ACCEED1416(config-Inband)# IP-Address
Description Configured IP address for inband management interface
Set to default Prohibited
------------------------------------------------------------------------------
Current value 10.128.3.99
Default value 10.0.0.1
ACCEED1416(config-Packet)# Destination-MAC-Address
Description MAC address of the remote circuit emulation function
------------------------------------------------------------------------------
Current value 00:1A:D0:00:00:11
Default value 00:00:00:00:00:00
To set a parameter the parameter name followed by the new parameter is used.
6.7.10.1 Clear
Syntax: clear <list>
Description: Clear the configuration or log files
Options:
ACCEED2104# clear ?
alarmlog Clear the alarm log
configuration Clear the configuration
Note: In case of ‘clear configuration’ a confirmation is asked. No reset of the board is
initiated.
ACCEED2104# clear configuration
Are you sure? [y|n]: y
6.7.10.2 Configure
Syntax: configure terminal
Description: Enter the configuration mode
Output:
ACCEED2104# configure terminal
ACCEED2104(config)#
Note: In case of write token unavailable, enter configuration mode read-only
ACCEED2104# configure terminal
ACCEED2104(RO-config)#
6.7.10.3 Copy
Syntax: copy <source> <destination>
Description: Copy the running-configuration to or from a server
Options: sources
ACCEED2104# copy ?
flash:104M_16wp_one_customer.txt Copy from file
flash:22M_4wp_one_customer.txt Copy from file
flash:60M_4wp_one_customer.txt Copy from file
flash:6M_1wp_four_customers.txt Copy from file
help Copy command help
running-config Copy the running-config
scp: Copy from server with SCP (scp:192.168.1.1:/tmp/file.txt)
tftp: Copy from TFTP server (tftp:192.168.1.1/tmp/file.txt)
Options: destinations dependent of the source type
ACCEED2104# copy running-config ?
flash: To flash (flash:file.txt)
scp: To server with SCP (scp:192.168.1.1:/tmp/file.txt)
tftp: To TFTP server (tftp:192.168.1.1/tmp/file.txt)
6.7.10.4 Default
Syntax: default [recursive]
Description: set all parameters in this folder to default values. In case of option “recursive”, all
parameters in all subfolders below this folder are recursively set to default
Output:
ACCEED2104(config-Switch-Local)# default
ACCEED2104(config-Switch-Local)#
Option: recursive
ACCEED2104(config-Switch-Local)# default recursive
Setting parameter values to default.
ACCEED2104(config-Switch-Local)#
6.7.10.5 Delete
Syntax: delete <source>
Description: Delete an existing configuration file
Options:
ACCEED2104# delete ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Note: Each deletion action needs to be confirmed
ACCEED2104# delete flash:test.abc
Are you sure? [y|n]: Y
6.7.10.6 Detail
Syntax: detail
Description: display all parameters in this folder and their values
Output:
ACCEED2104(config-Board)# detail
Last-Configuration-Change 17.01.2013 - 13:38:46
Sample-Device false
ACCEED2104(config-Board)#
6.7.10.7 Disable
Syntax: disable
Description: return to exec mode
Output:
ACCEED2104# disable
ACCEED2104>
6.7.10.8 Enable
Syntax: enable
Description: Enter the privileged mode
Output:
ACCEED2104> enable
ACCEED2104#
6.7.10.9 Erase
Syntax: erase <source>
Description: Erase all files from flash
Options:
ACCEED2104# erase ?
flash: Erase the contents of flash:
Note: erase action needs to be confirmed
ACCEED2104# erase flash:
Are you sure? [y|n]: y
6.7.10.10 Exit
Syntax: exit
Description: In privileged mode: Terminate CLI session
In navigation mode root: return to privileged mode
In navigation mode folder: goto parent folder
Output:
ACCEED2104(config-Board)# exit
ACCEED2104(config)# exit
ACCEED2104# exit
C:\>
6.7.10.11 Fwsync
6.7.10.12 Fwupdate
Syntax: fwupdate <source> [target]
Description: Start local firmware update.
Distribute passive LT Firmware to local-array’s passive firmware bank.
Distribute passive NT Firmware to remote-array-<PAF>’s passive firmware bank.
Options:
ACCEED2104# fwupdate ?
abort Abort a currently running remote download
bank:active Remote download source bank:active
bank:passive Remote download source bank:passive
help Fwupdate command help
info Display the version information
scp: Download image with scp
status Show state of currently running updates
tftp: Download image from TFTP address
Output:
ACCEED2104# fwupdate tftp:10.128.3.65/ACCEED2104/Rel_1.80/ACCEED_2104_644_01.80.tgz
Downloading firmware ...........
Firmware download complete
Writing firmware to passive bank.........................................
Written firmware to flash
Awaiting update..........
Done.
ACCEED2104#
Output:
ACCEED2104# fwupdate info
Active ID: 644/ACCEED 2104
Active Version: 1.70
Passive ID: 644/ACCEED 2104
Passive Version: 1.80
Output:
ACCEED2104# fwupdate bank:active ?
shdsl-nt-port-1 Remote download destination shdsl-nt-port-1
shdsl-nt-port-2 Remote download destination shdsl-nt-port-2
shdsl-nt-port-3 Remote download destination shdsl-nt-port-3
shdsl-nt-port-4 Remote download destination shdsl-nt-port-4
efm-nt-a Remote download destination efm-nt-a
scc-address-12 Remote download destination scc-address-12
6.7.10.13 Help
Syntax: help
Output:
ACCEED2104# help
Please use '?' instead of the keyword 'help'.
There are two possible usages:
a) Show the available commands that start with the already entered
characters e.g. 'c?'
b) Show all possible commands with a parameter description on the
current level e.g. 'show ?'
6.7.10.14 Logout
Syntax: logout
Description: Terminate CLI session
Output:
ACCEED2104# logout
C:\>
6.7.10.15 Match-capabilities
Syntax: match-capabilities
Description: Match the capabilities of this device
ACCEED2104# match-capabilities
Match capabilities......
ACCEED2104#
6.7.10.16 More
Syntax: more <file>
Description: display the content of the selected file
Options:
ACCEED2104# more ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Output:
ACCEED1416# more flash:22M_4wp_one_customer.txt
! Current Configuration
! Device: ACCEED 1416
! Part Number: S3118-D644-E126-05
! Mode: LT
! FW ID: 644
! FW Version: 1.80
! HW Options: 4wp (Eth+RPS180V+SyncE)
! Last Configuration Change: 15.01.2013 - 15:51:46 - UTC
!
root
Aggregation
EFM-Link 1
Remote-PAF Slot-1-PAF-A
!
.
.
.
!
root
Board
EFM-NT 4
Management-Access
Inband
Ports P4 false
IP-Configuration Static
ACCEED1416#
6.7.10.17 Ping
Syntax: ping <ip>
Description: ping a remote host
Options:
ACCEED2104# ping ?
xyz.xyz.xyz.xyz Enter a dot separated IP address
Output:
ACCEED2104# ping 10.0.0.199
PING 10.0.0.199 (10.0.0.199): 56 data bytes
64 bytes from 10.0.0.199: seq=0 ttl=255 time=0.673 ms
6.7.10.18 Preview
Syntax: preview-mode [enable/disable]
Description: show status of preview mode or set it
Options:
ACCEED2104(config)# preview-mode ?
disable Disable the preview mode
enable Enable the preview mode
Output:
ACCEED2104(config)# preview-mode
Preview mode is enabled
ACCEED2104(config)# preview-mode enable
ACCEED2104(config)# preview-mode disable
ACCEED2104(config)#
6.7.10.19 Pwdp
Syntax: pwdp
Description: show path of actual folder
Output:
ACCEED2104(config-Tag-Protocol-Identifier)# pwdp
/Ethernet/Switch-Local/LAN-Ports/P1/VLAN/Ingress/Tag-Protocol-Identifier
ACCEED2104(config-Tag-Protocol-Identifier)#
6.7.10.20 Reboot
Syntax: reboot <target> [swap]
Description: reboot local system or remote via a channel. If swap is attached, an additional swap of
passive to active firmware bank is forced.
Options:
ACCEED2104# reboot ?
refresh update the data
local Reboot target local
shdsl-nt-port-1 Reboot target shdsl-nt-port-1
shdsl-nt-port-2 Reboot target shdsl-nt-port-2
shdsl-nt-port-3 Reboot target shdsl-nt-port-3
shdsl-nt-port-4 Reboot target shdsl-nt-port-4
efm-nt-a Reboot target efm-nt-a
local-array-linecard-2 Reboot target local-array-linecard-2
local-array Reboot target local-array
remote-array-a-linecard-1 Reboot target remote-array-a-linecard-1
remote-array-a Reboot target remote-array-a
6.7.10.21 Rename
Syntax: rename <file> <new-file>
Description: rename a file in the flash file system
Options:
ACCEED2104# rename ?
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
Note: erase action needs to be confirmed
ACCEED2104# rename flash:6M_1wp_four_customers.txt 1.txt
Are you sure? [y|n]: y
6.7.10.22 Restore
Syntax: restore <file> [force]
Description: restore a configuration from factory defaults or file in the flash
Options:
ACCEED1416# restore ?
factory-settings Restore factory settings and reboot
flash:104M_16wp_one_customer.txt
flash:22M_4wp_one_customer.txt
flash:60M_4wp_one_customer.txt
flash:6M_1wp_four_customers.txt
ACCEED1416# restore factory-settings ?
force Run the command without asking
Output: restored file
ACCEED1416# restore flash: 6M_1wp_four_customers.txt
Are you sure? [y|n]: y
ACCEED1416#
%_Clear configuration done
ACCEED1416#
%_Configuration successfully restored
C:\>
Output: factory defaults
ACCEED1416# restore factory-settings
ACCEED1416# restore factory-settings ?
force Run the command without asking
C:\>
6.7.10.23 Root
Syntax: root
Description: change path of actual folder to the top (root) level
Output:
ACCEED2104(config-Tag-Protocol-Identifier)# root
ACCEED2104(config)#
6.7.10.24 Set
Syntax: set <parameter>
Description: restore a configuration from factory defaults or file in the flash
Options:
ACCEED2104# set ?
password Set a new password
session-timeout Set the session timeout
time Set system date and time
ACCEED2104# show ?
alarm Display active alarms
flash: Display contents of the flash: directory
mismatch Display all the mismatches on this device
running-config Display current operating configuration
tree Display the datamodel tree below the current folder
version Display system status
alarmlog Dumps a copy of the alarm log
boardinfo Display the content of Board/Local/Information
time Display the content of Board/Local/Time-Settings
mactable Dumps a copy of the current MAC table entries
EVC-Report Displays a report of all EVC configurations
SAT-Report Opens the service activation test report
systemlog Show system log
resources Show system resources
inventory Show inventory list of all connected devices
CoS Identifiers:
--------------------------------------------------------------------------------
EVC 1:
--------------------------------------------------------------------------------
Identifier:
Type: Point To Point
VLAN Map:
UNI List:
Port List:
CoS Instances:
----------------------------------------------------------------------------
CoS Identifier Ingress Modifier Egress Modifier
.
.
.
<End of list>
Devices In Aggregation
Devices In Array/SHDSL/EFM
Number of Entries: 3
<End of list>
ACCEED2104#
! Current Configuration
! Device: ACCEED 1416
! Part Number: S3118-D644-E126-05
! Mode: LT
! FW ID: 644
! FW Version: 118.12
! HW Options: 4wp (Eth+G703+RPS180V+SyncE)
! Last Configuration Change: 13.01.2002 - 19:25:44 - UTC
!
root
Aggregation
EFM-Link 1
Remote-PAF Slot-3-PAF-A
!
.
.
.
!
root
Board
EFM-NT 4
Management-Access
Inband
Ports P4 false
IP-Configuration Static
ACCEED2104#
Test Setup
=============================================================================
Service Configuration Test: Yes
Service Performance Test: No
Color Mode: Color Blind
Color Method: PCP
Test Port: WAN1
Destination MAC Address: 00:1A:D0:17:34:01
Source MAC Address: 00:1A:D0:0F:93:B1
Tunnel VLAN ID: None
CIR Test
--------------------------------------------------------------------------
Duration: 30 s
FD [us] PASS
Min Avg Max
617 1298 2340
Throughput Frames
Total Sent Received Lost
6229 6229 0
Delay Frames
Sent Received Lost
30 30 0
Total
Sent CIR Sent Received Lost
6259 6259 6259 0
<End of list>
Aggregation
EFM-Link[]
...
PME[]
...
Ethernet
Switch-Local
...
Switch-EFM-NT[]
...
CES-IWF
Local
...
EFM-NT[]
...
Board
Alarm-Configuration
...
Local
...
EFM-NT[]
...
Array
Local
SCC[]
SHDSL[]
ACCEED2104#
C:\>Telnet 10.128.3.27
Username:
Password :
ACCEED2104> enable
ACCEED2104# fwupdate tftp:10.128.3.65/ACCEED2104/Rel_1.80/ACCEED_2104_644_01.80.tgz
Downloading firmware ...........
Firmware download complete
Writing firmware to passive bank.........................................
Written firmware to flash
Awaiting update..........
Done.
ACCEED2104#
While connecting the ACCEED TFTP client to the server a transfer file window opens and shows the
progress of the data transfer.
After the transfer is done you will get an output similar to the this screenshot
To reduce the risk of configuration loss when updating the firmware it is recommended
to always save the configuration to a file before each download.
The load configuration is described in 6.6.2.
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 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 ACCEED 2104 unit. The download is performed
according to the following procedure:
To initiate a download the file containing the FW (*.dwl file) must be opened. This is done
1
by clicking the ‘Browse’ button.
The `dwl` file is checked to ensure that only allowed FW can be downloaded.
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
The download can be aborted at any time. After aborting the passive bank is empty. A new download
can be restarted at any time.
To activate the new FW, the `Reboot` button must be pressed and the `Swap` checkbox
3
must be enabled. This will load the downloaded FW in the active bank.
Remote Download
Remote download is the procedure needed to update the FW of the ACCEED 2104 unit via the in
band channel.
The in band channel can be very fast, if no rate limiting is applied to in band channel it uses the same
bandwidth as the payload and requires an IP address on the remote ACCEED 2104 unit.
The in band download procedure is the same as the procedure for local download.
Please refer to 6.3.4 for more information.
7
EFMC Aggregation
8
Ethernet Switch
This chapter describes the powerful feature set of the ACCEED regarding
packet evaluation, manipulation and prioritization for traffic engineering.
Highlights are:
Highly flexible VLAN manipulation
Powerful ingress and egress Policy Engines
Low Latency, low Jitter
QoS
Ethernet OAM
Traffic Shaping
Traffic Counting
Protection Mechanisms
Switch control
Aging enable/disable
Aging time configurable
MAC table 16k, self-learning
MAC table readout
Limit number of MAC-Addresses learned
Port isolation
Protection
Linear Protection G.8031
Ring Protection G.8032
VLAN
802.1Q (VLAN)
- 4095 C-VLANs
- Port VID explicit settable
802.1ad (Provider Bridge)
- Provider/Service VID (S-VID)
- Provider/Service Ethertype (S-TPID)
- Multiple customer services (different C-VLANs to S-VLANs) on same customer port
TR-101 VLAN manipulations
- Inner/outer swap
- 1:1 translation
- N:1 service multiplexing
- Port-based stacking
- VLAN-based stacking/multiplexing
Classification
Predefined criteria:
- Ingress Port
- Destination MAC-Address
- Source MAC-Address
- Ethertype (TPID)
- VLAN-ID
- VLAN Priority
- Destination IP-Address
- Source IP-Address
- IP Priority (DSCP)
- IP Datagram Protocol
- TCP/UDP Destination Port
A3118-X654-R620-01 153 / 398
ULAF+ 8 - Ethernet Switch ACCEED 2104 Manual
QoS/Policing
Prioritization based on:
Ingress port
802.1p (L2)
DSCP (L3)
any other criteria (flow)
MEF10.2 Ethernet Services Attributes (ingress and egress bandwidth profiles):
Committed Information Rate (CIR)
Excess Information Rate (PIR)
Committed Burst Size (CBS)
Excess Burst Size (EBS)
Peak Burst Size (PBS)
Color mode (CM)
Metering acc. to RFC2697, 2698 and 3290 with single or two rate three color marking
8 priority queues per egress port
Per color queue size
Hard QoS (guaranteed traffic profile)
Strict priority (SP)
Weighted fairness algorithms (WFQ, WRR, SDWRR)
Per port shaping (rate and burst size)
Per queue shaping (rate and burst size)
Random early detection (RED)
Flexible L2/L3 remarking
Flexible traffic class assignment
Counters
Per port packet and byte counters (RMON Etherstats)
Per ingress and egress service counters (packet or byte / per color)
Transmit queue counters (packet or byte)
Per service counters (EVC)
History for all packet counters
OAM
Link OAM (802.3ah)
Service OAM (802.1ag, Y.1731)
Depending on the solution to be implemented, the functions in these building blocks are applied to the
packets.
MAC
This first stage represents the physical port of the ACCEED device connected to the switch. The
Medium Access Control defines the speed and duplex operation of the port. At this stage the packet is
reassembled from its serial form to a full packet stored in a memory buffer. Its FCS is checked.
Port
In this mandatory stage the packet is analysed regarding the VLAN information and the primary and
secondary VLAN tag assignment is done. The primary and secondary VLAN tag information is further
used as decision criteria in the upcoming stages.
The ports can be configured with port specific VLAN and QoS settings.
VLAN Translation
The "Primary VLAN translation" is an optional stage and can be performed on the ingress and egress
path (see also stage 7).
Policing
In addition to the port based configuration settings, traffic can be separated into flows for individual
filtering, metering, VLAN- and QoS manipulation.
Bridge
The packets entering the bridge are switched to the egress side according to the primary VLAN ID and
the switching criteria defined in the VLAN database. This database defines the VLAN membership of
the physical ports.
Queuing
On the egress path the packets are enqueued in the transmit queues according to the mapping
scheme that has been assigned on the ingress path. Traffic shaping is possible per queue and per
port.
VLAN Translation
On the egress path an optional translation of the primary VLAN ID can be applied. This post process
allows the changing of the primary tag.
Policing
On the egress path, a policing stage is available for flow based filtering, metering, VLAN- and QoS
manipulation.
Port
Before the packet is leaving the Ethernet switch on the egress port, VLAN and QoS settings can be
changed on the port level according to the requirement for the packet delivery.
MAC
The leaving packet is prepared for delivery on the egress port. Optionally it can be looped back into
the ingress pipeline of the same port. The Medium Access Control also sets the speed and duplex
operation of the port.
The upcoming chapters describe the functionality in more detail and make reference to the GUI
representation in the LCT+.
The Ethernet Switch settings can be found in the Tree- or the View area of the LCT+.
The graphical representation of the ACCEED LT and NT in the View area is linked to the Tree Area.
By clicking on the descriptions (EVC, PROT, VLAN, etc.) in the graphical view, the respective tree
structure is opened and the Table area with the current settings is shown.
The Ethernet Switch chapter describes the "Switch Local" (LT) configuration. The configuration for the
respective "Switch EFM-NT" has the equal settings.
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 2104 are
greyed out.
Please note that accessible switch ports are P1 – P4 and the SFP1 – SFP4 port. The WAN and BPL
(backplane port) are internal switch ports.
Maximum Frame Size values in ACCEED 2104: [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.
The Power Save mode is applicable only for twisted pair cables up to 30m
Enable
Enables or shuts down the port
Mode
Defines port speed and duplex operation
Auto Negotiation port speed and duplex operation is negotiated with peer port
10MBit/s Full Duplex port speed and duplex operation is forced to these values
10MBit/s Half Duplex port speed and duplex operation is forced to these values
100MBit/s Full Duplex port speed and duplex operation is forced to these values
100MBit/s Half Duplex port speed and duplex operation is forced to these values
Force Full Duplex
If enabled, the MAC transmits with full duplex independently of the auto-negotiation result. This
means, if a device with auto-negotiation disabled is connected to this port, the auto-negotiation will
discover the speed correctly, but the duplex mode cannot be determined and by default would
fallback to half duplex. This duplex result is then ignored by the MAC and forced to full duplex.
Port Type
RJ45 interface pinout definition
Auto-MDI/MDIX Automatically detects the required cable connection type (straight-through or
crossover) and configures the connection appropriately
MDI Port Medium Dependent Interface port, typically used on the end devices
MDIX Port Medium Dependent Interface Crossover port, typically used on switches
Description
Individual port description with up to 64 characters, e.g. Service Name or Location
Advertised Modes
Restrict port speed and duplex operation combinations for negotiation with the link partner
Only applicable when the Auto Negotiation mode is enabled
Flow Control
Enables the Flow Control mechanism by sending out "PAUSE" frames (full duplex operation) or
using backpressure (half duplex operation)
Please note that in case of electrical SFPs, flow control is available but the “flow control status” is
void.
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.
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.
The sources to trigger an LFP and therefore initiate a forced link down of Ethernet ports are:
LAN, SFP, BPL and LAG ports (“no link” alarm)
WAN ports (“aggregation loss” or “partial aggregation loss” alarm)
SOAM-MEP (“SOAM-RemoteCCM” alarm or reception of SOAM CSF frames, 9.2.1.4)
LFP Target: The LFP group configured here is notified if the connectivity on the path
between the MEPs is interrupted and shuts down the Ethernet ports in the selected target
group. The LFP target group is also triggered upon reception of SOAM CSF messages (
9.2.1.4)
LFP Example:
The example in the above figure shows an ACCEED unit with the WAN1 interface being the LFP
source. Port P1 and P2 are assigned to the LFP group A.
If a loss is detected on interface WAN1 as indicated with the red cross, the port P1 and P2 are shut
down and report a forced shutdown state accordingly.
8.3.2.3 LAG
LAG (Link Aggregation Group) in ACCEED 2104 allows combining up to 4 links to increase the
throughput and provide redundancy in case one link fails.
ACCEED 2104 provides two LAG interfaces on which it is possible to aggregate statically (static LAG)
or via LACP (Link Aggregation Control Protocol Active or Passive modes) any SFP interfaces and any
electrical ports P1, P2, …, Px and BPL1.
The LAG is a logical entity that can be configured and used as a physical port. When 1 physical ports is
added to a LAG entity, then all the setting available under the port configuration are not used anymore.
This is true for all the settings but the Flow control, which can be still configured on the port level of the
LAG members.
A3118-X654-R620-01 163 / 398
ULAF+ 8 - Ethernet Switch ACCEED 2104 Manual
Packets sent to the LAG are distributed over the active ports according to the LAG hash algorithm.
The distribution algorithm is based on the combined Layer 2, Layer 3 and Layer 4 packet header
information.
The link OAM of all involved ACCEED 2104 ports in the LAG are automatically enabled and set to
configuration mode for LAG ports.
Any LAN; SFP and Backplane ports can be added to the LAG using the button “Add”, while the
configuration can be checked through the following parameters.
Index
Index in aggregation list.
Port
Shows the member port of this link aggregation group.
Ethernet/Switch Local/LAG/LAG1
Enable
Enables or shuts down the port
Description
Individual port description with up to 64 characters, e.g. service name or location.
Available Bandwidth
Shows the currently available bandwidth for the LAG port
LACP Mode
Defines the LACP (Link Aggregation Control Protocol) activity. If LACP is disabled, the ports are
aggregated statically.
Active LACP is enabled and set in Active Mode.
Passive LACP is enabled and set in Passive Mode.
Disabled LACP is disabled. The port works with static LAG.
Period
Defines the time between the transmission of LACP frames
1s An LACP frame is sent every second (fast LACP)
30s An LACP frame is sent every 30 seconds (slow LACP)
Aggregator State
The aggregator state is "up" if at least one aggregation port is collecting or both collecting and
distributing, and "down" otherwise
LFP Sources
All selected LFP sources are monitored. If at least one LFP source is active, this port will be set to
down to signal the counter device on this Ethernet link an LFP alarm. Additionally the “LFP” alarm
is raised.
If all selected LFP sources change to inactive, this Ethernet link will be restored and the “LFP”
alarm cleared.
MAC Address
MAC address of this port.
The figure below shows a LAG configuration between two ACCEED 2104 desktop units as it is presented
in the LCT+.
Ethernet/Switch Local/<port>/Loopback
In the Fault / Maintenance tab of the table area, select “Port Loopback Enable”.
An active loopback is indicated with the “Port Loopback State” parameter. Additionally, the
inward facing loopback arrow of the corresponding port turns red in the Ethernet view.
When a port is in loopback mode, it affects all frames that are normally leaving this port. The external
link of a port with active port loopback is forced down.
There are four additional parameters that can be configured for the port loopback:
Type (Timed/Permanent)
Timed – The Loop will be active for the time defined in duration or a reboot
Permanent – The Loop will be active till the next reboot
Duration (1 .. 1440 minutes)
Number of minutes which the port loop is active
Swap MAC Addresses
Disabled
MAC addresses are not swapped for the looped frames. MAC address learning
should therefore be disabled; otherwise all looped frames will be discarded. VLAN
modifications in the ingress pipeline are possible
Enabled (VLAN Tags Modifiable)
Source and Destination MAC addresses are swapped for all frames and they are
forwarded to the “Redirected Port”. Existing VLAN tags will be tunneled and therefore
preserved, but it is possible to modify the primary VLAN ID in the ingress pipeline, e.g.
to add an additional VLAN tag.
Enabled (VLAN Tags Not Modifiable)
Source and Destination MAC addresses are swapped for all frames and they are
forwarded to the “Redirected Port”. No VLAN modifications or additions are possible.
Redirected Port
Egress port for the looped frames. This is only relevant if “Swap MAC Addresses” is enabled.
The port loopback is a maintenance function. For this reason, the maintenance LED on
ACCEED 2104 will be on whenever at least one port loopback is active.
After a reboot, all loopbacks will be deactivated, regardless of their state before the reboot.
Ethernet/Switch Local/<port>/VLAN/Ingress/Loopback
In the Fault / Maintenance tab of the table area, select “VLAN Loopback Enable”.
An active loopback is indicated with the “VLAN Loopback State” parameter. Additionally,
the outward facing loopback arrow of the corresponding port turns red in the Ethernet view.
When the VLAN loopback mode is active, all frames that are not caught by the loopback method will
be forwarded normally to the bridge.
Frames that are looped are not matched by any ingress policies or VLAN filters.
There are some additional parameters that can be configured for the port loopback:
Tunnel VLAN
Optionally the looped frames can be put into a VLAN tunnel (an additional tunnel VLAN tag is
added). The port where the loopback is active must me member of the tunnel VLAN in the VLAN
database.
Tunnel VLAN ID (1 .. 4094)
VLAN ID used if “Tunnel VLAN” is enabled.
Swap MAC Addresses
Disable
MAC addresses are not swapped for the looped frames.
Enable
Source and Destination MAC addresses are swapped for all looped frames and these
frames are forwarded to the egress of this port.
The VLAN loopback is a maintenance function. For this reason, the maintenance LED on
ACCEED 2104 will be on whenever at least one VLAN loopback is active.
After a reboot, all loopbacks will be deactivated, regardless of their state before the reboot.
L2 Control Protocols
The following table shows how ACCEED 2104 handles different layer 2 protocols. The behavior is
configurable on a per port basis:
Tunnel the Ethernet Control Protocol frames are forwarded transparently
Discard the Ethernet Control Protocol frames are discarded
Peer the Ethernet Control Protocol frames are terminated / peered in the control
plane
Tunnel (L2PT) the Ethernet Control Protocol frames are encapsulated using a special MAC
address and send across the network (see 8.4.6 for more details)
Discard
Tunnel
Tunnel
(L2PT)
Types of Ethernet frames / layer 2 control protocols
Peer
MAC-DA: L2PT
IEEE 802.AB - Link Layer Discovery Protocol (LLDP): 01-80-C2-00-00-0E
Multicast address: 01-80-C2-00-00-3x (x is between 0 - F)
IEEE 802.1D und 802.1D-2004 - MAC bridges and Spanning Tree
Protocol - STP
IEEE 802.1w - Rapid Spanning Tree Protocol (RSTP)
IEEE 802.1s – Multiple Spanning Tree Protocol (MSTP)
IEEE 802.1Q - Virtual LANs
IEEE 802.1Qay
IEEE 802.1p - Traffic Class Expediting and Dynamic Multicast Filtering
IEEE 802.1ag - Ethernet Service OAM - Connectivity Fault Management
(CFM)
ITU-T Y.1731 - OAM Functions and Mechanisms for Ethernet-based
Networks
IEEE 802.1ah Provider Backbone Bridges (MAC-in-MAC)
IEEE 802.1X - Port Based Network Access Control
IEEE 802.3ad - Link Aggregation Control Protocol (LACP)
IEEE 802.3ah - Ethernet in the First Mile (EFM) / Ethernet Link OAM
IEEE 802.3x - Flow Control
Generic Attribute Registration Protocol (GARP)
Cisco VTP
CDP
Table 2 ACCEED 2104 Layer 2 Control Protocol handling
Forwarding Database
In VLAN Unaware mode one MAC address table stores the source MAC addresses learned from the
packets received on all ports of the switch. The related VLAN ID is always 1 which is the default VLAN
ID. This MAC address table can store up to 16k MAC addresses. The switching is done solely based
on the MAC address. This behavior is also known as Shared VLAN Learning (SVL).
In VLAN Aware mode, a MAC address table is maintained for each VLAN ID. The sum of all MAC
addresses in these VLAN related MAC address tables can not exceed 16k. The switching is done
based on the MAC address and the related VLAN ID. This behavior is also known as Independent
VLAN Learning (IVL).
The ACCEED 2104 MAC table can be read out with the LCT+ and saved as text file. It can also be
manually flushed (all entries are deleted).
The `MAC Table` and `MAC Table Flush` buttons are located in the LCT+ dialogue `Switch
Local` and `Switch EFM-NT`
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.
Learning Mode
There are two learning modes configurable:
Automatic learning: learning mode=automatic, aging time=10..600
Each source MAC address is stored with its primary VID and ingress port in the forwarding
database. In case there is already an equal entry existing the aging is renewed. If the MAC table
reaches its maximum limit (16k) the source MAC will not be learned, but bridged in its primary VID.
The learning is done in hardware at wire speed.
Limited learning: learning mode=limited, aging time=10..600, number of allowed MAC=1..128
All new source MAC addresses (not in forwarding database) will be learned by the CPU. If the
maximum number of allowed MAC addresses per switch is reached, the packets will be dropped.
This feature is designed for the NT, CS and CPE, where typically one customer is attached to the
service.
Disabled learning: aging time=learning disabled
No MAC address will be learned. All frames will be bridged within their primary VLAN group. The
forwarding is done in wire speed.
Aging Time
The MAC Table Aging Time defines how long the learned MAC address is kept in the database if this
MAC address is no longer learned on the corresponding ingress port.
The MAC address learning can be switched off by choosing Learning Disabled as MAC Table Aging
Time. With this setting the switch becomes transparent and acts like a hub.
The value range for MAC table aging time is [Learning Disabled, 10 … 300 … 600] seconds
Port isolation
To prevent switching between specified ports, these ports can be isolated from other ports.
This is done by restricting the allowed egress ports for frames entering via a specific port.
Typical applications are:
WAN Isolation (Rooted-Multipoint EVC)
Multi EPL Mode (LAN1 - WAN1 connection is isolated from LAN2 - WAN2 connection)
The example (Figure 8-14) shows that the traffic of customer 1 (orange) connected on WAN1 using
transmit ports P1 and SFP1 is separated from the traffic of customer 2 (green) connected on WAN2
using transmit ports P2 and P3.
To separate traffic of different customers using the same switch port, VLANs must be used. Please
refer to chapter 8.5.1
To separate traffic of different customers using the same switch port, VLANs must be used. Please
refer to chapter 8.5.1
If Link OAM is turned on for a specific port, this port must be enabled in its own port
isolation table to allow a Link OAM loopback.
Port mirroring
Port mirroring allows to duplicate the ingress and/or egress traffic of a port (mirror source port) and to
send it to a different port (mirror analyzer port).
ACCEED supports port based mirroring. All packets without MAC-level errors of the mirror source port
are duplicated and sent to the mirror analyzer port.
ACCEED also supports flow based mirroring. See 8.7.3.5
Switch Local/Mirroring
Port mirroring can be configured in the LCT+ in the Switch dialogues (local and EFM-NT)
L2PT
Layer 2 Protocol Tunneling (L2PT) allows to tunnel Layer 2 BPDUs such as STP, LACP, and Cisco
CDP across a network avoiding that intermediate switches can intercept and interpret them. With this
feature a Service Provider can separate its own network from customer networks without blocking the
transmission of the L2 BPDUs.
Ethernet/Switch […]/L2PT
In the figure above the Global Switch configuration is set in order to use the Albis standard MAC
address in order as L2PT destination MAC Address. Furthermore the CoS 5 is assigned to L2PT
frames, that cannot be sent with a rate higher than 100 Frame/s.
Egress Port
Port where L2PT encapsulated and decapsulated frames will be forwarded to
Tunnel VLAN
If enabled L2PT encapsulated frames will be VLAN tagged
Tunnel VLAN ID
L2PT encapsulated frames will be tagged and forwarded in this VLAN
Add Default VLAN
Untagged L2PT encapsulated frames that will additionally get a default VLAN tag
Remove Default VLAN
The default VLAN tag of L2PT decapsulated frames will be removed
Default VLAN ID
Untagged L2PT encapsulated frames will be tagged and forwarded in this VLAN
In the figure above the L2 BPDUs entering port P2 are tunneled in the VLAN 4000 and sent to port
SFP1. If the L2 BPDUs are untagged, then the default VLAN tag 8 is added, resulting in a double
tagged BPDU.
On the reverse direction, L2PT BPDUs coming from SFP1 are sent to the customer throughout port P2
removing the Tunnel tag 4000. If the L2PT BPDUs are double tagged and the inner tag is 8 (Default
VLAN ID), than the inner tag is removed and the frame is sent untagged to the customer.
Ethernet/Switch […]/<port>/L2CP
The figures above show a typical configuration of L2CP of the Tunnel port and of the Peer port.
8.5 VLAN
This chapter describes the VLAN modes and the port based VLAN manipulation options. The
reference model below shows the respective stages that are addressed.
VLAN mode
ACCEED can be configured to work in the global modes VLAN unaware or VLAN aware.
The VLAN unaware mode is a transparent mode that can evaluate the VLAN tags, remark .1p bits but
does not change the VLAN ID or TPID information of the packet.
In the VLAN aware mode various VLAN manipulations like tagging, stacking, translation and swapping
can be configured. The port based VLAN manipulation options are explained in this chapter.
The flow (service) based VLAN manipulation options are explained in chapter 8.7.3
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.
The VLAN mode can be configured in the LCT+ in the Switch dialogues (local and EFM-
NT)
Bridging decisions in ACCEED are always done based on the Primary VLAN tag.
VLAN ID 1 is the default value and is always present in the VLAN Database.
VLAN ID 0 will be overwritten with the port VLAN ID without losing the 1.p bits information.
VLAN ID 4095 is reserved according to IEEE 802.1Q and can therefore not be used.
Ethernet/Switch Local/VLAN/Database[]
VLANs are added to the Database via the Add button by entering the desired VLAN ID.
VLAN IDs or a VLAN ID range can be entered in the same input line (see below).
Additionally, a name can be assigned to each VLAN ID. Please note, that this name has
only local relevance.
Additionally to the VLAN ID definition, the "egress tagging mode" for each port and VLAN ID relation
needs to be set.
Please note that the setting in the LCT+ reflects the modification done to the packets on the egress
port.
The packets leaving on the egress port can have various tagging formats (e.g. untagged, single
tagged, double tagged). These packets are modified according to the egress tagging mode.
Ethernet/Switch Local/VLAN/Database[]
The result of the applied "egress tagging mode" are explained in the tables on the next pages.
The port based VLAN settings are only applicable if the VLAN aware mode is enabled.
The Egress direction offers a sub set of these parameters only as shown in the picture
below
The global TPID list ( 8.5.3.3) defines the values that are offered to define the primary and
secondary TPIDs for this specific port.
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
The egress TPID list has 1 Primary and 1 Secondary TPID value that can be set
Default value for primary and secondary TPID is 0x8100
If the egress tagging command for the primary VLAN is “Remove Outer Tag”, the TPID of
the inner tag will not be modified.
VLAN Filters
It is possible to filter specific traffic flows by their VLAN IDs and CoS values. These traffic flows can
then be either dropped, redirected or explicitly forwarded.
Figure 8-28) is divided into two sections, area : criteria selection and area : detailed parameter
configuration. For each of the selected criteria in area , the corresponding parameter is available in
area for detailed configuration.
Index [1..32]
Internal unique Filter ID
Description
Frame Command
“Forward” Forward all matching frames normally along the ingress pipeline
“Drop” Discard all matching packets immediately
“Redirect” Send all matching packets to the “Redirected Port”
“Redirect With MAC Swap” Send all matching packets to the “Redirected Port” and swap source
and destination MAC addresses
Redirected Port
Destination port for redirected packets
Criteria
Enable all relevant matching criteria. These are combined by mathematical “and”.
Up to 32 filters can be configured per port. They are applied in ascending order of their index, i.e. the
filter with the lowest index that matches an incoming packet is applied. If a packet does not match any
of the filters, or if there are no filters configured, the packet follows the ingress pipeline in its orderly
way.
The parameters “Primary VLAN Tag Presence” and “Secondary VLAN Tag Presence”
are both fixed to the value “Present”. This implies that VLAN filters can only be applied
for double tagged packets. For single tagged and untagged packets, the mechanisms in
chapter 8.7.3 can be used.
The VLAN filter stage comes after the VLAN translation stage (but before the policing
stage) in the ingress pipeline. Therefore, if VLAN translation is used, the new
(translated) primary VLAN ID has to be used in the VLAN filter.
At the ingress port , a set of QoS attributes is initialized for each packet. At the ingress policing
stage , traffic flows can be identified and processed independently. Here, those QoS attributes can
be modified, for example based on bandwidth profile conformance of the traffic flows. The same is
possible at the egress policing stage . Between the two policing stages there is the egress queuing
stage which is responsible for traffic prioritization and shaping.
Trust Mode
“Untrusted” Assign QoS attributes according to port profile ( 8.7.2.1)
“Trust CoS Value Only” Assign QoS attributes according to the packet’s .1p bit value (if
trusted VLAN tag is found) and the global CoS profile ( 8.7.2.2)
“Trust DSCP Value Only” Assign QoS attributes according to the packet’s DSCP field (if it is
an IP packet) and the global DSCP profile ( 8.7.2.3)
“Trust DSCP/CoS Values” The packet’s .1p bit value and DSCP are used for QoS
assignment. If both are available, DSCP is used.
Trusted VLAN Tag
“Primary VLAN Tag” In “Trust CoS Value” modes, use .1p bits from primary VLAN tag
“Secondary VLAN Tag” In “Trust CoS Value” modes, use .1p bits from secondary VLAN
tag
Remark CoS [Yes / No] Initial remark decision for the packet’s .1p bits
Remark DSCP [Yes / No] Initial remark decision for the packet’s DSCP value
Default CoS [CoS 0 .. CoS 7] Initial CoS, if there is no trusted VLAN tag found in the packet. This
may result from Trust mode=”untrusted” or Primary TPID settings
different to the received ones.
For each of the 3 available trust modes (untrusted mode, CoS trust mode, DSCP trust mode), the
following initial QoS attribute values can be configured:
Assigned Queue [0 .. 7] Transmit queue in the egress pipeline
Assigned CoS Value [0 .. 7] IEEE802.1p priority bits that are set in the packet’s primary VLAN
tag. Only relevant if the “Remark CoS” attribute is set.
Assigned DSCP Value [0 .. 63] DSCP value for IP packets Only relevant if the “Remark DSCP”
attribute is set.
Assigned Initial Color [green, yellow, red]
Initial color for color aware metering ( 8.7.3.4)
These are the initial QoS attributes, assigned to each packet. They may be modified in
the policing stages.
In untrusted mode, these attributes are configured in the port profile ( 8.7.2.1).
In CoS trust mode, they are configured in the global CoS profiles ( 8.7.2.2).
In DSCP trust mode, they are configured in the global DSCP profiles ( 8.7.2.3).
In the CoS profiles, the term “CoS Value” stands for the .1p bits of the packet’s VLAN
tag.
The DCSP profiles can only be applied to IP packets. For non-IP packets, the QoS
attributes are initialized according to the CoS profiles (if Trust mode=“Trust DSCP/CoS
Values” and the received frame has a primary VLAN Tag), or the port profile.
Policing
As indicated in Figure 8-29, ACCEED 2104 features two policing stages, one in the ingress pipeline
and another one in the egress pipeline. In these stages traffic can be processed on a per-flow base.
A flow is a stream of packets that are classified equal with respect to certain user-defined criteria.
These can be attributes like VLAN tags, CoS, ingress or egress ports, specific values in the IP or TCP
headers, or any combination thereof.
A policy in ACCEED consists of a set of rules and a modifier. The rules define a flow that is treated by
the policy, while the modifier defines the action(s) that are performed on the flow. Policies can be
instantiated at any port in either the ingress or egress policing stage.
Flow = series of frames with a common attribute (e.g. VLAN ID, QoS, …)
Rule
Modifier
= definition of the criteria that define a flow
= actions to be performed on a flow
Policy = treatment / processing of a flow with a modifier
8.7.3.2 Rules
Figure 8-33 shows an example of a typical Ethernet Packet with stacked VLANs, primary VLAN
tagged with ID=1 and secondary VLAN tagged with ID=5:
It is also possible to look deeper into the Packet structure, e.g. IP and TCP/UDP streams:
In ACCEED 2104, flows are identified by matching incoming packets with rules. These rules define
specific values for the packet fields listed above (or a subset of them).
Rules can be added or removed under Ethernet/Switch […]/Policing/Rules[] with the “Add” and
“Remove” buttons. Up to 200 different rules can be defined. They can then be used in the policy
definition ( 8.7.3.6)
Figure 8-35) consists of area : matching criteria selection and area : the detailed parameter
area. By default all criteria in section are disabled, except “Match All Frames” and section
is empty. Criteria (e.g. Primary VLAN ID, Primary VLAN Priority) enabled in get their detailed
Figure 8-35 shows all criteria’s and parameters visible. The selected criteria’s are combined with a
logical ‘and’.
Ethernet/Switch […]/Policing/Rules[]
Rule ID [1..200]
Internal unique Rule ID.
Description
Alphanumeric rule name with 32 characters. This name is also displayed in the tree view, and in
the policy configuration. It is recommended to use meaningful names for the rules, e.g. “VID=1”.
Criteria
Select all relevant matching criteria. These are combined by logical “and”.
Ethertype [0x0...0x0800…0xFFFF]
Match the exact value of the Ethertype (describes the content of the Datagram)
VLAN Tag Presence
“Secondary VLAN Tag or Untagged” match, if packets carry no primary VLAN tag
“Primary VLAN Tag or Priority Tag” match, if packets are PVA or PV0 tagged
Primary VLAN ID [0...4094]
Match the exact value of VLAN ID within the primary VLAN tag
Primary VLAN ID Priority [0...7]
Match the exact value of the IEEE802.1p Priority bits within the primary VLAN tag
Destination IP Address and Destination IP Address Mask
Match the range of Destination IP Addresses that are described with IP and Mask.
E.g. IP=192.168.0.0 and Mask=255.255.0.0 -> IP-Range= 192.168.0.0 … 192.168.255.255
Source IP Address and Source IP Address Mask
Match the range of Source IP Addresses that are described with IP and Mask.
E.g. IP=10.5.64.0 and Mask=255.255.192.0 -> IP-Range= 10.5.64.0 … 10.5.127.255
IP Priority (DSCP) [0…63]
Match the exact Diff Serv Code Point (DSCP) value within the IP Packet
IP Datagram Protocol [0…255]
Match the exact number of the enveloped IP Protocol, e.g. ICMP(1), TCP(6), UDP(17)
TCP-UDP Destination Port [0…65535]
Match the exact Destination Port number within the IP Packet
TCP-UDP Source Port [0…65535]
Match the exact Source Port number within the IP Packet
SAT Test Frames
Match ACCEED service activation test frames
Match All Frames
All frames are matched (e.g. if all traffic from one port should be dropped)
The relationship between CIR (committed information rate), PIR (peak information rate)
and EIR (excess information rate) is given by:
With the application of a bandwidth profile to a traffic flow one of the three colors is assigned to each
packet. The packets can then be treated differently according to their color. Green packets are
normally forwarded with high priority, yellow packets are usually seen as best-effort traffic and are
treated with a low priority, while red packets are normally dropped immediately. However, this
behavior can be changed if needed.
Bandwidth profiles in ACCEED 2104 can operate in color aware and in color unaware mode.
In color aware mode, the current color attribute of a packet which was assigned at the ingress (and
possibly already modified with a service class profile) is taken into consideration. Packets can not
improve their color with the application of a bandwidth profile, so yellow packet can only be marked
yellow or red by the bandwidth profile, but never green.
In color unaware mode, the initial color attribute is ignored, and all packets are considered green
when entering the bandwidth profile.
Traffic metering is implemented using token bucket algorithms, which use the concept of an imaginary
bucket filled with tokens representing data bytes. The capacity (size) of the bucket thereby represents
A3118-X654-R620-01 212 / 398
ULAF+ 8 - Ethernet Switch ACCEED 2104 Manual
the maximum burst size that is allowed for a traffic flow, while the rate at which the bucket is filled
represents the maximum information rate for a traffic flow (CIR or PIR).
Two different types of metering modes can be used in ACCEED 2104: Single Rate Three Colors
according to RFC 2697, and Two Rate Three Colors according to RFC 2698. The following examples
illustrate the behavior of the two metering options in both color aware and color unaware mode. For
simplification it is assumed that each packet takes only one token (i.e. the packets are only one byte
long)
Each passing packet takes a color token from the bucket, starting with
the green tokens.
If there are no more green tokens, yellow tokens are used.
If the bucket is empty the packet is colored red.
The picture shows an example of a 5 packet burst. Let us assume that we do not get additional tokens
during this burst and the bucket is full with tokens. Each packet passing by the bucket will take a token
from it, starting with the green ones and continue with the yellow ones. If no tokens are in the bucket
anymore, the color of the packet gets red.
This example demonstrates that a burst with initially colored yellow packets empties the yellow bucket
before the green and leads to red packets with still green available tokens. Compared to the color
blind mode we may now exactly drop the right initially colored packets (3 and 6)
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.
This example shows a 6 packet burst with different initial colors. As the green bucket get empty the 3rd
packet gets the replace color yellow, because it has already got a yellow token. The 5 th and 6th packet
cannot get any yellow tokens therefore they replace their color with red.
Frames that are classified green in the metering always keep the QoS attributes that were assigned to
them at the ingress port or in the service class profiles.
Color Mode
“Color blind”: Initial color of packets is ignored
“Color aware”: Initial color of packets is considered
Metering Mode
“Single Rate, Three Colors”: Single Rate, Three Colors metering according to RFC 2697
“Two Rates, Three Colors”: Two Rates, Three Colors metering according to RFC 2698
Ethernet/Switch […]/<port>/QoS/Egress
DEI remarking can be enabled individually for each egress port
8.7.3.5 Modifiers
Modifiers define the actions that are performed on a flow by a policy. Since not all actions are possible
in both the ingress and egress policing stage, ingress and egress modifiers are defined separately.
The following actions are possible in the ingress policing stage:
Drop the packets
Modification of QoS attributes using Service Class Profiles
Application of a bandwidth profile (including QoS attribute remarking of yellow and red
packets)
Encapsulation into a tunnel VLAN
Explicit redirection to a given egress port
The following actions are possible in the egress policing stage:
Drop the packets
Remarking of DSCP value and .1p bits of outer VLAN tag
Application of a bandwidth profile (including QoS attribute remarking of yellow packets)
Modification of outer VLAN ID
Frame Command
“Forward”: Packets will be normally forwarded via the bridge
“Drop”: All packets will be dropped
“Redirect”: Packets redirected to the Redirect Port without bridge lookup
“Redirect with MAC swap”: Packets will be redirected to a port without bridge lookup.
Additionally their source and destination MAC addresses will be
swapped
Redirect Port Egress port for redirected packets
Mirror to Analyzer Port A copy of each packet of will be sent to the global ingress mirroring
analyzer port. Ethernet/Switch […]/Mirroring/
Service Class Profile Modify initial QoS attribute settings according to the selected Service
Class Profile ( 8.7.3.3)
Remark CoS
“No”: Do not remark the .1p bits in the primary VLAN tag. This setting
overrides the “Remark CoS” configuration done at the ingress port.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
QoS attribute (defined in service class profile, or, if none is
selected, at the ingress port). This setting overrides the “Remark
CoS” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark CoS” configuration done at the ingress
port.
Remark DSCP
“No”: Do not remark the DSCP bits in IP header. This setting overrides
the “Remark DSCP” configuration done at the ingress port.
“Yes”: Remark the DSCP bits in the IP header with DSCP value QoS
attribute (defined in service class profile, or, if none is selected, at
Bandwidth Profile Name of the applied bandwidth profile. Metering can be disabled by
selecting “None”. Ethernet/Switch […]/Policing/Bandwidth Profiles
Dedicated Bandwidth Profile
A dedicated metering instance is created each time a policy with
this modifier is instantiated.
The bandwidth profile is shared among all ingress policies that use
a modifier with the same bandwidth profile.
Yellow Frames Command
“Transmit unchanged”: Yellow frames are treated like green frames
“Drop”: Discard all packets that are marked yellow
“Assign Yellow Frames QoS Profile”:
Re-assign QoS attributes according to selected Yellow Frames
QoS Profile
Yellow Frames QoS Profile Yellow Frames Profile ID if command is “Assign Yellow Frames
QoS Profile”: Profiles are configured under
Ethernet/Switch[…]/QoS/Ingress/Metering Yellow Frames
Profile
Red Frames Command
“Transmit unchanged”: Red frames are treated like green frames
“Drop”: Discard all packets that are marked red
“Assign Red Frames QoS Profile”:
Re-assign QoS attributes according to the Red Frames QoS Profile
Ethernet/Switch […]/QoS/Ingress/Metering Red Frames Profile
Remark CoS Yellow Red
“No”: Do not remark the .1p bits in the primary VLAN tag for yellow or red
frames. This setting overrides the “Remark CoS” configuration done
at the ingress port.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
defined in the Yellow/Red Frames Profile. This setting overrides the
“Remark CoS” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark CoS” configuration done at the ingress
port. If that decision is “Yes”, remark the .1p bits in the primary
VLAN tag with the CoS value defined in the Yellow/Red Frames
Profile.
Remark DSCP Yellow Red
“No”: Do not remark the DSCP bits in the IP header for yellow or red
frames. This setting overrides the “Remark DSCP” configuration
done at the ingress port.
“Yes”: Remark the DSCP bits in the IP header with the DSCP value
defined in the Yellow/Red Frames Profile. This setting overrides the
“Remark DSCP” configuration done at the ingress port.
“Keep Port Remark Decision”: Do not override the “Remark DSCP” configuration done at the
ingress port. If that decision is “Yes”, remark the DSCP bits in the
IP header with the DSCP value defined in the Yellow/Red Frames
Profile.
VLAN Command
“Force Primary VLAN ID”: Remark the ID of the primary VLAN tag
“Enable VLAN Tunneling”: Add a new VLAN tag to the VLAN stack. This will be the primary
VLAN tag and the ID will be as defined in the Primary VLAN ID
parameter. Already existing VLAN tags are kept unchanged
Primary VLAN ID [1…4094] Value of the primary VLAN tag ID for force and tunneling
commands
If VLAN tunneling is enabled, all CoS remarking actions are executed on the new tunnel
VLAN tag.
Frame Command
“Forward”: Packets will be normally forwarded
“Drop”: All packets will be dropped
Bandwidth Profile Name of the applied bandwidth profile. Metering can be disabled by
selecting “None”. Ethernet/Switch […]/Policing/Bandwidth Profiles
Dedicated Bandwidth Profile
A dedicated metering instance is created each time a policy with
this modifier is instantiated.
The bandwidth profile is shared among all egress policies that use
a modifier with the same bandwidth profile.
Yellow Frames Command
“Assign Yellow Frames QoS Profile”:
Re-assign QoS attributes according to the Egress Yellow Frames
QoS Profile.
Ethernet/Switch […]/QoS/Egress/Metering Yellow Frames Profile
This is currently the only option for egress metering.
Red Frames Command
“Drop”: Discard all packets that are marked red.
Remark CoS Yellow
“No”: Do not remark the .1p bits in the primary VLAN tag for yellow
frames.
“Yes”: Remark the .1p bits in the primary VLAN tag with the CoS value
defined in the Yellow Frames Profile.
Remark DSCP Yellow Red
“No”: Do not remark the DSCP bits in the IP header for yellow frames.
VLAN Command
“Force Outer VLAN ID”: Remark the ID of the outer VLAN tag
Outer VLAN ID [1…4094] Value of the outer VLAN tag ID if forced
CoS (.1p bit) remarking in the ingress policing stage is always executed on the primary
VLAN tag. CoS remarking in the egress policing stage is executed on the outer VLAN
tag, which could be either the primary or the secondary VLAN tag. The only exception is
the CoS remarking of yellow frames, which is always performed on the primary VLAN
tag.
The 8 rules used by a policy are combined with a logical OR, i.e. the policy applies to a
packet as soon as it matches one of the rules.
Entries in the policy map with no selected policy (Policy ID “None”) have no effect.
Queuing
There are traffic situations in Ethernet networks which lead to overload conditions on the interfaces. In
situations where frequent packet drops should be prevented to achieve an optimized throughput
(TCP/IP) large packet buffers may be an appropriate solution. In case of low latency traffic (e.g. VoIP),
buffers should be minimized and this traffic should be prioritized against other services. To solve this
conflict, the best solution is using a flexible queuing mechanism that can be individually configured
according to the customer’s demand.
The packet processor of ACCEED 2104 features a flexible queuing engine with 8 egress queues per
port which allows combining strict priority and weighted fairness scheduling on the same port. The
scheduling distribution amongst the queues is done based on bandwidth ratio and not on inaccurate
packet ratio calculations.
Before packet streams are stored in the queues they need to be allocated to a specific queue. This is
done at the ingress port and optionally at the ingress policing stage, where the “egress queue” QoS
attribute ( 8.7.1) for each packet is assigned.
The egress interface is a constant data rate sink limited through the physically or the logically (rate
shaping) defined port capacity. Packet streams from different ingress ports and traffic bursts may lead
to a congestion situation on that interface and will fill the corresponding buffers of the queues.
Each egress port has a shaped deficit weighted round robin (SDWRR) mechanism with 8 independent
queues.
The following parameters can be individually configured per queue:
- Strict priority (SP) or weighted fairness queuing (WFQ) with different weights
- Queue buffer size for low latency (16x256 bytes) or high burst coverage (224x256 bytes) or
steps in between
- Threshold value to early drop yellow and red packets
- Shaper with queue data rate and the maximum burst size
This scheduling mechanism starts from the highest (#7) to the lowest priority (#0) queue and handles
its queued packets in the following manner:
1) “strict priority”
As long as there are packets in this queue and no packets in a higher queue are waiting, this
queue will send its packets until the queue is empty.
2) “WFQ Weight x”
All Queues with mode “WFQ Weight x” share the available bandwidth in the configured
bandwidth ratios.
Example: available bandwidth is 8 Mbit/s. There are 3 queues with different weights 2, 4 and
10. Result: The first queue will get 1MBit/s, the second 2MBit/s and the third 5Mbit/s.
Recommendation: configure the highest priority queues with “strict priority” and the rest in “WFQ”.
Use short queue buffer sizes for strict priority queues to get lowest latency.
Select individually for each port which of the four profiles is used
Ethernet/Switch […]/<port>/QoS/Egress/
The following parameters are available for each queue in Queue Profile 1 ... 4:
Buffer Size [16 … 224 buffer blocks à 256 Bytes, step: 16]
Queue buffer depth of the queue in 256 Byte blocks. Each packet is split in 256
Byte segments.
Packet size ≤ 256 Bytes: 1 buffer block
Packet size > 256 Bytes: n = round up((Packet size) / 256) buffer blocks
Buffer Threshold [25 … 75 … 100 %, step: 25]
All yellow marked packets exceeding this threshold are dropped immediately
Scheduling
“Strict Priority” all traffic within this queue is transmitted in case there are no packets in higher
queues scheduled for transmit. This mechanism is preemptive and interrupts
lower priority queues and lower WFQ on packet level
“WFQ Weight x” covers that even in congestion a small “fair” amount of low priority traffic passes
through, where x is the bandwidth weight
8.7.4.2 Shaping
The egress data rate of each queue and each port can be limited. This process is called traffic
shaping. The difference between shaping and the application of bandwidth profiles in policing is that
with shaping, packets are not dropped immediately but kept in a buffer (egress queue) and may be
sent at a later moment, if the queue is not full already.
Each port in ACCEED 2104 has 9 independent shapers, one for each queue and one for the whole
port. Queue and port shapers can also be combined and used in a serial configuration (first queue
shaper(s) then port shaper).
The following parameters can be configured for both queue and port shapers:
Enable
Shaping Rate [1’667 … 5’000 … 1’000’000 kbit/s, step: 1’667]
Shaping Burst Size [8 … 16 … 128 kByte, step: 8]
The configuration is achieved in two steps, the global configuration of MEF Services and the local
association of a MEF service to the UNI port.
In the first step most of EVC and EVC per UNI attributes are set under the MEF-Service Folder
available in the Switch configuration. The description of the attributes can be found in chapters from
8.8.2 to 8.8.6.
During the second step the UNI attributes and the remaining EVC and EVC per UNI attributes are set.
These attributes are described in chapters 8.8.7 and 8.8.9.
The EVC statistics are described in chapter 8.8.11.
The following pictures illustrate the relation between the MEF Services tables that are explained in
detail in the next paragraphs and show the mapping between ACCEED MEF Services and MEF
official EVC representation.
Note: From this point on we will use the abbreviation BWPG to refer to Bandwidth Profile Group and
the abbreviation BWP to refer to Bandwidth Profile.
The first picture represents the relations between MEF Services Tables. Each table is drawn with a
green rectangle and is connected with arrows to some other tables. The direction of the arrows
represent the link between the tables.
From the picture is clear that the Bandwidth Profile Group (BWPG) contains one or more Bandwidth
Profiles (BWP) in relation 1:n and can be applied either to the Interface (UNI), in that case the BWPG
is applied per port, or to the EVC, where the BWPG is applied to the EVC.
When the properties of a BWP are defined, they must include a CoS ID that identify the customer
frames the BWP is applied to. Optionally some actions like remarking CoS or DSCP can be done on
green and yellow frames coming from customer, this actions are specified in the CoS ID indicating
which CoS Name an then Service Class is applied to the defined frames. If no CoS ID is specified then
no actions on customer frames is performed.
The next three pictures show how the BWP are mapped to the MEF Services concept according to
their properties. The first BWP is applied at UNI level, the second at UNI/EVC, ther third at
UNI/EVC/CoS ID level. For each case the attributes used changes, for example in the first case the
bandwidth profile is applied directly at the UNI interface (Ethernet/Switch […]/<port>/MEF
Services/UNI), in the third case the BWPG contains three different BWP to assign different profiles to
the three CoS ID specified.
Please note that the EVC Concept supported by current version of ACCEED OS is able to
configure only UNI ports.
The ENNI port configuration is supported with the manual configuration of rules, modifiers
and policies, while the configuration of ENNI ports via EVC Concept is foreseen in next OS
versions.
"Point To Point": The service is a point to point service. This attribute is set in E-Line
service type.
"Multipoint To Multipoint" The service is a multipoint to multipoint service. This attribute is in E-
LAN service type.
"Rooted Multipoint" The service is a Rooted multipoint service. This attrtribute is set in E-
Tree service type.
Service VLAN If set, the service frames of this EVC will be tagged with a service VLAN
Service VLAN ID Service frames will be tagged with this VLAN ID
A CoS IDs entry in the CoS IDs folder allows to classify customer service frames and mapping them to
the EVC. Customer frames can be matched based on the values of the PCP bits, the values of DSCP
bits, the port on which they have been received or the virtual circuit to which they belong.
CoS Names folder contains the CoS policies belonging to the EVCs. An instance of CoS Names
specifies which kind of actions will be performed by the ACCEED switch on the frames belonging to
A3118-X654-R620-01 230 / 398
ULAF+ 8 - Ethernet Switch ACCEED 2104 Manual
the EVC. For example it is possible to remark the P-Bit of the green EVC frames or select to apply a
certain QoS profile to Yellow frames.
An instance of Bandwidth Profiles allows to limit the bandwidth of a given CoS ID in accordance to the
Service Level Specification (SLS) agreed with the customer. At this aims it is possible to set proper
values for CIR, CBS, EIR and EBS.
Color Mode
“Color blind”: Initial color of packets is ignored
“Color aware”: Initial color of packets is considered
CIR Committed Information Rate. This parameter defines a guaranteed bandwidth
[0 … 10’000 … 1’000’000 kbit/s, step: 1]
CBS Commited Burst Size for the guaranteed bandwidth (green packets)
[0 … 10’000 … 500’000 Bytes, step: 1]
EIR Excess Information Rate. This parameter defines the exceeding bandwidth of
this service
[0 … 10’000 … 1’000’000 kbit/s, step: 1]
EBS Excess Burst Size for the exceeding burst matching guaranteed bandwidth
(yellow packets)
[0 … 10’000 … 500’000 Bytes, step: 1]
Once the general EVC configuration is ready, the Network Interface (UNI / ENNI) can be configured
associating the EVC to that Interface.
Note: currently the MEF Services abstraction layer supports only UNI ports.
Any ports of the ACCEED can be configured as UNI port, for this reason a MEF Services folder is
available under the port configuration of any port.
Note: In case the EVC belonging to the UNI port have already an Ingress or an
Egress Bandwidth Profile Group set at EVC level, setting it at UNI level will
cause an unpredictable behaviour.
Port – UNI
The UNI folder describes some UNI port attributes, showing the unique UNI ID and some attributes
that are derived from the general EVC configuration.
Port – EVCs
The table EVCs contains the list of the EVC currently associated to this UNI port.
In order to associate an EVC to the UNI port it is needed to add a new entry to the EVC table of the
UNI port and to configure it properly selecting the interface role, the VLAN map (list of C-VLAN
belonging to this EVC) and the bandwidth profile.
According to the type of EVC configured it will be possible to add only one (EPL, EP-LAN, EP-Tree)
EVC to the UNI or more than one (EVPL, EVP-LAN, EVP-Tree).
Note: if a Bandwidth profile defined as described in chapter 8.8.6 is used as Ingress Bandwidth Profile,
it cannot be used neither in any other EVC nor as Egress Bandwidth Profile of the same EVC.
The MEF Services view is a table that shows an overall view of the EVC and Bandwidth Profiles
currently configured on the ACCEED, both the ones active and the ones not yet activated.
Each lines of the table shows the configuration and the status of a single Bandwidth Profile belonging
to an EVC. The group of lines that has the same EVC-ID defines an EVC.
The MEF Services view is available in the Area View of the LCT+ as shown in the picture below.
The information displayed in the MEF Services view are the following:
EVC Statistics
The ACCEED provides EVC traffic statistics and utilization with the same approach used for any other
kind of statistics.
The statistics must be enabled in the folder Ethernet/Switch Local/MEF Services/Statistics and then
are displayed in the folder Ethernet/Switch Local/MEF Services/Bandwidth Profiles[].
These statistics are also available via SNMP from the standard MEF 40 MIB.
Note: the data can be only accessed when connected directly to an ACCEED (i.e. not via MCUx). In
next ACCEED OS version the SNMP proxy feature will be released and this limitation will be solved.
Please note that the global Ingress/Egress Policy Counters must be enabled and
Ingress/Egress Metering counters must be set to Bytes or Packets. If set to Packets, the
Green, Yellow and RED frames are counted, when set to Bytes, the Green, Yellow and
Red Bytes are counted accordingly.
The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
The Refresh button reads out the latest counters and updates the values in the GUI.
Diagram… opens the window to select the values to be shown in the graph.
EVCs - Examples
The following example shows how to create an EPL circuit configuring an EVC and the related UNI
port on ACCEED. To better understand the example the EPL has been represented in a draw and
some of its attributes in accordance with MEF 10.3 are shown.
UNI Attributes:
- UNI Type =root
- Multiplexing = Disabled
- Bundling = Disabled
- All-to-one bundling = Enabled
EVC Attributes:
- EVC Type = Point to point
- Preservation = Yes
- Class of Service ID = per EVC
This section shows how to configure the Global EVC settings for the EVC of the example.
1. Select
Ethernet/Switch Local/MEF Services/EVCs[]
2. Add a new EVC.
3. Select
Ethernet/Switch Local/MEF Services/EVCs[]/EVC 1
4. Configure the EVC as shown in the picture below
7. Select
Ethernet/Switch Local/MEF Services/CoS Names[]/Cos Name 1
8. Configure the CoS Name as described in the picture
9. Select
Ethernet/Switch Local/MEF Services/CoS IDs[]
10. Add an instance of CoS ID
11. Select
Ethernet/Switch Local/MEF Services/CoS IDs[]/CoS Identifier 1
12. Configure it as described in the picture
15. Select
Ethernet/Switch Local/MEF Services/Bandwidth Profile Groups[]/Group 1
16. Configure the BPG as shown in the picture below
17. Select
Ethernet/Switch Local/MEF Services/Bandwidth Profiles[]/
18. Add a new Bandwidth profile
19. Select
Ethernet/Switch Local/MEF Services/Bandwidth Profiles[]/Bandwidth Profile ID 1
20. Configure as shown in the picture
This section shows how to associate the EVC created in the global EVC settings to an UNI port, P1
has been selected as UNI port for this example.
3. Select
Ethernet/Switch […]/<port>/MEF Services/UNI/EVC
4. Set the parameter as shown in the picture below
5. Select
Ethernet/Switch […]/<port>/MEF Services/UNI/
6. Double check that the configuration applied is the following
8.9 Protection
Linear Protection
Linear protection is utilized to protect services against failures on the path between the two service
end points.
ITU-T G.8031 defines the APS (Automatic Protection Switching) protocol and linear protection
switching mechanisms for point-to-point VLAN-based connection in Ethernet transport networks.
Linear 1+1 and 1:1 protection switching architectures with unidirectional and bidirectional
switching are defined in G.8031.
ACCEED provides linear protection in any combination of the available ports of the unit. The traffic can
be protected based on the port (all traffic) or specific VLANs (services).
Note: The linear protection is an end-2-end service. All intermediate nodes along the working /
protection path are unaware of the protection.
Protection Application
The following figure shows a possible protection scenario with the ACCEED on one side and a 3rd party
device with linear protection functionality on the other end.
The working and protection link on the ACCEED is connected via an optical link to the edge / aggregation
switch in this example.
Protection Level
Protection Type
The protection type defines the behavior of the selector and the bridge.
“1+1” protection type sends the frames on both paths (working and protection) at the same time. On
the receiving side (selector), the frames are taken from the working path in normal operation.
“1:1” protection sends the frames on the working path only in normal operation and also the selector
takes the frames from the working patch.
Switching Type
The switching type defines whether the selector and bridge work independently or synchronized.
Unidirectional switching works independently on both ends of the protection and consequently no
coordination between the protection instances is required.
Bidirectional switching type is a coordinated switching between the working and protection patch.
Selectors and bridges on both ends are coordinated with the APS protocol (Automatic Protection
Switching). The following combinations of protection and switching types are supported:
If Protection Level is set to “Working VLAN” then the Protection and Switching type can
be set only to “1:1” and “bidirectional”
Inband Management and CES services are protected automatically and therefore no
specific protection configuration is required (if linear protection is enabled).
Operation Type
The operation type defines if the services are switched back from the protection path, if the working
path has been restored.
In revertive operation the traffic is switched back after the defined “wait to restore” time.
In non-revertive operation the traffic stays on the protection path.
For APS communication, APS PDUs are exchanged between the same MEPs that send CCMs (the
protection path is used)
The APS-PDU information consists of the bridge / selector state and the following protection types:
(A)PS: yes / no
(B)ridging: 1+1 or 1:1
(D)irection: uni or bi
(R)evertive Mode: yes or no
Ethernet/Switch Local/Protection/Linear/Instance x
The configuration of the linear protection can be done per instance:
The APS folder shows the actual status of the last received APS PDU.
The differentiation between revertive and non-revertive mode is made to explicitly signal the loss of the
working path in revertive mode. In revertive mode, it is desired that the traffic is taken from the working
path due to better connection or due to traffic engineering purposes. In non-revertive mode, both the
working and protection paths are considered equal.
The protection instance(s) will also have an alarm location called "Protocol" with this alarm:
APS Protocol Alarm
OK None
Not OK APS-Failure of Protocol
The configuration required for linear protection for EDD A is described step by step below. Please note
that the configuration for EDD B need to done accordingly.
Ethernet/Switch Local/VLAN/Database[]
3.3) Configuration of the maintenance points (MEP) and CCM data base
Ethernet/Switch Local/SOAM/MPs/MP1 and MP2
Ring Protection
Ethernet Ring Protection Switching (ERPS) provides sub-50ms protection and recovery switching
for Ethernet traffic in a ring topology and at the same time ensures that there are no loops formed at
the Ethernet layer. Ethernet ring protection is defined in ITU-T G.8032 and describes the protection
switching mechanisms and a protocol for Ethernet layer network rings. Ethernet rings can provide
wide-area multipoint connectivity more economically due to their reduced number of links. The
mechanisms and protocol defined in ITU-T G.8032 achieve highly reliable and stable protection.
Each Ethernet Ring Node is connected to adjacent Ethernet Ring Nodes participating in the same
Ethernet Ring, using two independent links. A ring link is bound by two adjacent Ethernet Ring Nodes,
and a port for a ring link is called a ring port.
The event of an Ethernet Ring failure results in protection switching of the traffic. This is achieved
under the control of the Ethernet flow forwarding function on all Ethernet Ring Nodes. The R-APS
(Ring Automatic Protection Switching) protocol is used to coordinate the protection actions over the
ring.
Protection Application
The following figure show possible ring protection scenarios where the rings are completely build based
on EFM fiber connections. A combination of different media for the ring links is also supported – e.g.
ring links based on SHDSL EFM copper or microwave technology, given that these nodes support ring
protection acc. to ITU-T G.8032.
Please refer to our copper based ACCEED products for more information.
Any failure along the ring triggers an R-APS (SF) (R-APS signal fail) message along both directions
from the nodes adjacent to the failed link after these nodes have blocked the port facing the failed link.
On obtaining this message, RPL owner unblocks the RPL port. (Note that a single link failure
anywhere in the ring ensures a loop free topology.)
During the recovery phase when the failed link gets restored the nodes adjacent to the restored link
send R-APS (NR) (R-APS no request) messages. On obtaining this message, the RPL owner block
the RPL port and then sends an R-APS (NR, RB) (R-APS no request, root blocked) message. This will
cause all other nodes other than RPL owner in the ring to unblock all the blocked ports.
This protocol is robust enough to work for unidirectional failure and multiple link failure scenarios in a
ring topology. It includes a mechanism to force switch (FS) or manual switch (MS) which is used in
CES Protection
The CES services are automatically protected by ACCEED device. If the CES egress port is
configured to be one of the protected ports (east or west port) then the CES frames are concurrently
sent out to the opposite side of the ring automatically (east or west port).
SAT Protection
SAT protection works with the same principle as the CES protection. The SAT frames are sent out the
east and west port concurrently if the SAT egress ports is equal to the east or west port of the ring
protection instance.
Source and destination MAC addresses of the SAT frames need to be swapped at the far end loop in
order to be processed at the receiving side of the SAT instance.
Operation Type
The operation type defines if the services are switched back from the protection path, if the working
path has been restored.
In revertive operation the traffic is switched back after the defined “wait to restore” time. In non-
revertive operation, the traffic stays on the protection path.
Request or State
Forced Switch Forces the blocking on the respective ring port with priority over the
SF condition
Signal Fail (SF)
Manual Switch (MS) Forces the blocking on the respective ring port. SF condition has
higher priority
No Request (NR)
Status
RB: RPL Blocked Indicates whether the RPL is blocked or not (valid only, if frames are
from RPL owner node)
DNF: Do Not Flush Indicates whether a MAC table flush is allowed or not
BPR: Blocked Port Reference Indicates whether port 0 (East) or port 1 (West) is blocked
Ethernet/Switch Local/Protection/Ring/Instance x
The configuration of the ring protection can be done per instance:
Operator Command
Ethernet/Switch Local/Protection/Ring/Instance x
The operator commands can be initiated via the following buttons:
Manual Switch (MS) Forces the blocking on the respective ring port. SF condition has
higher priority
Forced Switch (FS) Forces the blocking on the respective ring port with priority over the
SF condition
Clear Clears the operator command (MS / FS)
The protection instance(s) will also have an alarm location called "Protocol" with this alarm:
APS Protocol Alarm
OK None
Not OK APS-Failure of Protocol
The configuration required for ring protection for EDD A is described step by step below. Please note
that the configuration for EDD B and C need to be done accordingly.
Ethernet/Switch Local/VLAN/Database[]
Please note, for Ethernet ports LFP targets need to be configured accordingly
Note: the CCM interval defines the time until the protection switching is triggered by the R-
APS protocol (3.5 times the CCM interval)
3.3) Configuration of the maintenance points (MEP) and CCM data base
Ethernet/Switch Local/SOAM/Domains/D1/MPs/MP1 and MP2
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.
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:
The metering counters (ingress and egress) are always enabled, but must be globally configured to
either count bytes or packets.
Please refer to chapter 8.3.1 for more information.
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.
If the Statistics – Current is not active, the performance value are displayed as “Inactive”
Ethernet/Switch Local/<port>/Statistics/Continuous
To activate the statistics proceed as follow:
In the tree area, go to Ethernet/Switch Local/<port>/Statistics/Continuous
Ethernet/Switch Local/<port>/Statistics/Historic[]
To add historic statistics proceed as follow:
In the tree area, go to Ethernet/Switch Local/<port>/Statistics/Historic[]
Port statistics
A data network switch permits data communication among a plurality of media stations in a network.
Data packets or packets are transferred between stations by means of data network switch Media
Access Controllers (MACs). The network switch passes data packets received from a transmitting
station to a destination station based on the header information and the received data packet. Packet
transmission events typically are tracked to provide a basis for statistical analysis of network operation
with respect to each data network switch port. For example, the number of transmitted packets,
received packets, transmissions collisions, and the like can be counted and polled periodically. These
significant parameters, called "objects", are collected in a Remote Network Monitoring Management
Information Base (RMON MIB). Through the use of statistical counters, determination can be made of
improper device operations, such as, for example, loss of packets.
ACCEED supports group 1 of the RMON MIB parameters (Ethernet Statistics Group). This group
contains statistics measured by the probe for each monitored Ethernet interface on this device.
Individual RMON statistics are available for each switch port of the ACCEED device. Additionally the
HC-RMON MIB overflow counters (High Capacity) are implemented to cover overflows of the 32 bit
RMON counters.
The content of the Ethernet Statistics Group is listed and described in the etherStatsTable
(see Table 16).
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+.
Counter values of the other ports (LAN, WAN, SFP, BPL) are presented in the same way
by choosing the appropriate port in the tree area.
The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
Additional overflow counters exist for some RMON counters to meet the requirements for
HC-RMON. HC-RMON counters are 64 bits wide, compared to RMON counters, which are
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.
For every service the total counted frames and bytes are displayed.
Please note that the global Ingress/Egress Policy Counters must be enabled and
Ingress/Egress Metering counters must be set to Bytes or Packets. If set to Packets, the
Green,Yellow and RED frames are counted, when set to Bytes, the Green, Yellow and Red
Bytes are counted accordingly. please
Counter values of the other ports (LAN, WAN, SFP, BPL) are presented in the same way
by choosing the appropriate port in the tree area.
The figure below shows the continuous egress statistics for Policy 1 of the port WAN1. The
global egress metering counters are set to Bytes.
The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
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.
The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
EVC statistics
For any EVC configured and activated the ACCEED make available the EVC statistics. The ACCEED
count any frames that belongs to the EVC and displays in the statistics table the information related to
the action taken on this frames. Please refer to chapter 8.8 for more information on the EVC concept.
EVC statistics provide the following information:
Total matched frames or bytes of the CoS instances of any EVC
Green, Yellow and Red frames of bytes of the CoS instances of any EVC
The Refresh button reads out the latest counters and updates the values in the GUI.
Reset zeroes all counters of the respective port currently being displayed
Save As… opens a dialogue to save the statistics values of the actual screen to a comma
separated values file (*.csv)
Statistics: Countinuous or the Historic statistics is displayed.
Utilization
Utilization provides information on data rates in kbit/s and link or service utilization in percent [%].
The data rates and utilization can be displayed in a real time diagram which is updated regularly. The
data rates and utilization are derived from the counter values.8.8
Utilization information 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)
Ok opens the Realtime Diagram window and starts displaying the selected data (see
below)
Cancel closes this window and returns back to the main utilization window
Clear deselects all selected data
The graphs in the Bitrate and Utilization diagram to be displayed can be selected on the
right side of the diagrams.
9
Operation and
Maintenance
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.
The OAMPDUs are terminated by the OAM entities or are discarded if there is no OAM layer
implemented. OAMPDUs are never forwarded to other links.
Link OAM Configuration
The active entity initiates the Link OAM; at least one entity of a link must therefore be active. The other
may be passive, but it can be active as well.
An entity in the active mode detects automatically if the remote entity supports OAM. It discovers also
which specific capabilities are supported.
Capabilities
Among the optional Link OAM capabilities, ACCEED 2104 currently supports Remote Loopback. If the
Remote Loopback capability is enabled, the remote peer can initiate a loopback on that port.
A3118-X654-R620-01 275 / 398
ULAF+ 9 - Operation and Maintenance ACCEED 2104 Manual
For interoperability reasons, the “Variable Retrieval” capability can also be enabled in
ACCEED 2104. This allows for certain 3rd party devices to complete the Link OAM
discovery process. The Variable Retrieval functionality itself is currently not supported by
ACCEED 2104, i.e. Variable Requests are not answered.
9.1.2.2 Loopbacks
The Link OAM loopbacks control panel can be found in in the Fault/Maintenance Tab under
Ethernet/Switch […]/Port .../Link OAM
The Link OAM standard defines that looped packets from the remote side have to be dropped in the
local entity. Additionally, ACCEED 2104 also offers the (non-standard) option to forward looped
packets coming from the remote side
The Link OAM loopback does not swap MAC addresses of packets. Therefore, if
forwarding of looped frames is activated, MAC address learning must be disabled in
network elements that are passed by looped packets.
Service OAM is an Operations, Administration and Maintenance mechanism defined for an Ethernet
network (Service OAM Domain). It can generally be divided into Fault Management (FM) and
Performance Management (PM) functions.
Domains and Maintenance Points
MEP: MEG End Point [ITU-T] or Maintenance association End Point [IEEE]
MIP: MEG Intermediate Point [ITU-T] or Maintenance domain Intermediate Point [IEEE]
The example in
Figure 9-5 shows a network with 3 endpoints and the 3 possible endpoint-to-endpoint connections.
In the general case of n MEPs there exist n•(n-1)/2 MEs. These MEs constitute a ME Group (MEG)
[ITU-T] respectively a Maintenance Association (MA) [IEEE].
Every MEG / MA has a unique MEG ID [ITU-T] / MAID [IEEE] for differentiation from neighboring
MEGs / MAs
MEGs / MDs on higher levels have to span wider (or at least equally wide) than those on lower levels.
This means that all SOAM traffic from lower levels is terminated at MEPs from higher levels.
The example in Figure 9-6 illustrates how the level can be used to differentiate the maintenance level:
Customer or subscriber level
Service provider level
Operator level
Ethernet link level
Ethernet/Switch […]/SOAM/Domains[]
New domains can be created by pressing the “Add” button.
The following parameters can be configured per domain:
Domain parameters:
Maintenance Domain Name Format:
[No Maintenance Domain Name Present, Character String]
Maintenance Domain Name is optional. If used, it can be up to 43 characters long, and the
maximum length of the “Short MA Name” is reduced from 45 to 43 characters.
Maintenance Domain Name: [“Maintenance Domain”, max. length is 43 characters]
Only available if the maintenance domain name format is set to “Character String”
Short MA Name Format: [Character String, ICC based Format]
Short MA Name [“SOAM Domain x”, max. length is 45 characters characters or 43 characters in
case a Maintenance Domain Name is used]
Maintenance Domain Level [0.. 3 .. 7]
Level of Maintenance Domain (MD), higher numbers correspond to domains with greater physical
reaches (e.g. the Customer ME in Figure 9-6)
Source Associated VLAN [none, any VLAN ID listed in the “Associated VLAN[]” folder]
VLAN ID among the list of associated VLANs in which all Service OAM PDUs (except LMM and
DMM PDUs) generated by Maintenance Points (MP) are to be transmitted.
Note: The corresponding VLAN ID has to be created in the “Associated VLAN[]” folder before it can
be selected.
MEP Orientation [Down / Up]
Orientation of the Maintenance End Points (MEPs) on this device for this domain
- Down orientation designates a MEP which transmits and receives packets towards the LAN.
- Up orientation means the MEP transmits and receives packets in direction of the Bridge Relay
Entity (“into” the switch).
The MEP orientation doesn’t affect Maintenance Intermediate Points (MIPs) as they do not have
any orientation. Please refer to 9.2.1.3 for additional explanation on MEP orientation.
Continuity Check Messages [enabled / disabled]
This parameter enables the sending of continuity check messages (CCM) by all MEPs in this
domain ( 9.2.2.1).
CCM Period [3.33ms, 10ms, 100ms, 1s, 10s. 1min, 10min]
This parameter determines the interval between continuity check messages
CCM CoS Value [CoS 0 .. CoS 7]
A3118-X654-R620-01 282 / 398
ULAF+ 9 - Operation and Maintenance ACCEED 2104 Manual
CoS value for CCM, AIS, LCK, APS and CSF frames generated in this domain
CCM Transmit Queue [Queue 0 .. Queue 7]
Transmit Queue used for CCM, AIS, LCK, APS and CSF frames generated in this domain
RDI [enabled / disabled]
This parameter enables the sending of Remote Defect Indications (RDI) in the continuity check
messages (CCM). A defect condition exists if the MEP has a RemoteCCM, ErrorCCM, or XconCCM
alarm. A MEP detects the defect condition in receive direction and sets the RDI flag in the CCM
messages in transmit direction if RDI is enabled. Additionally, if RDI is enabled and a CCM with the
RDI flag set is received, then the MEP’s LFP Target Group is triggered (if there is one configured)
and the RDICCM alarm is raised.
Alarm Indication Signal [enabled / disabled]
Enables the Alarm Indication Signal (AIS) function in this domain (see 9.2.2.2)
Locked Signal [enabled / disabled]
Enables the Locked Signal (LCK) function in this domain (see 9.2.2.2)
AIS LCK Period [1s, 1min]
Time period between two AIS or LCK frames
Client Signal Fail [enabled / disabled]
Enables the Client Signal Fail (CSF) function in this domain (see 9.2.2.3)
CSF Period [1s, 1min]
Time period between two CSF frames
CSF LFP Source [LFP Group A .. LFP Group E]
Defines which LFP target group triggers the CSF function in this domain (see 9.2.2.3)
Associated VLAN
Maintenance Domains can be associated with VLANs. A domain can receive packets from multiple
different VLANs (called “Associated VLANs”), but all frames generated by the MPs in a domain will be
sent in the same VLAN (“Source Associated VLAN”). The Source Associated VLAN is selected in the
Domain configuration
LMM / LMR and DMM / DMR frames can be configured to be sent in an associated VLAN
different from the Domain’s Source Associated VLAN ( 9.2.3.1/ 9.2.3.2).
ACCEED devices also support sending and receiving double-tagged SOAM frames. In the device
configuration this is implemented by allowing to configure an optional tunnel VLAN for an associated
VLAN. Therefore, an “Associated VLAN” in ACCCED device configuration describes all VLAN tags (0,
1 or 2 VLAN tags) of a SOAM frame.
Each “Associated VLAN” has to be unique and can only be linked to one Domain.
It is also possible to send / receive untagged SOAM frames. There are two ways to achieve this:
- If no “Associated VLAN” is linked to the corresponding Domain
- If an “Associated VLAN” with “VLAN ID”=“Tunnel VLAN ID”=”none” is created and linked to the
corresponding Domain
If tunneling (double tagging) is applied, make sure to configure the following parameters
accordingly:
- VLAN egress tagging commands in the VLAN DB
- Ingress/Egress TPIDs of the tunnel port(s). Only VLAN tags that are recognized by
the device are considered.
If a tunnel VLAN tag is present at incoming SOAM frames, it has to be the outer and the
primary VLAN tag.
Not more than 8 MEPs can be added to Domains with CCM intervals <= 10ms.
Ethernet/Switch […]/SOAM/MPs
Domain ID
Enables the Maintenance point and associates it with a Domain. The Domain has to be created
first.
Locked
Administrative locking of the MP, see 9.2.2.2
Type [MEP / MIP]
Maintenance point type, either MEP (Maintenance association End Point [IEEE 802.1ag] or
equivalently MEG end point [ITU-T Y.1731]) or MIP (Maintenance domain Intermediate Point
[IEEE 802.1ag] or equivalently MEG Intermediate point [ITU-T Y.1731])
Associated Port [port list depends on specific ACCEED type]
Port on which the maintenance point should reside
MEP ID [1... 8’191]
Unique number which identifies the MEP in its Maintenance Domain
CCM Database
All remote MEPs from which a local MEP expects to receive CCMs have to be entered in the CCM
Database. CCM messages received from unknown MEPs (MEP not present in the CCM database),
raise an XconCCM alarm. Invalid CCM messages (e.g. with unexpected CCM interval) which are
received raise an ErrorCCM alarm.
Lack of messages from MEPs (No CCM message received within 3.5 times the CCM interval) present
in the CCM database, raise a RemoteCCM alarm.
Remote MEPs are entered in the CCM data base by clicking the Add button and entering
the remote MEP’s ID. Up to 16 remote MEPs can be added per local MEP.
For each MEP in the CCM Database the following (read-only) information is available:
MEP ID
ID of the remote MEP
State
The following states are possible:
- Idle Continuity Check not yet started
- Start Continuity Check starting
- Failed No Continuity Check Messages received from remote MEP
- OK Continuity Check Messages received from remote MEP
Last State Change
This parameter indicates the time and time at which the remote MEP last entered the Failed or Ok
state or 0 (zero) if it has not yet entered either state.
MAC Address
MAC address learned for the remote MEP
RDI
This parameter reports the state of the Remote Defect Indication (RDI) flag in the received Continuity
Check Messages (CCM).
CSF
Received CSF defect type, if any. See 9.2.2.3
LFP Target
Defines the LFP target group, which will be notified if connectivity to this MEP has failed or CSF
messages are received. Please refer to 8.3.2.2 for more information on LFP (Link Failure
Propagation)
Each local MEP supports up to 16 remote MEPs. Additionally there is a global limitation on
the number of incoming CCMs. The maximum total number of CCMs received in all
domains with CCM intervals >10ms is 300 CCMs/second. For domains with CCM intervals
<=10ms the total number is limited to 3000 CCMs/second. The CCM rate depends on the
number of configured remote MEPs and the CCM intervals of each domain. A “Resource
Shortage” alarm is raised when the expected number of received CCMs exceeds the limit.
In case of connectivity failures (ErrorCCM or XconCCM alarms), there may be some helpful
detail information on the reason of failure in the Fault/SOAM tab. The information displayed
relates to the last defective CCM received by the respective MEP.
9.2.2.2 Y.1731 Alarm Indication Signal (AIS) and Locked Signal (LCK)
Client MPs
Client MPs are configured to forward AIS and LCK signal of the domain where a problem occurred, to
the higher level domain MP.
Up to 29 client MPs can be assigned to one MEP whereas the client MPs of a MEP resides always on
the same ACCEED unit as the MEP itself. The client MP can be a MEP or MIP.
Client MP are entered by clicking the Add button on the Client MP[] level.
For each Client MP, the Service Domain and the corresponding Maintenance Point on that
domain level (can be MEP or MIB) must be assigned.
AIS is initiated if a defect condition on an MEP appears and AIS is enabled on this MEP. This MEP
forwards the AIS to all configured client MPs on the higher MEG levels. The client MPs (MIP) then
send AIS frames in the defined period. AIS frames are only sent in opposite direction of the MEP that
detected the defect condition.
Please refer to 9.2.1.4 for AIS configuration information on the domain level.
both directions. A MEP receiving LCK frames will register a defect condition. Therefore, on higher
levels AIS frames are sent. This is illustrated in the following example.
This is illustrated in Figure 9-10. Normally LFP is used with equipment that does not support
mechanisms like SOAM. LFP will force one ore more UNI ports on a device down if the WAN port
goes down, for example to trigger protection mechanisms like spanning tree or LAG on a router/switch
A3118-X654-R620-01 289 / 398
ULAF+ 9 - Operation and Maintenance ACCEED 2104 Manual
connected to the LAN port (more info on LFP under 8.3.2.2). Using SOAM CSF, the LFP
functionality can be extended over a Layer 2 network between 2 MEPs. The mechanism works as
follows: If the physical link at the UNI port of MEP A goes down, MEP A starts transmitting CSF
frames. MEP B, upon reception of such frames then forces its UNI port down, to signal a remote
failure condition to the link partner which does not support SOAM.
In ACCEED, CSF functionality is configured using the LFP Group concept described under
8.3.2.2
First a port (or MEP) has to be activated as a trigger for an LFP group. For example,
choose LFP Group A as the target group for P1
Ethernet/Switch ../<Port>
In the SOAM domain config, CSF can be enabled and an LFP Group can be selected.
When this group is triggered (in this example because P1 goes down), all MEPs in the
Domain will start transmitting CSF messages.
../SOAM/Domains/Dx
On the remote side, the peer MAP can itself be configured to trigger an LFP group upon
reception of CSF messages
(Remote device) ../SOAM/MPs/MP x/CCM Database/Remote MEP ID y
Finally this LFP Group can then be used to force a port down when triggered by CSF
messages.
(Remote device) Ethernet/Switch ../<Port>
When a MEP receives CSF frames this is indicated in the CCM database, even if the CSF function is
not enabled.
ACCEED can display the following standardized CSF defect types: LOS (Loss of Signal), FDI
(Forward Defect Indication), RDI (Reverse Defect Indication).
Note: When transmitting CSF messages, ACCEED will always use the LOS defect type.
If ACCEED is receiving CSF messages in a domain where CSF is enabled, it will also raise an alarm
(SOAM-LOSCSF, SOAM-FDICSF or SOAM-RDICSF Alarm).
SOAM loopbacks are available under the following node, in the Fault/SOAM tab:
../SOAM/Diagnostics/Loopback
SOAM Linktrace is available under the following node, in the Fault/SOAM tab:
../SOAM/Diagnostics/Linktrace
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.
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
The purpose of Service OAM performance monitoring is to verify that SLAs are met in terms of the
contracted performance attributes. With ACCEED devices, the following attributes can be specified for
a service:
The protocols and mechanisms required for the measurements are defined in ITU-T Y.1731 [17]
ACCEED supports:
The measurement protocols always run between two MEPs. If the measurement is “dual-ended”, both
MEPs can gather results. If it is “single-ended”, only the initiating MEP gathers results.
Independently from the type of measurement (single-/dual-ended), IFDV, FLR, and Availability results
can be calculated separately for forward and backward direction (one-way), while FD measurement
using DMMs gives round-trip (two-way) results.
The measurement of inter-frame delay variation can be performed using the same DMM and DMR
messages that are used for delay measurement.
The delay of the last completed measurement is compared with the delay of the current completed
measurement in forward and backward direction. The picture below illustrates the measurement
principle.
../SOAM/Performance/DM Sessions/Session x
In most cases DMRs should have the same CoS value as the corresponding DMMs. DMR
CoS values that differ from the configured DMM CoS value should only be selected if CoS
values are translated at some point within the network.
Up to 60 responders can be configured. The configuration information of the responder must match
the domain and VLAN / CoS settings of the respective DM session. A responder must be enabled in
order to reply to the DM session with DMR frames.
..\SOAM\Performance\DM Responders\
Responders can be created by clicking the Add button
One historic data set can be added and enabled for up to 32 past intervals. The interval
duration is taken from the current statistics setting.
History settings can be enabled under
../SOAM/Performance/DM Sessions/Session x/Statistics/Historic[]
If measurement values are “unknown” and/or completed and valid measurements are
zero, then a possible communication problem between the DM session and responder
might cause the failure. Verify the session and responder settings and the communication
path in-between.
If the value is showing “Inactive”, this indicates that the current statistics counter is not
enabled. To enable the statistics counter go to
../SOAM/Performance/DM Sessions/Session x/FD/Statistics/Current
Every delay measurement result is assigned to one of maximum 10 intervals called bins, whose
corresponding counter is increased.
The range of bin x is defined by the lower threshold (thld) assigned to bin x and the lower threshold
assigned to bin (x+1).
Measurements with a delay greater than 5 sec are not considered and therefore discarded. The
threshold of Bin 1 should always be set to zero. In the figure below an example with 5 Bins is shown.
Up to 10 Bins can be configured for each DM session (individually for roundtrip FD, forward and
backward IFDV), whereas the threshold of Bin 1 is a permanent list entry. Bins 2 to 10 can be added
with the respective Add button.
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.
Only one end point gathers results for both directions. Multi-CoS setups are supported, but not
multi-point EVCs (LAN scenarios).
Dual-ended synthetic LM using 1SL
Dedicated Synthetic Loss Measurement Messages (1SL) are transmitted by a MEP. A
receiving MEP can calculate frame loss statistics for one traffic direction based on the loss
rates of these 1SL. This method supports multi-point scenarios.
Single-ended synthetic LM using SLM / SLR
Dedicated Synthetic Loss Measurement Messages / Replies (SLM / SLR) are transmitted
between MEPs. Frame loss statistics are calculated based only on loss rates of these SLM /
SLR. This method supports multi-point scenarios.
ACCEED devices support all mentioned loss measurement methods
Two LM metrics are evaluated, Frame Loss Ratio (FLR) and Availability.
Frame Loss Ratio (FLR) measurement is performed by exchanging local transmit (TxFC) and receive
service frame counters (RxFC) between MEPs. For CCM and LMM based measurements, real service
traffic is counted, while synthetic measurement uses the count of transmitted and received SLM / SLR
/ 1SL.
If there is no traffic (e.g. ΔTxFwd = 0) or the previous counters are zero/unknown, then the FLR is
unknown (and the measurement is considered as completed, but not valid).
Figure 9-16 Service OAM – Frame loss ratio (FLR) measurement principle
Availability is defined by the frame loss ratio during a sequence of consecutive short time FLR
measurements (availability indicators) and the last availability state.
A single availability indicator is evaluated over a time interval ∆t = k * LM Frame Period. The number
of LM PDUs (k) that are used to calculate a single availability indicator is configurable. For LM based
on real customer traffic, k is typically set to 1, while for synthetic LM, k should be set to a value of at
least 10. This means that depending on the LM frame period, a single availability indicator covers a
time period (∆t) between 100ms up to a few seconds. Depending on the FLR in that time period
compared to a predefined threshold, there are two possible values a single availability indicator can
have, “high FLR” or “low FLR”.
“Availability” is then assessed over sliding window of size n = {1, …, 10} availability indicators. Its state
changes only if all availability indicators in the sliding window have the same value (see
Figure 9-17).
../SOAM/Performance/LM Sessions/Session x
Frames sent and received by the selected special applications are counted with this LM session.
Only relevant for LM types “LMM” and “CCM”.
Use MEP ID / Target MEP ID
Enables and defines the target MEP ID. If enabled, Target MAC address cannot be set.
Target MAC Address
If the remote MEP is not addressed by MEP ID (“Use MEP ID” disabled), the remote MEP’s MAC
address can be specified manually.
LM VLAN
Defines the VLAN that is used for LM frames. Entries among the list of associated VLAN can be
selected. Not relevant if LM Type is “CCM”.
Attention: The LM VLAN can be different from the domain “source associated VLAN ID”.
CoS Value [CoS 0 .. CoS 7]
Not relevant if LM Type is “CCM”.
Transmit Queue [Queue#0 .. Queue#7]
Not relevant if LM Type is “CCM”.
Accepted CoS Values
LMRs with the selected CoS values are accepted for this LM session. Not relevant if LM Type is
“CCM”.
The used policies needs to apply a bandwidth profile, and only frames marked as green
by the bandwidth profile are considered for the FLR and Availability measurement.
Global counter setting
If LM is done using LMM/LMR or CCM, metering counters need to be set to packets according to the
picture below.
These settings are done on switch level and therefore apply to all ports.
Ethernet/Switch […]/
Only Ingress and Egress Metering Counters need to be set to “Packets” to use LM. Ingress
and Egress Policy Counters are not relevant for LM
Dual-ended frame loss measurements are based on the LM type CCM or 1SL and
therefore an LM session needs to be configured on each end.
Single-ended frame loss measurements are based on the LM type LMM or SLM. These
configurations consist of a LM Session on the initiating MEP and a LM Responder on the
other MEP.
Policy used for counting Tx frames in case of Up-MEP or Rx frames in case of Down-MEP. The
index refers to the index in the ingress policy map of the port where the selected MEP resides
Egress Policy
Policy used for counting Tx frames in case of Down-MEP or Rx frames in case of Up-MEP. The
index refers to the index in the egress policy map of the port where the selected MEP resides
Applications (L2PT)
Frames sent and received by the selected special applications are counted with this LM session.
LM VLAN
Defines the VLAN that is used for LMM/LMR frames. Entries among the list of associated VLAN can
be selected.
Attention: The LM VLAN can be different from the domain “source associated VLAN ID”.
CoS Value [Incoming CoS]
LMRs are always sent back with the same CoS value as the received LMM.
Transmit Queue [Queue#0 .. Queue#7]
Accepted CoS Values
LMMs with the selected CoS values are accepted for this LM session.
9.2.3.2.3 LM Session Statistics
LM session statistics and history are configured the same way as DM session statistics with the
following exceptions:
- FLR and Availability statistics can be configured independently whereas statistics
configuration for FD and IFDV is combined. This allows to have different statistics interval
durations for FLR and Availability
- Larger interval duration range for FLR and Availability [1..525’600min (1year)]
Please refer to 9.2.3.1.3 for information on how to configure the statistics and history section.
A threshold can be defined on the average FLR to raise an alarm in case of high FLR. The alarm is
raised if the average FLR threshold is exceeded after completion of a statistics interval. After that the
alarm remains active until a statistics interval is completed with an average FLR below the threshold.
Note: In case of dual-ended synthetic LM using 1SL, only backward results are available.
The current Availability is evaluated immediately after each single FLR measurement. The size of the
sliding window (n) as well as the FLR threshold (C) between high and low FLR are configurable.
Availability Alarms also exist. Unlike for FLR alarms, Availability alarms are not only raised after
conclusion of a statistics interval, but immediately when the ratio of single measurements in the
current interval with an “Unavailable” result exceeds the configured Unavailability threshold.
Note: In case of dual-ended synthetic LM using 1SL, only backward results are available.
SAT can be performed prior to deploying the "live service” for verifying the quality requirements of a
MEF service. These requirements are:
Committed Information Rate (CIR)
Excess Information Rate (EIR)
Frame Loss Ratio (FLR)
Availability
Frame Delay (FD) (Round-trip based, i.e. fd = measured round-trip delay / 2)
Inter-Frame Delay Variation (IFDV) (Round-trip based, i.e. ifdv = abs(fd_t2 – fd_t1)
At the end of the measurement, a report is generated with the results, and PASS/FAIL is indicated.
The qualification measurement can also be performed in service, in parallel with running traffic
belonging to previously installed services on the ACCEED unit. No additional equipment is required to
perform SAT measurements with ACCEED. Traffic generator and analyzer are built in functions of the
ACCEED unit.
Up to 4 different customer traffic flows (Test CoS Instances) are emulated on the ACCEED unit, sent
out through the defined testport to the destination network element. The destination network element
has looped back activated which sent back these traffic flows with swapped source and destination
MAC addresses. At arrival on the SAT flow injecting ACCEED the flows are terminated and evaluated.
The necessary layer 2 loopback with MAC swapping can be performed with an ACCEED unit or any
capable 3rd party equipment. Note: A loopback without MAC swapping would also work, but may lead
to unpredictable traffic conditions (e.g. Port locks due to STP or overload conditions of MAC learning
events on old switching devices)
This methodology of measuring traffic during the activation phase of a service is based on the Y.1564
standard (formerly known as Y.156sam).
It closes the gap between RFC2544 method and the today’s service demand, by
Testing services along the network and not the maximum limit of just one network element
Verifying CIR and EIR profiles
Doing recurring frame delay and frame delay variation measurements
Measuring frame loss and availability
This advanced set of actions enables the network planners and service teams to bring up services
quickly and to troubleshoot in case of Service Level Agreement violations.
Y.1564 is separated in 2 phases: the Service Configuration Test, verifying the configuration of the
bandwidth profile parameters, and the Service Performance Test, proving the long term stability of the
new service.
Measurement Principle
The ACCEED acts like a 100 Mbit/s Ethernet traffic generator and detector. The traffic is injected into
the existing service through the generator ingress policy.
This test traffic is then forwarded via the WAN interface (or any other configured test port) to Carrier
Ethernet network to the remote Ethernet demarcation unit. This unit must be capable of swapping the
Source with the Destination MAC and loop the packets back to the local EDD.
On its way the test packets pass the egress policy of the local WAN, the ingress policy of the remote
WAN, the egress policy of the remote WAN and before passing the ingress policy of the local WAN
they are trapped to the analyzer.
In most cases services are defined by ingress policies. Therefore, by default only the ingress policy of
the remote ingress is tested with SAT. If the ingress policy of the service at the local EDD should be
tested, the ACCEED has the ability to use the same ingress policy of the LAN port. This is done by
applying the corresponding ingress modifier of the LAN port to the SAT/Test CoS Instance/Applied
Modifier.
Always take all ingress and egress bandwidth profiles along the SAT stream into account.
They may influence your measurement by additional bandwidth restrictions (smallest
information rate wins) or burst sequence cuts (smallest burst size wins)
For trustful measurements it is recommended to start with one bandwidth profile, the one
with the highest CIR/PIR values and to measure the throughput. Then add step by step the
other bandwidth profiles in decreasing bandwidth order and measure each time.
In principle initiating SAT measurements from both sides provide the most accurate results.
The test stream consists of performance packets for evaluating the maximum bandwidth based on CIR
and EIR, which is accumulated in “color blind” mode to one PIR, and timing packets for measuring the
roundtrip delay.
The format of the test frames is described in 9.3.3
The performance parameters FLR, Availability, frame delay, inter-frame delay variation are based on
measurements of CIR frames only.
This test will PASS, if the following parameters are matched for each instance
This test will PASS, if the following parameters are matched for each instance
rxIFDV IFDVThreshold
The sum of all txRates shall not exceed 100 Mbit/s. This allows the maximum for this test case of
Σ(CIR+EIR) = 100 Mbit/s.
9.3.2.3 Traffic Policing Test
Goal of this test case is to overshoot (by up to 25%) the throughput service limits and test the limitation
capabilities of the bandwidth profile rules. For each of the configured Test CoS Instance a throughput
and delay stream is created. The transmit rate depends on the ratio between CIR and EIR:
If CIR (5 EIR ) (true for most 2 rate three colour bandwidth profiles)
txRate CIR ( EIR 125 %)
Else (true for most single rate three colour bandwidth profiles)
txRate (CIR 125 %) EIR
The sum of all txRates shall not exceed 1000 Mbit/s. This allows the maximum for this test case of
Σ(CIR+EIR) = 800 Mbit/s.
This test is especially designed to get into congestion of the bandwidth profile under test. Therefore
not only the bandwidth parameters (CIR and EIR) need to be taken into account, but also the burst
buffer sizes (CBS and EBS). They define how many traffic bursts are allowed, before the bandwidth
profile starts dropping traffic.
Therefore the Y.1564 introduced a correction factor called MFactor adjusting the upper bandwidth limit.
Its range is between 0% and 25% and it depends on the burst buffer size, the test duration and the
txRate. The default value of the MFactor on the ACCEED is 10%. It can be roughly calculated with the
following formula, where the CBS&EBS are in [Bytes] and CIR&EIR in [kbit/s] for the Bandwidth profile
under test:
CBS EBS 1 8
M Factor %
CIR EIR SingleTestDuration 10
The maximum received data rate shall not exceed the sum of CIR and EIR corrected by the M Factor and
its lower limit is the CIR with its allowed frame loss ratio. The configured thresholds for frame delay
(FD) and inter frame delay variation (IFDV) need to be matched, too.
This test will PASS, if the following parameters are matched for each instance
This test will PASS, if the following parameters are covered for each instance
rxIFDV IFDVThreshold
rxAvailability AvailabilityThreshold
MAC DA 6 Bytes
MAC Header
MAC SA 6 Bytes
Tunnel sTag Primary TPID 2 Bytes
(optional) .1p bits + VLAN ID 2 Bytes
TPID = 0x8100 (fix) 2 Bytes
VLAN cTag (optional)
.1p bits + VLAN ID 2 Bytes
Ethertype 0x88’B7 2 Bytes
Albis OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier
Albis Ethertype (0x00’11) 2 Bytes
Sequenznummer 4 Bytes
Payload
Padding (0x00) variable
FCS 4 Bytes
Table 17 Format of Test Frames for throughput measurement
MAC DA 6 Bytes
MAC Header
MAC SA 6 Bytes
Primary TPID 2 Bytes
Tunnel sTag (optional)
.1p bits + VLAN ID 2 Bytes
TPID = 0x8100 (fix) 2 Bytes
VLAN cTag (optional)
.1p bits + VLAN ID 2 Bytes
Ethertype 0x88’B7 2 Bytes
OUI (0x00'1A'D0) 3 Bytes
Protocol Identifier Albis Ethertype 2 Bytes
(0x00’90, 0x00’91, 0x00’92)
TxTimeStampf 8 Bytes
(like DMM)
Payload RxTimeStampf 8 Bytes
(like DMM)
Padding (0x00) variable
FCS 4 Bytes
Table 18 Format of delay measurement frames
►Ethernet/Switch […]/SAT
Tunnel VLAN
Defines if a tunnel VLAN is added (common to all CoS Instances)
Tunnel VLAN ID
Sets the S-Tag VLAN ID in case of an VLAN tunnel
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 .. 1000000 kbit/s]
Committed information rate of the test traffic
EIR [0 .. 1000000 kbit/s]
Excess information rate of the test traffic
Measurements
For each of the measurement parameters FLR, Availability, FD and IFDV it can be defined
whether or not the results are included in the final test report. If one of the parameters is not
selected, the corresponding threshold is not relevant, and the measurement result for that
parameter is not a PASS / FAIL criterion for the test.
M Factor [0 .. 25 %]
Correction factor added on CIR+EIR threshold to compensate the start up effects of the burst
buffer settings (CBS and EBS)
FLR Threshold [0 .. 100.000 %]
Maximum Frame Loss Ratio Threshold to detect a PASS
Availability Threshold [0 .. 100.000 %]
Minimum Availability Threshold to detect a PASS
Availability Consecutive Measurements [1 .. 10]
Number of successful Availability Measurements necessary to get an accountable result
Availability FLR Threshold [0 .. 100.000 %]
This setting defines valid availability intervals in dependency of the FLR. If the Frame Loss Ratio is
below this threshold, the availability is accounted. See 9.2.3.2
FD Threshold [0 .. 5000000 us]
Maximum Frame Delay acceptable for a PASS
IFDV Threshold [0 .. 5000000 us]
Maximum inter frame delay variation acceptable for a PASS
VLAN Tagged
enabled: a VLAN Tag is attached to all test frames configured in this Test CoS Instance.
“enabled” is the default setting for Instance 2, 3 and 4.
disabled: test frames are untagged
Assigned VLAN ID [1 .. 4094]
This VLAN ID value is always attached to the VLAN Tag in case VLAN tagging is enabled,
otherwise for untagged frames it defines the internally assigned VLAN ID
Assigned CoS Value [0 .. 7]
This .1p value is always attached to the VLAN Tag in case VLAN tagging enabled
Accepted CoS Value
Outgoing CoS: Received SAT frames are only accepted by this CoS instance if their CoS value
is identical to the CoS value of frames transmitted by this CoS instance. Normally,
the Outgoing corresponds to the Assigned CoS Value, but the Applied Modifier
could force an Outgoing CoS Value which is different from the originally Assigned
CoS Value (if no VLAN tunnel is present). “Outgoing CoS” is the default
configuration.
Any: This CoS instance accepts received frames with any CoS value. Note: In this
case, no other CoS instance must be activated with the same VLAN ID.
CoS 0 .. Cos 7: This CoS instance only accepts received frames with this specific CoS value
Accepted Tunnel CoS Value
Outgoing CoS: Received SAT frames are only accepted by this CoS instance if their tunnel CoS
value is identical to the tunnel CoS value of frames transmitted by this CoS
instance. Normally, the Outgoing corresponds to the Assigned CoS Value, but the
Applied Modifier could force an Outgoing CoS Value which is different from the
originally Assigned CoS Value. “Outgoing CoS” is the default configuration.
Any: This CoS instance accepts received frames with any tunnel CoS value.
CoS 0 .. Cos 7: This CoS instance only accepts received frames with this specific tunnel CoS
value
Applied Modifier
To verify correct configuration of an ingress policy, an ingress modifier can be applied to SAT
frames. For example, if an ingress policy is applied at a UNI port, the modifier of that policy can
also be applied to SAT frames.
Frame Pattern
“Fixed Size”: All test frames do have the same length
“EMIX”: Frames are sent in a repeating sequence of configurable frames with sizes 64B, 128B,
256B, 512B, 1024B, 1280B, 1518B or 2048B
EMIX Frame Sizes
Selectable frame sizes 64B, 128B, 256B, 512B, 1024B, 1280B, 1518B or 2048B
Frame Size [64 .. 2048 bytes]
Sets the frame length of all test frames, if frame pattern is “Fixed size”
The “Frame Command” and “Redirected Port” parameters of the Applied Modifier have no
influence on SAT frames. Also, if a tunnel VLAN is set in the general SAT configuration (
9.3.4), the “VLAN Command” and “Primary VLAN ID” of the Applied Modifier are ignored. If
no tunnel VLAN is set in the general SAT configuration, the “VLAN Command” of the
Applied Modifier should be set to its default value for correct operation.
All other parameters of the Applied Modifier (like Bandwidth Profile, QoS attribute
manipulations) are also relevant for SAT frames
Test execution
The SAT can be executed by pressing the “Start” button in the Configuration tab under
Ethernet/Switch […]/SAT. It can be terminated any time during the test phase by pressing the “Abort”
button.
The test report can be displayed anytime during the tests showing the current status of the test cases
by pressing the “Test Report …” button.
At the end of the test the test report automatically pops up with the final results. It can be stored as a
text or pdf file by pressing the “Save As…” button on the bottom of the test report window.
Results
Test Report
The test report has two sections: First the setup parameters and second the measurement results.
In the first section the basic configuration of the System (Date and Time, Firmware Version, Hardware
ID and Slot number) and the test port (Test groups enabled, color mode, color method, port name,
MACs and Tunnel VID) are printed. It is followed by the configuration of each Test CoS Instance that
is enabled (CIR, EIR, M, Pattern, Size, VID and CoS, as well as FLR, Availability, FD and IFDV
thresholds, if the corresponding measurement parameters are enabled).
The second section contains the results of each single test parameter that is selected in the Test CoS
Instance configuration. The headline of each test section (service configuration test or service
performance test) shows the overall result.
A FAIL of one of the test parameters leads to a FAIL of the whole Test Cos Instance and is shown in
the headline. This FAIL leads then to a FAIL of the whole test section.
Additionally, the results for each single EMIX frame size are displayed if the detailed test reports are
enabled. The results are not assessed with a “FAIL/PASS”.
At the end of the test, the test report automatically pops up with the final results. It can be stored as a
text or pdf file by pressing the “Save As…” button.
The default filename for the test report is generated from the unit’s Management IP and its slot
position number, e.g. “Test_Report_192.168.1.1_S13”
10
CES – Circuit
Emulation for TDM
Services
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.
Technical Challenges
The different approach of transporting the TDM service with CES compared to the traditional TDM way
implies some technical challenges which need to be carefully looked at when considering an
introduction of CES.
The challenges are:
Clock recovery and synchronization
With a packet network, the connection between the ingress and egress frequency is broken,
since packets are discontinuous in time
Delay and Jitter
Packetization and jitter buffer adding delay which are crucial to some applications (e.g. voice,
mobile, backhauling)
Frame Loss and Reordering
Packets can be dropped in the packet network or packets may not arrive in the order they
have been sent out.
The answers to these challenges are addressed by the ACCEED CES solution and are explained in
the following chapters.
Payload Type
TDM signals can be divided in structured and unstructured signals.
Structured (structure aware) TDM consists of a framing with time slots as defined in ITU-T G.704
where as unstructured (structure agnostic) TDM is a bit stream with no framing information.
The TDM payload type therefore needs to be defined in the CES IWF (Inter-Working Function).
Structure aware TDM payload is referred to as
CESoPSN Circuit Emulation Service over Packet Switched Network
With CESoPSN the configured subscriber rate (nx64kbit/s) is transmitted by the CES IWF.
Time slot zero is not transported over the packet network. The time slot zero is generated at the
far end IWF and added to the TDM frame. The maximum subscriber rate with CESoPSN is 31 TS
or 1’984 kbit/s (time slot 1 ..32).
Example: A service with 512 kbit/s (8 TS) should be transmitted via CESoPSN. The TDM service
must arrive in timeslot 1-9 at the ACCEED. All information in TS0 (e.g. SA-Bits) are not forwarded.
With SAToP the complete TDM (32 TS) bit stream is transmitted and the data rate is 2’048kbit/s.
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.
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.
L and M bit
The local TDM failure indicates a TDM defect impacting the TDM data.
When the L bit is set, the payload of the CES packet is set to 1 (one).
The M bit is set to supplement the meaning of the L bit.
The following local TDM failure indication are mapped to the L- and M-bit with ACCEED:
L M
Interpretation
Bit 4 Bit 6 Bit 7
0 0 0 Indicates no local TDM defect detected.
0 1 0 Reports the receipt of RAI or RDI at the local TDM interface in case the
framer is set to termination or monitoring. CES-RAI is raised at the remote
IWF.
1 0 0 Indicates a local TDM defect that triggers CES-AIS generation at the
remote CES IWF.
Local TDM defect is LOS in case the framer is set to transparent operation
and LOS, AIS, or LFA in case the framer is set to termination or
monitoring.
R bit
When the R bit is received, it indicates that the remote IWF did not receive the CES frame and
consequently has raised a LOF alarm. AIS is sent the TDM interface.
Thus the setting of the R bit indicates failure of the connection in the opposite direction. This indicates
congestion or other network related faults.
The fragmentation bits (FRG) are not used with ACCEED and are set to 0 (zero).
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.
Framer
The Framer is an optional component that operates on the TDM interface and produces the service
(e.g. G.704 or n*64 kbit) that is emulated across the packet network.
In case of ACCEED the framer can be configured to operate the following modes:
Transparent: signal passes unchanged
Monitoring: signal passes unchanged, framing and CRC4 errors are evaluated
Termination: frame is regenerated, CRC4 section is terminated
There are two basic interfaces in the TDM domain. These are indicated in the
TDM Interface
At this interface the actual TDM service is handed off to the customer or TDM network operator. It
therefore provides a physical connector. In case of ACCEED it is a RJ-45 connector for the E1 service.
The TDM service can be transported in two ways, structure-agnostic or structure-aware. See also
10.1.4.
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.
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).
Packetization
The size of TDM payload per packet influences the following parameter:
Bandwidth Efficiency
The larger the payload per CES packet, the lower the overhead ratio. Larger packets therefore
result in better bandwidth efficiency.
PayloadSize [ Bytes ]
BandwidthEffciencyCESoEth[%]
30 PayloadSize [ Bytes ]
PayloadSize [ Bytes ]
BandwidthEffciencyCESoMPLS [%]
34 PayloadSize [ Bytes ]
SubscriberRate[kBits / s ] * 100
TotalBandwidth[kBit / s ]
BandwidthEffciency[%]
Packetization Delay
The packetization delay is dependant on the choosen payload size per packet and the TDM
subscriber rate.
PayloadSize [ Bytes]
PacketizationDelay [ms ]
8 * SubscriberRate[TS ]
Note: in case of SAToP payload type, the subscriber rate is always equal to 32 time slots [TS]
The optimal compromise between bandwidth efficiency and packetization delay is depending on the
operators requirements.
Example:
The default CES packet payload size in ACCEED is 256 Bytes which results in a packetization delay
of 1ms for a subscriber rate of 32TS (2’048 kBit/s). The resulting Bandwidth Efficiency is 89.5% for
CESoEth and 88.3% for CESoMPLS. This equals 2’288 kBit/s and 2’320 kBit/s respectively on the
Ethernet transmission interface.
Jitter Buffer
When packets arrive at the far end CES IWF, they can be out of sequence or arrive too early to be
delivered to the TDM interface. The jitter buffer allows the reordering of the packets to compensate the
packet delay variation (PDV) to a certain extent, depending on the chosen jitter buffer size.
The reordering of the packet is based on the sequence number contained in the control word of each
CES packet. When a packet is received, the sequence number is verified and reordering is done if
applicable.
The jitter buffer is initialized to work at a fill grade of 50%. This leads to an initial delay caused by the
jitter buffer of 50% of the maximum delay variation that can be compensated by the jitter buffer.
The amount of delay and PDV can change dynamically in the packet network depending on e.g. the
load in the network elements.
To compensate this effect, ACCEED applies an algorithm which automatically adjusts the delay of
each packet to achieve a constant delivery of CES packets to CES IWF. This automatic adjustment of
the jitter buffer delay does not change the maximal size of the jitter buffer.
Note: In case of increased packet delay, the compensation of the packet delay variation is smaller
than in case of decreased packet delay.
The optimal jitter buffer size can only be set, if the maximum PDV is known. Since the PDV is
dynamic, the max. PDV need to be monitored over a period of time.
Refer to 10.4.2 for information on how to read out the max. PDV with the LCT+
A3118-X654-R620-01 333 / 398
ULAF+ 10 - CES – Circuit Emulation for TDM Services ACCEED 2104 Manual
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:
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 and no
more than 256 times the configured payload size.
Please note that packets with large MTU size being transported over a low speed SHDSL
link can add high jitter and therefore can be critical for a correct operation of the CES
service. A packet with MTU = 1500Bytes being transported over a single copper wire pair
at SHDSL data rate of 1Mbit/s, introduces a jitter of 12ms to the CES packets.
Therefore carefully plan the jitter buffer size in context of all traffic being sent over the
SHDSL link. In-band Management and OAM traffic also need to be taken into account.
Operator Hint:
Since the maximum PDV is normally not know when configuring the CES IWF for ACCEED, the
following procedure could be followed to define the jitter buffer size:
1. Establish the CES service with the default jitter buffer size of 4’096 Bytes.
Read out the measured maximum PDV after the value has reached the maximum as
described in 10.4.2.
2. Calculate the jitter buffer with the formula below. The
2 * max .PDV [ms ] SubscriberRate[kbit / s ]
JitterBuffer[ Bytes ]
8
3. Round up the calculated jitter buffer size to the next multiple of the payload size and enter the
jitter buffer size in the packet settings.
Example: the calculated value is 591 Bytes. The configured payload size is 256 Bytes.
The recommended jitter buffer size therefore is 768 Bytes.
4. Monitor the CES performance if there are any jitter buffer overflows or under runs.
5. In case of overflows/under runs, increase the jitter buffer size by multiples of the payload size.
Actual values of the packetization- and jitter buffer delay are provided by the ACCEED unit. For more
information please refer to 10.3.2 for packetization delay and 10.4.2 for jitter buffer delay.
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.
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 10.3 for more information on the ACCEED 2104 CES configuration
options.
The ACCEED 2104 provides four E1 TDM interface which is represented as TDM1–TDM4
in the LCT+ view as shown in the figure below.
Enabling the CES function and the TDM interface can be done here:
CES IWF/Local/TDM/TDM1/2
Mode [Clock, TDM] Clock: 2 MBit or 2048 kHz clock, see 11.4.2
TDM: 2 MBit/s clock
Impedance [120, 75 Ohm] Impedance of TDM interface
Description Individual interface description with up to 64 characters, e.g. Service
Name or Location
Please refer to 10.1.6 for more information on jitter buffer- and payload size.
Addressing Mode [Ethernet, IP], please refer to 10.3.2.1 for more information
Destination MAC Address [00:00:00:00:00:00, destination MAC address], relevant only
in Ethernet addressing mode
Pseudowire VLAN Defines if a VLAN tag is added to CES data (payload) AND control
traffic
Pseudowire VLAN ID [1 .. 4094] VLAN ID that is assigned to CES data and control traffic
of this pseudowire
CoS Value [0 .. 7] CoS value that is assigned to CES data traffic of this pseudowire
Transmit Queue [0 .. 7], Transmit queue at egress port that is assigned to CES data
traffic of this pseudo wire
Jitter Buffer Size [2 ..4’096 .. 8’192] Please refer to 10.1.6 for more information
Maximum PDV Compensation The maximal possible PDV compensation based on the
configured jitter buffer size. This value is calculated and
therefore read only.
Payload Size [1 .. 256 .. 1’023] Please refer to 10.1.6 for more information
Packetization Latency Delay caused by the packetization. This value is calculated
and therefore read only.
The assigned VLAN ID and CoS value must be the same in the local and remote packet
configuration of the IWF.
With the Ethernet addressing mode, the MAC address of the remote CES function must be known
and is entered in the field named “Destination MAC Address”. The local MAC address of the CES
function is displayed in the LCT+ under CES IWF/Local.
With the IP addressing mode, the destination MAC address is resolved based on the ARP process
and is therefore set in the “Resolved Destination MAC Address” field automatically.
In order to do so, the local and remote CES functions must be configured with appropriate IP
addresses, netmask and gateway information. Additionally, CoS value and transmit queue can be
configured for the CES control packets. The tagging configuration of the CES control packets is done
in the CES packet configuration section for each pseudo wire individually and is equal to the tagging
and VLAN ID of the CES data traffic (payload). Please refer to 10.3.2 for more information on the
CES packet configuration.
If the MAC address cannot be resolved a CES-ARE (Address Resolution Alarm) alarm is raised.
Please refer to 10.5.2 for more information on trouble shooting CES.
The configuration of the IP addressing and control traffic for the CES function can be done
here:
CES IWF/Local
MAC Address MAC Address of the CES function. Read only value
The Addressing configuration must be done on both ends of the pseudo wire and must
match the remote information. E.g. the MAC or IP addresses respectively must match.
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)
The CES IWF packet performance is consisting of the packet statistic counters and the
CES jitter buffer performance.
The Packet Statistics can be displayed as a continuous counter and as history counter with
definable interval duration and stored number of intervals.
Up to 5 history counters can be added. Refer to 10.4.3 for the activation and
configuration of the packet statistics.
The packet and jitter buffer performance can be found here:
CES IWF/Local/TDM/TDM1/Packet
Please note, that the statistics view can be switched between “Continuous” and the defined
historic counters.
CES IWF/Local/TDM/TDM1/Packet/Statistics/Historic[]
└110x_1404_1416_2104_2202_End
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.
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.
The alarms presented by the ACCEED unit provide a good entry point for CES trouble shooting.
See 10.4.4 for all alarms related to CES and TDM.
For the CES alarms (CES LOF), various problems might be present.
SHDSL data rate is not sufficient (CES LOF).
See utilization of CES egress port. Refer to 8.10.6 for port utilization
The Packet configuration (Encapsulation and Payload Type) must match between both CES
IWF. Example: VID=22, CoS=7, CESoPSN, Payload Size=256
The Configured VLAN ID in the packet section must be existing in the VLAN DB and the
tagging command must be set to “Primary Tag Only” for the respective CES egress port.
Verify CES packet and jitter buffer performance, see 10.4.2
Statistics: are the lost, early or late frames counted?
CES: are jitter buffer overflows, under runs counted?
Adjust the jitter buffer size accordingly, see 10.1.6
Verify that the CES packets are sent to the correct egress queue and no packets are dropped
in this egress queue.
The CES-ARE alarm indicates a connectivity problem, preventing the automatic MAC
exchange between the CES IWF. The connectivity between the CES IWF on the IP layer can
be tested based on ping messages as shown in the figure below:
The CES stream generated by the IWF is directly sent to the egress queue of the egress
port configured in the packet section. Egress modifiers therefore do not apply to the CES
packets. In the ingress direction, the CES stream is directly linked to the CES IWF before
any ingress modifier can be applied. Consequently, statistics and utilization which base on
└110x_1404_1416_2104_2202_End
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.
System Log
Board/Local/Information
Board/EFM-NT/[x]/Information
System Log lists the events on the ACCEED and can be used as source for trouble
shooting.
Entries listed under “NVD entries” are critical events stored to a non volatile memory since
the first start of the ACCEED unit.
“actual entries” lists all events since the last startup of the ACCEED device.
The events are listed in chronological order with the most recent at the button of the list.
The example below shows a System Log excerpt of an ACCEED 1416 unit.
Save As… saves the system log list in a text or pdf file
Cancel closes this window
Refresh updates the System Log window
Ressources
Board/Local/Information
Board/EFM-NT/[x]/Information
The resource information provides insight in the ACCEED units for trouble shooting
purposes. Up time and system load a process list and memory usage are displayed.
In case of the ACCEED desktop units, temperature of the CPU and the FPGA, and fan
speed information are displayed additionally.
The resources information window also indicates percentage usage of certain system resources such
as policy rules, counters, etc…
Additionally in case of shortage of system resources (resource shortage alarm 12.3.23), the
reasons are stated here:
“Too many EVC, PTP or Inband Management resources used”. Solution: reduce number of EVC
or CoS Instances
“Too many policy rules used” Solution: reduce the number of policy rules
“Too many policy ingress/egress metering entities used”. Solution: reduce number of
ingress/egress bandwidth profiles
“Too many transmit buffer resources used”: Queue profiles attached to active Ethernet ports
assign more buffers than available in the buffer pool. Additional packet drops due to buffer under
run may occur in heavy overload conditions. Solution: reduce number of active (enabled) ports
and/or reduce the number of buffer blocks in the queue profiles
“Too many Service OAM resources used”. Solution: reduce number of CCM or performance
measurement instances. Reducing the number of associated VLANs, or using Down MEPs
instead of Up MEPs may also help.
“Too many remote MEP resources used”. Solution: reduce number of configured remote MEPs or
reduce CCM intervals
“Too many performance statistic resources used”. Solution: reduce number of enabled historic
statistics.
Inventory
Board/Local/Information
Board/EFM-NT/[x]/Information
The inventory lists all devices in the aggregation and the array respectively.
The information listed under Inventory is depending on the ACCEED unit and application.
The example below shows an ACCEED 1416 plug in (LT) to desktop (NT) application with 4
SHDSL ports being aggregated and assigned to PAF A. In the Aggregation section you see
the 2 SHDSL links and the connected NT devices. All of them end on the same NT device,
because the serial number of all NT links is the same. The Text “S13Px” describes here that
all used SHDSL are connected in Slot 13. In the Array section shows that via the SCC bus
are connected 4 more LT are connected (Slot 12, 14-16). The top LT in the list is the local
one which is connected to NTs via SHDSL and logically to the EFM-NT A. The difference of
the EFM-NT_A to the SHDSL lines (serial number) signals, that the EFM-NT_A is not on the
same NT as the SHDSL lines are terminated, but in a device connected to the SCC ring of
them.
Suppress Power Failure if enabled, no alarm is raised in case of a DC power failure
Minimum Trap Level when an alarm is raised and the defined severity of this alarm
is equal or above the trap level, a respective alarm trap is
generated. The trap level is applied to the whole ACCEED
unit.
Inhibit LOSWS During UAS if enabled, LOSWS counter stops counting during
Unavailable State (this method is mainly used by DSLAMs).
LOSWS equals then the number of retraining seconds and
heavy error conditions.
Severity
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.3 Local
Information
The board information are accessible under Board/Local/Information
The values of the active and passive FW version reflect the actual FW loaded on the
ACCEED unit.
The housing is depending on the ACCEED unit variant, being a desktop or plug in module.
The CLEI (Common Language Equipment Identification) code is individual for each ACCEED
unit type and allows to identify and track the network equipment.
The example blow represents an ACCEED 1416 plug in unit.
SCC Configuration
Not applicable.
Maintenance
Possible maintenance reasons for ACCEED 2104 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
Time Settings
For the time setting configuration please refer to 5.8.8
Management Access
For the management access options please refer to 5.8.2
11.3.5.1.2 Authorization
Additionally, the server informs the client of the access privileges attached to the user (authorization).
Currently two access privilege levels are supported, Administrator (full access) and Maintenance (read-
only access and maintenance functions). The server can communicate this authorization information
with RADIUS attribute value pairs (AVP) carried in the access accept messages.
ACCEED uses the “Service-Type” attribute. If ACCEED receives an access accept message with the
“Service-Type” attribute set to the value “Administrative” (value 6), the corresponding user is granted
Administrator privileges. If the “Service-Type” AVP has a different value or is missing, the user is set to
Maintenance rights.
The procedures for a combined use of local and RADIUS authentication methods are described in the
following two flow charts.
11.3.5.1.5 Configuration
Board/Local/Management Access/Authentication
Zero Touch Provisioning is available for all ACCEED units running in CPE mode. For the LT /NT
mode, the configuration is distributed to the NT(s) via the LT.
The mechanism is based on standard protocols which allow an integration of the provisioning process
into the customer environment. The communication for the provisioning process is done via the inband
management interface.
The CPE can request the following parameters via DHCP during the initial provisioning phase,
depending on the settings in the ACCEED unit.
Management IP, Netmask and Default Gateway
Management VLAN ID
Management VLAN CoS
NTP Server
Bootfile
TFTP Server Address
Specific ACCEED device configuration (cfg file)
Step by step
1. ACCEED requests an IP address, net mask and default gateway from the DHCP server
2. If required,
a) the VLAN configuration can be changed
b) the IP address, net mask and default gateway is requested again, now in the configured
VLAN
3. Request of boot file which contains further provisioning information
4. If applicable, the firmware is updated
5. If applicable, a configuration file is received from a tftp server and applied to the ACCEED unit.
The following parameter can be set in ACCEED for zero touch provisioning
Board/Local/Management Access
Board/Local/Management Access/Inband
Please note, the ACCEED CPEs are prepared to support the zero touch provisioning
process, but integration in the specific environment is always required.
11.4 Synchronization
Introduction
ACCEED 2104 is an Ethernet device. Due to Ethernet’s asynchronous packet character there is no need
for synchronization for basic data transmission services. However, timing critical applications like mobile
backhaul or CES require accurate synchronization on remote locations. This is why ACCEED offers a
comprehensive feature set to provide high quality timing to customer locations.
ACCEED’s internal high-quality PLL (phase locked loop) can be synchronized to one of several possible
clock sources: SyncE, IEEE1588v2 and external reference inputs (HDB3 or 2MHz). The selection of the
input is done automatically, based on a configurable priority list. The active reference clock can then be
forwarded to different output interfaces.
This also allows the use of ACCEED 2104 as a clock interface converter, e.g. to convert from SyncE to
a 2 MHz clock interface or vice versa.
Active … State [Warmup, Free Run, Fast, Normal, Bridging, Holdover, Recovery, Hand Set]
Actual State of the frequency/time clock
Active … Source [Internal, TDMx. SFPx, Px]
Actual source port of the frequency/time clock
Active … Quality [Quality Level defined in 11.4.4]
Actual source quality of the frequency/time clock
Active … Priority [0 .. 255]
Actual source priority of the frequency/time clock
Current PTP Date and Time
Actual date and time transported within the PTP
Current Leap Seconds
Actual delta seconds due to transmission delays between UTC and TAI
Leap Seconds [0 … 35 … 2147483646]
Number of delay seconds between UTC and TAI (International Atomic Time) in case they are
not transmitted by time source.
Please note: NMS, Inband, PTP Master and PTP Slave IP Addresses must be in different
subnets.
Please note, the ACCEED PTP supports time stamping in 100 Mbit or 1000 Mbit full
duplex mode. 10BT is not supported.
The DNU (Do Not Use) quality level is also sent out on interfaces that are currently used as active clock
source, in order to prevent timing loops.
Priority
Clock priority can be configured to the following values:
Range: 0..255
0 defines the highest priority
255 represents the lowest priority
Clock Sources
The following section shows the configuration of the different possible clock sources. Not all interfaces
shown in the screenshots may be available on a specific device.
For frequency synchronization up to 4 frequency inputs can be used (each TDM interface, 2 out of 4
SyncE electrical and 2 out of 4 SyncE optical Gigabit Ethernet).
For phase synchronization one PPS input can be used (BNC-1PPS or ToD-1PPS)
Please note, if more than the number of allowed clock inputs is used, the inputs with
lowest priority get into state “spare” which means, the ACCEED OS cannot determine
whether a valid signal is on this input or not.
E.g. the ports SFP1-4 carry valid SyncE signals, all selected as “Enable clock input” and
have the same Priority=255. But only 2 SFP can be used and observed. The SFP3 and
SFP4 status will get “spare” and will not be used as clock source, since SFP1 or SFP2 will
be disabled as “clock input”.
Board\Local\Clocking\PTP
Board\Local\Clocking\PTP\Slave
Enable
Enables the PTP Slave module
Use For Time
Enabled: PTP Slave clock is used for time synchronization.
Use For Frequency
A3118-X654-R620-01 369 / 398
ULAF+ 11 - General Board settings ACCEED 2104 Manual
Board\Local\Clocking\PTP\Slave\Parents[]\Parent x
Port
Transmit port of the PTP traffic.
A3118-X654-R620-01 370 / 398
ULAF+ 11 - General Board settings ACCEED 2104 Manual
IP
IP Address of the clock master/source.
Quality [2, 4, 8, 11]
Quality of the clock source.
Trust Quality
Enabled: trust the quality level stored in the announce message.
Priority [0 … 255]
Priority of the clock source in case of equal quality level.
Trust Priority
Enabled: trust the priority value stored in the announce message.
Board\Local\Clocking\PTP\Master
Enable
Enabled: PTP master function enabled. Slaves will now be supported.
IP Address
Own IP Address of the clock master.
Note: Must be in a different subnet than inband and outband NMS and the PTP Slave function
of this ACCEED unit.
IP Netmask
Own IP netmask of the clock master.
Client Ports
Ingress ports of PTP clients. PTP messaged at disabled ports will be dropped
Master VLAN
Enabled: VLAN ID is used for the PTP messages.
A3118-X654-R620-01 371 / 398
ULAF+ 11 - General Board settings ACCEED 2104 Manual
Master VLAN ID
VLAN ID of the PTP messages.
CoS Value [0 .. 7]
.1p priority value of the VLAN Tag in case of tagged communication of the PTP master
Transmit Queue [0 .. 7]
Transmit queue used for the TX communication frames
Two Step Clock [disabled .. enabled]
Enabled: use Two Step Clock operation. Disabled: Timestamp information is included in the
first packet
The performance Tab of the PTP menu delivers counters to analyze and optimize the PTP
transmission within the PTP network.
Board\Local\Clocking\PTP
Please note, the minimal round trip delay may contain large values, if PTP is only used for
frequency synchronization, but not time.
Board\Local\Clocking\PTP
The “Trust SSM” parameter enables automatic configuration of the clock quality via received
SSM. The “Send SSM” parameter enables sending of SSMs with the quality of the currently
active clock source. Both parameters are only relevant if Clock Type is set to “2 Mbps”.
SyncE is not supported with electrical SFP modules and 100Base-FX SFP modules.
Electrical ports in 1000Base-T mode can only be used as SyncE clock inputs if the GbE
clocking mode (Ethernet/Switch … /Lan Ports/Px/Gbe Clocking Mode) is set to “Manual
(Slave)”.
Board\Local\Clocking\LAN Ports
Board\Local\Clocking\SFP Ports
The “Trust SSM” parameter enables automatic configuration of the clock quality via
received SSM.
The “Send SSM” parameter enables sending of SSMs with the quality of the currently
active clock source.
Board\Local\Clocking\Internal
SyncE is not supported with electrical SFP modules and 100Base-FX SFP modules.
11.4.6.3 PTP
To be described
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.
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
To find out the exact alarm cause the LCT+ must be utilized. Information about
debugging with LCT+ can be found in 12.3.
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
CES-ARE Alarm
description Adress Resolution Error at CES interface detected
alarm location CES
defect location CES IWF
default severity Critical
default logging Log
LED signaling None
debug hints Check the local and remote CES configuration
CES-LOF Alarm
description Loss of Frames at CES interface detected
alarm location CES
defect location CES IWF
default severity Critical
default logging Log
LED signaling None
debug hints Check the connectivity between the two CES IWF
CES-RAI Alarm
description Remote Alarm Indication at CES interface detected
alarm location CES
defect location CES IWF
default severity Minor
default logging Log
LED signaling None
debug hints Check the TDM interface at the remote IWF
Equipment Alarm
description Equipment failure
alarm location Equipment
defect location Equipment
default severity Critical
default logging log
LED signaling none
debug hints The HW is damaged. Replace the unit.
LAG-Aggregation Loss
description All members ports of the LAG port are down
alarm location Aggregation
defect location ……………..…
default severity Critical
default logging log
LED signaling ……………..…
debug hints ……………..…
LAG-Aggregation Mismatch
description Link Aggregation is not set up properly
alarm location Aggregation
defect location ……………..…
default severity Critical
default logging log
LED signaling ……………..…
debug hints ……………..…
LFP Alarm
description Link failure propagation (link forced down due to PAF alarm)
alarm location ETH Port
defect location ETH Port
default severity Critical
default logging log
LED signaling none
debug hints Possible causes are
Aggregation Loss (configurable)
Partial Aggregation Loss (configurable)
Configuration error
Check the PAF / SHDSL line alarms and the LFP configuration
SOAM-AIS Alarm
description AIS messages received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling None
possible causes Check for possible loss of continuity on lower layer
SOAM-Avail Objective
description Availability objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging Log
LED signaling None
defect(s)
possible causes ……………………….
SOAM-ErrorCCM Alarm
description Invalid CCM received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling None
defect(s)
possible causes A service OAM MEP is receiving invalid CCM packets
Packets are not compatible (e.g. interval configuration)
Malformed packets
Service OAM debug information is available via LCT+. See 9.2.1.5, in
the section Last CCM Failure parameters.
SOAM-FDICSF
description Client Signal Fail (Forward Defect Indication)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with FDI flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.
SOAM-FD Objective
description Frame delay objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….
SOAM-FLR Threshold
description Average Frame loss ratio has exceeded the configured threshold
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….
SOAM-IFDV Objective
description Inter-Frame delay variation objective has been exceeded
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes ……………………….
SOAM-LCK Alarm
description LCK messages received
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging log
LED signaling none
possible causes Intended Maintenance Mode (not a defect)
SOAM-LOSCSF
description Client Signal Fail (Loss of Signal)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with LOS flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.
SOAM-RDICCM Alarm
description Remote defect indication
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging Log
LED signaling none
debug hints A MEP in the domain has loss of continuity
Service OAM debug information is available via LCT+. See 9.2.1.5, in
the section Last CCM Failure parameters.
SOAM-RDICSF
description Client Signal Fail (Reverse Defect Indication)
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Critical
default logging log
LED signaling none
defect(s)
possible causes CSF messages with RDI flag set received. Alarm is only raised if CSF is
enabled in the corresponding domain.
SOAM-RemoteCCM Alarm
description CCMs missing
alarm location MEP
defect location Remote MEP (CCM Database)
default severity Minor
default logging log
LED signaling none
debug hints Loss of continuity: at least 3 subsequent CCM packets have been lost (or
received too late). Loss of continuity may be caused by:
Interruption in the connection
Configuration error
SOAM-XconCCM Alarm
description Cross connect error
alarm location MEP
defect location MEP
default severity Critical
default logging log
LED signaling none
debug hints This alarm indicates, that a service OAM MEP is receiving alien CCM
packets
CCM packets from a different domain (CCM leak)
CCM packets from a lower CCM layer (configuration error CCM in lower
layer not terminated)
Service OAM debug information is available via LCT+. See 9.2.1.5, in
the section Last CCM Failure parameters.
SFP-Incompatible Alarm
description SFP module is incompatible
alarm location SFP
defect location SFP
default severity Critical
default logging log
LED signaling RED SFP LED Blink-Slow
debug hints The equipped SFP module type is not supported.
SFP-Missing Alarm
description SFP module missing
alarm location SFP
defect location SFP
default severity Critical
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.
TDM-AIS Alarm
description Loss of Frame Alignment at TDM/Clock interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Critical
default logging Log
LED signaling CLOCK RED Blinking-Fast
debug hints Check the TDM device connected to ACCEED
TDM-BER3 Alarm
description Bit Error Rate of 10E-3 at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Critical
default logging Log
LED signaling none
debug hints Check the TDM device connected to ACCEED
TDM-BER6 Alarm
description Bit Error Rate of 10E-6 at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Minor
default logging Log
LED signaling None
debug hints Check the TDM device connected to ACCEED
TDM-LFA Alarm
description Alarm Indication Signal at TDM interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Minor
default logging Log
LED signaling CLOCK YELLOW ON
debug hints Check the TDM device connected to ACCEED
TDM-LOS Alarm
description Loss of Signal at TDM/Clock interface detected
alarm location TDM / G.703
defect location TDM interface
default severity Critical
default logging log
LED signaling CLOCK RED ON
debug hints Check the TDM connection and input signal
TDM-RAI Alarm
description Remote Alarm Indication at TDM interface detected
alarm location TDM
defect location TDM interface
default severity Minor
default logging Log
LED signaling none
debug hints Check the TDM device connected to ACCEED
If the fan is in operation, the temperature alarm is raised at about 65°C environment
temperature and the device is shut down at about 80°C.
If the fan is out of order the temperature alarm will likely occur at any environment
temperature and the device is shut down at about 20°C.
The device is specified up to 55°C environment temperature and must never be used at
higher temperatures
13
References
[6] ULAF+ User Manual (UMN) for the Advanced Bridge and Router Module
Albis Technologies Ltd
A3118-X300-H100-*-7619
[15] ETSI TS 101 524 - Symmetric single pair high bit rate digital subscriber line (SDSL)
transmission system on metallic local lines
[17] ITU-T Recommendation Y.1731 - OAM functions and mechanisms for Ethernet based
networks
14
Glossary
Term Explanation
AcI Access Integrator the ULAF+ Network Management System
BER Bit Error Rate
BERT Bit Error Rate Test
BiDi Bidirectional transmission over a single fiber
The Bundling service attribute enables two or more VLAN IDs to be
mapped to a single EVC at a UNI. With bundling, the provider and
subscriber must agree on the VLAN IDs used at the UNI and the
Bundling mapping between each VLAN ID and a specific EVC.
A special case of bundling is where every VLAN ID at the UNI
interface maps to a single EVC. This service attribute is called all-to-
one bundling.
Committed Burst Size, CBS is a bandwidth profile parameter. It
CBS limits the maximum number of bytes available for a burst of service
packets sent at the UNI speed to remain CIR-conformant.
CCM Continuity Check Message (Service OAM)
CE Customer Edge, Equipment on the Subscriber side of the UNI.
CES Circuit Emulation Service
CF is a bandwidth profile parameter. The Coupling Flag allows the
CF choice between two modes of operation of the rate enforcement
algorithm.
Committed Information Rate, CIR is a bandwidth profile parameter.
It defines the average rate in bits/s of service packets up to which
CIR
the network delivers service packets and meets the performance
objectives de-fined by the CoS Service Attribute.
A set of service packets that have a commitment from the Service
Class of Service
Provider to receive a particular level of performance.
Information derivable from a) the EVC to which the service packet is
mapped, b) the combination of the EVC to which the service packet
is mapped and a set of one or more CE-VLAN CoS values, c) the
Class of Service Identifier combination of the EVC to which the service packet is mapped and
a set of one or more DSCP values, or d) the combination of the EVC
to which the service packet is mapped and a set of one or more
tunneled Layer 2 Control Protocols.
Color Mode, CM is a bandwidth profile parameter. The color mode
CM parameter indicates whether the color-aware or color-blind property
is employed by the bandwidth profile
CFM Continuity Fault Management
A Bandwidth Profile property where a pre-determined level of
Bandwidth Profile compliance for each service packet is taken into
Color-aware
account when determining the level of compliance for each service
packet.
A bandwidth profile property where a pre-determined level of
bandwidth profile compliance for each service packet, if present, is
Color-blind
ignored when determining the level of compliance for each service
packet.
CoS Class of service, corresponds to IEEE 802.1p priorities
DNU Do Not Use (for synchronization)
DSCP Diffserv Codepoints, extended priority field in IPv4 header
Extended Burst Size, EBS is a bandwidth profile parameter. It limits
the maximum number of bytes available for a burst of service
EBS
packets sent at the UNI speed which are colored yellow. This setting
is only available in single rate policing mode
EFM Ethernet in the First Mile, IEEE 802.1ah
Egress Outbound direction
EOC Embedded Operating Channel
EPL Ethernet Private Line, P2P connection via one EVC