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

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

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

7 . The term ―management web-interface‖ refers to the web-based interface that comes with the unit. 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. service providers and cable MSO personnel to provide service assurance and service creation solutions to their clients. 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. The term ―unit‖ in this manual refers to any one of these network devices.About This Manual This document provides information about the technologies and standards used in Accedian Network‘s equipment and procedure to help wireless operators. configuration and use of Accedian‘s network interface devices such as the EtherNID and ® MetroNID . Organization This document contains three main parts: an introduction.

0001 is for SFP-A and 01 means temperature high alarm. including death 8 . So. the 2 refers to SFP modules.yyyy. 2.01. For such features. For example. The third number (z) is the specific alarm code. Menu navigation example: CFM > DMM > Configuration Brackets [ ] are used when several options are available and you need to select a specific option. If the same parameter is labelled differently on the pages.01 means SFP-A temperature high alarm. The first number (x) refers to a general category. 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. in 2.0001. <SFP module> can refer to any SFP module.0001. as far as is possible. from which you can then select one element in order to get more detailed information on a separate page. one parameter table covers both the summary page and the detailed page. For example. In the alarm descriptions.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.zz. then both labels are listed in the table. Commands and keywords are in bold. The second number (yyyy) refers to the specific component. The parameters are listed in the order that they appear on the page. 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. depending upon what the component number yyyy is.

refer to the following:  IEEE 802.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 .Provider Backbone Bridges  ITU-T Y.1731 : OAM functions and mechanisms for Ethernet-based networks  Technical Specification – MEF 17 – Service OAM Requirements & Framework – Phase 1  Technical Specification – MEF 6. technical specifications and technologies.References The use of equipment such as the EtherNID and MetroNID involves the understanding of different networking standards. This document provides basic information on the standards and technologies. For more information about the standards and technical specifications.Connectivity Fault Management  IEEE 802.1ah .1ag .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.

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

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

Establish end-to-end OAM. data center interconnection. including transparent LAN access. video conferencing. 12 . QoS performance and realtime visibility. assuring end-to-end SLA performance while providing individual performance metrics for each Operator Virtual Connection (OVC). 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. remote storage and transactional services with carrier-grade availability. VoIP. QoS-optimized EVCs. A MetroNID unit effectively establishes E-NNI handoffs and reaches remote customer sites with complete control and visibility.Assured Business Services Accedian enables and assures SLA-backed business services.

technologies and manufacturers—in-line and in real-time— without affecting customer traffic. 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 . with Accedian Networks' SLA-Meter™. providing end-to-end control over real-time applications. filtering and switch-free aggregation for each Class-ofService. Enterprise WAN QoS Accedian‘s applications for the Enterprise optimize WAN performance and accelerate critical business applications with traffic shaping. peering fabrics.Carrier Ethernet Global Interconnect Deploying Accedian‘s MetroNID units at the ENNIs joining multiple operator networks enables performance assurance for services spanning multiple carriers. Accedian Networks‘ delay-free and delay-variation-free demarcation solutions bridge segments and monitor network boundaries.

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. Optimize service and core network performance with hardwarebased rate limiting. traffic shaping. 14 .

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

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

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

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. Test up to 100 sites from a single EtherNID or MetroNID demarcation unit. frame loss and availability monitoring. refer to the chapter Monitoring Network Performance. For more information about PAA. 18 .

refer to the chapter Managing Traffic. Performance is fully transparent over multi-manufacturer. 19 .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™. multi-carrier. For more information about SLA Assurance. multi-technology networks.

Create. filtering and switch-free aggregation at the intelligent access edge. enables the units to maintain EVCs at GbE and 10-GbE speeds without introducing delay or delay variation to critical. For more information about service creation features of Accedian‘s EtherNID and MetroNID. optimize and manage Ethernet services with per-flow service mapping.com. the industry‘s only wire-speed performance assurance agent.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. Multi-technology networks EVC service mapping functionality transparently creates Ethernet LAN services and avoids interoperability issues. traffic shaping. Optimize service and core network performance with wire-speed traffic conditioning and flexible rate limiting. real-time traffic. accelerate. 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. E-LAN and E-Tree services with EVC service mapping: advanced networking functionality is built right into EtherNID and MetroNID units designed for customer. aggregation and head-end sites. Easily configured remotely. traffic shaping. Quickly create Ethernet Virtual Connections (EVCs) for E-Line. Accedian‘s unique Fast-PAAs engine. refer to Accedian‘s website at www. building EVCs is as simple as installing EtherNID units at the demarcation points and provisioning services from the web. 20 . media or protocol. cell. Leverage real-time multi-port aggregation and bypass switches altogether. filtering and bandwidth policing directly at the demarcation point and bypass costly switches upgrades.accedian. 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.

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

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. 22 . refer to the chapter Managing Traffic. 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.

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

hardware-based traffic shaping that passes critical. reduce network overhead. while standard traffic is priority-queued. 24 . real-time traffic at wire-speed using the Fast-PAAs zero-delay cut-through queue. and economize bandwidth with advanced.Traffic Shaping Accelerate low delay services. refer to the chapter Managing Traffic. shaped and forwarded. 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. The elements of a typical user interface screen are shown in the following figure. 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. or Internet Explorer 6. second and third level menus Working Area Write lock Logout 26 . Typical Screen Date and time Alarms First. via an SSL client. to all system control. management and monitoring functions.About the Management Web-Interface The web-based management interface provides secure access.0 or higher.

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

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

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

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

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

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

proceed as follows: 7. 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. For more information on specific parameters. ACP: Only proprietary Accedian format is supported for now. refer to the table Interface Settings (System > Configuration > Interface). Configure the Auto interface of the remote units to listen for Beacon frames in the Discovery settings parameters. 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. 40 . Click the Interface name to edit it. Configuring a Logical interface for Beacon You can configure a logical interface to use Beacon frames. When enabled. Note: if the interface configured for beacon is part of a bridge. To add or edit a route. Go to System > Configuration > Interface. The frame format to use when sending information 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. the advertisement transmission rate matches the rate that is configured in the beacon settings. The advertisement transmission rate to use when the beacon rate option is disabled.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 sending the Beacon frames. Refer to Managing Network Inventory. Fill in the required field of the Beacon settings section and click Apply. the central unit or the Beaconner. 8. To configure a logical interface for Beacon advertisement. Go to System > Configuration > Interface. 9. Configure only one unit in your network. proceed as follows: 1.

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

