Paradyne 6302 User Manual

Hotwire

DSL Routers

Models 6301, 6302, 6341, 6342,

6351, and 6371

User’s Guide

Document No. 6300-A2-GB20-10

November 2003

Notice

This publication is protected by federal 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 of Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773.

Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporation reserves the right to revise this publication and to make changes from time to time in the contents hereof without obligation of Paradyne Corporation to notify any person of such revision or changes.

Changes and enhancements to the product and to the information herein will be documented and issued as a new release to this manual.

Warranty, Sales, Service, and Training Information

Contact your local sales representative, service representative, or distributor directly for any help needed. For additional information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or Paradyne worldwide office locations, use one of the following methods:



Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at www.paradyne.com/warranty.)



Telephone: Call our automated system to receive current information by fax or to speak with a company representative.

— Within the U.S.A., call 1-800-870-2221

— Outside the U.S.A., call 1-727-530-2340

Document Feedback

We welcome your comments and suggestions about this document. Please mail them to Technical Publications, Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to userdoc@paradyne.com. Include the number and title of this document in your correspondence. Please include your name and phone number if you are willing to provide additional clarification.

Tradem ark s

ACCULINK, COMSPHERE, ETC, EtherLoop, FrameSaver, GranDSLAM, Hotwire, the Hotwire logo, Jetstream, MVL, NextEDGE, OpenLane, Paradyne, the Paradyne logo, Paradyne Credit Corp., the Paradyne Credit Corp. logo, Performance Wizard, StormPort, and TruePut are all registered trademarks of Paradyne Corporation. ADSL/R, BitStorm, Connect to Success, GrandVIEW, Hotwire Connected, iMarc, JetFusion, JetVision, MicroBurst, PacketSurfer, ReachDSL, Spectrum Manager, StormTracker, and TriplePlay are trademarks of Paradyne Corporation. All other products and services mentioned herein are the trademarks, service marks, registered trademarks, or registered service marks of their respective owners.

A November 2003 6300-A2-GB20-10

About This Guide

 Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . vii

 New Features for this Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

 Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

 Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

1 Introduction to Hotwire DSL Routers

 What is a Hotwire DSL Router? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

DSL Technologies Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

 Typical DSL Router System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

 Hotwire DSL Router Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

 Service Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

2 Accessing the DSL Router

 Access Control to the DSL Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Levels of Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

 Local Console Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Changing Access Session Levels . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Setting Up the New User’s Login . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

 Telnet Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

 Determining the Current Access Level. . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Determining the Available Commands . . . . . . . . . . . . . . . . . . . . . 2-5

 Using the List Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

 Changing the System Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

 Exiting from the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Manually Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Automatically Logging Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

3 Configuring the DSL Router

 DSL Router Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

 The DSL Router’s Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Interface Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

6300-A2-GB20-10 November 2003 i

Contents

 Service Domain IP Address Assignments. . . . . . . . . . . . . . . . . . . . . . 3-2

Numbered DSL or Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . 3-3

Unnumbered DSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

 IP Options Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

 Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

 Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

 Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

 Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Basic NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Network Address Port Translation (NAPT/PAT) . . . . . . . . . . . . . . 3-7

Simultaneous Basic NAT and NAPT . . . . . . . . . . . . . . . . . . . . . . . 3-8

Applications Supported by NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

 Dynamic Host Configuration Protocol (DHCP) Server . . . . . . . . . . . . . 3-9

 DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

IP Protocol Type Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Ethernet Type Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Land Bug/Smurf Attack Prevention . . . . . . . . . . . . . . . . . . . . . . . . 3-12

 Routed vs. Bridged PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

 PPPoE Client Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

4 DSL Router Configuration Examples

 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Basic Bridging Configuration Example . . . . . . . . . . . . . . . . . . . . . 4-2

Basic Routing Configuration Example . . . . . . . . . . . . . . . . . . . . . . 4-3

Basic NAT Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . 4-4

NAPT Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Simultaneous Basic NAT and NAPT Configuration Example . . . . 4-8

Unnumbered DSL Interface with Proxy ARP Configuration Example 410

DHCP Relay with Proxy ARP Configuration Example . . . . . . . . . . 4-11

DHCP Server with Basic NAT Configuration Example . . . . . . . . . 4-12

PPPoE Client with NAPT and DHCP Server Configuration Example 413

Downstream Router Configuration Example . . . . . . . . . . . . . . . . . 4-14

