Paradyne Hotwire Routers User Manual

Paradyne dsl routers user's guide
Table of Contents

Advertisement

Quick Links

HOTWIRE DSL ROUTERS
USER'S GUIDE
Document No. 6371-A2-GB20-10
August 2000

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Hotwire Routers and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Paradyne Hotwire Routers

  • Page 1 HOTWIRE DSL ROUTERS USER’S GUIDE Document No. 6371-A2-GB20-10 August 2000...
  • 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 Document Conventions Introduction to Hotwire DSL Routers What is a Hotwire DSL Router? DSL Technologies Supported Typical DSL Router System Hotwire DSL Router Features Service Subscriber Accessing the DSL Router Access Control to the DSL Router Levels of Access Changing Access Session Levels...
  • Page 4 Contents Configuring the DSL Router Overview of DSL Router Configuration Interfaces for the DSL Router Ethernet and DSL Interface Identifiers Service Domain IP Address Assignments Numbered DSL Interface Unnumbered DSL Interface IP Routing Network Considerations Address Resolution Protocol (ARP) Proxy ARP Network Address Translation (NAT) Basic NAT Network Address Port Translation (NAPT)
  • Page 5 Monitoring the DSL Router What to Monitor Detecting Problems Status of Interfaces Interface Statistics Clearing Statistics List of Discard Reasons Diagnostics and Troubleshooting Diagnostics and Troubleshooting Overview Device Restart Alarms Inquiry System Log SYSLOG Events SYSLOG Message Display Ping Ping Test Results TraceRoute TraceRoute Test Results Command Line Interface...
  • Page 6 Extension to Interfaces Table (RFC 1573) IP Group (RFC 1213) IP CIDR Route Group (RFC 2096) Transmission Group SNMP Group Ethernet-Like MIB (RFC 2665) Paradyne Enterprise MIBs Device Control MIB Device Diagnostics MIB Health and Status MIB Configuration MIB Interface Configuration MIB...
  • Page 7: About This Guide

    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: Hotwire 6301/6302 IDSL Router Hotwire 6341/6342 Symmetric DSL Router Hotwire 6371 RADSL Router This document is intended for administrators and operators who maintain the endpoints at customer premises.
  • Page 8: Document Summary

    Appendix A Appendix B Appendix C Appendix D Index A master glossary of terms and acronyms used in Paradyne documents is available on the Web at www.paradyne.com. Select Library Manuals Description Introduction to Hotwire DSL Routers. Provides an overview of the Hotwire DSL Routers.
  • Page 9: Product-Related Documents

    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 & MVL . 6371-A2-GB20-10 Document Title Hotwire 6301/6302 IDSL Routers Installation...
  • Page 10: Document Conventions

    About This Guide Document Conventions The following syntax is used throughout this document. Syntax Italics Bold x.x.x.x xx:xx:xx:xx:xx:xx viii 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 11: Introduction To Hotwire Dsl Routers

    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 12: Typical Dsl Router System

    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.
  • Page 13: 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) — DHCP Server (Dynamic Host Configuration Protocol) and DHCP Relay Agent — A full set of IP filters —...
  • Page 14: 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. August 2000 6371-A2-GB20-10...
  • Page 15: Accessing The Dsl Router

    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. 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 16: Changing Access Session Levels

    Accessing the DSL Router Changing Access Session Levels 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.
  • Page 17: Setting Up The New User's Login

    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. At the password> prompt (for Operator), type the default password abc123 and press Enter.
  • Page 18: Telnet Access

    To determine the commands available at the current login access level, enter: help or ? (question mark) the command without any parameters And if you entered a System identity of PARADYNE, the Then the DSL router prompt displays . . . access level is . . . Operator, display mode PARADYNE>...
  • Page 19: Using The List Command

    (no spaces allowed), press Enter, type save, and press Enter. system identity new system identity For example: system identity PARADYNE and press Enter save and press Enter 3. In this example, after saving the entry and ending the configuration mode, the System identity will display: PARADYNE #>...
  • Page 20: Manually Logging Out

    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.
  • Page 21: Configuring The Dsl Router

    Configuring the DSL Router Overview of DSL Router Configuration The Hotwire DSL Routers support various customer premises distribution networks that contain IP forwarding devices or routers, in addition to locally attached hosts or subnets. The Hotwire DSL Router has an IP Routing Table that contains IP address and subnet mask information.
  • Page 22: Ethernet And Dsl Interface Identifiers

    Configuring the DSL Router 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.
  • Page 23: Numbered Dsl Interface

    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.
  • Page 24: Ip Routing

    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.
  • Page 25: Address Resolution Protocol (Arp)

    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...
  • Page 26: Network Address Translation (Nat)

    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) .
  • Page 27: Ip Options Processing

    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. The DSL Router does not process (and drops) any IP datagrams with the following IP options: Loose source and record route (type 131) Strict source and record route (type 133)
  • Page 28: Dhcp Relay Agent

    Configuring the DSL Router When the DHCP IP address range is changed, all binding entries, automatically added routes, and ARP table entries for the clients configured with the old address range are removed. When the DHCP Server is enabled, there can be only one service domain (Ethernet interface) configured.
  • Page 29: Security

    Security The DSL router offers security via the following: IP Filtering – Can be enabled or disabled. 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. If enabled, filtering provides security advantages on LANs by restricting traffic on the network and hosts based on the IP source and/or destination addresses.
  • Page 30: Routed Vs. Bridged Pdus

    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.
  • Page 31: Dsl Router Configuration Examples

    DSL Router Configuration Examples Configuration Examples The Hotwire DSL Router configuration examples include only a few of the possible scenarios. This chapter covers some of the common configurations. The command syntax will vary based on your network setup. Configuration commands require the access level of Administrator-Config and changes need to be saved while in configuration mode to take effect.
  • Page 32: Basic Configuration Example

    DSL Router Configuration Examples Basic Configuration Example Core Router 155.1.4.253 155.1.4.254 In this basic 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 33: Basic Nat Configuration Example

    Basic NAT Configuration Example Core Router 155.1.3.1 155.1.3.2 NAT Mapping Public IP Addresses 192.128.1.1 192.128.1.2 192.128.1.3 192.128.1.4 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 34: Napt Configuration Example

    DSL Router Configuration Examples NAPT Configuration Example Core Router 155.1.3.1 155.1.3.2 NAPT Mapping Public IP Addresses 155.1.3.2 Port 23 155.1.3.2 Port 23 155.1.3.2 Port 23 155.1.3.2 Port n 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 35: Unnumbered Dsl Interface With Proxy Arp Configuration Example

    Unnumbered DSL Interface with Proxy ARP Configuration Example Core Router 155.1.3.253 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. The DSL interface is unnumbered.
  • Page 36: Dhcp Relay With Proxy Arp Configuration Example

    DSL Router Configuration Examples DHCP Relay with Proxy ARP Configuration Example 155.1.3.252 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 37: Dhcp Server With Basic Nat Configuration Example

    DHCP Server with Basic NAT Configuration Example Core Router 155.1.3.1 155.1.3.2 Public IP Addresses for Basic NAT 192.128.1.1 192.128.1.2 . . . 192.128.1.8 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).
  • Page 38: Downstream Router Configuration Example

    DSL Router Configuration Examples Downstream Router Configuration Example Core Router 155.1.3.1 dsl1 155.1.3.2 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. The command line syntax for this example is: ifn address eth1 ifn address dsl1...
  • Page 39: Monitoring The Dsl Router

    Monitoring the DSL Router 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: LEDs on the DSL router’s front panel. DSL Router Interfaces Status, including DSL and Ethernet LED status.
  • Page 40: Status Of Interfaces

    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.
  • Page 41: Interface Statistics

    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.
  • Page 42: Clearing 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.
  • Page 43 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...
  • Page 44 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.
  • Page 45: Diagnostics And Troubleshooting

    Diagnostics and Troubleshooting Diagnostics and Troubleshooting Overview There are several features available to assist in evaluating the Hotwire DSL Router. The following sections are covered in this chapter: Device Restart Alarms Inquiry System Log Ping TraceRoute Device Restart The DSL router can be restarted locally or remotely. From the Command Line Interface, type Restart and press Enter.
  • Page 46: System Log

    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: The DSL router must be configured to enable the output of SYSLOG messages via the syslog enable command.
  • Page 47: Syslog Events

    syslog level level Specifies the minimum severity level to be logged. Refer to Table 6-1, SYSLOG Messages, for a list of messages by severity level. Minimum access level: Administrator/Config level – The minimum level to be logged. The default is NORM. The choices for severity level (displayed as high severity to low severity) are as follows: EMER –...
  • Page 48: Syslog Message Display

    Diagnostics and Troubleshooting Table 6-1. SYSLOG Messages (2 of 2) Level NORM INFO 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 Description Event...
  • Page 49: Ping

    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.
  • Page 50: Traceroute

    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.
  • Page 51: Command Line Interface

    Command Line Interface Command Line Interface Feature The Hotwire DSL router is managed with text commands from the Command Line Interface. The Command Line Interface can be accessed: Locally with an ASCII terminal connected to the Console port, or Remotely via a Telnet session. The Command Line Interface is ASCII character-based and provides the capability to: Display the syntax of commands.
  • Page 52: Navigation

    Command Line Interface Navigation The Hotwire DSL router 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 entered. Up Arrow –...
  • Page 53: Command Line Interface Commands

    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 –...
  • Page 54: Interface And Service Domain Ip Address

    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.
  • Page 55: Ip Routing Table

    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.
  • Page 56 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.
  • Page 57: Arp Table

    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.
  • Page 58: Nat

    Command Line Interface 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.
  • Page 59 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.
  • Page 60: Dhcp Server

    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: Domain Name Domain Name Server...
  • Page 61: Dhcp Relay Agent

    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.
  • Page 62: Ip Packet Processing

    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 –...
  • Page 63: Show Command Outputs

    Command Line Interface Show Command Outputs show console Displays: console enabled 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...
  • Page 64 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.
  • Page 65 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-ip x.x.x.x show traps Sample show traps display: warmstart { disabled | enabled } authen fail { disabled | enabled } selftest { disabled | enabled } devfail { disabled | enabled }...
  • Page 66 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 show Refer to Chapter 5,...
  • Page 67: Configuration Defaults & Command Line Shortcuts

    Configuration Defaults & Command Line Shortcuts Configuration Default Settings All configuration options and factory default settings are listed alphabetically in Table B-1, Default Configuration Settings. Refer to Table B-2, Shortcuts, for abbreviated command line input. Table B-1. Default Configuration Settings (1 of 2) Configuration Option 1483 encap ARP cache entries...
  • Page 68 (trap) traceroute data size traceroute time-out traceroute max number of hops warmstart (trap) August 2000 Factory Default Setting purged disabled enabled disabled disabled paradyne disabled purged purged purged 20 minutes abc123 64 bytes 10 seconds disabled disabled customer...
  • Page 69: Command Line Input Shortcuts

    Configuration Defaults & Command Line Shortcuts Command Line Input Shortcuts Text in bold is the minimum input for each command line entry. Table B-2. Command Line Input Shortcuts (1 of 3) 1483encap [llc | vc] admin {disable | enable} arp create <ip–addr> <mac–addr> arp delete <ip–addr>...
  • Page 70 Configuration Defaults & Command Line Shortcuts Table B-2. Command Line Input Shortcuts (2 of 3) ip route create <dest–ip> <dest–mask> remote ip route create upstream eth1[:ifn] <next–hop–ip> ip route delete <dest–ip> <dest mask> ip route delete upstream eth1[:ifn] ip route purge list [config] logout name <name>...
  • Page 71 Configuration Defaults & Command Line Shortcuts Table B-2. Command Line Input Shortcuts (3 of 3) show dhcp {relay | server} show interface {dsl1 | eth1} show ip route [<ip–addr>] show log [<number of entries>] show nat {basic | napt} show statistics [dsl1 | eth1 | ip] show syslog show system syslog {disable | enable}...
  • Page 72 Configuration Defaults & Command Line Shortcuts August 2000 6371-A2-GB20-10...
  • Page 73: Traps & 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 74: Dsl Router Traps

    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 authenticationFailure...
  • Page 75: Mibs Overview

    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.
  • Page 76 TraceRoute. Setting/Contents The object is set to display a string in the following format: PARADYNE Hotwire DSL; Model: xxxx-xx-xxx ; S/W Release: yy.yy.yy; H/W Revision: zzz; Serial Number: ssssssssssss ; Boot: bb.bb.bb ; 2nd Boot: xx.xx.xx ; DSP: xxx Model starts with the 4-digit model number: 6301 –...
  • Page 77: Interfaces Group (Rfc 1573

    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.
  • Page 78 Traps & MIBs Table C-3. Interfaces Group Objects (2 of 2) Object Description ifOperStatus Specifies the current ( ifEntry 8 ) operational state of the interface. ifLastChange Indicates the amount of ( ifEntry 9 ) time the interface has been up and running. ifInOctets Input Counter objects that (ifEntry 10)
  • Page 79: Extension To Interfaces Table (Rfc 1573

    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 ifName Provides the name of the ( ifXEntry 1) interface. ifHighSpeed Displays the downstream ( ifXEntry 15) speed for the DSL or...
  • Page 80: Ip Cidr Route Group (Rfc 2096

    Traps & MIBs Table C-5. IP Group Objects (2 of 2) Object Description ipNetToMediaTable This table allows access to (ip 22) contents of the ARP cache. ipNetToMediaType Supported for ARP table entries. (ipNetToMediaEntry 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).
  • Page 81: Transmission Group

    Table C-6. IP CIDR Route Group Objects (2 of 2) Object Description ipCidrRouteType This is a read-only object. (ipCidrRouteEntry 6) ipCidrRouteProto Corresponds to routing (ipCidrRouteEntry 7) mechanisms via which this route was learned. Inclusion of values for gateway routing protocols does not imply that the host supports these protocols.
  • Page 82: Snmp Group

    Traps & MIBs SNMP Group The SNMP Group objects that apply to a management agent are fully supported. The following objects apply only to an NMS and return a value of 0 (zero) if accessed: snmpInTooBigs (snmp 8) snmpInNoSuchNames (snmp 9) snmpInBadValues (snmp 10) snmpInReadOnlys (snmp 11) snmpInGenErrs (snmp 12)
  • Page 83: Paradyne Enterprise Mibs

    Paradyne Enterprise MIBs The following Paradyne Enterprise MIB Objects are supported by the unit: Device Control MIB Device Diagnostics MIB Health and Status MIB Configuration MIB Interface Configuration MIB ARP MIB NAT MIB DHCP MIB DSL Endpoint MIB SYSLOG MIB...
  • Page 84: Device Diagnostics Mib

    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.
  • Page 85 Table C-8. Application Test Group Objects (2 of 3) Object applTestOwner Identifies who started the test. (testStatusEntry 5) applTestRowStatus Use to create a new row or (testStatusEntry 6) delete an existing row. applPingTestId Contains identifier that allows the (applpingTestEntry 1) Network Manager to view the results of Ping and TraceRoute tests.
  • Page 86 Traps & MIBs Table C-8. Application Test Group Objects (3 of 3) Object applTraceroutePacketSize (traceroute 4) applTracerouteTimeOut (traceroute 5) applTracerouteMaxHops (traceroute 6) applTracerouteDomain (traceroute 7) applTracerouteIfIndex (traceroute 8) applTracerouteTestOwner (traceroute 9) applTracerouteTestId (applTracerouteResultsEntry 1) applTracerouteHopCount (applTracerouteResultsEntry 2) applTracerouteResultsIpAddr (applTracerouteResultsEntry 3) applTracerouteResultsHopCount (applTracerouteResultsEntry 4) applTracerouteResultsPacketSize...
  • Page 87: Health And Status Mib

    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 This object displays alarm (devStatus1)
  • Page 88: Configuration Mib

    Traps & 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 devConfigAreaCopy...
  • Page 89: Interface Configuration Mib

    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 pdnInetIpAddress Identifies the interface IP (pdnInetIpAddressTableEntry 1) address. pdnInetIpSubnetMask Identifies the interface subnet (pdnInetIpAddressTableEntry 2) mask.
  • Page 90: Dhcp Mib

    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: DHCP Server Configuration Group – Fully supported. One object is clarified below: —...
  • Page 91: Dsl Endpoint Mib

    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: 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 92: Syslog Mib

    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: 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.
  • Page 93: 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 set to 19.2 kbps (19200 bps) Character length set to 8 Parity set to None...
  • Page 94: Terminal Emulation Programs

    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 95: Index

    Index Symbols ? for user access, commands available, 2-4 Numbers 6301/6302 IDSL Routers, 1-1 6341/6342 Symmetric DSL Routers, 1-1 6371 rate adaptive DSL Router, 1-1 access control, 2-1 address resolution protocol, 3-5 Administrator access, 2-2 alarms inquiry, 6-1 ARP, 3-5 enable proxy, A-7 proxy, 3-5 proxy configuration, 4-5...
  • Page 96 Index factory defaults, A-3, B-1 filtering IP packets, 3-9 frame, Ethernet format, A-3 FTP and NAT, 3-7 glossary, vi help, for current access levels, 2-4 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 addresses, A-4 status, 5-1...
  • Page 97 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...

This manual is also suitable for:

6371

Table of Contents