Z-Edge 64 Configuration Guide - Visionary Broadband 64_config.pdfZhone Technologies makes no representation or warranties with respect to the contents hereof and specifically disclaims

Z-Edge 64 Configuration Guide

For software version 1.6.1October 2002Document Part Number: 830-00519-04, Rev B

2 Z-Edge 64 Configuration Guide

Zhone Technologies@Zhone Way7001 Oakport StreetOakland, CA [email protected]

COPYRIGHT ©2000-2002 Zhone Technologies, Inc. and its licensors. All rights reserved.

This publication is protected by copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission from Zhone Technologies, Inc.

AccessNode, Arca-DACS, BAN, MALC, NetHorizhon, Sechtor, SkyZhone45, SLMS, Z-Edge, Z-Plex, ZMS, and Universal Edge are trademarks of Zhone Technologies, Inc.

Zhone and the Zhone logo are trademarks of Zhone Technologies, Inc.

All other trademarks and registered trademarks are the property of their respective holders.

Zhone Technologies makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability, noninfringement, or fitness for a particular purpose. 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.

http://www.zhone.com

mailto:[email protected]

Z-Edge 64 Configuration Guide 3

CONTENTS

About This Guide ...............................................................................................................................7

Document organization.............................................................................................7

Style and notation conventions ..............................................................................8Typographical conventions.......................................................................................8

Acronyms......................................................................................................................9

Related documents ..................................................................................................10

Contacting Global Service and Support.............................................................10Technical support....................................................................................................11Service requirements...............................................................................................11

Chapter 1 Features and capabilities ...................................................................................13

Product description .................................................................................................13

Features ......................................................................................................................14

Protocols and technologies...................................................................................14ATM........................................................................................................................14DSL .........................................................................................................................15NAT ........................................................................................................................15DHCP......................................................................................................................16RIP ..........................................................................................................................16SNMP......................................................................................................................17Automatic rate adaption ..........................................................................................17

Physical interfaces ...................................................................................................18

Managing the Z-Edge 64 .........................................................................................18SNMP......................................................................................................................19CLI ..........................................................................................................................19ZMS ........................................................................................................................19

Chapter 2 WAN configuration................................................................................................21

Configuring the local management channel .....................................................21Logging in and out of the system............................................................................21

System security ........................................................................................................22Changing the default user password .......................................................................22

Contents


Configuring a DSL connection..............................................................................22SDSL interface........................................................................................................24G.SHDSL interface .................................................................................................25Verifying connection with showlinestatus command .............................................28

Chapter 3 System configuration ..........................................................................................29

System defaults ........................................................................................................29

Configuring a connection to the ZMS .................................................................30

Chapter 4 Basic configuration ..............................................................................................33

Configuration overview...........................................................................................33Interface types (iftype) ............................................................................................33Profiles ....................................................................................................................34Interface indexes .....................................................................................................34

Configuring an Ethernet interface........................................................................35

Configuring static routes........................................................................................37Adding a default route ............................................................................................37Deleting routes ........................................................................................................38Verifying routes ......................................................................................................38

Displaying the routing table .............................................................................39traceroute command .........................................................................................39

Configuring RIP on the WAN interface ...............................................................39Displaying RIP information....................................................................................40

Chapter 5 Configuring Data and Voice ..............................................................................41

Overview .....................................................................................................................41

Configuring data communications ......................................................................41Updating the ATM traffic descriptor for data.........................................................42

Calculating PCR for an interface......................................................................42Updating the ATM Virtual Channel Link...............................................................43Updating the IP interface record .............................................................................44

Configuring voice communications ....................................................................45Creating a new ATM traffic descriptor...................................................................45Creating a new ATM Virtual Circuit Link (VCL)..................................................46AAL2 VCL profiles ................................................................................................47

POTS ................................................................................................................49ISDN.................................................................................................................49

AAL2 audio profiles ..............................................................................................50AAL2 CID profiles .................................................................................................51

POTS ................................................................................................................51ISDN.................................................................................................................53

Subscriber profiles ..................................................................................................54POTS ................................................................................................................55


ISDN.................................................................................................................55Subscriber voice profiles.........................................................................................56

POTS ................................................................................................................57ISDN.................................................................................................................57

Subscriber-voice endpoint profiles .........................................................................59POTS ................................................................................................................59ISDN.................................................................................................................60

Activating voice connections..................................................................................62

Chapter 6 Advanced IP configuration ................................................................................63

Configuring NAT on the WAN interface..............................................................63

Configuring the Z-Edge 64 as a DHCP server...................................................64DHCP server profiles and scope .............................................................................65Setting DHCP server options ..................................................................................66Creating DHCP server subnet options ....................................................................67Creating dhcp-server-group profile.........................................................................69Creating dhcp-server-host profile ...........................................................................70Enabling DHCP server............................................................................................71

Creating DHCP client identifiers...........................................................................72

Transparent bridging ...............................................................................................73

Configuring DNS resolver ......................................................................................76

PPP over ATM ............................................................................................................79

Chapter 7 Advanced voice configuration.........................................................................85

ADPCM voice compression ...................................................................................85

POTS voice options .................................................................................................86

ISDN B-channel data................................................................................................89

Silence suppression and comfort noise generation .......................................92

Chapter 8 Administration ........................................................................................................97

LED indicators ...........................................................................................................97Power LED..............................................................................................................98Diagnostic LED ......................................................................................................98Operational LED.....................................................................................................98WAN LED ..............................................................................................................98Line LEDs...............................................................................................................99

Z-Edge 64 BH2A (ISDN BRI) ........................................................................99 Z-Edge 64 H2A (POTS)..................................................................................99

CLI diagnostic methods ..........................................................................................99showlinestatus command ........................................................................................99interface show command ......................................................................................101traceroute command..............................................................................................101

Contents


SNMP administration .............................................................................................101Creating SNMP community names and access lists .............................................101

Creating a community profile.........................................................................102Creating community access lists ....................................................................102

Configuring traps ..................................................................................................103

User accounts ........................................................................................................104Adding a user ........................................................................................................104

Manually binding interfaces ................................................................................105

System logging .......................................................................................................106

Real time statistics .................................................................................................107

Saving and restoring configurations ................................................................107

Setting system date and time..............................................................................109

Rebooting the system ...........................................................................................109

Appendix A Specifications........................................................................................................111

Z-Edge 64 specifications ......................................................................................111

Appendix B Cable pinouts ........................................................................................................113

RJ11 pinouts for WAN line ...................................................................................113

RJ45 pinouts for LAN line ....................................................................................114

ISO 8877 pinouts for ISDN BRI voice lines ......................................................115

RJ11 pinouts for POTS voice lines ....................................................................116

Index ....................................................................................................................................................117


ABOUT THIS GUIDE

This guide is intended for use by Z-Edge 64 users and administrators. Z-Edge 64 users should have a fundamental knowledge of telephony, derived voice concepts, ATM networking, DSL protocols, and IP bridging and routing.

Refer to the Z-Edge 64 Quick Start Guide for hardware installation and connection information.

Document organizationThis guide contains the following information:

To Learn About Read

Z-Edge 64 functionality and features. Chapter 1, Features and capabilities, on page 13

Configuring a local management channel; system security; as well as configuring and activating a DSL connection.

Chapter 2, WAN configuration, on page 21

System on the Z-Edge 64; and configuring a connection to the ZMS.

Chapter 3, System configuration, on page 29

Configuring an Ethernet interface; configuring static routes; configuring RIP; and configuring DNS.

Chapter 4, Basic configuration, on page 33

Configuring data communications; and configuring voice communications.

Chapter 5, Configuring Data and Voice, on page 41

Configuring NAT; configuring the Z-Edge 64 as a DHCP server; and creating DHCP client identifiers.

Chapter 6, Advanced IP configuration, on page 63

Configuring ADPCM voice compression; POTS voice options; and ISDN B-channel data

Chapter 7, Advanced voice configuration, on page 85

About This Guide


Style and notation conventionsThe following conventions are used in this document to alert users to information that is instructional, warns of potential damage to system equipment or data, and warns of potential injury or death. Carefully read and follow the instructions included in this document.

Caution: A caution alerts users to conditions or actions that could damage equipment or data.

Note: A note provides important supplemental or amplified information.

Tip: A tip provides additional information that enables users to more readily complete their tasks.

WARNING! A warning alerts users to conditions or actions that could lead to injury or death.

WARNING! A warning with this icon alerts users to conditions or actions that could lead to injury caused by a laser.

Typographical conventions

The following typographical styles are used in this guide to represent specific types of information.

LEDs; CLI diagnostics; SNMP administration; user accounts; manually binding interfaces; saving and restoring configurations; and rebooting the system.

Chapter 8, Administration, on page 97

Z-Edge 64 product specifications. Appendix A, Specifications, on page 111

Pinouts for cables that attach to the Z-Edge 64.

Appendix B, Cable pinouts, on page 113

To Learn About Read

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.

Fixed Used in code examples for computer output, file names, path names, and the contents of online files or directories.

Acronyms


Acronyms

The following acronyms are related to the Z-Edge 64 and will appear throughout this manual:

Fixed Bold Used in code examples for text typed by users.

Fixed Bold Italic

Used in code examples for variable text typed by users.

Italic Used for book titles, chapter titles, file path names, notes in body text requiring special attention, section titles, emphasized terms, and variables.

PLAIN UPPER CASE

Used for environment variables.

Acronym Description

AAL2 ATM Adaption Layer 2

AAL5 ATM Adaption Layer 5

ATM Asynchronous Transfer Mode

BAN Zhone Broadband Access Node

CAS Channel Associated Signaling

CID AAL2 Channel Identifier

CLI Command Line Interface

CO Central Office

CPE Customer Premises Equipment

dB Decibel

DHCP Dynamic Host Configuration Protocol

DSL Digital Subscriber Line

DSLAM Digital Subscriber Line Access Multiplexer

DSS1 Digital Subscriber Signaling System number 1

ELCP Emulated Loop Control Protocol

FXO Foreign eXchange Office

FXS Foreign eXchange Station

G.SHDSL Global Symmetrical High-bit-rate Digital Subscriber Line

HDSL2 High-bit-rate Digital Subscriber Line, second generation

IANA Internet Assigned Numbers Authority

About This Guide


Related documentsRefer to the following publications for additional information:

• Z-Edge 64 Quick Start Guide

• Z-Edge 64 Release Notes

Contacting Global Service and SupportContact 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

• System configuration

• Software version running on the system

ISDN BRI Integrated Services Digital Network Basic Rate Interface

Kbps kilobits per second

LAN Local Area Network

MALC Zhone Multi-Access Loop Concentrator

MIB Management Information Base

NAT Network Address Translation

PBX Private Branch Exchange

POTS Plain Old Telephone Service

PSTN Public Switched Telephone Network

RIP Routing Information Protocol

SDSL Symmetric Digital Subscriber Line

SNMP Simple Network Management Protocol

TDM Time Division Multiplexing

TFTP Trivial File Transfer Protocol

VCI Virtual Channel Identifier

VCL Virtual Channel Link

VPI Virtual Path Identifier

WAN Wide Area Network

Acronym Description

Contacting Global Service and Support


• Description of the issue

Technical support

If you require assistance with the installation or operation of your product, or if you want to return a product for repair under warranty, contact GSS. The contact information is as follows:

If you purchased the product from an authorized dealer, distributor, Value Added Reseller (VAR), or third party, contact that supplier for technical assistance and warranty 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.

E-mail [email protected]

Telephone (North America) 877-ZHONE20

Telephone (International) 510-777-7133

Internet www.zhone.com/support

mailto:[email protected]

http://www.zhone.com/support

About This Guide



1

FEATURES AND CAPABILITIES

This chapter includes the following topics:

• Product description, page 13

• Protocols and technologies, page 14

• Physical interfaces, page 18

• Managing the Z-Edge 64, page 18

Product descriptionThe Z-Edge 64 is a compact integrated access device (IAD) that provides Internet Protocol (IP) routing features as well as traditional voice services over a single Digital Subscriber Line (DSL) WAN connection. The Z-Edge 64 BH2A offers Integrated Services Digital Network Basic Rate Interface (ISDN BRI) voice transport. The Z-Edge 64 H2A supports Plain Old Telephone Service (POTS).

Figure 1: The Z-Edge 64

In a traditional Voice over DSL (VoDSL) architecture, the Z-Edge 64 can operate with a Digital Loop Carrier (DLC), like the Zhone Multi-Access Loop Concentrator (MALC), or a voice gateway, such as a Zhone Sechtor 100A. Figure 2 shows an example application for the Z-Edge 64.

Features and capabilities


Figure 2: Typical Z-Edge 64 network application

FeaturesThe Z-Edge 64 has the following features:

• Toll-quality voice support with custom calling features

• Internet Protocol (IP) routing

• Network Address Translation (NAT) capabilities

• Dynamic Host Configuration Protocol (DHCP) server/client functionality

• Simple Network Management Protocol (SNMP) manageability

Protocols and technologiesThe Z-Edge 64 supports the following networking protocols and technologies. You should have an understanding of these concepts before operating the Z-Edge 64:

ATM

Asynchronous Transfer Mode (ATM) is a cell-based, high-speed networking technology. The ATM cell has a fixed length of 53 bytes. The cell is broken into two parts, the header and the payload. The header (5 bytes) contains the

Z-Edge 64

Internet

MALC

WAN connection

PSTN

voice linesLANconnection

Protocols and technologies


addressing information, and the payload (48 bytes) carries the voice or data message. Since each ATM cell has its own addressing mechanism, the cells can be sent asynchronously, or in any order.

ATM uses virtual channels (VCs) and virtual paths (VPs) to route cells in an ATM network. A VC, identified by a virtual channel identifier (VCI) is a connection between two communicating ATM entities. A VC consists of a concatenation of one or more ATM links. A VC provides a certain quality of service, which is defined in the ATM Traffic Descriptor. A VP, identified by a virtual path identifier (VPI), is a group of VCs between two ATM endpoints. A physical link can support many VPs. Similarly, a VP can contain many VCs.

DSL

Digital Subscriber Line (DSL) technologies provide access to high-bandwidth networks over a unshielded twisted pair (UTP) of copper wires. By using frequencies above the telephone bandwidth (300Hz to 3,200Hz), DSL can encode more data to achieve higher data rates than would otherwise be possible in the restricted frequency range of a POTS network. The DSL family includes several variations.

Symmetric Digital Subscriber Line (SDSL) provides data-only symmetric transfer rates of up to 2.32Mbps over a single pair of copper wires. SDSL uses the same 2B + 1Q signaling as ISDN. SDSL service requires that the customer is no further than 10,000 feet from the central office. SDSL is defined in ITU G.991.1.

Global Symmetric High-bit-rate Digital Subscriber Line (G.SHDSL) is designed to operate with both HDSL and SDSL networks. G.SHDSL extends the reach and transfer rates of DSL services. G.SHDSL supports adaptive data transfer rates of 192Kbps to 2.3Mbps with a reach of over 20,000 feet. The G.SHDSL specification (ITU standard G.991.2) allows for transmission over single-pair and two-pair copper wires.

NAT

Network Address Translation (NAT) is an Internet standard that enables a local area network (LAN) to use one set of IP addresses for internal traffic and a second set of addresses for external traffic. Hosts in a private network can transparently access an external network and enable access to selective local hosts from the outside.

A NAT device connecting the public Internet and the network it serves rewrites IP addresses and port numbers in IP headers. The packets appear to be coming from a single public IP address of the NAT device, instead of the actual source or destination.

NAT serves two main purposes: It provides a type of firewall by hiding internal IP addresses, and it enables a company to define more internal IP



addresses. Since the addresses are used internally only, there is no possibility of conflict with IP addresses used by other companies and organizations.

DHCP

The Dynamic Host Control Protocol (DHCP) provides a mechanism through which client computers using TCP/IP can obtain configuration parameters (such as the default router and the Domain Name System [DNS] server, subnet mask, gateway address, and lease time) from a centrally located DHCP server. DHCP dynamic reconfiguration requires a DHCP server, a forwarding agent in each router, and DHCP capability in each client TCP/IP stack. The most important configuration parameter carried by DHCP is the IP address.

Dynamic addressing allows a device to have a different IP address every time it connects to the network, and in some systems, the device IP address can change while it is still connected to the network. DHCP also supports a mix of static and dynamic IP addresses.

Figure 3: Z-Edge 64 as DHCP client

A DHCP client is an Internet host using DHCP to obtain configuration parameters such as a network address. A DHCP server is an Internet host that returns configuration parameters to DHCP clients. As a DHCP client, the Z-Edge 64 receives its IP address and configuration parameters from a DHCP server, such as the BAN.

RIP

Routing Information Protocol (RIP) is widely used for routing traffic on the Internet and is an interior gateway protocol (IGP), which means that it performs routing within a single autonomous system. RIP is based on

Internet

BAN

Z-Edge 64

DHCP server

DHCP client

10.0.0.2

10.0.0.1

Protocols and technologies


distance-vector algorithms that measure the shortest path between two points on a network, based on the addresses of the originating and destination devices. The shortest path is determined by the number of hops between those points. RIP routers maintain only the best route (the route with the lowest metric value) to a destination. After updating its routing table, the router immediately begins transmitting routing updates to inform other network routers of the shortest route.

Routing Information Protocol version 2 (RIPv2) is the latest enhancement to RIP. RIPv2 allows more information to be included in RIP packets and provides an authentication mechanism.

SNMP

Z-Edge 64 users can manage their system with Simple Network Management Protocol (SNMP) software. SNMP is based on network management stations (managers) and network managed elements (agents). SNMP allows network managers and network agents to communicate.

There are three types of SNMP transactions—a Get, a Set, or a Trap. The Get and Set commands are sent from the manager to the agent to determine (Get) or configure (Set) network variables and status. A Trap is an exception to this SNMP transaction pattern, in that the Trap is an unsolicited event report sent from the agent to the manager. When the SNMP manager receives the Trap message, it can be stored in the Management Information Base (MIB) and displayed on a terminal screen.

A MIB is a virtual database that identifies each manageable object by name, syntax, accessibility, status, a text description, and a unique manageable-Object Identification number (OID). MIBs come in three varieties: Public, Experimental, and Private Enterprise.

Automatic rate adaption

Automatic baud rate detection (also known as rate adaption) allows receiving devices to communicate with transmitting devices operating at different speeds without the need to establish data rates in advance. By determining the baud rate from the transmitting device, the receiving Z-Edge 64 automatically trains to match the line rate of the incoming data.

Usually there is one central office (CO) device transmitting to many customer premises equipment (CPE) units. When a CO device trains with a CPE unit, the devices will settle on the lower of the two devices’ line rates. It is optimal to set the CPE line rate to 2320 kbps because it allows a wide range of rates for CO and CPE devices to agree upon.

The training of line rates is faster on G.SHDSL than on SDSL. The G.SHDSL rate adaption process occurs during the CO and CPE modems’ handshake, where the devices probe the G.SHDSL line to find the best possible line rate. The SDSL autobaud process is slower because the CO and CPE modems use an algorithm to step through a sequence of line rates, where the devices



establish a connection at each line rate and then move to the next higher rate until they reach the final rate, which is the lower of the line rates. Note that the Z-Edge 64 does not currently support SDSL autobaud.

Physical interfacesThe Z-Edge 64 has following physical interfaces:

• WAN: One RJ11 port.A standard RJ11 port connects unshielded twisted pair (UTP) copper wire to DSL networks.

• LAN: One 10/100BaseT RJ45 port. A RJ45 port carries both management and data traffic, and interconnects with most Transfer Control Protocol/Internet Protocol (TCP/IP) hubs and networks.

• Phone lines:

Z-Edge 64 BH2A: Four ISO 8877 ports support ISDN BRI.

or

Z-Edge 64 H2A: Four RJ11 ports support POTS.