IP Passthrough Configuration Example. . . . . . . . . . . . . . . . . . . . . 4-15

5 Monitoring the DSL Router

 Monitoring the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

ii November 2003 6300-A2-GB20-10

 LED Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

 Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

 Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Reasons for Discarded Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

6 Diagnostics and Troubleshooting

 Diagnostics and Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . 6-1

 Device Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

 Alarms Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

 System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

SYSLOG Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

SYSLOG Message Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

 Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Ping Test Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

 TraceRoute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

TraceRoute Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Contents

A Command Line Interface

 Command Line Interface Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Navigating the Router’s CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Command Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

 CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

RFC 1483 Encapsulation Command . . . . . . . . . . . . . . . . . . . . . . . A-5

Ethernet Frame Format Command . . . . . . . . . . . . . . . . . . . . . . . . A-5

Interface and Service Domain IP Address Commands . . . . . . . . . A-6

IP Routing Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Bridge Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

ARP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Proxy ARP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

NAT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11

DHCP Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

DHCP Relay Agent Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

IP Packet Processing Commands . . . . . . . . . . . . . . . . . . . . . . . . . A-17

PPPoE Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18

Telnet Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21

Traps Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23

Clearing Statistics Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23

6300-A2-GB20-10 November 2003

iii

Contents

Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24

B Configuration Defaults and Command Line Shortcuts

 Configuration Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

 Command Line Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

C Traps and MIBs

 SNMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

 Traps Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

DSL Router Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

 MIBs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

 Standard MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

MIB II (RFC 1213) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

Interfaces Group (RFC 1573) . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

Extension to Interfaces Table (RFC 1573) . . . . . . . . . . . . . . . . . . C-7

IP Group (RFC 1213). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

IP CIDR Route Group (RFC 2096) . . . . . . . . . . . . . . . . . . . . . . . . C-9

Transmission Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

SNMP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

Ethernet-Like MIB (RFC 2665) . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11

 Paradyne Enterprise MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11

Device Control MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12

Device Diagnostics MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Health and Status MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16

Configuration MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17

Interface Configuration MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18

ARP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18

NAT MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18

DHCP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19

DSL Endpoint MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

SYSLOG MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

Interface Configuration MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

D DSL Router Terminal Emulation

 DSL Router Terminal Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Accessing the List Command Output . . . . . . . . . . . . . . . . . . . . . . D-1

Terminal Emulation Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

iv November 2003 6300-A2-GB20-10

E Firmware Upgrade

 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

 Firmware Upgrade Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

 Firmware Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Index

Contents

6300-A2-GB20-10 November 2003

Contents

vi November 2003 6300-A2-GB20-10

About This Guide

Document Purpose and Intended Audience

This guide describes how to configure and operate Hotwire DSL routers. It addresses the following models:

 Hotwire 6301/6302 IDSL Router

 Hotwire 6341/6342 Symmetric DSL Router

 Hotwire 6351 ReachDSL Router

 Hotwire 6371 RADSL Router

This document is intended for administrators and operators who maintain the endpoints at customer premises. A basic understanding of internetworking protocols and their features is assumed. Specifically, you should have familiarity with the following internetworking concepts:

 TCP/IP applications

 IP and subnet addressing

 IP routing

 Bridging

It is also assumed that you have already installed a Hotwire DSL Router. If not, refer to Product-Related Documents for installation documents.

6300-A2-GB20-10 November 2003 vii

About This Guide

New Features for this Release

This version of the Hotwire DSL Routers User’s Guide documents firmware release 4.4, which adds the following new features for the Hotwire 6351 ReachDSL Router:

 IP passthrough. This feature allows the router to pass through or share its

public IP address with a single LAN device. The DSL router establishes a PPPoE and PPP session with the Network Access Server (NAS). The public IP address is negotiated via IPCP, installed on the router’s DSL interface, and served to the passthrough device via DHCP.

 Automatic configuration of options provided by the DHCP server to its clients.

This feature is available when PPPoE is enabled and is the default unless explicitly refused by the user. This allows the DHCP Server option configuration items to be set automatically with values negotiated during the network layer protocol phase of PPP (IPCP).

 Secondary DNS server. The DHCP server can specify a secondary DNS

server in its offer to a client.

 No router option required. Configuration of the DHCP Server feature no longer

requires that a value for the Router option be specified.

viii November 2003 6300-A2-GB20-10

Document Summary

Section Description

About This Guide

Chapter 1, Introduction to Hotwire

