Accedian NID User Manual

EtherNID™ Administrator’s Guidefor the EtherNID™ EE EtherNID™ OE EtherNID™ GE MetroNID™ TE EtherNID™ DE+ 1 Release 3.1.3 (April 2008) Accedian Networks, EtherNID, EtherSHELF, MetroNID and Performance Assurance Agent (PAA) are 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 furnished 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 on this manual or the products it describes, address them to: Accedian Networks Inc. Attention: Publications 4878, Levy street, Suite 202 Saint-Laurent, Québec Canada H4R 2P1 Tel: (514) 331-6181 Fax: (514) 331-2210 Toll free: 1-866-685-8181 Accedian Networks Inc. may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligations to you. Copyright © 2005-2008 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. 2 Contents Setting the system date and time . . . . . . . . . . . . 31 Timezone and Daylight saving . . . . . . . . . . . . . . 32 SNMP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 SNMP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 34 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 Introducing the EtherNID . . . . . . . . . . . . . . . . . . . 6 Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . 7 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 History buckets . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 35 Remote retrieval of history buckets . . . . . . . . . . . 36 Scheduling and file transfer configuration . . . . . . . . 37 Application scenario . . . . . . . . . . . . . . . . . . . . . . . 8 Session management . . . . . . . . . . . . . . . . . . . . . 38 2 Management parameters . . . . . . . . . . . . . . . . . . . . 38 Hardware installation . . . . . . . . . . . . . . . . 9 Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . 9 Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Status lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . 39 Session configuration . . . . . . . . . . . . . . . . . . . . . 40 Session parameters. . . . . . . . . . . . . . . . . . . . . . . . . 40 Session management . . . . . . . . . . . . . . . . . . . . . 41 Management parameters . . . . . . . . . . . . . . . . . . . . 41 Mounting options . . . . . . . . . . . . . . . . . . . . . . . . 15 Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . 15 Rack mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Session RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 42 RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . 42 Management bridge . . . . . . . . . . . . . . . . . . . . . . 44 Configuration procedure . . . . . . . . . . . . . . . . . . . . . 44 Powering the EtherNID . . . . . . . . . . . . . . . . . . . . 19 Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Resetting to factory defaults . . . . . . . . . . . . . . . . 21 4 Port configuration . . . . . . . . . . . . . . . . . .46 Port list and port status . . . . . . . . . . . . . . . . . . . . 46 Port configuration and status . . . . . . . . . . . . . . . . . . 49 Port options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3 Management and configuration . . . . . . . 22 About the management web interface . . . . . . . . 22 Starting the management web interface . . . . . . . . . 22 Managing web interface accounts . . . . . . . . . . . . . . 22 Configuring port settings . . . . . . . . . . . . . . . . . . . 51 Port parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 PHY auto-negotiation configuration . . . . . . . . . . . 55 PHY parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 DNS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Configuring interfaces . . . . . . . . . . . . . . . . . . . . . 26 Creating or editing an interface . . . . . . . . . . . . . . . . 26 Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 27 SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . 57 SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 SFP thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 SFP memory and monitor memory . . . . . . . . . . . . . 61 Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Adding a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Route parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Cable verification . . . . . . . . . . . . . . . . . . . . . . . . . 62 Testing a cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Syslog options . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Syslog parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3 . . . . . . . . 111 OAM detailed statistics information . . . 131 Viewing RFC-2544 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 OAM configuration . . . . . . . . . . . . . . . . . . . . . Traffic filters . . . . . .117 RFC-2544 flows . . . . . . . . . 120 RFC-2544 measurements . . . . . . . . . 120 Viewing RFC-2544 Configuration . . . . . . . . . . . . . . . 80 Configuring an L2 filter on an EtherNID EE. . Administration and Maintenance . . . 77 Loopbacks . . . . . . . 132 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 65 65 66 67 67 68 69 70 70 70 71 71 Alarms . Access policies . . . . . 123 Bandwidth policing . . . . . . . . . 82 Viewing IPv4 filters. . . . . . . . . . .5 6 Monitoring and filtering . . . . . . . . . . . . . . . . . . . . . . 103 OAM events . . . . 117 Viewing RFC-2544 Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Viewing RFC-2544 Testsuites . . . 79 Viewing L2 filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 IPv4 filter parameters . . . 106 OAM status . . . . . . . . . . . . . . . . . . . . 98 Configuring an OAM instance . 118 RFC-2544 configuration . . . . . 91 RFC-2544 testsuite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Traffic filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OE or DE+ 81 L2 filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Viewing CoS profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 L2 filter parameters . 77 Policy settings . . . . . . . . . 79 Configuring an L2 filter on an EtherNID GE or MetroNID TE . Bandwidth regulator set parameters . 89 Configuring a regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Service mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 OAM instance parameters . . . . . . . . 99 Traffic policies and monitoring . . . . OE or DE+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Alarm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forwarding parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Configuring RFC-2544 Flows . . . . . . . . . . . . . . 90 Regulator settings . . . . . . . . . . . . . . . . . 90 Assigning a regulator to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Chassis alarms . . . . . . . . Assigning a Bandwidth regulator set to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring an IPv4 filter on an EtherNID EE. . . . . . . . . 102 Adding a loopback . . . . . . . Assigning a CoS profile to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Transmitted and Received event notifications . . . . . . . . . . . . . . . . . 122 Viewing RFC-2544 Measurements . . . . Configuring a CoS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Bandwidth regulator sets . . . . . . . 112 8 RFC-2544. . . . . . . . . . . 93 Customizing an alarm . . . . . . . Monitoring . . . . . . . 73 Policy settings . . . . . . . . . . . . . . . . . . . 126 Detailed view of RFC-2544 Testsuites . . . . . . . . . . . . . . . . . 86 IPv4 filter parameters . . . . . 122 Detailed view of RFC-2544 Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 RFC-2544 reports . . . . . . . . . . . . . . . . . . . . CoS Profile parameters . . . . . . . . . . . 94 Alarm status . . . . . . 92 Alarm configuration . . . 72 Configuring a traffic policy on an EtherNID GE or MetroNID TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Loopback parameters . . . . . . . . . . . . . . . 70 Operations. . . . . . . . . . . . . . . . . . . . . . Configuring a Bandwidth regulator set . . . . . . . . . . . . . . . . . . . . . . . . 83 Configuring an IPv4 filter on an EtherNID GE or MetroNID TE . 108 Detailed status information . . . . . . . . . . . . . . . 87 OAM statistics . . . . 97 7 Traffic forwarding . . OE or DE+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Configuring a traffic policy on an EtherNID EE. . . . . Configuring traffic forwarding . . . . . . . . . . . . . . 131 Starting an RFC-2544 Testsuite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Detailed PAA status . . . . 147 11 Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .MIB support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 5 . . . . . . . . . . . . . . . . . . . 143 10 Command Line Interface. . . . . . . . . 137 PAA status . . . . . . . . . . . . . . 151 Private MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarms . . . . . . . . . . . . . . . 134 PAA configuration . . . . . . . . . . . . . . 148 12 Appendix B . . . . . . . . . . . . . . . 145 Command syntax . 145 Command summary . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Performance Assurance Agent . . . . . . . . . . . . . . . . . . . . . . 141 PAA results . . . . . . . . . . . . . . . . . 134 Configuring a probe . . . . . 142 Detailed PAA results . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 PAA parameters. 148 Alarms . . . . . 151 Public MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1: Introduction Introducing the EtherNID Chapter 1: Introduction 1 Introduction Introducing the EtherNID The growing demand for Ethernet Services is exploding everywhere. avoiding dependency on end-customer's UPS. thus offering independent Monitoring Access to each direction independently. a function that carriers are used-to with traditional demarcation devices but lacking from current Ethernet service delivery methods. Administration and Maintenance (OAM). The EtherNID comes equipped with two Monitor Ports where external test equipment can be connected to perform non-intrusive troubleshooting. especially when adding cascaded network devices. Carriers contending in this competitive market space are faced with several challenges: • • • Setting a clear Demarcation Point between the Customers' and the Carriers' Ethernet Network. Implementing Operations. two parameters critical in real-time applications such as Voice and Video over IP. while the service is running. the EtherNID allows combining both signal directions on a single Monitor Access port by using a Port Mirroring function. Accedian's EtherNID Demarcation Point offers a solution to address these challenges by implementing standards-based Ethernet OAM and loop-back capabilities as part of the industry's first Line-Powered Ethernet NID (patent pending). to reduce operational expenses and minimize truck-roll. Furthermore. The Performance Assurance Agent™ (PAA™) allows measuring and tracking End-to-End SLA parameters such as Latency. meeting the reliability objectives that carriers have come to expect from telecom demarcation units. The EtherNID interacts seamlessly with Ethernet OAM compliant devices. All of this while optimizing end-to-end Network Performance and keeping capital expenses at a minimum.3af standard Power over Ethernet (PoE). comes with an embedded Web Server User Interface and can be optionally managed directly via SNMP. Accedian's EtherNID’s unique Fast-Thru™ architecture minimizes packet-jitter and latency. thus. 6 . the EtherNID implements a transparent fail-safe bypass. Designed cost effectively for volume deployment. Additionally. Jitter. the EtherNID allows for systematic installation on every customer Ethernet line and therefore obtaining a consistent look & feel across the network. Packet Loss and Availability in a continuous manner. Accedian's EtherNID extends the reliability of the Carrier's Network all the way to the customer's IT closet. Installed in-line on the Ethernet media. Offering Carrier-Grade Reliability. By using the EtherNID's 802. Sectionalizes Multi-Carrier E-lines. Allows offering full NID power responsibility and reliability as a value-added SLA. management and easier maintenance. The EtherNID’s ultra-compact form factor also allows for high-density rackmount installation. Extends the Network's OAM capabilities all the way to the customer's IT closet. Line-Powered via PoE — 48V power-plant reliability brought up to the IT closet Fail-safe Bypass — No impact on the MTBF of the E-Line Fast-Thru ™ Architecture — Minimizes Packet Jitter and Latency. Increases service reliability and availability. providing non-intrusive Monitor Access to each direction or combined access to both directions using port mirroring.1: Introduction Introducing the EtherNID Features and benefits • • • • • • • • • • • • Ethernet OAM & loop-back — Increases visibility. Applications • • • Acts as an Ethernet OAM extension for Metro Access Platforms. Increases end-customer satisfaction. Eliminates finger pointing. (important for Video & VoIP) Dual Tap/Mirror ports — Allows non-intrusive Monitor Access Creates a clear demarcation point between the Carrier's and Customer's Network. Adds Ethernet OAM capability to legacy media-converters and Access Platforms. 7 . Reduces Carrier's operational expenses by reducing truck-roll. Its fail-safe bypass architecture allows it to be used as a Modular Intelligent Ethernet Patch Panel. Customer device is the customer-owned switch or router residing on the customer’s network. or Microsoft Internet Explorer 6. Access to the EtherNID management web interface occurs through a secure shell (SSL) via a web browser session and requires a JavaScript-enabled Web browser such as Firefox 1. Transport media provides connectivity between the carrier site and the customer premises. Test equipment provides the test suite that is used to validate the link to the customer premises. • • • • • • 8 . This station can be eliminated if a DHCP server is available on the network.0 or higher. Local management station is the computer that is used to define initial configuration settings on the EtherNID when it is installed.0 or higher. Access node provides network connectivity for one or more customer devices at a remote location. Hub node provides network connectivity for the carrier site. In this case the DHCP server can be configured to provide a specific IP address to the EtherNID based on its MAC address. Carrier Site Remote Site Remote Site Customer Site Remote Management Station Hub Node Test Equipment Customer traffic Local Management Station Management port Transport Media Access Node Network port EtherNIDTM Client port Customer Device Demarcation point Test traffic Legend Test traffic Test traffic looped back Customer traffic Ethernet connection About this scenario: • Remote Management station is a computer that is used to remotely manage the EtherNID and to setup loopbacks.1: Introduction Application scenario Application scenario The following scenario illustrates how the EtherNID can be used to provide a remotely manageable customer premises demarcation point for the delivery of Ethernet services. DE+ and MetroNID TE Rear panel .EtherNID GE.2: Hardware installation Hardware overview Chapter 2: Hardware installation 2 Hardware installation Hardware overview Front panel .EtherNID OE Front panel .EtherNID EE Front panel .All units 9 . depending on the model. Model EE SFP N/A RJ-45 10Base-THD/TFD 100Base-TX/TXHD/TXFD (Auto-negotiation/Auto MDIX) OE 100Base-BX10D/BX10U/FX/F XHD/FXFD/LX10 10Base-THD/TFD 100Base-TX/TXHD/TXFD (Auto-negotiation/Auto MDIX) 10Base-THD/TFD 100Base-TX/TXFD 1000Base-T/TFD (Auto-negotiation/Auto MDIX) GE / TE Fiber SFP 100Base-BX10D/BX10U/FX/F XFD/LX10 1000Base-BX10D/BX10U/LX/L XFD/LX10/SX/SXFD/T/TFD (Auto-negotiation) Copper SFP 10Base-TFD 100Base-TX/TXFD 1000Base-T/TFD (Auto-negotiation/Auto MDIX) 10 . auto-MDIX and have RJ-45 connectors. N/A Flashing Port is receiving data. Port functionality The following table lists the capabilities of each port. Each port has two indicator lights as follows: Light Link/RX TX Solid Port is connected at the link layer.2: Hardware installation Hardware overview Front panel The front panel features different ports and status lights depending on the model. Port is transmitting data SFP ports All SFP ports are compliant with INF-8074 and must be connected to SFP modules that are class 1 lasers and are compliant with IEC825-1. supporting auto-negotiation. Ethernet ports All Ethernet ports are 10/100/1000BaseT or 10/100BaseT Ethernet. SFP-B: By default this port is configured for traffic monitoring. • • 11 . this port is set to the static IP address 192.1. • • • • EtherNID OE • Management: For connection of a local management station.1. this port is set to the static IP address 192.168. RJ-45-A: This port is configured for connection to the client network.254/24 and connection is made by using an SSL or SSH Client.3af).3af). RJ-45-A: This port is configured for connection to the client network.254/24 and connection is made by using an SSL or SSH Client. EtherNID EE • Management: For connection of a local management station. RJ-45-B: This port is configured for connection to the carrier network and is set to operate as a DHCP client. By default. Configuration can be changed using the management web interface. This is an Ethernet port that provides support for PoE (803.3af). This configuration can be changed using the management web interface.168. Monitor 2: Configured for traffic monitoring. • • • • EtherNID GE / MetroNID TE • • • SFP-A: By default.168. Monitor 1: Configured for traffic monitoring. this port is set to the static IP address 192. Use the management web interface to change these settings as required by your installation. Management: For connection of a local management station.2: Hardware installation Hardware overview DE+ Fiber SFP 100Base-BX10D/BX10U/FX/F XFD/LX10 (Auto-negotiation) Copper SFP 10Base-TFD 100Base-TX/TXFD (Auto-negotiation/Auto MDIX) 10Base-THD/TFD 100Base-TX/TXFD (Auto-negotiation/Auto MDIX) The following describes the factory default configuration settings for all ports. this port is configured for connection to the client network. RJ-45-B: This port is configured for connection to the carrier network and is set to operate as a DHCP client. SFP-B: By default this port is configured for connection to the carrier network and is set to operate as a DHCP client. Monitor 1: Configured for traffic monitoring. RJ-45-A: This port is configured for connection to the client network.254/24 and connection is made by using an SSL or SSH Client.1. This is an Ethernet port that provides support for PoE (803. By default. By default. This port supports PoE (803. Monitor 2: Configured for traffic monitoring. SFP-B: By default.254/24 and connection is made by using an SSL or SSH Client.2: Hardware installation Hardware overview EtherNID DE+ • SFP-A: By default. RJ-45-A: By default. Configuration can be changed using the management web interface however this port must remain on NID-1. this port is configured for connection to the carrier network-1. By default. Management: For connection of a local management station. • • • • 12 . this port is configured for connection to the client network-2.168. this port is configured for connection to the carrier network-2.1. Configuration can be changed using the management web interface however this port must remain on NID-1. Configuration can be changed using the management web interface however this port must remain on NID-2. Configuration can be changed using the management web interface however this port must remain on NID-2. RJ-45-B: By default. this port is configured for connection to the client network-1. this port is set to the static IP address 192. SFP (green): • • TX: Flashes when the port transmits data. MAJ (red): On when a major alarm condition is present. LPBK (yellow): On when the loopback function is enabled.25A connector: For use with the EtherSHELF connectors or a discrete power cord (connector sold separately) providing +/-40 to +/-57 V DC. Pin-outs for both ends of the console cable are as follows: RJ-45 Cable Console 8 DB-9 Female 1 1 TERMINAL 6 9 5 13 . Console: RJ-45 serial connection for access to the console interface. Link/RX: Solid when the link level is present.2: Hardware installation Hardware overview Status lights • • • • • • PWR (green): On when power is applied. MIN (yellow): On when a minor alarm condition is present. Flashes when traffic is being looped-back. Rear panel The rear panels on all units are identical. Flashes when the port receives data. Port/Connectors • • • +/-40-57V---0. 5V---2A connector: For use with the DC power adapter. CRIT (red): On when a critical alarm condition is present. Buttons The Bypass and Loopback buttons are used to reset the EtherNID.2: Hardware installation Hardware overview RJ-45 Connector Pins # 1 2 3 4 5 6 7 8 Signals Not connected Not connected Tx Data Ground Ground Rx Data Not connected Not connected 2 5 5 3 DB-9 Connector Pins # Signals Rx Data Ground Ground Tx Data To establish a connection with the CLI interface on the EtherNID from your computer. 14 . See "Resetting to factory defaults" on page 21 for instructions. use a terminal emulation program with the following settings: • • • • • • • Protocol: Serial Port: COM1 to 8 Baud rate: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: None Status light • 5V: On when power is applied via the power adapter. 15 .4 pounds) cable pull (accidental or otherwise) does not make the unit exceed the 2 kg (4. Attach the brackets as follows: Screw Screw Mounting bracket When mounting the EtherNID on a wall. ensure that: • • the surface you attach the EtherNID to and the fasteners you use are able to support at least 2 kg (4.2: Hardware installation Mounting options Mounting options Several different mounting options are available as described in this section.4 pound) limit Desktop installation Attach the included rubber feet to the bottom of the unit for added stability when placing on a desktop or other flat surface. Wall mounting Optional brackets and screws are available for mounting the EtherNID on a wall. 2. Turn OFF power to the unit. and then tape the switch handle of the circuit breaker in the OFF position. 5. Remove all network interface cables. 16 . To ensure that all power is OFF. (20 mm). locate the circuit breaker on the panel board that services the DC circuit. Warning: Before proceeding to the next step. Use a Phillips #2 screwdriver to fasten the ground lug to the bottom hole on the left side of the unit (towards the rear) using a 4-40. switch the circuit breaker to the OFF position. 3/16 stainless steel screw with an oversized washer.75 in. Strip one end of a 10-AWG wire to expose approximately 0. However. Crimp the ground lug around the exposed wire.2: Hardware installation Mounting options Rack mounting To install the EtherNID in a standard 19” rack. do not unplug the power cable. ensure that power is removed from the DC circuit. An optional 1U bracket is available that can hold two units. attach the optional 1U rack mount bracket as shown. Grounding the EtherNID Connect the EtherNID to a ground point on the rack as follows: 1. 3. 4. to channel ESD voltages to ground. Connect the other end of the wire to a grounding point on the rack. Warning: Before proceeding to the next step. To mount an EtherNID in the EtherSHELF. L-shaped brackets must be attached to the left and right side of the unit. ensure that power is removed from the DC circuit. 4U shelf is available for large-scale installations. However.2: Hardware installation Mounting options EtherSHELF The EtherSHELF. locate the circuit breaker on the panel board that services the DC circuit. To ensure that all power is OFF. 3. an optional 12 unit. do not unplug the power cable. Crimp the two-hole grounding lug around the exposed wire. to channel ESD voltages to ground. switch the circuit breaker to the OFF position. (20 mm). Strip one end of a 10-AWG wire to expose approximately 0. 2. Attach brackets before mounting in the drawer. Turn OFF power to the shelf. 17 . Remove all network interface cables. Grounding the EtherSHELF Connect the EtherSHELF to a ground point on the rack as follows: 1.75 in. and then tape the switch handle of the circuit breaker in the OFF position. 2: Hardware installation Mounting options 4. 18 . Connect the other end of the wire to a grounding point on the rack. Use a small wrench to tighten the bolts around the two grounding screws to secure the two-hole grounding lug to the back of the EtherSHELF 5. The Terminal Block Adapter fastens to the back of the EtherNID to provide such an installation. Voltage must be in the range +/-40 to +/-57 V DC using AWG 14 gauge or larger cable.2: Hardware installation Powering the EtherNID Powering the EtherNID The EtherNID can be powered using one of the following options: Power over Ethernet (PoE) The EtherNID can be powered via the network port using any 802. 48V DC from the 12 unit EtherSHELF You can power EtherNIDs mounted in the EtherSHELF using the shelf’s built-in 48 V DC power connector. it is sometimes preferable to use 48V DC power through directly secured wires as opposed to the DC power adapter. 19 . DC power adapter Connect the supplied power adapter to the 5V/2A DC connector on the rear of the unit. located at the bottom right on the back of the Terminal Block Adapter. The EtherSHELF’s power feed must be limited with a 5A/48V fuse. 48V DC from the Terminal Block Adapter In a 1U rack mount bracket installation. To ground the Terminal Block Adapter. Slide the EtherNID into the shelf to engage the power connector on the rear of the unit.3af-compliant power injector. to secure the grounding lug. use a small wrench to tighten the bolt around the grounding screw. There should be one fuse per power feed.2: Hardware installation Powering the EtherNID 48V DC via discrete power cord It is possible to power units with a custom built 48V DC power cable.250 0.48V Return is being used with the Terminal Block Adapter. Wall mounting is not allowed. Warning: Fuses must be installed on the live wire(s) and not on the grounded wire(s).25A).48V Return • I007-… or more then the unit has an isolated +/. then the two +/.48V Return A and B If an EtherNID™ with a Common +/. the unit must be installed horizontally to meet all applicable safety regulations. please refer to the sticker on the Rear Panel of the unit. Removing fuses can be used as a disconnect method. 20 .48V Return screws corresponding to the “RTN FEED A” and “RTN FEED B” on the Terminal Block Adapter must be tied together: Terminal Block Adapter with Return Feeds tied The power source (+/-40 to +/-57 V DC) must be limited by a 0. whereas other models will have an isolated Return A and Return B.48V Return Isolated +/. Therefore.48V connector on the rear panel of the EtherNID™: Common +/. To locate your serial number. Warning: Disconnect all power sources (feed A and feed B) when servicing.48V Return A and Return B • P005-… or more then the unit has an isolated +/. supported mounting options are desktop mounting or 1 or 2 unit rack mounting. the +/. If the serial number starts with: • I006-… or less then the unit has a common +/.48V Return A and Return B The following diagram depicts the pin-out of the white +/.48V Return • P004-… or less then the unit has a common +/.25A/48V slow blow fuse or equivalent (Little fuse 0217.48V Return is common to both Feed A and Feed B. When powered in this manner. On older models of the EtherNID™. 3. Press and release the Loopback button. 3. The unit will restart. Resetting to factory defaults To reset the EtherNID to factory default settings: 1. If required. Continue to press the Bypass button until the following lights all flash at the same time: • • • • Minor Major Critical Power 4. Press and hold the Bypass button. Press and hold the Bypass button. the EtherNID can also be restarted using the command line interface. See Chapter 10 for details. Release the Bypass button. 2.2: Hardware installation Restarting Restarting To restart the EtherNID: 1. 2. Press and release the Loopback button. Release the Bypass button. 21 . It is recommended that you change the default password immediately after installation to safeguard the system. a computer must: • • have a JavaScript-enabled Web browser installed (Firefox 1. The management station is the computer that you use to connect to the management web interface. be able to establish an IP connection with the EtherNID Starting the management web interface To start the management interface.254 and press Enter. Configure the computer with the static IP address 192.3af) to power-up the EtherNID. via an SSL client. Start your Web browser and specify the following in the address box: https://192. To act as a management station. 5. or Internet Explorer 6. The administrator account provides access to all EtherNID features. to all EtherNID control. The EtherNID login page opens.2. The username and password are case-sensitive. and monitoring functions. Connect the power adaptor or use PoE (802.168. Managing web interface accounts One administrator account is created by default with username and password both set to admin. 22 . do the following: 1.3: Management and configuration About the management web interface Chapter 3: Management and configuration 3 Management and configuration About the management web interface The web-based management web interface provides secure access.0 or higher).0 or higher. 3. Use an Ethernet cable to connect the LAN port on a computer to the management port on the front of the EtherNID.1. Login as admin with the Password admin. management. 4.1. 2.168. Specify the new password. 3. 23 . confirm it. Changing the default administrator password 1. Click Apply. 2. Lost administrator password If you forget the username or password the only way to gain access to the management web interface is to perform a factory reset as described in "Resetting to factory defaults" on page 21.3: Management and configuration About the management web interface Managing accounts Administrator accounts are managed on the Session > Users page. Open the Session > Users page and click admin in the list. 2. specify the new user name and other details. 24 . Open the Session > Users page and click Add. 3. In the new user setting box. Click Apply.3: Management and configuration About the management web interface Creating additional accounts 1. Use DHCP results Set DNS manually In either case. You can either choose to use the DNS settings obtained via DHCP on a specific port. Note: The default host name is the serial number of the NID and will be displayed in the banner at the top of the management web interface.3: Management and configuration DNS settings DNS settings To define DNS options. or manually set DNS settings. you can define the host name for the EtherNID. 25 . open the System > DNS page. Define interface parameters as required by your setup and then click Apply. Click the Add button to add a new interface. Open the System > Interface page. if you click the Management interface you will see: Note: Different fields will appear depending on the selections you make for Interface type. two interfaces are defined: • Management: This is the default interface that enables access to the management web interface via the management port. This includes defining bridges and VLANs.3: Management and configuration Configuring interfaces Configuring interfaces The EtherNID lets you define multiple logical interfaces for management purposes that can be active on different ports. To see a list of all logical interfaces. For example. 3. or click the name of an existing interface to edit its settings. • Creating or editing an interface To create or edit an interface. If you modify this interface you may lose access to the management web interface. do the following: 1. 2. By default. Network: This is the default interface active on the network port. Open the System > Interface page. 26 . Automatic IP (DHCP) Select this option to have the interface act as a DHCP client and automatically obtain its IP address. VLAN: VLAN interface associated with a single port. select multiple ports by holding down the control key when you click on port names in the list. Manual configuration Select this option to manually configure IP addressing settings. to create a default gateway. Select one of the following options: • • • • Standard: Standard IP interface associated with a single port. Network mask: Specify the network mask associated with the IP address. DNS server. Bridge: Bridged interface than connects two or more ports.1q in . VLANinVLAN: VLAN in VLAN (. On port(s) Select the port the interface will be active on. Gateway address: Specify a default gateway address. Interface type Sets the interface type to use.) Specify the VLAN ID (Management VLAN) to assign to the interface. it will be applied to the EtherNID. Valid Ethertypes are: 0x8100 (C-VLAN) and/or 0x88A8 (S-VLAN). VLAN ID (Only available when Interface type is set to VLAN or VLANinVLAN. Ethertype (Only available when Interface type is set to VLANinVLAN. For example.0 when the interface is not required to be an IP interface. when the interface is used for OAM or test set interaction. to route configuration. This provides a shortcut alternative. Use DHCP route information If the DHCP server has routing information. and gateway settings from a DHCP server.) Specify the Ethertypes for the first and second VLAN IDs. Interface name Specify a name to identify the interface.1q) interface associated with a single port. • • • IP address: Specify an IP address to assign to the interface.0. In the case of a bridge.0. 27 .3: Management and configuration Configuring interfaces Interface parameters Note: It is valid to set the IP address for an interface to 0. which shows all active routes on the EtherNID. Open the System > Routes page. Define route parameters as required by your setup and then click Apply.3: Management and configuration Routes Routes Select System > Interface to open the routes pages. no routes are defined. 28 . Adding a route To add a system route. Initially. do the following: 1. 2. 3. Click the Add button in the Routes box. Type Select a route type: • • Network Host Interface Select the interface to which the route is associated. Note: This field is optional if a matching active route is already associated to the interface. 29 . Network mask Specify the mask to assign to the route.0.3: Management and configuration Routes Route parameters Name Specify the name to assign to the route. Gateway Specify the gateway associated with this route. Only used for routes of type Network. Destination Network or host address of the route.0. Use 0.0 for default. 30 . then all messages with level CRITICAL. Remote syslog configuration Remote syslog enable Enables the sending of messages to a remote syslog server. If CRITICAL level is selected. ALERT or EMERGENCY will be logged. For example. Syslog parameters Facility configuration Device facility All messages are logged using this user defined facility instead of the default ones. open the System > Syslog page. Syslog information can be sent to a remote server by setting the options in the Remote Syslog Configuration box. The syslog page displays all syslog entries with the most recent entry at the top. Host Specify the IP address or domain name of the remote syslog server. Configure these options as required and then click Apply.3: Management and configuration Syslog options Syslog options To define syslog options. Level configuration Level threshold Log all messages with level equal to or above the selected one in the drop down list. To add a new server. Select a time server from the list. 2. Open the System > Time page. 31 . The EtherNID can also act as an NTP server by selecting the NTP server enable option.3: Management and configuration Setting the system date and time Setting the system date and time To set the system date and time. Then select the new server in the list and click Apply. The following options will be displayed: 3. 4. select the NTP enable option. Specify the current date and time and click Apply or to automatically update the system date and time using the Network Time protocol. do the following: 1. specify its name or IP address in the Added Server box and then click add. Min=0 DST end: Month=April. Week=2. Hour=3. The events are described as: "the change will take place on the n'th (week) of (month) on a (day) at (hour) (min)" To describe the last day of the month. New Zealand GMT offset=12. Hour=2. this can be enabled. please refer to: http://www. use week=5 Examples: Montreal. Canada time: GMT offset=-5. Daylight saving enable For regions of the world implementing Daylight saving time. North America would have negative values while Eastern Europe would have positive values. DST start: Month=September. Hour=2.com/. Day=Sunday. Beware that syslog and other services that timestamp events using the current date and time will be affected during transitions of DST periods. Quebec. Day=Sunday. DST offset=1 DST start: Month=March. Day=Sunday. There will possibly be an hour gap or duplicate time stamps because the clock was set back.3: Management and configuration Timezone and Daylight saving Timezone and Daylight saving For a list of time zones and daylight saving time rules. Min=0 DST end: Month=November. Most of the time it will be one hour. Week=1. Week=5. Daylight saving offset Time correction to apply to GMT offset during the Dailight saving period. DST offset=1. Week=1. DST enable=check. GMT offset Offset from Greenwich Mean Time. Min=0 Wellington.worldtimezone. DST start and DST end Period where daylight saving time is in effect. DST enable=check. Min=0 32 . Hour=2. Day=Sunday. 3: Management and configuration SNMP settings SNMP settings To configure SNMP options. Open the System > SNMP page. 33 . 2. Define SNMP parameters as required by your setup and then click Apply. do the following: 1. By convention. this is the node's fully-qualified domain name.3: Management and configuration SNMP settings SNMP parameters Enable agent Select this checkbox to enable the SNMP agent. the well-known SNMP trap port (162) is used. Management host Specify the IP address or host name of the device that will receive SNMP traps (and/or inform notifications). Read-write community Specify the community string to control read/write access to the EtherNID. Contact information Specify contact information for the EtherNID. see Appendix B. System location Identify the physical location of the EtherNID. Note: For a list of Public and Private supported MIBs. Generally an email address. UDP port Specify the UDP port that the EtherNID will use to send traps to the management host(s). By default. 34 . Read-only community Specify the community string to control read-only access to the EtherNID. Enable trap host Enable these options to have the unit send SNMPv1 or SNMPv2c traps to the specified management host(s). The EtherNID sends a Cold Start trap when it starts up. Agent UDP port Specify the UDP port the SNMP agent uses for all IPv4 interfaces. SNMP system name Specify a name to identify the EtherNID. Community string Specify the community string required to send traps to the management host(s). 2. This will enable the remote retrieval of these files as well as protect against losing these statistics history in the event of a power failure or reboot. Local Configuration Enable history This will start the creation of history files being stored in RAM. 35 .3: Management and configuration History buckets History buckets To configure local history bucketing. Enable filing This will enable the history files to be stored locally instead of storing this information in the RAM. Unchecking this box will result in the existing history files for this feature to be removed locally. Open the System > History page. Define the history parameters as required and then click Apply. in minutes. Period The frequency. do the following: 1. These will then be accessible through SNMP. of storing the statistics history into files. 3: Management and configuration Remote retrieval of history buckets Remote retrieval of history buckets NOTE: The Remote retrieval feature is only available on the MetroNID TE models. 2. Open the System > History page on the local MetroNID TE and add a new remote device. Ensure filing is enabled for the desired history buckets and then click Apply. To configure remote retrieval of history buckets. 36 . 3. Then enable scheduling at the desired time slot(s) and provide the URL for the file transfer server. do the following: 1. Open the System > History page on the remote NIDs. (Hold CTRL key to select more than one hour) This feature is dependant on the Enable filing check boxes in the Local configuration sections of the local and remote devices. then only the remote history buckets will be retrieved. as well as the remote device(s). Example: If Enable scheduling is checked and the local device. then both the local and remote history buckets will be retrieved. The history buckets will be retrieved according to the Scheduled hours selected. Example: If Enable scheduling is checked but the local device has not checked Enable filing.com tftp://192.3: Management and configuration Remote retrieval of history buckets Scheduling and file transfer configuration Enable scheduling Enable the history buckets to be retrieved from the local device and/or the list of remote devices.1. 37 .5 NOTE: The status of the Remote devices can be obtained by clicking on the Remote device name in the Remote device configuration window. Examples: http://mypc.com ftp://username:[email protected]. have checked Enable filing. Server URL The full URL of the Server on which to send the history bucket files once retrieved. Terminate Select one or more sessions and then click the Terminate button to force a log out. Define session management parameters as required by your setup and then click Apply. Writeunlock: Click this button to unlock the configuration so someone else can make changes. Session ID Unique number that identifies a session. 2. Writelock Indicates which session has the ability to make configuration changes.3: Management and configuration Session management Session management To configure session management options. Current sessions Lists all sessions currently logged into the EtherNID. 38 . Uptime Indicates how long the session has been active. Automatically generated by the EtherNID. Management parameters Writelock session The management web interface supports multiple concurrent users. only one user at a time has the ability to make changes. • • Writelock: Click this button to lock the configuration so you can make changes. An asterisk (*) next to the username indicates the username of the session that is viewing this web page. Open the Session > Management page. Username Identifies the user account that is logged in. therefore to maintain the integrity of the configuration settings. do the following: 1. Type Indicates which interface the session is using. 4. Open the System > Firmware page. Specify the location and name of the new firmware file or click Browse and select it. 39 . do the following: 1. 2. Click Upload. Once the firmware has been uploaded the unit will restart.3: Management and configuration Firmware upgrade Firmware upgrade To upgrade the EtherNID firmware. 3. do the following: 1. 40 . Open the Session > Configuration page.3: Management and configuration Session configuration Session configuration To configure session options. Session parameters Max CLI sessions Specify the maximum number of CLI sessions that are supported at the same time. Max total sessions Specify the total number of CLI and WEB sessions that are supported at the same time. Refer to RADIUS configuration page for server configuration instructions. WEB timeout Specify the maximum number of seconds that a management tool session can remain idle before it is automatically logged out. 2. CLI timeout Specify the maximum number of seconds that a CLI session can remain idle before it is automatically logged out. This parameter is described in the RADIUS section below on page 35. Max WEB sessions Specify the maximum number of management tool sessions that are supported at the same time. Authentication Order Authentication method to use in order of availability. Define session parameters as required by your setup and then click Apply. 2. Define session management parameters as required by your setup and then click Apply. Writeunlock: Click this button to unlock the configuration so someone else can make changes. Type Indicates which interface the session is using. 41 . Username Identifies the user account that is logged in. Session ID Unique number that identifies a session. Uptime Indicates how long the session has been active. Current sessions Lists all sessions currently logged into the EtherNID.3: Management and configuration Session management Session management To configure session management options. Management parameters Writelock session The management web interface supports multiple concurrent users. only one user at a time has the ability to make changes. • • Writelock: Click this button to lock the configuration so you can make changes. An asterisk (*) next to the username indicates the username of the session that is viewing this web page. Writelock Indicates which session has the ability to make configuration changes. therefore to maintain the integrity of the configuration settings. Terminate Select one or more sessions and then click the Terminate button to force a log out. Open the Session > Management page. do the following: 1. Automatically generated by the EtherNID. This can be one of the following methods: • PAP : Password Authentication Protocol RADIUS timeout Time to wait for the RADIUS server to respond before retrying the connection. a connection to the next configured server will be attempted. Realm A string to append to the user's name using the "username@realm" method. RADIUS retry Number of times to retry the server before trying the next server configured. Open the Session > RADIUS page. do the following: 1. After the number of retries has been exhausted. RADIUS parameters Authentication method Authentication method to use. 42 . Define RADIUS parameters as required by your setup and then click Apply. in which the same timeout and retry scheme will apply. 2.3: Management and configuration Session RADIUS Session RADIUS To configure RADIUS authentication. Configuration examples Callback-Id = "Admin" A userid member of the built-in Admin group. the unit supports Authentication and Authorization as configured on the RADIUS server. Callback-Id = "Config Firmware Log Management. They can be a mix of either locally defined user permission groups or individial privileges. Users" A list of individual privileges. Radius server configuration When RADIUS authentication is enabled.The permissions tokens are case sensitive.3: Management and configuration Session RADIUS Server-1 / Server-2 Host RADIUS server host-name or IPV4 address. If the attribute is not configured then the permissions will be set to viewer only. .RADIUS assigned permissions cannot be viewed with the CLI or web based interface. Notes: . The permissions are the same as those that can be configured locally on the unit. The RADIUS Callback-Id (id=20) attribute is used to provide the Authorization (permissions) info to the unit. Secret Shared secret for this RADIUS server. It is a space or coma separated list of tokens. 43 . Port RADIUS server UDP port to connect to. Power on EtherNID #1 with factory default settings. Connect your computer to serial port on the back of the EtherNID. If an EtherNID GE is being used. in-band through a bridged interface. Open a terminal emulation session with the following configuration: • • • • Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: None 4. the first EtherNID is connected to the private network and manages the other EtherNIDs in-band through its out-of-band Management port. The following diagram describes the typical setup scenario for a bridged interface: Configuration procedure 1. type the following command: media-selection select RJ45-A_RJ45-B 44 . A minimum of two EtherNIDs are required for this setup. 5. Login to the CLI with username admin and password admin. Instead. An out-of-band EtherNID management port will be used to manage the other EtherNIDs. and the setup requires the Client and Network ports to be set as copper medium. 3. 2. This is useful when the core transport devices do not need to be connected to the internal private management network.3: Management and configuration Management bridge Management bridge This section describes how to set up a bridged management port using the command line interface. Connect the Network port of EtherNID #2 to the Network port of EtherNID #1. Repeat configuration steps 1.255.255. Open a second web browser and enter the address 192.255.252 to reach the management web interface on EtherNID #3. 11.168. 14. Delete any existing interfaces with the following commands: interface delete Management interface delete Network 7.cli10.1.1.net10 address 192.255. The Network port of EtherNID #1 will be used for the in-band management.168. 45 . Open a web browser and enter the address 192. Configure the Network port with the following command: interface add net1-10 type vlan 10 port Network address 192.0 8. Execute the following command to bridge all three interfaces together for access using the Management port.0 12. 17. Execute the following commands to add three interfaces on EtherNID #2: interface add mgmt type standard port Management interface add cli10 type vlan 10 port Client interface add net10 type vlan 10 port Network The interface 'mgmt' will be used to connect to the management bridge. Next. on EtherNID #3 using the following settings when defining the new interface: interface add net3-10 type vlan 10 port Network address 192. 10. Connect the Client port of EtherNID #2 to the Network port of EtherNID #3.1. 15.1. Repeat configuration steps 1.168.1. Open a third web browser and enter the address 192.253 to reach the management web interface on EtherNID #1. Open a web browser on a computer connected to the private network and enter the address 192.168.168. on EtherNID #2. 18.255.254 netmask 255.1.252 netmask 255. to 6.254 to reach the management web interface on EtherNID #2. 13. to 7.253 netmask 255. Connect the Management port of EtherNID #2 to the private network.1. 16. The other two interfaces will be used to access the other two EtherNIDs remotely. create the bridge interface.0 9.168.255.168. interface add Bridge type bridge sub-intf mgmt.3: Management and configuration Management bridge 6.254 to reach the management web interface on EtherNID #2. open the Port > Configuration page. You will see the following page on an EtherNID EE: 46 .4: Port configuration Port list and port status Chapter 4: Port configuration 4 • Port configuration Port list and port status To view a list of all ports and their status. 4: Port configuration Port list and port status • You will see the following page on an EtherNID OE: 47 . 4: Port configuration Port list and port status • You will see the following page on an EtherNID GE or MetroNID TE: 48 . Port name Identifies the logical name assigned to the port. 49 . Red: The port is enabled but the physical link is down. Yellow: The port is not totally functional. Connector Identifies the physical connector the port is using. Port state Indicates if the port is enabled (ready to connect) or disabled.4: Port configuration Port list and port status • You will see the following page on an EtherNID DE+: Port configuration and status Status Indicates the status of the port. Grey: The port is disabled. • • • • Green: The port is up and running. all the associations between connectors and ports will be reflected in the Port configuration and status table. Port options Media-selection (Supported on the EtherNID GE and MetroNID TE only) Lets you select which two media connectors will be used to carry traffic. connectors RJ45-A and SFP-A are mapped to port Monitor-1. SFP-A with RJ-45-B (PoE) is selected. Four options are available: • • • • SFP-A with SFP-B SFP-A with RJ-45-B (PoE) RJ-45-A with SFP-B RJ-45-A with RJ-45-B (PoE) If you change the setting and then click Apply. Select one of the following options: • • • Client: If the EtherNID detects a link down condition on the Network port it will also bring down the Client port. 50 .4: Port configuration Port list and port status Speed Indicates the current port speed and duplex type. Two-way: If the EtherNID detects a link down condition on either the Client port or the Network port it will bring down both ports. When used as monitor ports. This denotes Traffic-A is connected to the SFP-A connector and Traffic-B is connected to the RJ-45-B connector Fault propagation Enable fault propagation Select this check box to enable fault propagation. Network: If the EtherNID detects a link down condition on the Client port it will also bring down the Network port. When this feature is enabled the EtherNID will propagate link faults between the Client and Network ports. For this to work the device must also be configured to support auto-negotiation. Propagate fault on port Select the port that the EtherNID will use for fault propagation. The two other connectors on the device will be monitor ports. and RJ45-B and SFP-B are mapped to port Monitor-2. MAC address Indicates the MAC address of the port. For example: By default. If set to Auto-nego the EtherNID automatically negotiates port speed and duplex type with the device it is connected to. Define port parameters as required by your setup and then click Apply.4: Port configuration Configuring port settings Configuring port settings To configure port settings. 51 . do the following: 1. 2. The port configuration page will open. Click the name of the port that you want to configure. Open the Port > Configuration page. • If you are configuring a copper port it will be similar to the following page: • If you are configuring an SFP fiber port it will be similar to the following page: 3. Note: Auto-negotiation is mandatory for 1000BASE-T. Link speed (copper ports only) Sets port speed and duplex type. a Remote Fault Indicator using auto-negotiation advertisement is sent to the link partner. If this option is disabled. the FEFI idle pattern is sent to the link partner. Client.4: Port configuration Configuring port settings Port parameters Port enable Select this check box to enable the port. Port name Specify a name to identify the port. Select Auto-negotiation enable to have the EtherNID automatically negotiate port speed and duplex type with the device it is connected to. Link Loss Return (LLR) (SFP fiber ports only) This option determines how the EtherNID notifies its link partner when a valid receive signal is absent on the link. For this to work the device must also be configured to support auto-negotiation. For 100BASE-FX links. If this option is enabled. you can manually define port speed and duplex type using the available options. this is set to 1522. Network. Port MTU Specify the maximum transmission unit. ports are named as follows: Management. Note that this range is platform dependant. puts the laser into a disabled state waiting for the opposite side to send a light pulse in order to re-establish the link. then the EtherNID turns off its transmitter for the amount of time defined by LLR period. If you do not select Auto-negotiation enable. then: • • For 1000BASE-X links. the exact behavior depends on the auto-negotiation result. Alias This is an 'alias' name for the port as specified by a network manager. When this option is set to local or transparent and the Auto-negotiation option is also enabled under Link speed. 52 . So for this reason. This cycle is repeated until the link is re-established. Example range: 1518 to 10240. By default. Entering a value of 0. Flow control Select how pause frames are processed by setting the Pause mode option to local. transparent or disabled. Monitor-1 and Monitor-2. after which it is re-enabled. By default. 0 should not be configured on both sides or the link will never re-establish. If you do not select Auto MDI Enable. MAC address Identifies the MAC address of the port. Connector Identifies the physical connector associated with the port. A cross-over cable present on the cabling plant will result in both partners using the same connector configuration. Large packet threshold Specify the threshold such that all packets above this value will be classified as Large Packets on the Port > Statistics page Medium dependent interface (Copper ports only) Select Auto MDI Enable to have the EtherNID automatically adapt the configuration of the connector to the cabling plant and link partner type. you can manually define port settings as follows: • • MDI: Typical setting for an Ethernet station. 53 .4: Port configuration Configuring port settings Current status Reports the following for Ethernet ports: • • 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. MDIX: Typical setting for an Ethernet switch. Link partner must be set to MDIX or a cross-over cable must be used. Link partner must be set to MDI or a cross-over cable must be used. Click the name of a port to view detailed statistics. For example. Open the Port > Statistics page. do the following: 1. if you click the Management port on an EtherNID GE or MetroNID TE you will see a page similar to the following: 54 .4: Port configuration Port statistics Port statistics To view port statistics. 2. Click the name of a port that you want to configure. Define PHY parameters as required by your setup and then click Apply. Open the Port > PHY page. Note: Advertised parameters are checked and parameters that are not configurable are greyed-out based on the capabilities of the port. if you click the Client port name you will see the following page.4: Port configuration PHY auto-negotiation configuration PHY auto-negotiation configuration To configure PHY auto-negotiation settings. 3. 55 . do the following: 1. For example. 2. 4: Port configuration PHY auto-negotiation configuration PHY parameters Advertisement configuration Sets the abilities that are advertised to the link partner. The state disabled indicates that auto-negotiation is not supported by the media or disabled by configuration. • • • • • • • • 10Mbps Half 100Mbps Half 1Gbps Half 10Mbps Full 100Mbps Full 1Gbps Full Pause Symmetric Pause Asymmetric State The state field corresponds to ifMauAutoNegConfig and ifMauAutoNegRemoteSignaling from RFC3636. Supported options include: • • • • • • • • 10Mbps Half 100Mbps Half 1Gbps Half 10Mbps Full 100Mbps Full 1Gbps Full Pause Symmetric Pause Asymmetric Link Partner Ability Lists the abilities of the link partner. 56 . • • • "SFP information" on page 57 "SFP thresholds" on page 59 "SFP memory and monitor memory" on page 61 SFP information This box displays general SFP information and monitoring information. 57 . Refer to the following sections for more information. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h). do the following: 1.4: Port configuration SFP information SFP information (Supported only on the EtherNID OE / GE / MetroNID TE) To view SFP information. Open the Port > SFP page. Vendor Indicates the vendor name. 2. Click the name of the port for which you want to view detailed statistics. SFP information Connector Type Indicates the external optical or electrical cable connector provided as the media interface. Thresholds Additionally. Temperature accuracy is vendor specific but must be better than 3 degrees Celsius over specified operating temperature and voltage. which are converted into real units per the convention “External Calibration”. Transmit power Measured coupled TX output power. Accuracy is vendor specific but must be better than 3dB over specified operating temperature and voltage. Data is assumed to be based on measurement of a laser monitor photodiode current. 58 . External: If bit 4 is set. alarm and warning thresholds must be written as specified in this document at locations 00 – 55 on 2 wire serial address 1010001X (A2h). Data is not valid when the transmitter is disabled. SFP present Indicates the presence of a recognized SFP. Laser bias current Measured coupled TX output power. received power monitoring. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h). • • Internal: If bit 5 is set. bias current monitoring. address 92 is set indicating that digital diagnostic monitoring has been implemented. Part number Indicates the vendor part number or product name. the values are calibrated to absolute measurements. Calibration The values in this field are interpreted differently depending upon the option bits set at address 92. Monitoring information Temperature Internally measured transceiver temperature. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h). Serial number Indicates the vendor serial number for the transceiver. Data is assumed to be based on measurement of a laser monitor photodiode current.4: Port configuration SFP information Wave Length Indicates the nominal transmitter output wavelength at room temperature in nm. This is a 16-byte field that contains ASCII characters padded on the right with ASCII spaces (20h). Data is not valid when the transmitter is disabled. the values are A/D counts. Diagnostics If bit 6 is set. supply voltage monitoring and temperature monitoring will all be displayed. Revision Indicates the vendor’s product revision. which should be interpreted according to the convention “Internal Calibration”. Accuracy is vendor specific but must be better than 3dB over specified operating temperature and voltage. transmitted power monitoring. 59 . Refer to the device specification for more detail. In that case. accuracy should be better than 3dB over specified temperature and voltage. transmitter supply voltage and receiver supply voltage are isolated. For the vendor specified wavelength.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. Supply voltage Internally measured transceiver supply voltage. Low warning Low Warning transceiver temperature. only one supply is monitored. It should be maintained down to the minimum transmitted power minus cable plant loss (insertion loss or passive loss) per the appropriate standard.4: Port configuration SFP information Receive power Measured received optical power. Absolute accuracy is dependent upon the exact optical wavelength. Note that in some transceivers. SFP thresholds Temperature High alarm High Alarm transceiver temperature. High warning High Warning transceiver temperature. Low alarm Low Alarm transceiver temperature. Absolute accuracy beyond this minimum required received input optical power range is vendor specific. 2 dBm).2 dBm).2 dBm). Low alarm Low Alarm Rx input power in dBm (~ -40 to +8. Tx power High alarm High Alarm TX output power in dBm (~ -40 to +8.4: Port configuration SFP information Vcc High alarm High Alarm transceiver supply voltage. 60 . High warning High Warning TX bias current in micro-Amps. High warning High Warning TX output power in dBm (~ -40 to +8. Low warning Low Warning TX bias current in micro-Amps.2 dBm).2 dBm). Low alarm Low Alarm transceiver supply voltage. Low warning Low Warning transceiver supply voltage. Low warning Low Warning TX output power in dBm (~ -40 to +8. Low alarm Low Alarm TX output power in dBm (~ -40 to +8. Laser bias current High alarm High Alarm TX bias current in micro-Amps. Low alarm Low Alarm TX bias current in micro-Amps. Rx power High alarm High Alarm Rx input power in dBm (~ -40 to +8. High warning High Warning transceiver supply voltage.2 dBm). standard interfaces. 61 . SFP memory and monitor memory SFP memory The SFP serial ID provides access to sophisticated identification information that describes the transceivers capabilities.2 dBm). Low warning Low Warning Rx input power in dBm (~ -40 to +8. Refer to INF-8074 for detailed descriptions of the individual data fields.4: Port configuration SFP information High warning High Warning Rx input power in dBm (~ -40 to +8.2 dBm). and other information. manufacturer. The status of each channel is updated as the tests are run. Some of the possible problems that the EtherNID can diagnose are: opens. connectors.4: Port configuration Cable verification Cable verification The EtherNID uses Time Domain Reflectometry (TDR) to determine the quality of cables. do the following: 1. Click Perform Test. and termination mismatch. 2. 3. 62 . Open the Port > Cable page. and terminations. Testing a cable To perform a cable test. bad connectors. 4. cable impedance mismatch. shorts. Click the name the connector you want to test. if you click RJ45-B you will see the following page. For example. 4: Port configuration Cable verification When completed, test status will be one of the following: • • GOOD: Normal cable. SHORT: Indicates that the positive and the negative lines of the same cable pair are touching: Possible causes include: • • • Cable wire may be touching the wire closet patch panel. Cable may be worn or broken allowing the positive and negative lines to touch. OPEN: Indicates that one pair on the cable is not connected at the far end of the cable. Possible causes include: • • Cable is not connected. Cable was cut. • FORCED: Indicates a persistent noise on the cable. This can be caused by a link partner running forced at 10/100 Mbps. Cable length is not available when the test results indicate FORCED. FAIL: If the remote partner sends traffic at the same time as the test is being conducted, then these packets may interfere with the TDR resulting in a FAIL status. Impedance Mismatch: Indicates that the effective impedance is not 100 Ohms. the TDR can determine an impedance mismatch. Possible causes include: • • Different quality cables are connected together through a cable extender. A low quality cable is being used. • • 63 5: Monitoring and filtering Service mapping Chapter 5: Monitoring and filtering 5 Monitoring and filtering Service mapping NOTE: The Service mapping feature is only available on the EtherNID GE and MetroNID TE models. For other models, see the Traffic forwarding section below. The EtherNID can perform EVC mapping (which is essentially a VLAN push), CoS mapping and Bandwidth Policing mapping. These options can be used together or separately. Prior to creating CoS profiles and/or Bandwidth regulator sets, appropriate filters and bandwidth regulators will need to be created. See section Traffic Filters and Bandwidth Policing below for details about creating filters and regulators. A CoS profile is used to map an input packet to an L2 class of service. This traffic mapping (classification) is accomplished using the following fields in the incoming packet: • • • p-bits in 802.1Q / 802.1Q .1Q tags IP precedence bits in IPv4 TOS byte DSCP bits in IPv4 DSCP byte The class of service value (0-7) assigned to the outgoing traffic is selected based on the conformance level (Green/Yellow) of the incoming traffic. Viewing CoS profiles To view a list of configured CoS profiles, open the Traffic > Mapping page. By default, commonly used profiles. Index CoS profile's unique identifier. 64 5: Monitoring and filtering Service mapping Name CoS profile's name as defined in the configuration page. Click this name for more details. Type CoS profile's type. Possible values are: • • • PCP IP precedence DSCP Reference count The reference count is the number of policies that are currently using this CoS profile. Configuring a CoS Profile Once a Cos profile is created, it can be applied to policies for traffic classification. To configure a CoS profile, do the following: 1. Open the Traffic > Mapping page. 2. Click Add in the CoS profiles section, or click a profile name to edit and existing one. 3. Configure CoS profile parameters and click Apply. CoS Profile parameters Name Name of the CoS profile. 65 5: Monitoring and filtering Service mapping Type Indicates the type of CoS profile. Possible values are: • • • PCP IP precedence DSCP Decode DEI This field is only valid for PCP CoS profiles. If this field is set, the pre-marking color is decoded from the DEI bit (Drop Eligible Indication). Otherwise, the user defined pre-color is used. Encode using DEI This field controls the DEI bit in an S-VLAN tag. If this field is set and the outgoing packet is marked yellow then the DEI bit is set to 1. Otherwise, the DEI is set to 0. Reference count (only visible on existing profiles) The reference count is the number of policies that are currently using this CoS profile. Mapping table The mapping table maps the input traffic to a specific class of service. This table has four columns and 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. Otherwise, the CoS profile is a DSCP profile and N=64. Each row in this table represents a mapping entry and each entry has the following parameters: PCP/IP precedence/DSCP [IN] PCP/IP precedence/DSCP input value. Pre-marking color The pre-marking color that will be assigned to the input packet that has this PCP/IP precendence/DSCP value. Green [OUT] The class of service value that will be used in the outgoing green packets. This value is selected if the result of the bandwidth regulator assigned to this entry is green or if the pre-marking color is green and no bandwidth regulator is assigned to this entry. Yellow [OUT] The class of service value that will be used in the outgoing yellow packets. This value is selected if the result of the bandwidth regulator assigned to this entry is yellow or if the pre-marking color is yellow and no bandwidth regulator is assigned to this entry. Assigning a CoS profile to a policy Once a CoS profile has been configured you can assign it to a policy. See "Traffic policies and monitoring" on page 72. 66 it can be applied to policies for traffic classification. Index Bandwidth regulator set's unique identifier. To configure a Bandwidth regulator set.5: Monitoring and filtering Service mapping Viewing Bandwidth regulator sets To view a list of configured Bandwidth regulator sets. Click this name for more details. Name Bandwidth regulator set's name as defined in the configuration page. 3. open the Traffic > Mapping page. Open the Traffic > Mapping page. Possible values are: • • • PCP IP precedence DSCP Reference count The reference count is the number of policies that are currently using this Bandwidth regulator set. Click Add in the Bandwidth regulator sets section. 67 . or click a regulator set name to edit and existing one. Configuring a Bandwidth regulator set Once a Bandwidth regulator set is created. Configure Bandwidth regulator set parameters and click Apply. 2. Type Bandwidth regulator set's type. do the following: 1. 5: Monitoring and filtering Service mapping Bandwidth regulator set parameters Name Name of the Bandwidth regulator set. Each row in this table allows assigning a traffic regulator to a specific PCP/IP precedence/DSCP > value. 68 . Otherwise. Possible values are: • • • PCP IP precedence DSCP Reference count (only visible on existing sets) The reference count is the number of policies that are currently using this Bandwidth regulator set. If the type is PCP or IP precedence then N=8. the regulator set type is DSCP and N=64. PCP/IP precedence/DSCP [IN] PCP/IP precedence/DSCP input value. Type Indicates the type of Bandwidth regulator set. Regulator set This table has three columns and N rows. where N depends on the type of the regulator set. Bandwidth regulator The bandwidth regulator that will be used to regulate the traffic flow that has this PCP/IP precendence/DSCP value. IP precedence or DSCP value. Assigning a Bandwidth regulator set to a policy Once a Bandwidth regulator set has been configured you can assign it to a policy. 69 . See "Traffic policies and monitoring" on page 72.5: Monitoring and filtering Service mapping Enable regulator Enable or disable traffic regulation for this PCP. Each policy defines the settings for: • • • • • • the traffic filter to apply to traffic on the port the action (permit or drop) to apply to traffic Define a traffic filter (if you are not going to use a default filter) Define an access policy. Traffic A policies apply to connectors labeled A. permitting either the Network or Client port to be connected to a VLAN trunk.5: Monitoring and filtering Traffic forwarding Traffic forwarding NOTE: The description below for Traffic forwarding is only available on the EtherNID EE. Traffic filters The EtherNID uses traffic filters (which use bit patterns to recognize incoming packets) to control access policies and to monitor traffic on the Client and Network ports. Access policies are used to allow monitoring traffic to be received by the EtherNID. Each policy can be configured to monitor incoming traffic from either Monitor-1 or Monitor-2. Access policies The EtherNID uses access policies to control the monitoring and filtering of traffic on the Client and Network ports. Traffic B policies apply to connectors labeled B. OE and DE+ models. see the Service mapping section above. you must: There are two sets of policies: Traffic A policies and Traffic B policies. Up to eight access policies can be configured for Client and Network ports. To set up an access policy. The EtherNID provides VLAN support. For GE and MetroNID TE models. Monitoring The EtherNID has two external connectors through which traffic can be monitored: Monitor-1 and Monitor-2. 70 . Enable P-Bits preservation Select this check box to preserve the incoming VLAN priority in the added outgoing VLAN encapsulation instead of using the VLAN priority set in the Forwarding options. Allows you to provide QoS prioritization by using the standard based 802.5: Monitoring and filtering Traffic forwarding Configuring traffic forwarding To configure traffic forwarding. Possible values are 0 to 7.1Q priority tag. If a frame received at an Ethernet port has a CFI set to 1. VLAN ID Specify the VLAN ID that will be used to encapsulate all traffic forwarded to the port. 2. This should always be set to zero for connection to Ethernet switches. Note: If the incoming traffic is not already tagged with a VLAN. Trunk port Select the port to which the VLAN trunk is connected. Interpretation is based on the carrier’s equipment and administrative policies VLAN CFI Specify the Canonical Format Indicator. Forwarding parameters Enable VLAN encapsulation Select this check box to enable VLAN support. 71 . Open the Traffic > Forwarding page. then that frame should not be forwarded “as is” to an untagged port. then this option has no effect and the VLAN priority on outgoing traffic will be taken from the Forwarding options specified. Define parameters as required by your setup and then click Apply. CFI is used for compatibility reasons between Ethernet type networks and Token Ring type networks. do the following: 1. VLAN priority Specify the VLAN priority. A bad packet is a packet that has a valid framing but contains an error within the packet. A good packet is an error-free frame that has a length between 64 bytes and the maximum frame length. 72 . Filter name: Indicates the name of the filter assigned to the policy. Packets good: The number of good packets that matched the policy. For example. A rule. Disabled policies are skipped when the rules are applied to incoming data. This page shows the access policy rules that are enabled for a specific port. Note: The *default filter is a factory default rule that forwards all traffic.5: Monitoring and filtering Traffic policies and monitoring Traffic policies and monitoring To view a list of all traffic policies and their settings. Action: Indicates the action that the policy applies to data that it matches. When rules are applied they are processed from the top down and the first suitable rule that is found is applied. such as this is required to have traffic forwarded. Access policy rules are ordered by their priority. if the Network port is selected then this is the list of policy rules that are enabled or disabled for the Network port. Note: The following information is presented for each policy: • • • • • • • Entry: Indicates the position of the rule in the access list. Packets bad: The number of bad packets that matched the policy. State: Indicates if the policy is enabled or disabled. open the Traffic > Policies page. has a bad CRC or either shorter than 64 bytes or longer than the maximum frame length. Bytes good: This is the total number of bytes in good packets that matched the policy. To define a new filter. 73 . Click the policy entry that you want to configure. Configure policy settings and click Apply. open the Port > L2 Filters/IPv4 Filters page. a catchAll filter is defined.5: Monitoring and filtering Traffic policies and monitoring Configuring a traffic policy on an EtherNID GE or MetroNID TE To configure a traffic policy. do the following: 1. L2 filter / IPv4 filter The list shows all available filters. This enables you to monitor all traffic on a port. By default. Open the Traffic > Policies page. 3. The filter type is either a Layer 2 or IPv4 filter. 2. Filter type Select the filter type that will be used to capture traffic. Policy settings Enable policy Select this check box to activate the policy. 5: Monitoring and filtering Traffic policies and monitoring Action Select the action that will be applied to traffic that matches the filter. Enable monitoring Select this check box to activate monitoring. Monitor port Indicates the port to which traffic will be forwarded for monitoring. Encapsulation Push Add a new VLAN. Ethertype The ethertype of the VLAN to be added. Possible values are: C-VLAN=0x8100 or S-VLAN=0x88a8 VLAN ID A value between 0 and 4095. PCP action This section selects the PCP (Priority Code Points) action to perform. Possible values are: • Preserve: Keep the PCP bits if the packet is already tagged • • Direct: Add the default PCP value Map: Use a CoS profile for PCP selection For each PCP action there is one or two traffic mapping choices and the default PCP bits to use if the packet does not match the first and the second choices. The following tables show the valid selection of the first and second choice for each of the PCP actions PCP Preservation If this option is selected, PCP bits are copied from the first VLAN(if any). If the packet is not tagged, the user may select the PCP bits from an IP precedence / DSCP CoS profile. It is also possible to select a bandwidth regulator set for traffic regulation. Parameter Type CoS profile BWR set First choice IP Precedence / DSCP CoS profile Optional Second choice N/A N/A N/A PCP Direct If this option is selected, the first and second choices are ignored. The PCP bits are forced to the default green or yellow values based on the result of the bandwidth regulator or the pre-marking color. It should be noted that the pre-marking color red is ignored if the default bandwidth regulator is not enabled. 74 5: Monitoring and filtering Traffic policies and monitoring Parameter Type CoS profile BWR set First choice N/A N/A N/A Second choice N/A N/A N/A PCP mapping If this option is selected, the first and second choices can be used to map and regulate traffic based on PCP / IP precedence /DSCP values. The table below shows the valid configurations of the first and second choices. Parameter Type First choice VLANinVLAN VLAN IP precedence, DSCP Second choice VLAN, IP precedence, DSCP IP precedence, DSCP VLAN, VLANinVLAN CoS profile Optional CoS profile BWR set CoS profile Optional Encapsulation None This option can be used to perform traffic regulation based on PCP / IP precedence /DSCP values. The selected CoS profile in the first and second choices are ignored. The table below shows the valid configurations of the first and second choices. Parameter Type First choice VLANinVLAN VLAN IP precedence, DSCP Second choice VLAN, IP precedence, DSCP IP precedence, DSCP VLAN, VLANinVLAN Ignored BWR set CoS profile BWR set Ignored BWR set Encapsulation Pop This option can be used to perform traffic regulation based on PCP / IP precedence /DSCP values before removing the VLAN tag. The selected CoS profile in the first and second choices are ignored. 75 5: Monitoring and filtering Traffic policies and monitoring Parameter Type First choice VLANinVLAN VLAN IP precedence, DSCP Second choice VLAN, IP precedence, DSCP IP precedence, DSCP VLAN, VLANinVLAN Ignored BWR set CoS profile BWR set Ignored BWR set Default/Direct Bandwidth regulator Enable bandwidth regulation Check this box to activate a default bandwidth regulator. Pre-marking color Pre-mark, with a specific color, the traffic that does not match the first and second 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 packets. Green traffic will use buffers from CIR until depleted at which time it will be tagged as Yellow data. Yellow traffic will use 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 will be dropped. Please note, that it's not possible to pre-mark data as red if there bandwidth regulator is disabled. Traffic color will affect how the regulator handles the traffic. For details see "Color mode" on page 91. Bandwidth regulator Choose a default bandwidth regulator that will be associated with the traffic matched by this policy. To define a bandwidth regulator see "Bandwidth policing" on page 89. CFI/PCP 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 choices. 76 5: Monitoring and filtering Traffic policies and monitoring Configuring a traffic policy on an EtherNID EE. Click the policy entry that you want to configure. Actions Select the action that will be applied to traffic that matches the filter. 3. Filter type Select the filter type that will be used to capture traffic. a catch-all filter is defined. Layer 2 filter / IPv4 filter The list shows all available filters. 77 . The filter type is either a Layer 2 or IPv4 filter. open the Port > Filter page. By default. Configure policy settings and click Apply. This enables you to monitor all traffic on a port. Monitor port Indicates the port to which traffic will be forwarded for monitoring. Enable bandwidth regulation Select this check box to activate bandwidth regulation. To define a new filter. OE or DE+ To configure a traffic policy. Policy settings Policy enable Select this check box to activate the policy. Open the Traffic > Policies page. Enable monitoring Select this check box to activate monitoring. 2. do the following: 1. For details see "Color mode" on page 91. 78 . Traffic color will affect how the regulator handles the traffic. then pre-marking has no effect.5: Monitoring and filtering Traffic policies and monitoring Pre-marking color Select the color this port will use to pre-mark all traffic before it is sent to the selected bandwidth regulator. the bandwidth limitation imposed by the regulator applies to the sum of the traffic of all policies sharing the same regulator. Note: Since many policies may share the same bandwidth regulator. Bandwidth regulator Select the bandwidth regulator that will be associated with the traffic matched by this policy. If a bandwidth regulator is not defined. To define a bandwidth regulator see "Bandwidth policing" on page 89. By default. Used to process VLAN in VLAN traffic. MAC destination: Indicates the destination MAC address assigned to the filter. The address is specified as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). The following information is presented for each filter: • • Filter name: Unique name assign to the filter. The address is specified as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). The filter will only process frames being sent to this address. By default. The filter will only process frames tagged with this VLAN ID. commonly used filters are defined. VLAN1: Indicates the VLAN ID assigned to the filter. MAC source: Indicates the source MAC address assigned to the filter. open the Traffic > L2 Filters page. custom (layer 2 or IPv4) filters can be applied to the traffic before it is presented on the monitor ports. commonly used filters are defined for both layer 2 and IPv4. • • • • 79 . Ethertype: Identifies the Ethernet frame type that this filter will process. VLAN 2: Indicates the second VLAN ID assigned to the filter.5: Monitoring and filtering Traffic filters Traffic filters To develop specific access policies and to make traffic monitoring more efficient and effective. The filter will only process frames received from this address. Viewing L2 filters To view a list of active L2 traffic filters. Other frame types are ignored. This reduces overhead and enables access policies and monitoring to be targeted at specific types of traffic only. or click the filter name to edit and existing one. Specify the address as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Configure filter parameters and click Apply. 80 . Open the Traffic > L2 Filters page. Only the bits specified by the mask are used. L2 filter parameters L2 filter name Specify a name to uniquely identify the filter. MAC destination / mask Specify the destination MAC address and mask.5: Monitoring and filtering Traffic filters Configuring an L2 filter on an EtherNID GE or MetroNID TE To configure an L2 filter. MAC source / mask Specify the source MAC address and mask. Specify the address as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Ethernet header settings The following characteristics can be defined. Click Add to create a new file. The other bits are ignored. do the following: 1. Only the bits specified by the mask are used. The other bits are ignored. 3. Ethertype Select a well-known protocol from the list or specify a value manually (hexadecimal). 2. 81 . Allows you to provide CoS prioritization by using the standard based 802. If a frame received at an Ethernet port has a CFI set to 1. Configure filter parameters and click Apply. Open the Traffic > L2 Filters page. DSCP/IP precedence Specify the DSCP/IP precedence that will be used to filter traffic. Less than. do the following: 1. VLAN ID operator VLAN ID operator. or click the filter name to edit and existing one. Priority operator VLAN priority operator. Ethertype Specify the VLAN Ethernet Type. Valid operator types are: Greater than. OE or DE+ To configure an L2 filter. CFI/DEI Specify the Canonical Format Indicator or the Drop Eligibility Indicator. The Ethernet type identifies if the following VLAN is a C-VLAN an S-VLAN or if we accept both types. This should always be set to zero for connection to Ethernet switches. 3. For instance if you select a Range for the second VLAN ID operator you need to select Equal to for the first VLAN ID operator. Valid operator types are: Greater than. Note: If a check box is not checked. Priority Specify the VLAN priority. Note: A limitation exists for the operators. VLAN ID Specify the VLAN ID that will be used to filter traffic. Equal to or Range (inclusive range).1Q priority tag. Less than. CFI is used for compatibility reasons between Ethernet type networks and Token Ring type networks. Click Add to create a new file. Less than.5: Monitoring and filtering Traffic filters "VLAN" and "VLAN in VLAN" settings You can specify several VLAN fields for the first VLAN (VLAN 1) as well as the second level VLAN (VLAN 2). Equal to or Range (inclusive range). then that frame should not be forwarded "as is" to an untagged port. Configuring an L2 filter on an EtherNID EE. DSCP/IP precedence operator DSCP/IP precedence operator. Valid operator types are: Greater than. Only one of the VLAN operators can be set to a range. Possible values are 0 to 7. 2. then the value is ignored. Equal to or Range (inclusive range). the other needs to be set to Equal to. Interpretation is based on the carrier's equipment and administrative policies. then the value is ignored. Specify the address as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). The other bits are ignored. Ethernet header settings The following characteristics can be defined: • MAC destination / mask: Specify the destination MAC address and mask. You can specify three VLAN fields for the first level VLAN (VLAN 1) as well as the second level VLAN (VLAN 2). Possible values are 0 to 7. Ethertype: Select a well-known protocol from the list or specify a value manually (hexadecimal). 82 . Only the bits specified by the mask are used. • • “VLAN” and “VLAN in VLAN” settings To match VLAN traffic you must select VLAN for Ethertype. This should always be set to zero for connection to Ethernet switches. The other bits are ignored. CFI is used for compatibility reasons between Ethernet type networks and Token Ring type networks. Interpretation is based on the carrier’s equipment and administrative policies VLAN CFI Specify the Canonical Format Indicator. Note: If a check box is not checked. 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. Allows you to provide QoS prioritization by using the standard based 802. VLAN priority Specify the VLAN priority. Specify the address as six pairs of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx).5: Monitoring and filtering Traffic filters L2 filter parameters L2 filter name Specify a name to uniquely identify the filter.1Q priority tag. Only the bits specified by the mask are used. MAC source / mask: Specify the source MAC address and mask. You should ensure that all IP addresses specified in a filter are static or reserved. 83 . The following information is presented for each filter: • • Filter name: Unique name assigned to the filter. 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. commonly used filters are defined. Otherwise you must have to manually update your filter every time the addresses change. The address is specified in dotted decimal notation. Note: Filtering source or destination IP address assigned by Dynamic Host Control Protocol (DHCP) can cause problems. Note: Filtering source or destination IP address assigned by Dynamic Host Control Protocol (DHCP) can cause problems.5: Monitoring and filtering Traffic filters VLAN ID Specify the VLAN ID that will be used to filter traffic. IP source: Indicates the source address assigned to the filter. • IP destination: Indicates the destination address assigned to the filter. The filter will only process packet being sent to this address. open the Traffic > IPV4 Filters page. By default. Viewing IPv4 filters To view a list of active IPV4 traffic filters. The filter will only process packets received from this address. The address is specified in dotted decimal notation. UDP is used by DNS. Click Add to create a new file. ICMP is used by Ping. 3. or click the filter name to edit and existing one. Common protocol are TCP (6). do the following: 1. By default. SMTP.UDP (17) and ICMP (1) • • • TCP is used by HTTP. 2. FTP. Other protocol types are ignored. SNMP. This setting is only valid when the protocol field is set to TCP (6) or UDP (17). Open the Traffic > IPV4 Filters page. Configure filter parameters and click Apply. commonly used filters are defined. Configuring an IPv4 filter on an EtherNID GE or MetroNID TE To configure an IPV4 filter. RIP. This setting is only valid when the protocol field is set to TCP (6) or UDP (17). Dst port: Identifies the destination port that will be used to match this rule. 84 .5: Monitoring and filtering Traffic filters • Protocol: Identifies the protocol type that this filter will process. Telnet. • • Src port: Identifies the source port that will be used to match this rule. Specify either 0 or 3. Specify a value in the range of 5 . IPv4 header settings The following characteristics can be defined: IPv4 source / mask Specify the source address and mask.15. These settings are only valid when the Protocol field is set to TCP (6) or UDP (17).5: Monitoring and filtering Traffic filters IPv4 filter parameters IPv4 filter name Specify a name to uniquely identify the filter.iana. Note: If a check box is not checked. Header length Specify the header length in 32-bit units. Only the bits specified by the mask are used. TTL Specify the time-to-live value to match. Protocol Select a well-known protocol from the list or specify a port number manually (decimal). IPv4 destination / mask Specify the destination address and mask. 85 . Only the bits specified by the mask are used. Some well-known ICMP types are: Echo Reply (0) Destination Unreachable (3) Redirect (5) Echo (8) Time Exceeded (11) ICMP Code: See www. The other bits are ignored. These settings are only valid when the Protocol field is set to ICMP (1). The other bits are ignored.org for current values "VLAN" and "VLAN in VLAN" settings You can specify several VLAN fields for the first VLAN (VLAN 1) as well as the second level VLAN (VLAN 2). UDP/TCP port settings Specify the UDP or TCP port number used by the IPv4 source and IPv4 destination port fields. ICMP settings Specify the ICMP message type that this filter will match. then the value is ignored. DSCP The DiffServ Code Points (DSCP) value may be selected from a list of predefined values or a decimal value between 0 and 63 may be defined. ECN Explicit Congestion Notification. The Ethernet type identifies if the following VLAN is a C-VLAN an S-VLAN or if we accept both types. 3. Equal to or Range (inclusive range).5: Monitoring and filtering Traffic filters Ethertype Specify the VLAN Ethernet Type. Priority operator VLAN priority operator. 86 . commonly used filters are defined. Less than. then that frame should not be forwarded "as is" to an untagged port. Possible values are 0 to 7. Priority Specify the VLAN priority. VLAN ID operator VLAN ID operator. CFI is used for compatibility reasons between Ethernet type networks and Token Ring type networks. Configure filter parameters and click Apply. do the following: 1. Less than. DSCP/IP precedence Specify the DSCP/IP precedence that will be used to filter traffic. the other needs to be set to Equal to. Equal to or Range (inclusive range). Less than. or click the filter name to edit and existing one. For instance if you select a Range for the second VLAN ID operator you need to select Equal to for the first VLAN ID operator. VLAN ID Specify the VLAN ID that will be used to filter traffic. By default.1Q priority tag. Interpretation is based on the carrier's equipment and administrative policies. CFI/DEI Specify the Canonical Format Indicator or the Drop Eligibility Indicator. This should always be set to zero for connection to Ethernet switches. DSCP/IP precedence operator DSCP/IP precedence operator. Allows you to provide CoS prioritization by using the standard based 802. Equal to or Range (inclusive range). Valid operator types are: Greater than. Note: A limitation exists for the operators. Open the Traffic > IPV4 Filters page. Configuring an IPv4 filter on an EtherNID EE. Valid operator types are: Greater than. Click Add to create a new file. If a frame received at an Ethernet port has a CFI set to 1. 2. Valid operator types are: Greater than. OE or DE+ To configure an IPV4 filter. Only one of the VLAN operators can be set to a range. Specify either 0 or 3. Protocol: Select a well-known protocol from the list or specify a port number manually (decimal). Some well-known ICMP types are: 87 .5: Monitoring and filtering Traffic filters IPv4 filter parameters IPV4 filter name Specify a name to uniquely identify the filter. These settings are only valid when the Protocol field is set to TCP (6) or UDP (17). Only the bits specified by the mask are used. Only the bits specified by the mask are used. IPv4 header settings The following characteristics can be defined: • • • • • • • IPv4 source / mask: Specify the source address and mask. ECN: Explicit Congestion Notification. TTL: Specify the time-to-live value to match. ICMP settings Specify the ICMP message type that this filter will match. The other bits are ignored. Header length: Specify the header size in bytes. The other bits are ignored. These settings are only valid when the Protocol field is set to ICMP (1). DSCP: The DiffServ Code Points (DSCP) value may be selected from a list of predefined values or a decimal value between 0 and 63 may be defined. UDP/TCP port settings Specify the UDP or TCP port number used by the IPv4 source and IPv4 destination port fields. IPv4 destination / mask: Specify the destination address and mask. 5: Monitoring and filtering Traffic filters • • • • • • Echo Reply (0) Destination Unreachable (3) Redirect (5) Echo (8) Time Exceeded (11) ICMP Code: See www.org for current values 88 .iana. Range: < 2 to 62 > Color mode: Indicates if the regulator reacts to data color. EBS: Excess Burst Size. EIR: Excess Information Rate. To view a list of all defined regulators.5: Monitoring and filtering Bandwidth policing Bandwidth policing Traffic regulators enable you to limit the flow of traffic for a specific policy. open the Traffic > Regulators page. 89 . Coupling Flag: Modifies the way in which the regulator processes yellow traffic. A total of 15 traffic regulators can be defined. CIR: Committed Information Rate. Initially this page is empty as no regulators are defined by default. Range. CBS: Committed Burst Size. The following information is presented for each filter: • • • • • • • Name: Unique name assigned to the regulator. Configure settings and click Apply. Yellow traffic in excess of this maximum will be declared red by the regulator and will be dropped. Regulator settings Traffic regulator name Specify a name to uniquely identify the regulator. Range: 0 to maximum port speed (in kbps) Committed Burst Size Specify the maximum burst size for traffic declared green by the traffic regulator. do the following: 1. Click Add to define a new regulator.: 3. Green traffic in excess of this maximum will be declared yellow by the regulator and will be submitted to EIR regulation. Range: 2 to 62 kBytes Note: Burst size must be greater than the port MTU. Open the Traffic > Regulators page. Range: 0 to maximum port speed (in kbps) Excess Burst Size Specify the maximum burst size for traffic declared yellow by the traffic regulator. Committed Information Rate (CIR) Specify the maximum average bandwidth for traffic declared green by the regulator. Excess Information Rate (EIR) Specify the maximum average bandwidth for traffic declared yellow by the regulator. Range: 2 to 62 kBytes Note: Burst size must be greater than the port MTU.5: Monitoring and filtering Bandwidth policing Configuring a regulator To configure a traffic regulator. 90 . 2. color-blind: All incoming traffic enters the traffic regulator initially green. True: Yellow data is limited by the setting of the Committed Information Rate plus the Excess Information Rate. Assigning a regulator to a policy Once a regulator has been configured you can assign it to a policy. • • color-aware: Traffic enters the traffic regulator with the color set by a policy. See "Traffic policies and monitoring" on page 72. Coupling Flag Modifies the way in which the regulator processes yellow traffic. 91 .5: Monitoring and filtering Bandwidth policing Color mode Specifies how the initial color of traffic should be attributed. • • False: Yellow data is limited by the setting of the Excess Information Rate. • • • • Enable LED reporting: Reports alarms by activating the appropriate EtherNID LED corresponding to the severity of the alarm. Notification There are four mechanisms for alarm reporting: LED. Enable syslog reporting: Reports alarms by creating syslog entries. Thresholds • • Threshold on (soaking time in msecs): Delay after an event is detected before the alarm notification occurs. SNMP.3AH reporting: Reports alarms via 802. Threshold off (soaking time in msecs): Delay after an event clears before the alarm clear notification occurs.6: Alarms Alarm settings Chapter 6: Alarms 6 Alarm settings Alarms General alarm settings are defined on the Alarm > General page. and 802. 92 . syslog. see Appendix A. Enable 802.3AH. Enable SNMP reporting: Reports alarms via SNMP traps from Accedian’s private MIB. Note: For a list of all supported alarms.3AH organization specific OAMPDUs. For a description of each field see "Customizing an alarm" on page 94.6: Alarms Alarm configuration Alarm configuration The Alarm > Configuration page lists all defined alarms. 93 . temp. Unassigned Unassigned Enable Indicates if the alarm is enabled (true) or disabled (false). ID 1 2 3 4 5 6 7 8 9 10 Description Port module for link down and others related alarms. vcc and lbc alarms and warnings. The alarm number look like this AAA. A module number is assigned for each source of alarm in the system. AAA: Module number (1-999). PAA module for CC. For instance the port module is set to 1. If enabled. the PAA is set to 3 and the environmental is set to 8. click its Identifier. Packet Loss and others related alarms. power supplies and temperature sensors.BBB. the alarm will be reported 94 . SFP module for Rx/Tx power. Assigned by the EtherNID.CC and is express in decimal. the instance number and the error number.6: Alarms Alarm configuration Customizing an alarm To customize an alarm. The alarm identifier is compose of 3 fields. Unassigned Unassigned Unassigned Unassigned Environmental module for fans. BBB: Instance number (1-999). the module number. Identifier Unique number that identifies this alarm. the SFP module is set to 2. CC: Error number (1-99). 95 . Minor: A error condition has occurred that does not seriously affect system functionality. Provides status information. • • • • Informational: No effect on service.6: Alarms Alarm configuration Severity Indicates the severity level for the alarm. Major. Major: A serious disruption of service or hardware malfunction has occurred which requires immediate attention to restore system functionality. and Critical alarms will be indicated on the EtherNID front panel LEDs. Description Textual description of the alarm. If LED reporting is enabled on the Alarm > General page. Critical: A service-affecting condition has occurred that requires immediate corrective action. Service affecting Specify if the alarm will be displayed as service affecting or non-service affecting. the Minor. For a description of each field see "Customizing an alarm" on page 94. To view detailed information on an alarm click its Identifier.6: Alarms Alarm status Alarm status The Alarm > Status page presents a summary of all alarms. For example: 96 . and alarm settings. 97 . Temperature sensor thresholds • • First threshold: Indicates the temperature that will activate a first overheat temperature alarm.6: Alarms Chassis alarms Chassis alarms The Alarm > Chassis page presents chassis-related status. Power supply status Indicates the status of the various power sources. • • A green light indicates that the power source is connected and is operating normally. alarms. A red light indicates that the power source is not connected or is not operating normally. Second threshold: Indicates the temperature that will activate a second overheat temperature alarm. Temperature sensor status Indicates the current temperature inside the unit. • • 98 . Click this name to configure the instance. Administration and Maintenance OAM configuration To view a list of all OAM instances and their settings. the instance will only listen and reply to received information type length and value (TLV) frames during the discovery phase. open the OAM > Configuration page. Administration and Maintenance 7 Operations. When passive. This field does not indicate a successful discovery of an OAM peer. The following information is presented for each instance: • • • Name: The instance name as defined in the configuration page. See the status page for details. Encapsulation: Indicates if OAM packets are tagged with a VLAN or not. OAM state: Indicates if an instance is enabled or disabled. Administration and Maintenance OAM configuration Chapter 7: Operations. OAM mode: The OAM instance may be active or passive. An active instance actively transmit unsolicited information TLV frames. Port: Indicates the port used by this OAM instance.7: Operations. Administration and Maintenance OAM configuration Configuring an OAM instance To configure an OAM instance. do the following: 1. Enable OAM protocol Enable the passive or active OAM 802. Encapsulation Indicates if OAM packets are tagged with a VLAN or not. OAM instance parameters OAM instance name Specify a name to identify the OAM instance.3AH protocol for this OAM instance. An active instance will immediately start to send information OAMPDUs associated with the discovery process.7: Operations. Click Add to add a new OAM instance. Configure OAM instance settings and click Apply. Port name Indicates the port used by this OAM instance. 99 . 3. Open the OAM > Configuration page. 2. Active: Immediately searches for an OAM peer by sending OAMPDUs. long frames. This unit supports variable responses Enable this option to respond to OAMPDUs requests. but not limited to. as in EFE. This can be caused by various types of errors including. The window setting defines the time. Using a number of frames instead of a time period. in seconds. short frames. Administration and Maintenance OAM configuration Active Mode / Passive Mode Select the mode of operation for the OAM instance. or MAC level. An errored frame second is a one second period in which at least one frame was bad. This can be caused by various types of errors including. This enables you to limit the impact of the extra OAM traffic on a link that is already heavily loaded.7: Operations. Errored Frame Seconds Summary Event (EFSSE) Threshold and window Specify the threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. A frame error is an error detected at the layer 2. Number of Events re-transmitted Specify the number of times an event is re-transmitted to ensure its reception by the peer. etc. short frames. etc. or MAC. This unit supports events Enable this option to issue event OAMPDUs when needed. of the period. but not limited to: CRC errors. • • Passive: Listens for OAMPDUs and replies once it starts receiving them. Errored Frame Period Event (EFPE) Threshold and window Specify the threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. This unit supports loopback Enable this option to react to loopback requests from the OAM peer. The window setting defines the time. long frames. 100 . of the period. CRC errors. means that this event is generated based on the ratio of bad frames versus good frames. This setting is only valid if This unit supports events is enabled. The window setting defines the number of frames that make up a period. In other words. Max OAM PDU size Specify the maximum frame size the OAM instance will use. A frame error is an error detected at the layer 2. in seconds. level. Errored Frame Event (EFE) Threshold and window Specify the threshold setting that defines the number of frame errors that must be detected in a given period to trigger the transmission of an event. this 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. or MAC. This can be caused by various types of errors including. Administration and Maintenance OAM configuration A frame error is an error detected at the layer 2. level. but not limited to: CRC errors. short frames. 101 . etc. long frames.7: Operations. the user can select filters and can allow other traffic to flow through. An enabled remote loopback will instruct the unit to transmit a loopback request to its OAM partner. Click on an instance name to configure it. The following information is presented for each loopback: • • Name: This field reports the loopback instance name. effectively doing an in-service loopback.3ah mode or may be using a private or proprietary mode. Location: A loopback instance may be local or remote. Administration and Maintenance Loopbacks Loopbacks The EtherNID supports in-service loopbacks on either the client or network ports. a local loopback immediately applies the loopback to the unit as programmed. Filter type: For private loopback mode. this depends on the location setting. Once enabled. When using the private mode. Lpbk mode: The loopback control logic. may be using the standard IEEE 802. See the loopback configuration page for details. • • • 102 . as configured in the loopback configuration page. once enabled. open the OAM > Loopback page. An instance enabled to react on external loopback commands is not shown in this field. Lpbk state: Reports the enable/disable state of the loopback. An enabled loopback may not necessarily loopback traffic.7: Operations. a filter must be selected. To view a list of all loopbacks and their settings. Loopback parameters Name The OAM instance name as defined in the OAM configuration page. 103 . Loopback all packets that have a destination address equal to 00:30:79:FF:FF:FF Exfo L2: Loopback all packets that have a source MAC OUI equal to 00:03:01 Exfo L3: Loopback all UDP echo service packets.7: Operations. Administration and Maintenance Loopbacks Adding a loopback To add a loopback. you must first add an OAM instance on the OAM > Configuration page. 3. Loopback enable Enables the loopback function. State The current state of the loopback. Custom: Loopback all traffic that matches the user defined filter. Type • • • • Iometrix L1: Iometrix cNode level 1. before you can add a new loopback. 2. Open the OAM > Loopback page. do the following: 1. Therefore. Only one loopback is supported per OAM instance. Configure loopback parameters and click Apply. Remote loopback enable These options allow loopbacks to be activated remotely using the following devices/protocols: • JDSU/ActernaTM • • • Enable discovery loop commands: Accept or discard JDSU/Acterna discovery loopback commands. When the timeout expires the loopback is automatically removed. Actions • • • Swap MAC addresses: Swaps the source and destination MAC addresses. see "Traffic filters" on page 79. OAM 802. This option can only be set for Manual loopbacks with no timeout. Warning: Enabling this option will interrupt the Ethernet service in one direction. select the IPv4 filter that will be applied to loopback traffic. Tagged OAM instances only accept loopback commands from a specific VLAN.3AH Note: This option is not affected by the setting of Loopback enable. Note: This option is not affected by the setting of Loopback enable. SunriseTM: The EtherNID supports tests on layers 2 and 3. Drop opposite traffic Drops traffic originating from Client port when looping back to the Network port and vice versa. Administration and Maintenance Loopbacks Persistent Enable or disable loopback at startup time. IPV4 filter If Filter type is set to IPv4 filter. Swap TCP/UDP ports: Swaps the source and destination TCP/UDP ports. For more information on filters. VLAN loopback commands will be accepted. Swap IP addresses: Swaps the source and destination IP addresses. Accept VLAN loop commands: When enabled.7: Operations. select the L2 filter that will be applied to loopback traffic. Filter type Select the filter type that will be applied to the loopback traffic. L2 filter If Filter type is set to L2 filter. This option is only valid for untagged OAM instances. Loopback timeout Specify the number of minutes that the loopback will remain enabled. 104 . Txm event: The number of OAM events transmitted.7: Operations. Rcv duplicate: The number of received OAM events that were duplicated. For complete details on transmitted and received events. Txm duplicate: The number of transmitted OAM events that were duplicated. Rcv event: The number of OAM events received. lists a summary of all the events exchanged on an OAM connection. 105 . click a Name. Administration and Maintenance OAM events OAM events The OAM > Event page. The following information is presented for each event: • • • • • Name: The name of the OAM instance. The fourth INTEGER represents the Errored Symbols field.7: Operations. The second INTEGER represents the Errored Symbol Window field. The second INTEGER represents the Errored Frame Period Threshold field. OAM Local Error Frame Event A sequence of six integers corresponding to the respective fields in the most recently transmitted Errored Frame Event TLV in an Event Notification OAMPDU. • • • • • • The first INTEGER represents the Event Time Stamp field. 106 . This sequence is updated when a CTL:OAMI:request service primitive is generated within the OAM sublayer with an OAMPDU Code field value equal to the Event Notification code and Event TLV Type field equal to the Errored Frame Period Event value. The third INTEGER represents the Errored Frame Threshold field. The fifth INTEGER represents the Error Running Total field. The third INTEGER represents the Errored Symbol Threshold field. The sixth INTEGER represents the Event Running Total field. The third INTEGER represents the Errored Frame Period Threshold field. The fourth INTEGER represents the Errored Frames field. Administration and Maintenance OAM events Transmitted and Received event notifications OAM Local Error Symbol Period Event A sequence of six integers corresponding to the respective fields in the most recently transmitted Errored Symbol Period Event TLV in an Event Notification OAMPDU. The second INTEGER represents the Errored Frame Window field. • • • • • • The first INTEGER represents the Event Time Stamp field. The fourth INTEGER represents the Errored Frame Period Threshold field. OAM Local Error Frame Period Event A sequence of six integers corresponding to the respective fields in the most recently transmitted Errored Frame Period Event TLV in an Event Notification OAMPDU. The sixth INTEGER represents the Event Running Total field. The fifth INTEGER represents the Error Running Total field. This sequence is updated when a request service primitive is generated within the OAM sublayer with an OAMPDU Code field value equal to the Event Notification code and Event TLV Type field equal to the Errored Frame Event value. The fifth INTEGER represents the Error Running Total field. The sixth INTEGER represents the Event Running Total field. • • • • • • The first INTEGER represents the Event Time Stamp field. This sequence is updated when a request service primitive is generated within the OAM sublayer with an OAMPDU Code field value equal to the Event Notification code and Event TLV Type field equal to the Errored Symbol Period Event value. Administration and Maintenance OAM events OAM Local Error Frame Seconds Summary Event A sequence of six integers corresponding to the respective fields in the most recently transmitted Errored Frame Seconds Summary Event TLV in an Event Notification OAMPDU.7: Operations. This sequence is updated when a request service primitive is generated within the OAM sublayer with an OAMPDU Code field value equal to the Event Notification code and Event TLV Type field equal to the Errored Frame Seconds Summary Event value. • • • • • • The first INTEGER represents the Event Time Stamp field The second INTEGER represents the Errored Frame Seconds Summary Window field The third INTEGER represents the Errored Frame Seconds Summary Threshold field The fourth INTEGER represents the Errored Frame Seconds Summary field The fifth INTEGER represents the Error Running Total field The sixth INTEGER represents the Event Running Total field 107 . The fifth bit corresponds to the Local Stable bit in the Flags field. The seventh bit corresponds to the Remote Stable bit in the Flags field. The sixth bit corresponds to the Remote Evaluating bit in the Flags field. The second bit corresponds to the Dying Gasp bit in the Flags field. The second bit corresponds to the Dying Gasp bit in the Flags field.7: Operations. The enumerations match the states within the Discovery state diagram (see Figure 57-5 of IEEE802. Administration and Maintenance OAM status OAM status The OAM > Status page presents a summary of the status of each OAM instance. The third bit corresponds to the Critical Event bit in the Flags field. The third bit corresponds to the Critical Event bit in the Flags field. • Remote flags: A string of seven bits corresponding to the Flags field in the most recently received OAMPDU. The fifth bit corresponds to the Local Stable bit in the Flags field. • • • • • The first bit corresponds to the Link Fault bit in the Flags field. The following information is presented for each instance: • • Name: OAM instance name.3). Discovery: Identifies the current state of the OAM Discovery function. The fourth bit corresponds to the Local Evaluating bit in the Flags field. 108 . The fourth bit corresponds to the Local Evaluating bit in the Flags field. • • • • • • • The first bit corresponds to the Link Fault bit in the Flags field. • • • • • • • LINK_FAULT ACTIVE_SEND_LOCAL PASSIVE_WAIT SEND_LOCAL_REMOTE SEND_LOCAL_REMOTE_OK SEND_ANY Local flags: A string of seven bits corresponding to the Flags field in the most recently transmitted OAMPDU. click a Name. Administration and Maintenance OAM status • • • The sixth bit corresponds to the Remote Evaluating bit in the Flags field.7: Operations. This value is updated on reception of a valid frame. • Remote revision: The value of the Revision field in the Local Information TLV of the most recently received Information OAMPDU. This value is updated on reception of a valid frame. Parser state / Mux state A string of three bits corresponding to the State field of the most recently transmitted Information OAMPDU. The seventh bit corresponds to the Remote Stable bit in the Flags field. Local revision: The value of the Revision field in the Local Information TLV of the most recently transmitted Information OAMPDU. For example: Detailed status information Local Info TLV revision The value of the Revision field in the Local Information TLV of the most recently transmitted Information OAMPDU. with: • • • • • DestinationField equal to the reserved multicast address for slow protocols LengthOrType 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 109 . For detailed status information. The first and second bits corresponds to the Parser Action bits in the State field. This value is updated on reception of a valid frame. Vendor specific info The value of the Vendor Specific Information field of the most recently received Information OAMPDU. Vendor OUI The value of the OUI variable in the Vendor Identifier field of the most recently transmitted Information OAMPDU. The third bit corresponds to the Multiplexer Action bit in the State field. Note: These states will change when a loopback is enabled. • Note: The revision number indicates the number of times that the configuration for the local OAM instance has been modified. Vendor OUI The value of the OUI variable in the Vendor Identifier field of the most recently received Information OAMPDU.7: Operations. Vendor specific info The value of the Vendor Specific Information field of the most recently received Information OAMPDU. Parser state / Mux state A string of three bits corresponding to the State field of the most recently received Information OAMPDU. 110 . The third bit corresponds to the Multiplexer Action bit in the State field. Administration and Maintenance OAM status Remote Info TLV revision The value of the Revision field in the Remote Information TLV of the most recently received Information OAMPDU. Note: These states will change when a loopback is enabled. The first and second bits corresponds to the Parser Action bits in the State field. Include all types: info. var response. Include all types: info.7: Operations. Txm OAMPDU: Number of OAMPDUs transmitted by this instance. loopback etc. The following information is presented for each instance: • • • • • Name: OAM instance name. Rcv OAMPDU: Number of OAMPDUs received by this instance. loopback etc. For complete detailed statistics. var request. Txm Info OAMPDUs: Number of Info OAMPDUs transmitted by this instance. var response. presents a summary of the statistics for each OAM instance. var request. click a Name. Rcv Info OAMPDUs: Number of Info OAMPDUs received by this instance. Administration and Maintenance OAM statistics OAM statistics The OAM > Statistics page. For example: 111 . Administration and Maintenance OAM statistics OAM detailed statistics information Name The name of the OAM instance. Generalized nonresettable counter. with: • • • • • DestinationField equal to the reserved multicast address for slow protocols. This counter is incremented on reception of a valid frame. A slow protocols subtype value equal to the subtype reserved for OAM. Length Or Type field value equal to the reserved Type for slow protocols. Information A count of OAMPDUs received that contain the OAM Information code. Generalized nonresettable counter. Generalized nonresettable counter.7: Operations. This counter is incremented on reception of a valid frame. The OAMPDU code equals the OAM Information code and is supported by the device. Unique event A count of the OAMPDUs received that contain the Event Notification code. A slow protocols subtype value equal to the subtype reserved for OAM. This counter is incremented on reception of a valid frame with: • • • • Destination Field equal to the reserved multicast address for slow protocols. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). 112 . The Sequence Number field is not equal to the Sequence Number field of the last received Event Notification OAMPDU and is supported by the device. Length Or Type field value equal to the reserved Type for slow protocols. Receive Unsupported codes A count of OAMPDUs received that contain an OAM code that are not supported by the device. A slow protocols subtype value equal to the subtype reserved for OAM. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). An OAMPDU code for a function that is not supported by the device. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). The OAMPDU code equals the Event Notification code. LengthOrType field value equal to the reserved Type for slow protocols. with: • • • • Destination Field equal to the reserved multicast address for slow protocols. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). The Sequence Number field is equal to the Sequence Number field of the last received Event Notification OAMPDU. A slow protocols subtype value equal to the subtype reserved for OAM. A slow protocols subtype value equal to the subtype reserved for OAM. The OAMPDU code equals the Loopback Control code and is supported by the device. with: • • • • • DestinationField equal to the reserved multicast address for slow protocols. A slow protocols subtype value equal to the subtype reserved for OAM. LengthOrType field value equal to the reserved Type for slow protocols. Variable response A count of OAMPDUs received that contain the Variable Response code. Administration and Maintenance OAM statistics Duplicate event A count of the OAMPDUs received that contain the Event Notification code. Generalized nonresettable counter. with: • • • • DestinationField equal to the reserved multicast address for slow protocols. The OAMPDU code equals the Variable Request code and is supported by the device. LengthOrType field value equal to the reserved Type for slow protocols. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). Loopback control A count of OAMPDUs received that contain the Loopback Control code. 113 . Generalized nonresettable counter. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). Generalized nonresettable counter.7: Operations. This counter is incremented on reception of a valid frame. with: • • • • DestinationField equal to the reserved multicast address for slow protocols. A slow protocols subtype value equal to the subtype reserved for OAM. LengthOrType field value equal to the reserved Type for slow protocols. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). Generalized nonresettable counter. with: • • • • DestinationField equal to the reserved multicast address for slow protocols. Variable request A count of OAMPDUs received that contain the Variable Request code. This counter is incremented on reception of a valid frame. This counter is incremented on reception of a valid frame. This counter is incremented on reception of a valid frame. LengthOrType field value equal to the reserved Type for slow protocols. The OAMPDU code equals the Variable Response code and is supported by the device. The OAMPDU code equals the Event Notification code. Generalized nonresettable counter. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). A slow protocols subtype value equal to the subtype reserved for OAM. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAMPDU code indicating an Information OAMPDU. Unique event A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Event Notification code. The OAMPDU code equals the Organization Specific code and is supported by the device. The OAMPDU code equals the Event Notification code. LengthOrType field value equal to the reserved Type for slow protocols. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period).7: Operations. Generalized nonresettable counter. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). • • • A Slow_Protocols subtype value equal to the subtype reserved for OAM. 114 . This counter is incremented on reception of a valid frame. Information A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the OAM Information code. 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 nonresettable counter. This counter is incremented when a request service primitive is generated within the OAM sublayer. Transmit Unsupported codes A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that are not supported by the device. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). Administration and Maintenance OAM statistics Organization specific A count of OAMPDUs received that contain the Organization Specific code. The Sequence Number field is not equal to the Sequence Number field of the last transmitted Event Notification OAMPDU. Generalized nonresettable counter. with: • • • • DestinationField equal to the reserved multicast address for slow protocols. Generalized nonresettable counter. Variable request A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Variable Request code. • • The OAMPDU code equals the Event Notification code. 115 . 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 nonresettable counter. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period).7: Operations. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Response OAMPDU. Generalized nonresettable counter. The Sequence Number field is equal to the Sequence Number field of the last transmitted Event Notification OAMPDU. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Loopback Control OAMPDU. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM code indicating a Variable Request OAMPDU. Loopback control A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Loopback Control code. Generalized nonresettable counter. Variable response A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Variable Response code. This counter is incremented when a request service primitive is generated within the OAM sublayer. Generalized nonresettable counter. Organization specific A count of Organization Specific OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Organization Specific code. This counter has a maximum increment rate of slow protocol frames (No more than 10 frames shall be transmitted in any one-second period). Administration and Maintenance OAM statistics Duplicate event A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain the Event Notification code. Administration and Maintenance OAM statistics 116 .7: Operations. Once defined.8: RFC-2544 RFC-2544 flows Chapter 8: RFC-2544 8 RFC-2544 flows RFC-2544 NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE models. open the RFC-2544 > Flows page. To edit any existing flow. click the flow name in the list. To add a new flow. the flow can be selected under the Configuration tab in the Traffic flow settings pull down menus. 117 . Viewing RFC-2544 Flows To view and add flows to use in RFC-2544 tests. A total of 15 flows can be defined. Supported values for 1Gbps products: 1 Mbps to 1 Gbps (step of 1 Mbps). click the Add button. Name Unique name assigned to the flow. Description Description configured to identify the flow and its characteristics. Note: Supported values for 100Mbps products: 1 to 100 Mbps (step of 1 Mbps). 3. Click Add. do the following: 1. or click a flow name to edit and existing one. Configure the flow parameters and click Apply. 118 . Flow description Description to identify the flow and its characteristics. 2. Flow name Unique name assigned to the flow. Open the RFC-2544 > Flows page. Note: Supported values for 100Mbps products: 1 to 100 Mbps (step of 1 Mbps). it can be selected to run in the RFC-2544 > Configuration page. To configure an RFC-2544 Flow. Supported values for 1Gbps products: 1 Mbps to 1 Gbps (step of 1 Mbps).8: RFC-2544 RFC-2544 flows Configuring RFC-2544 Flows Once an RFC-2544 Flows is created. For the random configuration you need to select one of the supported patterns. packets : Stops after sending a specified amount of packets. The period is a number of milli-seconds between each burst of packets. Burst The burst traffic type consist of sending a configured number of packets at every period. Size type Select between fixed or random size. Payload pattern Select between fixed-data. Constant The constant traffic type consist of sending a specific number of bits per second. Bit rate The rate. The fixed configuration requires a packet Size to be specified. at which to send this flow. bytes : Stops after sending a specified amount of bytes. 119 .8: RFC-2544 RFC-2544 flows Flow traffic settings Traffic type Select between burst or constant rate traffic. • • • seconds : Stops after a specified amount of seconds. Flow duration settings Duration type Choose between the following duration types: • continuous : Stops only when user manually stops the test. in Kbps. The random configuration requires a Minimum size value and a Maximum size value to be specified. incremental or random patterns in the payload part of the transmitted frames. When enabled. Viewing RFC-2544 Configuration To view the RFC-2544 configuration. all test packets are encapsulated into the specified VLAN ID. Applies only when VLAN 1 header is enabled. 120 .8: RFC-2544 RFC-2544 configuration RFC-2544 configuration NOTE: The RFC-2544 feature is only available on the EtherNID GE andMetroNID TE models. VLAN 1 Ethernet type First VLAN Ethernet type. VLAN 1 Priority First VLAN priority bits. Test packet settings MAC destination This is the peer MAC address. VLAN 1 ID First VLAN ID. Applies only when VLAN 1 header is enabled. open the RFC-2544 > Configuration page. Enable VLAN 1 header This is to encapsulate all packets with 1 VLAN header. VLAN 2 CFI Second VLAN canonical format indicator (CFI). Applies only when VLAN 1 header is enabled. Applies only when VLAN 2 header is enabled. When enabled.8: RFC-2544 RFC-2544 configuration VLAN 1 CFI First VLAN canonical format indicator (CFI).1Q in . Traffic flow settings First flow Name of the first flow to send. (. all test packets are encapsulated into the second specified VLAN ID. Applies only when VLAN 2 header is enabled. Test port settings Port name Name configured for the port on which to send the flow(s). 121 . Applies only when VLAN 2 header is enabled. VLAN 2 Ethernet type Second VLAN Ethernet type.1Q) VLAN 2 ID Second VLAN ID. Second flow Name of the second flow to send. Enable VLAN 2 header This is to encapsulate all packets with 2 VLAN headers. Applies only when VLAN 1 header is enabled. VLAN 2 Priority Second VLAN priority bits. bytes or run until you stop it. Viewing RFC-2544 Measurements To view the RFC-2544 measurements. The trial can contain one or two specific flows and can last for a specified amount of time. packets. Received packets Total packets received by the associated inspector. Flow measurements With the RFC-2544 measurements feature you can perform specific testcases to pinpoint device or network problems or to measure current latency and jitter on a specific network segment.8: RFC-2544 RFC-2544 measurements RFC-2544 measurements NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE models. Flow name Unique name assigned to each flow. open the RFC-2544 > Measurements page. Flow state Indicates the flow's current state. Running : The flow is currently running. Transmitted packets Total packets transmitted by this flow. • • • • Failed : The flow was deleted before the test was started. Stopped : The tester stopped the flow before it completed. 122 . Possible values are: • Waiting : Waiting to be started by the tester. Completed : The flow reached its duration limit. 8: RFC-2544 RFC-2544 measurements Average delay Average two-way delay (latency) in microseconds. Transmitted bytes Total bytes transmitted by this flow. shows when the test was completed or stopped. click on the details link for the specific flow. Test stopped at: Ending time. shows when the test was started. Rate Data rate in Mbps. Transmit statistics Transmitted packets Total packets transmitted by this flow. Detailed view of RFC-2544 Measurements To view the deatiled view of RFC-2544 measurements. 123 . This is the amount of Mbits received in the last second. Test times Test started at: Starting time. Average DV Average two-way delay variation (jitter) in microseconds. Possible values are: • Waiting : Waiting to be started by the tester. Stopped : The tester stopped the flow before it completed. Number of gaps Number of gaps in the sequence number. Average Average two-way delay in microseconds. Completed : The flow reached its duration limit. Maximum gap Maximum size of the received gaps. Running : The flow is currently running. This is the amount of Mbits received in the last second. Two-way delay Instantaneous Two-way instantaneous delay value in microseconds. Maximum Maximum two-way delay in microseconds. Receive statistics Received packets Total packets received by the associated inspector. Minimum Minimum two-way delay in microseconds. 124 .8: RFC-2544 RFC-2544 measurements State Indicates the flow's current state. Rate Data rate in Mbps. OOO or duplicates Out of order or duplicate packets received by this inspector. • • • • Failed : The flow was deleted before the test was started. Received bytes Total bytes received by the associated inspector. Average Average two-way delay variation in microseconds.8: RFC-2544 RFC-2544 measurements Two-way delay variation Instantaneous Two-way instantaneous delay variation value in microseconds. Minimum Minimum two-way delay variation in microseconds. Maximum Maximum two-way delay variation in microseconds. 125 . click the testsuite name in the list. Name Unique name assigned to the testsuite. 126 . To add a new testsuite. the Testsuite can be run to determine the conformance of a network section or a specific device. Viewing RFC-2544 Testsuites To view the RFC-2544 testsuites.8: RFC-2544 RFC-2544 testsuite RFC-2544 testsuite NOTE: The RFC-2544 testsuite feature is only available on the MetroNID TE models. Once defined. 1Gbps product supported values: 1 Mbps to 1 Gbps (step of 1 Mbps). click the Add button. Note: 100Mbps product supported values: 1 to 100 Mbps (step of 1 Mbps). open the RFC-2544 > Testsuite page. A total of 8 testsuites can be defined. To edit any existing testsuite. Description Description configured to identify the testsuite and its characteristics. 8: RFC-2544 RFC-2544 testsuite Detailed view of RFC-2544 Testsuites To view the deatiled view of RFC-2544 testsuites. click on the testsuite name from the testsuite configuration list. 1Gbps product supported values: 1 Mbps to 1 Gbps (step of 1 Mbps). Suite configuration Note: 100Mbps product supported values: 1 to 100 Mbps (step of 1 Mbps). 127 . 1Q network when VLAN is chosen. he would enter a range of 800 Mbps and 1000 Mbps with a step size of 10 Mbps. Test to run Select all conformance tests you want to run in this testsuite. VLAN protocol IDs are set to 0x8100 for 802. Y. the 10000 byte frame size (Jumbo frame) is unselected as it was not a frame size defined by the RFC-2544 standard. Suite description Description configured to identify the testsuite and its characteristics. but which Accedian supports nevertheless. a setting of 1 would mean a 0. MAC destination The peer MAC address. By default. possible values are 0 to 7.1731 MEG level The Maintenance Entity Group level. Test packets are Y. which searches for the maximum rate for which there is no frame loss. Applies only when the specific VLAN is enabled. Peer settings Information relative to the remote peer and the test packet contents. For example. VLAN CFI Specify the Canonical Format Indicator. 128 . The Frame Size parameters let the user choose which frame sizes are to be tested. VLAN priority VLAN priority bits. Port name The port in which direction the NID can reach the peer. The default value is 0. The frame loss setting defines the acceptable difference between measured frame loss. Applies only when the specific VLAN is enabled. Throughput settings These settings are used to define the Throughput test. possible values are 0 to 4095. which means absolutely no frame loss is the target for defining full throughput. 1000 Mbps and perform a dichotomist algorithm between 800 and 1000 (and a granularity of 10) to find the highest rate for which there is no frame loss. The Trial duration parameter defines the length during which throughput will be analyzed and during which no frame loss shall occur. The NID would then test at full GigE speed. The Maximum rate and Minimum rate define the range of rates to search for while the Step size defines the granularity of the range.8: RFC-2544 RFC-2544 testsuite Suite name Unique name assigned to the testsuite.1% frame loss would be acceptable and considered as no frame loss by the test. Applies only when the specific VLAN is enabled. VLAN ID VLAN identifier.1731 LBM and the MEG (ME Group) level is configurable. For example. This should always be set to zero for connections to Ethernet switches. if the user wishes to measure the quality of a wirespeed GigE circuit. Minimum rate The Minimum rate defines the lower bound of rates to search for while the Step size defines the granularity of the range. The test will run for each Frame size selected. but which Accedian supports nevertheless.8: RFC-2544 RFC-2544 testsuite Trial duration The Trial duration parameter defines the length during which throughput will be analyzed and during which no frame loss shall occur. for a duration defined by Trial duration. The Step size indicates the step between each rate being tested. Trial duration The Trial duration is the duration for which the test will be run. Frame loss The frame loss setting defines the acceptable difference between measured frame loss. which means absolutely no frame loss is the target for defining full throughput. The frame loss setting defines the acceptable difference between measured frame loss. Trial duration The Trial duration is the duration for which the test will be run. The Frame Size parameters let the user choose which frame sizes are to be tested. the test will run at 1000 Mbps and 980 Mbps (for a Step size of 20 Mbps). or a lower rate will then be tested. the NID will perform a short throughput test first (based on the throughput settings). Frame loss settings The Frame loss test will verify that no frames are being lost for a duration of time. at two consecutive rates. Frame loss The frame loss setting defines the acceptable difference between measured frame loss. Step size The Step size defines the granularity of the range. By default. the delay and delay variation test will measure the latency and jitter at that specific rate. Two consecutive rates must be frame loss less in order to successfully pass this test. if the DUT is able to perform full wirespeed at GigE.1% frame loss would be acceptable and considered as no frame loss by the test. Maximum rate The Maximum rate defines the upper bound of rates to search for while the Step size defines the granularity of the range. The default value is 0. For example. Both tests must yield no frame loss to be successful. a setting of 1 would mean a 0. Delay and delay variation settings Once a wirespeed rate with no frame loss has been defined by the throughput test. For example. the 10000 byte frame size (Jumbo frame) is unselected as it was not a frame size defined by the RFC-2544 standard. If the throughput test has not been run prior to the delay test. The NID will start at the Maximum rate defined in the throughput settings and step down by the value set in the Step size parameter of the Frame loss settings. Step size The Step size defines the granularity of the range. 129 . A pause of 2 seconds will be done after each burst. Trial duration The Trial duration is the duration for which the test will be run in milli-secs. the DUT must not create any frame loss for each burst. Repeat Indicates the number of bursts perform for each packet size. To be successful. and the NID will perform a number of bursts as defined by the Repeat parameter. The NID will again perform a Back-to-back test for each one of the Frame sizes selected. A burst will have a duration specified by the Total duration parameter. 130 .8: RFC-2544 RFC-2544 testsuite Back to back settings The Back-to-back test performs a burst for a duration of time. click on the Start new testsuite button in the RFC-2544 > Reports page. 131 . Description Provide a description to identify the report and its characteristics. Configure the report then click the Run button to start the testsuite. Starting an RFC-2544 Testsuite To start an RFC-2544 testsuite. RFC-2544 report configuration File name Unique name assigned to the report. Testsuite configuration Select the testsuite you want to run in this report. Special note Information relative to the report not included in the previous fields.8: RFC-2544 RFC-2544 reports RFC-2544 reports NOTE: The RFC-2544 reports feature is only available on the MetroNID TE models. Technician name Who executed the testsuite. open the RFC-2544 > Reports page and click on the name of the report to view. 132 . Completed : The Testsuite has completed. Description Provide a description to identify the report. Testsuite Report Name Unique name assigned to the report.8: RFC-2544 RFC-2544 reports Viewing RFC-2544 Reports To view the RFC-2544 reports. Status Indicates the report's current status. Stopped : A user stopped the testsuite during its execution. Possible values are: • • • • Failed : An error occurred during the testsuite execution. Running : The testsuite is currently running. 133 .8: RFC-2544 RFC-2544 reports Report contents Once a test suite has finished running. the bottom of the report will look similar to the below screen shot. The entire report is displayed below. click the probe name and then select the PAA state checkbox. Click the name to configure the probe. Type: Indicates the type of probe. Running: Running one time measurement. Disabled: This probe is disabled. latency and packet loss of a given network. Probe name: Unique name assigned to the probe. State: Indicates the probe's current state. either allowing a single PAA instance to exchange data with another PAA instance or enabling it to communicate with several PAA instances simultaneously. open the PAA > Configuration page. Possible values are: 134 . UDP: Probe occurs using UDP. The PAA can be configured in a point-to-point or point-to-multi-point fashion. To view a summary of all PAA probes.9: Performance Assurance Agent PAA configuration Chapter 9: Performance Assurance Agent 9 Performance Assurance Agent PAA configuration The EtherNID Performance Assurance Agent™ can be used measure the jitter. Possible values are: • • • • • • • layer-2: Probes occurs at layer 2. Two EtherNIDs with matching settings will communicate with each other to collect data. To enable it. Associated: Peer was found. • • • Index: A unique identifier assigned to the probe. Associating: Probe is looking for peer. The following information is presented for each probe. 9: Performance Assurance Agent PAA configuration • • • • • Idle: Idle after one time measurement completed. For UDP probe this is the peer’s IPV4 address. Destination: For layer-2 probes this is the peer’s MAC address. Locked OOS: Locked traffic out of service. Sampling period: Interval at which measurement packets are issued. 135 . Locked IS: Locked traffic in service. 9: Performance Assurance Agent PAA configuration Configuring a probe 1. 2. 3. Configure parameters and click Apply. Open the PAA > Configuration page. Click Add to create a new probe or click the probe name to edit an existing probe. 136 . VLAN 2 Encapsulation Select this checkbox to enable encapsulation on VLAN 1. VLAN 1 Priority First VLAN priority bits. This applies only if the outgoing interface is encapsulated over a VLAN. Packet size Size of PAA sample packets.Ethernet) nor the 4 CRC bytes. Layer-2 peer address discovery will be done to automatically find the peer MAC address. VLAN 2 ID Set the ID to use for VLAN 2. • • layer-2: Probes occurs at layer 2. UDP maximum value is 1472. 137 . When set to FF:FF:FF:FF:FF:FF. VLAN 1 Encapsulation Select this checkbox to enable encapsulation on VLAN 1. VLAN 1 ID Set the ID to use for VLAN 1. Does not include protocol headers (UDP. Port name Select the outgoing port. Sampling Period Set the interval (in milliseconds) at which the probe issues measurement packets. VLAN 2 Priority Second VLAN priority bits. IP.9: Performance Assurance Agent PAA configuration PAA parameters General Name Specify a unique name to identify this probe. UDP: Probe occurs using UDP. PAA state Select this checkbox to enable the probe. Layer-2 maximum value is 1500. Layer-2 Parameters Destination MAC address Specify the peer’s MAC address. Minimum value is 61. Type Select the type of probe. This applies only if the outgoing interface is encapsulated over two VLANs. Continuity Packet loss reference period Packet loss reference period. VLAN 1 Priority First VLAN priority bits. Number of consecutive sampling periods without receiving peer packets before declaring loss of continuity. Delay variation threshold One-way delay variation threshold in samples. Diff-Serv Codepoint (DSCP) The Diff-Serv CodePoint value. Explicit Congestion Notification (ECN) The Explicit Congestion Notification value. Average delay threshold One-way average delay threshold. Continuity check threshold Continuity check threshold.9: Performance Assurance Agent PAA configuration UDP parameters Destination IP address The peers IPv4 destination address. Maximum delay variation Maximum one-way delay variation allowed. Average delay variation threshold One-way average delay variation threshold. One-way Reference period One-way reference period. Maximum delay Maximum one-way average delay. This applies only if the outgoing interface is encapsulated over a VLAN. Delay threshold Maximum one-way delay allowed in samples. Packet loss threshold Packet loss threshold in %. 138 . 139 . Average delay threshold Two-way average delay threshold. Delay threshold Maximum two-way delay allowed in samples. Average delay variation threshold Two-way average delay variation threshold. Maximum delay variation Maximum two-way delay variation allowed. Delay variation threshold Two-way delay variation threshold in samples.9: Performance Assurance Agent PAA configuration Two-way Reference period Two-way reference period. Maximum delay Maximum two-way average delay. The following information is presented for each probe. Running: Running one time measurement. To enable it. Locked OOS: Locked traffic out of service. click the probe name and then select the PAA state checkbox. Probe name: Unique name assigned to the probe. CC: Continuity Check EPL: Excessive Packet Loss ODV: One-way Delay Variation OAV: One-way Average Delay Variation TD: Two-way Delay TAD: Two-way Average Delay TDV: Two-way Delay Variation TAV: Two-way Average Delay Variation Status codes 140 . • • • Index: A unique identifier assigned to the probe. Associating: Probe is looking for peer. Possible values are: • • • • • • • • • • • • • • • • Disabled: This probe is disabled. State: Indicates the probe's current state. Locked IS: Locked traffic in service. Associated: Peer was found. open the PAA > Status page.9: Performance Assurance Agent PAA status PAA status To view the status of all PAA probes. Click the name to view detailed status information. Idle: Idle after one time measurement completed. The following information is presented for the probe. 141 . Locked OOS: Locked traffic out of service. Click the name to view detailed status information. Locked IS: Locked traffic in service. To enable it. Alarms and status Indicates the state of each probe’s alarm. State: Indicates the probe's current state.9: Performance Assurance Agent PAA status Detailed PAA status Clicking a probe name on the PAA > Status page presents more detailed information on a probe. Idle: Idle after one time measurement completed. click the probe name and then select the PAA state checkbox. Possible values are: • • • • • • • Disabled: This probe is disabled. Associated: Peer was found. Index: A unique identifier assigned to the probe. • • • Probe name: Unique name assigned to the probe. Associating: Probe is looking for peer. Running: Running one time measurement. The following information is presented for each probe. PLFE: Packet Loss ratio Far-End. Locked IS: Locked traffic in service. Locked OOS: Locked traffic out of service. Idle: Idle after one time measurement completed. TADV: Two-way Average Delay Variation. To enable it. click the probe name and then select the PAA state checkbox. Running: Running one time measurement.9: Performance Assurance Agent PAA results PAA results To view the results of all PAA probes. 142 . • • • Index: A unique identifier assigned to the probe. Probe name: Unique name assigned to the probe. Associating: Probe is looking for peer. State: Indicates the probe's current state. PLNE: Packet Loss ratio Near-End. TAD: Two-way Average Delay. open the PAA > Results page. Click the name to view detailed results information. Associated: Peer was found. Possible values are: • • • • • • • • • • • • Disabled: This probe is disabled. OADV: One-way Average Delay Variation. 9: Performance Assurance Agent PAA results Detailed PAA results Clicking a probe name on the PAA > results page presents more detailed information. • • • Current results for probe: Unique name assigned to the probe. Index: A unique identifier assigned to the probe. State: Indicates the probe's current state. Possible values are: • • • • • • Disabled: This probe is disabled. To enable it, click the probe name and then select the PAA state checkbox. Associating: Probe is looking for peer. Associated: Peer was found. Running: Running one time measurement. Idle: Idle after one time measurement completed. Locked IS: Locked traffic in service. • Period: Interval at which measurement packets were issued. 143 9: Performance Assurance Agent PAA results Packet loss This section provides Packet loss statistics for the near-end probe and the far-end probe. • • Near End: Represents the statistics of a specific probe. Far End: Represents the statistics as seen by the peer probe. One-way delay variation Two-way delay variation • • • • • Instantaneous DV: Instantaneous delay variation value in microseconds. Minimum DV: Minimum delay variation in microseconds over one period. Maximum DV: Maximum delay variation in microseconds over one period. Average DV: Average delay variation in microseconds over one period. Nbr threshold exceeded: Number of times the threshold was exceeded. Two-way delay • • • • • Instantaneous delay: Instantaneous delay value in microseconds. Minimum delay: Minimum delay microseconds over one period. Maximum delay: Maximum delay microseconds over one period. Average delay: Average delay in microseconds over one period. Nbr threshold exceeded: Number of times the threshold was exceeded. 144 10: Command Line Interface Command summary Chapter 10: Command Line Interface 10 Command Line Interface Command summary Note: For a list of all CLI command descriptions, use the help command in the CLI. The CLI provides the following commands. Ethernet port commands • • • • • cable-test: Perform time domain reflectometry diagnostics. fault-propagation: Manage the link fault propagation between ports. media-selection: Select the ports' media type. port: Manage the link and physical level port settings. sfp: Display the SFP information, including digital diagnostics. User traffic/flow through commands • • • • • • bandwidth-regulator: Manage bandwidth regulator database. cos-profile: Manage class of service profiles for service mapping. filter: Manage the filter database. forwarding: Manage user traffic encapsulation. policy: Manage policy entries applied on ports. regulator-set: Manage bandwidth regulator sets for service mapping. System management commands • • • • • • • • • • • • console: Manage the serial (RS-232) console port. date: Print or set the system date and time. dns: Manage the DNS settings. interface: Manage the interfaces used to access the management plane. motd: Manage the MOTD of the unit. mtr: Manage management traffic regulation settings. ntp: Manage the network time client and server functions. permission-group: Manage the user privilege profiles. radius: Manage RADIUS authentication methods. route: Manage the IP routes and gateways. session: Manage the session settings or active sessions. snmp: Manage the SNMP agent settings. 145 version: Display cli version. 146 . syntax: Display the general command syntax.policies. (port. firmware: Install a new firmware or display current firmware version. quit: Terminate the current CLI session. equivalent to a power up boot. Miscellaneous commands • • • • • • board: Manage assembly and environmental information. OAM commands • • • • alarm: Manage the alarm settings. statistics: Clear all statistics. import or factory reset the device configuration. ping: Send pings to a specified host.3ah). paa: Manage the Performance Assurance Agent instances.OAM) traceroute: Display the hops used to reach a given host. reboot: Restart the device. oam: Manage the OAM instances (802.10: Command Line Interface Command summary • • syslog: Manage the remote syslog settings.regulators. exit: Terminate the current CLI session. user: Manage user account settings including privilege profile. loopback: Manage the loopback settings associated with an OAM instance. Utilities • • • • • • configuration: Export. help <command-name>: Display this help or for a specific given command. <string>[.<string>]+ .<0-255>.<attribute-value> [.<string> Getting help To get help on any CLI command type help command_name 147 .<string> .{a-z} [{a-z} | {0-9} | {\-}]* .<0-255>.{a-z | A-Z} [{a-z | A-Z |0-9 | : | ! | $ | % | ^ | & | \-}]* .{<string>/}+ .<0-255> .0{x | X}{0-9 | a-f | A-F } [0-9 | a-f | A-F]* .Optionally matches one in the set .<attribute-name> <attribute-value-list> <command> <attribute-specifier> <attribute-value_list> .<key-word> . type syntax to display the following information: Description: Display CLI syntax explanations.{"} <characters> [[ _ | <characters>]* <characters>] {"} .<decimal> | <hexadecimal> .Matches one in the set .Matches one in the range .Single space character .{<characters> | <quoted-string>} .<key-word> .<ip-addr>/[<path>]<file-name> .Repeat 1 or more times . Syntax: syntax Syntax metacharacters {} [] * + | \ _ <> .<0-FF>:<0-FF>:<0-FF>:<0-FF>:<0-FF>:<0-FF> .<command-name> <command-modifier>* [[<target>] <attribute-specifier>*] .<0-255>.Escape a metacharacter .Repeat 0 or more times .Separates options in a set .Syntax variable .<string> .10: Command Line Interface Command syntax Command syntax To see the syntax conventions used for all help commands. <attribute-value-list>] <command-name> <attribute-name> <attribute-value> <key-word> <string> <quoted-string> <characters> <number> <decimal> <hexadecimal> <ip-addr> <mac-addr> <url> <path> <file-name> <dns-name> <port-name> <connector-name> .{0-9}+ .{<key-word> | <number> | <string>} . 15 -> SFP-A transmit power high warning 2.06 -> SFP-A supply voltage low alarm 2.003.001.005.02 -> SFP-A temperature low alarm 2.001.001.001.001.Alarms Alarms Chapter 11: Appendix A .01 -> link down on Network port SFP module for Rx/Tx power.01 -> link down on Management port 1. • • • • • • • • • • • • • • • • • • • • 2.001.10 -> SFP-A laser bias current low alarm 2.Alarms 11 Alarms Appendix A .004. temp.001.001.001.14 -> SFP-A transmit power low alarm 2.Alarms The following alarms are supported: Port module for link down and others related alarms.01 -> link down on Monitor-2 port 1.11: Appendix A .01 -> link down on Monitor-1 port 1.001.05 -> SFP-A supply voltage high alarm 2. • • • • • 1.01 -> SFP-A temperature high alarm 2.12 -> SFP-A laser bias current low warning 2.16 -> SFP-A transmit power low warning 2. vcc and lbc alarms and warnings.03 -> SFP-A temperature high warning 2.001.17 -> SFP-A receive power high alarm 2.19 -> SFP-A receive power high warning 2.18 -> SFP-A receive power low alarm 2.001.07 -> SFP-A supply voltage high warning 2.20 -> SFP-A receive power low warning 148 .001.001.001.11 -> SFP-A laser bias current high warning 2.001.001.001.09 -> SFP-A laser bias current high alarm 2.001.13 -> SFP-A transmit power high alarm 2.001.001.01 -> link down on Client port 1.04 -> SFP-A temperature low warning 2.002.08 -> SFP-A supply voltage low warning 2. Alarms Alarms • • • • • • • • • • • • • • • • • • • • • • 2.002.002.03 -> SFP-B temperature high warning 2.002.002.17 -> SFP-B receive power high alarm 2.002.001.11 -> SFP-B laser bias current high warning 2.18 -> SFP-B receive power low alarm 2.002.12 -> SFP-B laser bias current low warning 2.07 -> SFP-B supply voltage high warning 2.002.002.13 -> SFP-B transmit power high alarm 2.06 -> SFP-B supply voltage low alarm 2.02 -> SFP-B temperature low alarm 2.15 -> SFP-B transmit power high warning 2.002.002.10 -> SFP-B laser bias current low alarm 2.002.11: Appendix A .002.01 -> SFP-B temperature high alarm 2.05 -> SFP-B supply voltage high alarm 2.002.002.19 -> SFP-B receive power high warning 2.002.002.09 -> SFP-B laser bias current high alarm 2.21 -> SFP-B not present 149 .002.002.002.20 -> SFP-B receive power low warning 2.04 -> SFP-B temperature low warning 2.16 -> SFP-B transmit power low warning 2.21 -> SFP-A not present 2.002.14 -> SFP-B transmit power low alarm 2.002.08 -> SFP-B supply voltage low warning 2. 10 -> <probe-name> PAA_TW_AVG_DV_ALERT Example: With only 1 PAA probe created.05 -> <probe-name> PAA_OW_DV_ALERT 3. power supplies and temperature sensors.11: Appendix A .04 -> Power supply on -48V feed A 8.05 -> Power supply on -48V feed B 150 .xxx.000.xxx.000.10 -> paa_probe_1 PAA_TW_AVG_DV_ALERT Environmental module for fans. these alarms will be created: 3.07 -> paa_probe_1 PAA_TW_DELAY_ALERT 3.06 -> <probe-name> PAA_OW_AVG_DV_ALERT 3.xxx.001.01 -> First overheat threshold 8.07 -> <probe-name> PAA_TW_DELAY_ALERT 3.02 -> paa_probe_1 PAA_PL_ALERT 3.000.000. called “paa_probe_1”.xxx. • • • • • 8.001.xxx.06 -> paa_probe_1 PAA_OW_AVG_DV_ALERT 3.09 -> <probe-name> PAA_TW_DV_ALERT 3. Note: These alarms are dynamically created based on the PAA probes configured.000.01 -> paa_probe_1 PAA_CC_ALERT 3.09 -> paa_probe_1 PAA_TW_DV_ALERT 3.03 -> Power supply +5V DC 8.xxx. xxx : PAA instance number <probe-name> : PAA probe name • • • • • • • • 3.01 -> <probe-name> PAA_CC_ALERT 3.xxx.001.02 -> <probe-name> PAA_PL_ALERT 3.05 -> paa_probe_1 PAA_OW_DV_ALERT 3.001.001.001.02 -> Second overheat threshold 8.001.xxx.001.08 -> <probe-name> PAA_TW_AVG_DELAY_ALERT 3.08 -> paa_probe_1 PAA_TW_AVG_DELAY_ALERT 3.Alarms Alarms EtherNID Performance Assurance Agent ™ alarms. MIB support 12 Appendix B . IF-MIB • ifXTable EtherLike-MIB • • • dot3StatsTable dot3PauseTable dot3HCStatsTable RMON-MIB • • • • etherStatsTable etherHistoryHighCapacityTable historyControlTable etherHistoryTable MAU-MIB • • ifJackTable ifMauAutoNegTable 151 .MIB support Public MIBs Chapter 12: Appendix B .MIB support Public MIBs The following public MIBs are supported: RFC-1213-MIB • • • system group interface group snmp group Note: Some groups have been removed for security reasons of the standard MIB-II.12: Appendix B . mib This MIB contains all the information about the bandwidth regulator configurations and statistics. The alarms are in SNMPv2 format and include the following fields. ACCEDIAN-SMI. Alarms format The alarm format is defined in the ACD-ALARM-MIB.mib This MIB contains the general setting of the alarm manager and the tables for alarm configuration and status.12: Appendix B . ACD-ALARM-MIB. ACD-DESC-MIB. ACD-REGULATOR-MIB. • • • • • acdAlarmCfgID acdAlarmCfgSeverity acdAlarmCfgDesc acdAlarmStatusLastChange acdAlarmCfgServiceAffecting 152 . ACD-SFP-MIB.mib This MIB contains all the information related to Accedian private tree and principal branches. information and environmental values and status.mib This MIB contains all the information related to the SFP present in the NID.MIB support Private MIBs Private MIBs The following private Accedian MIBs expose EtherNID configuration and status information. ACD-POLICY-MIB. ACD-PAA-MIB.mib This MIB contains the Layer 2 and IPV4 filter tables.mib This MIB contains all the information about PAA configurations and measurement results. ACD-FILTER-MIB.mib file.mib This MIB contains the policies configuration table and the counters table for policy entries.mib This MIB contains the NID description.