• Serial: One DB9 port. A single DB9 asynchronous serial port provides direct PC or virtual terminal (such as VT100) access to the Z-Edge 64. The serial port allows access to the CLI.

Figure 4: The back panel of the Z-Edge 64

Managing the Z-Edge 64The Z-Edge 64 provides the following physical interfaces to configure the unit:

• Serial (craft)—An out-of-band RS232 serial interface

• Ethernet—A 10/100Base-T RJ45 port

WAN Phonelines

Serial port LAN Power

Managing the Z-Edge 64


You can configure the Z-Edge 64 using any of the following methods:

• Simple Network Management Protocol (SNMP)

• Command Line Interface (CLI)

• Zhone Management System (ZMS)

SNMP

The Z-Edge 64 supports SNMP version 1 and version 2 for system management. Network object variables are MIB-II compliant.

SNMP can be accessed over IP interfaces or the Ethernet interface. The SNMP agent on the Z-Edge 64 uses port 161 of user datagram protocol (UDP) for management traffic and UDP port 162 for error events and SNMP traps.

The MIBs for the Z-Edge 64 control the following:

• Data port configuration, status, and diagnostics

• General system management, field upgrades, and alarms

• Traps

CLI

The CLI is functionally similar to SNMP. The CLI commands are equivalent to SNMP get and set commands and allow you to configure the unit. The interface is accessible both using telnet and through a local serial port. You can configure the same elements with the CLI as you can with SNMP.

ZMS

ZMS allows Z-Edge 64 users to navigate, monitor, and manage their Zhone networks with a graphical user interface.




2

WAN CONFIGURATION

This chapter details how to configure the Z-Edge 64 physical connection to the WAN. The WAN connection is necessary for all automatic provisioning of the Z-Edge 64. This chapter includes the following topics:

• Configuring the local management channel, page 21

• System security, page 22

• Configuring a DSL connection, page 22

Configuring the local management channelThe Z-Edge 64 unit provides an out-of-band serial (local or craft) interface for managing the unit. To access the serial port, configure your terminal interface software with the following settings:

• 9600bps

• 8 data bits

• No parity

• 1 stop bit

• No hardware flow control

Logging in and out of the system

Perform the initial configuration of the system using the serial interface. After you have completed the initial configuration, you can manage the Z-Edge 64 unit over the network using a telnet session.

Log into the system (the default user name is admin, the default password is zhone):

login:adminpassword: *****zSH>

To log out of the system, enter the logout command:

zSH> logout

WAN configuration


Note: When you turn the Z-Edge 64 on, you may receive error messages about automatic DHCP client configuration because there is no WAN connection set up. This is normal. Proceed to configure the WAN connection.

System securityThere are several methods to guard against unauthorized access to your Z-Edge 64, such as changing the default user password. You can also set up SNMP access lists to restrict access to your system. See SNMP administration in Chapter 7 for more information about setting SNMP access lists.

Changing the default user password

When adding users, the system automatically assigns a temporary password to each user. Most users will want to change their password. The changepass command changes the password for the current logged in user. The following is an example of changing a password:

jsmith> changepassCurrent Password: the password is case-sensitive and will not appear as you type itNew Password : the password is case-sensitive and will not appear as you type itConfirm New Password : the password is case-sensitive and will not appear as you type itUser record updated.Password change successful.

Configuring a DSL connectionThe first step in configuring your Z-Edge 64 is connecting to the WAN by setting up a DSL connection over the Z-Edge 64 WAN interface.

The dsl-config profile is automatically created by the system when the Z-Edge 64 is turned on. Update the dsl-config profile to match your line-type and unit-mode.

Configuring a DSL connection


The dsl-config profile supports the following parameters:

Below is an example showing the default settings for a dsl-config profile:

zSH> get dsl-config 1-1-1-0/hdsl2 hdsl2 type includes HDSL2, SDSL, and G.SHDSLline-type: -> {shdsllatest} shdsl | sdsl | shdsllatest | sdsllatestunit-mode: -> {cpe}

Depending on the line-type, configuration profiles are automatically created for the DSL variations. To change the DSL variation, modify the line-type in the dsl-config profile and then update the specific DSL configuration profiles.

Parameter Description

line-type The DSL type supported on this interface.

Values: shdsl GlobespanVirata firmware for G.SHDSL (not compatible with shdsllatest firmware)

sdsl GlobespanVirata firmware for SDSL (not compatible with sdsllatest firmware).

shdsllatest Compatible with most GlobespanVirata G.SHDSL firmware. This value is required for automatic rate adaption on G.SHDSL.

sdsllatest Compatible with most transparent mode ATM SDSL implementations. This value is required for automatic rate adaption on SDSL.

Default: shdsllatest

unit-mode Specifies whether the unit is configured as a CO or CPE device. If you are connecting Z-Edge 64 units back-to-back, set the unit-mode to co (central office) on one Z-Edge 64, and set the downstream Z-Edge 64 to cpe (customer premises equipment).

Values: co

cpe

Default: cpe

WAN configuration


SDSL interface

The sdsl-config profile supports the following parameters (all others should be left at their default values):


config-line-rate The line rate.

Values: line-rate-144kbps, line-rate-160kbps, line-rate-192kbps, line-rate-208kbps, line-rate-224kbps, line-rate-256kbps, line-rate-272kbps, line-rate-320kbps, line-rate-368kbps, line-rate-384kbps, line-rate-400kbps, line-rate-416kbps, line-rate-528kbps, line-rate-768kbps, line-rate-784kbps, line-rate-1040kbps, line-rate-1152kbps, line-rate-1168kbps, line-rate-1536kbps, line-rate-1552kbps, line-rate-1568kbps, line-rate-2320kbps, line-rate-176kbps, line-rate-240kbps, line-rate-288kbps, line-rate-304kbps, line-rate-336kbps, line-rate-352kbps, line-rate-432kbps, line-rate-464kbps, line-rate-496kbps, line-rate-560kbps, line-rate-592kbps, line-rate-624kbps, line-rate-656kbps, line-rate-688kbps, line-rate-720kbps, line-rate-752kbps, line-rate-816kbps, line-rate-848kbps, line-rate-880kbps, line-rate-912kbps, line-rate-944kbps, line-rate-976kbps, line-rate-1008kbps, line-rate-1072kbps, line-rate-1104kbps, line-rate-1136kbps, line-rate-1200kbps, line-rate-1232kbps, line-rate-1264kbps, line-rate-1296kbps, line-rate-1328kbps, line-rate-1360kbps, line-rate-1392kbps, line-rate-1424kbps, line-rate-1456kbps, line-rate-1488kbps, line-rate-1520kbps, line-rate-1584kbps, line-rate-1616kbps, line-rate-1648kbps, line-rate-1680kbps, line-rate-1712kbps, line-rate-1744kbps, line-rate-1776kbps, line-rate-1808kbps, line-rate-1840kbps, line-rate-1872kbps, line-rate-1904kbps, line-rate-1936kbps, line-rate-1968kbps, line-rate-2000kbps, line-rate-2032kbps, line-rate-2064kbps, line-rate-2096kbps, line-rate-2128kbps, line-rate-2160kbps, line-rate-2192kbps, line-rate-2224kbps, line-rate-2256kbps, line-rate-2288kbps

Default: line-rate-1552kbps

fix-bit-rate Enables or disables automatic baud rate detection.

Values: fix-bit-disable This value enables automatic baud rate detection. If the CO and CPE devices have different line rates at startup, the lower of the two rates will be selected.

fix-bit-enable This value is used for static (set) baud rates. This option is available if the device’s unit-mode is set to co in the dsl-config profile. This value is ignored if the device’s unit-mode is set to cpe.

Default: fix-bit-disable

ntr Network timing recovery (NTR) specifies that the system synchronizes with an external (network) clocking source.

Values: ntr-enable the system synchronizes with the network.

ntr-disable the system relies on its own clocking source.

Default: ntr-disable



Note: In order to achieve optimum results when provisioning automatic baud rate adaption than 9000 feet, set the fix-bit-rate parameter to fix-bit-enable in the sdsl-config profile on both ends of the connection. Also, ensure that the config-line-rate is the same on both ends of the connection.

Below is an example of the sdsl-config record created by setting the line-type parameter to sdsllatest in the dsl-config profile. Update this profile if you want to change the line rate or to override autobaud.

zSH> update sdsl-config 1-1-1-0/hdsl2Please provide the following: [q]uit.config-line-rate: -> {line-rate-1552kbps}: line-rate-2320kbpsfix-bit-rate: -----> {fix-bit-disable}: connect-mode: -----> {flowpoint-mode}:ntr: --------------> {ntr-disable}:framer-type: ------> {atm-clear-channel}:power-scale: ------> {17664}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

G.SHDSL interface

Updating the dsl-config profile, with the line-type set to shdsl, automatically creates an associated shdsl-config profile. To configure a G.SHDSL interface:

zSH> update dsl-config 1-1-1-0/hdsl2line-type: -> {sdsl}: shdslunit-mode: -> {cpe}:.................... Save changes? [s]ave, [c]hange or [q]uit: sRecord updated

WAN configuration


The shdsl-config profile supports the following parameters (all others should be left at their default values):


shdsl-config-line-rate The line rate.

Values: line-rate-72kbps, line-rate-80kbps, line-rate-136kbps, line-rate-144kbps, line-rate-200kbps, line-rate-208kbps, line-rate-264kbps, line-rate-272kbps, line-rate-328kbps, line-rate-336kbps, line-rate-392kbps, line-rate-400kbps, line-rate-456kbps, line-rate-464kbps, line-rate-520kbps, line-rate-528kbps, line-rate-584kbps, line-rate-592kbps, line-rate-648kbps, line-rate-656kbps, line-rate-712kbps, line-rate-720kbps, line-rate-776kbps, line-rate-784kbps, line-rate-840kbps, line-rate-848kbps, line-rate-904kbps, line-rate-912kbps, line-rate-968kbps, line-rate-976kbps, line-rate-1032kbps, line-rate-1040kbps, line-rate-1096kbps, line-rate-1104kbps, line-rate-1160kbps, line-rate-1168kbps, line-rate-1224kbps, line-rate-1232kbps, line-rate-1288kbps, line-rate-1296kbps, line-rate-1352kbps, line-rate-1360kbps, line-rate-1416kbps, line-rate-1424kbps, line-rate-1480kbps, line-rate-1488kbps, line-rate-1544kbps, line-rate-1552kbps, line-rate-1608kbps, line-rate-1616kbps, line-rate-1672kbps, line-rate-1680kbps, line-rate-1736kbps, line-rate-1744kbps, line-rate-1800kbps, line-rate-1808kbps, line-rate-1864kbps, line-rate-1872kbps, line-rate-1928kbps, line-rate-1936kbps, line-rate-1992kbps, line-rate-2000kbps, line-rate-2056kbps, line-rate-2064kbps, line-rate-2120kbps, line-rate-2128kbps, line-rate-2184kbps, line-rate-2192kbps, line-rate-2248kbps, line-rate-2256kbps, line-rate-2312kbps, line-rate-2320kbps, line-rate-2368kbps

Default: line-rate-2320kbps

shdsl-transmit-power-back-off-mode

Determines if the transmit power backoff, defined in the SHDSL standard, is used:

Values: backoffdisable

backoffenable

Default: backoffenable

shdsl-fix-bit-rate Enables or disables automatic baud rate detection.

Values: fix-bit-disable This value enables automatic baud rate detection. If the CO and CPE devices have different line rates at startup, the lower of the two rates will be selected.

fix-bit-enable This value is used for static (set) baud rates. This option is available if the device’s unit-mode is set to co in the dsl-config profile. This value is ignored if the device’s unit-mode is set to cpe.

Default: fix-bit-disable



Note: Set both ends (CO and CPE devices) of the G.SHDSL connection to fix-bit-disable in the shdsl-config profile to ensure automatic baud rate adaption.

Below is an example of the shdsl-config record created by setting the line-type parameter to shdsllatest in the dsl-config profile. Update this profile if you want to change the line rate or to override autobaud.

zSH> update shdsl-config 1-1-1-0/hdsl2Please provide the following: [q]uit.shdsl-config-line-rate: -------------> {line-rate-2320kbps}: shdsl-transmit-power-back-off-mode: -> {backoffenable}:shdsl-fix-bit-rate: -----------------> {fix-bit-disable}: shdsl-ntr: --------------------------> {ntr-local-osc}:shdsl-clock-offset: -----------------> {0}:shdsl-repeater-id: ------------------> {repeaterdisable}:shdsl-standard: ---------------------> {annex-b}:shdsl-startup-margin: ---------------> {6}:shdsl-wire-mode: --------------------> {four-wire-disable}:shdsl-frame-sync: -------------------> {45}:

shdsl-standard Determines the SHDSL standards.

Values: annex-a

annex-b

Default: annex-b

shdsl-startup-margin Used to negotiate the bit rate during startup. The amount of margin is specified in decibels (dB) and its value ranges from 0 to 15.

Values: 0 to 15

Default: 6

shdsl-frame-sync Enables the user to select a 14-bit frame sync word identifier (FSW).

Values: From 0 to 65535

Default: 45

shdsl-power-scale Adjusts transmit power in small increments to compensate for minor differences in power between units.

Values: 17664 For loop lengths from 0 to 10 feet (0 to 3.05 meters). Corresponds to -3.39dB.

20992 For loop lengths less than 4000 feet (1219 meters). Corresponds to -1.9dB.

29952 For loop lengths greater than 4000 feet (1219 meters). Corresponds to -1.19dB.

Default: 29298


WAN configuration


shdsl-decoder-coeffA: ---------------> {366}:shdsl-decoder-coeffB: ---------------> {817}:shdsl-power-scale: ------------------> {29298}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Note: If sdsl-config or shdsl-config profiles exist before setting the line-type parameter to shdsllatest or sdsllatest in the dsl-config profile, the parameter settings will not be changed in the sdsl-config or shdsl-config profiles. You may need to update these profiles to change the line rate or enable autobaud.

Verifying connection with showlinestatus command

Verify that the DSL connection is operational by entering a showlinestatus command for the WAN port. The showlinestatus command uses this syntax:

showlinestatus shelf slot port subport

The following example displays the status of the connection on shelf 1, slot 1, port 1 (the WAN interface):

zSH> showlinestatus 1 1 1Search in progress ......... ................. GroupId --------> 6 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 3 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 1 SubPort --------> 0

Now that the WAN connection is active, you can proceed to configure rest of the system.

Table 1: Automatic baud rate detection configuration settings

DSL line type setting Fixed bit rate setting Suggested line rates

sdsllatest fix-bit-disable for both CO and CPE devices

CPE - 2320 kbps

CO - any supported rate

shdsllatest shdsl-fix-bit-disable for both CO and CPE devices

CPE - 2320 kbps

CO - any supported rate


3

SYSTEM CONFIGURATION

This chapter details how to configure system-wide settings of the Z-Edge 64. It includes the following topics:

• System defaults, page 29

• Configuring a connection to the ZMS, page 30

System defaultsWhen the Z-Edge 64 is turned on, several profiles are automatically configured. Here are some of the Z-Edge 64 default configurations:

• The Z-Edge 64 is set up as a DHCP client in the ip-interface-record for the WAN port of the system.

• The Ethernet (LAN) interface is 10/100 Mbps autosensing, autonegotiating.

• The DSL (WAN) interface is set to SDSL, customer premises equipment, with a line speed of 1552kbps.

• The Virtual Path Indicator (VPI) and Virtual Channel Identifier (VCI) values for the WAN interface: VPI/VCI = 0/35.

The Z-Edge 64 automatically creates ip-interface-record, atm-traf-descr record and atm-vcl profiles for the WAN interface when the Z-Edge 64 is turned on. These three profiles enable ATM traffic over IP on the WAN port. Enter get commands to view these default profiles:

zSH> get ip-interface-record 1-1-1-0/ipvpi: ---------------> {0}vci: ---------------> {35}rdindex: -----------> {1}dhcp: --------------> {client} addr: --------------> {0.0.0.0}netmask: -----------> {0.0.0.0}bcastaddr: ---------> {0.0.0.0}destaddr: ----------> {0.0.0.0}farendaddr: --------> {0.0.0.0}mru: ---------------> {1500}reasmmaxsize: ------> {0}ingressfiltername: -> {}egressfiltername: --> {}

System configuration


pointtopoint: ------> {no}mcastenabled: ------> {yes}ipfwdenabled: ------> {yes}mcastfwdenabled: ---> {yes}natenabled: --------> {no}bcastenabled: ------> {yes}ingressfilterid: ---> {0}egressfilterid: ----> {0}ipaddrdynamic: -----> {dhcpclient}dhcpserverenable: --> {false}

zSH> get atm-traf-descr 1td_type: -------------> {atmNoClpNoScr}td_param1: -----------> {3659} this is the peak cell rate (PCR)td_param2: -----------> {0}td_param3: -----------> {0}td_param4: -----------> {0}td_param5: -----------> {0}td_service_category: -> {ubr}trnk-vcl-rate: -------> {unused}

zSH> get atm-vcl 1-1-1-0-hdsl2/atm/0/35vpi: -----------------------------> {0}vci: -----------------------------> {35}admin_status: --------------------> {up}receive_traffic_descr_index: -----> {1}transmit_traffic_descr_index: ----> {1}vcc_aal_type: --------------------> {aal5}vcc_aal5_cpcs_transmit_sdu_size: -> {9188}vcc_aal5_cpcs_receive_sdu_size: --> {9188}vcc_aal5_encaps_type: ------------> {llcencapsulation}vcl_cast_type: -------------------> {p2p}vcl_conn_kind: -------------------> {pvc}fault-detection-type: ------------> {disabled}

The Z-Edge 64 uses DHCP to obtain configuration parameters, such as an IP address, from a DHCP server. To act as a DHCP client, the Z-Edge 64 must be connected to the DHCP server over an active WAN connection. Set up the WAN connection and the DHCP client configuration will occur as set up on the DHCP server.

Configuring a connection to the ZMS

Note: Most of the parameters in the system profile should be left at their default values. ZMS uses them to update status of the configuration process.

The system profile is automatically created. The following parameter in the system profile determines whether authentication failure traps are sent to ZMS:

Configuring a connection to the ZMS


The following example shows the parameters the ZMS sets to communicate with the Z-Edge 64:

zSH> update system 0Please provide the following: [q]uit.syscontact: ----------> {Zhone Technologies 7001 Oakport Street Oakland CA 94621}:sysname: -------------> {Z-Edge 64H2A}:syslocation: ---------> {}:syslocation: ---------> {Oakland}:enableauthtraps: -----> {disabled}: enabled optionalsetserialno: ---------> {0}:zmsexists: -----------> {false}:zmsconnectionstatus: -> {inactive}:zmsipaddress: --------> {192.168.210.28}:configsyncexists: ----> {false}:configsyncoverflow: --> {false}:configsyncpriority: --> {high}:configsyncaction: ----> {noaction}:configsyncfilename: --> {192.168.94.226_4_1014067321329}:configsyncstatus: ----> {synccomplete}:configsyncuser: ------> {cfgsync}:configsyncpasswd: ----> {}: ** private ** the password is hiddennumshelves: ----------> {1}:shelvesarray: --------> {}:numcards: ------------> {3}:ipaddress: -----------> {192.168.1.2}: alternateipaddress: --> {0.0.0.0}:countryregion: -------> {us}:primaryclocksource: --> {0/0/0/0/0}:ringsource: ----------> {internalringsourcelabel}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Caution: Enter the correct country name for the countryregion parameter. The voice quality might be affected if the setting is incorrect.


enableauthtraps Indicates whether the system is permitted to generate authenticationFailure traps. The value of this parameter overrides any configuration information; it provides a means to disable all authenticationFailure traps.

Values: enabled

disabled

Default: disabled

System configuration


CLI provisioning and ZMS

Note: For details on using ZMS, refer to the ZMS Administrator's Guide and the NetHorizhon User's Guide.