Refer to the CLI Command Manual for information on the CLI. Click Enable console or Disable console as required. 42 . To enable or disable the console port. Number of hops to try: 1–30. 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. 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.Ping (System > Maintenance > System tools) Parameter IP address timeout Description IP address to PING. 2. To use the console port. Number of PING messages to send: 1–10 Traceroute (System > Maintenance > System tools) Parameter IP address Hops Description IP address to TRACEROUTE. Go to System > Configuration > Console. The console port provides a CLI interface to the unit. Verify the current state of the console port in the console state field. you can enable or disable the console port. 3. After logging in. proceed as follows: 1.

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 MAC address of the remote unit port that sends advertisement frames.g. This displays a table of all units that have advertisement enabled to send an information frame on the network. AMN-1000-TE. e. proceed as follows: 1. Click Enable inventory tracking and click Apply. For more information on specific parameters. 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. 2. refer to the following table. The MAC address associated with the unit. The type of remote equipment. The advertisement frames are added to inventory only if they are received on a port that has an interface with the beacon state enabled. Go to Show > Inventory. 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. you must disable the advertisement frame to be able to see the inventory of all units advertising on this interface.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). as displayed in the Home tab. Note that if the interface configured for beacon is part of a bridge. 44 . The domain ID that was used in the discovery process to configure this unit. To view a network inventory. Filter advertisement frames based on the beacon configuration state of the unit interfaces. Discovery config and inventory (Show > Inventory) Parameter Enable inventory tracking Enable advertisement frame filtering Description Enables the gathering of discovery inventory.

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

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

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

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

Maximum number of seconds that a CLI 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. go to System > Session > Management. The telnet server on the NID may be enabled or disabled. 2.To terminate a session. The session is immediately terminated and the current user is logged out. Enter the different session configurations parameters and click Apply. Go to System > Session > Configuration. select the session you want to terminate by checking the Terminate check box and the Terminate button. Maximum number of management tool sessions that are supported at the same time. 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. 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 . Maximum number of seconds that a management tool session can remain idle before it is automatically logged out. Total number of CLI and WEB sessions that are supported at the same time. You will then see the screen displayed in System > Session > Configuration. For more information on specific parameters. refer to the following table. proceed as follows: 1.

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

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

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.       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 . Privileges given to the user permission group allow a member to edit. refer to the following table. Config: Import/Export configuration files  configuration Filters: Edit/Add L2 filters. add or enable within these sections.For more information on specific parameters. service mapping. IPv4 filters. traffic shaping and regulators. Group Privileges (System > Session > Permissions) Parameter Group name Privileges Description User permission group.

refer to the following table. For more information on specific parameters. 53 . fill in the fields and click Apply. Click the Add button or click the User name if you want to edit a user account. proceed as follows: 1. This displays all user accounts that exist for the unit. 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. 3. refer to the table at the end of this procedure. In the [User name] user settings page. For more information on specific parameters. 2. Go to System > Sessions > Users.Parameter Description OAM: Edit/Add/Enable OAM. Adding or Editing User Accounts To add or edit a user account.

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

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

The permissions tokens are case sensitive. permissions are set to viewer only. Service-Type (id=6): Provides for full admin privileges if attribute is set to "AdministrativeUser". The permissions are the same as those that can be configured locally on the unit.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. Notes: You cannot view RADIUS assigned permissions with the CLI or webbased interface. Users" Grant full administration privileges (Same as first example): Service-Type = "AdministrativeUser" 56 . They can be a mix of locally-defined user permission groups and individual privileges. See also Managing Users and Privileges. A member of the built-in Admin group: Callback-Id = "Admin" A list of individual privileges: Callback-Id = "Config Firmware Log Management. If the attribute is valid (valid Callback-Id or valid Service-Type) then the permissions are set to:   If the username exists locally. If the username does not exist locally. local permissions are assigned to the user. not for the unit. The list of tokens is separated by spaces or commas.

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. Aggregator 2x1 Mode Aggregator 2x1 mode is for one protected network port aggregated with two client ports. The number of VID sets also depends upon the model of NID. Note: The media-selection option does not apply in Aggregator 2x1 mode. This mode provides one client port and one network port. You can assign port function (network port or client port) with the media-selection option. The operation mode affects the number of traffic policies and the number of VID sets. as explained in Setting up Media-Selection on page 76. 57 . Standard Mode Standard mode is for standard network interface device functions.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. You can assign port function (network or net-protection) with the port protection option. each for a different network architecture. Refer to Setting up Traffic Policies on page 100 and to Setting up VID Sets on page 101.

 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-D policies are associated with the network port. The traffic shaper also behaves in a specific way in Aggregator 3x1 mode. as described in Understanding Traffic Shaping on page 118.  Traffic-C policies are associated with the Client-3 port. Note: The media-selection option does not apply in Aggregator 4x1 mode.  Traffic-B policies are associated with the Client-2 port. Port Configuration for Aggregator 4x1 Mode Aggregator 4x1 mode modifies traffic policies as follows:  Traffic-A policies are associated with the Client-1 port. 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.Aggregator 2x1 mode also modifies traffic policies as follows:  Traffic-A policies are associated with the Client-1 port. Refer to the figure below for the port configuration.  Traffic-C policies are associated with the network port. 58 .  Traffic-B policies are associated with the Client-2 port. Aggregator 4x1 Mode Aggregator 4x1 mode is for one network port aggregated with four client ports. as described in Understanding Traffic Shaping on page 118. The traffic shaper also behaves in a specific way in Aggregator 2x1 mode. Aggregator 3x1 Mode Aggregator 3x1 mode is for one network port aggregated with three client ports.

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

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

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

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

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

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

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

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

Release the Bypass button. CPU usage average from the last completed period of 60 seconds.For more information on specific parameters. Go to System > Maintenance > Firmware. Restarting the Unit To restart the unit. To reboot the unit. Press and hold the Bypass button on the rear panel of the unit. press and release the Loopback button. CPU usage over the last 100 seconds presented as a graph. 2. 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. Simultaneously. 2. CPU usage average from the last completed period of 5 minutes. It applies changes in the unit’s configuration and affects current operations. CPU usage over the last second. 3. The unit will restart. 71 . 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. refer to the following table. Click the Reboot button. proceed as follows: 1. CPU usage average from the last completed period of 15 seconds. CPU usage average from the last completed period of 30 seconds. proceed as follows: 1.

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

refer to the following table. Note: The page varies depending on whether you are setting up a copper port or an SFP fiber port. proceed as follows: 1. 3. 2.Managing Ports This chapter describes how to manage the ports. This displays a list of all ports and their status. Define port parameters as required by your setup and then click Apply. Grey: the port is disabled. Go to Port > Configuration. refer to the table below. For more information on specific parameters. Red: the port is enabled but the physical link is down and no signal is detected. For more information on specific parameters. 73 . To view ports or set up a port. Yellow: the port is not totally functional. Click the Port name to edit its settings. link speed (auto-negotiation) and flow control. Port State The port may be enabled or disabled. Port Configuration (Port > Configuration) Parameter Status Description The following colours indicate port status: Green: the port is up and running. 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).

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