DSL Routers

Chapter 2, Accessing the DSL Router

Chapter 3, Configuring the DSL Router

Chapter 4, DSL Router Configuration Examples

Chapter 5, Monitoring the DSL Router

Chapter 6, Diagnostics and Troubleshooting

Appendix A, Command Line Interface

Appendix B, Configuration Defaults and Command Line Shortcuts

Appendix C, Traps and MIBs Summarizes the MIBs and SNMP traps supported

Appendix D, DSL Router Terminal

Emulation

Provides an overview of the Hotwire DSL Routers.

Describes the Hotwire DSL Routers access control and provides instructions on how to log in and log out of the system.

Describes the DSL router interfaces, Domain Types, IP Routing, and network considerations.

Presents several common DSL router configuration examples.

Describes operator programs that monitor the Hotwire system.

Describes common Hotwire operational problems and solutions. Contains SysLog information.

Provides explanation of the DSL router’s Command Line Interface and command syntax with examples.

Provides a list of all configuration options with factory default settings and a list of all command line shortcuts with the abbreviated command line input.

by the DSL routers.

Provides configuration setup procedures for two common text file programs.

Appendix E, Firmware Upgrade Provides commands and procedures for performing

a firmware upgrade for the Hotwire 6351 ReachDSL Router from the service domain.

Index Lists key terms, acronyms, concepts, and sections

in alphabetical order.

A master glossary of terms and acronyms used in Paradyne documents is available on the Web at www.paradyne.com. Select Library → Te ch n ica l

Manuals → Technical Glossary.

6300-A2-GB20-10 November 2003

About This Guide

Product-Related Documents

Document Number Document Title

5030-A2-GN10 Hotwire 5030 POTS Splitter Customer Premises

5038-A2-GN10 Hotwire 5038 Distributed POTS Splitter Customer

6050-A2-GZ40 Hotwire Central Office Universal POTS Splitter, Models

6301-A2-GN10 Hotwire 6301/6302 IDSL Routers Installation

6341-A2-GN10 Hotwire 6341/6342 SDSL Routers Installation

6351-A2-GN10 Hotwire 6351 ReachDSL Router Installation Instructions

6371-A2-GB20 Hotwire DSL Router User’s Guide (previous versions of

Installation Instructions

Premises Installation Instructions

6050 and 7020, Installation Instructions

Instructions

this document)

6371-A2-GN10 Hotwire 6371 RADSL Router Installation Instructions

8000-A2-GB22 Hotwire Management Communications Controller

(MCC) Card, IP Conservative, User's Guide

8000-A2-GB26 Hotwire MVL, ReachDSL, RADSL, IDSL, and SDSL

Cards, Models 8310, 8312/8314, 8510/8373/8374, 8303/8304, and 8343/8344, User's Guide

Contact your sales or service representative to order additional product documentation.

Paradyne documents are also available on the World Wide Web at

www.paradyne.com. Select Library → Technical Manuals →

Hotwire DSL Systems.

x November 2003 6300-A2-GB20-10

Document Conventions

The following conventions are used throughout this document.

Convention Translation

About This Guide

[ ]

{ }

Italics

Bold

x.x.x.x 32-bit IP address and mask information where x is an

xx:xx:xx:xx:xx:xx MAC address information where x is a hexadecimal

Square brackets represent an optional element.

Braces represent a required entry.

Vertical bar separates mutually exclusive elements.

Entry is a variable to be supplied by the operator.

Enter (type) as shown.

8-bit weighted decimal notation.

notation.

6300-A2-GB20-10 November 2003

About This Guide

xii November 2003 6300-A2-GB20-10

Introduction to Hotwire DSL Routers

What is a Hotwire DSL Router?

The Hotwire® DSL (Digital Subscriber Line) Router operates as a bridge and IP router connecting a DSL link to an Ethernet network. This system provides high-speed access to the Internet or a corporate network over a traditional twisted-pair copper telephone line to the end user.

DSL Technologies Supported

Paradyne’s Hotwire DSL network supports the following types of technologies:

 Hotwire IDSL (ISDN DSL) products provide IDSL multirate symmetric packet

transport and can operate over a connection with an ISDN repeater or digital facilities. Data rates of 64 Kbps, 128 Kbps, or 144 Kbps can be configured.

 Hotwire SDSL (Symmetric DSL) packet-based products provide high-speed

