Hotwire® DSL Routers Models 6301, 6302, 6341, 6342, 6351, and 6371 User’s Guide Document No.
Copyright © 2003 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.
Contents About This Guide 1 Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . vii New Features for this Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 Service Domain IP Address Assignments. . . . . . . . . . . . . . . . . . . . . . 3-2 Numbered DSL or Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . 3-3 Unnumbered DSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 IP Options Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6 LED Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Reasons for Discarded Data . . . . . . . . . . . . . . . . . . . . . .
Contents Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24 B Configuration Defaults and Command Line Shortcuts Configuration Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Command Line Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 C Traps and MIBs SNMP Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Traps Overview . . . . . .
Contents E Firmware Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 Firmware Upgrade Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 Firmware Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents vi November 2003 6300-A2-GB20-10
About This Guide Document Purpose and Intended Audience This guide describes how to configure and operate Hotwire DSL routers. It addresses the following models: Hotwire 6301/6302 IDSL Router Hotwire 6341/6342 Symmetric DSL Router Hotwire 6351 ReachDSL Router Hotwire 6371 RADSL Router This document is intended for administrators and operators who maintain the endpoints at customer premises. A basic understanding of internetworking protocols and their features is assumed.
About This Guide New Features for this Release This version of the Hotwire DSL Routers User’s Guide documents firmware release 4.4, which adds the following new features for the Hotwire 6351 ReachDSL Router: viii IP passthrough. This feature allows the router to pass through or share its public IP address with a single LAN device. The DSL router establishes a PPPoE and PPP session with the Network Access Server (NAS).
About This Guide Document Summary Section Description Chapter 1, Introduction to Hotwire DSL Routers Provides an overview of the Hotwire DSL Routers. Chapter 2, Accessing the DSL Router Describes the Hotwire DSL Routers access control and provides instructions on how to log in and log out of the system. Chapter 3, Configuring the DSL Router Describes the DSL router interfaces, Domain Types, IP Routing, and network considerations.
About This Guide Product-Related Documents Document Number Document Title 5030-A2-GN10 Hotwire 5030 POTS Splitter Customer Premises Installation Instructions 5038-A2-GN10 Hotwire 5038 Distributed POTS Splitter Customer Premises Installation Instructions 6050-A2-GZ40 Hotwire Central Office Universal POTS Splitter, Models 6050 and 7020, Installation Instructions 6301-A2-GN10 Hotwire 6301/6302 IDSL Routers Installation Instructions 6341-A2-GN10 Hotwire 6341/6342 SDSL Routers Installation Instructio
About This Guide Document Conventions The following conventions are used throughout this document. 6300-A2-GB20-10 Convention Translation [] Square brackets represent an optional element. {} Braces represent a required entry. | Vertical bar separates mutually exclusive elements. Italics Entry is a variable to be supplied by the operator. Bold Enter (type) as shown. x.x.x.x 32-bit IP address and mask information where x is an 8-bit weighted decimal notation.
About This Guide xii November 2003 6300-A2-GB20-10
Introduction to Hotwire DSL Routers 1 What is a Hotwire DSL Router? The Hotwire® DSL (Digital Subscriber Line) Router operates as a bridge and IP router connecting a DSL link to an Ethernet network. This system provides high-speed access to the Internet or a corporate network over a traditional twisted-pair copper telephone line to the end user.
1. Introduction to Hotwire DSL Routers Typical DSL Router System DSL is a local loop technology that uses standard twisted-pair copper wire to support high-speed access over a single pair of twisted copper wires. DSL applications are point-to-point, requiring DSL devices at central and end-user sites.
1. Introduction to Hotwire DSL Routers Hotwire DSL Router Features Hotwire DSL routers contain the following features.
1. Introduction to Hotwire DSL Routers Console Terminal Interface. Provides an interface for: — Configuring and managing the DSL router — Local console access Management from an NMS using SNMP. In addition, the following features are provided for the Hotwire 6351 ReachDSL Router: Telnet access to the Command Line Interface (CLI) in the service domain for Network Service Provider (NSP) use. TFTP client support for NSP service domain software downloads.
Accessing the DSL Router 2 Access Control to the DSL Router The Hotwire DSL Router can be managed from an NMS using SNMP or from the Command Line Interface (CLI). There are several methods available for accessing the command line interface: Local access at the DSL router through the Console port. Access by a Telnet session (controlled through the management interface at the Hotwire chassis). For the Hotwire 6351 ReachDSL Router, access by a Telnet session from the service domain.
2. Accessing the DSL Router Local Console Access Your user account can be configured with one user login name and different passwords for accessing a CLI session. The DSL router ships with the local console enabled. After login, the local console can be disabled. To disable with the local console, type: console disable save exit Press Enter after each command that you type. Entering console disable results in NO local access to the DSL router. If you attempt to log in, you will receive an error message.
2. Accessing the DSL Router Setting Up the New User’s Login A login prompt appears when the local console connection is first established. When the login prompt appears, a locally connected console defaults to Console Enabled, with Operator access. Procedure To access the router’s CLI for the first-time: 1. At the initial Login> prompt, type the default login ID paradyne and press Enter. 2. At the Password> prompt (for Operator), type the default password abc123 and press Enter.
2. Accessing the DSL Router 8. At the prompt, enter the new Administrator-level password to replace abc123: password admin new password save NOTE: Any input during an Administrator configuration session must be saved while still in configuration mode. If denied access during a Telnet session, the session stops and an error is logged. If accessing the router locally and a Telnet session is active, you receive a Local console disabled by conflict message.
2. Accessing the DSL Router 3. To create a login ID and password for a specified access level, enter: telnet name create level login ID password Example: Type telnet name create operator 238clrd3 1234 and press Enter. NOTE: Login ID and password are NOT case-sensitive. See Step 7 on page 2-3 for list of invalid characters. 4. Enable Telnet login so that the ReachDSL Router will perform login and password validation for the Telnet session connection.
2. Accessing the DSL Router Using the List Command The list command displays a sequence of commands in the form of ASCII strings that would have the effect of setting all configuration settings to the current values. Secure information such as passwords and login IDs are not displayed. To determine the commands available, enter Administrator configuration mode and type either: list Displays the output in on-screen page mode. In on-screen page mode, the user interface displays 23 lines of information.
2. Accessing the DSL Router Exiting from the System You can manually log out of the system, or let the system automatically log you out. The DSL router will log you out immediately if you disconnect the Console cable. Any unsaved configuration input will be lost. Manually Logging Out To log out, there are two commands: logout and exit. Procedure To log out of a CLI session: 1. At the > prompt, type logout and press Enter. 2. The system ends the session immediately.
2. Accessing the DSL Router Automatically Logging Out The DSL router has an automatic timeout feature that logs you out of the system after five minutes of inactivity. Unsaved configuration input is lost. The default for the autologout command is enable. When autologout is: Enabled, the system inactivity timer is enabled. Disabled, the system inactivity timer is disabled. To log back in, press Enter at the console to display the Login> prompt.
Configuring the DSL Router 3 DSL Router Configuration Overview Hotwire DSL Routers support various customer premises distribution networks that contain IP forwarding devices or routers, as well as locally attached hosts or subnets. The Hotwire DSL Router’s IP Routing Table contains IP address and subnet mask information. The DSL router supports Internet Protocol, as specified in RFC 791, and Internet Control Message Protocol (ICMP), as specified in RFCs 792 and 950.
3. Configuring the DSL Router Ethernet Interface — The Ethernet interface is a 10/100BaseT interface that automatically negotiates the rate to be used, 10 Mb or 100 Mb. If all Ethernet-attached devices are capable of operating at 100 Mb, the router defaults to 100 Mb. Otherwise, it operates at 10 Mb. — The interface can be configured for either DIX or IEEE 802.3 frame format. When configured to use IEEE 802.3 format, SNAP encapsulation is used, as specified in RFC 1042.
3. Configuring the DSL Router Numbered DSL or Ethernet Interface In this scenario, the hosts attached to the DSL router’s Ethernet interface are on a different logical network than the core router. The DSL router is the next hop router for the hosts. The DSL router’s upstream next hop router is the core router.
3. Configuring the DSL Router IP Routing Hotwire DSL Routers use destination-based routing for downstream traffic. An IP Routing Table is maintained to specify how IP datagrams are forwarded downstream. The DSL Router is capable of supporting static routes configured by the user. This table can be viewed by both Operator and Administrator access levels.
3. Configuring the DSL Router Network Considerations The routers can be configured to function in a variety of network environments.
3. Configuring the DSL Router Operating mode (Standard or VNET) can be changed without reconfiguration of the router. Static ARP entries can be configured, regardless of the current operating mode. If static ARP entries are configured, they remain in the database and can be displayed using the show arp CLI command. Using CLI commands, you can: Create up to 64 static ARP Table entries. Display the ARP Table. Delete ARP Table entries.
3. Configuring the DSL Router Network Address Translation (NAT) The DSL router provides NAT, as described in RFC 1631, IP Network Address Translator (NAT). NAT allows hosts in a private (local) network to transparently access the external (public or global) network using either a block of public IP addresses (Basic NAT) or a single IP address (NAPT). Static mapping enables access to selected local hosts from outside using these external IP addresses.
3. Configuring the DSL Router Simultaneous Basic NAT and NAPT Simultaneous Basic NAT and NAPT (or PAT) is supported. In this mode, the servers (private IP addresses) using Basic NAT are configured and the devices (private IP addresses) using NAPT are optionally configured (static mappings). If not configured, the remaining private IP addresses default to NAPT. Enabling Basic NAT does not disable NAPT.
3. Configuring the DSL Router Dynamic Host Configuration Protocol (DHCP) Server The router provides a DHCP Server feature, as specified in RFC 2131, Dynamic Host Configuration Protocol, and RFC 2132, DHCP Option and BOOTP Vendor Extensions. DHCP is the protocol used for automatic IP address assignment. DHCP setup considerations: The range of IP addresses to be used by the DHCP server must be configured. The maximum number of clients is 256.
3. Configuring the DSL Router DHCP Relay Agent The router provides the capability of serving as a DHCP Relay Agent, as specified in RFC 2131, Dynamic Host Configuration Protocol. The 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. When DHCP Relay is enabled, it is possible to limit the number of DHCP clients.
3. Configuring the DSL Router Security The router offers security via the following: Filtering. A filter consists of a set of rules applied to a specific interface to indicate whether a packet received or sent on that interface is forwarded or discarded.
3. Configuring the DSL Router Ethernet Type Filtering Ethernet Type filtering (Ethertype) does not apply when the DSL router is in router-only mode. By default, Ethertype filtering is disabled on the Hotwire DSL card for the DSL router. If enabled, separate Ethertype filters are applied to the Ethernet and/or DSL interface with one filter per interface direction. There is a maximum of 16 rules per list. Each rule access list allows filtering of a single Ethertype or a range of Ethertypes.
3. Configuring the DSL Router Routed vs. Bridged PDUs The router supports both the VNET model and 1483 Routed model (derived from RFC 1483) for the transportation of PDUs (Protocol Data Units) from the DSL router to the router in the core network. When operating in Standard mode, the DSL router in conjunction with the DSL line card with an ATM uplink (for example, Model 8304, 8344, etc.) supports routed PDUs.
3. Configuring the DSL Router Figure 3-1, 1483 Routed Network Model (Standard mode), illustrates the 1483 Routed model (Standard mode) in the network. NSP's Access Device POWER NAP's Core Router A B DSL Router OI IPC NSP's Access Device Client ALARMS Fan Major Minor NAP's ATM Network Hotwire GranDSLAM IP/1483/ATM IP/1483/FUNI Client IP/MAC 00-16802 FUNI = Frame-based User-to-Network Interface Figure 3-1.
3. Configuring the DSL Router When the negotiated IP address is assigned to the . . . Then . . . Ethernet interface of the ReachDSL Router The DSL interface will automatically be configured as unnumbered, and any IP address(es) previously assigned to the Ethernet and DSL interfaces are removed. A route for the subnet defined by the negotiated IP address assigned to the Ethernet interface will automatically be added to the IP routing table.
3. Configuring the DSL Router 3-16 If the DSL interface IP address changes, the Basic NAT static mapping that conflicts with the new DSL IP interface address and all Basic NAT dynamic mappings are removed. If the IP Passthrough feature is used, the DHCP Server feature is automatically enabled and the negotiated IP address is the only IP address served.
DSL Router Configuration Examples 4 Configuration Examples The Hotwire DSL Router configuration examples in this chapter 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. DSL Router Configuration Examples NOTES: — Configuration examples included in this chapter cover some common configurations, providing only a few of the possible scenarios. — IP addresses used in the examples are for illustrative purposes only; they are not intended to be used when configuring your local network. — Adding static routes to the core router is typically necessary when routing is enabled. — Bridging-only mode is the default configuration.
4. DSL Router Configuration Examples Basic Routing Configuration Example Customer Premises (CP) End-user Systems Core Router 155.1.3.2 Console Port Connection 155.1.4.1 WAN DSL dsl1 155.1.4.254 Ethernet DSL Router eth1 155.1.3.254 155.1.3.3 Hub 155.1.3.8 01-16613-02 In this basic routing example: There are multiple clients with statically assigned public IP addresses configured on the Ethernet side of the DSL router.
4. DSL Router Configuration Examples To enable Telnet through the service domain via the DSL router Ethernet (eth1) port, use the following commands: telnet enable telnet login enable telnet name create admin paradyne abc123 Basic NAT Configuration Example Customer Premises (CP) End-user Systems 10.1.3.2 Core Router 155.1.3.1 WAN 10.1.3.3 Console Port Connection DSL Ethernet dsl1 155.1.3.2 eth1 DSL 10.1.3.1 Router 10.1.3.4 Hub 10.1.3.
4. DSL Router Configuration Examples The commands and syntax for this example are: ip routing enable ifn address eth1:1 10.1.3.1 255.255.255.0 ifn address dsl1 155.1.3.2 255.255.255.0 ip route create upstream eth1 155.1.3.1 nat basic address 155.1.3.0 nat basic map 155.1.3.3 10.1.3.2 10.1.3.5 nat basic enable proxy arp dsl1 enable NOTES: — The IP address assigned for the DSL interface and the IP address in NAT static mappings can be in the same subnet, but cannot be the same IP address.
4. DSL Router Configuration Examples NAPT Configuration Example Customer Premises (CP) 10.1.3.2 Web Server 10.1.3.3 Core Router Console Port Connection 155.1.3.1 WAN End-user Systems DSL Ethernet dsl1 155.1.3.2 eth1 10.1.3.1 DSL Router 10.1.3.4 Telnet Server Hub 10.1.3.8 01-16611-03 NAPT Mapping Public IP Addresses Private IP Addresses inbound 155.1.3.2, destination Port 23 10.1.3.4 (Telnet server) inbound 155.1.3.2, destination Port 80 10.1.3.
4. DSL Router Configuration Examples NOTES: — The ip routing enable command is only required when using firmware version 4.2.5 or higher. — FUNI/MPOA (1483 routed) link encapsulation can be used with this configuration and the DSL card Models 8304, 8314, 8344, and 8374. Link encapsulation is configured on the DSL port. This link encapsulation must match the core network encapsulation type. The ip route create upstream command is not necessary when using FUNI/MPOA link encapsulation.
4. DSL Router Configuration Examples Simultaneous Basic NAT and NAPT Configuration Example The DSL router can be configured for Basic NAT and NAPT simultaneously. In the private address space, multiple work stations can use NAPT and the servers can use Basic NAT. This allows a server to support traffic other than TCP/UDP traffic and accommodate multiple inbound traffic types. Using Basic NAT also allows you to have multiple servers of the same type (Web, FTP, Telnet) on the private network.
4. DSL Router Configuration Examples NOTES: — When IP Scoping is enabled, Basic NAT is enabled and the dsl1 interface is NOT part of the Basic NAT global IP network, only the dsl1 interface’s IP address must be entered into the client VNID table. — This configuration is only supported with firmware version 4.2.5 or higher. — FUNI/MPOA (1483 routed) link encapsulation can be used with this configuration and the DSL card Models 8304, 8314, 8344, and 8374. Link encapsulation is configured on the DSL port.
4. DSL Router Configuration Examples Unnumbered DSL Interface with Proxy ARP Configuration Example Customer Premises (CP) Core Router End-user Systems 155.1.3.1 Console Port Connection 155.1.3.2 155.1.3.3 DSL WAN dsl1 Unnumbered Ethernet eth1 DSL 155.1.3.254 Router Hub 155.1.3.
4. DSL Router Configuration Examples DHCP Relay with Proxy ARP Configuration Example Core Router Customer Premises (CP) 155.1.3.1 End-user Systems DHCP 155.1.3.253 Server Console Port Connection 155.1.3.2 155.1.3.3 DSL WAN dsl1 Unnumbered Ethernet eth1 DSL 155.1.3.254 Router Hub 155.1.3.
4. DSL Router Configuration Examples DHCP Server with Basic NAT Configuration Example Customer Premises (CP) DNS Name Server End-user Systems Core Router 132.53.4.2 10.1.3.2 Console Port Connection 155.1.3.1 WAN DSL dsl1 155.1.3.2 Ethernet DSL Router eth1 10.1.3.10 10.1.3.3 Hub 10.1.3.9 01-16952 In this DHCP Server with Basic NAT example: The clients are using dynamic IP address assignment and use the Ethernet interface (eth1) of the DSL router as the next hop router (default gateway).
4. DSL Router Configuration Examples PPPoE Client with NAPT and DHCP Server Configuration Example Customer Premises (CP) DNS Name Server End-user Systems SMS 132.53.4.2 10.1.3.2 Console Port Connection PPPoE WAN DSL Ethernet dsl1 eth1 10.1.3.10 DSL Router 10.1.3.3 Hub 10.1.3.9 02-17133 In this PPPoE client with NAPT and DHCP server example: The clients are using dynamic IP address assignment and use the Ethernet interface (eth1) of the DSL router as the next hop router (default gateway).
4. DSL Router Configuration Examples Downstream Router Configuration Example Customer Premises (CP) End-user Systems 120.26.7.1 Console Port Connection 155.1.3.1 DSL WAN End-user Systems 120.26.7.2 Core Router Ethernet dsl1 155.1.3.2 130.26.7.1 120.26.7.3 130.26.7.2 Hub 120.26.7.100 DSL eth1 Router 120.26.7.5 Router Hub 130.26.7.3 00-16591-01 In this downstream router example: There are clients statically configured and connected to the DSL router.
4. DSL Router Configuration Examples IP Passthrough Configuration Example Customer Premises (CP) NAS Console Port Connection WAN DSL dsl1 197.23.26.51 Ethernet eth1 192.168.158.1 Public FTP Server 192.168.158.10 197.23.26.51 Public Web Server 192.168.158.11 03-17489 In this example, the 6351 router shares its public IP address with another device. NAPT is configured to support public FTP and web servers connected directly to the router’s LAN interface.
4.
Monitoring the DSL Router 5 Monitoring the Router The DSL router detects and reports problem conditions that you can monitor. The following indicators can alert you to possible problems: LEDs On the DSL router’s front panel. Refer to LED Status on page 5-2. Status Messages For the Ethernet and DSL interface links. Refer to Interface Status on page 5-3. Performance Statistics For service and management domains, Ethernet and DSL interface and links, IP processing, and bridge operation.
5. Monitoring the DSL Router LED Status The Hotwire DSL Router’s front panel includes LEDs (light-emitting diodes) that provide status on the router and its interfaces. In Table 5-1, Front Panel LEDs, the Condition in BOLD shows what the LED should display after a successful power-on self-test. For the Hotwire 6351 ReachDSL Router, the DSL LED is replaced by the LINE and TX/RX LEDs.
5. Monitoring the DSL Router Interface Status Current status of the Ethernet (eth1) or DSL (dsl1) interface can be accessed using the show interface CLI command. Information provided about each interface includes the direction of the link, the MAC address, Proxy ARP setting, the numbered interfaces, their IP addresses and subnet masks. See show interface {eth1 | dsl1} on page A-27 in Appendix A, Command Line Interface, for information about the command and what is displayed when the command is entered.
5. Monitoring the DSL Router Reasons for Discarded Data The router may discard frames or packets, shown when the show statistics CLI command is entered. The following tables list the reasons why those frames and packets were discarded: Ethernet Interface (Table 5-2) DSL Interface (Table 5-3) IP Processing (Table 5-4) Bridge (Table 5-5) See show statistics eth1 on page A-30 in Appendix A, Command Line Interface, for additional information. Table 5-2.
5. Monitoring the DSL Router See show statistics dsl1 on page A-31 in Appendix A, Command Line Interface, for additional information. Table 5-3.
5. Monitoring the DSL Router See show statistics ip on page A-31 in Appendix A, Command Line Interface, for additional information. Table 5-4.
5. Monitoring the DSL Router See show statistics bridge on page A-31 in Appendix A, Command Line Interface, for additional information. Table 5-5.
5. Monitoring the DSL Router See show statistics pppoe on page A-32 in Appendix A, Command Line Interface, for additional information. Table 5-7.
Diagnostics and Troubleshooting 6 Diagnostics and Troubleshooting Overview Several features are available to assist you in evaluating the Hotwire DSL Router. The following sections are covered in this chapter: Device Restart Alarms Inquiry System Log on page 6-2 Ping on page 6-5 TraceRoute on page 6-7 Device Restart The DSL router can be restarted locally or remotely. From the CLI, type Restart and press Enter.
6. Diagnostics and Troubleshooting System Log The router can log significant system events (SYSLOG). The SYSLOG can be maintained locally on the router and can also be sent to a remote SYSLOG server. To activate: The router must be configured to enable the output of SYSLOG messages via the syslog enable command. The Management Controller Card (MCC) always has SYSLOG enabled. An IP address (loopback or remote) must be supplied.
6. Diagnostics and Troubleshooting Table 6-1. SYSLOG Commands (2 of 2) syslog ip ip-addr { mgt | srvc } Minimum Access Level: Administrator Command Mode: Config Specifies the IP address of the device to receive system log entries. ip-addr – The IP address for SYSLOG. The loopback address of 127.0.0.1 can be used to have the functionality of the SYSLOG (entries kept locally). mgt – The IP address resides in the management domain. This is the default setting.
6. Diagnostics and Troubleshooting SYSLOG Events The following are some SYSLOG events that are reported for defined severity levels. Table 6-2.
6. Diagnostics and Troubleshooting SYSLOG Message Display The SYSLOG message displays the following fields: Date Time Severity Level DSLAM Slot #/Port # System Identifier SYSLOG Event Description This is an example of a SYSLOG message: 01/06/00 21:22:38 5 03/01 CUSTOMER Console logout complete Ping 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.
6. Diagnostics and Troubleshooting Ping Test Results Ping test results display in the following formats. For a successful Ping: Ping reply from [x.x.x.x]: bytes of data=nn Where nn is the number of bytes of data. For a timeout: Ping reply from [x.x.x.x]: REQUEST TIMED OUT For an ICMP echo response of an unreachable destination: Ping reply from [x.x.x.
6. 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 a TraceRoute to identify the link (destinations up to 64 hops) between the router and the device that is not forwarding the Ping message. Table 6-4.
6. Diagnostics and Troubleshooting TraceRoute Test Results TraceRoute results display in the following format: Tracing route to x.x.x.x over a max. of nn hops, with nnn byte packet Round Trip Time Hop # Try #1 Try #2 Try #3 IP Address of Responding System 1 <100 ms <100 ms <100 ms x.x.x.x 2 <100 ms <100 ms <100 ms x.x.x.x 3 <200 ms <200 ms <200 ms x.x.x.x 4 <200 ms <200 ms <200 ms x.x.x.x The Hop # is the Time to Live (TTL) value set in the IP packet header.
Command Line Interface A Command Line Interface Capability The Hotwire DSL router is managed with text commands from the Command Line Interface (CLI). The CLI can be accessed: Locally with an ASCII terminal connected to the Console port, or Remotely via a Telnet session (through the management interface or from the service domain). The CLI is ASCII character-based and provides the capability to: Display the syntax of commands.
A. Command Line Interface Navigating the Router’s CLI The Hotwire DSL router’s CLI uses the following keys (as do most terminal emulation programs): Enter or Return – Accepts the input. Ctrl-c – Aborts the entry or clears the input line. Down Arrow – Repeats an entry within the last five entries made. Up Arrow – Displays the last entry. Left Arrow – Moves the insertion point one space to the left. Right Arrow – Moves the insertion point one space to the right.
A.
A. Command Line Interface Configuration Commands To show a configuration, refer to show config on page A-25. Table A-1. Configuration Commands configure {terminal | factory} Minimum Access Level: Administrator Command Mode: Config Causes the router to enter configuration mode. Configuration mode remains in effect until the exit or logout command is entered. While in configuration mode, show commands are unavailable.
A. Command Line Interface RFC 1483 Encapsulation Command Table A-2. RFP 1483 Encapsulation Command 1483encap [LLC | VC ] Minimum Access Level: Administrator Command Mode: Config Specifies the method for carrying the routed PDUs (Protocol Data Units). LLC – Logical Link Control encapsulation. This is the default setting. VC – Virtual Circuit-based multiplexing. Ethernet Frame Format Command Table A-3. Ethernet Frame Format Command frame [802.
A. Command Line Interface Interface and Service Domain IP Address Commands Table A-4. Interface and Service Domain IP Address Commands ifn address {eth1[:ifn] | dsl1[:ifn] } ip-address mask [primary] ifn {dsl1[:ifn] | eth1[:ifn] } primary ifn address dsl1 unnumbered delete {dsl1[:ifn] | eth1[:ifn] } Minimum Access Level: Administrator Command Mode: Config Specifies the IP address associated with either the Ethernet or DSL interface. Examples: ifn address dsl1 135.300.41.8 255.255.255.
A. Command Line Interface IP Routing Commands Table A-5. IP Routing Commands (1 of 2) ip route create dest-ip dest-mask {next-hop-ip | remote} ip route delete dest-ip dest-mask Minimum Access Level: Administrator Command Mode: Config Configures the downstream static routes. Downstream routes cannot be created unless at least one Ethernet interface has been configured. To configure upstream routers, refer to the next set of entries. Example: Refer to Chapter 4, DSL Router Configuration Examples.
A. Command Line Interface Table A-5. IP Routing Commands (2 of 2) ip route create upstream eth1[:ifn] next-hop-ip ip route delete upstream eth1[:ifn] Minimum Access Level: Administrator Command Mode: Config Enters or deletes upstream IP routing table entries. When the DSL interface is unnumbered, an IP routing table entry is automatically created, with the next hop router as remote. To configure downstream routers, refer to the previous set of entries.
A. Command Line Interface Table A-6. Bridge Commands (2 of 2) bridge aging-timeout [time] Minimum Access Level: Administrator Command Mode: Config Specifies the amount of time that an unused dynamic entry to the bridge’s filtering database will be maintained before it is automatically deleted. If no time is specified, the timeout value is reset to the default setting. time – Valid range for aging timeout is 10–1000000. The default is 300 seconds.
A. Command Line Interface Table A-7. ARP Commands (2 of 2) arp create ip-address mac-address arp delete ip-address Minimum Access Level: Administrator Command Mode: Config Creates or deletes a single, static Address Resolution Protocol (ARP) Table entry. Static ARP entries created with this command are retained across resets/power cycles. Examples: arp create 132.53.4.2 00:10:4b:97:6c:44 arp delete 132.53.4.2 create – Create an ARP table entry. A maximum of 64 entries can be created.
A. Command Line Interface NAT Commands Table A-9. NAT Commands (1 of 4) nat basic { enable | disable } Minimum Access Level: Administrator Command Mode: Config Enables or disables the one-to-one mapping function of Basic Network Address Translation (NAT). For Basic NAT, Proxy ARP on the dsl1 interface must be enabled when the dsl1 interface address is part of the Basic NAT global IP network address. enable – The one-to-one mapping function of Basic NAT is active.
A. Command Line Interface Table A-9. NAT Commands (2 of 4) nat napt purge Minimum Access Level: Administrator Command Mode: Config Deletes all many-to-one NAPT mapping entries. nat timeout [time] Minimum Access Level: Administrator Command Mode: Config Specifies the NAT timeout value for mappings set up dynamically. If no time is specified, the timeout value is reset to the default setting.
A. Command Line Interface Table A-9. NAT Commands (3 of 4) nat basic map public-ip private-ip nat basic map lower-public-ip lower-private-ip upper-private-ip Minimum Access Level: Administrator Command Mode: Config 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.
A. Command Line Interface Table A-9. NAT Commands (4 of 4) nat disable Minimum Access Level: Administrator Command Mode: Config Disables the currently enabled Basic NAT, NAPT, or both Basic NAT and NAPT. nat purge Minimum Access Level: Administrator Command Mode: Config Purges all mapping entries. DHCP Server Commands The Dynamic Host Configuration Protocol (DHCP) Server can be enabled and disabled.
A. Command Line Interface Table A-10. DHCP Server Commands (2 of 2) dhcp server leasetime min-lease-time max-lease-time Minimum Access Level: Administrator Command Mode: Config Specifies the lease-time settings used by the DHCP server. Example: dhcp server leasetime 120 320 min-lease-time – Specifies the minimum amount of time allowed. The default is 120 minutes (2 hours) max-lease-time – Specifies the maximum amount of time allowed.
A. Command Line Interface DHCP Relay Agent Commands Table A-11. DHCP Relay Agent Commands dhcp relay {enable | disable} Minimum Access Level: Administrator Command Mode: Config Enables or disables the DHCP relay agent. The DHCP relay agent will maintain up to 256 DHCP clients. Example: dhcp relay enable enable – Enables the DHCP relay. disable – Disables the DHCP relay. This is the default setting.
A. Command Line Interface IP Packet Processing Commands Table A-12. IP Packet Processing Commands IP multicast {enable | disable} Minimum Access Level: Administrator Command Mode: Config Enables or disables the forwarding of IP multicast packets. This setting is retained across power cycles. enable – Enable forwarding of IP multicast packets. disable – Disable forwarding of IP multicast packets. This is the default setting.
A. Command Line Interface PPPoE Client Commands PPPoE Client commands are supported only for the Hotwire 6351 ReachDSL Router, and only when the router is configured for IP routing (bridging must be disabled) and is operating in VNET mode. See PPPoE Client Support in Chapter 3, Configuring the DSL Router for more information. Table A-13.
A. Command Line Interface Table A-13. PPPoE Client Commands (2 of 3) ppp ip {eth1 | dsl1 | passthrough} [mask] [no-dns] (Continued from previous page) The passthrough device is selected as the first to broadcast a DHCP DISCOVER. The DHCP Server feature of the DSL Router will be automatically enabled and the negotiated IP address will be configured as the range of IP addresses to be served.
A. Command Line Interface Table A-13. PPPoE Client Commands (3 of 3) ppp username [username] Minimum Access Level: Administrator Command Mode: Config Specifies the CHAP host name or PAP peer ID to use for authentication in the PPP session when PPP authentication is enabled and successfully negotiated. To delete the user name, enter this command without specifying a user name on the command line. NOTE: A change to this option does not take effect until the next PPP link establishment.
A. Command Line Interface Telnet Commands The Telnet commands are only available for the Hotwire 6351 ReachDSL Router. Table A-14. Telnet Commands (1 of 2) telnet {enable | disable} Minimum Access Level: Administrator Command Mode: Config Enables or disables service domain Telnet access. enable – Enable service domain Telnet access to the CLI. disable – Service domain Telnet access to the CLI is not allowed.
A. Command Line Interface Table A-14. Telnet Commands (2 of 2) telnet timeout [time] Minimum Access Level: Administrator Command Mode: Config Determines the duration that a service domain Telnet session can be idle before being disconnected by the ReachDSL Router. NOTE: The autologout command can be used to enable/disable the Telnet timeout feature. time – The timeout value in minutes (1–60). The default is 5. If no time is specified, the timeout value is reset to the default setting.
A. Command Line Interface Traps Command Table A-15. Traps Command trap {enable | disable} name of trap Minimum Access Level: Administrator Command Mode: Config Enables or disables the sending of traps. The default is disable. name of trap: authen fail – An incorrect login was entered at the console. ccn – A configuration change has occurred (configuration change notification). devfail – The router has detected an internal failure. link up – The Ethernet link is up and operational.
A. Command Line Interface Show Commands Table A-17. Show Commands (1 of 10) show alarms Minimum Access Level: Operator Command Mode: Standard Displays a list of the current alarm conditions, if any. Possible alarm conditions include: Alarm: Management Address Conflict Alarm: Failed Selftest Alarm: System Error Alarm: DSL Handshake Failure No alarm condition is set Alarm condition reverts to Normal when the problem has been corrected.
A. Command Line Interface Table A-17. Show Commands (2 of 10) show bridge Minimum Access Level: Operator Command Mode: Standard Displays the bridge configuration and forwarding database. Sample show bridge display: Bridging – disabled Spanning tree – enabled Configured aging timeout: 300 seconds Filtering database entries: MAC addr action interface timeout (sec.) xx:xx:xx:xx:xx:xx xxxxxxx xxxxxx xxxxxxxxxxxx NOTES: – Action can be discard or forward.
A. Command Line Interface Table A-17. Show Commands (3 of 10) show dhcp relay Minimum Access Level: Operator Command Mode: Standard Displays the DHCP relay agent’s current status and configuration. Sample show dhcp relay display: DHCP relay – {enabled | disabled } DHCP relay – server ip-addr: x.x.x.x Maximum number of DHCP relay clients: xxx show dhcp server Minimum Access Level: Operator Command Mode: Standard Displays the DHCP relay’s current status and configuration.
A. Command Line Interface Table A-17. Show Commands (4 of 10) show interface {eth1 | dsl1} Minimum Access Level: Operator Command Mode: Standard Displays interface status for the specified interface, eth1 or dsl1, and whether the interface is available to transport data. eth1 – Ethernet interface status. dsl1 – DSL interface status. Status information displayed for show interface eth1: Ethernet Link: {up | down}, {available | unavailable} (This is the same status as the Ethernet LED.
A. Command Line Interface Table A-17. Show Commands (5 of 10) show log [number ] Minimum Access Level: Operator Command Mode: Standard Displays the contents of the local system error log. (The 100 most recent SYSLOG entries are kept locally.) You specify the number of entries you wish to view. Entries are displayed in reverse order, from the most recent to the oldest. number – Number of local entries to be viewed. The default is 10, with a range of 1–100.
A. Command Line Interface Table A-17. Show Commands (6 of 10) show pppoe Minimum Access Level: Operator Command Mode: Standard Sample show pppoe display: PPPoE {enabled | disabled} PPPoE stage - {initial | discovery | PPP session} PPPoE session ID - {xYYYY | none} Peer IP address - x.x.x.
A. Command Line Interface Table A-17. Show Commands (7 of 10) show statistics [ eth1 | dsl1 | ip | bridge | pppoe | tftp] Minimum Access Level: Operator Command Mode: Standard Displays the specified set of statistics. If no set is specified, ALL statistics for the router are shown except: TFTP statistics. Bridge statistics are only displayed when bridging is enabled. PPPoE statistics are only displayed when the PPPoE client is enabled. eth1 – Ethernet interface statistics.
A. Command Line Interface Table A-17.
A. Command Line Interface Table A-17.
A. Command Line Interface Table A-17.
A.
Configuration Defaults and Command Line Shortcuts B 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 command line syntax and abbreviated command line input. Table B-1. 6300-A2-GB20-10 Default Configuration Settings (1 of 3) Configuration Option Factory Default Setting See . . .
B. Configuration Defaults and Command Line Shortcuts Table B-1. B-2 Default Configuration Settings (2 of 3) Configuration Option Factory Default Setting See . . .
B. Configuration Defaults and Command Line Shortcuts Table B-1. Default Configuration Settings (3 of 3) Configuration Option Factory Default Setting See . . .
B. Configuration Defaults and Command Line Shortcuts Table B-2.
B. Configuration Defaults and Command Line Shortcuts Table B-2.
B. Configuration Defaults and Command Line Shortcuts Table B-2.
Traps and MIBs C SNMP Overview The Simple Network Management Protocol (SNMP) is an application-level protocol used in network management to gather information from network devices. Each DSL router runs an SNMP agent that collects data. The network management station in the NAP domain can exercise all the management functions remotely from the Network Operations Center (NOC). There is no discovery of the DSL router, and it does not appear on the Management Domain map.
C. Traps and MIBs DSL Router Traps Table C-1, DSL Router Traps, lists the traps supported by the DSL router. All traps are defined with a severity of Critical, Major, Minor, Warning, or Normal. By default, all traps are initially disabled. Table C-1. DSL Router Traps Trap Event(Trap #) Severity Description MIB Variable Binding* authenticationFailure Minor The authenticationFailure trap signifies an event where access has been attempted and failed.
C. Traps and MIBs MIBs Overview The Hotwire DSL system supports standard as well as Paradyne Enterprise MIBs. Various configuration, status, and statistical data within the SNMP agent is accessible from the NMS. The content of an SNMP agent’s MIBs is defined by various Internet Request for Comments (RFC) documents. The following sections provide brief descriptions about supported MIBs. Complete, up-to-date details about the content of all DSL MIBs are available on the Paradyne Web site at www.paradyne.com.
C. Traps and MIBs System Group System Group objects are fully supported by the DSL router, as shown in Table C-2, System Group Objects. NOTE: The System Name, System Contact, and System Location objects can be configured via the port card (A-F). Values will display in Monitoring (B-E). However, the DSL router uses and displays the SNMP information set via the System Group. Table C-2.
C. Traps and MIBs Table C-2. System Group Objects (2 of 2) Object Description Setting/Contents sysServices (system 7) The DSL router provides routing and host application services; i.e., Ping and TraceRoute. physical(1) – Layer 1 functionality for DSL and Ethernet interfaces. datalink/subnetwork(2) – Layer 2 functionality for: – DSL interface and – Ethernet interface (LLC) internet(4) – Layer 3 functionality (IP) for all management links.
C. Traps and MIBs Table C-3. Interfaces Group Objects (2 of 3) Object Description Setting/Contents ifType (ifEntry 3) Identifies the interface type based on the physical/link protocol(s). Supported values: ifMtu (ifEntry 4) Identifies the largest datagram that can be sent or received on an interface. ifSpeed (ifEntry 5) Provides the interface’s current bandwidth in bits per second (bps). ifPhysAddress (ifEntry 6) Identifies the physical address for the interface.
C. Traps and MIBs Table C-3. Interfaces Group Objects (3 of 3) Object Description Setting/Contents ifInOctets (ifEntry 10) Input Counter objects that collect input statistics on data received by the interface. Integer. Output Counter objects that collect output statistics on data received by the interface. Integer.
C. Traps and MIBs IP Group (RFC 1213) The Internet Protocol Group objects are supported by the unit for all data paths that are currently configured to carry IP data to/from the unit. All of the objects in the IP Group, except for the IP Address Translation table, are fully supported. Table C-5, IP Group Objects, provides clarification for objects contained in the IP Group. Table C-5.
C. Traps and MIBs IP CIDR Route Group (RFC 2096) This MIB obsoletes and replaces IP Group from MIB II. The IP CIDR Route Group objects are supported for all data paths currently configured to carry IP data to or from the device (i.e., the DSL and Ethernet interfaces). All of the objects in this group are fully supported except as noted in Table C-6, IP CIDR Route Group Objects. The IP Forwarding Group is not supported. Table C-6.
C. Traps and MIBs Table C-6. IP CIDR Route Group Objects (2 of 2) Object Description Setting/Contents ipCidrRouteNextHopAS (ipCidrRouteEntry 10) Next hop route. Always set to a value of 0 (zero). ipCidrRouteMetric1 – ipCidrRouteMetric5 (ipCidrRouteEntry 11 – ipCidrRouteEntry 15) For future use. Only value accepted is –1. ipCidrRouteStatus (ipCidrRouteEntry 16) Used to create or delete rows in a table.
C.
C. Traps and MIBs Device Control MIB Objects supported by the Device Control MIB, pdn-Control.mib, include the Device Control Group (fully supported) and the Device Control Download group. Table C-7. Device Control Table Objects Object Description Setting/Contents devHWControl Reset (control 1) Initiates a hardware power-on reset. Value from this object: devControlDownLoadIndex (devControlDownloadEntry 1) Represents the firmware bank.
C. Traps and MIBs Device Diagnostics MIB Objects supported by the Device Diagnostics MIB, pdn_diag.mib, include the Application Test Input Group (Ping and TraceRoute) and Test Traps, providing an NMS a trigger for a diagnostic test. To start a test from NMS, you must obtain the Test ID by performing a Get. This Test ID is then used as the index when setting the parameters via objects in the Application Test Table. Refer to the applNewTestId object in Table C-8, Application Test Group Objects. Table C-8.
C. Traps and MIBs Table C-8. Application Test Group Objects (2 of 3) Object Description Setting/Contents applTestErrorCode (testStatusEntry 4) Contains additional test details, such as error codes. Test Error codes: none – No errors. timeout icmpError systemError applTestOwner (testStatusEntry 5) Identifies who started the test. 1 – 40 characters. applTestRowStatus (testStatusEntry 6) Use to create a new row or delete an existing row. Set to active(1) to create a new row.
C. Traps and MIBs Table C-8. Application Test Group Objects (3 of 3) Object Description Setting/Contents applTracerouteTestId (traceroute 1) Unique TraceRoute test ID. Contains applNewTestID after Get. applTracerouteIpAddress (traceroute 2) Destination IP address for TraceRoute test. Set destination IP address. applTracerouteSourceIpAddress (traceroute 3) Identifies the source IP address. Set source IP address. applTraceroutePacketSize (traceroute 4) Specifies TraceRoute packet size.
C. Traps and MIBs Health and Status MIB Objects supported by the Health and Status MIB, pdn_HealthAndStatus.mib, include the following groups: Table C-9. Device Health and Status Device Selftest Status Device Abort Status Device Failure Status Traps Device Status Group Objects Table Object Description Setting/Contents devHealthandStatus (devStatus1) This object displays alarm messages if any alarms are generated by the device.
C. Traps and MIBs Configuration MIB The supported groups used with the DSL Configuration MIB, pdn_Config.mib, are: Device Configuration Copy Group Trap Configuration Group Paradyne Device Configuration Time Group Traps Table C-10. Device Configuration Copy Group Objects Table Object Description Setting/Contents devConfigAreaCopy (devConfigArea1) Use to configure the current configuration to the factory defaults settings.
C. Traps and MIBs Interface Configuration MIB The Paradyne proprietary Interface Configuration group, pdn_inet.mib, is supported. Refer to Table C-11, Interface Configuration Group Objects Table, for additional details. Table C-11. Interface Configuration Group Objects Table Object Description Setting/Contents pdnInetIpAddress (pdnInetIpAddressTableEntry 1) Identifies the interface IP address. pdnInetIpSubnetMask (pdnInetIpAddressTableEntry 2) Identifies the interface subnet mask.
C. Traps and MIBs DHCP MIB The supported objects in the DHCP Server/Relay MIB, pdn_dhcp.mib, facilitates the creation and configuration of DHCP server table entries. The following groups are supported: DHCP Server Configuration Group – Fully supported. One object is clarified below: — dhcpServerRouterIpAddr (dhcpserv 7) – Enables you to configure the router IP address used by the DHCP server. This address is provided to clients in the DHCP reply message from the DHCP server.
C. Traps and MIBs DSL Endpoint MIB This DSL Endpoint MIB, pdn_DslEndpoint.mib, facilitates configuration of DSL multirate products and is fully supported. Objects are clarified in Table C-12, DSL Endpoint Configuration Group Objects Table. The groups in this MIB are: IP Routing Group – This table is an extension of the ipCidrRoute table (see IP CIDR Route Group (RFC 2096) on page C-9). IP Multicast Group IP Processing Group Console Group Table C-12.
DSL Router Terminal Emulation D 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: Data rate is set to 19.2 Kbps (19200 bps). Character length is set to 8. Parity is set to None. Stop bits is set to 1. Flow control is set to Off or None.
D. DSL Router Terminal Emulation Terminal Emulation Programs Examples of configuring two different terminal emulation programs: HyperTerminal – playback feature is accessed through its Transfer menu. 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.
Firmware Upgrade E Overview The Hotwire 6351 ReachDSL Router supports a TFTP client for the purpose of firmware upgrades within the service domain. The Network Service Provider (NSP) can initiate upgrades for the ReachDSL Router using CLI commands from the local console or through Telnet access.
E. Firmware Upgrade Firmware Upgrade Procedures The NSP can enter CLI commands from the local console or via Telnet to upgrade Hotwire 6351 ReachDSL firmware and activate an alternate firmware image. Procedure To upgrade firmware for the Hotwire 6351 ReachDSL Router within the service domain: 1. Log in and enter ADMIN-configuration mode. 2. At the CUSTOMER-CONFIG#> prompt, type the interface for the TFTP session, the TFTP server host IP address, and the firmware image file name.
E. Firmware Upgrade NOTE: A checksum of the file is calculated and verified prior to programming the flashbank. However, a checksum of the active flashbank does not occur until a power-on self-test. If the flashbank was not successfully programmed, the verification of the checksum image in flash memory will fail during self-test and the valid image in the alternate bank will be copied to the active bank.
E.
Index Symbols !, CLI display for every 10 packets received from the server during file transfer, E-2 ?, for determining commands available, 2-5 Numerics 802.
Index D data rates for DSL routers, 1-3 default gateway, 4-10–4-11 delete destination IP route, A-7 upstream eth1 IP route, A-8 device restart, 6-1 DHCP (Dynamic Host Configuration Protocol) relay network configuration, 4-11 server, 3-9 commands, A-14 network configuration, 4-12–4-13 with basic NAT configuration, 4-12–4-13 show commands, A-26 diagnostics, 6-1 disable console access, 2-2 discarded data, reasons, 5-4 DIX frame format, 3-2 domain name system (DNS), A-15 statistics, A-31 downstream router conf
Index IP address assignments for service domain, 3-2 interface and service domain, A-6 syslog, 6-3 filtering, 3-11 options processing, 3-8 passthrough, example, 4-15 passthrough, in ppp command, A-18 processing clearing statistics, A-23 statistics, 5-3, A-31 statistics, reasons for discarded packets, 5-6 route purge all, A-8 routing, 3-4 L LAN extension configuration, 4-10 learning the path of packets, 6-7 leasetime DHCP server, A-14 settings, A-15 LED status, 5-2 levels of access to the DSL router, 2-5 o
Index PPP authentication, A-19 IP interface and address assignment, A-18–A-19 reasons for discarded frames, 5-8 statistics, A-32 user name, A-19–A-20 PPPoE Client configuration example, 4-13 client support, 3-14 configuration, A-18–A-19 statistics, 5-7, A-32 primary interface status, A-27 IP address, A-6 printing command line input, D-1 processing IP packets, A-17 protocol Address Resolution (ARP), A-9 ARP, A-9 Data Units (PDUs), 3-13, A-5 Dynamic Host Configuration (DHCP), A-14 IP and ICMP, 3-1 PDU, A-5 s
Index show alarms, 6-1 arp command, 3-6 bridge, A-25 commands, A-24 console, A-25 DHCP relays and servers, A-26 interface, 5-3 NAT basic and NAPT configurations, A-28 PPPoE, A-29 PPPoE configuration, A-29 spanning-tree topology, A-29 statistics, 5-3 system log and system information, 6-2, A-32 traps, A-33 show commands for interface status, 5-3 statistics, 5-3 Simple Network Management Protocol (SNMP), C-1 agent overview, C-1 simultaneous NAT and NAPT, 4-8 SNAP encapsulation, 3-2 spanning-tree show command
Index IN-6 November 2003 6300-A2-GB20-10