CLI configuration of a device being managed by the ZMS is disabled by default. Attempting to configure the device results in an error:

zSH> update system 0

Provisioning via CLI is currently not available.

If you need to configure the device from the CLI, use the resetcliprov command.

If you plan to use a script to provision the device from the CLI while it is being managed by the ZMS:

1 Update the system profile to disable partial config syncs to ZMS:

zSH> update system 0Please provide the following: [q]uit.syscontact: ----------> {Zhone Global Services and Support 7001 Oakport Road Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113 [email protected]}:sysname: -------------> {Z-Edge}:syslocation: ---------> {Oakland}:enableauthtraps: -----> {disabled}: setserialno: ---------> {0}:zmsexists: -----------> {true}: falsezmsconnectionstatus: -> {inactive}:zmsipaddress: --------> {192.168.210.28}:configsyncexists: ----> {false}:configsyncoverflow: --> {false}:configsyncpriority: --> {high}:configsyncaction: ----> {noaction}:configsyncfilename: --> {192.168.94.226_4_1014067321329}:configsyncstatus: ----> {synccomplete}:configsyncuser: ------> {cfgsync}:configsyncpasswd: ----> {}: ** private ** numshelves: ----------> {1}:shelvesarray: --------> {}:numcards: ------------> {3}:ipaddress: -----------> {192.168.8.21}: alternateipaddress: --> {0.0.0.0}:countryregion: -------> {us}:primaryclocksource: --> {0/0/0/0/0}:ringsource: ----------> {internalringsourcelabel}:revertiveclocksource: -> {true}voicebandwidthcheck: --> {false} ....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

2 After the provisioning is complete, perform a full config sync from ZMS.


4

BASIC CONFIGURATION

This chapter covers basic configuration of the Z-Edge 64:

• Configuration overview, page 33

• Configuring an Ethernet interface, page 35

• Configuring static routes, page 37

• Configuring RIP on the WAN interface, page 39

Configuration overviewThe Z-Edge 64 uses the shelf-slot-port-subport/type syntax to identify system interfaces. The Z-Edge 64 is always 1 for the shelf and slot values and 0 for the subport value. The type is based on the Internet Assigned Numbers Authority interface type (IANAiftype) definitions.

Note: When configuring the Z-Edge 64 using the command line interface (CLI), enter all text strings in lower case. The CLI is case sensitive.

Interface types (iftype)

Interfaces on the Z-Edge 64 use Internet Assigned Numbers Authority interface type (IANAifType) definitions to indicate the type of physical interface which a virtual connection is bound.

The following are some common iftypes you might need to configure your unit. You can enter either the name or the number of the iftype:

• ethernetcsmacd (6): Ethernet

• hdsl2 (168): HDSL2 and SDSL

• ip (126): Internet Protocol

• isdns (63): ISDN S/T

• isdnu (76): ISDN U

• voiceFXO (101): Foreign Exchange Office

• voiceFXS (102): Foreign Exchange Subscriber

Basic configuration


Profiles

The Z-Edge 64 uses profiles to store configuration data. Profiles are similar to templates, in that they have fields for data and once they are saved they become records. Each profile uses an index, or an address, to identify it. The valid indexes, or addresses, are listed after the profile name in the output of the list command.

Note: Refer to the Zhone CLI Reference Guide for more information about ifindexes, iftypes, profiles, and records.

Interface indexes

Enter a list if-translate command to display the logical addresses and types of the physical interfaces of the Z-Edge 64. Then enter an linegroup command to find the line group identifier (lineGroupId) for each line. The lineGroupId numbers will be used for configuring applications to a specific line on the Z-Edge 64.

Tip: You can also find the lineGroupId for a line with the showlinestatus command.

The following example is from the Z-Edge 64 BH2A:.

zSH> list if-translateif-translate 1-1-2-0/ethernetcsmacdif-translate 1-1-2-0-ethernetcsmacd/otherif-translate 1-1-1-0/hdsl2if-translate 1-1-1-0-hdsl2/otherif-translate 1-1-3-0/isdnsif-translate 1-1-3-0-isdns/otherif-translate 1-1-4-0/isdnsif-translate 1-1-4-0-isdns/otherif-translate 1-1-5-0/isdnsif-translate 1-1-5-0-isdns/otherif-translate 1-1-6-0/isdnsif-translate 1-1-6-0-isdns/otherif-translate 1-1-1-0-hdsl2/atmif-translate 1-1-1-0-hdsl2/aal5if-translate 1-1-1-0-hdsl2/rfc1483if-translate 1-1-1-0/ip16 entries found.zSH> linegroup 1-1-1-0/hdsl2 lineGroupId: 4zSH> linegroup 1-1-2-0/ethernetcsmacd lineGroupId: 2zSH> linegroup 1-1-3-0/isdns lineGroupId: 6zSH> linegroup 1-1-4-0/isdns lineGroupId: 8zSH> linegroup 1-1-5-0/isdns

Configuring an Ethernet interface


lineGroupId: 10zSH> linegroup 1-1-6-0/isdns lineGroupId: 12

The following example is from the Z-Edge 64 H2A:

zSH> list if-translateif-translate 1-1-2-0/ethernetcsmacdif-translate 1-1-2-0-ethernetcsmacd/otherif-translate 1-1-3-0/voicefxsif-translate 1-1-3-0-voicefxs/otherif-translate 1-1-4-0/voicefxsif-translate 1-1-4-0-voicefxs/otherif-translate 1-1-5-0/voicefxsif-translate 1-1-5-0-voicefxs/otherif-translate 1-1-6-0/voicefxsif-translate 1-1-6-0-voicefxs/otherif-translate 1-1-1-0/hdsl2if-translate 1-1-1-0-hdsl2/otherif-translate 1-1-1-0-hdsl2/atmif-translate 1-1-1-0-hdsl2/aal5if-translate 1-1-1-0-hdsl2/rfc1483if-translate 1-1-1-0/ip16 entries found.zSH> linegroup 1-1-1-0/hdsl2 lineGroupId: 12zSH> linegroup 1-1-2-0/ethernetcsmacd lineGroupId: 2zSH> linegroup 1-1-3-0/voicefxs lineGroupId: 4zSH> linegroup 1-1-4-0/voicefxs lineGroupId: 6zSH> linegroup 1-1-5-0/voicefxs lineGroupId: 8zSH> linegroup 1-1-6-0/voicefxs lineGroupId: 10

Configuring an Ethernet interfaceConfiguring IP interfaces involves creating an ip-interface-record on the LAN interface. This profile specifies the basic IP parameters of the LAN interface. These include the IP address and netmask, and the services enabled on the interface. Each ip-interface-record is associated with a specific physical interface.

Basic configuration


Figure 5: Logical addresses of the Z-Edge 64

To create an IP interface, you need to know the logical address of the physical interface over which IP will run: 1/1/1 for WAN, and 1/1/2 for LAN.

Tip: If you use the address format (with slashes instead of dashes) when creating the IP interface, the system will recognize the physical address and automatically bind the Ethernet line group to the new IP interface over the Ethernet port.

zSH> new ip-interface-record 1/1/2/0/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {0}:rdindex: -----------> {1}:dhcp: --------------> {none}: ** read-only **addr: --------------> {0.0.0.0}: 192.168.88.200netmask: -----------> {0.0.0.0}: 255.255.255.0bcastaddr: ---------> {0.0.0.0}: 192.168.88.255destaddr: ----------> {0.0.0.0}:farendaddr: --------> {0.0.0.0}:mru: ---------------> {1500}:reasmmaxsize: ------> {0}:ingressfiltername: -> {}:egressfiltername: --> {}:pointtopoint: ------> {no}:mcastenabled: ------> {yes}:ipfwdenabled: ------> {yes}:mcastfwdenabled: ---> {yes}:natenabled: --------> {no}:bcastenabled: ------> {yes}:ingressfilterid: ---> {0}:egressfilterid: ----> {0}:ipaddrdynamic: -----> {static}:dhcpserverenable: --> {false}:....................Save new record? [s]ave, [c]hange or [q]uit: sThis IP Interface has been automatically bound to 1-1-2-0-ethernetcsmacd/otherNew record saved.

port 2

Shelf 1, slot 1LAN WAN

port 1

Configuring static routes


Note: Refer to Chapter 8, Administration, on page 97 for information on manually binding interfaces.

Verify that the Ethernet interface has been set up with the interface show command:

zSH> interface showInterface Status Rd/Address Media/Dest Address-----------------------------------------------------------------1/1/1/0/ip UP 1 0.0.0.0/32 0/351/1/2/0/ip UP 1 192.168.88.200/24 00:01:47:01:af:20

Configuring static routesStatic routes are manually configured and define paths to destinations in terms of an interface identifier or the IP address of a next-hop router or gateway.

Adding a default route

After creating the IP interface, you can create a default route to the remote device’s LAN interface using the route add command. The command uses the following syntax:

route add destination mask next-hop cost

Note: The word default can be substituted for a 0.0.0.0 destination.

The following example adds a route to the 192.168.8.0 network using 192.168.1.2 as the gateway.

route add 192.168.8.201 255.255.255.0 192.168.1.2 1

Figure 6: IP routing addresses

The following example creates a default route using the gateway 192.168.1.2:

zSH> route add default 198.168.1.2 1

192.168.88.200 192.168.1.1 192.168.1.2

Basic configuration


Deleting routes

To delete static routes, use the route delete command. The command uses the following syntax:

route delete destination mask next-hop

The following example deletes the network route to 192.168.88.201 using the gateway 192.168.1.2:

route delete 192.168.88.201 255.255.255.0 192.168.1.2

Verifying routes

To verify the connection to a remote device:

• Ping the WAN interface:

zSH> ping 192.168.1.1PING 192.168.1.1: 56 data bytes64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms64 bytes from 192.168.1.1: icmp_seq=1. time=0. ms64 bytes from 192.168.1.1: icmp_seq=2. time=0. ms64 bytes from 192.168.1.1: icmp_seq=3. time=0. msping: Interrupted by user----192.178.8.2 PING Statistics----4 packets transmitted, 10 packets receivedround-trip (ms) min/avg/max = 0/0/0

• Ping the LAN interface:


• Ping the far end device:


Configuring RIP on the WAN interface


To stop the ping, press CTRL+C.

Displaying the routing table

Use the route show command to verify that the routes were added:

zSH> route showDest Nexthop Cost Owner------------------------------------------------------------0.0.0.0/0 198.168.88.201 1 STATICLOW198.168.88.200/24 1/1/2/0/ip 1 LOCAL

traceroute command

The traceroute command allows the user to see the route that IP datagram follows from one host to another. The traceroute command is another method of verifying routes.

Configuring RIP on the WAN interfaceRouting Interface Protocol (RIP) enables dynamic routing, where routes to a specific IP addresses vary according the Z-Edge 64 routing table, which maintains the best route to a destination based on the number of hops (or metric) to a destination. Configure RIP on the Z-Edge 64 WAN interface as shown below.

RIP behavior for the system is configured in the rip-global-config profile. The Ethernet IP interface is then configured for RIP using the rip command. The Z-Edge 64 supports RIP v1 and v2. The only routing domain supported is domain 1.

Configuring RIP global defaults

The following example configures RIP global behavior on the Z-Edge 64:

1 Create a rip-global-config profile with a user-defined index number:

zSH> new rip-global-config 1Please provide the following: [q]uit.admin-state: -> {disabled}: enabledupdate-time: -> {30}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

2 Enable RIP for the system as a whole:

zSH> rip enable

3 To enable receipt of RIP version 1 or version 2 advertisements on an interface, use the rip command and specify the interface and the type of advertisements to receive:

Basic configuration


zSH> rip interface 192.168.8.21 listen v1v2

4 To enable transmission of RIP advertisements on an interface:

a zSH> rip interface 192.168.8.21 talk v2

or

b zSH> rip interface 192.168.8.21 talk v1compat

Displaying RIP information

Use the rip show command to verify that the route has been established to the correct IP address:

zSH> rip showRIP Globals----------------------------------------------------------Route Route Route Admin UpdateDomain Changes Queries State Time----------------------------------------------------------1 0 0 enabled 30----------------------------------------------------------RIP Interface Statistics---------------------------------------------------------------Route IP Recv Bad Recv Bad UpdatesDomain Address Packets Routes Sent To---------------------------------------------------------------1 198.168.8.21 0 0 0---------------------------------------------------------------RIP Interface Configuration-----------------------------------------------------------------------------------------------------------------Route IP Auth Auth DefaultSrcDomain Address Type Key Talk Listen MetricAddress Static Poison -----------------------------------------------------------------------------------------------------------------1 198.168.8.21 none (write-only) disabled disabled 0198.168.8.21 none enabled-----------------------------------------------------------------------------------------------------------------RIP Peers--------------------------------------------------------------------------------Route IP Last Recv Bad Recv BadDomain Address Update Version Packets Routes------------------------------------------------------------------------------


5

CONFIGURING DATA AND VOICE

This chapter explains how to configure ATM data and voice connections on the Z-Edge 64. This chapter has the following sections:

• Overview, page 41

• Configuring data communications, page 41

• Configuring voice communications, page 45

Note: Refer to Chapter 7, Advanced voice configuration, on page 85 for information on configuring ADPCM voice compression, POTS voice options, and ISDN B-channel data communications.

OverviewThe WAN interface can support two ATM permanent virtual circuits (PVCs):

• Data

• Voice

Voice and data communications have different networking requirements. For example, voice traffic is sensitive to delay, while data traffic is not. Because of these different needs, you must configure ATM differently for data and voice. On the Z-Edge 64, data is carried over ATM Adaption Layer 5 (AAL5) at an Unspecified Bit Rate (UBR), while voice is transported by ATM Adaption Layer 2 (AAL2) at a Constant Bit Rate (CBR).

Configuring data communicationsModify the following records to configure an ATM connection for data communications:

• ATM traffic descriptor

• ATM virtual circuit link (VCL)

• IP interface record.

Configuring Data and Voice


Updating the ATM traffic descriptor for data

Each ATM endpoint requires a traffic descriptor that defines the traffic parameters and type of service provided on ATM interfaces. Traffic descriptors are configured in atm-traf-descr records.

Note: An atm-traf-descr profile for the WAN port (with a PCR of 3659cps and UBR service as defaults) is automatically created when the Z-Edge 64 is turned on.

Calculating PCR for an interface

To calculate the PCR, divide the configured line rate of the interface by 424 (424=a 53 byte ATM cell x 8 bits per byte). For example, for an SDSL interface configured with a line speed of 2,320Kbps, calculate the PCR as follows:

2,320k/424=5471cps

Once the peak cell rate (PCR) has been set, traffic shaping ensures that the PCR limitations are enforced.

Refer to the following specifications for more information about PCR:

• ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification, 1994.

• ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification, November 1994.

The following parameters of the default atm-traf-descr profile should be modified to match your network:

zSH> update atm-traf-descr 1Please provide the following: [q]uit.td_type: -------------> {atmNoClpNoScr}:td_param1: -----------> {3659}: 5471td_param2: -----------> {0}:td_param3: -----------> {0}:td_param4: -----------> {0}:td_param5: -----------> {0}:td_service_category: -> {ubr}: for datatrnk-vcl-rate: -------> {unused}:


td_param1 The peak cell rate (PCR), measured in cells per second.

td_service_category The ATM service category.

Values: ubr - unspecified bit rate (used for data)

cbr - constant bit rate (used for voice)

Default: ubr

Configuring data communications


....................Save changes? [s]ave, [c]hange or [q]uit:s

Updating the ATM Virtual Channel Link

The Z-Edge 64 automatically creates an atm-vcl profile for the WAN port when it is turned on. The atm-vcl profile specifies the Virtual Path Identifier/Virtual Channel Identifier (VPI/VCI) pair for the ATM virtual channel link (VCL). The default atm-vcl record on the WAN interface specifies data traffic (AAL5) over the 0/35 VPI/VCI pair.

Note: You cannot modify an active VCL. If you want to make changes to the atm-vcl profile, you must first change the admin_status to down and save the updated record.

The following table list the parameters of the default atm-vcl profile:

The example below shows the default atm-vcl record created by the system:

zSH> get atm-vcl 1-1-1-0-hdsl2/atm/0/35vpi: -----------------------------> {0}vci: -----------------------------> {35}admin_status: --------------------> {up}receive_traffic_descr_index: -----> {1}transmit_traffic_descr_index: ----> {1}vcc_aal_type: --------------------> {aal5}vcc_aal5_cpcs_transmit_sdu_size: -> {9188}


admin_status Administrative status of the link.

Values: up

down

Default: up

receive_traffic_descr_index The index of the atm-traf-descr profile used for this VCL. Both the receive and transmit traffic descriptors must be the same.

transmit_traffic_descr_index The index of the atm-traf-descr profile used for this VCL. Both the receive and transmit traffic descriptors must be the same.

vcc_aal_type ATM adaption layer type.

Values: aal5 for data

aal2 for voice

Default: aal5



vcc_aal5_cpcs_receive_sdu_size: --> {9188}vcc_aal5_encaps_type: ------------> {llcencapsulation}vcl_cast_type: -------------------> {p2p}vcl_conn_kind: -------------------> {pvc}fault-detection-type: ------------> {disabled}

Updating the IP interface record

Update the default ip-interface-record on the WAN port to activate data communications.

Modify the following parameters of the ip-interface-record to configure ATM data traffic:

The following example updates the ip-interface-record for the WAN port:

zSH> update ip-interface-record 1/1/1/0/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {35}:rdindex: -----------> {1}:dhcp: --------------> {client}: ** read-only **addr: --------------> {0.0.0.0}: 192.168.1.2netmask: -----------> {0.0.0.0}: 255.255.255.0bcastaddr: ---------> {0.0.0.0}: 192.168.1.255destaddr: ----------> {0.0.0.0}:farendaddr: --------> {0.0.0.0}:


addr The IP address of the Z-Edge 64 in dotted-decimal format.

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.

bcastaddr The IP broadcast address used for sending datagrams on the (logical) interface associated with the IP interface. The broadcast address is determined by the IP address and the netmask. It should always be set to an IP address that is the network address of the interface with all ones in the host portion of the address.

mru The size, in octets, of the largest packet that can be received on the IP interface. For interfaces used for network datagrams, this is the size of the largest network datagram that can be received on the interface.

Configuring voice communications


mru: ---------------> {1500}: reasmmaxsize: ------> {0}:ingressfiltername: -> {}:egressfiltername: --> {}:pointtopoint: ------> {no}:mcastenabled: ------> {yes}:ipfwdenabled: ------> {yes}:mcastfwdenabled: ---> {yes}:natenabled: --------> {no}:bcastenabled: ------> {yes}:ingressfilterid: ---> {0}:egressfilterid: ----> {0}:ipaddrdynamic: -----> {dhcpclient}:dhcpserverenable: --> {false}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Configuring voice communicationsThe ATM Forum Loop Emulation Service (LES) specifies the use of ATM virtual circuits to transport voice information and signalling. LES uses ATM Adaption Layer 2 (AAL2) to carry voice signals over a broadband subscriber line connection such as SDSL/HDSL2. (Refer to AF-VMOA-0145.000 for more information.)

The following profiles are used to configure ATM voice connections on the Z-Edge 64:

• atm-traf-descr, or ATM traffic descriptor profile, to specify the ATM traffic and quality of service (QoS) parameters.

• atm-vcl, or ATM virtual channel link profile, to define the subscriber ATM endpoint, with the use of virtual path identifiers (VPIs) and virtual channel identifiers (VCIs).

• aal2-vcl-profile, to configure the AAL2-specific settings for the interface. aal2-vcl-profiles are automatically created when atm-vcls are configured for AAL2.

• aal2-cid-profile, to configure the AAL2 Channel Identifiers (CIDs) for a voice connection.

• aal2-audio-profiles, which specify audio settings for the voice connection. These profiles should not be changed from the default.