symmetric DSL services with bandwidth for business applications. These products are configurable from 144 Kbps up to 2.3 Mbps. This gives service providers the opportunity to sell multiple services with a single product.

 Hotwire ReachDSL™ packet-based products provide high-speed Internet or

corporate LAN access over traditional twisted-pair copper telephone wiring, regardless of line conditions (poor quality loops, long loops, or bad wiring at customer premises), for guaranteed service delivery up to 18,000 feet. These products are configurable from 128 Kbps up to 960 Kbps and give service providers the opportunity to sell multiple services using a single product.

 Hotwire RADSL (Rate Adaptive DSL) products are applicable for both

asymmetric and symmetric applications. The 1 Mbps symmetric operation is ideal for traditional business applications while the 7 Mbps downstream with

1.1 Mbps upstream asymmetric operation provides added bandwidth for corporate Internet access. RADSL products can also save line costs by optionally supporting simultaneous data and voice over the same line.

6300-A2-GB20-10 November 2003 1-1

1. Introduction to Hotwire DSL Routers

Typical DSL Router System

DSL is a local loop technology that uses standard twisted-pair copper wire to support high-speed access over a single pair of twisted copper wires. DSL applications are point-to-point, requiring DSL devices at central and end-user sites.

Hotwire DSL routers interoperate with the following types of Hotwire DSL line cards, at the DSLAM (Digital Subscriber Line Access Multiplexer) or GranDSLAM chassis, to deliver applications at high speeds, supporting packet services over a DSL link:

 Hotwire 8303 or 8304 IDSL Cards interoperate with two Hotwire IDSL Routers:

— Hotwire 6301 IDSL Router with one Ethernet port

— Hotwire 6302 IDSL Router with a 4-port Ethernet hub

 Hotwire 8343 or 8344 SDSL Cards interoperate with two Hotwire Symmetric

DSL Routers:

— Hotwire 6341 SDSL Router with one Ethernet port

— Hotwire 6342 SDSL Router with a 4-port Ethernet hub

 Hotwire 8312 or 8314 ReachDSL Cards interoperate with the Hotwire 6351

ReachDSL Router with one Ethernet port

 Hotwire 8510, 8373, and 8374 RADSL Cards interoperate with the Hotwire

6371 RADSL Router with one Ethernet port

The following illustration shows a typical Hotwire system with a Hotwire DSL Router. All Hotwire DSL routers transport data. The Hotwire 6371 RADSL Router can transport data and POTS simultaneously.

Customer Premises (CP)

Data

Interface

POTS

Voice

Interface

POTS

Splitter

Optional

Network

Service

Provider

Central Office (CO)

Hotwire

IPC

AT M

SCM

DSL

CARD

GranDSLAM

POTS

Splitter

Switched

Network

Optional

MDF

POTS/DSL

Legend: DSL – Digital Subscriber Line IPC – Interworking Packet Concentrator

MDF – Main Distribution Frame POTS – Plain Old Telephone Service SN – Service Node

01-16968

1-2 November 2003 6300-A2-GB20-10

Hotwire DSL Router Features

Hotwire DSL routers contain the following features.

 IP routing with:

— NAT (Network Address Translation)

— NAPT (Network Address Port Translation), also called PAT (Port Address

Translation)

— Simultaneous Basic NAT (for several fixed servers) and NAPT (on the rest

of the PCs on the LAN)

— DHCP Server (Dynamic Host Configuration Protocol) and DHCP Relay

Agent

— A full set of IP filters, two per DSL card (one for upstream and one for

downstream traffic), with up to 33 rules per filter

— SNMP Set/Get capability

 Three Configurable Modes of Operation. Supports the following modes of

operation:

1. Introduction to Hotwire DSL Routers

— IP routing only

— IP routing, and bridging of all other protocols (using VNET mode)

— Bridging all protocols (using VNET mode)

 Protocol Filters. Provides the ability to:

— Filter MAC frames when bridging

— Configure two Ethertype filters via the Hotwire DSL card, one for upstream

and one for downstream traffic, with up to 16 filter rules per filter

— Compare the Ethertype in frames to a particular value, or configured set of

values, to perform filtering

— Support ICMP (Internet Control Management Protocol) filters for firewalls

via the Hotwire DSL card, based on the ICMP message type, to selectively discard some ICMP message types while forwarding others

 High-speed Internet or intranet access.

 Diagnostics. Provides the capability to diagnose device and network