The protecting port is reserved by the protection mechanism and can not be used for monitoring purposes while protection is enabled. Revertive When enabled. Protection Mode Switching protection to a standby connector can be based on Link status or LACP status. Note that this parameter is available on the network port only. This is available for link status protection mode only. Working connector The working connector for the specified port. Note that protection is available on the network port only. the system switches back to the working connector. The name of the port from which faults are propagated. 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.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. 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. Note that this parameter is available on the network port only. The timer is restarted if a signal loss is detected during this period. Enable fault propagation Fault propagation mode Enables the propagation of link faults between the ports specified in Propagate from port. traffic is switched back to the main connector after the revert period has expired. when both ports are working. Note that protection is available on the network port only. the traffic reverts to the working connector. Protection Enable Enable protection for the port selected in the working connector. If LACP status is selected. 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. disable: pause frames are disabled. you must create an L2PT rule with an operation mode of ―Peer and Protocol LACP‖ on this port in order to terminate LACP packets. Propagate from port Flow control 75 . One-way link: Propagate faults in one direction based on the link status of the opposite port. In revertive mode. Choosing the connector when enabling the protection allows you to perform a switchover operation. If the timer (link time out) expires and the link stays down. This is available for only link status protection mode and only on the network port.

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

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

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

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

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

no PHY errors and no FIFO errors. The count includes the four CRC bytes (if present) but does not include the preamble or SFD bytes. The total number of large packets transmitted by this port. Receive statistics Bytes good Count of the total number of bytes received by the port in good packets. Number of errors received. Good packets are described above. A packet is error-free if it has a valid CRC. Packets with PHY or FIFO errors are not counted.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. Packets 1024 and above are only available on certain types of units. Bytes in bad packets resulting from a collision are counted if the SFD is detected. 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. Octets in otherwise good packets with a dribble nibble are included in this count. transmitted by this port. Count of error-free packets received on this port that are shorter than 64 bytes. Define the size of large packets from Port > Configuration > [port name]. Count of error-free packets received that are longer than MTU configured on the port. A packet is error-free if it has a valid CRC. long packets (greater than MTU configured on the port). packets with bad CRC. packets with PHY errors and packets with receive FIFO errors. 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). Bytes total Rcv packets Rcv errors Short OK Short bad Long OK 81 . Count of the total number of bytes received by the port in good and bad packets. Count of packets received on this port that are shorter than 64 bytes and have a bad CRC. Bad packets include short packets (less than 64 bytes). no PHY errors and no FIFO errors. good or bad. The count includes the four CRC bytes but does not include the preamble or SFD bytes.

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

normally sized) with an unknown opcode. Packets 1024 and higher are available on only certain types of units. Count of the number of received packets dropped or aborted due to receiving a FIFO overflow. Unknown control packets are identified by a type field of 88-08 and an opcode field not equal to 00-01. 83 . Count of the number of received packets that have been ignored by this port.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). The total number of packets. 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. that were exactly 64 bytes in length (excluding preamble and SFD but including CRC). received by this port. The FIFO overflow error takes precedence over all other errors: if this counter is incremented. The preamble rules include long preamble enforcement (greater than 23 nibbles) and pure preamble enforcement (only 55h bytes). A packet is ignored if it violates the programmed preamble rules or if it violates the minimum data gap. The normal data gap is 20 bytes long (12 bytes of IPG and 8 bytes of preamble/SFD). then none of the other packet counters is incremented. no PHY or FIFO errors. Count of the good control packets received by this port (good CRC. Define the size of large packets on the Port > Configuration > [port name] page. Packets with a FIFO error are not counted. The total number of packets. that were 65 to 127 bytes (or the other length) in length inclusive (excluding preamble and SFD but including CRC). The enforcement limit is set to 10 bytes (half the normal gap length). 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. good or bad. received by this port. good or bad.

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

Possible values are:  Other  Configuring  Complete  Disabled  Parallel Detect Fail Each of the above values may be With auto or Without auto.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 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 abilities of the link partner. 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.

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

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

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

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

IP Precedence or PCP. and CF). CM. are enforced via a token bucket algorithm according to Technical Specification MEF 5. EBS. bandwidth profiles. 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. per flow: upstream and down. CoS mapping. EIR.1. CBS. or EBS.Managing Traffic This chapter describes how to create and manage Ethernet services. Bandwidth Policing (also referred to as Rate Enforcement or Bandwidth Regulation): Bandwidth profiles. 90 . refer to the chapter on Monitoring Network Performance. e. Bandwidth policing: sets rate limiting based on the bandwidth profile defined for the selected flow: CIR. Bandwidth profiles can be used to offer bandwidth to your client according to predefined SLAs. per-circuit. It also explains how to configure some of the service attributes for the created services. etc. You can also specify. E-LAN and E-Tree services as described in MEF 6. E-LAN and E-Tree services by mapping traffic to an Ethernet Virtual Connection (EVC). which are defined by the values of their associated parameters (CIR. CBS.g. 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. The services you can create are: Ethernet Service Mapping: Create E-Line. The Bandwidth policing assures SLAs by regulating committed and excess information throughput. Layer-2 control protocol processing options. EIR. For the definition and monitoring of the service performance attributes.

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 .

Refer to your unit’s datasheet for the maximum number of specific filters possible for traffic policies. 92 . 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. or sent for service mapping.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. VLAN settings and DSCP for Layer-2 filters. This way. 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. or based on IPv4 Header settings. CoS mapping and/or bandwidth policing. Defining Filters You can set up a specific filter (layer 2 or IPv4) and use this filter for loopbacks or for traffic policies. ICMP settings and VLAN settings.

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

This should always be set to zero for connection to Ethernet switches. The other bits are ignored. For instance. Ethertype Protocol may be selected or entered manually (hexadecimal). The other bits are ignored. Only the bits specified by the mask are used. VLAN priority allows the provision of CoS prioritization using the standard 802. 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. If a frame received at an Ethernet port has a CFI set to 1. the other needs to be set to Equal to. CFI is used to ensure compatibility between Ethernet networks and Token Ring networks.1Q priority tag. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). The source MAC address and mask. 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. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN).Parameter Description Ethernet header settings MAC destination / mask The destination MAC address and mask. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Priority 94 . Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range. then that frame should not be forwarded "as is" to an untagged port. Only the bits specified by the mask are used.

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.Parameter VLAN ID VLAN 1 VLAN 2 Description VLAN ID to use for filtering traffic. 95 . DSCP/IP precedence DSCP/IP precedence DSCP/IP precedence operator. Valid operator types are: Greater than Less than Equal to Range (inclusive range). if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN). For instance. the other needs to be set to Equal to.

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

Specify a value in the range of 5–15. UDP (17) and ICMP (1). You should ensure that all IP addresses specified in a filter are static or reserved. The other bits are ignored. Common protocols are TCP (6). Destination address and mask. SNMP and RIP. Telnet and SMTP. TCP is used by HTTP. 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 . Only the bits specified by the mask are used. Time-to-live value. The protocols available. Explicit Congestion Notification. Header length in 32-bit units. Otherwise you must have to manually update your filter every time the addresses change.Parameter Description Control Protocol (DHCP) can cause problems. in the format of ―protocol name (port number)‖. Note that filtering source or destination IP address assigned by Dynamic Host Control Protocol (DHCP) can cause problems. Protocol may be selected from the list or a manually entered port number (decimal). Specify either 0 or 3. FTP. ICMP is used by Ping. You should ensure that all IP addresses specified in a filter are static or reserved. UDP is used by DNS. Otherwise you must have to manually update your filter every time the addresses change.

