AREA CODE CHANGE Please note that the area code for Paradyne Corporation in Largo, Florida has changed from 813 to 727. For any Paradyne telephone number that appears in this manual with an 813 area code, dial 727 instead.
HOTWIRE DIGITAL SUBSCRIBER LINE ACCESS MULTIPLEXER (DSLAM) NETWORK CONFIGURATION GUIDE Document No.
Copyright 1997 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 Avenue North, P.
Contents About This Guide Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . v Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 1 Introduction to the HotWire DSLAM What is the HotWire DSLAM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 HotWire DSLAM Components .
Contents 4 Components of the Network Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Customer Domain Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Management Domain Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8 SNMP Agent Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 MIB Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Supported Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 General SNMP Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents C SNMP Configuration Worksheets Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Summarizing the General SNMP Agent Configuration . . . . . . . . . . . . . . . C-1 SNMP Agent Configuration Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 Defining a Community and Enabling Traps . . . . . . . . . . . . . . . . . . . . . . C-2 Preventing Unauthorized Access . . . . . . . . . . . . . . . . . . . . . .
About This Guide Document Purpose and Intended Audience This guide describes the HotWire Digital Subscriber Line Access Multiplexer (DSLAM), its internetworking features, and how it works. It also provides information on what you need to know before planning your network.
About This Guide Document Summary vi Section Description Chapter 1 Introduction to the HotWire DSLAM. Provides an overview of the HotWire DSLAM and its components. It also briefly describes the network model and the domain types. Chapter 2 Customer Domain Features. Describes the features that are supported in the customer domain. Chapter 3 Management Domain Features. Describes the features that are supported in the management domain. Chapter 4 Components of the Network Model.
About This Guide Product-Related Documents Document Number Document Title 5020-A2-GN10 HotWire POTS Splitter Central Office Installation Instructions 5030-A2-GN10 HotWire POTS Splitter Customer Premises Installation Instructions 5446-A2-GN10 HotWire 5446 Remote Termination Unit (RTU) Customer Premises Installation Instructions 7700-A2-GB23 DCE Manager for HP OpenView for Windows User’s Guide 7800-A2-GB26 DCE Manager for HP OpenView User’s Guide 8000-A2-GB20 HotWire Digital Subscriber Line Acce
Introduction to the HotWire DSLAM 1 What is the HotWire DSLAM? The HotWire Digital Subscriber Line Access Multiplexer (DSLAM) is a DSL platform that interoperates with a HotWire 5446 Remote Termination Unit (RTU) to deliver applications at multimegabit speed in support of packet services over a Digital Subscriber Line (DSL) link. High-speed service traffic types from the DSL links are groomed and then concentrated for efficient forwarding to backbone routers.
Introduction to the HotWire DSLAM Internet Service Provider Central Office (CO) Data Network Router POTS/ DSL Ethernet DSL CARD DSLAM *CO POTS Splitter MDF CO Switch Legend: DSL - Digital Subscriber Line MDF - Main Distribution Frame Customer Premises (CP) POTS/ DSL HUB RTU HotWire 5446 POTS *CP POTS Splitter 97-15490 RTU - Remote Termination Unit POTS - Plain Old Telephone Service * Optional HotWire DSLAM Components The HotWire DSLAM resides in a Central Office (CO) or wire center.
A B 4 5 6 1 .. ALM A RADSL 8546 RADSL 8546 3 2 1 LINE LAN/WAN SLOT MANAGEMENT 8000 4 3 D DC PWR C ol R X FAN MCC 4 3 2 PO SL D RT 2 SL 1 PO ol C X ET R N . . 1 RT ET ol C N X R ER H ET 3 2 48VDC CLASS 2 OR LIMITED PWR SOURCE TX ER H ET DC FUSES T4A, MIN.
Introduction to the HotWire DSLAM MCC Card The MCC card is a single resource in the HotWire DSLAM that provides consolidated management access for the DSL cards and the HotWire 5446 RTU from any one of the following: SNMP management systems, such as Paradyne’s DCE Manager Remote telnet sessions Local asynchronous terminal Remote asynchronous terminal connected to a modem The MCC card connects to the NMS network via its 10BaseT interface.
Introduction to the HotWire DSLAM What is the HotWire 5446 RTU? The HotWire 5446 RTU resides at the customer premises and is composed of a DSL modem and an IP forwarder. The RTU connects to the local loop to provide high-speed connectivity to the HotWire DSLAM up to distances of 18,000 feet. You can connect the HotWire 5446 RTU directly to an end-user system or to multiple end-user systems via an Ethernet (10BaseT) hub.
Introduction to the HotWire DSLAM End-user System 1 POTS POTS POTS/DSL NID From Network Access Provider POTS Splitter (optional) DSL 10BaseT RTU 10BaseT End-user System 2 HUB . . . NID = Network Interface Device End-user System 32 97-15456 For more information about the HotWire 5446 RTU, see the HotWire 5446 Remote Termination Unit (RTU) Customer Premises Installation Instructions.
Introduction to the HotWire DSLAM Overview of the HotWire DSLAM Network Model The HotWire DSLAM and the HotWire 5446 RTU provide high-speed Internet or Intranet connectivity to a central site from customer premises. NOTE: Data rates and distances vary depending on line speed and line conditions (i.e., the DSL cards measure performance during operation and can adjust the upstream or downstream rate to match changing loop characteristics due to temperature, humidity, or electrical interference).
Introduction to the HotWire DSLAM The following illustration shows a detailed view of the network model: Network Service Provider ISP Router Network Access Provider Wiring Center Access to Point-ofPresence RTU WAN Wiring Center Access to Point-ofPresence Internet Service Subscriber RTU Wiring Center Router RTU Corporate Intranet WAN-C (Router or VLAN Switch) DSLAM DSL RTU RTU 97-15499-01 The Service Subscriber is the user (or set of users) that has contracted to receive networking se
Introduction to the HotWire DSLAM Typically, the NAP network is organized into three components: — Wiring center The wiring center is usually a local serving office where the DSLs from the service subscribers are terminated on the HotWire DSLAM. — Wide Area Network (WAN) The WAN concentrates and switches data traffic from multiple wire centers to one or more Regional Centers. — Regional center The NSP’s Point of Presence (POP) is located (i.e.
Introduction to the HotWire DSLAM — Packets flowing from the NSP network to the subscribers are routed within the NAP network based on the destination IP address (of the subscriber) as is most common for IP-routed networks. If WAN-C is a VLAN switch, the WAN must be a layer 2 switching network supporting a Virtual LAN overlay interconnected via a point-to-point network, a frame relay switching network, or an ATM switching network. In this case: — Each NSP would be a member of a different Virtual LAN.
Introduction to the HotWire DSLAM Understanding the Domain Types Functionally, the HotWire DSLAM network model can be divided into: Features supporting customers Features integral to supporting customers are the DSL cards and HotWire 5446 RTUs. Features supporting overall system management The central point of access for overall system management is the MCC card.
Customer Domain Features 2 Overview This chapter describes the following features that are supported in the customer domain: Data Rates Protocols Address Resolution Protocol (ARP) with Proxy ARP Filtering Data Rates The HotWire DSL card employs Rate Adaptive Digital Subscriber Line (RADSL) devices based on Carrierless Amplitude & Phase (CAP) technology. The RADSL speed is asymmetric.
Customer Domain Features The following are the maximum upstream and downstream data rates with standard #26 AWG wiring, and 24 ISDN disturbers in the same 25-pair binder group: Maximum upstream data rate: 1088 kbps (remote access from the customer premises to the CO up to a distance of 8,300 feet) Maximum downstream data rate: 2560 kbps (remote access from the customer premises to the CO up to a distance of 12,300 feet) For a complete listing of the DSL card data rates, see Appendix C, Data Rates,
Customer Domain Features Proxy ARP (Theory of Operation) An Address Resolution Protocol (ARP) request is used to dynamically bind an IP address to a MAC address. Proxy ARP is a technique by which a router answers ARP requests intended for another machine by supplying its own MAC address (also referred to as the physical address). By answering for another device, the router accepts responsibility for forwarding packets to that device. ARP is supported by the MCC and DSL cards, and the HotWire 5446 RTU.
Customer Domain Features Scenario 2: With Proxy ARP In this scenario, a router is running the proxy ARP software, and WS2 and the default router for WS1 are on the same network (135.1.0.0). LAN A WS1 Default Router (for WS1) 135.1.2.3/16 LAN B WS2 Router 135.1.2.6/24 135.1.3.45/24 135.1.3.9/24 97-15459-01 WS1 again needs to send a packet to WS2. This time, however, the router is running proxy ARP and knows that WS2 lies on LAN B on the same logical subnetwork as the default router (135.1.0.0).
Customer Domain Features Filtering By default, filtering is disabled on the HotWire DSLAM system, but you can enable filtering to selectively filter source or destination packets being routed through the MCC or DSL cards. Filtering provides security advantages on LANs by restricting traffic on the network and hosts based on the IP source/destination address. NOTE: Each time you create a static route for an end-user system behind an RTU, you should also create a corresponding filter.
Management Domain Features 3 Overview This chapter describes the following features that are supported in the management domain: Network Management Systems (NMSs) Applications for Diagnostics Network Management Systems — SNMP and DCE Manager You may want to use an SNMP NMS, such as Paradyne’s DCE Manager for HP OpenView (UNIX) or DCE Manager for HP OpenView for Windows (MS Windows), to simplify the operation and management of very large networks.
Management Domain Features These SNMP capabilities provided by Paradyne’s DCE Manager provide access to MIB II, Entity MIB, and private-enterprise MIB extensions to facilitate: Monitoring and uploading/downloading configuration information from the HotWire DSLAM, and Monitoring and uploading/downloading information to the MCC card, DSL cards, and HotWire 5446 RTU. The DSLAM uses a processor card called the Management Communications Controller (MCC) card in conjunction with DCE Manager.
Management Domain Features tFTP Client The MCC card and DSL card each provide client trivial File Transfer Protocol (tFTP) applications that work with the firmware download and configuration upload or download features. tFTP sessions are established between the MCC card or the DSL card to a tFTP server accessible through the LAN interfaces during these data transfers. A recommended use for configuration transfers is to upload a DSL card configuration to save (archive) the configuration set.
Components of the Network Model 4 Overview The customer and management domains logically comprise the network model. This chapter describes the components that comprise these domains. Customer Domain Components The primary purpose of the customer domain network is to provide IP routing of customer data between the Internet Service Provider (ISP) and the end-user system (ES).
Components of the Network Model The following illustration shows another internetworking configuration. This configuration has multiple end users connected to the HotWire 5446 RTU using a hub. The number of supported end-user systems depends on what route type is used (host or structured subnetting). For more information, see Chapter 5, IP Address Allocation. 10BaseT WAN 10BaseT Router or VLAN Switch ISP End-user System 1 DSL Card DSL/POTS HotWire 5446 RTU End-user System 2 . . .
Components of the Network Model When your HotWire DSLAM system is maximally configured, more users can be supported. With a maximally-configured HotWire DSLAM system (i.e., a HotWire DSLAM with 18 DSL cards with each DSL card having its four ports connected to a HotWire 5446 RTU for a total of 72 modem ports, and each modem can connect via a hub to 32 active end systems), a total of 2304 users can be supported.
Components of the Network Model In this illustration: The local router does an ARP request for the ES. The DSL card receives the broadcast ARP request. The DSL card does an ARP reply for the ES by replying with its own MAC address. Addresses for which the DSL card will proxy ARP must be configured as part of static route configuration. See the HotWire Digital Subscriber Line Access Multiplexer (DSLAM) User’s Guide for more information.
Components of the Network Model Management Domain Components The following illustration shows the components of the network management domain. Note that the router between the MCC card’s 10BaseT interface and the DCE Manager is optional. The MCC card, as previously noted, provides consolidated management for the DSL cards and HotWire 5446 RTUs from SNMP workstations or its VT100 interface. Router DCE Manager * * Ordinarily, when DCE Manager is on a separate subnetwork, it will not be in the 135.1.
Components of the Network Model In other words, the router’s interface to the MCC must be multihomed. This is necessary to support proxy ARP. Discovering Devices on the Network (Discovery) In the illustration on page 4-5, the IP addresses assigned for the router’s interface to the MCC card are 135.1.2.1 and 135.1.3.254. The second IP address is on the same subnetwork as the internal addresses of the DSL cards and the HotWire 5446 RTUs.
Components of the Network Model MCC Card Proxy ARP Proxy ARP is also supported by the MCC card. In a HotWire DSLAM network configuration, when an ARP request is sent by a device (such as a router) to the MCC card’s 10BaseT interface to resolve either the DSL card or HotWire 5446 MAC address, the MCC card will proxy ARP for those devices so long as their IP addresses are on the same network (135.1.3.x). The MCC card responds to these ARP requests with its own MAC address (proxy ARP).
IP Address Allocation 5 Overview IP addresses are assigned throughout the network model for components comprising both the customer and management domains. This chapter describes the IP address allocation schemes for the components that make up the HotWire DSLAM network model. It also describes the naming convention used for the HotWire DSLAM system interfaces.
IP Address Allocation The following illustrates the logical interface naming convention.
IP Address Allocation The following illustration is an example of host addressing. 200.200.200.1 / 255.255.255.255 ES1 200.200.200.2 / 255.255.255.255 ES2 200.200.200.3 / 255.255.255.255 ES3 200.200.200.4 / 255.255.255.255 ES4 DSL Card 200.200.200.n / 255.255.255.
IP Address Allocation To understand why this subnetting scheme works, you may want to consider the IP addresses and subnet masks in hexadecimal: Dotted Decimal Dotted Hexadecimal 200.200.200.00 / 255.255.255.0 C8.C8.C8.00 / FF.FF.FF.00 200.200.200.240 / 255.255.255.240 C8.C8.C8.F0 / FF.FF.FF.F0 200.200.200.224 / 255.255.255.240 C8.C8.C8.E0 / FF.FF.FF.F0 200.200.200.208 / 255.255.255.240 C8.C8.C8.D0 / FF.FF.FF.F0 200.200.200.192 / 255.255.255.240 C8.C8.C8.C0 / FF.FF.FF.
8000-A2-GB21-10 June 1997 ISP16 170.1.1.1/16 .. . ISP8 162.1.1.1/16 ISP7 161.1.1.1/16 ISP6 160.1.1.1/16 ISP5 159.1.1.1/16 ISP4 158.1.1.1/16 ISP3 157.1.1.1/16 ISP2 156.1.1.1/16 ISP1 155.1.2.2/16 a WAN /32 /24 /16 a, b 10BT Notes: b 170.1.3.2/24 .. . IP Interface e1a: 155.1.3.2/24 156.1.3.2/24 DSL Card s1b: 135.1.3.2/24 s1f s1e s1d s1c System Backplane s1b: 135.1.3.1/24 MCC Card DSLAM DCE Manager Server e1a: 135.1.2.2/24 10BT = 255.255.255.255 = 255.255.255.00 = 255.255.00.
IP Address Allocation Management IP Address Allocation The primary functionality of the management domain is monitoring and configuring the network. To provide this capability, IP addresses must be allocated for the components that are monitored and configured by the NMS and MCC card. Component IP Address Requirement MCC Card The MCC card must have two IP addresses: One IP address for connectivity to the NMS or Router (connecting to the NMS). This address is also known as the Router ID.
IP Address Allocation Peer IP Addresses Synchronous ports are configured with peer IP addresses. Peer IP addresses are used to indicate directly connected systems. For the MCC card’s s1b (backplane) interface, the peer IP address should be set to indicate the subnet encompassing the DSL cards and RTUs. The following illustration shows a HotWire DSLAM system configured with one MCC card and four DSL cards. DSLAM System System Backplane Bus DSL Card 1 s1b: 135.1.3.2/24 DSL Card 2 MCC Card s1b: 135.1.3.
IP Address Allocation The following illustration shows the DSL card with four RTUs connected to its DSL ports. The peer address for the four DSL card ports are: — s1c = 135.1.3.3 — s1d = 135.1.3.4 — s1e = 135.1.3.5 — s1f = 135.1.3.6 DSL Card DSL Port 1 (s1c) RTU1 135.1.3.3 DSL Port 2 (s1d) RTU2 135.1.3.4 DSL Port 3 (s1e) RTU3 135.1.3.5 DSL Port 4 (s1f) RTU4 135.1.3.
IP Address Allocation Customer IP Address Allocation Each ISP allocates IP addresses for the components in each customer’s network as described below. How the IP addresses are allocated is also noted. Component IP Address Requirement ISP Domain Router The router that routes ISP traffic to the HotWire DSLAM DSL cards must have one IP address in each customer domain. The router should be multihomed on its LAN port connection to the HotWire DSLAM.
IP Address Allocation Recording Your Configuration Settings It is recommended that you keep a record of your configuration settings when assigning IP addresses to the devices on your network. Appendix A contains the worksheets to help you record those settings. Store the worksheets for reference, as needed. You may also save your configuration settings on the tFTP server.
IP Routing 6 Overview This chapter presents information regarding the theory behind the configuration of static routes on the HotWire DSLAM, as well as examples. Both standard destination-based routes as well as source-based routes are described. Static Routes The routing table stores information about possible destinations for packets being routed through the HotWire DSLAM and identifies the next hop address to which to send the packet.
IP Routing If a match is found for more than one destination address, the order of precedence is: 1. Host route 2. Subnet route 3. Network route 4. Default route Therefore, the packet is sent to the next-hop address specified for that destination which matches and has the highest precedence. A packet routed through the HotWire DSLAM that has a destination address not matching any entry in the routing table is dropped unless a default route is specified.
IP Routing MCC Card Static Route Example The following illustration shows an example of the MCC card routing table. DCE Manager Router 135.1.1.1 135.1.1.2 MCC Card 135.1.2.1 135.1.3.254 e1a:135.1.2.2 DSL Card s1b:135.1.3.1 Unnumbered Interface RTU 135.1.3.4 MCC Routing Table Host/Net/Subnet Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 135.1.3.4* 2) 0.0.0.0 255.255.255.255 0.0.0.0 135.1.3.1 135.1.2.
IP Routing DSL Card Static Route Example The following illustration shows an example of how static routes configured on a DSL card are used in its routing table: 135.1.2.2/16 MCC Card Router ISP 155.1.2.2/16 155.1.2.1/16 155.1.3.1/24 135.1.3.1/16 Unnumbered DSL RTU DSL Card Interface 135.1.3.3 155.1.3.2/16 ES 155.1.3.4 DSL Routing Table Host/Net/Subnet Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 155.1.3.4 2) 135.1.1.1 3) 0.0.0.0 255.255.255.255 255.255.255.0 0.0.0.0 135.1.3.3 135.
IP Routing Source-Based Routing In addition to destination-based routing, the HotWire DSLAM system also supports source-based routing. Source-based routing is a security feature for preventing ES-to-ES routing when they are attached to LANs on different RTUs that are attached to the same DSL card. That is, sourced-based routing can ensure that all upstream traffic within a customer’s domain is sent to the ISP.
IP Routing DSL Card Router RTU 1 s1c ES1 155.1.3.4 135.1.3.3 Packet Flow e1a 155.1.3.1 RTU 2 155.1.2.1 s1d ES2 155.1.3.5 135.1.3.4 155.1.2.2 ISP Partial DSL Routing Table Host/Net/Subnet Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 155.1.3.4 2) 155.1.3.5 255.255.255.255 255.255.255.255 155.1.3.1 155.1.3.1 src (source) src (source) 97-15473-01 Upstream packets from ES1 (and ES2) are sent to 155.1.3.1, where in turn the router would forward them to the ISP.
IP Routing The following illustration shows the packet flow when ES1 sends to ES3, ES1 and ES3 are in different customer domains, and source-based routes are defined for ES1 and ES2 (indicated by the S/D flag). ES1 155.1.3.4 ISP1 155.1.2.2 DSL Card 155.1.2.1 RTU 1 s1c Router Packet Flow 135.1.3.3 ES2 155.1.3.5 Internet 155.1.3.1 159.1.3.1 e1a RTU 2 159.1.2.1 s1d ES3 159.1.3.4 135.1.3.4 159.1.2.
IP Filtering 7 Overview A filter is a useful mechanism. It can be used to secure a network by implementing security rules (policies). You can use a filter to prevent unauthorized network access without making authorized access difficult. By default, filtering is not active on the HotWire DSLAM system. However, you can enable filtering to selectively filter source or destination packets being routed through the MCC or DSL cards.
IP Filtering NOTE: You can specify an input filter for one interface and an output filter for another interface. Do not, however, specify an input filter and an output filter for the same interface. For each filter type, you must set up one or more of the following rule types on the IP Filter Configuration screen (Configuration → IP Router → IP Router Filters): A network address rule type to discard or forward packets/traffic from a specified network or a segment of the network.
IP Filtering Security Advantages Filtering provides security advantages on LANs as described in the following subsections. NOTE: All upstream traffic from an ES is forwarded by the HotWire 5446 RTU to the DSL card unless it is addressed to another ES (in the same subnet) on the same LAN. Management Traffic Leakage Filtering can be used to prevent unwanted traffic from leaking into the management domain.
IP Filtering The following illustration is an example of this type of filtering: End-user System 1 155.1.3.4 RTU End-user System 2 DSL Card X 155.1.3.4 RTU 97-15491 For information on how to set filters on the upstream DSL ports, see Chapters 5 and 6 of the HotWire Digital Subscriber Line Access Multiplexer (DSLAM) User’s Guide. Service Security Filtering Scenario The following is an example of filtering to ensure service security: Router ISP1 155.1.2.2 155.1.2.1 155.1.3.
IP Filtering In the following illustration, ES2 spoofs ES1’s IP address (that is, ES2 assumes ES1’s IP address of 155.1.3.4): Router ISP1 155.1.2.2 DSL Card s1c 155.1.2.1 155.1.3.1 RTU 1 135.1.3.3 ES1 155.1.3.4 155.1.3.2 RTU 2 s1d 135.1.3.5 ES2 155.1.3.4 ES2 spoofing ES1’s address DSL Routing Table Host/Net/Subnet Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 155.1.3.4 2) 155.1.3.4 3) 155.1.3.6 4) 155.1.3.6 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255 155.1.3.
SNMP Agent 8 Overview The Simple Network Management Protocol (SNMP) is an application-level protocol used in network management. A Network Management System (NMS), such as Paradyne’s DCE Manager, communicates to an SNMP agent via SNMP in order to obtain (get) specific parameters or variables within control of the SNMP agent. Note that the set capability will be supported in a future release of the HotWire DSLAM software.
SNMP Agent The HotWire DSLAM supports the following MIBs: MIB II — System Group (described in RFC 1213) MIB II — ICMP Group (described in RFC 1213) MIB II — UDP Group (described in RFC 1213) MIB II — Transmission Group (described in RFC 1213) MIB II — SNMP Group (described in RFC 1213) MIB II — Definitions of Managed Objects for the Ethernet-like Interface Types (described in RFC 1398) MIB II — Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Pro
SNMP Agent authenticationFailure(4). The sending SNMP agent has received an SNMP message specifying a community name which it does not recognize, or requesting an action not permitted for the specified community. There are additional supported traps, which can be found in the Paradyne DSL Enterprise MIBs. See the MIBs for a complete list of traps. The generation of SNMP trap messages can be selectively enabled per configured community.
Packet Walk-Throughs 9 Overview This chapter provides examples of how data packets are routed through the customer and management domains. Customer Packet Walk-Through To examine how data packets flow through the customer domain, an example of ES1 issuing a ping to ISP1 will be used.
Packet Walk-Throughs 7 6 155.1.2.2 155.1.2.1 155.1.3.1 1 Unnumbered DSL Interface DSL Card Router ISP1 2 3 4 ES1 pings ISP1 4 3 2 1 5 155.1.3.2 5 6 RTU 135.1.3.3 7 ES1 155.1.3.4 8 ISP1 issues reply to ping Partial DSL Routing Table Host/Net/Subnet Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 155.1.3.4 2) 155.1.3.4 255.255.255.255 255.255.255.255 155.1.3.1 135.1.3.3 src (source) dst (destination) 97-15474-01 When ES1 pings ISP1: 1.
Packet Walk-Throughs 7. The DSL card then forwards the packet over the DSL port to that RTU. 8. Upon receiving the packet, the RTU forwards the packet to its 10BaseT port because it has a host route for ES1. Management Packet Walk-Through To examine how data packets flow through the management domain, an example of the DCE Manager workstation 1 (WS1) performing a ping to the HotWire 5446 RTU will be used. The following is assumed: A host route to the RTU (135.1.3.4) exists on the MCC card.
Packet Walk-Throughs When WS1 pings a HotWire 5446 RTU: 1. The packet addressed to 135.1.3.4 is routed to the router by normal means. 2. The router then does an ARP request for the RTU because the router’s IP address of 135.1.3.254 is on the same subnetwork as the RTU (with an IP address of 135.1.3.4). Note that the router’s interface to the MCC is multihomed (i.e., it has two IP addresses (135.1.2.1 and 135.1.3.254) assigned to the one interface). 3.
Network Configuration Worksheets A Overview This appendix summarizes the mandatory minimum configuration steps and provides worksheets to assist you in preparing for the configuration of your HotWire DSLAM network. Use the worksheets to record configuration settings such as IP addresses and subnet masks for the MCC card, DSL cards, and RTUs. After the worksheets are completed, you can then configure your network with the assigned settings.
Network Configuration Worksheets Management Domain Configuration Worksheets For the management domain, configure the MCC card, DSL cards, and HotWire 5446 RTUs as follows: Perform this task . . . On this screen . . . To access screen . . . 1. Assign an IP address to the MCC card. Who Am I screen Power on the HotWire DSLAM system. The system displays the Who Am I screen. 2. Assign an IP address to the backplane (s1b) on the MCC card.
Network Configuration Worksheets Who Am I Screen Prompt Your Configuration Setting 1. Enter the IP address to the MCC card (e1a) at the (nnn.nnn.nnn.nnn): prompt. IP Address = 2. Enter the subnet mask at the (nnn.nnn.nnn.nnn): prompt. Note that the system automatically calculates the subnet mask. Press Return to accept the default value or enter a new value at the prompt. Subnet Mask = 3. Reboot the system by typing yes at the yes/no: prompt, when the system highlights OK to restart?.
Network Configuration Worksheets Assign an IP Address to the Backplane (s1b) On the IP Network screen, assign an IP address to the backplane (s1b). Access the . . . By . . . IP Network screen Selecting Configuration → Interfaces → IP Network from the HotWire – MCC menu. IP Network Screen A-4 A-C-B Prompt Your Configuration Setting 1. Enter the interface name at the Input Interface Name: prompt. IP Interface = s1b 2. Enter the base IP address at the (nnn.nnn.nnn.nnn): prompt. Base IP Addr = 3.
Network Configuration Worksheets Assign IP Addresses to the DSL Cards On the Configure DSL IP Addr screen, assign an IP address to each DSL card in the system. 8000-A2-GB21-10 Access the . . . By . . . Configure DSL IP Addr screen Selecting Configuration → DSL Cards → Set IP Address from the HotWire – MCC menu.
Network Configuration Worksheets Configure DSL IP Addr Screen A-G-A Prompt Your Configuration Setting 1. Enter the DSL card subnet mask at the (nnn.nnn.nnn.nnn): prompt. This is the subnet mask for the backplane (s1b) management subnet. DSL Card Subnet Mask = 2. Enter the IP address for each DSL card in the system. Select the appropriate slot number by using the arrow keys to move from one field to another. Once the slot number is selected, enter the IP address for that DSL card at the (nnn.nnn.nnn.
Network Configuration Worksheets Create a Default Route On the Static Routes screen, create a default route to the management domain next hop router. This default route will be used when no other routes in the routing table apply. Access the . . . By . . . Static Routes screen Selecting Configuration → IP Router → Static Routes from the HotWire – MCC menu. Static Routes Screen A-E-A Prompt Your Configuration Setting 1.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 5. Enter 1 at the Input Number: prompt to specify the preference for this route. 1 has the highest preference. The greater the number the lower the preference. Pref= 1 6. Enter dst or press Return at the Source (Src)/ Destination(dst): prompt. S/D= dst 7. Enter no or press Return at the yes/no: prompt to keep the NO value under the PA (proxy ARP) column. PA= no 8.
Network Configuration Worksheets Reset the MCC Card After configuring the MCC card for the management domain, reset the card to install the configuration setting. On the Card Reset screen (Configuration → Card Status → Card Reset), reset the MCC card by entering yes at the yes/no: prompt. NOTE: After resetting the MCC card, select a DSL card to continue with the management domain configuration. To select a DSL card: — Press Return to display the top-level menu (HotWire Chassis menu).
Network Configuration Worksheets Configure the HotWire 5446 RTU Management Domain IP Addresses On the IP Network screen, configure the HotWire 5446 RTU IP addresses on each DSL card, which are the RTU’s management domain IP addresses. Access the . . . By . . . IP Network screen Selecting Configuration → Interfaces → IP Network from the HotWire – DSL menu. IP Network Screen A-C-B Prompt Your Configuration Setting For DSL port 1 (s1c): 1. Enter the interface name at the Input Interface Name: prompt.
Network Configuration Worksheets IP Network Screen A-C-B Prompt Your Configuration Setting 3. Enter route type HOST at the Route to peer (host/net): prompt. Route to Peer= HOST For DSL port 3 (s1e): 1. Enter the interface name at the Input Interface Name: prompt. IP Interface = s1e 2. Enter the peer IP address at the (nnn.nnn.nnn.nnn)or address-pool: prompt. Peer IP Address = 3. Enter route type HOST at the Route to peer (host/net): prompt. Route to Peer= HOST For DSL port 4 (s1f): 1.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 1. Enter 0 or press Return at the Item Number (0 to add new record): prompt to add a new record. 2. Enter the IP address of the NMS at the Destination (or space to delete route): prompt.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 3. Do one of the following at the Subnet:(nnn.nnn.nnn.nnn): prompt: – Enter 255.255.255.255 if you want to create a host route to the IP address specified in Step 2, or – Enter the appropriate subnet mask if you want to enter a network or subnet route.
Network Configuration Worksheets Customer Domain Configuration Worksheets For the customer domain, select the DSL card you want to configure, and then configure the following for each of the DSL cards in the HotWire DSLAM: Perform this task . . . On this screen . . . To access screen . . . 1. Assign IP addresses to the DSL card LAN interface (e1a). (HotWire – DSL) IP Network screen From the HotWire – DSL menu, select: Configuration → Interfaces → IP Network 2.
Network Configuration Worksheets Assign IP Addresses to the DSL Card LAN On the IP Network screen, assign IP addresses to the DSL card LAN. Up to 16 ISP domains can be supported per DSL card. 8000-A2-GB21-10 Access the . . . By . . . IP Network screen Selecting Configuration → Interfaces → IP Network from the HotWire – DSL menu.
Network Configuration Worksheets IP Network Screen A-C-B Prompt Your Configuration Setting 1. Enter the interface name at the Input Interface Name: prompt. IP Interface = e1a 2. Enter the IP address at the 1) IP Addr = (nnn.nnn.nnn.nnn): prompt. 2) IP Addr = This address must be different than the 3) IP Addr = management domain IP address.
Network Configuration Worksheets Create Static Routes to End-User Systems On the Static Routes screen, create a static route to end-user systems on each DSL card. For host addressing, fill out one worksheet for each end-user system. For structured subnet addressing, complete up to 16 worksheets (up to four worksheets for each of the DSL ports corresponding to the four domains supported on each port).
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 1. Enter 0 or press Return at the Item Number (0 to add new record): prompt to add a new record. 2. Enter the IP address of the end-user system at the Destination (or space to delete route): prompt. Host/Net = 3. Do one of the following at the Subnet:(nnn.nnn.nnn.nnn): prompt: – Enter 255.255.255.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 1. Enter 0 or press Return at the Item Number (0 to add new record): prompt to add a new record. 8000-A2-GB21-10 2. Do one of the following: – To create a default route, enter 0.0.0.0 at the Destination (or space to delete route): prompt, or – To create a source route, enter the source route address at the Destination (or space to delete route): prompt. Host/Net = 0.0.0.0 3.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 5. Enter 1 at the Input Number: prompt to specify the preference for this route. 1 has the highest preference. The greater the number the lower the preference. Pref= 1 6. Enter dst or src at the Source (Src)/ Destination(dst): prompt. S/D= 7. Enter no or press RETURN at the yes/no: prompt to keep the NO value under the PA (proxy ARP) column. PA= no 8.
IP Filtering Configuration Worksheets B Overview This appendix provides worksheets to assist you in creating filters for your HotWire DSLAM network. Use the worksheets to record filter parameters such as IP filter types and rule types for the MCC card and DSL cards. Photocopy the worksheets as needed. After the worksheets are completed, define the filters and rule types via the HotWire DSLAM user interface. The worksheets are based on the network model and IP filtering theory described in this guide.
IP Filtering Configuration Worksheets NOTE: For each DSL card, the HotWire DSLAM provides the following default filter names: — lan1 – bound to e1a — dsl1 – bound to DSL port #1 — dsl2 – bound to DSL port #2 — dsl3 – bound to DSL port #3 — dsl4 – bound to DSL port #4 For the MCC card, lan1 (bound to e1a) is the only default filter. When using these filter names as input filters, by default, these filters are already bound to their corresponding interfaces.
IP Filtering Configuration Worksheets Filtering Configuration Worksheets The following sections provide worksheets for configuring filters. Use these worksheets when creating filters on the MCC or DSL cards. Defining the Filter and Rules On the IP Filter Configuration screen, create a filter and define its rules. Complete one worksheet for each rule. NOTE: In this release, up to 33 rules can be configured for each filter. By default, if you do not specify rules, the system will forward packets.
IP Filtering Configuration Worksheets IP Filter Configuration A-E-C Prompt Your Configuration Setting 1. At the Action: (Add/Delete/Edit): prompt, type A to add a rule. 2. Enter the name of the filter for which you want to define rules at the Enter Filter Name: prompt. The DSLAM provides the following filter names that are already bound to the appropriate interface: – For the e1a interface, enter lan1. – For the DSL port #1 interface, enter dsl1. – For the DSL port #2 interface, enter dsl2.
IP Filtering Configuration Worksheets IP Filter Configuration A-E-C Prompt Your Configuration Setting 3. Depending on the rule type (or combination of rule types) you want to define, do one or more of the following: – To define a network address rule type, specify either an IP address or subnet mask in the Source Address and Source Address mask fields, or the Destination Address and Destination Address mask fields.
IP Filtering Configuration Worksheets Binding the Filter On the IP Network screen, indicate whether you want to use the filter you have just defined on the IP Filter Configuration screen as an input filter or an output filter for a specific interface on the MCC or DSL card. NOTE: When using the default input filter names, you do not need to complete a worksheet. The default filter names are already bound to their corresponding interfaces, and no further action needs to be done.
IP Filtering Configuration Worksheets IP Network Screen A-C-B Prompt Your Configuration Setting 1. Enter the interface name at the Input Interface Name: prompt. IP Interface = s1b 2. Enter one of the following: Input Filter = – For the Input Filter field, enter the or desired filter name at the Filter Output Filter = Name (blank to disable filtering): prompt. NOTE: You can specify an input filter for one interface and an output Use an input filter to prevent packets filter for another interface.
SNMP Configuration Worksheets C Overview This appendix provides worksheets to assist you in setting up general SNMP configurations for your HotWire DSLAM network, such as defining communities, enabling traps, and preventing unauthorized access to the DSLAM. Use the worksheets (when configuring both MCC and DSL cards) to record SNMP configuration parameters such as community names and IP addresses for associated SNMP NMS managers for a specific card.
SNMP Configuration Worksheets SNMP Agent Configuration Worksheets The following sections provide worksheets for configuring the SNMP agent. Use these worksheets when preparing SNMP configuration on both the MCC and DSL cards. Defining a Community and Enabling Traps On the SNMP Communities/Traps screen, define a community by specifying the SNMP NMS manager who will receive traps and who has permission to browse. Up to three managers can be assigned for each community.
SNMP Configuration Worksheets SNMP Communities/Traps Prompt Your Configuration Setting 1. Determine whether you want to enable or disable Authentication Failure traps: – Enter enable at the Enable/Disable: prompt to forward authentication failure traps to all SNMP NMS managers assigned to a community name. – Enter disable at the Enable/Disable: prompt to prevent the forwarding of authentication failure traps to all SNMP NMS managers assigned to a community name. Authentication Failure Trap = 2.
SNMP Configuration Worksheets SNMP Communities/Traps Prompt Your Configuration Setting 3. For each community name, you can enter IP addresses of up to three SNMP NMS managers. – At the (nnn.nnn.nnn.nnn): prompt, enter the IP addresses of the SNMP NMS managers. – At the Input Number: prompt, enter the port number for each SNMP NMS manager specified. – At the Enable/Disable: prompt, indicate whether or not you want to enable or disable the generation of traps. Enter E to enable traps.
SNMP Configuration Worksheets Preventing Unauthorized Access Use the SNMP Security screen to enable SNMP security (i.e., prevent unauthorized managers from browsing the HotWire DSLAM network). If address security is to be activated, it should be activated on the MCC and all DSL cards. If the NSP wants to allow an ISP or customer access to a limited set of DSL cards, that NMS’s IP address should only be entered on the MCC and those DSL cards in the limited set. Access the . . . By . . .
SNMP Configuration Worksheets SNMP Security Prompt Your Configuration Setting 1. Determine whether you want to enable or disable IP address security: – Enter enable at the Enable/Disable: prompt to enable (turn on) security. – Enter disable at the Enable/Disable: prompt to disable (turn off) security. IP Address Security = 2. At the (nnn.nnn.nnn.nnn) prompt, enter the IP address of an SNMP NMS manager(s).
Glossary 10BaseT The technical term for twisted-pair Ethernet. Address Mask See Subnet Address Mask. ARP Address Resolution Protocol. The TCP/IP protocol used to dynamically bind an IP address to a low-level physical hardware address (usually a Media Access Control (MAC) address). ATM Asynchronous Transfer Mode. Cell-switching rather than frame relay technology. BootP BOOTstrap Protocol. A protocol the MCC card uses to obtain startup information, including IP address from the DSL cards.
Glossary ISDN Integrated Services Digital Network. ISP Internet Service Provider. LAN Local Area Network. Any physical network technology designed to span short distances. MAC Address Media Access Control Address. Areas of memory your CPU uses to distinguish between the various peripheral devices connected to your system when transferring or receiving data. The MAC address is also known as the physical address. MCC Card Management Communications Controller Card.
Glossary Routing Table A table that stores information about possible destinations for packets being routed through the HotWire DSLAM and identifies the next hop address to which to send the packet. RTU Remote Termination Unit. A device, such as the HotWire 5446 RTU, that is installed at the end-user site (or customer premises). The RTU connects to the local loop to provide high-speed Internet or Intranet connectivity to the HotWire DSLAM.
Index Numbers 10BaseT interface on the MCC and DSL cards (e1a), 5-1 5446 RTU configuring the management domain IP addresses, A-10 description, 1-5 proxy ARP, 4-4 8600 DSLAM, 1-2 8800 DSLAM, 1-3 A address allocation schemes host addressing, 5-2 structured subnet addressing, 5-3 Address Resolution Protocol (ARP), 1-9 address types in routing table, 6-1 applications for management ping, 3-2 telnet, 3-3 tFTP client, 3-3 assigning an IP address to the backplane (s1b), A-4 an IP address to the MCC card, A-2 IP
Index destination–based routing, 6-1 directed broadcasts, 2-2 discovering devices on the network, 4-6 discovery, 4-6 document purpose, v summary, vi domain types, 1-11 DSL card assigning IP addresses, A-15 assigning IP addresses to the DSL cards, A-5 description, 1-4 proxy ARP, 4-3 resetting the card, A-20 static route example, 6-4 DSL ports (s1c, s1d, s1e, and s1f) naming convention of ports on the DSL card, 5-1 setting the peer IP address, 5-7 DSLAM components, 1-2 description, 1-1 overview of the networ
Index tFTP client, 3-3 MCC card assigning an IP address to the MCC card, A-2 description, 1-4 proxy ARP, 4-7 resetting the card, A-9 static route example, 6-3 MIB compliance, 8-1 multicasting, 2-2 N Network Access Provider (NAP), 1-8 network address rule type, 7-2 network configuration worksheets, A-1 Network Management System (NMS), 8-1 network model customer domain components, 4-1 discovering devices on the network, 4-6 domain types, 1-11 management domain components, 4-5 network model Network Access Pr
Index static routes, 6-1, A-17 structured subnet addressing, 5-3 subnet broadcasts, 2-2 subnet route address, 6-1 summarizing filter configuration, B-1 general SNMP agent configuration, C-1 network configuration, A-1 summary of document, vi supported MIBs, 8-2 system backplane interface (s1b), 5-1, 5-7 T telnet, 3-3 tFTP client, 3-3 U using a filter for security advantages, 7-3 V VLAN switch, 1-10 W Wide Area Network (WAN), 1-9 Wide Area Network concentrator (WAN–C), 1-9 wiring center, 1-9 IN-4 June