Creating a new ATM traffic descriptor

Create a new atm-traf-descr with a unique index for a voice connection. To calculate PCR for voice connections, use the following formula:

number of voice calls x 200 = PCR value.



For example, if the interface is carrying four voice calls, determine the PCR as follows:

4 x 200 = 800 CPS

Creating a traffic descriptor

The following example creates a new atm-traf-descr with an index value of 2:

zSH> new atm-traf-descr 2 index can be any valuePlease provide the following: [q]uit.td_type: -------------> {atmNoClpNoScr}: td_param1: -----------> {0}: 800 PCR for the interfacetd_param2: -----------> {0}:td_param3: -----------> {0}:td_param4: -----------> {0}:td_param5: -----------> {0}:td_service_category: -> {ubr}: cbr for voicetd_frame_discard: --------> {true}:cac-divider: -------------> {1}:usage-parameter-control: -> {true}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Creating a new ATM Virtual Circuit Link (VCL)

Create a new atm-vcl record specifically for voice.

Note: Each new VCL created must have a unique VPI/VCI pair to specify separate virtual channels. Create a new atm-vcl profile on the WAN interface to specify voice traffic (AAL2) over a different VPI/VCI pair than the VPI/VCI values used in the system default atm-vcl profile.

Modify the following parameters in the atm-vcl profile to enable voice communications:


vci The VCI for this VCL. This must match the remote end of the connection.

admin_status Administrative status of the link.

Values: up

down

Default: down



zSH> new atm-vcl 1-1-1-0-hdsl2/atm/0/37Please provide the following: [q]uit.vpi: ----------------------------- {0}:vci: ----------------------------- {0}: 37 must be different than data VCIadmin_status: -------------------- {down}: upreceive_traffic_descr_index: ----- {0}: 2 the td_index from atm-traf-descr 2transmit_traffic_descr_index: ---- {0}: 2vcc_aal_type: -------------------- {aal5}: aal2 for voicevcc_aal5_cpcs_transmit_sdu_size: - {9188}:vcc_aal5_cpcs_receive_sdu_size: -- {9188}:vcc_aal5_encaps_type: ------------ {llcencapsulation}:vcl_cast_type: ------------------- {p2p}:vcl_conn_kind: ------------------- {pvc}:fault-detection-type: ------------> {disabled}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

AAL2 VCL profiles

The aal2-vcl-profile defines the type of AAL2 traffic (POTS or ISDN BRI) and general AAL2 configuration settings of the VCL.

Note: When a new atm-vcl record of the type AAL2 is created, the Z-Edge 64 automatically creates an associated aal2-vcl-profile.

receive_traffic_descr_index The index of the atm-traf-descr profile used for this VCL. Both the receive and transmit traffic descriptors must be the same.

transmit_traffic_descr_index The index of the atm-traf-descr profile used for this VCL. Both the receive and transmit traffic descriptors must be the same.

vcc_aal_type ATM adaption layer type.

Values: aal5 for data

aal2 for voice

Default: aal5




The following table defines the CID ranges for voice connections based on loop emulation using AAL2 (specified in AF-VMOA-0145.000). Use these ranges when assigning CIDs in the aal2-cid-profile:

Modify the following parameters in the aal2-vcl-profile to match your network:

Table 2: CID assignments for voice connections

CIDs Description

16...127 POTS

128..159 D-channels for ISDN BRI

160..223 B-channels for ISDN BRI


app-id Application Identifier. It specifies the protocol used between the IAD and the ATM switch.

Values: caspotsonlynoelcp Loop Emulation Service using Channel Associated Signaling (CAS) without Emulated Loop Control Protocol (ELCP), which is used for POTS.

dss1brionlynoelcp Loop Emulation Service using Digital Subscriber Signaling System number 1 (DSS1) in support of ISDN BRI without ELCP.

audio-profile-identifier From the aal2-audio-profile, the audio-profile-identifier is an index number that refers to the type of audio service provided.

Values: 7 for G..711 or G.726, 44-octet packets, and silence-suppression

8 for G.711, 44-octet packets, and silence-suppression

sscs-default-type The Service Specific Convergence Sublayer (SSCS) is the portion of the convergence sublayer that is dependent on the type of traffic that is being converted. Channels that are used to carry media streams (POTS or ISDN B channels) use the SSCS defined in I.366.2. Channels that are used to carry control and management plane traffic (CCS, ELCP, ISDN D channels, and LES-EOC) use the SSCS defined in I.366.1.

Values: i3661 for ISDN D channels

i3662 for POTS and ISDN B channels

Default: i3662

max-cid-for-aal2-user-channels Maximum Channel Identifier (max-cid) value for AAL2 user channels as defined by the ATM Forum. Refer to Table 2 on page 48 for CID values.



POTS

For POTS, update the aal2-vcl-profile.

zSH> update aal2-vcl-profile 1-1-1-0-hdsl2/atm/0/37Please provide the following: [q]uit.app-id: -------------------------> {caspotsonlynoelcp}:vcc-i: --------------------------> {0}:audio-profile-identifier: -------> {7}: ATM Forum specified audio profile typesscs-default-type: --------------> {i3662}:max-cps-sdu-size: ---------------> {45}:max-number-multiplex-channels: --> {239}:min-cid-for-aal2-user-channels: -> {16}: ATM Forum specifiedmax-cid-for-aal2-user-channels: -> {127}: ATM Forum specifiedtimer-cu: -----------------------> {0}:audio-service: ------------------> {enabled}:frame-mode-data: ----------------> {disabled}:cas: ----------------------------> {enabled}: trunk-type: ---------------------> {loopstart}:pcm-encoding: -------------------> {mulaw}: alaw | mulawmax-length-frame: ---------------> {65535}:max-sdu-length: -----------------> {1536}:ras-timer: ----------------------> {0}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

ISDN

For ISDN, update the aal2-vcl-profile.

zSH> update aal2-vcl-profile 1-1-1-0-hdsl2/atm/0/37Please provide the following: [q]uit.app-id: -------------------------> {dss1brionlynoelcp}: vcc-i: --------------------------> {0}:

frame-mode-data The transport of data units as specified in the transmission error detection service of Recommendation I.366.1. This setting is inherited by the CIDs associated with the AAL2 VCL.

Values: enabled

disabled

Default: disabled

cas Channel Associated Signaling (CAS). This setting is inherited by the CIDs associated with the AAL2 VCL.

Values: enabled

disabled

Default: enabled




audio-profile-identifier: -------> {7}: ATM Forum specified audio profile typesscs-default-type: --------------> {i3661}: max-cps-sdu-size: ---------------> {45}:max-number-multiplex-channels: --> {239}:min-cid-for-aal2-user-channels: -> {160}: 128 ATM Forum specifiedmax-cid-for-aal2-user-channels: -> {223}: ATM Forum specifiedtimer-cu: -----------------------> {0}:audio-service: ------------------> {enabled}:frame-mode-data: ----------------> {enabled}: cas: ----------------------------> {disabled}: trunk-type: ---------------------> {loopstart}:pcm-encoding: -------------------> {mulaw}: alaw | mulawmax-length-frame: ---------------> {65535}:max-sdu-length: -----------------> {1536}:ras-timer: ----------------------> {0}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

AAL2 audio profiles

Caution: Do not change any aal2-audio-profile parameters during system configuration.

The aal2-audio-profile sets the audio characteristics (for example, encoding format and packet length) of AAL2 voice connections on the Z-Edge 64. The aal2-audio-profile is created by the Z-Edge 64 when you turn it on for the first time. (The AAL2 audio profiles are defined in ATM Forum specification AF-VMOA-014.000.)

The syntax is aal2-audio-profile audio-profile-identifier/preferred-ap-index. The Z-Edge 64 system supports aal2-audio-profiles 7/1, 7/2, and 8/1.

zSH> get aal2-audio-profile 7/1min-uui: ------------> {0}max-uui: ------------> {7}sdu-multiples: ------> {1}algorithm: ----------> {g711}pkt-time: -----------> {55}sequence: -----------> {55}silence-Supression: -> {enabled}packet-Length: ------> {44}

According to the ATM Forum, AAL2 audio profile identifier 7 defines Pulse Code Modulated (PCM) 64kbps voice signal that travels in 44-octet packets. A preferred ap index of 1 specifies G.711 encoding for PCM at a 8 kHz sample rate. A preferred ap index of 2 specifies G.726 ADPCM encoding.

Note: The AAL2 audio-profile-identifier will be used in the aal2-vcl-profile.The preferred-ap-index will be used in the aal2-cid-profile.



AAL2 CID profiles

Create an aal2-cid-profile for each voice line. The traffic will go over the same interface (WAN: 1/1/1/0), but each virtual voice connection will be differentiated by an AAL2 Channel Identifier (CID).

Modify the following parameters in the aal2-cid-profile to configure CID settings:

POTS

For POTS, create one aal2-cid-profile for each voice port. The syntax is new aal2-cid-profile shelf/slot/port/subport/type/vpi/vci/cid. This example is voice port 1, and it uses the lowest ATM Forum-specified CID for POTS:

zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/16Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: audio-service: ------> {enabled}:


admin-status Administrative status of the link.

Values: up

down

Default: down

sscs-type Specifies the default Service Specific Convergence Sublayer (SSCS) that the CIDs use.

Values: i3661 for ISDN D channels

i3662 for POTS and ISDN B channels

Default: i3662

frame-mode-data See description in AAL2 VCL profiles on page 47.

cas See description in AAL2 VCL profiles on page 47.

preferred-ap-index From the aal2-audio-profile, this index number defines the preferred audio encoding format.

Values: 1 : used for G.711 encoding

2 : used for G.726 compression

Default: 1



frame-mode-data: ----> {disabled}: cas: ----------------> {enabled}: pcm-encoding: -------> {mulaw}: max-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

This example is voice port 2, and it uses the next available CID:

zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/17Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: audio-service: ------> {enabled}: frame-mode-data: ----> {disabled}: cas: ----------------> {enabled}: pcm-encoding: -------> {mulaw}: max-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved


zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/18Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: audio-service: ------> {enabled}: frame-mode-data: ----> {disabled}: cas: ----------------> {enabled}: pcm-encoding: -------> {mulaw}: max-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved


zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/19Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: audio-service: ------> {enabled}:



frame-mode-data: ----> {disabled}: cas: ----------------> {enabled}: pcm-encoding: -------> {mulaw}: max-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

ISDN

For ISDN, create a aal2-cid-profile for the D channel. The B channels’ CIDs will be automatically generated once the D channel aal2-cid-profile is saved. Then update the aal2-cid-profiles to configure the B channels.

First, create a new aal2-cid-profile for the D channel using one of the ATM Forum-specified CIDs:

zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/128Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: i3661 for D channelsaudio-service: ------> {enabled}: frame-mode-data: ----> {disabled}: enabledcas: ----------------> {enabled}: disabledpcm-encoding: -------> {mulaw}: alawmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

After saving the new aal2-cid-profile for the ISDN D channel, the aal2-cid-profiles for the associated ISDN B channels are automatically created. You can see the aal2-cid-profiles created for the B channels by issuing a list command:

zSH> list aal2-cid-profileaal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/128aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/160aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/161

Modify the aal2-cid-profiles that have been automatically created for the ISDN B channels to match the pcm-encoding of the aal2-cid-profile for the D channel:

zSH> update aal2-cid-profile 1-1-1-0/atm/0/37/160Please provide the following: [q]uit.admin-status: -------> {up}:sscs-type: ----------> {i3662}: this is for B channels



audio-service: ------> {enabled}:frame-mode-data: ----> {enabled}:cas: ----------------> {disabled}:pcm-encoding: -------> {mulaw}: alawmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

zSH> update aal2-cid-profile 1-1-1-0/atm/0/37/161Please provide the following: [q]uit.admin-status: -------> {up}:sscs-type: ----------> {i3662}: this is for B channelsaudio-service: ------> {enabled}:frame-mode-data: ----> {enabled}:cas: ----------------> {disabled}:pcm-encoding: -------> {mulaw}: alawmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Subscriber profiles

A subscriber profile defines the basic configuration of the subscriber’s physical interface. Subscriber profiles use an index in the form subId/lineGroupId, where:

• subId (subscriber identifier) is a unique index for the subscriber and is used to associate voice and data profiles with a subscriber.

• lineGroupId is the index number of the WAN port.

The subscriber supports the following parameters (all others should be left at their default values):


id User-defined value for the subscriber.

line-group-id The line group identifier of the WAN port.

iad-type Identifies the type of IAD used by the subscriber.

Values: zedge64s



POTS

Use the linegroup command to get the line group identifier value for the WAN interface on the Z-Edge 64 H2A:

zSH> linegroup 1-1-1-0/hdsl2 lineGroupId: 12

The following example configures a subscriber record with a subID of 1 (which is user-defined) and a lineGroupId of 12 (which is the linegroupID of the WAN port):

zSH> new subscriber 1/12Please provide the following: [q]uit.id: ----------------------> {0}: 1line-group-id: -----------> {0}: 12name-group-id: -----------> {}:service-provider-id: -----> {0}: iad-type: ----------------> {NONE(0)}: zedge64sline-rate-limit: ---------> {0}: 64000 for a 64kbps voice linecapable-line-rate-limit: -> {0}: 64000 for a 64kbps voice line....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

ISDN

Use the linegroup command to get the line group identifier value for the WAN interface on the Z-Edge 64 BH2A:


The following example configures a subscriber record with a subID of 1 (which is user-defined) and a lineGroupId of 4 (which is the linegroupID of the WAN port):

ZSH> new subscriber 1/4Please provide the following: (q=quit)id: ------------------------>[0]: 1line-group-id: ------------->[0]: 4name-group-id: ------------->[]: oakservice-provider-id: ------->[0]:

line-rate-limit The maximum line rate (in bits per second) that the subscriber is provisioned to receive from the service provider. This value is the total line rate or bandwidth of the subscriber connection, including voice and data.

capable-line-rate-limit The line rate capability.




iad-type: ------------------>[NONE(0)]: zedge64sline-rate-limit: ----------->[0]: 144000 capable-line-rate-limit: --->[0]: 144000.......................Save new record? (s=save/c=change/q=quit): sNew record saved.

Subscriber voice profiles

After saving the subscriber profile, create subscriber-voice profiles to associate the subscriber-side and network-side endpoints.

Note: A subscriber profile must exist before subscriber-voice profiles can be added.

The subscriber-voice profile uses an index in the syntax subId/lineGroupId/subVoiceId, where:

• subId is the user-specified value used to create the subscriber profile. See Subscriber profiles on page 54.

• lineGroupId is the line group identifier for the ATM side of the connection. In this case, the WAN interface.

• subVoiceId is an user-defined index number that is unique for the particular subscriber voice record.

Note: The lineGroupIds for the WAN interfaces on Z-Edge 64 H2A units and Z-Edge 64 BH2A units are different.

Modify the following parameters in the subscriber-voice profile to enable voice service:


voice-connection-type This describes the connection type between the two voice end points.

Values: potstoaal2

isdntoaal2

voice-endpoint1-addr-index The index for the subscriber-side voice endpoint, usually POTS or ISDN.

voice-endpoint2-addr-index The index for the network-side voice endpoint, usually AAL2.



POTS

Use the linegroup command to get the line group identifier value for the WAN interface on the Z-Edge 64 H2A:


This example creates a subscriber-voice profile for subscriber 1 (configured in Subscriber profiles on page 54), line group 12 (the line group identifier of the WAN interface), with a user-defined voice index value:

zSH> new subscriber-voice 1/12/1 subId/lineGroupId/subVoiceIdPlease provide the following: (q=quit)voice-connection-type: ---------->[aal2togr303]: potstoaal2voice-endpoint1-addr-index: ----->[0]: 1 user-defined index for the subscriber-voice-pots profilevoice-endpoint2-addr-index: ----->[0]: 2 user-defined index for the subscriber-voice-aal2 profilevoice-connection-description: --->[]: voice-admin-status: ------------->[disabled]: .......................Save new record? (s=save/c=change/q=quit): sNew record saved.

After creating the subscriber-voice-profile, the system automatically creates subscriber voice endpoint profiles for the subscriber side (subscriber-voice-pots profiles) and network side (subscriber-voice-aal2 profiles).

ISDN

Use the linegroup command to get the line group identifier value for the WAN interface on the Z-Edge 64 BH2A:


Create three subscriber-voice profiles per ISDN voice port

voice-connection-description A text string describing this voice call entry. This value is not used by the system and is provided for operator reference only.

voice-admin-status The administrative state for this connection.

enabled

disabled

Default: disabled




This example creates a subscriber-voice profile for subscriber 1 (configured in Subscriber profiles on page 54), line group 4 (the line group identifier of the WAN interface), with a user-defined voice index value of 1:

zSH> new subscriber-voice 1/4/1 subId/lineGroupId/subVoiceIdPlease provide the following: (q=quit)voice-connection-type: ---------->[aal2togr303]: isdntoaal2voice-endpoint1-addr-index: ----->[0]: 1 user-defined index for the subscriber-voice-isdn profilevoice-endpoint2-addr-index: ----->[0]: 2 user-defined index for the subscriber-voice-aal2 profilevoice-connection-description: --->[]: voice-admin-status: ------------->[disabled]: .......................Save new record? (s=save/c=change/q=quit): sNew record saved.





After creating the subscriber-voice profiles, the system automatically creates subscriber voice endpoint profiles for the subscriber side (subscriber-voice-isdn profiles) and network side (subscriber-voice-aal2 profiles).

zSH> list subscriber-voice-isdnsubscriber-voice-isdn 1subscriber-voice-isdn 3subscriber-voice-isdn 5



zSH> list subscriber-voice-aal2subscriber-voice-aal2 2subscriber-voice-aal2 4subscriber-voice-aal2 6

Subscriber-voice endpoint profiles

After the subscriber-voice profiles have been created, you must update the subscriber voice endpoint profiles. On Z-Edge 64 H2A systems, there is the subscriber-voice-aal2 profile on the network side and the subscriber-voice-pots profiles on the subscriber side. On Z-Edge 64 BH2A systems, there is the subscriber-voice-aal2 profile on the network side and the subscriber-voice-isdn profile on the subscriber side.

POTS

Update the subscriber voice endpoint profile for the network side of the connection:

zSH> update subscriber-voice-aal2 2 voice-endpoint1-addr-index from subscriber-voice profilePlease provide the following: [q]uit.voice-aal2-line-group-id: -> {}: 12 line group ID of WAN interfacevoice-aal2-vpi: -----------> {}: 0 VPI defined in atm-vcl profilevoice-aal2-vci: -----------> {}: 37 VCI defined in atm-vcl profilevoice-aal2-cid: -----------> {}: 16 CID defined in aal2-cid-profile....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Update the subscriber voice endpoint profile for the subscriber side of the connection. Use the linegroup command to get the ifIndex value for the POTS interfaces on the Z-Edge 64 H2A:

zSH> linegroup 1-1-3-0/voicefxs lineGroupId: 4

Modify the following parameter in the subscriber-voice-pots profile to enable POTS subscriber-side endpoints:

zSH> update subscriber-voice-pots 1Please provide the following: [q]uit.voice-pots-line-group-id: -> {0}: 4 ifindex for the line....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.


voice-pots-line-group-id The line group identifier for the POTS line, equal to the ifindex of the line. The default value is 0.



ISDN

For ISDN, update the subscriber-voice-aal2 profiles for each voice port. First, update the subscriber-voice-aal2 profile for the D channel:

zSH> update subscriber-voice-aal2 2 voice-endpoint1-addr-index from subscriber-voice profilePlease provide the following: [q]uit.voice-aal2-line-group-id: -> {0}: 6 ifindex of the voice portvoice-aal2-vpi: -----------> {0}:voice-aal2-vci: -----------> {0}: 37 from the atm-vcl profilevoice-aal2-cid: -----------> {0}: 128 from the aal2-cid profile....................Save new record? [s]ave, [c]hange or [q]uit: sRecord updated.

