User Manual
ML600
Revision No. A01
Document Identification ML600 Release 5.2
Document No. 520R51111E Revision No. A01
Date: March 2007 Copyright
Copyright © 2007 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. Disclaimer of Warranties and limitation of Liabilities
Actelis Networks, Inc. (hereafter referred to as Actelis Networks, Inc. or Actelis Networks), makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, in no event, shall Actelis Networks be liable for incidental or consequential damages in connection with or arising from the use of the ML600 series, cards and modules,
accessories kits, this manual or any related materials. Actelis Networks reserves the right to revise this publication from time to time and to make changes in the content hereof without obligation to notify any person of such revisions or changes.
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.
Introduction About this Document
II User Manual ML600
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.
About this Document Introduction
About this Document
Document ObjectivesThis manual provides a general description of the ML device, detailed instructions for the deployment and maintenance of the ML 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.
Symbols Used in this Manual
Warning: Indicates information on how to avoid personal injury.
Caution: Indicates information on how to avoid damage to the equipment or to avoid possible service disruption.
ESD: Indicates information on how to avoid discharge of static electricity and subsequent damage to the Actelis system.
Introduction System Documentation and Software Applications
IV User Manual ML600
System Documentation and Software
Applications
Actelis supplies each product with the following system documentation and applications:
• ML User Manual - provides a general description, detailed instructions for the
deployment, configuration and maintenance of the product. The User Manual is supplied in PDF format and as Online Help on the included CD. A hard copy can be ordered separately.
• ML Quick Installation Guide - provides summary explanations of the procedures for
installing the Actelis system. The Quick Installation Guide is included in each Actelis product package and also can be ordered separately.
• MetaASSIST View - software (secure and standard) and MetaASSIST View
Obtaining Technical Assistance Introduction
Obtaining Technical Assistance
Contact InformationPlease 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:
• Internet: Visit the Actelis Networks World Wide Web site http://www.Actelis.com
• Actelis Networks customer support Mailto: [email protected] for technical support.
• Customer support: Contact Actelis Networks Customer Support directly at one of the
following numbers: • Belgium: (0) 800 71180 • Denmark: 80 887 771 • France: (0) 800 918 450 • Germany: (0) 800 1833504 • Netherlands: (0) 800 0225982 • UK: (0) 800 9179049 • USA: +1 866 638 2544 or +1 510 545 1071
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 mail to: [email protected] mailto:[email protected]. 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.
Introduction Certification
VI User Manual ML600
Certification
FCC Class B ComplianceML600 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 radio-frequency energy and, if not installed and used in accordance with this User Manual 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.
Canadian Emissions Requirements
This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.
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).
Certification Introduction
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.
Introduction General Safety Instructions
VIII User Manual ML600
General Safety Instructions
1. Read and follow all warning notices and instructions marked on this product or included
in this manual.
2. This equipment is for use in a RESTRICTED ACCESS AREA only.
3. All installation, repair or replacement procedures must be performed by qualified service
personnel.
4. Grounding (earthing) requirements:
• This equipment must have a connection between the grounded conductor of the DC
supply circuit and the grounded conductor.
• All equipment in the immediate vicinity must be grounded the same way and must
not be grounded elsewhere.
• Before attempting to operate or repair this product, make sure product is properly
grounded.
5. DC system powering requirements:
• The DC supply source must be located within the same premises as this equipment. • DC supply circuit must have a grounded conductor.
• This equipment should be located in the same immediate area (such as adjacent
cabinets) as any other equipment that has a connection between the grounded conductor of the same DC supply circuit and the grounding conductor, and also the point of grounding of the DC system. The DC system should not be grounded elsewhere.
• The DC power source should be protected with a disconnection device located in the
same immediate area.
• Overcurrent Protection - a readily accessible listed circuit breaker rated 5A should be
connected to the non-grounding conductor. A 5A overcurrent protective device can feed two ML600 units installed in the rack mount sleeve.
• There should be no switching or disconnecting devices in the grounded circuit
conductor between the DC source and the point of connection of grounding electrode conductor.
6. This product uses an external power source. Do not touch exposed connections,
components or wiring when power is present. 7. Keep product surfaces clean and dry.
8. Provide proper ventilation. Refer to the installation instructions in Chapter 2 of this
General Safety Instructions Introduction
9. Do not operate this product with panels removed or with suspected failure or damage to
electrical components.
10. Do not operate or repair this product in wet or damp conditions or in an explosive
atmosphere.
11. 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.
12. 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.
13. 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 110–16, 110–17 and 110–18 and the Canadian Electrical Code, Section 12. If necessary, consult with the appropriate regulatory agencies and inspection authorities to ensure compliance.
Disposal
Consumer Notice: The purchased Actelis' product is subject to Directive 2002/96/EC of the European Parliament and the Council of the European Union on waste electrical and electronic equipment (WEEE) and, in jurisdictions adopting that Directive, is marked as being put on the market after August 13, 2005, and should not be disposed of as unsorted municipal waste. Please utilize your local WEEE collection facilities in the disposition of this product and otherwise observe all applicable requirements.
Contents
About this Document...III System Documentation and Software Applications... IV Obtaining Technical Assistance...V Certification ... VI General Safety Instructions...VIII Disposal ... IX
About ML600 ... 1-2 Deployment Topologies... 1-3 Point-to-Point ... 1-3 Point-to-Point via Repeaters... 1-4 Point-to-Dual Point... 1-5 Drop-and-Continue... 1-6 Point-to-Multipoint... 1-7 ML600 Architecture ... 1-8 Management Applications ... 1-9
Front and Rear Panel Descriptions ... 2-2 Rear Panel Description ... 2-2 Front Panel Description ... 2-3 Connecting to and Navigating the MetaASSIST View... 2-4 Connecting to the ML via the MetaASSIST View ... 2-4 The MetaAssist View Workplace... 2-11 Current Alarms Area ... 2-18 ML600 Commissioning ... 2-19 Initial Setup Procedure (Wizard)... 2-19 1. ML CO Physical Site Installation ... 2-19 2. ML CO Configuration - for Link Verification... 2-20 3. ML CPE Physical Site Installation ... 2-20 4. ML CO - Link Verification... 2-21 5. ML CO - HSL Operation... 2-22 6. ML CO - Service Configuration ... 2-23 7. ML CO - Administration Configuration... 2-24 8. ML CO - Configuration Backup... 2-25
Introduction General Safety Instructions
ii User Manual ML600
Overview ... 3-2 NE Management Communication Protocols... 3-3 Craft Port Configuration ... 3-4 IP/LAN Connectivity on Directly Connected NE... 3-5 L2 (MGMT VLAN) Connectivity ... 3-5 L3 (IP) Connectivity... 3-6 IP/LAN Connectivity on Indirectly Connected NE ... 3-8 SNMP Agent and Trap Parameters... 3-9 SNMP Agent Configuration ... 3-9 SNMP Trap Destinations... 3-11 SNMP Trap Filtering... 3-12 L2 (MGMT VLAN) and L3 (IP) Connectivity... 3-13 System Name Configuration... 3-15 System Time and Date... 3-16 Configuring Date and Time Manually... 3-16 Automatic Date and Time Adjustment ... 3-17 Daylight Saving Time (DST) Configuration ... 3-18 !
Pluggable Equipment (SFP) Control (optional)...2
SFP Module Automatic Control ...2
SFP Module Manual Control...3
PFU-8 Configuration ...4
System Configurable Attributes...5
Alarms and Indications Control...7
General Purpose Output (GPO) Configuration...7
Environmental Alarm (GPI) Configuration...10
Modem Line Ports (MLP) Configuration ...13
HSL Configuration ...15
HSL Configuration ...15
HSL Calibration...17
DSS Profile...19
Customized S.Mode File ...20
Ethernet Port Configuration...22
LLCF ...26
Static Link Aggregation (LAG) Configuration...29
Overview of the LAG Configuration Procedure...29
LAG Configuration Procedure ...30
Allocating Ethernet Ports to LAGs...31
General Safety Instructions Introduction
" #
IEEE 802.1 Switching Principles...2
ML600 Ethernet Bridge ...3 ML640 Ethernet Bridge ...6 $ % & % STP/RSTP Principles...2 STP/RSTP in ML Systems ...4 STP/RSTP Bridge Configuration...5 STP/RSTP Ports Configuration ...7 '( ) * + VLAN Configuration Principles...2
Membership Principles ...3
VLAN Membership Forms...3
VLAN Membership Rules...6
Management VLAN Configuration ...10
Traffic VLAN Configuration...12
VLAN Topologies ...15
Symmetric Topologies...16
Asymmetric Topologies ...23
, " -Service Configuration Procedure...2
1. Service Traffic Identification...3
2. Service VID Filtering and Stacking ...4
3. Assigning NE Resources for the Service ...5
4. Quality of Service ...6
Classification to Queues ...7
5. Flow Control...17
6. Service Throughput Configuration ...18
ML600 Throughput Configuration ...18
ML640 Throughput Configuration ...20
7. COS Marking of the Service...21
8. L2CP Processing...23
Supported L2CP Protocols ...24
Configuring Handling of L2CP Frames ...24
9. Service Connectivity...31
10. EVC Configuration ...32
Defining EVCs ...33
Associating VLANs with EVC...33
ML640 - BW Profile Definition ...34
ML640 - Defining EVC Services ...37
ML640 - Defining Identification Rules ...39
Introduction General Safety Instructions
iv User Manual ML600
11. Ethernet Service Control...43
. / Users ...2
Default User Accounts...2
The User Accounts Pane...2
Password Control...4
Managing User Accounts ...7
User Session Information ...11
Editing Password in Session...12
IP Access Control ...13
Viewing IP Access Control List ...15
Procedure...17
Adding a Client IP Address to the Access Control List...18
Configuring the IP Access Control State...18
Editing the IP Access Control List ...19
Deleting a Client...19
SSH - Secure Shell...21
Managing SSH Communication...22
Generating SSH Client Key...23
SSH Server Overview...23
Generating SSH Server Key ...25
SSH Server/Client Authentication...26
Enable Authentication Control on SSH Server...31
0 * Using MetaASSIST View...2
Configuration Backup and Restore...2
Log Files Management ...5
Updating the System Software ...11
Restarting the System ...21
Using Web Browser...22
Support Page Overview ...23
Displaying the TL1 Document ...23
Configuration Backup and Restore...24
Retrieving the Logs ...25
Updating the System Software...26
Download ML Device Software...26
Activating the New Software...26
Configuring Sound Effects ...2
Managing Element Specific Alarms ...3
About Alarm Severity and Conditions ...4
Operating Alarms ...5
Systems Alarms View...6
System Status Monitoring...7
Network Element Monitoring...7
General Safety Instructions Introduction
Equipment Inventory and Status Monitoring...9
Ethernet Bridge Monitoring...15
MAC Forwarding Database Monitoring...16
STP Bridge Status Monitoring...17
STP Ports Status Monitoring ...20
Ethernet Service Monitoring...25
Ethernet Ports ...25
Ethernet Statistics ...31
Ethernet LAG Status Monitoring...34
Ethernet BW Monitoring ...34
HSL and MLP Performance Monitoring ...38
MLP PM Operations...38
Modem Ports ...47
High Speed Link Monitoring...61
Ethernet CFM ...66
About CFM...66
Ethernet CFM Configuration Window ...68
Ethernet CFM Configuration...69
Monitoring CFM Connections - TBD ...75
% ! / - 1 '$ % 2 " Recommended Test Equipment ...2
Power On Faults ...3
No Power Indication...3
ML600 does not start initialization...3
LED Fault Indications...4
Alarmed Conditions...6
Troubleshooting Workflow ...6
Field Descriptions...7
Alarmed Conditions Tables ...8
Copper Lines Troubleshooting ...24
Copper Lines Installation Problems...24
Repeated Copper Failure ...25
Copper Lines Fault Isolation Tools ...27
About Testing the Copper Pairs...28
Test Prerequisites...28
Line-impairment Test ...29
Crosstalk Test ...29
Noise-to-ground Test...30
Ethernet Service Troubleshooting...33
Non-Alarmed Service Problems ...33
Ethernet Service Fault Isolation Tools...36
Resolving Management Connection Problems ...45
Configuration Problems...45
Login problems (common for all interfaces) ...47
Introduction General Safety Instructions
vi User Manual ML600
Resolving Configuration Restrictions Due to Dipswitch Settings ...50
* ! ! 3 * * / * ! ! 3 # ) ML600 Models ...2 SFP Modules...3 Accessories ...5 Cables ...6 SW and Documentation ...7 $* ! ! 3 % " ! Specifications...2 Supported SNMP MIBs...4 Customer Logs...5
Spectral Compatibility Standards ...6
Available Spectral Modes...7
'* ! ! 3 4 5 / ! ML600 Factory Setup ...2
ML640 Factory Setup ...5
This chapter introduces Actelis ML600 chassis based systems, their basic architecture and the most common topologies in which it can be installed. Descriptions of the front and rear panels are also provided.
In This Chapter About ML600... 1-2 Deployment Topologies... 1-3 ML600 Architecture... 1-8 Management Applications ... 1-9
.
1
1
Introduction
Introduction About ML600
1-2 User Manual ML600
About ML600
ML600 family of Ethernet Access Device (EAD) products provides compact, cost-effective Ethernet in the First Mile (EFM) that deliver up to 45 Mbps symmetrical Ethernet traffic at fiber quality over existing copper pairs.
Depending on the model, ML600 devices can support up to 8 copper wires and fiber
connections and can be deployed in a Point-to-Point configuration, copper add-drop chain, or as the CPE in a Point-to-Multi-Point configuration with Actelis’ EFM switches. The ML600 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-T Ethernet interfaces and an optional 100Base-FX or 1000Base-FX Small Form Factor (SFP) port, the ML600 EAD platform enables assigning services and customers per port. A DS3/E3 uplink can be used to connect to legacy SONET/SDH networks.
ML640 EAD models allow service providers to create an intelligent Ethernet access edge with advanced bandwidth control and traffic management features, fully compliant with the MEF 9 and 14 specifications. This model enables flexible service provisioning using Ethernet Virtual Connections (EVCs). 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/Diff-Serv) classification with four traffic classes, RSTP/STP, bandwidth monitoring and Multicast/Broadcast limiting.
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 command line interface and SNMP, using standard MIBs for seamless integration with third party Network
Management Systems (NMS). Optional Features
• Optical Interfaces - a range of optical interfaces accommodates short and long distances
over speeds of 100Mbps or 1000Mbps.
• Copper Add-Drop EADs - allow interconnecting multiple nodes 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 passing the rest of the traffic. With up to 22.8Mbps aggregated traffic, the copper Add-Drop EAD is a powerful tool for distribution of Ethernet traffic across linear/ring copper networks.
Deployment Topologies Introduction
Deployment Topologies
ML600 system 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) 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-to-multipoint, are implemented using additional Actelis equipment such as ML1300 systems. Some common examples of physical installation topologies are described in this section. These include:
• Point-to-Point (on page 1-3)
• Point-to-Point Via Repeaters (on page 1-4)
• Point-to-Dual Point (on page 1-6)
• Drop-and-Continue (on page 1-6)
• Point-to-Multipoint (on page 1-7)
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.
Introduction Deployment Topologies
1-4 User Manual ML600
Point-to-Point via Repeaters
Point-to-point topologies are recommended for installations in which distances between ML CO to ML CPE do not exceed 5.5Km. XR239 repeaters can be used to extend the distances. Depending on the type of powering, PFU-8 equipment is installed at the CO side only (single-side powering) or at both the CO and the CPE side (dual-side powering). XR239 Repeaters are installed at various intervals.
Single Side Powering
This topology connects a Main Office site to a single Customer Premises location that is at a distance of up to 14.6Km/48Kft between the CO and the remote unit. It is implemented using two ML600 units: one at the Main Office and one at the Customer Premises.
The ML600 is installed at the head-end site along with the PFU-8 unit to power the XR239 repeaters. The repeaters are then installed and finally the remote unit is installed as shown in the figure below.
The copper pairs can be of length 3, 6, 9 or 12Kft. for each segment. In this deployment topology, a maximum of 5 segments (4 repeaters) can be deployed. This method allows the user to achieve a reach of over 48Kft. (using equal length segments of 12Kft.).
Figure 2: Single-side powering for repeaters.
Deployment Topologies Introduction
Dual Side Powering
Figure 3: Dual Side Powering
Point-to-Dual Point
In this deployment topology, a ML688 is installed on the head-end node and two ML644 units are installed at the remote site. Utilizing the dual HSL ports on the ML688, this topology allows the user to
achieve a P2Point-to-Dualpoint configuration of 4 copper pairs on each HSL.
Note: ML688 (Dual HSL) which serves up to 2 destination sites is installed at the ML CO site. However, any ML600 model can be used for Remote Terminal/Customer Premises equipment.
Introduction Deployment Topologies
1-6 User Manual ML600
Drop-and-Continue
In this deployment topology, an ML624 unit is first installed at the head-end site, an ML688 unit is installed in an outdoor cabinet 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.
Note: The number of intermediate sites (N) are limited by the HSL bandwidth shared between all chained NEs and the aggregated propagation delay on all NEs.
Deployment Topologies Introduction
Point-to-Multipoint
In this type of configuration, an ML CO chassis system (ML1300 in the example) supports a number of ML CPE remote sites (ML600 in the example). The maximum number of CPE sites differs according to the type of installed ML CO: ML130 supports up to 16 ML CPEs, while ML1300 supports up to 32 ML CPEs.
Introduction ML600 Architecture
1-8 User Manual ML600
ML600 Architecture
Actelis ML600 consists of the following main blocks:
• Ethernet Bridge - 802.1q VLAN aware Ethernet bridge that bridges packets between
Ethernet service ports and the HSL(s).
• 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 ML600 model dependent.
• G.SHDSL.bis modems - internal standard G.SHDSL (ITU G.991.2) modems with
extended capabilities, enabling modem rates of up to 5.7 Mbps. These, interface to the copper loops in the access network and convert Ethernet data to line coding required by Copper Pair wires and vice versa.
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 provided to carry services.
Management Applications Introduction
Management Applications
The following applications for Actelis system management are available:
• 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.
• TL1 - intrinsic user interface based on Transaction Language 1 (TL1™): a universal
transaction language developed by Telcordia Technologies, Inc. The application is provided with the system.
• MetaASSIST EMS® - is a java-based modular and scalable software application enabling system-level management to converging Actelis systems on the entire network. MetaASSIST EMS consists of MetaASSIST EMS server and MetaASSIST EMS client and requires the MetaASSIST View application. To obtain these software applications and the MetaASSIST EMS Online Help contact your local Actelis Networks sales representative, service representative or distributor.
This chapter describes the ML600 rear-panel and front-pane, provides information 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-4 ML600 Commissioning... 2-19
Getting Started Front and Rear Panel Descriptions
2-2 User Manual ML600
Front and Rear Panel Descriptions
This section describes the ML600 front and rear panel connections and LEDs.
Rear Panel Description
Note: All intrabuilding interfaces are to be used with shielded and grounded cables at both ends.
Table 1: Rear Panel Interfaces
Port Description
(1) GND/Earth Accommodates the ground wiring for the unit.
(2) Dipswitches (Covered by a non-transparent label). Used to configure the unit without
MetaASSIST View. The dipswitch settings override any software configurations performed via the MetaASSIST. Refer to Dipswitch Settings.
(3) 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.
(4) Reset Reset button. Restarts SW with current or factory setup depending on the time duration which it is pressed:
• Pressed for up to 10 seconds - restarts with with current configuration • Pressed for more than 10 seconds - restarts with factory setup
(5) AUX Connects the ML600 unit to the PFU-8. Allows monitoring PFU-8 via ML600. (6) ALARMS Two inputs (IN1/IN2)
(7) ALARMS One output (OUT)
(8) Power DC Barrier Terminal Block for DC power input.
Power requirement: -48/-60 VDC nominal (-40 to -72 VDC max), 2 Amp. max.
Front and Rear Panel Descriptions Getting Started
Front Panel Description
The ML600 front panel contains the Ethernet service and the management connection ports. For ease of viewing, the front panel contains all the indicators corresponding to both the front panel ports (Ethernet) and rear panel ports (copper pair, power), as well as system status indications.
Figure 8: Front Panel Connections Table 2: Front Panel Interfaces Description
Interface Description
(9, 10)
ETH, 100BaseFx, HSL and MGMT ports
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.
(11) Power Input power detection.
(12) Status Indicates general status of unit.
(13) Alarm Indicates alarm on head-end or one of the remote units. The alarm criteria of this LED are configurable according to System Configurable Attributes (on page
5) Alarm LED Indication.
(14) 100BaseFx or
1000BaseFx Available on some ML600 models. Duplex transceiver optical trunk socket. Supports various standard SFP module types. LC connector, simplex or duplex fiber optical cable assembly.
See SFP Card Models for a list of supported SFPs. (15) ETH 1..4 Four Ethernet 10/100 BaseT service ports
(16) MGMT Ethernet management connection.
(17) MLP Indicators Synchronization status of corresponding modem.
(18) CRAFT RS232 Local RS232 connection used for service and basic setup operations. Local terminal connection for CO installation.
Getting Started Connecting to and Navigating the MetaASSIST View
2-4 User Manual ML600
Connecting to and Navigating the
MetaASSIST View
With the MetaASSIST View Actelis supplies Graphical User Interface (GUI) application based on ML device CLI.
MetaASSIST View is a Java based GUI PC application for Configuration, Administration, Monitoring and Troubleshooting for all ML products. The application translates user actions into a stream of TL1 commands and displays TL1 responses and autonomous messages in an easily understandable form.
It is assumed that MetaASSIST View is already installed in the PC and all the required ML devices installation procedures described in Chapter 2 are completed. For MetaASSIST View installation instructions see the MetaASSIST View Installation Guide.
The ML device can be configured and operated using Command Line Interface (CLI) driven by TL1 agent, available on each ML device. This CLI is accessible locally via craft port or remotely by Telnet over IP via COLAN/ETH ports (requires configuration).
Connecting to the ML via the MetaASSIST View
The ML device can support up to 20 concurrent management sessions, 19 remotely (via LAN) and 1 locally (via craft port) connected management hosts.
CPEs that have not been assigned IPs can be accessed via a connection to the corresponding CO NE. This is used to provide basic monitoring and configuration functions. This can be used in installations in order to save on IP Addresses. Note that SNMP monitoring is disabled.
Note: MetaASSIST View performs auto-logout (for Write and Admin access privilege) if no user operation was performed for a pre-defined period (default: 30 minutes). Read only user, by default, is never logged out (can be reconfigured).
A MetaASSIST View session can be opened to the ML system either locally or remotely:
• 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. By factory setup, it is disabled.
• Ethernet ETH-{1-5 service ports. By factory setup, configured for service traffic only
Connecting to and Navigating the MetaASSIST View Getting Started
• HSL port. Enables indirect access to remote ML systems from the directly connected
system.
The following figure summarizes the management connections to the ML600 devices.
Figure 9: Available Management Connections
Local Connection to the ML
Note 1: If the MetaASSIST View is not already installed on the computer to be used for the commissioning procedure, install it according to the instructions given in the MetaASSIST View Installation Guide.
Note 2: Craft is limited to perform SW, Configuration Setup and Log files transfer.
To open a local session to the ML
1. Interconnect the computer's RS232 port and the ML device front panel Craft port using a standard RS232 cable.
2. Launch the MetaASSIST application by doing one of the following: • Click the MetaASSIST View icon on the Desktop, or
• from the Start menu, select Programs> Actelis Networks>MetaASSIST View.
Getting Started Connecting to and Navigating the MetaASSIST View
2-6 User Manual ML600
Note: For basic information on navigating the MetaASSIST Main window, refer to The MetaAssist View Workplace (on page 2-11). To resolve unsuccessful connections, see
Resolving Management Connection Problems (on page 45).
To locally connect via MetaASSIST View
1. Under Management Interface:
• Enable the Craft option.
• Select the computer COM port to which the ML600 unit is currently connected. • Set the Baud Rate to 9,600 Bps
Note: Computers are usually set to 9600 baud rate. If your computer is set to operate with a different baud rate (i.e. 19,200) set the field accordingly.
2. Under Login Details:
• Enter the User Name: admin (to perform configuration) • Enter the corresponding Password: admin
Connecting to and Navigating the MetaASSIST View Getting Started
Note: User Name and Password are case sensitive.
3. To save parameters for the next login, checkmark Save Parameters.
4. Click OK. The MetaASSIST View Main window appears showing directly connected ML device and all auto-discovered indirectly (via HSL) connected ML devices.
Remote Connection to the ML
Note: It is assumed that the CO ML has already been assigned an IP address.
To open a remote session to the ML
1. Verify that:
• The ML unit communicate 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
2. Launch the MetaASSIST application by doing one of the following: • Click the MetaASSIST View icon on the Desktop, or
• from the Start menu, select Programs> Actelis Networks>MetaASSIST View.
Getting Started Connecting to and Navigating the MetaASSIST View
2-8 User Manual ML600
Note: For basic information on navigating the MetaASSIST Main window, refer to The MetaAssist View Workplace (on page 2-11). To resolve unsuccessful connections, see
Resolving Management Connection Problems (on page 45).
3. Under Management Interface:
• Enable the TCP/IP option.
• Enter or select the IP Address of the CO to which a session will be opened.
Note: Inorder to search for defined systems use the Search option with defined IP addresses in the network.
4. Under Login Details:
• Enter the User Name: admin (to perform configuration) • Enter the corresponding Password: admin
Note: User Name and Password are case sensitive.
Connecting to and Navigating the MetaASSIST View Getting Started
6. Click OK. The MetaASSIST View Main window appears showing the ML CO and ML CPE units elements.
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: Auto-discovery detects only ML devices that are on the same local segment. Discovering Currently Active ML device in the LAN
Note: Only ML systems that have been assigned an IP address can be discovered.
To discover currently active ML device in the LAN:
1. In the Connect dialog box, click Search. The Search dialog appears.
Getting Started Connecting to and Navigating the MetaASSIST View
2-10 User Manual ML600
Note: ML device that cannot be managed by this version of MetaASSIST View are grayed out.
Viewing and Selecting Previously Monitored Systems
To view and select previously monitored systems
1. In the Connect dialog box, select the TCP/IP Address radio button.
2. From the adjacent list box, choose the system to be monitored according to its IP address
Connecting to and Navigating the MetaASSIST View Getting Started
3. In the Login Details, enter your User Name and Password and click OK.
The MetaAssist View Workplace
The MetaASSIST View Main window consists of the following areas:
• Menu bar - contains various options. See Menu Bar (on page 2-13).
• NE/Links - provides access to two tabs:
• NE tab - this tab is displayed by default. It displays the host CO to which a session
was opened, and the corresponding CPE elements. It also provides access to the configuration and monitoring options of each ML device at the site. See Physical Tab (on page 2-15).
• LINKS tab - is used to monitor status and setup of the particular Ethernet
Connection (already defined via NE tab).
LINK tab also provides Ethernet Connection Fault Management (CFM )
configuration and monitoring options applicable per group of NE participating in a Ethernet Connection. This tab is described in detail in Ethernet CFM
Getting Started Connecting to and Navigating the MetaASSIST View
2-12 User Manual ML600
• Work Area - displays panes corresponding to the item selected the selected items. • Alarms area - shows the alarms of the currently selected NE. A summary of the alarms is
displayed in the Status Bar
Note: View areas are resizable. Where applicable, panes with tables have a multiple selection feature allowing you to click and drag to select multiple rows.
Connecting to and Navigating the MetaASSIST View Getting Started
Menu Bar
The menu bar provides you access to the functions as described in the following table.
Table 3: Menu Bar Options
Menu Item Description of Options
Session menu. Provides element connection options, session information and password editing options.
• Connect Network Element - used to open a direct
session to a new network element
• Disconnect Network Element - used to disconnect
directly connected network element
• Session Information - provides a summary of the
currently open session.
• Edit Password - used to change the password of the
current user.
• Generate SSH Client Key - for secure version only) -
used to generate new keys for secure connection with ML device (SSHv2) with or without a passphrase
• Exit - closes the application.
View Menu. Provides options that determine how the information is displayed and refreshing options:
• Refresh - updates information of the currently
displayed pane.
• Refresh All - updates information on all panes. • Navigation Tree Order - Alphabetical - use to sort the
Topology tree elements alphabetically. (Option is available only when the MetaASSIST View session is disconnected.)
• Periodic Refresh - when enabled, information
Getting Started Connecting to and Navigating the MetaASSIST View
2-14 User Manual ML600
Menu Item Description of Options
Tools menu. Provides Wizards that guide you through the initial setup procedures, access to TL1 options, log and performance reports saving and configuration of audible alarm notifications.
• Initial Setup Procedure - Wizard that guides you
through the initial configuration procedures.
• Execute TL1 Command.- accesses TL1 Command
dialog.
• View TL1 Log - used to view TL1 Command history
and autonomous messages log.
• View Support Logs - enables field engineers to save,
configure and initialize the Info, Install and Blackbox log files.
• Save All Logs as - used to save all log files to a
specified location.
• Save Performance Report - saves the performance
report on the local disk.
• Sound Effects - used to configure audible alarm report
indications.
This menu provides a range of configuration options that can be applied to a selected Group and is implemented on all NEs belonging to that group.
• Users - user account management options.
• IP Access Control - Access Control List management
options applied to the selected NEs.
• SNMP - SNMP configuration options for selected NE
or Group.
• Software Release - provides S/W download,
activation and SW commit options. Used for downloading new SW to the selected NEs.
• Date and Time - Set Local Time - used to set the date
and time to the selected NEs.
This menu provides help and MetaASSIST View version information.
• Actelis Systems Online Help - contains full user
manual of the ML600 with advanced search capabilities.
• About MetaASSIST View - MetaASSIST View
Connecting to and Navigating the MetaASSIST View Getting Started
NE Tab
The NE tab is selected by default. It provides configuration and monitoring options applicable per each NE separately.
NE tab space is divided to Topology Tree and NE Navigation Tree. Topology Tree
Topology Tree displays those ML device (Network Element or NE), to which a session was manually opened from the PC (locally or remotely). If the NE performs as CO (Central Office) device, then all corresponding CPE (Customer Premises Equipment) NEs are also displayed in a sub-directory of the CO NE
The content of a single NE Navigation Tree depends on the login user privileges. Some panes require specific (Write or Admin) permissions and are available only to users with the
appropriate access levels. Adjacent to each element in the tree there is a name and an icon as shown in the following table. The icon displays NE in the tree and its color according to the most severe alarm on it.
Table 4: Tree element Icon meanings
Tree Element
Icon Meaning
My Computer
<IP Address> Indicates MetaASSIST View running on your computer and shows the IP address of the computer. When the computer is not connected to the LAN (ML NE is monitored via craft), the loopback IP address appears (127.0.0.1). When the IP address of the computer was changed, MetaASSIST View will update the displayed value only when MetaASSIST View is re-started. Represents connected ML1500 or ML1300.
Represents connected ML50 or ML600 series. Represents connected ML100, ML100E1 or ML130. Displays NE trying to connect as a slanted blue icon. Note: You cannot drag/drop items in the Navigation tree.
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;
Getting Started Connecting to and Navigating the MetaASSIST View
2-16 User Manual ML600
In most cases, all HSL linked NEs are automatically added during connection. TID and IP (or HSL-x when an IP is unavailable) are displayed for these NEs. For other cases, see Logging In descriptions.
Content of the single NE Navigation Tree depends on:
• Logging In User Privilege - some panes require specific (write or admin) permissions and
are available only to users with the appropriate access privileges.
• IP address availability - File Transfer Based features are supported on devices without a
configured IP address. These features include SW load, Log File, Configuration Setup, and Up and DownLoad operations. SNMP agent is unavailable while IP address is not provided per NE.
Network Element Tree
When NE in the Topology tree is selected, the Network Element tree displays selected NE content Navigation Tree. The Navigation Tree includes an expandable/collapsible hierarchy and alphabetical list (user selectable). By clicking a tree element, the appropriate pane appears.
Connecting to and Navigating the MetaASSIST View Getting Started
The following table provides the meaning of each icon that appears in the Navigation tree as well as in the work area and system alarms table.
Table 5: Icon meanings
Icon Meaning
Gray Icon - for the following cases:
• No critical, major or minor alarms;
• Entities that have no alarm status (such as Users); • Entities are disabled.
Red Icon - Critical Alarm Orange Icon - Major Alarm Yellow Icon - Minor Alarm
Icon with an x - Inaccessible element Tool Icon - Maintenance mode
The Navigation Tree can be alphabetically sorted. This can only be applied before a session is connected. If you are running a session, you must disconnect to apply alphabetical tree order. To alphabetically order the tree, from the View menu option, select Navigation Tree Order -> Alphabetical.
Content of the single NE Navigation Tree depends on:
• Logging In User Privilege - some panes require specific (write or admin) permissions and
are available only to users with the appropriate access privileges.
Getting Started Connecting to and Navigating the MetaASSIST View
2-18 User Manual ML600
Current Alarms Area
The Current Alarms Area displays all the current alarms of the Monitored NE alarms. Alarms are sorted according to severity, starting with the critical alarms, and then by date-and-time. You can scroll through the table to view additional existing alarms. Clicking on any of the alarms navigates to the appropriate pane.
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.
ML600 Commissioning Getting Started
ML600 Commissioning
This chapter provides information how to commission the ML600 in its various system deployment topologies.
You can perform the commissioning procedure using either the wizard provided in the MetaAssist View or by following the step-by-step instructions.
Initial Setup Procedure (Wizard)
MetaAssist View provides an initial setup procedure Wizard that guides through the required configuration operations. This procedure is available for a directly connected CO element. This section describes the procedures to perform before running the Wizard and how to run the Initial Setup Wizard.
Prior to performing a configuration setup (using the Wizard), verify:
1. ML600 or ML50 system installed on Remote site is powered up, connected to the copper
plant (via MDF) and to adjacent Ethernet equipment.
2. All modem ports on both Actelis systems are connected via valid (non-faulty) copper
loops;
3. MetaASSIST View application is available on PC and connected with Actelis system
located on CO via craft port.
Running the Initial Setup Procedure (Wizard):
After verifying that the above requirements have been met:
1. Launch MetaASSIST View and Login to the Actelis system on Central Office using factory user accounts, see Connecting to Actelis systems via MetaASSIST View. 2. In the Topology Tree, select the CO element.
3. From the MetaAssist View Tools menu, select Initial Setup Procedure and follow the displayed prompts. (If the Initial Setup Procedure is not enabled, verify that a CO was selected and not a CPE
1. ML CO Physical Site Installation
Before you begin the commissioning procedure, verify that the ML system at the CO site is installed properly according to the instructions in the corresponding (ML130/1300/2300) Quick Installation Guide:
1. System is mounted at the Central Office site.
Getting Started ML600 Commissioning
2-20 User Manual ML600
3. System is properly Grounded.
4. Copper lines are connected to the ML CO device.
5. GPI/GPO dry contacts are connected to Environmental Controls/External Alarms or
External Controls.
6. Power connections and relevant issues (AC/DC or DC power, installation of fuses, etc.)
are implemented properly.
7. ML CO is powered up, and power on sequence is completed.
8. Fan assembly is working
9. For regenerated (repeated) span deployment scenarios: • Configure the PFU-8 using its dipswitches.
• Install according to the PFU-8 Quick Installation Guide. • Connect PFU-8 to the ML product.
• Power up the PFU-8 (where up to eight PFUs can be cascaded) in the Central Office
Site.
10. This completes the physical installation of the ML device in the Central Office
environment .
2. ML CO Configuration - for Link Verification
This procedure sets up the ML CO for communication with ML CPEs as the CPEs are installed.
1. Open a local session to the MetaASSIST View (see Local Connection to the ML).
2. Verify no HWFLT or PROGFLT alarm condition exists. Any other alarms are not
relevant at this point.
3. For ML600 and ML50 - the HSL(s) and MLPs are ENABLED by default and automatically monitored for alarm conditions. It is require to:
o Configure the HSL to -O (Office) mode
o Disable all unused MLP ports (to prevent alarm condition control on these ports
and to allow HSL operations.)
o HSLDOWN alarm condition will appear on HSL while at least one modem is not
synchronized.
3. ML CPE Physical Site Installation
1. For a 'Simple' link (without repeaters and without Drop and Continue), refer to 1. CO
Site Installation for the ML device installation at Customer Premises / Remote Terminal site.
ML600 Commissioning Getting Started
2. If you configured the ML CO device according to 2. ML CO Configuration - for Link
Verification, then the copper connectivity can be verified by ensuring the MLP and HSL LEDs will GREEN (blinking or steady), indicating the modems of ML devices on CO and CPE sites are synchronizing/ed.
This completes the physical installation of the ML device in the Customer Premises / Remote Terminal environment.
3. For Drop-and-Continue spans deployment scenarios (P2P and P2MP):
a) Repeat Step-2 for each ML600 CPE device. At each site check that:
o The ML device Modems 5-8 and HSL-2 LEDs are GREEN (blinking or steady),
indicating synchronizing/ed modems towards the previous ML device (upstream to CO).
o Downstream Modems 1-4 and HSL-1 should be off (as not synchronized yet).
b) Continue according to 4. On CO: Commit Customer Site Installation (on page 2-21)
4. For regenerated (repeated) span deployment scenarios (P2P and P2MP):
• All repeated segments should be installed starting from the CO towards the CPE/RT. • This installation order allows LED indication assistance, available on each
synchronizing/ed modem port of XR239.
• Install the ML CPE last according to 1. CO Site Installation.
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
• If necessary, use the MLP Ports pane to troubleshoot.
2. Configure the IP connectivity attributes of the: • ML CO device - Management Interface pane • ML CPE device - NEs Linked via HSL pane
Getting Started ML600 Commissioning
2-22 User Manual ML600
3. For Drop & Continue deployment the following three operations should be repeated on
each ML 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.
4. 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.
5. Set System ID to provide unique identification of the remote ML device. The step may be
skipped, the serial number of installed equipment must be booked and the location of installation must be specified to provide System ID configuration later.
5. ML CO - HSL Operation
For the following steps, all Actelis systems involved in the deployment scenario should be installed. Actelis systems should be 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 Calibration BW (Best Efforts or Specify Target BW), Target SNR margin, DSS Profile and S. Mode. 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).
3. By this step, all Actelis systems copper/equipment deployment is completed.
4. In case of P2P deployment scenario, factory default of ML600 and ML50 Actelis systems
provides bi-directional traffic, which is transparently tunneled between each Ethernet port and HSL port. For CHASSIS Actelis systems and more advanced Ethernet topology, configuration should be continued as defined below.
ML600 Commissioning Getting Started
6. ML CO - Service Configuration
Determine the relevant Ethernet traffic topology for your site prior to the Actelis systems configuration, see L2 Network configuration in various topologies (on page 15). 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.
1. Configure Ethernet bridge-wide features:
• 802.1Q/D - where VLAN-aware (802.1Q) is configured by default. Modes should be
set equally on all Actelis systems installed in the particular deployment.
• Aging Time - Tune the Aging time value.
• STP configuration - STP is used to resolve Ethernet loops. It can be enabled at
bridge and at port level. By default, STP is DISABLED at bridge level and enabled at port levels. If enabled at bridge level, STP is also enabled per port.
For installations where HSL is the only Ethernet link to customer's LAN via Actelis systems and to separate Provider WAN and Customer LAN:
o Disable STP on ML CO HSL port - this provides "Always Forwarding" behavior
for service traffic and drops BPDUs.
o Disable STP at bridge level on ML CPE installed as the Customer LAN Access.
2. Configure Ethernet Service facilities (physical interface parameters):
• In models ML600 and ML50 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.
3. Configure Service Connection by VLAN:
• In ML600 and ML50 models, bi-directional traffic is transparently tunneled between
each Ethernet port and HSL port. There are from 1 to 5 Traffic VLANs (depending on model) provided by default.
• To define or change traffic behavior VLAN should be re-configured depending on
the ML device installation site (Access to Provider WAN or Access to Customer LAN). To decide about Service Traffic Topology to use, see L2 Network configuration in various topologies (on page 15).
4. Configure Service Connection Rate limiting/QoS parameters:
QoS features are applicable per Ethernet port. Configuration of parameters should be coordinated with selected Ethernet topology, see step 3.
Getting Started ML600 Commissioning
2-24 User Manual ML600
QoS features are:
• Ingress rate limit (any or broadcast/multicast incoming traffic policing) • Egress rate limiting (all outgoing traffic shaping)
• Classification to 4 Classes/Queues by L2 Priority, L3 Priority (ML50, ML600 only)
or per Port forced priority - applicable per port on ML50, ML130/ML1300 and ML600 models;
• L2 and L3 Priority classification rules are configurable per Actelis system; • Queues Scheduler type - bridge-wide configurable in ML50 and ML600.
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 15).
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
ML600 Commissioning 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
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
Overview... 3-2 NE Management Communication Protocols... 3-3 Craft Port Configuration... 3-4 IP/LAN Connectivity on Directly Connected NE... 3-5 IP/LAN Connectivity on Indirectly Connected NE ... 3-8 SNMP Agent and Trap Parameters... 3-9 L2 (MGMT VLAN) and L3 (IP) Connectivity... 3-13 System Name Configuration ... 3-15 System Time and Date... 3-16
.
3
3
Management
Management Configuration Overview
3-2 User Manual ML600
Overview
As described in Connecting to the ML via the MetaASSIST View (on page 2-4), each ML NE can be accessed either locally or remotely using:
• Serial Craft connection
• Ethernet out-band - via COLAN/MGMT port • In-band - via Service ETH ports and HSL ports
Remote ML NEs can be accessed using:
• Embedded Operational Channel (EOC) - single SHDSL mode-based connectivity that is
always available for the STU-R NE. EOC is used to detect STU-R NE and to enable remotely configuring IP/VLAN connectivity from STU-C NE (NE with HSL configured in –O mode).
• IP-less Ethernet - based on 802.1ah Fast Operation Administration and Management
(OAM). This connectivity is available between all ML NE models. IP-less Ethernet allows full management access, including file transfer (except in ML688). IP-less connectivity is available for CPE NE, where STU-C (CO installed) NE requires an IP address.
SNMP agent is inaccessible on an IP-less connected NE and IP-less access from the Peer can be controlled (enabled or disabled).
• IP/Ethernet connection - requires the configuration of IP Address, Gateway and Subnet
Mask configured on the NE. The MGMT VLAN must be consistently configured on all
NEs.
Note: The IP/Ethernet access on each NE can be controlled and additionally secured (by ACL or SSH).
NE Management Communication Protocols 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
• 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.
Management Configuration Craft Port Configuration
3-4 User Manual ML600
Craft Port Configuration
This procedure describes how to configure the Craft port interface. By default, the baud rate of the ML device Craft port is set to 9,600 bps. You can modify the baud rate to 115,200, 57,600, 38,400, 19,200 or 4,800 bps. After modifying the baud rate, set the PC to the same baud rate.
Note: You may configure the Dial-up modem to operate as an additional craft port. See Dialup Modem Port Configuration.
To configure the Craft interface
1. In the Network Element tree, open Management Interfaces. The Management Interfaces pane opens.
2. In the Craft Interface section, click Configure. The Configure Management Craft Interface dialog appears.
3. From the Port Rate box, select the baud rate. 4. Click OK.
IP/LAN Connectivity on Directly Connected NE Management Configuration
IP/LAN Connectivity on Directly
Connected NE
NEs can be connected to the management LAN using an out-of-band, dedicated management port COLAN (MGMT) connection, or an in-band connection that is implemented through any service port (ETH or HSL).
Note: COLAN (MGMT) port is disabled by factory default.
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 33).
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.
L2 (MGMT VLAN) Connectivity
ML600 systems (except for ML640) operate in either 802.1Q (default) or 802.1D bridge modes. ML640 units operate only in 802.1Q mode.
Configure the units Management LAN access according to the operation mode:
• 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 10).
• 802.1D bridge mode (VLAN unaware) - ML600 (not relevant for ML640), by factory
setup, is accessible for untagged traffic via any port.
To enable tagged management traffic access to ML600 in 802.1D bridge
mode
1. In the Network Element tree, open Ethernet Bridge. The Ethernet Bridge pane opens in the work area.
Management Configuration IP/LAN Connectivity on Directly Connected NE
3-6 User Manual ML600
3. From the Mode box, select the mode 802.1D.
4. For in-band management you need to specify management traffic type (VLAN-tagged or
untagged) and for tagged traffic (clear the Untagged check box) to set the Management VLAN ID.
5. Click OK.
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.