Other ICMP Code: See www. Interpretation is based on the carrier's equipment and administrative The source port used to match this rule. 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 ICMP (1). Specify the ICMP message type for this filter to match. Priority 98 . This should always be set to zero for connection to Ethernet switches. These settings are valid only when the Protocol is set to TCP (6) or UDP (17).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. Echo (8) and Time Exceeded (11). This setting is valid only when the protocol field is set to TCP (6) or UDP (17). then that frame should not be forwarded "as is" to an untagged port.iana. The destination port used to match this rule. If a frame received at an Ethernet port has a CFI set to 1. VLAN priority allows provisioning CoS prioritization using the standard 802.1Q priority tag. CFI is used to ensure compatibility between Ethernet type networks and Token Ring type networks.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. Some well-known ICMP types are Echo Reply (0). Destination Unreachable (3). Redirect (5).

VLAN ID VLAN ID used to filter traffic. 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. the other needs to be set to Equal to. Valid operator types are: Greater than Less than Equal to Range (inclusive range) The possible values for each operator are: 0 to 7.Parameter Description policies. For instance. if you select a Range for the second VLAN (VLAN in VLAN) you need to select Equal to for the first VLAN (VLAN). 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). 99 . 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). For instance. Note that you can set only one VLAN (VLAN or VLAN in VLAN) to a range.

Create the service (See Setting up Traffic Policies) :  Select the filter that you defined in the first step. VLAN ID)  CoS Mapping (PCP action. The major steps required to create or manage services are: 1. CoS profile or default mapping)  Bandwidth profile (Regulator set if CoS Mapping is Preserve or Map. See Defining Filters. Three different types of filters can be defined:  Layer-2 filters and IPv4 filters.Setting up Traffic Policies You can create and manage Ethernet services through the Traffic menus.  Define Bandwidth regulator sets. See Setting up Bandwidth Regulator Sets 3. Type. Ethertype. 2. See Setting up CoS Profiles. Define service attributes:  Define bandwidth profiles. See Setting up Bandwidth Regulators. 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 . 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. See Setting up VID Sets. IP Precedence or PCP values of the ingress frame. 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). bandwidth profile or filters).  VID Sets.  Define CoS mapping: Sets VLAN priority based on DSCP.  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.

Refer to the section Understanding Operation Modes on page 57. 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. Setting up VID Sets You can define VID sets for each traffic stream (Traffic-A.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. 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 . Traffic-C and Traffic-D) to classify the incoming traffic before sending it to the service creation function.

you can apply it to traffic policies as a filter (See Setting up Traffic Policies). Traffic-A. you also need to select the VLAN (inner or outer VLAN) for filtering the traffic for each policy list.g. VLAN Filtering You can create VLAN filters using the VLAN type field (S-VLAN or C-VLAN) and VLAN ID or range.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. See Selecting VLAN or VLAN-in-VLAN filtering). 102 . e.

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

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

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

refer to the following table. color-blind: All incoming traffic enters the traffic regulator initially green. Traffic that is declared green and that conforms to CIR or CBS is allowed to pass through the Policer without rate limitation. none are defined initially.1. Go to Traffic > Regulators > Configuration. False: Yellow data is limited by the setting of the Excess Information Rate. 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. The burst size must be greater than the port Maximum Transfer Unit (MTU). 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. Green traffic in excess of this maximum is declared yellow by the regulator and is submitted to EIR regulation. 2. refer to the table at the end of this procedure. Coupling Flag The way in which the regulator processes yellow traffic. 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. 3. By default. Yellow traffic in excess of this maximum is declared red by the regulator and is dropped. 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. This displays a summary of all existing bandwidth regulators. color-aware: Pre-determined level of Bandwidth Profile compliance for each Frame is taken into account when determining the level of compliance. For more information on specific parameters. Click the Add button to add a new bandwidth regulator or click the name of an existing bandwidth regulator to edit its settings. For more information on specific parameters. 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. Fill in the required fields and click Apply. 106 .

you can apply it to Traffic policies for CoS mapping and bandwidth policing. four commonly used profiles are set up. This displays existing CoS Profiles. If the CoS profile is a DSCP. Fill in the required fields and click Apply. 2. For more information on specific parameters. Click the Add button to add a new CoS profile or click the name of an existing CoS profile to edit its settings.Parameter Description True: Yellow data is limited by the setting of the Committed Information Rate plus the Excess Information Rate. CoS Profile Configuration (Traffic > Mapping > CoS profiles) Parameter Name Type Description Name identifying the CoS profile.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. N=64. Specifies which incoming packets are going to be mapped to the CoS. Go to Traffic > Mapping > CoS profiles. IP precedence: IP precedence mapping 107 . 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. To set up a CoS profile. 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. proceed as follows: 1. 3. By default. refer to the table at the end of this procedure. where N depends on the type of the CoS profile. For more information on specific parameters. Type may be one of the following: PCP: Priority Code Point mapping. you need to assign in the mapping table. refer to the following table. To set up the CoS profile. The mapping table has N rows. If the CoS profile type is PCP or IP precedence then N=8. See Setting up Traffic Policies.

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. This value is selected if:  the result of the bandwidth regulator assigned to this entry is green.1Q-in-Q tags IP precedence: IP precedence bits in IPv4 TOS byte DSCP: DSCP bits in IPv4 DSCP byte 108 . 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). the DEI is set to 0. 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. This value is selected if:  the result of the bandwidth regulator assigned to this entry is yellow. or  the pre-marking color is yellow and no bandwidth regulator is assigned to this entry. CoS value (0-7) for use in the outgoing green frames. This parameter is only available when PCP CoS profiles type is selected. or  the pre-marking color is green 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. Otherwise. IP precedence or DSCP type frame. The number of policies that are currently using this CoS profile. Encode using DEI This makes the unit Control the DEI bit in an S-VLAN tag.1Q / 802. otherwise. the user defined pre-color is used. If this field is checked and the outgoing frame is marked yellow then the DEI bit is set to 1. 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. IP precedence or DSCP value. CoS value (0-7) for use in the outgoing yellow frames.

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

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

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

Options for the PCP Action MAP Parameter Type First choice PCP VLANinVLAN PCP VLAN IP precedence. Click the name in the Policy lists to view the summary of the policy configurations of a particular port. DSCP IP precedence. 112 . Map Use this option to map and regulate traffic based on PCP. For more information on specific parameters. The pre-marking color red is ignored if the default bandwidth regulator is disabled. 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. The table below shows the valid configurations of the first and second choices. The first and second choices can be used. refer to the following table. Filters based on VID sets use direct access to identify the corresponding policy for an incoming frame. IP precedence.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. Note: The first and second choices are ignored. DSCP CoS profile BWR set CoS profile Optional Second choice PCP VLAN. 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 PCP VLAN.

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

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

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

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

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

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

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