Then update the subscriber-voice-aal2 profile for the first B channel:

zSH> update subscriber-voice-aal2 4Please provide the following: [q]uit.voice-aal2-line-group-id: -> {0}: 6 ifindex of the voice portvoice-aal2-vpi: -----------> {0}:voice-aal2-vci: -----------> {0}: 37 from the atm-vcl profilevoice-aal2-cid: -----------> {0}: 160 from the aal2-cid profile....................Save new record? [s]ave, [c]hange or [q]uit: sRecord updated.

Then update the subscriber-voice-aal2 profile for the second B channel:

zSH> update subscriber-voice-aal2 6Please provide the following: [q]uit.voice-aal2-line-group-id: -> {0}: 6 ifindex of the voice portvoice-aal2-vpi: -----------> {0}:voice-aal2-vci: -----------> {0}: 37 from the atm-vcl profilevoice-aal2-cid: -----------> {0}: 161 from the aal2-cid profile....................Save new record? [s]ave, [c]hange or [q]uit: sRecord updated.

Use the linegroup command to get the line group identifier value for the ISDN interfaces on the Z-Edge 64 BH2A:

zSH> linegroup 1-1-3-0/isdns lineGroupId: 6

Modify the following parameters in the subscriber-voice-isdn profiles to enable ISDN subscriber-side endpoints:



The following example updates the subscriber-voice-isdn profile for the D channel:

zSH> update subscriber-voice-isdn 1Please provide the following: [q]uit.voice-isdn-line-group-id: -> {}: 6 ifindex for the linevoice-isdn-port-type: --> {0}: isdndchannelvoice-isdn-channel-id : --> {0}: 1 D channel....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

The following example updates the subscriber-voice-isdn profile for the first B-channel:

zSH> update subscriber-voice-isdn 3Please provide the following: [q]uit.voice-isdn-line-group-id: -> {}: 6 ifindex for the linevoice-isdn-port-type: --> {0}: isdnbchannelvoice-isdn-channel-id : --> {0}: 2 first B channel....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

The following example updates the subscriber-voice-isdn profile for the second B-channel:

zSH> new subscriber-voice-isdn 5Please provide the following: [q]uit.voice-isdn-line-group-id: -> {}: 6 ifindex for the linevoice-isdn-port-type: --> {0}: isdnbchannel


voice-isdn-line-group-id The line group identifier for the ISDN line, equal to the ifindex of the line

voice-isdn-port-type Defines the type of ISDN: D channel or B channel.

Values: isdndchannel

isdnbchannel

Default: 0 (none)

voice-isdn-channel-id The channel identifier for the connection.

Values: 1 D channel

2 B channel

3 B channel

Default: 0 (none)



voice-isdn-channel-id : --> {0}: 3 second B channel....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Activating voice connections

Enable the voice-admin-status parameter in all of the subscriber-voice profiles to activate the voice connection:

zSH> update subscriber-voice 1/4/1 Please provide the following: [q]uitvoice-connection-type: --------> {pots2aal2}:voice-endpoint1-addr-index: ---> {1}: voice-endpoint2-addr-index: ---> {2}: voice-connection-description: -> {}: voice-admin-status: -----------> {disabled}: enabled....................Save new record? [s]ave, [c]hange or [q]uit: sRecord updated.




6

ADVANCED IP CONFIGURATION

This chapter details configuring advanced IP applications for Z-Edge 64. It includes the following topics:

• Configuring NAT on the WAN interface, page 63

• Configuring the Z-Edge 64 as a DHCP server, page 64

• Creating DHCP client identifiers, page 72

• Transparent bridging, page 73

• Configuring DNS resolver, page 76

• PPP over ATM, page 78

Configuring NAT on the WAN interfaceNetwork Address Translation (NAT) translates outbound traffic from the Z-Edge 64 so that IP addresses are conserved and the network behind the Z-Edge 64 is easier to manage. NAT allows multiple clients on a LAN to access the WAN with only one valid IP address.

Modify the following parameters in the ip-interface-record for the WAN interface to enable NAT:

To enable NAT, use the following commands:

zSH> update ip-interface-record 1-1-1-0/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {35}:rdindex: -----------> {1}:dhcp: --------------> {client}: ** read-only **addr: --------------> {192.168.8.21}:


natenabled Network address translation enabled.

Values: no

yes

Default: no

Advanced IP configuration


netmask: -----------> {255.255.255.0}:bcastaddr: ---------> {192.168.8.22}:destaddr: ----------> {0.0.0.0}:farendaddr: --------> {0.0.0.0}:mru: ---------------> {1500}:reasmmaxsize: ------> {0}:ingressfiltername: -> {}:egressfiltername: --> {}:pointtopoint: ------> {no}:mcastenabled: ------> {yes}:ipfwdenabled: ------> {yes}:mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: yes bcastenabled: ------> {yes}: ingressfilterid: ---> {0}:egressfilterid: ----> {0}:ipaddrdynamic: -----> {dhcpclient}:dhcpserverenable: --> {false}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Configuring the Z-Edge 64 as a DHCP serverAs a DHCP server, Z-Edge 64 can assign temporary (leased) IP addresses to client PCs. Each DHCP client PC sends a request to the Z-Edge 64 for an IP address lease. The Z-Edge 64 then assigns an IP address and lease time to the client PC. The Z-Edge 64 keeps track of a range of assignable IP addresses from a subnetwork.

Figure 1: Z-Edge 64 as DHCP server

The Z-Edge 64 DHCP server can be enabled on the LAN interface (port 2), and it supports the following types of DHCP configurations:

WAN

DHCPclients

DHCPserver

LAN

192.168.1.6

port 1:192.168.1.2

port 2:192.168.1.1

192.168.1.8

192.168.1.7

network:192.168.1.0/24

Configuring the Z-Edge 64 as a DHCP server


• Dynamic address allocation, where the server chooses and allocates an IP address with a finite lease. Dynamic addressing allows a device to be assigned an IP address every time it connects to the network. If a device reconnects to the network while the address lease is still active, the Z-Edge 64 assigns it the same address. If the lease has expired, the device gets a new address.

• Static address allocation, where the server allocates the same IP address every time a device connects to the network.

DHCP server profiles and scope

To configure the DHCP server on the Z-Edge 64 use the following profiles:

• dhcp-server-options—Configures a default profile that is used to generate default configurations for networks that are not explicitly configured.

• dhcp-server-subnet—Defines options for a specific network that is being managed by the DHCP server. Settings in the dhcp-server-subnet record override the default address pool set up by the dhcp-server-options record.

• dhcp-server-group—Defines options for a set of clients in a given domain. Inclusion of a given client into the group is based on a substring match of either the client’s DHCP vendor class identifier, its DHCP client identifier values, or both. The scope of a group object always overrides those of a subnet object for any DHCP client lease.

• dhcp-server-host—Defines options for a specific host within a given domain.

• ip-interface-record—enables DHCP on the interface. The IP address defined in the ip-interface-record is used to determine the DHCP address pool for the attached network.

The DHCP server looks for configuration settings in order from the most specific record (the dhcp-server-host) to the most general (the dhcp-server-options record). It uses parameter settings in the following order:

1. dhcp-server-host

2. dhcp-server-group

3. dhcp-server-subnet

4. dhcp-server-options

If a parameter is set in multiple profiles (for example, lease times or default routers), the Z-Edge 64 uses the settings that are in the most specific record. This means that the DHCP server could use parameter settings in multiple records (if, for example, all client lease times were set in the dhcp-server-options record, and address ranges were set in the dhcp-server-subnet records.)



If only the dhcp-server-options record exists, the Z-Edge 64 uses those settings as the default for all DHCP server interfaces.

Setting DHCP server options

At startup, the Z-Edge 64 creates a default dhcp-server-options record. This profile defines global options for the Z-Edge 64 DHCP server.

The following example shows the dhcp-server-options profile with its default values:

zSH> get dhcp-server-options 0Please provide the following: [q]uit.lease-time: -----> {2700}:min-lease-time: -> {1800}:max-lease-time: -> {3600}:reserve-start: --> {5}: reserve-end: ----> {5}: restart: --------> {no}: ....................

The dhcp-server-options profile supports the following parameters (all others should be left at their default values):


lease-time The global default time in seconds that will be assigned to a DHCP lease if the client requesting the lease does not request a specific expiration time.

min-lease-time The minimum expiration time in seconds that will be assigned to a DHCP lease by the server, regardless of the value specified by a client.

Values: -1 to 2147483647

-1 indicates the parameter should be ignored.

Default: 0

max-lease-time The maximum time in seconds that will be assigned to a lease regardless of the value specified by a client.

Values: -1 to 2147483647.

-1 indicates the parameter should be ignored.

Default: 86400



The following example changes the dhcp-server-options record to specify that each DHCP server reserve the first 10 addresses and the last 10 addresses in a network and does not include them in the DHCP server address pool.

zSH> update dhcp-server-options 0Please provide the following: [q]uit.lease-time: -----> {43200}:min-lease-time: -> {0}:max-lease-time: -> {86400}:reserve-start: --> {5}: 10reserve-end: ----> {5}: 10restart: --------> {no}: ....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

In this example, if a DHCP server on the 192.168.9.0 network reserved the first 10 addresses and last 10 addresses, it would assign addresses from 192.168.9.10 to 192.168.9.245.

Creating DHCP server subnet options

The dhcp-server-subnet profile allows you to define options for a specific network that is being managed by the DHCP server. All subnets within a routing domain must be unique, so a given subnet object will provide options for exactly one connected network.

reserve-start The default number of IP addresses, at the beginning of the Z-Edge 64 subnet IP address space, that are reserved by the DHCP server. To override this default, create a specific subnet rule for each subnet that needs to be handled differently.

reserve-end The default number of IP addresses at the end of the Z-Edge 64 ‘s subnet IP address space that are reserved by the DHCP server. To override this default, create a specific subnet rule for each subnet that needs to be handled differently.




The dhcp-server-subnet profile supports the following parameters (all others should be left at their default values):

The following example defines a DHCP server subnet profile that is set up as follows:

• Defines a single DHCP address pool with 11 addresses.

• Defines a default router.

• Defines a boot server and a boot filename.


network The IP network address of this subnet.

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.

domain The routing domain to which this subnet, group, or host parameter applies.

range1-start, range2-start, range3-start, range4-start

The starting IP address of an address pool in this subnet. If either the start or end range has a value of 0 then the entire address pool is ignored.

range1-end, range2-end, range3-end, range4-end

The ending IP address of an address pool in this subnet. If either the start or end range has a value of 0, then the entire address pool is ignored.

default-lease-time The default time, in seconds assigned to a lease if the client requesting the lease does not request a specific expiration time.

min-lease-time See description in dhcp-server-options profile.

max-lease-time See description in dhcp-server-options profile.

boot-server The IP address of the server from which the initial boot file (specified in the bootfile parameter) is to be loaded.

bootfile The name of the initial boot file loaded by the client. The filename should be recognizable to the file transfer protocol that the client will be using to load the file.

default-router The IP address of the client default gateway.

primary-name-server The IP address of the primary domain name server that the client should use for DNS resolution.

secondary-name-server The IP address of the secondary domain name server that the client should use for DNS resolution.

domain-name The name of the DNS domain.



• Defines a domain name.

• Defines two DNS servers.

• Uses the minimum, maximum, and default lease time (by accepting the default settings for the default-lease-time, min-lease-time, and max-lease-time).

zSH> new dhcp-server-subnet 12Please provide the following: [q]uit.network: ---------------> {0.0.0.0}: 192.168.1.0netmask: ---------------> {0.0.0.0}: 255.255.255.0domain: ----------------> {0}: 1range1-start: ----------> {0.0.0.0}: 192.168.1.10range1-end: ------------> {0.0.0.0}: 192.168.1.20range2-start: ----------> {0.0.0.0}:range2-end: ------------> {0.0.0.0}:range3-start: ----------> {0.0.0.0}:range3-end: ------------> {0.0.0.0}:range4-start: ----------> {0.0.0.0}:range4-end: ------------> {0.0.0.0}:default-lease-time: ----> {-1}:min-lease-time: --------> {-1}:max-lease-time: --------> {-1}:boot-server: -----------> {0.0.0.0}: 192.168.1.55bootfile: --------------> {}: zedgebh2a.bindefault-router: --------> {0.0.0.0}: 192.168.1.1 primary-name-server: ---> {0.0.0.0}: 192.168.8.21secondary-name-server: -> {0.0.0.0}: 201.23.20.2domain-name: -----------> {}: zhone.com....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Creating dhcp-server-group profile

The dhcp-server-group defines options for a set of clients in a given domain. Inclusion of a given client into the group is based on a substring match of either the client’s DHCP vendor class identifier, its DHCP client identifier values, or both. The scope of a group object always overrides those of a subnet object for any DHCP client lease.

Modify the following parameters to create a new dhcp-server-group profile:


name The DHCP server group name.



zSH> new dhcp-server-group 1Please provide the following: [q]uit.name: ------------------> {}: group1domain: ----------------> {0}:vendor-match-string: ---> {}: 'oakland' this is converted to an octet stringvendor-match-offset: ---> {0}:vendor-match-length: ---> {-1}:client-match-string: ---> {}: 'oakland'this is converted to an octet stringclient-match-offset: ---> {0}:client-match-length: ---> {-1}:default-lease-time: ----> {-1}:min-lease-time: --------> {-1}:max-lease-time: --------> {-1}:boot-server: -----------> {0.0.0.0}:bootfile: --------------> {}:default-router: --------> {0.0.0.0}:primary-name-server: ---> {0.0.0.0}:secondary-name-server: -> {0.0.0.0}:domain-name: -----------> {}:....................Save new record? [s]ave, [c]hange or [q]uit: sRecord created.

Creating dhcp-server-host profile

The dhcp-server-host defines options for a specific host within a given domain.

Set the following parameters in the dhcp-server-host profile:

zSH> new dhcp-server-host 1Please provide the following: [q]uit.name: ------------------> {}: host1

vendor-match-string The vendor class identifier match string that determines which clients should be placed in the group.

client-match-string Client identifier match string that determines which clients should be placed in this group.



name The DHCP host name for the client

hwaddr The MAC address of the network interface that was used to acquire the lease.

clientId The DHCP client identifier



domain: ----------------> {0}:hardware-address: ------> {}: 09:00:07:A9:B2:EBclient-identifier: -----> {}: ‘clientgroup1’ipaddr1: ---------------> {0.0.0.0}:ipaddr2: ---------------> {0.0.0.0}:ipaddr3: ---------------> {0.0.0.0}:ipaddr4: ---------------> {0.0.0.0}:default-lease-time: ----> {-1}:min-lease-time: --------> {-1}:max-lease-time: --------> {-1}:boot-server: -----------> {0.0.0.0}:bootfile: --------------> {}:default-router: --------> {0.0.0.0}:primary-name-server: ---> {0.0.0.0}:secondary-name-server: -> {0.0.0.0}:domain-name: -----------> {}:....................Save new record? [s]ave, [c]hange or [q]uit: sRecord created.

Enabling DHCP server

The following example enables the DHCP server on an IP interface associated with the Z-Edge 64 LAN port (2) in shelf 1, slot 1, subport 0:

Modify the following parameters in the ip-interface-record to enable DHCP server (all others should be left at their default values):

zSH> update ip-interface-record 1-1-2-0/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {0}:rdindex: -----------> {1}:dhcp: --------------> {client}: serveraddr: --------------> {0.0.0.0}: 192.168.88.200netmask: -----------> {255.255.255.0}:bcastaddr: ---------> {192.168.88.255}:destaddr: ----------> {0.0.0.0}:


dhcp Indicates whether this interface is a DHCP client, a DHCP server, both, or neither.

Values: none

client

server

both

Default: none

address The IP address of LAN port.



farendaddr: --------> {0.0.0.0}:mru: ---------------> {1500}:reasmmaxsize: ------> {0}:ingressfiltername: -> {}:egressfiltername: --> {}:pointtopoint: ------> {no}:mcastenabled: ------> {yes}:ipfwdenabled: ------> {yes}:mcastfwdenabled: ---> {yes}:natenabled: --------> {no}:bcastenabled: ------> {yes}:ingressfilterid: ---> {0}:egressfilterid: ----> {0}:ipaddrdynamic: -----> {static}:dhcpserverenable: --> {false}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Creating DHCP client identifiersThe dhcp-client-lease-resource is automatically created by default. Update the dhcp-client-lease-resource profile to create specific client identifiers or groups. The DHCP client identifier (dhcpClientID) value is passed on to the DHCP server for classifying a client or group of clients.

The syntax for updating the dhcp-client-lease-resource profile is update dhcp-client-lease-resource shelf/slot/interface number.

Note: The dhcpClientId can be entered as a text string using single quotes.

zSH> update dhcp-client-lease-resource 1/1/10Please provide the following: [q]uit.serverName: ----> {}:renew: ---------> {0}:rebind: --------> {0}:bootFile: ------> {}:tftp: ----------> {0.0.0.0}:hostName: ------> {}:domainName: ----> {}:vendorClassId: -> {fe:5a:48:4f:4e:45:52:55:4c:45:53:fe:00:00:00:0b:00:00:00:01:00:00:00:03:00:00:00:06:00:00:00:01:00:00:00:04:00:00:00:01:00:00:15:80:00:00:00:01:00:00:00:02:00:00:00:01:00:00:00:02:fe:00:00:00:06:31:31:30:33:36:32:fe:00:00:00:19:5a:45:44:47:45:36:34:42:48:32:41:20:43:41:4e:20:31:2e:33:2e:30:2e:32:2e:61:fe:00:00:00:04:50:61:73:73:fe:4e:fe}:


dhcpClientId DHCP client identifier.

Transparent bridging


dhcpClientId: --> {}: 'clientgroup1'state: ---------> {invalid}:dnsArray has 5 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? nUsing current values for elements 1-5routersArray has 5 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? nUsing current values for elements 1-5....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

The system displays the vendorclassID and the dhcpclientID as octet strings:

zSH> get dhcp-client-lease-resource 1/1/10serverName: ----> {}renew: ---------> {0}rebind: --------> {0}bootFile: ------> {}tftp: ----------> {0.0.0.0}hostName: ------> {}domainName: ----> {}vendorClassId: -> {fe:5a:48:4f:4e:45:52:55:4c:45:53:fe:00:00:00:0b:00:00:00:01:00:00:00:03:00:00:00:06:00:00:00:01:00:00:00:04:00:00:00:01:00:00:15:80:00:00:001:00:00:00:02:00:00:00:01:00:00:00:02:fe:00:00:00:06:31:31:30:33:36:32:fe:00:00:00:19:5a:45:44:47:45:36:34:42:48:32:41:20:43:41:4e:20:31:2e:33:2e:30:2e:32:2e:61:fe:00:00:00:04:50:61:73:73:fe:4e:fe}dhcpClientId: --> {63:6c:69:65:6e:74:67:72:6f:75:70:31} this is the DHCP client-identifier in octet form. It will be used in the dhcp-server-lease profile of the system’s DHCP server.state: ---------> {invalid}dnsArray has 5 elements. Display [a]ll, [n]one, a [s]ubset, or [q]uit? nroutersArray has 5 elements. Display [a]ll, [n]one, a [s]ubset, or [q]uit? n

Transparent bridgingZ-Edge 64 units can use transparent bridging across Ethernet/802.3 networks. As a transparent bridge, the unit’s presence and operation are not visible to other IP network hosts.

Note: Your personal computer, the Z-Edge 64 unit on which you created the bridge-interface-record profiles, and the destination terminal equipment must be in the same subnet for transparent bridging to be functional.

Transparent bridging is not configurable over ZMS.

Modify the following parameters of the atm-vcl profile to enable transparent bridging:



Modify the following parameters of the bridge-interface-record profile to enable transparent bridging:

Setting up transparent bridging

Follow these steps to set up transparent bridging:

1 First bring down the atm-vcl since you cannot modify an active VCL:

zSH> update atm-vcl 1-1-1-0-hdsl2/atm/0/35Please provide the following: [q]uit.vpi: -----------------------------> {0}: ** read-only **vci: -----------------------------> {35}: ** read-only **admin_status: --------------------> {up}: downreceive_traffic_descr_index: -----> {1}:transmit_traffic_descr_index: ----> {1}:vcc_aal_type: --------------------> {aal5}:vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:vcc_aal5_cpcs_receive_sdu_size: --> {9188}:vcc_aal5_encaps_type: ------------> {llcencapsulation}:vcl_cast_type: -------------------> {p2p}:vcl_conn_kind: -------------------> {pvc}:fault-detection-type: ------------> {disabled}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.


admin_status The administrative status of the VCL.

Values: up

down

vcc_aal5_encaps_type The type of data encapsulation used over the AAL5 SSCS layer.

Values: llcencapsulation sets logical link control encapsulation over AAL5.

other sets RFC 1483 multiprotocol encapsulation over AAL5.

Default: llcencapsulation


vci Specifies the ATM virtual channel identifier. If the bridge interface is not an ATM virtual channel, this field is ignored.

bridgeLowerIfIndex Defines the bridge interface.

Transparent bridging


2 Set up bridged encapsulation over AAL5 by setting the vcc_aal5_encaps_type parameter in the atm-vcl profile to other:

zSH> update atm-vcl 1-1-1-0-hdsl2/atm/0/35Please provide the following: [q]uit.vpi: -----------------------------> {0}: ** read-only **vci: -----------------------------> {35}: ** read-only **admin_status: --------------------> {down}:receive_traffic_descr_index: -----> {1}:transmit_traffic_descr_index: ----> {1}:vcc_aal_type: --------------------> {aal5}:vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:vcc_aal5_cpcs_receive_sdu_size: --> {9188}:vcc_aal5_encaps_type: ------------> {llcencapsulation}: othervcl_cast_type: -------------------> {p2p}:vcl_conn_kind: -------------------> {pvc}:fault-detection-type: ------------> {disabled}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

3 Bring the VCL back up:

zSH> update atm-vcl 1-1-1-0-hdsl2/atm/0/35Please provide the following: [q]uit.vpi: -----------------------------> {0}: ** read-only **vci: -----------------------------> {35}: ** read-only **admin_status: --------------------> {down}: upreceive_traffic_descr_index: -----> {1}:transmit_traffic_descr_index: ----> {1}:vcc_aal_type: --------------------> {aal5}:vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:vcc_aal5_cpcs_receive_sdu_size: --> {9188}:vcc_aal5_encaps_type: ------------> {other}:vcl_cast_type: -------------------> {p2p}:vcl_conn_kind: -------------------> {pvc}:fault-detection-type: ------------> {disabled}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

4 Create bridge profiles for both ends of the connection—one for DSL (WAN) and for Ethernet (LAN). The Zhone interface type for bridged encapsulation is bridge.

zSH> new bridge-interface-record 1-1-1-0-hdsl2/bridgePlease provide the following: [q]uit.vpi: ----------------> {0}:vci: ----------------> {0}: 35portGroupIndex: -----> {0}:stpenabled: ---------> {false}:bridgefilterindex: --> {0}:bridgeLowerIfIndex: -> {0}: 1 ....................



Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

zSH> new bridge-interface-record 1-1-2-0-ethernetcsmacd/bridgePlease provide the following: [q]uit.vpi: ----------------> {0}:vci: ----------------> {0}: 35portGroupIndex: -----> {0}:stpenabled: ---------> {false}:bridgefilterindex: --> {0}:bridgeLowerIfIndex: -> {0}: 1 ....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

5 After saving the bridge-interface-record, bind the bridge profiles to the appropriate line group.

On the WAN side, bind the bridge profile to the RFC 1483 line group:

zSH> stack bindEnter the upper layer: 1-1-1-0-hdsl2/bridgeEnter the lower layer: 1-1-1-0-hdsl2/rfc1483Stack bind successful.

On the LAN side, bind the bridge profile to the other line group:

zSH> stack bindEnter the upper layer: 1-1-2-0-ethernetcsmacd/bridgeEnter the lower layer: 1-1-2-0-ethernetcsmacd/otherStack bind successful.

6 Verify that bridging has been set up by PINGing over the transparent bridge you created to a destination IP address.

Configuring DNS resolverDomain Name Server (DNS) maps domain names to IP addresses, enabling the system to reach destinations when it knows only the domain name of the destination. DNS configuration uses the following profiles:

• resolver—Configures the global DNS resolver, including the DNS search order, default domain name, and list of nameserver addresses. The DNS settings in this record can be used for local applications by administrators on the system, such as traceroute or ping.

• hosts—A replacement for the Unix local hosts table. Up to four host aliases can be defined for each host entry. Settings in the resolver record determine whether the hosts table is searched.

Configuring DNS resolver


The resolver profile supports the following parameters (all others should be left at their default values):

The following example creates a resolver record for a routing domain:

zSH> new resolver 1Please provide the following: [q]uit.query-order: -------> {hosts-first}: domain: ------------> {}: zhone.comfirst-nameserver: --> {0.0.0.0}: 192.168.8.21second-nameserver: -> {0.0.0.0}: 201.23.20.2third-nameserver: --> {0.0.0.0}:....................Save new record? [s]ave, [c]hange or [q]uit: sRecord created.


query-order The kind of resolver query for this routing domain.

Values: hosts-first searches the local hosts table first then the list of nameservers.

dns-first searches the list of nameservers first then the local hosts table.

dns-only searches only the list of nameservers.

Default: hosts-first

domain The routing domain to which this host parameter applies. The default is an empty string.

The only routing domain supported is domain 1.

first-nameserver The IP address of the first or primary nameserver for this routing domain. The default value is 0.0.0.0.

second-nameserver The IP address of the second or secondary nameserver for this routing domain. This nameserver is queried if the first nameserver cannot resolve the query. The default value is 0.0.0.0.

third-nameserver The IP address of the third or tertiary nameserver for this routing domain. This nameserver is queried if the first nameserver cannot resolve the query. The default value is 0.0.0.0.



Optionally, you can create a hosts profile after the resolver profile has been created. The syntax is new hosts routingdomain/ipoctet1/ipoctet2/ipoctet3/ipoctet4.

The hosts profile supports the following parameters (all others should be left at their default values):

zSH> new hosts 1/192/168/8/32Please provide the following: [q]uit.hostname: ---> {}: www.zhone.comipaddress: --> {0.0.0.0}: 192.168.8.32hostalias1: -> {}: engineering.zhone.comhostalias2: -> {}: marketing.zhone.comhostalias3: -> {}: sales.zhone.comhostalias4: -> {}: gss.zhone.com....................Save new record? [s]ave, [c]hange or [q]uit: sRecord created.

PPP over ATMPoint to point protocol over ATM (PPPoA) allows an ATM interface to terminate PPP connections. With PPPoA, each PPP session is encapsulated in a separate ATM permanent virtual circuit (PVC) which then can be carried over physical connections. Challenge handshake authentication protocol (CHAP) and password authentication protocol (PAP) are used on PPPoA connections.

Setting up PPPoA

Follow these steps to enable PPPoA on the Z-Edge 64.


hostname Client host name (if any) that the client used to acquire its address. The default is an empty string.

hostalias1 Host name alias for the specified host. The default value is an empty string.

hostalias2 Secondary host name alias for the specified host. The default value is an empty string.

hostalias3 Tertiary host name alias for the specified host. The default value is an empty string.

hostalias4 Quaternary host name alias for the specified host. The default value is an empty string.

PPP over ATM


1 Create a new atm-traf-descr with a unique index for the PPPoA connection:

zSH> new atm-traf-descr 99 index can be any valuePlease provide the following: [q]uit.td_type: -------------> {atmNoClpNoScr}: td_param1: -----------> {0}: 800 PCR for the interfacetd_param2: -----------> {0}:td_param3: -----------> {0}:td_param4: -----------> {0}:td_param5: -----------> {0}:td_service_category: -> {ubr}: for datatd_frame_discard: --------> {true}:cac-divider: -------------> {1}:usage-parameter-control: -> {true}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

2 Create an ATM virtual channel link (VCL) over the WAN interface:

Note: Do not use the VPI/VCI combination of 0/35 when creating an ATM VCL for PPPoA. That VPI/VCI combination is used by the system default VCL.

zSH> new atm-vcl 1-1-1-0-hdsl2/atm/0/36Please provide the following: [q]uit.vpi: -----------------------------> {0}: vci: -----------------------------> {0}: 36admin_status: --------------------> {down}: upreceive_traffic_descr_index: -----> {0}: 99transmit_traffic_descr_index: ----> {0}: 99vcc_aal_type: --------------------> {aal5}: vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {llcencapsulation}: vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}: fault-detection-type: ------------> {disabled}: ....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

3 Create a new ppp-interface profile with the same VPI/VCI combination set in the atm-vcl profile:

zSH> new ppp-interface 1-1-1-0/pppPlease provide the following: [q]uit.vpi: ----------> {0}: vci: ----------> {0}: 36call-mode: ----> {nocall}: frame-type: ---> {atmllc}:



num-channels: -> {1}: ....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

4 Bind the PPP interface to ATM interface:

zSH> stack bindEnter the upper layer: 1-1-1-0/pppEnter the lower layer: 1-1-1-0-hdsl2/aal5Stack bind successful.

5 Use the stack show command to verify interface stacking:

zSH> stack show 1-1-1-0/pppAAL5 layer: 1-1-1-0-hdsl2/aal5ATM layer: 1-1-1-0-hdsl2/atmLine Group: 1-1-1-0-hdsl2/otherPhysical: 1/1/1/0/hdsl2

6 After binding the interfaces, the system creates a ppp-lcp profile. Update the ppp-lcp profile to set link control protocols (LCP) for establishing, configuring, and testing the data-link connection. The following example leaves the default settings:

zSH> update ppp-lcp 1-1-1-0/pppreceive-auth-enable: ---> {disabled}receive-auth-protocol: -> {pap}send-auth-enable: ------> {disabled}send-auth-protocol: ----> {pap}send-auth-identity: ----> {}mru-enable: ------------> {enabled}initial-mru: -----------> {1500}accm-enable: -----------> {disabled}rx-acc-map: ------------> {ff:ff:ff:ff}tx-acc-map: ------------> {ff:ff:ff:ff}fcs-alt-enable: --------> {disabled}fcs-size: --------------> {0}lqr-period: ------------> {3000}lqr-status: ------------> {disabled}quality-protocol: ------> {lqr}magic-number-enable: ---> {true}magic-number: ----------> {0}max-pad: ---------------> {4}callback-enable: -------> {disabled}callback-type: ---------> {byauth}callback-dial-string: --> {}restart-timer: ---------> {3}max-config-retries: ----> {10}max-term-retries: ------> {2}max-fail-retries: ------> {10}pfc-enable: ------------> {disabled}acfc-enable: -----------> {disabled}sdp-enable: ------------> {disabled}

PPP over ATM


num-mode-enable: -------> {disabled}....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

7 Create an ip-interface-record profile, modify the following parameters:

zSH> new ip-interface-record pppoa/ipPlease provide the following: [q]uit.vpi: ---------------> {0}: vci: ---------------> {0}: 36rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only **addr: --------------> {0.0.0.0}: netmask: -----------> {0.0.0.0}: 255.255.255.255 netmask must be /32 for point-to-point connectionsbcastaddr: ---------> {0.0.0.0}: destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: yesmcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: noingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: pppdhcpserverenable: --> {false}: ....................Save new record? [s]ave, [c]hange or [q]uit: sIP Interface record contains VPI/VCI values, but no 1483 layer could be found.Could not automatically bind this IP InterfaceNew record saved

8 Because the system does not recognize an IP interface named pppoa, you need to manually create the if-stack bindings:

zSH> stack bindEnter the upper layer: pppoa/ipEnter the lower layer: 1-1-1-0/pppStack bind successful.

9 Use the stack show command to verify interface stacking:

zSH> stack show pppoa/ipAAL5 layer: 1-1-1-0-hdsl2/aal5ATM layer: 1-1-1-0-hdsl2/atmLine Group: 1-1-1-0-hdsl2/otherPhysical: 1/1/1/0/hdsl2



10 Create a ppp-auth record to set up password authentication for PPPoA connections:

zSH> new ppp-auth 1/1 user-defined subscriber ID/user-defined PPP authentication IDPlease provide the following: [q]uit.ip-ifindex: ---> { }: 1-1-1-0/ip lgid: ---------> {0}: 12 lineGroupId of WAN portpap-enable: ---> {disabled}: enabledpap-peer-id: --> {}: ‘test’ user-defined peer IDpap-password: -> {}: ‘test’ user-defined passwordchap-enable: --> {disabled}:chap-name: ----> {}:chap-secret: --> {}:status: -------> {valid}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

Note: The pap-peer-id and pap-password values must be entered as strings with single quotes. After the ppp-auth record is saved, the pap-peer-id and pap-password values will be converted to hexadecimal values. For example, the string ‘test’ will be returned as 74:65:73:74.

11 PPPoA is now enabled.Verify that your connection has been setup by issuing a route show or interface show command. You can also ping the destination IP address.

12 The ppp-ncp profiles are used to set up network control protocols (NCPs) for establishing and configuring network-layer protocols. Create a ppp-ncp record using the name of the name of the ip-interface-record on which the PPPoA connection is carried (see Step 7):

zSH> new ppp-ncp pppoa/ipPlease provide the following: [q]uit.ip-comp-protocol: ------> {none}:max-slot-id: -----------> {3}:comp-slot-id: ----------> {disabled}:ip-addr-enable: --------> {disabled}:restart-timer: ---------> {3}:max-config-retries: ----> {10}:max-terminate-retries: -> {2}:max-failure-retries: ---> {10}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Deleting a PPPoA interface

1 Delete the PPPoA ip-interface-record profile:

zSH> delete ip-interface-record ip-interface-record pppoa/ip

PPP over ATM


Delete ip-interface-record pppoa/ip? [y]es, [n]o, [q]uit : yip-interface-record pppoa/ip deleted

2 Delete the ppp-interface record to disable PPPoA.

zSH> delete ppp-interface 1-1-1-0/pppDelete ppp-interface 1-1-1-0/ppp? [y]es, [n]o, [q]uit : yppp-interface 1-1-1-0/ppp deleted

Note: The associated ppp-lcp, ppp-ncp, and ppp-auth records are automatically deleted when you delete the ppp-interface record.




7

ADVANCED VOICE CONFIGURATION

This chapter details configuring advanced voice applications for the Z-Edge 64. It includes the following topics:

• ADPCM voice compression, page 85

• POTS voice options, page 86

• ISDN B-channel data, page 89

• Silence suppression and comfort noise generation, page 92

ADPCM voice compressionThe ITU standard G.726 specifies using an Adaptive Differential Pulse Code Modulation (ADPCM) algorithm for voice compression. ADPCM voice compression reduces the voice-traffic bandwidth and increases your network’s carrying capacity. For example, ADPCM reduces a 64kbps voice circuit to 32 kbps without a significant loss in voice quality.

To apply G.726 voice compression on the Z-Edge 64, set the preferred-ap-index to 2 in the aal2-cid-profile for both endpoints of a voice connection.

Modify the following parameters in the aal2-cid-profile to configure ADPCM voice compression:


admin-status Administrative status of the link.

Values: up

down

Default: down

preferred-ap-index From the aal2-audio-profile, this index number defines the preferred audio encoding format.

Values: 1 : used for G.711 encoding (default)

2 : used for G.726 encoding

Advanced voice configuration


First set ADPCM voice compression on the Z-Edge 64:

zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/160Please provide the following: [q]uit.admin-status: -------> {down} upsscs-type: ----------> {i3662}audio-service: ------> {enabled}frame-mode-data: ----> {enabled}cas: ----------------> {disabled}pcm-encoding: -------> {mulaw}max-length-frame: ---> {65535}max-sdu-length: -----> {1536}ras-timer: ----------> {0}preferred-ap-index: -> {1} 2....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

Then set ADPCM voice compression on the other end of the voice connection, ensuring matching VPI/VPIs and CIDs between the nodes.

Changing from G.711 to G.726 encoding

To change from G.711 to G.726 encoding on pre-existing aal2-cid-profiles:

1 Update the pre-existing aal2-cid-profile, changing the admin-status to down.

2 Change the preferred-ap-index to 2.

3 Save the record.

4 Update the aal2-cid-profile again, changing the admin-status to up.

5 Save the record.

Note: You must change the admin-status to down and then up again for voice encoding changes to take effect on pre-existing aal2-cid-profiles.

POTS voice optionsOn the Z-Edge H2A, there are several voice digital signal processing (DSP) options which you can modify in the analog-if-cfg-profile and the analog-fxs-cfg-profile records.

Configuring POTS gain settings

Modify the following parameters in the analog-if-cfg-profile if you need to change the gain settings for each POTS voice line:

POTS voice options



if-cfg-receive-tlp The receive Transmission Level Point (TLP) determines how much gain or loss is added to the incoming signal after it is decoded to analog. The receive TLP signal range is +3 db to -9 dB.

Values: fxsRtlpN9db

fxsRtlpN8db

fxsRtlpN7db

fxsRtlpN6db

fxsRtlpN5db

fxsRtlpN4db

fxsRtlpN3db

fxsRtlpN2db

fxsRtlpN1db

fxsRtlp0db

fxsRtlp1db

fxsRtlp2db

fxsRtlp3db

Default: fxsRtlp0db



If you need to modify the gain settings, update the analog-if-cfg-profile for each interface. For example:

zSH> update analog-if-cfg-profile 1-1-3-0/voicefxsPlease provide the following: (q=quit)if-cfg-impedence: ------------>{ohms600complex}: if-cfg-receive-tlp: ---------->{fxsrtlp0db}: modify if requiredif-cfg-transmit-tlp: --------->{fxsttlp6db}: modify if requiredif-cfg-trunk-conditioning: --->{idle}: if-maintenance-mode: --->{off}: if-cfg-pcm-encoding: --->{mulaw}: alaw | mulaw....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Configuring POTS signal type and ring frequency

Modify the following parameters in the analog-fxs-cfg-profile if you need to change signalling type, ring frequency, and ring back options for each voice line:

if-cfg-transmit-tlp The transmit TLP determines the gain or loss added to a voice signal from customer premises equipment (CPE) before it is digitally encoded to pulse code modulation (PCM). The transmit TLP signal range is +9 db to -3 dB.

Values: fxsTtlp9db

fxsTtlp8db

fxsTtlp7db

fxsTtlp6db

fxsTtlp5db

fxsTtlp4db

fxsTtlp3db

fxsTtlp2db

fxsTtlp1db

fxsTtlp0db

fxsTtlpN1db

fxsTtlpN2db

fxsTtlpN3db

Default: fxsTtlp0db

if-cfg-pcm-encoding Line encoding.

Values: alaw for E1.

mulaw for T1.


ISDN B-channel data


If you need to modify the signaling and ring frequency, update the analog-fxs-cfg-profile for each interface. For example:

zSH> update analog-fxs-cfg-profile 1-1-3-0/voicefxssignal-type: ----> {fxsloopstart}ring-frequency: -> {ringfrequency20} modify if requiredring-back: ------> {off} modify if required....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

ISDN B-channel dataThe ATM Forum’s specification for carrying voice over ATM (AF-VMOA-0145) details the delivery of ISDN BRI service over ATM adaption layer 2 (AAL2) virtual circuits. Based on this specification, a separate ATM virtual channel connection (VCC) is used for each of the two ISDN B (bearer) channels and the ISDN D (signalling) channel. The ISDN B channels can be used to carry voice calls as well as dial-up data calls to fax machines or modems.