problems and perform tests.

 Device and Test Monitoring. Provides the capability of tracking and

evaluating the unit’s operation.

 Remote Firmware Download. Provides easy setup and activation of

firmware upgrades from a remote location.

 Security. Provides multiple levels of security, which prevents unauthorized

access to the DSL router.

6300-A2-GB20-10 November 2003

1-3

1. Introduction to Hotwire DSL Routers

 Console Terminal Interface. Provides an interface for:

— Configuring and managing the DSL router

— Local console access

 Management from an NMS using SNMP.

In addition, the following features are provided for the Hotwire 6351 ReachDSL Router:

 Telnet access to the Command Line Interface (CLI) in the service domain for

Network Service Provider (NSP) use.

 TFTP client support for NSP service domain software downloads.

 SYSLOG availability in the service domain.

 Point-to-Point Protocol over Ethernet (PPPoE) client provided as defined in

RFC 2516.

 Asymmetric maximum upstream/downstream setting.

Service Subscriber

The Service Subscriber is the user (or set of users) that has contracted to receive networking services (e.g., Internet access, remote LAN access) for the end-user system from an NSP (Network Service Provider). Service subscribers may be:

 Residential users connected to public network services (e.g., the Internet)

 Work-at-home users connected to their corporate intranet LAN

 Commercial users at corporate locations (e.g., branch offices) connected to

A Hotwire DSL Router must be installed at the customer premises to provide the end user with access to any of the above services.

other corporate locations or connected to public network services

NOTE:

If you would like more information on DSL-based services, applications, and network deployment, refer to Paradyne’s The DSL Sourcebook. The book may be downloaded or ordered through Paradyne’s World Wide Web site at www.paradyne.com/library.

1-4 November 2003 6300-A2-GB20-10

Accessing the DSL Router

Access Control to the DSL Router

The Hotwire DSL Router can be managed from an NMS using SNMP or from the Command Line Interface (CLI). There are several methods available for accessing the command line interface:

 Local access at the DSL router through the Console port.

 Access by a Telnet session (controlled through the management interface at

the Hotwire chassis).

 For the Hotwire 6351 ReachDSL Router, access by a Telnet session from the

service domain.

Levels of Access

The Hotwire DSL Router accepts only one login session at a time.

There are two levels of privileges on the Hotwire DSL system:

 Administrator. The Administrator has two levels of access to the DSL router.

— Administrator, non-configuration mode: Provides read-only capabilities.

This is the same level of access as Operator.

— Administrator, configuration mode: Provides complete write access to the

DSL router.

 Operator. The Operator has read-only access to display device information

with no modification permission and no access to management functions.

Refer to Appendix A, Command Line Interface, for access level details for each command line entry.

For local console access, the Operator and Administrator have the same Login ID, but with different passwords for their access level. For Telnet access through the service domain for the ReachDSL Router, up to four login/password/access level combinations can be configured.

6300-A2-GB20-10 November 2003 2-1

2. Accessing the DSL Router

Local Console Access

Your user account can be configured with one user login name and different passwords for accessing a CLI session. The DSL router ships with the local console enabled. After login, the local console can be disabled.

 To disable with the local console, type:

Press Enter after each command that you type.

Entering console disable results in NO local access to the DSL router. If you attempt to log in, you will receive an error message.

After saving this change and ending the session, there is no local access through the console port. Any access must be through a Telnet session or the NMS.

 To determine via a Telnet session whether a console is enabled, enter:

console disable save exit

show console

One of the following messages is returned:

— console enabled – Command line management is available at the

console.

— console disabled – No command line management is available at the

console.

Changing Access Session Levels

 To change the Administrator access level, enter:

admin enable

This command provides Administrator access privileges. The router responds with a prompt to enter the password for Administrator access.

 To end the Administrator access level, enter:

admin disable

This command ends the Administrator session. No password is needed.

Entering exit has the same result. Refer to Exiting from the System on page 2-7 for further details on ending a session.

 To determine the access level for a session, refer to Determining the Current

Access Level on page 2-5.

2-2 November 2003 6300-A2-GB20-10

Setting Up the New User’s Login

A login prompt appears when the local console connection is first established. When the login prompt appears, a locally connected console defaults to Console Enabled, with Operator access.

Procedure

To access the router’s CLI for the first-time:

1. At the initial Login> prompt, type the default login ID paradyne and press Enter.

2. At the Password> prompt (for Operator), type the default password abc123 and press Enter. The login ID and password are validated together when a login is entered.

3. At the system identity of CUSTOMER> prompt, type admin enable and press Enter.

4. At the Password> prompt (for Administrator), type the default password abc123 and press Enter.

2. Accessing the DSL Router

System identity changes to the Administrator display mode of CUSTOMER#>.

5. Type configure terminal and press Enter.

System identity changes to the Administrator configuration mode of CUSTOMER - CONFIG#>.

6. To change or add a new login ID, enter text to replace the default of

paradyne:

name your new login ID

NOTE:

7. Enter a new password and specify the level:

password level password

Example: Type password operator 238clrd3 and press Enter.

Both the login ID and password are 1– 31 printable alphanumeric ASCII characters, in the ASCII hex range of 0x21– 0x7E. No spaces are allowed.

The following table lists invalid characters.

Invalid Characters Value ASCII Hex Translation

# Number sign 0x23

$ Dollar sign 0x24

% Percentage 0x25

& Ampersand 0x26

6300-A2-GB20-10 November 2003

2-3

2. Accessing the DSL Router

Telnet Access

8. At the prompt, enter the new Administrator-level password to replace abc123:

password admin new password save

NOTE:

Any input during an Administrator configuration session must be saved while still in configuration mode.

If denied access during a Telnet session, the session stops and an error is logged.

If accessing the router locally and a Telnet session is active, you receive a Local console disabled by conflict message.

Telnet access through the management interface in the DSLAM is always enabled and defaults to Administrator level. For information on accessing the router through the MCC card in the DSLAM, see the Hotwire Management Communications Controller (MCC) Card, IP Conservative, User’s Guide.

For the Hotwire 6351 ReachDSL Router, Telnet access from the service domain is allowed. Telnet Login and a user name and password should be configured if Telnet access is enabled on the router (the factory default is disable). Up to four access level/login/password combinations can be configured for the service domain from which the ReachDSL Router will accept Telnet connections when the Telnet login feature is enabled.

NOTE:

For network security, Telnet access in the service domain should be disabled after the the initial remote configuration unless a firewall or some other security mechanism is used at the subscriber management system. This ensures that Telnet access to the endpoint is limited to the service provider.

Procedure

To set up Telnet access from the service domain:

1. Type configure terminal and press Enter.

System identity changes to the Administrator configuration mode of CUSTOMER - CONFIG#>.

2. Enable Telnet access form the service domain. Enter:

telnet enable save

2-4 November 2003 6300-A2-GB20-10

2. Accessing the DSL Router

3. To create a login ID and password for a specified access level, enter:

telnet name create level login ID password

Example: Type telnet name create operator 238clrd3 1234 and press Enter.

NOTE:

4. Enable Telnet login so that the ReachDSL Router will perform login and password validation for the Telnet session connection. Enter:

telnet login enable save

NOTE:

Any input during an Administrator configuration session must be saved while still in configuration mode.

Determining the Current Access Level

The command line prompt displays the access level. The factory default for System identity is CUSTOMER>. You can set your own system identity name to replace CUSTOMER. See the examples below.

Or, if a System identity of If the prompt format appears as . . .

CUSTOMER> PARADYNE> Operator, display mode

CUSTOMER #> PARADYNE #> Administrator, display

CUSTOMER – CONFIG#> PARADYNE – CONFIG#> Administrator,

Determining the Available Commands

To determine the commands available at the current login access level, enter any of the following:

 help

PARADYNE is entered, the

prompt displays . . .

Then the DSL router access level is . . .

mode

configuration mode

 ? (question mark)

 the command, without any parameters

6300-A2-GB20-10 November 2003

2-5

2. Accessing the DSL Router

Using the List Command

The list command displays a sequence of commands in the form of ASCII strings that would have the effect of setting all configuration settings to the current values. Secure information such as passwords and login IDs are not displayed.

To determine the commands available, enter Administrator configuration mode and type either:

 list

Displays the output in on-screen page mode. In on-screen page mode, the user interface displays 23 lines of information. When the 24th line is reached, More... appears. Pressing any key displays the next page.

 list config

Displays the output in scroll mode as a text file. Scroll mode captures and displays all command strings in a text file for use with a terminal emulation program. Refer to Appendix D, DSL Router Terminal Emulation.

