Accedian NID User Manual

152
1 EtherNID™ Administrator’s Guide for the EtherNID™ EE EtherNID™ OE EtherNID™ GE MetroNID™ TE EtherNID™ DE+

description

EtherNIDMetroNID

Transcript of Accedian NID User Manual

  • 1EtherNID

    Administrators Guidefor the

    EtherNID EEEtherNID OEEtherNID GEMetroNID TEEtherNID DE+

  • 2Release 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: Publications4878, Levy street, Suite 202Saint-Laurent, QubecCanadaH4R 2P1

    Tel: (514) 331-6181Fax: (514) 331-2210Toll 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.

  • 3Contents

    1Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6Introducing the EtherNID . . . . . . . . . . . . . . . . . . . 6

    Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . 7Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    Application scenario . . . . . . . . . . . . . . . . . . . . . . . 8

    2Hardware installation . . . . . . . . . . . . . . . . 9Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . 9

    Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Status lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

    Mounting options . . . . . . . . . . . . . . . . . . . . . . . . 15Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . 15Rack mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Powering the EtherNID . . . . . . . . . . . . . . . . . . . . 19

    Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

    Resetting to factory defaults . . . . . . . . . . . . . . . . 21

    3Management and configuration . . . . . . . 22About the management web interface . . . . . . . . 22

    Starting the management web interface . . . . . . . . . 22Managing web interface accounts . . . . . . . . . . . . . . 22

    DNS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    Configuring interfaces . . . . . . . . . . . . . . . . . . . . . 26Creating or editing an interface . . . . . . . . . . . . . . . . 26Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 27

    Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Adding a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Route parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 29

    Syslog options . . . . . . . . . . . . . . . . . . . . . . . . . . 30Syslog parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 30

    Setting the system date and time . . . . . . . . . . . . 31

    Timezone and Daylight saving . . . . . . . . . . . . . . 32

    SNMP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 33SNMP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 34

    History buckets . . . . . . . . . . . . . . . . . . . . . . . . . . 35Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Remote retrieval of history buckets . . . . . . . . . . . 36Scheduling and file transfer configuration . . . . . . . . 37

    Session management . . . . . . . . . . . . . . . . . . . . . 38Management parameters . . . . . . . . . . . . . . . . . . . . 38

    Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . 39

    Session configuration . . . . . . . . . . . . . . . . . . . . . 40Session parameters. . . . . . . . . . . . . . . . . . . . . . . . . 40

    Session management . . . . . . . . . . . . . . . . . . . . . 41Management parameters . . . . . . . . . . . . . . . . . . . . 41

    Session RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 42RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . 42

    Management bridge . . . . . . . . . . . . . . . . . . . . . . 44Configuration procedure . . . . . . . . . . . . . . . . . . . . . 44

    4Port configuration . . . . . . . . . . . . . . . . . .46Port list and port status . . . . . . . . . . . . . . . . . . . . 46

    Port configuration and status. . . . . . . . . . . . . . . . . . 49Port options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

    Configuring port settings . . . . . . . . . . . . . . . . . . . 51Port parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

    Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

    PHY auto-negotiation configuration . . . . . . . . . . . 55PHY parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . 57SFP information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57SFP thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59SFP memory and monitor memory . . . . . . . . . . . . . 61

    Cable verification . . . . . . . . . . . . . . . . . . . . . . . . . 62Testing a cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

  • 45Monitoring and filtering . . . . . . . . . . . . . 64Service mapping . . . . . . . . . . . . . . . . . . . . . . . . . 64

    Viewing CoS profiles . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring a CoS Profile . . . . . . . . . . . . . . . . . . . . 65CoS Profile parameters . . . . . . . . . . . . . . . . . . . . . . 65Assigning a CoS profile to a policy . . . . . . . . . . . . . 66Viewing Bandwidth regulator sets . . . . . . . . . . . . . . 67Configuring a Bandwidth regulator set . . . . . . . . . . . 67Bandwidth regulator set parameters . . . . . . . . . . . . 68Assigning a Bandwidth regulator set to a policy . . . 69

    Traffic forwarding . . . . . . . . . . . . . . . . . . . . . . . . 70Access policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Traffic filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Configuring traffic forwarding . . . . . . . . . . . . . . . . . . 71Forwarding parameters . . . . . . . . . . . . . . . . . . . . . . 71

    Traffic policies and monitoring . . . . . . . . . . . . . . 72Configuring a traffic policy on an EtherNID GE or Met-roNID TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Configuring a traffic policy on an EtherNID EE, OE or DE+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

    Traffic filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Viewing L2 filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring an L2 filter on an EtherNID GE or MetroNID TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80L2 filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . 80Configuring an L2 filter on an EtherNID EE, OE or DE+81L2 filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . 82Viewing IPv4 filters. . . . . . . . . . . . . . . . . . . . . . . . . . 83Configuring an IPv4 filter on an EtherNID GE or MetroN-ID TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84IPv4 filter parameters. . . . . . . . . . . . . . . . . . . . . . . . 85Configuring an IPv4 filter on an EtherNID EE, OE or DE+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86IPv4 filter parameters. . . . . . . . . . . . . . . . . . . . . . . . 87

    Bandwidth policing . . . . . . . . . . . . . . . . . . . . . . . 89Configuring a regulator . . . . . . . . . . . . . . . . . . . . . . 90Regulator settings . . . . . . . . . . . . . . . . . . . . . . . . . . 90Assigning a regulator to a policy . . . . . . . . . . . . . . . 91

    6Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Alarm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

    Alarm configuration . . . . . . . . . . . . . . . . . . . . . . . 93Customizing an alarm . . . . . . . . . . . . . . . . . . . . . . . 94

    Alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

    Chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    7Operations, Administration and Maintenance . . . . . . . . . . . . . . . . . . . . . . .98OAM configuration . . . . . . . . . . . . . . . . . . . . . . . . 98

    Configuring an OAM instance . . . . . . . . . . . . . . . . . 99OAM instance parameters. . . . . . . . . . . . . . . . . . . . 99

    Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Adding a loopback . . . . . . . . . . . . . . . . . . . . . . . . . 103Loopback parameters . . . . . . . . . . . . . . . . . . . . . . 103

    OAM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Transmitted and Received event notifications. . . . 106

    OAM status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Detailed status information . . . . . . . . . . . . . . . . . . 109

    OAM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 111OAM detailed statistics information . . . . . . . . . . . . 112

    8RFC-2544. . . . . . . . . . . . . . . . . . . . . . . . .117RFC-2544 flows . . . . . . . . . . . . . . . . . . . . . . . . . 117

    Viewing RFC-2544 Flows . . . . . . . . . . . . . . . . . . . 117Configuring RFC-2544 Flows . . . . . . . . . . . . . . . . 118

    RFC-2544 configuration . . . . . . . . . . . . . . . . . . 120Viewing RFC-2544 Configuration . . . . . . . . . . . . . 120

    RFC-2544 measurements . . . . . . . . . . . . . . . . . 122Viewing RFC-2544 Measurements . . . . . . . . . . . . 122Detailed view of RFC-2544 Measurements. . . . . . 123

    RFC-2544 testsuite . . . . . . . . . . . . . . . . . . . . . . 126Viewing RFC-2544 Testsuites . . . . . . . . . . . . . . . . 126Detailed view of RFC-2544 Testsuites . . . . . . . . . 127

    RFC-2544 reports . . . . . . . . . . . . . . . . . . . . . . . 131Starting an RFC-2544 Testsuite . . . . . . . . . . . . . . 131Viewing RFC-2544 Reports . . . . . . . . . . . . . . . . . . 132

  • 59Performance Assurance Agent . . . . . . 134PAA configuration . . . . . . . . . . . . . . . . . . . . . . . 134

    Configuring a probe . . . . . . . . . . . . . . . . . . . . . . . . 136PAA parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . 137

    PAA status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Detailed PAA status . . . . . . . . . . . . . . . . . . . . . . . . 141

    PAA results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Detailed PAA results . . . . . . . . . . . . . . . . . . . . . . . 143

    10Command Line Interface. . . . . . . . . . . . 145Command summary . . . . . . . . . . . . . . . . . . . . . 145

    Command syntax . . . . . . . . . . . . . . . . . . . . . . . 147

    11Appendix A - Alarms . . . . . . . . . . . . . . . 148Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

    12Appendix B - MIB support . . . . . . . . . . 151Public MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

    Private MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

  • 1: Introduction Introducing the EtherNID

    6

    Chapter 1: Introduction

    Introducing the EtherNID The growing demand for Ethernet Services is exploding everywhere. 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, Administration and Maintenance (OAM), to reduce operational expenses and minimize truck-roll.

    Offering Carrier-Grade Reliability.

    All of this while optimizing end-to-end Network Performance and keeping capital expenses at a minimum.

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

    By using the EtherNID's 802.3af standard Power over Ethernet (PoE), Accedian's EtherNID extends the reliability of the Carrier's Network all the way to the customer's IT closet, thus, avoiding dependency on end-customer's UPS.

    Installed in-line on the Ethernet media, the EtherNID implements a transparent fail-safe bypass, meeting the reliability objectives that carriers have come to expect from telecom demarcation units.

    Furthermore, Accedian's EtherNIDs unique Fast-Thru architecture minimizes packet-jitter and latency, two parameters critical in real-time applications such as Voice and Video over IP, especially when adding cascaded network devices.

    The EtherNID comes equipped with two Monitor Ports where external test equipment can be connected to perform non-intrusive troubleshooting, 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. Additionally, the EtherNID allows combining both signal directions on a single Monitor Access port by using a Port Mirroring function.

    The Performance Assurance Agent (PAA) allows measuring and tracking End-to-End SLA parameters such as Latency, Jitter, Packet Loss and Availability in a continuous manner, while the service is running.

    The EtherNID interacts seamlessly with Ethernet OAM compliant devices, comes with an embedded Web Server User Interface and can be optionally managed directly via SNMP.

    Designed cost effectively for volume deployment, the EtherNID allows for systematic installation on every customer Ethernet line and therefore obtaining a consistent look & feel across the network.

    1 Introduction

  • 1: Introduction Introducing the EtherNID

    7

    Features and benefits

    Ethernet OAM & loop-back Increases visibility, management and easier maintenance.

    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, (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.

    Extends the Network's OAM capabilities all the way to the customer's IT closet.

    Allows offering full NID power responsibility and reliability as a value-added SLA.

    Increases service reliability and availability.

    Reduces Carrier's operational expenses by reducing truck-roll.

    Eliminates finger pointing.

    Increases end-customer satisfaction.

    Applications Acts as an Ethernet OAM extension for Metro Access Platforms. Adds Ethernet OAM capability to legacy media-converters and Access Platforms.

    Sectionalizes Multi-Carrier E-lines.

    The EtherNIDs ultra-compact form factor also allows for high-density rackmount installation. Its fail-safe bypass architecture allows it to be used as a Modular Intelligent Ethernet Patch Panel, providing non-intrusive Monitor Access to each direction or combined access to both directions using port mirroring.

  • 1: Introduction Application scenario

    8

    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.

    About this scenario: Remote Management station is a computer that is used to remotely manage the

    EtherNID and to setup loopbacks. 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.0 or higher, or Microsoft Internet Explorer 6.0 or higher.

    Test equipment provides the test suite that is used to validate the link to the customer premises.

    Hub node provides network connectivity for the carrier site.

    Transport media provides connectivity between the carrier site and the customer premises.

    Access node provides network connectivity for one or more customer devices at a remote location.

    Local management station is the computer that is used to define initial configuration settings on the EtherNID when it is installed. This station can be eliminated if a DHCP server is available on the network. In this case the DHCP server can be configured to provide a specific IP address to the EtherNID based on its MAC address.

    Customer device is the customer-owned switch or router residing on the customers network.

    Demarcationpoint

    RemoteManagement

    Station

    Hub Node Transport Media Access Node EtherNIDTM Customer Device

    Networkport

    Clientport

    Test traffic

    Test traffic looped back

    Management port

    LocalManagement

    Station

    Customer SiteCarrier Site

    TestEquipment

    Remote SiteRemote Site

    Customertraffic

    Legend

    Test traffic

    Customer traffic

    Ethernet connection

  • 2: Hardware installation Hardware overview

    9

    Chapter 2: Hardware installation

    Hardware overview Front panel - EtherNID EE

    Front panel - EtherNID OE

    Front panel - EtherNID GE, DE+ and MetroNID TE

    Rear panel - All units

    2 Hardware installation

  • 2: Hardware installation Hardware overview

    10

    Front panel The front panel features different ports and status lights depending on the model.

    Ethernet portsAll Ethernet ports are 10/100/1000BaseT or 10/100BaseT Ethernet, depending on the model, supporting auto-negotiation, auto-MDIX and have RJ-45 connectors.

    Each port has two indicator lights as follows:

    SFP portsAll 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.

    Port functionalityThe following table lists the capabilities of each port.

    Light Solid FlashingLink/RX Port is connected at the link layer. Port is receiving data.

    TX N/A Port is transmitting data

    Model SFP RJ-45EE N/A 10Base-THD/TFD

    100Base-TX/TXHD/TXFD(Auto-negotiation/Auto MDIX)

    OE 100Base-BX10D/BX10U/FX/FXHD/FXFD/LX10

    10Base-THD/TFD

    100Base-TX/TXHD/TXFD(Auto-negotiation/Auto MDIX)

    GE / TE

    Fiber SFP

    100Base-BX10D/BX10U/FX/FXFD/LX101000Base-BX10D/BX10U/LX/LXFD/LX10/SX/SXFD/T/TFD(Auto-negotiation)

    Copper SFP10Base-TFD100Base-TX/TXFD1000Base-T/TFD(Auto-negotiation/Auto MDIX)

    10Base-THD/TFD

    100Base-TX/TXFD1000Base-T/TFD(Auto-negotiation/Auto MDIX)

  • 2: Hardware installation Hardware overview

    11

    The following describes the factory default configuration settings for all ports. Use the management web interface to change these settings as required by your installation.

    EtherNID EE Management: For connection of a local management station. By default, this port is set to

    the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH Client.

    Monitor 1: Configured for traffic monitoring.

    Monitor 2: Configured for traffic monitoring.

    RJ-45-A: 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. This is an Ethernet port that provides support for PoE (803.3af).

    EtherNID OE Management: For connection of a local management station. By default, this port is set to

    the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH Client.

    Monitor 1: Configured for traffic monitoring.

    Monitor 2: Configured for traffic monitoring.

    SFP-B: By default this port is configured for connection to the carrier network and is set to operate as a DHCP client.

    RJ-45-A: This port is configured for connection to the client network. This port supports PoE (803.3af).

    EtherNID GE / MetroNID TE SFP-A: By default, this port is configured for connection to the client network.

    Configuration can be changed using the management web interface.

    SFP-B: By default this port is configured for traffic monitoring.

    Management: For connection of a local management station. By default, this port is set to the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH Client.

    RJ-45-A: This port is configured for connection to the client network. This configuration can be changed using the management web interface.

    RJ-45-B: This port is configured for connection to the carrier network and is set to operate as a DHCP client. This is an Ethernet port that provides support for PoE (803.3af).

    DE+ Fiber SFP

    100Base-BX10D/BX10U/FX/FXFD/LX10(Auto-negotiation)

    Copper SFP10Base-TFD100Base-TX/TXFD(Auto-negotiation/Auto MDIX)

    10Base-THD/TFD

    100Base-TX/TXFD(Auto-negotiation/Auto MDIX)

  • 2: Hardware installation Hardware overview

    12

    EtherNID DE+ SFP-A: By default, this port is configured for connection to the carrier network-1.

    Configuration can be changed using the management web interface however this port must remain on NID-1.

    SFP-B: By default, this port is configured for connection to the carrier network-2. Configuration can be changed using the management web interface however this port must remain on NID-2.

    Management: For connection of a local management station. By default, this port is set to the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH Client.

    RJ-45-A: By default, this port is configured for connection to the client network-1. Configuration can be changed using the management web interface however this port must remain on NID-1.

    RJ-45-B: By default, this port is configured for connection to the client network-2. Configuration can be changed using the management web interface however this port must remain on NID-2.

  • 2: Hardware installation Hardware overview

    13

    Status lights PWR (green): On when power is applied. LPBK (yellow): On when the loopback function is enabled. Flashes when traffic is being

    looped-back.

    MIN (yellow): On when a minor alarm condition is present.

    MAJ (red): On when a major alarm condition is present.

    CRIT (red): On when a critical alarm condition is present.

    SFP (green):

    TX: Flashes when the port transmits data.

    Link/RX: Solid when the link level is present. Flashes when the port receives data.

    Rear panel The rear panels on all units are identical.

    Port/Connectors +/-40-57V---0.25A connector: For use with the EtherSHELF connectors or a discrete

    power cord (connector sold separately) providing +/-40 to +/-57 V DC.

    5V---2A connector: For use with the DC power adapter.

    Console: RJ-45 serial connection for access to the console interface. Pin-outs for both ends of the console cable are as follows:

    ConsoleRJ-45Cable

    8 1

    TERM

    INAL

    5

    1

    9

    6

    DB-9 Female

  • 2: Hardware installation Hardware overview

    14

    To establish a connection with the CLI interface on the EtherNID from your computer, 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.

    ButtonsThe Bypass and Loopback buttons are used to reset the EtherNID. See "Resetting to factory defaults" on page 21 for instructions.

    RJ-45 Connector DB-9 Connector

    Pins # Signals Pins # Signals

    1 Not connected

    2 Not connected

    3 Tx Data 2 Rx Data

    4 Ground 5 Ground

    5 Ground 5 Ground

    6 Rx Data 3 Tx Data

    7 Not connected

    8 Not connected

  • 2: Hardware installation Mounting options

    15

    Mounting options Several different mounting options are available as described in this section.

    Wall mounting Optional brackets and screws are available for mounting the EtherNID on a wall. Attach the brackets as follows:

    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.4 pounds)

    cable pull (accidental or otherwise) does not make the unit exceed the 2 kg (4.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.

    Mountingbracket

    ScrewScrew

  • 2: Hardware installation Mounting options

    16

    Rack mounting To install the EtherNID in a standard 19 rack, attach the optional 1U rack mount bracket as shown.

    An optional 1U bracket is available that can hold two units.

    Grounding the EtherNIDConnect the EtherNID to a ground point on the rack as follows:

    1. Turn OFF power to the unit. However, to channel ESD voltages to ground, do not unplug the power cable. Remove all network interface cables.

    Warning: Before proceeding to the next step, ensure that power is removed from the DC circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that services the DC circuit, switch the circuit breaker to the OFF position, and then tape the switch handle of the circuit breaker in the OFF position.

    2. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).

    3. Crimp the ground lug around the exposed wire.

    4. 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, 3/16 stainless steel screw with an oversized washer.

    5. Connect the other end of the wire to a grounding point on the rack.

  • 2: Hardware installation Mounting options

    17

    EtherSHELFThe EtherSHELF, an optional 12 unit, 4U shelf is available for large-scale installations.

    To mount an EtherNID in the EtherSHELF, L-shaped brackets must be attached to the left and right side of the unit.

    Grounding the EtherSHELFConnect the EtherSHELF to a ground point on the rack as follows:

    1. Turn OFF power to the shelf. However, to channel ESD voltages to ground, do not unplug the power cable. Remove all network interface cables.

    Warning: Before proceeding to the next step, ensure that power is removed from the DC circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that services the DC circuit, switch the circuit breaker to the OFF position, and then tape the switch handle of the circuit breaker in the OFF position.

    2. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).

    3. Crimp the two-hole grounding lug around the exposed wire.

    Attach brackets before mounting in the drawer.

  • 2: Hardware installation Mounting options

    18

    4. 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. Connect the other end of the wire to a grounding point on the rack.

  • 2: Hardware installation Powering the EtherNID

    19

    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.3af-compliant power injector.

    DC power adapterConnect the supplied power adapter to the 5V/2A DC connector on the rear of the unit.

    48V DC from the 12 unit EtherSHELFYou can power EtherNIDs mounted in the EtherSHELF using the shelfs built-in 48 V DC power connector. Slide the EtherNID into the shelf to engage the power connector on the rear of the unit.

    The EtherSHELFs power feed must be limited with a 5A/48V fuse. Voltage must be in the range +/-40 to +/-57 V DC using AWG 14 gauge or larger cable.

    48V DC from the Terminal Block AdapterIn a 1U rack mount bracket installation, it is sometimes preferable to use 48V DC power through directly secured wires as opposed to the DC power adapter.The Terminal Block Adapter fastens to the back of the EtherNID to provide such an installation.

    To ground the Terminal Block Adapter, use a small wrench to tighten the bolt around the grounding screw, located at the bottom right on the back of the Terminal Block Adapter, to secure the grounding lug.

  • 2: Hardware installation Powering the EtherNID

    20

    48V DC via discrete power cordIt is possible to power units with a custom built 48V DC power cable. When powered in this manner, the unit must be installed horizontally to meet all applicable safety regulations. Therefore, supported mounting options are desktop mounting or 1 or 2 unit rack mounting. Wall mounting is not allowed.

    On older models of the EtherNID, the +/- 48V Return is common to both Feed A and Feed B, whereas other models will have an isolated Return A and Return B.

    To locate your serial number, please refer to the sticker on the Rear Panel of the unit. If the serial number starts with: I006- or less then the unit has a common +/- 48V Return P004- or less then the unit has a common +/- 48V Return I007- or more then the unit has an isolated +/- 48V Return A and Return B P005- or more then the unit has an isolated +/- 48V Return A and Return B

    The following diagram depicts the pin-out of the white +/- 48V connector on therear panel of the EtherNID:

    Common +/- 48V Return Isolated +/- 48V Return A and B

    If an EtherNID with a Common +/- 48V Return is being used with the Terminal Block Adapter, then the two +/- 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.25A/48V slow blow fuse or equivalent (Little fuse 0217.250 0.25A). There should be one fuse per power feed.

    Warning: Disconnect all power sources (feed A and feed B) when servicing. Removing fuses can be used as a disconnect method.

    Warning: Fuses must be installed on the live wire(s) and not on the grounded wire(s).

  • 2: Hardware installation Restarting

    21

    Restarting To restart the EtherNID:

    1. Press and hold the Bypass button.

    2. Press and release the Loopback button. The unit will restart.

    3. Release the Bypass button.

    If required, the EtherNID can also be restarted using the command line interface. See Chapter 10 for details.

    Resetting to factory defaults To reset the EtherNID to factory default settings:

    1. Press and hold the Bypass button.

    2. Press and release the Loopback button.

    3. Continue to press the Bypass button until the following lights all flash at the same time:

    Minor

    Major

    Critical

    Power

    4. Release the Bypass button.

  • 3: Management and configuration About the management web interface

    22

    Chapter 3: Management and configuration

    About the management web interface The web-based management web interface provides secure access, via an SSL client, to all EtherNID control, management, and monitoring functions.

    The management station is the computer that you use to connect to the management web interface. To act as a management station, a computer must:

    have a JavaScript-enabled Web browser installed (Firefox 1.0 or higher, or Internet Explorer 6.0 or higher).

    be able to establish an IP connection with the EtherNID

    Starting the management web interface

    To start the management interface, do the following:

    1. Use an Ethernet cable to connect the LAN port on a computer to the management port on the front of the EtherNID.

    2. Configure the computer with the static IP address 192.168.1.2.

    3. Connect the power adaptor or use PoE (802.3af) to power-up the EtherNID.

    4. Start your Web browser and specify the following in the address box: https://192.168.1.254 and press Enter.

    5. The EtherNID login page opens. Login as admin with the Password admin.

    Managing web interface accounts

    One administrator account is created by default with username and password both set to admin. The username and password are case-sensitive. It is recommended that you change the default password immediately after installation to safeguard the system. The administrator account provides access to all EtherNID features.

    3 Management and configuration

  • 3: Management and configuration About the management web interface

    23

    Managing accountsAdministrator accounts are managed on the Session > Users page.

    Changing the default administrator password1. Open the Session > Users page and click admin in the list.

    2. Specify the new password, confirm it.

    3. Click Apply.

    Lost administrator passwordIf 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

    24

    Creating additional accounts1. Open the Session > Users page and click Add.

    2. In the new user setting box, specify the new user name and other details.

    3. Click Apply.

  • 3: Management and configuration DNS settings

    25

    DNS settings To define DNS options, open the System > DNS page. You can either choose to use the DNS settings obtained via DHCP on a specific port, or manually set DNS settings.

    Use DHCP results

    Set DNS manually

    In either case, you can define the host name for the EtherNID.

    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 Configuring interfaces

    26

    Configuring interfaces The EtherNID lets you define multiple logical interfaces for management purposes that can be active on different ports. This includes defining bridges and VLANs.

    To see a list of all logical interfaces. Open the System > Interface page.

    By default, two interfaces are defined:

    Management: This is the default interface that enables access to the management web interface via the management port. If you modify this interface you may lose access to the management web interface.

    Network: This is the default interface active on the network port.

    Creating or editing an interface

    To create or edit an interface, do the following:

    1. Open the System > Interface page.

    2. Click the Add button to add a new interface, or click the name of an existing interface to edit its settings. For example, if you click the Management interface you will see:

    Note: Different fields will appear depending on the selections you make for Interface type.

    3. Define interface parameters as required by your setup and then click Apply.

  • 3: Management and configuration Configuring interfaces

    27

    Interface parameters

    Note: It is valid to set the IP address for an interface to 0.0.0.0 when the interface is not required to be an IP interface. For example, when the interface is used for OAM or test set interaction.

    Interface nameSpecify a name to identify the interface.

    Interface typeSets the interface type to use. Select one of the following options:

    Standard: Standard IP interface associated with a single port.

    Bridge: Bridged interface than connects two or more ports.

    VLAN: VLAN interface associated with a single port.

    VLANinVLAN: VLAN in VLAN (.1q in .1q) interface associated with a single port.

    On port(s)Select the port the interface will be active on. In the case of a bridge, select multiple ports by holding down the control key when you click on port names in the list.

    VLAN ID (Only available when Interface type is set to VLAN or VLANinVLAN.)

    Specify the VLAN ID (Management VLAN) to assign to the interface.

    Ethertype (Only available when Interface type is set to VLANinVLAN.) Specify the Ethertypes for the first and second VLAN IDs. Valid Ethertypes are: 0x8100 (C-VLAN) and/or 0x88A8 (S-VLAN).

    Automatic IP (DHCP)Select this option to have the interface act as a DHCP client and automatically obtain its IP address, DNS server, and gateway settings from a DHCP server.

    Use DHCP route informationIf the DHCP server has routing information, it will be applied to the EtherNID.

    Manual configurationSelect this option to manually configure IP addressing settings.

    IP address: Specify an IP address to assign to the interface.

    Network mask: Specify the network mask associated with the IP address.

    Gateway address: Specify a default gateway address. This provides a shortcut alternative, to route configuration, to create a default gateway.

  • 3: Management and configuration Routes

    28

    Routes Select System > Interface to open the routes pages, which shows all active routes on the EtherNID. Initially, no routes are defined.

    Adding a route To add a system route, do the following:1. Open the System > Routes page.

    2. Click the Add button in the Routes box.

    3. Define route parameters as required by your setup and then click Apply.

  • 3: Management and configuration Routes

    29

    Route parameters NameSpecify the name to assign to the route.

    TypeSelect a route type:

    Network

    Host

    InterfaceSelect the interface to which the route is associated. Note: This field is optional if a matching active route is already associated to the interface.

    DestinationNetwork or host address of the route. Use 0.0.0.0 for default.

    Network maskSpecify the mask to assign to the route. Only used for routes of type Network.

    GatewaySpecify the gateway associated with this route.

  • 3: Management and configuration Syslog options

    30

    Syslog options To define syslog options, open the System > Syslog page. The syslog page displays all syslog entries with the most recent entry at the top.

    Syslog information can be sent to a remote server by setting the options in the Remote Syslog Configuration box. Configure these options as required and then click Apply.

    Syslog parameters

    Facility configurationDevice facility All messages are logged using this user defined facility instead of the default ones.

    Level configurationLevel threshold Log all messages with level equal to or above the selected one in the drop down list. For example, If CRITICAL level is selected, then all messages with level CRITICAL, ALERT or EMERGENCY will be logged.

    Remote syslog configurationRemote syslog enable Enables the sending of messages to a remote syslog server.

    Host Specify the IP address or domain name of the remote syslog server.

  • 3: Management and configuration Setting the system date and time

    31

    Setting the system date and time To set the system date and time, do the following:

    1. Open the System > Time page.

    2. Specify the current date and time and click Apply or to automatically update the system date and time using the Network Time protocol, select the NTP enable option. The following options will be displayed:

    3. Select a time server from the list. To add a new server, specify its name or IP address in the Added Server box and then click add. Then select the new server in the list and click Apply.

    4. The EtherNID can also act as an NTP server by selecting the NTP server enable option.

  • 3: Management and configuration Timezone and Daylight saving

    32

    Timezone and Daylight saving For a list of time zones and daylight saving time rules, please refer to: http://www.worldtimezone.com/.

    GMT offsetOffset from Greenwich Mean Time. North America would have negative values while Eastern Europe would have positive values.

    Daylight saving enableFor regions of the world implementing Daylight saving time, this can be enabled.

    Beware that syslog and other services that timestamp events using the current date and time will be affected during transitions of DST periods. There will possibly be an hour gap or duplicate time stamps because the clock was set back.

    Daylight saving offsetTime correction to apply to GMT offset during the Dailight saving period. Most of the time it will be one hour.

    DST start and DST endPeriod where daylight saving time is in effect.

    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, use week=5

    Examples:Montreal, Quebec, Canada time:GMT offset=-5, DST enable=check, DST offset=1DST start: Month=March, Week=2, Day=Sunday, Hour=2, Min=0DST end: Month=November, Week=1, Day=Sunday, Hour=2, Min=0

    Wellington, New ZealandGMT offset=12, DST enable=check, DST offset=1,DST start: Month=September, Week=5, Day=Sunday, Hour=2, Min=0DST end: Month=April, Week=1, Day=Sunday, Hour=3, Min=0

  • 3: Management and configuration SNMP settings

    33

    SNMP settings To configure SNMP options, do the following:

    1. Open the System > SNMP page.

    2. Define SNMP parameters as required by your setup and then click Apply.

  • 3: Management and configuration SNMP settings

    34

    SNMP parameters Enable agentSelect this checkbox to enable the SNMP agent.

    SNMP system nameSpecify a name to identify the EtherNID. By convention, this is the node's fully-qualified domain name.

    Contact informationSpecify contact information for the EtherNID. Generally an email address.

    System locationIdentify the physical location of the EtherNID.

    Agent UDP portSpecify the UDP port the SNMP agent uses for all IPv4 interfaces.

    Read-only communitySpecify the community string to control read-only access to the EtherNID.

    Read-write communitySpecify the community string to control read/write access to the EtherNID.

    Enable trap hostEnable these options to have the unit send SNMPv1 or SNMPv2c traps to the specified management host(s).

    Community stringSpecify the community string required to send traps to the management host(s).

    Management hostSpecify the IP address or host name of the device that will receive SNMP traps (and/or inform notifications). The EtherNID sends a Cold Start trap when it starts up.

    UDP portSpecify the UDP port that the EtherNID will use to send traps to the management host(s). By default, the well-known SNMP trap port (162) is used.

    Note: For a list of Public and Private supported MIBs, see Appendix B.

  • 3: Management and configuration History buckets

    35

    History buckets To configure local history bucketing, do the following:

    1. Open the System > History page.

    2. Define the history parameters as required and then click Apply.

    Local Configuration

    Enable history This will start the creation of history files being stored in RAM. These will then be accessible through SNMP.

    Enable filing This will enable the history files to be stored locally instead of storing this information in the RAM. 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. Unchecking this box will result in the existing history files for this feature to be removed locally.

    Period The frequency, in minutes, of storing the statistics history into files.

  • 3: Management and configuration Remote retrieval of history buckets

    36

    Remote retrieval of history buckets NOTE: The Remote retrieval feature is only available on the MetroNID TE models.

    To configure remote retrieval of history buckets, do the following:

    1. Open the System > History page on the remote NIDs.

    2. Ensure filing is enabled for the desired history buckets and then click Apply.

    3. Open the System > History page on the local MetroNID TE and add a new remote device. Then enable scheduling at the desired time slot(s) and provide the URL for the file transfer server.

  • 3: Management and configuration Remote retrieval of history buckets

    37

    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. The history buckets will be retrieved according to the Scheduled hours selected. (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.

    Example: If Enable scheduling is checked but the local device has not checked Enable filing, then only the remote history buckets will be retrieved.

    Example: If Enable scheduling is checked and the local device, as well as the remote device(s), have checked Enable filing, then both the local and remote history buckets will be retrieved.

    Server URL The full URL of the Server on which to send the history bucket files once retrieved.

    Examples:

    http://mypc.com

    ftp://username:[email protected]

    tftp://192.168.1.5

    NOTE: The status of the Remote devices can be obtained by clicking on the Remote device name in the Remote device configuration window.

  • 3: Management and configuration Session management

    38

    Session management To configure session management options, do the following:

    1. Open the Session > Management page.

    2. Define session management parameters as required by your setup and then click Apply.

    Management parameters

    Writelock sessionThe management web interface supports multiple concurrent users, therefore to maintain the integrity of the configuration settings, 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.

    Writeunlock: Click this button to unlock the configuration so someone else can make changes.

    Current sessionsLists all sessions currently logged into the EtherNID.

    Session IDUnique number that identifies a session. Automatically generated by the EtherNID.

    TypeIndicates which interface the session is using.

    UsernameIdentifies the user account that is logged in. An asterisk (*) next to the username indicates the username of the session that is viewing this web page.

    UptimeIndicates how long the session has been active.

    WritelockIndicates which session has the ability to make configuration changes.

    TerminateSelect one or more sessions and then click the Terminate button to force a log out.

  • 3: Management and configuration Firmware upgrade

    39

    Firmware upgrade To upgrade the EtherNID firmware, do the following:

    1. Open the System > Firmware page.

    2. Specify the location and name of the new firmware file or click Browse and select it.

    3. Click Upload.

    4. Once the firmware has been uploaded the unit will restart.

  • 3: Management and configuration Session configuration

    40

    Session configuration To configure session options, do the following:

    1. Open the Session > Configuration page.

    2. Define session parameters as required by your setup and then click Apply.

    Session parameters

    Max CLI sessionsSpecify the maximum number of CLI sessions that are supported at the same time.

    Max WEB sessionsSpecify the maximum number of management tool sessions that are supported at the same time.

    Max total sessionsSpecify the total number of CLI and WEB sessions that are supported at the same time.

    CLI timeoutSpecify the maximum number of seconds that a CLI session can remain idle before it is automatically logged out.

    WEB timeoutSpecify the maximum number of seconds that a management tool session can remain idle before it is automatically logged out.

    AuthenticationOrderAuthentication method to use in order of availability. Refer to RADIUS configuration page for server configuration instructions. This parameter is described in the RADIUS section below on page 35.

  • 3: Management and configuration Session management

    41

    Session management To configure session management options, do the following:

    1. Open the Session > Management page.

    2. Define session management parameters as required by your setup and then click Apply.

    Management parameters

    Writelock sessionThe management web interface supports multiple concurrent users, therefore to maintain the integrity of the configuration settings, 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.

    Writeunlock: Click this button to unlock the configuration so someone else can make changes.

    Current sessionsLists all sessions currently logged into the EtherNID.

    Session IDUnique number that identifies a session. Automatically generated by the EtherNID.

    TypeIndicates which interface the session is using.

    UsernameIdentifies the user account that is logged in. An asterisk (*) next to the username indicates the username of the session that is viewing this web page.

    UptimeIndicates how long the session has been active.

    WritelockIndicates which session has the ability to make configuration changes.

    TerminateSelect one or more sessions and then click the Terminate button to force a log out.

  • 3: Management and configuration Session RADIUS

    42

    Session RADIUS To configure RADIUS authentication, do the following:

    1. Open the Session > RADIUS page.

    2. Define RADIUS parameters as required by your setup and then click Apply.

    RADIUS parameters

    Authentication methodAuthentication method to use. 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. After the num-ber of retries has been exhausted, a connection to the next configured server will be attempted, in which the same timeout and retry scheme will apply.

    RADIUS retry Number of times to retry the server before trying the next server configured.

    Realm A string to append to the user's name using the "username@realm" method.

  • 3: Management and configuration Session RADIUS

    43

    Server-1 / Server-2 Host RADIUS server host-name or IPV4 address.

    Port RADIUS server UDP port to connect to.

    Secret Shared secret for this RADIUS server.

    Radius server configuration When RADIUS authentication is enabled, the unit supports Authentication and Authorization as configured on the RADIUS server. The RADIUS Callback-Id (id=20) attribute is used to provide the Authorization (permissions) info to the unit. If the attribute is not configured then the permissions will be set to viewer only.

    The permissions are the same as those that can be configured locally on the unit. It is a space or coma separated list of tokens. They can be a mix of either locally defined user permission groups or individial privileges.

    Notes:- RADIUS assigned permissions cannot be viewed with the CLI or web based interface.- The permissions tokens are case sensitive.

    Configuration examples

    Callback-Id = "Admin"A userid member of the built-in Admin group.

    Callback-Id = "Config Firmware Log Management, Users"A list of individual privileges.

  • 3: Management and configuration Management bridge

    44

    Management bridge This section describes how to set up a bridged management port using the command line interface.

    A minimum of two EtherNIDs are required for this setup. An out-of-band EtherNID management port will be used to manage the other EtherNIDs, in-band through a bridged interface. This is useful when the core transport devices do not need to be connected to the internal private management network. Instead, 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. Power on EtherNID #1 with factory default settings.

    2. Connect your computer to serial port on the back of the EtherNID.

    3. 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. Login to the CLI with username admin and password admin.

    5. If an EtherNID GE is being used, and the setup requires the Client and Network ports to be set as copper medium, type the following command:

    media-selection select RJ45-A_RJ45-B

  • 3: Management and configuration Management bridge

    45

    6. Delete any existing interfaces with the following commands:

    interface delete Management

    interface delete Network

    7. The Network port of EtherNID #1 will be used for the in-band management. Configure the Network port with the following command:

    interface add net1-10 type vlan 10 port Network address 192.168.1.253 netmask 255.255.255.0

    8. Repeat configuration steps 1. to 7. on EtherNID #3 using the following settings when defining the new interface:

    interface add net3-10 type vlan 10 port Network address 192.168.1.252 netmask 255.255.255.0

    9. Repeat configuration steps 1. to 6. on EtherNID #2.

    10. 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. The other two interfaces will be used to access the other two EtherNIDs remotely.

    11. Next, create the bridge interface. Execute the following command to bridge all three interfaces together for access using the Management port.

    interface add Bridge type bridge sub-intf mgmt,cli10,net10 address 192.168.1.254 netmask 255.255.255.0

    12. Connect the Management port of EtherNID #2 to the private network.

    13. Open a web browser on a computer connected to the private network and enter the address 192.168.1.254 to reach the management web interface on EtherNID #2.

    14. Connect the Client port of EtherNID #2 to the Network port of EtherNID #3.

    15. Connect the Network port of EtherNID #2 to the Network port of EtherNID #1.

    16. Open a web browser and enter the address 192.168.1.254 to reach the management web interface on EtherNID #2.

    17. Open a second web browser and enter the address 192.168.1.253 to reach the management web interface on EtherNID #1.

    18. Open a third web browser and enter the address 192.168.1.252 to reach the management web interface on EtherNID #3.

  • 4: Port configuration Port list and port status

    46

    Chapter 4: Port configuration

    Port list and port status To view a list of all ports and their status, open the Port > Configuration page.

    You will see the following page on an EtherNID EE:

    4 Port configuration

  • 4: Port configuration Port list and port status

    47

    You will see the following page on an EtherNID OE:

  • 4: Port configuration Port list and port status

    48

    You will see the following page on an EtherNID GE or MetroNID TE:

  • 4: Port configuration Port list and port status

    49

    You will see the following page on an EtherNID DE+:

    Port configuration and status

    StatusIndicates the status of the port.

    Green: The port is up and running.

    Red: The port is enabled but the physical link is down.

    Yellow: The port is not totally functional.

    Grey: The port is disabled.

    ConnectorIdentifies the physical connector the port is using.

    Port nameIdentifies the logical name assigned to the port.

    Port stateIndicates if the port is enabled (ready to connect) or disabled.

  • 4: Port configuration Port list and port status

    50

    SpeedIndicates the current port speed and duplex type. If set to Auto-nego the EtherNID automatically negotiates port speed and duplex type with the device it is connected to. For this to work the device must also be configured to support auto-negotiation.

    MAC addressIndicates the MAC address of the port.

    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. 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, all the associations between connectors and ports will be reflected in the Port configuration and status table.

    The two other connectors on the device will be monitor ports. When used as monitor ports, connectors RJ45-A and SFP-A are mapped to port Monitor-1, and RJ45-B and SFP-B are mapped to port Monitor-2.

    For example: By default, SFP-A with RJ-45-B (PoE) is selected. This denotes Traffic-A is connected to the SFP-A connector and Traffic-B is connected to the RJ-45-B connector

    Fault propagationEnable fault propagationSelect this check box to enable fault propagation. When this feature is enabled the EtherNID will propagate link faults between the Client and Network ports.

    Propagate fault on portSelect the port that the EtherNID will use for fault propagation. 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.

    Network: If the EtherNID detects a link down condition on the Client port it will also bring down the Network port.

    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.

  • 4: Port configuration Configuring port settings

    51

    Configuring port settings To configure port settings, do the following:

    1. Open the Port > Configuration page.

    2. Click the name of the port that you want to configure. The port configuration page will open.

    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. Define port parameters as required by your setup and then click Apply.

  • 4: Port configuration Configuring port settings

    52

    Port parameters Port enableSelect this check box to enable the port.

    Port nameSpecify a name to identify the port. By default, ports are named as follows: Management, Client, Network, Monitor-1 and Monitor-2.

    AliasThis is an 'alias' name for the port as specified by a network manager.

    Port MTUSpecify the maximum transmission unit. By default, this is set to 1522. Example range: 1518 to 10240.

    Note that this range is platform dependant.

    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.

    If this option is disabled, then:

    For 1000BASE-X links, a Remote Fault Indicator using auto-negotiation advertisement is sent to the link partner.

    For 100BASE-FX links, the FEFI idle pattern is sent to the link partner.

    If this option is enabled, then the EtherNID turns off its transmitter for the amount of time defined by LLR period, after which it is re-enabled. This cycle is repeated until the link is re-established. Entering a value of 0, puts the laser into a disabled state waiting for the opposite side to send a light pulse in order to re-establish the link. So for this reason, 0 should not be configured on both sides or the link will never re-establish.

    Link speed(copper ports only)

    Sets port speed and duplex type.

    Select Auto-negotiation enable to have the EtherNID automatically negotiate port speed and duplex type with the device it is connected to. For this to work the device must also be configured to support auto-negotiation.

    If you do not select Auto-negotiation enable, you can manually define port speed and duplex type using the available options.

    Note: Auto-negotiation is mandatory for 1000BASE-T.

    Flow controlSelect how pause frames are processed by setting the Pause mode option to local, transparent or disabled.

    When this option is set to local or transparent and the Auto-negotiation option is also enabled under Link speed, the exact behavior depends on the auto-negotiation result.

  • 4: Port configuration Configuring port settings

    53

    Current statusReports 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. A cross-over cable present on the cabling plant will result in both partners using the same connector configuration.

    ConnectorIdentifies the physical connector associated with the port.

    MAC addressIdentifies the MAC address of the port.

    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.

    If you do not select Auto MDI Enable, you can manually define port settings as follows:

    MDI: Typical setting for an Ethernet station. Link partner must be set to MDIX or a cross-over cable must be used.

    MDIX: Typical setting for an Ethernet switch. Link partner must be set to MDI or a cross-over cable must be used.

  • 4: Port configuration Port statistics

    54

    Port statistics To view port statistics, do the following:

    1. Open the Port > Statistics page.

    2. Click the name of a port to view detailed statistics. For example, if you click the Management port on an EtherNID GE or MetroNID TE you will see a page similar to the following:

  • 4: Port configuration PHY auto-negotiation configuration

    55

    PHY auto-negotiation configuration To configure PHY auto-negotiation settings, do the following:

    1. Open the Port > PHY page.

    2. Click the name of a port that you want to configure. For example, if you click the Client port name you will see the following page.

    3. Define PHY parameters as required by your setup and then click Apply.

    Note: Advertised parameters are checked and parameters that are not configurable are greyed-out based on the capabilities of the port.

  • 4: Port configuration PHY auto-negotiation configuration

    56

    PHY parameters Advertisement configurationSets the abilities that are advertised to the link partner. Supported options include:

    10Mbps Half

    100Mbps Half

    1Gbps Half

    10Mbps Full

    100Mbps Full

    1Gbps Full

    Pause Symmetric

    Pause Asymmetric

    Link Partner AbilityLists the abilities of the link partner.

    10Mbps Half

    100Mbps Half

    1Gbps Half

    10Mbps Full

    100Mbps Full

    1Gbps Full

    Pause Symmetric

    Pause Asymmetric

    StateThe state field corresponds to ifMauAutoNegConfig and ifMauAutoNegRemoteSignaling from RFC3636.

    The state disabled indicates that auto-negotiation is not supported by the media or disabled by configuration.

  • 4: Port configuration SFP information

    57

    SFP information (Supported only on the EtherNID OE / GE / MetroNID TE)

    To view SFP information, do the following:

    1. Open the Port > SFP page.

    2. Click the name of the port for which you want to view detailed statistics. Refer to the following sections for more information.

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

    SFP informationConnector TypeIndicates the external optical or electrical cable connector provided as the media interface.

    VendorIndicates the vendor name. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h).

  • 4: Port configuration SFP information

    58

    Wave LengthIndicates the nominal transmitter output wavelength at room temperature in nm.

    Part numberIndicates the vendor part number or product name. This is a 16-byte field that contains ASCII characters padded on the right with ASCII spaces (20h).

    Serial numberIndicates the vendor serial number for the transceiver. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h).

    RevisionIndicates the vendors product revision. This is a 16 character field that contains ASCII characters padded on the right with ASCII spaces (20h).

    SFP presentIndicates the presence of a recognized SFP.

    DiagnosticsIf bit 6 is set, address 92 is set indicating that digital diagnostic monitoring has been implemented, received power monitoring, transmitted power monitoring, bias current monitoring, supply voltage monitoring and temperature monitoring will all be displayed.

    CalibrationThe values in this field are interpreted differently depending upon the option bits set at address 92.

    Internal: If bit 5 is set, the values are calibrated to absolute measurements, which should be interpreted according to the convention Internal Calibration.

    External: If bit 4 is set, the values are A/D counts, which are converted into real units per the convention External Calibration.

    ThresholdsAdditionally, alarm and warning thresholds must be written as specified in this document at locations 00 55 on 2 wire serial address 1010001X (A2h).

    Monitoring informationTemperatureInternally measured transceiver temperature. Temperature accuracy is vendor specific but must be better than 3 degrees Celsius over specified operating temperature and voltage.

    Laser bias currentMeasured 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. Data is not valid when the transmitter is disabled.

    Transmit powerMeasured 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. Data is not valid when the transmitter is disabled.

  • 4: Port configuration SFP information

    59

    Receive powerMeasured received optical power. Absolute accuracy is dependent upon the exact optical wavelength. For the vendor specified wavelength, accuracy should be better than 3dB over specified temperature and voltage.This accuracy should be maintained for input power levels up to the lesser of maximum transmitted or maximum received optical power per the appropriate standard. It should be maintained down to the minimum transmitted power minus cable plant loss (insertion loss or passive loss) per the appropriate standard. Absolute accuracy beyond this minimum required received input optical power range is vendor specific.

    Supply voltageInternally measured transceiver supply voltage. Note that in some transceivers, transmitter supply voltage and receiver supply voltage are isolated. In that case, only one supply is monitored. Refer to the device specification for more detail.

    SFP thresholds

    TemperatureHigh alarmHigh Alarm transceiver temperature.

    Low alarmLow Alarm transceiver temperature.

    High warningHigh Warning transceiver temperature.

    Low warningLow Warning transceiver temperature.

  • 4: Port configuration SFP information

    60

    VccHigh alarmHigh Alarm transceiver supply voltage.

    Low alarmLow Alarm transceiver supply voltage.

    High warningHigh Warning transceiver supply voltage.

    Low warningLow Warning transceiver supply voltage.

    Laser bias current High alarmHigh Alarm TX bias current in micro-Amps.

    Low alarmLow Alarm TX bias current in micro-Amps.

    High warningHigh Warning TX bias current in micro-Amps.

    Low warningLow Warning TX bias current in micro-Amps.

    Tx powerHigh alarmHigh Alarm TX output power in dBm (~ -40 to +8.2 dBm).

    Low alarmLow Alarm TX output power in dBm (~ -40 to +8.2 dBm).

    High warningHigh Warning TX output power in dBm (~ -40 to +8.2 dBm).

    Low warningLow Warning TX output power in dBm (~ -40 to +8.2 dBm).

    Rx power High alarmHigh Alarm Rx input power in dBm (~ -40 to +8.2 dBm).

    Low alarmLow Alarm Rx input power in dBm (~ -40 to +8.2 dBm).

  • 4: Port configuration SFP information

    61

    High warningHigh Warning Rx input power in dBm (~ -40 to +8.2 dBm).

    Low warningLow Warning Rx input power in dBm (~ -40 to +8.2 dBm).

    SFP memory and monitor memory

    SFP memoryThe SFP serial ID provides access to sophisticated identification information that describes the transceivers capabilities, standard interfaces, manufacturer, and other information. Refer to INF-8074 for detailed descriptions of the individual data fields.

  • 4: Port configuration Cable verification

    62

    Cable verification The EtherNID uses Time Domain Reflectometry (TDR) to determine the quality of cables, connectors, and terminations. Some of the possible problems that the EtherNID can diagnose are: opens, shorts, cable impedance mismatch, bad connectors, and termination mismatch.

    Testing a cable To perform a cable test, do the following:1. Open the Port > Cable page.

    2. Click the name the connector you want to test. For example, if you click RJ45-B you will see the following page.

    3. Click Perform Test.

    4. The status of each channel is updated as the tests are run.

  • 4: Port configuration Cable verification

    63

    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.

  • 5: Monitoring and filtering Service mapping

    64

    Chapter 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 con-formance 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.

    IndexCoS profile's unique identifier.

    5 Monitoring and filtering

  • 5: Monitoring and filtering Service mapping

    65

    NameCoS profile's name as defined in the configuration page. Click this name for more details.

    TypeCoS profile's type. Possible values are:

    PCP

    IP precedence

    DSCP

    Reference countThe 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

    NameName of the CoS profile.

  • 5: Monitoring and filtering Service mapping

    66

    TypeIndicates the type of CoS profile. Possible values are:

    PCP

    IP precedence

    DSCP

    Decode DEIThis 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 DEIThis 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 tableThe 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 colorThe 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.

  • 5: Monitoring and filtering Service mapping

    67

    Viewing Bandwidth regulator sets

    To view a list of configured Bandwidth regulator sets, open the Traffic > Mapping page.

    IndexBandwidth regulator set's unique identifier.

    NameBandwidth regulator set's name as defined in the configuration page. Click this name for more details.

    TypeBandwidth regulator set's type. Possible values are:

    PCP

    IP precedence

    DSCP

    Reference countThe reference count is the number of policies that are currently using this Bandwidth regulator set.

    Configuring a Bandwidth regulator set

    Once a Bandwidth regulator set is created, it can be applied to policies for traffic classification.To configure a Bandwidth regulator set, do the following:

    1. Open the Traffic > Mapping page.

    2. Click Add in the Bandwidth regulator sets section, or click a regulator set name to edit and existing one.

    3. Configure Bandwidth regulator set parameters and click Apply.

  • 5: Monitoring and filtering Service mapping

    68

    Bandwidth regulator set parameters

    NameName of the Bandwidth regulator set.

    TypeIndicates the type of Bandwidth regulator set. 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.

    Regulator setThis table has three columns and N rows, where N depends on the type of the regulator set. If the type is PCP or IP precedence then N=8. Otherwise, the regulator set type is DSCP and N=64. Each row in this table allows assigning a traffic regulator to a specific PCP/IP precedence/DSCP > value.

    PCP/IP precedence/DSCP [IN]PCP/IP precedence/DSCP input value.

    Bandwidth regulatorThe bandwidth regulator that will be used to regulate the traffic flow that has this PCP/IP precendence/DSCP value.

  • 5: Monitoring and filtering Service mapping

    69

    Enable regulatorEnable or disable traffic regulation for this PCP, 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. See "Traffic policies and monitoring" on page 72.

  • 5: Monitoring and filtering Traffic forwarding

    70

    Traffic forwarding NOTE: The description below for Traffic forwarding is only available on the EtherNID EE, OE and DE+ models. For GE and MetroNID TE models, see the Service mapping section above.

    Access policies The EtherNID uses access policies to control the monitoring and filtering of traffic on the Client and Network ports. Up to eight access policies can be configured for Client and Network ports. 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

    To set up an access policy, you must:

    Define a traffic filter (if you are not going to use a default filter)

    Define an access policy.

    There are two sets of policies: Traffic A policies and Traffic B policies.

    Traffic A policies apply to connectors labeled A.

    Traffic B policies apply to connectors labeled B.

    Monitoring The EtherNID has two external connectors through which traffic can be monitored: Monitor-1 and Monitor-2.

    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.

    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.

    The EtherNID provides VLAN support, permitting either the Network or Client port to be connected to a VLAN trunk.

  • 5: Monitoring and filtering Traffic forwarding

    71

    Configuring traffic forwarding

    To configure traffic forwarding, do the following:

    1. Open the Traffic > Forwarding page.

    2. Define parameters as required by your setup and then click Apply.

    Forwarding parameters

    Enable VLAN encapsulationSelect this check box to enable VLAN support.

    Enable P-Bits preservationSelect 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.

    Note: If the incoming traffic is not already tagged with a VLAN, then this option has no effect and the VLAN priority on outgoing traffic will be taken from the Forwarding options specified.

    Trunk portSelect the port to which the VLAN trunk is connected.

    VLAN prioritySpecify the VLAN priority. Allows you to provide QoS prioritization by using the standard based 802.1Q priority tag. Possible values are 0 to 7. Interpretation is based on the carriers equipment and administrative policies

    VLAN CFISpecify the Canonical Format Indicator. This should always be set to zero for connection to Ethernet switches. CFI is used for compatibility reasons between Ethernet type networks and Token Ring type networks. If a frame received at an Ethernet port has a CFI set to 1, then that frame should not be forwarded as is to an untagged port.

    VLAN IDSpecify the VLAN ID that will be used to encapsulate all traffic forwarded to the port.

  • 5: Monitoring and filtering Traffic policies and monitoring

    72

    Traffic policies and monitoring To view a list of all traffic policies and their settings, open the Traffic > Policies page.

    This page shows the access policy rules that are enabled for a specific port. For example, if the Network port is selected then this is the list of policy rules that are enabled or disabled for the Network port.

    Access policy rules are ordered by their priority. When rules are applied they are processed from the top down and the first suitable rule that is found is applied.

    Note: The *default filter is a factory default rule that forwards all traffic. A rule, such as this is required to have traffic forwarded.

    Note: The following information is presented for each policy:

    Entry: Indicates the position of the rule in the access list.

    State: Indicates if the policy is enabled or disabled. Disabled policies are skipped when the rules are applied to incoming data.

    Action: Indicates the action that the policy applies to data that it matches.

    Filter name: Indicates the name of the filter assigned to the policy.

    Packets good: The number of good packets that matched the policy. A good packet is an error-free frame that has a length between 64 bytes and the maximum frame length.

    Bytes good: This is the total number of bytes in good packets that matched the policy.

    Packets bad: The number of bad packets that matched the policy. A bad packet is a packet that has a valid framing but contains an error within the packet, has a bad CRC or either shorter than 64 bytes or longer than the maximum frame length.

  • 5: Monitoring and filtering Traffic policies and monitoring

    73

    Configuring a traffic policy on an EtherNID GE or MetroNID TE

    To configure a traffic policy, do the following:

    1. Open the Traffic > Policies page.

    2. Click the policy entry that you want to configure.

    3. Configure policy settings and click Apply.

    Policy settings Enable policy Select this check box to activate the policy.

    Filter type Select the filter type that will be used to capture traffic. The filter type is either a Layer 2 or IPv4 filter.

    L2 filter / IPv4 filter The list shows all available filters.

    To define a new filter, open the Port > L2 Filters/IPv4 Filters page. By default, a catchAll fil-ter is defined. This enables you to monitor all traffic on a port.

  • 5: Monitoring and filtering Traffic policies and monitoring

    74

    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.

    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.

    Parameter First choice Second choice

    Type IP Precedence / DSCP N/A

    CoS profile CoS profile N/A

    BWR set Optional N/A

  • 5: Monitoring and filtering Traffic policies and monitoring

    75

    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.

    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.

    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.

    Parameter First choice Second choice

    Type N/A N/A

    CoS profile N/A N/A

    BWR set N/A N/A