UserManual_NID_5-2_4-9-1_Ra | Transport Layer Security | Computer Network

User Manual

Release 5.2 and 4.9.1 Revision a

EtherNID™ MetroNID™

Document revision number: a. Last updated on 13 June 2011, to accompany software release 5.2 and 4.9.1. Accedian Networks, EtherNID, ESAP, EtherSHELF, Fast-PAAs, High Performance Service Assurance, MetroNID, Plug & Go, Packet Performance Assurance, Performance Assurance Agent (PAA) and SLA-Meter are trademarks or registered trademarks of Accedian Networks Inc. All other brand and product names are trademarks or registered trademarks of their respective corporations. The mention of any product does not constitute an endorsement by Accedian Networks Inc. The content of this manual is provided for informational use only, is subject to change without notice and should not be construed as a commitment by Accedian Networks Inc. Accedian Networks Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. Except as permitted by such lease agreement, no part of this publication may be reproduced, stored in any retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without prior written consent of Accedian Networks Inc. Changes are periodically made to the information herein; these changes will be incorporated into new editions of this publication. Accedian Networks Inc. may make improvements and/or changes in the products and/or software programs described in this publication at any time. If you have comments regarding this manual or the products it describes, address them to: Accedian Networks Inc. Attention: Publications 4878, Levy street, Suite 202 Saint-Laurent, Québec Canada H4R 2P1 Tel: (514) 331-6181 Fax: (514) 331-2210 Toll free: 1-866-685-8181 Accedian Networks Inc. may use or distribute whatever information you provide in any way it believes appropriate without incurring any obligation to you. Copyright © 2005-2011 Accedian Networks Inc. All rights reserved, including those to reproduce this publication or parts thereof in any form without permission in writing from Accedian Networks Inc.

Table of Contents
ABOUT THIS MANUAL ....................................................................................... 7
Organization ............................................................................................................................................... 7 Conventions ................................................................................................................................................ 8 References .................................................................................................................................................. 9

INTRODUCTION TO THE ETHERNID AND METRONID .................................. 10
Applications .................................................................................................................................................11 Mobile Backhaul .......................................................................................................................................11 Assured Business Services ........................................................................................................................12 Carrier Ethernet Exchange Services ..........................................................................................................12 Carrier Ethernet Global Interconnect .........................................................................................................13 Enterprise WAN QoS ................................................................................................................................13 Ethernet Service Creation ..........................................................................................................................14 Features ........................................................................................................................................................15 Service Assurance .....................................................................................................................................15 Service Creation ........................................................................................................................................20

MANAGING THE UNIT ...................................................................................... 25
About the Management Web-Interface .....................................................................................................26 Starting the Management Web-Interface ..................................................................................................28 Physically Connecting to the Unit .............................................................................................................28 Logging In .................................................................................................................................................28 Working in the Home Page .......................................................................................................................29 Modifying the Unit Identifier ....................................................................................................................30 Managing SSL Certificates ........................................................................................................................31 Configuring the Logical Interfaces ............................................................................................................34 Adding or Editing a Logical interface .......................................................................................................36 Configuring a Logical interface for Beacon ..............................................................................................40 Adding or Editing a Route .........................................................................................................................40 Finding a Host (Ping and Traceroute) .......................................................................................................41 Using the Serial Console ...........................................................................................................................42 Managing Network Inventory ....................................................................................................................44 Viewing Network Inventory ......................................................................................................................44 Logging in to a remote unit .......................................................................................................................46 Sending a Beacon Frame ...........................................................................................................................46 Managing Sessions .......................................................................................................................................47 Locking or Unlocking User Sessions ........................................................................................................48 Terminating a User Session .......................................................................................................................48 Configuring Session Options .....................................................................................................................49 Managing Users and Privileges ..................................................................................................................51 Setting Up the Administrator Account ......................................................................................................51

3

Defining Permission for a Group of Users ................................................................................................51 Adding or Editing User Accounts..............................................................................................................53 Administering User Account Privileges ....................................................................................................54 Changing Passwords ..................................................................................................................................54 Using a RADIUS Server for Authentication .............................................................................................55

CONFIGURING THE UNIT ................................................................................. 57
Understanding Operation Modes ...............................................................................................................57 Setting Operation Mode ..............................................................................................................................61 Setting Date and Time .................................................................................................................................62 Setting SyncE ...............................................................................................................................................65 Setting up DNS .............................................................................................................................................66 Setting IGMP Version .................................................................................................................................67 Setting S-VLAN Ethertype .........................................................................................................................67 Upgrading the Firmware ............................................................................................................................67 Importing/Exporting the Unit’s Configuration ........................................................................................68 Viewing CPU Usage .....................................................................................................................................70 Rebooting the Unit .......................................................................................................................................71 Restarting the Unit ......................................................................................................................................71 Resetting to Factory Defaults .....................................................................................................................72

MANAGING PORTS........................................................................................... 73
Setting up Ports ...........................................................................................................................................73 Setting up Media-Selection .........................................................................................................................76 Setting up Port Protection ..........................................................................................................................77 Setting up Fault Propagation......................................................................................................................78 Viewing Port Statistics ................................................................................................................................78 Setting up Port PHY ....................................................................................................................................84 Viewing SFP Information ...........................................................................................................................86 Testing a Cable ............................................................................................................................................88

4

............................................................................................................................................164 Setting up Loopback Messages ...............90 Defining Filters .....................124 Setting up a Traffic Shaper ............................................................................................................................................................................................................................118 Setting up Traffic Shaping ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................128 Setting up an L2 Tunnel .......................110 Viewing Traffic Regulator Statistics ......172 Viewing Packet Loss Results .................................................................................................173 Setting up CFM Defaults ..............................................................144 Deleting a Probe ..........................................................................................................135 Viewing OAM Events ...........................................................135 Setting up an OAM Instance ....................................130 MONITORING NETWORK PERFORMANCE ........................................100 Setting up VID Sets ...........148 Viewing Probe Status ........................................................................127 Using Layer-2 Protocol Tunnelling ..................................................................................................................................................................................................................................................................................................................................................................................................................137 Viewing OAM Status ........................................................................................................................................................................................................................126 Viewing General Traffic Shaping Statistics ...........................................................................................125 Viewing the Real-time Queue PCP Lists ..........143 Setting up a Probe ..........................................................................................................................138 Viewing OAM Statistics ........................................................................................................................................................................................................................................................................................................................................................123 Setting Global Traffic Shaping Parameters for the Network Port ....................................................................................................................................................................................139 Using the Performance Assurance Agent™ .......................................................................96 Setting up Traffic Policies ................................123 Setting the PCP-to-Queue Map ............166 Setting up Delay Measurements ........108 Setting up Traffic Policies ......................................................................................................................93 Configuring an IPv4 Filter ...................127 Viewing Traffic Shaping Statistics ....................................107 Setting up Bandwidth Regulator Sets ..117 Understanding Traffic Shaping ............................................................................. 90 Understanding the Creation of Ethernet Services ...........................................................................................................................................174 5 ..........................................................................................................................................................................................................................................................................................................153 Setting up CFM .......................................................................................................................................................................................................101 Setting up Bandwidth Regulators ...............................................................................170 Setting up Packet Loss Measurement ...............................149 Viewing Probe Results .........105 Setting up CoS Profiles ..........150 Using Service OAM .................................................................................................................................................................................................................................................................................................................................................153 Setting up Link Trace Messages ...................................................................168 Viewing Delay Measurement Results ........................................... 135 Using Ethernet OAM .................................................................MANAGING TRAFFIC ............................................92 Configuring a Layer-2 Filter ........................................

..................................................................................................................................................................................................209 Transferring History Files ................................................................................................................ 194 Understanding Loopback Testing .....................................................................................................................184 Viewing the Traffic Analyzer Test Results .........................................................195 Setting up and Enabling Loopbacks ...206 Enabling the EchoAgent™ .................................................178 Starting the Traffic Generator and Viewing Test Results ................................................176 Setting up the Traffic Generator ..................................................................................................................................................................................................................192 MANAGING LOOPBACKS .............................206 Managing the SNMP Agent .........186 Setting up a Test Suite ...........................................................................................................200 Viewing Chassis Alarms .208 Managing History Files ..............................182 Setting up the Traffic Analyzer ............................................TESTING NETWORK PERFORMANCE ..........................198 Setting General Alarms ...............................................................................209 Creating History Files .............................................................................................199 Viewing Alarms................................................................................................................................................................................205 Defining Syslog Parameters ................................................................210 6 .........................................................................................................187 Running a Test Suite and Viewing Test Reports ......................................205 Sending Syslog Messages to a Remote Location .....204 Managing Syslog Messages ......................................................................................................................................................................................................... 176 Understanding Traffic Generation and Analysis ..............................................................198 Customizing Alarms .......194 Enabling or Disabling a Local Loopback .........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................205 Managing the EchoAgentTM ..................................................................................................................................197 MANAGING ALARMS AND SYSTEM MESSAGES ...............................................................................................................................................195 Enabling or Disabling a Remotely Controlled Loopback ...................207 Setting up the SNMP Trap Receivers .................................................... 198 Managing Alarms ......................................................................................................................................................................................................207 Enabling the SNMP Agent .................................................................................................................

The term ―management web-interface‖ refers to the web-based interface that comes with the unit. service providers and cable MSO personnel to provide service assurance and service creation solutions to their clients. 7 . The Introduction chapter provides information about technologies and standards used in Accedian‘s equipment. This document is intended to help the network designers and network administrators in the ® design. several chapters of detailed procedures and examples of networking scenarios. The chapters containing information and procedures for configuring the equipment are as follows:  Managing the Unit  Configuring the Unit  Managing Ports  Managing Traffic  Monitoring Network Performance  Testing Network Performance  Managing Loopbacks  Managing Alarms and System Messages The chapter on Networking Scenarios shows configuration examples of networking scenarios. configuration and use of Accedian‘s network interface devices such as the EtherNID and ® MetroNID .About This Manual This document provides information about the technologies and standards used in Accedian Network‘s equipment and procedure to help wireless operators. Organization This document contains three main parts: an introduction. The term ―unit‖ in this manual refers to any one of these network devices.

Note: a tip or suggestion on how to carry out a task Warning: potential for injury (to people) Caution: potential for damage to equipment Danger: likelihood of serious injury. the 2 refers to SFP modules. If the same parameter is labelled differently on the pages. Menu navigation example: CFM > DMM > Configuration Brackets [ ] are used when several options are available and you need to select a specific option. one parameter table covers both the summary page and the detailed page. as far as is possible. So. including death 8 .Conventions Tables of parameters are present to help you understand the function of each parameter that is displayed for a particular feature. The initial display for some features is a summary page of all elements. In the alarm descriptions. For example. For example.01 means SFP-A temperature high alarm. in the following line you need to select a specific port name when you reach the PHY page: Port > PHY > [Port name] Alarm numbers are composed of three parts: x.0001. For such features. 2. then both labels are listed in the table. Commands and keywords are in bold.0001.yyyy. depending upon what the component number yyyy is. The second number (yyyy) refers to the specific component. in 2.zz. <SFP module> can refer to any SFP module. The parameters are listed in the order that they appear on the page. 0001 is for SFP-A and 01 means temperature high alarm. from which you can then select one element in order to get more detailed information on a separate page.01. The third number (z) is the specific alarm code. The first number (x) refers to a general category.

1731 : OAM functions and mechanisms for Ethernet-based networks  Technical Specification – MEF 17 – Service OAM Requirements & Framework – Phase 1  Technical Specification – MEF 6.1ah . technical specifications and technologies.Connectivity Fault Management  IEEE 802. This document provides basic information on the standards and technologies. For more information about the standards and technical specifications.1 – Ethernet Services Definitions – Phase 2  RFC-2544 – Benchmarking Methodology for Network Interconnect Devices  Technical Specification – MEF 9 – Abstract Test Suite for Ethernet Services at the UNI  Technical Specification – MEF10. refer to the following:  IEEE 802.Provider Backbone Bridges  ITU-T Y.References The use of equipment such as the EtherNID and MetroNID involves the understanding of different networking standards.1ag .2 – Ethernet Services Attributes Phase 2  Technical Specification – MEF 14 – Abstract Test Suite for Traffic Management Phase 1  Technical Specification – MEF 22 – Mobile Backhaul Implementation Agreement Phase 1  Technical Specification – MEF 26 – External Network Network Interface (ENNI) – Phase 1  RFC-2544 – Benchmarking Methodology for Network Interconnect Devices 9 .

carrier-grade in-line element.Introduction to the EtherNID and MetroNID Accedian Networks' EtherNID and MetroNID Network Interface Devices (NID units) provide demarcation between the service provider and subscriber. With a comprehensive selection of models to choose from. including the rack-mount EtherSHELF™ enable easy installation at the customer premise. refer to Accedian‘s website at www.accedian. With transparent fail-over.com. Accedian‘s unique hardware-based architecture delivers the most precise in-service measurements of any demarcation device. no fans or moving parts and three-way redundant power. NEBS Level-3 certification. without adding delay or delay variation to passthrough traffic. there is an EtherNID or MetroNID unit that fits your particular application and network location. cell site or CO. while at the same time providing microsecond measurement resolution and real-time processing of every packet flowing through the unit. cost efficient. For more information about each device. A variety of mounting options. Unlike store-and-forward architectures. enabling end-to-end service provisioning and high performance service assurance. and define the boundaries of your network. EtherNID and MetroNID demarcation units are truly carrier-grade. The EtherNID and MetroNID units provide advanced performance testing and service creation capabilities in a compact. All EtherNID and MetroNID NIDs use Accedian‘s patent-pending Fast-PAAs™ processing engine. the silicon data-path of the Fast-PAAs engine provides wire-speed pass-through performance without introducing addition or frame delay. 10 .

loopback testing. revenue-driving SLAs and dependable performance. IP/MPLS and converged networks. For more information about Accedian‘s EtherNID and MetroNID platforms‘ possible applications. The world‘s leading 4G/LTE deployments rely on Accedian Networks to deliver unparalleled real-time performance. hitless throughput and remote loopback testing. 11 . real-time services over Ethernet.Applications Accedian Networks is the leading provider of high-performance service-assurance solutions which enable service providers to deploy. guaranteed throughput and carrier-grade reliability—as well as operational efficiency that reflects today‘s competitive telecom marketplace. Services created and assured by Accedian Networks‘ High Performance Service Assurance Platform benefit from real-time service mapping. low delay and delay variation. in-service monitoring. mesh-network support and advanced traffic control edge-to-edge. 4G / LTE wireless backhaul. enabling Carrier Ethernet to be used effectively for backhauling mobile broadband applications.accedian. Mobile Backhaul Accedian provides the industry‘s most accurate high performance backhaul assurance with micro-second delay and delay variation measurement. service management and demarcation that enable you to establish end-to-end operational control. real-time business and carrier hand-off applications require ultra-low delay and delay variation.com. traffic conditioning. refer to Accedian‘s website at www. High-performance 3G. monitor and maintain high performance.

VoIP.Assured Business Services Accedian enables and assures SLA-backed business services. data center interconnection. remote storage and transactional services with carrier-grade availability. QoS-optimized EVCs. video conferencing. QoS performance and realtime visibility. including transparent LAN access. Carrier Ethernet Exchange Services High performance service assurance enables wholesale providers to offer reliable Ethernet services wholesale to generate new revenue by extending Ethernet services to off-net locations with fully-assured. assuring end-to-end SLA performance while providing individual performance metrics for each Operator Virtual Connection (OVC). A MetroNID unit effectively establishes E-NNI handoffs and reaches remote customer sites with complete control and visibility. 12 . Establish end-to-end OAM.

providing end-to-end control over real-time applications. Enterprise WAN QoS Accedian‘s applications for the Enterprise optimize WAN performance and accelerate critical business applications with traffic shaping. Accedian Networks‘ delay-free and delay-variation-free demarcation solutions bridge segments and monitor network boundaries. with Accedian Networks' SLA-Meter™.Carrier Ethernet Global Interconnect Deploying Accedian‘s MetroNID units at the ENNIs joining multiple operator networks enables performance assurance for services spanning multiple carriers. filtering and switch-free aggregation for each Class-ofService. technologies and manufacturers—in-line and in real-time— without affecting customer traffic. peering fabrics. The same high-performance service-assurance platform used by service providers can be used to continuously monitor and optimize the performance of every application‘s data flow. 13 .

Ethernet Service Creation Create fully transparent Ethernet Virtual Connections (EVC) over any network—without replacing or configuring network elements. and filtering directly at the demarcation point. traffic shaping. Optimize service and core network performance with hardwarebased rate limiting. 14 .

For more information about service-assurance features for Accedian‘s EtherNID and MetroNID. remote troubleshooting. troubleshooting. loopback testing. Service Demarcation Define the boundaries of your network and services with intelligent demarcation between your network and those of your customers and third-party network operators. refer to Accedian‘s website at www. service management and network demarcation for high-performance mobile backhaul. 15 . Accedian EtherNID and MetroNID high-performance service-assurance demarcation units establish end-to-end OAM. Establish complete. Accedian provides the highest performance network monitoring.Features Service Assurance Accedian Networks' high-performance service-assurance Platform provides standards-based inservice monitoring. The industry's first SLAMeter™ has a comprehensive suite of active and passive in-service performance testing.accedian. end-to-end control of your services. and network management tools that maintain and assure carrier-grade Ethernet. business services and carrier interconnect and exchange applications.com. enable in-service loopback and performance testing and let you create and assure carrier-grade SLAs. intelligent layer 1-4 loopback functionality and per-flow traffic monitoring. Map-out the Health of your Network™. and increase the dollar value of every packet flowing through it with Accedian Networks' service assurance solutions.

service level. Loop traffic by multiple packet-filtering criteria. monitoring system or other EtherNID and MetroNID units. destination and source MAC / IP addresses without interrupting customer traffic. 16 . including VLAN. For more information about Loopback testing. refer to the chapter Managing Loopbacks.Layer 1-4 Loopback Testing with Test Set Support Establish Layer 1–4 loopbacks from your existing test set.

refer to the chapter Testing Network Performance. For more information about Traffic Generation and Analysis. delay variation and packet loss to troubleshoot. Measure delay. in-line Traffic Generation and Analysis. 17 . throughput and performance testing without impacting customer traffic. provision and validate Ethernet services and SLAs.Traffic Generation and Analysis Perform in-service.

For more information about PAA.Performance Monitoring Accedian Network‘s Performance Assurance Agent (PAA™) keeps continuous watch over the critical services on the network with one-way-delay and delay-variation measurements. frame loss and availability monitoring. Test up to 100 sites from a single EtherNID or MetroNID demarcation unit. 18 . refer to the chapter Monitoring Network Performance.

refer to the chapter Managing Traffic. multi-technology networks.SLA Performance Assurance Establish end-to-end transparent LAN services with EVC service creation functionality and monitor them in real-time with the industry‘s only SLA-Meter™. 19 . Performance is fully transparent over multi-manufacturer. multi-carrier. For more information about SLA Assurance.

Quickly create Ethernet Virtual Connections (EVCs) for E-Line. traffic shaping. cell. For more information about service creation features of Accedian‘s EtherNID and MetroNID. Leverage real-time multi-port aggregation and bypass switches altogether. traffic shaping. accelerate. real-time traffic. Optimize service and core network performance with wire-speed traffic conditioning and flexible rate limiting. Accedian‘s unique Fast-PAAs engine. refer to Accedian‘s website at www. Create. optimize and manage Ethernet services with per-flow service mapping. Easily configured remotely.accedian. aggregation and head-end sites.Service Creation Accedian‘s high-performance demarcation devices provide a uniform network interface for creating MEF-compliant Ethernet Virtual Connections (EVC) services over any network topology.com. the industry‘s only wire-speed performance assurance agent. media or protocol. MetroNID units provide advanced traffic classification at wire-speed to indentify individual services and add the provisioned EVC service tags and CoS markings without adding delay to the service flows as they enter the Carrier Ethernet network. enables the units to maintain EVCs at GbE and 10-GbE speeds without introducing delay or delay variation to critical. Accedian Networks‘ high-performance service-assurance platform helps you create services by deploying end-to-end Ethernet transparent LAN services with guaranteed performance and availability over any network—without disturbing your switches or your customers. filtering and bandwidth policing directly at the demarcation point and bypass costly switches upgrades. E-LAN and E-Tree services with EVC service mapping: advanced networking functionality is built right into EtherNID and MetroNID units designed for customer. building EVCs is as simple as installing EtherNID units at the demarcation points and provisioning services from the web. 20 . filtering and switch-free aggregation at the intelligent access edge. Multi-technology networks EVC service mapping functionality transparently creates Ethernet LAN services and avoids interoperability issues.

21 . refer to the chapter Managing Traffic. E-LAN and E-Tree services. For more information about Ethernet Service Mapping. each EVC is conditioned with bandwidth profiles and class-of-service markings that deliver high-performance SLA-backed E-Line.Ethernet Service Mapping Accedian MetroNID demarcation devices establish identify. Once created. service providers can use any Ethernet. at wire-speed. IP or Transport layer header information to steer traffic into specific service EVC. With a variety of EVC service creation capabilities. classify and mark individual traffic flows into provisioned Ethernet Virtual Connections over any network.

Bi-direction per-EVC throughput management enables service providers to enforce admission control policies that assure network performance integrity and guarantee the delivery of CIRs even during network congestion. 22 . For more information about Bandwidth Policing.Bandwidth Profile Regulators Accedian assures SLA compliance by protecting the network from congestion by providing continuous bandwidth regulation of the committed information rate (CIR) and excess information rate (EIR) flows in the network. refer to the chapter Managing Traffic.

23 . For more information about Traffic Filtering. refer to the chapter Managing Traffic. They provide wire-speed traffic filtering by VLAN.Traffic Filtering Accedian‘s advanced comprehensive traffic filters help preserve network security and prevent broadcast messages and malicious traffic from flooding your network. Ethernet/IP address. service class or TCP/UDP port. Ethertype.

24 . refer to the chapter Managing Traffic. while standard traffic is priority-queued. hardware-based traffic shaping that passes critical. real-time traffic at wire-speed using the Fast-PAAs zero-delay cut-through queue. and economize bandwidth with advanced. reduce network overhead. shaped and forwarded.Traffic Shaping Accelerate low delay services. For more information about Traffic Shaping.

Managing the Unit This chapter contains the following sections:  About the Management Web-Interface  Starting the Management Web-Interface  Configuring the Logical Interfaces  Managing Network Inventory  Managing Sessions  Managing Users and Privileges  Using a RADIUS Server for Authentication 25 .

