Академический Документы
Профессиональный Документы
Культура Документы
ML600
Release R6.1
Revision No. A02
Preface Material
Document Identification
ML600 Release 6.1
Document No. 520R60621E
Revision No. A02
Date: APR 2009
Copyright
Copyright 2009 Actelis Networks, Inc.
All rights reserved.
Printed in U.S.A.
This publication is protected by International copyright law. No part of this publication may
be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated
into any human or computer language in any form or by any means, electronic, mechanical,
magnetic, manual or otherwise, or disclosed to third parties without the express written
permission of Actelis Networks, Inc., 6150 Stevenson Boulevard, Fremont, CA 94538.
Trademarks
Actelis, Actelis Networks, EFMplus, Carrier Ethernet over Copper and related logos and
icons are the registered trademarks or copyrights of Actelis Networks. Other identifiers may
be trademarks or marks of their respective owners.
Patent protection
The products described in this document are protected by U.S. Patent No. 6,744,811 and
other U.S. patents, foreign patents, and/or pending applications.
Preface Material
Document Objectives
This manual provides a general description of the ML600 device, detailed instructions for the
deployment and maintenance of the ML600 device.
Intended Audience
The intended audience for this document is both technical and non-technical staff within
Network Service Provider (NSP) organizations, and it is assumed that the reader has a
general understanding of voice and data communications, the xDSL industry and high-speed
digital services.
Contact Information
Please contact your local sales representative, service representative or distributor directly for
any help needed. For additional information concerning warranty, sales, service, repair,
installation, documentation, training or distributor locations, use any one of the following:
ii
Internet: Visit the Actelis Networks World Wide Web site http://www.Actelis.com
Preface Material
Customer support: Contact Actelis Networks Customer Support directly at one of the
following numbers:
Belgium:
Denmark:
80 887 771
France:
Germany:
UK:
USA:
For all other inquiries, please call +1 866 ACTELIS (+1 866 228 3547) or +1 510 545 1071.
Document Feedback
We welcome your comments and suggestions about this document. Please mail them to
Technical Publications, Actelis Networks, 6150 Stevenson Boulevard, Fremont, CA 94538 or
to userdoc@actelis.com mailto:userdoc@actelis.com. Include the document number,
revision number and title of this document in your correspondence. Please include your name
and phone number if you are willing to provide additional clarification.
iii
ML600 Certification
ML600 Certification
FCC Class B Compliance
ML600 series complies with the limits for a Class B digital device, pursuant to part 15 of the
FCC rules.
These limits are designed to provide reasonable protection against harmful interference when
the equipment is operated in a residential environment notwithstanding use in commercial,
business and industrial environments. This equipment generates, uses, and can radiate radiofrequency energy and, if not installed and used in accordance with this Online Help may
cause harmful interference to radio communications.
The authority to operate this equipment is conditioned by the requirement that no
modifications will be made to the equipment unless the changes or modifications are
expressly approved by Actelis Networks, Inc.
CE Mark
This equipment complies with the Council Directive 89/336/EEC for electromagnetic
compatibility. Conformity with this directive is based upon compliance with the following
harmonized standard ETSI EN 300 386 V1.3.1 (2001- 09).
MEF Certification
The ML device has undergone testing in accordance with MEF 14 requirements and found to
comply with certain requirements detailed in the Iometrix detailed test report.
iv
9. Observe all ratings and markings on the product. Use only the fuse type and rating
specified for this product. Before making connections to the product, consult the
appropriate chapters of this manual for further ratings information.
Observez toutes les valeurs nominales et indications sur le produit. Utilisez uniquement
le genre de fusible spcifi pour ce produit. Avant d'tablir des connexions au produit,
consultez les chapitres du manuel pour obtenir plus d'informations sur les valuations.
10. Many of the cables for this product are supplied by Actelis Networks. Cables that are
supplied by the customer must comply with the regulatory inspection authorities and are
the responsibility of the customer. To reduce the risk of fire, make sure all cables are UL
Listed or CSA Certified.
De nombreux cbles de ce produit sont fournis par la socit Actelis Networks. Les
cbles qui sont fournis par le client doivent adhrer aux normes des autorits
d'inspection et relvent de la responsabilit du client. Pour diminuer le risque d'incendie,
assurez vous que les cbles soient sur la liste UL ou certifis CSA.
11. This equipment must be installed according to country national electrical codes. For
North America, equipment must be installed in accordance with the US National
Electrical Code, Articles 11016, 11017 and 11018 and the Canadian Electrical Code,
Section 12. If necessary, consult with the appropriate regulatory agencies and inspection
authorities to ensure compliance.
Cet quipement doit tre install en fonction des codes d'lectricit du pays. En Amrique
du Nord, l'quipement doit tre install suivant le Code National d'Electricit Amricain,
Articles 110-16, 110-17 et 110-18 et suivant le Code d'Electricit Canadien, Section 12.
Si ncessaire, consultez les organismes de rglementation et les autorits d'inspection
appropris pour vous assurer de la conformit de l'installation.
12. Overcurrent Protection: It is recommended to incorporate in the building wiring, a readily
accessible Listed branch circuit overcurrent protective device rated 2A minimum - 5A
maximum. A 5A circuit over current protective device can feed two ML600 units in rack
mount sleeve.
Protection en cas de courant excessif: nous recommandons d'ajouter un appareil de
protection 2A min. - 5A max., facilement accessible dans le circuit lectrique de
l'immeuble. Un appareil de protection circuit 5A peut alimenter 2 units ML600 placs
l'un sur l'autre en tagres.
13. The equipment shall be connected to a properly earthed supply system.
L'quipement doit tre connect un systme d'alimentation mis la terre correctement.
14. All equipment in the immediate vicinity shall be earthed the same way and shall not be
earthed elsewhere.
Tout quipement proximit immdiate doit avoir la mme mise la terre et ne doit pas
avoir une mise la terre ailleurs.
15. A disconnect device is not allowed in the earthed circuit between the DC supply source
and the frame/earthed circuit connection.
Ne placez pas u la tern appareil dconnect dans le circuit mis la terre entre la
source d'alimentation DC et la connexion au circuit misre.
16. In case of FAN alarm, it is required to replace ML600 within four (4) hours.
Dans le cas d'une alarme FAN, vous devez remplacer le ML600 dans les 4 heures qui
suivent.
vi
Contents
Preface Material............................................................................................................................................1
ML600 Certification .....................................................................................................................................4
General Safety Instructions...........................................................................................................................5
1 Introduction
1-1
2 Getting Started
2-1
3 Management Configuration
3-1
vii
Contents
Physical Tab ................................................................................................................................ 3-12
Connectivity Tab ......................................................................................................................... 3-14
Current Alarms Area ................................................................................................................... 3-15
Performing Group Operations ..................................................................................................... 3-16
Multi-lingual Support .................................................................................................................. 3-17
SNMP Agent and Trap Parameters......................................................................................................... 3-18
SNMP Agent Configuration ........................................................................................................ 3-18
SNMP Trap Destinations............................................................................................................. 3-20
SNMP Trap Filtering................................................................................................................... 3-21
System Name Configuration................................................................................................................... 3-22
System Time and Date............................................................................................................................ 3-23
Configuring Date and Time Manually......................................................................................... 3-23
Automatic Date and Time Adjustment ........................................................................................ 3-24
Daylight Saving Time (DST) Configuration ............................................................................... 3-25
4-1
5-1
viii
Contents
Configuring ML600 Ethernet Bridge ............................................................................................ 5-3
LLDP Configuration...................................................................................................................... 5-7
Quality of Service (QOS) .............................................................................................................. 5-8
STP/RSTP and Provider Bridge Configuration ...................................................................................... 5-20
STP/RSTP Principles................................................................................................................... 5-21
STP/RSTP in ML Systems .......................................................................................................... 5-22
STP/RSTP Bridge Configuration ................................................................................................ 5-23
STP/RSTP Ports Configuration ................................................................................................... 5-24
6-1
7 VLAN Configuration
7-1
8 L2CP Processing
8-1
9 EVC Configuration
9-1
10-1
ix
Contents
CFM Messages in ML Systems................................................................................................... 10-4
CFM on ML NE .......................................................................................................................... 10-5
Ethernet CFM Configuration Procedure ................................................................................................. 10-7
Ethernet CFM Configuration Window ........................................................................................ 10-7
Defining a CFM Domain............................................................................................................. 10-9
Defining Domain MIPs ............................................................................................................. 10-11
Defining CFM Maintenance Associations................................................................................. 10-13
Defining MEPs .......................................................................................................................... 10-15
11 Security Management
11-1
12 Administration
12-1
Contents
Restarting the ML NE ............................................................................................................... 12-28
Using Web Browser.............................................................................................................................. 12-29
Accessing and Navigating the Support Page ............................................................................. 12-29
Configuration Backup and Restore............................................................................................ 12-31
Retrieving Logs ......................................................................................................................... 12-34
Retrieving Files ......................................................................................................................... 12-34
ML Software Control ................................................................................................................ 12-35
Repeaters SW Control via Web Browser .................................................................................. 12-37
Displaying the TL1 Document .................................................................................................. 12-37
13 Monitoring
13-1
xi
Contents
14 Troubleshooting
14-1
xii
Contents
Resolving Configuration Considerations Due to Dipswitch Settings ................................................. 14-105
15 Appendix A - Acronyms
A-1
B-1
SFP Modules.............................................................................................................................................B-2
ML600 SW and Documentation ...............................................................................................................B-4
Cables .......................................................................................................................................................B-5
Accessories ...............................................................................................................................................B-7
C-1
ML600 Specifications...............................................................................................................................C-2
Supported SNMP MIBs ............................................................................................................................C-5
Customer Logs..........................................................................................................................................C-6
Spectral Compatibility Standards .............................................................................................................C-7
Available Spectral Modes.........................................................................................................................C-8
D-1
xiii
.1
1 Introduction
This chapter introduces Actelis devices, the basic architecture and the most
common topologies in which ML600 devices can be installed. The descriptions
differentiate between various types of ML600 product models.
In This Chapter
About ML600 ................................................................. 1-2
Deployment Topologies................................................. 1-5
About ML650 ............................................................... 1-12
Management Applications ........................................... 1-14
1-1
Introduction
About ML600
About ML600
Ethernet Access Devices (EAD) from Actelis Networks enables delivery of high-speed
Carrier Ethernet services over the existing copper and fiber infrastructure. The ML600
products are a compact, cost-effective Ethernet in the First Mile (EFM) EADs that deliver up
to ~100 Mbps (for RoHS6 compliant systems) or ~45 Mbps (for RoHS6 non-compliant
systems) symmetrical Ethernet traffic at fiber quality over existing copper pairs.
Available in 1 to 8 copper pairs and fiber configurations, the ML600 EAD can be deployed in
a Point-to-Point configuration, optional copper add-drop chain, or as the CPE in a Point-toMulti-Point configuration with Actelis ML130 / ML1300 / ML2300 aggregation switches.
With its superior performance, extensive functionality and low cost, the ML600 EAD
platforms offer rapid service delivery and allow for complete utilization of the existing
network infrastructure.
The ML 600 EAD platform is interoperable with any standard Ethernet switch, router or hub.
Compliant with Metro Ethernet Forum (MEF) specifications, ML600 EAD systems
seamlessly integrate into Carrier Ethernet Networks. Equipped with four 10/100Base-TX
Ethernet interfaces and an optional 100Base-FX or 1000Base-FX Small Form Factor port
(SFP), the ML600 EAD platform allows assignment of a service or a customer per port. A
DS3/E3 uplink can be used to connect to legacy networks in ML600 units supporting SFP
option.
Implementing the standard IEEE 802.3ah-2004 (EFM) long reach Ethernet-over-copper
specification, the ML600 EAD platform bonds up to 8 copper pairs together to create a
2Base-TL aggregated link. The systems support current and evolving Ethernet Quality of
Service (QoS) requirements and has the highest available packet throughput efficiency.
Powered by Actelis Networks field-proven EFMplus technology, the rate and reach are
increased significantly, using advanced Dynamic Spectrum Management (DSM) and
Dynamic Spectral Shaping (DSS) techniques. This technology ensures the best rate/reach
performance and most resilient fiber-quality transmission ensuring carrier class service
availability.
All ML600 EAD models provide 802.1q VLAN-aware wire-speed bridging, double tagging
(VLAN stacking) for end-user VLAN transparency, L2 (Ethernet priority) and L3 (ToS/DiffServ) classification with four (8 hybrid scheduled queues for the ML640/ML650 series)
traffic classes, RSTP/STP, bandwidth monitoring, Multicast/Broadcast limiting, HSL (High
Speed Link - bonded copper link) rate limiting and Link Aggregation (LAG) on all Ethernet
ports.
1-2
About ML600
Introduction
The ML640 series lets service providers create an intelligent Ethernet access edge with
advanced bandwidth control and traffic management features, fully compliant with the MEF
9 and 14 specifications. The ML640 enables flexible service provisioning using Ethernet
Virtual Connections (EVCs) and Quality of Service capabilities that maximize the efficiency
of access bandwidth and strictly enforce Service Level Agreements (SLA) for each
subscriber and class of service, allowing service providers to safely aggregate multiple
services or multiple subscribers on the same access port.
The ML650 series provides a smooth migration path from TDM based networks to Ethernet
based networks while maintaining the required clock quality. It is designed to answer the
needs of mobile operators for cost effective solutions that provides efficient transport of both
data and circuit traffic, while maintaining accurate clock synchronization required for cellular
networks. ML650 enables the delivery of high-speed Carrier Ethernet, E1/T1 TDM services
and accurate clock synchronization over the existing copper infrastructure up to ~45 Mbps
symmetrically. (More information on ML650 is provided in About ML650 (on page 1-12)).
ML systems Ethernet OAM capabilities provide a set of tools that enable Metro Ethernet
operators and service providers to more effectively manage and troubleshoot the overall
Ethernet infrastructure in order to minimize downtime. One of the supported Ethernet OAM
tools is CFM which allows service providers to individually manage customer service
instances.
The ML600 EAD platforms can be managed In-Band and Out-of-Band, by the
MetaASSIST View graphical craft application and via the multi-platform Element
Management System, MetaASSIST EMS. The management protocols include standard TL1
rd
command line interface and SNMP, using standard MIBs for seamless integration with 3
party Network Management Systems (NMS).
ML CO systems can support ML CPE systems at distances of several kilometers (actual
distance depends on loop topology). The distances can be extended by using Actelis XR239
Repeaters and the corresponding power feeding units (PFU-8/PFU-8C/PFU-8E).
Optional Features
Optical Interfaces - Choice of optical interfaces accommodate short and long distances as
needed with speeds of 100Mbps or 1000Mbps. These optical interfaces provide an
evergreen investment by allowing a smooth migration to higher service speeds over fiber
without changing the EADs at the customer premises.
The optical interfaces allow optical infrastructure overlay (i.e. implementing Ethernet
network over existing Sonet/SDH fiber networks) by using WDM/DWDM optical
interfaces and passive optical filter splitters.
Copper Add-Drop EADs - The Copper Add-Drop EADs allow multiple nodes to be
connected to each other over copper, in a linear chain or ring configuration. Each node
has the full switching capabilities of the ML600 EAD and can drop and add Ethernet
traffic at each location, while transferring the rest of the traffic through.
1-3
Introduction
About ML600
Providing up to 22.8 Mbps aggregated traffic (up to 50 Mbps with high rates support), the
copper Add-Drop EAD is a powerful tool for distribution of Ethernet traffic across
linear/ring copper networks.
ML600 Architecture
This section describes the architecture of all ML600 models except for ML650 (which is
described in the following section). The architecture consists of the following blocks:
Ethernet Bridge - 802.1q VLAN aware Ethernet bridge that bridges packets between
Ethernet service ports and the HSL(s). The type and number of Ethernet service ports are
model dependent.
HSL- EFM Engine block that encapsulates and aggregates the frames according to IEEE
802.3ah EFM. The number of available HSLs (one or two) is model dependent.
The bandwidth of the system is proportional to the number of copper pairs. That is, the more
copper pairs that are used, the more bandwidth is available to carry services.
1-4
Deployment Topologies
Introduction
Deployment Topologies
ML600 devices can be installed as:
WAN/MAN Access Ethernet switch, installed in Central Office site, with the HSL
performing in O (Office) mode.
Customer LAN Access Ethernet switch, installed in Customer site, with the HSL
performing in R (Customer/Remote) mode.
Both WAN/MAN and Customer LAN Access Ethernet switch, installed in-between
Central Office and remote sites, with one HSL performing in O (Office) mode and
second HSL performing in R (Customer/Remote) mode.
The systems can be installed in various physical topologies according to site requirements. In
some installations, such as point-to-point or point-to-dualpoint, ML600 systems are installed
both at the Central Office and at the Customer sites. Other installations such as, point-tomultipoint, are implemented using additional Actelis equipment such as
ML130/ML1300/ML2300 aggregation switches systems.
This section describes some common examples of physical installation topologies. These
include:
1-5
Introduction
Deployment Topologies
ML600 Point-to-Point
This topology connects a Main Office site to a single Customer Premises location that is at a
distance of up to 5.5 Km (18 Kft). This is implemented using two ML600 units: one at the
Main Office and one at the Customer Premises.
An application example is illustrated below. ML600 is deployed as a transport product
providing data connectivity for Business Customers that require Transparent LAN
interconnect services and Ethernet access services between small / medium enterprises to the
Central office.
1-6
Deployment Topologies
Introduction
1-7
Introduction
Deployment Topologies
1-8
Deployment Topologies
Introduction
ML600 in Point-to-Multipoint
In this type of configuration, an ML CO aggregation switch supports a number of ML CPE
remote sites (ML600 and ML1300/2300 in the example). The maximum number of CPE sites
differs according to the type of installed ML aggregations switch and the hardware
configuration of the system.
Figure 5: Point-to-Multipoint
1-9
Introduction
Deployment Topologies
1-10
Deployment Topologies
Introduction
ML688 Drop-and-Continue
In this deployment topology, an ML624 unit (or any ML aggregation switch chassis) is first
installed at the head-end site, intermediate ML688 units are installed in an outdoor cabinets
and an ML624 is installed at the remote side. Employing the ML688, the user can achieve
greater reach (similar to a repeater) while allowing an Ethernet connection "along the way" as
shown in the figure below.
Note: The number of intermediate sites (N) is limited by the HSL bandwidth shared between
all chained NEs and the aggregated propagation delay on all NEs.
1-11
Introduction
About ML650
About ML650
ML650 series consists of ML658 and ML654 models. This series enables the delivery of
high-speed Carrier Ethernet, TDM data and synchronization services of up to ~45 Mbps
symmetrically over an existing copper infrastructure. Supporting a Point-to-Point topology,
the ML650 series delivers up to 4x10/100M copper Ethernet ports 1x100BaseFX SFP (MSA
compliant) and up to 4xT1/E1 circuits over the copper infrastructure (with or without
repeaters along the span).
The device also delivers a strict timing reference delivered either from a synchronized T1/E1
port or identical BITS ports maintaining frequency stability and low wander tolerance over
the copper plant.
ML650 Architecture
ML650 supports concurrent bi-directional transfer of both Ethernet and T1/E1 data, together
with unidirectional (from CO to CPE) TDM clock transfer. The TDM clock serves T1/E1 line
transmission needs and can also be used as a separate clock source.
Data acquired from the Ethernet ports is routed according to 802.1Q Bridge module decision.
If the data is forwarded to an HSL port, it is additionally handled according to IEEE 802.3ah
EFM, fragmented and forwarded to the SHDSL modem (copper-pair) interfaces. In the other
direction, Ethernet fragments arriving from the SHDSL modem (copper-pair) interface are
encapsulated as Ethernet frames and forwarded to 802.1Q Bridge module, where it is routed
to the Ethernet port as determined by the bridge switch.
Data acquired from the E1/T1 ports is encapsulated into Ethernet frames by the CES module
and then handled in the same way as Ethernet ports data. The clock derived from E1/T1
services at CO side is transferred to CPE side which reconstructs the clock.
1-12
About ML650
Introduction
ML650 Topologies
ML650 is installed in a Point-to-Point topology that delivers up to 4x10/100M copper and
100M fiber (SFP module) Ethernet lines and up to 4xT1/E1 circuits. ML650 transfers data
between the 2G (MSC) or 3G (RNC) switching centers and the co-located 2G (BTS) or 3G
(Node-B) base stations. The following two diagrams show ML650 devices in a P2P in an
SDH/PDH based cellular network and in an SDH/PDH Ethernet integrated cellular
network.
The figure below illustrates interface with T1 circuits. In this installation type, the ML650 is
used to interconnect between the switch center and the BTS, Node-B, WiMAX or WiFi
station over up to four T1 lines.
The figure below illustrates interface with SDH/PDH circuits integrated with Ethernet. In this
topology the ML650 devices are used to interconnect the switch center and the BTS, Node-B,
WiMAX or WiFi station over four T1 lines in addition to Ethernet connection. This topology
is used in networks with an Ethernet and PDH based infrastructure.
1-13
Introduction
Management Applications
Management Applications
The following applications for Actelis system management are available:
1-14
MetaASSIST View - a Java based Graphical User Interface (GUI) application used for
local and remote management of a connected ML system and (in case of an ML CO) its
hosted ML elements. The application is provided with the system.
WEB Access - enables performing basic operation on the system from any standard Web
Browser.
.2
2 Getting Started
This chapter describes the rear-panel and front-panel interfaces of the ML600
models. In addition, it provides information on how to connect to and navigate
the MetaASSIST View and configure and operate the ML device in its various
system deployment models (topologies).
In This Chapter
Front and Rear Panel Descriptions ............................... 2-2
Connecting to and Navigating the MetaASSIST View... 2-5
ML600 Commissioning Procedures ............................ 2-16
2-1
Getting Started
Interface
Description
ETH 1..4
100BaseFx or
1000BaseFx
MGMT
LNK, ACT
LEDs
LEDs common to ETH, 10/100BaseFx, HSL and MGMT ports. Two types of
LEDs are provided for each port:
LNK - Link status: up or down. A LNK indicator is provided for each of the
Ethernet and for the HSL ports.
ACT - Link activity (sending or receiving frames) state. An ACT indicator is
provided for each of the Ethernet and for the HSL ports.
2-2
Getting Started
T1/E1
LNK, ERR
LEDs
CRAFT
RS232
Local RS232 connection used for service and basic setup operations. Local
terminal connection for CO installation.
Power, Status,
Alarm LEDs
MLP LEDs
Indicate status of the copper-pair ports located on the device rear panel. Each
LED indicates the synchronization status of corresponding modem.
2-3
Getting Started
Port
Description
Copper Pairs
Ports for connection of copper pair wires. The number of available ports
(1, 2, 4 or 8) varies depending on the ML600 model.
AUX
Connects the ML600 unit to the PFU-8. Allows monitoring PFU-8 via
ML600.
ALARM inputs
ALARM output
Power
GND/Earth
GND/Earth
Dipswitches
Reset
2-4
Getting Started
Serial RS-232 Craft interface. Used mainly for first time operation, before the IP
address is set to perform the initial configuration procedures. It can also be used to
reconfigure IP addresses.
Ethernet COLAN (MGMT) port. Disabled by factory setup. By factory setup, COLAN
is included in default MGMT VLAN (VID=100) as untagged member.
Ethernet service port. Factory configured for service traffic only. Can also be configured
for in-band management.
HSL port. Enables indirect access to remote ML systems from the directly connected
system. By factory default, all HSL ports are included in default MGMT VLAN
(VID=100) as tagged members.
Up to R3.0 version - up to 20 local accounts. The same account cannot be re-used from
another host.
Starting R3.0 version - up 20 Local user-shared accounts. The same user account can be
re-used from different hosts, but not from the same IP.
Starting R6.00 - up to 100 Local user-shared accounts. Either RADIUS (on page 11-15),
local DB or a combination of both is used.
2-5
Getting Started
Starting R6.10 - 100 Local user/IP-shared accounts. The same user account can be reused from the same IP host
If an indirectly connected ML NE (linked via HSL) cannot be accessed (no physical copper
connection or configuration on ML NE), only a directly connected ML NE is shown in the
MetaASSIST View. If an indirectly connected NE can be accessed, MetaASSIST View
performs auto-login to both directly and indirectly connected ML NE, using the User Name
and Password typed for the directly connected ML NE.
The MetaASSIST Main window opens and the Connect dialog is automatically invoked.
2-6
Getting Started
Note: For basic information on navigating the MetaASSIST Main window, refer to
MetaASSIST View Workplace (on page 3-9). To resolve unsuccessful connections, see
Resolving Management Connection Problems.
Select the computer COM port to which the ML600 unit is currently connected.
Set the Baud Rate to 9,600 bps (factory default rate on ML unit).
Note: Computer COM1/COM2 ports are usually set to 9600 baud rate. If your computer
is set to operate with a different baud rate the baud rate configured on the ML unit,
change the computer setting to match the Craft port setting. (There is no auto-negotiation
on the Craft port).
4. Under Login Details:
2-7
Getting Started
The ML unit communicates with Management LAN (through MGMT port or in-band
through one of the ETH ports).
The computer with MAV application has a network connection to the Management
LAN
The MetaASSIST Main window opens and the Connect dialog is automatically invoked.
2-8
Getting Started
Note: For basic information on navigating the MetaASSIST Main window, refer to The
MetaASSIST View Workplace (on page 3-9). To resolve unsuccessful connections, see
Resolving Management Connection Problems.
By default, the MAV connection to the ML uses UDP broadcast communication (for
NE and its version discovery). For Management Network, where UDP traffic is
blocked by Firewall, uncheck the check-box Automatically discover Network
Element version (using UDP). This will allow communication (since MAV then
uses only TCP/IP communication).
Note: In order to search for defined systems use the Search option.
4. Under Login Details:
2-9
Getting Started
Auto-discovery of ML Systems
Previously monitored systems via the TCP/IP Address list box can be viewed and selected in
the Connect dialog box. To the right of the list box the System ID (TL1 TID) of the last
connected system is displayed. In addition, the Search dialog box displays accessible ML
device on the LAN.
Note the following:
Auto-discovery detects only ML devices that are on the same local segment.
The Search button (even if enabled) doesn't work in a Management Network, where UDP
traffic is blocked by Firewall.
2-10
Getting Started
Note: ML device that cannot be managed by this version of MetaASSIST View are grayed
out.
2-11
Getting Started
3. In the Login Details, enter your User Name and Password and click OK.
CO and CPE are connected by copper pairs, and configured appropriately: one NE as
STU-C NE (HSL configured in O mode), other NE as STU-R NE (HSL configured
in R mode).
The peer NE (either CO or CPE) has "Access from Peer" Enabled (factory setup).
Note: When opening a local (craft connection) MetaASSIST View session to an ML600
CPE in a P2P topology, the CO NE linked via HSL is displayed as well.
MetaASSIST View, running on Management host connected to the ML NE(CO or CPE) via
Ethernet/IP/TCP/telnet/TL1 connection (over ETH-x, COLAN or HSL-x port), is able to
show directly (via ETH-x, COLAN) and indirectly connected (Linked via HSL) NE, if the
following conditions are true:
2-12
CO and CPE are connected by copper pairs, and configured appropriately: one NE as
STU-C NE (HSL configured in O mode), other NE as STU-R NE (HSL configured
in R mode).
Getting Started
L2 (LAN) and L3 (IP) setting on both ML NE (CO and CPE) are configured
correctly. For security reasons, remote (telnet) access to each ML NE can be secured
enabling SSH, ACL features on selected NE or by separating IP/LAN network,
differently configured on CO and CPE NE.
In mixed configuration (CO NE has IP address and CPE NE doesn't have IP address),
MetaASSIST View will connect to IP-less CPE NE using non-IP access (also controlled by
"Access From Peer").
Note: CPE NE with SW earlier then R5.0a supports basic non-IP access capabilities for
monitoring of NE statuses and basic configuration. CPE NE with SW=R5.10 or higher
supports full non-IP access capabilities (including file transfer-based features). Note that on
any IP-less NE, SNMP communication is disabled.
Note: If CPE NE is of 3-rd party (and not Actelis ML NE). EOC discovered information
will be shown on HSL.
Note: IP-less access from the Peer can be controlled: enabled (factory default) or
disabled.
Note: The IP/Ethernet access on each NE can be controlled and additionally secured (by
ACL or SSH).
2-13
Getting Started
If the NE selected is a CO, this option will display all ML devices that are connected as
CPEs (ML600) and failed to auto-connect to the CO.
To view the ML50 and ML600 devices that failed to auto-connect or login
In the Network Element Tree:
2-14
Click Network Elements Linked via HSL and then ML failed to auto-connect or/and
login or
Click on the corresponding link on the Network Elements Linked via HSL pane
Getting Started
The corresponding pane appears in the work area. The pane shows all the ML devices that
failed to auto-connect, according to their HSL, along with general information on each
device. The operation buttons are described after the figure.
Description
Restart
Commit SW
Commit a new SW version (already located on the device). For more details
about this procedure, see Updating the System Software (on page 12-12).
Login
Configure
Accesses the L2/L3 setting configuration options. Used to change IP, subnet
mask, Gateway configuration mismatch or MGMT VLAN configuration
mismatch.
Configure VLANs
(link)
Accesses the VLAN configurations options of the selected device. For more
details about this procedure, see VLAN Configuration (on page 7-1).
2-15
Getting Started
Note: For configuring the ML600 using the dipswitches, refer to the ML600 Quick Installation
Guide - Appendix A.
2-16
Getting Started
It is recommended to use the factory (default) setup as initial configuration for the above
topologies.
Prior to performing a configuration setup (using the Wizard), verify that:
1. The Initial Setup Procedure (either via the Wizard or step-by-step) was completed
successfully.
2. The Management plane was set and CO and CPEs are available via the MGMT
VLAN/IP.
3. The computer (laptop) running the MetaASSIST View application is connected via
RS232 local connection to the ML CO Craft port.
2-17
Getting Started
This completes the physical installation of the ML device in the Central Office environment.
2-18
Disable all unused MLP ports (on page 4-21) (to prevent alarm condition control
on these ports and to allow HSL operations.)
HSLDOWN alarm condition will appear on HSL while at least one modem is not
synchronized.
Getting Started
The ML device Modems 5-8 and HSL-2 LEDs are blinking or steady GREEN,
indicating synchronizing/ed modems towards the previous ML device (upstream
to CO).
Downstream Modems 1-4 and HSL-1 should be off (as not synchronized yet).
All repeated segments should be installed starting from the CO towards the CPE/RT.
Install the ML CPE last according to 1. ML CO Physical Site Installation (on page
2-18).
4. ML CO - Link Verification
If a technician is not available at the remote CPE site, equipment/inventory issues can be
resolved from the ML CO via the MetaASSIST View, according to the steps described in this
section:
1. For each HSL port:
Verify that the following alarms are NOT displayed: HSLDOWN, HSLFLT or
COPPERMIS.
2-19
Getting Started
For Drop & Continue deployment the following three operations should be repeated on
each ML688 device:
1) Access Linked via HSL Network Element;
2) Provide an IP connectivity for this NE;
3) Connect (login) to the NE via IP.
As a result, all remotely installed ML devices should be accessible for MetaASSIST
View application, running on a PC, which is directly connected only to the ML device
installed in the Central Office.
3. Check alarmed conditions on remotely installed ML device equipment:
Verify no HWFLT or PROGFLT alarm condition exists. The rest of alarms are not
relevant at this point.
4. Set System ID to provide unique identification of the remote ML device.
Note that by default, the system ID is defined as the system serial number.
5. ML CO - HSL Operation
For the following steps, all Actelis systems involved in the deployment scenario should be
installed, and linked via HSL (by at least 1 synchronized modem between Actelis systems).
1. On ML CPE - configure the HSL<ID> and MLP <ID> options. Disable all unused MLP
ports.
2. On ML CO - Calibrate HSL <ID> in -O (Office) mode:
Apply required calibration parameters: Calibration Type (Best Efforts,Target BW or
Force Rate), Target SNR margin, DSS Profile, Spectral Mode , Min PBO, Extended
rates, Circuit length (only in specific Spectral Mode), Rate Adjust and Extended
rates. Calibration begins when a link is implemented and all copper lines between two
Actelis systems are synchronized (at minimal rate).
For single and repeated span deployment scenarios (P2P and P2MP), HSL calibration
is required once, on CO site installed ML device only.
For drop & continue spans deployment scenarios (P2P and P2MP), HSL calibration
is required on each ML device with HSL available in -O (Office) mode (ML688
model).
2-20
Getting Started
6. ML CO - Service Configuration
Note: Refer to the Service Configuration Wizard (on page 2-17) for instructions on
performing this procedure automatically.
Determine the relevant Ethernet traffic topology for your site prior to the Actelis systems
configuration, see L2 Network configuration in various topologies (on page 7-13). All
steps should be implemented starting from the most remote ML device, to avoid Management
LAN integrity loss during configuration.
Note: A computer running MetaASSIST View should be locally connected to avoid
Management LAN integrity loss during configuration.
Disable STP at bridge level on ML CPE installed as the Customer LAN Access.
In models ML600 Ethernet facilities are auto-entered and immediately monitored for
alarm conditions. Alarms on ETH<ID> show that adjacent equipment is not
connected yet or physical interface configuration does not match. Connect Ethernet
cables and if required, adjust the configuration. Disable unused Ethernet ports to omit
their LOS alarm.
2-21
Getting Started
7. ML CO - Administration Configuration
The following steps enable remote Management Access and the configure security policy.
Implement this procedure for all units, starting from the most remote ML device, to avoid
Management LAN connectivity loss during configuration.
Note: Use a local CRAFT port connection to avoid Management LAN connectivity loss during
configuration.
1. Set System ID to provide unique identification of System and its location for managing
via TL1 (applied as TID) and SNMP (applied as System Name) interfaces. TL1 and
SNMP identification can be applied equally or differently. By factory setup, each ML
device Serial Number is reported as TID/System Name.
2. Set Date and Time (manually or enable SNTP) to provide correct timestamp of alarm
conditions reported from the Actelis systems.
3. Configure Management LAN connectivity according to installed Ethernet Service traffic
topology and use guidelines for MGMT traffic in various topologies, see L2 Network
Configuration in Various Topologies (on page 7-13).
4. Set User Accounts. Enable Password control (complexity, history, failed login, etc.), if
required by Provider Management access policy.
5. If required, configure SSH and ACL according to Provider Management access policy.
6. If required, block non-IP access on ML device installed on CO to avoid insecure access
to CO NE from remote NEs.
2-22
Getting Started
8. ML CO - Configuration Backup
The following steps complete the configuration by service validation and capturing the
backup file of the approved configuration of each ML device involved in the deployment
scenario.
1. Verify Ethernet connectivity between all Actelis systems: Ping the IP Address of each
ML device. Apply Ping on any IP known in the Customer site if MGMT is not
terminated on CPE.
2. Backup the configuration of each ML device, starting from the most remote system. See
Configuration Backup and Restore .
2-23
.3
3 Management
Configuration
Each ML NE can be accessed via either a local RS232 connection or remotely
using Ethernet in-band or out-of-band connections. This chapter describes the
connectivity methods and the required configuration procedures.
In This Chapter
NE Management Communication Protocols ................. 3-2
Craft Port Configuration................................................. 3-3
IP/LAN Connectivity on Directly Connected NE ............ 3-4
IP/LAN Connectivity on Indirectly Connected NE.......... 3-7
MetaASSIST View Workplace....................................... 3-9
SNMP Agent and Trap Parameters............................. 3-18
System Name Configuration ....................................... 3-22
System Time and Date................................................ 3-23
3-1
Management Configuration
NE Management Communication
Protocols
Each ML NE can be managed via different communication protocols:
Prompted TL1 via TCP port 3083 (not configurable) - for man-machine interface
Unprompted TL1 via TCP port 3082 (not configurable) - for machine-machine interface
Discovery Protocol via UDP port 3087 (not configurable) - for ML discovery by
MetaASSIST View
Telnet via TCP port 23 (not configurable) to provide TL1 connections described above
SSHv2 via TCP port 22 (not configurable) - for secure TL1 connections described above
HTTP via TCP port 80 (not configurable) - for file transfer operations
SNMP via UDP input port 161 (not configurable) and output port 162 (configurable)
SNTP via UDP port 123 (not configurable) - for date and time auto-synchronization in
the LAN
Access via each communication protocol can be controlled via Access Control List, see
System Security. User Accounts secure TL1 communication protocol, see System Security.
3-2
Management Configuration
Note: The Apply to adjacent SDU box appears only for ML2300 systems with two SDU300 series cards (as two individual systems).
3. From the Port Rate box, select the baud rate.
4. Click OK.
3-3
Management Configuration
When enabling the COLAN (MGMT), ensure that there are no Ethernet loops between the
COLAN (MGMT) and Service ports (ETH or HSL), see Resolving Non-Alarmed Service
Problems (on page 14-81).
To provide IP/LAN connectivity on a locally connected NE, you will need the Management
VLAN, IP address, IP gateway address, and IP subnet mask information from your Network
Administrator for each NE installed in the topology.
802.1Q bridge mode (VLAN aware) - ML600 is accessible via COLAN (MGMT) for
untagged management traffic. To enable tagged management traffic access to the ML600,
see Management VLAN Configuration (on page 7-9).
802.1D bridge mode (VLAN unaware) - ML600 (not relevant for ML640/ML650), by
factory setup, is accessible for untagged traffic via any port.
3-4
Management Configuration
L3 (IP) Connectivity
ML systems are assigned the default IP address and Gateway of 0.0.0.0 (unusable) and a
Subnet Mask of 255.255.0.0 (Class IP Addresses).
To set IP connectivity parameters on monitored units
1. In the Network Element tree, open Management Interfaces. The Configure
Management IP Interfaces pane opens.
3-5
Management Configuration
2. In the IP Interface area, click the Configure button. The Configure Management IP
Interface dialog appears.
3-6
Management Configuration
3-7
Management Configuration
3. Click Configure button. The Configure NEs Linked via HSL dialog appears.
IP Address
Subnet mask
Gateway
5. Set the LAN Configuration parameters using one of the following options:
Set as local - Read only - sets the LAN parameters to the same values as those of the
host CO.
Set manually - initially displays the configuration of the remote NE. The parameters
can be modified.
6. Click OK.
3-8
Management Configuration
3-9
Management Configuration
Menu Bar
The menu bar provides you access to the functions as described in the following table.
Table 4: Menu Bar Options
Menu
Description
3-10
Management Configuration
3-11
Management Configuration
Physical Tab
The Physical tab is displayed by default. It provides access to monitoring and configuration
options for the Network Element (NE) to which a session was opened. If the NE is a CO, this
tab also provides access to the hosted CPEs. The NE tab space is divided to Topology Tree
and NE Navigation Tree.
Topology Tree
The Topology Tree displays the ML device (Network Element or NE), to which a session
was opened. If the NE performs as CO (Central Office) device, then the corresponding
connected CPE (Customer Premises Equipment) is also displayed.
Note: ML688 supports connections to two Network Elements.
An icon adjacent to the item indicates the type of device and its status, where the color
corresponds to the most severe alarm on the device (Blue - OK, Yellow - Minor, Orange Major, Red - Critical).
Meaning
My Computer
<IP Address>
3-12
Management Configuration
MetaASSIST View applies the following features on the assets in this Tree:
Displays TID (Target Identifier) on successfully logged in NEs for ease of monitoring by
logical name;
In most cases, all HSL linked NEs along with the corresponding TID and IP are
automatically added during connection. For other cases, see Logging In descriptions.
Logging In User Privilege - some panes require specific (write or admin) permissions and
are available only to users with the appropriate access privileges.
3-13
Management Configuration
The following table describes the icons in the Navigation tree. These also appear in the work
area and system alarms table.
Table 6: Icon meanings
Icon
Meaning
Connectivity Tab
The Connectivity tab provides three types of options, available as main tree items:
3-14
Ethernet Connection (on page 13-81) - used to monitor status and setup of the particular
Ethernet Connection (predefined via the Physical tab).
DSX1 Connection (on page 13-85) - The DSX1 Connection pane is used to compare
configuration and status information of an ML650 unit and its peer. It can be used for
troubleshooting and to verify that the configuration parameters on the two units are
compatible.
Management Configuration
Below is an example of the display invoked when the Ethernet Connection option is selected.
3-15
Management Configuration
The Status bar displays the total number of Critical, Major and Minor alarms in the
Monitored NE, management (TL1) traffic direction and Monitored NE date-and-time. In
addition, when the cursor resides over the management traffic direction area, a pop-up
displays management traffic statistics that includes the received and sent bytes between the
MetaASSIST View application and the Monitored NE.
2. Click the Group Operation menu option and choose the required operation from the
available menu option. The selected operation will be applied to the selected NEs.
3-16
Management Configuration
Multi-lingual Support
All labels in the MetaASSIST View are in English. Any printable 8-bit ASCII-extended
characters are valid for all configurable "free string" parameters (i.e. User Name, Password,
System, Port ID, etc.).
Typically used ISO 8859-1, also called as ISO Latin1, refines ASCII-extended (8-bit) codes
and is sufficient for the most common European languages,including characters such as
(German), (Spanish), (Swedish and other Nordic languages) and (Hungarian).
Note: MetaASSIST View and MetaASSIST EMS ignore ? (0x3F ASCII code), " (0x22 ASCII
code) and /n line feed (0x0A ASCII code) characters.
3-17
Management Configuration
In the Network Element tree, expand the Management Access item and select
SNMP.
In the invoked pane, Configuration area, click Configure. The SNMP Settings pane
opens.
Note: To invoke the dialog for a selected Group: in the Network Topology tree select the
Group item, in the Menu bar, select Group Operations, SNMP Configure. The SNMP
Settings pane opens.
3-18
Management Configuration
System Name - The system name is set by default as the unit ID. A recognizable
name may be assigned to the system. Range = up to 255 alphanumeric characters.
Note: If a name is assigned via TL1 and want the same name to be assigned via SNMP,
enable Same as TL1 TID.
Contact Name - Optional - Enter information of the contact person such as name,
phone number, etc. Range = up to 255 alphanumeric characters.
Change the Read community name - to limit Get or Read access to the ML unit.
Range = up to 32 characters.
Change the Write community name - to limit Set or Write access to the ML unit.
Range = up to 32 characters.
4. Click OK.
3-19
Management Configuration
Note: For group operations, open the Add SNMP Trap Destination dialog box via the
menu bar: Group Operations, SNMP, Add.
4. In the Destination IP Address box, type the IP address of the SNMP management
system.
5. In the Community String box, type the community string of the SNMP management
system. If an incorrect string is typed, the SNMP management system may not receive
the SNMP traps.
6. In the SNMP version box, select the version of the SNMP used by the management
system. The SNMP version defines the structure of the traps that will be sent to the
SNMP management system.
7. In the Port box, type the SNMP/UDP trap notification port of OSS/NMS host where the
ML device traps are to be received. Click OK.
3-20
Management Configuration
3-21
Management Configuration
3. In the System ID field, type the new system name. This will be the TL1 TID. Range: up
to 20 alphanumeric characters.
4. To assign the logical name to the system in SNMP, enable Apply to SNMP System
Name. Unless this box is enabled, the SNMP System Name will be displayed as the
serial number.
5. Click OK.
Note: For SNMP, see SNMP Agent Configuration (on page 3-18).
3-22
Management Configuration
Note: For group operations, open the Set Local Time dialog box via the menu bar:
Group Operations, Date and Time, Configure.
5. To set the date: in the Date box type the date in accordance to the computer format (for
example, 2/14/2006).
6. To set the time: in the Time box type the time in accordance to the computer format (for
example, 10:08:57 AM).
Note: Refer to Daylight Saving Time (DST) Configuration (on page 3-25).
3-23
Management Configuration
7. To set the time zone from the Time Zone list box, select the time zone in accordance to
the local time zone (for example, GMT +4:00).
Note: Time Zone is effective in Auto Sync mode only.
8. Click OK.
j
4. To enable automatic synchronization, select the Auto Sync check box.
5. From the Mode box, select Unicast or Broadcast (determines whether SNTP client listens
to broadcasts or queries the server (polling)).
Note: Broadcast mode is unsupported in the current SW release although it appears as a
selectable option.
6. In Unicast mode only, in the Polling Interval box, type in the polling interval in seconds.
This is an interval between SNTP client attempts initiated by the ML device. Default
interval provided by the ML device is 600 seconds. Value is configurable in range from
60 to 10,800 seconds.
7. In Unicast mode only, in the Timeout Interval box, type in the timeout interval in
seconds (the interval of time allowed without synchronization). When this interval is
expired without successful connection to the server, an alert is sent to the user. Default
interval is 3,600 seconds. Value is configurable in range from 60 to 86,400 seconds.
Note: Timeout Interval must be greater than the Polling Interval.
8. In Unicast mode only, in the Server IP Address box, type in the server IP address
(default value on factory setup is 0.0.0.0).
9. Click OK.
3-24
Management Configuration
10. To verify setting the Time Zone, see Configuring Date and Time Manually (on page 323).
To set DST:
1. On the Navigation tree in the Network Element tree, expand System Administration.
2. Open Date and Time. The Date and Time pane opens in the work area.
3. In the Daylight Saving Time area, click Configure. The Configure Daylight Saving
Time Parameters dialog appears.
3-25
.4
4-1
3. Set the Output Relays (on page 4-4) according to the installation: External Controls or
Office Alarms.
4. Set the Module Configuration method - determines if external modules (SFP) are
enabled automatically (default). The external module is always identified. However, in
order for it to be monitored, the appropriate option has to be enabled as well.
4-2
Sealing Current is disabled (OFF) by default. To enable the Sealing Current, set the
option to ON only on the ML CO. If applied from both sides, the Sealing Current will be
neutralized.
7. Alarm LED Indication - defines the behavior responses of the Alarm LED on the unit
front panel. This option is NOT relevant if the Preset dipswitch (DS#1) is enabled.
8. Click OK.
4-3
The default setting is office alarm, which can be connected to external alarm device(s).
4-4
ML600 initialization
Note: Alarms suppressed due to Partial alarm LED configuration are not reported via GPO.
Select Operated/Release
4-5
4. From the Control Type list box, select a control type (AIRCOND, ENGINE, FAN,
GEN, HEAT, LIGHT, MISC or SPKLR).
5. Click OK.
4-6
Reported via GPO available on ML device (when connected and configured for External
Alarm purposes).
4.
5.
6.
7.
8.
To enable an alarm, in the appropriate row, select the Enabled check box.
From the Alarm Type list box, select the alarm type that fits the connected detector.
From the Alarm Severity list box, select the required alarm severity.
In the Alarm Description box, type a short description of the alarm.
Click OK.
4-7
4-8
FIRE Fire;
FLOOD Flood;
INTRUDER Intrusion;
MISC Miscellaneous;
SMOKE Smoke;
3. To set Cards/Modules Configuration control, from the Modules Configuration list box,
select Automatically/Manually for automatic or manual provisioning accordingly.
4. Click OK.
4-9
For SFP modules details see SFP Modules (on page 2).
To configure SFP module:
1. On the Navigation tree in the lower side bar, open Modules. The ML device Module
pane opens in the work area.
2. From the table select the SPF-1-1 row. Click Configure. The Configure Module SFP-11 dialog appears.
4-10
PFU-8 Configuration
PFU-8 Configuration
PFU-8 devices can be remotely monitored and controlled via the ML600 unit to which the
PFU-8 is connected. In order to enable PFU-8 monitoring and controlling, it is required to
configure the relevant PFU-8 module for monitoring via the ML device.
PFU-8 operation is configured via dip switches on the PFU. See the PFU-8/PFU-8C/PFU-8E
Quick Installation Guide for detailed instructions on PFU-8 installation.
Note: In order to allow remote monitoring, it is required to connect the AUX cable between
the PFU-8 and the ML device and to set the PFU dip-switch to remote control.
4-11
In order to enable TDM service in ML650 NE, Clock, Circuit Emulation Service (CES) and
DSx1 (E1 or T1 protocol type) Service parameters should be configured. To enable TDM
Service through ML650 series P2P link, the following parameters should be configured on
the CO and CPE NEs:
4-12
2. In the Configuration area of the invoked pane, click the Configure button. The DSx1
configuration dialog appears.
3. Select the DSx1 Type - this defines the service type on a devices level.
Note: DSx1 Type defines the service type (applied on all DSx1 ports). All enabled DSx1
ports should be disabled prior to DSx1 Type change.
The ML650 series supports the following DSx1Types:
T1 Framed - 1,544 Mbps speed interface with ability of frame alignment monitoring
(signal problems and frame problems LOF/RAI are monitored). T1 framed
selected protocol allows to select specific data channels (1-24 available in T1) to be
forwarded through CES (this will reduce BW needs on HSL required for DSx1
emulation).
4-13
E1 Framed - 2,048 Mbps speed interface with ability of frame alignment monitoring
(signal problems and frame problems LOF/RAI are monitored). E1 framed
selected protocol allows to select specific data channels (1-31 available in E1, time
slot '0' is always used for frame signaling) to be forwarded through CES (this reduces
BW needs on HSL required for DSx1 emulation).
4. Select the CES Payload - specifies the quantity of TDM data (by bytes or TDM frames)
to be accumulated in a single Ethernet packet prior to being forwarded towards the CES
interface (HSL port).
The CES Payload size has a direct impact on received Delay and bandwidth required on
HSL port to support the TDM traffic. Larger CES Load size will reduce the required BW
to support the TDM traffic, however it will increase the service latency.
The following table summarize the delay and overhead, if framed, TDM services (in case
of unframed - each frame is equivalent to 192 bytes of unframed T1 or 256 bytes of
unframed E1):
Table 7: Payload Size
Payload size
CES delay
Additional OH (vs. 8
TDM frames)
0.125ms
134%
0.25ms
56%
0.5ms
12.5%
1.0
0 (reference value)
2.0ms
-9.8%
4.0ms
-14%
Increasing the number of TDM frames per packet by 8 frames adds 1 millisecond delay
(i.e. 16 frames per packet would add 2 milliseconds).
For unframed DSx1 Types - CES Payload is specified in bytes/packet (bytes per Ethernet
packet) units.
For Framed DSx1 Types - CES Payload is specified in TDM frames/packet (TDM frames
per Ethernet packet)units
The supported ranges and default configurations are:
4-14
For T1/E1 Unframed - selectable from values of 24, 48, 96, 192, 384, 768 for T1
Unframed and 32, 64, 128, 256, 512 for E1 Unframed. CES Payload is specified in
bytes/packet units.
5. Set the CES Jitter Buffer - specifies the size (in milliseconds) of the packet jitter buffer.
The buffer absorbs packet delay variations in order to provide steady (synchronous) bitstream of TDM data.
CES Jitter Buffer has a direct impact on transmitted traffic delay, the jitter buffer size is
typically added to the link latency (e.g. additional 4 miliseconds in case of keeping
default 4 milisecond jitter buffer value) and in worst case scenario the latency may
increase by double. Too small CES jitter buffer may cause data slips (reported as
CESLOS alarm) and data errors.CES Jitter Buffer size is specified in ms units, with
available values of 1, 2, 4 (default), 8, 16 ms (milliseconds) regardless DSx1 Type
configured.
Note: In case of HSL calibrated on low modem rates (less then 1 Mbps per modem), CES
jitter buffer may need to be increased from it's default value
4-15
The pane lists the available DSx1 ports along with status and configuration information
on each port. The pane provides access to port specific configuration options.
2. Select the port to be configured and click Configure. The port specific configuration
pane appears.
3. Enable the port by checkmarking the Enabled field in the upper left corner of the pane.
4-16
For E1 - always starting from channel number 1. Range: 1-31 (the 0 channel of the
E1 is always forwarded as a part of the frame signaling).
Note: The system has a limit on the minimal number of channels (limit depends also on
the configured "CES Payload Size" configured. In case that the configured number of
channels is not sufficient, appropriate warning message is provided.
6. Set the following fields according to your network services and click OK to save the
definitions and close the dialog.
Line Code
Line Mode
Line
sensitivity
(RX)
Line build out
* Relevant for
T1 service
only
4-17
4-18
Primary/Secondary (optional) clocks can be selected from enabled DSx1 Ports (on CO
NE only). If only None option is available in the Primary/Secondary Clock Sources fields
enable DSX1 (on page 4-12) ports as needed.
Note: ML650 system allows selecting clock source quality. Higher quality clock assumes
less tolerance to insufficient quality of incoming signal.
To avoid unneeded automatic protection clock switch, set the clock quality according to
the actual clock source quality.
3. To assign Clock Source quality, select one of three available options.
4-19
Holdover - switch to holdover. Output clock stops tracking any external clock
source and the clock keeps the same clock frequency which it was locked on prior the
clock switch. The clock quality is equal to internal clock oscillator source (output
clock will drift according to internal clock oscillator drift caused mainly by
temperature and aging).
Free-run - switch to free-run. Output clock stops tracking any external clock
source. Clock quality is equal to internal clock oscillator source (output clock will
drift according to internal clock oscillator drift caused mainly by temperature and
aging).
Note: after reboot (if occurs), the ML650 system will always try to re-synchronize with Primary
or Secondary external Clock Source if available.
4-20
For ML600 systems that support one HSL - all MLPs are allocated to HSL-1 (the only
available HSL)
For ML688 model (two HSLs) - MLPs 1 to 4 are allocated to HSL1 and MLPs 5 to 8 are
allocated to HSL2.
MLPs may be added to an HSL regardless of the calibration state of the HSL.
Note: It is not required to recalibrate the HSL each time an MLPs is added or removed
(although without calibration, HSL performance may be less than optimal).
Required MLP configuration: The only required MLP operation is to disable MLPs that
are not in use. (This procedure is usually performed as part of the preliminary configuration
performed during the installation procedure). In addition, MLP performance threshold can be
set per modem.
To configure modems:
1. In the Network Element tree, select Modem Ports. The Modem Ports pane opens
showing the list of MLPs according to individual MLU cards and corresponding modems
per card.
2. Select the modem(s) to be enabled or configured and click the Configure button. The
Configure Modem Port dialog appears.
4-21
Note: To select more then one MLP at at a time, click on the wanted MLPs while
holding the SHIFT button.
3. To disable modems not in use, clear the Enabled checkbox. The definitions will be
retained and reapplied when the MLP is enabled.
Note that in manual calibration mode, activated calibration will remain pending as long
as not all enabled modems are synchronized.
4. Set additional parameters according to the described criteria:
Circuit ID - used to enter text or information identifying the specific copper pair.
Max Allowed Rate - Only relevant for modems allocated to HSL configured to -O
(Office) mode. Set the maximum rate (in Kbps) for the specific modem. Default =
5,696 Kbps (see Maximum Rate Limits (on page 4-23) table for exceptions).
Minimum rate for ML deployed WITHOUT repeaters = 192 Kbps
Minimum rate for ML deployed WITH repeaters = 960 Kbps
Note: For more information on Alarm Threshold, see Copper Line Performance (on
page 13-68).
7. For extended (with Actelis repeaters) links, record the connections between copper-pair,
MLPs, PFU and XR-239 repeater:
4-22
Note: This does not affect the configuration - it is only a record for connections that can
be used in troubleshooting the links:
PFU Device - PFU device to which this MLP port is connected (only PFU-1 for
ML600 P2P topology).
For P2P topology, to indicates that the PFU ports are auto-assigned to MLPs select PFU Port = None and PFU Device = None.
8. Click OK.
RoHS6 Compliant
ML622
15,232 kbps
5,696 kbps
ML624
15,232 kbps
5,696 kbps
ML628
15,232 kbps
5,696 kbps
ML638
15,232 kbps
5,696 kbps
ML648
--
5,696 kbps
ML658
--
5,696 kbps
ML688
15,232 kbps
5,696 kbps
4-23
HSL Configuration
HSL Configuration
All ML600 systems, except for ML688, support one HSL; ML688 supports two HSLs. Each
HSL comprises of a set of modems (MLPs). In the case of ML688 that supports two HSLs,
the modems are preassigned to specific HSLs: modem 1 to 4 to HSL-1 and modems 5 -8 to
HSL-2. The modem allocation cannot be modified.
High Speed Link requires the "Calibration" process to be activated by the operator. The
calibration process achieves optimized modem rates for best-aggregated performance of the
modems in the HSL. During calibration, modems in the system need to pass a qualification
stage that identifies faulty pairs.
Notes: Before calibration ensure that all modems are synchronized. Non-synchronized
modems should be repaired or excluded (disabled) from the HSL.
This chapter describes how to configure and calibrate the High Speed Link.
HSL Configuration
HSL configuration consists of required and optional operations as follows:
You may also configure other parameter that optimize the link operation and determine
how the calibration procedure is performed
4-24
HSL Configuration
3. In the HSL ID field, enter an identifiable name for the HSL link (up to 32 characters. i.e.
Martin Indust Zone Build A).
If Apply to SNMP Alias is selected, the defined ID will be sent along with SNMP
information.
4. Configure the HSL according to the system topology:
Select the Topology according to whether Repeaters are installed over the HSL link:
Number of Repeaters (hops) fed from CO side or No Repeaters. Repeaters are
auto-discovered regardless of this configuration.
4-25
HSL Configuration
Enter the low BW threshold for this link in Kbps. Low range = 100, upper range
depends on module type, see Target BW Allowed values (on page 4-32) for specific
models configuration values.
This does not initiate the BW restoration procedure (on page 4-32), it only generates
an alarm.
6. To set the minimum Ethernet bandwidth threshold which will activate LLCF (Link Loss
Cary Forward):
Enter the desired value. Lower range = 100, upper range depends on module type see
Target BW Allowed values (on page 4-32) for specific models configuration values.
Automatic - Relevant for -O(Office) Mode units only. HSL calibration is activated
automatically on each restart (on Head-end and remote unit) and the following
parameters are predefined: BW = Best Effort, Spectral Mode = EU1, SNR margin = 3
dB. Spectral Mode and SNR Margin can then be re-configured. However, other
manual commands (stop HSL calibration or Cancel HSL calibration results) are not
allowed while auto-calibration is enabled.
4-26
Checkmark BW Restoration
Enter the desired value. Lower range = 100, upper range depends on module type
(see Target BW Allowed values (on page 4-32) for specific models configuration
values).
HSL Configuration
9. Enter the schedule of the BW restoration action (any time or scheduled to specific
hour/day)
10. To enable or disable the HSL link, in the dialog box, select or clear the Enabled check
box accordingly.
Note: You must disable modems prior to disabling the HSL.
11. To enter a detailed description or information on the HSL, such as Repeater locations or
any other relevant data:
RoHS6 Compliant
ML621
5,300 kbps
5,300 kbps
ML622
29,000 kbps
10,800 kbps
ML624
58,000 kbps
21,600 kbps
ML688
58,000 kbps
21,600 kbps
ML628
116,000 kbps
43,300 kbps
ML638
116,000 kbps
43,300 kbps
ML648
--
43,300 kbps
ML668
116,000 kbps
--
4-27
HSL Configuration
HSL Calibration
After basic configuration of the HSL, Ethernet traffic communication between two linked
Actelis systems is enabled using all the modems synchronized at 192 Kbps (or at 960 kbps in
case of repeater). To achieve the required throughput, the HSL should be calibrated, enabling
the modems to operate at the optimal rate under the existing environmental conditions. HSL
calibration can be performed regardless of the modems operating status. Calibration will
begin when the required modems becomes available.
Prior to configuring the system, obtain the following information:
Keep the following criteria in mind when specifying the calibration parameters:
Required HSL BW should NOT BE LESS than required Ethernet service BW.
Note 1: Required HSL BW should not be less than required Ethernet service BW. The
Achievable Calibration Target bandwidth depends on copper condition, topology, length,
gauge, etc. If no planning fault occurred, Achieved bandwidth will equal Calibration Target
bandwidth. If specified Target BW cannot be achieved, then calibration will complete with a
PLANFLT alarm raised on HSL.
4-28
HSL Configuration
Best Effort - Use Best Efforts Calibration if you require only an estimated expected
bandwidth result. This option will provide maximum BW achievable with the
connected copper loops under specified Spectral Mode and required SNR margin.
Achievable rates can be limited per modem port using the parameters Max Allowed
Rate.
Target Bandwidth - specified bandwidth. Lower range = 100, upper range depends
on module type, see Target BW Allowed values (on page 4-32) table for specific
models target BW values. The range can be modified in 1 Kbps steps.
Force Rate - calibration is performed only for modems that have reached the
required rate. Otherwise, those modems will not be included in the calibration
process. Minimizes the time required for calibration - faster than any other calibration
(about 2 minutes), however final HSL BW and modem's SNR margin are not
optimal.
4. Set the Required SNR Margin - the target Signal to Noise Ratio margin (in dB) required
for the copper lines. Default = 5dB
5. Select the Spectral Mode (Spectral Compatibility Mode). By default, NA1 is selected.
Appendix C - Technical Specifications lists and provides explanations on the available
Spectral Modes.
4-29
HSL Configuration
Spectral Mode that are not on the list can be added to the list using the procedure
described in Custom Spectral Mode (on page 4-37).
6. Setting the DSS (Dynamic Spectral Shaping) mode:
When Dynamic Spectral Shaping is enabled, the ML system takes into account
interference with other services in the binder and thus prefers, when possible, to use
higher TC-PAM constellations and increase PBO. See DSS Profile for additional
information on DSS parameters (on page 4-36).
YES - provides the highest PBO and highest TC-PAM achievable for specified SNR
Margin target within particular Spectral Mode and BW target (if applicable).
NO - provides the highest SNRM achievable within particular Spectral Mode and BW
target (if applicable).
7. Setting the Minimum Power Backoff (PBO):
This parameter defines the minimum PBO value available to the HSL modems during
(and after) the calibration process. This PBO is a transmit power reduction mechanism in
order to reduce interference to adjacent services in the binder.
The actual PBO is the GREATER value of the three: Min PBO, default PBO defined by
the Spectral mode and measured EWL, and max possible PBO computed by the DSS (in
case of DSS calibration). For more information see DSS profile description.
PBO range: 0 dB to 28 dB, default value is 0dB.
8. Set the Circuit Length Type - sets the EWL parameter:
Manual - type value manually. This is only relevant for EU5 and EU10 Spectral
Modes. The following table describes these Spectral Modes and the appropriate
categories.
Loop Attenuation
EU5
EU10
Ultra Short
Att. 11 dB
Extra Short
11 dB < Att. 21 dB
Short
21 dB < Att. 26 dB
Medium
26 dB < Att. 29 dB
Long
4-30
@100 kHz
29 dB < Att.
V
V
9. Verify the Rate Adjustment parameter is set according to your needs. This parameter
affects HSL modem(s) behavior during recovery (restoring failed modem
synchronization).
HSL Configuration
Note: If the Rate Adjustment is set to Not Allowed, Bandwidth Restoration will not
work.
After setting the Rate Adjustment to Allowed - re-calibration is required.
10. Extended Rates - supported by RoHS6 compliant models. Extended Rates allows up to
15Mbps for each copper-pair. This option is used for short distances and is relevant only
if the configured Spectral Mode supports these extended rates. Extended Rates
configuration also affects the Maximum Rate parameter.
Note: To see whether ML600 supports Extended Rates, see if the Spectral Mode field
options includes No Limit (up to 15M).
11. Click OK. The dialog box closes and a progress bar is displayed. You may pause or stop
the calibration process at any time by clicking Stop Calibration. This terminates
calibration and places the system in Up (MGMT only) mode.
Note: If the required number of modems is not currently available, a message indicating
so will appear. You may choose to automatically continue the process with the available
number of modems by clicking the Start Calib. Anyway button. A notification will
appear to confirm the action.
12. Verify the HSL Status is changed to Up. If within a few minutes the HSL status does not
change to Up, view the alarm displayed in the Alarms, Conditions table. See High Speed
Link Alarms Troubleshooting (on page 14-19).
13. The calibration process takes a few minutes. After successful calibration, the High Speed
Link pane appears showing information on the corresponding HSL.
4-31
HSL Configuration
RoHS6 Compliant
ML621
--
5,300 kbps
ML622
28,800 kbps
10,800 kbps
ML624
57,600 kbps
21,600 kbps
ML688
57,600 kbps
21,600 kbps
ML628
115,200 kbps
43,300 kbps
ML638
115,200 kbps
43,300 kbps
ML648
--
43,300 kbps
ML658
--
43,300 kbps
Upon detecting a reduced bandwidth level on an HSL, the ML is able (or can be configured)
to automatically begin BW Restoration on that HSL, to restore the calibrated bandwidth. The
individual modems that have adjusted down will, one by one, periodically, try to restore
themselves to the originally calibrated rate. The system can also be configured to begin the
bandwidth restoration procedure when a user defined minimum bandwidth threshold is
crossed, according to a user defined schedule.
In addition, the bandwidth restoration process can be initiated manually at a user's command.
Both automatic and manual BW Restoration procedure will start only when the following
conditions are met:
The HSL was stable (no failed modems) during at least 10 minutes before the low
bandwidth is identified or the scheduled time is due (automatic), or the manual command
is given
The HSL is qualified for BW restoration (i.e. there is high probability that the modems
will allow BW restoration).
4-32
HSL Configuration
2. Click the Configure button in the configuration pane area. The Configure High Speed
Links pane is invoked.
4-33
HSL Configuration
Note: It is recommended to set scheduled BW restoration (i.e. at hour (e.g. night) and
days (e.g. weekends) and not immediately, at any time) since operation interferes with
traffic.
4. Set the date and time for the procedure to start.
5. The procedure will start automatically at the set time (if necessary conditions are met).
Note: After the procedure starts, the Start BW restoration button that appears in the
bottom of the specific HSL pane toggles to Stop BW restoration button.
6. To stop the BW restoration procedure, click the Stop BW restoration button.
4-34
HSL Configuration
4-35
HSL Configuration
DSS Profile
DSS, Dynamic Spectral Shaping, configures the ML system to minimize the interference
with other services in the binder and thus uses, when possible, higher TC-PAM constellations
and increases PBO.
Power Back-Off (PBO) reduces the transmitted power on the DSL line. The modem power
backoff is set by the following:
Initial (default) power backoff set according to loop's Estimated Power LOSS (EPL) and
the region (North America or Europe). The initial PBO varies from 0dB to 6dB in North
America region and 0dB to 10dB in Europe region. This PBO is always supported.
User may configure a minimal PBO per HSL. The ML device will provide the greater
value between the initial PBO (1) and configured minimal PBO.
In case DSS Calibration is used, additional PBO may be set to the modems if the link
capacity enables it. The PBO is added in an iterative manner, number and step size of
PBO iterations is explained below.
4-36
The maximum Power Backoff (PBO) parameters define the maximal PBO on the
modems.
The max PBO per Iteration defines the maximal PBO step per iteration (PBO may be
set after multiple iteration in order to provide optimal PBO without reducing HSL
link performance).
The num of Iterations defines the number of PBO step iteration (PBO may be set
after multiple iterations in order to provide optimal PBO without reducing HSL link
performance).
HSL Configuration
Copper AWG/diameter
1-20 rows of Rate/Distance limitations for PAM16/PAM32 (option for PAM64 and
PAM128 for "non-standard" modem constellations). Instead of rates PSD masks may be
provided by the user to Actelis.
Max Rate
for PAM16
Max Rate
for PAM32
Max Rate
for PAM64
[Kbps]
[kbps]
[kbps]
Max Rate
for
PAM128
[kbps]
4-37
HSL Configuration
4-38
HSL port(s)
COLAN port - The COLAN (MGMT) Port by factory setup, is dedicated for out-of-band
Management but can be used also as a service port. Ensure that there are no Ethernet
loops between the COLAN (MGMT), ETH and HSL ports (use STP if required). To
dedicate the COLAN (MGMT) Ethernet port for service purposes, see Traffic VLAN
Procedure (on page 7-11). In addition, port priority and pinout must be changed
according to your setup. To dedicate the COLAN (MGMT) Ethernet port for
management purposes, see Management VLAN Procedure (on page 7-9).
The Ethernet configuration dialogs are invoked for each specific port and are similar in
appearance. However, not all attributes are relevant for all types of ports. For example, some
of the Physical Interface options which are accessible on Ethernet service ports dialogs are
not relevant (and so not accessible) on the HSL Ethernet configuration dialog.
4-39
4. In the SNMP Alias field, enter an identifiable name for the Ethernet link. Range = up to
32 characters. This description is NOT sent along with SNMP messages such as log
information.
5. Setting port communication. This parameter is not relevant to HSL ports.
4-40
The port communication mode is by default defined as Auto-negotiation, where the speed
and duplex mode are automatically recognized. In some cases, such as assigning the port
to a LAG or for 100BaseFX (fiber) ports, it is required to select the speed and duplex
mode.
ML624, ML628, ML648, ML658, ML654 - ETH-5 as 100 FULL (no AUTO)
Note: upon insertion of SFP module to the system. ETH-5 port is automatically
configured with: MODE=AUTO, Flow Control=OFF.
6. If Auto-negotiation is NOT selected, then perform this step. This step is not relevant for
ETH-5 port.
Note: When Auto-negotiation is enabled and link is Up, the MDI mode is automatically
detected (Auto-MDIX).
From the Pinout option, select the MDI (Medium Dependent Interface) - This is the
cable connector (pinout) between the signal transceivers and the link. Select as follows:
MDI-X - Default for Ethernet COLAN port. Crossed connection. Used when
connecting to an MDI device such as a PC NIC.
7. LAG assignment:
If the port is to be assigned to a LAG, select the LAG to which the port will be allocated.
Note that all ports assigned to the same LAG must have the same definitions. See Static
Link Aggregation (LAG) Configuration (on page 4-52).
8. Isolated Port:
To set the port as Isolated Port (on page 4-44) , select the Isolated Port filed to be
enabled.
By default the Isolated Ports option is disabled.
4-41
9. MAC Learning - defines MAC address learning operation mode on the interface:
Off - disables MAC address learning on the port. If MAC learning is disabled, traffic
is forwarded to all non-RX ports (broadcasted) participating in the VLAN with RXport.
Note: Learning can be applied asymmetrically: Limit learning on Customer access side of
CPE (ETH ports of ML600) and unlimited (AUTO or OFF) learning on Network access
side of CPE
10. Set the port Flow Control (not relevant to HSL ports). Flow Control is used to pause
ingress traffic (regardless of frame priority) when the egress port is congested.
Flow control on RX direction obeys instructions from the opposite port, to slow down its
own port transmit rate.
Flow control on TX direction instructs the opposite port to slow down it's transmit rate.
Flow Control can be established as a part of Auto-negotiation or can be set manually.
In manual setting it is important that both ports are configured in the same way and in the
same MODE, as the Flow control applied in HALF-DUPLEX and in FULL-DUPLEX
modes are incompatible.
Flow Control can be set to:
ON Flow Control mechanism starts work in both TX and RX directions of the port.
LLCF (Link Loss Carry Forward) (on page 4-45) - enabling this option reports
link loss problems on the network. The ports do not transmit a link signal until they
receive a link signal from the link partner. Link loss is "carried forward" to the
managed switch or hub that is sending the link. LLCF can be used on Ethernet ports
to propagate the HSL port failure.
EFM OAM - configures the port for OAM and automatically enables all the
corresponding options. See 802.3ah Ethernet OAM (on page 14-88) for more
information.
4-42
From the Ingress Frames to Limit list box, select All (default), Broadcast or
Broadcast / Multicast
Set the Ingress Rate Limit and Egress Rate Limit according to Coarse or Fine
granularity (Fine granularity is not available in all ML models) - see Rate Limit
Configuration (on page 4-50) for more information and limitations:
o
Fine granularity - Not available in all models. 1 Kbps steps (rounded upwards to
multiples of 64 Kbps)
4-43
On ML688 devices, any ETH or HSL port can be configured as an Isolated Port. On ML688,
Isolated ports can be used to direct the flow of information in one direction (i.e. toward the
Central Office).
To implement above case, set ETH-x ports and HSL-1 port as ISOLATED. (ETH-x, HSL-1
and HSL-2 should be in the same VLAN.)
This configuration guarantees bi-directional traffic between HSL-2 and ETH-x and HSL-1
and HSL-2, but NOT between HSL-1 and ETH-x .
Note: Isolated Ports configuration is done via the Ethernet Ports configuration pane. For more
details see Configuring Ethernet Ports (on page 4-39).
4-44
LLCF occurrence on an Ethernet port signifies that the ML NE port halts a link signal
transmit, emulating LOS on the connected ML devices.
LLCF clearance on an Ethernet port signifies that the ML NE port renegotiates and starts
transmit toward connected ML devices.
LLCF is raised immediately upon local HSL failure and within ~100 msec of remote
Ethernet failure.
LLCF is cleared only when Ethernet traffic is restored on the HSL (when synchronization
of all bonded in HSL modems is complete).
ML600 supports LLCF in both Downstream (on page 4-45) and Upstream (on page 4-47).
For additional configuration criteria, refer to When Configuring LLCF in ML Devices (on
page 4-49).
Downstream LLCF
For DOWNSTREAM link monitoring (useful in P2MP or P2P topologies):
CPE NE - should be configured to monitor local HSL port as an LLCF trigger this
allows monitoring local HSL port physical failure as well as CO NE port failures, which
are propagated via HSL by messages (CO failures will be sent to CPE NE only if HSL on
CO NE is configured appropriately).
If another CPE is configured as an LLCF trigger port, it shall detect LOS on its Ethernet
port and notify the CO NE. The CO NE provides "Intra-switch" between the CPEs and
sends LLCF to the target CPE.
4-45
Note: CO NE HSL can be optionally configured to monitor available HSL BW and report
LLCF notification upon configurable threshold crosses down.
The following figures illustrate end-to-end downstream LLCF notification for four types of
failures: HSL down, low bandwidth on the HSL, CO Ethernet port down and CPE port down.
4-46
4-47
The following two figures show examples of Upstream LLCF: loss of HSL and loss of CPE
Ethernet port.
4-48
In the Ports List, select each of the ports that will trigger the LLCF response if they
are disconnected, the frequency is below the defined threshold or the extended limits.
Click Add Port after each selection. The port will be added to the list. (To remove a
port, select the port and click Remove Port.)
A port which is specified as LLCF trigger on another port, cannot use this other port as
an LLCF trigger for itself.
4-49
A LAG cannot be added (as an item) to the list of monitored ports; however, individual
ports allocated to a LAG can be monitored.
On ML600 devices - either HSL or ETH ports can be specified as LLCF target or LLCF
trigger.
On ML130/1300/2300 devices - only HSL can be specified as LLCF target and only
either ETH(s) or neighbor HSL(s) can be specified as LLCF trigger
Multiple Ports can be set as LLCF trigger on all ML devices. If multiple LLCF triggers
are listed, the LLCF target port will forward the event (by message or disconnect) only if
all enabled ports listed as trigger will fail. If any one of the failed ports in the LLCF
Trigger List is up again, the LLCF target port will forward the event (by message or
recovery).
An SDU-400 system allows specifying the same port(s) in LLCF and APS trigger list.
An SDU-400 will not send LLCF trigger if the last port that failed in LLCF should be
immediately protected (i.e. is last in ALL APS group or belongs to ANY APS group and
no PROTFBLK SST occurs).
If an LLCF port cannot be immediately protected (i.e. is in ALL APS group which is still
active, or PROTFBLK time does not allow performing APS) an LLCF (toward the
HSL) will be sent.
Since the ingress rate limit is applied prior to classification, this type of limiting conflicts
with Quality of Service objectives configured on the ML600 NE.
Ingress rate limit on ANY type of traffic is available on ETH-x ports only - not on HSL
(to prevent in-band management loss)
Ingress rate limit less than 10 Mbps, may operate inaccurately for TCP traffic.
Some applications that use TCP transport will be affected by blocking ingressing traffic,
causing low utilization of Ethernet transmission bandwidth (significantly below the
configured limit). This may be improved by allowing ingress limit burst (per bridge
configured); however, for UDP type of traffic this setting will increase the Ethernet
transmission bandwidth above the configured limit.
4-50
Note: It is recommended to apply limiting on ETH-x port facing the customer is to set egress
rate limit on the customer side of the link, on the port of device attached to the ML NE port.
The following limitations applied to Egress Rate Limits are important deployment
consideration:
Egress rate limit on HSL ports should be set symmetrically on CO and CPE side
If egress rate limit is configured on an ETH-x port that operates in Half-Duplex (HD)
mode, the rate limit is NOT applied even if it is configured (and the status display
indicates configuration)
Egress rate limit applied on ETH-x ports using values selected from the Coarse
Granularity list, guarantee up to 95% accuracy of limited rate value. Values selected from
Fine Granularity (free text typed values) may provide less accuracy of limited rate value.
Egress rate limit applied on HSL port(s), may pass 30% more traffic (then in case of
1636 bytes frames) in case of frames of 64-bytes size. This is due to the NET traffic
calculation method and lack of Ethernet media overhead (IFG (Inter-frame-gap) and
Preamble bytes) on HSL "wire", which transmit Ethernet NET frames via MEF
aggregation over SHDSL modems.
The following figure shows a deployment example. For more information on how to
configure Rate Limit on each NE and port, see appropriate model User Manual, Ethernet
port Configuration (on page 4-39) chapter.
4-51
Logical aggregation
Load balancing - where load balancing is optimized for 2 and 4 ports in LAG. Load
between 3 and 5 LAG members may not be balanced equally
4-52
Configuration Considerations
STP is always disabled on the LAG (and participating ports); therefore the LAG cannot
be auto-disabled by STP decision, and continuously provides forwarding. It is strongly
recommended to avoid configurations where ML ETH-x ports or other LAG have a
duplicate connection with the LAG.
It may take up to 50 msec (and cause some traffic disruption) to recognize operational
failure of a port (LAG member) and switch over to another port (LAG member).
A LAG takes on the VLAN definitions of the first port assigned to the LAG.
For ML628 - when using PPPoE classification by layer 3 on an Ethernet port, this port
cannot be part of a Link Aggregation (LAG) group and there is load sharing.
Note: ML600 re-configuration from D-mode (VLAN-unaware) with LAG to Q-mode will
cause LAG members to be unbundled.
4-53
2. In the Link Aggregation pane, Configure area, click Configure. The LAG
Configuration dialog appears.
3. Activate the LAG by selecting the Enable box. The available LAG configuration
parameters will become activated.
The following parameters are automatically defined by the first port that is allocated:
Mode - the speed supported by the LAG, and LLCF - Link Loss Carry Forward. .
4. ML600 operate according to the Load Balancing Policy - MAC Source and Destination.
In this policy, packets are matched with given MAC source and destination addresses.
5. Allocate Ethernet ports to the LAG.
4-54
1. Referring to Ethernet Service, HSL and COLAN Ports Configuration (on page 4-39),
access the Ethernet Configuration dialog of each port that will be allocated to a LAG and
configure the following parameters:
Select full-duplex modes only and assign the same speed for all Ethernet port
allocated to a specific LAG.
Select the LAG to which this Ethernet port will be allocated. (Only enabled LAGs
will be displayed).
Configure ONE of the ports of the LAG according to VLANs (on page 7-1).
The VLAN configuration of the rest of the ports to be allocated to a LAG must be
empty.
4-55
.5
5-1
5-2
5-3
2. Click the Configure button. The Configure Ethernet Bridge dialog appears.
3. From the Mode list box, select the Ethernet bridge mode:
802.1D - VLAN-unaware
Note: Bridge-wide modes should be set equally on all Actelis systems installed in the
particular deployment.
4. Tune the Aging parameter - time that each newly learned address in the Forwarding
database entity is valid. Range 10 to 3600 sec. (Default = 300 sec.)
To disable Aging, clear the Aging check box.
Note: Since in ML device Bridge Learning is always enabled for all ports, disabling
Aging would eventually stop learning new addresses. When this happens, all subsequent
packet's source addresses cannot be learned. Packets designated to unknown addresses
are broadcast to all possible ports (all the ports that are members of the appropriate
VLAN).
5-4
5. MAC Limit Size - MAC Learning limit. This value selected limits the NE Learning
capabilities cumulatively on all Ethernet ports that are configured (see Ethernet Port
Configuration) to Limit MAC Learning. While no ports are configured to Limit MAC
Learning, MAC Limit Size value does not affect the system. Range: 2 to 32 (MAC
addresses). (see Ethernet Port Configuration (on page 4-39)).
Note: MAC learning limit is available in Q-bridge mode only. The number of VLANs
available for configuration is limited to 255 (in range from 1 to 4095) when MAC
learning limit is enabled (configured on at least 1 Ethernet port).
6. MAC Limit Handler - determines the behaviour of ports whose MAC Learning is
defined as Limit in the Ethernet Ports Configuration (on page 4-39). The options are:
Drop Unknown Unicast - All Unknown MAC SA frames in ingress direction (from
wire) and Unknown MAC DA frames in egress direction (towards wire) are dropped.
PPPoE (option available on ML624/628 and ML622 RoSH-6 compliant models) with presence of this encapsulation type, ML NE allows either L2 (by CoS bits) or
Layer-3 (by DSCP/ToS bits) classification with the following limitations:
o
L3 Classification can be applied only on a single Port (all other ports can be
configured to Fixed classification)
Two VLAN ID (4093 and 4094) are deleted (if configured) and reserved for
internal use only.
9. Select Ingress Limit Burst behaviour, applied only when Ingress Rate Limit is specified
on the Ethernet port(s):
5-5
If Ingress Limit Burst is Allowed (default) and Ingress Rate Limit is set on the
Ethernet port, an additional memory buffer is allocated on the ingress direction of the
port, which allows - in case of TCP traffic (with burst nature), to accept more traffic
without dropping it immediately, and to forward toward egress port, where egress
behavior is applied. The ingress burst buffer doesn't guarantee that all accepted traffic
will be forwarded, but it improves the TCP traffic utilization through the Ingress
Limited Port.
If Ingress Limit Burst is Not Allowed and Ingress Rate Limit is set on the Ethernet
port, the port accepts an exact amount of traffic as specified within ingress rate
limiting.
10. In 802.D mode, the Management VLAN ID box is configurable via this dialog box. For
in-band management you need to specify management traffic type (VLAN-tagged or
untagged) and for tagged traffic to set the Management VLAN ID.
Note: If STP is disabled, do not connect more than one ETH port and COLAN (MGMT)
port to the same adjacent switch. See Resolving Non-Alarmed Service Problems (on
page 14-81).
11. Tag Type is by default set to 0x8100 (HEX format) and can be changed (Q-Bridge mode
only) according to the devices in the network.
The Tag Type can be modified under the following conditions:
No Ports with Untagged Membership (in either TRFC VLAN or MGMT VLAN) are
defined.
No MGMT VLAN with more then one Tagged Membership port is defined.
5-6
LLDP Configuration
IEEE 802.1ab defined Link Layer Discovery Protocol (LLDP) allows L2 (Ethernet)
discovery of attached to ETH-x/COLAN ports of ML devices using the NEs Linked via
Ethernet (on page 13-83) option in the Network Element Tree. This feature is parallel to the
"NEs linked via HSL" feature (also in the NE Tree), which provides L1 (EOC) discovery of
attached to HSL-x ports devices (CPE NE).
LLDP is disabled by factory default on ML NE (in navigation tree this pane is grayed-out).
Enabling LLDP on an ML NE will cause the ML device to start sending identification
towards attached devices. If the attached devices don't support LLDP, the discovery table of
ML NE will stay empty.
To enable discovering NEs Linked via Ethernet
1. In the Network Element tree, select Ethernet Bridge. The Ethernet Bridge pane opens.
2. In the Configuration area, click the Configure LLDP button. The Configure LLDP
dialog appears.
Configure the Transmit Time Period - this is the interval of time between two
sequential LLDP messages to be sent. Default = 5
5-7
5-8
The general ML640/ML650 models Quality Of service flow is described by the following
figure:
Note: Flow control feature, when enabled, is related to the frames congestion control, and
may contradict with the expected Quality of Service result, due to the fact that frames will be
dropped prior to classification.
Classification to Queues
Classification is done on ingress direction of any port, inspecting the traffic frames Arrival
port, COS or TOS/DSCP bits content. The subject of inspection for classification can be
specified per each port differently.
ML600 devices support the following types of classification applied on ingress ports:
Forced priority.
By Layer 3 Priority.
5-9
5-10
HH, MH, L or LLL - provide forced priority. ALL of the port incoming frames are
mapped to the selected queue: HH - Highest, MH - High, L - Medium or LLL Lowest.
Layer 3 Priority - incoming frames are mapped to a queue (of egress port)
corresponding to their DSCP or ToS bits detected in the IP header of the frame. Both
VLAN-tagged and VLAN-untagged frames can be classified.
Note: By L3 Priority classification is limited to a single port only, if PPP
encapsulation is selected on bridge.
3. Click OK.
Note: Traffic may be briefly disrupted during the implementation of Ethernet port configuration
changes.
L3 DSCP bits
L3 ToS bits
Class (Queue)
0-1
0-15
0-1
LLL
2-3
16-31
2-3
4-5
32-47
4-5
MH
6-7
48-63
6-7
HHH
5-11
The current classification mapping rules are displayed, along with the ports on which By
L2 priority is configured (i.e. ports on which L2 Priority will be used).
2. In the invoked pane, click Configure. The Add L2 Classification Rule for Ethernet
Bridge dialog appears.
3. To configure a single priority, select the Priority option and type in the priority (from 0
to 7).
4. To configure a priority range, select the From Priority option and type in the From and
To range.
5. From the Traffic Class list box, select the traffic class.
6. Click OK. The priority range appears in the table. Multiple ranges in each class are
separated by a comma.
7. Repeat the procedure for additional priority configurations.
8. To restore default priorities, click Set to Default.
Note: If a particular Priority value is not specified for change then it is kept with its current
configuration.
5-12
3. To configure a single priority, select the Priority option and type in the priority (from 0
to 63).
4. To configure a priority range, select the From Priority option and type in the From and
To range.
5. From the Traffic Class list box, select the traffic class.
6. Click OK. The priority range appears in the table.
7. To restore default priorities, click Set to Default.
Note: If a particular Priority value is not specified for change then it is kept with its current
configuration.
5-13
ML640/ML650 Classification
As specified in the general ML640/650 QOS flow scheme (see Quality of Service (QOS)
(on page 5-8)), frames are additionally handled on egress direction of HSL port prior to being
forwarded to the HSL wire.
Identification Rules and Services (see EVC Configuration (on page 9-1)) configured for
HSL only, are additionally applied to the traffic and may be either equal to or differ from the
all-ports-applicable Classification Tables.
ML640/ML650 models by Factory default provide rules which are equal to the By L2
Priority classification scheme selected on all Ethernet ports, and apply default according to
the L2 Priority (COS) Classification Configuration (on page 5-11) table settings.
For frame routed to the Highest Priority Queue COS bits will be set to 7,
For frame routed to High Priority Queue COS bits will be set to 5,
For frame was routed to Medium Priority Queue COS bits will be set to 3,
For frame was routed to Low Priority Queue COS bits will be set to 1.
ML640/ML650 devices allow flexible COS bits marking towards the HSL using the
following configurable parameters:
5-14
SERVICE QUEUE ID - specifies the CLASS of the Ethernet frame, see ML640/ML650
- Defining EVC Services (on page 9-9).
CLASS to COS bits Mapping table - maps between CLASS assigned to the frame and
COS bit to be written in outer tag.
Marking flow is continued on CO NE, where ML devices allow overwriting COS bits of
external VLAN tag (usually already Service Provider tag), using COS bits translation table,
which is per-bridge configurable. Mapping is applied for Incoming traffic on HSL ingress
ports, before classification, on ML600 systems.
To view and modify COS marking
1. In the Network Element tree, expand Ethernet Bridge and select L2 priority Remarking. The pane shown below appears.
The pane shows the classification results translation table (and the translation
configuration dialog). By default, marking is transparent.
5-15
For ML640/ML650:
Click the Configure button in the window area (Egress or Ingress for
ML640/ML650). The Configure L2 Priority dialog appears as show above.
For each COS bit to be translated, select the corresponding value in the To COS bits
column.
3. Click OK.
5-16
5-17
2. To configure the Scheduler (under the QoS section), select one of the following schemes
from the drop down menu:
Strict Priority - Higher priority queues are prioritized over lower. No frame is sent
from a lower priority queue ever, while at least one frame waits to be transmitted to
the network in a higher priority queue. Note that if transmission of a frame from a
lower queue is started, switching to the higher queue will occur only after
transmission of the whole frame is completed.
3. Click OK.
5-18
2. Configure the Scheduler under the QoS section (as for all ML600 models, see ML600
Scheduler Configuration (on page 5-17))
3. In addition to the above, WFQ Weights (6 of 8) can be selected by configuring the
Scheduler field located under Toward HSL:
Queues H to LLL are handled by weighted fair queue scheduling. Each queue can be
assigned weight that determines the number of frames that will be forwarded from
this queue before the next (lower) queue is given priority (switched).
4. Click OK.
5-19
5-20
STP/RSTP Principles
cSpanning Tree provides a loop-free network. When a bridge that supports STP recognizes a
loop in the network topology, it blocks one or more redundant ports. Spanning Tree Protocol
continuously explores the network, so when the network topology changes, STP
automatically reconfigures the bridge ports to avoid failure by blocking a certain port.
Spanning tree algorithm-aware bridges exchange configuration messages periodically. The
configuration message is a multicast frame called BPDU (Bridge Protocol Data Unit) or
Hello message. According to the BPDU, these STP-aware bridges will construct a loop free
network with a tree architecture.
There is no difference between STP and RSTP implementation, except for defining the
addressing space which allows the coexistence of fully separated Customer and Provider
loopless topologies.
Note: For demarcation through a single NE, port-based onfig
should be used.
5-21
2. Path cost is the total cost of transmitting a frame on a LAN through that port to the bridge
root. It is assigned according to the bandwidth of the link. The slower the media, the
higher the cost. Some of the path costs specified in the IEEE 802.1d specification are
listed in the following table.
Note: When multiple ports have the same path cost to root bridge, the port with lowest
port priority is selected as the root port.
3. Select a designated port on each segment
For each LAN segment (collision domain), there is a designated port. The designated port has
the lowest cost to the root bridge. Designated ports are normally in the forwarding state to
forward and receive traffic to the segment. If more than one port in the segment has the same
path cost, the port on the bridge which has the lowest bridge ID is selected as a designated
port.
4. Active Topology Monitoring and Update
After STP determines the lowest cost spanning tree, it enables all root ports and designated
ports, and disables all other ports. Network packets are therefore only forwarded between
root ports and designated ports, eliminating any possible network loops. STP-aware devices
exchange BPDUs periodically. A new spanning tree is constructed when the bridged LAN
topology changes.
Once a stable network topology has been established, all bridges listen for Hello BPDUs
transmitted from the root bridge. If a bridge does not get a Hello BPDU after a predefined
interval (Max Age), the bridge assumes that the link to the root bridge is down. This bridge
then initiates negotiations with other bridges to reconfigure the network to re-establish a valid
network topology.
STP/RSTP in ML Systems
Actelis ML devices support STP/RSTP in accordance to either Customer Bridge (IEEE
802.1d) or Provider Bridge (IEEE 802.1ad) standards, where STP/RSTP BPDU Address is
configurable per Network Element:
5-22
IEEE 802.1d uses the reserved MAC 0x01-80-0C-00-00-00 for STP/RSTP BPDU.
IEEE 802.1ad uses the Reserved MAC 0x01-80-0C-00-00-08 for STP/RSTP BPDU.
The two reserved MACs are additionally controlled by L2CP application. When L2CP is
configured to DROP or TUNNEL, the reserved MAC, STP application is not triggered. The
STP BPDU behavior that is described below, is valid only when L2CP control (port level
configurable) for the chosen reserved MAC (0x01-80-0C-00-00-00 or 0x01-80-0C-00-00-08)
is set to PEER handler. PEER handler accepts BPDU locally on NE, and performs according
to the application configuration.
Table 14: STP Configuration Description
STP Configuration
Description
3. Configure the parameters according to the definitions in the table below and click OK.
5-23
Description
Enable
Protocol Type
Max Age
Maximum time for keeping the received protocol information recorded for a port
before discarding it.
Select the maximum age (6 to 40 seconds).
Hello Time
Determines how often the switch broadcasts its hello message to other switches.
Select the Hello Time (1 to 10 seconds)
Forward Delay
Defines the timeout to be spent by a port in the learning and listening states. It is
the value of the forward delay parameter of the bridge.
Bridge Priority
The bridge with the highest priority is the Root bridge: The higher the Bridge's
priority value, the lower it's priority.
Select the Bridge priority (0 to 61440 in steps of 4096)
Bridge Group
Address
5-24
3. Click Configure. The Configure STP for <port name> Port opens.
4. Configure the parameters according to the definitions in the table below and click OK.
Table 16: STP Port Level Parameters
Parameter
Description
Enabled
Enables this port to operate with STP/RSTP according to the bridge level
definitions.
Priority
Priority taken into account by STP when selecting a LAN port to put into the
forwarding state. Higher Priority ports will be selected first.
If all LAN ports have the same priority value, STP sets the LAN port with the
lowest LAN port number in the forwarding state and blocks other LAN ports.
Range: From 0 to 240 in steps of 16.
Path Cost
The STP/RSTP path cost default value is determined from the media speed of a
LAN interface.
Note: Possible values: 1 - 200,000,000 for RSTP and 1 - 65535 for STP.
Default values vary per AID; see Appendix C - Technical Specifications.
Edge Port
Link Type
Auto - Default.
P2P - Recommended for rapid-PVST+ mode only. Specify that the link type for
this port is point-to-point.
If you connect this port (local port) to a remote port through a point-to-point link
and the local port becomes a designated port, the switch negotiates with the
remote port and rapidly transitions the local port to the forwarding state.
5-25
.6
6 Ethernet Service
Configuration
Ethernet services are defined by a range of attributes, some of which are applied
at the UNI while others are applied at the EVC or service itself, to provide endto-end provisioning. This chapter describes how to implement service attributes
at the EVC (or service) on ML600 (and ML640/650) systems.
EVC service attributes can be defined either via the Service Configuration
Wizard (on page 2-17) or by following the step-by-step detailed instructions
according to the steps provided in this chapter.
In This Chapter
Service Configuration Procedure .................................. 6-2
Service Configuration Details ........................................ 6-3
6-1
6-2
6-3
Enable and add the new LAG to the LAG Ethernet Ports.
Verify that all of the Ethernet ports which will be assigned to the LAG are adjusted
with the same Speed attributes.
Note: the auto-mode cannot be used, and VLANs should not be assigned.
2. To configure the Ports see Ethernet Port Configuration (on page 4-39). To configure
the LAGs, see Static Link Aggregation (LAG) Configuration (on page 4-52).
3. To configure the VLANs see VLAN Configuration (on page 7-1)
Step 5: Control special content (L2CP) of the service
Configure the method in which the system handles L2CP frames (Eliminate / Handle /
Tunnel), according to the Customer Service Requirements.
For more information see L2CP Processing (on page 8-1).
Step 6: Check the Service Connectivity
After completing the above steps, the Ethernet Service traffic is configured. At this phase, the
Service Connectivity should be verified, and handled if needed, by performing the following
tests:
Send a Ping either to the CPE IP or to an IP beyond the CPE (if the customer LAN IPs
are known) from the WAN Management host. In addition check Ping to the CO.
If the ping fails, see Verifying Service Traffic and Connectivity (on page 14-81).
Check the CPE ETH port (which was previously configured to support the service traffic)
response to the commands: Suspend and Resume (the traffic should be stopped/resumed).
For more information see Ethernet Service Suspension and Restoration (on page 1493).
6-4
When planning the network service flow, note that the Ethernet service throughput of the ML
NEs (any model) is calculated as "Net" traffic; i.e. without the 20 bytes of the Ethernet media
overhead (Inter-frame-Gap and Preamble) added to each Ethernet frame, but rather with the
L2 frame content only.
For ML600 NE configuration instructions see Quality of Service (QOS) (on page 5-8), and
Rate Limit Configuration (on page 4-50).
For ML640/650 NE configuration instructions see Quality of Service (QOS) (on page 5-8),
Rate Limit Configuration (on page 4-50), and EVC Configuration (on page 9-1).
Step 8: Set CFM Maintenance Point
To complete the service provisioning, a CFM option can be enabled per EVC service flow,
controlling end-to-end consistency of Ethernet Service configuration, and providing
continuous connectivity check of Service traffic.
For more information about configuring the CFM Maintenance Point (either MIP or MEP) on
CO and CPE NEs, see Ethernet CFM Configuration (on page 10-1).
6-5
.7
7 VLAN Configuration
Actelis products use VLANs for cross-connections between Ethernet ports,
providing both Ingress and Egress VLAN Forwarding Rules in a single
operation VLAN configuration.
In This Chapter
VLAN Configuration Principles ...................................... 7-2
Membership Principles .................................................. 7-3
Management VLAN Configuration................................. 7-9
Traffic VLAN Configuration.......................................... 7-11
VLAN Topologies ........................................................ 7-13
7-1
VLAN Configuration
VLAN ID, VLAN name, VLAN type, VLAN port members and VLAN membership type are
configured per each VLAN.
VLAN type - defines the VLAN as either Traffic or Management. Only Management
VLAN includes implicitly (not user configurable) a CPU of ML Device, which allow ML
device Management access. Traffic VLANs will never access the CPU of ML Device.
VLAN port member parameter - defines the group of ports, which belong to the
particular Virtual LAN. The traffic is forwarded between VLAN members only, limiting
unknown MAC broadcast.
VLAN membership type parameter is specified per each VLAN port member and defines
both frame filtering and frame modification behavior of the port by a single parameter.
Filtering action types are one of the following:
1. Accept ANY traffic (VLAN-tagged or VLAN-untagged.
2. Accept only VLAN-untagged traffic.
3. Filter particular VLAN-tagged traffic.
Modification action types are:
1. Do not modify the frame.
2. Strip (on egress) and insert(on ingress) a new Tag.
Actelis products support 3 combinations of membership type called Untagged, Tagged,
Stacked. For more information see VLAN Membership Principles (on page 7-3).
7-2
Membership Principles
VLAN Configuration
Membership Principles
Port membership to a VLAN is determined by the bridge port on which data frames are
received. VLAN cross-connections provide forwarding rules applied on each port configured
as member in a specific VLAN. The guidelines provided in this section explain various
VLAN port membership forms.
The following figure shows how ports that are tagged members of a VID handle incoming
and outgoing frames.
7-3
VLAN Configuration
Membership Principles
Description
In
Out
Description
In
Out
7-4
Membership Principles
VLAN Configuration
The following figure shows how ports that are untagged members of a VID handle incoming
and outgoing frames.
Description
In
Out
7-5
VLAN Configuration
Membership Principles
Relevant Systems
All ML products
All ML products
ML600 products
ML130/ML1300/ML2300
7-6
ML600
Membership Principles
VLAN Configuration
Note: In addition, VLAN that have a Stacked port member, can have only ONE Tagged
member;
The following three figures illustrate the rules for Multiple VLANs that are members of the
same port.
7-7
VLAN Configuration
7-8
Membership Principles
VLAN Configuration
If out-of-band management traffic is tagged. In this case, modify the COLAN (MGMT)
port to be a tagged member of the Management VLAN;
If the assigned Management VLAN ID is already used in the MAN/WAN for traffic. In
this case, select a different VLAN ID for Management, equal to that used in MAN/WAN
for management purposes.
COLAN can be deleted from the MGMT VLAN and must be specified in MGMT
VLAN;
MGMT VLAN = 100 is defined on all HSLs (as Tagged member) regardless of their
provisioning status (even deleted).
7-9
VLAN Configuration
7-10
VLAN Configuration
Coordinate the VLAN number with the customer switch (network environment).
On ML600 models, if PPPoE option is enabled, VID=4094 and 4093 are reserved for
system use and cannot be configured.
On ML650 models VID=4092 is reserved for system use and cannot be configured.
All Ethernet ports including COLAN can be Untagged, Tagged or Stacked member of the
traffic VLAN.
If the VLAN has Stacked and Tagged ports, when Customer traffic is untagged, L2
Classification does not work on Tagged port (HSL). Therefore, if HSL BW is greater
than the ETH BW (limited by Port Mode), congested packets will be randomly dropped.
To add a VLAN
Note: This procedure is also relevant to Editing a VLAN (Edit VLAN).
1. In the Network Element tree, expand Ethernet Bridge and open VLANs. The VLANs
pane opens in the work area.
7-11
VLAN Configuration
You may assign the VLAN a name, in the Name box. Range: up to 16 characters.
To assign one or more ports simultaneously to more than one VLAN: Enable From VID
and enter a range of VLANs. Range: up to 4095
4. In the Service Port area, select either COLAN or ETH <ID> check box.
Note: COLAN as a regular Ethernet port, can be assigned as member of any traffic
VLAN.
5. Select the VLAN membership type for this port according to Provider/Customer network
requirements: : Untagged,Tagged or Stacked
6. Select the HSLs:
In the HSL Port area, select the HSL-1 check box (HSLs are always tagged
members)
7. Click OK.
7-12
VLAN Topologies
VLAN Configuration
VLAN Topologies
Actelis equipment allows building various Ethernet topologies in Service and Management
Traffic planes.
Prior to Ethernet topology planning verify and perform the following:
Verify that there are no loops in the Ethernet Topology - use Spanning Tree Protocol if
there are redundant connections;
Check MFS (Maximum Frame Size) size of frames - each new S-VLAN tag adds to the
frame an additional 4 bytes. Calculate the largest expected MFS size and check that it is
acceptable in the whole Network;
Ethernet Type of S-VLAN tag (default 0x8100 Q-n-Q Cisco) can be changed, but should
be acceptable on each Hop device;
Separate Customer and Provider Bridges Control planes - configure rules of L2CP.
This chapter provides examples of useful Ethernet topologies, with a description on how to
configure Actelis NEs to achieve each of them.
The desired topology should be carefully planned prior to configuration, preventing
Management LAN connectivity lost.
How to avoid L2 connectivity loss during Ethernet topology configuration:
Remember that the Management traffic plane may be affected by the Service traffic plane
you selected;
Start with the Management plane, not the Traffic plane configuration;
If integrity is lost, restore connection using Non-IP access to Linked by HSL NEs. The
channel works from the CO to CPE direction only and allows restoring the Management
LAN integrity.
Note: All Actelis NEs may perform as VLAN-aware (Q-bridge) or VLAN-unaware (D-bridge)
Ethernet Switches. Installations, which use different bridge modes (Q and D) on various NEs,
are possible but are not described in the examples below, and should be carefully planned by
the Providers' Ethernet Network Engineer.
7-13
VLAN Configuration
VLAN Topologies
Symmetric Topologies
In symmetric topologies, traffic beyond the ML edge devices (CO and CPE) is forwarded
unchanged. The symmetric topology matches with P2P installation needs, where ML NE is
used as a media converter only or where Customer and Provider site L2 plane is flatly
merged.
The following configurations of the ML link work for symmetric topologies:
HUB;
TUNNELS;
DROP-and-CONTINUE.
HUB Topology
In HUB mode, usually used in Campus /Enterprise environment, Actelis NEs behave as a
VLAN unaware switch (802.1D), where user cannot configure any VLANs.
Full connectivity is permitted from any port to any other port. Switching is done strictly
based on MAC address, ignoring VLAN information.
To configure "HUB" service traffic topology:
7-14
Set Bridge Mode= 802.1D on all NEs, starting from the most remote NE.
VLAN Topologies
VLAN Configuration
Note that in HUB mode management traffic is not separated from the Service Traffic and thus
cannot be terminated, i.e. there is no management demarcation point.
VLAN-tagged Management traffic can be recognized by Actelis NEs as well as VLANuntagged Management traffic.
7-15
VLAN Configuration
VLAN Topologies
Figure 17: Tunnels for any type of Customer Traffic, without Out-of-Band Untagged MGMT traffic
Table 21: Configuration summary for Tunnels for Any service traffic type:
CO NE
CPE NE
7-16
VLAN Topologies
VLAN Configuration
Figure 18: Tunnels for Untagged or Tagged with VID=PVID Customer Traffic, with In-band Tagged
MGMT Traffic
Table 22: Configuration summary for Tunnels for Untagged/Tagged with VID=PVID service traffic
type:
CO NE
CPE NE
7-17
VLAN Configuration
VLAN Topologies
7-18
Obtain the VID(s) (VID = 1 to 4095) to represent the Customer in Provider Network (by
SE-VID). Service Edge VLAN (SE-VID) can be added on each NE (CO or CPE or both).
Obtain the VLAN tag Ethernet type according to the Provider Network rules (default is
0x8100, like as in Cisco's Q-in-Q implementation);
Please use Online Help, available in MetaASSIST View, to get a detailed description on
how to perform the following configuration;
VLAN Topologies
VLAN Configuration
Configure chosen VID on all NEs, starting from the most remote NE, using the
guidelines for each topology, as described below.
Figure 19: Tagged Customer Traffic filtering, with in-band or out-of-band Tagged MGMT Traffic
available.
Table 23: Configuration summary for CE-VID no filtering, without preserving
CO NE
CPE NE
7-19
VLAN Configuration
VLAN Topologies
Configuration Procedure
Figure 20: Chained Tunnels for untagged Customer Traffic, with in-band Tagged MGMT Traffic
Table 24: Configuration summary for Chained Tunnels for Untagged/Tagged with VID=PVID traffic:
CO NE
Intermediate NE (optional)
CPE NE
COLAN [Tagged or
Untagged] for MGMT VID
(require STP).
7-20
VLAN Topologies
VLAN Configuration
Asymmetric Topologies
In asymmetric topologies ML NEs change the traffic, allowing inter-connect Customer and
Provider side L2 planes using VLAN stacking (adding SE-VLAN(s) in Provider direction
and stripping the SE-VLAN(s) in Customer direction).
The following configurations of ML link work for asymmetric topologies:
7-21
VLAN Configuration
VLAN Topologies
The follow sections provide schemes and the configuration order for all listed topologies
above.
7-22
Obtain the VID(s) (VID = 1 to 4095) to represent the Customer in Provider Network (by
SE-VID). Service Edge VLAN (SE-VID) can be added on each NE (CO or CPE or both).
Obtain the VLAN tag Ethernet type according to the Provider Network rules (default is
0x8100, like as in Cisco's Q-in-Q implementation);
Please use Online Help, available in MetaASSIST View, to get a detailed description on
how to perform the following configuration;
VLAN Topologies
VLAN Configuration
Configure chosen VID on all NEs, starting from the most remote NE, using the
guidelines for each topology, as described below.
Figure 21: CE-VID preserving without filtering, stacked per each Port on CPE NE.
Table 25: Configuration summary for CE-VID preserving/no filtering, with stacking per CPE port
CO NE
Intermediate NE (optional)
CPE NE
HSL-1 and HSL-2 are [Tagged] for HSL-1 [Tagged] for TRFC
TRFC VID and [Tagged] MGMT
VID and [Tagged] for
VID.
MGMT VID.
COLAN [Tagged or
Untagged] for MGMT VID.
7-23
VLAN Configuration
VLAN Topologies
Note: Equal VID on multiple HSL provides intra-switching between appropriate ports of
appropriated CPEs.
7-24
Obtain the VID(s) (VID = 1 to 4095) to represent the Customer in Provider Network (by
SE-VID). Service Edge VLAN (SE-VID) can be added on each NE (CO or CPE or both).
Obtain the VLAN tag Ethernet type according to the Provider Network rules (default is
0x8100, like as in Cisco's Q-in-Q implementation);
Please use Online Help, available in MetaASSIST View, to get a detailed description on
how to perform the following configuration;
VLAN Topologies
VLAN Configuration
Configure chosen VID on all NEs, starting from the most remote NE, using the
guidelines for each topology, as described below.
Figure 22: CE-VID preserving with filtering, VLAN stacking on CO NE per whole CPE NE
Table 26: Configuration summary for CE-VID preserving with filtering, with stacking on CO, per CPE
CO NE
Intermediate NE (optional)
CPE NE
COLAN [Untagged]
for MGMT VID (optional).
COLAN [Untagged]
for MGMT VID (optional).
7-25
VLAN Configuration
VLAN Topologies
7-26
TRFC VLAN with STACKED membership will serve Tagged Traffic (VID=20 in
the illustration below). All Customer traffic, passed through CPE is tagged natively
from Customer Side, or being modified on UNTAGGED port where default Port
VID is added
TRFC VLAN with UNTAGGED membership will serve Untagged Traffic (VID=200
in the illustration below). Only CPE Management traffic should be untagged.
MGMT VLAN ID on CPE NE (VID=200 in the illustration below) should be set on CPE
NE only. The same VID on the CO NE is configured as a TRFC VLAN (see above).
VLAN Topologies
VLAN Configuration
The next drawing illustrates configuration and traffic flow in case of CO/CPE Different
Management VLANs
For deployment with mixed (Tagged and Untagged) customer traffic (when CPE is in Dbridge mode) - CO HSL should be configured with Stacked TRFC VLAN only.
CPE management communication can be achieved only through non-IP CPE access (no
VLAN, IP configuration required). This case is illustrated in the figure below.
7-27
VLAN Configuration
VLAN Topologies
For deployment with Untagged customer traffic only (when CPE is in D-bridge mode) CO HSL should be configured with Untagged TRFC VLAN to accept and encapsulate
Service Traffic.
In this case the only way (except non-IP CPE access) CPE management communication
can be achieved is an additional Tagged MGMT VLAN on CO NE HSL (meaning that
CPE Management traffic must be Tagged and CPE NE D-bridge parameters should be
configured accordingly to specify MGMT VLAN on CPE).
For deployment with Tagged customer traffic only (when CPE is in D-bridge mode) - CO
HSL should be configured with Tagged TRFC VLAN(s) to accept Service Traffic.
In this case CPE management communication can be achieved by MGMT VLAN
configured on CO HSL - either Tagged (if Management traffic is tagged) or Untagged (if
Management traffic is untagged). Non IP-CPE access option is also available in such
deployments.
7-28
VLAN Topologies
VLAN Configuration
Obtain the VID(s) (VID = 1 to 4095) to represent the Customer in Provider Network (by
SE-VID). Service Edge VLAN (SE-VID) can be added on each NE (CO or CPE or both).
Obtain the VLAN tag Ethernet type according to the Provider Network rules (default is
0x8100, like as in Cisco's Q-in-Q implementation);
Please use Online Help, available in MetaASSIST View, to get a detailed description on
how to perform the following configuration;
7-29
VLAN Configuration
VLAN Topologies
Configure chosen VID on all NEs, starting from the most remote NE, using the
guidelines for each topology, as described below.
Figure 23: CE-VID preserving without filtering, VLAN dual stacking (per CPE port and per whole CPE)
7-30
VLAN Topologies
VLAN Configuration
Configuration summary for Dual CE-VID preserving/no filtering, stacking on CPE and CO
CO NE
Intermediate NE (optional)
CPE NE
COLAN [Tagged or
COLAN [Untagged] for MGMT
Untagged] for MGMT VID (to VID (optional).
manage CO NE)
(optional)(require STP).
7-31
.8
8 L2CP Processing
Layer 2 Control Protocols (L2CP) is a group of protocols standardized by IEEE
802.1, which are used by both Service Provider and Customer L2 Switching
Devices. The group of protocols is identified by its destination MAC address.
Each ML system allows per port behavior control over each MAC address of an
L2CP group. The following behavior can be defined:
- Discarding of undesired L2CP frames in Service Provider Network
Customer and vice versa, which provides full demarcation (as specified in IEEE
802.1ad standard) between Service and Customer L2 Switching devices.
- Peering (accepting and locally handling) of all L2CP frames, which
provides convergence of all L2 Switching devices into the one common
network.
- Tunneling (as specified in MEF-10), i.e. ability to forward Customer L2CP
frames through Provider Network. Two types of tunneling are supported:
Transparent and VLAN Tagged.
In This Chapter
Supported L2CP Protocols............................................ 8-2
Configuring Handling of L2CP Frames.......................... 8-3
Deployment Considerations .......................................... 8-6
8-1
L2CP Processing
ISL 01-00-0C-00-00-00
CDP 01-00-0C-CC-CC-CC
PVST 01-00-0C-CC-CC-CD
All other MAC in "X" range on ML600 will behave as regular traffic, i.e. they will be
accepted, dropped or modified according to VLAN membership of the port and received
frame format.
8-2
L2CP Processing
Note: To configure Cisco Frames behavior, click the Configure Cisco Address button.
Choose to either Drop the frames (default) or transparently transfer the frames to
specified multiple ports - regardless of the VLAN membership rules for these ports.
2. Select the MAC address corresponding to the protocol to be applied on the port and click
Configure Ports at the bottom of the pane. The following dialog appears.
The dialog shows all the ports along with the way they will be processed and the egress
ports.
8-3
L2CP Processing
Note: The Init button is used to reassign a selected port its default L2CP definitions. The
Init All Ports button is used to assign all ports their default L2CP definitions.
3. Select the port on which the previously selected protocol will be processed and click
Configure. The Behavior Configuration dialog appears. Note that only processing
relevant to the selected protocol are enabled.
4. Select the method according to which the protocol frame will be processed:
8-4
Peer - frame locally processed according to frame protocol. Requires that the ML is
configured to support the application (i.e. STP, OAM, Pause Frame, etc.).
L2CP Processing
Tunneling - Tunneling passes the customer control frames invisibly through to the
provider's bridge. Two types of tunneling are available: Transparent and Tag
(Tunneling by MAC is a future option):
Transparent - passes the customer control frames invisibly through to the provider's
defined Egress Port without modifying the header. Be sure tunneling is
unidirectional and defined properly on either side of each link along the route.
Manually configure the reverse direction of a transparent tunnel on all ports specified
as Egress Ports.
Tunnel by Tag Type - tags the frame and assigns it a VLAN ID. The frame is then
passed to the defined Egress Port and tunneled through the network as if it was a
regular data frame, according to the defined Tag and VLAN ID. After reaching its
destination (UNI) the tag and VLAN ID are removed. The modifications are made
only once on the CPE side. On the CO side, transparent tunneling is used. The
reverse direction of a tagged tunnel is defined automatically on all ports specified as
Egress Ports.
Tunnel by MAC and VLAN ID - Modifies the customer frame DST address to a
configurable MAC (only unicast address can be set) and encapsulates the frame
within a VLAN tag (with a configurable VLAN ID and Ethernet Type which is set
according to Bridge configuration). The frame is then passed to the provider's defined
Egress Port and tunneled through the network as if it was a regular data frame,
according to the defined MAC and VLAN ID. After reaching its destination (UNI),
the MAC and VLAN ID are removed. The modifications are made only once on the
CPE side. On the CO side, transparent tunneling is used. The reverse direction of a
MAC tunnel is defined automatically on all ports specified as Egress Ports.
Note: Tunnel by MAC should not be configured on Ethernet Ports which participate in
VLANs with stacked membership. In this case the configuration will not work.
5. Define the Egress Port (ETH-1 to ETH-5) via which the handled frame will be
forwarded to the network as follows:
From the drop-down options box adjacent to the Add Port button, choose the Egress
port.
Click Add Port. The selected port will be added to the Egress Port list. (To remove a
port, choose the port from the list and click Remove Port).
6. Click OK.
8-5
L2CP Processing
Deployment Considerations
Deployment Considerations
Special traffic (IEEE reserved multicast MAC addresses, Cisco management MAC
addresses) from the customer's LAN can be tunneled through the service provider WAN
without triggering L2 features (like STP) on service provider devices. This section provides
several examples to illustrate the issue.
Case 1. Customer LAN uses Cisco equipment and Cisco's STP (but not PVST+),
Provider WAN does not use STP
In most cases, Cisco equipment can be used in the customer's LAN without requiring
complex configuration of the ML - ML default L2CP configuration is sufficient.
By default each ML NE forwards all Cisco traffic (0x01-00-0C-**-**-** reserved for
proprietary Cisco protocols such as ISL, CDP, VTP, PVST+) as regular traffic (according to
VLANs membership rules (on page 7-6) configured on the NE).
To restore the default setting:
In the MetaAssist View, L2CP pane (on page 8-3), click the Configure Cisco
Addresses button, select as Regular Service Traffic, and click OK.
Note: Cisco frames can be also enforcedly forwarded ignoring regular traffic VLAN rules, and
using another VID dedicated for this purpose. For such deployment, use transparent tunnel
(see below) on CPE and tunnel by TAG on CO.
Case 2. Customer LAN uses Cisco PVST+, Provider WAN does not use STP
In some customer LAN configurations, where Cisco proprietary PVST+ works as standard
MSTP, it is additionally required to tunnel a standard BPDU frames (IEEE 802.1 Bridge
Group Access address 0x01-80-C2-00-00-00). Such tunnel should be configured on CPE and
CO ML on all Customer LAN sites using the following options:
1. Build transparent tunnel on CPE. This tunnel will forward the frame unchanged, cutthrough from Ingress to specified Egress ports, and ignore all VLAN filter, modification
and forwarding rules configured on the NE. Transparent tunnel should be set on all
directions on port(s) facing Customer LAN and port(s) facing Network WAN. Repeat
configuration on CPEs of all other customer site(s).
8-6
Deployment Considerations
L2CP Processing
2. Build tunnel by TAG (VID and optionally ETH-Type) on CO. This tunnel will forward
the frame after inserting a TAG with the specified VID and ETH-Type. The VID should
be set exactly as the Service VID (representing the Customer in WAN). This will allow
to merge this special frame with all other customer traffic that is forwarded toward the
service provider WAN. Tunnel by TAG is set manually only on ports ingressing from
Customer side (HSL-x on CO).
Note that the reverse direction of the tunnel on the same NE (ETH-x to HSL-x) is built
automatically (and invisible in L2CP table). Repeat configuration on COs of all other
customer site(s).
Note: You can apply TAG tunnel starting CPE (not very reasonable, but possible). Note do
not use 0x8100 Eth. type if frame is tunneled via stacked ETH port.
Case 3A. Customer uses Cisco PVST+, Provider uses IEEE 802.1 STP/RSTP or Cisco
PVST+.
In cases when BPDU frames (MAC 0x01-80-C2-00-00-00) are common for customer and
service provider devices it can be recommended to use MAC tunneling applied on CPE
(requires unicast MAC address to be used instead of MAC 0x01-80-C2-00-00-00).
The following configuration is allowed only if CPE has ETH port facing the customer
switches as Untagged or Tagged.
1. Build tunnel by MAC (and VID) on CPE .This tunnel will forward the frame with MAC
DA modified to specified multicast address and also tagged with VID equal to one of the
VID used for regular customer traffic forwarding. Tunnel by MAC is set manually only
on port(s) facing Customer LAN. Note that the reverse direction of the tunnel on the
same NE (HSL-1 to ETH-x) is built automatically. Repeat configuration on CPEs of all
other customer site(s).
2. Use regular traffic VLANs on CO. Repeat configuration on COs of all other customer
site(s).
8-7
L2CP Processing
Deployment Considerations
Case 3B. Customer uses Cisco PVST+, Provider uses IEEE 802.1 STP/RSTP
In cases when BPDU frames (MAC 0x01-80-C2-00-00-00) are common for customer and
service provider devices it can be recommended to switch Service Provider network (all
devices, including ML CO and even ML CPE NEs) to Provider Bridge MAC BPDU frames
(MAC 0x01-80-C2-00-00-08).
1. In the MetaAssist View, L2CP pane (on page 8-3), ensure that PEER handler is not
configured on any port for MAC 0x01-80-C2-00-00-00.
2. On L2CP pane, for MAC 0x01-80-C2-00-00-08, apply PEER handler on all ports
participating in the Provider Network and configure Drop handler on all Customer Facing
(demarcation) ports.
3. On the Ethernet Bridge pane, click the Configure STP button, select Bridge Group
Address equal to 0x01-80-C2-00-00-08 and Enable STP/RSTP. Click OK.
4. Repeat on all ML NE participating in the service provider STP.
Note: As demarcation between Provider / Customer Networks has no STP/RSTP solution,
ensure that ETH loops are avoided there.
8-8
.9
9 EVC Configuration
This chapter describes how ML640/ML650 models implement Advanced
Ethernet Services MEF features.
In This Chapter
Introducing MEF Terminology ....................................... 9-2
MEF10 QoS flow Overview ........................................... 9-4
Defining EVCs ............................................................... 9-5
Associating VLANs with EVC ........................................ 9-6
BW Profile Definition ..................................................... 9-7
EVC Services Definition ................................................ 9-9
Identification Rules Definition ...................................... 9-12
Deployment Considerations ........................................ 9-19
9-1
EVC Configuration
External VLAN TAG with Ethernet Type, VLANID and COS bits
Internal VLAN TAG with Ethernet Type, VLANID and COS bits
TOS/DSCP bits
9-2
EVC Configuration
The Bandwidth Profile handles a fundamental MEF concept of Ethernet Service throughput
control. A pool of up to 32 profiles can be configured on each ML device. The same BW
profile can be used by various Ethernet Services, simplifying the configuration process.
On the ingress port (prior to switch decision), the total bytes length and bits-per-second is
metered for each frame and it is determined whether the rate for this Ethernet Service
agreement (BW profile) was exceeded.
Three meter colors are used to distinguish between Committed (agreed for transmission with
guaranteed quality of service) and Excessive (allowed for transmission but with unguaranteed
quality) Informational rates (CIR and EIR). CIR and EIR rates are also provided with Burst
Buffer Size (to allow some fluctuations of traffic rate). These are named: CBS (committed
burst size) for CIR, and EBS (excessive burst size) for EIR. Traffic above
CIR+EIR+CBS+EBS is dropped (policed) on ingress, avoiding switching resources usage.
On the egress port (after switch decision), each Ethernet service flow can be (optionally)
shaped providing continuous un-bursty traffic transmission. The shaper rate is determined
according to the assigned BW profile (as CIR + EIR), and prevents from arriving ingress
bursts to be forwarded towards the next hop wire.
EVC Service handles the rest of the MEF fundamentals: a need for the Ethernet Service
classification (i.e. a decision regarding the appropriate queue in which the frame will be
stored prior to the transmission) and congestion avoidance control (how to schedule the
queue, allowing the prioritization of one service flow versus another). EVC Service on ML
NE is used for combining all of the above listed attributes:
9-3
EVC Configuration
As shown on scheme above, MEF10 QoS setting do not provide Ethernet Service traffic
connectivity between ports. Connectivity is provided by VLANs, which must be configured
in advance.
In ML640/ML650 systems Ethernet Service configuration flow is:
9-4
Define SERV (pool of 8) with selected BW profile to apply. Assign the SERV to EVC.
Up to 8 SERV can be assigned to the same EVC.
Define identification RULE (pool of 32 seven of which are internally used) with
particular L2, L3, L4 flow identification. Assign the RULE to SERV. Up to 32 RULES
can be assigned to the same SERV.
Defining EVCs
EVC Configuration
Defining EVCs
You may define up to eight EVC services.
To define an EVC
1. From the Network Topology tree, under Ethernet Services, select EVCs. The EVCs
pane appears. The pane lists the currently defined EVCs according to their EVC AID and
EVC ID and provides EVC management functions.
2. To add an EVC:
Click the Add button at the bottom of the pane. The Add EVC dialog appears.
Select the relevant EVC AID from the list (up to 64 EVCs can be defined).
Click OK. The description will be added to the EVC pane list.
Note: The defined EVC may be modified or deleted by selecting it and clicking the
corresponding buttons at the bottom of the pane.
9-5
EVC Configuration
To add an existing VLAN to an EVC, select the VLAN row and click Edit VLAN.
3. In the invoked Traffic VLAN pane, define the necessary parameters and select the EVC
with which the VLAN will be associated.
9-6
BW Profile Definition
EVC Configuration
BW Profile Definition
ML640 and ML650 supports the bandwidth profile definition (throughput) for each EVC
service. A single Bandwidth Profile is applied to all ingress Service Frames. In the example
illustrated below, there are three services, each identified by a CoS ID of the specific CEVLAN - each with a separate Bandwidth Profile.
This section describes how to create a pool of bandwidth profiles (up to 32) with meaningful
names. The profiles should be created according to the service provider's needs. They can
then be used as part of the attributes that make up definitions for various services.
To define a bandwidth profile
1. From the Network Element tree, under Ethernet Services, select BW Profiles. The BW
Profile pane appears.
The pane lists the currently defined pool of BW profiles (AID) along with their defined
rate limits (CIR, CBS, EIR and EBS) and the services to which each profiles were
assigned (Used by Services).
The operation buttons at the bottom of the pane are used to create and manage BW
Profiles.
9-7
EVC Configuration
BW Profile Definition
Use the the Rates (CIR/EIR) Presentation in option to configure the display of the BW
rate.
Click the Add button at the bottom of the pane. The Add BW Profile dialog appears.
Select from the list of the available Profile IDs, where defined profiles are removed
from the list: Range = BWPROFILE-0 to BWPRFILE-32
CIR (Committed Information Rate) - average rate up to which service frames are
delivered. All service frames are sent at the UNI speed, e.g., 10Mbps, and not at
the CIR, e.g., 2Mbps.
BS (Committed Burst Size) - the size up to which service frames may be sent
C
and be CIR-conformant. Range: Unlimited or up to 16,000 Bytes.
EIR (Excess Information Rate) - average rate, greater than or equal to the CIR,
up to which service frames are delivered without any performance objectives.
EBS (Excess Burst Size) - the size up to which service frames may be sent and
be EIR-conformant. Range: Unlimited or up to 16,000 Bytes.
3. Click OK. The new profile will be added to the Bandwidth Profiles list.
9-8
EVC Configuration
SERV-1 - for internal purposes, to allow L2CP and CFM features. Traffic of these
features is identified using Rules-{1-6}; SERV-1 cannot be deleted but its queue, shaper
and BW profile can be changed
SERV-2 - to set the default behavior of unclassified traffic to be passed at least with
lowest priority. Traffic is identified using Rule-32. SERV-2 cannot be deleted but its
queue, shaper and BW profile can be changed
SERV-3 is used for default MGMT traffic and can be deleted and edited.
SERV-4,5,6,7 is used for default L2 COS bits classification and can be deleted and
edited.
SERV-1 - for internal purposes, to allow L2CP and CFM features. Traffic of these
features is identified using Rules-{5-10}; SERV-1 cannot be deleted but its queue,
shaper and BW profile can be changed.
SERV-2 - to set the default behavior of unclassified traffic to be passed at least with
lowest priority. Traffic is identified using Rule-32. SERV-2 cannot be deleted but its
queue, shaper and BW profile can be changed.
SERV-3 is used for default MGMT traffic and can be deleted and edited.
SERV-4, 5, 6, 7 is used for default L2 COS bits classification and can be deleted
and edited.
SERV-8 is used for CES over ETH 4x DSx1 ports tunnel can be deleted or
edited.
9-9
EVC Configuration
Notes:
1. ML650 provides L2CP and CFM traffic prioritized (HHH) over DSx1 CES traffic (HH), this
configuration can be changed.
2. ML650 provides a single CES tunnel (HH) for all four DSx1 ports (each one identified by a
single rule). If required, DSx1 ports can be prioritized one to other, using various SERV AID
per Rule with different Queues ID configured for each SERV AID.
To change the default behavior of the system - i.e. all unclassified traffic to be dropped or
prioritized, use Lower Order Rule (RULE-31 and lower) to define the behavior.
To define an EVC service
1. In the Network Topology tree, under Ethernet Services select EVC Services. The
Services pane appears. The pane lists the currently defined services along with their
attributes.
9-10
EVC Configuration
2. To add a Service, Click the Add Service button at the bottom of the pane. The Add
Service dialog appears.
3. Select from the list of the available Service IDs. Up to 8 service IDs are supported
(SERV-1 to SERV-8). Only the available service IDs are displayed (i.e. defined services
are removed from the list).
4. In the Description field, assign the service a meaningful name.
5. Select from the list of predefined BW Profiles. Only defined BW profiles are displayed.
If the required BW profile is not available, define it via the BW Profile option and it will
be available for the service.
6. Select the Queue ID.
7. In the Shaper field, configure whether to apply shaper (Yes) or not (No) to the service as
the frames egress.
The Shaper is used to limit data transmit rate and remove data bursts. In ML640/650
models, the shaper is available per queue, and when "Service per Queue" is configured,
the shaper becomes a Service Shaper.
Service Shaper rate limit is calculated automatically as the sum of CIR + EIR (specified
in the BW profile(s) used by the Service(s) as Ingress Meter). For a Service with an
enabled Shaper, it is recommended to use a BW profile which doesn't limit the CBS/EBS
(should be set to unlimited), otherwise the shaper may work improperly.
Notes:
Shaper cannot be enabled for a Service, if the CIR and/or EIR specified in the BW
profile(s) used by that Service(s) are unlimited.
Shaper cannot be enabled for a Service, if the total sum of CIR+EIR specified for that
service(s) is greater than theoretically possible on the HSL port of the ML600 model.
8. Click OK. The new profile will be added to the Bandwidth Profiles list.
Note: The defined service may be modified or deleted by selecting it and clicking the
corresponding buttons at the bottom of the pane.
9-11
EVC Configuration
In ML640, the first six rules (identify reserved L2CP tunnel MAC addresses) cannot be
deleted or modified.
In ML650, additional four rules identify reserved Circuit Emulation Service (CES) tunnel and
cannot be deleted (but can be re-assigned to different and various SERV-AID to
separate/prioritize CES tunnels).
All other rules can be modified or deleted. The last rule identifies unclassified traffic and
forwards it with a lowest priority through the system.
To change the default behavior of the system, i.e. drop or prioritize all unclassified traffic, the
Lower Order Rule (RULE-31 and less) should be used to define the behavior.
The order of the identification rules is critical due to "First Match" principle implemented for
Identification Rules on ML640/ML650. A new rule can be added in any available rows (the
row number corresponds to the order of the rule). The order of configured rules (except for
the first six on ML640 / first ten on ML650 and last rule) can be modified.
Note: To change the order of pre-defined rules, use the up and down arrows at the right of
the rules table.
Rules can be imported (downloaded) to ML640/ML650 from a text file consisting of TL1
configuration commands.
9-12
EVC Configuration
The pane lists the currently defined Identification Rules along and provides access to rule
management options via the buttons at the bottom of the pane. The buttons are:
Configure rule - used to configure the attributes of the selected rule (for protected
from modification rules this button is grayed-out).
Load Config - used to load a text file of TL1 commands that defines the rule
attributes.
Select the appropriate rules from one of the rules available for configuration (the
Configure Rule button is enabled when relevant).
9-13
EVC Configuration
The dialog is divided into several areas that are described in the following steps.
2. General area - human-readable description and required behavior information of the
current rule. Configure the following:
9-14
Behaviour of frame - how to handle frames that match this rule. Values = Pass or
Drop (not supported on ML650)
Port - port to which this rule is applied. Only service Ethernet ports are supported
(HSL, COLAN and LAG port are not supported).
EVC Configuration
Class to COS Marking - COS bits of the frame will be set according to the Queue
where this frame was assigned (HHH,LLL). Classification Result (HHH ,
,LLL) mapping to COS bits (0 7) is configurable per ML640/ML650.
None - no additional marking applied. Which means that Original frame priority
is kept - when tagged original frame pass through a port with Tagged
membership defined on it). Or Port priority is assigned to the original frame when untagged frame pass through a port with Untagged membership defined on
it). Or Original frame Priority is copied to outer tag from inner tag when frame
pass through a port with Stacking membership defined.
Service - service (from the pool of predefined service IDs) to which the Rule
belongs. Multiple Rules can belong to the same Service. In this case BW Ingress and
Shaper definition are applied on a sum of traffic identified by these rules.
For Rules with Drop behavior - set Service ID to NONE.
3. Template area - pattern to recognize the traffic. Template defines the offset (relative to
the frame 1-st bit start) where the traffic should be validated with the parameter values
for L2, L3, L4 protocols.
In this area, rule pattern is defined according to templates. These should be inspected for
match. Deeper frame inspection requires more specific templates to be defined. Each rule
can use its own template. For example, in case of mix traffic (expected either single or
dual tagged on the same port) 2 rules should be prepared using different templates to
catch all required traffic.
Layer 2 - Untagged, Single tag, Double tag, CesOEth or unknown. CesOEth value is
available in ML650 series only.
4. Values area (Layer 2, Layer 3, External and Internal Tag and Layer 4). Defines the
content of rule. A frame is identified as belonging to the rule if the frame and rule content
matches in all specified fields. (Correct offset of fields is decided using the template of
the rule).
For CesOEth template selected, only CES ECID value selection is available, RULE-1
for DSx1-1-1 port traffic transfer, RULE-2 for DSx1-1-2, RULE-3 for DSx1-1-3, and
RULE-4 for DSx1-1-4.
For all other templates except CesOEth, Layer 2 values - MAC SRC and MAC DST
fields to inspect, available regardless template specification.
Define the MAC SRC and MAC DST to search for a match. The values can be
explicit or within a HEX range.See below the note regarding how to calculate the
range covered by a rule (using Hex Value and Hex Mask specified). See Calculating
the Range Covered by a Rule (on page 9-16).
9-15
EVC Configuration
External Tag Value - outer VLAN tag fields to inspect - available only if the
selected template refers to Single or Double tag pattern.
When available (depending on the selected template (Pattern)), allows to fill in outer
tag VLAN ID, COS or Tag Type (Eth.Type) to search for match. Either explicit
values or range (using BINARY mask) can be looked for match. See Calculating the
Range Covered by a Rule (on page 9-16).
Internal Tag value - inner VLAN tag fields to inspect - only available if template
refers to Double tag pattern.
When available (depend on selected template (Pattern), allows to fill in inner tag
VLAN ID, COS or Tag Type (Eth.Type) to search for match. Either explicit values or
range (using BINARY mask) can be looked for match. See Calculating the Range
Covered by a Rule (on page 9-16).
Layer 3 values - IP protocol fields to inspect. These values are available only if
selected template fully defines L2 and Encapsulation (between applied between L2
and L3).
In the Layer 4 area, when available (depend on pattern selected above), allows to fill
in L4 protocol value to match. Either explicit value can be looked for or HEX range
can be looked for (then mask should be specified)
5. Click OK.
9-16
Mask bit, when set to 1 requires result bit to be matched with a field value bit.
EVC Configuration
COS
Note that COS bit is provided in Decimal format and Mask is in Binary format.
The table below provides an example, how to use/convert formats for COS field
Table 27: COS
Numbering
System
Field Value
Mask
Result
DEC
{4-5}
HEX
0x4
0x7
{0x4 - 0x5}
BINARY
100
110
100 - 101
VID
Note that VID is provided in Decimal format and Mask is in HEX format.
The table below provides an example, how to use/convert formats for VID field
Table 28: VID
Numbering
System
Field Value
Mask
Result
DEC
16
16
{16-31}
HEX
0x10
0x10
-{0x10 - 0x1F}
BINARY
10000
10000
10000 - 11111
TOS/DSCP
Note that both TOS/DSCP and Mask fields are provided in HEX format.
Note that TOS/DSCP field values by DSCP standard are provided in Decimal value (0-63),
using 6 bits of 8 bits in a byte (starting from the highest bits of byte). To set TOS/DSCP field
value using HEX format, the value (e.g. PHB (per-hop-behavior) CS6 (class selector 6),
covers DSCP= 48-55) should be translated to BINARY 110000 and extended with 00
(for 2 lowest bits of the byte), the result value (11000000) should be translated to HEX
format (0XC0) and typed as a field value.
9-17
EVC Configuration
TOS
Numbering
System
Field Value
Mask
Result
DEC
192 :
224
{48 - 55}
PHB = 48
(x 4)
shifted left to
2 bits = 192
HEX
0xC0
0xE0
-{0xC0 - 0xDF}
BINARY
11000000
11100000
11000000 - 11011111
IP Address
Note that both IP Address field and mask are in Dot Numeric (decimal) format
Table 29: IP
Numbering
System
Field Value
Mask
Result
DEC
10.2.17.1
255.255.255.1
10.2.17.{0-255}
BINARY
00001010.
11111111.
00001010.
00000010.
11111111.
00000010.
00010001.
11111111.
00010001.
00000000
00000000
{00000000 11111111}
MAC
Note that both MAC address field and mask field are in HEX format.
Table 30: MAC
Numbering
System
Field Value
Mask
Result
HEX
0x00-03-8501-01-01
FF-FF-FF-00-0000
00-03-85-{00-FF}-{00-FF}{00-FF}
BINARY
00001010.
11111111.
00001010.
00000010.
11111111.
00000010.
00010001.
11111111.
00010001.
00000000
00000000
{00000000 11111111}
9-18
Deployment Considerations
EVC Configuration
Deployment Considerations
Queues Utilization
By default (factory setting), ML650 is configured to provide unlimited and prioritized TDM
services traffic throughout the HH queue, below management traffic. Management Traffic by
factory setting remains unlimited and prioritized through the HHH queue, above TDM
services.
It is not recommended to change Management Traffic priority, in order to maintain remote
management of the CPE.
The highest queue (even if handled as Strict Priority) cannot guarantee absence of disruption
from other queues traffic (see QoS, Scheduler page). This type of guarantee can be given
only if the queue is BUSY all the time, i.e. BW forwarded to this queue is equal to whole
HSL BW (calibrated and then, if applicable, egress rate limited).
To reduce Management traffic disruption on TDM services traffic, it can be useful to limit
Management Traffic with BW profile consists of CIR=100Kbps (can be more) and CBS=580
bytes (not less). It is recommended to use unlimited BW profile for Management Traffic in
maintenance window otherwise system administration operations (like SW, Configuration,
Log files transfer) will be seriously (tens of minutes) prolonged.
BW Profiles
Burst Size specified in BW profile should be correlated with Rate value of BW profile. Set
the burst size to at least a double of max frame size. If you dont know the fame size, you can
safely set the burst size to 3000 Bytes.
EIR rate value specified in BW profile is set in addition to CIR value specified (not including
CIR value, as available on some network devices).
ML doesnt count IFG (Inter-frame-gap) and Preamble bytes as part of Ethernet Service BW.
Rates specified in BW profiles are for NET Ethernet traffic (bytes of ETH frames).
Shaper Usage
Shaper OFF helps for higher quality of traffic which is sensitive to latency and frame delay
variation, i.e. the shaper OFF means that there is no additional controller which changes
traffic beat pattern.
Shaper ON helps for higher utilization of Ethernet throughput (reduce re-transmission) on
traffic with burst nature (like TCP).
If you disable the shaper the UDP traffic will have less delay variation and min latency, but
the TCP may not utilize all the available B/W. Some UDP traffic (e.g. video) is not that
sensitive to latency and PDV, so I would recommend enabling the shaper in this case (mix of
video and TCP).
9-19
EVC Configuration
Deployment Considerations
In configurations, where the same priority queue is used for different (TCP and UDP) Service
types, generally it is recommended to set shaper OFF. In case of some UDP traffic (e.g.
video) which is not that sensitive to latency and PDV, shaper can be enabled definitely
improving TCP session throughput.
Scheduler Usage
The weights of HSL WFP queues (1..15) are configured individually on each queue. To
recalculate this presentation to the % relative ratio between queues (as available on some
network devices), consider the following example.
The total sum of all weights is 100% of HSL Egress B/W minus the traffic via SP queues.
If HSL B/W is 10Mbps and traffic via SP queues is rate limited to 2Mbps, this leaves 8Mbps
for the WFQ queues. In Factory Default configuration the weights of the queues are
distributed as 1:1:2:2:4:8. The sum of weights is 1+1+2+2+4+8=18, which constitutes 100%
of 8Mbps, making the weights in % as: 5.6% : 5.6% : 11.1% : 11.1% : 22.2% : 44.4%.
9-20
. 10
10 Ethernet CFM
Configuration
IEEE 802.1ag Ethernet CFM (Connectivity Fault Management) is one of the
various functions provided by Ethernet OAM (Ethernet Operation,
Administration, and Maintenance). Ethernet OAM refers to a set of tools that
enable Metro Ethernet operators and service providers to more effectively
manage and troubleshoot the overall Ethernet infrastructure in order to minimize
downtime.
CFM allows service providers to individually manage customer service
instances. A customer service instance, or Ethernet Virtual Connection (EVC), is
the service that is sold to a customer and is designated by the Service-VLAN
tag. Hence, 802.1ag operates on a per-Service-VLAN (or per-EVC) basis. CFM
is an end-to-end per-service-instance (per VLAN) Ethernet layer OAM protocol
that is used for troubleshooting continuity of connection over HSLs and Ethernet
ports. It enables the service provider detect and identify EVC failure.
In order to use the mechanisms provided by CFM 802.ag, it is required to define
the CFM management infrastructure and to configure the ports that will function
as Maintenance Points within the administrative spaces comprising the
infrastructure.
Note: Each time a new service is added, it is required to configure the
corresponding ports within the infrastructure of the CFM.
This section provides general information on the CFM infrastructure elements
and describes how to configure the ML Actelis systems to support the CFM
functions. Refer to 802.3ah Ethernet OAM Tools (on page 14-88) for
information on using the OAM tools for end-to-end monitoring.
In This Chapter
About the CFM Infrastructure ...................................... 10-2
Ethernet CFM Configuration Procedure ...................... 10-7
10-1
Learning Ethernet Service path in the network through the link trace operation
Detecting the point of failure of Ethernet Service path through applying loopback
message
CFM Domain (on page 10-3) a part of Ethernet network (including ETH ports of an
NE as boundaries) where CFM protocol is valid.
Maintenance Intermediate Point (MIP) (on page 10-3) an ETH port on an NE which
is an internal part (not a boundary) of CFM domain. A MIP is capable to respond to CFM
operations.
Maintenance Association (MA) (on page 10-3) - Virtual LAN(s) (single or multiple
VIDs and NE or ETH ports are taking part) which are defined to take part in CFM
monitoring.
Maintenance End Point (MEP) (on page 10-4) a part of CFM MA, the principal CFM
element. MEP is specified by ETH port, VID and direction. An MEP
originates/terminates continuity check, loopback and link trace CFM operations.
Additional information about each CFM infrastructure element is provided in the following
sub-sections.
10-2
CFM Domains
A CFM maintenance domain is a management space defined by a set of ports that make up
the internal boundary of the domain. Each domain is owned and managed by a single entity
(single service provider or network operator).
Domains are labeled by their name and categorized by one of eight (0 to 7) maintenance
levels that usually correspond to their relative size (higher level for larger domains). Core
Network operator, for example, may have smaller domains - labeled 0 to 4, while service
providers (responsible for Peripheral Network - Access and Concentrator devices beyond the
Core Network) usually have larger domains - labeled 5 to 7.
Since each domain can only be managed by a single entity, domains cannot intersect or
overlap. Domains can touch and nest. When touching, the relay side (Switch) of an ML
device link may belong to one domain while the wired side (Port) can belong to another
domain. Nesting domains, enables a larger (i.e. service provider) domain to include smaller
domains (i.e. several service operators that have a contract with the same provider).
CFM MIP
A CFM Maintenance Intermediate Point (MIP) is a port which forwards CFM frames
identified by an equal or higher level and drops lower level, regardless of whether they are
received from the relay (Switch) or wire (Port) side.
MIP responds to CFM Loopback (unicast) and CFM Link Trace (multicast) messages of the
CFM Domain to which MIP belongs (identified by domain name and level in a message).
If MIPs are not configured on a device, CFM frames are forwarded on port according to
VLAN rules.
CFM MA
A CFM Maintenance Association (MA) is a list of VLANs (and their corresponding Ethernet
Ports) that take part in the CFM messaging procedure. Each CFM MA has its own
configurable attribute for Continuity Check Messaging transmit interval allowing the user
to determine CFM traffic load (affects ETH Service effective BW) per MA individually.
10-3
CFM MEP
A CFM Maintenance End Point (MEP) is a part of CFM MA. The MEP is specified by
particular PORT of VLAN (that belongs to MA), Direction, VID and COS to be sent in a
frame originated from MEP: CCM (periodically), Loopback (on demand) and Link Trace (on
demand).
MEP transparently forwards all CFM frames at a CFM domain of higher level, whether they
are received from the relay (Switch) or wire (Port) side.
10-4
CFM on ML NE
Note: CFM feature is unavailable if MetaASSIST View session with ML NE is open via Craft
port.
CFM Domain Instance Names/Level cannot be edited, DLT/ENT should be used instead.
All associated data should be deleted prior to Delete.
CFM MA
Up to 64 MA can be monitored using a one sec CCM interval (minimal). Other MEPs
can be monitored as part of a 10 sec interval.
CFM MEP
Up to 512 MEPs can be configured totally per NE (not per CFM Domain).
MEP is supported only on tagged/untagged ports (not stacked) in Down (towards wire)
direction only.
A maximal number of 5 Remote MEPs can be registered per MEP on each NE.
Discovered RMEPs are not aged (i.e. when 5 RMEP are registered by MEP, newly
discovered in network RMEP will be invisible.
CFM Operations
CFM MIB SNMP notifications are sent in a regular SNMPv2 over UDP over IP over
ETH way, a new transport SNMP over ETH, defined in IEEE802.1ag, is unsupported.
10-5
Limitations
10-6
ML50 specific: When configured as CPE, ML50 passes transparently CFM PDU
received on the port only if Stacked VLAN is configured on this port. In all other
configurations CFM PDU received on a port will be dropped if found as not matching to
ETH type configured by ED-BRIDGE on ML50.
ML600 specific: CFM Traffic of a layer lower then the lowest CFM Domain defined on
NE is not dropped (as required by the standard) but behaves as a regular service traffic
(dropped or passed as is or passed with VLAN encapsulation) depending on Port VLAN
membership where CFM traffic appears.
CFM Navigation tree- displays the configured CFM elements in a hierarchical topology.
Display Area - shows the window or dialog corresponding to the item selected in the
Connection tree.
10-7
Below is an example of the display invoked when the CFM item is selected. The Display
Area includes a table of the configured Domains discovered on the connected NEs (1 CO and
up to 32 CPE). Initially, the table is empty (before domains are configured on NEs).
(Once the required CFM configuration procedures are performed (according to the following
sections), selected service connections can be monitored through their associated (NE)
VLANs or ports.)
10-8
The buttons at the bottom of the pane provide Domain management options:
Add Domain - adds a new Domain (a procedure described in detail in the following
steps)
Edit Domain - used to modify the NE and the MIPs assigned to the selected domain
2. In the displayed pane, click Add Domain. The Add CFM Domain dialog appears.
Note: To remove a domain from the list, select the domain to be removed and click the
Delete Domain button.
10-9
3. Configure the CFM Domain name - in the Name field, type the name assigned to the
domain.
4. Assign the domain maintenance level - in the Level field, assign the domain a level
corresponding to its hierarchical position (size) relative to other domains in the network.
Range: 0 to 7, where higher numbers should represent larger domains. (Operator, for
example, may have smaller domains - labeled 0 to 4, while service providers usually have
larger domains - labeled 5 to 7.)
ML devices currently allow up to four different domains sizes to be used. Domains with
the same (lower - i.e. Level 2) level can be nested in a single (higher level - i.e. 4) domain
and monitored as a group. This can be used by service providers to monitor a number of
smaller operators under their contract.
5. Select the NEs participating from the Available NEs list.
Note: To select an NE from the list, select the item and click the > (right arrow).
6. Click OK. The domain will be listed under CFM in the sCFM Navigation tree.
10-10
2. In the MIPs pane area, click Edit MIPs. The Edit MIPs For CFM Domain dialog
appears.
10-11
3. Choose an NE from the Participating NEs list. The corresponding available ports and
configured MIPs appear in the boxes below.
4. To define the MIPs within the domain:
From the list of ports (under Ports for ML-XXX List), select the Port to be assigned
as MIP in the domain and click the > (right arrow) button. The selected port is listed
under MIPs of NEs in Domain List.
Note: To remove an MIP from the list, select the item and click the < (left arrow).
Repeat for additional MIPs to be added to the list from the same NE. Select a new
NE to define MIPs from another NE.
5. Click OK.
10-12
2. In the pane Associated MAs area, click the Add MA button. The CFM MA dialog
appears.
10-13
3. In the Name field, enter a recognizable CFM MA name. The MA name is a VLAN
number that should represent the group of services (VLANs).
4. Assign the NEs by selecting an NE from the Available NEs list and clicking the > (right
arrow) button. The NE will be displayed under the Participating NEs list.
Note: To remove an NE from the Participating NEs list, select the NE and click the <
(left-arrow) button.
5. Select the CCM Interval (Continuity Check Interval) from the drop-down list. CCM is
multicast heartbeat messages exchanged periodically between MEPs that allow MEPs to
discover other MEPs within a domain and allow MIPs to discover MEPs.
Options: 1 second, 10 seconds, 1 minute, 10 minutes (Default=1 minute).
Choose the CCM Interval according to the following criteria:
A lower interval takes up more bandwidth resources on one hand and reduces
monitoring feedback on the other. Choose a value that will not overload your band
while providing the required monitoring.
Up to 64 MA can be configured with 1 sec interval, the remaining MAs (up to 256
MAs per domain) can be configured with 10 or 60 sec intervals.
6. Click OK. The CFM MA will be displayed under the applicable Domain in the CFM
Navigation tree.
10-14
Defining MEPs
Maintenance End Points (MEPs) define the boundaries of the corresponding MA. MEPs are
specific ports interfaces located on the wired side of the domain. Each MEP is identified by
its NE, VLAN and, Port, direction and assigned attributes. Each MEP is configured by
defining it's boundaries. (The MEP CCM messages can be configured as well).
Note: Up to 16 VLANs and up to 512 MEP IDs can be configured per Maintenance
Association.
After configuring a MEP, it is added to the CFM navigation tree. Selecting the item invokes a
graphical display showing the MEP connections and providing access to additional tabs
showing MEP parameters. MEPs cannot only be defined on HSLs of ML devices defined as
CPE.
To add a MEP to a defined MA
1. From the Main window Connectivity tab, under CFM, select the relevant Domain Name,
and choose the relevant MA. The corresponding pane is invoked.
Associated MEPs - shows the list of associated MEPs and their details, and provides
MEP management options through the buttons at the bottom of the pane:
10-15
Add MEP - adds a new MEP to the domain (a procedure described in the
following steps)
2. In the Maintenance Association pane, Associated MEPs area, click Add MEPs. The
Add MEP dialog appears.
Select the relevant NE from the NEs drop-down list. The list of VLANs configured
to the selected NE will be available in the Primary VID drop-down list.
Select the relevant VLAN from the Primary VID drop-down list. The ports
associated with the selected VLAN will be listed in the Port drop-down list.
Select the port (on the wired - external side) to be associated with the defined MEP.
The Direction will be displayed.
5. Select the Lowest Priority Alarms - the lowest priority level that will be assigned to a
message processed by this MEP. Default: No defects
6. To enable Continuity Check Messages for the MEP:
10-16
. 11
11 Security
Management
This chapter describes the options available for managing security on an ML
device.
In This Chapter
Managing User Accounts ............................................ 11-2
Password Control ........................................................ 11-7
Locking Out Users..................................................... 11-10
Managing Sessions ................................................... 11-12
RADIUS..................................................................... 11-15
IP Access Control...................................................... 11-21
SSH - Secure Shell ................................................... 11-25
11-1
Security Management
All User Account management operations are performed via the User (accounts) (on page
11-3) pane.
When managing the user accounts list:
11-2
Security Management
Configuration area - summarizes the global password and login characteristics and
behavior and provides access to the corresponding configuration options via the
Configure button.
User Accounts area - shows the default users (admin, read, write) and any other defined
users along with configuration and status of each password.
11-3
Security Management
The buttons at the bottom of the pane provide access to various operations as described
below.
Table 31: User Accounts pane operations
Button
Description
Displays the users that are currently logged onto this NE and
enables an Admin level user to disconnect any user.
Lock Users
Locks out a selected user. This does not delete the user
account.
Logout User
Add User
Edit User
Delete User
Password
Privilege Rights
read
read
write
write
admin
admin
11-4
Security Management
Note: For group operations, open the Add User dialog box via the menu bar: Group
Operations, Users, Add.
3. Add an account as follows:
In the Access Privilege box, select the access privilege right (R-read, RW-write,
RWA-admin).
4. You may define the account to timeout after a defined time period. To define timeout, in
the Timeout list box, select the timeout in minutes. Range = 5 to 99 minutes.
5. To set no timeout, select the Set No Timeout check box. The Timeout box is grayed out.
6. Click OK. The Add User dialog box closes and the user is added to the list.
11-5
Security Management
3. To modify the password, clear the Do not change password check box.
4. Modify the details as necessary (see steps 3 to 8 in Adding a User Account (on page 115)).
5. Click OK. The Edit User dialog box closes.
11-6
Password Control
Security Management
Password Control
The general characteristics (complexity, etc.) of a password are defined on a system (global)
level. In addition, each of the users can change their own password in an ongoing session.
Only users with admin privileges can configure password control parameters.
The ML device Date/Time changes affect the remaining Password Expiration Time and
Time Between Password Changes. Each user accounts is updated according to the
following:
Date and/or Time are set forward before original expiration time: the times are
reduced accordingly so expiration would take place at the original date and hour.
Date and/or Time are set forward beyond original expiration time: the expiration
would take place immediately.
Date is set backward: the times are reset to the start (with time 00:00) so expiration
would take place as if the password was created today at 00:00.
Time is set backward (no date change): the times are unchanged, expiration would
take place after the remaining time.
11-7
Security Management
Password Control
Note: When Password Complexity is enabled, you can continue using your original noncomplex password. However, it is recommended to change your own password to a
complex one.
4. Set the Password Expires - this is the duration for each valid password before it expires.
By default, password expiration is disabled.
The user session is discontinued immediately after expiration of the password from the
attached system. MetaASSIST View and the ML device allows the user to log in with the
expired password but immediately displays a dialog box requiring the user to define a
new password before running the session. Expiration can be enabled/disabled by the
System Administrator only.
It is recommended to immediately change the password the first time after new password
setting by the administrator.
Note: Password expiration global change is not applied immediately on each user
account, but upon next change of the password, except when password expiration is
disabled/enabled (changed from/to No expiration).
About password history: When password complexity is enabled, then six previously
used passwords cannot be reused. This implies that after the expiration period has passed
and the user needs to enter a new password, the user cannot use the same password or
any earlier password (up to 6 passwords) as a new password. Password History size (6) is
not configurable. Password History control can be disable together with Password
complexity.
5. In the Password Change Allowed box, type the minimum amount of time in which a
password cannot be changed (0 - always allowed).
Note: When configuring the password, MetaASSIST View verifies that the password
Change Not Allowed value is smaller than the password Expires After value.
11-8
Password Control
Security Management
2.
3.
4.
5.
11-9
Security Management
The ML device Date/Time change does not affect actual count of Failed Login Attempts
and account Locking Period.
Note: The features described below are applied to all user accounts.
Only users with admin privileges can configure lockout control parameters as follows.
11-10
Security Management
Note: For group operations, open the Configure User Settings dialog box via the menu
bar: Group Operations, Users, Configure.
Auto-Lock After: The system can automatically lock users after a certain amount of
failed attempts. Locked users cannot log in to the system via MetaASSIST View, a
TL1 session or the support page for a configured amount of time. Both the number of
allowed incorrect attempts and the time for account locking are configurable as a
system-wide parameter controlled by the administrator only.
Auto-Lock for: By default, the lock out time period is 0 (no automatic unlock). In
this case, only a user with admin privileges can unlock the account before it can be
used again.
11-11
Security Management
Managing Sessions
Managing Sessions
Each of the users can view his own session information including password expiration and
change status in the Session.
In addition, an Admin level user can view all the currently connected sessions and disconnect
any session.
11-12
Managing Sessions
Security Management
Note: If more than one session is opened from the same IP, each additional session is
indicated by a letter. The example below shows three sessions opened from the same IP:
the first session is not marked by a letter, while each of the other sessions is assigned a
letter (A, B, etc.).
11-13
Security Management
Managing Sessions
Additional operations
Click..
To do this
Logout User
Refresh
Close
11-14
RADIUS
Security Management
RADIUS
Remote Authentication Dial-In User Service (RADIUS) is a distributed client/server system
that centralizes control of device access. If RADIUS is used, all user profiles and access
limits to the ML devices can be managed via the RADIUS server. The ML devices serve as
clients which send authentication requests to a central RADIUS server.
It is recommended to use RADIUS in the following network environments:
Networks with dynamic group of users (no need to set changes in the group on all NEs
but only in one location)
Authentication only (RFC 2865). All account messages (supported in RFC2866) are
discarded by the system.
Configure the ML NE (as a Radius client) with the RADIUS server address and with the
relevant communication parameters. See Configuring RADIUS on ML (on page 11-16).
Configure the Radius Server to respond with a Message (on page 11-18) which provide
Service-Type (on page 11-20) (Parameter ID #6) with values 1, 7 or 6 - for read, write
and admin user accordingly.
checking for the UserID privileges (read only, read-write, or full admin access)
idle session timeout (to close the session between ML and TL1 (MAV) agent
automatically if no activities detected).
11-15
Security Management
RADIUS
With the introduction of the RADIUS Client on ML, there are three ways to authenticate user
account during TL1 login to ML:
Using Local ML device user accounts records only (default configuration of ML device)
- In this case queries to Radius Server for user account authentication are not issued.
If the Server did not answer during defined period of time (Timeout Period x Number
of Retries), then Backup Server is queried (if configured).
If the Backup Server did not answer during the defined period of time (Timeout
Period x Number of Retries), then local ML device user account records are checked.
If the Server replies with reject (no user account found), neither Backup Server nor
Local ML device user account records are queried, and Login is denied.
Each new attempt of login always passes through the Server-Backup Server-Local
flow, which means that if the Primary Server is down, it takes (Timeout Period x
Number of Retries) time to access the Backup Server each time, where improper
configuration queries to the RADIUS may seriously slow down the login of TL1based management applications (MetaASSIST View, MetaASSIST EMS, etc.).
Configuring RADIUS on ML
To configure Radius on the ML device
1. From the Network Element tree, under Management Access, choose Radius. The
Radius client pane appears.
2. To define the Radius Server click the Configure button. The Configure Radius Client
pane is invoked.
11-16
RADIUS
Security Management
Under Primary Server, in the Server IP Address field - enter the IP the Radius
application server (0.0.0.0, by default).
Server Port the authentication destination port that is configured on the RADIUS
server. Options: 1645, 1812. (Default = port 1812)
Timeout Period Number of seconds the ML waits for a reply before retransmitting
the request to the Radius server (Default = 60 sec).
Dead Time Maximum time a client should wait before attempting to contact the
server again after the "Timeout period x Number of Retries" expired (default = 60
sec).
Secret A key string shared between the ML and a RADIUS server. The secret must
match the encryption key used on the RADIUS server and CANNOT be empty.
Note: The Secret is configured once per ML, and thus is used the same for both Primary
and Secondary Server (assuming the Secondary Server usually is a full replica of Primary
Server, with another IP address only).
4. Define the Method of access to the ML device:
11-17
Security Management
RADIUS
Local (ML factory default) - access is verified according to the user information
stored in the ML device.
Radius and Local - the Radius server (including backup Server) and then locally
stored on ML user information is queried for authentication.
Radius - only the Radius can authenticate access. If the Radius is not available, then
access the ML is not allowed.
NOTE: If a backup server is not defined (0.0.0.0 by default) query is skipped. If both
Servers are configured with the same IP, queries will be sent twice (if no reply from
Primary Server).
6. Click OK.
Authentication only (RFC 2865). All account messages (supported in RFC2866) are
discarded by the system.
11-18
RADIUS
Security Management
Name
Length
Description
Message(s)
User-Name
3-63 chars
Access-Request/
Access-Accept
UserPassword
16-128
chars
Access-Request
NAS-IPAddress
Access-Request
NAS-Port
Access-Request
Name
61
NAS-PortType
Length
Description
Message(s)
Service-Type
Access-Request/
Access-Accept
18
ReplyMessage
Access-Accept /
Access-Reject
28
Idle-Timeout
Access-Accept
11-19
Security Management
RADIUS
Type
Description
Notes.
Login
ML Users with
Read access
privilege.
Administrative
ML Users with
Admin access
privilege.
NAS Prompt
ML Users with
Write access
privilege.
11-20
IP Access Control
Security Management
IP Access Control
System Administrators with admin privilege can view and manage a list of clients, which are
allowed to access the ML device through the following specified protocols:
SNMP
Telnet
HTTP
Up to 100 individual client IP addresses can be configured, each with its own list of permitted
protocols in the Access Control pane. Access Control feature can be enabled or disabled
(default).
When disabled - all clients can connect to the ML device using any of the above supported
protocols.
When enabled - only clients specified in the Access Control List can connect to the ML
device using the above supported protocols. Incoming access attempts from other IP
addresses are denied. In addition, ongoing sessions from client IP addresses not specified in
the Access Control List or through non-permitted protocols specified in the list are aborted.
Note: When enabled, ML device allows to access the system through craft port from any PC.
At least one Client with any permitted access protocol must be configured before Access
Control can be enabled.
In addition, the user cannot delete the last entry in the list while the Access Control is
enabled. The Configure button is disabled if the Access Control List does not contain any
active entry (this prevents the possibility of IP access locking).
Note: If no client with permitted Telnet access protocol is defined then ML device cannot be
configured and monitored remotely via Telnet only via the craft port.
When the IP Access Control is enabled then only allowed Clients can access the node using
the protocols that were defined for it as seen in the following figure. As shown in the figure,
if the defined protocol is not defined in the IP Access Control List for client with IP C then a
time out is sent and no connection is established.
11-21
Security Management
IP Access Control
Add a client IP address to the IP Access Control List with a permitted connection
protocol;
11-22
IP Access Control
Security Management
Note: For group operations, open the Add Client to IP Access Control List dialog box
via the menu bar: Group Operations, ACL Host, Add.
2. In the IP Address box, type in the IP address.
3. In the Protocols check boxes, select permitted connection protocols.
4. Click OK. The Add Client to Access Control List dialog box closes and the IP is added
to the list.
Note: For group operations, open the Configure IP Access Control List dialog box via
the menu bar: Group Operations, ACL Host, Configure.
1. To enable the Access Control state, select the Enabled check box.
2. To disable the Access Control state, clear the Enabled check box.
3. Click OK. The Configure IP Access Control dialog box closes.
Note: All open management sessions running on IP addresses that are not listed are
disconnected when IP Access Control is enabled.
11-23
Security Management
IP Access Control
In the IP Access Control List, select an IP address to edit from the table.
Click Edit. The Edit Client <IP Address> of IP Access Control dialog appears.
In the Protocols check boxes, select permitted connection protocols.
Click OK. The Edit Client <IP Address> of IP Access Control dialog box closes.
Deleting a Client
You can delete a client from the IP Access Control list. For each deleted client, all ongoing
sessions from that client (for all supported protocols) are aborted, see the following table - if
IP Access Control is enabled.
Note: The last client IP address cannot be deleted while IP Access Control is enabled.
SNMP
SNMP
HTTP
HTTP
Telnet
TL1
TL1
11-24
Security Management
SSH is a protocol that provides authentication, encryption and data integrity to secure
network communication between management host and the ML device as follows:
Authentication - ML device supports DSA authentication keys 512, 768, or 1024 bits
long.
11-25
Security Management
For first time SSH communication operation you should perform as shown in the following
table:
Table 36: Task summaryfirst time SSH communication
Generate key pair on your Management Host using MetaASSIST View or any third party
SSH package. Optional - use the Passphrase. See Generating SSH Client Key (on page
11-27).
Add the generated Public key of the Management host(s) to the SSH Server authentication
list of the ML device. See SSH Server Overview (on page 11-27) to access the function
and Authenticated SSH Client Keys Control (on page 11-33) for detailed description.
Regenerate the key pair (optional) or view the generated (by default) SSH Server Public
key on the ML device. See SSH Server Overview (on page 11-27) to access the function
and Generating SSH Server Key (on page 11-29) for detailed description.
Enable Authentication control on the Server. See SSH Server Overview (on page 11-27)
to access the function and Enable Authentication Control on Server (on page 11-36) for
detailed description.
During log in to the ML device using SSH option (on initial connection), the system
prompts you to add (Accept Key <Signature> for Host <IP Address>?) ML device Public
key as a trusted host on your Management Host. If key is trusted (check with network
administrator), accept the key.
11-26
Security Management
2. In the File Name box, type the file name or click the Browse button to indicate a location
where the file will be created (optional).
3. To define a passphrase:
4. To select key size for additional protection, from the Key Length list box, select the
number of bits (512, 768 or 1024).
5. To use the generated key for next login, select the Save For Next Login check box.
6. Click OK.
11-27
Security Management
View Server public key parameters (Signature of Public Key, Authentication Key Type,
Key Length and Key Generation status);
Manage Authenticated Clients Public Key storage (add, replace, delete Authenticated
Client Key);
11-28
Security Management
2. From the Key Type list box, select the key type (currently only keys of type DSA are
supported and the selection box is disabled).
3. From the Key Length list box, select the key length.
4. Click OK. A warning opens New server key will be generated. Do you want to
continue. Click Yes. A progress bar appears and the Key Generation Status is In
Progress.
11-29
Security Management
11-30
Security Management
11-31
Security Management
11-32
Security Management
11-33
Security Management
Note: For group operations, open the Add Client Key dialog box via the menu bar:
Group Operations, SSH, Add.
2. In the Key Name box, type the key name.
11-34
Security Management
3. In the Client Key box, type the full public client key or click the From File button to
locate a file containing the client public key.
4. Click OK. The Add Client Key dialog box closes and the Client Key is added to the list
and will be written into the server pubic key database.
To replace an authenticated Client Key:
1. In the Authenticated Client Keys pane area a list of all authenticated client keys is
displayed. From the list, select a Client Key to replace.
2. On the bottom of the SSH review pane, click Replace Key. The Replace Client Key
dialog appears.
11-35
Security Management
Note: For group operations, open the Configure SSH Server dialog box via the menu
bar: Group Operations, SSH, Configure.
2. To enable SSH Client Key Authentication, select the Enabled check box.
3. Click OK.
11-36
. 12
12 Administration
This chapter describes how to perform various administration operations such as
configuration backup and restore, updating software on ML systems and on
XR239 Repeaters, log file management, updating MetaASSIST View software
and more.
These type of operations can be performed via the MetaASSIST View or, if the
available computer is not running MetaASSIST, some of the operations can be
performed by opening a session to the ML device from any standard Web
browser. Accordingly, this chapter is divided according to MetaASSIST View
operations and Web Browser operations.
In This Chapter
Using MetaASSIST View............................................. 12-2
Using Web Browser................................................... 12-29
12-1
Administration
File transfer is to be performed only via non-serial interface; connection cannot be via the
craft port.
IP attributes must be configured on the ML600-CO unit, where the CPE unit can be an
IP-less device.
If FTP/TFTP is used, the FTP or TFTP server must be installed and correctly configured
on the host computer.
Note: Timeout in the TFTP server must be configured to greater than 30 seconds.
12-2
Administration
2. Open Configuration Backup. The Configuration Backup pane opens in the work area.
3. On the Host, run an FTP/TFTP server (the FTP/TFTP directory must point to the
configuration backup directory). Skip this step for HTTP.
4. Click Save Config. The Save Configuration dialog appears.
12-3
Administration
4. Click Download New Config. The Download New Configuration dialog appears.
12-4
Administration
Full overwrite of current configuration - apply full backup file, including unique
management identification of NE and unique per deployment HSL Calibration setting
and Calibration results. This type of activation is suitable for replacing a faulty ML
device.
5. Click OK.
12-5
Administration
Note: This procedure can also be performed via a web browser. For more details see Using
Web Browser (on page 12-29).
COMMAND log includes all ML device TL1 commands and responses as configured by
the detail level, see Configuring the COMMAND log file (on page 12-6). The
COMMAND log assists in locating possible causes of the faults in the ML device.
AUDIT log includes management access events and SNTP synchronization events, see
Configuring the AUDIT log file (on page 12-7). The ML device does not log any
broadcast session attempts and attempts on permanently closed ports.
Each successful attempt is logged with the following information: Timestamp of event, IP
source/IP destination addresses and protocol type.
For rejected attempts the reason for rejection is also provided: rejected by Access
Control, rejected by account authentication (SNMP, TL1 or HTTP).
12-6
Administration
12-7
Administration
HTTP to copy the file to your computer. File Name and Host Directory are required;
TFTP to copy the file to a Host computer. Host IP Address and Host Directory are
required;
FTP to copy the file to a Host computer. Host IP address, Host Directory, User Name
and Password are required of user account on FTP server.
12-8
Administration
INFO log - registers selected internal software operations, which assist engineers in the
Customer Support department in locating system software problems.
BLACKBOX log - registers critical system events. Important for system troubleshooting.
The log files can be managed (disabled, saved, etc.) via the Support Log Files pane.
To invoke the Support Log Files pane
From the Tools Menu, click View Support Logs. The Support Log Files dialog appears. The
pane summarizes the types of enabled log files and provides access to log file management
options via buttons at the bottom of the pane.
The buttons functions are:
Save - used to save the selected log file in HTTP, FTP or TFTP format.
12-9
Administration
Init Log - clears the selected log file (after a verification message).
12-10
Administration
FTP to copy the file to a Host computer. Host IP address and Host Directory, User
Name and Password of user account on FTP server are required.
TFTP to copy the file to a Host computer. Host IP Address and Host Directory are
required;
12-11
Administration
ML Software Control
Software upgrade can be performed by using MetaASSIST View.
Note: The SW upgrade procedure can also be performed via a web browser. For more
details see Using Web Browser (on page 12-29).
SW Upgrade (not Downgrade) can also use the Auto Upgrade process which performs
Downloading, Activating and Committing SW automatically.
Note: Any restart aborts SW Download and SW Activate actions but does not affect Cancel
and Commit actions (always completed). Successfully downloaded SW is not affected
(removed) by any restart.
ML SW Release Pane
The ML SW Release Pane provides information on the SW in the currently accessed system,
status of SW upgrade and various upgrade related options.
To open the ML SW Release pane
In the Network Element tree, open System Administration and select SW Release. The SW
Release pane is invoked:
12-12
Administration
The SW Upgrade/Downgrade area contains the buttons used to perform the procedures:
Download New SW - see Downloading the Software from the Host (on page 12-14).
Activate the New SW - see Activating the New Software (on page 12-15).
File transfer is to be performed only via non-serial interface; connection cannot be via the
craft port.
IP attributes must be configured on the ML-CO unit, where the ML-CPE unit can be an
IP-less device.
If FTP/TFTP is used, the FTP or TFTP server must be installed and correctly configured
on the host computer.
Note: Timeout in the TFTP server must be configured to greater than 30 seconds.
12-13
Administration
HTTP;
12-14
Administration
10. Click Download. A progress bar is displayed in the SW Release pane. Please wait until
download is completed (the download time depends on the link speed and may take a few
minutes (for an Ethernet MGMT link).
Note: If the Download New SW button is disabled it is possible that a previous SW Upgrade
is still in progress. Check the SW Upgrade procedure status. Complete the process by either
clicking the Commit SW (recommended) button or the Revert to Backup button. If the Commit
SW button is disabled you can click either the Delete New SW (recommended) button or the
Activate New SW button.
Check that all other configuration data (VLAN, Bridge, Ethernet) were successfully
preserved during SW upgrade.
12-15
Administration
12-16
Administration
The centralized management model requires a single IP address for management access
over all NEs in a particular topology and therefore reports all alarm conditions under the
same System ID, but using specific Access Identifiers (AID).
Independent Management Models:
The independent management model (R5.00 and higher) serves any physical topologies
using any ML device, see Physical Topologies.
The independent management model requires an IP address for each NE and provides
notifications of alarms along with the corresponding System ID. It is easily integrated
with standard NMS solutions (TL1 and SNMP based), supporting apparent topology
presentation and clear fault isolation.
In case of P2MP SW upgrade from centralized (R4.00) to independent model (R5.00 and
higher), the ML50 CPE NE (the only CPE available in R4.00) upgrade is performed as
follows:
o
After SW upgrade, ML50 CPE NEs can remain un-managed (without IP address
allocated on it). R5.0a (the latest SW of ML50 models) allows full configuration and
local (via MetaASSIST View) monitoring of IP-less CPE NE with the following
limitations:
o
12-17
Administration
Procedure description
Upgrade Procedure
R4.x
R3.x
12-18
Administration
Upgrade Procedure
12-19
Administration
12-20
Administration
12-21
Administration
Using the Repeater SW Control pane, which provides both monitoring and control
capabilities.
All SW control operations (download new SW, apply new SW, etc.) on repeaters are
operated by choosing the MLP modem(s) of a selected HSL(s) on the CO NE, but are
simultaneously applied on all of the repeaters participating in the repeated line (span). There
is no ability to apply operations on single selected repeater.
Note: Old Repeaters (part number 501R2008612D) do not support SW upgrade; these should
be replaced by newer repeaters to enable repeater SW upgrade.
Repeaters SW should be downloaded to the ML NE prior to being distributed to the
repeaters, using the Repeater SW Release pane, as described below.
12-22
Administration
2. The Available SW Release area provides information on the Repeater software available
in the ML:
SW Issue - SW build
Note: The file names of the Repeater SW are as follows: *.bin.a when stored on the ML,
and *mft when selected for download from the PC.
3. The File Transfer Info area provides information on when the last SW download was
performed:
SW Status
12-23
Administration
12-24
Administration
2. Click Delete SW. The Repeater SW file will be deleted from the ML.
Activating the software to verify correct operation of the span - can revert to previous
software.
Committing the software to the Repeaters - when executed, the Repeaters permanently
operate with the new software - this operation cannot be reverted.
12-25
Administration
Display options (on top) allows to select the HSL to be upgraded (all or some of the
spans) and the parameters to be displayed.
Display area used to choose the spans to be upgraded and display relevant
information.
Action Buttons - used to start and go through the various steps in the upgrade
procedure.
2. In the HSLs drop-down menu, select the HSL whose spans are to be upgraded: select
either one HSL or ALL to display spans relevant to all the HSLs for this ML (in case of
multiple HSLs, the download operation may take longer).
12-26
Administration
Each span in the selected HSL(s) will be displayed as a row with MLP information and
HOP information for each Repeater in the span. The MLP information includes the DUO
and the synchronization status of the span. The Hop information includes the SW
upgrade status and phase, in addition to the versions.
3. To select the information to be displayed, choose from the Show the following
parameters field:
All displays all the information of every Hop in the span (Serial number, SW
upgrade status, etc.)
Note: Use the horizontal scroll bar to display additional Hops and the vertical scroll-bar
to display additional spans.
4. Select the spans to be upgraded by selecting ONE of the MLPs comprising the span.
When you select an MLP port, its DUO is automatically selected as well. If you select
both the MLP and it's DUO, you will get an error message indicating that the MLP has
already been selected.
5. Download the SW from the ML to the repeaters in the selected spans by clicking the
Download New SW button and following the prompts. The process may take up to two
hours. You may use the Cancel New SW button to stop the download procedure at any
time. During this time traffic is not affected.
6. If you would like to cancel the whole procedure, click the Stop Download button.
Note: If, for some reason, one or more of the repeaters along the span can not be upgraded,
the procedure will be stopped and an error message will appear.
12-27
Administration
Restarting the ML NE
The following restart options are available on the ML device:
Restart: Restarts the system and preserves configuration parameters. Users with admin
or write privileges can perform this restart.
Restart with Factory Setup: Restarts the system with initial system factory setup
parameters without preserving any management or service configurations. Only users
with admin privilege rights can perform this restart.
System restart can be performed locally by turning power off and then on. All configuration
parameters are preserved in this case.
System restart can be performed using the Reset button on the rear panel.
System restart can be performed remotely using MetaASSIST View as follows:
For the ML device, which is directly accessible via craft port or via Management LAN by
own IP address, use System pane accessible in the Network Element tree. Dialog box is
opened.
For logged in system, use System pane accessible in the Network Element tree.
Dialog box is opened.
For not logged in system (also without IP connectivity defined) use NEs Linked via
HSL pane accessible in the Network Element tree. Dialog box is opened.
12-28
Administration
Non-ML SW Control
Operations available on the Page are protected by TL1 User Account (User and Password)
and are allowed for Admin or Write access privilege Users only.
12-29
Administration
Tip: To go directly to the TL1 Documentation, enter the above URL without the word support.
The following figure shows the layout of the ML device Support Page:
12-30
Administration
The Support page Download and Upload/View areas are described below:
12-31
Administration
3.
4.
5.
6.
12-32
Administration
2. Select ML Setup.
3. Type in the path or use the Browse button to specify the Configuration file that was
previously saved at a backup location in your PC.
4. Click the Download to ML button.
5. After the file was successfully downloaded to the ML device it can be restored as
explained in Restore ML Device Backup File (on page 12-33).
The Configuration setup file is checked for validity and then downloaded to the system.
If the Configuration file is invalid or does not have the same version as the currently
running software, an error message is displayed.
This procedure requires opening a Telnet session. Log in to the system and enter the
following TL1 command:
init-sys:::::restore;
The ML device restarts and then operates with the new configuration.
To apply provisioning data only (without TID, IP address, Craft port rate and
Calibration data):
12-33
Administration
Retrieving Logs
To access the logs (Command and System Info):
1. In the Actelis System Support page, under View / Upload file from ML, type the
Username and Password.
2. Select a log option by checking its bullet.
3. Click the Upload from ML button. The relevant log will be displayed.
For more details about the available logs and their content, see Support Log File
Management (on page 12-9).
Retrieving Files
The MetaASSIST view running files and an OLH version of the system user manual are
stored on every ML system.
These files can be retrieved and saved on your PC or other storage location and later be
downloaded to other devices of the same model.
To retrieve a file
1. In the Actelis System Support page, under View / Upload file from ML, type the
Username and Password.
2. Select a file by checking its bullet. The available files are:
MAV Unix SW - a MetaASSIST view version for UNIX
MAV Windows SW - a MetaASSIST view version for Windows
12-34
Administration
ML Software Control
The process consists of:
1. Downloading the software from the Host
2. Activating the new software
3. Committing the software
The first step can be performed via the web browser from the support page.
For detailed explanations about this procedure and how to perform it via the MetaASSIST
view, see Updating Software Versions (on page 12-12).
12-35
Administration
2. Select ML SW.
3. Type in the path or use the Browse button to specify the SW upgrade file location in the
local PC or LAN.
Note: The file structure of the software consists of the NE type, release number and build
number followed by the extension mft.
For example, the file ml600-r610-108.mft refers to ML600, Release 6.10 and build 108.
4. Click the Download to ML button. The upgrade software is downloaded to the ML
device.
Log in to the ML device and enter the following TL1 command to activate the ML
device:
invk-sw;
The ML device reboots and the upgrade software status changes from pending to
running.
12-36
Administration
3. Type in the path or use the Browse button to specify the SW upgrade file location in the
local PC or LAN.
To complete the Repeaters SW update procedure, see Updating new SW onto
Repeaters (on page 12-25).
Click the TL1 Commands Reference hypertext link. The TL1 Documentation page
opens.
The TL1 document explains the syntax for the TL1 commands used in the Actelis ML
customer interface. It also defines the Access Identifiers (AIDs) for the Managed Objects in
these commands, as well as the required parameters and associated error codes.
12-37
. 13
13 Monitoring
MetaASSIST View is used to monitor a directly connected ML device and any
hosted ML systems. It provides a range of real-time monitoring options that
allow network administrators to follow the health and activity of Actelis network
elements. These tools include:
- Configurable, hierarchical, colored fault indicators for Network Elements and
(NEs) and NE components
- Summary displays of alarms according to various factors
- Glance views of status and configuration information relevant to the selected
NE
- Graphical connectivity trace tools
- Graphical traffic monitoring and analysis tools
This chapter describes the various monitoring tools and how they are used to
view faults and information for the overall system and for system elements such
as Ethernet Bridge, Equipment, Ethernet Services, etc. (Note that ML600 can
also be monitored through the MetaASSIST EMS application. For more
information, see the MetaASSIST EMS User Manual.)
In This Chapter
Monitoring and Managing Alarms................................ 13-2
System Status Monitoring ......................................... 13-11
Ethernet Bridge Monitoring........................................ 13-19
Ethernet Service Monitoring ...................................... 13-29
Performance Monitoring ............................................ 13-38
Monitoring Bandwidth Parameters ............................ 13-73
Service Connectivity Monitoring ................................ 13-81
Ethernet Topology Monitoring ................................... 13-83
DSx1 and Clock Monitoring Tools ............................. 13-85
CFM MEP Monitoring Tools ...................................... 13-90
13-1
Monitoring
13-2
Currently active alarms for a connected NE and its hosted NEs (if the connected NE is a
CO) - displayed at the bottom of the window area.
Active alarm per NE item (i.e. HSL, Modem, etc.) - in the Network Element tree. This
enables identifying the general source of the alarm.
All (active and history) alarms for a selected NE from the Navigation tree - via the
Alarms pane of the selected NE (Alarms Pane View (on page 13-4)).
Monitoring
Note: Clicking on an active alarm links to the NE item and invokes the corresponding pane.
The alarms' levels and notification can be customized by the user per Network Element. For
example, a critical alarm can be configured to be sent as a user selected sound (Configuring
Fault Notification Sound Effects (on page 13-8)). In addition, the fault levels for each NE
component can be modified from the corresponding glance (summary) pane and customized
to the operators requirements (About Alarm Severity and Conditions (on page 13-7)).
When performing maintenance on a system, alarms can be disabled so fault messages are not
unnecessarily sent to the control center (Disabling Alarms for Maintenance (on page 1310)).
13-3
Monitoring
Current alarms - shows active alarms for the NE selected in the Navigation tree
Configure CO Env. Alarms and Alarms Cut Off button - provides access to
environmental alarms configuration options for the NE and Alarms Cut Off option
Alarm History - shows all alarms generated for the selected NE, including those that are
no longer active. (The display is limited to the last 512 alarms).
Note: To reset the Alarm History (Admin privileges only), click the Clear History button in the
Alarm History area.
13-4
Monitoring
Meaning
13-5
Monitoring
The following table provides brief descriptions of the fields. For detailed information on
troubleshooting procedures for the alarms, refer to Alarmed Conditions Tables (on page 1410).
Table 39: Parameter Description
Field
Description
Time/TID
The field varies according to the table summary. Provides more information
such as source NE or time at which alarm was generated.
Severity
The Notification code of the alarm or message and the MTTR (Mean Time To
Repair) requirement according to GR-474-CORE.
The severity levels for a Network Element item can be modified according to
instructions in Modifying Alarm Severity (on page 13-9).
For more details on severity levels, refer to About Alarm Severity and
Conditions (on page 13-7).
Condition that caused the alarm or message. All conditions are detailed in
Alarmed Conditions Tables (on page 14-10).
Condition Type
AID
The Access Identifier of the component (entity) involved with the alarm or
message.
SA/NSA
The effect that reported event has on system operations. Possible values are:
SA means event is Service Affecting (i.e., it caused part or all traffic to be
dropped)
NSA means event is Not Service Affecting (e.g., redundant power input
failure).
Textual description of the event
Failure
Description
Location (Loc)
Direction (Dir)
13-6
Monitoring
MN
(Minor Alarm)
NA
(Not Alarmed)
NR
(Not Reported)
CL
(Cleared Alarm)
13-7
Monitoring
The sound files can be selected from a default list of files and played prior to activation. The
file list can be modified as necessary.
To configure sound effects:
1. On the Tools menu, select Sound Effects. The Sound Effects dialog appears.
2. To enable the audio file, select the Enable check box next to the appropriate alarm
severity.
3. From the Duration list box, select the time duration (1-10 seconds).
4. In the Audio File box, type the .WAV file location or locate it by clicking the Browse
button.
5. To listen to the audio file, in the dialog box, click the play button:
6. For additional alarm severities, repeat steps 2 to 6.
7. Click OK.
13-8
Monitoring
2. Every condition type is displayed along with preconfigured information describing the
condition and its default severity. See About Alarm Severity and Conditions (on page
13-7). The severity for any of the displayed conditions can be modified.
Note: To disable all alarms, check Maintenance - All Alarms Disabled. See Disabling
Alarms for Maintenance (on page 13-10).
3. Click OK to save changes.
13-9
Monitoring
Operating Alarms
MetaASSIST View allows you to disable alarm display for maintenance purposes. This
condition is indicated by the Maintenance wrench tool icon next to the relevant element in
the Navigation tree and in entities that report alarms. When Modem ports or Ethernet ports
are placed in Maintenance mode, service is interrupted on the port. A warning message
appears prior to performing this action.
After completing maintenance, make sure you enable the alarms.
Note: Users with write and admin privilege rights can disable alarms from panes using the
Configure Alarms button. Disabled entities cannot be placed in maintenance mode.
To disable alarms
1. In the Network Element tree, open the required entity. The entity detailed pane opens in
the work area.
2. From the work area (in Alarms and Conditions section), click Configure Alarms. The
Configure Alarms dialog appears.
3. Select the Maintenance - All Alarms Disabled check box.
4. Click OK. The Maintenance
icon appears.
Note: To enable alarms, clear the Maintenance - All Alarms Disabled check box.
13-10
Monitoring
13-11
Monitoring
The Monitored NE is displayed on the left hand side of the Network Element pane along with
the following detailed System information: System Name (TID), Model, SW Release,
Number of Enabled Modems and IP address. In addition there is a filter, allowing to display
linked NEs (All, Enabled, Disabled, Alarmed).
The linked via HSL NE is displayed by a NE-via-HSL-<ID> link. In addition, placing the
cursor on the NE displays a tool-tip with the following detailed information: System Name
(TID), Model, IP address, ETH BW available on the HSL and highest severity Alarm
condition (if occurs).
The NE-via-HSL-<ID> link behaves as follows:
Switches to the linked NE Network Element pane when HSL up and NE is logged in
Remains on Local NE and switches to NEs Linked via HSL pane when HSL up and NE
is not logged in
Remains on Local NE and switches to HSL-<ID> pane when HSL is operationally down
or disabled
System
The System pane displays, in glance view, system-wide features both configurable and not,
as follows:
13-12
Monitoring
In addition, the Last Reboot date and time are displayed in the System pane.
In models with SFP pluggable module, Auto-configuration feature is available and appears
on the System pane.
To access the System pane
In the Network Element tree, click System. The System pane opens in the work area.
13-13
Monitoring
ML600 View
The ML600 equipment can be monitored through the Modules pane that summarizes the
equipment plugged or configured in the device, and the Equipment module pane that
provides inventory details on each module.
Note: Models ML624 and higher support a pluggable SFP module as well.
13-14
Alarms and Conditions - shows current alarms and conditions sorted according to
severity and time-and-date and provides access to the corresponding alarm
configuration options (on page 13-9).
Status - shows devices status and failure description when relevant. The status can be
OK, HW failure or Failure (upon alarm conditions).
Monitoring
PFU-8 View
To invoke the PFU-8 View
In case that PFU-8 unit is installed and enabled, on the Network Element tree, click
Modules, PFU-8 Module. The PFU-8 Module pane is invoked. The pane includes the
following areas:
Configuration - shows Enable/Disable status of element and enables changing the status
through the Configure button.
Alarms and Conditions - shows any alarms currently active and the relevant information.
Provides access to alarm severity configuration (on page 13-9) options.
Status - provides status and failure description (when relevant). Three types of statuses
are provided: OK, HW failure or Failure (alarm condition). The Port Status button
provides a view of the status of each PFU-8 port.
13-15
Monitoring
13-16
Monitoring
2. In the Alarms and Conditions area, click Ports Status. The PFU-8 Ports Status dialog
box opens.
3. To reset the Last Fault and Last Fault Time columns, click Reset.
4. To refresh the table, click Refresh Now.
5. To close the dialog box, click Close.
SFP View
Note: The SFP View is relevant for all ML6xx models except ML622.
The SFP View summarizes general and status information on the SFP module. This pane also
provides access to the SFP module parameter configuration and alarm configuration dialogs.
To access the SFP view
On the Network Element tree, click Modules, SFP-1-x. The SFP Module pane is invoked.
The pane is divided into the following areas:
Alarms and Conditions - shows any SFP alarms with the relevant information. The
Configure Alarms button provides access to the SFP alarm management pane - used to
disable alarms and modify their severity.
13-17
Monitoring
13-18
Inventory - shows hardware and software information on the SFP module.The Details
button displays the SFP manufacturer details. Details provides additional information, if
available, on transceiver's parameters (i.e. rate, wave length, reach).
Monitoring
Configuration - shows the bridge level configuration settings and provides access to the
corresponding configuration dialog.
STP Bridge (on page 13-21) and STP Port (on page 13-24) Status monitoring
13-19
Monitoring
Due to hash function implementation of the Forwarding database some MAC addresses
(falling into the same place in the hash table) are learned but may not be displayed in the
Forwarding database.
CPU MAC Address is permanently reserved in the Forwarding database but cannot
be viewed;
When Ingress Rate Limiting is enabled (on any port), ML600 allocates 3 entries per
each VLAN (all of them) in advance, to allow IEEE L2 Control Protocol (L2CP).
The allocated addresses can be viewed in the Forwarding database:
When STP feature is enabled (in the bridge), ML600 allocates 3 entries per each
VLAN (all of them) in advance, to allow STP interoperability with Cisco. The
allocated addresses can be viewed in the Forwarding database:
o
Caution: Viewing all MAC addresses in the table via the craft port may take a few minutes
and may affect management access of other users.
13-20
Monitoring
5. To view MAC addresses, learned in particular VLAN, in the View MAC Addresses For
area select the All MAC Addresses for VLANs option and from the list box, select
<VLAN ID>.
6. Click View. The MAC addresses are displayed.
7. To filter the display, from the Filter MAC Address for Port list box, select ALL,
COLAN (MGMT), ETH-{1-5}or HSL-{1-2} (ETH-5 not for 1/2 pairs units, HSL-2 only
for ML688).
8. To delete the database, click Delete All.
13-21
Monitoring
2. In the STP area, view the STP configuration and detail parameters.
Table 41: STP Parameters
FIELD
Description
Default and
Valid Values
Enable
No
Protocol
Type
RSTP
Max Age
20 seconds
This is the time interval (in seconds) at which the root device
(for STP) or any devices (for RSTP) transmit a configuration
message.
2 seconds
Forward
Delay
15 seconds
Bridge
Priority
0-61,440 in steps
of 4,096
Transmission
Limit
Nonconfigurable
parameter equal
to 3.
Bridge
Group
Address
Actual Root
Bridge
Priority
Actual Root
Bridge MAC
Hello Time
13-22
Valid Values:
Yes/No
Valid Values:
RSTP of STP
Valid Values for
STP: 6-40
seconds
Valid Values for
STP: 1-10
seconds
Valid Values for
STP: 4-30
seconds
0-61,440 in steps
of 4,096
Monitoring
FIELD
Description
Actual Root
Port ID
Actual Root Port of this switch. This is the index of the port on
this switch that is closest to the root. This switch communicates
with the root device through this port. This is 0X0000 if your
bridge is the root device.
Actual Root
Path Cost
This is the cost for a packet to travel to the root in the current
Spanning Tree configuration. The slower the media, the higher
the cost. This is 0 if your bridge is the root device.
Actual Max
Age
Value derived
from the Root
port.
Actual Hello
Time
This is the time interval (in seconds) at which the root device
(for STP) or any devices (for RSTP) transmit a configuration
message.
Value derived
from the Root
port.
Actual
Forward
Delay
This is the time (in seconds) a device will wait before changing
states.
Value derived
from the Root
port.
Default and
Valid Values
13-23
Monitoring
13-24
Monitoring
13-25
Monitoring
Description
Enabled
No
128
Path Cost
The cost of using the port to reach the root bridge. When
selecting among multiple links to the root bridge, STP
chooses the link with the lowest path cost and blocks the
other paths. Each port type has its own default STP path
cost.
Edge Port
No
Default depends on
Half/Full Duplex
mode. AUTO value is
assigned by default.
Actual Edge
Port
Yes/No
Actual Link
Type
P2P/Shared/AUTO
Priority
Link Type
13-26
Valid values:
P2P/Shared/AUTO
Monitoring
FIELD
Description
Actual Port
Id
Actual State
<Disabled> - when
STP on port is disabled
Actual Role
Protocol
Type
STP or RSTP
Actual
Protocol
Type
STP or RSTP
Valid Values:
Forwarding,
Discarding or Learning
Root, Designated,
Alternate, Backup or
Disabled
13-27
Monitoring
FIELD
Description
Designated
Root Bridge
MAC
Displayed in HEX
format.
Designated
Root Bridge
Priority
Designated
Root Path
Cost
Designated
Bridge
MAC
Designated
Bridge
Priority
Designated
Port Id
13-28
Valid Values:
Displayed in HEX
format.
Monitoring
Port Summary View - provides a table summarizing the main information and status for
all ports of a specific type (i.e. Ethernet ports, LAG ports) in the device, where a table is
provided for each type of port.
13-29
Monitoring
To sort the display according to a parameter other than AID (default) - click the column
heading.
Buttons with additional options are provided at the bottom of the pane. These are
described in the following table.
Description
13-30
Monitoring
Statistics
Restart
Configure Alarms
Configure
Configuration - shows current physical and service configuration and provides access to
configuration change and port control options.
Alarms, Conditions and Statistics - shows alarms and provides access to port statistics
displays and to alarm configuration options
13-31
Monitoring
13-32
EFM OAM - shows EFM OAM status and provides loopback test operation and analysis
options.
Monitoring
To view additional information on a specific port - click on the row of the corresponding
port.
Buttons with additional options are provided at the bottom of the pane. These are
described in the following table.
Description
Statistics
Configure Alarms
Configure
13-33
Monitoring
13-34
Configuration - shows current physical and service configuration and provides access to
configuration change and port control options.
Alarms, Conditions and Statistics - shows alarms and provides access to port statistics
displays and to alarm configuration options
Monitoring
Ethernet Statistics
Ethernet port statistics are available separately per each Ethernet port.
Ethernet statistics counters can be manually reset. These counters are also automatically reset
when Ethernet port (ETH <ID>, COLAN (MGMT), HSL<ID>) is deleted or reverted to
factory setup.
Ethernet statistics include the following:
Table 45: Ethernet Statistics
Counter
Rx statistics:
Total frames received
Total octets received
Description
Notes
Received Valid
Broadcast frames
13-35
Monitoring
Tx statistics:
Total frames transmitted
Total octets transmitted
Transmitted Valid
Unicast frames
Transmitted Valid
Multicast frames
Transmitted Valid
Broadcast frames
Discarded error frames
13-36
Collision statistics:
Collisions
Monitoring
Procedure
To monitor, refresh or reset Ethernet Statistics for any Ethernet port
(ETH<ID>, HSL<ID> or COLAN/MGMT):
1.
2.
3.
4.
13-37
Monitoring
Performance Monitoring
Performance Monitoring
High Speed Link (HSL) Status Monitoring
The HSL aggregation characteristics are displayed via HSLs and HSL panes, where the
HSLs pane provides a glance view (table format) of all available HSLs. The single HSL pane
provides information on each HSL details as described below.
Note: To view the HSL Ethernet characteristics use Ethernet Ports pane.
13-38
Configuration - shows the current configuration of the HSL and provides access to HSL
configuration options.
Alarms, Conditions and Statistics - displays any alarms relevant to the HSL and provides
access to the alarm configuration options through the Configure Alarms button
Performance Monitoring
Monitoring
Description
Start BW Restoration
Stop BW Restoration
Calibrate
Cancel Calibration
Topology
Topology Test
Modem Details
HSL Details
13-39
Monitoring
Performance Monitoring
Details Area
The Details Status area provides detailed information on HSL Status, Modem Ports and
Calibration Parameters. Before the HSL is calibrated, only some of the information is
displayed. During calibration, a progress bar is displayed in the Status area.
Table 47: Detail fields
Parameter
Description
HSL Status
Calib. Status
13-40
Performance Monitoring
Monitoring
Table 48: HSL Status parameter list (applicable in HSL -O (Office) mode only)
Parameter
Description
Not enough
active lines
The link is down due to not enough active lines to immediately start
calibration.
If calibration was requested, it is pending until all assigned active lines to
the HSL modem ports become active (automatically synchronized).
Please check that all enabled HSL modems are connected with copper lines.
In such a case, either delete all non-relevant modem ports from the HSL or
force calibration to start by clicking the Start Calib. Anyway button.
Recovering
Equipment
outage
Trying to sync
modems
Copper outage
The link is down due to copper outage or NE linked via HSL is not
connected or powered down.
Planning Fault
The link is up with a bandwidth lower than the target bandwidth. This may
happen during calibration or after modem rate adjustment.
Low ETH
Bandwidth
The link is up with a bandwidth lower than the threshold configured for this
link.
Copper outage
during previous
calibration
Copper
connection
mismatch during
previous
calibration
Retrying calibration. Previous calibration failed due to cut line. At least one
cut line was detected during calibration.
All modems
failed
qualification
during previous
calibration
<Empty>
13-41
Monitoring
Performance Monitoring
Modem Ports
The Modem ports section provides details about the number of modem ports assigned to this
HSL and summary information.
Table 49: HSL Details - Modem Ports
Parameter
Description
Enabled
Qualified
13-42
Performance Monitoring
Monitoring
Parameter
Description
Active
Sum of Rates
Calibration Parameters
Notes:
1. All the parameters listed in the Calibration Parameters pane area are set during the HSL
Calibration
Procedure
(on
page
4-28).
2. Calibration Parameters list is applicable in HSL -O (Office) mode only.
Description
Calibration
Target
Spectral Mode
Required SNR
Margin
The target Signal to Noise Ratio margin (in dB) required for the copper
lines (5dB by default). To view the achieved SNR Margin, click Modems
Details link.
Minimum PBO
The minimum value of PBO (Power Back Off). This is a parameter that
may be increased to reduce the interference with other services in the
binder, however it may reduce ML link capacity.
Dynamic Spectral The DSS (Dynamic Spectral Shaping) calibration reduces the interference
with other services in the binder using higher constellation (more BW
Shaping (DSS)
efficient) and increased PBO whenever possible.
Circuit Length
Type
13-43
Monitoring
Performance Monitoring
Parameter
Description
Rate Adjustment
Extended Rates
Indicates whether the modem rates may go above 5,696 kbps and/or use
TC-PAM64 and TC-PAM128 constellations. BW shall be kept or HSL
BW may be decreased if environment has changed. Extended rates are
limited to some spectral modes, for more details regarding these Spectral
Modes see HSL Calibration.
Status
This Status area shows the calibration results for the selected HSL. This includes information
on the bandwidth and EWL.
Table 51: HSL Details - Status
Parameter
Description
Calibrated/Adjusted
BW
Available BW
Currently available Ethernet bandwidth over HSL for service connections. In case of degradation in
the lines, the Available bandwidth may drop below the Achieved bandwidth.
In a deployment where link capacity shall be smaller than available BW, use the Egress Rate Limit
to reduce the Ethernet BW over HSL.
EWL
About EWL The ANSI T1.417 standard defines deployment guidelines in terms of an equivalent
working length (EWL) of multi-gauge cable. EWL is intended to provide equivalence between the
length of a multi-gauge loop and that of a straight 26-AWG loop. It is auto-measured in any
Spectral Mode.
EWL = (1.41) x L28+ L26+ (0.75) x L24+ (0.60) x L22 + (0.40) x L19, where L26, L24, L22, and
L19 are the lengths of 28-, 26-, 24-, 22-, and 19-AWG cable in the subscriber loop excluding any
bridge taps, respectively.
Used for Calibration - reports the EWL value which was auto-measured for calibration using the
following measure algorithm: At first, the EWL of the Longest Segment (or the single segment for
non-repeated lines) per Modem is selected from all measured and then the EWL of the Median
Modem in the HSL is selected and used for Calibration.
Total Length - (optional for repeated lines only) reports the approximate EWL value automeasured for a repeated link (not used for calibration).
Note: you may choose to display this field in feet or in meters
Supported by RoHS6 compliant models. Extended Rates allows up to 15Mbps for each copper-pair.
Failure Reason
CPE Vendor
13-44
Performance Monitoring
Monitoring
Line performance for both N (toward network or NEND) and C (toward customer or
FEND) sides of the repeater.
Line inventory per hop. For repeated lines only, repeaters mismatches indications are
provided.
13-45
Monitoring
Performance Monitoring
13-46
Top area - shows the elements in the span according to their relative locations. For
repeated spans, each XR239 repeater is displayed as well.
Information area - the information available for each element is grouped under the
corresponding item. The type of displayed information depends on the Line view
information option that is selected (Line Performance is selected by default). If the
link is repeated by XR239 units, information on each Repeater hop is shown under
the corresponding hop number.
Description area - used to view detailed information on the HSL or HSL elements.
Range: up to 1300 alphanumeric characters.
Display Options - determine and filter the type of information displayed in the
Information area and a legend of the terms used.
Performance Monitoring
Monitoring
Line Inventory View - provides the Line inventory for each HOP.
For repeated lines only - in case of Repeater wiring mismatches, a yellow cell
background is displayed on the corresponding cell:
In case of DUO/ADUO mismatch, the cell of the first Hop S/N is colored yellow.
(For more on DUO/ADUO mismatch see Mismatch between Configuration
and Connections (on page 14-71)).
In case of Split Pairs (the two pairs of the repeater are wired to two different
repeaters in the next hop), the cells of the Hops S/Ns following the split are
colored yellow. (For more on Split Pairs see Split Pairs (on page 14-73)).
Power View - shows the power feeding status of each hop (actual power status and
repeaters dipswitch status).
2. Select the Show the following parameters options according to the selected group
parameters that are of interest: ALL (default) - shows all the parameters, or specified
parameters.
3. In the Measured In option, verify (or choose) the units in which the distance along the
span will be displayed in Line Performance.
4. By default, the display is refreshed every 60 seconds. You may disable the auto-refresh
option by un-checking Refresh every 60 sec. Note that you can update the display at any
time by clicking the Refresh button.
5. To close the pane, click Close.
13-47
Monitoring
Performance Monitoring
PM Operations Pane
Most modem PM configuration and display functions are provided in the Modem Ports pane.
DSx1 PM configuration and display functions are provided from the DSx1 Ports pane. This
section describes the relevant functions as they are displayed in the Modem Ports pane. All
Modem Ports pane PM functions except for Configure PM Threshold are similar to the DSx1
Ports PM functions.
To access PM operations
1. From the Network Element tree, click Modem Ports (to access the Modem Ports PM
options) or DSx1 Ports (to access the DSx1 Modem Ports PM options). The relevant
pane appears.
The figure below shows a partial image of the Modem Ports pane with the PM options.
The options are relevant to the selected port.
13-48
Performance Monitoring
Monitoring
Description
Init PM
Init PM all
View PM
Displays the PM counters data, data may be filtered in advance (to shorten the
time the operation takes).
Configure PM
Configure PM
Threshold
PM Counter Types
This section describes the MLP PM counters and the DSx1 PM counters.
Note: Some of the counters are common to both MLP and DSx1 lines while others are
specific to each type of line.
Description
CVL
Code Violation Online. The SHDSL parameter code violation is defined as a count of the
SHDSL CRC anomalies occurring during the accumulation period. This parameter is
subject to inhibiting.
ESL
Number of line errored seconds. The G.SHDSL parameter Errored Second is defined as a
count of 1-second intervals during which one or more CRC anomalies are declared
(and/or one or more LOSW defects are declared). Errored Seconds (ES) are not counted
during UnAvailable Seconds (UAS).
SESL
Severely line error seconds. The G.SHDSL parameter Severely Errored Second is
defined as a count of 1-second intervals during which at least 50 CRC anomalies were
declared or one or more LOSW defects were declared. Severely Errored Seconds (SES)
are not counted during UnAvailable Seconds (UAS).
13-49
Monitoring
Performance Monitoring
Parameter
Description
UASL
Unavailable seconds. The G.SHDSL parameter UnAvailable Second is a count of 1second intervals for which the G.SHDSL line is unavailable. The G.SHDSL line
becomes unavailable at the onset of 10 contiguous SESs. These 10 Severely Errored
Seconds are included in the Unavailable Seconds count. Once unavailable, the G.SHDSL
line becomes available at the onset of 10 contiguous seconds with no SESs. These 10
Severely Errored Seconds are not added to the Unavailable Seconds count.
LOSWSL
Description
CVL
Code Violation-Line. Number of DSx1 Line Coding Violations (CV-L) that occurred
during the interval.
CVP
Code violations-Path. Number of DSx1 framing errors (CV-P) that occurred during the
interval. In case of framing with CRC (i.e. ESF and E1CRC framing), counts CRC
errors. Monitor Type: P (Path). Note that CVP is not applicable for framing type UNFR
(Unframed).
ESL
Errored Seconds-Line. Number of DSx1 Line Errored Seconds (ES-L) that occurred
during the interval. A Line Errored Second is a second in which one or more Line Code
Violation error events were detected.
ESP
Errored Seconds-Path. Number of DSx1 Line Errored Seconds (ES-P) that occurred
during the interval. A Path Errored Second is a second in which one or more framing
error events were detected. In case of framing with CRC (i.e. ESF and E1CRC framing),
counts CRC errors. Note that SESP is not applicable for framing type UNFR
(Unframed).
SESL
Severely Errored Seconds-Line. Number of DSx1 Line Severely Errored Seconds (SESL) that occurred during the interval.
SESP
Number of DSx1 framing Severely Errored Seconds (SES-P) that occurred during the
interval. Monitor Type: P (Path). Note that SESP is not applicable for framing type
UNFR (Unframed). Monitored for Rx direction only.
SASP
Number of Seconds with SEF or AIS defect (SAS-P) that occurred during the interval. A
second with either one or more OOF defects or detected AIS defect.
Monitor Type: P (Path).
Note that SASP is not applicable for framing type UNFR (Unframed). Monitored for Rx
direction only.
13-50
Performance Monitoring
Monitoring
Parameter
Description
UASP
FCP
Number of Occurrences of near-end Path failure events (LOF or AIS) during the interval
(FC-P). Monitor Type: P (Path).
Note that FCP is not applicable for framing type UNFR (Unframed). Monitored for Rx
direction only.
UCSSL
Number of Uncontrolled Slipped Seconds (UCSS-L) that occurred during the interval.
Insufficient HSL BW would be counted in UCSSL-TX counter.
Monitor Type: L (Line). Monitored separately for Tx and Rx. Note that UCSSL is not
applicable for framing type UNFR (Unframed).
SUSSL
Number of DSx1 Suspended Seconds (in CO unit only) due to HSL down that occurred
during the interval. Monitor Type: L (Line). Monitored for Tx direction only.
PM Attribute Descriptions
Most PM dialog boxes use the following attributes as described below.
Table 55: View PM parameter list
Parameter
Description
Type
The counter types include all possible counters for this interface, see MLP PM
Types (on page 13-49) and DSx1 PM Counter Types (on page 13-50).
Value
Validity
Location
The location of the required information: NEND - Near End or FEND - Far End.
13-51
Monitoring
Performance Monitoring
Parameter
Description
Direction
Time Period
The starting date and time of the selected monitoring interval. Can be:
All - For any applicable date and time when all available intervals are monitored.
Current - Current date and time of the system.
Specific - Specific date and time
Threshold
The threshold value of a specific PM counter. Thresholds are applicable for both
15-minute and 1-day current intervals. Threshold value equals to 0 implies that
threshold control is disabled. If the Threshold value is empty, no change can be
made in multiple operations.
System Time of Day (TOD) adjustment will cause performance data interval timestamp
changes as follows:
When TOD is adjusted forward or backward then ALL recent history interval timestamps
are changed forward or backward accordingly;
When TOD changes due to DST(Daylight Saving Time) start (one hour is skipped), then
recent history intervals sequence will skip the non-existing hour, e.g. 01:15; 01:30; 01:45;
<DST start> 03:00; 03:15, etc. sequence will appear;
When TOD changes due to DST end (last hour is repeated twice), then recent history
intervals will represent this hour twice (before and after DST end) by intervals with
duplicated timestamps, e.g. 01:00, 01:15; 01:30; 01:45; <DST stop> 01:00; 01:15, etc.
sequence will appear;
Changing the DST range can cause a shift in interval timestamp as follows:
13-52
If an interval was collected within the DST range and after changing the range it is
not within the DST range then its timestamp will shift backward;
If an interval was collected outside the DST range and after changing the range it is
within the DST range then its timestamp will shift forward.
Performance Monitoring
Monitoring
Start time within a 24 hour day when the accumulation process starts
The line segments over which counters are collected - by default, counters are collected
from all line segments
3. From the PM Start Time list box, select the start hour when the PM counter
accumulation begins.
4. Click OK.
13-53
Monitoring
Performance Monitoring
Initializing PM Counter
The initialization resets or sets a specific value to the PM counter selected by the filter.
To configure the PM counters collection
Note: The procedure described below is the same for DSx1 PM counters.
1. From the appropriate pane (see PM Operations Pane (on page 13-48)), click Init PM.
The Initialize PM in MLP dialog appears.
Set the Counter Value - sets the value of the selected counter(s), default value is '0'.
Filter selects the counters that would be initialized. Filter is based on Counter Type,
Location, Direction, Period, Date and Time:
Counter Type - determines the type of counters (i.e. ESL, UASL). You may choose to
collect All counter types, a specific counter type or counter types from NEND or FEND.
Location - determines the location along the span from which the counters are collected.
You may choose to collect counters from the complete span (All) or from a specified
segment in the span (i.e. NEND, FEND).
Direction Direction is always Receive (equivalent to All).
Period - determines the counter values will be collected:
13-54
Performance Monitoring
Monitoring
Current Data -
2. Click OK.
Enabling/Disabling Line Segment's PM collection
The Configure PM button opens the Configure PM dialog box that allows you to turn on or
off the PM counters.
To turn on or off the PM counters for each modem:
1. In the Network Element tree, open Modem Ports, Modem Port MLP <ID>. The
Modem Port MLP <ID> pane opens.
2. In the Alarms, Conditions and Statistics area, click Configure PM. The Configure PM
in MLP <ID> dialog appears.
13-55
Monitoring
Performance Monitoring
View PM counters
In general, performance parameters are raw counts derived by the processing of performance
primitives within 1-second intervals. At the end of each second, the data in the current second
counter is nominally moved to the current period counters, unless some other action is
warranted. At the end of each accumulation interval, the current value of the performance
parameter counter is saved in a corresponding "previous period" counter, and the "current
counter" is reset to zero.
Performance parameters are accumulated over pre-determined accumulation periods (15minutes and 1-day) and maintained in designated storage counters. Additional counters are
provided to maintain a recent history of the parameter. Each interval can be defined as
incomplete or invalid for that interval. This might happen if the user resets the counter or
changes the time of day during the interval.
These storage counters are acting as a pushdown stack. That is, a new value is stored at the
most recent history counter, data in every history counter is shifted down to the next most
recent history counter, and the last value in the history is discarded.
On the Element Tree select Modem Ports and then Modem Port or DSx1 Port. The View
PM button in the Modem Ports pane opens the Filter View PM dialog box that allows you
to filter the View PM dialog box to minimize the number of information to monitor.
To monitor PM counters:
1. From the appropriate pane, click View PM. The Filter View PM dialog appears.
2. From the Counter Value box, select a discriminating filter for the counters presentation:
At least or At most.
13-56
Performance Monitoring
Monitoring
Current date - displays counters acquired over the current date (today)
7. To save the report, click Save Report. A Windows Save dialog opens allowing you to
save the report.
8. To print the report, click Print Report. A Windows Print dialog appears allowing you to
print the report.
9. To Filter the pane, click Filter. The Filter View PM dialog appears. Go to step 2.
13-57
Monitoring
Performance Monitoring
Threshold Alerts
Viewing PM Threshold Crossing Alerts
The ML device reports the PM counters threshold crossing event by notification (alert and
not alarm) which do not persist and is not retrievable from the ML device.
MetaASSIST View collects the notifications (while the session with the specific ML device
is open) and displays all notifications in glance view on a separate pane, accessible from
Network Element Tree, System Administration, Alarms, Threshold Crossing Alerts.
Notifications can be disabled via the Threshold Crossing Alerts (TCA) pane or when a popup notification appears.
To monitor threshold cross alerts
1. On the Navigation tree in the Network Element tree, open System Administration,
Alarms, Threshold Crossing Alerts. The Threshold Crossing Alerts pane opens.
13-58
Performance Monitoring
Monitoring
3. To stop displaying Threshold Crossing Alert warnings, select Do not display Threshold
Crossing Alert warnings check box. This step should be repeated for each NE to avoid
TCA warnings from displaying.
4. In case TCA warning appears, either click Close to close the dialog box or click Do not
display Threshold Crossing Alert warnings check box to stop displaying future TCA
warnings on this NE. Repeat this step for each NE when TCA warning appears.
3. From the Counter Type list box, select a specific counter type or ALL to set the
threshold for all counters.
4. Select a specific Location (NEND, FEND, Line-x, etc.), or ALL to set the threshold for
counters from all locations.
5. Select Period over which the threshold will be applied.
13-59
Monitoring
Performance Monitoring
6. Click OK. The Configure PM Threshold in Modem Port MLP dialog appears.
7. In the Threshold Level box, type the value (in seconds), to report an alert when the
number of counted error seconds crosses the configured threshold level.
Modem Ports
The ML device provides local Modem Ports configuration, operational status and inventory
monitoring.
This information is provided in the following forms:
Glance view for all modems available (enabled and disabled) in the ML device model,
also sorted by HSL AID;
Glance view for particular modems which are aggregated by the specific HSL of the ML
device;
In addition, the ML device provides monitoring of a particular copper line connected to the
Modem Port of the system. The ML device displays discovered copper line topology,
performance information (SNR Margin and Loop Attenuation) and inventory information of
the equipment, which terminate/regenerate the copper line.
13-60
Performance Monitoring
Monitoring
The following table describes the Modem Ports parameters that can assist you in monitoring
the Modem Ports.
Table 56: MLP pane parameter list
Parameter
Description
AID
Config
Alarms
13-61
Monitoring
Performance Monitoring
Parameter
Description
HSL
The HSL which this modem belongs to. HSL is displayed with its mode either
HSL<ID> (-O) for Office mode or HSL<ID> (-R) for Customer mode.
Linked NE
Circuit ID
The modem logical description such as location, room, shelf, MDF slot, etc.
Max Rate
HIATTN
High loop attenuation threshold in dB. An alarm is raised if the current loop
attenuation on the MLP is equal or exceeds the displayed value configured for this
MLP.
LOWSNRM
Low SNR margin threshold in dB. An alarm is raised if the current SNR margin on
the MLP is equal or less than the displayed value configured for this MLP.
13-62
Performance Monitoring
Monitoring
In the Network Element tree, click HSLs, HSL AID. The HSL AID pane opens in the
work area. Click Modems Details. The Details for Modem Ports dialog opens.
Figure 27: Details for modem ports of the particular HSL pane
The following table describes the Modem Port Details parameters that can assist you in
monitoring the Modem Ports.
Table 57: MLP pane parameter list
Parameter
Description
AID
HSL
Status
13-63
Monitoring
Parameter
Performance Monitoring
Description
Qualification
Modem Qualification status and calibration rate as determined by the High Speed
Link during calibration (equal to initial rate).
Qualifying - Qualification is currently in Qualification process.
Qualified at ... kbps - Modem successfully passed Qualification.
<Empty> - Not qualified
Qual. Failed: No Sync - Modem failed Qualification due to failure to synchronize on
minimum rate.
Qual. Failed: Low Rate - Modem failed Qualification due to Low SNR (Signal to
Noise Ratio) or due to low rate.
Qualified at ... kbps - Adjusted - Modem rate was reduced due to low SNR after last
calibration.
Qualified at ... kbps - Adjusting - Modem rate is currently being adjusted due to low
SNR.
Dynamic Addition - Modem currently added to already calibrated HSL is in the
process of performing synchronization. (An alarm is not generated during this time).
Adjusted Rate
Displays the reduced modem rate due to low SNR after last calibration.
SNR Margin
Lowest SNR margin (dB) measured at the termination points over the copper pair
line.
Loop Attn.
13-64
Performance Monitoring
Monitoring
Parameter
Description
Modulation
(PAM)
Modulation type, which is set automatically by the system during HSL initialization,
and can be changed during modem adjustment.
Valid values:
PAM16 - Pulse Amplitude Modulation having 16 levels in each symbol, enabling
transmission of 3 data bits per symbol;
PAM32 - Pulse Amplitude Modulation having 32 levels in each symbol, enabling
transmission of 4 bits per symbol (for G.SHDSL.bis).
PAM64/PAM 128 Optional on RoHS6 modules with Extended rates enabled,
Pulse Amplitude Modulation having 64/128 levels in each symbol, enabling
transmission of 5/6 bits per symbol.
13-65
Monitoring
Performance Monitoring
Configuration area - provides modem control, test and configuration options as well as a
summary of the configured parameter values.
Alarms, Conditions and Statistics area - displays current alarms and provides access to
performance monitoring and to alarm configuration options.
Details area - provides detailed connection information and access to line analysis,
diagnostics and inventory display options.
13-66
Performance Monitoring
Monitoring
Description
Port
Port shows the line segment. Odd line numbers are the NET (network) port side
of each hop, even line numbers are the CUST (customer) port side of each
segment.
Serial Number
Ports is numerated starting from local Modem Port of monitored NE and ending
on NE linked-via-HSL. Valid values are:
NEND (Near End);
FEND (Far End);
LINE-{1-16} - in case when SHDSL modem regenerators are detected.
Modem location displays an equipment type as defined in ITU-T G.991.2, where
the modem is located. Valid values are:
Hop-x - in a repeated line - segment between repeaters.
STU-C - modem termination point working in -O (Office mode);
STU-R - modem termination point working in -C (Customer mode);
SRU-N - modem regeneration point toward STU-C;
SRU-C - modem regeneration point toward STU-R.
Serial number of the equipment where the modem port is detected.
CLEI
CLEI (catalog code) of the equipment where the modem port is detected.
Model
HW Version
SW Version
Data
Ext. Rates
Location
13-67
Monitoring
Performance Monitoring
LOWSNRM Alarm is raised on crossing threshold down (SNR margin becomes equal or
less than the threshold value);
HIATTN Alarm Clearance is sent on crossing threshold down, usually after modem
synchronization (Loop attenuation becomes larger than the threshold value by at least 1 dB).
MetaASSIST View provides both non-repeated and repeated copper lines.
To view Line Performance details:
1. In the Network Element tree, click Modem Ports, MLP <AID> pane.
2. In the MLP <AID> pane, click View Line Performance. The View Line Performance
in MLP <AID> opens in the work area.
13-68
Performance Monitoring
Monitoring
Note: For a single modem belonging to an HSL in -R (Customer) mode only NEND
(STU-R) Termination Point is displayed.
Description
Termination Point
Modem termination point is numerated starting from local Modem Port of monitored
NE and ending on NE linked-via-HSL. Valid values are:
NEND (Near End);
FEND (Far End);
LINE-{1-16} - in case when SHDSL modem regenerators are detected.
Modem location displays an equipment type as defined in ITU-T G.991.2, where the
modem is located. Valid values are:
STU-C - modem termination point working in -O (Office mode), adjacent to
provider Network;
STU-R - modem termination point working in -C (Customer mode), adjacent to
Customer Premises Equipment;
SRU-N - modem regeneration point towards STU-C, i.e. Network;
SRU-C - modem regeneration point towards STU-R, i.e. Customer.
Local identification of the port on the device.
For STU-C: MLP AID;
For STU-R: MLP AID;
For SRU-N: Port #1/2 towards STU-C
For SRU-C: Port #1/2 towards STU-R
Current Signal to Noise Ratio Margin measured at the modem port.
Location
Port ID
Percent of frames received on MLP with CRC errors in the last 20 seconds.
13-69
Monitoring
Performance Monitoring
EWL (feet)
PFU Monitoring
In repeated link, the PFU Module monitoring pane provides information specific to the PFU
module and in addition detailed information on each port and on module alarms.
To access the PFU-x module pane
On the Navigation tree in the Network Element tree, click Modules and select PFU-x
module. The PFU-x Module pane appears in the work area. The pane is divided into areas
that provide configuration, alarm and detailed status information on the PFU-x module.
13-70
Configuration - shows if the PFU-x module is enabled or disabled. Use the Configure
button to Enable or Disable the module.
Alarms, Conditions and Statistics - displays any alarms relevant to the PFU and provides
access to the alarm configuration options through the Configure Alarms button
Status - shows Module status and provides access to module level Details (on page 1371) and Port Details (on page 13-72).
Performance Monitoring
Monitoring
Inventory Info - provides general information on the PFU, including versions, serial
number, etc.
PFU Details
The PFU Details display shows information on the PFU Module configuration, status and
measured values.
To display the PFU Module Details
1. In the Network Element tree, click Modules and select PFU-1 module. The PFU-1
Module pane appears in the work area.
2. In the Status area, click Details.
Click Refresh Now to update the display.
13-71
Monitoring
Performance Monitoring
Description
Reset
Refresh Now
13-72
Monitoring
Each line in the pane contains a port added for monitoring and information on that port
bandwidth. Up to four ports can be defined.
Note: Use the BW Presentation in to determine the measurement units of the display.
Note that when choosing the View Graph option, the measurement units will be as
selected in the BW Presentation in field.
2. To add a port to the list:
13-73
Monitoring
Click Add Port. The Add Port for BW Monitoring dialog appears.
From the Port list box, select the port and click OK.
Clear statistics on selected ports - select the relevant ports (more than one port may
be selected at a time) and click Reset Data.
Delete selected ports from the list - select the relevant ports (more than one port may
be selected at a time) and click delete.
View a graph of the average Tx and Rx bandwidth of a selected port - select the port
and click Show Graph. Refer to Port Traffic Graph (on page 13-74).
13-74
Monitoring
4.
5.
6.
7.
8.
9.
10.
13-75
Monitoring
13-76
4.
5.
6.
7.
8.
9.
10.
Monitoring
Each line in the pane contains a service added for monitoring and information on that
service bandwidth. Up to four services can be defined.
2. The BW Presentation in sets the measurement units of the display. Note that when
choosing the View Graph option, the measurement units will be as selected in the BW
Presentation in field.
13-77
Monitoring
Click Add Service. The Add Service for BW Statistics dialog appears.
From the list box, select the service and click OK.
13-78
Clear statistics on selected services - select the relevant services (more than one
service may be selected at a time) and click Reset Data.
Delete selected services from the list - select the relevant services (more than one
service may be selected at a time) and click delete.
View a graph of the average Tx and Rx bandwidth of a selected service - select the
service and click Show Graph. Refer to Service Bandwidth Graph (on page 1379).
Monitoring
13-79
Monitoring
2. On the table, select a row. Click Show Graph. The BW Monitor for <Port> dialog
appears.
3.
4.
5.
6.
7.
8.
9.
13-80
Monitoring
Port configuration
13-81
Monitoring
Automatic Link - This option is ENABLED by default - selecting any item (IP address,
VLAN or Port), automatically displays all the associated items on both NEs. If Automatic
Link is DISABLED, each item stands on its own. If it is modified, the associated items do
not change accordingly. This enables analyzing each element on its own.
Tabs at the bottom of the pane provide a range of detailed analysis options.
Description
Port
Bridge
Shows Bridge level configuration and status for each of the defined NEs
Ethernet Statistics
Shows traffic flow on the link or on a single interface in the selected direction
VLANs
Shows the Port Membership and Tag for each VID, for each displayed NE
EVC
EVC Statistics
To analyze a link
1. The link of interest can be selected using two methods:
From the Physical tab - Network Element tree, expand the Ethernet Port item and
choose the relevant port. For example, HSL-1 or ETH-2. Select the Connectivity
tab. The selected interface will be displayed along with any other interfaces and the
VLANs relevant to the link.
Under the relevant NE, select the HSL or ETH interface, the corresponding
information will be invoked.
2. The above figure shows an end-to-end link connection between HSL-1 on the ML2300
DSDU-1 (lower SDU card) and HSL-1 on the ML624. The service is defined by VLAN
100.
3. Click the relevant tab to show the required link information.
13-82
Monitoring
Description
AID
13-83
Monitoring
System Name
Enterprise
13-84
Monitoring
System/Clock tab - shows the DSx1 Type, CES and Clock configurations on a defined
link between two devices.
Ports tab - shows DSx1 port configuration and status on a defined link between two
devices
13-85
Monitoring
The configurations of the two chosen units (CO and CPE) should match under the following
parameters:
DSx1 Type, CES Payload and CES Jitter Buffer size shall match on CO and CPE
(separately configured per NE)
Framing Type (separately configured per port of NE) shall match on CO and CPE DSx1
port of the same number (For example, DSx1-1-3 on CO and DSx1-1-3 on CPE)
Channels (separately configured per port of NE) shall match on CO and CPE DSx1 port
of the same number (DSx1-1-2 on CO and DSx1-1-2 on CPE)
State of DSx1 port shall be enabled on both CO and CPE for the port of the same number
(DSx1-1-4 on CO and DSx1-1-4 on CPE)
All other mismatches are possible and should not affect the service.
13-86
In the Network Topology tree, under Ethernet Services, select Identification Rules.
The Frame Identification Rules pane appears. In example below ML650 rules are shown:
Monitoring
DSx1 Loopback
The DSx1 loopback test is used to assist in fault isolation. During the loopback test, the
external equipment (third-party equipment) connected to ML DSx1 ports analyzes the traffic
BER (Bit Error Rate).
Two types of tests can be run: Facility and Equipment loopback. The tests can be run from
either the CO side or from the CPE side. Usually, this test is initiated from the CO side and if
required, is also performed from the CPE side.
Note: Clock flow is always from the CO side to CPE side, even if loopback is initiated from
the CPE. See Clock Considerations (on page 13-88) for more information.
Facility loopback mode - The loopback is in the DSX port entry towards the line and
eliminates (except for rare cases of LIU failure) the ML as the root cause (i.e. the root
cause is at the DSX source or between the DSX source and the ML unit).
Equipment loopback mode - The loopback is in the far ML unit equipment towards the
near ML unit and eliminates (except for rare cases of LIU failure) the whole ML link
(both CO and CPE sides) as the root cause (i.e. the root cause is at the DSX termination
equipment at CPE side or between the DSX termination equipment and the ML unit).
13-87
Monitoring
Clock Considerations
Note: Clock flow is always from the CO side to CPE side, even if loopback is initiated from
the CPE.
During loopback, the CO side shall either get a clock from the external DSx1 equipment or
be configured for internal free-run clock if external DSx1 equipment is configured to retrieve
clock from line (not internal clock). DSx1 equipment shall always retrieve clock from the line
(and not internal timing), even in case of loopback initiated from CPE side.
13-88
Monitoring
In the Details area, the Loopback button will become available (this is true only after the
port has been suspended).
3. Click the Loopback button. The following dialog appears.
4. Select Line (Facility) or Inward (Equipment) according to the required loopback mode.
13-89
Monitoring
13-90
Monitoring
MEP Pane
The MEP pane provides general information and options relevant for the selected MEP.
These include MEP configuration and suspend options, alarm configuration options, as well
as display and MEP monitoring and test options that are described in this section.
To invoke the MEP Pane
In the Connectivity tab, under CFM, select the relevant MEP. The MEP pane is invoked.
At the bottom of the pane, under Remote MEPs (RMEP), a list of up to five remote MEPs
(in the MA) is displayed. Basic information on each MEP is provided in the displayed table.
Note: For more information on a MEP in the list, select the MEP row and click the Details
button.
To...
RMEP Details
Init RMEP
Loopback
13-91
Monitoring
Link Trace
Topology
MEP Topology
The MEP Topology provides a visual display of a defined link: as one interface point is
selected, the pane automatically displays the peer connection, relevant VLAN, relevant HSL
and services side (Ethernet) interfaces.
To invoke the MEP Topology display
1. From Connectivity tab, under CFM, select the relevant MEP.
2. In the invoked pane, click the Topology button at the bottom of the pane.
13-92
Select one of the NEs comprising the link (i.e. DSDU-1 or CPE1-624) to view the
relevant VLANs, Ports and HSLs for each NE.
Select a VLAN for an NE. If Automatic Link (at the top of the tab) is enabled, the same
VLAN on the other side of the link (other NE) will be displayed along with the relevant
ports and HSLs for each NE.
Monitoring
CFM Loopback
CFM loopback can be used by the operator to verify connectivity (ping). The test consists of
Unicast frames transmitted by a MEP at administrator request to verify connectivity to a
particular maintenance point, indicating if a destination is reachable.
A CFM loopback message is similar to an Internet Control Message Protocol (ICMP) ping
message; however, the CFM loopback message cannot pass through L3 switching (Routers)
devices, making the operation relevant only for L2 switching (Bridges) network.
Note: CFM loopback is dedicated for connectivity fault isolation and for SLA performance
monitoring
The Waiting interval between two loopback messages transmitted in series is set to 1 sec and
the timeout to report loopback failure is set to 5 sec. These options are not configurable.
Other attributes such as number of messages sequentially sent, length of data, etc. are user
configurable.
A total of 10 Loopback operations can be simultaneously executed from the same NE.
To configure and run CFM Loopback
1. In the Connectivity tab, under the relevant MA, select the MEP to be analyzed. The
corresponding pane is invoked.
13-93
Monitoring
3. Set the MAC address to which the loopback will be performed - this is the unicast
address of the remote device. Set the address using one of the following options:
Remote MEP - select from the list of addresses discovered during CCM remote MEP.
13-94
Data length - CFM Loopback Message Frame Payload (without CFM header). Range
1 to 1500
Monitoring
Sequence ID - number applied to each CFM LPBK frame. Uniquely identifies the
series.
To...
Clear
Save As...
Stop
Close
13-95
Monitoring
13-96
Only MIP and MEP objects participate. The regular ETH port on NE will not respond to
the CFM Link Trace Message.
Monitoring
13-97
Monitoring
2. Under Remote MEPs (RMEP), select Link Trace. The following dialog appears.
3. Set the MAC address (unicast address) of the remote device to which the link trace will
be performed, using one of the following methods:
TTL (Time To Live) Period of time a data unit can exist in the network. Used to
prevent packets that have not reached their destination from loading the network.
Sequence ID user defined ID assigned to the link trace sequence. Used to identify
and analyze the link trace messages.
Egress ID after the test is run, shows the ID of the port on which the link trace
packet egressed.
Time Stamp Index showing when the Link Trace test was run (shown after the test
is run).
5. Click Send. If connectivity is available (at some level), the returned message will be
displayed.
13-98
Monitoring
The message (e.g. illustrated below) shows the Seq ID (i.e. 5), other configured
parameters (i.e. TTL = 64) and link trace information.
Note: Use the scroll bar at the bottom of the window to show display additional
information.
For more explanations about the messages in this window, see Link Trace Result Example
(on page 13-100).
The Link Trace tab buttons can be used to control the test and save results:
Table 65: Link Trace Tab buttons
Click...
To...
Save As...
Stop
Close
Description
Seq ID
TTL
Rx Flag
13-99
Monitoring
Terminal MEP
Re-built by each hop when the CFM Link trace message is re-sent.
Used view directly communicating hops (as chain):
Two NEs are considered as connected if Next Egress ID of one of
them appears as (Last) Ingress ID on another (see example).
Egress ID format includes: Shared MAC (of Bridge) provided in the
low-order six octets, and internally used (MEP + PORT) unique NE
identification in the high-order two octets.
Specifies which forwarding table is used (MIP/MEP FRWDB or
Traffic FRWDB). On ML NE only MIP/MEP FRWDB is used for
CFM forwarding.
Relay
Ingress, Ingress
MAC, Ingress Port
ID
Reports Ingress Port Status, Address and Local Name of the Port on
which the CFM Linktrace Request message was received (come in).
Reports Egress Port Status, Address and Local Name of the Port on
which the CFM Linktrace Request message was forwarded (come out).
ORG TLV
Note: CFM Link Trace Response is sent backward through the port
specified as ingress.
13-100
Monitoring
13-101
. 14
14 Troubleshooting
ML products perform an extensive Self-test during power up, checking the
installed hardware, data paths and system configuration. In addition, an inservice diagnostic test is periodically performed during normal operation,
ensuring system sanity. In case of an alarmed condition, an indication of the
event is given through:
- Front panel LEDs
- Office alarms transmitted via the alarm relays
- Autonomous TL1 reports, alarms and non-alarmed conditions
- SNMP traps
For more information or if you are unable to resolve a problem using these
procedures, contact Actelis Networks customer support. mail
to:techsupport@actelis.com (techsupport@actelis.com).
In This Chapter
Recommended Test Equipment.................................. 14-2
Power On Faults.......................................................... 14-3
LED Fault Indications .................................................. 14-4
Dry Contact Alarm Indications..................................... 14-7
Alarmed Conditions ..................................................... 14-8
Copper Lines Troubleshooting .................................. 14-29
Ethernet Service Troubleshooting ............................. 14-81
Management Connection Problems .......................... 14-95
Resolving Management Connection Problems ....... 14-100
Resolving Configuration Considerations Due to Dipswitch Settings 14-105
14-1
Troubleshooting
14-2
Line test equipment, such as HP Transmission Impairment Measurement Set (HP TIMS),
for testing the copper pairs if required
Power On Faults
Troubleshooting
Power On Faults
No Power Indication
Symptom: All front panel LEDs are off.
Corrective action: Check the following:
14-3
Troubleshooting
Status
Recommended Responses
Power
ON
--
Status
14-4
Alarm
LNK
(ETH
port)
ACT
MLP
Troubleshooting
--
--
OFF
- Normal if link is down, or port is disabled.
- Otherwise, refer to recommended actions.
--
14-5
Troubleshooting
LNK
(DSx1
port)
ERR
(DSx1
port)
14-6
Troubleshooting
Critical or Major fault (including power input failure) activates (closes) the
corresponding alarm output of the ML600 device.
PFU HW fault (including power input failure) activates (closes) the PFU alarm output.
PFU port faults (e.g. over current, voltage limit) do not cause PFU's dry-contact alarm
output to activate. PFU port faults can be seen in the PFU pane (on page 13-15),
Topology pane (on page 13-45) and Topology Test pane (on page 14-53).
14-7
Troubleshooting
Alarmed Conditions
Alarmed Conditions
Troubleshooting Workflow
When an alarm condition occurs, one of the system front panel Critical, Major or Minor
alarms LEDs lights up according to the highest alarm severity that presently exists in the
system. The condition is also indicated on the MetaASSIST View system pane, see the
following figure.
To troubleshoot the alarm using MetaASSIST View:
1. As illustrated in the following figure, in the system alarms and conditions table (at the
bottom of the window), double-click the alarm (any where in the row). As a result:
The pane corresponding to the selected component is invoked. The pane provides
detailed information on the item.
14-8
Alarmed Conditions
Troubleshooting
Field Descriptions
The following table provides the field descriptions for the alarms and conditions table for
both the system pane and component pane.
Table 68: Field descriptions for alarms and conditions table
Field Name
Severity
The Notification code of the alarm or message and the MTTR (Mean Time To Repair)
requirement according to GR-474-CORE is as follows:
CRCritical - 45 minutes MTTR;
MJMajor - 90 minutes MTTR;
MNMinor - 120 minutes MTTR;
NANot Alarmed;
NRNot Reported.
For additional details on notification codes, see About Alarm Severity and
Conditions (on page 13-7).
Note: NA and NR are not displayed in MetaASSIST View unless their status is
change to CR, MJ or MN.
Condition
Type
The condition that caused the alarm or message. As will be explained later in this
section, the Condition Type field plays a key role in determining the troubleshooting
procedures.
AID
The Access Identifier of the component (entity) involved with the alarm or message.
The components can be one or more of the following:
System: COM;
Equipment: ML600;
Ethernet ports: ETH-{1-5}, COLAN (MGMT);
High Speed Links: HSL-1/2;
Modem Line Ports: MLP-1-{1-8};
Environmental Alarm Input: EC-1/2;
External Controls: CC-1.
The effect that reported event has on system operations. Possible values are:
SA means event is Service Affecting (i.e., it caused part or all traffic to be dropped);
NSA means event is Not Service Affecting (e.g., redundant power input failure).
SA/NSA
Time
Description
14-9
Troubleshooting
Alarmed Conditions
Field Name
Location
(Loc.)
Direction
(Dir.)
Note: The severity of a condition type is user configurable. The severity of each condition
type, mentioned in the following troubleshooting tables, is according to factory setup.
14-10
Alarmed Conditions
Troubleshooting
Description
Recommended Troubleshooting
Procedure
NOSETUP
No initial setup;
UPGRDIP
14-11
Troubleshooting
Alarmed Conditions
Description
Recommended Troubleshooting
Procedure
HWFLT
Hardware fault;
Replace ML600.
AID ML600
PROGFLT
AID ML600
14-12
Alarmed Conditions
Troubleshooting
Condition
Type
Description
Recommended Troubleshooting
Procedure
UEQ
Unequipped module;
AID SFP
14-13
Troubleshooting
Alarmed Conditions
Condition
Type
AID
Description
Recommended Troubleshooting
Procedure
HWFLT
SFP
14-14
Alarmed Conditions
Condition
Type
Troubleshooting
AID
UNKNOWN SFP
Description
Recommended Troubleshooting
Procedure
EOPTMIS
SFP
14-15
Troubleshooting
Alarmed Conditions
Description
Recommended Troubleshooting
Procedure
HIATTN
14-16
Alarmed Conditions
Troubleshooting
Condition
Type
Description
Recommended Troubleshooting
Procedure
LOSW
14-17
Troubleshooting
Condition
Type
Alarmed Conditions
Description
Recommended Troubleshooting
Procedure
QUALFLT
14-18
Alarmed Conditions
Troubleshooting
Description
Recommended Troubleshooting
Procedure
COPPERMI
S
14-19
Troubleshooting
Alarmed Conditions
Condition
Type
Description
Recommended Troubleshooting
Procedure
HSLDIAG
HSLDWN
14-20
Alarmed Conditions
Condition
Type
Description
HSLFLT
HSL is faulty;
LOWBW
Troubleshooting
Recommended Troubleshooting
Procedure
14-21
Troubleshooting
Alarmed Conditions
Condition
Type
Description
PLANFLT
Planning fault;
Recommended Troubleshooting
Procedure
14-22
Alarmed Conditions
Troubleshooting
Condition
Type
Description
Recommended Troubleshooting
Procedure
RPWFLT
CPEMISM
14-23
Troubleshooting
Alarmed Conditions
Description
Recommended Troubleshooting
Procedure
LOS
AID = ETH<ID> or
COLAN
(MGMT)
14-24
Alarmed Conditions
Troubleshooting
Condition
Type
Description
RFI
(AID=ETH)
Recommended Troubleshooting
Procedure
14-25
Troubleshooting
Alarmed Conditions
Condition
Type
Description
CFLT
(AID=MEP)
14-26
Recommended Troubleshooting
Procedure
Alarmed Conditions
Troubleshooting
Description
Recommended Troubleshooting
Procedure
CLKFLT
Do the following:
Check for another alarms (e.g. LOS, LOF or
AIS) on the same DSx1 port, if exist fix them
first
Check that the received clock quality
matches the configured clok quality.
Check that the received clock is valid (e.g.
clock accuracy, clock's jitter).
(AID=DSx1 {14})
LOS
(AID=DSx1 {14})
AIS
(AID=DSx1 {14})
14-27
Troubleshooting
Alarmed Conditions
LOF
(AID=DSx1 {14})
RAI
(AID=DSx1 {14})
CESLOS
(AID=DSx1 {14})
14-28
Do the following:
Check that framing configuration on ML650
and 3rd party mating equipment (e.g.
customer's premises equipment), are
configured to the same framing.
Troubleshooting
SHDSL Loopback (on page 14-39) used for BER measurements. A data signal
transmitted from the CO is returned (loopback) at a selected point (specified Repeater or
CPE) and the BER measured.
Audible tone injection (on page 14-37) a tone generated by the ML system is injected
in the NEND (near end device) and tracked on the far side for localization of a specific
pair.
TDR Test used to detect and locate (approximate location) shorts and opens in one
copper-pair (with or without Repeaters) at a time. The test is performed from the CO
towards the CPE side.
Topology Test (on page 14-53) - Used for detailed, hop-by-hop analysis of one copperpair (with Repeaters) at a time. Information on various parameters such as voltage,
dipswitch settings, etc. is given on each segment as it is tested.
Identifying the existence of a problem can be done through the Topology Glance View (on
page 13-45) monitoring tool.
14-29
Troubleshooting
The Topology glance view tool can display three types of information:
14-30
Line performance for both N (toward network or NEND) and C (toward customer or
FEND) sides of the repeater.
Line inventory per hop. For repeated lines only, repeaters mismatches indications are
provided.
Troubleshooting
For example, the following figure shows the result Topology Glance View for an HSL. Note
that no information is displayed on the CUST side of Hop-1 and after it. The problem is
apparently between Hop-1 and Hop-2 (can be a line problem between the two Hops or a
problem in Hop-2 itself).
14-31
Troubleshooting
ML600 system with HSL in -O (Office) mode provides automatic discovery of linked ML600
system (with HSL in mode -R (Customer)). It can be monitored using MetaASSIST View
panes "HSL port" and "MLP ports" if all Copper Lines bonded within the HSL are terminated
on the same system.
The Serial Number of the STU-R system is used to identify the linked ML system. In
installations where HSL -O is terminated on multiple -R (Customer) destinations, Ethernet
service and in-band management traffic will not be available. The problem is reported by
COPPERMIS Alarm on a specific HSL, which discovers the mismatch.
14-32
Troubleshooting
Reconnect each copper line with a different Serial Number discovered on distant end.
Note: the MLP provides Serial Number discovery immediately after synchronization.
Reconfigure the HSL (on local side) to exclude the incorrectly terminated copper lines.
De-calibrate the HSL (Cancel Calibration)
Delete the MLPs from the HSL
Re-calibrate the HSL.
In the Network Element tree, open Modem Ports. The Modem Ports pane opens.
From the table, double-click a row. The Modem Port MLP pane opens in the work area.
To suspend the modem port, select Suspend. A warning message appears. Click Yes.
To restore the modem port, select Resume.
Repeat steps 1-4 for additional modem ports.
14-33
Troubleshooting
Note: You also have access from the Navigation tree as follows: Open Modem Ports, MLPs.
The Modem Port MLP pane opens in the work area.
For detailed information on how to use the line tester to perform the procedures in this
section, refer to your line-tester documentation.
Line-impairment Test
About this test: It is always a good practice to verify that all cable pairs are fault free. Good
continuity between the two Actelis systems ensures optimal performance of the system.
Procedure: Use TIMS and follow standard telco operating procedures to ensure that all
copper facilities are free from physical and electrical faults, such as: opens, splits, grounds,
and load coils.
Crosstalk Test
Procedure: Use the line tester to transmit a signal with the following characteristics over one
of the lines and examine the signal on all adjacent lines:
14-34
Troubleshooting
Expected results: For optimum HSL performance, the crosstalk test results should be for
twisted pairs (not Quad cables) as follows:
Transmit Frequency (kHz)
Isolation (Attenuation)
80
67 dB
160
60 dB
196
58 dB
320
53 dB
If the test result is 10 dB less than the level specified in the previous table, the line should
not be used.
Noise-to-ground Test
About this test: This test ensures that the lines can withstand signal interferences from
electrical sources, such as radio stations, transformers, electric motors and power lines.
Procedure: Follow the instructions in your line-tester documentation to test the lines for an
input impedance of 135 Ohm. Make sure that the sleeve or shield of the cable for the lines
you are testing is grounded to an earth-ground point.
Expected result: The noise-to-ground test result should be 54 dBrn.
14-35
Troubleshooting
Qualification by ML NE
The line qualification routines are part of the calibration process. The results are reported in
the Modem Port Details pane (see the following figure). This report provides the
information for determining whether a line should be dropped or included in the HSL.
14-36
Qual. at ... kbps - Adjusted- Rate adjustment process is completed and the rate is
reduced;
Troubleshooting
Table 75: Possible causes for failures reported in Details for Modem Ports pane
If the Qualification parameter indicates
this failure type...
In repeated line environment the audible tone is limited on the last segment. i.e. the
segment between the last hop and CPE doesn't provide audible tone.
An audible tone can be injected to several suspended MLPs at a time. Regular tone
(1KHz) is applicable for multiple MLPs. Alternating tone (available on MLU-32 only)
cannot be used for several MLP at a time.
14-37
Troubleshooting
1.
2.
3.
4.
5.
6.
7.
8.
In the Network Element tree, open Modem Ports. The Modem Ports pane opens.
From the table, double-click a row. The Modem Port MLP pane opens in the work area.
Click Suspend. A warning message appears.
Click Yes to confirm the warning. The Suspend button toggles to Resume and a
maintenance icon appears in the pane and in the navigation tree. The modem state is
changed to Suspended.
To inject the audible tone, click Operate Tone. The modem state is changed to
Suspended-Tone.
To release the audible tone, click Release Tone.
Click Resume.
Repeat steps 1-8 for additional modem ports.
Note: You also have access from the Navigation tree as follows: Open Modem Ports, MLP.
The Modem Port MLP pane opens in the work area.
14-38
Troubleshooting
SHDSL Loopback is used to test suspected (reduced quality) synchronized modems and find
the problem location. SHDSL loopback test is operated from a selected modem at the CO
side and applied to that modem in a specific selected test location. CO modem instructs the
selected location remote modem to revert back (to the CO modem) all the received traffic (L1
traffic) on this modem. The CO modem continuously injects test signal(s) (i.e. traffic with a
specific pattern) over the copper pair connecting between the modems, until the Loopback
test is manually released. The CO modem analyzes the reverted back traffic pattern. All
mismatches are registered and reported as Bit Error Ratio (BER) in the test result. In case of a
modem with low rate, a few minutes of test may be required in order to achieve a reliable
BER result.
This test can be performed either on non-repeated or on repeated links (links extended using
XR239 Repeaters):
For a non-repeated link the test is performed only once, between two termination points:
the CO modem and the CPE modem.
For repeated links the test is performed hop-by-hop (i.e. each hop is tested individually by
the user, applying: Start, View Result and Stop per tested hop). The hops may be tested
sequentially, starting from the same (suspected) CO modem, and on each of the remote
modems locations (1st hop, 2nd hop etc.) hops down to CPE.
Moreover, for each hop, the SHDSL loopback can be applied on both sides of the repeater:
On the repeaters NET (network) modem port this is the port on the CO (and Network)
side
On the repeaters CUST (customer) modem port this is the port on the customer side.
SHDSL Loopback applied on the NET port is known as Facility Loopback, where repeater
hardware is almost not involved (except NET port Transceiver).
SHDSL Loopback applied on the CUST port is known as Equipment/Terminal Loopback,
where repeater hardware (terminal) is involved and may affect the test result.
When applying the test on both NET and CUST ports of the same repeater, a conclusion
regarding the faulty repeater on the current hop can be achieved. A conclusion regarding
copper pair faulty conditions is more complex, as the problem may exist on either:
14-39
Troubleshooting
Note: Suspending the modem and performing the test does not suspend services supplied by
the corresponding HSL, although the link throughput is reduced (proportional to the
suspended modem throughput).
In the Configuration area, click Suspend (available on single MLP pane only)
or
In the Alarms area, click the Configure Alarm button, and select In Maintenance
All Alarms Disabled (available on both - single and multiple MLP panes using group
operations).
Both operations will stop Service traffic on the modem and prevent the modem alarms.
14-40
Troubleshooting
3. In the MLP pane Configuration area, click Operate Loopback. The Operate Loopback
dialog appears.
4. From the Location field drop-down menu, select the relevant location on which loopback
is to be performed:
5. Click OK. This will initiate the test, returning the traffic that arrives at the chosen
location, back towards the -(O) MLP (it may take up to 60 sec until the test begins). The
State (of the Modem) parameter in the Configuration area should change to Suspended Loopback Activating (LINE-x) followed by Loopback Active.
6. When the MLP state changes to Suspended - Loopback Active, the test results can be
monitored.
To monitor the test results:
The dialog showing the Bit Error Rate (BER) will be invoked.
14-41
Troubleshooting
TDR Test
ML TDR (Time Domain Reflectometry) test is used to detect the existence and location of an
impedance mismatch such as short, open or bridge-tap on copper-pair line. The test is run on
a single copper-pair at a time, from the CO or from any hop (Repeater) on the line (towards
CPE direction). The test results are then graphically displayed for analysis.
Copper pair, like any transmission line has its own characteristic impedance. The impedance
of the cable is determined by the conductor diameter, the spacing of the conductors from each
other and the type of dielectric material or insulation that is used to separate the conductors.
TDR searches for a change in impedance. This can be due to a variety of causes such as cable
damage, change in cable type, improper installation, and even manufacturing flaws.
TDR sends electrical signals down the cable and samples the reflected energy. Any
impedance change will cause some energy to reflect back toward the TDR and will be
displayed. The amount of impedance changes and the distance to the line impairment
determine the amplitude of the reflection.
The received information is displayed as a waveform or cable "signature". OPEN or SHORT
impairments are indicated by high or low impedance change respectively and have typical
waveform signatures, that are graphically displayed on the TDR screen. From the TDR
waveforms the impairment type and its location can be determined.
14-42
Troubleshooting
A graph of the line condition and reference graphs are displayed. Available references are:
open line, shorted line, terminated line, bridge tapped line, line with loading coils and line
with short to ground. The results can be analyzed using zoom tools (for locating the distance
of the fault from the start point of the test), and reference graphs that show typical copperpair impairments on the line.
Test graphs can be saved for reference or comparison, either to the ML device from which
they can be reviewed via the TDR tool, or to an external *.CSV file for analysis through an
external application.
Note: ML system can keep two TDR test result per line, one is the last TDR test on the line
and one is the saved (if saved) TDR test of the line. Performing new TDR test (even if
performed on a different hop) overwrites existing (current) TDR test result. Saving to history a
new TDR test result overwrite the existing "history" TDR test result. In order to keep more
TDR test results per line (e.g. for multiple hops) the results shall be exported to PC (saved in
*.CSV format).
In the pane Configuration area, click Suspend. If the MLP is active, a Warning
appears.
Click Yes to confirm the suspension. This sets the MLP in Maintenance mode in
which alarms are not reported. Note that the MLP suspension enables the TDR test
button in the Details area.
3. In the Details area, click the TDR test button. The TDR Test Dialog (on page 14-45) is
invoked.
14-43
Troubleshooting
When run from the Topology Test dialog, the test is implemented as follows:
If the ML system is synchronized up to the required hop (segment) in this case the TDR
test is performed immediately upon request on the selected pair and current location of
the test.
If the ML system is not synchronized up to the required hop (segment) (probably due to
link collapse caused by PFU port shutdown) - synchronization will be performed in the
background (transparent to the user) up to the required hop. The TDR test will take a little
longer (several minutes), where the test progress would be reported on the screen.
1. In the Network Element tree, expand HSLs and choose the HSL to be tested. In the
invoked pane click Topology Test. The following screen will be displayed.
14-44
Troubleshooting
Current Test Configuration - used to select the point up to which the test will be run and
save graphs to *.CSV files (for reviewing via an external application).
History Graph - used to save graphs to the ML device (for reviewing via the TDR dialog)
Display Area - shows the currently run graph (Blue) and may also show a History graph
(Red). Refer to Analyzing the Graph (on page 14-48) for details.
Graph Analyzing - shows examples of graphs for short, open, Tip to ground, bridge tap
and loading coil. Use these for reference to identify types of faults.
Display attributes area at the bottom of the window - used to define display attributes and
refresh the view.
14-45
Troubleshooting
Description
Location
Start test
Graph saving options
Measurement Units*
Apply Filter*
Velocity Factor*
The Velocity Factor (on page 14-47) value of the cable being
tested (e.g. 0.58 for AWG26 jelly filled cable):
Custom - enter the required value. To calculate the velocity
factor with a known copper loop refer to Velocity Factor (on
page 14-47).
By Cable - choose the cable type.
To update the display according to the new Velocity Factor, click
Update Graph.
Zoom-in Scale
* It is not necessary to enter the parameters each time the test is run. The TDR test runs
according to the last settings.
1. Access the TDR dialog either from the Modem Ports pane (on page 14-43) or from the
Topology Test dialog.
2. Under Current Test Configuration, select the Location up to which the test will be
performed:
14-46
Troubleshooting
3. Define the display attributes using the parameters in the bottom area of the dialog.
Note: It is not necessary to enter the parameters each time the test is run. The TDR test
runs according to the last settings.
Apply Filter - This applies a filter to the displayed signal, improving visibility of
impairments in most cases - especially for shorter distances. This filter is enabled by
default and may be disabled if required.
Enter the Velocity Factor value or the cable type (if cable type is provided) of the
cable being tested (e.g. 0.58 for AWG 26 jelly filled cable). See Velocity Factor (on
page 14-47) for typical values and more information.
To update the display according to the new Velocity Factor, click Update Graph.
4. Click Start Test (in the top area). The test results will be graphed according to the
display attributes.
5. Zoom-in and analyze TDR test results, referring to the Short and Open sample graphs.Try
to locate a similar fault pattern within the given TDR measurement. Refer to Analyzing
the Graph (on page 14-48).
6. You can save the current graph and compare it to previously saved graphs using either
the TDR graphical display or an external application (for *.CSV files). See Saving and
Comparing Graphs (on page 14-50).
7. After completing the analysis, click Close to return to the MLP pane and in the pane.
8. Press Resume to return the modem (MLP) under test to service.
Velocity Factor
The time that it takes a signal to travel to the fault and back is used as reference. If the speed
of propagation of the electrical signal in the copper line is known, it can accurately display
the distance to that fault. To compensate for the fact that electrical signals travel at different
speeds within different types of cables, a Velocity Factor (VF) is used.
The VF is a specification of the speed at which a signal travels through the cable (compared
with the speed of light). This parameter varies for different types of cables and is a required
parameter when using TDR for fault location finding. By entering the correct VF or the cable
type, the instrument is calibrated to a specific cable.
Table 77: Typical TDR Velocity Factor Values
PIC
19 Gauge
.72
14-47
Troubleshooting
Jelly Filled
Pulp
22 Gauge
.67
24 Gauge
.66
26 Gauge
.64
19 Gauge
.68
22 Gauge
.62
24 Gauge
.60
26 Gauge
.58
22 Gauge
.67
24 Gauge
.68
26 Gauge
.66
Note: in case that the VF in not known, it may be measured by the following procedure:
1. Test TDR over a known copper pair length.
2. Set the VF to 1 and find the open location in the TDR figure.
3. VF equals to the actual loop length divided by the measured loop length
For example if we test an open loop with loop length of 3,000 feet and measure by the TDR
(when VF set to 1) an open at 4,500 feet than the VF of the cable is 3,000/4,500 = 0.66.
TDR Accuracy. Variations in the VF of the same type of cable are not uncommon. The VF
of a cable can change with temperature, age, and humidity. It can change approximately 1%
for every ten degrees centigrade of change from room temperature. It can also vary from one
manufacturing run to another. Every new cable can vary as much as +/-3%. With these
changes the VF changes and therefore the apparent length of the cable also changes. When
using a known length of cable to determine VF, be certain to use at least 500 feet (150 m).
The longer the test cable, the better.
14-48
In the field Zoom-in X Scale, define the area of interest by entering the From and To
values.
Click Zoom. The area of interest will be expanded on the graph and can now be
compared to the Short and Open sample graphs at the right of the display.
Troubleshooting
The following figure shows a short located at about 800 ft, where the fault slope begins to
change.
The following figure shows an open located at about 7,000 ft, where the fault slope begins to
change.
14-49
Troubleshooting
To an external storage directory as a *.CSV file - for review via an external application
ML system can store two TDR test result per line: the last TDR test on the line and the saved
(if saved) TDR test of the line. Performing new TDR test (even if performed on a different
hop) overwrite existing (current) TDR test result. Saving to history a new TDR test result,
overwrites the existing "history" TDR test result. In order to keep more TDR test results per
line (e.g. for multiple hops) the results shall be exported to PC (saved in *.CSV format).
Saved graphs can then be reviewed and compared. For example, after a fault has been
corrected a 'before' and 'after' display can be compared.
Table 78: Graph Management Options
To...
Do this...
14-50
Troubleshooting
2. During installation of the XR239 use LED indication to troubleshoot power feeding per
segment and line synchronization indication as described in the XR239 Quick Installation
Guide. Prior to the XR239 troubleshooting via LEDs, ensure that the ML unit on the CO
is properly configured (see step 5 in Repeated Copper lines guidelines).
3. Use Copper Lines LED indication on the ML unit to troubleshoot synchronization status
of the repeated copper lines as follows:
Steady green for synchronized on all segments down to the CPE unit copper;
Alarm LED is steady Red/Yellow, indicating problems on HSL (if all MLPs are not
synchronized - HSLDOWN) or MLP (LOSW alarm is raised per modem);
Modem LED is OFF for disabled or not assigned to HSL modem (MLP).
Improper connection between all components between ML and first hop XR239: ML
and PFU-8, PFU-8 and MDF, Cut-line between CO and first XR239 unit;
NET port failure of the 2nd XR239 unit or HW failure of 2nd XR239 unit.
6. Use View Line Inventory (on page 13-66) dialog to view line details for a specific
modem. This includes:
Location - line segment (determined according to the port and location fields)
Serial number, catalog code (CLEI), and Model of the equipment at each Hop.
14-51
Troubleshooting
7. Use the Topology Glance View dialog to provide analysis information on the spans. This
includes:
14-52
Line performance (SNR, loop Attenuation, etc.) for CO modems, both N (toward
network or NEND) and C (toward customer or FEND) sides of the repeaters and
CPE modems.
Troubleshooting
8. The Topology Glance view also indicates common faults of repeated line such as
DUO/ADUO mismatch and split pairs between Hops. For detailed information see
Topology Glance view (on page 13-45).
9. For advanced troubleshooting, refer to Topology Test (on page 14-53).
Topology Test
The Topology Test tool is used to troubleshoot Links extended with XR239 repeaters. This
tool is designed to allow technicians at various levels to source the failed segment and
determine its cause. It improves "Ease of Deployment" by reducing turn-up time.
The Topology Test tool can be used to:
Run step-by-step tests to detect the source of power budget faults such as shorted lines
Display information on repeater status and configuration, and on PFU status and
configuration.
XR239 and PFU dip switch settings used to verify configuration remotely
Voltage and current values at PFU ports used to locate various types of shorts, opens,
etc.
14-53
Troubleshooting
Note: In ML version 6.0 and higher, it is not required to modify XR239 repeater's dipswitches
for single-side fed systems.
The Topology Test can be performed on several spans at a time, HOP by HOP.
Figure 31: Illustration of four spans with four hops per span
A SPAN is considered per single MLP port from CO (NEND) to CPE (FEND) over twisted
copper-pair. The following figure shows two spans between the CO side and the CPE side:
14-54
Troubleshooting
14-55
Troubleshooting
By testing one segment (hop) at a time, the Topology Test tool can isolate the fault to a
specific hop by analyzing the detailed information for that hop from dipswitch
configuration to power levels at various points.
14-56
Duo parameter links between two copper-pairs that are terminated on the first repeated
Hop by the same XR239 unit. (see Modem Line Ports (MLP) Configuration).
Troubleshooting
MLPs to be tested must be Suspended (maintenance mode) this can be done from the
Topology Test dialog (on page 14-61) or from MLP pane (on page 14-33).
NOTE: Line Test CANNOT run on suspended MLPs that are running other
troubleshooting tests such as tone injection, loopback, etc.
The Number of Repeaters fed from CO side - in case that the XR239 dipswitches are in
their default position (no setting of power feed Loop for last repeater) it is required to
configure the number of CO fed repeaters in the span.
Main area (on page 14-58) - shows information on each MLP and each tested hop. Used
to select the spans to be tested. As each Hop in a span is tested, the test status is displayed
under the relevant HOP column. Refer to Test Results (on page 14-60) for details.
Test Control Options (on page 14-61) buttons for running the test, running TDR on a
selected segment and for suspending the MLPs.
14-57
Troubleshooting
Details area (on page 14-62) shows detailed information for selected MLPs and
detailed information on the hop (XR239 INFO) that the test reached.
14-58
The check box applies to Repeater Line Test (i.e. Start, Stop and Continue Test).
Troubleshooting
The line selection (only single line can be selected at a time) applies to the Suspend and
TDR functions.
For each tested segment (Hop) the displayed data indicates the segment topology (with or
without Repeaters), status of test and failure description.
Row selection - by highlighting, is used to choose the span on which other operation will be
performed - MLP suspension, Turn Off Power and running TDR test.
The test is run from the CO to the first Hop and on to next Hops step-by-step until a CPE is
detected.
The following table describes how to analyze the data:
Table 79: Analyzing the Data
Column
Description
CO MLP AID
ID of MLP port connection at CO. i.e. MLP-1-9 corresponds to MLU card 1 and
copper-pair 9. For ML600 and ML58N RevB it is always MLP-1-x {x=1..8}
MLP State
14-59
Troubleshooting
CO PFU Port
HOP 1..4
CPE MLP ID
Then..
Black XR239 ID
Gray XR239 ID
No Signal !
No sync !
PFU Fault !
Test failed, PFU port failed due to power problem on the failed
segment (e.g. earthed conductor).
14-60
Troubleshooting
The first section (left side) is used to control the Topology Test progress:
Start/Continue test
Stop test.
The second section (right side) is used to perform the following operations:
Description
Start/Continue Test
Stop Test
Stop stops the test. Used to reset and enable starting the test again.
Suspend
14-61
Troubleshooting
TDR
Runs TDR test on the span of the HIGHLIGHTED row of the current
hop location.
Detailed Information
This section provides details of the selected spans at the current Hop location.
Note: For efficient troubleshooting the selected MLPs shall be the DUO pairs.
The parameter descriptions in this section are grouped according to parameter types:
14-62
Troubleshooting
Description
MLP AID
MLP State
MLP Status
Description
Actual MLP that is connected at the first Hop to the same XR239
repeater. This value may differ from the "Configured Duo MLP
AID" in case of wrong configuration or wrong wiring.
Description
Actual Signal to Noise Ratio margin (in dB) for the copper lines.
Low margin indicate poor link quality.
MLP Loop Attenuation, dB Actual measured loop attenuation (i.e. the transmitted power less
the received power).
MLP Error Ratio, %
14-63
Troubleshooting
Description
ID of PFU port assigned to MLP (i.e. PFU-1-1 is for PFU unit '1'
port-1.)
For ML600 the PFU AID is always PFU-1-x with x={1..8}
Description
14-64
Troubleshooting
Description
Actual Current, mA
PFU-8
> 54 mA
> 60 mA
PFU-8C
None
> 57 mA
Under Load
< 3 mA
< 3 mA
PFU-8E
> 108 mA
> 60/120 mA
(dipswitch
configurable)
< 7 mA
Future option.
PFU Port output Voltage, Tip to Ground, Ring to Ground and Tip
to ring unbalance.
Measured PFU port TIP/Ring output voltage may greatly differ
from typical value due to leakage to ground in either Tip or Ring
wire. In such cases Unbalance would be large as well.
Description
PFU-8 or PFU-8E
14-65
Troubleshooting
Description
Description
Details
Data validity
XR239 CLEI
XR239 HW Revision
XR239 HW Revision
XR239 SW Revision
XR239 SW Revision
Details
14-66
Troubleshooting
Details
XR239 Port 1
DipSwitch(DS#1)
XR239 Port 2
DipSwitch(DS#2)
Details
XR239 Port ID
Network side Signal to Noise Ratio margin (in dB) for the copper
lines. Low margin indicate poor link quality.
14-67
Troubleshooting
Customer side Signal to Noise Ratio margin (in dB) for the copper
lines. Low margin indicate poor link quality.
14-68
It is recommended to checkmark SPECIFIC MLPs (the failed MLP and it's DUO
port) in case that the failed MLPs are known.
Troubleshooting
Use the scroll-bar at the right of the area view to see the rest of rows. Only suspended
MLPs can be tested (Highlight and click Suspend if the MLP is not suspended already).
NOTE: At this point, disregard any fault indications of the MLP State or CO PFU Port
state columns. These do not necessarily indicate a fault in the corresponding elements.
Begin running the test on the first Hop (according to the following step) and on following
Hops to locate the source of the fault.
3. In the Test Control Options area, click Start Test (the button toggles between Start and
Continue). The response will be according to the following:
If all tested copper pair lines prerequisites have not been met, the relevant warning
message will appear.
If all prerequisites had been met, testing will begin on the first hop. While the test is
being performed on a hop, an "In progress" will appear in the corresponding Hop
field.
14-69
Troubleshooting
After the test is completed on the hop, information indicating Test Results (on page 1460) will be displayed in the corresponding field. For example, if as illustrated below, a
hop is tested OK, the XR239 ID is displayed in black in the field.
4. Refer to Main Area Options (on page 14-58) for a description for each of the fields in
each row: i.e. CO MLP ID, CO PFU Port, Hop-n, etc.
5. If a PROBLEM was indicated on the hop field (i.e. the field showed a value other than
XR239 ID in black):
NOTE: Any additional faults that are detected (during the same Line Test) may or may
not be due to the same fault. Therefore, it is required to run the test after resolving each
problem.
6. If no problems were detected on the first HOP, click Continue (the Start button switches
to Continue after starting the test) to test the next HOP.
The last CPE MLP ID will indicate that the last segment in the tested span is reached
(CPE PFU port is used only for dual side feeding applications, using PFU-8E.
14-70
Troubleshooting
3. Perform the analysis end-to-end: MLP Port, PFU Port and module, XR239 in all hops
and CPE MLP Port in order to identify the source of the fault.
To do so:
Verify configurations for each relevant module in the line; i.e. MLP Configuration,
(on page 14-63) PFU Dipswitch Configuration (on page 14-64) , XR239 Dipswitch
settings (on page 14-66), etc
Verify correct wiring between CO, Repeaters and CPE using the ID of the repeaters
and the modem ports through the whole span.
Verify power for each relevant span i.e. PFU Port Current and Voltage
Parameters (on page 14-64), and for the PFU Module Info (on page 14-65).
Run TDR test to locate faults in the line. The TDR test is run on the hop at which the
Line Test was stopped.
Refer to Common Faults (on page 14-71) for descriptions of common faults and
how they can be identified and analyzed using the Topology Test.
Common Faults
The next section contains possible common faults and how to detect them.
Mismatch between Configuration and Connections
Description
The configured values of the copper-pairs connected between the CO PFU and the first
XR239 Repeater (DUO parameter) do not match the actual connections.
For example, it is recorded that MLP 1-2 is the DUO of MLP1-1, when in fact MLP 1-3 is
the DUO of MLP 1-1.
14-71
Troubleshooting
Fault Indications
In the Details area of MLP 1-1, the Duo MLP AID is not equal to the Actual Duo MLP ID
(see MLP configuration at MLP Info).
NOTE: This fault is also indicated via the Topology Glance view, for additional details see
Topology Glance view (on page 13-45).
14-72
Split/Re-split (on page 14-74) in the same pair tips split in the same pair and
reconnected properly on next connection
pairs swap between two CO/CPE links (on page 14-74) two pairs split between two
repeaters
Troubleshooting
Split Pairs
Description
The two copper-pairs from one repeater are split between two repeaters on the next HOP.
14-73
Troubleshooting
Split/Re-split
Description
The Tip side (or Ring) of two different pairs are crossed.
In case that the split/re-split introduces large amount of cross-talk (depends on length and
topology of pair's split) NO SYNC! Would be displayed on HOP where loops are crossed
(i.e. HOP 2).
In case that the split-resplit introduces small amount of cross-talk (depends on length and
topology of pair's split) poor performance (i.e. rate and SNR) would be achieved
(compared to other pairs) on the HOP where loops are crossed (i.e. HOP 2).
14-74
Troubleshooting
Split location can be identified using the Topology Testing, Hop's ID won't match (DUO
is violated) in the split location.
Span power is split between 2 XR239 on the same hop. This may cause power deficit for
XR239 on a next hop check PWR fields of Hop.
Open Lines
Description
Open line can be due to a range of reasons:
In the figure below the open is located on the second segment; however, it may be located in
any segment and any location within the segment.
If the cut is on the first Hop, an "Underload on PFU" message will appear.
14-75
Troubleshooting
Shorted Lines
Short on Same Pair
Description
Short between Tip and Ring of the same pair (loop). In the figure below the short is located
on first segment; however, it may be located in any segment and in any location within the
segment.
Fault Indications:
PFU Fault! displayed on failed HOP (Hop after the short problem)
In PFU port details Too high Current fault is raised. In PFU port details Too high
Current fault is raised (fault may be Current or Last, depending on short location, first
hop or following hops).
14-76
Troubleshooting
Fault Indications:
PFU Fault indication is provided on the failed line (PFU Fault may be also indicated on
the DUO line as seen in the figure below)
The whole span collapse, previously known AID are grayed and AID of the hop after the
failure is not known.
In details section the PFU port fault would be either "voltage Limit" or "Earthed
conductor", the alarm type depends on short location (how close to PFU) and loop
topology. The alarm is indicated as current in case of short in first segments or Last in
case of short after the first hop.
14-77
Troubleshooting
Loading Coil
Description
Loading Coils are added on long copper loops to improve voice quality; however, they
prevent broadband service traffic and thus must be removed. In the figure below the loading
coil is located on first segment; however, it may be located in any segment and any location
within the segment.
Fault Indications
The hop after the loading coils is not reached and a No Sync ! failure is indicated.
Note: The loading coils unlike cut line provide no Sync fault indication (and not no Signal) and
enable power feed.
Run TDR test to locate failure location in the segment (Loading coils has same graph as
cut line).
In case of multiple loading coils remove them one after the other.
Bridge Tap
Description
A bridge tap is hanging on sections of pairs as seen in the following figure. The bridge tap in
the figure below
is located on the first segment; however, it may be located in any segment and any location
within the segment.
14-78
Troubleshooting
Fault Indications
There are various indications for Bridge Tap fault, where the indications vary according to
the loop topology (i.e. bridge-tap location and bridge-tap length). The performance of the
span is usually degraded as follows:
Rate of span is lower than other spans, where in extreme cases the span may not even
sync
Repeater CLEI code and HW revision of old and new repeaters is provided.
Check the dipswitch settings provided by the Service is not available Topology Test.
14-79
Troubleshooting
Number of CO fed units kept in default value (4 hops) and there are less than 4 hops.
CO upgraded to R6.0 from previous SW versions (and repeaters are replaced in the
span)
Expected results
When the Continue test is applied to last repeater, the PFU fails due to current limit (CPE
overloads the PFU port).
Troubleshooting procedure
If the actual number of hops is known, verify that the number of CO FED hops is
configured correctly.
If the actual number of hops is unknown, run the TDR test (on the last detected hop)
to check existence of Tip/Ring short or normal termination. In case that normal
termination is detected, the problem is that the number of hops is not configured
correctly.
14-80
In case that the actual number of hops is known, verify that the number of CO FED
hops is configured correctly.
In case that the actual number of hops is unknown, run TDR test (on last detected
hop) to check existence of cut line or normal termination. In case that normal
termination is detected, the problem is that the number of hops is not configured
correctly.
Troubleshooting
Ensure that the planed Ethernet topology done prior to the configuration was
implemented correctly. Especially check and implement the following:
Ethernet Type of SE-VLAN tag (default 0x8100 Q-n-Q Cisco) can be changed, but
should be acceptable by equipment attached.
MTU size of frames each new SE-VLAN tag adds to the frame another 4 bytes.
Calculate the largest expected frame and check that it is acceptable in a whole
Switching Network.
Handle the No-Loop Ethernet Topology - use Spanning Tree Protocol if there are
redundant connections. Separate Customer and Provider Bridges Control planes
configure rules of L2CP.
2. Remember that Management traffic plane may be affected by the Service traffic plane
you select. Start with Management plane, not Traffic plane configuration.
3. Start from the most remote NE (from the Management Host).
4. If Management connection is lost, restore the connection using Non-IP access to Linked
by HSL NEs. The channel works from CO to CPE direction and allows Management
LAN connectivity restore.
5. Management LAN connectivity does not guarantee the particular Service connectivity.
14-81
Troubleshooting
No Ethernet Traffic
When Traffic does not pass through the system and there are no alarms or conditions raised
in the system, then perform the following in the recommended order:
1. Check if any required by deployment managed entity (equipment and facilities) is
disabled (grayed-out in MetaASSIST View). Enable the disabled entities and check for
alarms. To resolve alarms, see Troubleshooting Alarmed Conditions (on page 14-8).
2. Check if any required by deployment managed entity (equipment and facilities) is not in
maintenance mode (when alarms and conditions are not monitored). Restore the managed
entities from maintenance mode, see Operating Alarms (on page 13-10). For facilities
(MLP, ETH, HSL), you can also refer to Service Suspension and Restoration (on page
14-33). Check for alarms. To resolve alarms, see Troubleshooting Alarmed Conditions
(on page 14-8).
3. Check if some SA (Service Affecting) Alarm/Condition are configured with Severity NA
(Not Alarmed). Check and reconfigure each SA alarm to appropriate severity, see
Modifying Alarm. Check for alarms. To resolve alarms, see Troubleshooting Alarmed
Conditions (on page 14-8).
4. Check the system Ethernet bridge configuration, all NEs in the working topology must be
configured equally as 802.1D (VLAN unaware) or as 802.1Q (VLAN aware). To verify
and configure the Ethernet bridge mode, see Ethernet Bridge Configuration.
5. Check the system for Ethernet Loop:
Enable STP on the system, see STP Configuration (on page 5-20);
Check if STP is also enabled on each ETH/HSL port, see STP Configuration (on
page 5-20);
The system will automatically suspend redundant links, the LNK LED will turn Amber.
To resolve the Ethernet loop, perform one of the following:
14-82
Make sure that traffic VLANs are configured and match with VLANs defined in all
Actelis systems and adjacent WAN and LAN network;
You can use 802.1D (VLAN unaware) mode to circumvent incomplete VLAN
configuration problems.
Troubleshooting
14-83
Troubleshooting
Corrective action: Resolve the congestion by configuring the Ethernet port to 100Mbps on
the external equipment (if adjacent network equipment allows it).
Upstream from Customer Site Traffic is Congested on HSL
Congestion on HSL port occurs when HSL BW is less than Ethernet port BW (usual
100MBps). Congested frames will be dropped according with selected Port priority
classification type. The incoming frame in ML device can be classified by L2 or by L3
priority bits of customer traffic.
Corrective action: Apply L2 or L3 priority classification on Customer LAN Adjacent
Actelis system port to drop packets with selective precedence.
Asymmetric Ethernet Traffic
In case of two different Actelis system models used in any topology, you may have
asymmetric Ethernet traffic, due to different Egress (Tx) or Ingress (Rx) Rate limit
configuration on ports of adjacent Actelis systems (via HSL or Ethernet).
Corrective action: To resolve the problem configure the systems equally.
Forwarding By L2 Priority works improperly
Original traffic L2 prioritization can be enforced by Port Priority or higher layers priority
configuration (i.e. configured other than by L2 priority) or be affected by improper
configuration of L2 classification table.
Corrective action: Set Port Priority to By L2 Priority to classify packets according to their
VLAN tag (802.1p priority field) and configure L2 classification tables properly.
14-84
Troubleshooting
Ping for verifying IP connectivity from the ML device system to a particular (specified)
system on your network;
Ethernet Port Statistics providing standard Ethernet counters per port. For details, see
Ethernet Statistics or Ethernet BW Monitoring (on page 13-73).
14-85
Troubleshooting
Ping
The Ping dialog box is a network diagnostic tool interface used to verify connectivity to a
particular system on your network. For example, you can check if the customer premises
equipment is connected to the Actelis system and is online. Ping sends ICMP echo requests
in the form of a data packet to a remote destination and displays the results for each echo
request. This exchange is referred to as pinging. The Ping command also displays the time
for a response to arrive in milliseconds and packet size.
To send a Ping request:
1. In the Network Element tree, open Management Interfaces. The Management
Interfaces pane opens.
2. Click Ping. The Ping dialog appears. See the following figure.
3. In the Ping Request area, select the destination of the required NE: IP Address or Local
Host. Type the Host IP address if selected.
4. In the Packet Count box, you can set the number of data packets sent by the ping
command (default is 3).
5. Click the Send button.
The Ping tool sends an echo request and waits for the echo reply. If the ping was
successful, summary lines are displayed in the Ping Response area, indicating the result
of the ping. A response message appears after less than a second.
6. During pinging, the Send button toggles to Stop. You can click Stop at any time to stop
the ping.
14-86
Troubleshooting
7. Click Clear to erase the results from the Ping Response area.
Click Ping.
Select the Local Host option.
Click Send.
Check that Ping successfully replied 3 times.
Click Close.
Click Ping.
Select the IP Address option.
Type in the IP address (any known IP in Management Network).
Click Send.
14-87
Troubleshooting
Ethernet OAM layered behavior permits monitoring and troubleshooting at a single level. It
provides capabilities on a link level and an end-to-end service level. Link OAM provides
management and troubleshooting of a single link between two Ethernet interfaces while EFM
OAM provides management and troubleshooting in a multi-hop Ethernet network for
individual customer service instances. In the Open Systems Interconnection (OSI) reference
model, Ethernet OAM is an optional sublayer that is implemented in the data link layer
between the logical link control (LLC) and MAC sublayers (see the following figure).
14-88
Troubleshooting
14-89
Troubleshooting
3. To enable OAM, set EFM OAM to Enabled. All the OAM Capabilities (on page 1491) will be enabled.
4. The EFM OAM operation Mode for this interface is define as Active mode - provides
additional capabilities to initiate monitoring activities with the remote OAM peer entity.
5. The interface can be set to disconnect from a Remote Loopback (on page 14-92) test
after a defined period of time has elapsed:
6. Click OK.
14-90
Troubleshooting
OAM Capabilities
EFM OAM Discovery
EFM OAM Discovery is the first phase in the 802.3ah protocol and it identifies the 802.3ahcapable link partner. This OAM feature enables ML device systems to identify the OAM
capability of other ML device systems and exchange state and configuration information.
This includes:
Mode: active
Vendor: ATNW
UID: 0x000385
OAM Version: 1
Event Support: No
Variable Support: No
Note: The MAX OAM MFS size =1518 bytes. The transmit OAM size is optimized to the
content (minimum 64 bytes).
14-91
Troubleshooting
Dying Gasp
Note: This feature is not implemented by ML130 installed as a CPE.
Upon detection of power loss, ML CPE initiates a Dying Gasp signal on transmission
(SHDSL signal) level to inform CO immediately on the loss of power. The signal is detected
and reported by ML CO unit as power fault on remote device (reported as RPWFLT).
This is especially significant in deployments where the CPE power is fed by the customer,
and not by the provider, in order to target the source of the problem and rule out service level
agreement issues.
Remote Loopback
This OAM option enables an 802.3ah OAM-capable device to put its remote link partner into
loopback mode using a loopback control OAMPDU. Every frame received is transmitted
back on the same port to ensure the quality of links during installation or troubleshooting.
This OAM option is used for port level and service level (end-to-end) testing. It is
implemented by transmitting a specific packet at one end, and analyzing the received packet
at the other end. Ports can be configured with a loopback timeout of 5 to 30 minutes that
disconnects loopback if a an OAMPDU is not received within the set timeout period.
Remote Loopback can be used to:
1. Enable and configure the OAM (on page 14-89) on both ports on which the test will be
performed and configure the Loopback Timeout parameters as needed.
2. Interconnect the ports using a standard Ethernet cable.
3. Verify the connection as follows: in the pane of one (or both) of the interconnected ports,
in the EFM OAM area, click Details and verify that Peer Capabilities Loopback is
enabled; otherwise, check the connection.
4. In the port pane, EFM OAM area, click the Operate Loopback button to perform the
loopback test.
5. In the port pane, EFM OAM area, click the Loopback Statistics button. The EFM OAM
Statistics window appears.
6. Use the window to analyze the Loopback test results.
14-92
Troubleshooting
14-93
Troubleshooting
14-94
Troubleshooting
Configuration Problems
Craft Port Access problems:
Local Craft port setting (baud rate) specified in MetaASSIST View, configured on ML
device and configured on your management host serial port (COM1/COM2) do not
match. In this case, MetaASSIST View tries to reconnect indefinitely. It is recommended
to check the connection parameters. If local craft connection cannot be established,
configure your PC Baud Rate according to ML definitions, change the Baud Rate in the
Connect dialog box, and try to re-connect.
If connection was not established at any of the baud rates this implies that the Craft port
was disabled. Try one of the following:
Replace the Actelis system with another one (with factory setup).
Verify that the ML device COLAN (MGMT) port is enabled (using a craft connection).
By factory setup, ML device COLAN (MGMT) is disabled;
COLAN (MGMT) port settings do not match PC port configurations. This can be due to
the following:
Cable configuration does not match the attached cable. The COLAN (MGMT) MDI
pinout is by default MDIX and requires an RJ-45 connector with a crossover cable;
Speed and Duplex between the PC and COLAN (MGMT) do not match. By default,
the Speed and Duplex mode of the COLAN (MGMT) are auto-negotiated. If your PC
or workstation port does not support this feature, then speed and duplex mode should
be manually configured on the ML device via Craft;
14-95
Troubleshooting
You may have an Ethernet loop. Resolve the problem and re-connect;
If service traffic passes through the Actelis system, but management traffic does not, then
please check that the Management VLAN is configured correctly;
Management traffic (defined to be forwarded with HIGHEST priority) fails when HSL is
congested by service traffic. Check that Ingress Traffic limiting is not enabled on HSL (in
ML600 only). To resolve the problem, disable the feature via TL1.
If both Management and Service traffic do not pass through the Actelis system then
probably the Ethernet port setting does not match with network configurations:
The ETH-<ID> port MDI pinout is by default MDI and requires an RJ-45 connector
with straight-through cable;
Speed and Duplex mode of ETH-<ID> by default are auto-negotiated. You can
connect via Craft port and configure ML device Ethernet port according to your
network setting;
14-96
Incorrect IP address was typed in the "Connect" dialog box. In this case, MetaASSIST
View tries to connect to the NE and displays the following tooltip when the cursor is
located on the NE: 'Started Connecting...'. Re-connect with correct IP address.
On directly accessed NE, MetaASSIST View tries to connect to the NE and displays
the following tooltip when the cursor is located on the NE: 'Started Connecting...'.
Re-connect with correct IP address.
Troubleshooting
In this case, you need to add your IP address to the IP Access Control List with the
Telnet protocol specified as enabled for connection or connect through the Craft port and
disable IP Access Control. IP Access Control feature is enabled on ML device and the IP
address of your host (PC/Workstation) is not in the IP Access Control List.
SSH Authentication Failures and Warnings (optional - for secure version only)
Authentication Failed, Management Host does not have the ML device Public Key
or Passphrase is incorrect.
If the Public Key of the MetaASSIST View was not entered into the Network Element,
the Passphrase is incorrect, or user did not accept the public key of the Network Element,
you will receive the following error message: 'Authentication Failed'. Ask the system
administrator for a new Public Key.
14-97
Troubleshooting
MetaASSIST View displays the error message: "Currently too many sessions are open on the
Actelis system" in the following case:
14-98
Troubleshooting
14-99
Troubleshooting
Configuration Problems
Craft Port Access problems:
Local Craft port setting (baud rate) specified in MetaASSIST View, configured on
ML device and configured on your management host serial port (COM1/COM2) do
not match. In this case, MetaASSIST View tries to reconnect indefinitely. It is
recommended to check the connection parameters. If local craft connection cannot be
established, configure your PC Baud Rate according to ML definitions, change the
Baud Rate in the Connect dialog box, and try to re-connect.
If connection was not established at any of the baud rates this implies that the Craft
port was disabled. Try one of the following:
o
Replace the Actelis system with another one (with factory setup).
14-100
Verify that the ML device COLAN (MGMT) port is enabled (using a craft
connection). By factory setup, ML device COLAN (MGMT) is disabled;
COLAN (MGMT) port settings do not match PC port configurations. This can be due
to the following:
Troubleshooting
Cable configuration does not match the attached cable. The COLAN (MGMT)
MDI pinout is by default MDIX and requires an RJ-45 connector with a
crossover cable;
Speed and Duplex between the PC and COLAN (MGMT) do not match. By
default, the Speed and Duplex mode of the COLAN (MGMT) are autonegotiated. If your PC or workstation port does not support this feature, then
speed and duplex mode should be manually configured on the ML device via
Craft;
You may have an Ethernet loop. Resolve the problem and re-connect;
If service traffic passes through the Actelis system, but management traffic does not,
then please check that the Management VLAN is configured correctly;
If both Management and Service traffic do not pass through the Actelis system then
probably the Ethernet port setting does not match with network configurations:
o
The ETH-<ID> port MDI pinout is by default MDI and requires an RJ-45
connector with straight-through cable;
Speed and Duplex mode of ETH-<ID> by default are auto-negotiated. You can
connect via Craft port and configure ML device Ethernet port according to your
network setting;
Incorrect IP address was typed in the "Connect" dialog box. In this case,
MetaASSIST View tries to connect to the NE and displays the following tooltip when
the cursor is located on the NE: 'Started Connecting...'. Re-connect with correct IP
address.
14-101
Troubleshooting
In this case, you need to add your IP address to the IP Access Control List with the
Telnet protocol specified as enabled for connection or connect through the Craft port
and disable IP Access Control. IP Access Control feature is enabled on ML device
and the IP address of your host (PC/Workstation) is not in the IP Access Control List.
SSH Authentication Failures and Warnings (optional - for secure version only)
14-102
Authentication Failed, Management Host does not have the ML device Public
Key or Passphrase is incorrect.
If the Public Key of the MetaASSIST View was not entered into the Network
Element, the Passphrase is incorrect, or user did not accept the public key of the
Network Element, you will receive the following error message: 'Authentication
Failed'. Ask the system administrator for a new Public Key.
Troubleshooting
MetaASSIST View displays the error message: "Currently too many sessions are open on the
Actelis system" in the following case:
14-103
Troubleshooting
14-104
Troubleshooting
For more information regarding dipswitch configurations in various topologies, refer to the
ML600 Quick Installation Guide, Appendix A.
14-105
Appendix A - Acronyms
, A
15 Appendix A Acronyms
Meaning
ACO
Alarm Cut-Off
AID
Access Identifier
AIDTYPE
ANSI
AWG
BER
BERT
BIPT
BIT
Built-In Test
BPDU
BRUO
CHS
Chassis
CLE
CLEI
CO
Central Office
CoS
Class Of Service
CPE
CR
CRC
CSA
CTAG
Correlation Tag
A-1
Appendix A - Acronyms
Acronym
Meaning
CTC
CTM
dB
Decibel
dBm
dBrn
DCE
DCN
DF
Distribution Frame
DSL
DST
DTE
DVM
Digital Voltmeter
EIA
EMI
Electromagnetic Interference
ESD
Electrostatic Discharge
EMS
ETSI
EWL
FCM
FTP
GPI
G.SHDSL
GUI
HSL
HTTP
IEEE
IP
Internet Protocol
ITU
Kbps
Kft
Kilofeet
A-2
Appendix A - Acronyms
Acronym
Meaning
KHz
KiloHertz
LAN
LOS
Loss Of Signal
MDF
MDI
MDIX
MLU
MLP
MLU port
MN
MJ
MTU
MFS
NA
NEBS
NMS
OOS-AU
OOS-MT
OSS
PSD
PSTN
PVID
QA
Quality Assurance
RBOC
RLM
RSTP
SCM
SDU
SID
Source Identifier
SNMP
SNTP
A-3
Appendix A - Acronyms
Acronym
Meaning
SLA
SNR
Signal-to-Noise Ratio
SRU-C
SRU-N
STP
STU-C
STU-R
TFTP
TID
Target Identifier
TOD
Time Of Day
UPS
UTP
A-4
, B
16 Appendix B - Parts
List
This appendix summarizes the items which can be ordered from Actelis, including:
SFP Modules
SW and Documentation
Cables
Accessories
B-1
SFP Modules
SFP Modules
Note: ML638 RoHS6 compliant support multi-rate SFP (100 Mbps / 1000 Mbps)
Description
Part
Number
CLEI Code
506R00002
M3C1HH0BAA
506R00012
M3C1HG0BAA
506R00022
COUIABEGAA
506R00032
COUIABDGAA
506R00042
506R00052
COUIABCGAA
COUIACMGAA
506R00062
N/A
506R00072
N/A
506R00082
N/A
506R51750
N/A
Item
Description
P/N
CLEI Code
506R51510
N/A
B-2
506R51714
N/A
506R51514
N/A
506R51511
N/A
506R51711
N/A
506R51716
N/A
506R51712
N/A
506R51713
N/A
506R61120
N/A
506R51612
N/A
502R60510
N/A
B-3
Description
Part Number
CLEI Code
CD includes:
MetaASSIST EMS Server with HSQL database,
available for PC and UNIX.
515R00061
N/A
CD includes:
MetaASSIST EMS Client application, available
for PC and UNIX.
515R00060
N/A
520R50160E
N/A
ML130/1300/2300 R6.1
CD
522R66018E
N/A
ML600 R6.1 CD
522R66017E
N/A
ML130/1300/2300 R6.0
CD
522R61302E
N/A
ML600 R6.0 CD
522R66011E
N/A
ML-Secure
ML130/1300/2300 R5.20
CD
522R51395E
N/A
ML-Secure ML1300/130
R5.0 CD
522R51350E
N/A
522R56185E
N/A
ML-Standard
ML130/1300/2300 R5.20
CD
522R51390E
N/A
ML-Standard ML1300/130
R5.10 CD
522R51376E
N/A
522R56175E
N/A
522R56180E
N/A
B-4
Cables
Table 100: DSL Cables
Item
Description
Part Number
CLEI
Code
504R20020
N/A
504R20110
N/A
504R20130
N/A
504R20140
N/A
504R20170
N/A
504R20120
N/A
504R20150
N/A
504R20160
N/A
504R20180
N/A
504R06012
N/A
504R06015
N/A
504R06017
N/A
504R20090
N/A
Description
Part Number
CLEI
Code
504R06065
N/A
504R20010
N/A
B-5
Cables
504R20036
N/A
504R20025
N/A
504R20030
N/A
504R06060
N/A
Description
Part Number
CLEI
Code
504R20043
N/A
199A10040
N/A
199A10050
N/A
199A10060
N/A
199A10070
N/A
B-6
Accessories
Table 103: Kits
Item
Description
P/NNumber
CLEI Code
Accessories Kit
510K00060
N/A
AC-DC Adapter EU
506R00005E
N/A
AC-DC Adapter
506R00005
N/A
Installation Kit
510K05001
N/A
502R05080
N/A
510R21070
COMNH00DRA
510R21080
N/A
510R50955
N/A
Description
P/N
CLEI Code
501R00012
N/A
501R00011
N/A
Item
Description
P/N
CLEI Code
506R04820
N/A
506R04815
N/A
502R04810
N/A
506R04830
N/A
502R04825
N/A
508R04835
N/A
B-7
Accessories
, C
17 Appendix C Technical
Specifications
C-1
ML600 Specifications
ML600 Specifications
Table 106: ML600 Specifications
Interfaces
Ethernet Service
10/100Base-TX IEEE 802.3
Connector:
100/1000Base-Fx (option)
Connector:
T1/E1 (ML650 only)
Interface
Framing
Line Code
Sensitivity
Standard Compliance
Latency
Clock Synchronization
4 ports
RJ45, Auto-MDIX
1 port
SFP based, MSA compliant
4 ports
RJ45 (RJ-48c)
T1: Balanced 100; E1 Balanced 120
T1: Unframed, SF and ESF, both clear channel and fractional
E1: Unframed, E1 (PCM31) and E1-CRC (PCM31 CRC), both clear channel
and fractional
T1: B8ZS or AMI
E1: HDB3 or AMI.
Long haul: T1 -36 dB (@772kHz); E1 -43 dB (@1,024kHz).
Short haul: T1 -10 dB (@772kHz); E1 -10 dB (@1,024kHz).
Configurable (for T1): 0 133, 134 266, 267 399, 400 533 and 534
655 feet.
Configurable (for Long haul): 0 dB, -7.5 dB, -15 dB and -22.5dB
T1: ANSI T1.403, ITU-T G.704, G.706, G.734 and G.824
E1: ITU-T G.703, G.706, G.732 and G.823
Configurable (few milliseconds)
C-2
ML600 Specifications
Management (Out-of-Band)
10/100Base-TX
Connector:
Craft
Connector:
Flow control
Link Aggregation
IEEE 802.3x (pause frames for FULL/back pressure for HALF DUPLEX
modes)
IEEE 802.3ad
EFM OAM
Bridging
IEEE 802.1d/p/q
64 bytes
VLANs
RSTP, STP
255 user defined Traffic VLANs + 1 user defined MGMT VLAN, for VIDs in
range from 1 to 4094
~250 frames for 64-byte length frames;
~60 frames for 1532-byte length frames;
IEEE 802.1d compliant
Provider Bridge
LLDP
4 (ML640/ML650 8)
Scheduler
Classification
Marking
EVCs
Classification Rules
BW control
Ingress policing
Scheduler
Egress limiting and shaping
Management
Management Applications
EMS
MetaASSIST EMS
C-3
ML600 Specifications
MetaASSIST View
SNMP v1 and v2c
TL1
Telnet
SSH v2
SNTP v3
HTTP
FTP, TFTP
per modem/pair
per Ethernet/HSL port
per E1/T1 port (ML650 only)
Alarm Contacts
Terminal Block :
Max voltage/current
2 Input, 1 Output
72VDC/120mA max
Physical
Dimensions
Weight:
Mounting
Power
DC:
AC:
Environmental
Operating Temp.
Storage Temp.
Relative humidity
-40 to +65C
-40 to +70C
Up to 95%, non-cond.
CE certified
Environmental
C-4
IEEE8021-CFM-MIB(IEEE draft 8)
C-5
Customer Logs
Customer Logs
C-6
INSTALL
INFO
BLACKBOX
ANSI T1.417;
In addition, Actelis systems comply with country specific spectral mode standards. See
Available Spectral Modes (on page 8).
A specific spectral mode can be set, limiting spectral characteristics of modems to comply
with a particular standard.
C-7
Description
NA1
Compliant with ITU-T G.991.2 Annex F. Enables modem rates up to 5.7 Mbps (with an
option for up to 8.5 Mbps)
NA2
Compliant with ITU-T G.991.2 Annex F and ANSI T1.417. Enables modem rates up to 5.7
Mbps (with an option for up to 8.5 Mbps). Rates are subject to limiting (per reach).
NA3
Compliant with ANSI T1.417. Allows PAM16, PAM32, PAM64 and PAM128 constellation as
well as higher baud rate. Enables modem rates up to 15.2 Mbps. Rates are subject to
limiting (per reach).
EU1
Compliant with ITU-T G.991.2 Annex G, allows PAM32 constellation and Extended PSD
mask. Enables modem rates up to 5.7 Mbps.
EU2
Compliant with ITU-T G.991.2 Annex B and ETSI TS 101 524. Enables modem rates up to
2.3 Mbps.
EU3
Compliant with ITU-T G.991.2 Annex B, but additionally allows PAM32 constellation. Enables
modem rates up to 3.1 Mbps (with an option for up to 4.6 Mbps).
EU4
Compliant with ETSI TS 101 524 Annex E and ITU-T G.991.2 Annex G. Enables modem
rates up to 5.7 Mbps (with an option for up to 8.5 Mbps)
EU5
Compliant with UK ANFP (Access Network Frequency Plan) for British Telecom, according to
NICC ND1602:2005/08. Enables modem rates up to 3.1 Mbps (with an option for up to 4.6
Mbps). Rates are subject to limiting (per reach). Power Back-Off as specified in ETSI 101
524, Annex E.
EU6
Compliant with Belgian Institute for Postal services and Telecommunications (BIPT) Spectral
Management regulation for the Belgian access network as specified in BIPT BRUO 2005
"Belgacom Row Copper and Shared Pair Products - Technical Specifications", Annex C.
Enables modem rates up to 5.7 Mbps , limited per reach (with an option for up to 8.5
Mbps). Power Back-Off as specified in ETSI 101 524, Annex E.
EU7
Compliant with SOO, Netherlands SDSL Spectral Management regulation and xDSL
deployment rules for the Dutch access network. Enables modem rates up to 5.7 Mbps,
limited per reach (with an option for up to 8.5 Mbps). Power Back-Off as specified in ETSI
101 524, Annex E.
EU8
Compliant with German, DT, Spectral management regulations. Enables modem rates up to
5.7 Mbps, limited per reach (option for up to 8.5). Power Back-Off as specified in ETSI 101
524, Annex E.
EU9
Compliant with Denmark, TDC, Spectral Management regulation. Enables modem rates up
to 5.7 Mbps (with an option for up to 8.5 Mbps), limited per reach. Power Back-Off as
specified in ETSI 101 524, Annex E.
EU10
Compliant with UK ANFP (Access Network Frequency Plan) for British Telecom, according to
NICC ND1602:2007/03. Enables modem rates up to 5.7 Mbps (with an option for up to 8.5
Mbps), limited per reach. Power Back-Off as specified in ETSI 101 524, Annex E.
EU11
Compliant with Spain - "High Quality" pairs. Enables modem rates up to 5,696 Kbps, limited
per reach (with an option for up to 8.5). Power Back-Off as specified in ETSI 101 524,
Annex E.
C-8
EU12
Compliant with Spain - "Low Quality" pairs. Enables modem rates up to 4,224 Kbps, limited
per reach (with an option for up to 6.3 Mbps). Power Back-Off as specified in ETSI 101 524,
Annex E.
EU13
NOT IN USE
EU14
5.7 Mbps, limited per reach (with an option for up to 8.5 Mbps). Power Back-Off as
specified in ETSI 101 524, Annex E.
EU15
Compliant with Telekom Austria Spectral Management regulation. Enables modem rates up
to 5.7 Mbps, limited per reach (with an option for up to 8.5 Mbps). Power Back-Off as
specified in ETSI 101 524,Annex E.
EU16
Compliant with Sweden Spectral Management regulation. Enables modem rates up to 5.7
Mbps, limited per reach (with an option for up to 8.5 Mbps). Power Back-Off as specified in
Compliant with Ireland Spectral Management regulations. Enables modem rates up to 5.7
Mbps (with an option for up to 8.5 Mbps). Power Back-Off as specified in ETSI 101 524,
Annex E.
EU18
Compliant with Finland's Spectral Management regulations. Enables modem rates up to 5.7
Mbps (with an option for up to 8.5 Mbps). Power Back-Off as specified in ETSI 101 524,
Annex E.
EU19
Compliant with ARCEP France regulations. Enables modem rates up to 5.7 Mbps (with an
option for up to 8.5 Mbps). Power Back-Off as specified in ETSI 101 524, Annex E.
AP1
AP2
NOLMT
No Limit, Compliant with PAM16, PAM32, PAM64 and PAM128 constellation and Extended
PSD mask up to 2.5 Mbaud. Enables modem rates up to 15.2 Mbps.
C-9
, D
18 Appendix D - Factory
Setup Content
This appendix describes the factory setup for the ML600 models, where the factory setup for
each model is described in the appropriate sub-section.
D-1
Craft
IP access
Radius Client
LLDP (Link Layer Discovery
Protocol)
System identification
SNMP access
Security
Log files
PM counters
Time of Day
Alarm led
2Base-TL bonding
HSL
COLAN
HSL-1
Enabled
LAG-x
Not entered
EFM OAM is OFF. When enabled (per port) is set to ACTIVE mode
D-2
Ethernet Bridge
VLAN awareness
VLAN Tag type
PPPoE tunnel forwarding
FRWDB learning
FRWDB aging
VLANs
VLANs
For ML688:
VID= 100 is set for CPU, COLAN (untagged), and all HSL (tagged), even not
entered
VID=101: ETH-1/S + HSL-1/T
VID=102: ETH-2/S + HSL-1/T
VID=103: ETH-3/S + HSL-1/T
VID=104: ETH-4/S + HSL-1/T
VID=105: ETH-5/S + HSL-1/T
Where S - Stacked, T- Tagged
VID=101: ETH-1/U +HSL-{1-2}/T
VID=102: ETH-2/U+ HSL-{1-2}/T
VID=103: ETH-3/U+ HSL-{1-2}/T
VID=104: ETH-4/U+ HSL-{1-2}/T
VID=105: ETH-5/U+ HSL-{1-2}/T
Where U - Untagged, T- Tagged
WFQ
L2Prio-to-CLASS classification
L3Prio-to-CLASS classification
L2Prio Translation
CLASS-to-L2Prio mapping
D-3
not entered
STP
STP system-wide
Port setting
STP path costs defaults set
for RSTP
L2CP
Cisco Reserved MACs:
01-00-0C-00-00-00 (Cisco ISL),
01-00-0C-CC-CC-CC (Cisco CDP), 01-000C-CC-CC-CD (Cisco PVST+)
MAC 01-80-C2-00-00-00 (STP)
MAC 01-80-C2-00-00-01 (Pause Frames)
MAC 01-80-C2-00-00-02, subtype=2 (OAM)
MAC 01-80-C2-00-00-02, subtype=3 10
(UNKNOWN)
MAC 01-80-C2-00-00-02, subtype=0 or >11
MAC 01-80-C2-00-00-0E (LLDP)
MAC 01-80-C2-00-00-{03-0F}, 10, {20-21}
D-4
DS#2
DS#3
DS#4
Description
On
Off
Off
Off
On
On
Off
Off
Off
Off
On
Off
All other configurations are invalid, see ML600 Quick Installation Guide to troubleshoot Dip Switch setup.
D-5
EVCs
not entered
EVC Services
SERV-1:
SERV-2:
SERV-3:
SERV-4:
SERV-5:
SERV-6:
SERV-7:
Identification Rules
RULE-1: not editable
RULE-7:
D-6
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-00-0000, MASKMACDST=FF-FF-FF-FF-FF-F0, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR = L2CP MAC=0x0180C200000*
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-00-0010, PASSTOMETER=Y, SERV-1, ORDERNUM=-1, MARKING=NONE, DESCR= "
L2CP MAC=0x0180C2000010".
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-0020,MASKMACDST=FF-FF-FF-FF-FF-FE, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "L2CP MAC=0x0180C20020/1".
Default Template, All Values, except MACDST, =ANY, MACDST =01-00-0c-00-0000, MASKMACDST=FF-FF-FF-FF-FF-FF, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR="ISL MAC=0x01000C000000.
Default Template, All Values, except MACDST, =ANY, MACDST =01-00-0c-cc-cccc/D, MASKMACDST=FF-FF-FF-FF-FF-FE, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "CDP/PVST+ MAC=0x01000 CC-CC-CC-C/Dl.
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-00-0030, MASKMACDST=FF-FF-FF-FF-FF-F0, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "CFM MAC=0x0180C200003*".
Default Template, All Values, except VID, =ANY, EXTTAGVID = 100 (MGMTVID),
PASSTOMETER=Y,SERV-3, MARKING=NONE, DESCR= "MGMT VLAN".
RULE-8:
RULE-9:
RULE-10:
RULE-11:
BW Profiles
D-7
DS#
2
DS#
3
DS#
4
Description
On
Off
Off
Off
On
On
Off
Off
ML640 performs as CO device (not re-configurable). HSL is AutoCalibrated, i.e. starts calibration on each restart with Best Effort, EU1
Spectral Mode and 3dB SNR margins as target (Calibration BW Target,
SNR Margin and Spectral Mode can be reconfigured). 802.1Q bridge
mode (not re-configurable) is available. STP per system and port is
enabled (can be disabled by per port configuration). Alarm led
performs partially (reports PROGFLT alarm only). NOSETUP alarm is
not raised. ETH-{1-5} are as in factory setup: all enabled with
Mode=Auto, Pinout=MDI, Flow control=OFF.
Off
Off
On
Off
All other configurations are invalid, see ML640 Quick Installation Guide to troubleshoot Dip Switch setup.
D-8
not entered
EVC Services
SERV-1:
SERV-2:
SERV-3:
SERV-4:
SERV-5:
SERV-6:
SERV-7:
SERV-8
Identification Rules
RULE-1: editable
RULE-2: editable
RULE-3: editable
RULE-4: editable
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-0000-00, MASKMACDST=FF-FF-FF-FF-FF-F0, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR = "L2CP MAC=0x018-0C-20-00-00*l"
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-0000-10, PASSTOMETER=Y, SERV-1, ORDERNUM=-1, MARKING=NONE, DESCR=
"L2CP MAC=0x0180C2000010l".
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-0000-20/1, MASKMACDST=FF-FF-FF-FF-FF-FE, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "L2CP MAC=0x0180C20020/1".
Default Template, All Values, except MACDST, =ANY, MACDST =01-00-0c-0000-00, MASKMACDST=FF-FF-FF-FF-FF-FF, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "ISL MAC=0x01000C-00-00-00".
D-9
Default Template, All Values, except MACDST, =ANY, MACDST =01-00-0c-cc-cccc/D, MASKMACDST=FF-FF-FF-FF-FF-FE, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "CDP/PVST+ MAC=0x01000CCCCCCC/D".
Default Template, All Values, except MACDST, =ANY, MACDST = 01-80-C2-0000-30, MASKMACDST=FF-FF-FF-FF-FF-F0, PASSTOMETER=Y, SERV-1,
MARKING=NONE, DESCR= "CFM MAC=0x0180C200003".
RULE-11: editable
Default Template, All Values, except VID, =ANY, EXTTAGVID = 100 (MGMTVID),
PASSTOMETER=Y, SERV-3, MARKING=NONE, DESCR= "MGMT VLAN".
RULE-12: editable
RULE-13: editable
RULE-14: editable
RULE-15: editable
BW Profiles
D-10
DS#
2
DS#
3
DS#
4
Description
On
Off
Off
Off
On
On
Off
Off
ML650 performs as CO device (not re-configurable). HSL is AutoCalibrated, i.e. starts calibration on each restart with Best Effort,
EU1 Spectral Mode and 3dB SNR margins as target (Calibration BW
Target, SNR Margin and Spectral Mode can be reconfigured).
802.1Q bridge mode (not re-configurable) is available. STP per
system and port is enabled (can be disabled by per port
configuration). Alarm led performs partially (reports PROGFLT alarm
only). NOSETUP alarm is not raised. ETH-{1-5} are as in factory
setup: all enabled with Mode=Auto, Pinout=MDI, Flow control=OFF.
Off
Off
On
Off
All other configurations are invalid, see ML650 Quick Installation Guide to troubleshoot Dip Switch setup.
D-11