In traditional time division multiplexing (TDM) networks, the ISDN D channel notifies the receiving terminal equipment if the B channel will carry voice or dial-up data. But in ATM networks, the ISDN D channel is relayed and there is no way to look at the D channel signalling information. Therefore


signal-type The method by which an off-hook condition is indicated.

Values: fxsloopstart

Default: fxsloopstart

ring-frequency Rate in cycles per second (Hertz) at which polarity reversal occurs on ringing.

Values: ringfrequency20

ringfrequency25

ringfrequency30

ringfrequency50

Default: ringfrequency20

ring-back The ring back is requested if this variable is set to on.

Values: on

off

Default: off



the ATM network equipment must be able to determine if the ISDN B channel is carrying voice or data traffic and then act accordingly.

The Z-Edge 64 uses high level data link control (HDLC) as the framing protocol used for data link communications over ATM. The system detects that the ISDN B channel is carrying data payload by recognizing the hexadecimal 0x7E flags that are at the beginning and end of HDLC frames.

Note: Only HDLC-framed protocols (such as PPP and V.120) are supported for ISDN B-channel data communications.

Modify the following parameter in the aal2-cid-profile to enable ISDN B channel data communications:

Modify the following parameter in the system profile to enable ISDN B channel data communications:

Enabling ISDN B-channel data

To enable ISDN B channel dial-up data calls, the pcm-encoding parameter must be set to alaw in the aal2-cid-profile for the matching CID on both the Z-Edge 64 and the connecting voice gateway (Sechtor 100A).

Note: Ensure that both the Z-Edge 64 and the voice gateway have the pcm-encoding parameter set to alaw in the aal2-cid-profile for the matching CID to enable B-channel data.


pcm-encoding Pulse code modulation (PCM) encoding format.

Values: mulaw for North American countries

alaw for European countries

Default: mulaw


countryregion The country or region this system is operating in. This setting is used to adjust system settings for different countries. For example, digital signal processing (DSP) tones and time division multiplexing (TDM) companding are country-specific settings that can be determined by this setting.

ISDN B-channel data


Note: Ensure that both the Z-Edge 64 and the voice gateway have the countryregion parameter set to an A-law-compliant country (an European country) in the system profile to enable B-channel data.

1 First, create a new aal2-cid-profile for the ISDN D channel using one of the ATM Forum-specified CIDs:

zSH> new aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/130Please provide the following: [q]uit.admin-status: -------> {down}: upsscs-type: ----------> {i3662}: i3661 for D channelsaudio-service: ------> {enabled}: frame-mode-data: ----> {disabled}: enabledcas: ----------------> {enabled}: disabledpcm-encoding: -------> {mulaw}: alawmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: ATM Forum specified audio profile index....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved

2 After saving the new aal2-cid-profile for the ISDN D channel, the aal2-cid-profiles for the associated ISDN B channels are automatically created with pcm-encoding set to alaw. You can see the aal2-cid-profiles created for the B channels by issuing a list command:

zSH> list aal2-cid-profileaal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/130aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/164aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/165

3 Validate that the aal2-cid-profiles that have been created for the ISDN B channels with A law companding:

zSH> get aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/164Please provide the following: [q]uit.admin-status: -------> {up}:sscs-type: ----------> {i3662}: for B channelsaudio-service: ------> {enabled}:frame-mode-data: ----> {enabled}: matches D channelcas: ----------------> {disabled}: matches D channelpcm-encoding: -------> {alaw}: matches D channelmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}:

zSH> get aal2-cid-profile 1-1-1-0-hdsl2/atm/0/37/165Please provide the following: [q]uit.admin-status: -------> {up}:



sscs-type: ----------> {i3662}: audio-service: ------> {enabled}:frame-mode-data: ----> {enabled}: matches D channelcas: ----------------> {disabled}:matches D channelpcm-encoding: -------> {alaw}: matches D channelmax-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}:

4 Ensure that the countryregion parameter is set to an A-law-compliant country (an European country) in the system profile of the Z-Edge 64:

zSH> get system 0syscontact: ----------> {}sysname: -------------> {Z-Edge 64BH2A}syslocation: ---------> {}enableauthtraps: -----> {disabled}setserialno: ---------> {0}zmsexists: -----------> {false}zmsconnectionstatus: -> {inactive}zmsipaddress: --------> {0.0.0.0}configsyncexists: ----> {false}configsyncoverflow: --> {false}configsyncpriority: --> {high}configsyncaction: ----> {noaction}configsyncfilename: --> {}configsyncstatus: ----> {syncinitializing}configsyncuser: ------> {}configsyncpasswd: ----> ** private **numshelves: ----------> {1}shelvesarray: --------> {}numcards: ------------> {1}ipaddress: -----------> {10.10.10.200}alternateipaddress: --> {0.0.0.0}countryregion: -------> {germany} an A-law-compliant countryprimaryclocksource: --> {0/0/0/0/0}ringsource: ----------> {internalringsourcelabel}

Silence suppression and comfort noise generation

Note: Software version 1.6.1 is required to support silence suppression and comfort noise generation on voice over ATM calls.

Silence suppression detects and removes silence in a call, reducing the required bandwidth for the call, and thus increasing the number of calls carried on the same connection. One drawback of silence-suppressed voice compression is the lack of ambience, or background noise, during silent periods of phone conversations. Comfort noise generation adds background noise on the receiving side of the call which has been encoded with silence suppression.



ITU-T recommendation I.366.2 specifies the use of a generic silence insertion descriptor (SID) frame in the service specific convergence sublayer (SSCS) of the ATM Adaption Layer Two (AAL2) cell header. The SID frame contains information used for correctly inserting comfort noise during silent intervals on the receiving side of the call. An audio profile that contains a SID frame must be used to support silence suppression and comfort noise generation.

The ATM Forum has defined several audio profiles and preferred audio profile (AP) indexes for use by voice and voiceband data connections over ATM. The profiles and preferred AP indexes set the audio characteristics (for example, encoding format and payload length) of AAL2 connections. The AAL2 audio profiles and preferred AP indexes are defined in ATM Forum specification AF-VMOA-014.000. Table 3 lists audio profiles supported on Zhone devices.

Provisioning silence suppression and comfort noise generation

To enable silence suppression and comfort noise generation, you must use either aal2-audio-profile 7/1, aal2-audio-profile 7/2, or aal2-audio-profile 8/1. Update the aal2-vcl-profile and aal2-cid-profile records to ensure they use the audio-profile-identifiers and preferred-ap-indexes from these audio profiles.

Note: The AAL2 audio-profile-identifier will be used in the aal2-vcl-profile. The preferred-ap-index will be used in the aal2-cid-profile.

1 Several aal2-audio-profile records are created by the Z-Edge 64.

zSH> list aal2-audio-profile

Table 3: Audio profiles and preferred AP indexes supported on Z-Edge 64

Audio Profile Identifier

Preferred AP index

Description of audio profile

7 1 G.711 encoding for Pulse Code Modulated (PCM) 64 kilobits/second (kbps) voice calls, 44-octet payload, with SID frame for silence-suppression and comfort noise generation

7 2 G.726 Adaptive Differential Pulse Code Modulation (ADPCM) voice compression for 32 kbps voice calls, 44-octet payload, with SID frame for silence-suppression and comfort noise generation

8 1 G.711 PCM-encoded 64 kbps, 44-octet payload, with SID frame for silence suppression and comfort noise generation

9 1 G.711 PCM-encoded 64 kbps, 44-octet payload, no SID frame

10 1 G.711 PCM-encoded 64 kbps, 44-octet payload, no SID frame

10 2 G.726 ADPCM-compressed 32 kbps, 44-octet payload, no SID frame



aal2-audio-profile 7/1aal2-audio-profile 7/2aal2-audio-profile 7/3aal2-audio-profile 8/1aal2-audio-profile 8/2aal2-audio-profile 9/1aal2-audio-profile 10/1aal2-audio-profile 10/2aal2-audio-profile 11/1aal2-audio-profile 11/2aal2-audio-profile 12/1aal2-audio-profile 12/2aal2-audio-profile 12/313 entries found.

2 To view one of the profiles use the get command. The syntax is get aal2-audio-profile audio-profile-identifier/preferred-ap-index. The following example uses audio profile 7 and preferred ap index 1:

zSH> get aal2-audio-profile 7/1min-uui: ------------> {0}max-uui: ------------> {7}sdu-multiples: ------> {1}algorithm: ----------> {g711}pkt-time: -----------> {55}sequence: -----------> {55}silence-Supression: -> {enabled}packet-Length: ------> {44}

Caution: Do not change any aal2-audio-profile parameters during system configuration.

3 When the vcc_aal_type parameter of the atm-vcl record is set to aal2, the Z-Edge 64 automatically creates an associated aal2-vcl-profile. Check the audio-profile-identifier parameter of the aal2-vcl-profile to ensure that it uses audio profile 7 or 8.

zSH> update aal2-vcl-profile 1-1-1-0-sonet/atm/0/37Please provide the following: [q]uit.app-id: -------------------------> {caspotsonlynoelcp}:vcc-i: --------------------------> {0}:audio-profile-identifier: -------> {7}: this audio profile supports silence suppression sscs-default-type: --------------> {i3662}:max-cps-sdu-size: ---------------> {45}:max-number-multiplex-channels: --> {239}:min-cid-for-aal2-user-channels: -> {16}: max-cid-for-aal2-user-channels: -> {255}: timer-cu: -----------------------> {0}:audio-service: ------------------> {enabled}:frame-mode-data: ----------------> {disabled}:cas: ----------------------------> {disabled}: trunk-type: ---------------------> {loopstart}:pcm-encoding: -------------------> {mulaw}:



max-length-frame: ---------------> {65535}:max-sdu-length: -----------------> {1536}:ras-timer: ----------------------> {0}:....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

4 Enable silence suppression in the voice-dsp-profile of your system. The table below describes the supported values for the silence-suppression-type parameter.

zSH> update voice-dsp-default-profile 0Please provide the following: [q]uit.redundancy-over-subscription-type: -> {none}:jitter-buffer-type: ----------------> {static}:jitter-buffer-size: ----------------> {15}:inter-arriv-jit-threshold: ---------> {80}:pkts-lost-threshold: ---------------> {600}:echo-cancellation-type: ------------> {g168echotl48}:silence-supression-type: -----------> {silsupoff}: silsuponsidon....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.

Note: If you are using audio profile 7 and the silence-suppression-type parameter of the voice-dsp-profile is set to silsupoff, the voice packets will still be transmitted even if there is a period of silence.

5 Check the aal2-cid-profile for each voice line on your system to ensure that only the valid preferred-ap-index for each specific audio profile is used. Refer to Table 3 to find out which preferred-ap-indexes are supported by which audio-profile-identifiers.

zSH> update aal2-cid-profile 1-1-1-0-sonet/atm/0/37/17Please provide the following: [q]uit.admin-status: -------> {up}: sscs-type: ----------> {i3662}: audio-service: ------> {enabled}: frame-mode-data: ----> {disabled}: cas: ----------------> {enabled}:


silence-suppression-type Specifies what type of silence suppression algorithm is used.

Values: silSupOff silence suppression is off.

silSupOnSidOn begins sending SID frames intermittently.

Default: silSupOff



pcm-encoding: -------> {mulaw}: max-length-frame: ---> {65535}:max-sdu-length: -----> {1536}:ras-timer: ----------> {0}:preferred-ap-index: -> {1}: 2 audio profile 7 supports 1 or 2....................Save changes? [s]ave, [c]hange or [q]uit: sRecord updated.


8

ADMINISTRATION

This chapter describes Z-Edge 64 diagnostic tools such as the front panel LEDs, CLI commands, and SNMP administration. It includes the following topics:

• LED indicators, page 97

• CLI diagnostic methods, page 99

• SNMP administration, page 101

• User accounts, page 104

• Manually binding interfaces, page 105

• System logging, page 106

• Real time statistics, page 107

• Saving and restoring configurations, page 107

• Setting system date and time, page 109

• Rebooting the system, page 109

LED indicatorsThis section explains how to interpret the LED indicator lights located on the front panel of the Z-Edge 64 unit. The figure below displays the front panel of the Z-Edge 64 unit and LED positions.

Administration


Figure 8: Z-Edge 64 front panel

Power LED

A single, continuous green LED indicates the operational status of the power supply to the unit. If the LED is ON, the power is connected. If the LED is OFF, there is no power.

Diagnostic LED

A single, continuous amber LED indicates the fault status of the unit. The Diagnostic LED is ON during startup, and it is off during operation.

Operational LED

A single, continuous green LED is ON when the unit is running, and it is OFF when the unit is not running.

WAN LED

The WAN LED indicates the transmission status of the WAN interface port. If the DS1 line adminstatus is UP and does not have any alarms, the green WAN LED will be lit continuously. If the adminstatus of the DS1 line is DOWN or TESTING, or if alarms are present on the line, the WAN LED will be flashing.

CLI diagnostic methods


Line LEDs

Z-Edge 64 BH2A (ISDN BRI)

The Line LEDS (1 - 4) will light continuously green when the ISDN D channel is established. The Line LED will be off when there is no ISDN D channel.

Z-Edge 64 H2A (POTS)

The Line LEDS (1 - 4) will light continuously green when the phone is off-hook. The Line LED will be off when the phone is on-hook.

CLI diagnostic methodsSeveral diagnostic commands can be executed using the CLI, including the showlinestatus, interface show, and traceroute commands.

showlinestatus command

The showlinestatus command uses this syntax:

showlinestatus shelf slot port subport

You can display status of individual lines on the Z-Edge 64 by entering values for shelf, slot, and port.

zSH> showlinestatus 1 1 1Search in progress ......... ................. GroupId --------> 4 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 3 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 1 SubPort --------> 0

Display the status of all lines (or physical interfaces) connecting to the Z-Edge 64 by entering showlinestatus only, or by specifying only shelf and slot:

zSH> showlinestatus 1 1Search in progress ......... ................. GroupId --------> 6 Status ---------> ACTIVE (1) TxClk ----------> NONE (1)

Administration


RefClkSrc ------> NO If_index -------> 5 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 1 SubPort --------> 0 ................. GroupId --------> 8 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 7 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 2 SubPort --------> 0 ................. GroupId --------> 10 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 9 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 1 SubPort --------> 0 ................. GroupId --------> 12 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 11 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 2 SubPort --------> 0 ................. GroupId --------> 4 Status ---------> ACTIVE (1) TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 3 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 3 SubPort --------> 0 ................. GroupId --------> 2 Status ---------> ACTIVE (1)

SNMP administration


TxClk ----------> NONE (1) RefClkSrc ------> NO If_index -------> 1 Peer If_Index --> 0 Shelf ----------> 1 Slot -----------> 1 Port -----------> 4 SubPort --------> 0

interface show command

The interface show command displays the IP address and MAC address of the unit. Enter the following command to monitor the status of line interfaces:

zSH> interface showInterface Status Rd/Address Media/Dest Address-----------------------------------------------------------------1/1/1/0/ip UP 1 0.0.0.0/32 0/351/1/2/0/ip UP 1 192.168.88.200/24 00:01:47:01:af:20

traceroute command

The traceroute command allows the user to see the route that IP datagram follows from one host to another. The traceroute command is another method of verifying routes. Refer to the Zhone CLI Reference Guide for more information on the traceroute command.

SNMP administrationThe Z-Edge 64 can be monitored by SNMP. To enable SNMP administration create SNMP community names, access lists, and trap destinations.

Creating SNMP community names and access lists

Note: By default, the Z-Edge 64 has a single SNMP community defined with the name ZhonePrivate. This community has admin access to the system. Zhone recommends that you configure community names and access lists to prevent unauthorized access to the system.

The community-profile specifies the community name and an access level for SNMP manager to access the system. It can also optionally specify a community-access-profile that is used to verify the source IP address of the SNMP manager. The system supports up to 50 different access lists.

The following community access levels are supported:

• noaccess—the community has no access.

Administration


• read—the community has read-only access to the system, with the exception of information in the community-profile and community-access-profile.

• readandwrite—the community has read-write access to the system, with the exception of information in the community-profile and community-access-profile.

• admin—the community has read and write access to the entire system, including information in the community-profile and community-access-profile. The ZMS requires admin access to manage the system.

Creating a community profile

Note: Configuring a community profile disables the ZhonePrivate default community name.

Modify the following parameters in the community-profile to specify a community name (all others should be left at their default values):

The following example defines a community name public with read-only privileges:

zSH> new community-profile 1Please provide the following: [q]uit.community-name: -----> {}: publicpermissions: --------> {read}:access-table-index: -> {0}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Creating community access lists

The following example defines a community name private with read-write privileges and also creates an access list to verify that the SNMP managers attempting to access the Z-Edge 64 are coming from known IP addresses 192.168.9.10 and 192.168.11.12:

Modify the following parameters in the community-access-profile to specify privileges and access (all others should be left at their default values):


community-name Community name to be sent in all traps sent to this destination.

SNMP administration


First, create an access list for the first IP address:

zSH> new community-access-profile 2Please provide the following: [q]uit.access-table-index: -> {0}: 1ip-address: ---------> {0.0.0.0}: 192.168.9.10....................Save new record? [s]ave, [c]hange or [q]uit: s New record saved.

Then, create an access list for the second IP address with the same access-table-index (1):

zSH> new community-access-profile 3Please provide the following: [q]uit.access-table-index: -> {0}: 1ip-address: ---------> {0.0.0.0}: 192.168.11.12....................Save new record? [s]ave, [c]hange or [q]uit: s New record saved.

Finally, create a community-profile that specifies the community name, and uses the same access-table-index (1) as defined in the two community-access-profiles you just created:

zSH> new community-profile 4Please provide the following: [q]uit.community-name: -----> {}: privatepermissions: --------> {read}: readandwriteaccess-table-index: -> {0}: 1....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Configuring traps

The trap-destination profile defines a trap recipient for the Z-Edge 64. To configure a trap destination you need to know:

• the IP address of the SNMP manager workstation

• the community name the trap recipient expects


access-table-index The community-profile identifier.

Values: 1-50

ip-address The IP address of the SNMP manager of the system.

Administration


Modify the following parameters in the trap-destination profile to set up a trap destination:

The resendseqno and ackedseqno parameters are set by the ZMS. The following example configures a trap recipient with the IP address 192.168.3.21:

zSH> new trap-destination 32Please provide the following: [q]uit.trapdestination: -> {0.0.0.0}: 192.168.3.21communityname: ---> {}: publicresendseqno: -----> {0}:ackedseqno: ------> {0}:traplevel: -------> {low}:traptype: --------> {0}: 2trapadminstatus: -> {enabled}:gatewaytrapserveraddr: -> {none}:....................Save new record? [s]ave, [c]hange or [q]uit: sNew record saved.

Note: For communication with the ZMS, setting trap destinations can be done from the CLI or by the ZMS. Refer to the ZMS Administrator's Guide and the NetHorizhon User's Guide for more information on working with the ZMS.

User accounts Z-Edge 64 users have access to the CLI and are able to configure and administer the system.

Adding a user

Every administrative user on the system must have a user account. The account specifies their username and password, as well as their privilege level, which determines their access to commands.

Note: When entering access level responses, enter yes completely or the CLI interprets the response as no.


trapdestination The IP address of the SNMP manager.

communityname Community name to be sent in all traps sent to this destination.

traptype Array of allowed categories to be sent to this particular trap destination.

Manually binding interfaces


To add a user, enter the following commands:

zSH> adduserPlease provide the following: [q]uit.User Name: jsmithUser Prompt[zSH>]: jsmith> Please select user access levels.admin: -------> {no}: yeszhonedebug: --> {no}:voice: -------> {no}: yesdata: --------> {no}: yesmanuf: -------> {no}: yesdatabase: ----> {no}: yessystems: -----> {no}: yestool: --------> {no}: yesuseradmin: ---> {no}: yes..................................User name:(jsmith) User prompt:(jsmith>)Access Levels:(admin)(voice)(data)(manuf)(database)(systems)(tool)(useradmin)Save new account? [s]ave, [c]hange or [q]uit: sUser record saved.TEMPORARY PASSWORD: NiviuNmm