0 or higher) installed. or Internet Explorer 6. second and third level menus Working Area Write lock Logout 26 . The elements of a typical user interface screen are shown in the following figure. management and monitoring functions. to all system control. via an SSL client. The management station is the computer that you use to connect to the management webinterface and must have a JavaScript-enabled Web browser (Firefox 1.About the Management Web-Interface The web-based management interface provides secure access. Typical Screen Date and time Alarms First.0 or higher.

it reloads the page completely. Writelock button: Use this button to toggle between yes and no for Writelock. Apply: Use this button to apply the changes made on the page to the equipment. This action has the same effect as leaving this page to go to another page and then returning to this page. Each menu item you select will be highlighted. you can also click this button to refresh the status and values of each field. First. Note: Using your browser’s Refresh command does not simply refresh the values or list shown on one page. Once you have the desired list shown on the page. second and third level menus: The top row presents the first level menu. 27 .Date and time: date and time for this unit. You can configure the date and time from System > Configuration > Time. For example. wherever possible. For example. Working area: This is where you view information and configure system parameters. refer to the section on Locking or Unlocking User Sessions. The second level (second row) presents a submenu based on the option selected from the first menu. click an option on the first level menu. Alarms: indicates alarms that have been triggered. This action changes the equipment configuration immediately. helping you to view the changing results while a test is performed. If you then click one of the elements listed in the summary. For more information on alarms. The parameters present on both the summary and detailed pages are described within one table in this manual. The parameters are listed in the tables in the order in which they appear on the screen. then on the second level menu and so on until you see the function you want to use. this can be useful in a Results page. To navigate to different functions. Selecting a third-level menu option often displays a summary of the information requested. Reset: Use this button to reset the value of a page. before you apply the change. the table for System > Session > Permissions describes all parameters present on both the summary page for all sessions and the detailed page for a specific session. This is useful when you are not sure exactly what values you changed and you want to start over using the previous configuration. eliminating any filter that you had applied. Search: Use this button to filter any list shown on a page to narrow down the list to elements you have specified on the drop-down list. For more information about this function. refer to the chapter Managing Alarms and System Messages. you will obtain more detailed information on that element. Logout button: Use this button to logout from the current session. It is always visible. The third level (third row) submenu depends on the option selected from the second menu.

3.1. This allows you to login and configure the unit for the first time. you can set the unit‘s time and date and create other logical interfaces so you can connect through a LAN or WAN (refer to Configuring the Logical Interfaces). before logging in you must connect the LAN port on the management station to the management port on the front of the unit. To change the password. Be sure to change the admin password after your first login. proceed as follows: 1. for example 192. For more information on modifying IP addresses. use of DHCP and other options for logical interfaces. e.168. proceed as follows: 1. Make sure your management station has a route to the equipment.g. Start your Web browser and enter the following in the address box: https://192. thereby avoiding duplicate IP addresses with other existing factory default units. If you are using static IP addresses. you can login. Network. Note: This is the default password for the user admin. The login page for the unit opens. Depending on the configuration of the unit.1. you may login in different ways. For example. You can also configure the unit to use DHCP. Login as admin with the Password admin.Starting the Management WebInterface Physically Connecting to the Unit The first time you connect to the unit. Normally you would then configure another interface. Note: This is the factory default IP address of each unit. The default management ports for the MetroNID and EtherNID is the Management port. Configure the computer with a static IP address on the same subnet as the equipment you want to login to. If you already have configured another logical interface. The first time you login. ® ® Logging In Once you have a physical connection to the equipment.168. refer to Configuring the Logical Interfaces. you should then modify the unit’s IP address to be unique.2 2. 28 . You would usually connect to the unit for the first time using the Management port. This ensures that only the admin user can perform admin functions. refer to the section Changing Passwords.254. for in-band management through the network.

2. Start your Web browser and enter the equipment address in the address box, e.g. https://192.168.1.252 (or host_name.domain.com if you are using a DNS). Note: The unit uses TCP port number 443 (HTTPS) for connecting with the Management Web-Interface. If your network blocks this port number, you can change it to another number using the CLI interface. Refer to Using the Serial Console to enable the console port and to the CLI Command Manual for information on the CLI command. 3. The login page opens. Login using your user name and password.

Working in the Home Page
The home page provides general information about the unit. To view the home page shown in the figure below, go to Home.

Home Page

For information on specific parameters, refer to the following table.

Home Page Parameters (Home)
Parameter MAC base address Unit identifier Firmware version Serial number Assembly Description The base MAC address of the unit. The name that identifies the unit on the network. The firmware version of the unit. Go to System > Maintenance > Firmware to upgrade the firmware. The serial number of the unit. The hardware version of the unit.

29

Parameter Hardware info

Description The hardware option of the unit. This field is available only if this unit has a hardware option installed, e.g. GPS.

Modifying the Unit Identifier
The default host name (or unit identifier) is the serial number of the unit and is displayed in the banner at the top of the screen after logging in. You can change the host name to a name more meaningful to your organization or use other DHCP host name options. The host name identifies the unit on the network and can be used when you login to the unit. Note: The host name is also used in the CLI prompt and is added to system log entries. For information on specific parameters, refer to the following table.

DNS Parameters (System > Configuration > DNS)
Parameter Use DHCP results Host name DHCP host name Description Enables use of DNS settings obtained via DHCP. You can then select the interface to use for obtaining DHCP information using From interface. The name that identifies the unit on the network. This parameter is valid only when DHCP host name is set to Current hostname. The DHCP host name option. The choices are: Current hostname: The host name is the string entered in the Host name field. Serial number (DHCP option 12): The host name is the serial number of the unit. Custom hostname (DHCP option 12): The host name is the text string you enter in the field to the right of the DHCP client ID. Field to the right of DHCP host name DHCP client ID From interface DNS server 1 This field is used only when DHCP host name is set to Custom hostname.

This corresponds to DHCP option 61. It allows you to enter a text string for use as the unit‘s host name. When the text box is empty, the MAC address is used as the unit‘s client ID. The interface used for obtaining DHCP information. Available only when Use DHCP results is selected. The address of DNS server 1 is available only when Use DHCP results is not selected.

30

Parameter DNS server 2 Domain

Description The address of DNS server 2 is available only when Use DHCP results is not selected. The local domain name associated with the DNS is available only when Use DHCP results is not selected.

Managing SSL Certificates
The SSL protocol is used to secure the communication over the internet between the management station and the unit. You must load a valid SSL certificate, from a certificate authority, into the unit, to provide secure communication. Note: You may install the SSL certificate in each browser you want to use to connect to the unit. In other cases, you may want the unit to communicate with other application such as a FTP server or the Echo Agent. You can configure the unit for secure communication with these applications by using Application management, therefore managing the validation of certificate use. For more information about certificates, refer to the certificate authority and to the ITU-T Recommendation X.509. Go to System > Maintenance > Certificates to manage SSL certificates.

System > Maintenance > Certificates

You can view the SSL certificates installed on the unit in the Certificate management section. To view the details of the installed certificates, click the View button. To delete a certificate, click the delete button.

31

To import a new certificate, select the certificate by using Browse in the Certificate import section, fill in the other fields and click Upload when ready. The certificate will be loaded into the unit and will appear in the Certificate management section. To assign a certificate to a specific application such as an FTP server or the Echo Agent, select it from the Common name column in the Application management section. Fill in the other parameters as required and click Submit to assign it to the application. If you submitted a certificate for Web management (the one you are using right now), you must restart it by clicking Restart. For information on specific parameters, refer to the following three tables.

Certificate Parameters (System > Maintenance > Certificates)
Parameter Common name Description For a certificate authority (CA), this is the name of the organization that emitted the certificate. For a server, this is the Fully Qualified Domain name of the service using the certificate (only the web server at this time). For a client, this may be the name of the application. Valid until Function The date when the certificate expires. It may still be valid if the peer has disabled checking. Describes how the certificate can be used in the unit. CA: Used to validate peer certificates; provided as part of the certificate chain for server applications. Client/Server: These certificates were imported with a private key. It is possible for a CA certificate imported with a private key to be used for this function. In this case, it does not show up as a CA.

Application Management (System > Maintenance > Certificates)
Parameter Application Description The choices are: Web management: You are using this now! EchoAgent™: this can optionally be configured to use a secure link to connect to the EchoVault. File transfers: All applications sending or receiving files through a secure channel (https or ftps). For example firmware upgrades and configuration import/export using the CLI. Common name For a certificate authority (CA), this is the name of the organization that emitted the certificate. For a server, this is the Fully Qualified Domain name of the service using the certificate (only the web server at this time).

32

The name of the selected certificate appears here before you upload it. The pass code is only used once for importing. perform peer certificate validation. Validate CA Enable Client For client applications. this may be the name of the application. enable or disable the use of the selected client certificate. hostname and CA chain. For client applications. This includes expiration date. which use a pass code. pkcs12: to import client certificates including the private key and the CA chain of certificates. Import certificate 33 . pkcs7: to import multiple CA certificates. Certificate Import (System > Maintenance > Certificates) Parameter Type Description The following certificate file types are supported. Importing a private key separately from its certificate is not supported.Parameter Description For a client. x509-PEM is used to import either: A client or server certificate and its private key A single or multiple CA certificate x509-DER: to import single CA certificates. Passcode For pkcs12 or PEM encoded private keys.

you have the option of using a spanning tree protocol and the option of an IP address override for sub-interfaces. With a bridge interface. In this example. Note: An interface can also be used for other purposes. For more information on viewing the network inventory.1q): This interface type is again associated with a single port. you would create a VLAN for the management and another VLAN for the customer traffic. You can use this interface type when you want to use sub-VLAN. as with the standard interface. refer to the chapter Managing Traffic. you can assign priority and you have the option of Ethertype. Using filters and policies. refer to Managing Network Inventory. You may also want to configure an interface for advertisement settings. an interface is automatically configured for the port on which the beacon was received.Configuring the Logical Interfaces You can define one or more logical interfaces for managing the unit. An example of when you would use a VLAN interface would be if you want to separate the management traffic from the client traffic. This includes defining interface types such as bridges and VLANs.1q in . Once it receives a beacon. you can use an interface for OAM or for test set interaction. with a single port. For more information on filters and policies. For example. Once the interface is defined. Bridge: This interface type is used to connect two or more interfaces as one logical interface. VLAN: This interface type is associated.    Go to System > Configuration > Interface to view the existing logical interfaces and to configure new and existing logical interfaces. 34 . This allows you to see a network inventory of all Accedian units that have this option enabled. The following types of logical interface are available:   Standard: This interface type is associated with a single port. You would use a standard interface to manage the unit from one defined port. Bridge VLAN: This interface type is used to encapsulate a bridge interface in a VLAN. With a VLAN-in-VLAN interface. you would ‗drop‘ the management traffic and permit the customer traffic to flow through the unit. You would do this when you want to connect to the unit through your LAN or WAN without having to know which physical port connects your management station to the unit. Auto: This interface type is listening for beacons on all ports.  VLAN-in-VLAN (. you can also define a route to access the unit from outside the subnet of the unit. Note: This does not prevent the Management VLAN traffic from communicating with the unit.

By default, the following logical interfaces are defined:   Management: the default interface (type Standard) that enables access to the management web-interface via the management port. Auto: the default interface (type Auto) that listens for beacons on all ports. CAUTION: If you modify an interface, you or another user may lose access to the management web-interface.

System > Configuration > Interface

For information on specific parameters, refer to the table Interface Settings (System > Configuration > Interface).

35

Adding or Editing a Logical interface
After a factory default reset, there is a logical interface named Management that is bound to a port. You can add and edit more logical interfaces to provide the unit with multiple management options. To add or edit a logical interface, proceed as follows: 4. Go to System > Configuration > Interface. 5. Click the Add button to add a new interface or click the Interface name of an existing interface to edit its settings. 6. Fill in the required fields and click Apply. Note: Displayed fields vary depending on the Interface type you selected. Note: It is valid to set the IP address for an interface to 0.0.0.0 when the interface is not required to be an IP interface. For example, when the interface is used for OAM or test set interaction. For more information on specific parameters, refer to the following table.

Interface Settings (System > Configuration > Interface)
Parameter Description

For all interface types State Interface name Interface type Enabled or disabled. A name to identify the interface. Standard: Standard IP interface associated with a single port. Bridge: Bridged interface that connects two or more ports. VLAN: VLAN interface associated with a single port. VLANinVLAN: VLAN-in-VLAN (.1q in .1q) interface associated with a single port. Bridge VLAN: VLAN interface associated with a bridged interface. Auto: You can set up only one Auto interface for each device. This option cannot be selected on any other interfaces. On port(s) On interface Automatic IP (DHCP) / DHCP The port on which the interface is active. In the case of a bridge, select multiple interfaces by holding down the control key when you click interface names in the list. Allows the interface act as a DHCP client and automatically obtain its IP address, DNS server and gateway settings from a DHCP server.

36

Parameter Use DHCP route information Use static IP until DHCP response Manual configuration IP address Network mask Default gateway Info

Description Allows the unit to get the routing information from the DHCP server.

Uses the manually configured IP address on the interface until an address is resolved by DHCP. Available only when using Automatic IP (DCHP) mode. Not available with Auto interface. Manual configuration of IP address settings. IP address assigned to the interface, if required. The network mask associated with the IP address, if required. A default gateway address provides a shortcut to creating a default gateway through the route configuration. Only one default gateway can be set per unit. Brief description of the interface that appears on the network summary page, e.g. VLAN number, auto interface.

For Bridge interface type only Enable Spanning-Tree Protocol Enable subinterface IP override The Spanning Tree Protocol (STP) may be enabled or disabled.

This option disables DHCP and resets the IP address of each sub-interface to 0.0.0.0. You may use this option to use the IP address assigned to a subinterface and assign it to the bridge. For example, if the Management interface has address 192.168.1.254 and you configure a bridge interface with the Management interface as a sub-interface, by enabling the sub-interface IP override, you can assign an IP address to the bridge (e.g. 192.168.2.200) and the Management interface would be 0.0.0.0 and would be part of the bridge. The Management port would then respond to 192.168.2.200 as well as to any other interface‘s IP address in the bridge.

For VLAN, VLANinVLAN and Bridge VLAN interface types only (VLAN settings) VLAN ID VLAN priority Ethertype VLAN ID (Management VLAN) assigned to the interface. VLAN priority of 0–7. Ethertype for the first and second VLAN IDs. Ethertype may vary depending on the equipment the unit is connected to. C-VLAN: 0x8100 S-VLAN: 0x88A8,0x9100 Beacon settings: For all interface types except Auto State Beacon rate Transmission of beacon frames on the interface. How often the beacon frames will be sent: 3 sec, 1 min, 10 min, or 60 min. Default is 1 min.

37

Parameter Domain ID

Description In the discovery process, the domain ID can be matched by remote devices to select which beacons it should process. See the Domain ID and ID matching parameters in the Discovery settings parameters.

IP config mode

Tells the receiver the IP configuration mode that the receiver should use. Local: Use the receiver interface settings. Auto: Tell the remote device to compute an IP address, given the subnet, gateway and mask. Auto static: Behaves like Auto, but in the case of a power reset it preserves the IP address, gateway and mask if an IP is already configured (different from 0.0.0.0) DHCP: Use DHCP to get an IP address for the AUTO interface.

IP subnet Mask Gateway Authorize ID mismatch DHCP host name

Subnet used by the receiver when the Auto or Auto Static IP config mode is selected. Mask used by the remote device when the Auto or Auto Static IP config mode is selected. Gateway used by the remote device when the Auto or Auto Static IP config mode is selected. When enabled, it tells the receiver to accept beacon frames even if the beacon's domain ID does not match the local domain ID when ID matching is enabled at the receiver. Useful for troubleshooting Domain entry errors. Possible values are: Current hostname Serial number Custom hostname

DHCP client ID

Possible values are: Serial Number Custom client ID

IP exclusion list One shot beacon

In Auto and Auto IP Static configuration modes, this list of IP addresses is excluded from the remote NIDs. The IP addresses need to be separated by commas. Up to 64 IP addresses can be specified. When you press Send, the system sends a single beacon frame with the information that has previously been configured and applied. If changes to the beacon settings were made without clicking Apply, they would not be effective in the beacon frame.

38

Parameter Description Discovery settings (Auto interface only) Beacon discovery state Auto mediaselection Processing of beacon frames upon reception. When enabled. Default for Auto interface: Enable Default for other interfaces: Disable L3 state The advertisement of layer-3 information frames may be enabled or disabled. beacons and advertisement frames are forwarded using the bridge associated with this interface. Forward on bridge When enabled. The domain ID can be matched with the incoming beacon domain ID to determine if the beacon should be processed. The ACP frames level defines how far the ACP frames can go. All: All ACP frames will go through this unit without processing. When enabled. Default (all interfaces): Disabled 39 . A list of ports enabled to listen for incoming beacon frames. The choices are: 0–7: for a specific level. Tells the receiver to accept beacons only if the beacon's domain ID matches the local domain ID. Enable or disable port scanning to find out which ports have a link. the appropriate media-selection mode is automatically selected. A unit receiving a beacon frame will automatically set it's system ACP level to the one included in the beacon frame. Auto media-selection is disabled if Discovery state is disabled. Advertisement settings (all interface types) L2 state The advertisement of information frames may be enabled or disabled. The domain ID to use in the discovery process. Forwarding ports on match Forwarding ports on mismatch A list of ports to forward beacons and advertisement frames to when the domain ID of these frames matches the configured domain ID. This level is used in transmitted advertisement and beacon frames. the forwarding ports on match are not effective. a unit using ACP frames level 3 will be able to reach another unit if the other units in between have an ACP frame level of 2 or below. A unit requires a higher level to be used to run ‗above‘ a lower level. A list of ports to forward beacons and advertisement frames to when the domain ID of these frames does not match the configured domain ID. For example. the discovery ports listen for beacon frames and configure the Auto interface. if a bridge exists. Use this for initial system discovery and disable it after the system has been configured. When one or two links are detected. Information frames are used to advertise to a central unit. ID matching Domain ID Discovery ports Forwarding settings (Auto interface only) Level The ACP frames level.

Fill in the required field of the Beacon settings section and click Apply. To configure a logical interface for Beacon advertisement. the central unit or the Beaconner. Click the Interface name to edit it. proceed as follows: 1. be sure to disable the advertisement frame filtering in the Show > Inventory page if you want to be able to see the Inventory of all units advertising on this interface. Configure the Auto interface of the remote units to listen for Beacon frames in the Discovery settings parameters. refer to the table Interface Settings (System > Configuration > Interface). The advertisement transmission rate to use when the beacon rate option is disabled. When enabled. 40 . ACP: Only proprietary Accedian format is supported for now. The frame format to use when sending information frames. the advertisement transmission rate matches the rate that is configured in the beacon settings. proceed as follows: 7. To add or edit a route. for sending the Beacon frames. Adding or Editing a Route You can define a route that is outside the subnet defined by each interface to access a unit outside of the management station‘s subnet. For more information on specific parameters. Go to System > Configuration > Interface. Configuring a Logical interface for Beacon You can configure a logical interface to use Beacon frames. 9. Go to System > Configuration > Interface. Configure only one unit in your network. Note: if the interface configured for beacon is part of a bridge. Refer to Managing Network Inventory. A multicast frame is sent by a central unit (any unit configured as the ‗Beaconner‘) to all remote units that are used by the AUTO interface for auto provisioning. 8.Parameter Advertisement IP Advertisement format Use rate from beacon Transmission rate Description The destination IP address to be used in layer-3 advertisement frames.

For more information on specific parameters. refer to the following two tables. 0. Gateway associated with this route. This field is optional if a matching active route is already associated with the interface. 2. For more information on specific parameters. Click the Add button or click the route name to add or edit a route. Enter the host IP address and the timeout and click the Ping button. Go to System > Maintenance > System tools. e. 3. Network or host address of the route. 2. 41 . "Default".g. proceed as follows: 1. Finding a Host (Ping and Traceroute) The equipment provides ping and traceroute functions to help the administrator troubleshoot network problems.2. Mask assigned to the route. Fill in the required fields and click Apply.0. It can be a brief description of the route. for a range of addresses. The interface with which the route is associated. Only used for Network routes. or Host.0 is the default destination. Go to System > Maintenance > System tools. Route Settings (System > Configuration > Interface) Parameter Name Type Interface Destination Network mask / Netmask Gateway Description The name to assign to the route. Enter the host IP address and the maximum number of Hops and click the Traceroute button.0. You can use the ping function to verify whether a specific host (IP address) is reachable. You can use the traceroute function to identify which route uses the IP packet to traverse the network and reach a specific destination. To ping a remote host. To trace a route to a remote host. for a specific IP address. refer to the following table. Route type may be either Network. proceed as follows: 1.

To use the console port. The console port provides a CLI interface to the unit. 42 . you must use a terminal emulation program with the following settings: Terminal Emulation Settings Parameter Protocol Port Baud rate Data bits Parity Stop bits Flow control Setting Serial COM1 to 8 115200 8 None 1 None You can connect the serial port on the management station to the RJ45 console port on the unit using the following diagram and table. proceed as follows: 1. Go to System > Configuration > Console. you can enable or disable the console port. Using the Serial Console The unit provides a serial (RS232) console port (RJ45) to manage the equipment using a serial port on a management station. 2. Verify the current state of the console port in the console state field. Click Enable console or Disable console as required. 3.Ping (System > Maintenance > System tools) Parameter IP address timeout Description IP address to PING. To enable or disable the console port. Number of hops to try: 1–30. Refer to the CLI Command Manual for information on the CLI. After logging in. Number of PING messages to send: 1–10 Traceroute (System > Maintenance > System tools) Parameter IP address Hops Description IP address to TRACEROUTE.

Serial Console Cable Connectors Console Port Cable Pinouts Unit Console Port (RJ45) Management Station Serial Port (DB9) Pin Signal Pin 1 2 3 4 5 6 7 8 Signal Not connected Not connected Tx Data Ground Ground Rx Data Not connected Not connected 2 5 5 3 Rx Data Ground Ground Tx Data 43 .

The serial number of the remote unit The firmware version of the remote unit The hostname of the remote unit The list of enabled IP interfaces configured on the remote equipment.Managing Network Inventory Viewing Network Inventory You can view a network inventory of all Accedian units that have an interface configured for advertisement settings enabled (Refer to Configuring the Logical Interfaces for more information about the advertisement settings). This displays a table of all units that have advertisement enabled to send an information frame on the network. 2. 44 . The MAC address of the remote unit port that sends advertisement frames. The domain ID that was used in the discovery process to configure this unit. refer to the following table. The type of remote equipment. Inventory Remote NID IP System description Serial number FW version Hostname IP interfaces Domain ID Base MAC address Interface MAC address The remote unit IP address. The MAC address associated with the unit. you must disable the advertisement frame to be able to see the inventory of all units advertising on this interface. AMN-1000-TE.g. e. Note that if the interface configured for beacon is part of a bridge. proceed as follows: 1. Discovery config and inventory (Show > Inventory) Parameter Enable inventory tracking Enable advertisement frame filtering Description Enables the gathering of discovery inventory. Go to Show > Inventory. The advertisement frames are added to inventory only if they are received on a port that has an interface with the beacon state enabled. Filter advertisement frames based on the beacon configuration state of the unit interfaces. For more information on specific parameters. Click Enable inventory tracking and click Apply. To view a network inventory. as displayed in the Home tab.

Last time the information for this remote unit was updated. gateway and mask.0. The name of the local unit port that receives advertisement frames. It renews the configuration of all remote units that have the advertisement settings set to enable. Unicast beacon configuration Domain ID IP config mode In the discovery process. the system sends a single beacon frame with the information that has previously been configured. For more information on specific parameters. When enabled. The only choice is Renew config.0. Indicates whether the remote unit is running with the Default configuration or is User configured. You can also view more information for a specific unit by clicking the link in the Serial Number column. given the subnet. it tells the receiver to accept beacon frames even if the beacon's domain ID does not match the local domain ID when ID matching is enabled at the receiver. Mask used by the remote device when Auto or Auto Static IP config mode is selected. Auto static: Behaves like Auto. but in the case of a power reset preserves the IP address. refer to the table Discovery config and inventory (Show > Inventory). Auto: Tell the remote device to compute an IP address. gateway and mask if an IP is already configured (different from 0. When you press Send beacon.Parameter Remote port Local port SNMP port Web server port Config status Last update Description The name of the remote unit port that sends advertisement frames.0) DHCP: Use DHCP to get an IP address for the AUTO interface. if configured. Local: Use the receiver interface settings. 45 . Tells the receiver the IP configuration mode that the receiver should use. the domain ID can be matched by remote devices to select which beacons it should process. Gateway used by the remote device when Auto or Auto Static IP config mode is selected. The remote unit web port used. IP subnet Mask Gateway Authorize ID mismatch Beacon type Send beacon Subnet used by the receiver when Auto or Auto Static IP config mode is selected. The UPD port of the SNMP agent for the remote unit. Useful for troubleshooting Domain entry errors.

proceed as follows: 1. To connect to the remote unit. 2. Sending a Beacon Frame To send one beacon configuration frame to the remote units.Logging in to a remote unit You can connect and manage a remote unit by logging in to the web server of the remote unit. You can also configure a logical interface for beacon in the Interface settings page. For more information. 46 . The login page for the remote unit opens. Enter your user name and password to start managing the remote unit. Click the hyperlink in the Remote NID IP column. proceed as follows: 1. 2. Go to Show > Inventory. Refer to Configuring a Logical interface for Beacon. Click Send beacon. 3. refer to the table Discovery config and inventory (Show > Inventory). refer to the table Discovery config and inventory (Show > Inventory). Go to Show > Inventory. For more information on specific parameters.

To view current sessions. System > Session > Management 47 . go to System > Session > Management.Managing Sessions The unit‘s management system provides multiple configurable management sessions to allow multiple users to control the unit. There is a writelock mechanism to avoid two users writing to the unit at the same time.

An asterisk (*) indicates your own session. Current Sessions (System > Session > Management) Parameter Session ID Type Host Username Uptime Writelock Terminate Description Uptime Interface the session is using. You can also control the locking and unlocking of your session using the Writelock button. How long the session has been active. Indicates which session has the ability to make configuration changes. You will no longer be able to modify parameters on the unit. Unlocks write acess so that is is available to other users. go to System > Session > Management and click the Writelock button. Selecting one or more sessions and then clicking Terminate forces a log out. to maintain the integrity of the configuration settings.For more information on specific parameters. IP address of the management station for that session. 48 . Since the web interface supports concurrent sessions. Refer to Managing Users and Privileges. Terminating a User Session It may be sometimes necessary to terminate one or more sessions. go to System > Session > Management and click the Writeunlock button. Only you will have access to modify parameters of the unit. The other users will only be able to view the unit‘s configuration. refer to the following table. Locking or Unlocking User Sessions The administrators communicate with the equipment within a particular session. only one user at a time has the ability to make changes. Users open their own sessions to administer the equipment. To unlock a session for write access so other users can lock it. Note: You need the right privileges to terminate a session. To lock a session for write access. User account that is logged in. Writelock (System > Session > Management) Parameter Writelock Writeunlock Description Locks your session so that only you have write access.

Enter the different session configurations parameters and click Apply. Maximum number of management tool sessions that are supported at the same time. 2. Maximum number of seconds that a management tool session can remain idle before it is automatically logged out. Configuring Session Options You can configure the following parameters related to sessions:  Max CLI sessions  Max WEB sessions  Max total sessions  CLI timeout  WEB timeout  Telnet server  Authentication order To configure session parameters. The telnet server on the NID may be enabled or disabled. select the session you want to terminate by checking the Terminate check box and the Terminate button. Maximum number of seconds that a CLI session can remain idle before it is automatically logged out. For more information on specific parameters.To terminate a session. go to System > Session > Management. refer to the following table. proceed as follows: 1. Session Configuration (System > Session > Configuration) Parameter General Max CLI sessions Max WEB session Max total sessions CLI timeout WEB timeout Telnet server Authentication Order Authentication method to use in order of availability. You will then see the screen displayed in System > Session > Configuration. Options are: Local: Validate locally only Radius: Validate on the Radius server only Maximum number of CLI sessions that are supported at the same time. Description 49 . Go to System > Session > Configuration. Total number of CLI and WEB sessions that are supported at the same time. The session is immediately terminated and the current user is logged out.

then validate on the Radius server. Fall back to local happens only if the radius authentication times out. access is denied. Strict radius-local: Validate on the Radius server first. if the validation does not succeed. then validate on local server. If the authentication fails. System > Session > Configuration 50 . Radius-local: Validate on the Radius server first.Parameter Description Local-radius: Validate locally first. and if the validation does not succeed.

are used to give different levels of access to different user groups. ports. or traffic and others to have full access. It is recommended that you change the default password immediately after installation to safeguard the system (Refer to Changing Passwords).Managing Users and Privileges You may configure each unit to be managed by several users. Note: To prevent losing administrator access to the unit. proceed as follows: 1. Setting Up the Administrator Account One administrator account is created by default with username and password both set to admin. Go to System > Sessions > Permissions. Select the Privileges you want to give to that user group and click Apply. This user group has full access to all functions. OAM. Note: You cannot change the privileges of user group Admin. CAUTION: If you. you cannot modify the administrator account privileges or delete the administrator account. 2. such as firmware updates. To define permissions for a group of users. 51 . Defining Permission for a Group of Users You must first define group permissions before you can assign users to groups. Click the Add button or click the Group name that you want to edit. Refer to Resetting to Factory Defaults. You must first define permission for user groups before you define user accounts. Privileges. The username and password are case-sensitive. forget your username or password the only way to regain access to the management web-interface is to perform a factory reset. as the administrator. or permissions. You may want certain users to have access to only certain configuration options. The administrator account provides access to all features. each with different privileges. 3.

refer to the following table. Group Privileges (System > Session > Permissions) Parameter Group name Privileges Description User permission group. IPv4 filters. service mapping. Config: Import/Export configuration files  configuration Filters: Edit/Add L2 filters. traffic shaping and regulators. add or enable within these sections.       bandwidth-regulator cfm cos-profile regulator-set filter traffic-shaping Firmware: Upgrade firmware Log: Edit syslog configuration and view logged entries Management: Edit/Add management access to the unit          console date dns interface motd mtr ntp route snmp 52 . The following command can be used by all users whatever their privileges:  Home page information (CLI: board)  date  Logout (CLI: exit)  ? (CLI: help)  ping  quit  sfp  syntax  traceroute  version Select the name of the section in which to give Edit/Add/Enable privileges to the group. Privileges given to the user permission group allow a member to edit.For more information on specific parameters.

In the [User name] user settings page. refer to the following table. Click the Add button or click the User name if you want to edit a user account. Adding or Editing User Accounts To add or edit a user account. refer to the table at the end of this procedure. For more information on specific parameters. 3. This displays all user accounts that exist for the unit. 2. For more information on specific parameters. 53 .Parameter Description OAM: Edit/Add/Enable OAM. fill in the fields and click Apply. Go to System > Sessions > Users. proceed as follows: 1. loopback and PAA    loopback oam paa Policies: Edit/Add/Enable policies for filtering traffic Port: Edit/Add/Enable port configurations    cable-test media-selection port Sessions: Manage sessions and edit session configuration   reboot session Traffic: Edit/Enable VLAN encapsulation settings   fault-propagation forwarding Users: Edit/Add and manage user accounts and permissions   permission-group user Alarms: Edit/Add/Enable alarm reporting configurations All-edit: Permission to edit in all sections that are viewable All-add: Permission to add in all sections that are viewable All-enable: Permission to enable in all sections that are viewable.

Select the User group and click Apply. Click the user name you want to edit. Specify a second time the password for the account. 2. proceed as follows: 1.User Settings (System > Session > Users) Parameter User name First name Last name Phone number e-mail address / email Password Confirm password Description Login name for the account. Administering User Account Privileges You can give different privileges or permissions to each user account. Phone number of the account holder. 3. 4. 3. contact your Administrator for a password reset. Password for the account. To give privileges to a user account. proceed as follows: 1. First name of the account holder. if you have already defined both the user account and permission groups. Changing Passwords To change a user password. In the [User name] user settings page. 54 . E-mail address of the account holder. Go to System > Sessions > Users. CAUTION: Modifying or reassigning the user groups for your account may result in you being unable to perform some tasks. Note: If you forget your username or password. Click the user name that you want to edit. Type the new password in both the Password and Confirm password fields and click Apply. 2. Go to System > Sessions > Users. Last name of the account holder. click the Permission button.

Shared secret for this RADIUS server. To configure session parameters. Go to System > Session > RADIUS. Using a RADIUS Server for Authentication You can use a RADIUS server for authenticating users. the unit supports Authentication and Authorization as configured on the RADIUS server. When RADIUS authentication is enabled. The only option available is: PAP : Password Authentication Protocol RADIUS timeout RADIUS retry Realm Time the RADIUS server waits before retrying the connection. refer to the following table. A string to append to the user's name using the "username@realm" method. proceed as follows: 1. a connection to the next configured server will be attempted. refer to the table User Settings (System > Session > Users). in which the same timeout and retry scheme apply. After the number of retries has been exhausted. RADIUS Configuration (System > Session > RADIUS) Parameter General Authentication method Authentication method to use.For more information on specific parameters. 2. Description Server-1 / Server-2 Host Port Secret RADIUS server host-name or IPV4 address. Number of times to retry the server before trying the next server configured. RADIUS server UDP port to connect to. The unit can be connected to up to two RADIUS servers allowing for RADIUS server redundancy. A RADIUS server can be useful if you want to centrally manage user accounts instead of managing them on each unit. For more information on specific parameters. Enter the different RADIUS configuration parameters and click Apply. 55 .

Notes: You cannot view RADIUS assigned permissions with the CLI or webbased interface. If the username does not exist locally. See also Managing Users and Privileges. local permissions are assigned to the user. Users" Grant full administration privileges (Same as first example): Service-Type = "AdministrativeUser" 56 .Configuration examples for RADIUS Server Note that the following examples are configurations for the RADIUS Server. Two methods are supported by RADIUS servers for providing authorization using standard RADIUS attributes: Callback-Id (id=20): Provides a fine-grained permissions mechanism. The permissions tokens are case sensitive. A member of the built-in Admin group: Callback-Id = "Admin" A list of individual privileges: Callback-Id = "Config Firmware Log Management. The list of tokens is separated by spaces or commas. The permissions are the same as those that can be configured locally on the unit. Service-Type (id=6): Provides for full admin privileges if attribute is set to "AdministrativeUser". not for the unit. They can be a mix of locally-defined user permission groups and individual privileges. permissions are set to viewer only. If the attribute is valid (valid Callback-Id or valid Service-Type) then the permissions are set to:   If the username exists locally.

You can assign port function (network or net-protection) with the port protection option. as explained in Setting up Media-Selection on page 76. The number of VID sets also depends upon the model of NID. Aggregator 2x1 Mode Aggregator 2x1 mode is for one protected network port aggregated with two client ports. as described in Setting up Port Protection on page 77. The five modes are:  Standard  Aggregator 2x1  Aggregator 3x1  Aggregator 4x1  Ring topology Note: The aggregator modes and ring topology mode are available only on TE and TE-S models of the MetroNID. 57 . You can assign port function (network port or client port) with the media-selection option. This mode provides one client port and one network port. each for a different network architecture. The operation mode affects the number of traffic policies and the number of VID sets. Refer to Setting up Traffic Policies on page 100 and to Setting up VID Sets on page 101. Standard Mode Standard mode is for standard network interface device functions. Note: The media-selection option does not apply in Aggregator 2x1 mode.Configuring the Unit This chapter contains the following sections:  Understanding Operation Modes  Setting Operation Mode  Setting Date and Time  Setting SyncE  Setting up DNS  Setting IGMP Version  Setting S-VLAN Ethertype  Upgrading the Firmware  Importing/Exporting the Unit‘s Configuration  Viewing CPU Usage  Rebooting the Unit  Restarting the Unit  Resetting to Factory Defaults Understanding Operation Modes The MetroNID has five operation modes.

as described in Understanding Traffic Shaping on page 118.  Traffic-B policies are associated with the Client-2 port. Aggregator3x1 mode modifies traffic policies as follows:  Traffic-A policies are associated with the Client-1 port.  Traffic-B policies are associated with the Client-2 port.  Traffic-C policies are associated with the network port.  Traffic-C policies are associated with the Client-3 port. Aggregator 3x1 Mode Aggregator 3x1 mode is for one network port aggregated with three client ports. The traffic shaper also behaves in a specific way in Aggregator 3x1 mode. You can assign port function (network port or client port) with the media-selection option as described in Setting up Media-Selection on page 76. Note: The media-selection option does not apply in Aggregator 4x1 mode.  Traffic-D policies are associated with the network port.Aggregator 2x1 mode also modifies traffic policies as follows:  Traffic-A policies are associated with the Client-1 port. 58 . Refer to the figure below for the port configuration. Port Configuration for Aggregator 4x1 Mode Aggregator 4x1 mode modifies traffic policies as follows:  Traffic-A policies are associated with the Client-1 port. as described in Understanding Traffic Shaping on page 118. The traffic shaper also behaves in a specific way in Aggregator 2x1 mode. Aggregator 4x1 Mode Aggregator 4x1 mode is for one network port aggregated with four client ports.  Traffic-B policies are associated with the Client-2 port.

To prevent loops. switch.   Traffic-C policies are associated with the Client-3 port. you must use an Ethernet switch capable of Rapid Spanning Tree Protocol (RSTP). Ring Topology Mode Ring topology mode allows the MetroNID to be used in an Ethernet ring network. 59 . or component fails. Note: A NID cannot be configured as the root node. and still allow a redundant network. allowing data to continue along an alternate path if a cable. Traffic-E policies are associated with the network port. as described in Understanding Traffic Shaping on page 118. providing two 1-Gbps network ports for the ring and two 1-Gbps client ports to add/drop traffic. Refer to the figure below for the port configuration. Note: The media-selection option does not apply in ring topology. The RSTP allows switches and nodes to automatically sort out loops. Ring Topology with MetroNIDs and RSTP Switch The MetroNID can be used in this architecture. The traffic shaper also behaves in a specific way in Aggregator 4x1 mode. Traffic-D policies are associated with the Client-4 port.

1ad) frames are discarded. QoS/CoS performed on the ingress to the ring by each node: Each MetroNID node provides a three-queue shaping function in the ingress (local port to ring). except for the VLAN IDs defined for local drop (i. For more information. 60 . the NIDs will start exchanging RSTP BPDUs with the root bridge and the ring will be automatically configured. The nodes extract (drop) 802. Policies must be configured in Traffic-A to determine where the ring traffic must be dropped (Client-1 or Client-2).1q (or 802. Yellow frames on the ring may be discarded in favour of local green frames. pop and permit traffic actions. Frames are colourmarked before entering the shaper using a three-colour bandwidth policer. Only E-Line services defined individually between the home node and any other node are supported. the incoming port will always be identified as Network-A in the Policies menu. VLAN based add/drop and Logical loop prevention : Each unit transparently forwards all 802. green frames are guaranteed delivery and have the highest priority. Once on the ring. The other ring port is a blocked port (BP) or designated port (DP). Non 802. The nodes can optionally add/push/pop the 802.1ad) frames from the root port only.1q (or 802. Whether Network-A or Network-B is the active port. Queue management uses the BLUE algorithm.1ad) frames from node to node. Each shaper queue is individually configured using a dual leaky bucket scheme supporting three colours.Port Configuration for Ring Topology Mode Ring topology mode provides for the following: Standard RSTP operation: The unit implements standard RSTP and can operate with a root node (RSTP switch). A real-time queue is also provided. The nodes insert (add) local frames onto the ring on the root port (RP) only.  Traffic-B and Traffic-C policies are used to add client traffic onto the ring. refer to Defining Filters on page 92 and to Setting up Traffic Policies on page 100. except for those that must be peered. You must therefore set VLAN filters and traffic policies for the traffic to be added and dropped correctly with the appropriate push. Once the root node is properly set up. to local client port or local CPU).1q (or 802.1ad) VLAN tag.1q (or 802.e. Ring topology mode also modifies three other pages: Port > Configuration  Ring ports are: Network-A and Network-B  Add/drop ports are: Client-1 and Client-2 Traffic > Policies  Traffic-A policies are associated with the ring port that is active.

Note: Aggregator and ring topology modes are available only on MetroNID TE and TE-S models. CAUTION: After changing the operation mode. traffic policies need to be configured on the network port in order to have the incoming traffic forwarded out the proper client port. Note that the 61 .g.g. refer to the following table. The operation mode that will be applied after a reboot of the unit. Go to System > Configuration > Mode. aggregator.g. 3x1 Gbps) is forwarded through the network port (e. General System Settings (System > Configuration > Mode) Parameter Current operation mode Next operation mode Description The current operation mode. Select the Next operation mode and click Apply. e. refer to Understanding Operation Modes. For more information about operation modes. Aggregator3x1: Traffic for all three client ports (e. 1 Gbps) with equal priority.g. For more information on specific parameters. Changing the operation mode will reset the unit to factory default. you need to perform a system reboot to make the change effective. Refer to Rebooting the Unit. Setting Operation Mode You can set up the unit to work in different modes of operation that allow building different network topologies. 2x1 Gbps) is forwarded through the network port (e. Aggregator4x1: Traffic for all four client ports (e.System > Configuration > Interface: A ring bridge is automatically created. 1 Gbps) with equal priority.g. To set the unit to operation mode.g. proceed as follows: 1. The options are: Standard: This is the default mode of operation where ports are not aggregated. 1 Gbps) with equal priority.g. 2. This bridge includes the sub-interfaces that are assigned to the ring ports (Net-A and Net-B). The Traffic Policy page shows any new field added (Outgoing port) for the Network Traffic for specifying the outgoing port that will be based on a traffic filter. Aggregator2x1: Traffic for both client ports (e. ring. 4x100 Mbps) is forwarded through the network port (e. When using Aggregator mode.

S-VLAN ethertype Bandwidth regulator rate adjustment Setting Date and Time Date and time is important in the management and troubleshooting of a network. To manually set the date and time.Parameter Description protection port in Aggregator2x1 mode cannot be used as a monitor port. For automatic time setting you may use either an NTP server or GPS. two network ports (SFP-A and SFP-B) and one management port. Ring topology: Allows Ethernet ring network topology. 2. interfaces. Go to System > Configuration > Time. Verify whether the NTP server you want to use is listed. This affects the IGMP configuration of all interfaces on the unit. If not. Your options are:  0x88A8  0x9100 This is used to preserve a specific bandwidth rate when an encapsulation is being pushed by a policy onto an EVC. However. It allows. Select the NTP enable option. Note: Only one NTP server can be used in a network. time-stamping alarms. add a new server by specifying its name or IP address in the NTP Server box and then click Add. filters. proceed as follows: 1. To automatically update the date and time using the Network Time Protocol. Specify the current date and time and click Apply.e. it must be used for Link or LACP protection. RFC-2544. among other things. 3. i. 62 . IGMP version The IGMP version for the unit. It provides two client ports (RJ-45A and RJ-45B). Go to System > Configuration > Time. Your options are:  System default  V2  V3 This affects all elements that make use of the S-VLAN ethertype. proceed as follows: 1. The system date and time can be set manually or automatically. 2. The traffic of the two client ports is forwarded to one of the working network ports. The GPS option is available only with some hardware versions. The GPS option will provide the highest accuracy. The working network port is chosen according to the network port RSTP status. any unit can act as an NTP server if you select the NTP server enable option.

Go to System > Configuration > Time. Starts the NTP server service. TAI has been exactly 34 seconds ahead of UTC. 24 leap seconds were added to the difference. If you want to set the time zone and the daylight saving function. In this mode. 2. 63 . please refer to: http://www. Fill in the parameters and click Apply. the NTP server is queried multiple times and the resulting time is derived from an averaging process based on a hardware clock. the priority of the packets can be set in the VLAN priority bits if the link is through a VLAN. For a list of time zones and daylight-saving-time rules. DSCP VLAN priority Date and Time When using NTP. From 1972 until 31 December 2008.com/. 3. If your unit supports the GPS feature.4. If not using NTP you can set the date and time manually. For more information. Select Daylight saving time enable. When using NTP. refer to the following tables of parameters and examples.worldtimezone. To automatically set the date and time using GPS. At the start of 1972. Offset to be added to UTC time to convert to Temps Atomique International (TAI)—atomic international time. the priority can be set in the DiffServ Code Point. proceed as follows: 1. TAI was exactly 10 seconds ahead of UTC. If unchecked. 2. Select a time server from the list and click Apply. High resolution sync TAI offset Uses high-resolution hardware synchronization. Select a server from the list or add your own. Go to System > Configuration > Time. select GPS enable and click Apply. the NTP server is queried only every 30 minutes and the system time is set accordingly. proceed as follows: 1. Note that only one NTP server can be used in a network. The unit also provides for time zones and Daylight-saving time. Since the last second was added on 31 Dec 2008. without further processing. Time Parameters (System > Configuration > Time) Parameter NTP enable NTP server enable Description Sets the system time automatically by polling an NTP server. The unit becomes an NTP server and can be used by other NID units as the NTP server.

GPS Parameters (System > Configuration > Time) Parameter GPS enable Satellite SNR GPS fix Latitude / longitude Description Use the GPS receiver to set the system time automatically. Shows whether the GPS receiver is locked to a GPS signal. day. Day=Sunday. week. Use daylight saving time. Day=Sunday. Hour=2. To describe the last day of the month. Be aware that syslog and other services that timestamp events with the current date and time are affected during DST transitions. use week=5 Examples of Setting Time Setting the Time for Montreal. Quebec. Canada Parameter UTC offset DST enable DST offset DST start DST end Value -5 Check 1 Month=March. Usually it is one hour. Min=0 64 . Eastern Europe would have positive values. There may be a gap of an hour or duplicate time stamps because the clock was changed. Min=0 Month=November. Hour=2. Period where daylight saving time is in effect. Time Zone Parameters (System > Configuration > Time) Parameter UTC offset Daylight saving enable Daylight saving offset DST start and DST end Description Offset from Coordinated Universal Time. The current location of the unit according to its GPS receiver. DST start and end are defined using month. Week=1. The Signal-to-Noise ratio (in dB – Hz) of each satellite in view. North America has negative values. hour and minute. Week=2. Time correction to apply to GMT offset during the daylight saving period.

For more information on specific parameters. This is optional and may be set to none if only a single reference clock is desired. Forced clock This forces the clock selector to use a specific clock source. clock status information is also displayed. Options Primary clock source Secondary clock source Revertive The port from which the Primary Reference Clock is recovered. New Zealand Parameter UTC offset DST enable DST offset DST start DST end Value 12 Check 1 Month=September. refer to the following table.Setting the Time for Wellington. 2. Select Enable SyncE. When enabled. When disabled. When enabled. Day=Sunday. the clock reference port(s) operate as clock slave(s) and all the other ports on the system operate as masters. In this mode. should it become available again. You also have the option to define a Secondary Clock Source on another physical port. all ports on the system operate as clock master. Hour=3. Week=1. the clock selector is allowed to switch back to a higher priority clock source that previously failed. transmitting the clock signal from the clock reference port. Min=0 Setting SyncE You can use the synchronous Ethernet (SyncE) feature to synchronize the unit and all its outputs over Ethernet networks. When enabled. Go to Port > SyncE. Week=5. If none is specified. fill in the parameters and click Apply. the selector cannot revert to a clock that previously failed. Hour=2. The port from which the Secondary Reference Clock is recovered. When disabled. To set up SyncE. It takes the clock signal from the selected clock reference port and transmits it to all other ports. Min=0 Month=April. Day=Sunday. proceed as follows: 1. 65 . the clock selector is allowed to go to a lower priority clock source only should the currently selected source become unavailable. SyncE Parameters (Port > SyncE) Parameter Enable SyncE Description Enable or disable the synchronous Ethernet feature.

Parameter source Status Clock selector

Description clock source selection is automatic.

The clock source that is currently in use by the SyncE hardware. Possible values are: Primary: The primary reference clock is in use. Secondary: The secondary reference clock is in use. Holdover: The selected reference clocks are no longer available and the system is in holdover mode, using a frequency based on the computed average of the last known good reference clock. Local: The local oscillator is in use. This should only happen when SyncE is disabled.

Primary clock status Secondary clock status

The current status of the primary reference clock. The current status of the secondary reference clock.

Setting up DNS
You can use the DHCP to automatically configure the unit‘s IP parameters. When the unit uses DHCP, it uses the DNS settings from the DHCP. If the unit does not use DHCP, you can manually specify the address for each DNS server. Two DNS servers can be used for redundancy. To use the DHCP, proceed as follows: 1. Go to System > Configuration > DNS. 2. Put a check mark in the Use DHCP results box. 3. Use From interface to select the interface from which to obtain DHCP information. For more information on specific parameters, refer to the table DNS Parameters (System > Configuration > DNS). To manually specify the address of DNS servers, proceed as follows: 1. Go to System > Configuration > DNS. 2. Remove the check mark from the Use DHCP results box. 3. Manually specify the address of DNS server 1 and DNS server 2 (if required), specify the Domain and then click Apply.

66

For more information on specific parameters, refer to the table DNS Parameters (System > Configuration > DNS).

Setting IGMP Version
Internet Group Management Protocol (IGMP) is a layer-3 communication protocol used by networking equipment to more efficiently manage multicast traffic. You must select the unit‘s IGMP version. This changes the IGMP version for all interfaces of the unit. To set the unit IGMP version, go to System > Configuration > Mode. For more information on specific parameters, refer to the table General System Settings (System > Configuration > Mode) on page 61.

Setting S-VLAN Ethertype
S-VLAN Ethernet is used often. You must select the unit‘s S-VLAN Ethertype that applies to the unit‘s elements. The S-VLAN Ethernet options are:  0x88A8: Provider Bridging (IEEE 802.1ad)  0x9100: Q-in-Q To set the unit S-VLAN Ethertype, proceed as follows: 1. Go to System > Configuration > Mode. 2. Select the S-VLAN Ethertype that should be applied to all entities and click Apply. For more information on specific parameters, refer to the table General System Settings (System > Configuration > Mode) on page 61.

Upgrading the Firmware
New firmware versions usually provide:  New functions  Enhancements to functions  Defect corrections. To verify the current software version, see the Current version field of the Firmware maintenance section in the System > Maintenance > Firmware page. To upgrade the unit‘s firmware, proceed as follows: 1. Go to System > Maintenance > Firmware. 2. Click the Browse button next to the New version field.

67

3. Select the firmware file and click OK. Note: The firmware is distributed in a binary file with the filename extension .afl. 4. Click the Upgrade button. Once the firmware has been loaded, the unit will restart in order to activate the new firmware. 5. To verify that the upgrade was successful, go to Home and verify the Firmware version. If you want to revert to the previous version of software, proceed as follows: 1. Check that the version displayed in Rollback version is the one you want to revert to.

2. Click Rollback. For more information on specific parameters, refer to the following table.

Firmware Parameters (System > Maintenance > Firmware)
Parameter Current version New firmware Rollback version Rollback button Reboot button Description The current version of the firmware. The firmware version that is applied when you click upgrade. The previous firmware version that you can revert to. Reverts to the firmware version listed in Rollback version. Reboots the unit and activates the new configuration

Importing/Exporting the Unit’s Configuration
If you need multiple units in your network to have the same configuration, you can configure your first unit and then export this configuration to a file. You will then be able to import this configuration file into other units to configure them in the same way. CAUTION: When using the Import/export function, be careful with the DNS settings. The IP connectivity to each unit might be at risk if you are using a static IP address configuration in the Management interface. The use of DHCP is therefore recommended when importing the unit’s configuration to multiple units. Two formats are available for exporting configurations. The format depends on how you want to import the configuration:

68

 

Regular (Linux format): import using the management web-interface. Vision EMS PPT configuration: import using the Vision EMS management tool.

Each configuration file provides an identifier to help prevent importing a wrong file. CAUTION: Although you can edit the configuration files, this risks corrupting the file! The regular format is Linux and you should not open the file using a Windows® application such as Notepad. To export a configuration in regular format, proceed as follows: 1. Go to System > Maintenance > Firmware. 2. Enter a configuration filename in the Config export filename text box. For more information on the other parameters, refer to the table below. 3. Click Export. To import a regular configuration file, proceed as follows: 1. Go to System > Maintenance > Firmware. 2. Click the Browse button next to the Config import file field. 3. Select the firmware file and click OK. 4. Click the Import button. 5. Once the file is uploaded, click Reboot to activate the new configuration.

69

Go to System > Maintenance > Firmware. The name for the regular configuration file name to export. 2. To export a configuration in a Vision EMS PPT format. 3. The name for the PPT configuration file name to export. Refresh the CPU usage data by clicking the Refresh button. proceed as follows: 1. put a check mark on the Poll every Seconds box and enter the number of seconds you want to have between refreshing the data. A large amount of PAA processing or SNMP gets could increase CPU usage. 1. refer to the table below. Configuration Import/Export Parameters (System > Maintenance > Firmware) Parameter Config import file Config export filename PPT export filename Factory default button Cancel changes button Rollback button Description The configuration file to import. The factory default and rollback actions require a system reboot. You can cancel these actions by clicking Cancel changes. 3. proceed as follows: Note: A configuration exported in a Vision EMS PPT format can only be imported into another unit with the Vision EMS.For more information on specific parameters. 2. Applies the factory default settings. To view the unit‘s CPU usage. 70 . CPU usage has no impact on customer traffic. Rolls back the configuration to the version from the last reboot of the unit. Click Export. Viewing CPU Usage Viewing CPU usage can be useful for managing the unit. Enter a filename for the PPT configuration file in the PPT export filename text box. Go to Show > CPU usage. Or. The PPT file is exported as a compressed XML file.

CPU usage over the last second. CPU usage average from the last completed period of 60 seconds. proceed as follows: 1. Rebooting the Unit You need to reboot the unit for applying unit configuration after importing a new configuration (Refer to Importing/Exporting the Unit’s Configuration): CAUTION: Rebooting a unit is disruptive. proceed as follows: 1. To reboot the unit. Click the Reboot button. 2. Go to System > Maintenance > Firmware. CPU usage average from the last completed period of 5 minutes. refer to the following table. CPU usage average from the last completed period of 30 seconds. Restarting the Unit To restart the unit. The unit will restart. CPU usage (Show > CPU usage) Parameter Poll every Seconds Current 15 seconds average 30 seconds average 60 seconds average 5 minutes average CPU usage history Description The frequency with which to refresh CPU usage data. CPU usage average from the last completed period of 15 seconds. It applies changes in the unit’s configuration and affects current operations. CPU usage over the last 100 seconds presented as a graph. press and release the Loopback button. Release the Bypass button. 71 . 3.For more information on specific parameters. Simultaneously. 2. Press and hold the Bypass button on the rear panel of the unit.

to reset the unit to factory default settings from the unit‘s rear panel. 3. Note: “HARD RESET” is for use when the management web-interface is not responding properly. Or. 4. proceed as follows: 1. 72 . press and release the Loopback button. Each way is described below. Major. Press and hold the Bypass button. To reset the unit to factory default settings using the management web-interface. Click the Factory default button. Simultaneously. proceed as follows: 1. Release the Bypass button. Continue to press the Bypass button until the LEDS for Minor. 2.Resetting to Factory Defaults You can reset the unit to factory defaults either by using buttons on the rear panel of the unit or by using the management web-interface. Go to System > Maintenance > Firmware. Critical and Power flash at the same time. 2.

Port Configuration (Port > Configuration) Parameter Status Description The following colours indicate port status: Green: the port is up and running. Grey: the port is disabled. To view ports or set up a port. Red: the port is enabled but the physical link is down and no signal is detected. Click the Port name to edit its settings. For more information on specific parameters. 3. refer to the table below. Define port parameters as required by your setup and then click Apply. link speed (auto-negotiation) and flow control. 73 . For more information on specific parameters. Blue: the port is enabled and a signal is detected. which are physical interfaces on the unit and contains the following sections:  Setting up Ports  Setting up Media-Selection  Setting up Port Protection  Setting up Fault Propagation  Viewing Port Statistics  Setting up Port PHY  Viewing SFP Information Setting up Ports The parameters you can set up for each port include options such as protection (when available). Note: The page varies depending on whether you are setting up a copper port or an SFP fiber port. proceed as follows: 1.Managing Ports This chapter describes how to manage the ports. Yellow: the port is not totally functional. 2. refer to the following table. This displays a list of all ports and their status. Port State The port may be enabled or disabled. Go to Port > Configuration.

the other device must also be set up for auto-negotiation. Link partner must be set to MDIX or a cross-over cable must be used. This cycle is repeated until the link is re-established. Default: 2000 Large packet threshold MAC address Connector Media dependent interface (Copper ports only) Packets above this threshold will be classified as Large Packets. The 'alias' name for the port as specified by a network manager. Link Loss Return (LLR) (SFP fiber ports only) This option determines how the unit notifies its link partner when a valid receive signal is absent on the link. For this to work. The default port name varies depending on the operation mode. after which it is re-enabled. If Auto MDI is not in use. The MAC address of the port. Entering a value of 0 puts the laser into a disabled state waiting for the opposite side to send a light pulse in order to reestablish the link. So. If this option is disabled. 0 should not be configured on both sides or the link will never re-establish. Speed Link speed Sets port speed and duplex type. If this option is enabled. for this reason.Parameter Enable Port Name Name Alias Port MTU Description The name that identifies the port. then: For 1000BASE-X links. including all headers. The Large Packets count can be viewed on the Port > Statistics page. a Remote Fault Indicator (RFI) using auto-negotiation advertisement is sent to the link partner. The maximum transmission unit in bytes that a port can receive and forward. Auto-negotiation: The unit automatically negotiates port speed and duplex type with the device it is connected to. If Auto-negotiation is not in use. Supported values: 1518 to 10240. the FEFI idle pattern is sent to the link partner. you can manually define port settings as follows: MDI: Typical setting for an Ethernet station. The physical connector associated with the port. For 100BASE-FX links. MDIX: Typical setting for an Ethernet switch. Link partner must be set to MDI or a cross-over cable must be used. you can manually define port speed and duplex type using the following available options:  10 Mbps  100 Mbps 74 . Auto MDI means that the unit automatically adapts the configuration of the connector to the cabling plant and type of link partner. then the unit turns off its transmitter for the amount of time defined in the LLR period.

If the timer (link time out) expires and the link stays down. The protecting port is reserved by the protection mechanism and can not be used for monitoring purposes while protection is enabled. Working connector The working connector for the specified port. you must create an L2PT rule with an operation mode of ―Peer and Protocol LACP‖ on this port in order to terminate LACP packets. disable: pause frames are disabled. This is available for only link status protection mode and only on the network port. Propagate from port Flow control 75 . In revertive mode. The timer is restarted if a signal loss is detected during this period. Revertive When enabled. Note that protection is available on the network port only. One-way link: Propagate faults in one direction based on the link status of the opposite port. One-way EVC: Propagate faults in one direction based on the link status of the opposite port or the EVC status. Note that this parameter is available on the network port only. traffic is switched back to the main connector after the revert period has expired. Protection Enable Enable protection for the port selected in the working connector. when both ports are working. Enable fault propagation Fault propagation mode Enables the propagation of link faults between the ports specified in Propagate from port. the system switches back to the working connector. Revertive period The time (in seconds) that the system must continuously detect a valid signal on the main connector in order to switch back to this connector. This is available for link status protection mode only. Link time out The time (in seconds) for the protection link to come up after switching to the protection connector when the protection link is down. Note that protection is available on the network port only. If LACP status is selected. Note that this parameter is available on the network port only.Parameter Description  1 Gbps  Half-Duplex: Transmission in one direction at a time  Full-Duplex: Transmission in both directions at the same time Note that Auto-negotiation is mandatory for 1000 BASE-T. Choosing the connector when enabling the protection allows you to perform a switchover operation. Protection Mode Switching protection to a standby connector can be based on Link status or LACP status. The name of the port from which faults are propagated. Note that this parameter is available on the network port only. the traffic reverts to the working connector.

otherwise it is master. The tables below show the media-selection options and the connector-to-port mapping for the operation modes that use media-selection. Current connector configuration: If the link partner is also using Auto MDI. proceed as follows: 1. In standard operation mode. The TTL value indicates the number of seconds that the recipient LLDP agent is to regard the information associated with this MSAP identifier as valid. To select connectors via media-selection. In Aggregator 3x1 mode. In forced mode. the clock master is determined by the auto-negotiation process.Parameter Description local: pause frames are processed locally. refer to the two following tables: Media Selection Options in Standard Operation Mode (Port > 76 . use media-selection to select the connectors to be used by the client and network ports. For more information on specific parameters. Note: The media-selection option is supported on certain types of units only. the resulting connector configuration is correct but random. Mastership mode: On 1-Gbps copper ports. the clock is forced into slave if the port is a clock reference for the system. 2. A cross-over cable present on the cabling plant results in both partners using the same connector configuration. Setting up Media-Selection Media-selection is used to specify which connectors will carry traffic. The media-selection option is available in two operation modes. Rate: The LLDP frame transmission rate (in seconds) on the selected port [1–65535]. as described in Understanding Operation Modes on page 57. Select Media-selection and then click Apply. Go to Port > Configuration. TTL: The TTL value (Time to Live TLV) in the LLDP frame on the selected port [0–65535]. In auto mode. use media-selection to select the connector to be used by the network port. Note: The names of the ports in the tables below are the factory default names. all associations between connectors and ports will be reflected in the port configuration and status pages. transparent: pause frames are transparently passed through. this reports the clock mastership mode. LLDP Enable or disable LLDP (Link Layer Discovery Protocol) frame transmission on the selected port. Current status Current link speed and duplex type when Auto-negotiation enable is selected. usually when using SyncE. When changing this setting.

Go to Port > Configuration. If we refer to the default ports names. Protection is available on the network port only. When a switchover or a failover operation is performed. the protected port is always the network port and the protect port is always the Monitor-1 port. For more information on specific parameters. proceed as follows: 1. the two ports are swapped. Media Selection Options in Standard Operation Mode (Port > Configuration) Media Selection Option SFP-A with SFP-B SFP-A with RJ45-B RJ45-A with RJ45-B RJ45-A with SFP-B SFP-A Client Client Monitor-1 Monitor-1 SFP-B Network Monitor-2 Monitor-2 Network MGMT Management Management Management Management RJ45-A Monitor-1 Monitor-1 Client Client RJ45-B Monitor-2 Network Network Monitor-2 Media Selection Options in Aggregator 3x1 Operation Mode (Port > Configuration) Media Selection Option SFP-A SFP-B RJ45-A RJ45-B SFP-A Network Client-1 Client-2 Client-3 SFP-B Client-1 Network Client-1 Client-1 MGMT Management Management Management Management RJ45-A Client-2 Client-2 Network Client-2 RJ45-B Client-3 Client-3 Client-3 Network Setting up Port Protection The port protection is a mechanism used to switch the traffic to a standby connector if a down link is detected on the main connector. To set up port protection. refer to the table Port Configuration (Port > Configuration). if we choose RJ45-A with SFP-B. Note: Port protection is available only on a MetroNID with an SFP 1000X port set to link-status mode. 3. For example. Click the Port name to edit its settings. To perform a switch to the standby port. the main connector is SFP-B and standby connector is SFP-A. proceed as follows: 77 . Define port protection parameters as required by your setup and then click Apply. 2. Main and standby connectors are determined by Mediaselection in the Port > Configuration page.Configuration) and Media Selection Options in Aggregator 3x1 Operation Mode (Port > Configuration).

Go to Port > Configuration. Select the Working connector to which you want to perform the switch and then click Apply. refer to the following table. 3. Viewing Port Statistics You can view a summary and a detailed port statistics for each port. If there is no PAA probe and no CFM MEP set up in EVC fault propagation mode for the specified port. Click the Port name on which you want to perform the switch. 78 . If you are using EVC status. then the port selected for fault propagation will stay down. To set up port fault propagation. 3. Define port parameters as required by your setup and then click Apply.1. At least one PAA probe or CFM MEP should be free of connectivity errors to enable fault propagation on EVC status to the specified port. 2. For more information on PAA and CFM MEP. go to Port > Statistics. proceed as follows: 1. from SFP-A to SFP-B. To view a summary of statistics for all ports. For more information on specific parameters. 2. refer to the chapter Monitoring Network Performance. refer to the table Port Configuration (Port > Configuration). Click the Port name to edit its settings. the status of PAA probe(s) and/or CFM MEP(s) are propagated to the other port.g. For more information on specific parameters. refer to the table below. select a port name. only a link that is down on one port can bring the other port down. 2. To view the detailed port statistics. This can be used to propagate one of the following:  link status only  EVC status (link status is included). If you are using link status. Go to Port > Configuration. Setting up Fault Propagation You can set up the unit to propagate a fault detected on one port to another port. e. For more information on specific parameters. 1.

The deferral time starts at the beginning of each transmission attempt and ends when the transmission starts (regardless of collisions).e. Count of the good (not dropped and having valid CRC) unicast packets transmitted by this port. For FIFO underflows. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i. Count of the good (not dropped and having valid CRC) broadcast packets transmitted by this port. Multicast packets are identified by having a 1 in the least significant bit of the first byte of the destination address (i. all bytes transmitted before the start of the collision as well as the colliding and jam bytes are counted. Packets dropped due to excess deferral during the initial transmit attempt are not counted. Bad packets include normal collisions. Count of the good (not dropped and having valid CRC) multicast packets transmitted by this port.Port Statistics (Port > Statistics) Parameter Port name Description Ports for which statistics are shown. Count of the transmitted packets with a bad non-appended CRC field. It is assumed that all transmitted packets are properly sized: from 64 bytes (after any padding) up to the maximum size. Count of the number of packets dropped by this port due to excessive deferral. VLAN packets are identified by a type field equal to 8100h set in the outer VLAN tag. after a collision back off) are not counted. Count of the good (not dropped and having valid CRC) flow control pause packets transmitted by this port. Bytes total Txm packets Txm errors Unicast packets Multicast packets Broadcast packets Pause frames Tagged frames CRC errors Deferred Excessive deferrals 79 . Transmit statistics Bytes good Count of the total number of bytes transmitted by the port in good packets. Count of the good (not dropped and having valid CRC) VLAN packets transmitted by this port. the first bit transmitted is a 0). Number of transmission errors. all bytes actually transmitted are counted. The count includes the four CRC bytes but does not include the preamble or SFD bytes. The count includes the four CRC bytes but does not include the preamble or SFD bytes. Count of the total number of bytes transmitted by the port in good and bad packets.e. For collisions. This count does not include packets with a bad CRC due to a FIFO underflow. Count of the number of packets that were deferred on the first transmit attempt due to the medium being busy. Broadcast packets are identified by a destination address of all 1's. The deferral is excessive if more than 3036 byte times have passed without the transmission starting. Flow control pause packets are identified by a type of 88-08 and an opcode field of 00-01. Whether the packet is eventually transmitted successfully or not is irrelevant to this counter. Packets with subsequent deferrals (for instance. A good packet is one that has been transmitted successfully (not aborted) with a good CRC. the first bit transmitted is a 1). Broadcast packets are not included in this count. late collisions and FIFO underflows.

