Paradyne 6342 User Manual
Hotwire
Document No. 6371-A2-GB20-20
®
DSL Routers
User’s Guide
May 2001
Copyright © 2001 Paradyne Corporation.
All rights reserved.
Printed in U.S.A.
Notice
This publication is protected by federal copyright law. No part of this publication may be copied or distributed,
transmitted, tr ansc ribed, store d in a re trie v al syst em, or tr ans lated into a n y huma n or com puter l anguag e in an y form or
by any means, electronic, mechanical, magnetic, manual or otherwis e , or disclosed to third parties without the ex pre ss
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 sale s representativ e, se rvice representativ e, or distrib utor directly f or any hel p needed. F or additional
information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or
Paradyne worldwide office locations, use one of the following methods:
Internet:
www.paradyne.com/warranty
Telephone:
representative.
— Within the U.S.A., call 1-800-870-2221
— Outside the U.S.A., call 1-727-530-2340
Visit the Paradyne World Wide Web s i te at
.)
Call our automated system to receive current information by fax or to speak with a company
www.paradyne.com
. (Be sure to register your warranty at
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
number and title of this document in your correspondence. Please include your name and phone number if you are
willing to provide additional clarification.
userdoc@paradyne.com
. Include the
Trademarks
ACCULINK, COMSPHERE, FrameSaver, Hotwire, MVL, NextEDGE, OpenLane, and Performance Wizard are
registered trademarks of Paradyne Corporation. ReachDSL and TruePut are trademarks of Paradyne Corporation. All
other products and s ervices m en tion ed here in are the trademarks, service marks , reg is tere d trademarks, or registered
service marks of their respective owners.
May 2001 6371-A2-GB20-20
A
Contents
About This Guide
Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . vii
Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
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
Changing Access Session Levels . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Local Console Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Setting Up the New User's Login. . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Telnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Determining the Current Access Level . . . . . . . . . . . . . . . . . . . . . 2-4
Determining the Available Commands . . . . . . . . . . . . . . . . . . . . . 2-4
Using the List Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Changing the System Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Exiting from the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Manually Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Automatically Logging Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
6371-A2-GB20-20 May 2001
i
Contents
3 Configuring the DSL Router
DSL Router Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
The DSL Router’s Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Interface Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Service Domain IP Address Assignments. . . . . . . . . . . . . . . . . . . . . . 3-2
Numbered DSL or Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . 3-3
Unnumbered DSL Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Address Resolution Protocol (ARP). . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Basic NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Network Address Port Translation (NAPT/PAT) . . . . . . . . . . . . . . 3-6
Simultaneous Basic NAT and NAPT . . . . . . . . . . . . . . . . . . . . . . . 3-7
IP Options Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Applications Supported by NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Dynamic Host Configuration Protocol (DHCP) Server. . . . . . . . . . . . . 3-8
DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
IP Protocol Type Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Ethernet Type Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Land Bug/Smurf Attack Prevention . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Routed vs. Bridged PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
DHCP Relay with Proxy ARP Configuration Example. . . . . . . . . . 4-11
DHCP Server with Basic NAT Configuration Example . . . . . . . . . 4-12
Downstream Router Configuration Example . . . . . . . . . . . . . . . . . 4-13
May 2001 6371-A2-GB20-20
ii
5 Monitoring the DSL Router
Monitoring the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
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
6371-A2-GB20-20 May 2001
iii
Contents
A Command Line Interface
Command Line Interface Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Navigating the Router’s CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
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-15
IP Packet Processing Commands. . . . . . . . . . . . . . . . . . . . . . . . . A-16
Traps Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Clearing Statistics Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
B Configuration Defaults and Command Line Shortcuts
Configuration Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Command Line Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
May 2001 6371-A2-GB20-20
iv
C Traps and MIBs
SNMP Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Traps Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
MIBs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Standard MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Paradyne Enterprise MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Contents
DSL Router Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
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
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
Index
6371-A2-GB20-20 May 2001
v
Contents
May 2001 6371-A2-GB20-20
vi
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.
6371-A2-GB20-20 May 2001
vii
About This Guide
Document Summary
Section Description
Chapter 1,
Routers
Chapter 2,
Chapter 3,
Chapter 4,
Examples
Chapter 5,
Chapter 6,
Troubleshooting
Appendix A,
Appendix B,
and Command Line Shortcuts
Appendix C,
Introduction to Hotw ire DSL
Accessing the DSL Router
Configuring the DSL Router
DSL Router Configuration
Monitoring the DSL Router
Diagnostics and
Command Line Interface
Configuration Defaults
Traps and MIBs
Provides an overview of the Hotwire DSL
Routers.
Describes the Hotwire DSL Routers access
control and provide s instructions on ho w 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 al l c om ma nd
line shortcuts with the abbre viated comma nd line
input.
Summarizes the MIBs and SNMP traps
supported by the DSL routers.
Appendix D,
Emulation
Index
DSL Router Terminal
Provides configuration setup procedures for two
common text file programs.
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
Manuals
→
Technical Glossary.
www.paradyne.com
. Select
Library → Technical
May 2001 6371-A2-GB20-20
viii
Product-Related Documents
Docume n t Number Docume n t Title
About This Guide
5030-A2-GN10
5038-A2-GN10
6050-A2-GZ40
6301-A2-GN10
6341-A2-GN10
6351-A2-GN10
6371-A2-GN10
8000-A2-GB22
8000-A2-GB26
Hotwire 5030 POTS Splitter Customer Premises
Installation Instructions
Hotwire 5038 Distributed POTS Splitter Customer
Premises Installation Instructions
Hotwire Central Office Universal POTS Splitter, Models
6050 and 7020, Installation Instructions
Hotwire 6301/6302 IDSL Routers Installation
Instructions
Hotwire 6341/6342 SDSL Routers Installation
Instructions
Hotwire 6351 ReachDSL Router Installation Instructions
Hotwire 6371 RADSL Router Installation Instructions
Hotwire Management Communications Controller
(MCC) Card, IP Conservative, User's Guide
Hotwire MVL, ReachDSL/MVL, 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
Hotwire DSL and MVL Systems
. Select
Library → Technical Manuals →
.
6371-A2-GB20-20 May 2001
ix
About This Guide
Document Conventions
The following conventions are used throughout this document.
Convention Translation
[ ]
{ }
|
Italics
Bold
x.x.x.x
xx:xx:xx:xx:xx:xx
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.
32-bit IP address and mask information where x is an
8-bit weighted decimal notation.
MAC address information where x is a hexadecimal
notation.
May 2001 6371-A2-GB20-20
x
Introducti on 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:
1
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 Mbps 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.
6371-A2-GB20-20 May 2001
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
SN
POTS
Voice
Interface
CP
POTS
Splitter
Optional
Network
Service
Provider
Central Office (CO)
Hotwire
IPC
ATM
SCM
DSL
CARD
GranDSLAM
CO
POTS
Splitter
Switched
Network
Optional
MDF
POTS/DSL
Legend: DSL – Digital Subscriber Line IPC –Interworking Packet Concentrator
May 2001 6371-A2-GB20-20
1-2
MDF – Main Distribution Frame POTS – Plain Old Telephone Service
SN – Service Node
01-16968
Hotwire DSL Router Features
The 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 capabil it y
Three Configurable Modes of Operation.
operation:
:
1. Introduction to Hotwire DSL Routers
Supports the following modes of
— 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.
6371-A2-GB20-20 May 2001
1-3
1. Introduction to Hotwire DSL Routers
Console Terminal Interface.
— Configuring and managing the DSL router
— Terminal access
Management from an NMS using SNMP.
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
other corporate locations or connected to public network services
Provides an interface for:
A Hotwire DSL Router must be installed at the customer premises to provide the
end user with access to any of the above services.
NOTE:
If you would like more information on DSL-based services, applications, and
network deployment, refer to Paradyne’s
may be downloaded or ordered through Paradyne’s World Wide Web site at
www.paradyne.com/library
.
The DSL Sourcebook.
The book
May 2001 6371-A2-GB20-20
1-4
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 two methods to access the command
line interface:
Local access at the DSL router through the Console port, or
Access by a Telnet session (controlled through the management interface at
the Hotwire chassis).
2
Levels of Access
When a local console connection is first established, a login prompt appears. The
Hotwire DSL Router accepts only one login session at a time. It is configured at
the factory with a default login ID and password. Howev er , to provide login security
to the DSL system or set up a new user’s log in, r efer to
Login
on page 2-3.
There is one login ID and two levels of privileges on the Hotwire DSL system.
Your user account can be configured with one user name and different
passwords for:
Administrator
— 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. However, MIB sets are done from the NMS vs. the command
line.
Operator
with no modification permission and no access to management functions.
Refer to Appendix A,
command line entr y.
. The Administrator has two levels of access to the DSL router.
. The Operator has read-only access to display device information
Command Line Interface
, for access level details for each
Setting Up the New User's
6371-A2-GB20-20 May 2001
2-1
2. Accessing the DSL Router
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.
Local Console Access
Entering
exit
has the same result. Refer to
Exiting from the System
on
page 2-5 for further details on ending a session.
The Operator and Administrator have the same Login ID, but with different
passwords for their access level.
To determine the access level for a session, refer to
Access Level
on page 2-4.
Determining the Curre nt
The DSL router ships with the local console enabled. After login, the local console
can be disabled.
To disable with the local console, type:
console disable
save
exit
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:
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.
May 2001 6371-A2-GB20-20
2-2
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:
2. Accessing the DSL Router
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
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.
abc123
Password>
and press Enter.
prompt (for Administrator), type the default password
System identity changes to the Administrator display mode of
configure terminal
and press Enter.
CUSTOMER#>
4. At the
5. Type
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:
Login ID and password are NOT case-sensitive.
abc123
.
7. Enter a new password and specify the level:
password
Example: Type
level password
password operator 238clrd3
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
#
$
%
&
6371-A2-GB20-20 May 2001
Number sign 0x23
Dollar sig n 0x24
Percentage 0x25
Ampersand 0x26
and press Enter.
2-3
2. Accessing the DSL Router
8. At the prompt, enter the new Administrator-level password to replace
password admin
save
NOTE:
Any input during an Administrator configuration session must be saved
while still in configuration mode.
If denied access during a T elnet 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
Telnet Access
Telnet access defaults to Administrator level. If the login is at the Operator level,
then Operator level access is available. Telnet access is always enabled.
Determining the Current Access Level
The command line prompt displays the access level. The factory default for
System identity is
replace
CUSTOMER
new password
CUSTOMER>
. You can set your own system identity name to
. See the examples below.
message.
abc123
:
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
?
(question mark)
the command, without any parameters
Or, if a System identity of
PARADYNE is entered, the
prompt displays . . .
Then the DSL router
access level is . . .
mode
configuration mode
May 2001 6371-A2-GB20-20
2-4
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.
(The two passwords are not output.)
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...
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,
Changing the System Identity
2. Accessing the DSL Router
appears. Pressing any key displays the next page.
DSL Router Terminal Emulation.
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
1. Log in and enter ADMIN-configuration mode.
2. At the
CUSTOMER-CONFIG#>
(no spaces allowed) and press Enter. Then type
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
prompt, type the new System identity
new system identity
to end configuration mode.
CUSTOMER>
save
and press Enter.
:
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.
6371-A2-GB20-20 May 2001
2-5
2. Accessing the DSL Router
Manually Logging Out
To log out, there are two commands:
logout
and
exit
.
Procedure
To log out of a CLI or Telnet 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
To exit the DSL router’s current access level:
1. At the > prompt, type
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
exit
and press Enter. If there are any unsaved
You are placed at the Operator level. Any
configuration updates must be saved or
they will be lost.
At the Local console and logged in at
the Admini strator 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
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.
To log back in, press Enter at the console to display the
default for the
{enable | disable}
When
Enabled, the system inactivity timer is enabled.
Disabled, the system inactivity timer is disabled.
autologout
autologout
command is enable (appears as
in command line syntax).
is:
You are placed at the Operator level.
exit
The
the Logout command.
Entering either of the following immediately
ends the Telnet session:
command responds exactly like
exit
Ctrl + ]
(Control and right bracket keys)
Login>
prompt. The
autologout
May 2001 6371-A2-GB20-20
2-6
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.
3
For more information on supported RFCs, refer to
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.
Appendix C, Traps and MIBs.
6371-A2-GB20-20 May 2001
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 M b.
— 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.
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
This is the default
) 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.
May 2001 6371-A2-GB20-20
3-2
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 ro uter’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.
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 ro uter’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.
Enable Proxy ARP for both the eth1 and dsl1 interfaces.
6371-A2-GB20-20 May 2001
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,
Network Considerations
The routers can be configured to function in a variety of network environments.
The following sections provide descriptions of some of the router’s features:
Address Resolution Protocol (ARP)
Proxy ARP
Network Address Translation (NAT)
Basic NAT
—
Network Address Port Translation (NAPT/PAT)
—
IP Options Processing
—
Simultaneous Basic NAT and NAPT
—
Dynamic Host Configuration Protocol (DHCP) Server
DHCP Relay Agent
Security
IP Protocol Type Filtering
—
DSL Router Configuration Examples,
on page 3-5
on page 3-9
on page 3-10
for further details.
on page 3-5
on page 3-6
on page 3-8
Ethernet Type Filtering
—
Land Bug/Smurf Attack Prevention
—
Routed vs. Bridged PDUs
May 2001 6371-A2-GB20-20
3-4
on page 3-12
Address Resolution Protocol (ARP)
Address Resolution Protocol, as specified in RFC 826, is supported in the router.
Up to 265 ARP Tab le entries are supported, and a timeout period for complete and
incomplete ARP Table entries can be configured.
ARP requests and responses are not processed on the DSL interface when the
interface is configured to support RFC 1483 PDU routing (Standard mode). Refer
Routed vs. Bridged PDUs
to
Operating mode (Standard or VNET) can be changed without reconfiguration of
the router. Static ARP entries can be configured, regardless of the current
operating mode. If static ARP entries are configured, they remain in the database
and can be displayed using the
Using CLI commands, you can:
Create up to 64 static ARP Table entries.
Display the ARP Table.
Delete ARP Table entries.
on page 3-12 for more information.
show arp
3. Configuring the DSL Router
CLI command.
Proxy ARP
Display and delete automatically added ARP Tab le entries made by the DHCP
server and relay functions. Refer to
(DHCP) Server
The DSL router supports Proxy ARP. Proxy ARP responses are based on the
contents of the IP Routing Table for service domain traffic. The table must have
entry information that indicates what hosts can be reached on the Ethernet
interface, including hosts for which the router will not forward packets because of
IP filters. For additonal information on filtering, see
page 3-10.
Proxy ARP is not available on the DSL interface when the router is configured to
support RFC 1483 PDU routing. See
more information.
If an ARP request is received on one interface, and the requested IP address can
be reached on the other interface, the router responds with its own MAC address.
Using CLI commands, you can enable and disable Proxy ARP for each interface.
on page 3-8.
Dynamic Host Configuration Protocol
IP Protocol Type Filtering
Routed vs. Bridged PDUs
on page 3-12 for
on
NOTE:
When Basic NA T is enabled, the DSL interface (dsl1) must have Proxy ARP
enabled when the dsl1 interface address is part of the Basic NAT global IP
network address.
6371-A2-GB20-20 May 2001
3-5
3. Configuring the DSL Router
Network Address Translation (NAT)
The DSL router provides NAT, as described in RFC 1631, IP Network Address
Translator (NAT).
access the external (public or global) network using either a block of public IP
addresses (Basic NAT) or a single IP address (NAPT). Static mapping enables
access to selected local hosts from outside using these external IP addresses.
NAT is used when a private network’s internal IP addresses cannot be used
outside the private network. IP addresses may be restricted for privacy reasons, or
they may not be valid public IP addresses.
Simultaneous Basic NAT and Network Address Port Translation (NAPT) are
supported. Refer to
information.
Basic NAT
Basic NAT allows hosts in a private network to transparently access the external
network by using a block of public addresses. Static mapping enables access to
selected local hosts from the outside. Basic NAT is often used in a large
organization with a large network that is set up for internal use, with the need for
occasional external access.
NAT allows hosts in a private (local) network to transparently
Simultaneous Basic NAT and NAPT
on page 3-7 for additional
Basic NAT provides a one-to-one mapping by translating a range of assigned
public IP addresses to a similar-sized pool of private addresses (typically from the
x.x.x
10.
host appears to have an unique IP address.
address space). Each local host currently communicating with a external
IP addresses
A total of 256 IP addresses can be allocated for use with Basic NAT. Two IP
addresses are reserved, and 254 IP addresses are available for use. Up to
64 static mappings can be configured.
Network Address Port Translation (NAPT/PAT)
NAPT allows multiple clients in a local network to simultaneously access remote
networks using a single IP address. This benefits telecommuters and SOHO
(Small Office/Home Office) users that have multiple clients in an office running
TCP/UDP applications. NAPT is sometimes referred to as PAT (Port Address
Translation).
NAPT provides a many-to-one mapping and uses one public address to interface
numerous private users to an external network. All hosts on the global side view
all hosts on the local side as one Internet host. The local hosts continue to use
their corporate or private addresses. When the hosts are communicating with
each other, the translation is based on the IP address and the protocol port
numbers used by TCP/IP applications.
May 2001 6371-A2-GB20-20
3-6
Simultaneous Basic NAT and NAPT
Simultaneous Basic NAT and NAPT (or PAT) are supported. In this mode, the
servers (private IP addresses) using Basic NAT are configured and the devices
(private IP addresses) using NAPT are optionally configured (static mappings). If
not configured, the remaining private IP addresses default to NAPT.
Enabling Basic NAT does not disable NAPT. When both Basic NAT and NAPT are
enabled, Proxy ARP can also be enabled, although it is only used for Basic NAT.
IP Options Processing
Basic NA T and NAPT functions handle and process the 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)
3. Configuring the DSL Router
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)
Applications Supported by NAT
The DSL routers support the following applications and protocols:
FTP
HTTP
Ping
RealPlayer
Telnet
TFTP
6371-A2-GB20-20 May 2001
3-7
3. Configuring the DSL Router
Dynamic Host Configuration Protocol (DHCP) Server
The router provides a DHCP Server feature, as specified in RFC 2131, Dynamic
Host Configuration Protocol, and RFC 2132, DHCP Option and BOOTP Vendor
Extensions. DHCP is the protocol used for automatic IP address assignment.
DHCP setup considerations:
The range of IP addresses to be used by the DHCP server must be
configured. The maximum number of clients is 256.
The DHCP server is not activated until one IP address and subnet mask are
assigned to the Ethernet interface and routing is enabled.
The DHCP server must be enabled, and the DHCP server and DHCP relay
functions cannot be enabled at the same time.
When the DHCP IP address range is changed, all binding entries,
automatically added routes, and ARP Table entries for the clients configured
with the old address range are removed.
When the DHCP Server is enabled, there can be only one IP address
configured for the service domain (Ethernet interface).
The IP address for the next hop router provided to the hosts in the DHCP reply
must be configured.
The subnet mask can be configured along with the IP address range
(optional).
The DHCP server domain name can be configured (optional).
The Domain Name Server (DNS) IP address can be configured (optional).
A minimum and maximum lease time setting can be configured.
For additional information, refer to Chapter 4,
DSL Router Configuration
Examples.
May 2001 6371-A2-GB20-20
3-8
Loading...