HOTWIRE DSL ROUTERS USER’S GUIDE Document No.
Copyright E 2000 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
Contents About This Guide H Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . v H Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii H Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3 Configuring the DSL Router H Overview of DSL Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 H Interfaces for the DSL Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Ethernet and DSL Interface Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Service Domain IP Address Assignments . . . . . . . . . . . . . . . . . . . . . . . 3-2 Numbered DSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5 Monitoring the DSL Router H What to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 H Detecting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 H Status of Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 H Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents B Configuration Defaults & Command Line Shortcuts H Configuration Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 H Command Line Input Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 C Traps & MIBs H SNMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 H Traps Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Guide Document Purpose and Intended Audience This guide describes how to configure and operate Hotwire DSL routers. This document addresses the use of the following Hotwire DSL Router models: H Hotwire 6301/6302 IDSL Router H Hotwire 6341/6342 Symmetric DSL Router H Hotwire 6371 RADSL Router This document is intended for administrators and operators who maintain the endpoints at customer premises. A basic understanding of internetworking protocols and their features is assumed.
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. Chapter 4 DSL Router Configuration Examples.
About This Guide Product-Related Documents Contact your sales or service representative to order additional product documentation.
About This Guide Document Conventions The following syntax is used throughout this document. viii Syntax 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.
Introduction to Hotwire DSL Routers 1 What is a Hotwire DSL Router? The Hotwirer DSL (Digital Subscriber Line) Router operates as an IP router connecting a DSL link to an Ethernet network. This system provides high-speed access to the Internet or a corporate network over a traditional twisted-pair copper telephone line to the end user.
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 the central site and at the end-user site.
Introduction to Hotwire DSL Routers Hotwire DSL Router Features The Hotwire DSL routers contain the following features. H IP routing with: — NAT (Network Address Translation) — NAPT (Network Address Port Translation) — DHCP Server (Dynamic Host Configuration Protocol) and DHCP Relay Agent — A full set of IP filters — SNMP Set/Get capability H High-speed Internet or intranet access. H Diagnostics. Provides the capability to diagnose device and network problems and perform tests.
Introduction to Hotwire DSL Routers Service Subscriber The Service Subscriber is the user (or set of users) that has contracted to receive networking services (e.g., Internet access, remote LAN access) for the end-user system from an NSP (Network Service Provider). Service subscribers may be: H Residential users connected to public network services (e.g., the Internet) H Work-at-home users connected to their corporate intranet LAN H Commercial users at corporate locations (e.g.
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. There are two methods to access the command line interface: H Local access at the DSL router through the Console port, or H Access by a Telnet session (controlled through the management interface at the Hotwire chassis). When a local console connection is first established, a login prompt appears.
Accessing the DSL Router Changing Access Session Levels H You can change the Administrator access level by entering: admin enable This command provides Administrator access level privileges. The DSL router will respond with a prompt to enter the password for Administrator access. H You can end the Administrator access level by entering: admin disable This command results in ending the Administrator access level session. No password is needed. Entering exit has the same results.
Accessing the DSL Router Setting Up the New User’s Login The DSL router will provide the login prompt when the local console connection is first established. When the login prompt appears, a locally connected console defaults to Console Enabled with Operator access only. " Procedure For first-time access to the Hotwire DSL Router’s command line interface: 1. At the initial login> prompt, type the default login ID paradyne and press Enter. 2.
Accessing the DSL Router 9. At the prompt, enter the new Administrator-level password to replace abc123: password admin new password and press Enter save and press Enter NOTE: Any input during an Administrator configuration session must be saved while still in configuration mode. For more information regarding the system identity, refer to Determining the Current Access Level, below. If you are denied access during a Telnet session, the session stops and an error is logged.
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. (The two passwords are not output.) To determine the commands available, enter the Administrator configuration mode and enter either: H list Displays the output in on-screen page mode. In on-screen page mode, the user interface displays 23 lines of information.
Accessing the DSL Router Manually Logging Out To log out, there are two commands: logout and exit. " Procedure To log out of the Hotwire DSL Router command line session or Telnet session: 1. At the > prompt, type logout and press Enter. 2. The system ends the session immediately. Any configuration updates must be saved before exiting or the updates will be lost. " Procedure To exit the Hotwire DSL Router’s current access level: 1. At the > prompt, type exit and press Enter.
Configuring the DSL Router 3 Overview of DSL Router Configuration The Hotwire DSL Routers support various customer premises distribution networks that contain IP forwarding devices or routers, in addition to locally attached hosts or subnets. The Hotwire DSL Router has an IP Routing Table that contains IP address and subnet mask information. The DSL router supports Internet Protocol as specified in RFC 791 and Internet Control Message Protocol (ICMP) as specified in RFCs 792 and 950.
Configuring the DSL Router H Ethernet Interface — All DSL routers have an Ethernet interface with a unique MAC address assigned before shipping. — The Ethernet interface is a 10/100BaseT interface that automatically negotiates the rate. If all attached Ethernet devices support 100BaseT, the DSL router will default to 100BaseT. Otherwise, the DSL router operates at 10BaseT. — The DSL router can be configured for either DIX format or IEEE 802.3 format. When the DSL router is configured to use IEEE 802.
Configuring the DSL Router Numbered DSL Interface In this scenario, the hosts attached to the DSL router’s Ethernet interface are on a different logical network than the core router. The DSL router is the next hop router for the hosts. The upstream next hop router for the DSL router is the core router. Simplified Network Topology Core Router WAN DSL Router Host (End Users) 99-16609 The hosts can be assigned IP addresses on the network attached to the DSL router’s Ethernet interface.
Configuring the DSL Router IP Routing The DSL router uses destination-based routing for downstream traffic. An IP Routing Table is maintained to specify how to forward IP datagrams downstream. The DSL router is capable of supporting 32 entries in the IP Routing Table. This table can be viewed by both Operator and Administrator access levels.
Configuring the DSL Router Address Resolution Protocol (ARP) Address Resolution Protocol, as specified in RFC 826, is supported in the DSL router. The DSL router provides for a total of 265 ARP table entries. The timeout for completed and uncompleted ARP table entries is configurable. NOTE: The DSL router does not process ARP requests and ARP responses on its DSL interface when it is configured to support RFC 1483 PDU routing (Standard mode). See Routed vs. Bridged PDUs on page 3-10 for more information.
Configuring the DSL Router Network Address Translation (NAT) Network Address Translation is used when a private network’s internal IP addresses cannot be used outside the private network. The IP addresses may be restricted for privacy reasons or they may not be valid public IP addresses. The DSL router provides NAT as described in RFC 1631 The IP Network Address Translator (NAT). NAT allows the private (local) hosts to transparently access public (global) external IP addresses.
Configuring the DSL Router IP Options Processing The NAT and NAPT functions handle and process the IP datagrams with options set as described below. No command is available to set IP options.
Configuring the DSL Router H When the DHCP IP address range is changed, all binding entries, automatically added routes, and ARP table entries for the clients configured with the old address range are removed. H When the DHCP Server is enabled, there can be only one service domain (Ethernet interface) configured. H The IP address for the next hop router that is provided to the hosts in the DHCP reply must be configured. H The subnet mask can be configured along with the IP address range (optional).
Configuring the DSL Router Security The DSL router offers security via the following: H IP Filtering – Can be enabled or disabled. H Land Bug/Smurf Attack Prevention – Always present. IP Filtering NOTE: All Hotwire DSL Router filters are configured on the Hotwire DSL card. By default, filtering is disabled on the Hotwire DSL card for the DSL router.
Configuring the DSL Router Routed vs. Bridged PDUs The DSL router supports both the VNET model and the 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 supports both routed and bridged PDUs. When operating in VNET mode, the DSL router supports bridged PDUs only. NOTE: Standard mode vs. VNET mode is configured on the DSL card at the DSLAM/GranDSLAM chassis.
DSL Router Configuration Examples 4 Configuration Examples The Hotwire DSL Router configuration examples include only a few of the possible scenarios. This chapter covers some of the common configurations. The command syntax will vary based on your network setup. Configuration commands require the access level of Administrator-Config and changes need to be saved while in configuration mode to take effect. Refer to Chapter 2, Accessing the DSL Router.
DSL Router Configuration Examples Basic Configuration Example Customer Premises (CP) End-user Systems 155.1.3.1 Core Router 155.1.3.2 155.1.4.253 WAN Console Port Connection DSL dsl1 155.1.4.254 Ethernet eth1 DSL Router 155.1.3.254 155.1.3.3 Hub 155.1.3.4 00-16590-01 In this basic example: H There are multiple clients with statically assigned public IP addresses configured on the Ethernet side of the DSL router.
DSL Router Configuration Examples Basic NAT Configuration Example Customer Premises (CP) End-user Systems 10.1.3.2 Core Router WAN 10.1.3.3 Console Port Connection 155.1.3.1 DSL Ethernet dsl1 155.1.3.2 eth1 DSL Router 10.1.3.1 10.1.3.4 Hub 10.1.3.5 00-16767 NAT Mapping Public IP Addresses Private IP Addresses 192.128.1.1 10.1.3.2 192.128.1.2 10.1.3.3 192.128.1.3 10.1.3.4 192.128.1.4 10.1.3.5 In this Basic NAT example: H NAT is used for one-to-one mapping of addresses.
DSL Router Configuration Examples NAPT Configuration Example Customer Premises (CP) End-user Systems 10.1.3.2 Core Router 10.1.3.3 Console Port Connection 155.1.3.1 WAN DSL Ethernet dsl1 155.1.3.2 eth1 DSL Router 10.1.3.1 10.1.3.4 Hub 10.1.3.n 00-16611-02 NAPT Mapping Public IP Addresses Private IP Addresses 155.1.3.2 Port 23 10.1.3.4 155.1.3.2 Port 23 10.1.3.2 155.1.3.2 Port 23 10.1.3.3 155.1.3.2 Port n 10.1.3.
DSL Router Configuration Examples Unnumbered DSL Interface with Proxy ARP Configuration Example Customer Premises (CP) Core Router End-user Systems 155.1.3.253 Console Port Connection 155.1.3.1 155.1.3.2 DSL WAN dsl1 Unnumbered Ethernet eth1 DSL 155.1.3.254 Router Hub 155.1.3.
DSL Router Configuration Examples DHCP Relay with Proxy ARP Configuration Example Core Router Customer Premises (CP) 155.1.3.253 End-user Systems DHCP 155.1.3.252 Server Console Port Connection 155.1.3.1 155.1.3.2 DSL WAN dsl1 Unnumbered Ethernet eth1 DSL 155.1.3.254 Router Hub 155.1.3.
DSL Router Configuration Examples DHCP Server with Basic NAT Configuration Example Customer Premises (CP) End-user Systems Core Router 10.1.3.2 155.1.3.1 WAN DSL dsl1 155.1.3.2 Console Port Connection Ethernet eth1 DSL Router 10.1.3.10 10.1.3.3 Hub 10.1.3.9 00-16613-01 Public IP Addresses for Basic NAT Private IP Addresses 192.128.1.1 10.1.3.2 192.128.1.2 10.1.3.3 ... ... 192.128.1.8 10.1.3.
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 dsl1 155.1.3.2 Ethernet 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: H There are clients statically configured and connected to the DSL router.
Monitoring the DSL Router 5 What to Monitor This chapter presents information on how to access and monitor the Hotwire DSL Router’s status and performance statistics. You can monitor DSL router operations by viewing: H LEDs on the DSL router’s front panel. H DSL Router Interfaces Status, including DSL and Ethernet LED status. H DSL Router Statistics, including DSL Service Domain, DSL Management Domain, Ethernet, and IP statistics. H DSL Router SNMP traps.
Monitoring the DSL Router Status of Interfaces From the Command Line Interface, the current status of the Ethernet (eth1) Interface and the DSL (dsl1) Interface can be obtained with one command: show interface The information displayed for Ethernet and DSL Interfaces is presented below. show interface {eth1 | dsl1} Use to request status statistics for the named interface, eth1 or dsl1.
Monitoring the DSL Router Interface Statistics From the Command Line Interface, statistics are available for DSL, Ethernet, and IP processing. Statistics are available for all three selections, eth1, dsl1, and ip, with one command: show statistics The format of the statistics information display is presented below. show statistics [ eth1 | dsl1 | ip ] Use to request statistics for the named interface, eth1 or dsl1, or IP processing statistics.
Monitoring the DSL Router Clearing Statistics From the Command Line Interface, the statistics can be cleared. clear statistics [ eth1 | dsl1 | ip ] Clears the statistics for the named interface. If no interface is entered, ALL statistics for all interfaces are cleared.
Monitoring the DSL Router Table 5-1. Discard Reasons for the Ethernet Interface (eth1) (2 of 2) Discard Reasons for the Ethernet Interface (eth1) Receiver Missed Frame Signal Quality Error on TX Srv Domain Phy TX Queue Overflows Srv Domain Receive Queue Overflows Srv Domain Wrpr TX Queue Overflows TX Halted TX Parity Error TX Underflow Unsupported Encapsulation Protocol Unsupported SNAP Network Protocol Unsupported TypeII Network Protocol Table 5-2.
Monitoring the DSL Router Table 5-2. Discard Reasons for the DSL Interface (dsl1) (2 of 2) Discard Reasons for the DSL Interface (dsl1) Srv Domain Wrpr TX Queue Overflows Unknown Frame Type Errors Unrecognized VNID Unsupported Encapsulation Protocol Unsupported Network Protocol Table 5-3.
Diagnostics and Troubleshooting 6 Diagnostics and Troubleshooting Overview There are several features available to assist in evaluating the Hotwire DSL Router. The following sections are covered in this chapter: H Device Restart H Alarms Inquiry H System Log H Ping H TraceRoute Device Restart The DSL router can be restarted locally or remotely. From the Command Line Interface, type Restart and press Enter.
Diagnostics and Troubleshooting System Log The Hotwire DSL Router can log significant system events (SYSLOG). The SYSLOG can be maintained locally on the DSL router and can also be sent to a remote SYSLOG server, preferably in the management domain. To activate: H The DSL router must be configured to enable the output of SYSLOG messages via the syslog enable command. (The Management Controller Card (MCC) has SYSLOG always enabled.) H An IP address (loopback or remote) must be supplied.
Diagnostics and Troubleshooting syslog level level Specifies the minimum severity level to be logged. Refer to Table 6-1, SYSLOG Messages, for a list of messages by severity level. Minimum access level: Administrator/Config level – The minimum level to be logged. The default is NORM.
Diagnostics and Troubleshooting Table 6-1.
Diagnostics and Troubleshooting 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. From the Command Line Interface, Ping can test connectivity upstream or downstream. ping dest-ip [ mgt | -x source-ip ] [-l bytes ] [-w time ] [-i {eth1 | dsl1} ] Pings the specified destination IP address.
Diagnostics and Troubleshooting TraceRoute The TraceRoute program is an IP diagnostic tool that allows you to learn the path a packet takes from the service domain local host to its remote host. If you are unable to ping a device in a Hotwire network configuration, you may want to run TraceRoute to identify the link (destinations up to 64 hops) between the DSL router and the device that is not forwarding the Ping message.
Command Line Interface A Command Line Interface Feature The Hotwire DSL router is managed with text commands from the Command Line Interface. The Command Line Interface can be accessed: H Locally with an ASCII terminal connected to the Console port, or H Remotely via a Telnet session. The Command Line Interface is ASCII character-based and provides the capability to: H Display the syntax of commands. H Change the operational characteristics of the DSL router by setting configuration values.
Command Line Interface Navigation The Hotwire DSL router uses the following keys (as do most terminal emulation programs): H Enter or Return – Accepts the input. H Ctrl-c – Aborts the entry or clears the input line. H Down Arrow – Repeats an entry within the last five entered. H Up Arrow – Displays the last entry. H Left Arrow – Moves the insertion point one space to the left. H Right Arrow – Moves the insertion point one space to the right.
Command Line Interface Command Line Interface Commands Configuration Control Commands configure {terminal | factory } Enables the Administrator configuration mode. Configuration mode will remain in effect until the exit or logout command has been entered. While in configuration mode, the show commands are unavailable. Minimum access level: Administrator configure terminal – Configuration mode is in effect and all changes entered by the Administrator are made on top of the current running configuration.
Command Line Interface Interface and Service Domain IP Address ifn address {eth1[:ifn ] | dsl1[:ifn ] } ip-address mask [ primary] ifn {dsl1[:ifn ] | eth1[:ifn ] } primary ifn address dsl1 unnumbered Specifies the IP address associated with either the Ethernet interface or the DSL interface. Up to four (4) IP addresses may be assigned on each interface. An interface address and mask cannot be changed while there is a static route (upstream or downstream) that uses it.
Command Line Interface delete {eth1[:ifn ] | dsl1[:ifn ] } Deletes any of the assignments that are configured for the interface. Only the specific Ethernet or DSL interface number needs to be specified. An interface address and mask cannot be deleted while there is a static route (upstream or downstream) that uses it. First, delete the IP route with the ip route delete command (see IP Routing Table). Minimum access level: Administrator/Config eth1, eth1:1, eth1:2, eth1:3, eth1:4 – Ethernet interface.
Command Line Interface ip route create upstream eth1[:ifn] next-hop-ip ip route delete upstream eth1[:ifn] Enter or delete upstream IP routing table entries. When the DSL interface is unnumbered, an IP routing table entry will be created automatically with the next hop router as remote. To configure downstream routers, refer to the previous set of entries. Minimum access level: Administrator/Config create – Create an upstream IP route table entry. delete – Delete an upstream IP route table entry.
Command Line Interface ARP Table arp timeout incomplete [time] Specifies the ARP table timeout value in seconds for incomplete ARP table entries. Default = 5 seconds. Minimum access level: Administrator/Config arp timeout complete [time] Specifies the ARP table timeout value in minutes for complete ARP table entries. Default = 20 minutes. Minimum access level: Administrator/Config arp { create | delete } ip-address mac-address Creates or deletes a single, static ARP table entry.
Command Line Interface NAT nat basic enable Enables the one-to-one mapping function of Basic NAT. Enabling Basic NAT automatically disables NAT NAPT. If Basic NAT is enabled, Proxy ARP must be enabled on the dsl1 interface when the dsl1 interface address is part of the Basic NAT global IP network address. Minimum access level: Administrator/Config nat napt enable Enables the many-to-one mapping function of NAPT. Enabling NAT NAPT automatically disables Basic NAT.
Command Line Interface nat basic map public-ip private-ip nat basic map lower-public-ip lower-private-ip upper-private-ip Statically maps public to private IP addresses for the one-to-one mapping function of Basic NAT. In the first command, a single address pair is mapped. In the second command, a range of IP addresses will be contiguously mapped starting at the pair defined by the lower-public-ip and lower-private-ip argument.
Command Line Interface nat disable Disables the currently enabled NAT, either Basic NAT or NAPT. Minimum access level: Administrator/Config nat purge Purges all mapping entries. Minimum access level: Administrator/Config DHCP Server The DHCP Server can be enabled and disabled. Based on RFC 2131 and RFC 2132, supported options are: H Domain Name H Domain Name Server H Router H Subnet Mask dhcp server {enable | disable } Enables or disables the DHCP server.
Command Line Interface dhcp server leasetime min-lease-time max-lease-time Specifies the lease-time settings used by the DHCP server. Minimum access level: Administrator/Config min-lease-time – Default = 120 minutes (2 hours) max-lease-time – Default = 4320 minutes (72 hours) Example: dhcp server leasetime 120 320 dhcp server router ip-address Specifies the router IP address used by the DHCP server. Minimum access level: Administrator/Config Example: dhcp server router 132.53.4.
Command Line Interface IP Packet Processing IP multicast {enable | disable } Enables or disables the forwarding of IP multicast packets. This setting is retained across power cycles. Minimum access level: Administrator enable – Enable forwarding of IP multicast packets. disable – Disable forwarding of IP multicast packets. Default = disable. IP processing { enable | disable } Enables or disables the processing of IP packets in the service domain. This setting is retained across power cycles.
Command Line Interface Show Command Outputs show console Displays: console enabled or console disabled show system Sample show system display: May 21 09:53:26 2000 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 Selftest Result: [0xxxxx] (if failed) { pass | fail } show config Sample show config display: syslog { enabled | disabled }
Command Line Interface show ip route [ ip-address ] If an IP address is not provided, the entire table will be displayed with the upstream routes displayed first and the downstream routes next. If the IP address is provided, only the specific entry will be displayed. If the next hop IP address = 0.0.0.0, the host is directly reachable on the Ethernet interface (eth1). Minimum access level: Operator Sample show ip route display: source ip-addr source subnet-mask nexthop ip-addr interface x.x.x.x x.x.x.
Command Line Interface show NAT napt Sample show NAT napt display: NAT NAPT – { disabled | enabled } NAT NAPT – public IP-address: x.x.x.x NAT timeout: xx minutes NAT NAPT mappings: private-port private-ip x.x.x.
Command Line Interface show DHCP relay Displays the DHCP relay agent’s current status and configuration. Minimum level access: Administrator Sample show dhcp relay display: DHCP relay – { disabled | enabled } DHCP relay – server ip-addr: x.x.x.x Maximum number of DHCP relay clients: xxx show interface show statistics Refer to Chapter 5, Monitoring the DSL Router. show alarms show syslog show log # Refer to Chapter 6, Diagnostics and Troubleshooting.
Configuration Defaults & 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 abbreviated command line input. Table B-1.
Configuration Defaults & Command Line Shortcuts Table B-1.
Configuration Defaults & Command Line Shortcuts Command Line Input Shortcuts Text in bold is the minimum input for each command line entry. Table B-2.
Configuration Defaults & Command Line Shortcuts Table B-2.
Configuration Defaults & Command Line Shortcuts Table B-2.
Configuration Defaults & Command Line Shortcuts B-6 August 2000 6371-A2-GB20-10
Traps & 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.
Traps & MIBs DSL Router Traps The table below 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 hot_sys.mib signifies an event where access (Hotwire System has been attempted and failed.
Traps & 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.
Traps & MIBs 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. System Group Objects Object Description Setting/Contents sysDescr ( system 1) Provides a full name and version identification for the Hotwire system’s hardware and software.
Traps & MIBs 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. Refer to Table C-3 for the objects supported for the DSL and Ethernet interfaces. The Interface Stack Group table does not apply, but is required for MIB compliance.
Traps & MIBs Table C-3. Interfaces Group Objects (2 of 2) Object Description Setting/Contents ifOperStatus ( ifEntry 8 ) Specifies the current operational state of the interface. H DSL interface: – up(1) – DSL link is established. – down(2) – DSL link is not established. H Ethernet interface: – up(1) – There is a physical connection. – down(2) – There is no physical connection. ifLastChange ( ifEntry 9 ) Indicates the amount of time the interface has been up and running.
Traps & MIBs Extension to Interfaces Table (RFC 1573) This extension contains additional objects for the Interface table. Table C-4 shows the objects supported. Table C-4. Extension to Interfaces Table Object Description Setting/Contents ifName ( ifXEntry 1) Provides the name of the interface. Specifies the interface name: H dsl1 – DSL interface. H eth1 – Ethernet interface.
Traps & MIBs Table C-5. IP Group Objects (2 of 2) Object Description Setting/Contents ipNetToMediaTable (ip 22) This table allows access to contents of the ARP cache. This table is implemented with read/write access. ipNetToMediaType Supported for ARP table entries. (ipNetToMediaEntry 4) H other(1) – Entry is incomplete. H invalid(2) – Invalidates corresponding entry in the ipNetToMediaTable. H dynamic(3) – Results in a response with a badValue error status.
Traps & MIBs Table C-6. IP CIDR Route Group Objects (2 of 2) Object Description Setting/Contents ipCidrRouteType (ipCidrRouteEntry 6) This is a read-only object. H other(1) – Not specified by this MIB (used as interface route). H reject(2) – Entry not valid for downstream routing. H local(3) – Route to a directly connected local host or service network. H remote(4) – Route to a nonlocal host or service network.
Traps & MIBs SNMP Group The SNMP Group objects that apply to a management agent are fully supported.
Traps & MIBs Paradyne Enterprise MIBs The following Paradyne Enterprise MIB Objects are supported by the unit: H Device Control MIB (pdn_Control.mib) H Device Diagnostics MIB (pdn_diag.mib) H Health and Status MIB (pdn_HealthAndStatus.mib) H Configuration MIB (pdn_Config.mib) H Interface Configuration MIB (pdn_inet.mib) H ARP MIB (pdn_Arp.mib) H NAT MIB (pdn_NAT.mib) H DHCP MIB (pdn_dhcp.mib) H DSL Endpoint MIB (DslEndpoint.mib ) H SYSLOG MIB (pdn_syslog.
Traps & 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. Table C-8.
Traps & MIBs Table C-8. Application Test Group Objects (2 of 3) Object Description Setting/Contents 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. applPingTestId (applpingTestEntry 1) Contains identifier that allows the Network Manager to view the results of Ping and TraceRoute tests. Device supports only one at a time.
Traps & MIBs Table C-8. Application Test Group Objects (3 of 3) Object Description Setting/Contents applTraceroutePacketSize (traceroute 4) Specifies TraceRoute packet size. Range + 28 bytes of header information. H 28 — 15028 – Range. applTracerouteTimeOut (traceroute 5) Timeout value in seconds between echo request attempts. H 10 – Default. applTracerouteMaxHops (traceroute 6) Maximum number of hops to be tested. H 8 – Default.
Traps & MIBs Health and Status MIB Objects supported by the Health and Status MIB, pdn_HealthAndStatus.mib, include the following groups: H Device Health and Status H Device Selftest Status H Device Abort Status H Device Failure Status H Traps Table C-9. Device Status Group Objects Table Object Description Setting/Contents devHealthandStatus (devStatus1) This object displays alarm messages if any alarms are generated by the device. Possible alarms are: H Alarm: Management Address Conflict.
Traps & MIBs Configuration MIB The supported groups used with the DSL Configuration MIB, pdn_Config.mib, are: H Device Configuration Copy Group H Trap Configuration Group H Paradyne Device Configuration Time Group H 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.
Traps & MIBs Interface Configuration MIB The Paradyne proprietary Interface Configuration group, pdn_inet.mib, is supported. Refer to Table C-11 for additional details. Table C-11. Interface Configuration Group Objects Table Object Description Setting/Contents pdnInetIpAddress (pdnInetIpAddressTableEntry 1) Identifies the interface IP address. H Interface IP address or pdnInetIpSubnetMask (pdnInetIpAddressTableEntry 2) Identifies the interface subnet mask.
Traps & 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: H 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.
Traps & 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. The groups in this MIB are: H IP Routing Group – This table is an extension of the ipCidrRoute table (see IP CIDR Route Group (RFC 2096) on page C-8. H IP Multicast Group H IP Processing Group H Console Group Table C-12.
Traps & MIBs SYSLOG MIB The System Log MIB (SYSLOG), pdn_syslog.mib, is fully supported. Interface Configuration MIB The Interface Configuration MIB, pdn_IfExtConfig.mib, is used to configure interface-related objects and is fully supported. One object is clarified below: H C-20 pdn_IfExtConfigIPRoutedPDUs (pdnIfExtConfigEntry 1) – You can configure the IP-routed PDUs in the LLC SNAP encapsulation or VC-based Multiplexing encapsulation (RFC1483) in the upstream direction.
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: H Data rate set to 19.
DSL Router Terminal Emulation Terminal Emulation Programs Examples of configuring two different terminal emulation programs: H HyperTerminal – playback feature is accessed through its Transfer menu. H Procomm+ – playback feature is accessed through its Online menu. " Procedure To configure the HyperTerminal: 1. Select menu option Transfer → Send Text File. 2. Select File → Properties. 3. In the Properties dialog, select the Settings tab. 4. Set Emulation to VT100. 5.
Index Symbols D ? for user access, commands available, 2-4 daemon for SYSLOG, 6-2 data rates for DSL routers, 1-3 delete, ip route, A-5 destination IP address, 3-9, A-5 device restart, 6-1 troubleshooting, 6-1 DHCP, 3-7 DHCP relay, configuring, 4-6, A-11 DHCP server, configuring, 4-7, A-10 diagnostics, 6-1 disable, console access, 2-2 discard reasons, for interface statistics, 5-4 DNS, 3-7 downstream router, configuring, 4-8 DSL access system, 1-1 DSL interface, 3-1 configuring, 4-5 statistics, 5-3 DSL
Index F M factory defaults, A-3, B-1 filtering IP packets, 3-9 frame, Ethernet format, A-3 FTP and NAT, 3-7 MAC address, in ARP table, A-7 mapping, NAT function, 4-3, A-9 messages, from SYSLOG, 6-3 MIB compliance, C-3 MIB II IP Group, C-7 System Group, C-3 mode Standard, 3-10 VNET, 3-10 monitoring, DSL router, 5-1 G glossary, vi H help, for current access levels, 2-4 I ICMP, 3-1, 6-5 identifiers, for interfaces, 3-2 IDSL 6301/6302 routers, 1-1 interfaces for DSL routers, 3-1 identifiers, 3-2 IP addre
Index P S Packet SDSL, 6341/6342 DSL routers, 1-1 password, 2-3 PAT (Port Address Translation), see NAPT, 3-6 PDUs Bridged, 3-10 Routed, 3-10 performance statistics, 5-1 Ping, 6-5 POTS, with 6371 DSL router, 1-1 primary IP address, A-4 printing command line input, D-1 proxy ARP, 3-5 configuring, 4-5, A-7 configuring with DHCP relay, 4-6 purge ARP, A-7 IP route, A-6 NAT, A-10 SDSL 6341/6342 routers, 1-1 security, 3-9 server, DHCP, 3-7, 4-7 service domain, IP addresses, 3-2 service subscriber, 1-4 shortcu