The collision window time is measured from the rising edge of TX_EN to COL asserted at the MII interface.Parameter Single collisions Multiple collisions Description Count of the number of times a packet is successfully transmitted from this port after experiencing a single collision. This count does not include erroneous (dropped) packets and also does not include packets dropped due to excess collisions. Count of the number of packets dropped by this port due to an underflow in the transmit FIFO. Count of the number of packets dropped by this port due to excess collisions (number of collisions equals MaxRetry+1). Count of the number of packets dropped by this port due to late collisions. This count does not include packets dropped due to FIFO underflow. This count does not include collisions during half-duplex back pressure. then none of the other packet type counters is incremented. Late collisions are not retried. Count of the total number of normal collisions that have occurred on this port during all transmission attempts. This count does not include erroneous (dropped) packets. transmission is immediately aborted after sending a known bad (inverted) CRC sequence. The FIFO underflow error takes precedence over all other errors if this counter is incremented. FIFO underflows. This count does not include packets dropped due to FIFO underflow or late collisions (even if the late collision is also an excessive collision). A late collision is a collision that occurs after the collision window delay (normally 512bit times). transmitted by this port that were exactly 64 bytes in length (excluding preamble and SFD but including CRC). late collisions and collisions that occur while this port is not trying to transmit are not counted. Count of the number of times a packet is successfully transmitted from this port after experiencing multiple collisions. good or bad. Excessive collisions Late collisions Normal collisions FIFO errors Packets 64 80 . The total number of packets. When an underflow is detected.

Number of errors received. A packet is error-free if it has a valid CRC. Count of the total number of bytes received by the port in good and bad packets. The count includes the four CRC bytes (if present) but does not include the preamble or SFD bytes. packets with PHY errors and packets with receive FIFO errors. Count of error-free packets received on this port that are shorter than 64 bytes. that were 65 to 127 bytes (or the other length listed in the parameter column) in length inclusive (excluding preamble and SFD but including CRC). Octets in otherwise good packets with a dribble nibble are included in this count. A packet is error-free if it has a valid CRC. Packets with PHY or FIFO errors are not counted. Bytes total Rcv packets Rcv errors Short OK Short bad Long OK 81 . Packets 1024 and above are only available on certain types of units. no PHY errors and no FIFO errors. Define the size of large packets from Port > Configuration > [port name]. Good packets are described above. Count of packets received on this port that are shorter than 64 bytes and have a bad CRC. The count includes the four CRC bytes but does not include the preamble or SFD bytes. transmitted by this port. Bad packets include short packets (less than 64 bytes). packets with bad CRC. A good packet is a well-formed normally-sized packet (64 to MTU configured on the port) with good CRC and no PHY or FIFO errors. The total number of large packets transmitted by this port. no PHY errors and no FIFO errors. Count of error-free packets received that are longer than MTU configured on the port.Parameter Packets 65– 127 Packets 128–255 Packets 256–511 Packets 512– 1023 Packets 1024–1518 Packets 1519–2047 Packets 2048–4095 Packets 4096–8191 Packets 8192 and more Large packets Description The total number of packets. Receive statistics Bytes good Count of the total number of bytes received by the port in good packets. Bytes in bad packets resulting from a collision are counted if the SFD is detected. long packets (greater than MTU configured on the port). good or bad.

Count of the good flow control pause packets received by this port (good CRC. the update of the RxRunts counter is suspended until the next valid packet is received. A length error occurs when the value in the length field is within the valid range for data length (3–1500 bytes) but does not match the actual data length of the packet. the first bit received is a 1). Count of the number of receive packets (or events) detected by this port without SDF detection but with carrier assertion. Packets with PHY or FIFO errors are not counted. normal size). A good broadcast packet is a normal size packet (64 to MTU configured on the port) that is not dropped and has a good CRC.e.e. Count of the good broadcast packets received by this port. Field lengths less than 46 bytes (smaller than the minimum legal packet size of 64 bytes) are not checked. Count of normally-sized packets (64 to MTU configured on the port) received by this port with a CRC error and a dribbling nibble (packet length is not an integral number of bytes). the first bit received is a 0). Broadcast packets are not included in this count. normally sized). due to padding. update of the RxFalseCRS counter is suspended until the next valid packet is received. Count of the good unicast packets received by this port. Multicast packets are identified by having a 1 in the least significant bit of the first byte of the destination address (i. no PHY or FIFO errors. the RxFalseCRS counter is incremented only once. If multiple false carrier events occur between valid packets. Packets with valid SFD but no data bytes are also counted as runts. Multicast packets Broadcast packets Pause frames Tagged frames CRC errors Align errors Runt frames Length errors False CRS 82 . Broadcast packets are identified by a destination address of all 1's. Count of the number of good packets received by this port with an error in the length field. no PHY or FIFO errors.Parameter Long bad Unicast packets Description Count of packets received that are longer than MTU configured on the port and have a bad CRC. Count of normally-sized packets (64 to MTU configured on the port) received by this port with a CRC error but not a dribbling nibble (packet length is an integral number of bytes). A good unicast packet is a normally-sized packet (64 to MTU configured on the port) that is not dropped and has a good CRC. After detecting a runt packet. Packets with PHY or FIFO errors are not counted. the RxRunts counter is incremented only once. A good multicast packet is a normally-sized packet (64 to MTU configured on the port) that is not dropped and has a good CRC. Count of the good multicast packets received by this port. VLAN packets are identified by a type field equal to 8100h set in the outer VLAN tag. Packets with FIFO or PHY errors are not counted. After detecting a false carrier. If multiple runt packets occur between valid packets. Count of the good VLAN packets received by this port (good CRC. Flow control pause packets are identified by a type of 88-08 and an opcode field of 00-01. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i. Count of the number of received packets (or events) detected by this port with a false carrier (SSD1 not followed by SSD2).

then none of the other packet counters is incremented. The total number of packets. The minimum data gap is the time between packet data transfers and is measured from immediately after the last CRC byte of the previous packet to the SFD field of the current packet. no PHY or FIFO errors. normally sized) with an unknown opcode. Count of the good control packets received by this port (good CRC. good or bad. A packet is ignored if it violates the programmed preamble rules or if it violates the minimum data gap. received by this port. 83 . good or bad. The normal data gap is 20 bytes long (12 bytes of IPG and 8 bytes of preamble/SFD). Count of the number of received packets dropped or aborted due to receiving a FIFO overflow. Count of the number of received packets that have been ignored by this port. Unknown control packets are identified by a type field of 88-08 and an opcode field not equal to 00-01. Packets 1024 and higher are available on only certain types of units. The enforcement limit is set to 10 bytes (half the normal gap length). FIFO errors Ignored Bad opcode Packets 64 Packets 65– 127 Packets 128–255 Packets 256–511 Packets 512–1023 Packets 1024–1518 Packets 1519–2047 Packets 2048–4095 Packets 4096–8191 Packets 8192 and more Large packets The total number of large packets received by this port. The FIFO overflow error takes precedence over all other errors: if this counter is incremented. that were exactly 64 bytes in length (excluding preamble and SFD but including CRC).Parameter PHY errors Description Count of the number of packets received by this port with RX_ER asserted during reception (while RX_DV is asserted). that were 65 to 127 bytes (or the other length) in length inclusive (excluding preamble and SFD but including CRC). The preamble rules include long preamble enforcement (greater than 23 nibbles) and pure preamble enforcement (only 55h bytes). received by this port. Packets with a FIFO error are not counted. The total number of packets. Define the size of large packets on the Port > Configuration > [port name] page.

Grey: The port is disabled. the unit automatically negotiates port speed and duplex type with the device it is connected to. 84 . Define port PHY parameters as required by your setup and then click Apply. Go to Port > PHY. To set up a port‘s PHY parameters. The PHY parameters are used to set the abilities that are advertised to the link partner. If enabled. For this to work. For more information on specific parameters. Red: The port is enabled but the physical link is down and no signal is detected. Blue: The port is enabled and a signal is detected. refer to the table below. the device and its partner must both be configured to support auto-negotiation (Port Configuration). State The current auto-negotiation state of the port. Indicates whether the auto-negotiation feature is enabled or disabled. For more information on specific parameters. proceed as follows: 1. 3. 2. The logical name assigned to the port. This displays a list of PHY configuration and status for all copper ports. Port Configuration (Port > PHY) Parameter Status Description Port status may be one of the following: Green: The port is up and running. To view PHY parameters.Setting up Port PHY You can view both SFP and copper ports and can set up PHY parameters for each copper port. Connector Port name Auto-nego The physical connector the port is using. Yellow: The port is not totally functional. This displays a list of PHY configuration and status for all ports. go to Port > PHY. Click the Port name to edit its settings. refer to the following table.

Possible values are:  Other  Configuring  Complete  Disabled  Parallel Detect Fail Each of the above values may be With auto or Without auto. The state disabled indicates that auto-negotiation is not supported by the media or is disabled by the configuration. Supported options include:  10 Mbps Half  100 Mbps Half  1 Gbps Half  10 Mbps Full  100 Mbps Full  1 Gbps Full  Pause Symmetric: can receive and transmit pause frames  Pause Asymmetric: can either receive or transmit pause frames The state field corresponds to ifMauAutoNegConfig and ifMauAutoNegRemoteSignaling from RFC3636. Supported options include:  10 Mbps Half  100 Mbps Half  1 Gbps Half  10 Mbps Full  100 Mbps Full  1 Gbps Full  Pause Symmetric: can receive and transmit pause frames  Pause Asymmetric: can either receive or transmit pause frames The abilities of the link partner.PHY Configuration (Port > PHY > [Port name]) Parameter Advertisement configuration Description The abilities that are advertised to the link partner. Link partner ability State 85 .

The manufacturer‘s part number or product name. which are converted into real units according to the ―External Calibration‖ convention. For more information on specific parameters. 86 . refer to the following table. SFP information Connector Type Vendor Wave Length Part number Serial number Revision SFP present Diagnostics Calibration The external cable connector provided as the media interface.Viewing SFP Information You can view both summary and detailed information about the SFPs. Thresholds Indicates whether alarm and warning thresholds are supported. Supported indicates that diagnostic information is provided in the SFP memory section. This is a 16-byte field that contains ASCII characters padded on the right with ASCII spaces (20h). The manufacturer‘s serial number for the transceiver The nominal transmitter wavelength at room temperature in nm. Supported or unsupported. Internal: The values are calibrated to absolute measurements. Indicates the presence of a recognized SFP. 1 Gbps. Connector Part number Serial number Wavelength Speed The physical connector the port is using. The manufacturer serial number for the transceiver. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h). The manufacturer‘s product revision. Red: the SFP is not present. External: The values are A/D counts. The manufacturer name.g. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h). To view a summary of all SFPs go to Port > SFP. The manufacturer part number or product name. Indicates the nominal transmitter wavelength at room temperature in nm. e. SFP Information (Port > SFP) Parameter Present Description Green: the SFP is present. The speed supported by the SFP. which should be interpreted according to the ―Internal Calibration‖ convention. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h).

For the manufacturer‘s specified wavelength. measured internally. Data is not valid when the transmitter is disabled. measured internally. In that case. Low-temperature warning for the transceiver. only one supply is monitored. Accuracy depends on the exact optical wavelength. Received optical power. Coupled TX output power. Data is not valid when the transmitter is disabled. 1 Gbps. e. measured internally.g. Coupled TX output power. transmitter supply voltage and receiver supply voltage are isolated. High-temperature alarm for the transceiver. High-supply voltage warning for the transceiver. Monitoring information Temperature Transceiver temperature. accuracy should be better than 3 dB for the specified temperature and voltage. Data is assumed to be based on measurement of a laser monitor photodiode current. Accuracy is manufacturer specific but must be better than 3 dB for the specified operating temperature and voltage. measured internally. Transceiver supply voltage. Low-supply voltage warning for the transceiver. measured internally. Description Laser bias current 87 . This accuracy should be maintained for input power levels up to the lesser of maximum transmitted or maximum received optical power per the appropriate standard.Parameter Speed Description The speed supported by the SFP. Temperature accuracy is manufacturer -specific but must be better than 3 degrees Celsius for the specified operating temperature and voltage. Accuracy is manufacturer specific but must be better than 3 dB for the specified operating temperature and voltage. It should be maintained down to the minimum transmitted power minus cable plant loss (insertion loss or passive loss) per the appropriate standard. Low-temperature alarm for the transceiver. Low-supply voltage alarm for the transceiver. Note that in some transceivers. Accuracy beyond this minimum required received input optical power range is manufacturer specific. Data is assumed to be based on measurement of a laser monitor photodiode current. High-temperature warning for the transceiver. Laser bias current Transmit power Receive power Supply voltage SFP thresholds (Port > SFP > [connector]) Parameter Temperature High alarm Low alarm High warning Low warning Vcc High alarm Low alarm High warning Low warning High-supply voltage alarm for the transceiver. Refer to the device specifications for more detail.

