1. Manuals
  2. Brands
  3. Paradyne Manuals
  4. Network Router
  5. Hotwire 6301
  6. User manual

Paradyne Hotwire 6301 User Manual

Paradyne dsl routers user's guide
Hide thumbs Also See for Hotwire 6301:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Instruction and Installation Manual
Hotwire
®
DSL Routers
User's Guide
Document No. 6371-A2-GB20-20
May 2001

Advertisement

Table of Contents
loading

Related Manuals for Paradyne Hotwire 6301

Summary of Contents for Paradyne Hotwire 6301

  • Page 1 Hotwire ® DSL Routers User’s Guide Document No. 6371-A2-GB20-20 May 2001...
  • Page 2 Paradyne worldwide office locations, use one of the following methods: Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at www.paradyne.com/warranty.) Telephone: Call our automated system to receive current information by fax or to speak with a company representative.

  • Page 3: Table Of Contents

    Contents About This Guide Document Purpose and Intended Audience ....Document Summary ........Product-Related Documents .
  • Page 4 Contents 3 Configuring the DSL Router DSL Router Configuration Overview ......The DSL Router’s Interfaces ....... . Interface Identifiers .
  • Page 5 5 Monitoring the DSL Router Monitoring the Router........LED Status .
  • Page 6 Contents A Command Line Interface Command Line Interface Capability ......Navigating the Router’s CLI......Command Recall .
  • Page 7 Ethernet-Like MIB (RFC 2665) ......Paradyne Enterprise MIBs ........
  • Page 8 Contents May 2001 6371-A2-GB20-20...

  • Page 9: Document Purpose And Intended Audience

    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.

  • Page 10: Document Summary

    Command Line Shortcuts Appendix C, Traps and MIBs Appendix D, DSL Router Terminal Emulation Index A master glossary of terms and acronyms used in Paradyne documents is available on the Web at www.paradyne.com. Select Library Manuals viii Description Provides an overview of the Hotwire DSL Routers.
  • Page 11 6371-A2-GN10 8000-A2-GB22 8000-A2-GB26 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 Hotwire DSL and MVL Systems . 6371-A2-GB20-20 Document Title Hotwire 5030 POTS Splitter Customer Premises...

  • Page 12: Document Conventions

    About This Guide Document Conventions The following conventions are used throughout this document. Convention Italics Bold x.x.x.x xx:xx:xx:xx:xx:xx Translation 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.

  • Page 13: Dsl Technologies Supported

    DSL Technologies Supported Paradyne’s Hotwire DSL network supports the following types of technologies: Hotwire IDSL (ISDN DSL) products provide IDSL multirate symmetric packet transport and can operate over a connection with an ISDN repeater or digital facilities.

  • Page 14: Typical Dsl Router System

    DSL link: Hotwire 8303 or 8304 IDSL Cards interoperate with two Hotwire IDSL Routers: — Hotwire 6301 IDSL Router with one Ethernet port — Hotwire 6302 IDSL Router with a 4-port Ethernet hub Hotwire 8343 or 8344 SDSL Cards interoperate with two Hotwire Symmetric DSL Routers: —...

  • Page 15: Hotwire Dsl Router Features

    Hotwire DSL Router Features The Hotwire DSL routers contain the following features. IP routing with: — NAT (Network Address Translation) — NAPT (Network Address Port Translation), also called PAT (Port Address Translation) — Simultaneous Basic NAT (for several fixed servers) and NAPT (on the rest of the PCs on the LAN) —...

  • Page 16: T Service Subscriber

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

  • Page 17: Levels Of Access

    Accessing the DSL Router Access Control to the DSL Router The Hotwire DSL Router can be managed from an NMS using SNMP or from the Command Line Interface (CLI). There are two methods to access the command line interface: Local access at the DSL router through the Console port, or Access by a Telnet session (controlled through the management interface at the Hotwire chassis).

  • Page 18: Changing Access Session Levels

    2. Accessing the DSL Router Changing Access Session Levels To change the Administrator access level, enter: admin enable This command provides Administrator access privileges. The router responds with a prompt to enter the password for Administrator access. To end the Administrator access level, enter: admin disable This command ends the Administrator session.

  • Page 19: Setting Up The New User's Login

    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.

  • Page 20: Telnet Access

    CUSTOMER. See the examples below. If the prompt format appears as . . . CUSTOMER> CUSTOMER #> CUSTOMER – CONFIG#> PARADYNE – CONFIG#> Determining the Available Commands To determine the commands available at the current login access level, enter any of the following: help...

  • Page 21: Using The List Command

    2. At the CUSTOMER-CONFIG#> prompt, type the new System identity (no spaces allowed) and press Enter. Then type save and press Enter. system identity new system identity For example: system identity PARADYNE save In this example, after saving the entry and ending configuration mode, the System identity will display: PARADYNE#>...

  • Page 22: Manually Logging Out

    2. Accessing the DSL Router Manually Logging Out To log out, there are two commands: logout and exit. Procedure To log out of a CLI or Telnet session: 1. At the > prompt, type logout and press Enter. 2. The system ends the session immediately. Any configuration updates must be saved before exiting or the updates will be lost.

  • Page 23: Dsl Router Configuration Overview

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

  • Page 24: Interface Identifiers

    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.

  • Page 25: Numbered Dsl Or Ethernet Interface

    Numbered DSL or Ethernet Interface In this scenario, the hosts attached to the DSL router’s Ethernet interface are on a different logical network than the core router. The DSL router is the next hop router for the hosts. The DSL router’s upstream next hop router is the core router. Simplified Network Topology Core Router...

  • Page 26: Network Considerations

    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.

  • Page 27: Proxy Arp

    Address Resolution Protocol (ARP) Address Resolution Protocol, as specified in RFC 826, is supported in the router. Up to 265 ARP Table entries are supported, and a timeout period for complete and incomplete ARP Table entries can be configured. ARP requests and responses are not processed on the DSL interface when the interface is configured to support RFC 1483 PDU routing (Standard mode).

  • Page 28: Basic Nat

    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).

  • Page 29: Simultaneous Basic Nat And Napt

    Simultaneous Basic NAT and NAPT Simultaneous Basic NAT and NAPT (or PAT) are supported. In this mode, the servers (private IP addresses) using Basic NAT are configured and the devices (private IP addresses) using NAPT are optionally configured (static mappings). If not configured, the remaining private IP addresses default to NAPT.
  • Page 30 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.

  • Page 31: Dhcp Relay Agent

    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.

  • Page 32: Ip Protocol Type Filtering

    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.

  • Page 33: Ethernet Type Filtering

    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.
  • Page 34 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.
  • Page 35 Figure 3-1, 1483 Routed Network Model (Standard 1483 Routed model (Standard mode) in the network. NSP's Access Device NAP's Core Router NSP's Access Device FUNI = Frame-based User-to-Network Interface Figure 3-1. 6371-A2-GB20-20 POWER ALARMS Major Minor NAP's ATM Network Hotwire GranDSLAM IP/1483/ATM IP/1483/FUNI...
  • Page 36 3. Configuring the DSL Router 3-14 May 2001 6371-A2-GB20-20...

  • Page 37: T Configuration Examples

    DSL Router Configuration Examples 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.

  • Page 38: Basic Bridging Configuration Example

    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. —...

  • Page 39: Basic Routing Configuration Example

    Basic Routing Configuration Example Core Router 155.1.4.1 155.1.4.254 In this basic routing example: There are multiple clients with statically assigned public IP addresses configured on the Ethernet side of the DSL router. The IP addresses of the clients are contained within the subnet specified by the configured Ethernet IP address and subnet mask.

  • Page 40: Basic Nat Configuration Example

    4. DSL Router Configuration Examples Basic NAT Configuration Example Core Router 155.1.3.1 155.1.3.2 NAT Mapping Public IP Addresses 155.1.3.3 155.1.3.4 155.1.3.5 155.1.3.6 In this Basic NAT example: NAT is used for one-to-one mapping of addresses. There are four private IP addresses configured on the Ethernet side of the DSL router, with NAT static mappings to four public IP addresses.
  • Page 41 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: —...

  • Page 42: Napt Configuration Example

    4. DSL Router Configuration Examples NAPT Configuration Example Core Router 155.1.3.1 155.1.3.2 NAPT Mapping Public IP Addresses inbound 155.1.3.2, destination Port 23 inbound 155.1.3.2, destination Port 80 In this NAPT example: The DSL router is configured for NAPT using a single public IP address. When using NAPT, the DSL interface (dsl1) must be numbered because the Ethernet interface will be configured within the private address space.
  • Page 43 NOTES: — The NAPT address does not have to be the same IP address as the DSL interface. — 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.

  • Page 44: Simultaneous Basic Nat And Napt Configuration Example

    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.
  • Page 45 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. — The ip routing enable command is only required when using firmware version 4.2.5 or higher.

  • Page 46: Example

    4. DSL Router Configuration Examples Unnumbered DSL Interface with Proxy ARP Configuration Example Core Router 155.1.3.1 Unnumbered In this unnumbered DSL Interface with Proxy ARP example: The clients are statically configured and use the core router as the next hop router (default gateway) in order to create the LAN extension configuration.

  • Page 47: Dhcp Relay With Proxy Arp Configuration Example

    DHCP Relay with Proxy ARP Configuration Example 155.1.3.253 DHCP Server In this DHCP Relay with Proxy ARP example: The clients are using dynamic IP address assignment and use the core router as the next hop router (default gateway) in order to create the LAN extension configuration.

  • Page 48: Dhcp Server With Basic Nat Configuration Example

    4. DSL Router Configuration Examples DHCP Server with Basic NAT Configuration Example Name Server 132.53.4.2 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). The DSL interface (dsl1) must be numbered.

  • Page 49: Downstream Router Configuration Example

    Downstream Router Configuration Example Core Router Console Port 155.1.3.1 Connection Ethernet dsl1 eth1 155.1.3.2 120.26.7.5 Router In this downstream router example: There are clients statically configured and connected to the DSL router. There are also clients connected behind a downstream router. The DSL interface (dsl1) is numbered.
  • Page 50 4. DSL Router Configuration Examples 4-14 May 2001 6371-A2-GB20-20...

  • Page 51: Monitoring The Router

    Monitoring the DSL Router 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 Status Messages For the Ethernet and DSL interface links. Refer to page 5-3.

  • Page 52: Led Status

    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 the following table, 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.

  • Page 53: Clearing Statistics

    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.

  • Page 54: Reasons For Discarded Data

    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 DSL Interface IP Processing Bridge...
  • Page 55 show statistics dsl1 additional information. Table 5-2. Reason Alignment Error Mgmt (management) Domain Phy (physical) Tx Queue Overflows Mgmt Domain Rcv (received data) Queue Overflows Mgmt Domain Tx Link Down Discards Mgmt Domain Wrpr (wrapper) Tx Queue Overflows Receive Aborts Receive Buffer Pool Depletion Receive CRC (Cyclic Redundancy Check) Errors Receive Frame Too Short or Too Long...
  • Page 56 5. Monitoring the DSL Router show statistics ip additional information. Table 5-3. Reason Bad Port to Destination Bad Port to Source DSL Receive Packets Filtered DSL Transmit Packets Filtered Ethernet Receive Packets Filtered Ethernet Transmit Packets Filtered Fragmentation Failures ICMP (Internet Control Management Protocol) Errors Non-routable Packets No Route to Destination No Route to Source...
  • Page 57 show statistics bridge for additional information. Table 5-4. Reason Broadcast Attempts Dropped Frames Discarded byFilters. Frames Exceeding MTU (Maximum Transmission Unit) Frames Filtered by Database. Frames Used for Learning Only SW CRC (software Cyclic Redundancy Check) Check Fails 6371-A2-GB20-20 on page A-24 in Appendix A, Command Line Interface Reasons for Bridge Discarded Frames May 2001...
  • Page 58 5. Monitoring the DSL Router May 2001 6371-A2-GB20-20...

  • Page 59: T Device Restart

    Diagnostics and Troubleshooting 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 Ping on page 6-5 TraceRoute Device Restart The DSL router can be restarted locally or remotely.

  • Page 60: System Log

    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, preferably in the management domain. To activate: The router must be configured to enable the output of SYSLOG messages via the syslog enable command.
  • Page 61 syslog port [ port-number ] Minimum Access Level: Administrator Command Mode: Config Specifies the User Datagram Protocol (UDP) port number on the server to which the system events will be sent. port-number – The UDP port number. The default is 514. syslog level level Minimum Access Level: Administrator Command Mode: Config...

  • Page 62: Syslog Events

    6. Diagnostics and Troubleshooting SYSLOG Events The following are some SYSLOG events that are reported for defined severity levels. Table 6-1. Level EMER NORM INFO SYSLOG Messages Description Event Emergency and Alarm Cleared the unusable Alarm Set system reporting System Abort Error condition ARP Table size exceeded reporting...

  • Page 63: Syslog Message Display

    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 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.

  • Page 64: Ping Test Results

    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.x ]: DESTINATION UNREACHABLE...
  • Page 65 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.

  • Page 66: Traceroute Test Results

    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 Hop # The Hop # is the Time to Live (TTL) value set in the IP packet header. The Round Trip Time contains the time in 100 ms intervals for each attempt to reach the destination with the TTL value.

  • Page 67: Navigating The Router's Cli

    Command Line Interface 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. The CLI is ASCII character-based and provides the capability to: Display the syntax of commands.

  • Page 68: Command Recall

    A. Command Line Interface Command Recall The router keeps a history of the last several commands entered on the CLI. For example, if you press the Up Arrow key, the most recently entered command appears on the command line, where it can be edited and reentered by pressing Enter.

  • Page 69: Cli Commands

    CLI Commands The following types of commands are included in this section: Configuration Commands RFC 1483 Encapsulation Command Ethernet Frame Format Command Interface and Service Domain IP Address Commands IP Routing Commands ARP Commands Proxy ARP Command NAT Commands DHCP Server Commands DHCP Relay Agent Commands IP Packet Processing Commands Traps Command...

  • Page 70: Configuration Commands

    A. Command Line Interface Configuration Commands To show a configuration, refer to 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.

  • Page 71: Rfc 1483 Encapsulation Command

    RFC 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. The default is LLC. VC – Virtual Circuit-based multiplexing. Ethernet Frame Format Command frame [802.3 | DIX] Minimum Access Level: Administrator...

  • Page 72: Interface And Service Domain Ip Address Commands

    A. Command Line Interface 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.

  • Page 73: Ip Routing Commands

    IP Routing Commands 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.

  • Page 74: Bridge Commands

    A. Command Line Interface ip route purge Minimum Access Level: Administrator Command Mode: Config Deletes all IP route table entries, including interface routes and those automatically added by DHCP Server and DHCP Relay agent. NOTE: An interface route is created automatically when an IP address and subnet mask are assigned to an Ethernet interface with the ifn address command.

  • Page 75: Arp Commands

    ARP Commands arp timeout incomplete [ time ] Minimum Access Level: Administrator Command Mode: Config Specifies the Address Resolution Protocol (ARP) Table timeout value, in seconds, for incomplete ARP table entries. The default is 5 seconds. arp timeout complete [ time ] Minimum Access Level: Administrator Command Mode: Config Specifies the ARP table timeout value in minutes for complete ARP Table entries.

  • Page 76: Proxy Arp Command

    A. Command Line Interface Proxy ARP Command proxy arp { eth1 | dsl1 } [ enable | disable ] Minimum Access Level: Administrator Command Mode: Config Enables or disables Proxy ARP for the specified interface. If enable or disable is not entered, enable is assumed.

  • Page 77: Nat Commands

    NAT Commands 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.
  • Page 78 A. Command Line Interface nat timeout time Minimum Access Level: Administrator Command Mode: Config Specifies the NAT timeout value for mappings set up dynamically. Example: nat timeout 90 time – Specifies the amount of inactive time, in minutes, that can elapse before the network address translator times out.
  • Page 79 A. Command Line Interface nat basic delete private-ip nat basic delete lower-private-ip upper-private-ip Minimum Access Level: Administrator Command Mode: Config In the first command, the command deletes static mapping entry associated with the specified one-to-one mapping of Basic NAT. In the second command, a range of mappings will be contiguously deleted starting at the pair defined by the lower-private-ip and ending with the upper-private-ip argument.

  • Page 80: Dhcp Server Commands

    A. Command Line Interface DHCP Server Commands The Dynamic Host Configuration Protocol (DHCP) Server can be enabled and disabled. Based on RFC 2131 and RFC 2132, supported options are: Domain Name Domain Name Server Router Subnet Mask dhcp server {enable Minimum Access Level: Administrator Command Mode: Config Enables or disables the DHCP server.

  • Page 81: Dhcp Relay Agent Commands

    dhcp server name domain name Minimum Access Level: Administrator Command Mode: Config Specifies the domain name used by the DHCP server. Example: dhcp server name Clearwater7 dhcp server nameserver ip-address Minimum Access Level: Administrator Command Mode: Config Specifies the Domain Name System (DNS) IP address used by the DHCP server. Example: dhcp server nameserver 132.53.4.2 DHCP Relay Agent Commands dhcp relay {enable | disable}...

  • Page 82: Ip Packet Processing Commands

    A. Command Line Interface 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 –...

  • Page 83: Traps Command

    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 –...

  • Page 84: Show Commands

    A. Command Line Interface Show Commands 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.
  • Page 85 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 xx:xx:xx:xx:xx:xx NOTES: – Action can be discard or forward. –...
  • Page 86 A. Command Line Interface show dhcp server Minimum Access Level: Operator Command Mode: Standard Displays the DHCP relay’s current status and configuration. Sample show dhcp server display: DHCP server {enabled | disabled } DHCP server – router ip-addr: x.x.x.x DHCP server – name: domain name.com DHCP server –...
  • Page 87 show ip route [ ip-address ] Minimum Access Level: Operator Command Mode: Standard 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.
  • Page 88 A. Command Line Interface show spanning-tree Minimum Access Level: Operator Command Mode: Standard Displays the spanning-tree topology for the router. Sample show spanning-tree display: Spanning tree protocol – enabled Bridge ID – priority 120, address 00:00:0d:00:00:00 Topology change detected/received – false Timers (seconds): hello 2, max age 20, forward delay 15, topology change 35, hold 1, aging 300 Root ID –...
  • Page 89 show statistics [ eth1 | dsl1 | ip | bridge ] 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. eth1 – Ethernet interface statistics. dsl1 –...
  • Page 90 A. Command Line Interface show statistics [ eth1 | dsl1 | ip | bridge ] (Continued from previous page.) show statistics ip The following statistics are displayed for show statistics ip: ip statistics: Total Packets Received Total Packets Transmitted Total Packets Discarded Zero valued discards are not shown Refer to Table 5-3, Reasons for IP Processing Discarded Packets,...
  • Page 91 A. Command Line Interface show system Minimum Access Level: Operator Command Mode: Standard Sample show system display: March 23009:53:26 2001 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 DSP: FW-Version xxx...
  • Page 92 A. Command Line Interface A-26 May 2001 6371-A2-GB20-20...

  • Page 93: Configuration Default Settings

    Configuration Defaults and Command Line Shortcuts Configuration Default Settings All configuration options and factory default settings are listed alphabetically in Table B-1, Default Configuration Shortcuts, for command line syntax and abbreviated command line input. Table B-1. Configuration Option 1483 encap arp cache entries arp timeout for complete entries arp timeout for incomplete entries...
  • Page 94 (trap) test stop (trap) Default Configuration Settings (2 of 3) Factory Default Setting purged purged purged purged disabled disabled disabled disabled paradyne disabled disabled purged purged disabled purged 20 minutes enabled abc123 64 bytes 10 seconds disabled...

  • Page 95: Command Line Shortcuts

    Table B-1. Configuration Option traceroute data size traceroute time-out traceroute max number of hops warmstart (trap) Command Line Shortcuts Text in bold is the minimum input for each command line entry. Table B-2. Command 1483encap [ llc | vc] admin {enable | disable} arp create ip-addr mac-addr arp delete ip-addr arp timeout complete [ time ]...
  • Page 96 B. Configuration Defaults and Command Line Shortcuts Table B-2. Command dhcp server nameserver ip-addr dhcp server router ip-addr exit frame [dix | 802.3] help ifn address {dsl1[:ifn] | eth1[:ifn]} ip-addr ip-mask [primary] ifn address dsl1 unnumbered ifn {dsl1[:ifn] | eth1[:ifn]} primary ip multicast {enable | disable} ip route create dest-ip dest-mask [ next-hop-ip ] ip route create dest-ip dest-mask remote...
  • Page 97 B. Configuration Defaults and Command Line Shortcuts Table B-2. Command Line Shortcuts (3 of 3) Command nat timeout time packet processing {enable | disable} password {admin | operator} password ping dest-ip [ mgt | -x source-ip ] [-l bytes ] [-w time ] [-i {eth1 | dsl1}] proxy arp {dsl1 | eth1} [ enable | disable] restart save...
  • Page 98 B. Configuration Defaults and Command Line Shortcuts May 2001 6371-A2-GB20-20...

  • Page 99: C Traps And Mibs

    Traps are configured via a Telnet session, terminal session, or via SNMP, and are based on community names. Traps are included in the MIB II, Entity and Hotwire Enterprise MIB definitions. MIBs can be accessed through the Paradyne Web site at www.paradyne.com. Select Technical Support The DSL system can send traps to three IP addressable destinations per community (for a total of 12 destinations).

  • Page 100: Dsl Router Traps

    C. Traps and MIBs DSL Router Traps Table C-1, DSL Router 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 authenticationFailure Minor The authenticationFailure trap...

  • Page 101: Mibs Overview

    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. Select Technical Support Standard MIBs...

  • Page 102: System Group

    Objects. Setting/Contents The object is set to display a string in the following format: PARADYNE Hotwire DSL; Model: xxxx-xx-xxx ; S/W Release: yyy.yy.yy; H/W Release: zzzz- zzz; Serial Number: ssssssssssss ; Boot: B bb.bb.bb ; 2nd Boot: S xx.xx.xx ; DSP: x.xx Model starts with the 4-digit model number: 6301 –...

  • Page 103: Interfaces Group (Rfc 1573

    Table C-2. System Group Objects (2 of 2) Object Description sysServices The DSL router provides (system 7) routing and host application services; i.e., Ping and TraceRoute. Interfaces Group (RFC 1573) The evolution of the Interfaces Group of MIB II (RFC 1573 converted to SNMP v1) consists of an object indicating the number of interfaces supported by the DSL router and an interface table containing an entry for each interface.
  • Page 104 C. Traps and MIBs Table C-3. Interfaces Group Objects (2 of 3) Object Description ifType Identifies the interface type based (ifEntry 3) on the physical/link protocol(s). ifMtu Identifies the largest datagram (ifEntry 4) that can be sent or received on an interface.

  • Page 105: Extension To Interfaces Table (Rfc 1573

    Table C-3. Interfaces Group Objects (3 of 3) Object Description ifInOctets Input Counter objects that collect (ifEntry 10) input statistics on data received by the interface. ifInUcastPkts ifEntry 11) ifInDiscards (ifEntry 13) ifInErrors (ifEntry 14) ifInUnknownProtos (ifEntry 15) ifOutOctets Output Counter objects that (ifEntry 16) collect output statistics on data received by the interface.

  • Page 106: Ip Group (Rfc 1213

    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 Group.

  • Page 107: Ip Cidr Route Group (Rfc 2096

    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 Objects.

  • Page 108: Transmission Group

    C. Traps and MIBs Table C-6. IP CIDR Route Group Objects (2 of 2) Object Description ipCidrRouteInfo This object refers to the particular (ipCidrRouteEntry 9) routing protocol responsible for this route. ipCidrRouteNextHopAS Next hop route. (ipCidrRouteEntry 10) ipCidrRouteMetric1 – For future use. ipCidrRouteMetric5 (ipCidrRouteEntry 11 –...

  • Page 109: Ethernet-Like Mib (Rfc 2665

    (dot3StatsEntry 16) – Always 0 (zero) dot3StatsSymbolErrors (dot3StatsEntry 18) – Always 0 (zero) dot3StatsDuplexStatus (dot3StatsEntry 19) Paradyne Enterprise MIBs The following Paradyne Enterprise MIB Objects are supported: Device Control MIB Device Diagnostics MIB Health and Status MIB Configuration MIB...

  • Page 110: Device Control Mib

    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 devHWControl Reset ( control 1) devControlDownLoadIndex (devControlDownloadEntry 1) devControlDownLoadRelease...

  • Page 111: Device Diagnostics Mib

    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.
  • Page 112 C. Traps and MIBs Table C-8. Application Test Group Objects (2 of 3) Object Description applTestErrorCode Contains additional test details, (testStatusEntry 4) such as error codes. applTestOwner Identifies who started the test. (testStatusEntry 5) applTestRowStatus Use to create a new row or delete (testStatusEntry 6) an existing row.
  • Page 113 Table C-8. Application Test Group Objects (3 of 3) Object Description applTracerouteTestId Unique TraceRoute test ID. (traceroute 1) applTracerouteIpAddress Destination IP address for (traceroute 2) TraceRoute test. applTracerouteSourceIpAddress Identifies the source IP address. (traceroute 3) applTraceroutePacketSize Specifies TraceRoute packet size. (traceroute 4) Range + 28 bytes of header information.

  • Page 114: Health And Status Mib

    C. Traps and MIBs Health and Status MIB Objects supported by the Health and Status MIB, pdn_HealthAndStatus.mib, include the following groups: Device Health and Status Device Selftest Status Device Abort Status Device Failure Status Traps Table C-9. Device Status Group Objects Table Object Description devHealthandStatus...

  • Page 115: Configuration Mib

    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 devConfigAreaCopy Use to configure the current configuration (devConfigArea1) to the factory defaults settings.

  • Page 116: Interface Configuration Mib

    C. Traps and MIBs Interface Configuration MIB The Paradyne proprietary Interface Configuration group, pdn_inet.mib, is supported. Refer to additional details. Table C-11. Interface Configuration Group Objects Table Object Description pdnInetIpAddress Identifies the interface IP address. (pdnInetIpAddressTableEntry 1) pdnInetIpSubnetMask Identifies the interface subnet (pdnInetIpAddressTableEntry 2) mask.

  • Page 117: Dhcp Mib

    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.

  • Page 118: Dsl Endpoint Mib

    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 Endpoint Configuration Group Objects IP Routing Group – This table is an extension of the ipCidrRoute table (see IP CIDR Route Group (RFC 2096) IP Multicast Group IP Processing Group...

  • Page 119: D Dsl Router Terminal Emulation

    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: Data rate is set to 19.2 Kbps (19200 bps).

  • Page 120: Terminal Emulation Programs

    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.

  • Page 121: Index

    Index Symbols ?, for determining commands available, 2-4 Numerics 802.3, Ethernet frame format, A-5 access control, 2-1 Address Resolution Protocol (ARP), 3-5 show timeout, A-18 Administrator access, 2-2 alarm show command, 6-1, A-18 ARP, 3-5 show command, A-18 table, A-9 autologout, 2-6 basic configuring, A-11...
  • Page 122 Index DHCP (Dynamic Host Configuration Protocol) relay network configuration, 4-11 server, 3-8 commands, A-14 network configuration, 4-12 with basic NAT configuration, 4-12 show commands, A-19 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-23 downstream router...
  • Page 123 address assignments for service domain, 3-2 interface and service domain, A-6 syslog, 6-2 filtering, 3-10 options processing, 3-7 processing clearing statistics, A-17 statistics, 5-3, A-24 statistics, reasons for discarded packets, 5-6 route purge all, A-8 routing, 3-4 LAN extension configuration, 4-10 learning the path of packets, 6-7 leasetime DHCP server, A-14...
  • Page 124 Index Ping command, 6-5 message, 6-7 results, 6-6 POTS with 6371 DSL router, 1-1 primary interface status, A-20 IP address, A-6 printing command line input, D-1 processing IP packet, A-16 protocol Address Resolution (ARP), A-9 ARP, A-9 Data Units (PDUs), 3-12, A-5 Dynamic Host Configuration (DHCP), A-14 IP and ICMP, 3-1 PDU, A-5...
  • Page 125 show alarms, 6-1 arp command, 3-5 bridge, A-19 commands, A-18 console, A-19 DHCP relays and servers, A-19 interface, 5-3 NAT basic and NAPT configurations, A-21 spanning-tree topology, A-22 statistics, 5-3 system log and system information, 6-2, A-24 traps, A-25 show commands for interface status, 5-3 statistics, 5-3 Simple Network Management Protocol (SNMP), C-1...
  • Page 126 Index IN-6 May 2001 6371-A2-GB20-20...

This manual is also suitable for:

Hotwire 6351Hotwire 6371Hotwire 6341Hotwire 6342Hotwire 6302

Table of Contents