The traffic of each shaper then goes to the network port shaper. For each client 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 . Note: There are three sets of queues. In the direction from the client ports to the network port: 1. 3. You set up this shaper from Traffic > Shaping > Traffic shaper configuration. You set up this shaper from Traffic > Shaping > Traffic shaper menu > Port. The queued traffic of each client port next goes to its shaper and CIR for this client is applied. Queue-2 and Queue-3.Shaper for Aggregator 3x1 Mode Traffic shaping in Aggregator 3x1 mode is available for client-to-network traffic. 2. If there is more traffic to send out than the port‘s total bandwidth can manage. Queue-1. 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. You set up this queue from Traffic > Shaping > Traffic shaper configuration. one set for each client port.

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

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

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

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

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

The shaping burst (in Bytes) of yellow packets (maximum output burst of the shaper). 126 . the pm will be decreased. Once the queue empties to the specified percentage. The marking probability is decremented by this value if the link is idle. proceed as follows: 1. The buffer is used to queue the packets in order to be transmitted later. The shaping burst of yellow packets expressed as a multiple of 256 Bytes Queue management parameters Q-length Buffer's size in KB. the pm will be increased. Once the queue fills to the specified percentage. The management of this buffer is done by the management queue algorithm BLUE.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. See Setting the PCP-to-Queue Map. This is done using the traffic-shaper PCP map. 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 BLUE algorithm is disabled. The marking probability is incremented by this value if there is a buffer overflow. You can verify that this has been done correctly by viewing PCP lists for the real-time queue. The shaping rate of yellow packets expressed as a multiple of 125 Kbps. The shaping burst of green packets expressed as a multiple of 256 Bytes. Viewing the Real-time Queue PCP Lists The real-time queue is used to bypass the traffic shaper. Go to Traffic > Shaping > Traffic shaper configuration. To view the real-time queue. The shaping burst (in Bytes) of green packets (maximum output burst of the shaper). If this parameter is set to 0. The shaping rate (in Kbps) of yellow packets (average output rate of the shaper).

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

all PCPs are green. EIR In the summary page. 128 . Total bandwidth Total yellow Total green CIR The total number of yellow packets/bytes and rate (in Mbps) forwarded by this shaper. this is the instantaneous rate (in Mbps) of green packets. 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. In the summary page. Total number of packets/bytes and rate (in Mbps) dropped due to the shaper's queue overflow. Note that the Cfg value is the EIR you have configured (in Mbps). Total number of delayed (enqueued) packets/bytes and rate (in Mbps) forwarded by this shaper instance. Total number of packets/bytes and rate (in Mbps) forwarded by this shaper without any delay. Note that the Cfg value is the CIR you have configured. this is the instantaneous rate (in Mbps) of yellow packets. In the detailed page. By default. this is the total number of packets/bytes and rate forwarded by this shaper using the EIR bucket. expressed (in Mbps). Description The name assigned to this shaper. In the detailed page. this is the total number of packets/bytes and rate forwarded by this shaper using the CIR bucket. Total number of packets/bytes and rate (in Mbps) dropped by the queue management algorithm (BLUE). The total number of green packets/bytes and rate (in Mbps) forwarded by this shaper. this value is only shown when the port's global CIR is enabled. The rate (in Mbps) of dropped green packets. For the real-time shaper. This value is not available for the real-time shaper. The rate (in Mbps) of dropped yellow packets.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.

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

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

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

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

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

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

For more information on specific parameters. Description The OAM instance name. 135 . Note that this field does not indicate a successful discovery of an OAM peer. Check the appropriate check box to enable this field. you must create an OAM instance. 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. OAM Instances (OAM > Configuration) Parameter Name OAM instance name OAM state Enable OAM protocol Enables the passive or active OAM 802. fill in the required fields and click Apply. Setting up an OAM Instance Before using Ethernet OAM functions or enabling a loopback. For more information on specific parameters. 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. 2.3ah protocol for this OAM instance. To set up an OAM instance. refer to the following table. 3. This displays a summary of all OAM instances set up. An active instance immediately starts sending information OAMPDUs associated with the discovery process. Go to OAM > Configuration.Monitoring Network Performance The unit allows for monitoring network performance using a proprietary technology and two standard protocols. upon which the loopback is created. proceed as follows: 1.

Using a number of frames instead of a time period. When Enabled. short frames.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. long frames. When Enabled. or MAC level. Port used by this OAM instance. This enables you to limit the impact of the extra OAM traffic on a link that is already heavily loaded. 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. The window setting defines the time (in seconds) of the period. as in EFE. but not limited to the following: CRC errors. 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. A frame error is an error detected at the layer 2. Indicates whether OAM packets are tagged with a VLAN. long frames. 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. level. the unit responds to loopback requests from the OAM peer. etc. but not limited to the following: CRC errors. This setting is valid only if This unit supports events is enabled. This can be caused by various types of errors including. Number of times an event is re-transmitted to ensure its reception by the peer. This can be caused by various types of errors including. the unit responds to OAMPDUs requests. or MAC. short frames. the unit issues event OAMPDUs when needed. A frame error is an error detected at the layer 2. Active: Immediately searches for an OAM peer by sending OAMPDUs. For encapsulated packets only Maximum frame size for the OAM instance. When Enabled. etc. Errored Frame Period Event (EFPE) Threshold and window 136 .

In other words. The number of OAM events received. Viewing OAM Events To view a summary of all event exchanges on an OAM connection. 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. 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. The number of transmitted OAM events that were duplicated. but not limited to the following: CRC errors. click the OAM instance Name in the list. level. For more information on specific parameters. long frames. An errored frame second is a one-second period in which at least one frame was bad. A frame error is an error detected at the layer 2. This can be caused by various types of errors including. For more information on specific parameters. refer to the table below. 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. of the period. For complete details on transmitted and received events. etc. EFPE or EFSSE fieds Received event notifications 137 . short frames. EFSSE  Event values: EFE. The window setting defines the time. in seconds. EFPE. The number of received OAM events that were duplicated. or MAC. go to OAM > Events. refer to the table below.

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