High-input power warning for the Rx (~ -40 to +8. Go to Port > Cable.2 dBm). Note: You can test cables only on RJ-45 ports. and termination mismatches. SFPs (optical or electrical) are not supported.2 dBm).2 dBm).2 dBm). This displays a summary of all cable test results for all available copper ports.2 dBm). Low-input power warning for the Rx (~ -40 to +8. Low-output power warning for the TX (~ -40 to +8. Testing a Cable You can test the quality of copper cables.Parameter High alarm Low alarm High warning Low warning Tx power High alarm Low alarm High warning Low warning Rx power High alarm Low alarm High warning Low warning Description High-laser bias current alarm for the TX (micro-Amps). manufacturer and other information. You can quickly find opens. Refer to INF-8074 for detailed descriptions of the individual data fields. Low-input power alarm for the Rx (~ -40 to +8. Low-laser bias current warning for the TX (micro-Amps). proceed as follows: 4. For this. To test the quality of a cable and view results. High-output power warning for the TX (~ -40 to +8. Click the Connector to test a cable. 88 . cable impedance mismatches.2 dBm). High-output power alarm for the TX (~ -40 to +8. High-laser bias current warning for the TX (micro-Amps). For more information on specific parameters. The test should last only a few seconds and the status of each channel is updated as the tests are run. SFP memory (Port > SFP > [connector]) The SFP memory field provides access to sophisticated identification information that describes the transceivers capabilities. 5. refer to the table below. Click the Perform test button to start the test. High-input power alarm for the Rx (~ -40 to +8. the unit uses time-domain reflectometry (TDR). Low-laser bias current alarm for the TX (micro-Amps). 6. connectors and terminations attached to each unit. bad connectors. standard interfaces.2 dBm).2 dBm). shorts. Low-output power alarm for the TX (~ -40 to +8.

The possible causes are:   Different quality cables are connecting through a cable extender A wrong quality of cable is used. FORCED: A persistent noise in the channel. Description The physical connector the port is using. SHORT: The positive and the negative lines of the same pair touch each other. The link partner must lose the link in order to start the test. Line of the RJ-45 cable may be worn from constant use and positive and negative lines may be touching. 89 . The other end of the RJ-45 cable may be simply unconnected. OPEN: There is a cut on a pair. The status of the cable: GOOD: Normal Cable. Line of the RJ-45 cable may have been cut unintentionally. it reports test FAIL. The possible causes are:    Line of the RJ-45 cable may be left unconnected at the wiring closet patch panel. This can be caused by a link partner running in forced 10/100 Mbps. The possible causes are:   Line of the RJ-45 cable may be touching the wire closet patch panel. Cable length is not available in the FORCED state. If the PHY receives a continuous signal during 125 ms.Cable Verification (Port > Cable) Parameter Connector Channel A Channel B Channel C Channel D Length Status The approximate location of diagnosed problems. The results for each pair in a four-pair cable are presented in these four columns. Impedance Mismatch Status: Whenever the effective impedance is not 100 Ohms. FAIL: The test failed.

The Bandwidth policing assures SLAs by regulating committed and excess information throughput. EIR. refer to the chapter on Monitoring Network Performance. per-circuit. It contains the following sections:  Understanding the Creation of Ethernet Services  Defining Filters  Setting up Traffic Policies  Understanding Traffic Shaping  Setting up Traffic Shaping  Using Layer-2 Protocol Tunnelling Understanding the Creation of Ethernet Services This section presents the creation of E-Line. For the definition and monitoring of the service performance attributes. CBS. bandwidth profiles. E-LAN and E-Tree services as described in MEF 6. CBS. CM.g. IP Precedence or PCP. It also explains how to configure some of the service attributes for the created services. Bandwidth profiles can be used to offer bandwidth to your client according to predefined SLAs. EBS. EIR. any combination of the following:    VLAN tagging: adds a C-VLAN or S-VLAN tag to the frame (selective push) CoS mapping: sets PCP (C/S-VLAN priority) value based on DSCP. Bandwidth policing: sets rate limiting based on the bandwidth profile defined for the selected flow: CIR. You can also specify. etc. CoS mapping. e. and CF). which are defined by the values of their associated parameters (CIR. E-LAN and E-Tree services by mapping traffic to an Ethernet Virtual Connection (EVC). are enforced via a token bucket algorithm according to Technical Specification MEF 5. Bandwidth Policing (also referred to as Rate Enforcement or Bandwidth Regulation): Bandwidth profiles. Layer-2 control protocol processing options.1. The services you can create are: Ethernet Service Mapping: Create E-Line. 90 . per flow: upstream and down.Managing Traffic This chapter describes how to create and manage Ethernet services. or EBS.

Token Bucket Algorithm for Bandwidth Profile Bandwidth profiles can be specified as follows:    Bandwidth Profiles Per Ingress UNI Bandwidth Profiles Per EVC Bandwidth Profiles Per CoS ID 91 .

Note: The maximum number of traffic policies using a specific filter (L2 filter or IPv4 filter) is limited by the type of unit you use. ICMP settings and VLAN settings. VLAN settings and DSCP for Layer-2 filters. CoS mapping and/or bandwidth policing. Refer to your unit’s datasheet for the maximum number of specific filters possible for traffic policies. You can also use the preconfigured Layer-2 or IPv4 filters. you can loop back traffic or set up a traffic policy based on specific characteristics such as Ethernet Header settings. Defining Filters You can set up a specific filter (layer 2 or IPv4) and use this filter for loopbacks or for traffic policies. 92 .Bandwidth Profile Types Traffic Filtering: Filters can be defined to classify traffic based on any combination of the following frame characteristics:     VLAN ID PCP value DSCP value IP precedence value The filtered traffic can be either dropped. or sent for service mapping. This way. or based on IPv4 Header settings.

The filter processes frames being sent to this address only. you need to disable the loopback and re-enable it (See Setting up and Enabling Loopbacks). the changes that you make are not applied to Loopbacks in use when you click Apply. The second VLAN ID assigned to the filter. Note: By default. refer to the following table. Note: When you edit an existing Layer-2 filter. 93 . Ethertype VLAN1 VLAN 2 The type of Ethernet frame that this filter processes. commonly used filters are defined. The VLAN ID assigned to the filter. For more information on specific parameters. check the box to enable the field. Other frame types are ignored. Note: You can specify several VLAN fields for the first VLAN (VLAN 1) as well as for the second level VLAN (VLAN 2). refer to the table at the end of this procedure. The address is specified as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Check the appropriate check box to enable this field. Go to Traffic > Filters > L2 filters. 2. The address is specified as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). the value will be ignored. The filter processes frames received from this address only. Click the Add button to add a new filter or click the Filter name of an existing Layer-2 filter to edit its settings. Description Unique name to identify the filter. For more information on specific parameters. 3. proceed as follows: 1. L2 Filters (Traffic > Filters > L2 filters) Parameter L2 filter name Filter name MAC destination The destination MAC address assigned to the filter. fill in the required fields and click Apply. MAC source The source MAC address assigned to the filter.Configuring a Layer-2 Filter To set up a Layer-2 filter. If the checkbox is not checked. Used to process VLAN-in-VLAN traffic. The filter processes frames only if they are tagged with this VLAN ID. Note: For all fields. If you want those loopbacks to use the modified Layer-2 filter. This displays a summary of all Layer-2 filters set up.

For instance. Ethertype Protocol may be selected or entered manually (hexadecimal). MAC source / mask VLAN and VLAN-in-VLAN settings Ethertype VLAN Ethernet Type may be one of the following: C-VLAN S-VLAN Both: C-VLAN and S-VLAN CFI/DEI Canonical Format Indicator or the Drop Eligibility Indicator. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). then that frame should not be forwarded "as is" to an untagged port. VLAN priority allows the provision of CoS prioritization using the standard 802. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN). Only the bits specified by the mask are used.1Q priority tag. If a frame received at an Ethernet port has a CFI set to 1. Only the bits specified by the mask are used. The other bits are ignored.Parameter Description Ethernet header settings MAC destination / mask The destination MAC address and mask. CFI is used to ensure compatibility between Ethernet networks and Token Ring networks. the other needs to be set to Equal to. The source MAC address and mask. Priority 94 . Valid operator types are: Greater than Less than Equal to Range (inclusive range) The possible values for each operator are: 0 to 7. Interpretation is based on the carrier's equipment and administrative policies. The other bits are ignored. Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range. This should always be set to zero for connection to Ethernet switches. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx).

Parameter VLAN ID VLAN 1 VLAN 2 Description VLAN ID to use for filtering traffic. 95 . the other needs to be set to Equal to. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN). Valid operator types are: Greater than Less than Equal to Range (inclusive range). Valid operator types are: Greater than Less than Equal to Range (inclusive range) Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range. For instance. DSCP/IP precedence DSCP/IP precedence DSCP/IP precedence operator.

The destination address assigned to the filter. The other bits are ignored. The filter processes packets received from this address only. IPv4 Filters (Traffic > Filters > IPv4 filters) Parameter IPv4 filter name Filter name IP source IP destination Protocol Src port Dst port The source address assigned to the filter. Note that filtering source or destination IP address assigned by Dynamic Host 96 . you need to disable the loopback and re-enable it (See Setting up and Enabling Loopbacks).Configuring an IPv4 Filter To set up an IPv4 filter. the changes that you make are not applied to Loopbacks in use when you click Apply. commonly used filters are defined. The destination port used to match this rule. The address is specified in dotted decimal notation. Note: By default. Note: For all fields. Description Unique name to identify the filter. This setting is valid only when the protocol field is set to TCP (6) or UDP (17). The source port used to match this rule. refer to the following table. This displays a summary of all IPv4 filters set up. Note: When you edit an existing IPv4 filter. If the checkbox is not checked. the value will be ignored. 3. Note: You can specify several VLAN fields for the first VLAN (VLAN 1) as well as for the second-level VLAN (VLAN 2). Go to Traffic > Filters > IPv4 filters. If you want those loopbacks to use the modified IPv4 filter. refer to the table at the end of this procedure. 2. For more information on specific parameters. fill in the required fields and click Apply. The filter processes packets being sent to this address only. Click the Add button to add a new filter or click the Filter name of an existing IPv4 filter to edit its settings. Check the appropriate check box to enable this field. This setting is valid only when the protocol field is set to TCP (6) or UDP (17). Only the bits specified by the mask are used. The protocol type for this filter to process. The address is specified in dotted decimal notation. For more information on specific parameters. proceed as follows: 1. check the box to enable the field. IPv4 header settings IPv4 source / mask IP source Source address and mask. Other protocol types are ignored.

TCP is used by HTTP. Only the bits specified by the mask are used. Telnet and SMTP. The protocols available. FTP. Time-to-live value. The other bits are ignored. Explicit Congestion Notification. in the format of ―protocol name (port number)‖. Specify either 0 or 3.Parameter Description Control Protocol (DHCP) can cause problems. Header length in 32-bit units. Note that filtering source or destination IP address assigned by Dynamic Host Control Protocol (DHCP) can cause problems. UDP is used by DNS. Specify a value in the range of 5–15. Protocol may be selected from the list or a manually entered port number (decimal). ICMP is used by Ping. are: ICMP (1) IGMP (2) IP (4) TCP (6) EGP (8) IGP (9) UDP (17) IPv6 (41) SDRP (42) IPv6-Route (43) IPv6-Frag (44) IDRP (45) RSVP (46) GRE (47) MHRP (48) IPv4 destination / mask IP destination TTL ECN Header length Protocol 97 . Common protocols are TCP (6). Destination address and mask. You should ensure that all IP addresses specified in a filter are static or reserved. Otherwise you must have to manually update your filter every time the addresses change. You should ensure that all IP addresses specified in a filter are static or reserved. UDP (17) and ICMP (1). Otherwise you must have to manually update your filter every time the addresses change. SNMP and RIP.

If a frame received at an Ethernet port has a CFI set to 1. Echo (8) and Time Exceeded (11). These settings are valid only when the Protocol is set to ICMP (1). Destination Unreachable (3). VLAN priority allows provisioning CoS prioritization using the standard 802.Parameter Description ESP (50) AH (51) MOBILE (55) SKIP (57) EIGRP (88) OSPFIG (89) IPComp (108) VRRP (112) UDP/TCP port settings ICMP settings Specify the UDP or TCP port number used by the IPv4 source and IPv4 destination port fields. Other ICMP Code: See www. Priority 98 . CFI is used to ensure compatibility between Ethernet type networks and Token Ring type networks. This setting is valid only when the protocol field is set to TCP (6) or UDP (17). These settings are valid only when the Protocol is set to TCP (6) or UDP (17).iana. Some well-known ICMP types are Echo Reply (0). Specify the ICMP message type for this filter to match. The destination port used to match this rule. This setting is valid only when the protocol field is set to TCP (6) or UDP (17). This should always be set to zero for connection to Ethernet switches. Interpretation is based on the carrier's equipment and administrative The source port used to match this rule.1Q priority tag.org/ UDP/TCP port settings Source port Src port Destination port Dst port VLAN and VLAN in VLAN settings Ethertype VLAN Ethernet Type may be one of the following: C-VLAN S-VLAN Both: C-VLAN and S-VLAN CFI/DEI Canonical Format Indicator or the Drop Eligibility Indicator. Redirect (5). then that frame should not be forwarded "as is" to an untagged port.

Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range. VLAN ID VLAN ID used to filter traffic. Valid operator types are: Greater than Less than Equal to Range (inclusive range) The possible values for each operator are: 0 to 7. Valid operator types are: Greater than Less than Equal to Range (inclusive range) Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN). 99 .Parameter Description policies. For instance. For instance. DSCP/IP precedence DSCP/IP precedence DSCP/IP precedence operator may be one of the following: Greater than Less than Equal to Range (inclusive range). the other needs to be set to Equal to. the other needs to be set to Equal to. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN).

Define service attributes:  Define bandwidth profiles.  VID Sets. Define filters (classify traffic): The system is designed in a way that the traffic must first be classified before sending it to any service creation function (Service mapping. bandwidth profile or filters). See Setting up VID Sets. See Setting up Bandwidth Regulator Sets 3. single Regulator (bandwidth profile) for default mapping or direct CoS mapping The number of policies you can set up depends on the operation mode of the unit (refer to the section Understanding Operation Modes on page 57).Setting up Traffic Policies You can create and manage Ethernet services through the Traffic menus.  Select the action to be applied to the traffic flow defined by the filter (Drop or Permit Traffic)  Assign or select one or more of the following characteristics:  EVC Mapping (encapsulation. Type. The major steps required to create or manage services are: 1. Ethertype.  Define Bandwidth regulator sets. Policies Supported by each NID Model NID Model and Operation Mode TE / TE-S Standard TE / TE-S Aggregator 2 x 1 Maximum Number of Policies per Port Network: 16 Client-1: 16 Network: 20 Client-1: 16 Client-2: 16 TE / TE-S Aggregator 3 x 1 Network: 20 Client-1: 16 Client-2: 16 Client-3: 16 100 . IP Precedence or PCP values of the ingress frame. 2. VLAN ID)  CoS Mapping (PCP action. See Defining Filters.  Define CoS mapping: Sets VLAN priority based on DSCP. See Setting up CoS Profiles. Create the service (See Setting up Traffic Policies) :  Select the filter that you defined in the first step. Three different types of filters can be defined:  Layer-2 filters and IPv4 filters. CoS profile or default mapping)  Bandwidth profile (Regulator set if CoS Mapping is Preserve or Map. See Setting up Bandwidth Regulators.

Setting up VID Sets You can define VID sets for each traffic stream (Traffic-A. VID Sets Supported by each NID Model NID Model and Operation Mode TE / TE-S Standard TE / TE-S Aggregator 2 x 1 Maximum Number of VID Sets per Port Network: 15 Client-1: 15 Network: 20 Client-1: 15 Client-2: 15 TE / TE-S Aggregator 3 x 1 Network: 7 Client-1: 3 Client-2: 3 Client-3: 3 101 . The number of VID sets you can set up depend on the operation mode of the unit. A VID set is made of one or more VLANs grouped in a logical entity. Refer to the section Understanding Operation Modes on page 57.NID Model and Operation Mode TE / TE-S Aggregator 4 x 1 Maximum Number of Policies per Port Network: 40 Client-1: 16 Client-2: 16 Client-3: 16 Client-4: 16 TE / TE-S Ring topology Network-A: 20 Client-1: 16 Client-2: 16 TE-R / TE-RS Standard Network: 60 Client-1: 60 Go to Traffic > Policies to view a summary of the policy configurations. Traffic-B. Traffic-C and Traffic-D) to classify the incoming traffic before sending it to the service creation function.

102 . you can apply it to traffic policies as a filter (See Setting up Traffic Policies).NID Model and Operation Mode TE / TE-S Aggregator 4 x 1 Maximum Number of VID Sets per Port Network: 7 Client-1: 3 Client-2: 3 Client-3: 3 Client-4: 3 TE / TE-S Ring topology Network-A: 7 Client-1: 3 Client-2: 3 TE-R / TE-RS Standard Network: 60 Client-1: 60 Traffic > VLAN > VID Sets Once a VID set is created. When using VLAN filtering. e. VLAN Filtering You can create VLAN filters using the VLAN type field (S-VLAN or C-VLAN) and VLAN ID or range. Traffic-A. See Selecting VLAN or VLAN-in-VLAN filtering).g. you also need to select the VLAN (inner or outer VLAN) for filtering the traffic for each policy list.

103. assign VID 0.. you must assign VID 0–4095. [. Policy Policy list VID list Specify a list of VIDs in the following format: [.2. 2. The port name. Click the Add button to add a new VID set or click the name of an existing VID set to edit its settings.100. Go to Traffic > VLAN > VID Sets. For more information on specific parameters. Size The number of VLANs contained in the VID set.]..]. 103 . Policy Lists (Traffic > VLAN > VID Sets) Parameter Name Incoming port Number of VID sets Description The name assigned to the policy list. No VID sets are defined by default. Setting up VID sets To set up a VID set.Viewing VID sets Go to Traffic > VLAN > VID Sets to view the existing VID sets.100-200 will include VIDs 1.102.  C-VLAN  S-VLAN State of the VID set according to its use in the traffic policy lists. 200. For untagged frames. VID Sets (Traffic > VLAN > VID Sets) Parameter VID Set Name Name Type VLAN type State The VLAN Ethertype of the VID set.g. (e. proceed as follows: 1.  Free (not assigned to a policy)  Mapped (assigned to a policy) The policy list on which the VID set will be active. Description The name assigned to the VID set.. refer to the following two tables. Note that for a catch-all filter.. 1.101. The number of VID sets that are currently used by this policy list.2.

The port name. refer to the following two tables. No VLAN IDs are assigned to VID sets by default. The number of VLAN that are currently used by this policy list. For more information on specific parameters.Note: When you edit an existing VID set. You need to re-apply the VID set to the policies by selecting a traffic policy and clicking Apply. Viewing VLAN IDs Go to Traffic > VLAN > VLAN IDs to view the VLAN IDs‘ mapping state. Policy Lists (Traffic > VLAN > VLAN Ids) Parameter Name Incoming port Number of VIDs used Description The name assigned to the policy list. Traffic > VLAN > VLAN Ids For more information on specific parameters. the changes that you make are not yet applied to the traffic policies that use it. Fill in the required fields and click Apply. 104 . refer to the table VID Sets (Traffic > VLAN > VID Sets). 3.

2. indicates to which VID set (Name). Select which VLAN you want to filter on for each policy list and click Apply. you can apply it to traffic policies (See Setting up Traffic Policies). If the VLAN is assigned to a VID set.  C-VLAN  S-VLAN Indicates the state of a specific VLAN  Free (not assigned to any VID set)  Assigned (assigned to a VID set)  Mapped (VID set to which the VLAN is assigned is used in a traffic policy) The policy index number to which this VLAN ID is mapped. The VLAN Ethertype of the VLAN. State Policy VID set Selecting VLAN or VLAN-in-VLAN filtering When using traffic policies with VLAN sets. For more information on specific parameters. proceed as follows: 1. Traffic Configuration (Traffic > Configuration) Parameter Traffic-A Traffic-B Traffic-C Traffic-D Description Select a policy list to inspect the inner or the outer VLAN. When filtering on the inner VLAN. the outer VLAN is ignored.VLAN IDs (Traffic > VLAN > VLAN Ids) Parameter VLAN ID Type Description The VLAN ID number. To select the VLAN filtering option. proceed as follows: 105 . When using the option of inner VLAN. Default: Outer. you need to select to filter on the inner or on the outer VLAN for each policy list. the outer VLAN is ignored. refer to the following table. Go to Traffic > Configuration. Setting up Bandwidth Regulators You can set up bandwidth profiles (and the corresponding bandwidth regulators to enforce them) through the Traffic > Regulators > Configuration menu. The number of traffic regulators that can be defined varies between models. To set up a bandwidth regulator. Once a bandwidth regulator is created.

Regulator Configuration (Traffic > Regulators > Configuration) Parameter Bandwidth regulator name Name Committed Information Rate (CIR) CIR The average rate (in Kbps) up to which the network delivers frames and meets the performance objectives defined by the CoS Service Attribute. Go to Traffic > Regulators > Configuration. Click the Add button to add a new bandwidth regulator or click the name of an existing bandwidth regulator to edit its settings. 3. color-blind: All incoming traffic enters the traffic regulator initially green. Coupling Flag The way in which the regulator processes yellow traffic. refer to the table at the end of this procedure. For more information on specific parameters. color-aware: Pre-determined level of Bandwidth Profile compliance for each Frame is taken into account when determining the level of compliance. none are defined initially. 2. Description Name identifying the regulator. Range: 2 to 2015 KB The maximum average rate in Kbps of frames up to which the network may deliver Service Frames but without any performance objectives. refer to the following table. Yellow traffic in excess of this maximum is declared red by the regulator and is dropped.1. Range: 0 to maximum port speed (steps of 125 Kbps) Committed Burst Size CBS Excess Information Rate (EIR) EIR Excess Burst Size EBS Color mode The maximum number of kilobytes available for a burst of frames that are sent at the UNI speed and that remain CIR-conformant. By default. The burst size must be greater than the port Maximum Transfer Unit (MTU). False: Yellow data is limited by the setting of the Excess Information Rate. The burst size must be greater than the port MTU Range: 2 to 2015 KB Indicates whether the color-aware or color-blind property is employed by the Bandwidth Profile. Fill in the required fields and click Apply. Traffic that is declared green and that conforms to CIR or CBS is allowed to pass through the Policer without rate limitation. Green traffic in excess of this maximum is declared yellow by the regulator and is submitted to EIR regulation. 106 . This displays a summary of all existing bandwidth regulators. Range: 0 to maximum port speed (steps of 125 Kbps) The maximum number of kilobytes available for a burst of frames that are sent at the UNI speed and that remain EIR-conformant. For more information on specific parameters.

For more information on specific parameters. you need to assign in the mapping table.Parameter Description True: Yellow data is limited by the setting of the Committed Information Rate plus the Excess Information Rate. four commonly used profiles are set up. CoS Profile Configuration (Traffic > Mapping > CoS profiles) Parameter Name Type Description Name identifying the CoS profile. To set up a CoS profile. proceed as follows: 1. Click the Add button to add a new CoS profile or click the name of an existing CoS profile to edit its settings. refer to the table at the end of this procedure. The mapping table has N rows. Go to Traffic > Mapping > CoS profiles. Setting up CoS Profiles A CoS profile is used to map an input frame to a Layer-2 class of service based on the conformance level (Green/Yellow) of the incoming traffic and on the value of the following information of the incoming frames:    PCP: p-bits in 802.1Q / 802. If the CoS profile type is PCP or IP precedence then N=8. See Setting up Traffic Policies. Fill in the required fields and click Apply. IP precedence: IP precedence mapping 107 . To set up the CoS profile. For more information on specific parameters. a class of service value (0-7) to the outgoing traffic based on the conformance level (Green/Yellow) of the incoming traffic and on the mapping entry. Type may be one of the following: PCP: Priority Code Point mapping. Specifies which incoming packets are going to be mapped to the CoS.1Q-in-Q tags IP precedence: IP precedence bits in IPv4 TOS byte DSCP: DSCP bits in IPv4 TOS byte Once a CoS profile is created. 3. By default. 2. where N depends on the type of the CoS profile. N=64. This displays existing CoS Profiles. refer to the following table. you can apply it to Traffic policies for CoS mapping and bandwidth policing. If the CoS profile is a DSCP.

This value is selected if:  the result of the bandwidth regulator assigned to this entry is yellow. CoS value (0-7) for use in the outgoing yellow frames. otherwise. Otherwise. or  the frame has passed through a color-aware bandwidth policer and (due to the depletion of its CIR bucket) it has been marked as yellow. Reference count (only visible on existing profiles) PCP or IP precedence or DSCP [IN] Pre-marking color Green [OUT] Input value of the incoming frame for PCP. or  the pre-marking color is yellow and no bandwidth regulator is assigned to this entry.Parameter Description DSCP: Differentiated Services Code Point mapping Reference count Decode DEI The number of policies that are currently using this CoS profile.1Q-in-Q tags IP precedence: IP precedence bits in IPv4 TOS byte DSCP: DSCP bits in IPv4 DSCP byte 108 . CoS value (0-7) for use in the outgoing green frames. The number of policies that are currently using this CoS profile. If this field is checked and the outgoing frame is marked yellow then the DEI bit is set to 1. This value is selected if:  the result of the bandwidth regulator assigned to this entry is green. the DEI is set to 0. Encode using DEI This makes the unit Control the DEI bit in an S-VLAN tag. or  the pre-marking color is green and no bandwidth regulator is assigned to this entry. IP precedence or DSCP type frame. the user defined pre-color is used. Yellow [OUT] Setting up Bandwidth Regulator Sets A bandwidth regulator set is used to regulate traffic bandwidth based on the value of the following information of the incoming frames:    PCP: p-bits in 802. This parameter is only available when PCP CoS profiles type is selected.1Q / 802. Pre-marking color to assign to the input frame that has this PCP. This makes the unit decode the pre-marking color from the DEI bit (Drop Eligible Indication). IP precedence or DSCP value.

IP precedence or DSCP value of the incoming frame. IP precedence or DSCP value. you need to assign in the mapping table. This displays the existing bandwidth regulator sets. refer to the following table. 3. For more information on specific parameters. (See Setting up Traffic Policies). proceed as follows: 1. Go to Traffic > Mapping > Bandwidth regulator sets. IP precedence: IP precedence mapping DSCP: Differentiated Services Code Point mapping Reference count (only visible on existing sets) PCP or IP precedence or DSCP [IN] Bandwidth regulator Enable regulator The number of policies that are currently using this Bandwidth regulator set. 109 . Before configuring a Bandwidth regulator set. If the type is PCP or IP precedence then N=8. BWR Set Configuration (Traffic > Mapping > Bandwidth regulator sets) Parameter Index Name Type Description The unique identifier of the Bandwidth regulator set.Once a Bandwidth regulator set is created. PCP. To configure the Bandwidth regulator set. refer to the table at the end of this procedure. If the type is DSCP. Name of the Bandwidth regulator set. To configure a Bandwidth regulator set. a traffic regulator (to a specific PCP. 2. Specifies the type of priority the Bandwidth regulator set is based on. Enable or disable traffic regulation for this PCP. This table has N rows. Fill in the required fields and click Apply. IP precedence or DSCP value. you can assign it to traffic policies for rate enforcement based on the map type being used. where N depends on the type of the regulator set. IP precedence or DSCP value. Click the Add button to add a new Bandwidth regulator sets or click the name of an existing Bandwidth regulator set to edit its settings. N=64. Type may be one of the following: PCP: Priority Code Point mapping. you must first set up a number of traffic regulators (refer to Setting up Bandwidth Regulators). Bandwidth regulator to use to regulate the traffic flow that has this PCP. For more information on specific parameters.

thereby defining the new service and its attributes. The next sub-sections describe the different EVC encapsulation options and the different PCP actions available. DSCP PCP VLAN. Pop Use this option to regulate traffic based on PCP. The table below shows the valid configurations of the first and second choices. None Use this option when no VLAN ID manipulation is required for the selected traffic flow and you need to regulate bandwidth based on PCP. Refer to PCP Action Options. IP precedence. DSCP IP precedence. you may select the PCP action for CoS mapping if required. bandwidth regulators. the VLAN ID in the outer tag of the frame is passed on to the tag that is added on top of it. Push & Preserve Use this option to push the specified VLAN tag onto an untagged frame. Refer to PCP Action Options. When using the Push & Preserve option. IP precedence or DSCP values. you can assign them to a traffic policy. 110 .Setting up Traffic Policies Once you have set up the different elements (filters. When using the Push option. you may select the PCP action for CoS mapping if required. PCP VLANinVLAN CoS profile BWR set Push Use this option to push (add) a VLAN tag onto an untagged frame or push an outer tag (Q-in-Q) onto a tagged frame. If the frame is already tagged. CoS profiles and bandwidth regulator sets). Options for an Encapsulation of NONE Parameter Type First Choice PCP VLANinVLAN PCP VLAN IP precedence. EVC Encapsulation Options Use the encapsulation options to perform EVC mapping actions. IP precedence or DSCP values before removing the VLAN tag. DSCP CoS profile BWR set CoS profile BWR set Second Choice PCP VLAN.

111 . PCP VLANinVLAN Ignored BWR set Replace This action is similar to the Push action but rather than adding a new VLAN tag. DSCP CoS profile BWR set Ignored BWR set Second choice PCP VLAN. the user can use the PCP action Map and the default 8P0D8P0D CoS Profile to preserve the incoming PCP value. DSCP IP precedence. The table below shows the valid configurations of the first and second choices for this encapsulation option. the user can use the PCP action Map and the default 8P0D-8P0D CoS profile to preserve the incoming PCP value. The PCP action Preserve is not supported by this encapsulation option. Note: This action requires a filter that checks the presence of at least 1 VLAN tag. Pop & Replace Use this option to pop the outer VLAN tag and replace the inner VLAN tag with the information provided by Ethertype and VLAN ID parameters. However. Preserve Use this option to copy the PCP bits from the first VLAN (if any) to the pushed VLAN tag. IP precedence. The PCP action Preserve is not supported by this encapsulation option. However.The table below shows the valid configurations of the first and second choices for this encapsulation option. It is also possible to select a bandwidth regulator set for bandwidth policing. it replaces the VLAN tag with the information provided by Ethertype and VLAN ID parameters. Options for Pop Encapsulation Parameter Type First choice PCP VLANinVLAN PCP VLAN IP precedence. Note: This action requires a filter that checks the presence of 2 VLAN tags (Q-inQ). If the frame is not tagged. PCP Action Options Use the PCP action options to perform different Priority Code Points actions. you may select the PCP bits from an IP precedence / DSCP CoS profile. DSCP PCP VLAN.

DSCP PCP VLAN. Filters based on VID sets use direct access to identify the corresponding policy for an incoming frame. For more information on specific parameters.Options for the PCP Action PRESERVE Parameter Type CoS profile BWR set First choice IP Precedence / DSCP CoS profile Optional Second choice N/A N/A N/A Direct Use this option to forces PCP bits to the default green or yellow values based on the result of the bandwidth regulator or the pre-marking color. IP precedence or DSCP values. PCP VLANinVLAN CoS profile Optional Viewing a Summary of the Policy Configurations Go to Traffic > Policies to view a summary of the policy configurations. refer to the following table. Options for the PCP Action MAP Parameter Type First choice PCP VLANinVLAN PCP VLAN IP precedence. The pre-marking color red is ignored if the default bandwidth regulator is disabled. 112 . Each frame‘s VLAN ID is analyzed and the value of the VLAN ID is used to directly access the appropriate policy to apply. DSCP CoS profile BWR set CoS profile Optional Second choice PCP VLAN. Click the name in the Policy lists to view the summary of the policy configurations of a particular port. IP precedence. The first and second choices can be used. DSCP IP precedence. The table below shows the valid configurations of the first and second choices. Note: The first and second choices are ignored. Map Use this option to map and regulate traffic based on PCP.

is shorter than 64 bytes. has a bad CRC. Click the Index of the policy to edit its settings. Click the Name in the Policy lists to view the policy of this list. Disabled policies are ignored when the rules are applied to incoming data. Name of the port of the traffic policies. 113 . Name of the filter assigned to the policy. Number of policies. 2. A good frame is an error-free frame that has a length between 64 bytes and the maximum frame length. Number of bad frames that matched the policy. Setting up Traffic Policies To set up a traffic policy. Policy configuration Type Regulator Policy statistics Packets good Bytes good Packets bad Number of good frames that matched the policy. or is longer than the maximum frame length. Action that the policy applies to data that it matches. Total number of bytes in good frames that matched the policy. proceed as follows: 1.Policy (Traffic > Policies) Parameter Name Incoming port Number of policies Index State Action Filter name Description Name of the traffic policy. A bad frame is a packet whose framing is valid but contains an error within the frame. Fill in the required fields. 4. Filter type (VID set) that is used to classify traffic. Note: The fields available for configuration vary depending on the Encapsulation and the PCP action you select. For more information on specific parameters. The policy may be enabled or disabled. The position of the rule in the policy list. 3. refer to the table Policy Configuration (Traffic > Policies). Go to Traffic > Policies. Name of the bandwidth regulator assigned to this policy.

Refer to EVC Encapsulation Options. Policy Configuration (Traffic > Policies) Parameter Enable policy Description Activates the policy. 114 . For more information on specific parameters. Refer to PCP Action Options. select the CoS profile to apply and select the bandwidth Regulator set to apply. refer to the following table. c) Select the EVC mapping encapsulation option and the required EVC mapping parameters. Refer to your unit’s datasheet for the maximum number of specific filters possible for traffic policies. The maximum number of traffic policies using a specific filter (L2 filter or IPv4 filter) is limited by the type of unit you use. g) Click Apply. Note: Only the traffic matching the filter will have the rules applied to it. select the Type of traffic mapping to perform.Traffic > Policies a) b) c) d) e) f) a) Enable the policy b) Select the filter to classify traffic and the required action. e) If you selected the PCP action MAP or Preserve. fill in the Direct mapping parameters. f) If you selected the PCP action Direct. d) Select the PCP action for CoS mapping to perform if required. enable one or two traffic mapping choices.

