Professional Documents
Culture Documents
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, Qubec 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
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
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
Organization
This document contains three main parts: an introduction, several chapters of detailed procedures and examples of networking scenarios. The Introduction chapter provides information about technologies and standards used in Accedians equipment. 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.
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, from which you can then select one element in order to get more detailed information on a separate page. For such features, one parameter table covers both the summary page and the detailed page. If the same parameter is labelled differently on the pages, then both labels are listed in the table. The parameters are listed in the order that they appear on the page, as far as is possible. Commands and keywords are in bold. Menu navigation example: CFM > DMM > Configuration Brackets [ ] are used when several options are available and you need to select a specific option. For example, 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.yyyy.zz. The first number (x) refers to a general category. The second number (yyyy) refers to the specific component. The third number (z) is the specific alarm code. For example, in 2.0001.01, the 2 refers to SFP modules, 0001 is for SFP-A and 01 means temperature high alarm. So, 2.0001.01 means SFP-A temperature high alarm. In the alarm descriptions, <SFP module> can refer to any SFP module, depending upon what the component number yyyy is.
References
The use of equipment such as the EtherNID and MetroNID involves the understanding of different networking standards, technical specifications and technologies. This document provides basic information on the standards and technologies. For more information about the standards and technical specifications, refer to the following: IEEE 802.1ag - Connectivity Fault Management IEEE 802.1ah - 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.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.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
For more information about each device, refer to Accedians website at www.accedian.com.
10
Applications
Accedian Networks is the leading provider of high-performance service-assurance solutions which enable service providers to deploy, monitor and maintain high performance, low delay and delay variation, real-time services over Ethernet, IP/MPLS and converged networks. High-performance 3G, 4G / LTE wireless backhaul, real-time business and carrier hand-off applications require ultra-low delay and delay variation, guaranteed throughput and carrier-grade reliabilityas well as operational efficiency that reflects todays competitive telecom marketplace. Services created and assured by Accedian Networks High Performance Service Assurance Platform benefit from real-time service mapping, traffic conditioning, in-service monitoring, loopback testing, service management and demarcation that enable you to establish end-to-end operational control, revenue-driving SLAs and dependable performance. For more information about Accedians EtherNID and MetroNID platforms possible applications, refer to Accedians website at www.accedian.com.
Mobile Backhaul
Accedian provides the industrys most accurate high performance backhaul assurance with micro-second delay and delay variation measurement, hitless throughput and remote loopback testing, mesh-network support and advanced traffic control edge-to-edge. The worlds leading 4G/LTE deployments rely on Accedian Networks to deliver unparalleled real-time performance, enabling Carrier Ethernet to be used effectively for backhauling mobile broadband applications.
11
12
13
14
Features
Service Assurance
Accedian Networks' high-performance service-assurance Platform provides standards-based inservice monitoring, loopback testing, remote troubleshooting, service management and network demarcation for high-performance mobile backhaul, business services and carrier interconnect and exchange applications. Accedian provides the highest performance network monitoring, troubleshooting, and network management tools that maintain and assure carrier-grade Ethernet. The industry's first SLAMeter has a comprehensive suite of active and passive in-service performance testing, intelligent layer 1-4 loopback functionality and per-flow traffic monitoring. Establish complete, end-to-end control of your services, Map-out the Health of your Network, and increase the dollar value of every packet flowing through it with Accedian Networks' service assurance solutions. For more information about service-assurance features for Accedians EtherNID and MetroNID, refer to Accedians website at www.accedian.com.
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. Accedian EtherNID and MetroNID high-performance service-assurance demarcation units establish end-to-end OAM, enable in-service loopback and performance testing and let you create and assure carrier-grade SLAs.
15
For more information about Loopback testing, refer to the chapter Managing Loopbacks.
16
For more information about Traffic Generation and Analysis, refer to the chapter Testing Network Performance.
17
Performance Monitoring
Accedian Networks Performance Assurance Agent (PAA) keeps continuous watch over the critical services on the network with one-way-delay and delay-variation measurements, frame loss and availability monitoring. Test up to 100 sites from a single EtherNID or MetroNID demarcation unit.
For more information about PAA, refer to the chapter Monitoring Network Performance.
18
For more information about SLA Assurance, refer to the chapter Managing Traffic.
19
Service Creation
Accedians high-performance demarcation devices provide a uniform network interface for creating MEF-compliant Ethernet Virtual Connections (EVC) services over any network topology, media or protocol. MetroNID units provide advanced traffic classification at wire-speed to indentify individual services and add the provisioned EVC service tags and CoS markings without adding delay to the service flows as they enter the Carrier Ethernet network. Optimize service and core network performance with wire-speed traffic conditioning and flexible rate limiting, traffic shaping, filtering and switch-free aggregation at the intelligent access edge. 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 networkwithout disturbing your switches or your customers. Quickly create Ethernet Virtual Connections (EVCs) for E-Line, E-LAN and E-Tree services with EVC service mapping: advanced networking functionality is built right into EtherNID and MetroNID units designed for customer, cell, aggregation and head-end sites. Multi-technology networks EVC service mapping functionality transparently creates Ethernet LAN services and avoids interoperability issues. Create, accelerate, optimize and manage Ethernet services with per-flow service mapping, traffic shaping, filtering and bandwidth policing directly at the demarcation point and bypass costly switches upgrades. Leverage real-time multi-port aggregation and bypass switches altogether. Accedians unique Fast-PAAs engine, the industrys only wire-speed performance assurance agent, enables the units to maintain EVCs at GbE and 10-GbE speeds without introducing delay or delay variation to critical, real-time traffic. Easily configured remotely, building EVCs is as simple as installing EtherNID units at the demarcation points and provisioning services from the web. For more information about service creation features of Accedians EtherNID and MetroNID, refer to Accedians website at www.accedian.com.
20
For more information about Ethernet Service Mapping, refer to the chapter Managing Traffic.
21
For more information about Bandwidth Policing, refer to the chapter Managing Traffic.
22
Traffic Filtering
Accedians advanced comprehensive traffic filters help preserve network security and prevent broadcast messages and malicious traffic from flooding your network. They provide wire-speed traffic filtering by VLAN, Ethernet/IP address, Ethertype, service class or TCP/UDP port.
For more information about Traffic Filtering, refer to the chapter Managing Traffic.
23
Traffic Shaping
Accelerate low delay services, reduce network overhead, and economize bandwidth with advanced, hardware-based traffic shaping that passes critical, real-time traffic at wire-speed using the Fast-PAAs zero-delay cut-through queue, while standard traffic is priority-queued, shaped and forwarded.
For more information about Traffic Shaping, refer to the chapter Managing Traffic.
24
25
Typical Screen
Date and time Alarms First, second and third level menus Working Area Write lock Logout
26
Date and time: date and time for this unit. You can configure the date and time from System > Configuration > Time. Alarms: indicates alarms that have been triggered. For more information on alarms, refer to the chapter Managing Alarms and System Messages. Working area: This is where you view information and configure system parameters. First, second and third level menus: The top row presents the first level menu. It is always visible. 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. To navigate to different functions, click an option on the first level menu, then on the second level menu and so on until you see the function you want to use. Each menu item you select will be highlighted. Selecting a third-level menu option often displays a summary of the information requested. If you then click one of the elements listed in the summary, you will obtain more detailed information on that element. The parameters present on both the summary and detailed pages are described within one table in this manual. For example, 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. The parameters are listed in the tables in the order in which they appear on the screen, wherever possible. Writelock button: Use this button to toggle between yes and no for Writelock. For more information about this function, refer to the section on Locking or Unlocking User Sessions. Logout button: Use this button to logout from the current session. Reset: Use this button to reset the value of a page, before you apply the change. This is useful when you are not sure exactly what values you changed and you want to start over using the previous configuration. This action has the same effect as leaving this page to go to another page and then returning to this page. Apply: Use this button to apply the changes made on the page to the equipment. This action changes the equipment configuration immediately. 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. Once you have the desired list shown on the page, you can also click this button to refresh the status and values of each field. For example, this can be useful in a Results page, helping you to view the changing results while a test is performed. Note: Using your browsers Refresh command does not simply refresh the values or list shown on one page, it reloads the page completely, eliminating any filter that you had applied.
27
Logging In
Once you have a physical connection to the equipment, you can login. Depending on the configuration of the unit, you may login in different ways. You would usually connect to the unit for the first time using the Management port. Normally you would then configure another interface, e.g. Network, for in-band management through the network. The first time you login, proceed as follows: 1. Configure the computer with a static IP address on the same subnet as the equipment you want to login to, for example 192.168.1.2 2. Start your Web browser and enter the following in the address box: https://192.168.1.254. Note: This is the factory default IP address of each unit. If you are using static IP addresses, you should then modify the units IP address to be unique, thereby avoiding duplicate IP addresses with other existing factory default units. You can also configure the unit to use DHCP. For more information on modifying IP addresses, use of DHCP and other options for logical interfaces, refer to Configuring the Logical Interfaces. 3. The login page for the unit opens. Login as admin with the Password admin. Note: This is the default password for the user admin. Be sure to change the admin password after your first login. This ensures that only the admin user can perform admin functions. To change the password, refer to the section Changing Passwords. If you already have configured another logical interface, proceed as follows: 1. Make sure your management station has a route to the equipment.
28
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.
Home Page
29
Description The hardware option of the unit. This field is available only if this unit has a hardware option installed, e.g. GPS.
This corresponds to DHCP option 61. It allows you to enter a text string for use as the units host name. When the text box is empty, the MAC address is used as the units 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
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.
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.
32
Parameter
For client applications, perform peer certificate validation. This includes expiration date, hostname and CA chain. For client applications, enable or disable the use of the selected client certificate.
Import certificate
33
Go to System > Configuration > Interface to view the existing logical interfaces and to configure new and existing logical interfaces.
34
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.
For information on specific parameters, refer to the table Interface Settings (System > Configuration > Interface).
35
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 interfaces 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 07. 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.
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
In Auto and Auto IP Static configuration modes, this list of IP addresses is excluded from the remote NIDs. The IP addresses need to be separated by commas. Up to 64 IP addresses can be specified. When you press Send, the system sends a single beacon frame with the information that has previously been configured and applied. If changes to the beacon settings were made without clicking Apply, they would not be effective in the beacon frame.
38
Parameter
Description
Discovery settings (Auto interface only) Beacon discovery state Auto mediaselection Processing of beacon frames upon reception. When enabled, the discovery ports listen for beacon frames and configure the Auto interface. Enable or disable port scanning to find out which ports have a link. When one or two links are detected, the appropriate media-selection mode is automatically selected. Use this for initial system discovery and disable it after the system has been configured. Auto media-selection is disabled if Discovery state is disabled. 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. The domain ID can be matched with the incoming beacon domain ID to determine if the beacon should be processed. A list of ports enabled to listen for incoming beacon frames.
ID matching Domain ID
Discovery ports
Forwarding settings (Auto interface only) Level The ACP frames level. This level is used in transmitted advertisement and beacon frames. A unit receiving a beacon frame will automatically set it's system ACP level to the one included in the beacon frame. The choices are: 07: for a specific level. The ACP frames level defines how far the ACP frames can go. A unit requires a higher level to be used to run above a lower level. For example, 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. All: All ACP frames will go through this unit without processing. Forward on bridge When enabled, beacons and advertisement frames are forwarded using the bridge associated with this interface, if a bridge exists. When enabled, the forwarding ports on match are not effective. 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. 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.
Advertisement settings (all interface types) L2 state The advertisement of information frames may be enabled or disabled. Information frames are used to advertise to a central unit. Default for Auto interface: Enable Default for other interfaces: Disable L3 state The advertisement of layer-3 information frames may be enabled or disabled. Default (all interfaces): Disabled
39
Parameter Advertisement IP Advertisement format Use rate from beacon Transmission rate
Description The destination IP address to be used in layer-3 advertisement frames. The frame format to use when sending information frames. ACP: Only proprietary Accedian format is supported for now. When enabled, 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.
40
2. Click the Add button or click the route name to add or edit a route. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
41
You can connect the serial port on the management station to the RJ45 console port on the unit using the following diagram and table.
42
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
43
44
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. The name of the local unit port that receives advertisement frames. The UPD port of the SNMP agent for the remote unit, if configured. The remote unit web port used. 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.
Unicast beacon configuration Domain ID IP config mode In the discovery process, the domain ID can be matched by remote devices to select which beacons it should process. 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 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 Beacon type Send beacon Subnet used by the receiver when Auto or Auto Static IP config mode is selected. Mask used by the remote device when Auto or Auto Static IP config mode is selected. Gateway used by the remote device when 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. The only choice is Renew config. It renews the configuration of all remote units that have the advertisement settings set to enable. When you press Send beacon, the system sends a single beacon frame with the information that has previously been configured.
You can also view more information for a specific unit by clicking the link in the Serial Number column. For more information on specific parameters, refer to the table Discovery config and inventory (Show > Inventory).
45
46
Managing Sessions
The units management system provides multiple configurable management sessions to allow multiple users to control the unit. There is a writelock mechanism to avoid two users writing to the unit at the same time. To view current sessions, go to System > Session > Management.
47
48
To terminate a session, go to System > Session > Management, select the session you want to terminate by checking the Terminate check box and the Terminate button. The session is immediately terminated and the current user is logged out.
49
Parameter
Description Local-radius: Validate locally first, if the validation does not succeed, then validate on the Radius server. Strict radius-local: Validate on the Radius server first. If the authentication fails, access is denied. Fall back to local happens only if the radius authentication times out. Radius-local: Validate on the Radius server first, and if the validation does not succeed, then validate on local server.
50
51
Filters: Edit/Add L2 filters, IPv4 filters, service mapping, traffic shaping and regulators. 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
Parameter
Description OAM: Edit/Add/Enable OAM, 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
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.
53
Password for the account. Specify a second time the password for the account.
Changing Passwords
To change a user password, proceed as follows: 1. Go to System > Sessions > Users. 2. Click the user name that you want to edit. 3. Type the new password in both the Password and Confirm password fields and click Apply. Note: If you forget your username or password, contact your Administrator for a password reset.
54
For more information on specific parameters, refer to the table User Settings (System > Session > Users).
Server-1 / Server-2 Host Port Secret RADIUS server host-name or IPV4 address. RADIUS server UDP port to connect to. Shared secret for this RADIUS server.
55
A member of the built-in Admin group: Callback-Id = "Admin" A list of individual privileges: Callback-Id = "Config Firmware Log Management, Users" Grant full administration privileges (Same as first example): Service-Type = "AdministrativeUser"
56
Standard Mode
Standard mode is for standard network interface device functions. 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, as explained in Setting up Media-Selection on page 76.
57
Aggregator 2x1 mode also modifies traffic policies as follows: Traffic-A policies are associated with the Client-1 port. Traffic-B policies are associated with the Client-2 port. Traffic-C policies are associated with the network port. The traffic shaper also behaves in a specific way in Aggregator 2x1 mode, as described in Understanding Traffic Shaping on page 118.
Aggregator 4x1 mode modifies traffic policies as follows: Traffic-A policies are associated with the Client-1 port. Traffic-B policies are associated with the Client-2 port.
58
Traffic-C policies are associated with the Client-3 port. Traffic-D policies are associated with the Client-4 port. Traffic-E policies are associated with the network port.
The traffic shaper also behaves in a specific way in Aggregator 4x1 mode, as described in Understanding Traffic Shaping on page 118.
The MetroNID can be used in this architecture, providing two 1-Gbps network ports for the ring and two 1-Gbps client ports to add/drop traffic. Refer to the figure below for the port configuration. Note: The media-selection option does not apply in ring topology.
59
Ring topology mode provides for the following: Standard RSTP operation: The unit implements standard RSTP and can operate with a root node (RSTP switch). Once the root node is properly set up, the NIDs will start exchanging RSTP BPDUs with the root bridge and the ring will be automatically configured. VLAN based add/drop and Logical loop prevention : Each unit transparently forwards all 802.1q (or 802.1ad) frames from node to node, except for the VLAN IDs defined for local drop (i.e. to local client port or local CPU). Non 802.1q (or 802.1ad) frames are discarded, except for those that must be peered. The nodes insert (add) local frames onto the ring on the root port (RP) only. The other ring port is a blocked port (BP) or designated port (DP). The nodes extract (drop) 802.1q (or 802.1ad) frames from the root port only. Only E-Line services defined individually between the home node and any other node are supported. The nodes can optionally add/push/pop the 802.1q (or 802.1ad) VLAN tag. You must therefore set VLAN filters and traffic policies for the traffic to be added and dropped correctly with the appropriate push, pop and permit traffic actions. For more information, refer to Defining Filters on page 92 and to Setting up Traffic Policies on page 100. 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). A real-time queue is also provided. Each shaper queue is individually configured using a dual leaky bucket scheme supporting three colours. Queue management uses the BLUE algorithm. Frames are colourmarked before entering the shaper using a three-colour bandwidth policer. Once on the ring, green frames are guaranteed delivery and have the highest priority. Yellow frames on the ring may be discarded in favour of local green frames. 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. Whether Network-A or Network-B is the active port, the incoming port will always be identified as Network-A in the Policies menu. Policies must be configured in Traffic-A to determine where the ring traffic must be dropped (Client-1 or Client-2). Traffic-B and Traffic-C policies are used to add client traffic onto the ring.
60
System > Configuration > Interface: A ring bridge is automatically created. This bridge includes the sub-interfaces that are assigned to the ring ports (Net-A and Net-B).
The operation mode that will be applied after a reboot of the unit. When using Aggregator mode, traffic policies need to be configured on the network port in order to have the incoming traffic forwarded out the proper client port. 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. Changing the operation mode will reset the unit to factory default. The options are: Standard: This is the default mode of operation where ports are not aggregated. Aggregator4x1: Traffic for all four client ports (e.g. 4x100 Mbps) is forwarded through the network port (e.g. 1 Gbps) with equal priority. Aggregator3x1: Traffic for all three client ports (e.g. 3x1 Gbps) is forwarded through the network port (e.g. 1 Gbps) with equal priority. Aggregator2x1: Traffic for both client ports (e.g. 2x1 Gbps) is forwarded through the network port (e.g. 1 Gbps) with equal priority. Note that the
61
Parameter
Description protection port in Aggregator2x1 mode cannot be used as a monitor port, it must be used for Link or LACP protection. Ring topology: Allows Ethernet ring network topology. It provides two client ports (RJ-45A and RJ-45B), two network ports (SFP-A and SFP-B) and one management port. The traffic of the two client ports is forwarded to one of the working network ports. The working network port is chosen according to the network port RSTP status.
IGMP version
The IGMP version for the unit. This affects the IGMP configuration of all interfaces on the unit. Your options are: System default V2 V3 This affects all elements that make use of the S-VLAN ethertype, i.e. interfaces, filters, RFC-2544. 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.
S-VLAN ethertype
62
4. Select a time server from the list and click Apply. To automatically set the date and time using GPS, proceed as follows: 1. Go to System > Configuration > Time. 2. If your unit supports the GPS feature, select GPS enable and click Apply. The unit also provides for time zones and Daylight-saving time. For a list of time zones and daylight-saving-time rules, please refer to: http://www.worldtimezone.com/. If you want to set the time zone and the daylight saving function, proceed as follows: 1. Go to System > Configuration > Time. 2. Select Daylight saving time enable. 3. Fill in the parameters and click Apply. For more information, refer to the following tables of parameters and examples.
63
64
Setting SyncE
You can use the synchronous Ethernet (SyncE) feature to synchronize the unit and all its outputs over Ethernet networks. It takes the clock signal from the selected clock reference port and transmits it to all other ports. You also have the option to define a Secondary Clock Source on another physical port. To set up SyncE, proceed as follows: 1. Go to Port > SyncE. 2. Select Enable SyncE, fill in the parameters and click Apply. For more information on specific parameters, refer to the following table.
Options Primary clock source Secondary clock source Revertive The port from which the Primary Reference Clock is recovered. The port from which the Secondary Reference Clock is recovered. This is optional and may be set to none if only a single reference clock is desired. When enabled, the clock selector is allowed to switch back to a higher priority clock source that previously failed, should it become available again. When disabled, the clock selector is allowed to go to a lower priority clock source only should the currently selected source become unavailable. In this mode, the selector cannot revert to a clock that previously failed. Forced clock This forces the clock selector to use a specific clock source. If none is specified,
65
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.
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 units 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).
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.
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
The name for the PPT configuration file name to export. Applies the factory default settings.
The factory default and rollback actions require a system reboot. You can cancel these actions by clicking Cancel changes. Rolls back the configuration to the version from the last reboot of the unit.
To export a configuration in a Vision EMS PPT format, proceed as follows: Note: A configuration exported in a Vision EMS PPT format can only be imported into another unit with the Vision EMS. 1. Go to System > Maintenance > Firmware. 2. Enter a filename for the PPT configuration file in the PPT export filename text box. The PPT file is exported as a compressed XML file. 3. Click Export.
70
71
72
Managing Ports
This chapter describes how to manage the ports, 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), link speed (auto-negotiation) and flow control. To view ports or set up a port, proceed as follows: 1. Go to Port > Configuration. This displays a list of all ports and their status. For more information on specific parameters, refer to the table below. Note: The page varies depending on whether you are setting up a copper port or an SFP fiber port. 2. Click the Port name to edit its settings. 3. Define port parameters as required by your setup and then click Apply. For more information on specific parameters, refer to the following table.
73
Description
The name that identifies the port. The default port name varies depending on the operation mode. The 'alias' name for the port as specified by a network manager. The maximum transmission unit in bytes that a port can receive and forward, including all headers. Supported values: 1518 to 10240. Default: 2000
Large packet threshold MAC address Connector Media dependent interface (Copper ports only)
Packets above this threshold will be classified as Large Packets. The Large Packets count can be viewed on the Port > Statistics page. The MAC address of the port. The physical connector associated with the port. Auto MDI means that the unit automatically adapts the configuration of the connector to the cabling plant and type of link partner. If Auto MDI is not in use, you can manually define port settings as follows: MDI: Typical setting for an Ethernet station. Link partner must be set to MDIX or a cross-over cable must be used. MDIX: Typical setting for an Ethernet switch. Link partner must be set to MDI or a cross-over cable must be used.
This option determines how the unit notifies its link partner when a valid receive signal is absent on the link. If this option is disabled, then: For 1000BASE-X links, a Remote Fault Indicator (RFI) using auto-negotiation advertisement is sent to the link partner. For 100BASE-FX links, the FEFI idle pattern is sent to the link partner. If this option is enabled, then the unit turns off its transmitter for the amount of time defined in the LLR period, after which it is re-enabled. This cycle is repeated until the link is re-established. 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, for this reason, 0 should not be configured on both sides or the link will never re-establish.
Sets port speed and duplex type. Auto-negotiation: The unit automatically negotiates port speed and duplex type with the device it is connected to. For this to work, the other device must also be set up for auto-negotiation. If Auto-negotiation is not in use, you can manually define port speed and duplex type using the following available options: 10 Mbps 100 Mbps
74
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.
Protection Enable
Enable protection for the port selected in the working connector. The protecting port is reserved by the protection mechanism and can not be used for monitoring purposes while protection is enabled. Note that protection is available on the network port only.
Protection Mode
Switching protection to a standby connector can be based on Link status or LACP status. If LACP status is selected, you must create an L2PT rule with an operation mode of Peer and Protocol LACP on this port in order to terminate LACP packets. Note that protection is available on the network port only.
Working connector
The working connector for the specified port. Choosing the connector when enabling the protection allows you to perform a switchover operation. In revertive mode, when both ports are working, the traffic reverts to the working connector. Note that this parameter is available on the network port only.
Revertive
When enabled, traffic is switched back to the main connector after the revert period has expired. This is available for link status protection mode only. Note that this parameter is available on the network port only.
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. The timer is restarted if a signal loss is detected during this period. This is available for only link status protection mode and only on the network port.
The time (in seconds) for the protection link to come up after switching to the protection connector when the protection link is down. If the timer (link time out) expires and the link stays down, the system switches back to the working connector. Note that this parameter is available on the network port only.
Enables the propagation of link faults between the ports specified in Propagate from port. One-way link: Propagate faults in one direction based on the link status of the opposite port. One-way EVC: Propagate faults in one direction based on the link status of the opposite port or the EVC status. The name of the port from which faults are propagated. disable: pause frames are disabled.
75
Parameter
Description local: pause frames are processed locally. transparent: pause frames are transparently passed through.
LLDP
Enable or disable LLDP (Link Layer Discovery Protocol) frame transmission on the selected port. Rate: The LLDP frame transmission rate (in seconds) on the selected port [165535]. TTL: The TTL value (Time to Live TLV) in the LLDP frame on the selected port [065535]. 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.
Current status
Current link speed and duplex type when Auto-negotiation enable is selected. Current connector configuration: If the link partner is also using Auto MDI, the resulting connector configuration is correct but random. 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, this reports the clock mastership mode. In auto mode, the clock master is determined by the auto-negotiation process. In forced mode, usually when using SyncE, the clock is forced into slave if the port is a clock reference for the system, otherwise it is master.
Setting up Media-Selection
Media-selection is used to specify which connectors will carry traffic. When changing this setting, all associations between connectors and ports will be reflected in the port configuration and status pages. The media-selection option is available in two operation modes, as described in Understanding Operation Modes on page 57. The tables below show the media-selection options and the connector-to-port mapping for the operation modes that use media-selection. Note: The media-selection option is supported on certain types of units only. In standard operation mode, use media-selection to select the connectors to be used by the client and network ports. In Aggregator 3x1 mode, use media-selection to select the connector to be used by the network port. Note: The names of the ports in the tables below are the factory default names. To select connectors via media-selection, proceed as follows: 1. Go to Port > Configuration. 2. Select Media-selection and then click Apply. For more information on specific parameters, refer to the two following tables: Media Selection Options in Standard Operation Mode (Port >
76
Configuration) and Media Selection Options in Aggregator 3x1 Operation Mode (Port > Configuration).
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
77
1. Go to Port > Configuration. 2. Click the Port name on which you want to perform the switch. 3. Select the Working connector to which you want to perform the switch and then click Apply.
78
Transmit statistics Bytes good Count of the total number of bytes transmitted by the port in good packets. The count includes the four CRC bytes but does not include the preamble or SFD bytes. A good packet is one that has been transmitted successfully (not aborted) with a good CRC. It is assumed that all transmitted packets are properly sized: from 64 bytes (after any padding) up to the maximum size. Count of the total number of bytes transmitted by the port in good and bad packets. The count includes the four CRC bytes but does not include the preamble or SFD bytes. Bad packets include normal collisions, late collisions and FIFO underflows. For collisions, all bytes transmitted before the start of the collision as well as the colliding and jam bytes are counted. For FIFO underflows, all bytes actually transmitted are counted. Number of transmission errors. Count of the good (not dropped and having valid CRC) unicast packets transmitted by this port. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i.e. the first bit transmitted is a 0). Count of the good (not dropped and having valid CRC) multicast 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.e. the first bit transmitted is a 1). Broadcast packets are not included in this count. Count of the good (not dropped and having valid CRC) broadcast packets transmitted by this port. Broadcast packets are identified by a destination address of all 1's. Count of the good (not dropped and having valid CRC) flow control pause packets transmitted by this port. 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) VLAN packets transmitted by this port. VLAN packets are identified by a type field equal to 8100h set in the outer VLAN tag. Count of the transmitted packets with a bad non-appended CRC field. This count does not include packets with a bad CRC due to a FIFO underflow. Count of the number of packets that were deferred on the first transmit attempt due to the medium being busy. Packets with subsequent deferrals (for instance, after a collision back off) are not counted. Whether the packet is eventually transmitted successfully or not is irrelevant to this counter. Packets dropped due to excess deferral during the initial transmit attempt are not counted. Count of the number of packets dropped by this port due to excessive deferral. The deferral time starts at the beginning of each transmission attempt and ends when the transmission starts (regardless of collisions). The deferral is excessive if more than 3036 byte times have passed without the transmission starting.
Multicast packets
Excessive deferrals
79
Description Count of the number of times a packet is successfully transmitted from this port after experiencing a single collision. This count does not include erroneous (dropped) packets. Count of the number of times a packet is successfully transmitted from this port after experiencing multiple collisions. This count does not include erroneous (dropped) packets and also does not include packets dropped due to excess collisions. Count of the number of packets dropped by this port due to excess collisions (number of collisions equals MaxRetry+1). This count does not include packets dropped due to FIFO underflow or late collisions (even if the late collision is also an excessive collision). Count of the number of packets dropped by this port due to late collisions. A late collision is a collision that occurs after the collision window delay (normally 512bit times). The collision window time is measured from the rising edge of TX_EN to COL asserted at the MII interface. This count does not include packets dropped due to FIFO underflow. Late collisions are not retried. Count of the total number of normal collisions that have occurred on this port during all transmission attempts. FIFO underflows, late collisions and collisions that occur while this port is not trying to transmit are not counted. 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. When an underflow is detected, transmission is immediately aborted after sending a known bad (inverted) CRC sequence. The FIFO underflow error takes precedence over all other errors if this counter is incremented, then none of the other packet type counters is incremented. The total number of packets, good or bad, transmitted by this port that were exactly 64 bytes in length (excluding preamble and SFD but including CRC).
Excessive collisions
Late collisions
Normal collisions
FIFO errors
Packets 64
80
Parameter Packets 65 127 Packets 128255 Packets 256511 Packets 512 1023 Packets 10241518 Packets 15192047 Packets 20484095 Packets 40968191 Packets 8192 and more Large packets
Description The total number of packets, good or bad, transmitted by this port, 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). Packets 1024 and above are only available on certain types of units.
The total number of large packets transmitted by this port. Define the size of large packets from Port > Configuration > [port name].
Receive statistics Bytes good Count of the total number of bytes received by the port in good packets. The count includes the four CRC bytes but does not include the preamble or SFD bytes. 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. Count of the total number of bytes received by the port in good and bad packets. The count includes the four CRC bytes (if present) but does not include the preamble or SFD bytes. Good packets are described above. Bad packets include short packets (less than 64 bytes), long packets (greater than MTU configured on the port), packets with bad CRC, packets with PHY errors and packets with receive FIFO errors. Bytes in bad packets resulting from a collision are counted if the SFD is detected. Number of errors received. Count of error-free packets received on this port that are shorter than 64 bytes. A packet is error-free if it has a valid CRC, no PHY errors and no FIFO errors. Count of packets received on this port that are shorter than 64 bytes and have a bad CRC. Packets with PHY or FIFO errors are not counted. 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, no PHY errors and no FIFO errors.
81
Description Count of packets received that are longer than MTU configured on the port and have a bad CRC. Packets with PHY or FIFO errors are not counted. Count of the good unicast packets received by this port. 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. Unicast packets are identified by having a 0 in the least significant bit of the first byte of the destination address (i.e. the first bit received is a 0). Count of the good multicast packets received by this port. 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. Multicast packets are identified by having a 1 in the least significant bit of the first byte of the destination address (i.e. the first bit received is a 1). Broadcast packets are not included in this count. Count of the good broadcast 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. Broadcast packets are identified by a destination address of all 1's. Count of the good flow control pause packets received by this port (good CRC, no PHY or FIFO errors, normal size). Flow control pause packets are identified by a type of 88-08 and an opcode field of 00-01. Count of the good VLAN packets received by this port (good CRC, no PHY or FIFO errors, normally sized). VLAN packets are identified by a type field equal to 8100h set in the outer VLAN tag. 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). Packets with FIFO or PHY errors are not counted. 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 PHY or FIFO errors are not counted. Count of the number of receive packets (or events) detected by this port without SDF detection but with carrier assertion. Packets with valid SFD but no data bytes are also counted as runts. After detecting a runt packet, the update of the RxRunts counter is suspended until the next valid packet is received. If multiple runt packets occur between valid packets, the RxRunts counter is incremented only once. Count of the number of good packets received by this port with an error in the length field. A length error occurs when the value in the length field is within the valid range for data length (31500 bytes) but does not match the actual data length of the packet. Field lengths less than 46 bytes (smaller than the minimum legal packet size of 64 bytes) are not checked, due to padding. Count of the number of received packets (or events) detected by this port with a false carrier (SSD1 not followed by SSD2). After detecting a false carrier, update of the RxFalseCRS counter is suspended until the next valid packet is received. If multiple false carrier events occur between valid packets, the RxFalseCRS counter is incremented only once.
Multicast packets
Broadcast packets
Align errors
Runt frames
Length errors
False CRS
82
Description Count of the number of packets received by this port with RX_ER asserted during reception (while RX_DV is asserted). Packets with a FIFO error are not counted. Count of the number of received packets dropped or aborted due to receiving a FIFO overflow. The FIFO overflow error takes precedence over all other errors: if this counter is incremented, then none of the other packet counters is incremented. Count of the number of received packets that have been ignored by this port. A packet is ignored if it violates the programmed preamble rules or if it violates the minimum data gap. The preamble rules include long preamble enforcement (greater than 23 nibbles) and pure preamble enforcement (only 55h bytes). 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. The normal data gap is 20 bytes long (12 bytes of IPG and 8 bytes of preamble/SFD). The enforcement limit is set to 10 bytes (half the normal gap length). Count of the good control packets received by this port (good CRC, no PHY or FIFO errors, normally sized) with an unknown opcode. Unknown control packets are identified by a type field of 88-08 and an opcode field not equal to 00-01. The total number of packets, good or bad, received by this port, that were exactly 64 bytes in length (excluding preamble and SFD but including CRC). The total number of packets, good or bad, received by this port, that were 65 to 127 bytes (or the other length) in length inclusive (excluding preamble and SFD but including CRC). Packets 1024 and higher are available on only certain types of units.
FIFO errors
Ignored
Bad opcode
Packets 64 Packets 65 127 Packets 128255 Packets 256511 Packets 5121023 Packets 10241518 Packets 15192047 Packets 20484095 Packets 40968191 Packets 8192 and more Large packets
The total number of large packets received by this port. Define the size of large packets on the Port > Configuration > [port name] page.
83
To set up a ports PHY parameters, proceed as follows: 1. Go to Port > PHY. This displays a list of PHY configuration and status for all copper ports. 2. Click the Port name to edit its settings. 3. Define port PHY parameters as required by your setup and then click Apply. For more information on specific parameters, refer to the following table.
84
State
85
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. The manufacturer name. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h). Indicates the nominal transmitter wavelength at room temperature in nm. The manufacturer part number or product name. This is a 16-byte field that contains ASCII characters padded on the right with ASCII spaces (20h). The manufacturer serial number for the transceiver. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h). The manufacturers product revision. This is a 16-character field that contains ASCII characters padded on the right with ASCII spaces (20h). Indicates the presence of a recognized SFP. Supported or unsupported. Supported indicates that diagnostic information is provided in the SFP memory section. Internal: The values are calibrated to absolute measurements, which should be interpreted according to the Internal Calibration convention. External: The values are A/D counts, which are converted into real units according to the External Calibration convention. Thresholds Indicates whether alarm and warning thresholds are supported.
86
Parameter Speed
Monitoring information Temperature Transceiver temperature, measured internally. Temperature accuracy is manufacturer -specific but must be better than 3 degrees Celsius for the specified operating temperature and voltage. Coupled TX output power, measured internally. Accuracy is manufacturer specific but must be better than 3 dB for the specified operating temperature and voltage. Data is assumed to be based on measurement of a laser monitor photodiode current. Data is not valid when the transmitter is disabled. Coupled TX output power, measured internally. Accuracy is manufacturer specific but must be better than 3 dB for the specified operating temperature and voltage. Data is assumed to be based on measurement of a laser monitor photodiode current. Data is not valid when the transmitter is disabled. Received optical power, measured internally. Accuracy depends on the exact optical wavelength. For the manufacturers specified wavelength, accuracy should be better than 3 dB for the specified temperature and voltage. 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. It should be maintained down to the minimum transmitted power minus cable plant loss (insertion loss or passive loss) per the appropriate standard. Accuracy beyond this minimum required received input optical power range is manufacturer specific. Transceiver supply voltage, measured internally. Note that in some transceivers, transmitter supply voltage and receiver supply voltage are isolated. In that case, only one supply is monitored. Refer to the device specifications for more detail.
Transmit power
Receive power
Supply voltage
87
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). Low-laser bias current alarm for the TX (micro-Amps). High-laser bias current warning for the TX (micro-Amps). Low-laser bias current warning for the TX (micro-Amps).
High-output power alarm for the TX (~ -40 to +8.2 dBm). Low-output power alarm for the TX (~ -40 to +8.2 dBm). High-output power warning for the TX (~ -40 to +8.2 dBm). Low-output power warning for the TX (~ -40 to +8.2 dBm).
High-input power alarm for the Rx (~ -40 to +8.2 dBm). Low-input power alarm for the Rx (~ -40 to +8.2 dBm). High-input power warning for the Rx (~ -40 to +8.2 dBm). Low-input power warning for the Rx (~ -40 to +8.2 dBm).
Testing a Cable
You can test the quality of copper cables, connectors and terminations attached to each unit. For this, the unit uses time-domain reflectometry (TDR). You can quickly find opens, shorts, cable impedance mismatches, bad connectors, and termination mismatches. Note: You can test cables only on RJ-45 ports. SFPs (optical or electrical) are not supported. To test the quality of a cable and view results, proceed as follows: 4. Go to Port > Cable. This displays a summary of all cable test results for all available copper ports. For more information on specific parameters, refer to the table below. 5. Click the Connector to test a cable. 6. Click the Perform test button to start the test. The test should last only a few seconds and the status of each channel is updated as the tests are run.
88
OPEN: There is a cut on a pair. The possible causes are: Line of the RJ-45 cable may be left unconnected at the wiring closet patch panel. Line of the RJ-45 cable may have been cut unintentionally. The other end of the RJ-45 cable may be simply unconnected.
FORCED: A persistent noise in the channel. This can be caused by a link partner running in forced 10/100 Mbps. Cable length is not available in the FORCED state. FAIL: The test failed. The link partner must lose the link in order to start the test. If the PHY receives a continuous signal during 125 ms, it reports test FAIL. 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.
89
Managing Traffic
This chapter describes how to create and manage Ethernet services. 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
Bandwidth Policing (also referred to as Rate Enforcement or Bandwidth Regulation): Bandwidth profiles, which are defined by the values of their associated parameters (CIR, CBS, EIR, EBS, CM, and CF), are enforced via a token bucket algorithm according to Technical Specification MEF 5. Bandwidth profiles can be used to offer bandwidth to your client according to predefined SLAs. The Bandwidth policing assures SLAs by regulating committed and excess information throughput, per flow: upstream and down.
90
Bandwidth profiles can be specified as follows: Bandwidth Profiles Per Ingress UNI Bandwidth Profiles Per EVC Bandwidth Profiles Per CoS ID
91
Traffic Filtering: Filters can be defined to classify traffic based on any combination of the following frame characteristics: VLAN ID PCP value DSCP value IP precedence value
The filtered traffic can be either dropped, or sent for service mapping, 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. This way, you can loop back traffic or set up a traffic policy based on specific characteristics such as Ethernet Header settings, VLAN settings and DSCP for Layer-2 filters, or based on IPv4 Header settings, ICMP settings and VLAN settings. You can also use the preconfigured Layer-2 or IPv4 filters. 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. Refer to your units datasheet for the maximum number of specific filters possible for traffic policies.
92
93
Parameter
Description
Ethernet header settings MAC destination / mask The destination MAC address and mask. Only the bits specified by the mask are used. The other bits are ignored. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). The source MAC address and mask. Only the bits specified by the mask are used. The other bits are ignored. Address format: six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Ethertype Protocol may be selected or entered manually (hexadecimal).
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. This should always be set to zero for connection to Ethernet switches. CFI is used to ensure compatibility between Ethernet networks and Token Ring networks. If a frame received at an Ethernet port has a CFI set to 1, then that frame should not be forwarded "as is" to an untagged port. VLAN priority allows the provision of CoS prioritization using the standard 802.1Q priority tag. Interpretation is based on the carrier's equipment and administrative policies. Valid operator types are: Greater than Less than Equal to Range (inclusive range) The possible values for each operator are: 0 to 7. 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. 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).
Priority
94
Description VLAN ID to use for filtering 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. 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).
DSCP/IP precedence DSCP/IP precedence DSCP/IP precedence operator. Valid operator types are: Greater than Less than Equal to Range (inclusive range).
95
IPv4 header settings IPv4 source / mask IP source Source address and mask. Only the bits specified by the mask are used. The other bits are ignored. Note that filtering source or destination IP address assigned by Dynamic Host
96
Parameter
Description Control Protocol (DHCP) can cause problems. You should ensure that all IP addresses specified in a filter are static or reserved. Otherwise you must have to manually update your filter every time the addresses change. Destination address and mask. Only the bits specified by the mask are used. The other bits are ignored. Note that filtering source or destination IP address assigned by Dynamic Host Control Protocol (DHCP) can cause problems. You should ensure that all IP addresses specified in a filter are static or reserved. Otherwise you must have to manually update your filter every time the addresses change. Time-to-live value. Explicit Congestion Notification. Specify either 0 or 3. Header length in 32-bit units. Specify a value in the range of 515. Protocol may be selected from the list or a manually entered port number (decimal). Common protocols are TCP (6), UDP (17) and ICMP (1). TCP is used by HTTP, FTP, Telnet and SMTP. UDP is used by DNS, SNMP and RIP. ICMP is used by Ping. The protocols available, in the format of protocol name (port number), 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)
97
Parameter
Description ESP (50) AH (51) MOBILE (55) SKIP (57) EIGRP (88) OSPFIG (89) IPComp (108) VRRP (112)
Specify the UDP or TCP port number used by the IPv4 source and IPv4 destination port fields. These settings are valid only when the Protocol is set to TCP (6) or UDP (17). Specify the ICMP message type for this filter to match. These settings are valid only when the Protocol is set to ICMP (1). Some well-known ICMP types are Echo Reply (0), Destination Unreachable (3), Redirect (5), Echo (8) and Time Exceeded (11). Other ICMP Code: See www.iana.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. This should always be set to zero for connection to Ethernet switches. CFI is used to ensure compatibility between Ethernet type networks and Token Ring type networks. If a frame received at an Ethernet port has a CFI set to 1, then that frame should not be forwarded "as is" to an untagged port. VLAN priority allows provisioning CoS prioritization using the standard 802.1Q priority tag. 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). The destination port used to match this rule. This setting is valid only when the protocol field is set to TCP (6) or UDP (17).
Priority
98
Parameter
Description policies. Valid operator types are: Greater than Less than Equal to Range (inclusive range) The possible values for each operator are: 0 to 7. 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. 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).
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. 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).
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).
99
100
Maximum Number of Policies per Port Network: 40 Client-1: 16 Client-2: 16 Client-3: 16 Client-4: 16
Network: 60 Client-1: 60
101
Maximum Number of VID Sets per Port Network: 7 Client-1: 3 Client-2: 3 Client-3: 3 Client-4: 3
Network: 60 Client-1: 60
Once a VID set is created, you can apply it to traffic policies as a filter (See Setting up Traffic Policies).
VLAN Filtering
You can create VLAN filters using the VLAN type field (S-VLAN or C-VLAN) and VLAN ID or range. When using VLAN filtering, you also need to select the VLAN (inner or outer VLAN) for filtering the traffic for each policy list, e.g. Traffic-A. See Selecting VLAN or VLAN-in-VLAN filtering).
102
Specify a list of VIDs in the following format: [- ], [- ]... (e.g. 1,2,100-200 will include VIDs 1,2,100,101,102,103... 200. Note that for a catch-all filter, you must assign VID 04095. For untagged frames, assign VID 0.
Size
103
Note: When you edit an existing VID set, the changes that you make are not yet applied to the traffic policies that use it. You need to re-apply the VID set to the policies by selecting a traffic policy and clicking Apply. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the table VID Sets (Traffic > VLAN > VID Sets).
For more information on specific parameters, refer to the following two tables.
104
State
105
1. Go to Traffic > Regulators > Configuration. This displays a summary of all existing bandwidth regulators. By default, none are defined initially. For more information on specific parameters, refer to the table at the end of this procedure. 2. Click the Add button to add a new bandwidth regulator or click the name of an existing bandwidth regulator to edit its settings. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
106
Parameter
Description True: Yellow data is limited by the setting of the Committed Information Rate plus the Excess Information Rate.
Once a CoS profile is created, you can apply it to Traffic policies for CoS mapping and bandwidth policing. See Setting up Traffic Policies. To set up the CoS profile, you need to assign in the mapping table, 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. The mapping table has N rows, where N depends on the type of the CoS profile. If the CoS profile type is PCP or IP precedence then N=8. If the CoS profile is a DSCP, N=64. To set up a CoS profile, proceed as follows: 1. Go to Traffic > Mapping > CoS profiles. This displays existing CoS Profiles. By default, four commonly used profiles are set up. For more information on specific parameters, refer to the table at the end of this procedure. 2. Click the Add button to add a new CoS profile or click the name of an existing CoS profile to edit its settings. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
107
Parameter
The number of policies that are currently using this CoS profile. This makes the unit decode the pre-marking color from the DEI bit (Drop Eligible Indication). Otherwise, the user defined pre-color is used. This parameter is only available when PCP CoS profiles type is selected.
This makes the unit Control the DEI bit in an S-VLAN tag. If this field is checked and the outgoing frame is marked yellow then the DEI bit is set to 1; otherwise, the DEI is set to 0. The number of policies that are currently using this CoS profile.
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, IP precedence or DSCP type frame. Pre-marking color to assign to the input frame that has this PCP, IP precedence or DSCP value. CoS value (0-7) for use in the outgoing green frames. This value is selected if: the result of the bandwidth regulator assigned to this entry is green, or the pre-marking color is green and no bandwidth regulator is assigned to this entry. CoS value (0-7) for use in the outgoing yellow frames. 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, 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.
Yellow [OUT]
108
Once a Bandwidth regulator set is created, you can assign it to traffic policies for rate enforcement based on the map type being used. (See Setting up Traffic Policies). Before configuring a Bandwidth regulator set, you must first set up a number of traffic regulators (refer to Setting up Bandwidth Regulators). To configure the Bandwidth regulator set, you need to assign in the mapping table, a traffic regulator (to a specific PCP, IP precedence or DSCP value. This table has N rows, where N depends on the type of the regulator set. If the type is PCP or IP precedence then N=8. If the type is DSCP, N=64. To configure a Bandwidth regulator set, proceed as follows: 1. Go to Traffic > Mapping > Bandwidth regulator sets. This displays the existing bandwidth regulator sets. For more information on specific parameters, refer to the table at the end of this procedure. 2. 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. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
BWR Set Configuration (Traffic > Mapping > Bandwidth regulator sets)
Parameter Index Name Type Description The unique identifier of the Bandwidth regulator set. Name of the Bandwidth regulator set. Specifies the type of priority the Bandwidth regulator set is based on. Type may be one of the following: PCP: Priority Code Point mapping. 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.
Bandwidth regulator to use to regulate the traffic flow that has this PCP, IP precedence or DSCP value. Enable or disable traffic regulation for this PCP, IP precedence or DSCP value.
109
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, IP precedence or DSCP values. The table below shows the valid configurations of the first and second choices.
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 option, you may select the PCP action for CoS mapping if required. Refer to PCP Action Options.
Pop
Use this option to regulate traffic based on PCP, IP precedence or DSCP values before removing the VLAN tag.
110
The table below shows the valid configurations of the first and second choices for this encapsulation option.
Replace
This action is similar to the Push action but rather than adding a new VLAN tag, it replaces the VLAN tag with the information provided by Ethertype and VLAN ID parameters. The PCP action Preserve is not supported by this encapsulation option. However, the user can use the PCP action Map and the default 8P0D-8P0D CoS profile to preserve the incoming PCP value. Note: This action requires a filter that checks the presence of at least 1 VLAN tag.
Preserve
Use this option to copy the PCP bits from the first VLAN (if any) to the pushed VLAN tag. If the frame is not tagged, you may select the PCP bits from an IP precedence / DSCP CoS profile. It is also possible to select a bandwidth regulator set for bandwidth policing. The table below shows the valid configurations of the first and second choices for this encapsulation option.
111
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. The pre-marking color red is ignored if the default bandwidth regulator is disabled. Note: The first and second choices are ignored.
Map
Use this option to map and regulate traffic based on PCP, IP precedence or DSCP values. The first and second choices can be used. The table below shows the valid configurations of the first and second choices.
112
Policy configuration Type Regulator Policy statistics Packets good Bytes good Packets bad Number of good frames that matched the policy. A good frame is an error-free frame that has a length between 64 bytes and the maximum frame length. Total number of bytes in good frames that matched the policy. Number of bad frames that matched the policy. A bad frame is a packet whose framing is valid but contains an error within the frame, has a bad CRC, is shorter than 64 bytes, or is longer than the maximum frame length. Filter type (VID set) that is used to classify traffic. Name of the bandwidth regulator assigned to this policy.
113
a) b)
c) d) e)
f)
a) Enable the policy b) Select the filter to classify traffic and the required action. Note: Only the traffic matching the filter will have the rules applied to it. 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 your units datasheet for the maximum number of specific filters possible for traffic policies. c) Select the EVC mapping encapsulation option and the required EVC mapping parameters. Refer to EVC Encapsulation Options. d) Select the PCP action for CoS mapping to perform if required. Refer to PCP Action Options. e) If you selected the PCP action MAP or Preserve, enable one or two traffic mapping choices, select the Type of traffic mapping to perform, select the CoS profile to apply and select the bandwidth Regulator set to apply. f) If you selected the PCP action Direct, fill in the Direct mapping parameters.
g) Click Apply. For more information on specific parameters, refer to the following table.
114
Description Filter type (L2 filter, IPv4 filter or VID set) to classify traffic. The name of the filter. By default, a catchAll" filter is defined. This enables you to monitor all traffic on a port. The action applied to traffic that matches the filter. The choices are: Drop traffic: The traffic matching the filter is dropped. Permit traffic: The traffic matching the filter is counted in the statistics then forwarded. MGMT-OAM: The traffic matching the filter is forwarded to the CPU so that it can be processed. MGMT-OAM & Drop: The traffic matching the filter is forwarded to the CPU so that it can be processed, then it is dropped. MGMT-OAM & Forward: The traffic matching the filter is forwarded to the CPU so that it can be processed and forwarded.
EVC mapping Encapsulation Encapsulation may be one of the following: None: Use this option to perform traffic regulation based on PCP, IP precedence or DSCP values. Push: Use this option to add a new VLAN. Push & Preserve: Use this to add a new VLAN using the VLAN ID of the inner VLAN (if any). Pop: Use this option to perform traffic regulation based on PCP, IP precedence or DSCP values before removing the VLAN tag. Replace: Use this option to perform an action similar to the Push action, but rather than adding a new VLAN tag, it replaces the VLAN tag with the information provided by Ethertype and VLAN ID parameters. The PCP action Preserve is not supported by this encapsulation option. However, the user can use the PCP action Map and the default 8P0D-8P0D CoS profile to preserve the incoming PCP value. Note that this action requires a filter that checks the presence of at least 1 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. The PCP action Preserve is not supported by this encapsulation option. However, the user can use the PCP action Map and the default 8P0D-8P0D CoS Profile to preserve the incoming PCP value. Note that this action requires a filter that checks the presence of 2 VLAN tags. Note that this option will vary the available PCP action choices.
115
Parameter Ethertype
Description Ethertype of the VLAN to be added (if any). Possible values: C-VLAN=0x8100 or S-VLAN=0x88A8.
VLAN ID
VLAN ID of the VLAN to be added (if any). Possible values: A value between 0 and 4095.
CoS mapping PCP action PCP (Priority Code Points) action to perform. 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. If the frame does not match the first or the second choice, default PCP bits are used. Note that the choices vary depending on the Encapsulation option and on the PCP action you selected. Enable Type Enable or disable the first and second traffic mapping choices. Type of Layer 2 traffic mapping to perform for the first and second choices. The choices are: PCP VLAN: Priority Code Point (p-bits) in 802.1Q tags PCP VLANinVLAN: Priority Code Point (p-bits) in 802.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. Bandwidth regulator set to apply from the list. The list includes the bandwidth regulator sets you created.
Default/Direct Bandwidth regulator Enable bandwidth regulation Pre-marking color Activates a default bandwidth regulator. If the PCP action is Map and the traffic does not match the configured maps, direct default mapping is used. Pre-mark, with a specific color, the traffic that does not match the first and second traffic mapping choices. This option has no effect if the enabled bandwidth regulator is color-blind. In addition, if no bandwidth regulator is enabled, this option selects the default green/yellow CFI & PCP values to be used in the outgoing frames. Green traffic uses buffers from CIR until depleted, at which time it will be tagged as Yellow data.
116
Parameter
Description Yellow traffic uses buffers from either CIR + EIR or just EIR depending on the coupling flag set in the regulator. Once CIR + EIR buffers are depleted, this data will be tagged as Red data. Red traffic is dropped. Please note, that it is not possible to pre-mark data as Red if its bandwidth regulator is disabled. Traffic color affects how the regulator handles the traffic.
Default bandwidth regulator associated with the traffic matched by this policy. The default CFI and PCP values to be applied if the Encapsulation is Push. This would only be applied if the traffic does not match the first and second traffic mapping choices.
117
118
In the other direction, the traffic goes from the network port directly to the client port without being shaped or queued. This is illustrated in the figure below.
119
120
Round robin of Queue-3 EIR between all client ports Note: Traffic from the traffic generator is not shaped.
In the other direction, the traffic goes from the network port directly to the client port, without being shaped or queued. This is illustrated in the figure below.
121
122
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. The global shaping rate of green packets expressed as a multiple of 125 Kbps.
123
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. However, checking this option allows debiting the network port CIR bucket. As a result the bucket could become negative. Uncheck this option to bypass the traffic shaping for the real-time queue. In other words, the real-time traffic will always be forwarded even if there are no tokens in the global CIR bucket. In both cases, the CIR bucket is debited. As a result the bucket could become negative when this option is unchecked.
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, The port associated with the PCP map. When checked (enabled), the pre-marking color is decoded from the DEI bit (Drop Eligible Indication). Otherwise, you can specify the PCP precolor.
The PCP precolor (Green or yellow) to be used by the shaper. This parameter is available only when Use DEI as precolor is unchecked.
Queue/Shaper
124
Bandwidth profile parameters CIR The shaping rate (in Kbps) of green packets (average output rate of the shaper).
125
Parameter Committed Information Rate CBS Committed Burst Size EIR Excess Information Rate EBS Excess Burst Size
Description The shaping rate of green packets expressed as a multiple of 125 Kbps.
The shaping burst (in Bytes) of green packets (maximum output burst of the shaper). The shaping burst of green packets expressed as a multiple of 256 Bytes. The shaping rate (in Kbps) of yellow packets (average output rate of the shaper). The shaping rate of yellow packets expressed as a multiple of 125 Kbps. The shaping burst (in Bytes) of yellow packets (maximum output burst of the shaper). The shaping burst of yellow packets expressed as a multiple of 256 Bytes
Queue management parameters Q-length Buffer's size in KB. The buffer is used to queue the packets in order to be transmitted later. The management of this buffer is done by the management queue algorithm BLUE. Once the queue fills to the specified percentage, the pm will be increased. Once the queue empties to the specified percentage, the pm will be decreased.
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 marking probability is incremented by this value if there is a buffer overflow. If this parameter is set to 0, the BLUE algorithm is disabled.
126
2. Click the real-time traffic shaper Name to view its PCP lists.
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. Total number of bytes sent to the network port from the specified source. Bit rate, in Mbps, of traffic sent to the network port from the specified source.
Go to Traffic > Shaping > Traffic shaper menu > BLUE statistics to show the instantaneous statistics of the queue management algorithm (BLUE). For more information on specific parameters, refer to the table below.
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. Color of the dropped traffic. Current marking probability steps. Marking probability value. This is equal to the number of Pm steps multiplied by 0.0096. Current queue level occupation in KB. Percent of queue usage.
127
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. By default, all PCPs are green. Total number of packets/bytes and rate (in Mbps) forwarded by this shaper without any delay. 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) dropped due to the shaper's queue overflow. Total number of packets/bytes and rate (in Mbps) dropped by the queue management algorithm (BLUE). Description The name assigned to this shaper. The rate (in Mbps) of dropped green packets. The rate (in Mbps) of dropped yellow packets.
Total bandwidth Total yellow Total green CIR The total number of yellow packets/bytes and rate (in Mbps) forwarded by this shaper. The total number of green packets/bytes and rate (in Mbps) forwarded by this shaper. In the summary page, this is the instantaneous rate (in Mbps) of green packets. In the detailed page, this is the total number of packets/bytes and rate forwarded by this shaper using the CIR bucket. Note that the Cfg value is the CIR you have configured, expressed (in Mbps). For the real-time shaper, this value is only shown when the port's global CIR is enabled. EIR In the summary page, this is the instantaneous rate (in Mbps) of yellow packets. In the detailed page, this is the total number of packets/bytes and rate forwarded by this shaper using the EIR bucket. Note that the Cfg value is the EIR you have configured (in Mbps). This value is not available for the real-time shaper.
128
For example, the protocol tunnelling operates by replacing the protocol's specific destination MAC address with a multicast address that is transparently transported by the transit equipment and reinserted in the original destination MAC when the traffic reaches the destination equipment. The Protocol Tunnelling function works with rules to filter traffic being processed. Each incoming frame is tested against each rule in order until it finds a match. When there is a match, the frame is processed according to the mode of operation (Drop, Forwarding, Tunnelling or Peering). If there is no match with any rule, the frame is discarded. In tunnelling mode, tags are unconditionally pushed to processed frames, with user-configurable fields for ethertype, VLAN tags and PCP/CFI. When the unit is in forwarding mode, you can set it to perform VLAN tagging on the processed frames. In forwarding mode, the following operations are supported: None: frames are forwarded unmodified. Push: frames are forwarded with an extra VLAN tag added. The tag is defined by the VLAN ID, PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. Pop: frames are forwarded, with the VLAN tag stripped. This mode is only available when VLAN Filtering is enabled, as tags cannot be removed from non-tagged frames. Replace: frames are forwarded with their VLAN tag replaced. The replacement tag is defined by the VLAN ID, PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. This mode is only available when VLAN Filtering is enabled, as tags cannot be replaced in non-tagged frames. To view a list of all existing L2PT rules go to Traffic > L2PT > Configuration. For an example of the display, see the figure below. For more information on specific parameters, refer to the table L2PT Configuration (Traffic > L2PT > Configuration).
To view statistics for all L2PT rules go to Traffic > L2PT > Statistics. For more information on specific parameters, refer to the following table.
129
Layer-2 Protocol Tunnelling Frame Statistics (Traffic > L2PT > Statistics)
Parameter Name Dropped Description Unique name assigned to the rule. Total number of dropped frames by this rule since its creation. This counter is incremented under the following circumstances: The rule is set for drop operation mode and a matching frame was received. The rule is set for tunnel operation mode and a matching frame was received, but there was a VLAN ID mismatch. i.e. the VLAN tags in the frame could not be matched to any of the VLAN groups in the rule's list. Tunnelled Total number of tunnelled frames by this rule since its creation. 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, had the required VLAN tags added and was sent to the outgoing port). Note that if there are multiple VLAN groups in the VLAN list, this counter is incremented for each frame transmitted on the outgoing port. De-tunnelled Total number of de-tunnelled frames by this rule since its creation. 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). Forwarded Total number of frames forwarded by this rule since its creation. 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, unmodified, to the outgoing port. Peered Total number of frames peered by this rule since its creation. 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.
Setting up an L2 Tunnel
You can define up to 64 L2PT rules. To add or edit a L2PT rule, proceed as follows: 1. Go to Traffic > L2PT > Configuration. 2. Check Enable L2PT rule to enable the processing of the Layer-2 Control Protocols according to L2PT rules. If needed, also check Enable VLAN Filtering to enable the filtering of incoming frames with matching VLAN ID and Ethertype. For more information on specific parameters, refer to L2PT Configuration. 3. Click the Add button to add a new L2PT rule or click the rule name of an existing rule to edit its settings.
130
4. Fill up the required field and click Apply. For more information on specific parameters, refer to L2PT Configuration.
Name L2PT rule name State Enable L2PT rule Protocol Mode Operation mode
The state of the rule. Allows a rule to be enabled or disabled without being deleted.
Layer-2 Control Protocol to be processed by a specific rule. This controls how the rule handles the traffic associated with the specified protocol. Operation mode may be one of the following: Drop: frames matching the specific rule are dropped. Forward: frames are sent unaltered from the incoming to the outgoing port. Optionally, EVC mapping can be enabled on forwarding rules (see EVC Mapping). 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. Frames matching the specific rule get their original destination MAC address put back when received on the specified network port. Peer: the frames are sent to software layers for further processing.
Normal or catchall rule. Catchall rules operate on all frames that were not matched by a specific rule and can be set for forward or drop operation modes. The multicast MAC address to use as a replacement when protocol tunnelling is performed. The following replacement MAC can be used: The Cisco replacement: 01:00:0C:CD:CD:D0 MAC is used. Because it cannot be altered, it can be used only once amongst all rules. The Accedian replacement: 01:15:AD:CC:xx:yy MAC is used. Because this replacement MAC has variable elements, 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. These variable elements are set as follows: xx: the unique ID specified in the configuration (see Unique ID). When creating a tunnel between two units, the unique ID is used to match the
131
Parameter
Description replacement frames going both ways on the network port. As such, it is important that the matching rules on both endpoints have the same unique ID. yy: the protocol ID. This is automatically generated according to which Layer-2 control protocol the rule handles.
This allows the incoming port used by the rule to be selected. The incoming port is considered to be the port where the layer-2 control protocols will be received. This allows the outgoing port used by the rule to be selected. The outgoing port is considered to be the port where the tunnelled frames, containing a replacement destination MAC, will be transmitted. The ID of a rule used when performing tunnelling. This value is used when building the replacement destination MAC address if the Accedian multicast address is used. Note that the same ID value has to be used on both sides when performing tunnelling between a pair of units.
Unique ID
VLAN Filtering VLAN filtering Enable Ethertype VID range VLAN ID range PCP Status of the VLAN filtering for this L2PT rule. Only the frames with a VLAN ID and Ethertype matching the ones specified in the VLAN ID range, PCP, CFI and Ethertype are accepted. The ethertype that this specific rule accepts in the inbound Layer-2 Control Protocol frames. The VLAN IDs that this specific rule accepts in the inbound Layer-2 Control Protocol frames. If filtering on a single VID is desired, enter the same value in both fields (From, To). The Priority Code Point that this rule accepts in the inbound Layer-2 Control Protocol frames. The choices are: 07: 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. 01: for a specific priority All: to accept any CFI EVC Mapping EVC Mapping Mode In forwarding operation mode, the following choices are available: None: frames are forwarded unmodified. Push: frames are forwarded with an extra VLAN tag added. This tag is defined by the VLAN ID, PCP and CFI fields and the Ethernet type is set to
132
Parameter
Description the value specified by the VLAN ethertype field. Pop: frames are forwarded with the VLAN tag stripped. This mode is only available when VLAN Filtering is enabled, as tags cannot be removed from non-tagged frames. Replace: frames are forwarded with their VLAN tag replaced. The replacement tag is defined by the VLAN ID, PCP and CFI fields and the Ethernet type is set to the value specified by the VLAN ethertype field. This mode is only available when VLAN Filtering is enabled, as tags cannot be replaced in non-tagged frames.
The ethertype of the tag inserted in the forwarded frame. This is available only in Forwarding mode. The ethertype of the first tag inserted in the tunnelled frame. This is available only in Tunnelling mode. The ethertype of the second tag inserted in the tunnelled frame (for Q-in-Q). This is available only in Tunnelling mode. The VLAN tags to insert in the forwarded frames. The VLAN ID field is available only in Forwarding mode. The VLAN tags to insert in the tunnelled frames. The format is a list of commaseparated groups formatted as vlan1:vlan2. Entry of the second tag (Q-in-Q) is optional. For example, if you wanted to single-tag tunnelled frames with VLAN ID 3, and double-tag frames with VLAN IDs 56 and 2288, you would specify: 3, 5:6, 22:88. Note that the frames are duplicated for each entry in the VLAN list. In the example above, three frames would be transmitted on the network port for each incoming frame matching the rule on the client port. Note also that there should be at least one entry in the list, as tunnelling untagged frames is currently not supported. The VLAN list is available only in Tunnelling 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. Map is available when the forwarding mode is either PUSH or REPLACE, and is mandatory in tunnelling mode. Preserve: The PCP and CFI fields of the processed frame are copied from the ones in the incoming frame. This mode is only available when the forwarding mode is REPLACE.
The Priority Code Point mapped to the processed frame in CoS Map mode. Range: 07.
133
Description The Canonical Format Indicator mapped to the processed frame in CoS Map mode. The CFI is defined by 1 bit in the Ethernet frame.
134
135
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. Active: Immediately searches for an OAM peer by sending OAMPDUs. Port used by this OAM instance.
Indicates whether OAM packets are tagged with a VLAN. For encapsulated packets only Maximum frame size for the OAM instance. This enables you to limit the impact of the extra OAM traffic on a link that is already heavily loaded. When Enabled, the unit responds to loopback requests from the OAM peer.
Number of times an event is re-transmitted to ensure its reception by the peer. This setting is valid only if This unit supports events is enabled. The threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. The window setting defines the time (in seconds) of the period. A frame error is an error detected at the layer 2, or MAC level. This can be caused by various types of errors including, but not limited to the following: CRC errors, short frames, long frames, etc. 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 number of frames that make up a period. Using a number of frames instead of a time period, as in EFE, means that this event is generated based on the ratio of bad frames versus good frames. A frame error is an error detected at the layer 2, or MAC, level. This can be caused by various types of errors including, but not limited to the following: CRC errors, short frames, long frames, etc.
136
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. An errored frame second is a one-second period in which at least one frame was bad. In other words, this event is generated when the number of seconds with any number of bad frames is greater than or equal to the threshold during a period defined by the window. The window setting defines the time, in seconds, of the period. A frame error is an error detected at the layer 2, or MAC, level. This can be caused by various types of errors including, but not limited to the following: CRC errors, short frames, long frames, etc.
137
Local Local flags Flags A string of seven bits corresponding to the Flags field in the most recently transmitted OAMPDU. The seven LSB bits are expressed as a hexadecimal value. For example, a hex value of 0x0004 converted to binary is 0000100: first bit = 0, second bit = 0, third bit = 1, etc. The first bit corresponds to the Link Fault bit in the Flags field. The second bit corresponds to the Dying Gasp bit in the Flags field. The third bit corresponds to the Critical Event bit in the Flags field. The fourth bit corresponds to the Local Evaluating bit in the Flags field. The fifth bit corresponds to the Local Stable bit in the Flags field. The sixth bit corresponds to the Remote Evaluating bit in the Flags field. The seventh bit corresponds to the Remote Stable bit in the Flags field. The value of the Revision field in the Local Information TLV of the most recently transmitted information OAMPDU. Note that the revision number indicates the number of times that the configuration for the local OAM instance has been modified. A string of three bits corresponding to the State field of the most recently transmitted Information OAMPDU. The first and second bits correspond to the Parser Action bits in the State field. The third bit corresponds to the Multiplexer Action bit in the State field. Note that these states will change when a loopback is enabled. Vendor OUI The value of the OUI variable in the Vendor Identifier field of the most recently transmitted information OAMPDU. This value is updated upon reception of a valid frame. The value of the Vendor Specific Information field of the most recently received information OAMPDU. This value is updated upon reception of a valid frame
138
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 seven LSB bits are expressed as a hexadecimal value. For example, a hex value of 0x0004 converted to binary is 0000100: first bit = 0, second bit = 0, third bit = 1, etc. The first bit corresponds to the Link Fault bit in the Flags field. The second bit corresponds to the Dying Gasp bit in the Flags field. The third bit corresponds to the Critical Event bit in the Flags field. The fourth bit corresponds to the Local Evaluating bit in the Flags field. The fifth bit corresponds to the Local Stable bit in the Flags field. The sixth bit corresponds to the Remote Evaluating bit in the Flags field. The seventh bit corresponds to the Remote Stable bit in the Flags field. The value of the Revision field in the Local Information TLV of the most recently received information OAMPDU. This value is updated upon reception of a valid frame.
A string of three bits corresponding to the State field of the most recently received information OAMPDU. The first and second bits correspond to the Parser Action bits in the State field. The third bit corresponds to the Multiplexer Action bit in the State field. Note that these states will change when a loopback is enabled.
The value of the OUI variable in the Vendor Identifier field of the most recently received information OAMPDU. The value of the Vendor Specific Information field of the most recently received information OAMPDU.
139
140
Description A count of the OAMPDUs received that contain the Event Notification code. This counter is incremented upon reception of a valid frame with the following: DestinationField equal to the reserved multicast address for slow protocols. LengthOrType value equal to the reserved Type for slow protocols. A slow protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Event Notification code. The Sequence Number is equal to the Sequence Number of the last received Event Notification OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period.
Loopback control
A count of OAMPDUs received that contain the Loopback Control code. This counter is incremented upon reception of a valid frame with the following: DestinationField equal to the reserved multicast address for slow protocols. LengthOrType value equal to the reserved Type for slow protocols. A slow protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Loopback Control code and is supported by the device. 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.
Variable request
A count of OAMPDUs received that contain the Variable Request code. This counter is incremented upon reception of a valid frame with the following: DestinationField equal to the reserved multicast address for slow protocols. LengthOrType value equal to the reserved Type for slow protocols. A slow protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Variable Request code and is supported by the device. 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.
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. LengthOrType value equal to the reserved Type for slow protocols. A slow protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Variable Response code and is supported by the device. 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.
Organization specific
A count of OAMPDUs received that contain the Organization Specific code. This counter is incremented upon reception of a valid frame, with:
141
Parameter
Description DestinationField equal to the reserved multicast address for slow protocols. LengthOrType value equal to the reserved Type for slow protocols. A slow protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Organization Specific code and is supported by the device. 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.
Transmit Unsupported codes A count of transmitted OAMPDUs that have unsupported codes. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code for a function that is not supported by the device. 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. Information A count of transmitted OAMPDUs containing the OAM Information 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. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. 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. A Slow_Protocols subtype equal to the subtype reserved for OAM. The OAMPDU code equals the Event Notification code. The Sequence Number is not equal to the Sequence Number of the last transmitted Event Notification OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames are transmitted in any one-second period. Duplicate 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. The OAMPDU code equals the Event Notification code. The Sequence Number is equal to the Sequence Number of the last transmitted Event Notification OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period. Loopback control A count of transmitted OAMPDUs containing the Loopback Control code. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Loopback Control OAMPDU. Generalized non-resettable counter. This counter has a maximum increment
142
Parameter
Description 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 Request OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period.
Variable request
Variable response
A count of transmitted OAMPDUs containing the Variable Response 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. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period.
Organization specific
A count of transmitted OAMPDUs containing the Organization Specific code. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating an Organization Specific OAMPDU. Generalized non-resettable counter. This counter has a maximum increment rate for slow protocol frames: no more than 10 frames shall be transmitted in any one-second period.
143
Setting up a Probe
Adding/Modifying a Probe
1. Go to PAA > Configuration. This displays a summary of all PAA probes. For more information on specific parameters, refer to the table at the end of this procedure. 2. Click Add to create a new probe or click the probe name to edit an existing probe. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table. Note: The fields available for configuration vary depending on the probe type and operation mode you select.
144
Parameter
Description Disabled: Disabled by configuration. Associating: Enabled and looking for peer. Associated: Enabled peer index resolved.
Local and Peer Indexes Local Index Remote Index Local identifier for the probe. When you add a PAA instance, omitting the local identifier or specifying 0 means to allocate any free local identifier. Remote peer identifier. When 0 is specified, the remote peer identifier is discovered dynamically based on the probe name in the association phase.
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. Encapsulate layer-2 PAA packets into a VLAN. Encapsulate layer-2 PAA packets into a VLANinVLAN. VLAN2 represents the outer VLAN. Applies only when VLAN 1 ID is enabled. First VLAN ID. When enabled, layer-2 PAA packets are encapsulated into the specified VLAN ID. Second VLAN ID. When enabled, layer-2 PAA packets are encapsulated into a second VLAN. Applies only when VLAN 1 ID is enabled. First VLAN Ethertype: C-VLAN or S-VLAN. Second VLAN Ethertype: C-VLAN or S-VLAN. Applies only when VLAN 2 is enabled. First VLAN priority bits. Applies only when VLAN 1 ID is enabled. Second VLAN priority bits. Applies only when VLAN 2 ID is enabled. Peer MAC address. When set to FF:FF:FF:FF:FF:FF, layer-2 peer address automatically finds the peer MAC address.
EVC fault propagation (for Layer-2 probe only) Enable fault propagation Propagate on port Use this PAA probe's status in fault propagation. 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. That port should also be set up to perform EVC fault propagation for this parameter to take effect.
UDP parameters (for UDP probe only) Destination IP address Peer IPV4 Destination address.
145
Parameter Destination Source UDP port Destination UDP port Diff-Serv Codepoint (DSCP) Explicit Congestion Notification (ECN) VLAN 1 Priority
Description
Source UDP port. Default is 8793. Destination UDP port. Default is 8793. DSCP class selector. Six (6) bits..
ECN value. This can be used to associate an ECN value to the PAA packets, simulating ECN in the customer network. The ECN bits are the last two bits of the IP ToS field. Range: 0-3 First VLAN priority bits. This can be used to associate a priority value for the first VLAN. 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. This value needs to be at least 10 times the value of the Sampling period. One-way delay allowed for each sample in the Reference period. It is used in conjunction with the Delay threshold (sample) to trigger the alarm PAA_OW_DELAY_ALERT. Number of consecutive samples exceeding the Maximum delay that are allowed before declaring the one-way delay alarm for this Reference period. Average one-way delay is calculated for the samples during the reference period. For example, for a reference period of 10 ms, the average is calculated from samples taken during the last 10 ms. Exceeding the threshold triggers the alarm PAA_OW_AVG_DELAY_ALERT. Maximum one-way delay variation threshold to monitor during a test period. It is used in conjunction with the Delay variation threshold (sample) to trigger the alarm PAA_OW_DV_ALERT. Number of consecutive samples exceeding the Maximum delay variation that Reference period (in ms) for the continuity measurements. This value needs to be at least 10 times the value of the Sampling period. Threshold (in %) at which an Excessive packet loss (EPL) alarm is declared. Number of consecutive sampling periods without receipt of peer samples before declaring a Continuity loss alarm.
146
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. Average one-way delay variation is calculated for the samples during the reference period. Exceeding the threshold triggers the alarm PAA_OW_AVG_DV_ALERT.
Reference period (in ms) for the two-way measurements. This value needs to be at least 10 times the value of the Sampling period. Two-way delay allowed for each sample in the Reference period. It is used in conjunction with the Delay threshold to trigger the alarm PAA_TW_DELAY_ALERT. 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. Exceeding the threshold triggers the alarm PAA_TW_AVG_DELAY_ALERT. Maximum two-way delay variation threshold to monitor during a test period. It is used in conjunction with the Delay variation threshold to trigger the alarm PAA_TW_DV_ALERT. Number of consecutive samples exceeding the Maximum delay variation that are allowed before declaring the two-way delay variation alarm for this Reference period. Average two-way delay variation is calculated from samples during the reference period. Exceeding the threshold triggers the alarm PAA_TW_AVG_DV_ALERT.
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 period needs to be a multiple of the One-way reference period. This parameter is valid only if the One-way Join Period is not 0. 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, IGMP join and leave delay measurements are performed for this period during which one-way and packet loss samples are collected. This value should represent how long to collect measurements before issuing an IGMP leave for each period. Possible values (in msec): 0 (default): Constant, no join and leave measurements Minimum: 10 * sampling period
147
Description Maximum: One-way reference period (5 * sampling period) The maximum join delay objective. 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)
The maximum join average delay. Possible values (in msec): Minimum: 100 msec Maximum: One-way join period The maximum leave delay objective. Possible values (in msec): 0 (default): No IGMP measurement Minimum: 100 msec Maximum: (One-way reference period) (One-way join period) The maximum consecutive leave delay samples allowed greater than the maximum leave delay before incrementing the Leave delay Nbr threshold exceeded. Possible values (in samples): Minimum: 1 Maximum: (One-way reference period One-way join period) / (Sampling period)
The maximum leave average delay. Possible values (in msec): Minimum: 100 msec Maximum: (One-way reference period) (One-way join period)
Deleting a Probe
1. Go to PAA > Configuration. 2. Click the probe name to delete. 3. Click Delete.
148
149
150
Description One-way instantaneous delay value (in microseconds). This is the latest oneway delay value measured when the window was last refreshed. Gives the results for the previous and current periods. The current period is indicated on the right of One-way delay.
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 fastest sample over the period. One-way delay (in microseconds) of the slowest sample over the period. Average delay (in microseconds) of the samples during the reference period. Number of times the one-way delay exceeded the value of the parameter Maximum delay.
One-way delay variation Instantaneous DV Period One-way instantaneous delay variation 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. 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). This is the latest two-way delay measured when the window was last refreshed. Gives the results for the previous and current periods. The current period is indicated on the right of Two-way delay. 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. Two-way delay (in microseconds) of the slowest samples over the period. Average two-way delay (in microseconds) of the samples during the reference Total number of samples in the period. One-way delay variation (in microseconds) of the samples with the smallest delay skew over the period. One-way delay (in microseconds) of the samples with the highest delay skew over the period. Average one-way delay variation (in microseconds) of the samples during the reference period. Number of times the one-way delay variation exceeded the value of the parameter Maximum DV.
151
Description period. Number of times the two-way delay exceeded the value of the parameter Maximum delay.
Two-way delay variation Instantaneous DV Period Two-way instantaneous delay variation (in microseconds). Gives the results for the previous and current periods. The current period is indicated on the right of Two-way delay variation. Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded IGMP Join delay Instantaneous delay Period The latest IGMP join delay value (in microseconds), measured when the window was last refreshed. Gives the results for the previous and current periods. The current period is to the right of IGMP Join delay. Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded Total number of samples in the period. IGMP join delay (in microseconds) of the fastest sample over the period. IGMP join delay (in microseconds) of the slowest sample over the period. Average delay (in microseconds) over the period. Number of times the IGMP join delay exceeded the value of Maximum Join delay. Total number of samples in the period. Two-way delay variation (in microseconds) of the samples with the smallest delay skew over the period. Two-way delay (in microseconds) of the samples with the highest delay skew over the period. Average Two-way delay variation (in microseconds) of the samples during the reference period. 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), measured when the window was last refreshed. Gives the results for the previous and current periods. The current period is on the right of IGMP Leave delay. Nbr samples Minimum Total number of samples in the period. IGMP leave delay (in microseconds) of the fastest sample over the period.
152
Description IGMP leave delay (in microseconds) of the slowest sample over the period. Average delay (in microseconds) over the period. 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. For more information on specific parameters, refer to the following table.
153
Description The direction in which the MEP faces on the port. The index of the Maintenance Domain with which the MEP is associated. The index of the MA (or MEG) with which the MP is associated. The MEPID of the MEP. The MAC address of the Maintenance Point.
154
155
156
Parameter Level
Description Maintenance Level of the Maintenance Association or Maintenance Entity Group. Possible values: 0-7
Required interval (in ms) between continuity check messages (CCM). What, if anything, is to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs. The choices are: None: None. Chassis: Chassis ID and chassis subtype. Manage: Management Address. Chassis & manage: Chassis ID, subtype and Mgmt Address. Defer: Determined by domain configuration or system configuration.
VLAN type
VLAN type associated with this Maintenance association or MEG. The choices are: None: The association is not attached to a VLAN and the content of the VLAN ID list is ignored. C-VLAN S-VLAN
VLAN ID list
List of VLANs associated with this Maintenance association or MEG. If you leave the VLAN ID empty, the association is not attached to a VLAN and the VLAN type is set to None implicitly. List of all MEPs, separated by a comma, associated with this Maintenance association or MEG.
MEPID list
157
Note: The local MEP starts sending CCM frames, but will display continuity errors. You must configure the other end-point for valid results to be displayed.
158
Parameter VLAN
Description to the MEP's MA/MEG. The value 0 indicates that either the Primary VLAN ID is that of the MEP's MA/MEG, or that the MEP's MA/MEG is associated with no VLAN ID. Priority parameter for CCMs and LTMs transmitted by the MEP. The possible values are 0-7, 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)
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. Time (in ms) for which defects must be present before a Fault Alarm is issued.
Time (in ms) for which defects must be absent before resetting a Fault Alarm.
Enables the use of this MEP's status in fault propagation. EVC client port to which the MEP status should be propagated. That port should also be set up to perform EVC fault propagation for this parameter to take effect.
159
Description The possible values are: Reset Defect Report defect Defect reported Defect clearing
The highest defect priority sent. 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). 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 MEP is not receiving CCMs from a MEP in its configured list. Active (A) or Inactive (I). The MEP is receiving invalid CCMs. Active (A) or Inactive (I).
Indicates whether Y.1731 Alarm Indication Signal (AIS) PDUs are received. Active (A) or Inactive (I). Some packet loss measurement defect is active (A) or inactive (I) for that MEP.
160
Description
Some delay measurement defect is active (A) or inactive (I) for that MEP.
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 was initiated from that MEP. The time at which the latest loopback request from that MEP was completed or was stopped. The number of loopback messages requested. The number of loopback messages transmitted. The number of loopback replies received. The number of loopback replies received whose content did not match the corresponding LBM. The number of loopback replies received with a duplicate LBR sequence number. The packet loss ratio evaluated during the latest request. The number of loopback replies missing. The number of gaps evaluated inside the LBR stream. The number of missing packets for the largest gap. The number of LBRs received whose sequence number did not match the expected one.
161
Description information from the MEP Database is to be returned. The operational state of the remote MEP IFF state machines. The possible values are: Idle Start Failed OK
State of the RDI bit in the last received CCM. Possible values are: True: the RDI bit was set. False: if no CCM message was received.
The MAC address of the remote MEP. The time at which the IFF Remote MEP state machine last entered either the failed or OK state. The value of the port status TLV received in the last CCM from the remote MEP (see section 21.5.4 Port Status TLV of 802.1ag for more details). Possible values are: --- (none 0): No CCM was received or no port status TLV was received in the last CCM. Blocked (1) Up (2)
The value of the interface status TLV received in the last CCM from the remote MEP (see section 21.5.5 Interface Status TLV of 802.1ag for more details). Possible values are: --- (0): No CCM was received or no interface status TLV was received in the last CCM. Up (1) Down (2) Testing (3) Unknown (4) Dormant (5)
162
Parameter
163
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. The total number of valid, 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. The total number of LTRs received when no linktrace request is active for that MEP. The total number of link trace replies dropped because of a bad MAC address.
164
Parameter
Set FDB only flag Bottom of table LTM sequence number Next seq. # Target MAC address Target MAC TTL F T Action
Enables the LTM to set the flag "UseFDBonly" (IEEE 802.1ag) or the flag "HWonly" (Y.1731).
Sequence number used by the latest link trace request initiated from that MEP.
Link trace time to live received in link trace responses. Forwarded. Indicates that the responder maintenance point did forward the LTM. Terminal MEP. Indicates that the responder maintenance point is a MEP. Indicates how the responder system processes frames targeted for the destination address specified by the LTM. Possible values are: RlyHit: The LTM reached a maintenance point whose MAC address matches the target MAC address. RlyFDB: The Egress Port was determined by consulting the Filtering Database. RlyMPDB: The Egress Port was determined by consulting the MIP CCM Database.
Which Type Length Values (TLVs) are included in link trace responses. TLV values included in link trace responses.
165
166
Parameter
Description Incremental: A Data TLV with incremental byte values is included. Pattern: A Data TLV based on a user data pattern is included.
Length
Pattern
User data pattern for the Data TLV. Format: ASCII characters
Bottom of table Loopback request Target MAC address Latest start time Latest end time Next seq.# Nbr LBM requested LBM requested Nbr LBM sent The number of LBM sent for the latest loopback request. When the loopback is not active, this number should be the same as the number of LBM requested. If not, this implies the loopback request was stopped by a management command. The number of loopback replies (LBR) received for the latest loopback request. Indicates whether a loopback request is active or inactive for that MEP. The target MAC address used for the latest loopback request. The time the latest loopback request was initiated for that MEP. The time the latest loopback request has completed or was stopped for that MEP. The sequence number for the next LBM initiated from that MEP. The number of LBM requested for the latest loopback request.
Nbr LBR received LBR received LBR with bad MSDU Nbr LBR duplicated Packet loss ratio Nbr packet lost Nbr gaps Largest gap
The number of LBR received with a content that did not match the corresponding LBM for the latest loopback request. The number of LBR received with a sequence number already received for the latest loopback request. The computed packet loss ratio for the latest loopback request. The number of missing LBR for the latest loopback request. The number of times a sequence of LBR was missing during the latest loopback request. The size in packets of the largest gap during the latest loopback request.
167
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.
168
Parameter interval Interval Reference period One-way delay Enable Maximum allowed value Instantaneous threshold Average threshold
Description
Enables One-way delay measurement for this DMM instance. Maximum one-way delay (in ms) in the Reference period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. Number of consecutive measurements exceeding the Maximum allowed value that triggers a one-way delay alarm for this Reference period. One-way average delay threshold (in ms) that triggers the average 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. . If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. Number of consecutive measurements exceeding the Maximum allowed value that triggers a two-way delay alarm for this Reference period. Two-way average delay threshold (in ms) that triggers the average two-way delay alarm for this Reference period. Check to enable One-way delay variation measurements for this DMM instance. Maximum one-way delay variation (in ms) to monitor in the Reference period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. Number of consecutive measurements exceeding the Maximum allowed value that triggers a one-way delay variation alarm for this Reference period. One-way average delay variation threshold (in ms) that triggers the average one-way delay variation alarm for this Reference period.
Two-way delay variation Enable Maximum allowed value Instantaneous threshold Indicates whether the Two-way delay variation is computed by this DMM instance. Maximum Two-way delay variation (in ms) to monitor in the Reference period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. Specify the number of consecutive measurements exceeding the Maximum allowed value that triggers a two-way delay variation alarm for this Reference period.
169
Description Specify the Two-way average delay variation threshold (in ms) that triggers the average two-way delay variation alarm for this Reference period.
170
Description The One-way instantaneous delay (in microseconds). Gives the results for the previous and current periods. 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 minimum delay (in microseconds) over one period. The maximum delay (in microseconds) over one period. The average delay in microseconds over one period. Number of times the one-way delay exceeded the value of the parameter Maximum delay.
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. 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, is equal to or greater than the instantaneous threshold. The One-way instantaneous delay variation (in microseconds). Gives the results for the previous and current periods. The previous period is indicated in Period time. 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. 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, is equal to or greater than the instantaneous threshold. The two-way instantaneous delay (in microseconds). Gives the results for the previous and current periods. The previous period is indicated in Period time. Total number of samples in the period. The minimum delay variation in microseconds over one period. The maximum delay variation in microseconds over one period. The average delay variation in microseconds over one period. Number of times the one-way delay variation exceeded the value of the parameter Maximum DV.
171
Parameter Nbr samples Minimum delay Maximum delay Average delay Nbr threshold exceeded
Description Total number of samples in the period. The minimum delay (in microseconds) over one period. The maximum delay (in microseconds) over one period. The average delay in microseconds over one period. Number of times the two-way delay exceeded the value of the parameter Maximum delay.
Two-way delay variation Average alarm Instantaneous alarm Instantaneous DV Period Indicates if an alarm is raised (Active) because the current average two-way delay variation is equal to or greater than the average threshold. Indicates if an alarm is raised (Active) because the consecutive amount of times the two-way delay variation was equal to or greater than the maximum value, is equal to or greater than the instantaneous threshold. The two-way instantaneous delay variation (in microseconds). Gives the results for the previous and current periods. The previous period is indicated in Period time. Nbr samples Minimum DV Maximum DV Average DV Nbr threshold exceeded Total number of samples in the period. The minimum delay variation in microseconds over one period. The maximum delay variation in microseconds over one period. The average delay variation in microseconds over one period. Number of times the two-way delay variation exceeded the value of the parameter Maximum DV.
172
173
Parameter Period
Description Same as MEP's CCM priority. The number of periods elapsed since measurement started. The previous period is indicated in Period time. Continuous results in the section below gives the packet loss since the last time the statistics were cleared.
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. Indicates if an alarm is raised (Active) because the number of packets lost, for the current period, is greater that the packet loss threshold. Packet loss ratio expressed as a percentage.
Number of expected packets during the reference period. This should normally correspond to the reference period divided by the interval unless the period is incomplete. Number of packets lost during the period. For the current period, it is a continuous value that is not set to zero at the beginning of the period. 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. Number of times packets were missing during the interval. For the current period, this counter is set to zero at the beginning of the period. Size in packets of the largest gap during the period. For the current period, this counter is set to zero at the beginning of the period.
174
2. Click Add to create a packet loss instance or click a packet loss instance name to edit an existing packet loss instance. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
175
The test results provide information on the packets sent and received, transmission rates, delay and delay variation.
176
You can use the traffic generator to generate one or two flows of testing traffic. Each flow describes the characteristics of the test traffic, such as traffic type and bit rate. The generator also gives results for each flow. Each flow can be set up for: Layer-2, Layer-3 traffic VLAN or VLAN-in-VLAN encapsulation of test traffic Different traffic types and payload patterns
177
178
Parameter
Description
First packet header settings and Second packet header settings Type The type of test traffic: Layer-2: Y.1731 LBM frames. Layer-2 Accedian: Y.1731 LBM frames with Accedian ethertype. Layer-2 generic: special Y.1731 opcode frames to be used only with MAC-Address swap based loopback devices. Layer-3: IP/UDP packets to perform a test across the multi-layered network. IP multicast: IP multicast packets to test multiple receiving points. MAC destination Y.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. Maintenance Entity Group level. For Layer-2 traffic only. Refer to ITU-T Y.1731. Range: 07 IP address of the remote unit. For Layer-3 traffic only. DiffServ Code Point to set in the generated packets. For Layer-3 traffic only. The source IP address used for the IP header. For IP multicast traffic only. Source UDP port number used to generate the UDP packet. For Layer-3 traffic only. Destination UDP port number used to generate the UDP packet. For Layer-3 traffic only. This encapsulates all packets with 1 VLAN header. First VLAN ID. When enabled, all test packets are encapsulated into the specified VLAN ID. First VLAN Ethernet type. Applies only when VLAN 1 header is enabled. The choices are: S-VLAN and C-VLAN First VLAN priority bits. Applies only when VLAN 1 header is enabled. First VLAN canonical format indicator (CFI). Applies only when VLAN 1 header is enabled. Encapsulates all packets with 2 VLAN headers (Q in Q). VLAN1 must be enabled to use 2 VLAN headers. Second VLAN ID. When enabled, all test packets are encapsulated into the second specified VLAN ID. Applies only when VLAN 2 header is enabled.
179
Description Second VLAN Ethernet type. Applies only when a VLAN 2 header is enabled. The choices are: S-VLAN and C-VLAN Second VLAN priority bits. Applies only when VLAN 2 header is enabled. Second VLAN canonical format indicator (CFI). Applies only when VLAN 2 header is enabled.
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. When Out-of-service flow type is selected, this field has no effect. Name assigned to the flow. For reference in the Results section. A description to identify the flow and its characteristics. For reference in the Results section. Type of traffic may be one of the following: Constant: To send packets at a specific bit rate (Kbps). You need to specify the Bit rate. Burst: To send a predefined number of packets at every period. You need to specify the Packets per burst. For Constant traffic type, specify the bit rate (in Kbps). Supported values are: 0 to < 12.5 Mbps (steps of 0.125 Mbps) > 13 Mbps to 1 Gbps (steps of 1 Mbps) For Burst traffic type, 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). You must select a bit rate that does not exceed the capacity of the outgoing port used for that test. Failure to do so will result in inaccurate results. Size type Packet sizes may be fixed or random. For fixed packet size, specify the packet size. For random packet size only, specify the Minimum and the Maximum packet sizes. The size of test packets varies randomly between the minimum and maximum values. Note that you may need to modify your port MTU sizes to accommodate your selection.
180
Description May be a fixed-data, incremental or random pattern in the payload part of the transmitted frames. For a fixed payload pattern, specify the 32 bit value, e.g. 0x12345678 For a random payload pattern, select one of the pre-configured patterns. For an incremental 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. Seconds: Stops after a specified number of seconds (Duration (secs)). Bytes: Stops after sending a specified number of bytes (Duration (bytes)). Packets: Stops after sending a specified number of packets (Duration (packets)).
181
Transmit statistics Transmitted packets Transmitted bytes Rate State Flow state Total packets transmitted by this flow for this test. Total bytes transmitted by this flow for this test. The transmitting bit rate in Mbps. The flow's current state may be one of the following: Waiting: Waiting to be started by the tester. Failed: The flow was deleted before the test was started. Running: The flow is currently running. Stopped: The tester stopped the flow before it completed. Completed: The flow reached its duration limit. Receive statistics Received packets Received bytes Rate OOO or duplicates Number of Total packets received by the generators analysis component for this test, after being looped back by the peer device. Total bytes received by this generator (analysis component) for this test. The receiving bit rate, in Mbps. Out-of-order or duplicate packets received by this generator (analysis component). Number of gaps in the numbered sequence. Each packet contains a sequence
182
Parameter gaps Maximum gap Two-way delay Instantaneous Average Average delay Minimum Maximum
Description number and a time-stamp to identify the gap. Maximum size (in frames) of the received gaps.
Two-way instantaneous delay (in ms). The delay is measured for each packet from the generator to the loopback device and back to the generator. Average two-way packet delay in microseconds. The delay is measured for each packet from the generator to the loopback device and back to the generator (analysis). Minimum two-way delay (in ms). Maximum two-way delay (in ms).
Two-way delay variation Instantaneous Two-way instantaneous delay variation value (in ms). The delay variation is measured for each set of two consecutive packets from the generator to the loopback device and back to the generator. Average two-way delay variation (in ms).
Average Average DV Minimum Maximum Test times Test started at Test stopped at
Minimum two-way delay variation (in ms). Maximum two-way delay variation (in ms).
When the test was started. When the test was completed or stopped.
183
184
Parameter Type
Description The type of test traffic being inspected: Layer-2: Y.1731 LBM frames. Layer-2 Accedian: Y.1731 LBM frames with Accedian ethertype. Layer-2 Generic: special Y.1731 opcode frames to be used only with loopback devices based on MAC-Address swap. Layer-2 Swap: special Y.1731 opcode compatible frames with only MAC swap device. Layer-3: IP/UDP packets to perform a test across the multi-layered network.
MAC destination Y.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. (i.e. if this monitor is set in terminal mode type, the MAC destination will be equal to the incoming port's MAC address). For Layer-2 traffic only. Maintenance Entity Group level. For Layer-2 traffic only. Refer to ITU-T Y.1731. Range: 07 IP address of the remote unit. For Layer-3 traffic only. Diff Serv Code Point to set in the generated packets. For Layer-3 traffic only. Source UDP port number used to generate the UDP packet. For Layer-3 traffic only. Destination UDP port number used to generate the UDP packet. For Layer-3 traffic only. This encapsulates all packets with one VLAN header. First VLAN ID. When enabled, all test packets are encapsulated under the specified VLAN ID. First VLAN Ethernet type. Applies only when VLAN 1 header is enabled. The choices are: S-VLAN and C-VLAN. First VLAN priority bits. Applies only when VLAN 1 header is enabled. First VLAN canonical format indicator (CFI). Applies only when VLAN 1 header is enabled. Encapsulates all packets with two VLAN headers (Q in Q). VLAN 2 must be enabled to use two VLAN headers. Second VLAN ID. When enabled, all test packets are encapsulated under the second specified VLAN ID. Applies only when VLAN 2 header is enabled. Second VLAN Ethernet type. Applies only when a VLAN 2 header is enabled. The choices are: S-VLAN and C-VLAN.
185
Description Second VLAN priority bits. Applies only when VLAN 2 header is enabled. Second VLAN canonical format indicator (CFI). Applies only when VLAN 2 header is enabled.
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. Total bytes received by this monitor. The receiving bit rate, in Mbps. Out of order or duplicate packets received by this monitor. Out of order frames/packets are frames/packets received in a different order from that in which they were sent. Number of gaps in the sequence. Each packet contains a sequence number and a time-stamp to identify the gap. Maximum size (in frames) of the gaps. Total packets received by the associated inspector with an error inside the payload. Total bytes of the packets received with an error inside the payload. Data rate in Mbps. This is the number of Mb received in the last second with an
186
One-way instantaneous delay in microseconds. Minimum delay in microseconds. Maximum delay in microseconds. Average delay in microseconds.
One-way delay variation Instantaneous Minimum Maximum Average One-way instantaneous delay variation in microseconds. Minimum delay variation in microseconds. Maximum delay variation in microseconds. Average delay variation in microseconds.
187
Enable delay
188
Description Check to enable frame loss test. The Frame loss test verifies that no frames are being lost according to the test settings. 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. For example, 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). Both tests must yield no frame loss to be successful, or a lower rate will then be tested. Note that the transmit/receive rate is an average rounded to the nearest Mbps. Therefore it is possible to have a small amount of loss without affecting the rate values displayed. Make sure to enter all required parameters in the throughput settings since some of its parameters are applicable for the frame loss test.
Enable backto-back
Check to enable back-to-back test. The Back-to-back test performs a burst according to the test settings. To be successful, the DUT must not create any frame loss for each burst. A pause of 2 s is taken after each burst. Make sure to enter all required parameters in the throughput settings since some of its parameters are applicable for the back-to-back test.
Peer settings Type The type of test traffic may be one of the following: Layer-2: Y.1731 LBM frames. Layer-2 Accedian: Y.1731 LBM frames with Accedian ethertype. Layer-2 generic: special Y.1731 opcode frames to be used only with MAC-Address swap based loopback devices. Layer-3: IP/UDP packets to perform a test across the multi-layered network. MAC destination Y.1731 MEG level The Peer MAC address. For Layer-2 traffic only. The Maintenance Entity Group level. For Layer-2 traffic only. Refer to ITU-T Y.1731. Range: 07 Destination IP address DSCP Source port Destination port The IP address of the remote unit interface. For Layer-3 traffic only. The DiffServ Code Point to set in the generated packets. For Layer-3 traffic only. Source UDP port number used to generate the UDP packet. For Layer-3 traffic only. Destination UDP port number used to generate the UDP packet. For Layer-3 traffic only.
189
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. First VLAN ID. When enabled, all test packets are encapsulated into the specified VLAN ID. First VLAN Ethernet type. Applies only when a VLAN 1 header is enabled. The choices are: S-VLAN and C-VLAN. First VLAN priority bits. Applies only when a VLAN 1 header is enabled. First VLAN canonical format indicator (CFI). Applies only when a VLAN 1 header is enabled. Encapsulates all packets with 2 VLAN headers (Q in Q). Second VLAN ID. When enabled, all test packets are encapsulated into the second specified VLAN ID. Second VLAN Ethernet type. Applies only when a VLAN 2 header is enabled. The choices are: S-VLAN and C-VLAN Second VLAN priority bits. Applies only when a VLAN 2 header is enabled. Second VLAN canonical format indicator (CFI). Applies only when a VLAN 2 header is enabled.
Throughput settings Trial duration The period (in seconds) of time for the throughput test Default: 60 s. Range: 1 to 1800 s. Maximum rate The upper bound of rates (in Mbps) to search for. Range: 1 to 1000 Mbps (1 Gbps). You must select a Maximum rate that does not exceed the capacity of the outgoing port used for that test suite. Failure to do so will result in inaccurate results. This parameter also applies for the delay and delay variation test, and for the frame loss test. Minimum rate The lower bound of rates (in Mbps) to search for. Range: 1 to 1000 Mbps (1 Gbps). You must select a Minimum rate that does not exceed the capacity of the outgoing port used for that test suite. Failure to do so will result in inaccurate results. This parameter also applies for the delay and delay variation test, and for the frame loss test.
190
Description The granularity (in Mbps) of the range. Range: greater than zero to the maximum rate.
Enable fine stepping in case of low bandwidth testing (below 12 Mbps). The Step size configured is no longer used. The step size use for the range is 125 kbps. This parameter also applies for the delay and delay variation test, and for the frame loss test.
Frame loss
The acceptable difference between measured frame losses (N x 0.1%). For example, a setting of 1 would mean a 0.1% frame loss would be acceptable and considered as no frame loss by the test. Default: 0, which means a target of no frame loss is allowed for defining full throughput, i.e. losing a single frame will cause the test to fail.
Select the frame sizes to test. By default, the Jumbo frame size is not selected as it was not a frame size defined by the RFC-2544 standard. Note that the frame size selected must be smaller than the port MTU. Selecting a higher frame size will prevent you from running the test.
Delay and delay variation settings Trial duration The period (in seconds) of time over which the test is run. Default: 120 s. Range: 1 to 1800 s. The Delay and delay variation test uses also the Maximum Rate, Minimum Rate and Fine Stepping values set in the Throughput settings. Frame loss The acceptable difference between measured frame losses (N x 0.1%). For example, a setting of 1 would mean a 0.1% frame loss would be acceptable and considered as no frame loss by the test. Default: 0, which means the target is no frame loss is allowed for defining full throughput , i.e. losing a single frame will cause the test to fail. Frame size settings Select the frame sizes to test. By default, the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard. Note that the frame size selected must be smaller than the port MTU. Selecting a higher frame size will prevent you from running the test. Frame loss settings Trial duration The period (in seconds) of time over which the test is run. Default: 60 s. Range: 1 to 1800 s. The frame loss test uses also the Maximum Rate, Minimum Rate and Fine Stepping values set in the Throughput settings. Step size The granularity (in Mbps) of the range.
191
Description Select the frame sizes to test. By default, the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard. Note that the frame size selected must be smaller than the port MTU. Selecting a higher frame size will prevent you from running the test.
Back to back settings Trial duration The period (in milliseconds) of time over which the test is run. Default: 2000 ms. Range: 1 to 10000 ms. Repeat The number of bursts to perform for each frame/packet size. A pause of 2 s is taken after each burst. Default: 50 times. Range: to 100 times. Frame size settings Select the frame sizes to test. By default, the Jumbo frame size is not selected as it is not a frame size defined by the RFC-2544 standard. Note that the frame size selected must be smaller than the port MTU. Selecting a higher frame size will prevent you from running the test.
192
Parameter
Description Failed: An error occurred during the test suite execution. Running: The test suite is currently running. Stopped: A user stopped the test suite during its execution. Completed: The Test suite has completed.
The description to identify the report. Who executed the test suite. Select the test suite you want to run for this report. The information relative to the report not included in the previous field.
To view, save or delete a test suite report, proceed as follows: 1. Go to RFC-2544 > Testsuite > Report. This displays a summary of all test suite reports. For more information on specific parameters, refer to the table RFC-2544 Generator Results (RFC-2544 > Generator > Results). 2. Click the Name of an existing test suite report to view its report file or to perform other actions. While a test is running, click on Stop to stop it. You can then on Save to save it on the management station as a text file or on Delete to delete it.
193
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
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, Exfo L2, Exfo L3, Custom). Remotely controlled loopback: Loops back traffic and is initiated upon the reception of a predefined packet type (JDSU/Acterna, Sunrise).
194
Location
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)
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
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
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
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
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
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
The unit provides alarm functions to monitor and report the status of the unit, of the traffic performance and of other components.
198
Description The delay after an event clears before the alarm notification clears.
Customizing Alarms
To customize an alarm, proceed as follows: 1. Go to System > Alarm > Configuration. This displays the settings for all alarms. For more information on specific parameters, refer to the table at the end of this procedure. 2. Click the number of the alarm that you want to edit. 3. Fill in the required fields and click Apply. For more information on specific parameters, refer to the following table.
199
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). If enabled, alarms are reported. The severity of the alarm. If LED reporting is enabled on the Alarm > General page, the Minor, Major and Critical alarms are indicated on the unit's front panel LEDs. Informational: No effect on service. Provides status information. Minor: An error condition has occurred that does not seriously affect system functionality. Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality. Critical: A service-affecting condition has occurred that requires immediate corrective action.
Alarms may be displayed as service affecting or non-service affecting. Textual description of the alarm. The description is displayed in the Show > Alarm page.
Viewing Alarms
Go to Show > Alarm to view alarm status. For more information on specific parameters, refer to the following table.
200
Parameter
Description BBBB: Instance number (1-999/1-9999). 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. 2: SFP module for Rx/Tx power, temp, vcc and lbc alarms and warnings. 3: PAA module for Continuity Check, Delay, Packet Loss and other related alarms. 4: SOAM module for Continuity Check, Delay, Packet Loss and other related alarms. 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). Severity of the alarm may be one of the following: Informational: No effect on service. Provides status information. Minor: An error condition has occurred that does not seriously affect system functionality. Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality. Critical: A service-affecting condition has occurred that requires immediate corrective action.
Alarms may be displayed as service affecting or non-service affecting. Textual description of the alarm. This is displayed only when the alarm has changed status (the alarm was turned ON or OFF). The message explains why it was turned on or off, e.g. temperature was above the threshold.
201
Refer to the following table for a list of all alarms supported and their default description.
Port module for link down and others related alarms 1.0001.01 1.0002.01 1.0003.01 1.0004.01 1.0005.01 1.0004.02 1.0005.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, temp, vcc and lbc. In this section, yyyy specifies the SFP module, where 0001 = SFP-A, 0002 = SFP-B, 0003 = SFP-C, and 0004 = SFP-D 2.yyyy.01 2.yyyy.02 2.yyyy.03 2.yyyy.04 2.yyyy.05 2.yyyy.06 2.yyyy.07 2.yyyy.08 2.yyyy.09 2.yyyy.10 2.yyyy.11 2.yyyy.12 2.yyyy.13 2.yyyy.14 2.yyyy.15 2.yyyy.16 2.yyyy.17 <SFP module> temperature high alarm <SFP module> temperature low alarm <SFP module> temperature high warning <SFP module> temperature low warning <SFP module> supply voltage high alarm <SFP module> supply voltage low alarm <SFP module> supply voltage high warning <SFP module> supply voltage low warning <SFP module> laser bias current high alarm <SFP module> laser bias current low alarm <SFP module> laser bias current high warning <SFP module> laser bias current low warning <SFP module> transmit power high alarm <SFP module> transmit power low alarm <SFP module> transmit power high warning <SFP module> transmit power low warning <SFP module> receive power high alarm
202
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. In this section, yyyy specifies the index of the PAA instance 3.yyyy.01 3.yyyy.02 3.yyyy.03 3.yyyy.04 3.yyyy.05 3.yyyy.06 3.yyyy.07 3.yyyy.08 3.yyyy.09 3.yyyy.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, Delay, Packet Loss and other related alarms Note that these alarms are dynamically created based on the MEPs configured. In this section, yyyy specifies the MEPID number 4.yyyy.01 4.yyyy.02 4.yyyy.03 4.yyyy.04 4.yyyy.05 4.yyyy.06 4.yyyy.07 4.yyyy.08 4.yyyy.09 4.yyyy.10 4.yyyy.11 4.yyyy.12 4.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
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.0001.01 7.0001.03 NTP client lost server communication GPS communicationmay affect one-way delay measurements
Environmental module for power supplies and temperature sensors 8.0000.01 8.0000.02 8.0000.03 8.0000.04 8.0000.05 8.0000.50 8.0000.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, proceed as follows: 1. Go to Show > Alarm. 2. Click the alarm number to view its detailed status. For more information on specific parameters, refer to the table Alarm Status (Show > Alarm).
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. A green light indicates that the power source is connected and is operating normally. A red light indicates that the power source is not connected or is not operating normally. Temperature sensor status Temperature sensor The current temperature inside the unit. First threshold: The temperature that will activate the first overheating alarm.
204
Parameter thresholds
Description Second threshold: The temperature that will activate the second overheating alarm.
205
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. Default value is 4. Set the log level as 0 to filter out all but emergency (system is unusable) messages as defined by RFC 3164. Debug level The debug level (0500). Use value 0 unless otherwise advised by the support representative. The host name or IP address of the HTTP proxy. A TCP Port for proxy communication.
206
You can also view the status of the EchoAgent at the bottom of the System > Agents > EchoAgent page. Click the Reset_Agent button to set all configuration parameters to default values and to disable the EchoAgent. To reinitiate the connection to EchoVault, you must re-enter all the information. Click the Refresh_status button to refresh the EchoAgent logs. Click the Restart_Agent button to disconnect the agent and reconnect it to EchoVault.
207
Parameter Read-Write community Enable authentication trap generation Enable link trap generation
Description The community string to control read/write access to the unit. Enables the unit to generate a trap when authentication to the agent fails.
Enables trap generation when link status changes. Map to the generic traps 2 (1.3.6.1.6.3.1.1.5.3 linkDown) and 3 (1.3.6.1.6.3.1.1.5.4 linkUp).
208
Description The community string required to send traps to the notification receiver.
UDP port the unit uses to send traps to the notification receiver. By default, the well-known SNMP trap port 162 is used.
209
Parameter
Period
The frequency, in minutes, with which history statistics should be stored in non-volatile memory.
210
Parameter
Description reports are generated at 3:00, 3:30, 15:00 and 15:30. If a device has all hours selected in the Scheduled hours, plus 00:15 and 00:45 in the Scheduled minutes with a Schedule offset of 4 minutes, reports are generated at the 19th and 49th minute of every hour.
Random offset
This allows a random offset to be generated, anywhere between 0 and the specified value. This random offset is added to the schedule offset. This allows multiple devices set to generate reports at the same time and to the same destination to be randomly offset from one another, relieving the burden created by several connections happening at once. Note that the combined value of the schedule offset and random offset can't exceed 15 minutes (900 seconds). If the sum of those two values exceeds 900 seconds, the random offset value is automatically set to the highest possible value.
File transfer Server URL The full URL of the Server on which to send the history bucket files once retrieved. Examples: http://mypc.com ftp://username:password@mypc.com tftp://192.168.1.5 SCP password File options Period mode This controls which periods to include in the reports. Three modes of operation are available. Note that this setting affects both local and remote history buckets. All available periods: All the periods that are available on the devices are used to generate the reports, up to a fixed maximum number of periods. New periods since last file transfer: All the periods that have been generated since the previous report. If Include periods from previous incomplete transfers is selected, the periods from a previous report that couldn't be properly generated or sent to the server are also included. Fixed number of periods: All the periods available, up to the maximum number of periods specified by the user in Local periods (for local reports) and Remote periods (for remote reports). Options This allows control over how the reports are generated. Include disabled objects: When checked, all managed objects are included in the reports. If unchecked, only objects which are enabled are included. Include periods from previous incomplete transfers: When checked, Password required by the SSH server.
211
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, only the periods since the previous report are included.
212