Vendor OUI Vendor specific info The value of the OUI variable in the Vendor Identifier field of the most recently received information OAMPDU. go to OAM > Statistics. Note that these states will change when a loopback is enabled. 139 .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 value of the Revision field in the Local Information TLV of the most recently received information OAMPDU.  The fourth bit corresponds to the Local Evaluating bit in the Flags field. For example. etc. The first and second bits correspond to the Parser Action bits in the State field.  The fifth bit corresponds to the Local Stable bit in the Flags field.  The third bit corresponds to the Critical Event bit in the Flags field.  The first bit corresponds to the Link Fault bit in the Flags field. a hex value of 0x0004 converted to binary is 0000100: first bit = 0. third bit = 1. Viewing OAM Statistics To view a summary of the statistics of each OAM instance. For more information on specific parameters. second bit = 0.  The sixth bit corresponds to the Remote Evaluating 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. For detailed OAM statistics.  The seventh bit corresponds to the Remote Stable bit in the Flags field.  The second bit corresponds to the Dying Gasp bit in the Flags field. refer to the table below. refer to the table below. This value is updated upon reception of a valid frame. For more information on specific parameters. The third bit corresponds to the Multiplexer Action bit in the State field. click the OAM instance Name in the list. The value of the Vendor Specific Information field of the most recently received information OAMPDU. The seven LSB bits are expressed as a hexadecimal value.

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

 LengthOrType value equal to the reserved Type for slow protocols. Organization specific A count of OAMPDUs received that contain the Organization Specific code.  The OAMPDU code equals the Loopback Control code and is supported by the device.  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. 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. Loopback control A count of OAMPDUs received that contain the Loopback Control code. This counter is incremented upon reception of a valid frame.Parameter Duplicate event Description A count of the OAMPDUs received that contain the Event Notification code. 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.  LengthOrType value equal to the reserved Type for slow protocols.  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.  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. 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 Event Notification code. Generalized non-resettable counter.  A slow protocols subtype equal to the subtype reserved for OAM. Variable response A count of OAMPDUs received that contain the Variable Response code. This counter is incremented upon reception of a valid frame with the following:  DestinationField equal to the reserved multicast address for slow protocols. Variable request A count of OAMPDUs received that contain the Variable Request code. 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. 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. with: 141 .  The Sequence Number is equal to the Sequence Number of the last received Event Notification OAMPDU.

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

packet loss and continuity check. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. A count of transmitted OAMPDUs containing the Variable Request code. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Response OAMPDU. Two units with matching settings communicate with each other using measurement samples to collect data and measure system performance. Generalized non-resettable counter. using a different class of service (CoS) and/or VLAN ID as appropriate. delay variation (jitter). 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). 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. Variable request Variable response A count of transmitted OAMPDUs containing the Variable Response code. 143 . The PAA™ is capable of concurrently testing and maintaining multiple flows of active probes. Organization specific A count of transmitted OAMPDUs containing the Organization Specific code. When such a packet arrives at its destination. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. Generalized non-resettable counter. These packets may be independently destined to different peers or to the same peer.1Q-in. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Request OAMPDU. The PAA™ operates continuously. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating an Organization Specific 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.Parameter Description 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 (. Generalized non-resettable counter. measurements (delay.1Q). A measurement sample is a packet containing timing and sequence information. delay variation and packet loss) can be taken.

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

Local and Peer Indexes Local Index Remote Index Local identifier for the probe. Associated: Enabled peer index resolved. layer-2 PAA packets are encapsulated into the specified VLAN ID. 145 . When you add a PAA instance. 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. Second VLAN ID. layer-2 peer address automatically finds the peer MAC address. Second VLAN Ethertype: C-VLAN or S-VLAN. Applies only when VLAN 1 ID is enabled. 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 VLAN. First VLAN Ethertype: C-VLAN or S-VLAN. Encapsulate layer-2 PAA packets into a VLANinVLAN. 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. EVC client port to which the MEP status should be propagated. When 0 is specified. When set to FF:FF:FF:FF:FF:FF. Second VLAN priority bits. First VLAN priority bits. Remote peer identifier. UDP parameters (for UDP probe only) Destination IP address Peer IPV4 Destination address. Peer MAC address.Parameter Description Disabled: Disabled by configuration. 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. First VLAN ID. Applies only when VLAN 1 ID is enabled. Applies only when VLAN 2 ID is enabled. Associating: Enabled and looking for peer. layer-2 PAA packets are encapsulated into a second VLAN. 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. When enabled. Applies only when VLAN 2 is enabled. When enabled.

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

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

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. Click Delete. 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.Parameter Maximum join delay Description  Maximum: One-way reference period – (5 * sampling period) The maximum join delay objective. Click the probe name to delete. 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. 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. Possible values (in msec):  Minimum: 100 msec  Maximum: (One-way reference period) – (One-way join period) Deleting a Probe 1. 3. Possible values (in msec):  Minimum: 100 msec  Maximum: One-way join period The maximum leave delay objective. Go to PAA > Configuration. 148 .

For more information on specific parameters. PAA Status (PAA > Status) Parameter Name Probe name Index State The unique identifier assigned to the probe. Peer address Status codes The address of its peer PAA probe (L2 and L3). Click a probe name to view its detailed information. refer to the table PAA Status (PAA > Status). go to PAA > Status. Associated: Enabled peer index resolved. The probe's current state. 149 . To view the status of all PAA probes.Viewing Probe Status 1. Possible values are: Disabled: Disabled by configuration. 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. Associating: Enabled and looking for peer. refer to the following table. 2. It also gives detailed state information about local and remote clock synchronization status that is used for one-way measurements. For more information on specific parameters.

To view a summary of all PAA probe results. Percentage of samples lost in the period.Viewing Probe Results 1. refer to the table below. PAA Results (PAA > Results) Parameter Current results for probe Probe name Index State The unique identifier assigned to the probe. Click a probe name to view detailed results of a probe. Associated: Enabled peer index resolved. go to PAA > Results. For more information on specific parameters. Associating: Enabled and looking for peer. Largest number of consecutive frames that are missing. Possible values are: Disabled: Disabled by configuration. Number of gaps registered in the period. The current period is indicated on the right of Packet loss. Description The name of the probe. 2. The probe's current state. 150 . 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. 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. Number of samples Loss ratio Number of gaps Largest gap size One-way delay Total number of samples in the period.

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

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

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

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

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

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

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

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

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

Active (A) or Inactive (I). Active (A) or Inactive (I). 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. 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 latest CCM received by this MEP from a remote MEP containing the Remote Defect Indication (RDI) bit. Active (A) or Inactive (I).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. Some packet loss measurement defect is active (A) or inactive (I) for that MEP. 160 . The MEP is receiving invalid CCMs.1731 Alarm Indication Signal (AIS) PDUs are received. The MEP is not receiving CCMs from a MEP in its configured list. Active (A) or Inactive (I). Indicates whether Y.

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

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

Description Index assigned to the maintenance association end point. The number of connectivity check messages sent by this MEP with the RDI bit set. refer to the following table. The number of linktrace responses sent and received by this MEP. Go to CFM > MEP > Statistics to view the statistics summary of all MEPs. 163 . For more information on specific parameters. The number of delay measurement responses sent and received by this MEP per VLAN priority. The number of connectivity check messages received by this MEP. Maintenance association end point Identifier. The total number of out-of-sequence CCMs received from all remote MEPs. refer to the table below. Click any MEPID to view detailed statistics of this MEP. The number of linktrace messages sent and received by this MEP.Parameter Description Not present (6) Lower layer down (7) Viewing MEP Statistics To MEP statistics. 2. For more information on specific parameters. The number of connectivity check messages received by this MEP with the RDI bit set. The number of delay measurement messages sent and received by this MEP per VLAN priority. 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. 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.

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

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

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

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