a ―catchAll" filter is defined. Note that this option will vary the available PCP action choices. IP precedence or DSCP values before removing the VLAN tag.Parameter Filter type Filter Action Description Filter type (L2 filter. then it is dropped. Replace: Use this option to perform an action similar to the Push action. MGMT-OAM: The traffic matching the filter is forwarded to the CPU so that it can be processed. The PCP action Preserve is not supported by this encapsulation option. the user can use the PCP action Map and the default 8P0D-8P0D CoS Profile to preserve the incoming PCP value. IP precedence or DSCP values. Push & Preserve: Use this to add a new VLAN using the VLAN ID of the inner VLAN (if any). Permit traffic: The traffic matching the filter is counted in the statistics then forwarded. By default. Pop & Replace: This action pops the outer VLAN tag and replaces the inner VLAN tag with the information provided by Ethertype and VLAN ID parameters. Pop: Use this option to perform traffic regulation based on PCP. EVC mapping Encapsulation Encapsulation may be one of the following: None: Use this option to perform traffic regulation based on PCP. it replaces the VLAN tag with the information provided by Ethertype and VLAN ID parameters. 115 . However. the user can use the PCP action Map and the default 8P0D-8P0D CoS profile to preserve the incoming PCP value. MGMT-OAM & Drop: The traffic matching the filter is forwarded to the CPU so that it can be processed. IPv4 filter or VID set) to classify traffic. Note that this action requires a filter that checks the presence of 2 VLAN tags. However. The action applied to traffic that matches the filter. This enables you to monitor all traffic on a port. MGMT-OAM & Forward: The traffic matching the filter is forwarded to the CPU so that it can be processed and forwarded. Note that this action requires a filter that checks the presence of at least 1 VLAN tag. The PCP action Preserve is not supported by this encapsulation option. Push: Use this option to add a new VLAN. The choices are: Drop traffic: The traffic matching the filter is dropped. The name of the filter. but rather than adding a new VLAN tag.

with a specific color. if no bandwidth regulator is enabled.Parameter Ethertype Description Ethertype of the VLAN to be added (if any). Bandwidth regulator set to apply from the list. Possible values: C-VLAN=0x8100 or S-VLAN=0x88A8. this option selects the default green/yellow CFI & PCP values to be used in the outgoing frames. Default/Direct Bandwidth regulator Enable bandwidth regulation Pre-marking color Activates a default bandwidth regulator. Possible values: A value between 0 and 4095. Enable Type Enable or disable the first and second traffic mapping choices.1Q-in-Q tags IP precedence: IP precedence bits in IPv4 TOS bytes DSCP: DSCP bits in IPv4 DSCP bytes CoS profile Regulator set CoS profile to apply from the list. the traffic that does not match the first and second traffic mapping choices. The list includes the default CoS profile and the ones you created.1Q tags PCP VLANinVLAN: Priority Code Point (p-bits) in 802. In addition. If the PCP action is Map and the traffic does not match the configured maps. Green traffic uses buffers from CIR until depleted. Pre-mark. at which time it will be tagged as Yellow data. If the frame does not match the first or the second choice. 116 . Note that the choices vary depending on the Encapsulation option and on the PCP action you selected. This option has no effect if the enabled bandwidth regulator is color-blind. CoS mapping PCP action PCP (Priority Code Points) action to perform. Type of Layer 2 traffic mapping to perform for the first and second choices. default PCP bits are used. The choices are: PCP VLAN: Priority Code Point (p-bits) in 802. direct default mapping is used. The list includes the bandwidth regulator sets you created. VLAN ID VLAN ID of the VLAN to be added (if any). The choices are: Preserve: Keep the PCP value or gather its value from the CoS profile Direct: Use the direct mapping options Map: Map the PCP/DEI values according to the chosen CoS Profile For each PCP action there may be one or two traffic mapping choices.

refer to the following table. Please note. Total accepted frames by this regulator since its creation.Parameter Description Yellow traffic uses buffers from either CIR + EIR or just EIR depending on the coupling flag set in the regulator. This is the number of Mbits sent in the last second of transmission. this data will be tagged as Red data. Accepted line rate in Mbps. The default CFI and PCP values to be applied if the Encapsulation is Push. This would only be applied if the traffic does not match the first and second traffic mapping choices. Red traffic is dropped. 117 . 1. that it is not possible to pre-mark data as Red if its bandwidth regulator is disabled. Bandwidth regulator CFI/PCP Default bandwidth regulator associated with the traffic matched by this policy. refer to the table below. Click the Regulator name to view detailed statistics of this traffic regulator. Total dropped bytes by this regulator since the statistical count started. For more information on specific parameters. 2. Total accept bytes by this regulator since its creation. Traffic color affects how the regulator handles the traffic. Total dropped frames by this regulator since its creation. For more information on specific parameters. Go to Traffic > Regulators > Statistics to view the statistics summary of all traffic regulators. Viewing Traffic Regulator Statistics You can view a summary and detailed traffic regulator statistics for each traffic regulator. Once CIR + EIR buffers are depleted. Bandwidth Regulator Statistics (Traffic > Regulators > Statistics) Parameter Name Accept bytes Accept packets Accept rate Drop bytes Drop packets Drop Rate Description The name assigned to the regulator. Dropped data rate in Mbps.

Note: Traffic shaping is available on the network port of MetroNID models TE and TE-S. 2.  Network port loopback  Traffic generator Traffic shaping behaviours depend on the operation mode of the unit. The traffic next goes to the network port shaper. In the direction from the client port to the network port: 1. Queue-2 or Queue-3) based on the PCP and CFI/DEI fields in the packets.Understanding Traffic Shaping Traffic shaping is used to reduce traffic burstiness for an outgoing interface. for example management traffic  Client ports: client port traffic is classified and assigned to a shaper's queue based on PCP fields.g. Shaper for Standard Operation Mode Traffic shaping in standard operation mode is available for client-to-network traffic. All traffic going through the unit is automatically sent. Queue-1. The traffic going to the shaping function can therefore come from the following sources:  CPU traffic. such as port protection. You can use up to three traffic shapers (queues). as described in Understanding Operation Modes on page 57. A real-time queue is also available to allow selected traffic. Refer to Setting up Traffic Policies. the outgoing traffic is prioritized as follows:  CPU  Real-time queue  Queue-1 CIR  Queue-2 CIR  Queue-3 CIR  Network port loopback  Traffic generator  Queue-1 EIR  Queue-2 EIR  Queue-3 EIR Note: Traffic from the traffic generator is not shaped. and use them for different priority traffic. high priority traffic. after classification. Operation mode also affects other functions. The traffic first goes to the shaper and is assigned a queue (real-time. You set up this shaper from Traffic > Shaping > Traffic shaper menu > Port. e. to the traffic shaping function. each with a different configuration. 118 . You set up this shaper from Traffic > Shaping > Traffic shaper configuration. If there is more traffic to send out than the port‘s total bandwidth can manage. to bypass the shaping function.

In the other direction. In the other direction. 119 . the traffic goes from the network port directly to the client ports without being shaped or queued. Shaper for Aggregator 2x1 Mode Traffic shaping in Aggregator 2x1 mode is available for client-to-network traffic. shaping in the client-to-network direction is as described above for standard operation mode. This is illustrated in the figure below. This is illustrated in the figure below. the traffic goes from the network port directly to the client port without being shaped or queued. For either client port.

You set up this queue from Traffic > Shaping > Traffic shaper configuration. The traffic of each shaper then goes to the network port shaper.Shaper for Aggregator 3x1 Mode Traffic shaping in Aggregator 3x1 mode is available for client-to-network traffic. The queued traffic of each client port next goes to its shaper and CIR for this client is applied. For each client port. You set up this shaper from Traffic > Shaping > Traffic shaper menu > Port. the outgoing traffic is prioritized as follows:  CPU  Client-1 real-time queue (strict priority)  Client-2 real-time queue (strict priority)  Client-3 real-time queue (strict priority)  Round robin of Queue-1 CIR between all client ports  Round robin of Queue-2 CIR between all client ports  Round robin of Queue-3 CIR between all client ports  Network port loopback  Traffic generator  Round robin of Queue-1 EIR between all client ports  Round robin of Queue-2 EIR between all client ports 120 . Queue-2 and Queue-3. the traffic first goes to the queuing function and is assigned a queue based on the PCP and CFI/DEI fields in the packets. Each set includes a real-time queue. If there is more traffic to send out than the port‘s total bandwidth can manage. Note: There are three sets of queues. Queue-1. 2. one set for each client port. In the direction from the client ports to the network port: 1. 3. You set up this shaper from Traffic > Shaping > Traffic shaper configuration.

For the four client ports. 121 . Round robin of Queue-3 EIR between all client ports Note: Traffic from the traffic generator is not shaped. without being shaped or queued. Only queuing is performed. the traffic is assigned a queue based on the PCP and CFI/DEI fields in the packets. the traffic goes from the network port directly to the client port. traffic is shaped as described above for standard operation mode. In the other direction. In the other direction. You set up these queues from Traffic > Shaping > Traffic shaper configuration. from network port to client port. Note: There is no shaping in the network-to-client direction. in the direction from a client port to the network port. Shaper for Aggregator 4x1 Mode Traffic shaping in Aggregator 4x1 mode is available for client-to-network traffic. This is illustrated in the figure below.

This is illustrated in the figure below. Shaper for Ring Topology Mode Traffic shaping in ring topology mode is available for client-to-network traffic. 122 . without being shaped or queued. In the direction from client ports to the network port. traffic is shaped as described above for Aggregator 3x1 mode. This is illustrated in the figure below. In the other direction. the traffic goes from the network port directly to the client port.

See Setting Global Traffic Shaping Parameters for the Network Port on page 123. 5. set the value of the PCP and CFI/DEI fields for traffic you do not want to be shaped. (You will be setting the PCP and CFI/DEI fields in the next steps. This can be traffic coming any possible sources listed above. Setting Global Traffic Shaping Parameters for the Network Port Go to Traffic > Shaping > Traffic shaper menu > Port to configure the shaping parameter of the outgoing port. refer to the table below. See Setting Global Traffic Shaping Parameters for the Network Port on page 123. See Setting the PCP-to-Queue Map on page 124. Configure the three shapers and the real-time shaper. Use the same PCP value and CFI/DEI value as the one you define in the PCP-to-queue map for each shaper. Note: The CPU traffic is never shaped. See Setting up Traffic Policies on page 100. In the traffic policy. Define the PCP-to-queue map. Configure the traffic to send for shaping. you would want not to send traffic from the CPU to go though the traffic shapers. in most cases. This can be traffic coming from any possible sources listed above. The major steps required to set up traffic shaping are: 1. Network-Port Shaper Setup (Traffic > Shaping > Traffic shaper menu > Port) Parameter Port name Committed Information Rate Description Unique name given to this port as defined in the port settings. 3. 2. See Setting up a Traffic Shaper on page 125. Configure the output port (network port) of the shaper. Use the same PCP value and CFI/DEI value as you define in the PCP-to-queue map for the real-time queue.) Be sure to map to the real-time queue for all traffic you do not want to shape. but. See Setting up Traffic Policies on page 100. In the traffic policy.Setting up Traffic Shaping You can set up the traffic shaping function through the Traffic > Shaping menus. set the value of the PCP and CFI/DEI fields for traffic you want to be shaped. The global shaping rate of green packets expressed as a multiple of 125 Kbps. You can also avoid real-time queue traffic from being shaped by disabling the Enable CIR realtime traffic option in the global traffic shaping parameters for the network port. 123 . For more information on specific parameters. but in most cases will be traffic coming from the client port. Configure the traffic not to send for shaping. 4. This maps outgoing traffic to a specific shaper or queue based on the PCP and CFI/DEI fields in the packets.

the pre-marking color is decoded from the DEI bit (Drop Eligible Indication). Edit the PCP map parameters as required and click Apply. As a result the bucket could become negative when this option is unchecked. The PCP precolor (Green or yellow) to be used by the shaper. Uncheck this option to bypass the traffic shaping for the real-time queue. The port associated with the PCP map. To edit the PCP-to-queue map. checking this option allows debiting the network port CIR bucket. 124 . This parameter is available only when Use DEI as precolor is unchecked. 3. Traffic-Shaper PCP Map (Traffic > Shaping > Traffic shaper menu > Map) Parameter Name Outgoing port Decode DEI Use DEI as precolor Precolor Description The name that identifies the PCP map. proceed as follows: 1. refer to the table below. you can specify the PCP precolor. Each PCP map is used to map the outgoing traffic to a specific shaper or queue based on the PCP and CFI/DEI fields in the packets. As a result the bucket could become negative. For more information on specific parameters. Setting the PCP-to-Queue Map You can edit the PCP-to-queue map. Click the PCP map Name to edit its settings. In both cases. Queue/Shaper The queue to which the PCP will be mapped. the real-time traffic will always be forwarded even if there are no tokens in the global CIR bucket. Otherwise.Parameter Committed Burst Size Enable CIR for CPU traffic Enable CIR realtime traffic Description The global shaping burst of green packets expressed as a multiple of 256 Bytes The CPU traffic is never shaped. Note: The PCP and CFI/DEI fields are the values added to the incoming packet by the Service Mapping module. When checked (enabled). the CIR bucket is debited. In other words. 2. However. Go to Traffic > Shaping > Traffic shaper menu > Map.

proceed as follows: 1. This is because link is underused when congestion management is either too aggressive or too conservative. all the PCPs mapped to this shaper's queue will be dropped. It allows the changes in the marking probability to take effect before the value is updated again. The unit provides a double data rate shaper consisting of CIR. Each shaper uses BLUE to manage queues based on link use. The BLUE algorithm is as follows: Upon Qlen > L1) event: if ( ( now . Shaper Configuration (Traffic > Shaping > Traffic shaper configuration) Parameter Name State Enable PCP List Green Yellow List of PCPs mapped to this shaper's queue and pre-colored as green List of PCPs mapped to this shaper's queue and pre-colored as yellow. BLUE uses also freeze_time. For more information on specific parameters.Setting up a Traffic Shaper Once you have set up the PCP-to-queue map. CBS. Note: The value of d1 should be set significantly larger than d2. If the queue is empty or link is idle. Description The name assigned to this shaper. 2. 3. It maintains a marking probability (pm) that is used to either mark or drop the packets. Bandwidth profile parameters CIR The shaping rate (in Kbps) of green packets (average output rate of the shaper). refer to the table below. When disabled. Go to Traffic > Shaping > Traffic shaper configuration. Enable or disable the shaper. If the queue is continually dropping the packets.last_update) > freeze_time ) pm := pm + d1 last_update := now Upon Qlen < L2event: if ( ( now . but packet loss occurs only when congestion management is too conservative.last_update) > freeze_time) pm := pm . which determines the time interval between two successive updates of pm. Edit the shaping parameters as required and click Apply. you need to set up each traffic shaper with the desired shaping characteristics. 125 . Click the traffic shaper Name to edit its settings. pm is increased by the factor d1.d2 last_update := now To set up a shaper. EIR and EBS. pm is decreased by the factor d2.

The marking probability is incremented by this value if there is a buffer overflow. This is done using the traffic-shaper PCP map. The shaping burst of green packets expressed as a multiple of 256 Bytes. The management of this buffer is done by the management queue algorithm BLUE. proceed as follows: 1. The shaping rate of yellow packets expressed as a multiple of 125 Kbps.Parameter Committed Information Rate CBS Committed Burst Size EIR Excess Information Rate EBS Excess Burst Size Description The shaping rate of green packets expressed as a multiple of 125 Kbps. The shaping rate (in Kbps) of yellow packets (average output rate of the shaper). Once the queue empties to the specified percentage. the pm will be decreased. the pm will be increased. Once the queue fills to the specified percentage. You can verify that this has been done correctly by viewing PCP lists for the real-time queue. The buffer is used to queue the packets in order to be transmitted later. Queue full threshold Queue empty threshold Marking probability freeze time Marking probability increment (d1) Marking probability decrement (d2) This determines the minimum interval time (in milliseconds) between two successive updates of marking probability. The shaping burst of yellow packets expressed as a multiple of 256 Bytes Queue management parameters Q-length Buffer's size in KB. To view the real-time queue. The shaping burst (in Bytes) of green packets (maximum output burst of the shaper). The shaping burst (in Bytes) of yellow packets (maximum output burst of the shaper). If this parameter is set to 0. 126 . The marking probability is decremented by this value if the link is idle. See Setting the PCP-to-Queue Map. the BLUE algorithm is disabled. Go to Traffic > Shaping > Traffic shaper configuration. Viewing the Real-time Queue PCP Lists The real-time queue is used to bypass the traffic shaper.

Note: For each column in the table. For more information on specific parameters. To view a summary of statistics for all shapers. refer to the table below. Viewing Traffic Shaping Statistics You can view a summary of traffic shaping statistics or details for each shaper. Current queue level occupation in KB. BLUE Queue Statistics (Traffic > Shaping > Traffic shaper menu > BLUE statistics) Parameter Shaper Drop color Pm steps Pm value Queue level Queue usage Description The shaper's name associated with this queue. of traffic sent to the network port from the specified source. This is equal to the number of Pm steps multiplied by 0. loopback and traffic generator towards the network port. Marking probability value. which you have configured. 127 . The average CIR and EIR bit rates (in Mbps). 2.0096. For more information on specific parameters. Bit rate. Total number of bytes sent to the network port from the specified source.2. For more information on specific parameters. Color of the dropped traffic. For more information on specific parameters. are also shown. bytes and the bit rate (in Mbps) are displayed. refer to the table below. Current marking probability steps. Percent of queue usage. Network Port Statistics (Traffic > Shaping > Traffic shaper menu > Statistics) Parameter Packets Bytes Rate Description Total number of packets sent to the network port from the specified source. 1. To view the detailed shaper statistics. Go to Traffic > Shaping > Traffic shaper menu > BLUE statistics to show the instantaneous statistics of the queue management algorithm (BLUE). go to Traffic > Shaping > Traffic shaper statistics. refer to the following table. Click the real-time traffic shaper Name to view its PCP lists. the number of packets. select a shaper Name. refer to the table below. Viewing General Traffic Shaping Statistics Go to Traffic > Shaping > Traffic shaper menu > Statistics to show the statistics of the traffic originating from the CPU. in Mbps.

this is the instantaneous rate (in Mbps) of yellow packets. all PCPs are green. Total number of packets/bytes and rate (in Mbps) forwarded by this shaper without any delay. The rate (in Mbps) of dropped yellow packets. Total number of delayed (enqueued) packets/bytes and rate (in Mbps) forwarded by this shaper instance. Description The name assigned to this shaper. By default. this is the total number of packets/bytes and rate forwarded by this shaper using the CIR bucket. expressed (in Mbps). In the summary page. Note that the Cfg value is the CIR you have configured. The total number of green packets/bytes and rate (in Mbps) forwarded by this shaper. EIR In the summary page. Total number of packets/bytes and rate (in Mbps) dropped by the queue management algorithm (BLUE). Total number of packets/bytes and rate (in Mbps) dropped due to the shaper's queue overflow.Traffic Shaper Statistics (Traffic > Shaping > Traffic shaper statistics) Parameter Name Drop green Drop yellow PCP statistics PCPPrecolor Forward no delay Forward with delay Drop queue overflow Drop queue management (BLUE) The list of all PCPs and their pre-colors (yellow or green) that are currently mapped to this shaper. 128 . Note that the Cfg value is the EIR you have configured (in Mbps). In the detailed page. For the real-time shaper. this is the instantaneous rate (in Mbps) of green packets. Total bandwidth Total yellow Total green CIR The total number of yellow packets/bytes and rate (in Mbps) forwarded by this shaper. this value is only shown when the port's global CIR is enabled. this is the total number of packets/bytes and rate forwarded by this shaper using the EIR bucket. Using Layer-2 Protocol Tunnelling You can use the Layer-2 Protocol Tunnelling function to allow the client‘s layer-2 control protocol (L2CP) frames to be transparently transported (or to perform other actions such as drop traffic and forward traffic) across an EVC without interfering with the carrier/operator network and equipment. The rate (in Mbps) of dropped green packets. In the detailed page. This value is not available for the real-time shaper.