To change from the default (admin) user to the new user, log out from the system and then log in as the new user, or issue a su command while still in the admin user setting.

zSH> su jsmithPassword: the password is case sensitive and will not appear as you type itjsmith>

Manually binding interfacesWhen creating ip-interface-record profiles, the syntax is name/type. The name of the IP interface can be user-defined or match the naming of the if-translate record for the physical interface. The system automatically binds interfaces if the name of the new IP record matches the name of the if-translate profile or if the syntax shelf/slot/port/subport/type is used.

The example below shows a new ip-interface-record being created with a user-defined name. Since there is no if-translate record with the name 1-1-2-0, the system will not automatically bind this interface. Enter a list if-translate command to determine what if-translate records are available on your system.

zSH> new ip-interface-record 1-1-2-0/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {0}:rdindex: -----------> {1}:dhcp: --------------> {none}: ** read-only **

Administration


addr: --------------> {0.0.0.0}: 192.168.88.200netmask: -----------> {0.0.0.0}: 255.255.255.0bcastaddr: ---------> {0.0.0.0}: 192.168.88.255destaddr: ----------> {0.0.0.0}:farendaddr: --------> {0.0.0.0}:mru: ---------------> {1500}:reasmmaxsize: ------> {0}:ingressfiltername: -> {}:egressfiltername: --> {}:pointtopoint: ------> {no}:mcastenabled: ------> {yes}:ipfwdenabled: ------> {yes}:mcastfwdenabled: ---> {yes}:natenabled: --------> {no}:bcastenabled: ------> {yes}:ingressfilterid: ---> {0}:egressfilterid: ----> {0}:ipaddrdynamic: -----> {static}:dhcpserverenable: --> {false}:....................Save new record? [s]ave, [c]hange or [q]uit: sCannot determine binding for this IP interface.Could not automatically bind this IP Interface.New record saved.

Since the system did not automatically bind the new IP interface, manually bind the interface with the stack bind command:

zSH> stack bindEnter the upper layer: 1-1-2-0/ip the IP interface createdEnter the lower layer: 1-1-2-0-ethernetcsmacd/other the line group associated with EthernetStack bind successful.

Note: The stack bind command does not allow binding directly to physical interfaces. You must bind two logical interfaces.

Enter the stack show command (with name/type syntax) to see interface binding:

zSH> stack show 1-1-2-0/ipLine Group: 1-1-2-0-ethernetcsmacd/otherPhysical: 1/1/2/0/ethernetcsmacd

System loggingSystem logging is available on telnet sessions:

• logging can be enabled or disabled for the session using the log session command.

• logging can be enabled or disabled on the serial craft port using the log serial command.

Real time statistics


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, using the following command:

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 using the following command:

zSh> log serial on | off

This command setting persists across system reboots.

Real time statisticsThe Z-Edge 64 supports real time statistics using NetHorizhon. Performance information is useful for detecting and addressing network problems. For information on how to configure and enable this functionality see the NetHorizhon User’s Guide.

NetHorizhon monitors performance data on the following ZMS objects related to Z-Edge 64:

• Z-Edge devices

• Physical ports

• Logical interfaces

• Permanent Virtual Circuits (PVCs)

• IP Routing domains

Note: The actual statistics you can view within ZMS for an object depend on the type (such as device, performance, or port) and the release version of the device on which the object resides.

Saving and restoring configurationsThe dump and restore commands enable you to save and restore the system configuration. You can save the configuration to the console, or to a file on the network. The dump and restore commands use Trivial File Transfer Protocol (TFTP) to transfer files to the network.

Passwords are encrypted when they are saved to the configuration file. The encrypted passwords are used to restore the correct password, but cannot be used to log in.

Administration


Backing up the configuration

Before you upgrade or downgrade the software, back up your configuration using the dump command. The command uses the following syntax:

dump [network host filename]

To back up the configuration to the network:

1 Create the file in the destination location of the TFTP server and make it writable.

2 Save the configuration. The following example saves the configuration to a file named zedge.cfg on the host 192.168.8.21:

zSH> dump network 192.168.8.21 zedge.cfg

Restoring the full configuration from the network

The restore command restores the system configuration from a file previously created using the dump command.

1 Verify the file exists on the network drive.

2 Specify the host and file name that contains the configuration:

zSH> restore full network host filename

3 Reboot the system:

zSH> systemreboot

Restoring a partial configuration

To perform a partial restore:

1 Using a text editor, open a previously saved configuration file created with the dump command.

2 Identify the portion of the configuration you want to restore. Look for the series of commands between the create and commit commands in the dump file. For example, the following lines create an ATM VCL:

create atm-vcl 1-7-1-0-hdsl2/37/0/37set vpi = 0set vci = 37set admin_status = upset receive_traffic_descr_index = 25472set transmit_traffic_descr_index = 25472set vcc_aal_type = aal2set vcc_aal5_cpcs_transmit_sdu_size = 9188set vcc_aal5_cpcs_receive_sdu_size = 9188set vcc_aal5_encaps_type = llcencapsulationset vcl_cast_type = p2pset vcl_conn_kind = pvcset fault-detection-type = disabledcommit atm-vcl 1-7-1-0-hdsl2/37/0/37

3 Create a text file that contains only the configuration you want to restore.

Setting system date and time


4 Issue the partial restore command:

– To restore from the console, turn on the send text file option of your terminal emulation software and identify the file to send to the console. Then issue the following command:

zSH> restore partial console

– To restore from the network, place the file on a network TFTP server, then issue the following command:

zSH> restore partial network TFTPServer filename

Setting system date and timeUse the setdatetime command to set the date and time on your system. The syntax is setdatetime month day year hour minute second, where month is entered as a two-digit representation of the month, day is entered as a two-digit representation of the day, year is entered as a four-digit representation of the year, hour is entered as a two-digit representation of the hour, minute is entered as a two-digit representation of the minute, and second is entered as a two-digit representation of the second. The example below sets the system time:

zSH> setdatetime 09 30 2002 14 07 00Current Time: MON SEP 30 14:07:00 2002

You can view system date and time with the showdatetime command:

zSH> showdatetimeCurrent Time: MON SEP 30 14:18:13 2002

Rebooting the systemTo reboot the Z-Edge 64 system, use the following commands:

zSH> systemrebootDo you want to reboot the system? (yes or no) [no] yesDo you want to exit from this request? (yes or no) [yes] noAre you sure? (yes or no) [no] yes

Administration



A

SPECIFICATIONS

This appendix lists the technical specifications of the Z-Edge 64.

Z-Edge 64 specificationsThe Z-Edge 64 has the following specifications:

Table 4: Z-Edge 64 specifications

Dimensions Width: 25.4cm (10.00")Height: 2.8cm (1.12")Depth: 19.3cm (7.60")

Installation Desktop Wall mount

Power supply AC: 90 to 264 VAC, 47 to 63Hz(External power supply included)

Environment Operating temperature:

00C to +500C (320F to 1220F)Storage Temperature:

-400C to +700C (-400F to 1580F)Relative humidity:5 to 95% Humidity, Noncondensing

Phone lines Physical: Four RJ11for H2A (POTS)

Four ISO 8877 for BH2A (ISDN BRI)

LAN interface Physical: One RJ45

Frame format: Ethernet IEEE802.3

Interface speed: 10/100Mbps

Protocols: IP, SNMP, CLI

WAN interface Physical: One RJ11

Interface speed: up to 2.3Mbps

Protocols: SDSL, HDSL2, G.SHDSL

Specifications


Serial (craft) interface Physical: One female DB9

Interface speed: 9.6 kbps

Regulatory EN60950, EN55024, EN55022

Table 4: Z-Edge 64 specifications (Continued)


B

CABLE PINOUTS

This appendix lists the pinouts of the cables that are used with the Z-Edge 64.

RJ11 pinouts for WAN lineThe supplied RJ11 (green color-coded) is category 3, unshielded twisted pair, 4-pin standard telco cable:

Figure 9: RJ11 pinouts

1 2 3 4

T R

Table 5: RJ11 pinouts

Pin Name

1 not used

2 Tip

3 Ring

4 not used

Cable pinouts


RJ45 pinouts for LAN lineThe supplied RJ45 (blue color-coded) is category 5, 8-pin standard Ethernet (or LAN) cable:



Pin Name

1 Transmit +

2 Transmit -

3 Receive +

4 not used

5 not used

6 Receive -

7 not used

8 not used

1 2 3 4 5 6 7 8

T+T-R+ R-

ISO 8877 pinouts for ISDN BRI voice lines


ISO 8877 pinouts for ISDN BRI voice linesUse ISO 8877 cables for ISDN BRI voice connections.

Figure 11: ISO 8877 pinouts

Table 7: ISO 8877 pinouts

Pin Name

1 not used

2 not used

3 Receive +

4 Transmit +

5 Transmit -

6 Receive -

7 cable shield integrity

8 cable shield integrity

1 2 3 4 5 6 7 8

R+ T+ T- R-

Cable pinouts


RJ11 pinouts for POTS voice linesUse unshielded twisted pair (UTP), 4-pin standard telco cable for POTS voice connections:



Pin Name

1 not used

2 Ring

3 Tip

4 not used

1 2 3 4

R T


INDEX

A

AAL2audio profiles 93

configuration 50CID profile

configuration 51preferred AP indexes 93

AAL2 VCLprofiles

configuration 50modifying parameters 48POTS 49

aal2-audio-profile profile 50aal2-cid profile

ISDN 53POTS 51

aal2-cid-profile profile 51, 53aal2-vcl-profile profile 49access-table-index parameter 102ackedseqno parameter 103adding default route, configuration 37adding users, configuration 104adduser command, example using 105admin_status parameter 43, 46admin-status parameter 51, 85ADPCM voice compression 85advanced IP configuration

configuring as DHCP server 64configuring NAT 63

analog-fxs-cfg-profile 88analog-if-cfg-profile 86app-id parameter 47, 49Asynchronous Transfer Mode, see ATMATM VCL, creation of 46ATM voice connections

configuring 45ATM, description of 14atm-vcl profile 29, 43, 46audio-profile-identifiers parameter 47autobaud 17

configuring 22automatic baud rate adaption

configuring 22

automatic configuration, description of 29automatic rate adaption 17

B

back panel, description of 18baud rate detection 17bcastaddr parameter 44binding interfaces 105bootfile parameter 68boot-server parameter 68bridging 73

C

cable pinoutsRJ11 pinouts for POTS voice lines 116RJ11 pinouts for WAN line 113RJ45 pinouts for LAN line 114RJ48C cables for ISDN BRI voice 115

calculating PCR 42capable-line-rate-limit parameter 54cas parameter 48, 49, 51, 85changepass command 22changing default user password 22CLI

configuration 18diagnostic methods

showlinestatus command 99clientId parameter 70client-match-string parameter 70comfort noise generation 92Command Line Interface, See CLIcommands

adduserexample 105

changepass 22dump 107get 29interface show 99linegroup 55, 57, 59list 53logout 21new 53

Index


restore 107rip 39rip show 40route add 37route delete 38route show 39setdatetime 109showdatetime 109showlinestatus 28, 99stack bind 106su 105traceroute 39, 99

community-name command 102communityname parameter 103config-line-rate parameter 24configuration

AAL2 audio profiles 50AAL2 CID profile 51AAL2 VCL profiles 50adding users 104advanced IP 63automatic 29basic 33CLI 18CLI disabled 32creating ATM VCL 46creating DHCP client identifiers 72creating DHCP server subnet options 67creating dhcp-server-group profile 69creating dhcp-server-host profile 70data

calculating PCR 42updating ATM traffic descriptor 41updating ATM traffic descriptors 42updating ATM virtual channel link 43updating IP interface record 44

DHCP server options 65displaying RIP information 40DNS resolver 76DSL 22Ethernet

interface 35management channel 35

fundamentals 33description 33interface types 33profiles 34

interface indexes 34local management channel 21profiles 34

rebooting the system 109RIP 39

global defaults 39SNMP 18static routes 37subscriber profile 54subscriber voice endpoint profiles 57, 58system defaults 29traps 103updating ATM traffic descriptors 42updating ATM virtual channel link 43updating IP interface record 44user accounts 104voice 41, 45WAN 21WAN interface 39WAN system security 22ZMS 18

creating DHCP client identifiers, configuration 72

D

default profiles 29default-lease-time parameter 68default-router parameter 68DHCP server, enabling 71DHCP, description of 16dhcpClientId parameter 72dhcp-client-lease-resource profile 72dhcp-server-group profile 65, 69dhcp-server-host profile 65, 70dhcp-server-options profile 65dhcp-server-subnet profile 65, 67

supported parameters 68Digital Subscriber Line, see DSLdisplaying RIP information 40DNS resolver configuration

creating a host profile 77creating a resolver record 77

documents related to this guide 10domain parameter 68, 77domain-name parameter 68DSL

configuration 22verify showlinestatus command 28

description 14interface configuration

G.shdsl interface 25profile


configuration 22supported parameters 23

dsl-config profile 22, 25dump command 107Dynamic Host Control Protocol, see DHCP

E

Ethernetinterface

configuration 35management channel 35

F

features and capabilities 13first-nameserver parameter 77frame-mode-data parameter 48, 49, 51, 85

G

G.shdslconfiguration 25description 15supported parameters 25

get command 29Global Symmetric High-bit-rate Digital Subscriber

Loop, see G.shdsl

H

hdsl2 profile 23host profile 78hostalias1 parameter 78hostalias2 parameter 78hostalias3 parameter 78hostalias4 parameter 78hostname parameter 78hwaddr parameter 70

I

IAD, description of 13id parameter 54integrated access device, see IADinterface indexes, configuration of 34interface show command 99interface types, configuration of 33ip-address parameter 102

ISDN B-channel data 89

L

LANinterface 18

pinging 38lease-time parameter 66LED indicators

diagnostic LED 98operational LED 98power LED 98WAN LED 98

linegroup command 55, 57, 59line-group-id parameter 54line-rate-limit parameter 54list command 53local management channel

configuration 21logging in and out 21

loggingenabling/disabling for session 107enabling/disabling over the serial craft port 107

logging in and out, description of 21logout command 21

M

max-cid-for-aal2-user-channels parameter 48, 49max-lease-time parameter 66, 68min-cid-for-aal2-user-channels parameter 49min-lease-time parameter 66, 68mru parameter 44

N

name parameter 69, 70NAT

configuration 63description 15

netmask parameter 68Network Address Translation, see NATnetwork parameter 68new command 53ntr parameter 24

P

parameters

Index


access-table-index 102ackedseqno 103admin_status 43, 46admin-status 51, 85app-id 47, 49audio-profile-identifiers 47bcastaddr 44bootfile 68boot-server 68capable-line-rate-limit 54cas 48, 49, 51, 85clientId 70client-match-string 70community-name 102communityname 103config-line-rate 24default-lease-time 68default-router 68dhcpClientId 72domain 68, 77domain-name 68first-nameserver 77frame-mode-data 48, 49, 51, 85hostalias1 78hostalias2 78hostalias3 78hostalias4 78hostname 78hwaddr 70id 54ip-address 102lease-time 66line-group-id 54line-rate-limit 54max-cid-for-aal2-user-channels 48, 49max-lease-time 66, 68min-cid-for-aal2-user-channels 49min-lease-time 66, 68mru 44name 69, 70netmask 68network 68ntr 24preferred-ap-index 51, 85primary-name-server 68query-order 77range1-end 68range1-start 68range2-end 68range2-start 68

range3-end 68range3-start 68range4-end 68range4-start 68receive_traffic_descr_index 43, 46resendseqno 103reserve-end 67reserve-staff 67secondary-name-server 68second-nameserver 77shdsl-config-line-rate 25shdsl-transmit-power-back-off-mode 25sscs-default-type 48sscs-type 51, 85supported 23td_index 42td_param1 42td_service_category 42third-nameserver 77transmit_traffic_descr_index 43, 46trapdestination 103traptype 103vcc_aal_type 43, 46vci 46vendor-match-string 70

partial 108phone lines, interface with 18physical interfaces

back panel 18configuration 18description 18LAN 18phone lines 18serial port 18WAN 18

POTSgain settings 86ring frequency 88signal type 88

POTS options 86preferred-ap-index parameter 51, 85primary-name-server parameter 68product description 13profiles

aal2-audio-profile 50aal2-cid-profile 51, 53aal2-vcl-profile 49atm-vcl 29, 43, 46configuration 34default 29


dhcp-client-lease-resource 72dhcp-server-group 65, 69dhcp-server-host 65, 70dhcp-server-options 65dhcp-server-subnet 65, 67dsl-config 22, 25hdsl2-config 23host 78resolver 77, 78rip-global-config 39sdsl-config 23, 24shdsl-config 25subscriber 54trap-destination 103

protocols 14

Q

query-order parameter 77

R

range1-end parameter 68range1-start parameter 68range2-end parameter 68range2-start parameter 68range3-end parameter 68range3-start parameter 68range4-end parameter 68range4-start parameter 68rebooting the system, description of 109receive_traffic_descr_index parameter 43, 46resendseqno parameter 103reserve-end parameter 67reserve-staff parameter 67resolver profile 77, 78restore 108restore command 107restoring configuration, description of 107RIP

configurationdescription 39displaying RIP information 40

description 16global defaults

configuration 39rip command 39rip show command 40rip-global-config profile 39

route add command 37route delete command 38route show command 39Routing Information Protocol, see RIP

S

Saving and restoring configurations 107sdsl profile 23SDSL, description of 15sdsl-config profile 24secondary-name-server parameter 68second-nameserver parameter 77serial port, interface with 18Setting date and time 109shdsl profile 23shdsl-config profile 23, 25shdsl-config-line-rate parameter 25shdsl-transmit-power-back-off-mode 25showlinestatus command 99

verification 28silence suppression 92Simple Network Management Protocol, see SNMPSNMP

administrationconfiguring traps 103

community access listscreation 102

configuration 18creating access lists 101creating community names 101description 16

specifications 111sscs type parameter 51, 85sscs-default-type parameter 48stack bind 106static routes

adding default route 37configuration 37deleting routes 38verifying routes 38

statistics 107su command 105subscriber profile

configuration 54POTS 54

subscriber voice endpoint profiles 57, 58configuration 57, 58

Index


subscriber side 57, 58subscriber voice profiles

POTS 57Symmetric Digital Subscriber Line, see SDSLsystem security

changing default user password 22configuration 22

T

td_index parameter 42td_param1 parameter 42td_service_category parameter 42third-nameserver parameter 77traceroute command 39, 99transmit_traffic_descr_index parameter 43, 46transparent bridging 73trapdestination parameter 103trap-destination profile 103traps, configuration 103traptype parameter 103

U

updating ATM traffic descriptors, configuration 42updating ATM virtual channel link, configuration

43updating IP interface record, configuration 44user accounts

adding users 104configuration 104

V

vcc_aal_type parameter 43, 46vci parameter 46vendor-match-string 70verifying routes

displaying routing tables when 39traceroute command 39

voice configurationcreating ATM traffic descriptor 45creating ATM VCL 46

voice DSP options 86

W

WANconfiguration 22

description 21DSL 22DSL profile 22local management channel 21logging in and out 21NAT 63system security 22

DSL configuration 22DSL profile 22interface 18

configuring NAT 63pinging 38RIP configuration 39

system security 22

Z

Zhone Management System, see ZMSZMS

CLI configuration disabled 32configuration 18

Documents

Z-Edge 64 Configuration Guide - Visionary Broadband 64_config.pdfZhone Technologies makes no representation or warranties with respect to the contents hereof and specifically disclaims