proceed as follows: 1. The remote Maintenance association End Point Identifier. Description The delay measurement's unique identifier. For more information on specific parameters. Time (in ms) at which this Delay measurement instance issues DM frames. refer to the table MEP Loopback (CFM > MEP > LBM). 3. Go to CFM > MEP > LBM. refer to the following table. Note: One-way delay measurements require time synchronization. 2. For more information on specific parameters. The local Maintenance association End Point Identifier. 168 . Click Add to create a DMM instance or click the DMM instance name to edit an existing DMM instance. Enables sending DMM frames at the specified interval.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. Go to CFM > DMM > Configuration. in the transmitted frame. refer to the table at the end of this procedure. For more information on specific parameters. This displays all the existing Delay Measurement Instances. 2. Click the MEPID of the MEP for which you want to view LBM information. if present. 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. proceed as follows: 1. on units at each probe end. Viewing Loopback Messages Information To view the loopback messages information. Fill in the required fields and click Apply. The index assigned to the Maintenance association End Point. via NTP. Setting up Delay Measurements To configure DMM instances.

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

For more information on specific parameters. the one-way delay was equal or greater than the maximum value. Indicates whether an alarm is raised (Active) because the consecutive amount of times. The remote MEP's Maintenance association End Point Identifier. 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. 2.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. The number of periods that elapsed since measurement started. proceed as follows: 1. if present. Viewing Delay Measurement Results To view delay measurement results details. The index assigned to the Maintenance association End Point. 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. The time when the previous period was completed. 170 . Description The index of the Delay measurement. is equal to or greater than the instantaneous threshold. Go to CFM > DMM > Results. The local MEP's Maintenance association End Point Identifier. in the transmitted frame. refer to the following table. Click the Index of the DDM instance you want to view the DMM results. For more information on specific parameters. This displays results for all Delay Measurement Instances. refer to the table below.

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

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

The previous period is indicated in Period time. 174 . otherwise the MHF default parameters control the MHF creation. For a given VID. 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. Packet loss ratio expressed as a percentage. Number of expected packets during the reference period. This displays all existing packet loss instances. For the current period. For each port. refer to the table at the end of this procedure. 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. 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. is greater that the packet loss threshold. if at this level an MEP exists on that port or if an Up MEP exists on some other port. This should normally correspond to the reference period divided by the interval unless the period is incomplete. For the current period. If at this level the VID is attached to a Maintenance Association. this counter is set to zero at the beginning of the period. proceed as follows: 1. it is a continuous value that is not set to zero at the beginning of the period. Indicates if an alarm is raised (Active) because the number of packets lost. 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 the current period. Continuous results in the section below gives the packet loss since the last time the statistics were cleared. For more information on specific parameters. For the current period. Go to CFM > Defaults. the default MHF MD level plus the set of Maintenance Associations which include that VID define the VID's active MD levels. The number of periods elapsed since measurement started. Number of times packets were missing during the interval. the Maintenance Association parameters control the MHF creation. To set up CFM defaults. a VID is attached to a Maintenance Association at a specific MD level. Number of packets lost during the period.Parameter Period Description Same as MEP's CCM priority. this counter is set to zero at the beginning of the period. Size in packets of the largest gap during the period.

175 . Possible values are: None: no sender ID TLV included. Default: Create MHFs if there is no lower active MD level. Manage: management address. refer to the following table. Click Add to create a packet loss instance or click a packet loss instance name to edit an existing packet loss instance. Indicates if the management entity can create MHFs for VIDs on which no Up MEP is configured. For more information on specific parameters. 3. Chassis and manage: chassis ID. Fill in the required fields and click Apply. subtype and 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. Chassis: chassis ID and chassis subtype. is to be included in the Sender ID TLV transmitted in CCMs. and LTRs.2. MHF sender ID permission Indicates what. if anything. LBMs. or if there is a MEP at the next active MD level on the port. LTMs. Possible values are: None: No MHFs can be created. Explicit: Create MHFs only if there is a MEP at the next active MD level on the port.

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

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

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

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

Second VLAN canonical format indicator (CFI). A description to identify the flow and its characteristics. For fixed packet size. Burst: To send a predefined number of packets at every period. Applies only when VLAN 2 header is enabled. For random packet size only. Name assigned to the flow. Supported values are: 0 to < 12. 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).5 Mbps (steps of 0. For reference in the Results section. specify the Minimum and the Maximum packet sizes. When Out-of-service flow type is selected. The size of test packets varies randomly between the minimum and maximum values. Type of traffic may be one of the following: Constant: To send packets at a specific bit rate (Kbps). specify the packet size. Applies only when a VLAN 2 header is enabled. 180 .125 Mbps) > 13 Mbps to 1 Gbps (steps of 1 Mbps) For Burst traffic type. You need to specify the Bit rate. 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. Applies only when VLAN 2 header is enabled. specify the bit rate (in Kbps).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. Note that you may need to modify your port MTU sizes to accommodate your selection. Failure to do so will result in inaccurate results. this field has no effect. You must select a bit rate that does not exceed the capacity of the outgoing port used for that test. For reference in the Results section. For Constant traffic type. The choices are: S-VLAN and C-VLAN Second VLAN priority bits.

0x12345678 For a random payload pattern. 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. specify the 32 bit value. Packets: Stops after sending a specified number of packets (Duration (packets)). 181 .g. select one of the pre-configured patterns. incremental or random pattern in the payload part of the transmitted frames. Bytes: Stops after sending a specified number of bytes (Duration (bytes)). Seconds: Stops after a specified number of seconds (Duration (secs)). e. For an incremental payload pattern. For a fixed payload pattern.Parameter Payload pattern Description May be a fixed-data.

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