tags are unconditionally pushed to processed frames. the frame is processed according to the mode of operation (Drop. Forwarding.  Pop: frames are forwarded. The replacement tag is defined by the VLAN ID. To view a list of all existing L2PT rules go to Traffic > L2PT > Configuration. When the unit is in forwarding mode. 129 . refer to the following table. PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. see the figure below. VLAN tags and PCP/CFI.  Push: frames are forwarded with an extra VLAN tag added. Traffic > L2PT > Configuration To view statistics for all L2PT rules go to Traffic > L2PT > Statistics. This mode is only available when VLAN Filtering is enabled. Each incoming frame is tested against each rule in order until it finds a match. with user-configurable fields for ethertype. the protocol tunnelling operates by replacing the protocol's specific destination MAC address with a multicast address that is transparently transported by the transit equipment and reinserted in the original destination MAC when the traffic reaches the destination equipment. The Protocol Tunnelling function works with rules to filter traffic being processed. For an example of the display. If there is no match with any rule. For more information on specific parameters. with the VLAN tag stripped. as tags cannot be replaced in non-tagged frames. refer to the table L2PT Configuration (Traffic > L2PT > Configuration).For example. When there is a match. The tag is defined by the VLAN ID. as tags cannot be removed from non-tagged frames. you can set it to perform VLAN tagging on the processed frames. Tunnelling or Peering). the frame is discarded. This mode is only available when VLAN Filtering is enabled. PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. In forwarding mode.  Replace: frames are forwarded with their VLAN tag replaced. the following operations are supported:  None: frames are forwarded unmodified. In tunnelling mode. For more information on specific parameters.

proceed as follows: 1. also check Enable VLAN Filtering to enable the filtering of incoming frames with matching VLAN ID and Ethertype. Click the Add button to add a new L2PT rule or click the rule name of an existing rule to edit its settings. this counter is incremented for each frame transmitted on the outgoing port. This counter is incremented under the following circumstance: The rule is set for forward operation and a matching frame was received on the incoming port and forwarded. This counter is incremented under the following circumstance: The rule is set for tunnel operation mode and a matching frame was received on the incoming port and tunnelled (had its destination MAC replaced. This counter is incremented under the following circumstance: The rule is set for tunnel operation and a matching frame was received on the outgoing port and de-tunnelled (restored to its original state and sent to the incoming port). but there was a VLAN ID mismatch. Note that if there are multiple VLAN groups in the VLAN list. Go to Traffic > L2PT > Configuration. To add or edit a L2PT rule. Peered Total number of frames peered by this rule since its creation.Layer-2 Protocol Tunnelling Frame Statistics (Traffic > L2PT > Statistics) Parameter Name Dropped Description Unique name assigned to the rule. Check Enable L2PT rule to enable the processing of the Layer-2 Control Protocols according to L2PT rules. Tunnelled Total number of tunnelled frames by this rule since its creation. refer to L2PT Configuration. to the outgoing port. unmodified. 2. De-tunnelled Total number of de-tunnelled frames by this rule since its creation. Setting up an L2 Tunnel You can define up to 64 L2PT rules. Total number of dropped frames by this rule since its creation. Forwarded Total number of frames forwarded by this rule since its creation. i. had the required VLAN tags added and was sent to the outgoing port). This counter is incremented under the following circumstance: The rule is set for peer operation and a matching frame was received on the incoming port and sent to the software layers for further processing. 3. The rule is set for tunnel operation mode and a matching frame was received. For more information on specific parameters. 130 . If needed. This counter is incremented under the following circumstances: The rule is set for drop operation mode and a matching frame was received.e. the VLAN tags in the frame could not be matched to any of the VLAN groups in the rule's list.

The following replacement MAC can be used: The Cisco replacement: 01:00:0C:CD:CD:D0 MAC is used. Catchall rules operate on all frames that were not matched by a specific rule and can be set for forward or drop operation modes. The multicast MAC address to use as a replacement when protocol tunnelling is performed. The Accedian replacement: 01:15:AD:CC:xx:yy MAC is used. Operation mode may be one of the following: Drop: frames matching the specific rule are dropped. When creating a tunnel between two units. L2PT Configuration (Traffic > L2PT > Configuration) Parameter Enable L2PT Description The state of the L2CP processing. Tunnel: frames matching the specific rule get their destination MAC address replaced by the MAC specified in the rule's parameters when received on the specified client port. Fill up the required field and click Apply. it can be used on multiple rules as the variable elements allow a match to a specific rule when a tunnelled frame is received on the network port. Optionally. Name L2PT rule name State Enable L2PT rule Protocol Mode Operation mode The state of the rule. the Layer-2 Control Protocols are handled by the traffic policies. Because this replacement MAC has variable elements. These variable elements are set as follows: xx: the unique ID specified in the configuration (see Unique ID). For more information on specific parameters. Layer-2 Control Protocol to be processed by a specific rule. This controls how the rule handles the traffic associated with the specified protocol. When disabled. the unique ID is used to match the 131 . Allows the unit to process of the L2CP according to L2PT rules. it can be used only once amongst all rules. Because it cannot be altered.4. The name assigned to the rule. Forward: frames are sent unaltered from the incoming to the outgoing port. Type Catchall rule Replacement MAC Normal or catchall rule. Frames matching the specific rule get their original destination MAC address put back when received on the specified network port. refer to L2PT Configuration. Allows a rule to be enabled or disabled without being deleted. EVC mapping can be enabled on forwarding rules (see EVC Mapping). Peer: the frames are sent to software layers for further processing.

The choices are: 0–7: for a specific priority All: to accept any PCP CFI The Canonical Format Indicator that this rule accepts in the inbound Layer-2 Control Protocol frames. This allows the outgoing port used by the rule to be selected. As such. The VLAN IDs that this specific rule accepts in the inbound Layer-2 Control Protocol frames. PCP. Push: frames are forwarded with an extra VLAN tag added. The outgoing port is considered to be the port where the tunnelled frames. To). The ethertype that this specific rule accepts in the inbound Layer-2 Control Protocol frames. the following choices are available: None: frames are forwarded unmodified. yy: the protocol ID. Only the frames with a VLAN ID and Ethertype matching the ones specified in the VLAN ID range. Incoming port Outgoing port This allows the incoming port used by the rule to be selected. it is important that the matching rules on both endpoints have the same unique ID. 0–1: for a specific priority All: to accept any CFI EVC Mapping EVC Mapping Mode In forwarding operation mode. CFI and Ethertype are accepted. Note that the same ID value has to be used on both sides when performing tunnelling between a pair of units. This is automatically generated according to which Layer-2 control protocol the rule handles. PCP and CFI fields and the Ethernet type is set to 132 . The incoming port is considered to be the port where the layer-2 control protocols will be received. will be transmitted. enter the same value in both fields (From. The Priority Code Point that this rule accepts in the inbound Layer-2 Control Protocol frames. If filtering on a single VID is desired. The ID of a rule used when performing tunnelling. containing a replacement destination MAC.Parameter Description replacement frames going both ways on the network port. This tag is defined by the VLAN ID. Unique ID VLAN Filtering VLAN filtering Enable Ethertype VID range VLAN ID range PCP Status of the VLAN filtering for this L2PT rule. This value is used when building the replacement destination MAC address if the Accedian multicast address is used.

VLAN ethertype VLAN1 ethertype VLAN2 ethertype VLAN ID VLAN list The ethertype of the tag inserted in the forwarded frame. as tunnelling untagged frames is currently not supported. The ethertype of the first tag inserted in the tunnelled frame. as tags cannot be removed from non-tagged frames. This is available only in Tunnelling mode. This mode is only available when VLAN Filtering is enabled. CoS mapping PCP The Priority Code Point mapped to the processed frame in CoS Map mode. and double-tag frames with VLAN IDs 5–6 and 22–88. Map is available when the forwarding mode is either PUSH or REPLACE. For example. The VLAN tags to insert in the tunnelled frames. Preserve: The PCP and CFI fields of the processed frame are copied from the ones in the incoming frame. if you wanted to single-tag tunnelled frames with VLAN ID 3. The VLAN ID field is available only in Forwarding mode. and is mandatory in tunnelling mode. This is available only in Tunnelling mode. PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. Range: 0–7. In the example above. The VLAN list is available only in Tunnelling mode. This mode is only available when VLAN Filtering is enabled. Replace: frames are forwarded with their VLAN tag replaced.Parameter Description the value specified by the VLAN ethertype field. Entry of the second tag (Q-in-Q) is optional. as tags cannot be replaced in non-tagged frames. The ethertype of the second tag inserted in the tunnelled frame (for Q-in-Q). The format is a list of commaseparated groups formatted as vlan1:vlan2. This mode is only available when the forwarding mode is REPLACE. you would specify: 3. three frames would be transmitted on the network port for each incoming frame matching the rule on the client port. The replacement tag is defined by the VLAN ID. The VLAN tags to insert in the forwarded frames. Note also that there should be at least one entry in the list. Pop: frames are forwarded with the VLAN tag stripped. CoS Mapping Mode This allows you to control the PCP and CFI fields of the forwarding and tunnelling rules The following operations are supported: Map: The PCP and CFI fields of the processed frame are replaced by the ones specified in the PCP and CFI fields. Note that the frames are duplicated for each entry in the VLAN list. This is available only in Forwarding mode. 22:88. 5:6. 133 .

134 .Parameter Cos mapping CFI Description The Canonical Format Indicator mapped to the processed frame in CoS Map mode. The CFI is defined by 1 bit in the Ethernet frame.

Setting up an OAM Instance Before using Ethernet OAM functions or enabling a loopback. Go to OAM > Configuration. Note that this field does not indicate a successful discovery of an OAM peer. Description The OAM instance name. Check the appropriate check box to enable this field. OAM Instances (OAM > Configuration) Parameter Name OAM instance name OAM state Enable OAM protocol Enables the passive or active OAM 802. refer to the table at the end of this procedure. Click the Add button to add a new OAM instance or click the name of an existing OAM instance to edit its settings. 3.3ah protocol for this OAM instance. For more information on specific parameters. you must create an OAM instance. These monitoring techniques are presented in the following sections:  Using Ethernet OAM  Using the Performance Assurance Agent™  Using Service OAM Using Ethernet OAM Ethernet OAM allows you to monitor network performance. 135 . proceed as follows: 1. upon which the loopback is created. 2.Monitoring Network Performance The unit allows for monitoring network performance using a proprietary technology and two standard protocols. An active instance immediately starts sending information OAMPDUs associated with the discovery process. For more information on specific parameters. To set up an OAM instance. This displays a summary of all OAM instances set up. fill in the required fields and click Apply. refer to the following table.

Active: Immediately searches for an OAM peer by sending OAMPDUs. etc. This can be caused by various types of errors including. means that this event is generated based on the ratio of bad frames versus good frames. The window setting defines the number of frames that make up a period. long frames. but not limited to the following: CRC errors. This enables you to limit the impact of the extra OAM traffic on a link that is already heavily loaded. When Enabled. long frames. A frame error is an error detected at the layer 2. Indicates whether OAM packets are tagged with a VLAN. For encapsulated packets only Maximum frame size for the OAM instance. When Enabled. The threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. This can be caused by various types of errors including. Using a number of frames instead of a time period. the unit responds to OAMPDUs requests. Port used by this OAM instance. Errored Frame Period Event (EFPE) Threshold and window 136 . The window setting defines the time (in seconds) of the period. as in EFE. etc. or MAC. The threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. When Enabled. the unit issues event OAMPDUs when needed. This setting is valid only if This unit supports events is enabled. or MAC level.Parameter OAM mode Active Mode / Passive Mode Port name Port Encapsulation VLAN ID Max OAM PDU size This unit supports loopback This unit supports events This unit supports variable responses Number of Events retransmitted Errored Frame Event (EFE) Threshold and window Description Passive: Listens for OAMPDUs and replies once it starts receiving them. the unit responds to loopback requests from the OAM peer. short frames. Number of times an event is re-transmitted to ensure its reception by the peer. A frame error is an error detected at the layer 2. level. short frames. but not limited to the following: CRC errors.

refer to the table below. The window setting defines the time. EFPE or EFSSE fieds Received event notifications 137 . of the period. The number of received OAM events that were duplicated. Shows details of the transmitted event notification:  Event number  Transmit time  Sequence number  Event type Shows details of the received event notification:  Event number  Receive time  Sequence number  Event type: EFE. For more information on specific parameters. but not limited to the following: CRC errors. For complete details on transmitted and received events. level. or MAC. Viewing OAM Events To view a summary of all event exchanges on an OAM connection. OAM Events (OAM > Events) Parameter Name Txm event Txm duplicate Rcv event Rcv duplicate Transmitted event notifications Description The name of the OAM instance The number of OAM events transmitted.Parameter Errored Frame Seconds Summary Event (EFSSE) Threshold and window Description The threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. click the OAM instance Name in the list. This can be caused by various types of errors including. The number of OAM events received. go to OAM > Events. A frame error is an error detected at the layer 2. EFSSE  Event values: EFE. An errored frame second is a one-second period in which at least one frame was bad. in seconds. long frames. EFPE. The number of transmitted OAM events that were duplicated. short frames. For more information on specific parameters. etc. In other words. this event is generated when the number of seconds with any number of bad frames is greater than or equal to the threshold during a period defined by the window. refer to the table below.

refer to the table below.  The second bit corresponds to the Dying Gasp bit in the Flags field. You can also refer to IEEE802.  The fifth bit corresponds to the Local Stable bit in the Flags field. etc. The third bit corresponds to the Multiplexer Action bit in the State field. The seven LSB bits are expressed as a hexadecimal value. OAM Status (OAM > Status) Parameter Name Discovery Description The name of the OAM instance The current state of the OAM Discovery function. For more information on specific parameters. This value is updated upon reception of a valid frame Local revision Info TLV revision Parser state / Mux state Vendor specific info 138 . third bit = 1. For more information on specific parameters.  The third bit corresponds to the Critical Event bit in the Flags field. refer to the table below.Viewing OAM Status To view a summary of the status of each OAM instance. a hex value of 0x0004 converted to binary is 0000100: first bit = 0.  LINK_FAULT  ACTIVE_SEND_LOCAL  PASSIVE_WAIT  SEND_LOCAL_REMOTE  SEND_LOCAL_REMOTE_OK  SEND_ANY Local Local flags Flags A string of seven bits corresponding to the Flags field in the most recently transmitted OAMPDU. click the OAM instance Name in the list. The value of the Revision field in the Local Information TLV of the most recently transmitted information OAMPDU.3ah. For example. The states listed correspond to those within the discovery state diagram (see Figure 57-5 of IEEE802. go to OAM > Status. second bit = 0. Note that the revision number indicates the number of times that the configuration for the local OAM instance has been modified.  The seventh bit corresponds to the Remote Stable bit in the Flags field. Note that these states will change when a loopback is enabled. The first and second bits correspond to the Parser Action bits in the State field.  The fourth bit corresponds to the Local Evaluating bit in the Flags field.  The sixth bit corresponds to the Remote Evaluating bit in the Flags field.  The first bit corresponds to the Link Fault bit in the Flags field. This value is updated upon reception of a valid frame. The value of the Vendor Specific Information field of the most recently received information OAMPDU. A string of three bits corresponding to the State field of the most recently transmitted Information OAMPDU.3). For details OAM status information. Vendor OUI The value of the OUI variable in the Vendor Identifier field of the most recently transmitted information OAMPDU.

For detailed OAM statistics.  The second bit corresponds to the Dying Gasp bit in the Flags field. 139 . etc.Parameter Description with the following:  Destination Field equal to the reserved multicast address for Slow_Protocols  Length or Type field value equal to the reserved Type for Slow_Protocols  A Slow_Protocols subtype value equal to the subtype reserved for OAM  The OAMPDU code equal to the Information code  The frame contains a Local Information TLV Remote Remote flags Flags A string of seven bits corresponding to the Flags field in the most recently received OAMPDU.  The fourth bit corresponds to the Local Evaluating bit in the Flags field.  The third bit corresponds to the Critical Event bit in the Flags field. Remote revision Info TLV revision Parser state / Mux state A string of three bits corresponding to the State field of the most recently received information OAMPDU. The value of the Vendor Specific Information field of the most recently received information OAMPDU. For more information on specific parameters.  The first bit corresponds to the Link Fault bit in the Flags field. The first and second bits correspond to the Parser Action bits in the State field.  The sixth bit corresponds to the Remote Evaluating bit in the Flags field. This value is updated upon reception of a valid frame. Viewing OAM Statistics To view a summary of the statistics of each OAM instance. refer to the table below. second bit = 0. click the OAM instance Name in the list.  The seventh bit corresponds to the Remote Stable bit in the Flags field. For example. Vendor OUI Vendor specific info The value of the OUI variable in the Vendor Identifier field of the most recently received information OAMPDU. Note that these states will change when a loopback is enabled.  The fifth bit corresponds to the Local Stable bit in the Flags field. The seven LSB bits are expressed as a hexadecimal value. a hex value of 0x0004 converted to binary is 0000100: first bit = 0. The third bit corresponds to the Multiplexer Action bit in the State field. go to OAM > Statistics. For more information on specific parameters. The value of the Revision field in the Local Information TLV of the most recently received information OAMPDU. refer to the table below. third bit = 1.

var response.  The Sequence Number is equal to the Sequence Number of the last received Event Notification OAMPDU. This counter is incremented upon reception of a valid frame with the following:  Destination Field equal to the reserved multicast address for slow protocols.  Length Or Type value equal to the reserved Type for slow protocols. This counter is incremented upon reception of a valid frame with the following:  Destination Field equal to the reserved multicast address for slow protocols. Includes all types: info. Number of Info OAMPDUs received by this instance. This counter is incremented upon reception of a valid frame with the following:  Destination Field equal to the reserved multicast address for slow protocols.  A slow protocols subtype equal to the subtype reserved for OAM.  The OAMPDU code equals the Event Notification code. Unique event A count of the OAMPDUs received that contain the Event Notification code. Number of OAMPDUs received by this instance. var request.  LengthOrType value equal to the reserved Type for slow protocols. Number of Info OAMPDUs transmitted by this instance. Includes all types: info. Generalized non-resettable counter.OAM Statistics (OAM > Statistics) Parameter Name Rcv OAMPDU Txm OAMPDU Rcv Info OAMPDUs Txm Info OAMPDUs Receive Unsupported codes A count of OAMPDUs received that contain an OAM code that is not supported by the device. Generalized non-resettable counter. Number of OAMPDUs transmitted by this instance. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  A slow protocols subtype equal to the subtype reserved for OAM. Information A count of OAMPDUs received that contain the OAM Information code. loopback etc.  A slow protocols subtype equal to the subtype reserved for OAM. Description The name of the OAM instance. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. Generalized non-resettable counter. var request.  An OAMPDU code for a function that is not supported by the device.  The OAMPDU code equals the OAM Information code and is supported by the device. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. var response.  Length Or Type value equal to the reserved Type for slow protocols. 140 . loopback etc.

This counter is incremented upon reception of a valid frame with the following:  DestinationField equal to the reserved multicast address for slow protocols. This counter is incremented upon reception of a valid frame with the following:  DestinationField equal to the reserved multicast address for slow protocols. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. Generalized non-resettable counter.  LengthOrType value equal to the reserved Type for slow protocols. with: 141 .  A slow protocols subtype equal to the subtype reserved for OAM. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  A slow protocols subtype equal to the subtype reserved for OAM.  LengthOrType value equal to the reserved Type for slow protocols. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.Parameter Duplicate event Description A count of the OAMPDUs received that contain the Event Notification code. This counter is incremented upon reception of a valid frame with the following:  DestinationField equal to the reserved multicast address for slow protocols.  A slow protocols subtype equal to the subtype reserved for OAM. Generalized non-resettable counter.  The OAMPDU code equals the Loopback Control code and is supported by the device.  LengthOrType value equal to the reserved Type for slow protocols.  A slow protocols subtype equal to the subtype reserved for OAM. Variable request A count of OAMPDUs received that contain the Variable Request code.  The OAMPDU code equals the Event Notification code.  LengthOrType value equal to the reserved Type for slow protocols. Generalized non-resettable counter. Variable response A count of OAMPDUs received that contain the Variable Response code. Loopback control A count of OAMPDUs received that contain the Loopback Control code. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  The Sequence Number is equal to the Sequence Number of the last received Event Notification OAMPDU.  The OAMPDU code equals the Variable Request code and is supported by the device.  The OAMPDU code equals the Variable Response code and is supported by the device. Organization specific A count of OAMPDUs received that contain the Organization Specific code. This counter is incremented upon reception of a valid frame. Generalized non-resettable counter. This counter is incremented upon reception of a valid frame with the following:  DestinationField equal to the reserved multicast address for slow protocols.

This counter has a maximum increment 142 . Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  A slow protocols subtype equal to the subtype reserved for OAM. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. This counter is incremented when a request service primitive is generated within the OAM sublayer. Generalized non-resettable counter. Transmit Unsupported codes A count of transmitted OAMPDUs that have unsupported codes. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code for a function that is not supported by the device.  The Sequence Number is not equal to the Sequence Number of the last transmitted Event Notification OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  The OAMPDU code equals the Event Notification code. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAMPDU code indicating an Information OAMPDU. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.  The Sequence Number is equal to the Sequence Number of the last transmitted Event Notification OAMPDU. Generalized non-resettable counter. Loopback control A count of transmitted OAMPDUs containing the Loopback Control code. This counter is incremented when a request service primitive is generated within the OAM sublayer.  The OAMPDU code equals the Organization Specific code and is supported by the device. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. Duplicate event A count of transmitted OAMPDUs containing the OAM Event Notification code. Generalized non-resettable counter.Parameter Description  DestinationField equal to the reserved multicast address for slow protocols. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Loopback Control OAMPDU.  A Slow_Protocols subtype equal to the subtype reserved for OAM. Generalized non-resettable counter. Information A count of transmitted OAMPDUs containing the OAM Information code.  The OAMPDU code equals the Event Notification code.  LengthOrType value equal to the reserved Type for slow protocols. Unique event A count of transmitted OAMPDUs containing the OAM Event Notification code.

packet loss and continuity check. Generalized non-resettable counter. Generalized non-resettable counter. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Response OAMPDU. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating an Organization Specific OAMPDU.Parameter Description rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. These packets may be independently destined to different peers or to the same peer. Using the Performance Assurance Agent™ The Performance Assurance Agent™ (PAA™) is a hardware assisted active measurement function that computes layer 2 or 3 (IPv4 UDP) network delay (latency). A count of transmitted OAMPDUs containing the Variable Request code. A measurement sample is a packet containing timing and sequence information. delay variation (jitter). This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Request OAMPDU. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. measurements (delay. The PAA™ operates continuously. Two units with matching settings communicate with each other using measurement samples to collect data and measure system performance. using a different class of service (CoS) and/or VLAN ID as appropriate. Variable request Variable response A count of transmitted OAMPDUs containing the Variable Response code. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. Up to 2 VLAN tags can be specified (.1Q). The PAA™ is capable of concurrently testing and maintaining multiple flows of active probes. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period.1Q-in. Organization specific A count of transmitted OAMPDUs containing the Organization Specific code. 143 . The characteristics of the test packets for each flow are set to match the layer 2 (P-bit of VLAN tag) or layer 3 (IP ToS/DSCP value) characteristics of the services being monitored. When such a packet arrives at its destination. Generalized non-resettable counter. delay variation and packet loss) can be taken.

PAA Configuration (PAA > Configuration) Parameter General Index Name Type Unique identifier assigned to the probe. For more information on specific parameters. refer to the following table. Description 144 . This displays a summary of all PAA probes. Ethernet) or the four CRC bytes. 3. Specifies whether a probe generates (Source) PAA samples or collects them (Sink) or does both (Bi-Dir). The size does not include protocol headers (VLAN tags. Click Add to create a new probe or click the probe name to edit an existing probe. Note: The fields available for configuration vary depending on the probe type and operation mode you select. Type of probe: Layer-2: The probe operates at layer-2 UDP: The probe operates using UDP Operation mode Mode Packet size Size of PAA samples. refer to the table at the end of this procedure. Fill in the required fields and click Apply. Go to PAA > Configuration. For more information on specific parameters. 2.Setting up a Probe Adding/Modifying a Probe 1. IP. Minimum value: 61 Layer-2 maximum value: 1500 UDP maximum value: 1472 Sampling period Sampling Enable PAA probe State PAA probe may be enabled or disabled. UDP. Time between issues of PAA samples. The probe's current state: Enabled: Enabled by configuration. Name of the PAA probe.

That port should also be set up to perform EVC fault propagation for this parameter to take effect. Encapsulate layer-2 PAA packets into a VLANinVLAN. Second VLAN Ethertype: C-VLAN or S-VLAN. First VLAN Ethertype: C-VLAN or S-VLAN. layer-2 PAA packets are encapsulated into a second VLAN. layer-2 peer address automatically finds the peer MAC address. Remote peer identifier. EVC client port to which the MEP status should be propagated. First VLAN ID. Applies only when VLAN 1 ID is enabled. the remote peer identifier is discovered dynamically based on the probe name in the association phase. omitting the local identifier or specifying 0 means to allocate any free local identifier. layer-2 PAA packets are encapsulated into the specified VLAN ID. Second VLAN priority bits. Second VLAN ID. Local and Peer Indexes Local Index Remote Index Local identifier for the probe. VLAN 1 Priority VLAN 2 Priority EVC fault propagation (for Layer-2 probe only) Enable fault propagation Propagate on port Use this PAA probe's status in fault propagation. Associated: Enabled peer index resolved. First VLAN priority bits. Applies only when VLAN 2 ID is enabled. Layer-2 Parameters (for Layer-2 probe only) Destination MAC address Destination Port name VLAN 1 encapsulation VLAN 2 encapsulation VLAN 1 ID VLAN 2 ID VLAN 1 type VLAN 2 type Outgoing port used by this probe. UDP parameters (for UDP probe only) Destination IP address Peer IPV4 Destination address. Applies only when VLAN 1 ID is enabled. VLAN2 represents the outer VLAN. The port configuration Fault propagation must be enabled and set to One-way EVC mode to propagate the fault to the opposite port. 145 . Associating: Enabled and looking for peer. Applies only when VLAN 1 ID is enabled. Applies only when VLAN 2 is enabled. When enabled.Parameter Description Disabled: Disabled by configuration. When 0 is specified. When enabled. When set to FF:FF:FF:FF:FF:FF. Encapsulate layer-2 PAA packets into a VLAN. When you add a PAA instance. Peer MAC address.

. It is used in conjunction with the Delay variation threshold (sample) to trigger the alarm PAA_OW_DV_ALERT. This value needs to be at least 10 times the value of the Sampling period. One-way delay allowed for each sample in the Reference period. 146 . Range: 0-3 First VLAN priority bits. For example. Exceeding the threshold triggers the alarm PAA_OW_AVG_DELAY_ALERT. The ECN bits are the last two bits of the IP ToS field. the average is calculated from samples taken during the last 10 ms. simulating ECN in the customer network. Number of consecutive samples exceeding the Maximum delay variation that Reference period (in ms) for the continuity measurements. Number of consecutive samples exceeding the Maximum delay that are allowed before declaring the one-way delay alarm for this Reference period. Maximum one-way delay variation threshold to monitor during a test period. Default is 8793. DSCP class selector.Parameter Destination Source UDP port Destination UDP port Diff-Serv Codepoint (DSCP) Explicit Congestion Notification (ECN) VLAN 1 Priority Description Source UDP port. Number of consecutive sampling periods without receipt of peer samples before declaring a Continuity loss alarm. Default is 8793. Threshold (in %) at which an Excessive packet loss (EPL) alarm is declared. Range: 0-7 Continuity Packet loss reference period Packet loss threshold Continuity check threshold One-way Reference period Maximum delay Delay threshold (sample) Average delay threshold Maximum delay variation Delay Reference period (in ms) for the one-way measurements. Destination UDP port. This value needs to be at least 10 times the value of the Sampling period. It is used in conjunction with the Delay threshold (sample) to trigger the alarm PAA_OW_DELAY_ALERT. This can be used to associate a priority value for the first VLAN. Average one-way delay is calculated for the samples during the reference period. ECN value. for a reference period of 10 ms. Six (6) bits. This can be used to associate an ECN value to the PAA packets.

Exceeding the threshold triggers the alarm PAA_OW_AVG_DV_ALERT. IGMP join and leave delay measurements are performed for this period during which one-way and packet loss samples are collected. Maximum two-way delay variation threshold to monitor during a test period. Average two-way delay is calculated from samples during the reference period. This period needs to be a multiple of the One-way reference period. This value needs to be at least 10 times the value of the Sampling period. Average two-way delay variation is calculated from samples during the reference period. Possible values (in msec):  0 (default): Constant. IGMP (These parameters are valid only for a UDP sink probe configured with a multicast destination address) Reference Period (msec) The reference period for IGMP measurements. This parameter is valid only if the One-way Join Period is not 0. Average one-way delay variation is calculated for the samples during the reference period. Number of consecutive samples exceeding the Maximum delay that are allowed before declaring the two-way delay alarm for this Reference period. This value should represent how long to collect measurements before issuing an IGMP leave for each period. Reference period (in ms) for the two-way measurements. Exceeding the threshold triggers the alarm PAA_TW_AVG_DV_ALERT. It is used in conjunction with the Delay variation threshold to trigger the alarm PAA_TW_DV_ALERT. Two-way delay allowed for each sample in the Reference period. Exceeding the threshold triggers the alarm PAA_TW_AVG_DELAY_ALERT.Parameter variation threshold (sample) Average delay variation threshold Two-way Reference period Maximum delay Delay threshold Average delay threshold Maximum delay variation Delay variation threshold Average delay variation threshold Description are allowed before declaring the one-way delay variation alarm for this Reference period. no join and leave measurements  Minimum: 10 * sampling period 147 . It is used in conjunction with the Delay threshold to trigger the alarm PAA_TW_DELAY_ALERT. Possible values (in msec):  0 (default): No IGMP measurement  Minimum: One-way reference period * 10  Maximum: One-way reference period * 9000 One-way join period (msec) If not 0. Number of consecutive samples exceeding the Maximum delay variation that are allowed before declaring the two-way delay variation alarm for this Reference period.

Go to PAA > Configuration. 2. Possible values (in msec):  Minimum: 100 msec  Maximum: One-way join period The maximum consecutive join delay samples allowed greater than the maximum join delay before incrementing the Join delay Nbr threshold exceeded.Parameter Maximum join delay Description  Maximum: One-way reference period – (5 * sampling period) The maximum join delay objective. Possible values (in samples):  Minimum: 1  Maximum: (One-way reference period – One-way join period) / (Sampling period) Maximum leave delay Leave delay threshold Leave average delay threshold The maximum leave average delay. Click Delete. 148 . Possible values (in msec):  Minimum: 100 msec  Maximum: One-way join period The maximum leave delay objective. Possible values (in msec):  0 (default): No IGMP measurement  Minimum: 100 msec  Maximum: (One-way reference period) – (One-way join period) The maximum consecutive leave delay samples allowed greater than the maximum leave delay before incrementing the Leave delay Nbr threshold exceeded. Possible values (in msec):  Minimum: 100 msec  Maximum: (One-way reference period) – (One-way join period) Deleting a Probe 1. 3. Possible values (in samples):  Minimum: 1  Maximum: (One-way join period) / (Sampling period) Join delay threshold Join average delay threshold The maximum join average delay. Click the probe name to delete.

Associating: Enabled and looking for peer. The probe's current state. For more information on specific parameters.Viewing Probe Status 1. refer to the following table. Possible values are: Disabled: Disabled by configuration. Click a probe name to view its detailed information. PAA Status (PAA > Status) Parameter Name Probe name Index State The unique identifier assigned to the probe. For more information on specific parameters. 149 . Peer address Status codes The address of its peer PAA probe (L2 and L3). The current state (active or inactive) for all PAA alarms for the following status code: CC: Continuity Check EPL: Excessive Packet Loss OD: One-way Delay OAD: One-way Average Delay ODV: One-way Delay Variation OAV: One-way Average Delay Variation TD: Two-way Delay TAD: Two-way Average Delay TDV: Two-way Delay Variation TAV: Two-way Average Delay Variation Description The name of the probe. go to PAA > Status. It also gives detailed state information about local and remote clock synchronization status that is used for one-way measurements. refer to the table PAA Status (PAA > Status). Associated: Enabled peer index resolved. 2. To view the status of all PAA probes.

The probe's current state. For more information on specific parameters. 150 . Possible values are: Disabled: Disabled by configuration. Associated: Enabled peer index resolved. A summary of the results for the following parameters: PL : Packet Loss ratio OAD : One-way Average Delay OADV : One-way Average Delay Variation TAD : Two-way Average Delay TADV : Two-way Average Delay Variation Packet loss Period Gives the results for the previous and current periods. Description The name of the probe. refer to the table below.Viewing Probe Results 1. Largest number of consecutive frames that are missing. Number of gaps registered in the period. Percentage of samples lost in the period. Click a probe name to view detailed results of a probe. The current period is indicated on the right of Packet loss. It also gives detailed state information about local and remote clock synchronization status that is used for one-way measurements Period Results Codes Number of periods elapsed since the probe was enabled. To view a summary of all PAA probe results. Number of samples Loss ratio Number of gaps Largest gap size One-way delay Total number of samples in the period. PAA Results (PAA > Results) Parameter Current results for probe Probe name Index State The unique identifier assigned to the probe. Associating: Enabled and looking for peer. go to PAA > Results. 2.

Nbr samples Minimum delay Maximum delay Average Total number of samples in the period. One-way delay (in microseconds) of the fastest sample over the period. This is the latest one-way delay variation measured when the window was last refreshed Gives the results for the previous and current periods. Gives the results for the previous and current periods. Average one-way delay variation (in microseconds) of the samples during the reference period. Number of times the one-way delay exceeded the value of the parameter Maximum delay. This is the latest oneway delay value measured when the window was last refreshed. The current period is indicated on the right of Two-way delay. One-way delay variation (in microseconds) of the samples with the smallest delay skew over the period.Parameter Instantaneous delay Period Description One-way instantaneous delay value (in microseconds). This is the latest two-way delay measured when the window was last refreshed. One-way delay variation Instantaneous DV Period One-way instantaneous delay variation value (in microseconds). Number of times the one-way delay variation exceeded the value of the parameter Maximum DV. One-way delay (in microseconds) of the samples with the highest delay skew over the period. Average two-way delay (in microseconds) of the samples during the reference Total number of samples in the period. Average delay (in microseconds) of the samples during the reference period. The current period is indicated on the right of One-way delay. One-way delay (in microseconds) of the slowest sample over the period. Two-way delay (in microseconds) of the slowest samples over the period. Gives the results for the previous and current periods. The current period is indicated on the right of One-way delay variation. Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded Total number of samples in the period. Two-way delay (in microseconds) of the fastest samples over the period. 151 . Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded Two-way delay Instantaneous delay Period Two-way instantaneous delay (in microseconds).

IGMP Leave delay Instantaneous delay Period The latest IGMP leave delay measured (in microseconds). Two-way delay variation Instantaneous DV Period Two-way instantaneous delay variation (in microseconds). IGMP join delay (in microseconds) of the fastest sample over the period. IGMP join delay (in microseconds) of the slowest sample over the period. Gives the results for the previous and current periods. Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded Total number of samples in the period.Parameter delay Nbr threshold exceeded Description period. Average delay (in microseconds) over the period. IGMP leave delay (in microseconds) of the fastest sample over the period. Number of times the two-way delay exceeded the value of the parameter Maximum delay. The current period is on the right of IGMP Leave delay. The current period is to the right of IGMP Join delay. Number of times the IGMP join delay exceeded the value of Maximum Join delay. Gives the results for the previous and current periods. Total number of samples in the period. Gives the results for the previous and current periods. Average Two-way delay variation (in microseconds) of the samples during the reference period. Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded IGMP Join delay Instantaneous delay Period The latest IGMP join delay value (in microseconds). measured when the window was last refreshed. Two-way delay (in microseconds) of the samples with the highest delay skew over the period. Nbr samples Minimum Total number of samples in the period. 152 . The current period is indicated on the right of Two-way delay variation. Two-way delay variation (in microseconds) of the samples with the smallest delay skew over the period. measured when the window was last refreshed. Number of times the two-way delay variation exceeded the value of the parameter Maximum DV.

Number of times the IGMP leave delay exceeded the value of Maximum Leave delay. refer to the following table. If required. Using Service OAM This section describes the IEEE 802. Average delay (in microseconds) over the period.Parameter delay Maximum delay Average delay Nbr threshold exceeded Description IGMP leave delay (in microseconds) of the slowest sample over the period. See Setting up Delay Measurement and Setting up Packet Loss Measurement. CFM Stack (CFM > Stack) Parameter Port VID Level Description The port on which MEPs are set up. Possible values: 0-7. The steps required to set up Connectivity Fault Management (CFM) are:  Setting up Maintenance Domains (MD)  Setting up Maintenance Associations (Maintenance Entity Groups  Setting up Maintenance Endpoints  Setting up Link Trace Messages if required  Setting up Loopback Messages if required For viewing MEP information. For more information on specific parameters. you can set up CFM defaults. See Setting up CFM Defaults. 153 . see also Viewing MEP Status. The VLAN ID to which the Maintenance Point is attached. You can also set up delay measurements and packet loss measurements. or 0.1ag ―Service OAM‖ function and how to set it up in your Metro Ethernet Network to perform end-to-end monitoring. MD level (or MEG level) of the Maintenance Point. if none. Setting up CFM Viewing CFM Instances Go to CFM > Stack to view a list of all CFM instances and their settings. Viewing MEP Database and Viewing MEP Statistics.

The MEPID of the MEP.Parameter Dir MD idx MA idx MEPID MAC address Description The direction in which the MEP faces on the port. The index of the MA (or MEG) with which the MP is associated. 154 . The MAC address of the Maintenance Point. The index of the Maintenance Domain with which the MEP is associated.

1731 with the CFM MIB which requires MDs. Manage: Management Address. refer to the table at the end of this procedure. For more information on specific parameters. refer to the following table. The choices are: Character string: RFC2579 DisplayString. 3.1731 level 7.Setting up Maintenance Domains (MD) There are eight pseudo MDs defined by default. The name format must be the same for the other end points. named Y.1731 CCM's MEG-ID. To set up a Maintenance Domain. if anything. User interfaces show the pseudo MD name. It is not possible to delete pseudo MDs. The valid values are: None: None. is to be included in the Sender ID TLV transmitted in CCMs. but this name is not included in Y. DNS like name: Domain Name like string. Chassis and manage: Chassis ID. Possible values: 0-7 Sender ID permission What. Fill in the required fields and click Apply. Go to CFM > MD. LTMs and LTRs. LBMs. proceed as follows: 1.1731 uses MEG-IDs which are MAIDs without an MD name.1731 level 0 to Y. except that the character codes 0–31 (decimal) are not used. Name MD name Level Maintenance Level of the Maintenance Domain. Maintenance Domain (CFM > MD) Parameter Index Name format Description Unique index assigned to the Maintenance Domain. These MDs exist only to simplify the integration of MEGs for Y. Unique name for the Maintenance Domain. 155 . Click the Add button to add a new Maintenance Domain or click the name of an existing Maintenance Domain to edit its settings. Y. one for each level. This displays all existing Maintenance Domains. Chassis: Chassis ID and chassis subtype. Maintenance Domain name format. 2. subtype and Mgmt Address. For more information on specific parameters. globally unique text string derived from a DNS name.

refer to the following table.1731). ICC-Based: ITU Carrier Code format (Y. Maintenance association or MEG name format. proceed as follows: 1. Fill in the required fields and click Apply.1ag. Maintenance Associations (MA) are discussed in IEEE 802. Go to CFM > MA/MEG. 2. 2865VpnId: RFC 2685 VPN ID. the MEG name should be 13 characters or less. For more information on specific parameters. The choice are: PrimaryVid: Primary VLAN ID. Maintenance Entity Groups (MEG) are discussed in ITU-Y Y. This displays all Maintenance Associations / Maintenance Entity Groups. the CCM is generated with a non-compliant MEG ID field. String: RFC2579 DisplayString. the system will allow you to enter up to 45 characters for MEG name.a. Maintenance Association (CFM > MA/MEG) Parameter MA/MEG index Index MD index MD Name format Unique index assigned to the Maintenance Domain. refer to the table at the end of this procedure.1731.Setting up Maintenance Associations (Maintenance Entity Groups) Before setting up a MA (a. make sure you first set up the MD you want the MA/MEG to be part of. For more information on specific parameters. Click the Add button to add a new Maintenance Association or Maintenance Entity Group or click the name of an existing Maintenance Association or Maintenance Entity Group to edit its settings. MEG).k. To set up a Maintenance Association or Maintenance Entity Group. In the case of a MEG name more than 13 characters long. Description Unique index assigned to the Maintenance Association or Maintenance Entity Group 156 . 3. Int16: 2-octet integer/big endian. To comply with ICC standards. Name MA/MEG name Name of this Maintenance Association or Maintenance Entity Group. However. Maintenance Domain for this Maintenance Association or Maintenance Entity Group.

This displays all existing maintenance association endpoints. For more information on specific parameters. subtype and Mgmt Address. 157 . VLAN type VLAN type associated with this Maintenance association or MEG. associated with this Maintenance association or MEG. For more information on specific parameters. Go to CFM > MEP > Configuration. LTMs and LTRs. the association is not attached to a VLAN and the VLAN type is set to None implicitly. Chassis: Chassis ID and chassis subtype. MEPID list Setting up Maintenance Endpoints Before setting up a MEP. What. Defer: Determined by domain configuration or system configuration. make sure you first set up its MA/MEG. 3. 2. List of all MEPs. If you leave the VLAN ID empty. Click the Add button to add a new MEP or click the MEPID of an existing MEP to edit its settings. The choices are: None: The association is not attached to a VLAN and the content of the VLAN ID list is ignored.Parameter Level Description Maintenance Level of the Maintenance Association or Maintenance Entity Group. The choices are: None: None. separated by a comma. LBMs. To set up a Maintenance Endpoint. Fill in the required fields and click Apply to start the CCM. refer to the table below. Chassis & manage: Chassis ID. proceed as follows: 1. Possible values: 0-7 CCM interval Sender ID permission Required interval (in ms) between continuity check messages (CCM). if anything. refer to the table at the end of this procedure. Manage: Management Address. is to be included in the Sender ID TLV transmitted in CCMs. C-VLAN S-VLAN VLAN ID list List of VLANs associated with this Maintenance association or MEG.

a MEP transmits CCMs with a sequence number that increases by one for each CCM. CCM sequence number When enabled. When disabled. Note that a peer MEP should have sequence number enabled to allow a local MEP to perform CCM-based packet loss measurements. CCI enable Whether the MEP generates CCM messages. Refer to IEEE802. Domain of the maintenance association (or MEG). Checked (Enabled): The MEP generates CCM messages. Maintenance association End Point Identifier (MEPID) for this Maintenance association. unique to each MA. Unchecked (No): the MEP ceases functioning. Maintenance association (or MEG).Note: The local MEP starts sending CCM frames. An integer. You must configure the other end-point for valid results to be displayed. Index of the maintenance association (or MEG). Port used by this MEP. a MEP transmits CCMs with a sequence number set to zero. Active Administrative state of the MEP. Up: the MEP resides in a Bridge that transmits CFM PDUs toward and from the direction of the Bridge Relay Entity. Unchecked (Disabled): The MEP doesn‘t generate CCM messages. This is always one of the VLAN IDs assigned Description Index assigned to the Maintenance association End Point. identifying a specific MEP in CCM frames. Primary VID The Primary VLAN ID of the MEP. but will display continuity errors.1ag for more information. MAC address of the port used by this MEP. Port MAC address Direction 158 . Down: the MEP resides in a Bridge that receives CFM PDUs from and transmits them toward the LAN. Maintenance Endpoint (CFM > MEP > Configuration) Parameter MEP index Index MD index MD name MA/MEG index MA/MEG name MEPID Index assigned to the Maintenance Domain. Checked (Yes): the MEP is to function normally. The direction in which the MEP faces on the Bridge port.

Time (in ms) for which defects must be absent before resetting a Fault Alarm. Enables the use of this MEP's status in fault propagation. Priority parameter for CCMs and LTMs transmitted by the MEP. Next sequence number/transaction identifier to be sent in a link trace message. For more information on specific parameters.Parameter VLAN Description to the MEP's MA/MEG. The value 0 indicates that either the Primary VLAN ID is that of the MEP's MA/MEG. refer to the table below. 159 . EVC client port to which the MEP status should be propagated. Click any MEPID to view detailed status of this MEP. or that the MEP's MA/MEG is associated with no VLAN ID. 2. Link to this MEP's database. Note that the sequence number will restart at zero after the counter reaches its limit. proceed as follows: 1. Note that the sequence number will restart at zero after the counter reaches its limit. Viewing MEP Status To view maintenance association end point (MEP) status. That port should also be set up to perform EVC fault propagation for this parameter to take effect. The possible values are 0-7. Next sequence number/transaction identifier to be sent in a loopback message. MEP Status (CFM > MEP > Status) Parameter Index MEPID Database Next LBM sequence number Next LTM sequence number Description Index assigned to the maintenance association end point. Time (in ms) for which defects must be present before a Fault Alarm is issued. Go to CFM > MEP > Status to view the status summary of all MEPs. Identifier for the maintenance association end point. refer to the following table. For more information on specific parameters. with 7 being the highest numerical value allowed to passthrough the Bridge Port for any of this MEP's VLAN IDs Default value: 7 (highest priority) CCM and LTM priority Lowest priority defect alarm Fault notification alarm time Fault notification reset time Enable fault propagation Propagate on port Lowest priority defect that is allowed to generate a CFM Fault Alarm.

The last CCM received by this MEP from a remote MEP indicates that the transmitting MEP's associated MAC is reporting an error status via the Port Status TLV or Interface Status TLV. 160 . Active (A) or Inactive (I). Active (A) or Inactive (I). Indicates whether Y. The latest CCM received by this MEP from a remote MEP containing the Remote Defect Indication (RDI) bit. Some packet loss measurement defect is active (A) or inactive (I) for that MEP.Parameter Fault notifications state Description The possible values are: Reset Defect Report defect Defect reported Defect clearing Highest defect priority The highest defect priority sent. Active (A) or Inactive (I). The MEP is not receiving CCMs from a MEP in its configured list. Active (A) or Inactive (I).1731 Alarm Indication Signal (AIS) PDUs are received. Active (A) or Inactive (I). The possible values are: None RDI CCM MAC status Remote CCM Error CCM Xcon CCM AIS Defect RDI CCM RDI MAC MAC status R-CCM Remote CCM E-CC Errored CCM X-CCM Cross-connect CCM AIS Received AIS EPL The MEP is receiving CCMs that could be from some other MA. Active (A) or Inactive (I). The MEP is receiving invalid CCMs.

The time at which the latest loopback request was initiated from that MEP. MEP Database (CFM > MEP > Status > [Database]) Parameter MEP index MEPID Description Maintenance association end point index of the local unit. For more information on specific parameters. refer to the following table. The number of loopback messages transmitted. Go to CFM > MEP > Status and click the MEP database identifier for which you want to view a summary.Parameter Excessive packet loss EDM Excessive delay Description Some delay measurement defect is active (A) or inactive (I) for that MEP. The number of loopback replies missing. refer to the table below. The number of loopback messages requested. The number of loopback replies received with a duplicate LBR sequence number. The number of loopback replies received whose content did not match the corresponding LBM. For more information on specific parameters. The number of loopback replies received. proceed as follows: 1. Loopback (the status of the latest loopback request initiated from that MEP) Loopback request Latest start time Latest end time Nbr LBM requested Nbr LBM sent Nbr LBR received LBR with bad MSDU Nbr LBR duplicated Packet loss ratio Nbr packet lost Nbr gaps Largest gap size Nbr LBR out of order Indicates whether the loopback request process is active for that MEP. The time at which the latest loopback request from that MEP was completed or was stopped. The number of missing packets for the largest gap. The packet loss ratio evaluated during the latest request. Viewing MEP Database To view database information for MEPs. 2. Click any MEPID to view detailed database information. The number of LBRs received whose sequence number did not match the expected one. Maintenance association end point identifier of the remote MEP whose 161 . The number of gaps evaluated inside the LBR stream.

1ag for more details). Blocked (1) Up (2) Interface status TLV The value of the interface status TLV received in the last CCM from the remote MEP (see section 21.(none 0): No CCM was received or no port status TLV was received in the last CCM.(0): No CCM was received or no interface status TLV was received in the last CCM. The time at which the IFF Remote MEP state machine last entered either the failed or OK state.1ag for more details).Parameter Remote MEPID State Remote MEP state Description information from the MEP Database is to be returned. The possible values are: Idle Start Failed OK RDI Latest CCM RDI State of the RDI bit in the last received CCM.4 Port Status TLV of 802. Possible values are: --. The operational state of the remote MEP IFF state machines. Mac address Latest failed-ok time Port status TLV The MAC address of the remote MEP.5.5 Interface Status TLV of 802. The value of the port status TLV received in the last CCM from the remote MEP (see section 21. Possible values are: True: the RDI bit was set. Possible values are: --. False: if no CCM message was received. Up (1) Down (2) Testing (3) Unknown (4) Dormant (5) 162 .5.

MEP Statistics (CFM > MEP > Statistics) Parameter Index MEP index MEPID CCM sent CCM CCM received CCM RDI sent CCM with RDI RDI received CCM with RDI CCM seq error CCM received sequence errors LBM LBR LTM LTR DMM DMR The number of loopback messages sent and received by this MEP. Description Index assigned to the maintenance association end point. The number of delay measurement responses sent and received by this MEP per VLAN priority. The number of connectivity check messages sent by this MEP with the RDI bit set. For more information on specific parameters. refer to the following table. Maintenance association end point Identifier. The number of linktrace messages sent and received by this MEP. The total number of out-of-sequence CCMs received from all remote MEPs. The number of connectivity check messages received by this MEP with the RDI bit set. The number of linktrace responses sent and received by this MEP. The number of connectivity check messages received by this MEP. refer to the table below. The number of delay measurement messages sent and received by this MEP per VLAN priority. The number of loopback responses sent and received by this MEP. proceed as follows: 1. The number of connectivity check messages sent by this MEP. Go to CFM > MEP > Statistics to view the statistics summary of all MEPs.Parameter Description Not present (6) Lower layer down (7) Viewing MEP Statistics To MEP statistics. For more information on specific parameters. 2. 163 . Click any MEPID to view detailed statistics of this MEP.

Description Index of the Maintenance association End Point. Go to CFM > MEP > LTM. 2. The total number of LBRs received whose Mac Service Data Unit did not match (except for the OpCode) that of the corresponding LBM. The remote MEP MAC address is resolved into the local MEP database. refer to the following table. Targeted remote MEPID. The total number of link trace replies dropped because of a bad MAC address. proceed as follows: 1. For more information on specific parameters. Link trace target by remote MEPID or MAC address.Parameter Unexpected LBR received LBR received out of order LBR received with bad MSDU Unexpected LTR received LTR dropped because of BAD MAC Description The total number of LBRs received when no loopback request is active for that MEP. 3. out-of-order loopback replies received. Setting up Link Trace Messages Starting Link Trace Messages To start the link trace messages. MEP Link Trace (CFM > MEP > LTM) Parameter MEP index Index MEPID Target type Remote MEPID R-MEPID MAC address TTL Target MAC address. For more information on specific parameters. Only unicast MAC addresses are valid for link trace target address. The total number of LTRs received when no linktrace request is active for that MEP. This displays all existing link trace information for maintenance association endpoints. Fill in the required fields and click Start. The total number of valid. Link trace time to live. 164 . Click the MEPID of the MEP for which you want to start the LTM. Range: 0–255 Maintenance association End Point Identifier. refer to the table at the end of this procedure.

Terminal MEP. 2. Link trace time to live received in link trace responses. Set FDB only flag Bottom of table LTM sequence number Next seq. Possible values are: RlyHit: The LTM reached a maintenance point whose MAC address matches the target MAC address. Sequence number used by the latest link trace request initiated from that MEP.1ag) or the flag "HWonly" (Y. no response should be received. RlyFDB: The Egress Port was determined by consulting the Filtering Database. Indicates how the responder system processes frames targeted for the destination address specified by the LTM. Click the MEPID of the MEP for which you want to view LTM information. 165 . For more information on specific parameters. RlyMPDB: The Egress Port was determined by consulting the MIP CCM Database. Target MAC address used by the latest link trace request.Parameter Description If it is initially set to 0. # Target MAC address Target MAC TTL F T Action Enables the LTM to set the flag "UseFDBonly" (IEEE 802. Forwarded.1731). proceed as follows: 1. TLV values included in link trace responses. TLV type TLV value Which Type Length Values (TLVs) are included in link trace responses. Indicates that the responder maintenance point is a MEP. Indicates that the responder maintenance point did forward the LTM. refer to the table MEP Link Trace (CFM > MEP > LTM). Go to CFM > MEP > LTM. Viewing Link Trace Messages Information To view the link trace messages information.

Checking this box sets the DEI bit to 1. None: No Data TLV included. refer to the following table. 166 . For more information on specific parameters. The remote MEP MAC address is resolved into the local MEP database. refer to the table at the end of this procedure. Target MAC address. Range: 100–5000. Data TLV Indicates whether LBMs should include a Data Type Length Value (TLV). 2. Go to CFM > MEP > LBM. MEP Loopback (CFM > MEP > LBM) Parameter MEP index Index MEPID Active Target type Remote MEPID MAC address VLAN priority Maintenance association End Point Identifier. Loopback target by remote MEPID or MAC address. Indicates how to determine the LBM VLAN priority value: CCM priority: Use the same priority that MEP CCMs. 3. Specific: Use a specific value specified by the Priority field. Range: 0-7 VLAN drop eligibility Nbr message Interval Value for LBM VLAN drop eligibility bit. Number of LBMs to send.Setting up Loopback Messages Starting Loopback Messages To start the loopback messages. Only Unicast MAC address are valid for link trace target address. Indicates whether a loopback request is active for that MEP. For more information on specific parameters. proceed as follows: 1. Fill in the required fields and click Start. Description Index assigned to the Maintenance association End Point. Target remote MEPID. Click the MEPID of the MEP for which you want to start the LBM. Interval (in ms) between LBMs. Priority Value for LBM VLAN priority. This displays all existing loopback messages for maintenance association endpoints.

The target MAC address used for the latest loopback request. The number of loopback replies (LBR) received for the latest loopback request.Parameter Description Incremental: A Data TLV with incremental byte values is included. The number of LBM requested for the latest loopback request. When the loopback is not active. The sequence number for the next LBM initiated from that MEP. Indicates whether a loopback request is active or inactive for that MEP. this implies the loopback request was stopped by a management command. Pattern: A Data TLV based on a user data pattern is included. The time the latest loopback request has completed or was stopped for that MEP. If not. The computed packet loss ratio for the latest loopback request. Nbr LBR received LBR received LBR with bad MSDU Nbr LBR duplicated Packet loss ratio Nbr packet lost Nbr gaps Largest gap The number of LBR received with a content that did not match the corresponding LBM for the latest loopback request. The size in packets of the largest gap during the latest loopback request. 167 . Range: 1–1488 Pattern User data pattern for the Data TLV. Format: ASCII characters Bottom of table Loopback request Target MAC address Latest start time Latest end time Next seq. The number of missing LBR for the latest loopback request. The time the latest loopback request was initiated for that MEP. The number of LBR received with a sequence number already received for the latest loopback request. The number of times a sequence of LBR was missing during the latest loopback request. Length Amount of data bytes inside the data TLV.# Nbr LBM requested LBM requested Nbr LBM sent The number of LBM sent for the latest loopback request. this number should be the same as the number of LBM requested.

Viewing Loopback Messages Information To view the loopback messages information. refer to the table MEP Loopback (CFM > MEP > LBM). proceed as follows: 1. refer to the table at the end of this procedure. refer to the following table. 2. Click the MEPID of the MEP for which you want to view LBM information. For more information on specific parameters. Fill in the required fields and click Apply. For more information on specific parameters. For more information on specific parameters. Go to CFM > MEP > LBM. via NTP. Note: One-way delay measurements require time synchronization. The local Maintenance association End Point Identifier. Enables sending DMM frames at the specified interval. Go to CFM > DMM > Configuration. 168 . on units at each probe end. This displays all the existing Delay Measurement Instances. The index assigned to the Maintenance association End Point. 3. DMM Configuration (CFM > DMM > Configuration) Parameter Index MEP index MEP idx MEPID Remote MEPID R-MEPID Priority Enable Sampling Priority value used in VLAN tags. if present. The remote Maintenance association End Point Identifier. proceed as follows: 1. Setting up Delay Measurements To configure DMM instances.Parameter size Nbr LBR out of order Description The number of times an LBR was received with a sequence number that did not match the expected one during the latest loopback request. in the transmitted frame. Click Add to create a DMM instance or click the DMM instance name to edit an existing DMM instance. 2. Description The delay measurement's unique identifier. Time (in ms) at which this Delay measurement instance issues DM frames.

. Enables One-way delay measurement for this DMM instance. Maximum one-way delay (in ms) in the Reference period. If a certain number (set by next field value) of consecutive measurements exceeds this value. Number of consecutive measurements exceeding the Maximum allowed value that triggers a one-way delay variation alarm for this Reference period. Number of consecutive measurements exceeding the Maximum allowed value that triggers a one-way delay alarm for this Reference period. Two-way average delay threshold (in ms) that triggers the average two-way delay alarm for this Reference period. Maximum Two-way delay variation (in ms) to monitor in the Reference period. an alarm is triggered. Check to enable One-way delay variation measurements for this DMM instance. 169 . an alarm is triggered. One-way average delay threshold (in ms) that triggers the average one-way delay alarm for this Reference period. an alarm is triggered. If a certain number (set by next field value) of consecutive measurements exceeds this value. Maximum one-way delay variation (in ms) to monitor in the Reference period. Specify the number of consecutive measurements exceeding the Maximum allowed value that triggers a two-way delay variation alarm for this Reference period.Parameter interval Interval Reference period One-way delay Enable Maximum allowed value Instantaneous threshold Average threshold Description Reference period in minutes for the Delay measurements. One-way delay variation Enable Maximum allowed value Instantaneous threshold Average threshold Two-way delay Enable Maximum allowed value Instantaneous threshold Average threshold Check to enable Two-way delay measurement for this DMM instance. Number of consecutive measurements exceeding the Maximum allowed value that triggers a two-way delay alarm for this Reference period. One-way average delay variation threshold (in ms) that triggers the average one-way delay variation alarm for this Reference period. If a certain number (set by next field value) of consecutive measurements exceeds this value. If a certain number (set by next field value) of consecutive measurements exceeds this value. an alarm is triggered. Two-way delay variation Enable Maximum allowed value Instantaneous threshold Indicates whether the Two-way delay variation is computed by this DMM instance. Maximum Two-way delay (in ms) to monitor in the Reference period.

Click the Index of the DDM instance you want to view the DMM results.Parameter Average threshold Description Specify the Two-way average delay variation threshold (in ms) that triggers the average two-way delay variation alarm for this Reference period. Go to CFM > DMM > Results. The remote MEP's Maintenance association End Point Identifier. The number of periods that elapsed since measurement started. is equal to or greater than the instantaneous threshold. This displays results for all Delay Measurement Instances. The current value (in microseconds) for DMM results: OAD: One-way Average Delay OADV: One-way Average Delay Variation TAD: Two-way Average Delay TADV: Two-way Average Delay Variation One-way delay Average alarm Instantaneous alarm Indicates whether an alarm is raised (Active) because the current average oneway delay is equal to or greater than the average threshold. 2. The local MEP's Maintenance association End Point Identifier. Description The index of the Delay measurement. Indicates whether an alarm is raised (Active) because the consecutive amount of times. proceed as follows: 1. the one-way delay was equal or greater than the maximum value. refer to the table below. refer to the following table. For more information on specific parameters. For more information on specific parameters. The index assigned to the Maintenance association End Point. 170 . DMM Results (CFM > DMM > Results) Parameter Index MEP index MEP idx MEPID Remote MEPID R-MEPID Priority Period Period time Result codes The priority value used in VLAN tags. if present. in the transmitted frame. The time when the previous period was completed. Viewing Delay Measurement Results To view delay measurement results details.

The average delay in microseconds over one period. Indicates if an alarm is raised (Active) because the consecutive number of times the one-way delay variation was equal to or greater than the maximum value. The previous period is indicated in Period time. The two-way instantaneous delay (in microseconds). Total number of samples in the period. The maximum delay (in microseconds) over one period. Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded Total number of samples in the period. Gives the results for the previous and current periods. Number of times the one-way delay variation exceeded the value of the parameter Maximum DV. The minimum delay variation in microseconds over one period. The average delay variation in microseconds over one period.Parameter Instantaneous delay Period Description The One-way instantaneous delay (in microseconds). Gives the results for the previous and current periods. One-way delay variation Average alarm Instantaneous alarm Instantaneous DV Period Indicates if an alarm is raised (Active) because the current average one-way delay variation is equal to or greater than the average threshold. The One-way instantaneous delay variation (in microseconds). The maximum delay variation in microseconds over one period. is equal to or greater than the instantaneous threshold. Gives the results for the previous and current periods. 171 . Number of times the one-way delay exceeded the value of the parameter Maximum delay. Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded Two-way delay Average alarm Instantaneous alarm Instantaneous delay Period Indicates if an alarm is raised (Active) because the current average two-way delay is equal to or greater than the average threshold. The minimum delay (in microseconds) over one period. The previous period is indicated in Period time. is equal to or greater than the instantaneous threshold. The previous period is indicated in Period time. Indicates if an alarm is raised (Active) because the consecutive amount of times the two-way delay was equal to or greater than the maximum value.

For more information on specific parameters. Number of times the two-way delay variation exceeded the value of the parameter Maximum DV. Setting up Packet Loss Measurement To set up packet loss instances. The maximum delay (in microseconds) over one period. The average delay variation in microseconds over one period. Click Add to create a packet loss instance or click the packet loss instance name to edit an existing packet loss instance. proceed as follows: 1. The two-way instantaneous delay variation (in microseconds).Parameter Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded Description Total number of samples in the period. refer to the table at the end of this procedure. The previous period is indicated in Period time. Two-way delay variation Average alarm Instantaneous alarm Instantaneous DV Period Indicates if an alarm is raised (Active) because the current average two-way delay variation is equal to or greater than the average threshold. Indicates if an alarm is raised (Active) because the consecutive amount of times the two-way delay variation was equal to or greater than the maximum value. Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded Total number of samples in the period. refer to the following table. 2. Fill in the required fields and click Apply. 172 . Go to CFM > Packet loss > Configuration. The minimum delay variation in microseconds over one period. For more information on specific parameters. 3. is equal to or greater than the instantaneous threshold. The minimum delay (in microseconds) over one period. Gives the results for the previous and current periods. Number of times the two-way delay exceeded the value of the parameter Maximum delay. The average delay in microseconds over one period. This displays all existing packet loss instances. The maximum delay variation in microseconds over one period.

proceed as follows: 1. The Interval between packet loss measurements.Packet Loss Configuration (CFM > Packet loss > Configuration) Parameter Index MEP index MEP idx MEPID Remote MEPID R-MEPID Priority Interval Enable Reference period Threshold The local Maintenance association End Point Identifier. 2. Viewing Packet Loss Results To view packet loss measurement results details. if present. refer to the table below. The remote Maintenance association End Point Identifier. Same as MEP's CCM priority. in the transmitted frame. in the transmitted frame. Same as MEP's CCM interval. Enables packet loss measurements. For more information on specific parameters. if present. Description The packet loss instance unique identifier. For more information on specific parameters. Packet Loss Results (CFM > Packet Loss > Results) Parameter Index MEP index MEP idx MEPID Remote MEPID R-MEPID Priority The local Maintenance association End Point Identifier. 173 . This displays a summary of results for all packet loss instances. refer to the following table. The index assigned to the Maintenance association End Point. Specify (in %) the maximum ratio of packets lost allowed before issuing an alarm during the reference period. The priority value to be used in VLAN tags. Note that a peer MEP should have sequence number enabled to allow a local MEP to perform CCM based packet loss measurements. The remote Maintenance association End Point Identifier. Click the Index of the packet loss instance you want to view the packet loss results. Note that a peer MEP should have sequence number enabled to allow a local MEP to perform CCM based packet loss measurements The Priority value to be used in VLAN tags. The index assigned to the Maintenance association End Point. Description The packet loss instance unique identifier. Go to CFM > Packet loss > Results. Specify the reference period in minutes.

For the current period. Size in packets of the largest gap during the period. Nbr packets lost Nbr gaps Largest gap size Largest gap Setting up CFM Defaults The MIP Half-Function (MHF) default parameters control the MHF creation for VIDs that are not attached to a Maintenance Association. Continuous results in the section below gives the packet loss since the last time the statistics were cleared. the default MHF MD level plus the set of Maintenance Associations which include that VID define the VID's active MD levels. Indicates if an alarm is raised (Active) because the number of packets lost.Parameter Period Description Same as MEP's CCM priority. the Maintenance Association parameters control the MHF creation. For the current period. Number of packets lost during the period. is greater that the packet loss threshold. for the current period. it is a continuous value that is not set to zero at the beginning of the period. If at this level the VID is attached to a Maintenance Association. The previous period is indicated in Period time. proceed as follows: 1. Go to CFM > Defaults. For more information on specific parameters. The number of periods elapsed since measurement started. 174 . if at this level an MEP exists on that port or if an Up MEP exists on some other port. Period time Packet loss alarm Packet loss ratio Loss % Nbr packets The time when the current period results were moved to the previous period results. Number of expected packets during the reference period. this counter is set to zero at the beginning of the period. this counter is set to zero at the beginning of the period. The MD level at which MHFs could be created on a port for a given VID is the VID's lowest active MD level that is higher than any MEP configured on that port. For each port. This displays all existing packet loss instances. For a given VID. To set up CFM defaults. Packet loss ratio expressed as a percentage. a VID is attached to a Maintenance Association at a specific MD level. otherwise the MHF default parameters control the MHF creation. This should normally correspond to the reference period divided by the interval unless the period is incomplete. Number of times packets were missing during the interval. The current period counter is organized as FIFO where a new packet loss result is put into the start and the oldest packet loss result is removed at each interval. refer to the table at the end of this procedure. For the current period.

and LTRs. Fill in the required fields and click Apply. Possible values are: None: no sender ID TLV included. Chassis and manage: chassis ID.2. if anything. or if there is a MEP at the next active MD level on the port. Possible values are: None: No MHFs can be created. Click Add to create a packet loss instance or click a packet loss instance name to edit an existing packet loss instance. 3. subtype and management address. For more information on specific parameters. Manage: management address. Packet Loss Configuration (CFM > Packet loss > Configuration) Parameter MHF MD level MHF creation Description The default active MD level used by the MHF creation algorithm when no other lower active MD level applies. Explicit: Create MHFs only if there is a MEP at the next active MD level on the port. refer to the following table. LBMs. Indicates if the management entity can create MHFs for VIDs on which no Up MEP is configured. Default: Create MHFs if there is no lower active MD level. Chassis: chassis ID and chassis subtype. MHF sender ID permission Indicates what. LTMs. is to be included in the Sender ID TLV transmitted in CCMs. 175 .

It describes how to set this up in your Metro Ethernet Network and perform end-to-end testing and monitoring. You can do this in the unit using the OAM menu. in the peer unit. you need to program. delay and delay variation. This allows you to pinpoint device or network problems or to measure current throughput. the traffic generator must be used with another device to loop the traffic ® back. For IP multicast traffic you need to use the RFC monitor in the remote unit. 176 . For layer-2 generic or layer-3 testing with UDP packets. packet delay and packet-delay variation on a specific network segment. Tests are bidirectional with independent throughput tests in each direction. a private loopback with a swapping action to match the test traffic with the MAC addresses.Testing Network Performance This chapter presents Traffic Generation and Analysis as specified in the ITU-T Y. Test Generator and Loopback Device The test results provide information on the packets sent and received. It contains the following sections:  Understanding Traffic Generation and Analysis  Setting up the Traffic Generator  Starting the Traffic Generator and Viewing Test Results  Setting up the Traffic Analyzer  Viewing the Traffic Analyzer Test Results  Setting up a Test Suite  Running a Test Suite and Viewing Test Reports Understanding Traffic Generation and Analysis Advanced traffic generation and analysis test capabilities allow you to perform fully automated and documented turn-up tests.1731. transmission rates. The test capabilities include out-of-service tests. The MetroNID contains pre-programmed RFC-2544 loopbacks for layer-2 frames. IP addresses and port numbers. In out-of-service tests.

You can use the traffic generator to generate one or two flows of testing traffic. such as traffic type and bit rate. The generator also gives results for each flow. Each flow can be set up for:  Layer-2. Each flow describes the characteristics of the test traffic. Layer-3 traffic  VLAN or VLAN-in-VLAN encapsulation of test traffic  Different traffic types and payload patterns 177 .

Setting up the Traffic Generator You can set up the traffic generator to send one or two traffic flows. each with a different traffic type. An example display is shown in the figure below. VLAN and patterns configuration options. For more information on specific parameters. To set up the RFC-2544 generator. Go to RFC-2544 > Generator > Configuration. 178 . RFC-2544 > Generator > Configuration RFC-2544 Generator Configuration (RFC-2544 > Generator > Configuration) Parameter Outgoing port Enable flow Description Port on which to send the flow(s). Flow(s) included in the test. 2. proceed as follows: 1. Note: The page varies depending on which traffic type you select. To view the complete list of elements that can be configured for each traffic flow. refer to the table RFC-2544 Generator Configuration (RFC-2544 > Generator > Configuration). refer to the table below. Fill in the required fields and click Apply.

For Layer-3 traffic only. all test packets are encapsulated into the second specified VLAN ID.Parameter Description First packet header settings and Second packet header settings Type The type of test traffic: Layer-2: Y. For Layer-3 traffic only. Source UDP port number used to generate the UDP packet. For Layer-2 traffic only.1731 opcode frames to be used only with ―MAC-Address swap‖ based loopback devices. For Layer-3 traffic only. Range: 0–7 IP address of the remote unit. For Layer-3 traffic only. For IP multicast traffic only. DiffServ Code Point to set in the generated packets. Layer-2 generic: special Y. First VLAN canonical format indicator (CFI). Layer-2 Accedian: Y. Enable VLAN 2 header VLAN 2 ID 179 . When enabled. Refer to ITU-T Y. Applies only when VLAN 1 header is enabled.1731 LBM frames with Accedian ethertype. VLAN1 must be enabled to use 2 VLAN headers. Applies only when VLAN 2 header is enabled. Applies only when VLAN 1 header is enabled. First VLAN ID. all test packets are encapsulated into the specified VLAN ID. Encapsulates all packets with 2 VLAN headers (Q in Q). When enabled. Second VLAN ID. Layer-3: IP/UDP packets to perform a test across the multi-layered network. Maintenance Entity Group level.1731 LBM frames. MAC destination Y. Destination UDP port number used to generate the UDP packet. This encapsulates all packets with 1 VLAN header. Applies only when VLAN 1 header is enabled. The source IP address used for the IP header.1731.1731 MEG level Destination IP address DSCP Source IP address Source port Destination port Enable VLAN 1 header VLAN 1 ID VLAN 1 Ethernet type VLAN 1 Priority VLAN 1 CFI Peer MAC address. First VLAN Ethernet type. IP multicast: IP multicast packets to test multiple receiving points. For Layer-2 traffic only. The choices are: S-VLAN and C-VLAN First VLAN priority bits.

The size of test packets varies randomly between the minimum and maximum values. For random packet size only.5 Mbps (steps of 0. You need to specify the Bit rate. this field has no effect. specify the number of packets to send per period (Packets per burst) and the period (in ms) between each burst of packets (Inter-burst gap). For reference in the Results section. A description to identify the flow and its characteristics. Burst: To send a predefined number of packets at every period. 180 . The choices are: S-VLAN and C-VLAN Second VLAN priority bits. Applies only when a VLAN 2 header is enabled. For fixed packet size. specify the bit rate (in Kbps). Name assigned to the flow. specify the Minimum and the Maximum packet sizes. Applies only when VLAN 2 header is enabled. Failure to do so will result in inaccurate results.Parameter VLAN 2 Ethernet type VLAN 2 Priority VLAN 2 CFI Description Second VLAN Ethernet type. You need to specify the Packets per burst. Size type Packet sizes may be fixed or random. You must select a bit rate that does not exceed the capacity of the outgoing port used for that test. Second VLAN canonical format indicator (CFI). For reference in the Results section. Supported values are: 0 to < 12. Note that you may need to modify your port MTU sizes to accommodate your selection. specify the packet size. When Out-of-service flow type is selected. First flow profile settings and Second flow profile settings Flow type Regulator Flow name Flow description Traffic type Type of flow testing being done is: Out-of-service: two-way loopback using the full link bandwidth. For Constant traffic type.125 Mbps) > 13 Mbps to 1 Gbps (steps of 1 Mbps) For Burst traffic type. Type of traffic may be one of the following: Constant: To send packets at a specific bit rate (Kbps). Applies only when VLAN 2 header is enabled.

For an incremental payload pattern. Bytes: Stops after sending a specified number of bytes (Duration (bytes)). specify the 32 bit value. 181 . Seconds: Stops after a specified number of seconds (Duration (secs)).Parameter Payload pattern Description May be a fixed-data. select the increment factor of bytes for byte-by-byte increments or words (2 bytes) for word-by-word increments. Duration type Duration type may be one of the following: Continuous: Stops only when the user manually stops the test.g. 0x12345678 For a random payload pattern. Packets: Stops after sending a specified number of packets (Duration (packets)). For a fixed payload pattern. incremental or random pattern in the payload part of the transmitted frames. e. select one of the pre-configured patterns.

The flow's current state may be one of the following: Waiting: Waiting to be started by the tester. For more information on these results. Stopped: The tester stopped the flow before it completed. Click details of the first or second flow to view the detailed results for this flow.Starting the Traffic Generator and Viewing Test Results Go to RFC-2544 > Generator > Results to view a summary of the traffic generator results. Number of gaps in the numbered sequence. you can view the results of the last test performed. Failed: The flow was deleted before the test was started. Running: The flow is currently running. You can stop the step manually at any time by clicking Stop. Out-of-order or duplicate packets received by this generator (analysis component). Receive statistics Received packets Received bytes Rate OOO or duplicates Number of Total packets received by the generator‘s analysis component for this test. refer to the following table. click Start. The transmitting bit rate in Mbps. When you first enter this page. Each packet contains a sequence 182 . Total bytes received by this generator (analysis component) for this test. after being looped back by the peer device. Completed: The flow reached its duration limit. RFC-2544 Generator Results (RFC-2544 > Generator > Results) Parameter Flow name Description The name assigned to a flow. in Mbps. To start a new test. Total bytes transmitted by this flow for this test. The receiving bit rate. Transmit statistics Transmitted packets Transmitted bytes Rate State Flow state Total packets transmitted by this flow for this test.

183 . Two-way delay variation Instantaneous Two-way instantaneous delay variation value (in ms). When the test was completed or stopped. When the test was started. The delay is measured for each packet from the generator to the loopback device and back to the generator (analysis). Minimum two-way delay (in ms). The delay variation is measured for each set of two consecutive packets from the generator to the loopback device and back to the generator. Average two-way packet delay in microseconds. Average Average DV Minimum Maximum Test times Test started at Test stopped at Minimum two-way delay variation (in ms). Maximum two-way delay (in ms). Two-way instantaneous delay (in ms). Average two-way delay variation (in ms).Parameter gaps Maximum gap Two-way delay Instantaneous Average Average delay Minimum Maximum Description number and a time-stamp to identify the gap. The delay is measured for each packet from the generator to the loopback device and back to the generator. Maximum two-way delay variation (in ms). Maximum size (in frames) of the received gaps.

refer to the table below. RFC-2544 Monitor Configuration (RFC-2544 > Monitor > Configuration) Parameter Name Monitor name State Enable Monitor description Mode Monitor mode Port Incoming port Packet header settings The description set up to identify the monitor and its characteristics. When using a VLAN. The unit configured with a traffic analyzer must be peering with a remote unit to perform end-to-end testing. One way to use the traffic analyzer function is to perform in-Service RFC-2544 non-intrusive throughput tests. Terminal: The RFC-2544 test is terminated at this unit. the VLAN settings may have been changed throughout the network. while enduser traffic continues flowing without interruption. These settings will need to reflect the current state of the RFC-2544 traffic as it enters the unit. which can vary in traffic type. Note: The page varies depending on which traffic type you select. Fill in the required fields and click Apply. proceed as follows: 3. 184 . Go to RFC-2544 > Monitor > Configuration. For more information on specific parameters. The incoming port of the monitor. VLAN and patterns configuration options. Click a monitor Name to edit its settings. Description The name assigned to the monitor. The state of the monitor (Enabled or Disabled). 4. To set up the RFC-2544 analyzer. Bypass: The RFC-2544 test measurements are performed but the traffic follows the rules configured in the Policies for this specific traffic type.Setting up the Traffic Analyzer You can set up the traffic analyzer (or monitor) to receive and analyze one or two traffic flows. 5.

Layer-2 Accedian: Y.1731 opcode compatible frames with only MAC swap device. Applies only when a VLAN 2 header is enabled. The choices are: S-VLAN and C-VLAN. Layer-2 Generic: special Y. For Layer-2 traffic only. Range: 0–7 IP address of the remote unit. First VLAN priority bits.Parameter Type Description The type of test traffic being inspected: Layer-2: Y. Second VLAN ID. When enabled. MAC destination Y.1731 LBM frames with Accedian ethertype. When enabled. The choices are: S-VLAN and C-VLAN. For Layer-3 traffic only. First VLAN Ethernet type.1731 LBM frames. VLAN 2 must be enabled to use two VLAN headers. Diff Serv Code Point to set in the generated packets. Applies only when VLAN 2 header is enabled. Layer-3: IP/UDP packets to perform a test across the multi-layered network. First VLAN ID.1731 opcode frames to be used only with loopback devices based on ―MAC-Address swap‖. (i. Applies only when VLAN 1 header is enabled. Destination UDP port number used to generate the UDP packet. 185 . Layer-2 Swap: special Y. the MAC destination will be equal to the incoming port's MAC address). Source UDP port number used to generate the UDP packet. Maintenance Entity Group level.1731 MEG level Destination IP address DSCP Source port Destination port Enable VLAN 1 header VLAN 1 ID VLAN 1 Ethernet type VLAN 1 Priority VLAN 1 CFI Enable VLAN 2 header VLAN 2 ID VLAN 2 Ethernet type This is the MAC address of the terminating Monitor port. Refer to ITU-T Y. Applies only when VLAN 1 header is enabled. Encapsulates all packets with two VLAN headers (Q in Q).e. For Layer-3 traffic only. For Layer-3 traffic only. all test packets are encapsulated under the second specified VLAN ID. For Layer-3 traffic only. Second VLAN Ethernet type. For Layer-2 traffic only. Applies only when VLAN 1 header is enabled. This encapsulates all packets with one VLAN header. all test packets are encapsulated under the specified VLAN ID.1731. First VLAN canonical format indicator (CFI). if this monitor is set in terminal mode type.

Number of gaps in the sequence. in Mbps.Parameter VLAN 2 Priority VLAN 2 CFI Description Second VLAN priority bits. Total packets received by the associated inspector with an error inside the payload. For more information on specific parameters. Maximum size (in frames) of the gaps. One-way average delay in microseconds. The state of the monitor (Enabled or Disabled). Total bytes received by this monitor. refer to the table below. Applies only when VLAN 2 header is enabled. Applies only when VLAN 2 header is enabled. Second VLAN canonical format indicator (CFI). Out of order frames/packets are frames/packets received in a different order from that in which they were sent. This is the number of Mb received in the last second with an 186 . go to RFC-2544 > Monitor > Results. Receive statistics Received packets Received bytes Rate OOO or duplicates Number of gaps Maximum gap Bad packets Bad bytes Bad rate Total packets received by this monitor. One-way average delay variation in microseconds. Total bytes of the packets received with an error inside the payload. Data rate in Mbps. Viewing the Traffic Analyzer Test Results To view a summary of the traffic analyzer test results for each flow. For detailed traffic analyzer test results. click the flow details. Each packet contains a sequence number and a time-stamp to identify the gap. The receiving bit rate. For more information on specific parameters. RFC-2544 Monitor Results (RFC-2544 > Monitor > Results) Parameter Name State Average delay Average DV Description The name assigned to the monitor. refer to the table below. Out of order or duplicate packets received by this monitor.

Refer to the table at the end of this procedure for more information on the different tests and settings. Minimum delay in microseconds. Minimum delay variation in microseconds. Select the different tests to run.1731 LBM and the MEG (ME Group) level is configurable. For more information on specific parameters. One-way instantaneous delay in microseconds.Parameter One-way delay Instantaneous Minimum Maximum Average Description error inside the payload. Setting up a Test Suite You can run a test suite to determine the conformance of a network section or a specific device to a service level agreement (SLA) and/or to Ethernet standard fulfillment. 3. Average delay variation in microseconds. Average delay in microseconds. refer to the table at the end of this procedure. For more information on specific parameters. Maximum delay in microseconds. proceed as follows: 1. Layer-2 frames and Layer-3 UDP packets are Y. Click the Add button to add a new test suite or click the Name of an existing test suite to edit its settings. You can define a total of eight test suites and have the choice of enabling one or more of the following tests:  throughput  frame loss  delay  back-to-back You also have to set the information relative to the remote peer (Peer settings) and the test packet contents. To set up a test suite. 2. fill in their corresponding settings and other required fields and click Apply. Go to RFC-2544 > Testsuite > Configuration. refer to the table below. One-way delay variation Instantaneous Minimum Maximum Average One-way instantaneous delay variation in microseconds. This displays a summary of all test suites set up. Maximum delay variation in microseconds. 187 .

Check to enable delay and delay variation test. 1000 Mbps and perform a dichotomist algorithm between 800 and 1000 (and a granularity of 10) to find the highest rate for which the pass criteria are met. Once a wirespeed rate with no frame loss has been defined by the throughput test. Description The name of the test suite. Make sure to enter all required parameters in the throughput settings since some of its parameters are applicable for the delay and delay variation test. The unit would then test at full GigE speed. Enable delay 188 . As long as all frames/packets are received. the unit tolerates OOO and duplicates frames/packets. Note that the range is dependant on the unit type and must be less than or equal to the port MTU. When enabled. The Throughput test searches for the maximum rate for which there is no frame loss according to the test settings. When strict failure is disabled. Outgoing port Enable strict failure The port from which to send the flow(s). Binary duration The duration (in seconds) of each trial during the binary search for the maximum throughput. the report contains all tests (e. the test is marked as passed. The description configured to identify the test suite and its characteristics. Default: 2 s. Range: 1 to 10 s. Enable failure on Out Of Order (OOO) or duplicate frames/packets. the delay and delay variation test measures the latency and jitter at that specific rate. you would enter a range of 800 Mbps and 1000 Mbps with a step size of 10 Mbps. even if all frames/packets are received. OOO or duplicates frames/packets will cause a test to fail.RFC-2544 Test Suite Configuration (RFC-2544 > Testsuite > Configuration) Parameter Name Suite name Description Suite description Jumbo frame size The size (in bytes) at which a frame is considered a jumbo frame. When strict failure is enabled. Enable verbose report Test to run Enable throughput Check to enable throughput test. if you wish to measure the quality of a wirespeed GigE circuit. Default: 4096 Example range: 1518 to 10240.g. Out of Order frames/packets are frames/packets received in a different order that they were sent. a test that failed is also displayed in the report) and steps executed. For example.

For Layer-3 traffic only. Make sure to enter all required parameters in the throughput settings since some of its parameters are applicable for the frame loss test. The unit starts at the Maximum rate defined in the throughput settings and steps down by the value set in the Step size parameter of the Frame loss settings. Therefore it is possible to have a small amount of loss without affecting the rate values displayed. The DiffServ Code Point to set in the generated packets. 189 .1731 LBM frames.Parameter Enable frame loss Description Check to enable frame loss test. Layer-2 Accedian: Y. The Back-to-back test performs a burst according to the test settings. Make sure to enter all required parameters in the throughput settings since some of its parameters are applicable for the back-to-back test. For Layer-3 traffic only. Two consecutive rates must have no frame loss in order to successfully pass this test. For Layer-3 traffic only. The Frame loss test verifies that no frames are being lost according to the test settings.1731 LBM frames with Accedian ethertype. For Layer-2 traffic only. if the device under test (DUT) is able to perform full wirespeed at GigE.1731. Enable backto-back Check to enable back-to-back test. Layer-2 generic: special Y. MAC destination Y. Both tests must yield no frame loss to be successful. Source UDP port number used to generate the UDP packet. For example. or a lower rate will then be tested. the DUT must not create any frame loss for each burst. For Layer-2 traffic only. Destination UDP port number used to generate the UDP packet. Note that the transmit/receive rate is an average rounded to the nearest Mbps. Layer-3: IP/UDP packets to perform a test across the multi-layered network. For Layer-3 traffic only. Range: 0–7 Destination IP address DSCP Source port Destination port The IP address of the remote unit interface. the test runs at 1000 Mbps and 980 Mbps (for a Step size of 20 Mbps). A pause of 2 s is taken after each burst. Refer to ITU-T Y. To be successful. Peer settings Type The type of test traffic may be one of the following: Layer-2: Y.1731 opcode frames to be used only with ―MAC-Address swap‖ based loopback devices.1731 MEG level The Peer MAC address. The Maintenance Entity Group level.

When enabled. Applies only when a VLAN 1 header is enabled. You must select a Maximum rate that does not exceed the capacity of the outgoing port used for that test suite. Minimum rate The lower bound of rates (in Mbps) to search for. Applies only when a VLAN 1 header is enabled. The choices are: S-VLAN and C-VLAN Second VLAN priority bits. This parameter also applies for the delay and delay variation test. Applies only when a VLAN 1 header is enabled. Applies only when a VLAN 2 header is enabled. This parameter also applies for the delay and delay variation test. Encapsulates all packets with 2 VLAN headers (Q in Q). The choices are: S-VLAN and C-VLAN. First VLAN canonical format indicator (CFI). Second VLAN Ethernet type. When enabled. all test packets are encapsulated into the specified VLAN ID. First VLAN ID. Second VLAN ID. Second VLAN canonical format indicator (CFI). Applies only when a VLAN 2 header is enabled. and for the frame loss test. Failure to do so will result in inaccurate results. Range: 1 to 1000 Mbps (1 Gbps). You must select a Minimum rate that does not exceed the capacity of the outgoing port used for that test suite. 190 . Range: 1 to 1000 Mbps (1 Gbps).Parameter Enable VLAN 1 header VLAN 1 ID VLAN 1 Ethernet type VLAN 1 Priority VLAN 1 CFI Enable VLAN 2 header VLAN 2 ID VLAN 2 Ethernet type VLAN 2 Priority VLAN 2 CFI Description This encapsulates all packets with 1 VLAN header. and for the frame loss test. Applies only when a VLAN 2 header is enabled. Maximum rate The upper bound of rates (in Mbps) to search for. First VLAN Ethernet type. Range: 1 to 1800 s. First VLAN priority bits. all test packets are encapsulated into the second specified VLAN ID. Throughput settings Trial duration The period (in seconds) of time for the throughput test Default: 60 s. Failure to do so will result in inaccurate results.

e. The Step size configured is no longer used. By default.e. Use fine stepping Enable fine stepping in case of low bandwidth testing (below 12 Mbps).1%). the Jumbo frame size is not selected as it was not a frame size defined by the RFC-2544 standard. Delay and delay variation settings Trial duration The period (in seconds) of time over which the test is run. Frame loss settings Trial duration The period (in seconds) of time over which the test is run. the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard.Parameter Step size Description The granularity (in Mbps) of the range. By default. Range: 1 to 1800 s. Minimum Rate and Fine Stepping values set in the Throughput settings. Note that the frame size selected must be smaller than the port MTU. 191 . i. which means a target of no frame loss is allowed for defining full throughput. i. Note that the frame size selected must be smaller than the port MTU. Default: 0. which means the target is no frame loss is allowed for defining full throughput . Frame loss The acceptable difference between measured frame losses (N x 0. and for the frame loss test. Selecting a higher frame size will prevent you from running the test. Step size The granularity (in Mbps) of the range. For example.1% frame loss would be acceptable and considered as no frame loss by the test. losing a single frame will cause the test to fail. Frame loss The acceptable difference between measured frame losses (N x 0.1%). Frame size settings Select the frame sizes to test. Frame size settings Select the frame sizes to test. The step size use for the range is 125 kbps. a setting of 1 would mean a 0. Default: 120 s. Range: 1 to 1800 s. This parameter also applies for the delay and delay variation test. losing a single frame will cause the test to fail. Range: greater than zero to the maximum rate. For example.1% frame loss would be acceptable and considered as no frame loss by the test. Minimum Rate and Fine Stepping values set in the Throughput settings. The frame loss test uses also the Maximum Rate. a setting of 1 would mean a 0. Default: 60 s. Default: 0. Selecting a higher frame size will prevent you from running the test. The Delay and delay variation test uses also the Maximum Rate.

refer to the table at the end of this procedure. Selecting a higher frame size will prevent you from running the test. Frame size settings Select the frame sizes to test. Possible values are: 192 . You can run a specific test suite many times as long as you configure a new report. Default: 50 times. Since each test is association with one test report. the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard. Range: to 100 times. Default: 2000 ms. proceed as follows: 1. Selecting a higher frame size will prevent you from running the test. For more information on specific parameters. you can run it and view its report. To run a test suite. 3. RFC-2544 Test Suite Reports (RFC-2544 > Testsuite > Reports) Parameter Name Status Description The name assigned to the report The report's current status. By default. 2. Note that the frame size selected must be smaller than the port MTU. By default. Click the Start new testsuites button to configure a new report. the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard. Note that the frame size selected must be smaller than the port MTU. you have to configure a new report each time you want to run a new test. Running a Test Suite and Viewing Test Reports Once you have set up a test suite. A pause of 2 s is taken after each burst. Go to RFC-2544 > Testsuite > Report. Range: 1 to 10000 ms. Fill in the required fields and click Apply. refer to the table below. Repeat The number of bursts to perform for each frame/packet size. For more information on specific parameters. This displays a summary of all test suite reports.Parameter Frame size settings Description Select the frame sizes to test. Back to back settings Trial duration The period (in milliseconds) of time over which the test is run.

While a test is running. proceed as follows: 1.Parameter Description Failed: An error occurred during the test suite execution. This displays a summary of all test suite reports. save or delete a test suite report. Stopped: A user stopped the test suite during its execution. The information relative to the report not included in the previous field. Go to RFC-2544 > Testsuite > Report. 2. refer to the table RFC-2544 Generator Results (RFC-2544 > Generator > Results). 193 . Select the test suite you want to run for this report. For more information on specific parameters. Click the Name of an existing test suite report to view its report file or to perform other actions. Running: The test suite is currently running. You can then on Save to save it on the management station as a text file or on Delete to delete it. Description Technician name Testsuite configuration Special note The description to identify the report. Who executed the test suite. click on Stop to stop it. Completed: The Test suite has completed. To view.

The unit allows for two types of loopback: Local (or private) loopback: loops back all traffic matching the type of loopback in the setup (Iometrix L1. Sunrise™). IP address & port swap) permit remote QoS testing for Ethernet. 194 . Custom). so customer traffic continues to flow while tests are performed on selected streams. Exfo L2. IP / MPLS and triple-play services.Managing Loopbacks This chapter describes how to manage loopback and contains the following sections:  Understanding Loopback Testing  Enabling or Disabling a Local Loopback  Enabling or Disabling a Remotely Controlled Loopback Understanding Loopback Testing Layer 1-4 loopbacks (MAC address. Loopbacks can be established by any of the following combination of parameters:  VLAN  source or destination address  TCP/UDP port  Service level Loopback can be performed in-band or out-of-band. Exfo L3. Remotely controlled loopback: Loops back traffic and is initiated upon the reception of a predefined packet type (JDSU/Acterna™.

Enabling or Disabling a Local Loopback
The steps required to set up a local loopback are:  Define filters for capturing traffic (required for custom loopbacks only), referring to Defining Filters on page 92.  Create an OAM instance, referring to Setting up an OAM Instance on page 135.  Set up a loopback, referring to Setting up and Enabling Loopbacks on page 195.

Setting up and Enabling Loopbacks
You must first create the OAM instance from the OAM > Configuration page and then set up the loopback. To set up a local loopback, proceed as follows: 1. Go to OAM > Loopback. This displays a summary of all loopbacks set up. For more information on specific parameters, refer to the table at the end of this procedure. 2. Click the loopback Name to edit its settings. 3. Fill in the required fields (top part of page) and click Apply. For more information on specific parameters, refer to the following table. Note: Only the fields listed in the following table are required for a local loopback. Leave the other fields at their default settings.

OAM Loopback (OAM > Loopback)
Parameter Name State Lpbk state Lpbk mode Description The OAM instance name as defined in the OAM > Configuration page. The current state of the loopback. An enabled loopback may not necessarily loop back traffic; this depends on the location setting. An instance enabled for a remotely controlled loopback is not shown in this field. The loopback control logic, once enabled, may be using the standard IEEE 802.3ah mode or may be using a private or proprietary mode. When using the private mode, the user can select filters and can allow other traffic to flow through, effectively doing an in-service loopback. Indicates whether the loopback is controlled locally or remotely. Once enabled, a local loopback immediately applies the loopback to the unit as programmed. An enabled remote loopback instructs the unit to transmit a loopback request to its OAM partner. Enables the locally controlled loopback function. Type may be one of the following:

Location

Loopback enable Type

195

Parameter

Description Iometrix L1: Iometrix cNode level 1. Loop back all packets that have a destination address equal to 00:30:79:FF:FF:FF Exfo L2: Loop back all packets that have a source MAC OUI equal to 00:03:01 Exfo L3: Loop back all UDP echo service packets AnaCise L2: Loop back all packets that have a source MAC OUI equal to 00:18:75 AnaCise L3: Loopback all UDP echo service packets Custom: Loop back all traffic that matches the user defined filter (Filter type and related field)

Persistent Filter type

Enables the loopback at startup time. This option can only be set for locally controlled loopbacks with no timeout. Filter type to be applied to the loopback traffic: L2 filter IPv4 filter

L2 filter IPv4 filter Actions

The L2 filter to be applied to loopback traffic, if filter type is L2 filter. The IPv4 filter to be applied to loopback traffic, if filter type of IPv4 filter. Action may be one or more of the following: Swap MAC addresses: Swaps the source and destination MAC addresses Swap IP addresses: Swaps the source and destination IP addresses Swap TCP/UDP ports: Swaps the source and destination TCP/UDP ports

Drop opposite traffic

Drops traffic originating from the Client port when looping back to the Network port and vice versa. Note: enabling this option interrupts the Ethernet service in one direction.

Loopback timeout

Number of minutes for the loopback to remain enabled. When the timeout expires the loopback is automatically removed.

196

Enabling or Disabling a Remotely Controlled Loopback
The steps required to set up a remotely controlled loopback are:  Setting up an OAM Instance, referring to Setting up an OAM Instance on page 135.  Setting up the remotely controlled loopback and then enabling it Once the OAM instance is created, set up a remotely controlled loopback as follows: 1. Go to OAM > Loopback. 2. Click the loopback Name to edit its settings. 3. Fill in the required fields (top part of page) and click Apply. For more information on specific parameters, refer to the following table. Note: Only the fields listed in the following table are required for a remotely controlled loopback. Leave the other fields at their default settings.

OAM Loopback (OAM > Loopback)
Parameter Name State JDSU/Acterna
TM

Description The name of the OAM instance as defined in the OAM > Configuration page. The current state of the loopback. Enables the activation of this remotely controlled loopback by a TM JDSU/Acterna device. Accepts JDSU/Acterna
TM

Enable discovery loop commands Sunrise VeEX
TM

discovery loopback commands.

Enables the activation of this remotely controlled loopback by a Sunrise device. The unit supports tests on layers 2 and 3. Enables the activation of this remotely controlled loopback by a VeEX device. The unit supports tests on layers 2, 3 and 4.

TM

TM

TM

OAM 802.3ah Accept tagged loopback commands

Enables the activation of this remotely controlled loopback by a device supporting the OAM 802.3ah protocol. Accepts tagged loopback commands. This option is valid only for untagged OAM instances. Tagged OAM instances accept loopback commands only from a specific VLAN.

197

Managing Alarms and System Messages
This chapter describes functions related to alarms and system messages and contains the following sections:  Managing Alarms  Managing Syslog Messages TM  Managing the EchoAgent  Managing the SNMP Agent  Managing History Files

Managing Alarms
The unit provides alarm functions to monitor and report the status of the unit, of the traffic performance and of other components.

Setting General Alarms
To set up general alarms, proceed as follows: 1. Go to System > Alarm > General. 2. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.

Alarm Settings (System > Alarm > General)
Parameter Notification Enable LED reporting Enable syslog reporting Enable SNMP reporting Enable 802.3AH reporting Thresholds Threshold on (soaking time in msecs) The delay after an event is detected before the alarm notification occurs. Enables the reporting of alarms by activating the unit LED that is appropriate and that corresponds to the severity, e.g. minor, major, critical. Enables the reporting of alarms by creating entries in the syslog. Enables the reporting of alarms via SNMP traps from Accedian‘s private MIB. Enables reporting of alarms via 802.3AH OAMPDUs using organizationspecific events. Description

198

CC: Error number (1-99). Alarm Configuration (System > Alarm > Configuration) Parameter Number Description The unique number that identifies this alarm. For more information on specific parameters. Click the number of the alarm that you want to edit. Packet Loss and other related alarms 4: SOAM module for Continuity Check. refer to the following table. Go to System > Alarm > Configuration. 3. temp. proceed as follows: 1. Fill in the required fields and click Apply. Customizing Alarms To customize an alarm. This number is assigned by the unit and cannot be modified. 2. This displays the settings for all alarms. BBBB: Instance number (1-9999). refer to the table at the end of this procedure. Delay. Packet Loss and other related alarms 5: Unassigned 6: Unassigned 7: System module such as NTP and other agents 199 .Parameter Threshold off (soaking time in msecs) Description The delay after an event clears before the alarm notification clears. This alarm number is composed of three fields In the format: A.CC. Delay.BBBB. where the components are as follows: A: Module number (1-999). For more information on specific parameters. vcc and lbc alarms and warnings 3: PAA module for Continuity Check. A module number is assigned for each alarm in the system and may be one of the following: 1: Port module for link down and other related alarms 2: SFP module for Rx/Tx power.

where the parameters are as follows: A: Module number (1-999) 200 . If LED reporting is enabled on the Alarm > General page. This number is assigned by the unit and cannot be modified. Alarm Status (Show > Alarm) Parameter Status Number Description The status LED is ON if the alarm is enabled and has been triggered. Minor: An error condition has occurred that does not seriously affect system functionality. Textual description of the alarm. Viewing Alarms Go to Show > Alarm to view alarm status. the instance number and the error number. The format is A. Provides status information. refer to the following table. Major and Critical alarms are indicated on the unit's front panel LEDs. the Minor. alarms are reported. the module number. The description is displayed in the Show > Alarm page. If enabled. Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality. For more information on specific parameters.CC. This alarm number is composed of three fields. Informational: No effect on service. The unique number that identifies this alarm.BBBB.Parameter Description 8: Environmental module for power supplies and temperature sensors 9: Unassigned 10: Unassigned Enable Severity Indicates whether the alarm is enabled (true) or disabled (false). The severity of the alarm. Critical: A service-affecting condition has occurred that requires immediate corrective action. Service affecting Description Alarms may be displayed as service affecting or non-service affecting.

Packet Loss and other related alarms. Textual description of the alarm. Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality.g. This is displayed only when the alarm has changed status (the alarm was turned ON or OFF). 3: PAA module for Continuity Check. 5: Unassigned 6: Unassigned 7: System module such as NTP and other agents 8: Environmental module for power supplies and temperature sensors 9: Unassigned 10: Unassigned Presence Severity Indicates whether the alarm is currently present (true) or not (false). 201 . vcc and lbc alarms and warnings. e. Severity of the alarm may be one of the following: Informational: No effect on service. Delay. Critical: A service-affecting condition has occurred that requires immediate corrective action. 2: SFP module for Rx/Tx power. 4: SOAM module for Continuity Check.Parameter Description BBBB: Instance number (1-999/1-9999). Service affecting Description Message Alarms may be displayed as service affecting or non-service affecting. Provides status information. temperature was above the threshold. Packet Loss and other related alarms. Delay. CC: Error number (1-99) A module number is assigned for each alarm in the system and may be one of the following: 1: Port module for link down and other related alarms. The message explains why it was turned on or off. Minor: An error condition has occurred that does not seriously affect system functionality. temp.

yyyy.yyyy.17 <SFP module> temperature high alarm <SFP module> temperature low alarm <SFP module> temperature high warning <SFP module> temperature low warning <SFP module> supply voltage high alarm <SFP module> supply voltage low alarm <SFP module> supply voltage high warning <SFP module> supply voltage low warning <SFP module> laser bias current high alarm <SFP module> laser bias current low alarm <SFP module> laser bias current high warning <SFP module> laser bias current low warning <SFP module> transmit power high alarm <SFP module> transmit power low alarm <SFP module> transmit power high warning <SFP module> transmit power low warning <SFP module> receive power high alarm 202 .yyyy.13 2. temp.15 2.yyyy.01 2.0002.02 link down on Management port link down on Monitor-1 port link down on Monitor-2 port link down on Client port link down on Network port loopback on port Client loopback on port Network SFP module alarms and warnings for Rx/Tx power.yyyy. vcc and lbc. yyyy specifies the SFP module.01 1.0004.yyyy. In this section. 0002 = SFP-B.yyyy.03 2. Supported Alarms: MetroNID Number Default Description Port module for link down and others related alarms 1.11 2.01 1.04 2.0005.yyyy.0005.12 2.yyyy.yyyy.07 2.yyyy.yyyy.yyyy.yyyy.01 1.02 2.05 2.14 2.yyyy.16 2.01 1.06 2.0001. where 0001 = SFP-A. Refer to the following table for a list of all alarms supported and their default description.yyyy.0004.0003.yyyy.09 2.10 2.01 1.02 1.08 2. 0003 = SFP-C. and 0004 = SFP-D 2.Parameter Last change Description When the alarm changed status.

yyyy. In this section.yyyy.06 3.yyyy. In this section. yyyy specifies the MEPID number 4.yyyy.11 4.01 3.06 4.13 RDI on down MEP MAC status on down MEP Remote CCM on down MEP Errored CCM on down MEP Cross-connected CCM on down MEP AIS on down MEP One-way delay on down MEP One-way average delay on down MEP One-way delay variation on down MEP One-way average delay variation on down MEP Two-way delay on down MEP Two-way average delay on down MEP Two-way delay variation on down MEP 203 .yyyy.yyyy.yyyy.Number 2.18 2.08 4.yyyy.yyyy.04 4.20 2.10 <PAA probe name> PAA_CC_ALERT <PAA probe name> PAA_PL_ALERT <PAA probe name> PAA_OW_DELAY_ALERT <PAA probe name> PAA_OW_AVG_DELAY_ALERT <PAA probe name> PAA_OW_DV_ALERT <PAA probe name> PAA_OW_AVG_DV_ALERT <PAA probe name> PAA_TW_DELAY_ALERT <PAA probe name> PAA_TW_AVG_DELAY_ALERT <PAA probe name> PAA_TW_DV_ALERT <PAA probe name> PAA_TW_AVG_DV_ALERT SOAM module for Continuity Check.02 4.yyyy.yyyy.yyyy.03 3.01 4.yyyy.yyyy.yyyy.09 4.09 3.07 4.yyyy.yyyy. Packet Loss and other related alarms Note that these alarms are dynamically created based on the MEPs configured.yyyy.05 3.yyyy.yyyy. Delay.08 3.03 4.07 3.yyyy.yyyy.04 3.yyyy.yyyy.19 2.21 Default Description <SFP module> receive power low alarm <SFP module> receive power high warning <SFP module> receive power low warning <SFP module> not present Performance Assurance Agent alarms Note that these alarms are dynamically created based on the PAA probes configured.02 3. yyyy specifies the index of the PAA instance 3.12 4.yyyy.05 4.yyyy.yyyy.10 4.

04 8.yyyy.51 First overheating threshold Second overheating threshold Power supply +5 V DC Power supply on -48 V feed A Power supply on -48 V feed B Communication lost with GPS module Loss of fix for the GPS module To view the detailed status of an alarm. For more information on specific parameters. First threshold: The temperature that will activate the first overheating alarm.0000.01 7.02 8.Number 4.0001. Viewing Chassis Alarms Go to System > Alarm > Chassis to view the status of chassis-related alarms. A green light indicates that the power source is connected and is operating normally.03 NTP client lost server communication GPS communication—may affect one-way delay measurements Environmental module for power supplies and temperature sensors 8. proceed as follows: 1. Go to Show > Alarm. refer to the following table.0000.0000. 2. refer to the table Alarm Status (Show > Alarm).14 4. Temperature sensor status Temperature sensor The current temperature inside the unit. 204 .0000.0000.yyyy.01 8. For more information on specific parameters.05 8. Click the alarm number to view its detailed status. A red light indicates that the power source is not connected or is not operating normally.0001.15 Default Description Two-way average delay variation on down MEP Excessive packet loss on down MEP System module such as NTP and other agents 7.0000. Power Supplies and Temperature Sensors (System > Alarm > Chassis) Parameter Power supply status Description The status of the various power sources for Feed A and Feed B.0000.03 8.50 8.

a workstation.g. Go to System > Agents > Syslog. This displays all syslog entries with the most recent entry at the top. The IP address or domain name of the remote syslog server. refer to the table Syslog Configuration (System > Agents > Syslog). Managing Syslog Messages The unit logs information related to system operations as Syslog Messages. proceed as follows: 1. Enables the sending of messages to a remote syslog server. Log all messages with a level equal to or greater than the selected one. 2. 2. e. For more information on specific parameters. setting the priority threshold to DEBUG (lowest priority) causes all messages to be logged. Fill in the required fields and click Apply. Defining Syslog Parameters To configure Syslog parameters. Syslog Configuration (System > Agents > Syslog) Parameter Device facility Level threshold Description The device facility to log all messages using this user-defined facility instead of the default ones. refer to the following table. For example.Parameter thresholds Description Second threshold: The temperature that will activate the second overheating alarm. Go to System > Agents > Syslog. Fill in the required fields and click Apply. You can update the log window with the most recent messages by clicking Refresh. You can view the syslog messages directly in the Web-management interface or send the log to a remote location. Remote syslog enable Host Sending Syslog Messages to a Remote Location You can configure the unit to send Syslog messages to a Syslog server in a remote location. 205 . proceed as follows: 1. To do this. For more information on specific parameters.

The password is case sensitive. logs events and also triggers the EchoAgent™ to download a new configuration or firmware. The host name or IP address of the HTTP proxy. 206 . 2. Normally 80 for http or 443 for https. a component of Creanord's EchoVault platform is responsible to communicate with each EchoAgent™. For more information on specific parameters. Communication protocol Communication port Password The communication between the EchoAgent™ and Local Controller. Creanord EchoAgent™ configuration (System > Agents > EchoAgent™) Parameter General Local controllers The host name or IP address of the Local Controller. The TCP port number used to reach the Local Controller. Go to System > Agents > EchoAgent™. Use value 0 unless otherwise advised by the support representative. Enabling the EchoAgent™ To enable the EchoAgent™. The password that is used to authenticate the EchoAgent™ with the Local Controller. Description Proxy host (optional) Proxy host Proxy port Others Log level Level (0-7) of verboseness of EchoAgent™ and other syslog messages forwarded to the Creanord EchoVault platform. A TCP Port for proxy communication. Best practices recommend the use of alphanumeric passwords.Managing the EchoAgentTM With the help of Creanord EchoAgent™. the unit can be centrally managed through Creanord EchoVault Service and SLA delivery platform. Set the log level as 0 to filter out all but emergency (system is unusable) messages as defined by RFC 3164. proceed as follows: 1. refer to the following table. To do this. Debug level The debug level (0–500). you must configure the EchoAgent™ on each unit you want to manage with the Creanord EchoAgent™. The Local Controller. Choices are http or https. Up to three Local Controllers can be configured. Fill in the required fields and click Apply. Default value is 4. receives results.

The community string to control read-only access to the unit. Go to System > Agents > SNMP. you must re-enter all the information. Click the Reset_Agent button to set all configuration parameters to default values and to disable the EchoAgent™. Contact information for the unit.Parameter Report interval Description Period in seconds to communicate with the Local Controller. Click the Refresh_status button to refresh the EchoAgent™ logs. Uses host's name as system-name. Click the Restart_Agent button to disconnect the agent and reconnect it to EchoVault. The SNMP agent also allows the unit to send SNMP traps to a receiver. By convention. refer to the following table. To reinitiate the connection to EchoVault. Note that changing this value restarts the SNMP agent. UDP port that the SNMP agent uses for all IPv4 interfaces. The receiver is usually used to monitor the conditions of many units. The name to identify the unit. For more information on specific parameters. You can also view the status of the EchoAgent™ at the bottom of the System > Agents > EchoAgent™ page. 2. Generally an email address. proceed as follows: 1. this is the node's fully-qualified domain name. Enabling the SNMP Agent To enable the SNMP agent. SNMP Agent (System > Agents > SNMP) Parameter Enable Agent Use host name as system name SNMP system name Contact information System location Agent UDP port Read-Only community Description Enables the unit‘s SNMP agent. Managing the SNMP Agent You can configure an SNMP agent so that it provides an interface to an SNMP-based management system (for get and set commands). Physical location of the unit. Fill in the required fields and click Apply. 207 .

2. 208 . the IP address of the compatible notification receiver is automatically updated when the receiver connects to the unit and sends the appropriate CLI commands. Setting up the SNMP Trap Receivers You can configure the unit to send SNMP traps to different notification receivers.3 linkDown) and 3 (1. IP address or host name of the device that receives SNMP traps and/or notifications. refer to the table below.Parameter Read-Write community Enable authentication trap generation Enable link trap generation Description The community string to control read/write access to the unit. Go to System > Agents > Traps.5. Map to the generic traps 2 (1. Enables the unit to generate a trap when authentication to the agent fails. Fill in the required fields and click Apply.6.6. Enables the unit to send SNMPv1 or SNMPv2c traps to a specified notification receiver.1. For more information on specific parameters. Click the ID of the trap receiver you want to edit. Enables trap generation when link status changes. You can configure the unit to send SNMP v1 traps to one or two receivers and to send SNMP SMTP v2c traps to up to ten receivers.6.3.6. The notification receiver is usually used to monitor conditions of many units. proceed as follows: 1. you can also configure the unit to send SNMP traps (v1 or v2c) to other compatible notification receivers. If Enabled the unit sends SNMPv1 or SNMPv2c traps to a specified notification receiver. With the Auto trap receiver.4 linkUp).1.1.1. Refer to the CLI Command Manual for information on the CLI command.1. For more information on specific parameters.3. 3. The unit sends a Cold Start trap when it starts up.1. Using the Auto trap receiver. refer to the table below.3. Trap Receivers (System > Agents > Traps) Parameter Type ID State Enable trap Notification receiver Host name Description Type of SNMP Trap receivers may be SNMPv1 or SNMPv2c ID number of the trap receiver.3. This displays all current SNMP Trap receiver information.5. To configure the SNMP trap receiver information.

which are stored in RAM. UDP port the unit uses to send traps to the notification receiver. Managing History Files You can manage the creation and transfer of history files. The storage of these files also protects against losing history statistics in the event of a power failure or reboot. CFM PL) for which history has been enabled. Click Apply. By default. These files can ―pushed‖ to a server according to the schedule and filetransfer configuration defined in this menu. the well-known SNMP trap port 162 is used. Check the Enable filling box of each feature you want to create history files with and enter the Period after which you want to store the files into non-volatile memory.Parameter Community string Community Host UDP port UDP port Description The community string required to send traps to the notification receiver. The history files can be stored locally for the following features: PAA Regulator 209 . proceed as follows: 1. CFM DMM. For more information on specific parameters. refer to the following table. Check the Enable history box 3. 2. Policy. You can configure the local unit and remote units to transfer their history files to a server. Regulator. Go to System > Agents > History. These are accessible through SNMP (get command). Allows the history files to be stored locally into non-volatile memory (NVRAM). Creating History Files To enable the creation of history files for the local unit. 4. History files contain statistics about the services (PAA. Local Configuration (System > Agents > History) Parameter Enable history Enable filing Description Allows the creation of history files. Not checking this box results in the existing history files for this feature being removed locally.

proceed as follows: 1. Hold the CTRL key to select more than one time. Hold the CTRL key to select more than one time. Examples: If a device has 3:00 and 15:00 selected in the Scheduled hours. 00:30 and 00:45 boundaries. Only the objects that have their filing feature enabled on the local device generate a report file. When a large number of devices are set to generate report files. Ensure filing is enabled for the desired history files and click Apply. with which history statistics should be stored in non-volatile memory. Enable the history buckets report files to be transferred by the local device. Description Scheduled minutes Schedule offset 210 . at any minute. Enable scheduling at the desired time slot(s). plus 00:00 and 00:30 in the Scheduled minutes with a Schedule offset of 0 minutes. this can be used to spread the load on the network and servers. This allows the local scheduling to be set to trigger every 15 minutes. Transferring History Files To allow transfer of history files. either on the hourly boundary or on the 00:15. Go to System > Agents > History. 2. fill in the other fields and click Apply. See Creating History Files. Scheduling and File Transfer (System > Agents > History) Parameter Scheduling Scheduled hours Enable local The time at which history buckets are transferred. This allows the local scheduling to be offset by [0-14] minutes. Using this field. 3.Parameter Description Policy CFM DMM CFM PL Period The frequency. reports can be generated as often as four times per hour. This feature is dependant on the filing check boxes in the Local configuration sections of the local devices. provide the URL for the file transfer server. Any selection is valid as long as there is at least one box selected. in minutes. Scheduled hours The time at which history buckets are transferred. Finer granularity is possible using the Scheduled minutes and Schedule offset fields.

15:00 and 15:30.1. If Include periods from previous incomplete transfers is selected. This random offset is added to the schedule offset. only objects which are enabled are included. Fixed number of periods: All the periods available. reports are generated at the 19th and 49th minute of every hour.168. plus 00:15 and 00:45 in the Scheduled minutes with a Schedule offset of 4 minutes. 211 .com tftp://192. This allows multiple devices set to generate reports at the same time and to the same destination to be randomly offset from one another. the random offset value is automatically set to the highest possible value. If the sum of those two values exceeds 900 seconds. up to a fixed maximum number of periods. Options This allows control over how the reports are generated. Three modes of operation are available. New periods since last file transfer: All the periods that have been generated since the previous report. relieving the burden created by several connections happening at once.Parameter Description reports are generated at 3:00. If unchecked.5 SCP password File options Period mode This controls which periods to include in the reports. the periods from a previous report that couldn't be properly generated or sent to the server are also included. Random offset This allows a random offset to be generated.com ftp://username:password@mypc. Note that the combined value of the schedule offset and random offset can't exceed 15 minutes (900 seconds). Include disabled objects: When checked. All available periods: All the periods that are available on the devices are used to generate the reports. Note that this setting affects both local and remote history buckets. Examples: http://mypc. up to the maximum number of periods specified by the user in Local periods (for local reports) and Remote periods (for remote reports). all managed objects are included in the reports. Include periods from previous incomplete transfers: When checked. anywhere between 0 and the specified value. If a device has all hours selected in the Scheduled hours. 3:30. File transfer Server URL The full URL of the Server on which to send the history bucket files once retrieved. Password required by the SSH server.

only the periods since the previous report are included.Parameter Description the periods contained in a report that couldn't be properly generated or sent to the server are also included in the current report. If unchecked. 212 .

Sign up to vote on this title
UsefulNot useful