Zhone etherxtend 3300 series User Manual
  1. Manuals
  2. Brands
  3. Zhone Manuals
  4. Wireless Access Point
  5. EtherXtend 3300 Series
  6. User manual
Zhone etherxtend 3300 series User Manual

Zhone etherxtend 3300 series User Manual

Hide thumbs Also See for etherxtend 3300 series:
Table of Contents

Advertisement

Quick Links

Download this manual
EtherXtend 3300 Series User's Guide
For software version 1.14.2
June 2008
Document Part Number: 830-01613-06

Advertisement

Table of Contents
loading

Related Manuals for Zhone etherxtend 3300 series

Summary of Contents for Zhone etherxtend 3300 series

  • Page 1 EtherXtend 3300 Series User’s Guide For software version 1.14.2 June 2008 Document Part Number: 830-01613-06...
  • Page 2 Further, Zhone Technologies reserves the right to revise this publication and to make changes from time to time in the contents hereof without obligation of Zhone Technologies to notify any person of such revision or changes.

  • Page 3: Table Of Contents

    ONTENTS About This Guide ..........................7 Style and notation conventions................7 Typographical conventions..................7 Acronyms........................8 Related documents ....................9 Contacting Global Service and Support...............9 Technical support....................10 Service requirements....................10 Chapter 1 Overview ........................11 Product models......................12 Product description ....................12 Technology description ..................13 EFM media ........................14 Ethernet services......................15 Chapter 2 Safety, Regulations, and Certifications ............17...
  • Page 4 Chapter 3 Features and Capabilities ..................25 Ethernet in the first mile (EFM) overview............25 2BASE-TL........................25 Zhone EFM features....................26 PME aggregation ....................26 Loop bonding ......................27 EtherXtend bonding implementation ..............28 One Ethernet port mapped to one SHDSL port ............28 One Ethernet port mapped to an SHDSL bonded group.........29 Ethernet ports mapped to different SHDSL bonded groups ........29...
  • Page 5 EtherXtend auto-provisioning................49 Customize the EtherXtend default settings............53 System settings ......................55 System security .......................56 Changing the default user password..............56 Radius support ......................57 System logging......................60 Device interface ......................61 LAN interfaces to CPEs ..................61 Moving PC cables on Ethernet ports ..............62 Configure an interface on an Ethernet port............62 IP on a bridge......................65 Chapter 7 EtherXtend SHDSL WAN Interfaces...
  • Page 6 Contents Tagged and s-tagged bridging examples..............93 Bridge profile ......................94 Q-in-Q VLAN tagging ....................96 Advanced bridging configurations ..............97 Packet-rule records (Option 82, Forbid OUI, DHCP relay) ........98 VLAN ID stripandInsert parameter ..............100 Broadcast suppression...................101 Bridge with DHCP relay..................102 COS in bridges ......................104 Verifying bridge settings ..................105 EtherXtend CO and CPE mode bridge scenarios ..........107 Bridges on EtherXtend CPE mode ..............107...
  • Page 7 Display OAM statistics ..................127 Show the OAM profile ...................127 Chapter 10 IP Service Level Agreement ................131 Overview ........................131 IPSLA .........................131 EtherXtend User’s Guide...
  • Page 8 Contents EtherXtend User’s Guide...

  • Page 9: About This Guide

    BOUT UIDE This guide is intended for use by EtherXtend users and administrators. EtherXtend users should have a fundamental knowledge of DSL protocols, Ethernet, and IP concepts. Refer to the EtherXtend Quick Start Guide for hardware installation and connection information. Style and notation conventions The following conventions are used in this document to alert users to information that is instructional, warns of potential damage to system...

  • Page 10: Acronyms

    About This Guide Bold Used for names of buttons, dialog boxes, icons, menus, profiles when placed in body text, and property pages (or sheets). Also used for commands, options, parameters in body text, and user input in body text. Used in code examples for computer output, file names, path Fixed names, and the contents of online files or directories.

  • Page 11: Related Documents

    EtherXtend Release Notes Contacting Global Service and Support Contact Global Service and Support (GSS) if you have any questions about this or other Zhone products. Before contacting GSS, make sure you have the following information: • Zhone product you are using •...

  • Page 12: Technical Support

    Service requirements If the product malfunctions, all repairs must be performed by the manufacturer or a Zhone-authorized agent. It is the responsibility of users requiring service to report the need for service to GSS. EtherXtend User’s Guide...

  • Page 13: Chapter 1 Overview

    VERVIEW The EtherXtend devices are next-generation Ethernet-enabled customer premises equipment (CPE). EtherXtend provides 4-port and 8-port models that perform the functions of a network extender by lengthening the reach of Ethernet packets. EtherXtend allows Ethernet packets to pass over existing copper wires that link the service provider (a central office, street cabinet, pole, or tower) to a subscriber’s CPE.

  • Page 14: Product Models

    (ETHX-SHDSL-4 and ETHX-SHDSL-8) deliver bonded high-speed EFM services over SHDSL. The ETHX-SHDSL-x device family provides 802.3ah compliant SHDSL bonding with advanced features, including Zhone’s Multimedia Traffic Management (MTM). In addition, full compliance to 802.3ah industry standards provide high reliability, low latency, and integrated operation, administration, and maintenance (OAM) features for advanced management of Ethernet lines.

  • Page 15: Technology Description

    EtherXtend provides dual-mode operations to allow EtherXtend to aggregate into standards-based products such as the MALC broadband loop carrier, and other EtherXtend-SHDSL-x units. EtherXtend can also connect into pre-standard Ethernet loop bonding products such as Zhone’s Ethernet access products. Technology description EFM provides high performance for data traveling across a connection between the subscriber and the service provider.

  • Page 16: Efm Media

    20 Mbps of bandwidth. Loop bonding is an easy way to increase line speeds where extra copper is available. Zhone’s EtherXtend technology uses existing copper facilities to deliver high bandwidth Ethernet services over existing copper loops to business customers.

  • Page 17: Ethernet Services

    Ethernet services • Frame Relay migration to E-LAN services • T1/E1 replacement with E-Line services, including internet access, wireless backhaul, voice access, and wholesale services. • Transparent LAN service (TLS) EFM over copper technology supports a wide range of voice, data, and video services and applications.
  • Page 18 Overview EtherXtend User’s Guide...

  • Page 19: Safety, Regulations, And Certifications

    AFETY EGULATIONS ERTIFICATIONS This chapter describes how to prepare your site for the installation of the EtherXtend platform. It includes the following topics: • Grounding and isolation, page 17 • Installation safety precautions on page 17 • EMI notices, page 20 •...

  • Page 20: Important Safety Instructions

    Safety, Regulations, and CertificationsSafety, Regulations, and Certifications Do not block system air vents; this will deprive the system of the airflow required for proper cooling. Sufficient clearance must exist on all sides of the rack to permit equipment access. Connect the system to the power supply circuit as described in this document.
  • Page 21 The 48 VDC source is to be reliably connected to earth. Ground by attaching an earthing ground wire to the Sem Screw Zhone P/N 150-00071-01 (8-32 x 1/2 split lock steel screw) provided on the rear panel of the chassis next to the earth ground symbol.

  • Page 22: Emi Notices

    The authority to operate this equipment is conditioned by the requirements that no modifications will be made to the equipment unless the changes or modifications are expressly approved by Zhone Technologies, Inc. If the equipment includes a ferrite choke or chokes, they must be installed as described in the installation instructions.
  • Page 23 For additional information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or Zhone Technologies worldwide office locations, contact Global Service and Support. If the equipment is causing harm to the telephone network, the telephone company may request that you disconnect the equipment until the problem is resolved.

  • Page 24: Supplier's Declaration Of Conformity

    Largo, FL 33773-1502 Date of Issue: July 10, 2006 Zhone Technologies, located at the above address, hereby certifies that the Model ETHX-SHDSL-X (where X = 4 or 8 denoting the total number of WAN ports) bearing labeling identification number US:6RTDLNANETHX complies with: the Federal Communications Commission’s (“FCC”) Rules...

  • Page 25: Notice To Users Of The Canadian Telephone Network

    World Wide Web site at www.zhone.com. Contacting Global Service and Support Contact Global Service and Support (GSS) if you have any questions about this or other Zhone products. Before contacting GSS, make sure you have the following information: • Software version running on the system •...

  • Page 26: Service Requirements

    Service requirements If the product malfunctions, all repairs must be performed by the manufacturer or a Zhone-authorized agent. It is the responsibility of users requiring service to report the need for service to GSS. EtherXtend User’s Guide...

  • Page 27: Features And Capabilities

    EATURES AND APABILITIES Zhone EtherXtend provides EFM functionality for use in subscriber access networks. EtherXtend products have a series of features to deliver performance enhancements such as bonding and aggregation to the networks. This chapter provides: • Ethernet in the first mile (EFM) overview, page 25 •...

  • Page 28: Zhone Efm Features

    PCM modulator/demodulator. The PMD sublayer then passes electrical signals across a single pair of voice grade copper lines. Zhone EFM features Zhone’s EtherXtend equipment adds enhancements to the EFM standard. Some of these enhancements are: • PME aggregation on page 26 •...

  • Page 29: Loop Bonding

    Zhone EFM features Loop bonding Ethernet loop bonding refers to a technology where multiple physical SHDSL lines are grouped together to provide greater bandwidth potential over a single logical connection. The WAN connection terminates into a single Ethernet connection, providing a single connection to the end user.

  • Page 30: Etherxtend Bonding Implementation

    Features and Capabilities EtherXtend bonding implementation The following sections detail various implementations of EtherXtend. The following implementations are provided. • One Ethernet port mapped to one SHDSL port on page 28 • One Ethernet port mapped to an SHDSL bonded group on page 29 •...

  • Page 31: One Ethernet Port Mapped To An Shdsl Bonded Group

    EtherXtend bonding implementation configuration. Instead of an Ethernet to T1 conversion, this approach would allow native Ethernet throughout the network. One Ethernet port mapped to an SHDSL bonded group This configuration increases the speed of the WAN link. This configuration applies to the same scenarios as the instance where one Ethernet port is mapped to one SHDSL port.

  • Page 32: Multiple Ethernet Ports Mapped To Multiple Shdsl Ports

    Features and Capabilities from each company would be separated. A better solution could be to use just two units. Then the data is physically as well as logically separated. Multiple Ethernet ports mapped to multiple SHDSL ports This configuration allows multiple PCs to connect to the EAD eliminating the need for an additional router or switch for multiple users.

  • Page 33: Endpoint-To-Endpoint Cpes

    Scenarios • CO mode with subtened devices, page 32 Endpoint-to-endpoint CPEs The basic scenario is a pair of EtherXtend devices acting as endpoints. This pairing is where an explicit endpoint is directly connected to another explicit endpoint. This topology is known as back-to-back mode. The following figure details this.

  • Page 34: Co Mode With Subtened Devices

    Features and Capabilities Figure 6: Multiple endpoints connecting to multiple SHDSL cards on a MALC Subscriber cluster #1 MALC 719 populated with SHDSL cards Endpoint #1 Endpoint #2 Endpoint #3 Subscriber cluster #3 Subscriber Cluster #1 Subscriber cluster #2 CO mode with subtened devices In this scenario, one EtherXtend device functions in CO as the aggregation point to the network, while other EtherXtend devices are subtended in various locations and connected to CPEs.

  • Page 35: Product Specifications

    Product specifications Product specifications The following are product specifications for the ETHX-SHDSL-4 and ETHX-SHDSL-8. Specifications for the ETHX-SHDSL-4 Table 5: ETHX-SHDSL-4 specifications Specification Type Specification Dimensions 1.75” (4.45 cm) High x 10” (21.6 cm) Wide x 7.5” (19.1 cm) Deep Weight 3.35 lbs (1.52 kg) Power...

  • Page 36: Specifications For The Ethx-Shdsl-8

    Features and Capabilities Specifications for the ETHX-SHDSL-8 Table 6: ETHX-SHDSL-8 specifications Specification Type Specification Dimensions 1.75” (4.45 cm) High x 10” (21.6 cm) Wide x 7.5” (19.1 cm) Deep Weight 3.35 lbs (1.52 kg) Power -48V DC and Universal AC power options available.

  • Page 37: Chapter 4 Installation Preparation

    NSTALLATION REPARATION This chapter describes how to prepare your site for the installation of the EtherXtend platform. It includes the following topics: • Tools you need, page 35 • Selecting the system location, page 35 • Environmental specifications, page 36 •...

  • Page 38: Environmental Specifications

    Installation Preparation Install the system in reasonable proximity to all equipment with which it will connect. Ensure that proper cable grades are used for all system and network connections. For best results, use the cables and connectors recommended in this document. Environmental specifications Table 8 describes the EtherXtend chassis environmental specifications and...

  • Page 39: Etherxtend Installation

    THER TEND NSTALLATION This chapter explains how to install the EtherXtend hardware. It includes the following sections: • Unpacking the system, page 37 • Port and LED descriptions, page 38 • Connect the power supply, page 40 • Connect the WAN SHDSL lines, page 41 •...

  • Page 40: Port And Led Descriptions

    EtherXtend rear panel ports The following graphic shows where the ports are located. Figure 8: Location of rear panel ports ALARM 48VDC SERIAL 0.5 A RTN -48 POWER ZHONE TECHNOLOGIES, INC MODEL: ETHERXTEND Power Alarm Serial WAN (EFM) 10/100 LAN connector contact...

  • Page 41: Led States For The Etherxtend

    Port and LED descriptions The following table describes the both the system and port LEDs that appear on EtherXtend. The LED port lights are located on the port. Figure 9: LEDs on the EtherXtend Device LED states for the EtherXtend The state of the LEDs show how the device is operating.

  • Page 42: Connect The Power Supply

    EtherXtend Installation Table 11: LED states on the EtherXtend (Continued) Solid/Blinking Meaning of the LED Color LAN (10/ green The port operates in 10BASE-T 100) (right mode where it transmits and receives side) packets at 10Mbps. The port operates in 100BASE-T mode where it transmits and received packets at 100Mbps.

  • Page 43: Connect The Wan Shdsl Lines

    Connect the WAN SHDSL lines Connect the WAN SHDSL lines An important feature of the EtherXtend device is the loop bonding capability among all four SHDSL ports. However, both the provider and the subscriber units can function with a single SHDSL connection as follows: •...
  • Page 44 EtherXtend Installation For the best connection results, the remote device should be set to autonegotiate speed and duplex mode as well. If the remote device cannot be configured to autonegotiate, speed may be hard set at either 10 Mbps or 100 Mbps.
  • Page 45 Connect the WAN SHDSL lines zSH> show ether autonegstatus:----> enabled disabled mauType:----------> mauother mau10baset mau10basethd mau10basetfd mau100basetxhd mau100basetxfd mau1000baselxhd mau1000baselxfd mau1000basesxhd mau1000basesxfd mau1000basethd mau1000basetfd restart:----------> restart norestart ifType:-----------> mauother mau10baset mau10basethd mau10basetfd mau100basetxhd mau100basetxfd mau1000baselxhd mau1000baselxfd mau1000basesxhd mau1000basesxfd mau1000basethd mau1000basetfd autonegcap:------->...

  • Page 46: Ground The Device

    EtherXtend Installation Ground the device When the AC plug is used, but not grounded it is recommended to ground the device using minimum 16-guage wire to a building or earth ground. The ground screw is located on the far-right on the back of the device. EtherXtend User’s Guide...

  • Page 47: Chapter 6 Basic Configuration

    ASIC ONFIGURATION This chapter covers basic configuration of the EtherXtend: • Device management, page 45 • EtherXtend auto-provisioning, page 49 • Customize the EtherXtend default settings, page 53 • System settings, page 55 • Device interface, page 61 • LAN interfaces to CPEs, page 61 •...

  • Page 48: Etherxtend Local Management Interface

    Autonegotiating Enabled Bonding Mode Login admin Password zhone DHCP Client (WAN) Enabled EtherXtend local management interface The EtherXtend unit provides an out-of-band RS232 D serial (craft) interface to manage the unit locally. To access the serial port, configure the terminal interface software with the following settings: •...
  • Page 49 Device management management interface is built on the default N2N bond group, 1-1-1-bondgroupnumber/n2nbond, as a DHCP client using VLAN 7. Managing EtherXtend using the default management interface The MALC that connects to the EtherXtend can be configured as a local DCHP server or as a client with a bridge to an external DHCP server.
  • Page 50 Basic Configuration Managing EtherXtend using a non-default management interface To manage the EtherXtend through an interface different than the default AutoConfig address, delete the default AutoConfigIP address and then add the desired interface. If the new IP address is not compatible with the address of the management PC, the connection to the device will be lost.

  • Page 51: Etherxtend Auto-Provisioning

    EtherXtend auto-provisioning zSH> interface show 1 interface Interface Status Rd/Address Media/Dest Address IfName --------------------------------------------------------------------------- 1/1/4/0/ip 1 172.24.200.133/24 00:01:47:07:ef:ee AutoConfig --------------------------------------------------------------------------- Creating a default route The following example creates a default route using the gateway 192.168.8.1 with a cost of 1 (one): route add default 192.168.8.1 1 Verifying the route To verify that the routes were added, tenter route show:...
  • Page 52 EtherXtend default settings on page To verify the version of the software running on an EtherXtend enter swversion: zSH> swversion Zhone ethXShdsl software version ETHX 1.14.2.119 To view the auto-provisioned configuration, enter bridge show: zSH> bridge show Type VLAN Bridge...
  • Page 53 EtherXtend auto-provisioning 7 1-1-3-0-eth/bridge tls Tagged 1-1-3-0-eth-0/bridge 7 1-1-2-0-eth/bridge tls Tagged 1-1-2-0-eth-0/bridge zSH> To view the bond group and the members of the bond group, enter bond show group interface/type: zSH> bond show group 1-1-99-0/efmbond Bond Groups Slot GrpId Name Type State 1-1-99-0...
  • Page 54 Basic Configuration pointtopoint: ----------------> {no} mcastenabled: ----------------> {yes} ipfwdenabled: ----------------> {yes} mcastfwdenabled: -------------> {yes} natenabled: ------------------> {no} bcastenabled: ----------------> {yes} ingressPacketRuleGroupIndex: -> egressPacketRuleGroupIndex: --> ipaddrdynamic: ---------------> {dhcpclient} dhcpserverenable: ------------> {false} subnetgroup: -----------------> unnumberedindex: -------------> mcastcontrollist: ------------> vlanid: ----------------------> maxVideoStreams: -------------> tosOption: ------------------->...

  • Page 55: Customize The Etherxtend Default Settings

    Customize the EtherXtend default settings Customize the EtherXtend default settings When installing EtherXtend software for the first time with auto-provisioning, auto-provisioning creates default bridges and configures the IP interface. (For a description of EtherXtend auto-provisioning, see EtherXtend auto-provisioning on page 49).
  • Page 56 The destination directory and filename is always /onreboot/default. Reboot the EtherXtend and let it completely finish the reboot process. Note: The EtherXtend does not use auto-provisioning or Zhone’s factory defaults whenever you place a file named default in the onreboot directory.

  • Page 57: System Settings

    System settings alarm-config (1) bridge-interface-record (4) dhcp-client-lease-resource (3) dhcp-client-resource (1) dhcp-server-options (1) dsl-alarm (4) dsl-config (4) efm-port (4) ether-oam (1) info-reconcile (9) ip-interface-record (2) ipsla-cos-act (8) ipsla-cos-map (64) ipsla-global (1) ntp-client-config (1) pat-bind (1) pme-profile (4) rip-global-config (1) rip-if-config (2) system (1) user-profile (2) if-stack (22)

  • Page 58: System Security

    Tip: The system automatically logs you out after a period of inactivity. The default logout time is 10 minutes, but can be changed with the timeout command. Refer to the Zhone CLI Reference Guide for information on the timeout command.

  • Page 59: Radius Support

    System settings Radius support The EtherXtend supports local and RADIUS (Remote Authentication Dial In User Service) access authentication. The EtherXtend can be configured for local authentication, RADIUS authentication, or RADIUS then local authentication. RADIUS users are configured with the Service-Type attribute as Administrative-User or NAS-Prompt-User.
  • Page 60 Note: Before beginning this procedure, ensure that the EtherXtend has IP connectivity to the RADIUS server. Update the RADIUS server with settings for the Zhone prompts. Create a radius-client profile on the EtherXtend with the desired index number and RADIUS settings for server name, shared secret, number of retries, and other parameters.
  • Page 61 System settings ....Save new record? [s]ave, [c]hange or [q]uit: s Record created. Another method to reference the RADIUS server is by specifying the IP address. This example specifies the radius-client 1/1 with server IP address 172.24.36.148 and a shared-secret of secret. The index 1/1 specifies that this profile is the first profile in group 1.

  • Page 62: System Logging

    For users logging in through RADIUS, the system prompt appears as the username@systemname. For example, the system prompt for a basic user on a EtherXtend using the default Zhone EtherXtend system name will appear as basicuser@Zhone EtherXtend. The system name is configured using the sysname parameter in the System 0 profile.

  • Page 63: Device Interface

    Device interface Enabling and disabling logging By default logging is enabled on the serial craft port and disabled over telnet sessions. To enable or disable logging for the session, enter: zSh> log session on | off The log session command only applies to the current session. You can also enable or disable logging for all serial craft port sessions enter: zSh>...

  • Page 64: Moving Pc Cables On Ethernet Ports

    Basic Configuration A profile is available for each Ethernet LAN interface to configure Ethernet parameters. Use the following command to configure the Ethernet LAN port settings. This example changes the pauseFlowControl setting to symmetric. zSH> update ether 1-1-1-0/eth ether 1-1-1-0/eth Please provide the following: [q]uit.
  • Page 65 Configure an interface on an Ethernet port Table 15: Interface Parameters (Continued) Parameter Description netmask The subnet mask associated with the IP interface. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.
  • Page 66 Basic Configuration tosOption: ---------> {disable}: tosCOS: ------------> {0}: vlanCOS: -----------> {0}: s-tagTPID: ---------> {0x8100}: s-tagId: -----------> {0}: s-tagIdCOS: --------> {0}: ....Save new record? [s]ave, [c]hange or [q]uit: s This IP Interface has been automatically bound to 1-1-4-0-eth New record saved. To verify that the Ethernet interface has been set up, enter interface show: zSH>...

  • Page 67: Ip On A Bridge

    Configure an interface on an Ethernet port IP on a bridge IP on a bridge allows you to put an IP address on a bridged VLAN. This allows VLANs to be used to manage multiple EtherXtends or other devices. One IP on a bridge can be created on a EtherXtend. The following example provides a typical example of how you would configure IP on a bridge.
  • Page 68 Basic Configuration zSH> bridge add 1-1-99-0/efmbond tls vlan 200 tagged Adding bridge on 1-1-99-0/efmbond Created bridge-interface-record 1-1-99-0-efmbond-200/bridge The uplink connection is now reachable from the upstream, and IP 10.11.12.13/24 can reach other upstream devices on the same VLAN. Enter bridge show to verify the IP on a bridge and the upstream connection bridge on VLAN 200: zSH>...
  • Page 69 Configure an interface on an Ethernet port Verify that the bridges are deleted with bridge show: zSH> bridge show Type VLAN Bridge Table Data --------------------------------------------------------------------------------- 7 1-1-99-0-efmbond/bridge tls Tagged 1-1-99-0-efmbond-0/bridge 7 1-1-1-0-eth/bridge tls Tagged 1-1-1-0-eth-0/bridge 7 1-1-4-0-eth/bridge tls Tagged 1-1-4-0-eth-0/bridge 7 1-1-3-0-eth/bridge tls Tagged 1-1-3-0-eth-0/bridge...
  • Page 70 Basic Configuration EtherXtend User’s Guide...

  • Page 71: Etherxtend Shdsl Wan Interfaces

    SHDSL WAN I THER TEND NTERFACES This chapter describes the WAN SHDSL interfaces on the EtherXtend. • WAN SHDSL interfaces, page 69 • EtherXtend EFM 802.3ah bonding, page 76 • Bond group/physical line stats, page 78 WAN SHDSL interfaces The EtherXtend device can have either 4 or 8 SHDSL WAN interfaces for use as individual interfaces or as members of a bond group.
  • Page 72 EtherXtend SHDSL WAN Interfaces 8 entries found. To display the PME parameters in their default state, enter get pme-profile: zSH> get pme-profile 1-1-1-0/shdsl pme-profile 1-1-1-0/shdsl efmCuPmeAdminSubType: -----------> {ieee2basetlr} efmCuPmeAdminProfile: -----------> efmCuPAFRemoteDiscoveryCode: ----> efmCuPmeThreshLineAtn: ----------> efmCuPmeThreshSnrMgn: -----------> efmCuPmeLineAtnCrossingEnable: --> {false} efmCuPmeSnrMgnCrossingEnable: ---> {false} efmCuPmeDeviceFaultEnable: ------>...

  • Page 73: Setting Dsl Profile Settings

    WAN SHDSL interfaces To change pme-profile values, enter update pme-profile interface/type: zSH> update pme-profile 1-1-3-0/shdsl pme-profile 1-1-3-0/shdsl Please provide the following: [q]uit. efmCuPmeAdminSubType: -----------> {ieee2basetlr}: efmCuPmeAdminProfile: -----------> {0}: efmCuPAFRemoteDiscoveryCode: ----> efmCuPmeThreshLineAtn: ----------> {0}: efmCuPmeThreshSnrMgn: -----------> {0}: efmCuPmeLineAtnCrossingEnable: --> {false}: efmCuPmeSnrMgnCrossingEnable: ---> {false}: efmCuPmeDeviceFaultEnable: ------>...

  • Page 74: Specifying The Type Of Dsl Interface

    EtherXtend SHDSL WAN Interfaces rate and then move to the next higher rate until they reach the final rate they agree upon. The adaptive [fixed-rate=0] and fixed line rate settings are defined in the efmCuPme2BDataRate entry of the pme-profile. Table 17: Fix-bit-rate settings and modem train rates Then Disabled Disabled...

  • Page 75: Verifying The Interface

    WAN SHDSL interfaces admin-up-line-alarm: -----> {disabled}: ....Save changes? [s]ave, [c]hange or [q]uit: s Record updated. Verifying the interface Entering showlinestatus displays the status of the interfaces in the system. The following example displays some of the information returned by this command.

  • Page 76: Verifying The Type Of Dsl Interface

    EtherXtend SHDSL WAN Interfaces DslUpLineRate (bitsPerSec)....0 DslDownLineRate (bitsPerSec)....0 DslMaxAttainableUpLineRate (bitsPerSec)..5696000 DslMaxAttainableDownLineRate (bitsPerSec)..5696000 Out Octets........0 Out Pkts/Cells.......0 Out Discards.........0 Out Errors........0 In Octets........0 In Pkts/Cells........0 In Discards........0 In Errors........0 DSL Physical Stats: ------------------ DslLineSnrMgn (tenths dB)....0 DslLineAtn (tenths dB).......0 DslCurrOutputPwr (tenths dB)....0 LOFS.........0 LOLS.........0 LOSS.........0...

  • Page 77: Updating Efmcutargetworstcasesnrmgn

    WAN SHDSL interfaces To display the range or options of EFM port parameters, enter show efm-port. The following values are available on the efm-port interface. zSH> show efm-port efmCuPAFAdminState:----------------> enabled disabled efmCuPAFDiscoveryCode:-------------> {260} efmCuAdminProfile:-----------------> efmCuTargetDataRate:---------------> {1 - 999999} efmCuTargetWorstCaseSnrMgn:--------> {-10 - 21} efmCuThreshLowBandwidth:----------->...

  • Page 78: Etherxtend Efm 802.3Ah Bonding

    EtherXtend SHDSL WAN Interfaces efmCuTargetWorstCaseMode is TRUE and efmCuTargetWorstCaseSnrMgn is 0. Note: Previous releases of EtherXtend show the efmCuTargetWorstCaseSnrMgn to be 1. Enter the set2dafault command to view the current default setting of 0. To view current parameter settings, enter get efm-port interface/type: zSH>...

  • Page 79: Displaying Bond Groups

    EtherXtend EFM 802.3ah bonding zSH> bond add group 1-1-50-0/efmbond To add a new member to an existing bond group: zSH> bond add member 1-1-40-0/n2nbond 1-1-1-0/shdsl zSH> list if-stack ..if-stack 1-1-40-0/n2nbond/1-1-1-0-shdsl/n2nlink To create a bond group with multiple members and view the bond groups: zSH>...

  • Page 80: Changing Bond Group Type

    EtherXtend SHDSL WAN Interfaces Bond Groups Slot GrpId Name Type State 1-1-40-0 n2nbond Group Members Slot Port Name Type State 1-1-3-0 shdsl 1-1-4-0 shdsl Changing bond group type Bond group type can be changed for individual bond groups or all bond groups used in a specified slot using bond move and bond modify.

  • Page 81: Bond Group Bandwidth

    Bond group/physical line stats include all bytes received from all valid packets; bytes from errored packets and protocol overhead are not included. To display the aggregate statistics for a specified bond group interface or if-index, use bond stats. Use bond show to view the type of bond group and the interface name for the bond group to gather statistics.
  • Page 82 EtherXtend SHDSL WAN Interfaces Table 18: Bond group bandwidth Frame Size Downstream (pks/sec) Upstream (pks/sec) Total 40584 40584 81168 21478 21478 42956 11105 11105 22210 5547 5547 11094 1024 2826 2826 5652 1280 2269 2269 4538 1480 1967 1967 3934 EtherXtend User’s Guide...

  • Page 83: Configuring Bridging

    The bridge add command also supports uplink and downlink bridges that use VLANs. Refer to the Zhone CLI Reference Guide for a complete description of the command options and syntax. Bridging involves configuring the EtherXtend to direct traffic based on Ethernet MAC addresses.
  • Page 84 Configuring Bridging An uplink bridge uses one bridge interface in a VLAN as a default, and traffic from all other interfaces exits the system from this interface. As the default interface, packets entering the system on this interface do not have their source MAC addresses learned and associated with this interface.
  • Page 85 Bridging overview Intralink bridge interfaces require an additional configuration to take effect, which is a bridge-path. The bridge-path sets a default intralink path for either a specific VLAN or a global intralink for the system onto the intralink bridge. If an intralink is missing this configuration, traffic will not flow across the asymmetric VLAN.

  • Page 86: Bridge Enhancements To Flood Unknowns And Multicasts

    (dash-separated) ranges; <port> may be replaced with wildcard '*' for all ports on the card. Refer to the Zhone CLI Reference Guide for a complete description of the command options and syntax. Note: The EtherXtend ports can support both IP termination or bridging on different virtual circuits.

  • Page 87: Floodmulticast Parameter

    Bridge enhancements to flood unknowns and multicasts FloodMulticast parameter The FloodMulticast parameter allows the EtherXtend to flood all multicast traffic received on a bridge out to all other ports in the VLAN. This is useful for architectures where the EtherXtend is acting as an aggregation point with no user interfaces.

  • Page 88: Broadcasts And Bridging

    Configuring Bridging Broadcasts and bridging The EtherXtend supports a modified form of broadcast suppression when configured for bridge mode. The EtherXtend configures ports as the entered bridge type. In general, broadcasts sent to a downlink will traverse the uplink, but will not be sent down other downlinks, even within the same VLAN.
  • Page 89 VLANs downlink interfaces can be used for subtended EtherXtends or subscribers expecting tagged traffic with Transparent LAN Server (TLS) service. Note: The EtherXtend supports VLAN IDs from 1 to 4096. Multiple VLAN interfaces can be added to the same physical port and VC. Figure 13: Typical VLAN network VLAN 1 VLAN 1...
  • Page 90 Configuring Bridging This command adds a downlink to an Ethernet port on the LAN that uses VLAN 60. To verify the bridge interface, enter bridge-interface-record interface/ type: Note: It is recommended not to change the default settings unless advanced bridge configuration is required. zSH>...

  • Page 91: Bridging Behavior For Untagged, Tagged, And S-Tagged

    Bridging behavior for untagged, tagged, and s-tagged The global setting specifies that the EtherXtend should send all VLAN traffic to this port. A VLAN ID can also be used when the EtherXtend should send only traffic from a specific VLAN ID to this port. It is recommended not to change the default settings unless advanced bridge configuration is required.

  • Page 92: Overview

    Configuring Bridging • Tagged and s-tagged bridging examples on page 93 Overview Bridges also utilize VLAN and SLAN tagging for untagged, tagged, and s-tagged, traffic segregation. • Untagged bridging Untagged or transparent bridging accepts and sends traffic based on MAC addresses but does not provide traffic segregation.

  • Page 93: Untagged Bridging Examples

    EtherXtend uplink interface based on the destination MAC address without tagging or modification to the frame. Refer to the Zhone CLI Reference Guide for a complete description of the command options and syntax. Note: Ethernet interfaces can be addressed as either eth or ethernetcsmacd.
  • Page 94 Configuring Bridging s-tagStripAndInsert: -----------------> {true} s-tagOutgoingCOSOption: --------------> {s-tagdisable} s-tagIdCOS: --------------------------> s-tagOutgoingCOSValue: ---------------> mcastControlList: --------------------> maxVideoStreams: ---------------------> isPPPoA: -----------------------------> {false} floodUnknown: ------------------------> {false} floodMulticast: ----------------------> {false} bridgeIfEgressPacketRuleGroupIndex: --> bridgeIfTableBasedFilter: ------------> {NONE(0)} bridgeIfDhcpLearn: -------------------> {NONE(0)} To add a transparent bridge that accepts transparent/untagged traffic on the EtherXtend units’s downstream Ethernet port, enter bridge add interface/type: zSH>...

  • Page 95: Tagged And S-Tagged Bridging Examples

    Bridging behavior for untagged, tagged, and s-tagged maxVideoStreams: ---------------------> isPPPoA: -----------------------------> {false} floodUnknown: ------------------------> {false} floodMulticast: ----------------------> {false} bridgeIfEgressPacketRuleGroupIndex: --> bridgeIfTableBasedFilter: ------------> {NONE(0)} bridgeIfDhcpLearn: -------------------> {NONE(0)} To verify that both sides of the bridge are present, enter: zSH> bridge show Typ VLAN Bridge Table Data...

  • Page 96: Bridge Profile

    Configuring Bridging Bridge profile The following parameters in the bridge interface record are used for Ethernet COS support. Parameter Description vlanIdCOS Specifies the value loaded into the COS field of the VLAN header when an untagged packet received on this interface is tagged (VLAN ID inserted) for bridging.
  • Page 97 Bridging behavior for untagged, tagged, and s-tagged mcastControlList:--------------------> {264} maxVideoStreams:---------------------> {0 - 210} isPPPoA:-----------------------------> false true floodUnknown:------------------------> false true floodMulticast:----------------------> false true bridgeIfEgressPacketRuleGroupIndex:--> {0 - 2147483647} bridgeIfTableBasedFilter:------------> none+mac+ip bridgeIfDhcpLearn:-------------------> none+mac+ip To modify a parameter in the bridge-interface-record such as the COS, enter update bridge-interface-record interface/type and make the changes.

  • Page 98: Q-In-Q Vlan Tagging

    Configuring Bridging Q-in-Q VLAN tagging The IEEE 802.1ad (also know as Q-in-Q VLAN tagging) expands the VLAN space in the Ethernet frame to support the tagging of previously tagged packets. This second tag (SLAN) creates a "double-tagged" Ethernet frame. The double-tagged Ethernet frame enables service providers to offer additional services, such as Internet access on specific SLANs for specific customers, while still providing single-tagged VLAN services.

  • Page 99: Advanced Bridging Configurations

    Advanced bridging configurations To display the bridge-record profile, enter the get bridge-interface-record. zSH> get bridge-interface-record 1-1-2-0-eth-100/bridge bridge-interface-record 1-1-2-0-eth-100/bridge vpi: ---------------------------------> vci: ---------------------------------> vlanId: ------------------------------> {100} stripAndInsert: ----------------------> {false} customARP: ---------------------------> {false} filterBroadcast: ---------------------> {false} learnIp: -----------------------------> {true} learnUnicast: ------------------------> {true} maxUnicast: -------------------------->...

  • Page 100: Packet-Rule Records (Option 82, Forbid Oui, Dhcp Relay)

    Configuring Bridging Refer to the Zhone CLI Reference Guide for a complete description of the command options and syntax. Packet-rule records (Option 82, Forbid OUI, DHCP relay) The EtherXtend supports packet-rule records so an open-ended number of filter settings can be configured for on a uplink or downlink bridge interface.
  • Page 101 Advanced bridging configurations Configuring bridge interface record Configure the bridge-interface-record to a given bridge configuration group to a specified interface. Bridge configuration groups are assigned to the interface records by setting the bridgeIfConfigGroupIndex parameter. To configure a bridge configuration group: zSH>...

  • Page 102: Vlan Id Stripandinsert Parameter

    Configuring Bridging Configure a new packet-rule-record for group/instance and specify either bridgeinsertoption82, bridgedhcprelay, or bridgeforbidoui. Also specify the packet rule values (a string of information you want traced). For example: zSH> new packet-rule-record 1/1 packet-rule-record Please provide the following: [q]uit. packetRuleType: --->...

  • Page 103: Broadcast Suppression

    Advanced bridging configurations outgoingCOSOption: -------------------> {disable}: outgoingCOSValue: --------------------> {0}: s-tagTPID: ---------------------------> {0x8100}: s-tagId: -----------------------------> {4094}: s-tagStripAndInsert: -----------------> {true}: s-tagOutgoingCOSOption: --------------> {s-tagdisable}: s-tagIdCOS: --------------------------> {0}: s-tagOutgoingCOSValue: ---------------> {0}: mcastControlList: --------------------> maxVideoStreams: ---------------------> {0}: isPPPoA: -----------------------------> {false}: floodUnknown: ------------------------> {false}: floodMulticast: ----------------------> {false}: bridgeIfEgressPacketRuleGroupIndex: -->...

  • Page 104: Bridge With Dhcp Relay

    Configuring Bridging bridgeIfCustomDHCP: ------------------> {false}: true bridgeIfIngressPacketRuleGroupIndex: -> {0}: vlanIdCOS: ---------------------------> {0}: outgoingCOSOption: -------------------> {disable}: outgoingCOSValue: --------------------> {0}: s-tagTPID: ---------------------------> {0x8100}: s-tagId: -----------------------------> {4094}: s-tagStripAndInsert: -----------------> {true}: s-tagOutgoingCOSOption: --------------> {s-tagdisable}: s-tagIdCOS: --------------------------> {0}: s-tagOutgoingCOSValue: ---------------> {0}: mcastControlList: --------------------> maxVideoStreams: ---------------------> {0}: isPPPoA: ----------------------------->...
  • Page 105 Advanced bridging configurations Configuring bridges to support DHCP relay This procedure describes how to configure bridges on the EtherXtend to support DHCP relay. This procedure assumes the following configuration has already been performed on the EtherXtend. • Downlink bridge to the host •...

  • Page 106: Cos In Bridges

    Configuring Bridging s-tagId: ------------------> s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> s-tagOutgoingCOSValue: ----> Verify the dhcp-server-subnet with subnetgroup index matching the bridgeConfigValue is configured to forward DHCP requests to the desired external DHCP server. In this example, the bridgeConfigValue of 1 in the bridge-config-record matches the subnetgroup value specified in the dhcp-server-subnet profile.

  • Page 107: Verifying Bridge Settings

    Verifying bridge settings Adding a bridge Enter bridge add interface/type to create a bridge with a VLAN ID of 50. zSH> bridge add 1-1-2-0/eth vlan 50 Adding bridge on 1-1-2-0/eth Verifying bridge settings To verify bridge settings, enter get bridge-interface-record for each bridge. This command displays the bridge settings, including the learnMulticast and forwardToMulticast.
  • Page 108 Configuring Bridging learnIp: -----------------------------> {true} learnUnicast: ------------------------> {true} maxUnicast: --------------------------> learnMulticast: ----------------------> {true} forwardToUnicast: --------------------> {false} forwardToMulticast: ------------------> {false} forwardToDefault: --------------------> {true} bridgeIfCustomDHCP: ------------------> {false} bridgeIfIngressPacketRuleGroupIndex: -> vlanIdCOS: ---------------------------> outgoingCOSOption: -------------------> {disable} outgoingCOSValue: --------------------> s-tagTPID: ---------------------------> {0x8100} s-tagId: -----------------------------> s-tagStripAndInsert: -----------------> {true} s-tagOutgoingCOSOption: -------------->...

  • Page 109: Etherxtend Co And Cpe Mode Bridge Scenarios

    EtherXtend CO and CPE mode bridge scenarios EtherXtend CO and CPE mode bridge scenarios EtherXtends can be configured in either CO mode or CPE mode with either Transparent LAN Services (TLS) or uplink/downlink bridges. To enable bridged interfaces on the EtherXtend, different bridge types can be configured on the device depending on the mode of operation.

  • Page 110: Configure Uplink And Downlink Bridges

    Configuring Bridging Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------- 1/1/40/0/ip 1 10.250.1.40/24 00:01:47:36:2e:7b 1-1-40-0-efmbond-7 -------------------------------------------------------------------------------- The active default EFM interface 1-1-40-0-efmbond-7 is shown. To display the default bond group, enter bond show all: zSH> bond show all Bond Groups Slot GrpId Name Type...
  • Page 111 EtherXtend CO and CPE mode bridge scenarios the learning interface facing subscribers. Traffic coming into this interface is forwarded to the uplink regardless of the destination MAC address. Broadcasts and unicasts (known and unknown) will be sent out the default interface, which is the uplink bridge for the VLAN.

  • Page 112: Etherxtend Co Mode With Subtended Etherxtends In Cpe Mode

    Configuring Bridging zSH> bridge add 1-1-40-0/efmbond uplink Adding bridge on 1-1-40-0/efmbond Created bridge-interface-record 1-1-40-0-efmbond-0/bridge To create a bridge path for the uplink enter, bridge-path add interface/ type global: zSH> bridge-path add 1-1-40-0-efmbond-0/bridge global Bridge-path added successfully To create a downlink bridge on the LAN interface, enter bridge add interface/type downlink VLAN 100: zSH>...
  • Page 113 EtherXtend CO and CPE mode bridge scenarios Figure 18: EtherXtend CO scenario WAN/LAN TLS bridge interface using VLAN 100 EtherXtend CPE 1 downlink CO/CPE 1 VLAN 100 downlink CO/CPE 2 VLAN 200 EtherXtend CO WAN/LAN TLS bridge interface using VLAN 200 EtherXtend CPE 2 Configure the EtherXtend in CO mode On EtherXtend in CO mode, create an uplink bridge on a WAN Ethernet port...

  • Page 114: Configure The Etherxtend In Cpe Mode

    Configuring Bridging zSH> bridge-path add 1-1-40-0-efmbond-0/bridge global Bridge-path added successfully To create the downlink bridge on the WAN port for CPE 1 using VLAN 100, enter bridge add interface/type downlink vlan 100: zSH> bridge add 1-1-40-0/efmbond downlink vlan 100 All bridge traffic will be forwarded to the EtherXtend CPE 1 on VLAN 100.

  • Page 115: Etherxtend Bridge Commands

    Bridge show command on page 113 • Bridge stats on page 114 Refer to the Zhone CLI Reference Guide for a detailed explanation of the available bridge commands. Bridge delete command The bridge delete command deletes a specific bridge entry from the system.

  • Page 116: Bridge Stats

    Configuring Bridging zSH> bridge show Typ VLAN Bridge Table Data ------------------------------------------------------------------------------------- 123 1-1-4-0-eth/bridge D 00:1a:6d:13:19:8f S VLAN 123 default [U: 3600 sec, M: 150 sec, I: 0 sec] 0 1-1-3-0-eth/bridge Tagged 1-1-1-0-eth-0/bridge Tagged 4000 1-1-1-0-eth-4000/bridge Tg 1000/17 1-1-1-0-eth-1000/bridge 50 1-1-2-0-eth/bridge 100 1-1-40-0-efmbond/bridge Bridge stats The bridge stats command displays and clear bridge interface statistics for all...

  • Page 117: Chapter 9 Advanced Configuration

    DVANCED ONFIGURATION This chapter covers the following advanced configuration of the EtherXtend: • View EtherXtend statistics, page 115 • EtherXtend bond group statistics, page 117 • Display EFM profile parameters, page 121 • Perform EFM updates, page 122 • Modify EFM port interfaces, page 123 •...
  • Page 118 Advanced Configuration efmCuPAFInOverflows:------> {0 - 0} zSH> eth-oam stats *************** dot3OamStatsTable for interface 1-1-201-0/efmbond *************** Information Tx Information Rx UniqueEventNotification Tx UniqueEventNotification Rx DuplicateEventNotification Tx DuplicateEventNotification Rx LoopbackControl Tx LoopbackControl Rx VariableRequest Tx VariableRequest Rx VariableResponse Tx VariableResponse Rx OrgSpecific Tx OrgSpecific Rx UnsupportedCodes Tx UnsupportedCodes Rx...

  • Page 119: Etherxtend Bond Group Statistics

    EtherXtend bond group statistics EtherXtend bond group statistics This section describes EtherXtend bond group statistics including: • View bond group statistics, page 117 • View alarm activity, page 118 • View individual member of bond group statistics, page 119 • Set alarm thresholds, page 120 View bond group statistics The EtherXtend and other bonding capable devices provide the bond stats...

  • Page 120: View Alarm Activity

    Advanced Configuration Bcast Discards Check the output of the Bandwidth column in the Group Info section to view the aggregate train rate of the bond group. This aggregate rate can change depending on the status of the individual links in the bond group as shown in the Group members section.

  • Page 121: View Individual Member Of Bond Group Statistics

    EtherXtend bond group statistics OverflowAlarmTableCount ResourceId AlarmType AlarmSeverity ---------- --------- ------------- 1-1-2-0/eth linkDown critical 1-1-3-0/eth linkDown critical 1-1-99-0/efmbond threshold_alarm_active minor The output shows a minor alarm on the 1-1-99-0/efmbond interface. This change may be important when a loss of the aggregate rate affects service.

  • Page 122: Set Alarm Thresholds

    Advanced Configuration Set alarm thresholds Bonding capable devices provide an alarm-config profile to enable traps and alarms to be sent after meeting certain criteria. You can monitor the bond group bandwidth and have traps and alarms sent whenever the bandwidth drops below a particular threshold for a particular holdtime.

  • Page 123: Display Efm Profile Parameters

    Display EFM profile parameters bit-rate-threshold-holdtime: -> {0}: status-trap-enable: ----------> {enabled}: admin-up-alarm: --------------> {disabled}: ....Save changes? [s]ave, [c]hange or [q]uit: s Record updated. If the aggregate bandwidth of the links in the bond group drops below the bit-rate-threshold-value set in the alarm-config and remains below this value for the bit-rate-threshold-holdtime set in the alarm-config profile, then a trap and an alarm will be sent.

  • Page 124: Perform Efm Updates

    Advanced Configuration ocalloopback unknown ignoreLoopbackCommands:-----------> ignore process symbolPeriodSizeHi:---------------> {0 - 0} symbolPeriodSizeLo:---------------> {0 - 0} symbolPeriodErrorThresholdHi:-----> {0 - 0} symbolPeriodErrorThresholdLo:-----> {0 - 0} symbolPeriodErrorNotifyEnable:----> true false framePeriodSize:------------------> {0 - 0} framePeriodErrorThreshold:--------> {0 - 0} framePeriodErrorNotifyEnable:-----> true false intervalWindowSize:---------------> {0 - 0} intervalFrameErrorThreshold:------>...

  • Page 125: Update The Efm Bond

    Modify EFM port interfaces can occur because over time errors can increase causing retransmissions and lower throughput or cause a retrain of the link resulting in a lower traffic rate. The efmWorstCaseMode allows the line to sync assuming line conditions are the worst they can be by assuming that there are forty nine users/disburbers even if they do not currently exist.

  • Page 126: Modify An Efm Port

    Advanced Configuration efmCuTargetCurrentConditionMode: ---> {false} efmCuTargetCurrentConditionSnrMgn: -> efmCuTargetWorstCaseMode: ----------> {true} Modify an EFM port To modify an EFM port, enter update efm-port interface/type to display the profile parameters. zSH> update efm-port 1-1-1-0/shdsl efm-port 1-1-1-0/shdsl Please provide the following: [q]uit. efmCuPAFAdminState: ----------------> {enabled}: efmCuPAFDiscoveryCode: ------------->...

  • Page 127: Oam Modes

    802.3ah EFM OAM Release 1.14.1 introduces OAM support on MALC-EFM-SHDSL-24, MALC-EFM-SHDSL-24NT, MALC-EFM-SHDSL-24NTP card interfaces connected to an EtherXtend. MALC with EFM-SHDSL-24 card EtherXtend or compatible EFM OAM-enabled CPEs with EFM interfaces and ether-oam profiles in passive mode. OAM modes EFM/CPEs incorporating the OAM sublayer support active and/or passive mode.

  • Page 128: Active Mode

    Advanced Configuration Table 21: Active and passive mode Capability Active EFM/CPE Passive EFM/CPE Reacts to loopback control OAMPDUs Permitted to send organization specific OAMPDUs Requires the per EFM/CPE to be in active mode Active mode EFM/CPEs configured in active mode initiate the exchange of information OAMPDUs as defined by the discovery state.

  • Page 129: Display Oam Statistics

    802.3ah EFM OAM zSH> bridge show Typ VLAN Bridge Table Data --------------------------------------------------------------------------------- upl Tagged 1-1-201-0-efmbond-0/bridge S Global default [U: 3600 sec, M: 150 sec, I: 0 sec] 2 1-1-1-0-eth/bridge Enter the eth-oam add command to add OAM functionality to the bridge interface.
  • Page 130 Advanced Configuration ErroredFrame Window ErroredFrame Threshold ErroredFrame Notify enabled ErroredFramePeriod Window 4294967295 ErroredFramePeriod Threshold ErroredFramePeriod Notify disabled ErroredFrameSecondsSummary Window ErroredFrameSecondsSummary Threshold ErroredFrameSecondsSummary Notify disabled DyingGaspEnable disabled CriticalEventEnable disabled Configuring OAM support The OAM interface is defined by an ether-oam profile that specifies the options for active/passive mode, loopback, and notification for events.
  • Page 131 802.3ah EFM OAM active Sets OAM to active mode on this interface. The default is passive. passive Sets OAM to passive mode on this interface. The default is passive. eth-oam delete Deletes and disables the OAM configuration on the specified physical interface.
  • Page 132 Advanced Configuration EtherXtend User’s Guide...

  • Page 133: Chapter 10 Ip Service Level Agreement

    IP S ERVICE EVEL GREEMENT This chapter covers IP Service Level Agreement (IPSLA) for the EtherXtend. • Overview, page 131 • IPSLA, page 131 Overview The IP Service Level Agreement (IPSLA) feature assists service providers and network operators with enforcing and monitoring access network connections and performance.
  • Page 134 IP Service Level Agreement Figure 19: IPSLA MALC as IPSLA MALC as IPSLA IP Network Responder Initiator IPSLA Path for ICMP Pings IPSLA Path for IPSLA Path for ICMP Pings ICMP Pings EtherXtend as IPSLA EtherXtend as IPSLA Responder Responder Configuring IPSLA IPSLA requires the following configuration steps: •...
  • Page 135 IPSLA b Enter iplsa modify global state value pollseconds value to enable IPSLA and set the pollseconds interval. zSH> ipsla modify global state enabled pollseconds 120 Verify the IPSLA settings. zSH> ipsla show global state: -------> {enabled} pollseconds: -> {120} Create a ICMP path between devices.
  • Page 136 IP Service Level Agreement Table 23: CoS action index map to CoS queues (Continued) Default Name CoS Action Index CoS Queue AFClass 2 AFClass 3 AFClass4 Cos-5 ExpFwd NetwCtrl Each CoS action contains parameters as shown in Table Table 24: CoS action parameters Parameter Description Default...
  • Page 137 IPSLA Display the settings for an individual CoS action. The CoS Action determines IPSLA performance thresholds per CoS and how or whether to react to threshold crossings. The IPSLA Ping packet size may also be set in CoS Action. zSH> ipsla show cos-action cosactionindex 1 Cos Action Configuration for cosActionIndex: 1: name: ------->...
  • Page 138 IP Service Level Agreement timeOuts: ---> latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 6: name: -------> {Cos-5} traps: ------> {disabled} timeOuts: ---> latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 7: name: ------->...
  • Page 139 IPSLA Cos Action Configuration for cosactionindex: 1: name: -------> {Default} traps: ------> {enabled} timeouts: ---> latency: ----> {5000} jitter: -----> {10000} packetsize: -> {64} Change alarm-clearing thresholds, if necessary. The latency-clear parameter sets the criteria for when a trap (alarm) is sent based on how often a sample is taken.
  • Page 140 IP Service Level Agreement timeout-clear: -> latency: -------> {5000} latency-clear: -> jitter: --------> {10000} jitter-clear: --> metrics: -------> {enabled} packet-size: ---> {64} Configure the desired COS maps to modify the default DSCP to COS Action Index mappings. By default, DSCP are mapped to COS Action Index entries based of RFC 2599.
  • Page 141 IPSLA dscpIndex: 18 cosActionIndex: 0 dscpIndex: 19 cosActionIndex: 3 Type A<CR> to print all, <CR> to continue, Q<CR> to stop: Specify the desired index values in the command line to change the mapping of the DSCP index to COS action index. This example changes the mapping of DSCP index 1 to CoS action index 7.
  • Page 142 IP Service Level Agreement 172.16.78.11| Unknown| Unknown|Y|192.168.254.166|S| 14723|I| 192.168.254.15| Unknown| Unknown|Y|192.168.254.166|S| 14723|I| 171| 192.168.254.17| Unknown| Unknown|Y|192.168.254.166|S| 14723|I| The table below explains the statistics for the configured paths. Path Statistic Description Target IP Address IP Address of the device which is at the other end of the path. Target Name Name of the remote device.
  • Page 143 IPSLA 10.2.1.254 | Y | 10.2.1.254 | Y | zSH> ipsla stats cos ---+-----------------+---+--------+--------+--------+--------+--------+ | A | Cos| Target IP | C | Last Drop Idx| Address | T | Resp ---+-----------------+---+--------+--------+--------+--------+--------+ 172.16.78.11 | Y | 172.16.78.11 | Y | 172.16.78.11 | Y | 172.16.78.11 | Y | 172.16.78.11 | Y |...
  • Page 144 IP Service Level Agreement COS Action Index Description Statistic Avg RTT Average RTT since this statistic was last cleared to a zero value. Calculated as (RTT1 + RTT2 + RTT3 + …….+RTTn)/n where n equals the number of successful ping attempts since this statistic was last cleared to a zero value.
  • Page 145 IPSLA 1 | 6 | 10.2.1.254 |09/12/07-21:48:58|Y| 1 | 7 | 10.2.1.254 |09/12/07-21:48:58|Y| 1 | 8 | 10.2.1.254 |09/12/07-21:48:58|Y| zSH> ipsla stats history index 1 cosactionindex 3 ---+---+-----------------+-----------------+-+--------+--------+--------+------- I | C | n | O | Target IP DateTime | Drop t | S | Address |mm/dd/yy,hh:mm:ss|T|...
  • Page 146 IP Service Level Agreement EtherXtend User’s Guide...
  • Page 147 NDEX Numerics storage temperature 36 unpacking 37 Class of Service (COS) 96, 104 4-port EtherXtend 12 commands 4-port EtherXtend SHDSL 12 changepass 56 8-port EtherXtend 12 dslstat 73 showlinestatus 73 configuration basic 45, 69, 115, 131 ARP, broadcasts and bridging 86 Ethernet interface 62 bridging and IP support on VC 84...
  • Page 148 Index verifying the interface 73 description 46 logout command 46 timeout command 46 loop bonding 14 supported applications 14 technology description 13 EFM media modems copper services 14 DSL training rates 72 environmental requirements precautions 36 specifications 36 Ethernet overview 11 interface configuration 62 management channel 62...
  • Page 149 unpacking 37 system environmental dimensions fans 36 operating altitude 36 operating humidity 36 operating temperature 36 storage altitude 36 storage humidity 36 storage temperature 36 tagged bridging described 81 terminal interface, settings for 46 tools for installation 35 untagged bridging described 81 VLAN IDs supported 87 VLANs...
  • Page 150 Index EtherXtend User’s Guide...

Table of Contents