Changing the System Identity

The System identity is the same as the MIB entry of sysName. The sysContact

and sysLocation MIB entries are not displayed.

Procedure

To change System identity from the factory default of CUSTOMER>:

1. Log in and enter ADMIN-configuration mode.

2. At the CUSTOMER-CONFIG#> prompt, type the new System identity

(no spaces allowed) and press Enter. Then type save and press Enter.

system identity new system identity

For example:

system identity PARADYNE save

In this example, after saving the entry and ending configuration mode, the System identity will display:

PARADYNE#>

Refer to Exiting from the System on page 2-7 to end configuration mode.

2-6 November 2003 6300-A2-GB20-10

Exiting from the System

You can manually log out of the system, or let the system automatically log you out. The DSL router will log you out immediately if you disconnect the Console cable. Any unsaved configuration input will be lost.

Manually Logging Out

To log out, there are two commands: logout and exit.

Procedure

To log out of a CLI session:

1. At the > prompt, type logout and press Enter.

2. The system ends the session immediately. Any configuration updates must

be saved before exiting or the updates will be lost.

Procedure

2. Accessing the DSL Router

To exit the DSL router’s current access level:

1. At the > prompt, type exit and press Enter. If there are any unsaved

configuration changes, you will be prompted to save changes before exiting.

2. The exit command has the following effect:

If accessing the DSL router . . . Then . . .

At the Local console and logged in at the Administrator level, configuration mode

At the Local console and logged in at the Administrator level, non-configuration mode

At the Local console and logged in at the Operator level

Via a Telnet session and logged in at any access level

You are placed at the Operator level. Any configuration updates must be saved or they will be lost.

You are placed at the Operator level.

The exit command responds exactly like the Logout command.

Entering either of the following immediately ends the Telnet session:



exit



Ctrl + ] (Control and right bracket keys)

6300-A2-GB20-10 November 2003

2-7

2. Accessing the DSL Router

Automatically Logging Out

The DSL router has an automatic timeout feature that logs you out of the system after five minutes of inactivity. Unsaved configuration input is lost. The default for the autologout command is enable.

When autologout is:

 Enabled, the system inactivity timer is enabled.

 Disabled, the system inactivity timer is disabled.

To log back in, press Enter at the console to display the Login> prompt.

For Telnet access through the service domain for the ReachDSL Router, the Telnet session is automatically closed after a user-configurable number of minutes. The default for the telnet timeout command is 5 (minutes). The telnet timeout command overrides the 5-minute limit enabled by the autologout command. Also, the telnet keep-alive command can be enabled which allows the ReachDSL Router to close the Telnet session if it detects that the service domain Telnet client has crashed and is down or has rebooted.

2-8 November 2003 6300-A2-GB20-10

Configuring the DSL Router

DSL Router Configuration Overview

Hotwire DSL Routers support various customer premises distribution networks that contain IP forwarding devices or routers, as well as locally attached hosts or subnets. The Hotwire DSL Router’s IP Routing Table contains IP address and subnet mask information.

The DSL router supports Internet Protocol, as specified in RFC 791, and Internet Control Message Protocol (ICMP), as specified in RFCs 792 and 950. It acts as a router (or gateway), as defined in RFC 791. It also acts as a bridge, bridging all traffic in the service domain, or routing IP traffic and bridging all other traffic in the service domain, without affecting traffic in the management domain.

For more information on supported RFCs, refer to Appendix C, Traps and MIBs.

The DSL Router’s Interfaces

Hotwire DSL Routers have two interfaces: the DSL interface and the Ethernet interface.

 DSL Interface

The router’s interface type is determined by its model number:

— Models 6301 and 6302 are Hotwire IDSL Routers.

— Models 6341 and 6342 are Hotwire SDSL Routers.

— Model 6351 is the Hotwire ReachDSL Router.

— Model 6371 is the Hotwire RADSL Router.

The DSL interface has a unique MAC address, assigned before the router is shipped.

6300-A2-GB20-10 November 2003 3-1

3. Configuring the DSL Router

 Ethernet Interface

— The Ethernet interface is a 10/100BaseT interface that automatically

negotiates the rate to be used, 10 Mb or 100 Mb. If all Ethernet-attached devices are capable of operating at 100 Mb, the router defaults to 100 Mb. Otherwise, it operates at 10 Mb.

