Paradyne Hotwire 6321/6322 IDSL Router, Hotwire 6371 RADSL Router, Hotwire 6341/6342 Symmetric DSL Router User Manual

Page 1
HOTWIREr DSL ROUTERS
USERS GUIDE
Document No. 6371-A2-GB20-00
March 2000
Page 2
Copyright E 2000 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, 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:
H Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty
at www.paradyne.com/warranty.)
H 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.
Trademarks
ACCULINK, COMSPHERE, FrameSaver, and Hotwire are registered trademarks of Paradyne Corporation. NextEDGE, MVL, OpenLane, Performance Wizard, and TruePut 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
March 2000
Page 3
Table of Contents
About This Guide
H Document Purpose and Intended Audience v. . . . . . . . . . . . . . . . . . . . . . . . .
H Document Summary vi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Product-Related Documents vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Document Conventions viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Introduction to Hotwire DSL Routers
H What is a Hotwire DSL Router? 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSL Technologies Supported 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Typical DSL Router System 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Hotwire DSL Router Features 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Service Subscriber 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Accessing the DSL Router
H 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 Users 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Exiting from the System 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Logging Out 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatically Logging Out 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
March 2000
i
Page 4
Contents
3 Configuring the DSL Router
H Overview of DSL Router Configuration 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Interfaces for the DSL Router 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSL Interface 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Interface 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet and DSL Interface Identifiers 3-2. . . . . . . . . . . . . . . . . . . . . . . . . .
Service Domain IP Address Assignments 3-2. . . . . . . . . . . . . . . . . . . . . . .
Numbered DSL Interface 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unnumbered DSL Interface 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H IP Routing 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Network Considerations 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address Resolution Protocol (ARP) 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proxy ARP 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Network Address Translation (NAT) 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic NAT 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Address Port Translation (NAPT) 3-6. . . . . . . . . . . . . . . . . . . . . .
Applications Supported by NAT 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Host Configuration Protocol (DHCP) Server 3-7. . . . . . . . . . . .
DHCP Relay Agent 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Filtering 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 DSL Router Configuration Examples
H Configuration Examples 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Configuration Example 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic NAT Configuration Example 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NAPT Configuration Example 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unnumbered DSL Interface with Proxy ARP Configuration Example 4-5
DHCP Relay with Proxy ARP Configuration Example 4-6. . . . . . . . . . . . .
DHCP Server with Basic NAT Configuration Example 4-7. . . . . . . . . . . .
Downstream Router Configuration Example 4-8. . . . . . . . . . . . . . . . . . . . .
5 Monitoring the DSL Router
H What to Monitor 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Detecting Problems 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status of Interfaces 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Statistics 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Clearing Statistics 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Discard Reasons 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
March 2000
Page 5
6 Diagnostics and Troubleshooting
H Diagnostics and Troubleshooting Overview 6-1. . . . . . . . . . . . . . . . . . . . . . . . .
H Device Restart 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Alarms Inquiry 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H System Log 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSLOG Events 6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSLOG Message Display 6-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H PING 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PING Test Results 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H TraceRoute 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TraceRoute Test Results 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Command Line Interface
H Command Line Interface Feature A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigation A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Conventions A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Command Line Interface Commands A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Control Commands A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Frame Format A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface and Service Domain IP Address A-3. . . . . . . . . . . . . . . . . . . . . .
IP Routing Table A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ARP Table A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proxy ARP A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NAT A-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHCP Server A-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHCP Relay Agent A-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Packet Processing A-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Show Command Outputs A-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
B Configuration Defaults & Command Line Shortcuts
H Configuration Default Settings B-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Command Line Input Shortcuts B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C DSL Router Terminal Emulation
H DSL Router Terminal Emulation C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index
Accessing the List Command Output C-1. . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Emulation Programs C-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
March 2000
iii
Page 6
Contents
This page intentionally left blank.
iv
March 2000
Page 7
About This Guide
Document Purpose and Intended Audience
This guide describes how to configure and operate Hotwire DSL routers. This document addresses the use of the following Hotwire DSL Router models:
H Hotwire 6321/6322 IDSL Router H Hotwire 6341/6342 Symmetric DSL Router H 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:
H TCP/IP applications H IP and subnet addressing H IP routing H Bridging
It is also assumed that you have already installed a Hotwire DSL Router. If not, refer to Product-Related Documents on page vii for installation documents.
March 2000
v
Page 8
About This Guide
Document Summary
Section Description
Chapter 1 Introduction to Hotwire DSL Routers. Provides an overview
Chapter 2 Accessing the DSL Router. Describes the Hotwire DSL
Chapter 3 Configuring the DSL Router. Describes the DSL router
Chapter 4 DSL Router Configuration Examples. Presents several
Chapter 5 Monitoring the DSL Router. Describes operator programs
Chapter 6 Diagnostics and Troubleshooting. Describes common
of the Hotwire DSL Routers.
Routers access control and provides instructions on how to log in and log out of the system.
interfaces, Domain Types, IP Routing, and network considerations.
common DSL router configuration examples.
that monitor the Hotwire system.
Hotwire operational problems and solutions. Contains SysLog information.
Appendix A Command Line Interface. Provides explanation of the DSL
routers Command Line Interface and command syntax with examples.
Appendix B Configuration Defaults & Command Line Shortcuts.
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.
Appendix C DSL Router Terminal Emulation. Provides configuration
setup procedures for two common text file programs.
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 Technical
Manuals Technical Glossary.
vi
March 2000
Page 9
Product-Related Documents
Contact your sales or service representative to order additional product documentation.
Document Number Document Title
6321-A2-GN10 Hotwire 6321/6322 IDSL Routers Installation
6341-A2-GN10 Hotwire 6341/6342 Symmetric DSL Routers
6371-A2-GN10 Hotwire 6371 Rate Adaptive DSL Router Installation
8000-A2-GB22 Hotwire Management Communications Controller
8000-A2-GB26 Hotwire MVL, RADSL, IDSL, and Packet SDSL Cards,
About This Guide
Instructions
Installation Instructions
Instructions
(MCC) Card, IP Conservative, User’s Guide
Models 8310/8312, 8510/8373/8374, 8323/8324, 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 & MVL.
March 2000
vii
Page 10
About This Guide
Document Conventions
The following syntax is used throughout this document.
Syntax Translation
[ ] { }
|
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.
viii
March 2000
Page 11
Introduction to Hotwire DSL Routers
What is a Hotwire DSL Router?
The Hotwirer DSL (Digital Subscriber Line) Router operates as an IP router connecting a DSL link to an Ethernet network. This system provides high-speed Internet or corporate LAN (Local Area Network) access over traditional twisted-pair copper telephone wiring to the end user.
DSL Technologies Supported
1
The Paradynes Hotwire DSL network supports the following types of technologies:
H Hotwire IDSL (ISDN DSL) products provide IDSL multirate symmetrical
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.
H 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.
H Hotwire SDSL (Symmetric DSL) packet-based products provide high-speed
symmetric DSL services for business applications that require more bandwidth. 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.
March 2000
1-1
Page 12
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 all point-to-point, requiring DSL devices at the central site and at the end-user site.
The Hotwire DSL routers interoperate with the following types of Hotwire DSL cards to deliver applications at high speeds in support of packet services over a DSL link:
H The Hotwire 8323 or 8324 IDSL Cards interoperate with two Hotwire IDSL
Routers:
Hotwire 6321 IDSL Router with one Ethernet portHotwire 6322 IDSL Router with a 4-port Ethernet hub
H The Hotwire 8343 or 8344 Packet SDSL Cards interoperate with two Hotwire
Symmetric DSL Routers:
Hotwire 6341 SDSL Router with one Ethernet portHotwire 6342 SDSL Router with a 4-port Ethernet hub
H The Hotwire 8510, 8373, and 8374 RADSL Cards interoperate with the
Hotwire 6371 RADSL Router
The following illustration shows a typical Hotwire system with a Hotwire DSL Router. The Hotwire 6371 RADSL Router can function simultaneously with data and POTS. The other DSL routers transport data only.
Network Access Provider (NAP) Service Subscriber
Customer Premises (CP)
DSL
Router
POTS
CP
POTS
Splitter
Optional
Network
Service
Provider
Corporate
Intranet
Core
Router
Central Office (CO)
DSL
CARD
DSLAM
POTS
Splitter
Optional
CO
MDF
POTS/DSL
Data
Interface
1-2
Legend: DSL – Digital Subscriber Line POTS–Plain Old Telephone Service
MDF – Main Distribution Frame
March 2000
00-16576-01
Page 13
Hotwire DSL Router Features
The Hotwire DSL routers contain the following features.
H IP routing with:
NAT (Network Address Translation).DHCP Server (Dynamic Host Configuration Protocol) and DHCP Relay
Agent.
A full set of IP filters.
H High-speed Internet or intranet access. H Diagnostics. Provides the capability to diagnose device and network
problems and perform tests.
H Device and Test Monitoring. Provides the capability of tracking and
evaluating the units operation.
H Remote Firmware Download. Provides easy setup and activation of
firmware upgrades from a remote location.
Introduction to Hotwire DSL Routers
H Security. Provides multiple levels of security, which prevents unauthorized
H Console Terminal Interface. Provides an interface for configuring and
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 one or more NSPs (Network Service Provider). Service subscribers may be:
H Residential users connected to public network services (e.g., the Internet) H Work-at-home users connected to their corporate intranet LAN H Commercial users at corporate locations (e.g., branch offices) connected by
The Hotwire DSL Router must be installed at the customer premises to provide the end user with access to any of the above services.
access to the DSL router.
managing the DSL router.
a LAN to 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 Paradynes World Wide Web site at www.paradyne.com/library.
March 2000
1-3
Page 14
Introduction to Hotwire DSL Routers
This page intentionally left blank.
1-4
March 2000
Page 15
Accessing the DSL Router
Access Control to the DSL Router
The Hotwire DSL Router can be managed from the command line interface. There are two methods to access the command line interface:
H Local access at the DSL router through the Console port, or H Access by a Telnet session (controlled through the management interface at
the Hotwire chassis).
When a local console connection is first established, a login prompt appears. The Hotwire DSL Router accepts only one login session at a time. To provide login security to the DSL system, configure a login ID and password.
2
Levels of Access
There are two levels of privileges on the Hotwire DSL system. Your user account can be configured with a user name, password, and privilege of:
H 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, has complete read/write access to the
DSL router.
H 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.
March 2000
2-1
Page 16
Accessing the DSL Router
Changing Access Session Levels
H You can change the Administrator access level by entering:
admin enable
This command provides Administrator access level privileges. The DSL router will respond with a prompt to enter the password for Administrator access.
H You can end the Administrator access level by entering:
admin disable
This command results in ending the Administrator access level session. No password is needed.
Entering exit has the same results. 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 with different passwords for their access level. To determine the level of access for a session, refer to
Determining the Current Access Level on page 2-4.
Local Console Access
The DSL router ships with the local console enabled. After login, the local console can be disabled with the command console disable. After saving this command and ending the session, there is no local access through the console port. All access must be through a Telnet session.
NOTE:
Entering console disable results in NO local access to the DSL router.
To determine if the local console is enabled, log in and enter:
show console
The display returned for the show console command will be:
H console enabled Command line management at the local console is
available, or
H console disabled No command line management is available at the
local console.
For steps to set up the new users login, refer to Setting Up the New Users Login on page 2-3.
2-2
March 2000
Page 17
Setting Up the New User’s Login
The DSL router will provide the login prompt when the local console connection is first established. When the login prompt appears, a locally connected console defaults to Console Enabled with Operator access only.
" Procedure
For first-time access to the Hotwire DSL Routers command line interface:
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 fields are validated together.
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.
Accessing the DSL Router
5. The system identity will change to the Administrator display mode of CUSTOMER#>. Type configure terminal and press Enter.
6. The system identity will change to the Administrator configuration mode of CUSTOMER - CONFIG#>.
7. To change the login ID, enter text to replace the default of paradyne:
name your new login ID
NOTE:
The Login ID and Password fields are NOT case-sensitive.
8. Enter a new password and specify the level:
password level password
Example: type password operator 238clrd3 and press Enter.
Both the Login ID and the Password fields are 1–31 printable alphanumeric ASCII characters in the ASCII hex range of 0x21–0x7E. No spaces are allowed. The following table lists the invalid characters.
Invalid Characters
# Number sign 0x23 $ Dollar sign 0x24
Value ASCII Hex T ranslation
% Percentage 0x25 & Ampersand 0x26
March 2000
2-3
Page 18
Accessing the DSL Router
For more information regarding the system identity, refer to Determining the Current Access Level, below.
If you are denied access during a Telnet session, the session stops and an error is logged. If you accessing the DSL router locally and a Telnet session is active, you will receive a message:
Telnet Access
The 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.
9. At the prompt, enter the new Administrator-level password to replace abc123:
password admin new password and press Enter save and press Enter
NOTE:
Any input during an Administrator configuration session must be saved while still in configuration mode.
Local console disabled by conflict
Determining the Current Access Level
To determine the local console access level, log in to the DSL router. The command line prompt following the login displays the access level. The default System identity is CUSTOMER>.
If the prompt format appears as . . .
CUSTOMER> Operator, display mode Paradyne> CUSTOMER #> Administrator, display
CUSTOMER – CONFIG#> Administrator,
Determining the Available Commands
To determine the commands available at the current login access level, enter:
H help or
Then the DSL router access level is . . .
mode
configuration mode
And if you entered a System identity of Paradyne, the prompt displays . . .
Paradyne #>
Paradyne – CONFIG#>
H ? (question mark)
2-4
March 2000
Page 19
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 at the current login access level, enter the Administrator mode and enter either:
H 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... is displayed. Pressing any key will display the next page.
H list confg
Displays the output in scroll mode as a text file. Scroll mode creates a file and captures all command strings in the text file for use with a terminal emulation program. Refer to Appendix C, DSL Router Terminal Emulation.
Changing the System Identity
Accessing the DSL Router
Procedure
"
To change the System Identity from the factory default of CUSTOMER>:
1. Login and enter the ADMIN-configuration mode.
2. At the CUSTOMER-CONFIG#> prompt, type the new System identity (no spaces allowed), press Enter, type save, and press Enter.
system identity new system identity
For example:
system identity Paradyne and press Enter save and press Enter
3. In this example, after saving the entry and ending the configuration mode, the System identity will display:
Paradyne #>
Exiting from the System
You can manually log out of the system, unplug the Console cable, 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.
March 2000
2-5
Page 20
Accessing the DSL Router
Manually Logging Out
To log out, there are two commands: logout and exit.
" Procedure
To log out of the Hotwire DSL Router command line session or Telnet session:
" Procedure
To exit the Hotwire DSL Routers current access level:
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.
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 you are accessing the DSL router . . .
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
Automatically Logging Out
The DSL router has an automatic timeout feature that logs you out of the system after five minutes of inactivity. Any input that is not saved is lost. You will need to log back in. At the console, press Enter to display the login> prompt to log back in.
Then . . .
You are placed at the Operator level and any configuration updates must be saved or the updates will be lost.
You are placed at the Operator level.
The Exit command responds exactly like the Logout command.
Entering either of the following ends the Telnet session immediately:
H Exit H Ctrl + ] (right bracket)
The autologout {enable | disable} command factory default is enabled. Unsaved configuration input is lost.
H When enabled, the current configuration as displayed with the list command
is retained through a power recycle.
H When disabled, the system inactivity timer is disabled.
2-6
March 2000
Page 21
Configuring the DSL Router
Overview of DSL Router Configuration
The Hotwire DSL Routers support various customer premises distribution networks that contain IP forwarding devices or routers, in addition to locally attached hosts or subnets. The Hotwire DSL Router has an IP Routing Table that 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. The DSL router acts as a router (or gateway) as defined in RFC 791.
3
Interfaces for the DSL Router
The Hotwire DSL Router has two interfaces.
H DSL Interface H Ethernet Interface
DSL Interface
The Hotwire DSL Router interface type is determined by the model number.
H 6321 and 6322 are Hotwire IDSL Routers H 6341 and 6342 are Hotwire SDSL Routers H 6371 is a Hotwire RADSL Router
The DSL interface has a unique MAC address assigned before shipping.
March 2000
3-1
Page 22
Configuring the DSL Router
Ethernet Interface
H The Ethernet interface is a 10/100BaseT interface that automatically
H The DSL router can be configured for either DIX format or IEEE 802.3 format.
H The Hotwire 6322 IDSL and the 6342 SDSL Routers each have a hub
H All DSL routers have an Ethernet interface with a unique MAC address
H The DSL router only accepts frames on the Ethernet interface with its own
negotiates the rate. If all attached Ethernet devices support 100BaseT, the DSL router will default to 100BaseT. Otherwise, the DSL router operates at 10BaseT.
When the DSL router is configured to use IEEE 802.3 format, the DSL router uses SNAP encapsulation as specified in RFC 1042.
configuration with four Ethernet connectors. The hub acts as a bit-level repeater. There is logically one Ethernet communications interface and one single collision domain.
assigned before shipping.
MAC address or a broadcast or multicast MAC address.
Ethernet and DSL Interface Identifiers
The following are the naming conventions used for the Hotwire DSL Router interfaces:
H e0 – Ethernet interface name. H d0 – DSL interface name.
Service Domain IP Address Assignments
H Multiple Service Domains can be defined using network addresses and
subnet masks.
H For both the DSL interface and the Ethernet interface, four Service Domain
IP Addresses and subnet masks can be defined.
3-2
March 2000
Page 23
Numbered DSL 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 upstream next hop router for the DSL router is the core router.
Configuring the DSL Router
Simplified Network Topology
Core
Router
The hosts can be assigned IP addresses on the network attached to the DSL routers Ethernet interface. The upstream next hop router is assigned an address on a different logical network than the hosts.
Actions required to configure the DSL router interfaces in this scenario:
H Assign IP address to Ethernet interface: e0 H Assign IP address to DSL interface: d0 H Assign upstream next hop router
Unnumbered DSL Interface
In this LAN extension application scenario, the hosts connected to a corporate network for virtual office connection or teleworkers want to look like they are on the same network as the core router. The core router will be the next hop router for the hosts.
WAN
DSL
Router
Host
(End Users)
99-16609
Actions required to configure the DSL router interfaces in this scenario:
H Assign IP address to Ethernet interface: e0 H Specify the DSL interface as unnumbered: d0 H Assign upstream next hop router H Enable Proxy ARP for both the e0 and d0 interfaces H Disable scoping at the DSL card
March 2000
3-3
Page 24
Configuring the DSL Router
IP Routing
The DSL router uses destination-based routing for downstream traffic. An IP Routing Table is maintained to specify how to forward IP datagrams downstream. The DSL router is capable of supporting 32 entries in the IP Routing Table. 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 each of the configured Service Domains.
Refer to Chapter 4, DSL Router Configuration Examples, for further details.
Network Considerations
The DSL routers can be configured to function in a variety of network environments. The following sections provide descriptions of some of the DSL router features:
H Address Resolution Protocol (ARP) H Proxy ARP H Network Address Translation (NAT)
Basic NATNetwork Address Port Translation (NAPT)Applications Supported by NAT
H Dynamic Host Configuration Protocol (DHCP) Server H DHCP Relay Agent H IP Filtering
Address Resolution Protocol (ARP)
Address Resolution Protocol, as specified in RFC 826, is supported in the DSL router. The DSL router provides for a total of 256 ARP table entries. The timeout for completed and for uncompleted ARP table entries is configurable.
The Command Line Interface provides the ability to:
H Create up to 64 static ARP table entries to be retained across power cycles. H Display the ARP table. H Delete ARP table entries. H Add and delete dynamic ARP table entries by the DHCP server function.
Refer to Dynamic Host Configuration Protocol (DHCP) Server on page 3-7.
3-4
March 2000
Page 25
Proxy ARP
The DSL router supports Proxy ARP. Proxy ARP responses are based on the IP Routing table contents. The IP Routing table must have an entry for every host that is reachable on the Ethernet interface, including hosts for which the DSL router will not forward packets because of IP filters. If an ARP request is received on one interface for an IP address that is reachable on the other interface, the DSL router will respond with its own MAC address.
The Command Line Interface provides the ability to enable and disable Proxy ARP for each interface.
NOTES:
When Basic NAT is enabled, the DSL (d0) interface must have Proxy
ARP enabled if the d0 interface address is part of the Basic NAT global IP network address.
Proxy ARP and NAPT cannot be enabled at the same time.
Network Address Translation (NAT)
Configuring the DSL Router
Network Address Translation is used when a private network’s internal IP addresses cannot be used outside the private network. The IP addresses may be restricted for privacy reasons or they may not be valid public IP addresses.
The DSL router provides NAT as described in RFC 1631 The IP Network Address Translator (NAT). NAT allows the private (local) hosts to transparently access public (global) external IP addresses.
Two variations of traditional NAT are supported:
H Basic NA T H NAPT (Network Address Port Translation)
NOTE:
Basic NAT and NAPT cannot be enabled at the same time.
March 2000
3-5
Page 26
Configuring the DSL Router
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 selective local hosts from the outside. Basic NAT is often used in a large organization with a large network setup for internal use and the need for occasional external access.
Basic NAT provides a one-to-one mapping by translating a range of assigned public IP addresses to a similar-sized pool of unassigned private addresses (typically from the 10.x.x.x address space). Each local host currently communicating with a external host appears to have an unique IP address.
The public address used by NAT must be a Class C address. This private address space can be structured in any way. More than 254 clients can use Basic NAT but not simultaneously.
Network Address Port Translation (NAPT)
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 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 communicating with each other, the translation is based on the IP address and the IP port numbers used by TCP/IP applications.
Applications Supported by NAT
The DSL routers support the following applications and protocols when the connection or session is initiated from the local hosts on the Ethernet side of the DSL router:
H FTP H HTTP H NetMeeting H PING H RealPlayer H Telnet H TFTP
3-6
March 2000
Page 27
Dynamic Host Configuration Protocol (DHCP) Server
The DSL 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:
H The range of IP addresses to be used by the DHCP server must be
configured. The maximum number of clients is 256.
H When the DHCP IP address range is changed, all binding entries and
dynamic routes for the clients configured with the old address range are removed. When the DHCP Server is enabled, there can be only one service domain (Ethernet interface) configured.
H The IP address for the next hop router that is provided to the hosts in the
DHCP reply must be configured.
H The subnet mask can be configured along with the IP address range. This is
optional.
Configuring the DSL Router
DHCP Relay Agent
H The DHCP server must be enabled. H The DHCP server domain name can be configured. This is optional. H The Domain Name Server (DNS) IP address can be configured. This is
optional.
H The minimum and maximum lease time settings can be configured.
For additional information, refer to Chapter 4, DSL Router Configuration
Examples.
The DSL router provides the capability of serving as a DHCP Relay Agent, as specified in RFC 2131, Dynamic Host Configuration Protocol. The DSL router provides the capability to enable and disable the DHCP Relay Agent and to configure the IP address of the DHCP server to which the DHCP requests are to be forwarded.
The DHCP server assigns an IP address to the end-user system. The Hotwire DSL Router IP Routing tables are automatically updated.
The supported DHCP relay agent in the DSL router should be used when there is a DHCP server upstream in the service domain. DHCP relay agent setup considerations:
H DHCP server IP address must be configured. H DHCP relay must be enabled. H DHCP server function and DHCP relay function cannot be enabled at the
same time.
H NAT and DHCP relay cannot be enabled at the same time.
March 2000
3-7
Page 28
Configuring the DSL Router
IP Filtering
The DSL router can filter out IP packets.
By default, filtering is disabled on the Hotwire DSL Card for the DSL router. If enabled, filtering provides security advantages on LANs by restricting traffic on the network and hosts based on the IP source and/or destination addresses.
IP packets can be filtered based on:
H Destination IP Address H IP Protocol Type H Source and Destination Port Number (if applicable) H Source IP Address H TCP Filter (prevents the receipt of downstream TCP connect requests)
NOTE:
All Hotwire DSL Router filters are configured on the Hotwire DSL Card.
NOTE:
If the Source IP Address filter is enabled on the Hotwire card and an IP address is assigned to the DSL interface, there must also be an entry configured in the Hotwire Client Table for the DSL interfaces IP address.
For more information about IP filtering, see the Hotwire MVL, RADSL, IDSL, and
Packet SDSL Cards, Models 8310/8312, 8510/8373/8374, 8323/8324, and 8343/8344, Users Guide.
3-8
March 2000
Page 29
DSL Router Configuration Examples
Configuration Examples
The Hotwire DSL Router configuration examples include only a few of the possible scenarios. This chapter covers some of the common configurations. The command syntax will vary based on your network setup.
Configuration commands require the access level of Administrator-Config and changes need to be saved while in configuration mode to take effect. Refer to Chapter 2, Accessing the DSL Router.
4
The Hotwire DSL Router configuration examples include:
H Basic Configuration H Basic NA T H NAPT H Unnumbered DSL Interface with Proxy ARP H DHCP Relay with Proxy ARP H DHCP Server with Basic NA T H Downstream Router
Refer to Appendix A, Command Line Interface, for specific commands and syntax.
Refer to Appendix B, Configuration Defaults & Command Line Shortcuts, for specific command default settings and abbreviated command line syntax.
NOTES:
The examples in this chapter are provided to illustrate some of the
features of the Hotwire DSL Routers. Not all possible feature configurations are covered in the examples.
The IP addresses used in the examples are for illustrative purposes only.
These addresses are not intended for use when configuring your local network.
March 2000
4-1
Page 30
DSL Router Configuration Examples
Basic Configuration Example
Core
Router
155.1.4.253
WAN
155.1.4.254
In this basic example:
DSL
d0
DSL
Router
Customer Premises (CP)
Console Port Connection
Ethernet e0
155.1.3.254
Hub
End-user
Systems
155.1.3.1
155.1.3.2
155.1.3.3
155.1.3.4
99-16590
H There are multiple clients with statically assigned public IP addresses
configured on the Ethernet side of the DSL router.
H The IP addresses of the clients are contained within the subnet specified by
the configured Ethernet IP address.
H The next hop router of the clients is the Ethernet (e0) interface of the DSL
router.
H The next hop router for downstream forwarding from the core router is the
DSL (d0) interface of the DSL router. The command line syntax is:
ifn address e0 155.1.3.254 255.255.255.0 ifn address d0 155.1.4.254 255.255.255.0 ip route create upstream e0 155.1.4.253
4-2
March 2000
Page 31
Basic NAT Configuration Example
Core
Router
155.1.3.1
WAN
NAT Mapping Public IP Addresses Private IP Addresses
192.128.1.1 10.1.3.2
DSL
d0
155.1.3.2
DSL
Router
DSL Router Configuration Examples
Customer Premises (CP)
Console Port Connection
Ethernet e0
10.1.3.1
Hub
End-user
Systems
10.1.3.2
10.1.3.3
10.1.3.4
10.1.3.5
99-16611
192.128.1.2 10.1.3.3
192.128.1.3 10.1.3.4
192.128.1.4 10.1.3.5
In this Basic NAT example:
H NAT is used for one-to-one mapping of addresses. H There are four private IP addresses configured on the Ethernet side of the
DSL router with NAT static mappings to four public IP addresses.
H The Ethernet (e0) interface is in the private address space and the DSL
interface is in public address space.
H The next hop router for the clients is the Ethernet IP address of the DSL
router. The command line syntax is:
ifn address e0/1 10.1.3.1 255.255.255.248 ifn address d0 155.1.3.2 255.255.255.0 ip route create upstream e0 155.1.3.1 nat basic address 192.128.1.0 nat basic map 192.128.1.1 10.1.3.2 10.1.3.5 nat basic enable
March 2000
4-3
Page 32
DSL Router Configuration Examples
NAPT Configuration Example
Core
Router
155.1.3.1
WAN
DSL
d0
155.1.3.2
DSL
Router
Customer Premises (CP)
Console Port Connection
Ethernet e0
10.1.3.1
Hub
10.1.3.2
10.1.3.3
10.1.3.4
10.1.3.
End-user
Systems
n
NAPT Mapping Public IP Addresses Private IP Addr esses
155.1.3.2 Port 23 10.1.3.4
155.1.3.2 Port n 10.1.3.2
155.1.3.2 Port n 10.1.3.3
155.1.3.2 Port n 10.1.3.n
In this NAPT example:
00-16611-01
H The DSL router is configured for NAPT using a single public IP address. H When using NAPT, the DSL (d0) interface must be numbered because the
Ethernet interface will be configured within the private address space.
H NAPT static mapping is configured for a server (Telnet port 23) on the
Ethernet interface but publicly available. The command line syntax is:
ifn address e0 10.1.3.1 255.255.255.0 ifn address d0 155.1.3.2 255.255.255.0 ip route create upstream e0 155.1.3.1 nat napt address 155.1.3.2 nat napt map tcp 10.1.3.4 23 nat napt enable
4-4
March 2000
Page 33
DSL Router Configuration Examples
Unnumbered DSL Interface with Proxy ARP Configuration Example
Customer Premises (CP)
Core
Router
155.1.3.253
WAN
DSL
d0
Unnumbered
DSL
Router
Console Port Connection
Ethernet e0
155.1.3.254
Hub
155.1.3.1
155.1.3.2
155.1.3.3
End-user
Systems
99-16612
In this unnumbered DSL Interface with Proxy ARP example:
H The clients are statically configured and use the core router as the next hop
router in order to create the LAN extension configuration.
H The DSL interface is unnumbered in this configuration. H If Basic NAT is enabled, the DSL (d0) interface must have Proxy ARP
enabled if the d0 interface address is part of the Basic NAT global IP network address.
H Proxy ARP and NAPT cannot be enabled at the same time. H The clients, the DSL routers Ethernet interface, and the core router interface
are all on the same logical network. The command line syntax is:
ifn address e0 155.1.3.254 255.255.255.0 ifn address d0 unnumbered ip route create upstream e0 155.1.3.253 proxy arp e0 enable proxy arp d0 enable
March 2000
4-5
Page 34
DSL Router Configuration Examples
DHCP Relay with Proxy ARP Configuration Example
DHCP Server
Router
155.1.3.252
Core
155.1.3.253
WAN
Unnumbered
DSL
d0
DSL
Router
Customer Premises (CP)
Console Port Connection
Ethernet e0
155.1.3.254
Hub
End-user
Systems
155.1.3.1
155.1.3.2
155.1.3.3
99-16612
In this DHCP Relay with Proxy ARP example:
H The clients are using dynamic IP address assignment and use the core router
as the next hop router in order to create the LAN extension configuration.
H The DSL (d0) interface is unnumbered in this configuration. H The clients, the Ethernet (e0) interface, and the core router interface are all
on the same logical network.
H Scoping must be disabled at the DSL card. H The DSL router is configured as a DHCP relay.
The command line syntax is:
ifn address e0 155.1.3.254 255.255.255.0 ifn address d0 unnumbered ip route create upstream e0 155.1.3.253 proxy arp e0 enable proxy arp d0 enable dhcp relay enable dhcp relay address 155.1.3.252
4-6
March 2000
Page 35
DHCP Server with Basic NAT Configuration Example
Customer Premises (CP)
Core
Router
DSL
Router
Console Port Connection
Ethernet e0
10.1.3.10
155.1.3.1
WAN
DSL
d0
155.1.3.2
Public IP Addresses for Basic NAT Private IP Addresses
192.128.1.1 10.1.3.2
DSL Router Configuration Examples
End-user
Systems
10.1.3.2
10.1.3.3
Hub
10.1.3.9
99-16613
192.128.1.2 10.1.3.3
. . . . . .
192.128.1.8 10.1.3.9
In this DHCP Server with Basic NAT example:
H The clients are using dynamic IP address assignment and use the Ethernet
(e0) interface of the DSL router as the next hop router.
H The DSL (d0) interface must be numbered. H The DSL router is configured as the DHCP server giving the private IP
addresses to the clients.
H The Ethernet interface is in private address space. NAT is used for
one-to-one mapping of addresses. The command line syntax is:
ifn address e0 10.1.3.10 255.255.255.240 ifn address d0 155.1.3.2 255.255.255.0 ip route create upstream e0 155.1.3.1 nat basic address 192.128.1.0 nat basic enable dhcp server addresses 10.1.3.2 10.1.3.9 dhcp server router 10.1.3.10 dhcp server enable
March 2000
4-7
Page 36
DSL Router Configuration Examples
Downstream Router Configuration Example
Customer Premises (CP)
End-user
Systems
120.26.7.1
Core
Router
155.1.3.1
WAN
120.26.7.2
DSL
d0
155.1.3.2
DSL
Router
Console Port Connection
Ethernet e0
120.26.7.5
Hub
120.26.7.3
120.26.7.100 Router
Hub
130.26.7.1
130.26.7.2
130.26.7.3
In this downstream router example:
H There are clients statically configured and connected to the DSL router. H There are also clients connected behind a downstream router. H The DSL (d0) interface is numbered.
The command line syntax is:
ifn address e0 120.26.7.5 255.255.255.0 ifn address d0 155.1.3.2 255.255.255.0 ip route create upstream e0 155.1.3.1 ip route create 130.26.7.0 255.255.255.0 120.26.7.100
End-user
Systems
99-16591
4-8
March 2000
Page 37
Monitoring the DSL Router
What to Monitor
This chapter presents information on how to access and monitor the Hotwire DSL Routers status and performance statistics. You can monitor DSL router operations by viewing:
H LEDs on the DSL routers front panel. H DSL Router Interfaces Status, including DSL and Ethernet LED status. H DSL Router Statistics, including DSL Service Domain, DSL Management
Domain, Ethernet, and IP statistics.
5
Detecting Problems
The DSL router can detect and report problem conditions and the user can perform diagnostic tests. The DSL router offers a number of indicators to alert you to possible problems:
H LEDs provide status. Refer to Status LEDs in the Hotwire DSL Router
H Status messages for both the Ethernet and DSL links. Refer to Status of
H Network performance statistics for both the Ethernet and DSL links. Refer to
For additional information regarding diagnostic tests, System Log messages, and troubleshooting, refer to Chapter 6, Diagnostics and Troubleshooting.
Installation Instructions for LED indications and troubleshooting of the hardware installation.
Interfaces on page 5-2.
Interface Statistics on page 5-3.
March 2000
5-1
Page 38
Monitoring the DSL Router
Status of Interfaces
From the Command Line Interface, the current status of the Ethernet (e0) Interface and the DSL (d0) Interface can be obtained with one command:
The information displayed for Ethernet and DSL Interfaces is presented below.
show interface
show interface {e0 | d0}
Use to request status statistics for the named interface, e0 or d0. Minimum access level: Operator
e0 – Ethernet interface d0 – DSL interface e0 status – Fields included in the display of Ethernet status: e0
Ethernet Link – { up | down }
This is the same status as reflected by the Ethernet LED.
MAC address xx:xx:xx:xx:xx:xxproxy ARP e0 { enabled | disabled }ifn e0/1 ip-addr x.x.x.x mask x.x.x.x *ifn e0/2 ip-addr x.x.x.x mask x.x.x.xifn e0/3 ip-addr x.x.x.x mask x.x.x.xifn e0/4 ip-addr x.x.x.x mask x.x.x.x
d0 status Fields included in the display of DSL status: d0
DSL Link { up | down }
This is the same status as reflected by the DSL LED.
MAC address xx:xx:xx:xx:xx:xxproxy ARP d0 { enabled | disabled }ifn d0/1 ip-addr x.x.x.x mask x.x.x.x *ifn d0/2 ip-addr x.x.x.x mask x.x.x.xifn d0/3 ip-addr x.x.x.x mask x.x.x.xifn d0/4 ip-addr x.x.x.x mask x.x.x.x
* The Primary designation of a numbered interface marks that interface as the one
whose IP address will be used as a Router ID. If no interface is defined as Primary , the last numbered interface created will become the Primary IP Address.
5-2
March 2000
Page 39
Interface Statistics
Monitoring the DSL Router
From the Command Line Interface, statistics are available for DSL, Ethernet, and IP processing. Statistics are available for all three selections, e0, d0, and ip, with one command:
show statistics
The format of the statistics information display is presented below.
show statistics [ e0 | d0 | ip ]
Use to request statistics for the named interface, e0 or d0, or IP processing statistics. Minimum access level: Operator
e0 – Ethernet interface statistics d0 – DSL interface statistics ip – IP processing statistics
Information displayed for show statistics e0:
Total Bytes Received nnnn. . . . . . . . . . . . . .
Total Bytes Transmitted nnnn. . . . . . . . . . . .
Total Frames Received nnnn. . . . . . . . . . . .
Total Frames Transmitted nnnn. . . . . . . . . .
Total Frames Discarded: Each Discard Reason will display with # of frames
discarded for each specific Discard Reason. Refer to Table 5-1, Discard Reasons for the Ethernet Interface (e0).
Information displayed for show statistics d0:
H Service Domain Statistics (end-user traffic):
Total Bytes Received nnnn. . . . . . . . . . . . . .
Total Bytes Transmitted nnnn. . . . . . . . . . . .
Total Frames Received nnnn. . . . . . . . . . . .
Total Frames Transmitted nnnn. . . . . . . . . .
H Management Domain Statistics (management traffic):
Total Bytes Received nnnn. . . . . . . . . . . . . .
Total Bytes Transmitted nnnn. . . . . . . . . . . .
Total Frames Received nnnn. . . . . . . . . . . .
Total Frames Transmitted nnnn. . . . . . . . . .
H Total Frames Discarded: This total is for both the Service Domain and the
Management Domain. Each Discard Reason will display with # of frames discarded for each specific Discard Reason.
Refer to Table 5-2, Discard Reasons for the DSL Interface (d0).
Information displayed for show statistics ip:
Total Packets Received nnnn. . . . . . . . . . . .
Total Packets Transmitted nnnn. . . . . . . . . .
Total Packets Discarded: Each Discard Reason will display with # of packets
discarded for each specific Discard Reason. Refer to Table 5-3, Discard Reasons for IP.
March 2000
5-3
Page 40
Monitoring the DSL Router
Clearing Statistics
From the Command Line Interface, the statistics can be cleared.
clear statistics [ e0 | d0 | ip ]
Clears the statistics for the named interface. If no interface is entered, ALL statistics for all interfaces are cleared.
Minimum access level: Administrator
e0 d0 ip
Example: clear statistics e0
List of Discard Reasons
Ethernet interface statisticsDSL interface statistics
IP processing statistics
The Discard Statistics represents the number of frames or packets discarded. The display includes the reason for the discard. The following tables list discard reasons for:
H Ethernet Interface (Table 5-1) H DSL Interface (Table 5-2) H IP (Table 5-3)
Table 5-1. Discard Reasons for the Ethernet Interface (e0) (1 of 2)
Discard Reasons for the Ethernet Interface (e0)
Alignment Error CRC Error Defers on TX Excessive Collisions Excessive Defers on TX FIFO Overflow Error Frame Length Greater than Max Late Collision on TX No Carrier Detect on TX Parity Error Receive Buffer Pool Depletion Receiver Halted
5-4
March 2000
Page 41
Monitoring the DSL Router
Table 5-1. Discard Reasons for the Ethernet Interface (e0) (2 of 2)
Discard Reasons for the Ethernet Interface (e0)
Receiver Missed Frame Signal Quality Error on TX Srv Domain Phy TX Queue Overflows Srv Domain Receive Queue Overflows Srv Domain Wrpr TX Queue Overflows TX Halted TX Parity Error TX Underflow Unsupported Encapsulation Protocol Unsupported SNAP Network Protocol Unsupported TypeII Network Protocol
Table 5-2. Discard Reasons for the DSL Interface (d0) (1 of 2)
Discard Reasons for the DSL Interface (d0)
Alignment Error Mgmt Domain Phy TX Queue Overflows Mgmt Domain Rcv Queue Overflows Mgmt Domain TX Link Queue Overflows Mgmt Domain Wrpr TX Queue Overflows Receive Aborts Receive Buffer Pool Depletion Receive CRC Errors Receive Frame Too Short or Too Long Receive Interrupt Errors Receive Overruns Receive Unknown Errors Service Domain Rcv Queue Overflows Srv Domain Phy TX Queue Overflows Srv Domain TX Link Down Discards
March 2000
5-5
Page 42
Monitoring the DSL Router
Table 5-2. Discard Reasons for the DSL Interface (d0) (2 of 2)
Table 5-3. Discard Reasons for IP
Discard Reasons for the DSL Interface (d0)
Srv Domain Wrpr TX Queue Overflows Unknown Frame Type Errors Unrecognized VNID Unsupported Encapsulation Protocol Unsupported Network Protocol
Discard Reasons for IP
Bad Port to Destination Bad Port to Source DSL Receive Packets Filtered DSL Transmit Packets Filtered Ethernet Receive Packets Filter Ethernet Transmit Packets Filter Fragmentation Failures ICMP Errors IP Processing Disabled No Route to Destination No Route to Source No Upstream Route Other Reassembly Failures Other Receive Errors Other Transmit Errors Packets Pending on ARP Discarded Reassembly Timeout TCP Errors Time to Live Expired Transport Protocol Not Handled UDP Errors
5-6
March 2000
Page 43
Diagnostics and Troubleshooting
Diagnostics and Troubleshooting Overview
There are several features available to assist in evaluating the Hotwire DSL Router. The following sections are covered in this chapter:
H Device Restart H Alarms Inquiry H System Log H PING
6
Device Restart
Alarms Inquiry
H TraceRoute
The DSL router can be restarted locally or remotely. From the Command Line Interface, type Restart and press Enter.
The DSL router reinitializes itself, performing a power-on self-test and resetting the local System Log (SYSLOG).
show alarms
This command allows the operator to display the list of current alarm conditions, if any . Minimum access level: Operator The possible output lines are:
Alarm: Management Address Conflict Alarm: Failed Selftest Alarm: System Error No alarm condition is set
March 2000
6-1
Page 44
Diagnostics and Troubleshooting
System Log
The Hotwire DSL Router has the capability to log significant system events (SYSLOG). The SYSLOG can be maintained locally on the DSL router and can also be sent to a remote SYSLOG server. To activate:
H The DSL router must be configured to enable the output of SYSLOG
messages via the syslog enable command. (The Management Controller Card (MCC) has SYSLOG always enabled.)
H An IP address (loopback or remote) must be supplied. H The SYSLOG can also be captured by a remote SYSLOG server running the
UNIX daemon syslogd or an equivalent program. It is necessary to know the IP address where the syslogd resides and the UDP port number the syslogd is using.
The advantage of using a remote SYSLOG server is that ALL events will be maintained upon restart of the DSL router. The local SYSLOG is cleared upon restart.
Events are classified by severity level and the system administrator can specify the minimum severity to be logged.
show syslog
Displays the current status of system as enabled or disabled. If enabled, the severity level, management IP address, and UDP port will be displayed.
syslog – { enabled | disabled } level – { emer | err | norm | info } management ip-addr – x.x.x.x port – nnn
syslog {enable | disable}
Allows the user to enable or disable SYSLOG output. The SYSLOG IP address must be entered (next command) and saved to complete enabling SYSLOG.
Minimum access level: Administrator/Config
enable – Enables SYSLOG output. disable – Disables SYSLOG output.
{syslog ip ip-addr}
Specifies the IP address for the host to send system log entries to. Minimum access level: Administrator/Config
ip-addr – The IP address for SYSLOG (typically loopback address of 127.0.0.1).
{syslog port} [port-number]
Specifies the UDP port number on the server to which the system events will be sent. Minimum access level: Administrator/Config port-number The UDP port number. Default = 514.
6-2
March 2000
Page 45
Diagnostics and Troubleshooting
gy
unusable
syslog level level
Specifies the minimum severity level to be logged. Refer to Table 6-1, SYSLOG Messages, for a list of messages by severity level.
Minimum access level: Administrator/Config level – The minimum level to be logged. The default is NORM. The choices for severity level (displayed as high severity to low severity) are as follows:
EMER – emergency, the system is unusable ERR – error conditions reported NORM – normal or administrative reporting INFO – informational reporting
Example: To log EMER and ERR severity levels, enter syslog level ERR
show log [number]
Displays the contents of the local system error log. (The 100 most recent SYSLOG entries are kept locally.) The user specifies how many entries they wish to view. Entries are displayed in reverse order from most recent to oldest.
number The number of local entries to be seen. Default = 10. Range = 1100.
NOTE: The SYSLOG retained locally will be reset at the DSL router if the restart
command is issued. External logs are retained after a DSL router restart.
SYSLOG Events
The following are some of the SYSLOG events that will be reported for defined severity levels.
Table 6-1. SYSLOG Messages (1 of 2)
Level
EMER Emergency and
ERR Error conditions
Description Event
the system is unusable
reported
Alarm Cleared Alarm Set System Abort ARP Table size exceeded Executable image in flash invalid Frame received in error
March 2000
6-3
Page 46
Diagnostics and Troubleshooting
g
re orting
Table 6-1. SYSLOG Messages (2 of 2)
Level EventDescription
NORM Normal or
administrative reportin
INFO Informational
reporting
Admin enable Admin enable failure Any configuration change command Configuration changes saved Download completed Download failure Login Login failure Logout Statistics cleared Switch program LMC message received System started ARP table entry created due to packet arrival ARP table entry created for DHCP address assignment ARP table entry deleted due to time out Device information LMC message received Packet filter action Routing table entry created for DHCP address
assignment VNID update LMC message received
SYSLOG Message Display
The SYSLOG message displays the following fields:
H Date H Time H Severity Level H DSLAM Slot #/Port # H System Identifier H SYSLOG Event Description
This is an example of a SYSLOG message:
01/06/00 21:22:38 5 03/01 CUSTOMER Console logout complete
6-4
March 2000
Page 47
PING
Diagnostics and Troubleshooting
The PING program is an IP-based application used to test reachability to a specific IP address by sending an ICMP echo request and waiting for a reply. From the Command Line Interface, PING can test connectivity upstream or downstream.
ping dest-ip [mgt | -x source-ip] [-l bytes] [-w time]
PINGs the specified destination IP address. Once PING starts, the input prompt will not redisplay until either the PING finishes or the PING command is aborted with Ctrl-c.
Minimum access level: Administrator
dest-ip – The destination IP address of the device to PING. source-ip – The source IP address to be used. The default source address is from the
service domain in which the test is being done. The IP address is validated to verify that it is an interface IP address.
mgt Specifies that the IP address is in the management domain (through the MCC). Do not use with –x source-ip selection.
bytes – Bytes of data (l = length). Default = 64 bytes. Range = 015,000. time – Number of seconds to wait before ending PING attempt. Default = 10 seconds.
Range = 0–60. Example: ping 135.300.41.8 mgt –l 144 –w 30
PING Test Results
PING test results display in the following formats.
H PING successful:
Ping reply [x.x.x.x]: bytes of data=nn
H PING timeout:
Ping reply [x.x.x.x]: REQUEST TIMED OUT
H ICMP echo response of an unreachable destination:
Ping reply [x.x.x.x]: DESTINATION UNREACHABLE
March 2000
6-5
Page 48
Diagnostics and Troubleshooting
TraceRoute
The TraceRoute program is an IP diagnostic tool that allows you to learn the path a packet takes from the service domain local host to its remote host.
If you are unable to PING a device in a Hotwire network configuration, you may want to run TraceRoute to identify the link (destinations up to 64 hops) between the DSL router and the device that is not forwarding the PING message.
traceroute dest-ip [
Performs TraceRoute to the specified destination IP address. Once T raceRoute starts, the input prompt will not redisplay until either TraceRoute finishes or the T raceRoute command is aborted with Ctrl-c.
Minimum access level: Administrator
dest-ip – The destination IP address for TraceRoute. source-ip – The source IP address used. The default source address is from the
service domain in which the test is being done. The IP address is validated to verify that it is an interface IP address.
bytes – Bytes of data (l = length). Default = 64 bytes. Range = 0–15,000. time – Decimal number for time in seconds before the TraceRoute is abandoned.
Default = 10 seconds. Range = 0–60. hops Decimal number that specifies the maximum number of hops to be tested.
Default = 8. Range = 0–128. Example: traceroute 135.300.41.8 w 80
TraceRoute Test Results
TraceRoute results display in the following format:
-x source-ip] [-l bytes] [-w time] [-h hops]
Tracing route to [x.x.x.x] over a max of nn hops with nnn byte packet
Hop #
1 <100ms <100ms <100ms x.x.x.x 2 <100ms <100ms <100ms x.x.x.x 3 <200ms <200ms <200ms x.x.x.x 4 <200ms <200ms <200ms x.x.x.x
The Hop # is the Time to Live (TTL) value set in the IP packet header. The Round Trip Time contains the time in 100ms intervals for each attempt to reach the destination with the TTL value.
6-6
Round T rip Time
Try #1 Try #2 Try #3
March 2000
IP Address of Responding System
Page 49
Command Line Interface
Command Line Interface Feature
The Hotwire DSL Router is managed with text commands from the Command Line Interface. The Command Line Interface can be accessed:
H Locally with an ASCII terminal connected to the Console port, or H Remotely via a Telnet session.
The Command Line Interface is ASCII character-based and provides the capability to:
A
Navigation
H Display the syntax of commands. H Change the operational characteristics of the DSL router by setting
configuration values.
H Restore all configuration values to the initial factory defaults. H Display DSL router hardware and identification information. H Display system status, including DSL link status and Ethernet status. H Display a sequence of commands that would have the effect of setting all
configurable parameters to their current value.
Refer to Appendix B, Configuration Defaults & Command Line Shortcuts.
Most terminal emulation programs use the following keys:
H Enter or Return – Accepts the input. H Ctrl-c – Aborts the entry or clears the input line. H Down Arrow – Repeats an entry within the last five entered. H Up Arrow – Repeats the input selected with the down arrow.
March 2000
A-1
Page 50
Command Line Interface
Document Conventions
This syntax is used throughout this manual. The Command Line Interface is not case-sensitive, with the exception of the Login ID and Password fields.
Syntax Translation
[ ] { }
|
Italics
Bold
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.
x.x.x.x 32-bit IP address and mask information where x is an
8-bit weighted decimal notation.
xx:xx:xx:xx:xx:xx MAC address information where x is a hexadecimal
notation.
Command Line Interface Commands
Configuration Control Commands
configure {terminal | factory}
Enables the Administrator configuration mode. Configuration mode will remain in effect until the exit or logout command has been entered. While in configuration mode, the show commands are unavailable.
Minimum access level: Administrator configure terminal Configuration mode is in effect and all changes entered by the
Administrator are made on top of the current running configuration. When finished entering the commands needed to configure the DSL router, the save command must be input to save the configuration changes or the exit command can be used to discard the configuration changes and leave the configuration mode.
configure factory Causes the configuration mode to be entered and the factory default settings are loaded. The save command must be used to save the configuration factory defaults as the active configuration.
CAUTION: All interface IP address assignments, static and dynamic route table
save
Saves configuration changes to the active configuration in NVRAM. No configuration changes will be in effect until the save command is issued. If the save command is entered and there are changes that require a reboot of the DSL router, the Administrator will be prompted that a reset is required for the changes to take effect.
Minimum access level: Administrator/Config
yes – Changes are stored and the DSL router resets automatically. no – DSL router is left in configuration mode.
entries, ARP cache entries, NAT static entries, and DHCP server entries will be purged when the DSL router resets.
A-2
6371-A2-GB20-00March 2000
Page 51
Ethernet Frame Format
frame [format ]
Specifies the Ethernet frame format that is to be used. Minimum access level: Administrator/Config format 802.3 or DIX may be requested. Default = DIX
Interface and Service Domain IP Address
ifn address {e0/[ifn] | d0[/ifn]} [ip-address] [mask] [primary] ifn {d0/[ifn] | e0[/ifn]} primary ifn address d0 unnumbered
Specifies the IP address associated with either the Ethernet interface or the DSL interface. Up to four (4) IP addresses may be assigned on each interface. An interface address and mask cannot be changed while there is a static route (upstream or downstream) that uses it. Interface IP address ranges must not overlap.
Minimum access level: Administrator/Config
e0, e0/1, e0/2, e0/3, e0/4 – Ethernet interface. e0 is the same as e0/1. d0, d0/1, d0/2, d0/3, d0/4 – DSL interface. d0 is the same as d0/1. ip-address – The IP address associated with the specified interface. mask – Mask for the associated subnet. primary – The Primary designation of a numbered interface marks that interface as the
one whose IP address will be used as a Router ID. If no interface is defined as Primary , the last numbered interface created will become the Primary IP Address.
unnumbered Specifies that the DSL interface is to be unnumbered.
NOTES: – For each defined Ethernet interface, a corresponding upstream next hop
router IP address must be configured for routing of packets on that interface. See ip route create upstream command for more details.
– When the e0 is assigned an IP address, this section also defines the
logical network (subnet) containing the locally attached hosts. An IP route table entry will automatically be created to correspond to the subnet defined by the mask.
– When the DSL interface is numbered, multiple logical Ethernet interfaces
can be assigned to the same DSL logical interface by configuring the same upstream next hop router.
– The configured DSL logical interfaces must be either all numbered or a
single unnumbered interface. When NA T is being used, the DSL interface must be numbered. Only one logical interface must be defined for each physical interface, i.e., one IP address to each interface.
– When NAT, DHCP Server, or DHCP Relay is enabled, there can be only
one service domain configured.
Examples: ifn address d0 135.300.41.8
ifn d0 primary
Command Line Interface
March 2000
A-3
Page 52
Command Line Interface
IP Routing Table
delete {e0[/ifn] | d0[/ifn]}
Deletes any of the assignments that are configured for the IP address or interface. Only the specific Ethernet or DSL interface number needs to be specified.
An interface address and mask cannot be deleted while there is a static route (upstream or downstream) that uses it. First, delete the IP route with the ip route delete command (see IP Routing Table).
Minimum access level: Administrator/Config
e0, e0/1, e0/2, e0/3, e0/4 – Ethernet interface. e0 is the same as e0/1. d0, d0/1, d0/2, d0/3, d0/4 – DSL interface. d0 is the same as d0/1. Only d0 or d0/1 are
acceptable inputs for an unnumbered interface. Example: delete e0/4
ip route create dest-ip dest-mask {next-hop-ip | remote} ip route delete dest-ip dest-mask
Configures the downstream static routes. Downstream routes cannot be created unless at least one Ethernet interface has been configured.
create – Create an IP route table entry. delete – Delete an IP route table entry. This will delete an IP route placed in the table by
the DHCP server, the DHCP relay, or manually entered static entries.
NOTE: An interface route is created automatically when an address and mask are
dest-ip IP address of the destination. The destination IP address must be within the address range of a configured Ethernet interface.
dest-mask – IP mask for the destination IP address. next-hop-ip – IP address of the next hop (downstream) router used to reach the
destination. A next hop with an IP address of 0.0.0.0 specifies a directly reachable client. A nonzero next-hop-ip address must be within the address range of an Ethernet interface.
remote Indicates that the device specified by the destination ip and destination mask is logically within a local subnet route but is not on the physical Ethernet and resides upstream from the DSL Router. A remote route cannot be created unless at least one DSL interface has been configured.
Example: Refer to Chapter 4, DSL Router Configuration Examples.
assigned to an Ethernet interface with the ifn address command. The Ethernet interface route can be deleted with the ip route purge or the ip route delete command. Once deleted, the interface route must be entered manually using ip route create or the ifn address command.
A-4
6371-A2-GB20-00March 2000
Page 53
Command Line Interface
ip route create upstream e0[/ifn] next-hop-ip ip route delete upstream e0[/ifn]
Enter or delete upstream IP routing table entries. When the DSL interface is unnumbered, an IP routing table entry will be created automatically with the next hop router as remote.
Minimum access level: Administrator/Config
create – Create an IP route table entry. delete – Delete an IP route table entry. e0, e0/1, e0/2, e0/3, e0/4 – Ethernet interface. e0 is the same as e0/1. Specified logical
Ethernet interface. next-hop-ip IP address of the next hop upstream router used to reach the remote
destination.
NOTE: When the DSL interface is configured for numbered mode, the next hop
Example: Refer to Refer to Chapter 4, DSL Router Configuration Examples.
router IP address must fall into one of the (service domain) IP subnets configured for the DSL interface.
ip route purge
Deletes all static and dynamic IP route table entries, including interface routes.
NOTE: An interface route is created automatically when an address and mask are
Minimum access level: Administrator/Config
assigned to an Ethernet interface with the ifn address command. The Ethernet interface route can be deleted with the ip route purge or the ip route delete command. Once deleted, the interface route must be entered manually using ip route create or the ifn address command.
March 2000
A-5
Page 54
Command Line Interface
ARP Table
arp timeout incomplete time
Specifies the ARP table timeout value in seconds for incomplete ARP table entries. Default = 5 seconds.
Minimum access level: Administrator/Config
arp timeout complete time
Specifies the ARP table timeout value in minutes for complete ARP table entries. Default = 20 minutes.
Minimum access level: Administrator/Config
arp { create | delete } ip-address mac-address
Creates or deletes a single, static ARP table entry . Static ARP entries created with this command are retained across resets/power cycles.
Minimum access level: Administrator/Config
create – Create an ARP table entry. delete – Delete an ARP table entry. ip-address – The IP address of the ARP entry to be created or deleted. mac-address – MAC address (valid for create command).
Examples: arp create 132.53.4.2
arp delete 132.53.4.2
Proxy ARP
arp purge ALL
Deletes ALL static and dynamic ARP table entries. Minimum access level: Administrator/Config
proxy arp { e0 | d0 } [ enable | disable ]
Enables or disables proxy ARP for the specified interface. If enable/disable is not specified in the command, enable is the default.
Minimum access level: Administrator/Config
e0 – The Ethernet interface. d0 – The DSL interface. enable – Enable Proxy ARP. disable – Disable Proxy ARP.
NOTE: Proxy ARP and NAPT cannot be enabled at the same time. When Basic
NAT is enabled, Proxy ARP is allowed on the d0 interface.
Example: proxy arp d0 disable
A-6
6371-A2-GB20-00March 2000
Page 55
NAT
Command Line Interface
nat { basic | napt } address ip-addr
Defines the public IP addresses used in the one-to-one mapping function of Basic NA T or the public IP address of a single host for use in the many to one mapping function of NAPT. NAPT cannot accept incoming requests, unless a static NAT entry has been configured.
Minimum access level: Administrator/Config ip-addr For Basic NAT, ip-addr is the IP address of a Class C network. For NAPT,
ip-addr is any valid public IP address. Example: nat napt address 10.1.3.2
nat napt map {udp | tcp } server-ip port
Specifies global access to a local server, such as a Web server. Port-based static entries can be configured for NAPT. This allows a global host to access a server behind the DSL router without exposing the local servers IP address.
Minimum access level: Administrator/Config
udp, tcp – Specify the protocol to be used. server-ip – Enter the IP address of a local server. Only one server of a particular type
(FTP, Telnet, SMPT, TFTP, gopher, finger, http, etc.) can be supported at one time. port The destination port number for the specified server. Example: nat napt map tcp 192.128.1.1 102
nat timeout time
Specifies the NA T timeout values for mapping set up dynamically. Minimum access level: Administrator/Config time The timeout value in minutes. Default = 60 minutes. Example: nat timeout 90
nat basic map public-ip private-ip nat basic map lower-public-ip lower-private-ip upper-private-ip
Statically maps public to private IP addresses for the one-to-one mapping function of Basic NAT. In the first command, a single address pair is mapped. In the second command, a range of IP addresses will be contiguously mapped starting at the pair defined by the lower-public-ip and lower-private-ip argument.
Minimum access level: Administrator/Config public-ip IP address of the public address space which is to be mapped to the IP
address of a local host. private-ip IP address of a local host which is to be mapped to an IP address in the
public IP address space. lower-public-ip Lowermost IP address of a range of public addresses which are to be
mapped to a range of IP addresses of local hosts. lower-private-ip Lowermost IP address of a range of local host IP addresses which
are to be mapped to a range of IP addresses in the public IP address space. upper-private-ip Uppermost IP address of a range of local IP addresses which are to
be mapped to a range of IP addresses of local hosts. Example: nat basic map 192.128.1.1 10.1.3.2
March 2000
A-7
Page 56
Command Line Interface
nat basic delete private-ip nat basic delete lower-private-ip upper-private-ip
In the first command, the command deletes static mapping entries associated with the one-to-one mapping of Basic NA T. In the second command, a range of IP addresses will be contiguously deleted starting at the pair defined by the lower-private-ip and ending with the upper-private-ip argument.
Minimum access level: Administrator/Config
private-ip – Statically mapped IP address of the local host. lower-private-ip – Lowermost IP address of a range of local host IP addresses which
are to be deleted. upper-private-ip Uppermost IP address of a range of local IP addresses which are to
be deleted. Example: nat basic delete 192.128.1.1
nat napt delete {udp | tcp} port
Deletes static mapping entries which identify a local server. Minimum access level: Administrator/Config
udp, tcp – Specify the protocol used. port – The port number associated with the server-ip.
Example: nat napt delete tcp 102
nat basic enable
Enables the one-to-one mapping function of Basic NA T. Enabling Basic NAT automatically disables NA T NAPT. If Basic NAT is enabled, Proxy ARP must be enabled on the d0 interface when the d0 interface address is part of the Basic NA T global IP network address.
Minimum access level: Administrator/Config
nat napt enable
Enables the many-to-one mapping function of NAPT. Enabling NAT NAPT automatically disables Basic NAT.
Minimum access level: Administrator/ Config
NOTE: Proxy ARP and NAPT cannot be enabled at the same time.
nat disable
Disables the currently enabled NAT, either Basic NAT or NAPT. Minimum access level: Administrator/Config
nat purge
Purges all mapping entries. Minimum access level: Administrator/Config
A-8
6371-A2-GB20-00March 2000
Page 57
DHCP Server
Command Line Interface
The DHCP Server can be enabled and disabled, configured by IP address option. Based on RFC 2131 and RFC 2132, supported options are:
H Domain Name H Domain Name Server H Router
dhcp server {enable
Enables or disables the DHCP server. Minimum access level: Administrator/Config
enable – Enable the DHCP Server. disable – Disable the DHCP Server. Default = disable.
Example: dhcp server enable
| disable}
dhcp server addresses lower-ip-address upper-ip-address
Specifies the range of IP addresses to be used by the DHCP server. When the DHCP address range is changed, all binding entries and dynamic routes are removed.
Minimum access level: Administrator/Config Example: dhcp server address 132.53.4.2 132.53.4.350
dhcp server leasetime min-lease-time max-lease-time
Specifies the lease-time settings used by the DHCP server. Minimum access level: Administrator/Config
min-lease-time – Default = 120 minutes (2 hours) max-lease-time – Default = 4320 minutes (72 hours)
Example: dhcp server leasetime 120 320
dhcp server router ip-address
Specifies the router IP address used by the DHCP server. Minimum access level: Administrator/Config Example: dhcp server router 132.53.4.2
dhcp server name domain name
Specifies the domain name used by the DHCP server. Minimum access level: Administrator/Config Example: dhcp server name Clearwater7
March 2000
A-9
Page 58
Command Line Interface
DHCP Relay Agent
dhcp server nameserver ip-address
Specifies the DNS IP address used by the DHCP server. Minimum access level: Administrator/Config Example: dhcp server nameserver 132.53.4.2
dhcp relay {enable | disable}
Enables or disables the DHCP relay agent. The DHCP relay agent will maintain up to 256 DHCP clients.
Minimum level access: Administrator/Config
enable – Enable the DHCP relay. Default = enable. disable – Disable the DHCP relay.
Example: dhcp relay enable
dhcp relay address ip-address
IP Packet Processing
Use this command to specify the DHCP server to forward DHCP requests to. Minimum level access: Administrator/Config Example: dhcp relay address 132.23.4.2
IP multicast {enable | disable}
Enables or disables the forwarding of IP multicast packets. This setting is retained across power cycles.
Minimum access level: Administrator
enable – Enable forwarding of IP multicast packets. disable – Disable forwarding of IP multicast packets. Default = disable.
IP processing {enable | disable}
Enables or disables the processing of IP packets in the service domain. This setting is retained across power cycles.
Minimum access level: Administrator
enable – Enable processing of IP packets. Default = enable. disable – Disable processing of IP packets.
A-10
6371-A2-GB20-00March 2000
Page 59
Show Command Outputs
show console
Displays: console enabled or console disabled
show system
Sample show system display: Jul 21 09:53:26 1999 System ID: xxxxxxxx Model #: xxxx, Serial #: xxxxxxxxxxxx, HW-Rev: xxx Boot: FW-Version: xxxxxxxx 2nd Stage Boot: FW-Version: xxxxxxxx Image 0: FW-Version: xxxxxxxx, [active] Image 1: FW-Version: xxxxxxxx DSL: FW-Version: xxx Selftest Result: { pass | failed }
Command Line Interface
show config
Sample show config display: syslog – { enabled | disabled } e0 frame – { DIX | 802.3 } proxy ARP e0 – { enabled | disabled } proxy ARP d0 – { enabled | disabled } NAT disabled or NAT enabled – { basic NAT | NAPT } DHCP server – { enabled | disabled } DHCP relay – { enabled | disabled } IP multicast – { enabled | disabled } IP processing – { enabled | disabled }
show ip route [ip-address ]
If an IP address is not provided, the entire table will be displayed with the upstream routes displayed first and the downstream routes next. If the IP address is provided, only the specific entry will be displayed. If the next hop IP address = 0.0.0.0, the host is directly reachable on the Ethernet interface (e0).
Minimum access level: Operator
Sample show ip route display: source ip-addr x.x.x.x x.x.x.x x.x.x.x d0
source subnet-mask nexthop ip-addr interface
dest ip-addr x.x.x.x x.x.x.x x.x.x.x e0
dest subnet-mask nexthop ip-addr interface
March 2000
A-11
Page 60
Command Line Interface
show arp
Sample show arp display: ip-addr
x.x.x.x xx:xx:xx:xx:xx:xx xxxx xxxx
MAC address timeout (minutes) incomplete status (seconds)
NOTES: – The timeout value shown is the actual time left for the specific entry.
– The timeout value shown will be Static for configured static entries.
show arp timeout
ARP timeout for completed ARP table entries = nn minutes ARP timeout for incomplete ARP table entries = nn seconds
show nat basic
Sample show nat basic display: NAT basic – { disabled | enabled } NAT basic – public network address NAT timeout – xx minutes NAT basic mappings:
public ip-addr
x.x.x.x x.x.x.x
private-ip-addr
show NAT napt
Sample show NAT NAPT display: NAT napt – { disabled | enabled } NAT napt – public ip-addr xxx.xxx.xxx.xxx NAT timeout – xx minutes NAT napt mappings –
server ip-addr x.x.x.x xxxx { udp | tcp }
port protocol
A-12
6371-A2-GB20-00March 2000
Page 61
show dhcp server
Displays the DHCP relays current status and configuration. Minimum access level: Administrator
Sample show dhcp server display:
DHCP server – { disabled | enabled } DHCP server – router ip-addr: x.x.x.x DHCP server – name: domain name.com DHCP server – nameserver ip-addr: x.x.x.x DHCP server address range –
lower ip-addr upper ip-addr
DHCP server – leasetime –
minimum minutes xxxx maximum minutes
DHCP server bindings
ip-addr MAC address leasetime (minutes)
x.x.x.x xx:xx:xx:xx:xx:xx nnnn
x.x.x.x x.x.x.x
xxxx
Command Line Interface
show DHCP relay
Displays the DHCP relay agent’s current status and configuration. Minimum level access: Administrator
Sample show dhcp relay display:
DHCP relay – { disabled | enabled } DHCP relay – server ip-addr – x.x.x.x
show interface show statistics
Refer to Chapter 5, Monitoring the DSL Router.
show alarms show syslog show log #
Refer to Chapter 6, Diagnostics and Troubleshooting.
March 2000
A-13
Page 62
Command Line Interface
This page intentionally left blank.
A-14
6371-A2-GB20-00March 2000
Page 63
Configuration Defaults & Command Line Shortcuts
Configuration Default Settings
All configuration options and factory default settings are listed alphabetically in Table B-1, Default Configuration Settings. Refer to Table B-2, Command Line
Shortcuts, for abbreviated command line input.
Table B-1. Default Configuration Settings (1 of 2)
B
Configuration Option
ARP cache entries purged ARP timeout for complete entries 20 minutes ARP timeout for incomplete entries 5 seconds console access locally enabled d0 interface IP address (DSL) purged DHCP relay disabled DHCP relay address assignment purged DHCP server disabled DHCP server address assignment purged DHCP server max-lease-time 4320 minutes DHCP server min-lease-time 120 minutes DHCP server name assignment purged DHCP server nameserver assignment purged DHCP server router assignment purged
Factory Default Setting
Ethernet frame DIX e0 interface IP address (Ethernet) purged
March 2000
B-1
Page 64
Configuration Defaults & Command Line Shortcuts
Table B-1. Default Configuration Settings (2 of 2)
Configuration Option Factory Default Setting
IP multicast disabled IP processing enabled login-ID paradyne NAT disabled NAT basic static IP address mappings purged NAT IP address purged NAT NAPT static port mappings purged NAT timeout 20 minutes password abc123 ping data size 64 bytes ping time-out 10 seconds proxy ARP disabled system identity string customer syslog IP address purged syslog level norm syslog messages purged syslog port 514 syslog status disabled traceroute data size 64 bytes traceroute time-out 10 seconds traceroute max number of hops 8
B-2
6371-A2-GB20-00March 2000
Page 65
Command Line Input Shortcuts
Text in bold is the minimum input for each command line entry.
Table B-2. Command Line Input Shortcuts (1 of 2)
admin {disable | enable} arp create <ipaddr> <macaddr> arp delete <ip–addr> arp timeout complete [<time>] arp timeout incomplete [<time>] arp purge autologout {disable | enable} configure {factory | terminal} console {disable | enable} clear statistics {d0 | e0 | ip} delete {d0[/ifn] | e0[/ifn]} dhcp relay {disable | enable} dhcp relay address <ipaddr> dhcp server {disable | enable} dhcp server address <lowerip> <upperip> <ipmask> dhcp server leasetime <mintime> <maxtime> dhcp server name <name> dhcp server nameserver <ipaddr> dhcp server router <ipaddr> exit frame {dix | 802.3} help ifn address {d0[/ifn] | e0[ifn]} <ipaddr> <ipmask> [primary] ifn address d0 unnumbered ifn {d0[/ifn] | e0[/ifn]} primary ip multicast {disable | enable} ip processing {disable | enable} ip route create <destip> <destmask> <nexthopip> ip route create <destip> <destmask> remote ip route create upstream {e0[/ifn] | d0[/ifn]} <nexthopip> ip route delete <destip> <dest mask> ip route delete upstream e0[/ifn]> ip route purge list [config] logout name <name>
Configuration Defaults & Command Line Shortcuts
March 2000
B-3
Page 66
Configuration Defaults & Command Line Shortcuts
Table B-2. Command Line Input Shortcuts (2 of 2)
nat basic address <ip–addr> nat basic delete <private–ip> nat basic delete <lower–private–ip> <upper–private–ip> nat basic enable nat basic map <public–ip> <private–ip> nat basic map <lower–public–ip> <lower–private–ip> <upper–private–ip> nat disable nat napt address <ip–addr> nat napt delete {udp | tcp} <port> nat napt enable nat napt map {udp | tcp} <server–ip> <port> nat purge nat timeout <time> password {admin | operator} <password> ping <dest–ip> [mgt | –x <source_ip> ] [–l <bytes>] [–w <time>] proxy arp {d0 | e0} {disable | enable} restart save show alarms show arp show arp <ip–addr> show arp timeout show config show console show dhcp {relay | server} show interface {d0 | e0} show ip route show ip route <ip–addr> show log [<number of entries>] show nat {basic | napt} show statistics [d0 | e0 | ip] show syslog show system syslog {disable | enable} syslog ip <ip–addr> syslog level {emer | err | norm | info | debug} syslog port <port> system identity <identity> traceroute <dest–ip> [–x <src–ip>] [–l <bytes>] [–w <time>] [–h <hops>]
B-4
6371-A2-GB20-00March 2000
Page 67
DSL Router Terminal Emulation
DSL Router Terminal Emulation
The Command Line Interface is available at the DSL router when the Console cable is connected to a VT100-compatible terminal or a PC running a terminal emulation program. Verify the terminal settings:
H Data rate set to 19.2 kbps (19200 bps) H Character length set to 8
C
H Parity set to None H Stop bits set to 1 H Flow control set to Off or None
Accessing the List Command Output
Use the list confg command to output command strings needed to restore the current running configuration. Output from the List Confg command can be captured to a text file using most terminal emulation programs. Examples of two VT100-compatible programs are provided.
Once the text file is captured, the DSL router can be placed in configuration mode. The text file can be fed back to configure the DSL router and save the configuration.
March 2000
C-1
Page 68
DSL Router Terminal Emulation
Terminal Emulation Programs
Examples of configuring two different terminal emulation programs:
H HyperTerminal – playback feature is accessed through its T ransfer menu. H Procomm+ – playback feature is accessed through its Online menu.
" Procedure
To configure the HyperTerminal:
1. Select menu option Transfer Send Text File.
2. Select File Properties.
3. In the Properties dialog, select the Settings tab.
4. Set Emulation to VT100.
5. Select the Terminal Setup button and set to 132 column mode.
6. Select OK to exit Terminal Setup.
7. Select the ASCII Setup button.
Set Line delay to 50 ms.Set Character delay to 2 ms.
8. Select OK to exit ASCII Setup.
9. Select OK to exit Properties.
" Procedure
To configure Procomm+:
1. Select menu option Online Send File.
2. In the Send File dialog, set the protocol to ASCII.
3. Select the Setup button.
4. Select the Transfer Protocol button (on the left).
5. Select ASCII in the Current Protocol drop-down box.
Set delay between Character to 2 ms.Set delay between Lines to 2 ms.
6. Check and set Use 13 for Line pace character.
7. Check display text.
8. Save the configuration.
C-2
6371-A2-GB20-00March 2000
Page 69
Index
Symbols
? for user access, commands available, 2-4
Numbers
6321/6322 IDSL Routers, 1-1 6341/6342 Symmetric DSL Routers, 1-1 6371 rate adaptive DSL Router, 1-1
A
access control, 2-1 address resolution protocol, 3-4 Administrator access, 2-2 alarms inquiry , 6-1 ARP, 3-4
enable proxy , A-6 proxy, 3-5 proxy configuration, 4-5 table, A-6
autologout, 2-6
B
basic NAT, 3-6
configuring, 4-3, A-7
C
clear statistics, 5-4 command line interface, A-1
shortcuts, B-3 commands available, for access level, 2-4 configuration
commands, A-2
factory default settings, B-1 configure
DSL router, 4-1
terminal, 2-3 console access, 2-2 core router, 3-3 customer, system identity, 2-3
D
d0
DSL interface, 3-1
DSL interface statistics, 5-2 daemon for SYSLOG, 6-2 data rates for DSL routers, 1-3 delete, ip route, A-4 destination IP address, 3-8, A-4 device
restart, 6-1
troubleshooting, 6-1 DHCP, 3-7 DHCP relay, configuring, 4-6, A-10 DHCP server, configuring, 4-7, A-9 diagnostics, 6-1 disable, console access, 2-2 discard reasons, for interface statistics, 5-4 DNS, 3-7 downstream router, configuring, 4-8 DSL access system, 1-1 DSL interface, 3-1
configuring, 4-5
statistics, 5-3 DSL router
access, 2-1
configuring, 4-1
terminal emulation, C-1 DSL Sourcebook, 1-3 Dynamic Host Configuration Protocol (DHCP), 3-7
E
e0
Ethernet interface, 3-2
Ethernet interface statistics, 5-2 enable
Administrator access, 2-2
console access, 2-2 Ethernet
frame format, A-3
interface, 3-2
statistics, 5-3 events in SYSLOG, 6-3 exiting the system, 2-5
6371-A2-GB20-00 March 2000
IN-1
Page 70
Index
F
factory defaults, A-2, B-1 filtering IP packets, 3-8 frame, Ethernet format, A-3 FTP and NA T, 3-6
G
glossary, vi
H
help, for current access levels, 2-4
I
ICMP, 3-1, 6-5 identifiers, for interfaces, 3-2 IDSL 6321/6322 routers, 1-1 interfaces
for DSL routers, 3-1 identifiers, 3-2 IP addresses, A-3
status, 5-1 IP addresses, 3-2, A-3 IP filtering, 3-8 IP multicast, of IP packets, A-10 IP route purge, A-5 IP routing, 3-4
table, A-4 IP statistics, 5-3
L
leasetime, DHCP server, A-9 LEDs, DSL router status, 5-1 levels
of access to the DSL router, 2-4
of SYSLOG messages, 6-3 list command, 2-5
for command line output, C-1 local console access, 2-2 log system events, 6-2 login ID, 2-3 logout, automatically, 2-6
M
MAC address, in ARP table, A-6 mapping, NAT function, 4-3, A-7 messages, from SYSLOG, 6-3 monitoring, DSL router, 5-1
N
nameserver, DHCP server, A-9 NAPT, 3-6
configuring, 4-4, A-7
NAT, 3-5
applications supported, 3-6 basic, 3-6, 4-3 command line, A-7
configuring with DHCP server, 4-7 navigation, command line interface, A-1 NetMeeting, 3-6 network address port translation (NAPT), 3-6 network address translation (NAT), 3-5 network performance statistics, 5-1 new user setup, 2-3 numbered DSL interface, 3-3
O
Operator access, 2-2 output of show commands, A-1 1
P
Packet SDSL, 6341/6342 DSL routers, 1-1 password, 2-3 performance statistics, 5-1 PING, 6-5 POTS, with 6371 DSL router, 1-1 primary IP address, A-3 printing command line input, C-1 proxy ARP, 3-5
configuring, 4-5, A-6
configuring with DHCP relay , 4-6 purge
ARP, A-6
IP route, A-5
NAT, A-8
IN-2
March 2000
Page 71
Index
R
RADSL 6371 router, 1-1 rate adaptive 6371 DSL router, 1-1 relay agent
configuring, A-10
DHCP, 3-7, 4-6 remote route, A-4 restart device, 6-1 router, configuring downstream, 4-8 router ID, IP address, A-3 routing table, 3-4
S
SDSL 6341/6342 routers, 1-1 server, DHCP, 3-7, 4-7 service domain, IP addresses, 3-2 service subscriber, 1-3 shortcuts for command line, B-3 show
alarms, 6-1
commands, A-1 1
SYSLOG, 6-2 source IP address, 3-8 statistics, 5-1
clearing, 5-4 status, of interfaces, 5-2 Symmetric DSL, 6341/6342 DSL routers, 1-1 syntax, command line interface, A-1 SYSLOG, 6-2 system identity , 2-3, 2-5
T
TCP filter, 3-8 TCP protocol, A-7 Telnet access, 2-1, 2-4 terminal emulation, settings, C-1 timeout, for NA T, A-7 TraceRoute, 6-6 troubleshooting, 6-1
U
UDP protocol, A-7 unnumbered DSL interface, 3-3
configuring, 4-5
IP address, A-3 upstream route, 4-3 user login, 2-3
6371-A2-GB20-00 March 2000
IN-3
Loading...