Maximum size (in frames) of the received gaps. The delay variation is measured for each set of two consecutive packets from the generator to the loopback device and back to the generator. Maximum two-way delay variation (in ms). The delay is measured for each packet from the generator to the loopback device and back to the generator. 183 . Two-way instantaneous delay (in ms). When the test was completed or stopped. Two-way delay variation Instantaneous Two-way instantaneous delay variation value (in ms). Average two-way packet delay in microseconds. Minimum two-way delay (in ms). Maximum two-way delay (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 (analysis). When the test was started. Average Average DV Minimum Maximum Test times Test started at Test stopped at Minimum two-way delay variation (in ms). Average two-way delay variation (in ms).

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

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

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

Average delay variation in microseconds. Maximum delay in microseconds. refer to the table at the end of this procedure. 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. To set up a test suite. For more information on specific parameters. Select the different tests to run. Click the Add button to add a new test suite or click the Name of an existing test suite to edit its settings. This displays a summary of all test suites set up. 187 . Go to RFC-2544 > Testsuite > Configuration. fill in their corresponding settings and other required fields and click Apply. Minimum delay variation in microseconds. proceed as follows: 1. Refer to the table at the end of this procedure for more information on the different tests and settings. One-way delay variation Instantaneous Minimum Maximum Average One-way instantaneous delay variation in microseconds. One-way instantaneous delay in microseconds. 3. Maximum delay variation in microseconds. 2. For more information on specific parameters. Average delay in microseconds.1731 LBM and the MEG (ME Group) level is configurable. Layer-2 frames and Layer-3 UDP packets are Y. refer to the table below. Minimum delay in microseconds.Parameter One-way delay Instantaneous Minimum Maximum Average Description error inside the payload. 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.

a test that failed is also displayed in the report) and steps executed. When strict failure is disabled. OOO or duplicates frames/packets will cause a test to fail. For example. Enable failure on Out Of Order (OOO) or duplicate frames/packets. the test is marked as passed. Description The name of the test suite. Default: 4096 Example range: 1518 to 10240. the unit tolerates OOO and duplicates frames/packets. When strict failure is enabled.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. if you wish to measure the quality of a wirespeed GigE circuit. Range: 1 to 10 s. Out of Order frames/packets are frames/packets received in a different order that they were sent. As long as all frames/packets are received. the delay and delay variation test measures the latency and jitter at that specific rate. The description configured to identify the test suite and its characteristics.g. 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. Note that the range is dependant on the unit type and must be less than or equal to the port MTU. Once a wirespeed rate with no frame loss has been defined by the throughput test. The Throughput test searches for the maximum rate for which there is no frame loss according to the test settings. Enable delay 188 . Default: 2 s. The unit would then test at full GigE speed. Binary duration The duration (in seconds) of each trial during the binary search for the maximum throughput. the report contains all tests (e. Outgoing port Enable strict failure The port from which to send the flow(s). 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. 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. When enabled. Enable verbose report Test to run Enable throughput Check to enable throughput test.

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

The choices are: S-VLAN and C-VLAN Second VLAN priority bits. Encapsulates all packets with 2 VLAN headers (Q in Q). Failure to do so will result in inaccurate results. First VLAN Ethernet type. First VLAN canonical format indicator (CFI). First VLAN priority bits. Range: 1 to 1000 Mbps (1 Gbps). Failure to do so will result in inaccurate results. You must select a Maximum rate that does not exceed the capacity of the outgoing port used for that test suite. Applies only when a VLAN 1 header is enabled. Applies only when a VLAN 2 header is enabled.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. The choices are: S-VLAN and C-VLAN. Maximum rate The upper bound of rates (in Mbps) to search for. This parameter also applies for the delay and delay variation test. and for the frame loss test. When enabled. all test packets are encapsulated into the specified VLAN ID. Applies only when a VLAN 2 header is enabled. First VLAN ID. Applies only when a VLAN 1 header is enabled. Second VLAN Ethernet type. You must select a Minimum rate that does not exceed the capacity of the outgoing port used for that test suite. This parameter also applies for the delay and delay variation test. Second VLAN ID. Applies only when a VLAN 1 header is enabled. and for the frame loss test. 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. Minimum rate The lower bound of rates (in Mbps) to search for. Range: 1 to 1000 Mbps (1 Gbps). 190 . Second VLAN canonical format indicator (CFI). When enabled. Range: 1 to 1800 s. Applies only when a VLAN 2 header is enabled.

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

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

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

Sunrise™). 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. so customer traffic continues to flow while tests are performed on selected streams. 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. IP address & port swap) permit remote QoS testing for Ethernet. Exfo L3. 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. Remotely controlled loopback: Loops back traffic and is initiated upon the reception of a predefined packet type (JDSU/Acterna™. Custom). 194 . Exfo L2.

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

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

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

201 . Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality. 2: SFP module for Rx/Tx power. Provides status information. Severity of the alarm may be one of the following: Informational: No effect on service. temperature was above the threshold. The message explains why it was turned on or off. Delay.g. This is displayed only when the alarm has changed status (the alarm was turned ON or OFF). 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). Delay. temp. 4: SOAM module for Continuity Check. Critical: A service-affecting condition has occurred that requires immediate corrective action. Service affecting Description Message Alarms may be displayed as service affecting or non-service affecting. e. Packet Loss and other related alarms. Minor: An error condition has occurred that does not seriously affect system functionality.Parameter Description BBBB: Instance number (1-999/1-9999). Textual description of the alarm. Packet Loss and other related alarms. 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. 3: PAA module for Continuity Check. vcc and lbc alarms and warnings.

13 2. In this section.03 2.11 2.yyyy. Refer to the following table for a list of all alarms supported and their default description.0005. and 0004 = SFP-D 2.01 1.01 1. 0003 = SFP-C.0004.yyyy.16 2.06 2.02 2.07 2.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.01 1.yyyy.yyyy.Parameter Last change Description When the alarm changed status.0005.0001.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.10 2.yyyy.01 2.yyyy.yyyy.yyyy.0003. vcc and lbc.15 2.02 1.01 1.yyyy.04 2.05 2. temp.0004.yyyy.12 2.yyyy.yyyy.0002.yyyy. 0002 = SFP-B.08 2. Supported Alarms: MetroNID Number Default Description Port module for link down and others related alarms 1.yyyy.14 2.yyyy.09 2.01 1. yyyy specifies the SFP module. where 0001 = SFP-A.

08 3.yyyy.yyyy.20 2.yyyy. yyyy specifies the index of the PAA instance 3.yyyy. yyyy specifies the MEPID number 4.02 4.yyyy.10 4.yyyy.01 4.04 3.yyyy.05 4.09 3.yyyy.yyyy. In this section.03 3.yyyy.Number 2.yyyy.yyyy.yyyy.yyyy.03 4.yyyy.12 4.18 2.08 4.05 3.09 4.06 4.01 3.yyyy.06 3.yyyy.yyyy.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 .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 3.yyyy.04 4.yyyy. In this section.yyyy.07 4.yyyy.yyyy.yyyy.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. Packet Loss and other related alarms Note that these alarms are dynamically created based on the MEPs configured.07 3.yyyy. Delay.yyyy.19 2.yyyy.11 4.

50 8.04 8. Temperature sensor status Temperature sensor The current temperature inside the unit.0000.01 8.01 7. A red light indicates that the power source is not connected or is not operating normally. 2. For more information on specific parameters. proceed as follows: 1.05 8.0000. First threshold: The temperature that will activate the first overheating alarm.0001. Go to Show > Alarm. Viewing Chassis Alarms Go to System > Alarm > Chassis to view the status of chassis-related alarms.yyyy. 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. Click the alarm number to view its detailed status.0000.yyyy. 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.0000.02 8. 204 .Number 4.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.03 8. refer to the table Alarm Status (Show > Alarm). refer to the following table.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.14 4.0000. For more information on specific parameters.0000.0001.0000.

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

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

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

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

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

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

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

212 . 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.

Sign up to vote on this title
UsefulNot useful