— The interface can be configured for either DIX or IEEE 802.3 frame format.

When configured to use IEEE 802.3 format, SNAP encapsulation is used, as specified in RFC 1042.

— The interface has a unique MAC address, assigned before the router is

shipped.

— Hotwire 6302 IDSL and 6342 SDSL Routers have a hub configuration

(separate pins for input and output) with four Ethernet connectors. The hub acts as a bit-level repeater, with the four Ethernet interfaces logically appearing as one Ethernet communications interface with a single collision domain.

— In router mode, the router only accepts transmissions on the Ethernet

interface with the interface’s MAC address, or a broadcast or multicast MAC address.

— In bridge mode, the router accepts all transmissions. This is the default

setting.

Interface Identifiers

The following conventions are used for naming router interfaces:

 dsl1 (or d0) – Identifier for the DSL interface.

 eth1 (or e0) – Identifier for the Ethernet interface.

With exception to primary status, an interface cannot be deleted or changed as long as there is a declared route that uses the interface.

Service Domain IP Address Assignments

Hotwire DSL Routers support multiple service domains.

 Service domains are defined by the configured network addresses and subnet

masks using the CLI.

 Up to four service domain IP addresses and subnet masks can be assigned to

each DSL (dsl1) or Ethernet (eth1) interface.

When a numbered interface is designated as the primary interface, that interface’s IP address is used as the Router ID. If no interface is designated as the primary interface, the last numbered interface that was created becomes the Router ID.

3-2 November 2003 6300-A2-GB20-10

Numbered DSL or Ethernet Interface

In this scenario, the hosts attached to the DSL router’s Ethernet interface are on a different logical network than the core router. The DSL router is the next hop router for the hosts. The DSL router’s upstream next hop router is the core router.

Simplified Network Topology

3. Configuring the DSL Router

Core

Router

Hosts can be assigned IP addresses on the network attached to the DSL router’s Ethernet interface either statically or dynamically using DHCP. The upstream next hop router is assigned an address on a different logical network than the hosts.

To configure the router’s interfaces using this scenario, you must:

 Enable routing on the DSL router.

 Assign an IP address to the Ethernet interface, eth1.

 Assign an IP address to the DSL interface, dsl1.

 Assign an upstream next hop router (not necessary necessary when using

FUNI/MPOA DSL link encapsulation or when the PPPoE client is enabled).

Unnumbered DSL Interface

In this LAN extension application scenario, hosts connected to a corporate network for virtual office connections or telecommuters want to look like they are on the same network as the core router. The core router is the next hop router for the hosts and is on the same logical network as the hosts. This is not the same as enabling Bridging mode.

WAN

DSL

Router

Host

(End Users)

99-16609

To configure the router’s interfaces for this scenario, you must:

 Enable routing on the DSL router.

 Assign an IP address to Ethernet interface (eth1).

 Specify the DSL interface (dsl1) as unnumbered.

 Assign an upstream next hop router (not necessary necessary when using

FUNI/MPOA DSL link encapsulation or when the PPPoE client is enabled).

 Enable Proxy ARP for both the eth1 and dsl1 interfaces (not necessary to

enable Proxy ARP on the dsl1 interface when using FUNI/MPOA DSL link encapsulation or when the PPPoE client is enabled).

6300-A2-GB20-10 November 2003

3-3

3. Configuring the DSL Router

IP Routing

Hotwire DSL Routers use destination-based routing for downstream traffic. An IP Routing Table is maintained to specify how IP datagrams are forwarded downstream. The DSL Router is capable of supporting static routes configured by the user. This table can be viewed by both Operator and Administrator access levels.

The DSL router uses source-based forwarding for upstream traffic to ensure that packets are forwarded to the upstream router specified for the configured service domain.

Refer to Chapter 4, DSL Router Configuration Examples, for further details.

IP Options Processing

The DSL router handles and processes IP datagrams with options set as described below. No command is available to set IP options.

The router does not process (and drops) any IP datagrams with the following IP options:

 Loose source and record route (type 131)

 Strict source and record route (type 133)

 Security (type 130)

 Stream ID (type 136)

The router does process IP datagrams with the following IP options, but does not provide its IP address or timestamp information in the response message:

 Record route (type 7)

 Timestamp (type 68)

3-4 November 2003 6300-A2-GB20-10

+ 116 hidden pages