DSLAM FOR 8540 AND 8546 DSL CARDS NETWORK CONFIGURATION GUIDE Document No. 8000-A2-GB21-20 November 1997...
Page 2
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.O.
Contents About This Guide Document Purpose and Intended Audience Document Summary Product-Related Documents Introduction to the HotWire DSLAM What is the HotWire DSLAM? HotWire DSLAM Components HotWire DSLAM Chassis MCC Card DSL Cards What is an RTU? 5170 RTU 5171 Remote PC NIC 5216 and 5246 RTUs 5446 RTU Data Rates...
Page 4
Contents Management Domain Features Overview Network Management Systems — SNMP and DCE Manager Applications for Management Domain Ping TraceRoute TFTP Client Telnet Components of the Network Model Overview Service Domain Components Proxy ARP Management Domain Components Discovering Devices on the Network (Discovery) MCC Card Proxy ARP IP Address Allocation Overview...
Page 5
MIB Compliance Supported Traps General SNMP Agent Configuration Packet Walk-Throughs Overview Packet Walk-Through Using an 8540 DSL Card Service Domain Packet Walk-Through Management Domain Packet Walk-Through Packet Walk-Through Using an 8546 DSL Card Service Domain Packet Walk-Through Management Domain Packet Walk-Through 8000-A2-GB21-20 .
Page 6
Contents Network Configuration Worksheets Overview Summarizing the Network Configuration Management Domain Configuration Worksheets TASK 1: Assign an IP Address to the MCC Card TASK 2: Clear NVRAM TASK 3: Assign an IP Address to the Backplane (s1b) TASK 4: Assign IP Addresses to the DSL Cards TASK 5: Create a Default Route TASK 6: Reset the MCC Card TASK 7: (When Using an 8546 DSL Card) Configure...
Document Purpose and Intended Audience This guide describes the HotWire Digital Subscriber Line Access Multiplexer (DSLAM), its internetworking features, and how it works for the HotWire 8540 and 8546 Digital Subscriber Line (DSL) cards. It also provides information on what you need to know before planning your network.
Page 8
About This xxxx Document Summary Section Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Appendix A Appendix B Appendix C Glossary Index Description Introduction to the HotWire DSLAM. Provides an overview of the HotWire DSLAM and its components.
Page 9
Customer Premises Installation Instructions DCE Manager for HP OpenView for Windows User’s Guide DCE Manager User’s Guide HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide HotWire DSLAM Configuration for 8540 and 8546 DSL Cards Startup Guide HotWire 8100/8200 Interworking Packet Concentrator (IPC) User’s Guide...
Introduction to the HotWire DSLAM What is the HotWire DSLAM? The HotWire Digital Subscriber Line Access Multiplexer (DSLAM) is a multiservices DSL platform that provides high-speed Internet or Intranet access over traditional twisted-pair telephone wiring. The DSLAM chassis houses DSL cards that interoperate with multiple types of HotWire Remote Termination Units (RTU) to deliver applications at multimegabit speeds in support of packet services over a Digital Subscriber Line (DSL) link.
Page 11
Providers (NSPs) or corporate networks by means of the DSL phone line. When using an 8540 DSL card in the DSLAM, the DSLAM can be configured to interoperate with any one of the following RADSL RTUs on each of its four DSL ports: 5170 RTU —...
Page 12
IP addresses or subnets. The following illustration shows a HotWire network configuration from the 8800 DSLAM to multiple RTUs. (Stacked 8600 DSLAMs can also be used in place of an 8800 DSLAM.) 8546 8540 Card Card 8540 8546...
Introduction to the HotWire DSLAM HotWire DSLAM Components The HotWire DSLAM resides in a central office (CO) or wire center. It consists of the following components: HotWire DSLAM chassis MCC card DSL cards In addition, optional POTS splitters can be installed at the CO. For information about a CO POTS Splitter, see the HotWire POTS Splitter Central Office Installation Instructions .
HotWire 8800 DSLAM chassis The HotWire 8800 DSLAM is a 20-slot chassis designed to house up to 18 DSL cards and one MCC card. (The remaining slot is reserved for future use.) The HotWire 8800 DSLAM chassis requires one MCC card and at least one DSL card.
DSL ports are combined onto one 10BaseT interface for connecting to the Internet or Intranet by means of the Network Access Provider’s network. For a list of the supported features of the 8540 and 8546 DSL cards, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide .
The following illustration shows the HotWire 5170 RTU with its 10BaseT interface connected to multiple end-user systems (typically a PC with a LAN card). POTS/DSL From Network Access Provider NID = Network Interface Device For more information about the HotWire 5170 RTU, see the HotWire 5170 Remote Termination Unit User’s Guide .
Introduction to the HotWire DSLAM 5216 and 5246 RTUs The HotWire 5216 and 5246 RTUs are each composed of a DSL modem and a bridge. The HotWire 5216 RTU is designed for home office/residential applications and supports a single end user system. The 5216 RTU supports limited DSL line rates.
Page 18
POTS/DSL From Network Access Provider NID = Network Interface Device For more information about these RTUs, see the HotWire 5216 Remote Termination Unit (RTU) Customer Premises Installation Instructions and the HotWire 5246 Remote Termination Unit (RTU) Customer Premises Installation Instructions . 8000-A2-GB21-20 Introduction to the HotWire DSLAM Optional...
Introduction to the HotWire DSLAM 5446 RTU The HotWire 5446 RTU is composed of a DSL modem supporting full speed DSL line rates and an IP forwarder that can support multiple end-user systems. The 5446 RTU can be connected directly to an end-user system or to multiple end-user systems via an Ethernet (10BaseT) hub.
For a complete listing of the DSL card data rates and information on how to set the line speed, see Chapter 6, DSL Card Configuration , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . 8000-A2-GB21-20...
Introduction to the HotWire DSLAM Overview of the HotWire DSLAM Network Model The HotWire DSLAM and the HotWire RTUs provide high-speed connectivity to the Internet, corporation, or other network service from the end-user system. The HotWire DSLAM network model can be implemented in a number of ways. For example: A Small Office/Home Office (SOHO) implementation with one or more users connected to a LAN needing high-speed connectivity to an Internet Service...
Page 22
The following illustration shows a detailed view of the network model: Network Service Provider ISP Router Internet Router Corporate Intranet 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 one or more Network Service Providers (NSPs).
Page 23
Introduction to the HotWire DSLAM Typically, the NAP network is organized into three components: — Wire center The wire center is usually a local serving office where the wiring from the service subscribers is terminated on the HotWire DSLAM. This could be a CO.
Page 24
If WAN-C is a VLAN switch, the WAN must be a layer 2 switching network supporting a Virtual LAN overlay. In this case: — Each NSP would be a member of a different Virtual LAN. — The VLAN switch at the wire center would support either port-based VLAN switching (i.e., switching all MAC frames received on a specific port to a specific NSP VLAN on the WAN) or port-based VLAN switching with MAC-based attributes (i.e., switching frames received on a specific...
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 RTUs. Features supporting overall system management The central point of access for overall system management is the MCC card. However, the features integral to supporting overall system management are also distributed throughout the HotWire DSLAM and the HotWire RTUs.
Point-to-Point Protocol/High-level Data Link Control (PPP/HDLC) Packets transmitted over DSL links on an 8546 DSL card are encapsulated in PPP/HDLC frames. PPP/HDLC is not supported on the 8540 DSL card. Packets transmitted over LAN ports are encapsulated in Ethernet II MAC frames.
Service Domain Features Internet Control Management Protocol (ICMP) In general, ICMP is supported. However, the options field is not reflected back if the HotWire DSLAM is the destination address (i.e., the HotWire DSLAM receives the data and then returns the packet without the options field).
WS1 sends a packet to Router A. Router A consults its routing table to determine the next hop address (i.e., router IP address) for WS2 because WS2 is on another network (135.1.0.0). Now that it knows the next hop address to Router B, Router A then ARPs for Router B.
IP addressing and the dynamic access control option, see Chapter 5, 8546 DSL Cards User’s Guide . Components of the Network Model . IP Address Allocation , and the HotWire DSLAM for 8540 and November 1997 IP Filtering . For more 8000-A2-GB21-20...
Management Domain Features 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 to simplify the operation and management of very large networks.
DSLAM does, however, pass the packet with the options field to the next hop if the DSLAM is not specified as the destination address. For more information, see Chapter 8, Diagnostics and Troubleshooting , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . November 1997 8000-A2-GB21-20...
For more information, see Chapter 5, MCC Card Configuration , Chapter 6, DSL Card Configuration , and Appendix C, Download Code and Apply Download , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . Telnet The HotWire DSLAM system provides support for telnet, which is a simple remote terminal protocol that is part of the TCP/IP protocol suite.
Components of the Network Model Overview The service and management domains logically comprise the network model. This chapter describes the components that comprise these domains. Service Domain Components The primary purpose of the service domain network is to provide IP routing of customer data between the Network Service Provider (NSP) and the end-user system (ES).
Page 34
Components of the Network Model The following illustration shows another internetworking configuration. This configuration has multiple end users connected to the HotWire RTU using a hub. The number of supported end-user systems depends on whether you use a host or structured subnetting. For more information, see Chapter 5, Allocation NOTE: This illustration does not apply to the 5171 PC NIC and 5216 RTU.
Page 35
A maximally configured HotWire DSLAM system will have 18 DSL cards with each DSL card having its four ports connected to a HotWire RTU for a total of 72 modem ports. Each modem can connect via a hub to 32 active end-user systems to support a total of 2304 users.
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 DSLAM for 8540 and 8546 DSL Cards User’s Guide for more information.
DCE Manager 10BaseT 135.1.2.2/255.255.255.0 MCC Card 135.1.3.1/255.255.255.0 Backplane 135.1.3.3/255.255.255.0 135.1.3.2/255.255.255.0 8540 DSL Card DSL Port 1 DSL Port 2 DSL Port 3 DSL Port 4 November 1997 Components of the Network Model Ordinarily, when DCE Manager is on a separate subnetwork, it will not be in the 135.1.3 or...
NMS. NOTE: Management functions of RTUs associated with an 8540 DSL card are performed by an internal agent on the 8540 DSL card. Provide IP addresses on the router’s interface attached to the MCC card for both subnetworks, so that the router appears to be directly connected to the MCC card’s Ethernet interface as well as the HotWire DSLAM system...
If you want to manage DSL devices across the NSP network, use telnet. For more information on telnet see Chapter 8, Diagnostics and Troubleshooting , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . MCC Card Proxy ARP Proxy ARP is also supported by the MCC card.
Page 40
Components of the Network Model The following illustration shows the packet flow when the DCE Manager wants to send a packet to the HotWire 5446 RTU using proxy ARP. Local Router 135.1.1.2/ 255.255.0.0 Manager 135.1.1.1/ 255.255.255.0 255.255.0.0 DCE Manager: Sends packet to Local Router: Local Router ARP Request for RTU...
IP Address Allocation Overview IP addresses are assigned throughout the network model for components comprising both the service 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. 10BaseT Interface to Management Network Assigning IP Addresses In the HotWire DSLAM network model, there are two distinct domains: a management domain a service domain Within the management domain, there are two subnets as described in Management Domain Components of two IP address allocation schemes can be followed: host addressing or structured subnet addressing.
NOTE: Structured subnetting is supported on the 8546 DSL card and the 5446 RTU. It is not supported, however, on the 8540 DSL card and its corresponding RTUs on the DSL ports. Structured subnet addressing uses the following method: Within the service domain, the NSP would provision a subnet of its domain to a DSL card and all devices behind it.
Page 44
IP Address Allocation The following illustration is an example of structured subnet addressing. 200.200.200. n / 255.255.255.0 n = Any valid IP address, but not within the other subnets To understand why this subnetting scheme works, you may want to consider the IP addresses and subnet masks in hexadecimal: Dotted Decimal 200.200.200.00 / 255.255.255.0...
Page 45
IP Address Allocation 10BaseT 10BaseT 8000-A2-GB21-20 November 1997...
Page 46
IP Address Allocation 10BaseT 10BaseT November 1997 8000-A2-GB21-20...
HotWire 5446 RTU management IP addresses, use the HotWire DSLAM user interface. For step-by-step instructions, see Chapter 4, Configuring the HotWire DSLAM , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . 8000-A2-GB21-20 IP Address Requirement...
IP Address Allocation Peer IP Addresses The s1b backplane 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.
Page 49
The following illustration shows the DSL card with four 5446 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) DSL Port 2 (s1d)
IP Address Allocation Service IP Address Allocation Each NSP allocates IP addresses for the components in each service network as described below. How the IP addresses are allocated is also noted. Component Service Domain Router DSL Card HotWire 5446 RTU End-User System (ES) 5-10 IP Address Requirement...
For more information, see Chapter 5, MCC Card Configuration , Chapter 6, DSL Card Configuration , and Appendix C, Download Code and Apply Download , of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . 8000-A2-GB21-20...
IP Routing Overview This chapter presents information regarding the theory behind the configuration of routes (static and dynamic) on the HotWire DSLAM, as well as examples. Both standard destination-based routes and source-based routes are described. Routing Table The routing table stores information about possible destinations for packets that are routed through the HotWire DSLAM.
IP Routing With destination-based routing, the destination address of the packet being sent is compared to the destination address entries in the routing table. The destination address could possibly match one or more of three types of addresses in the routing table. It could match a: Host route address (that is, a specific destination IP address) e.g., 135.1.3.5, Subnet route, e.g., 135.1.3.0, or Network route, e.g., 135.1.0.0...
PA (proxy ARP) indicates whether or not the router answers ARP requests intended for another machine. For more information about the routing table, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . MCC Card Static Route Example The following illustration shows an example of the MCC card routing table.
The following illustration shows an example of how static routes configured on a DSL card are used in its routing table: 155.1.2.2/ 255.255.0.0 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. DSL Routing Table Host/Net 1) 155.1.3.4...
Dynamic Routes for Dynamic IP Addressing Alternatively, NSPs can administer IP addresses to the end users dynamically (automatically) rather than statically (manually). The dynamic IP addressing feature consists of the following components: DHCP relay agent The DSL card in the DSLAM acts as a DHCP relay agent. The DHCP relay agent is an intermediary function between the end-user system and the DHCP server.
IP Routing Automatic dynamic access control The DSL card supports IP filters to validate user access to the NSP network. If the automatic dynamic access control feature is enabled, filters are configured automatically. The IP filters examine the IP source address of the upstream traffic to validate the end-user system’s IP address.
Page 58
1. The end-user system requests an IP address by broadcasting a DHCP request message to the DHCP server. 2. The DSLAM performs a DHCP relay by acting as a DHCP relay agent. The DHCP relay function of the DSLAM acts as an intermediary between the end-user system and the DHCP server, and works with DHCP servers that support structured subnetting.
See the following section, Authentication Server Administrator For detailed information about the various DHCP relay screens, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide. Also Appendix A, Configuration Worksheets record your network configurations for dynamic IP addressing.
RADIUS Authentication If the authentication server is a RADIUS server, an Access-Request message will have the following format: The user_name will be the end-user’s user ID as received by the DSLAM in the type 0 client ID field of the DHCP request. If the end-user request does not contain a user ID, the corresponding domain name is used as the user_name.
ES2, the destination route is 155.1.3.5 and the next hop address for this destination is 135.1.3.4 (RTU 2). Router 155.1.3.1 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. DSL Routing Table Host/Net 1) 155.1.3.4...
Page 62
When using source routing, do not use the default route. 8000-A2-GB21-20 DSL Card* RTU 1* 135.1.3.3 RTU 2* 135.1.3.4 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. Subnet Mask Next-Hop Address 255.255.255.255 155.1.3.1 255.255.255.255 155.1.3.1...
Page 63
1) 155.1.3.4 2) 155.1.3.5 3) 159.1.3.4 6-12 DSL Card* RTU 1* 135.1.3.3 RTU 2* 135.1.3.4 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. Subnet Mask Next-Hop Address 255.255.255.255 155.1.3.1 255.255.255.255 155.1.3.1 255.255.255.255 159.1.3.1...
IP Filtering Overview A filter is a useful mechanism and can be used to: Secure a network by implementing security rules (policies) 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.
Page 65
The dynamic access control feature is configurable on the DHCP Relay Servers screen. See Chapter 6 of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide for more information. You can create the following filter types: An input filter to prevent packets entering the DSL card through a specified interface from being forwarded.
(either to forward or discard packets). For detailed information on the IP Filter Configuration screen and the IP Network screen, see Chapters 5 and 6 of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . Security Advantages Filtering provides security advantages on LANs as described in the following subsections.
The following illustration is an example of this type of filtering: DSL Card For information on how to set filters on the upstream DSL ports, see Chapters 5 and 6 of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . 155.1.3.4 155.1.3.4...
Service Security Filtering Scenario The following is an example of filtering to ensure service security: NSP1 155.1.2.2 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. DSL Routing Table Host/Net 1) 155.1.3.4 2) 155.1.3.4 3) 155.1.3.6...
Page 69
In the following illustration, ES2 spoofs ES1’s IP address (that is, ES2 assumes ES1’s IP address of 155.1.3.4): NSP1 155.1.2.2 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. DSL Routing Table Host/Net 1) 155.1.3.4...
HotWire DSLAM. This chapter does not, however, describe the procedures on how to configure the SNMP agent. For those procedures, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . MIB Compliance Various pieces of configuration, status, and statistical data within the HotWire DSLAM SNMP agent form a database of information that is accessible from the DCE Manager.
Page 71
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 —...
Supported Traps SNMP defines six basic or standard traps. These messages are identified with a value of 0 through 5 within the generic-trap field of the trap message. (Note that the HotWire DSLAM SNMP agent does not support trap messages with a value of 5.) The specific-trap field of standard trap messages is set to 0 (zero).
Page 73
RTUs. For detailed information about the various SNMP Agent screens mentioned in this chapter, see Chapters 5 and 6 of the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . Also Appendix C, guide provides worksheets to help you plan and record your SNMP configurations.
This chapter provides examples of how data packets are routed through the service and management domains. Packet Walk-Through Using an 8540 DSL Card Service Domain Packet Walk-Through To examine how data packets flow through the service domain, an example of ES1 issuing a ping to NSP1 will be used.
Page 75
4. After ES1 receives the ARP reply, it sends the packet to the MAC address of the 8540 DSL card. 5. Upon receiving this packet, the RTU forwards it to the 8540 DSL card over its DSL interface. 6. When the 8540 DSL card receives this packet, the 8540 DSL card consults its routing table to determine how to route the packet.
6. The 8540 DSL card then consults its routing table to identify the next hop to forward the packet. Since a host route is defined for ES1 (route #2), the DSL interface is used as the next hop. 7. The 8540 DSL card then forwards the packet over the DSL port to that RTU.
Packet Walk-Throughs When ES1 pings NSP1: 1. ES originates a packet addressed to 155.1.2.2. Because they are both on the 155.1 network, ES1 ARPs to map NSP1’s IP address into a MAC address. 2. The RTU receives the broadcast ARP request from ES1. 3.
Page 78
In the following illustration, WS1 is connected to the same LAN as the NMS. Manager 135.1.1.1 WS1 pings the RTU MCC Routing Table Host/Net 1) 135.1.3.4 2) 0.0.0.0 Partial DSL Routing Table Host/Net 1) 135.1.2.0 2) 135.1.1.0 3) 135.1.3.4 When WS1 pings a HotWire RTU: 1.
Page 79
Packet Walk-Throughs 7. From the routing table, the 8546 DSL card determines that 135.1.3.4 is directly connected over s1c (one of the 8546 DSL card’s DSL ports). 8. The 8546 DSL card then forwards the ping to the RTU over s1c. The HotWire RTU then issues a ping reply to IP address 135.1.1.1.
For specific information about the user interface screens and fields, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . Summarizing the Network Configuration...
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 . . . Assign an IP address to the MCC card. (See page A-3.) Clear NVRAM Am I screen does not appear in Task 1.
TASK 1: Assign an IP Address to the MCC Card On the Who Am I screen, assign an IP address to the MCC card. Access the . . . Who Am I screen 8000-A2-GB21-20 Network Configuration Worksheets By . . . Powering on the HotWire DSLAM system.
Page 83
Network Configuration Worksheets Who Am I Screen Prompt 1. Enter the IP address to the MCC card (e1a) at the (nnn.nnn.nnn.nnn): prompt. 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.
TASK 2: Clear NVRAM On the Clear NVRAM screen, clear the non-volatile RAM if the Who Am I screen does not appear after power up (in Task 1) by entering yes at the Initialize NVRAM: yes/no prompt. NOTE: An answer of yes causes the loss of all static configuration information. Any changed parameters will return to default values, including user accounts, filtering information, interface configurations, and port configurations.
You will need to create a separate and distinct network or subnetwork for the 8546 DSL cards and 5446 RTUs, or for 8540 DSL cards. However, the RTUs associated with the 8540 DSL cards do not need to be included in the network.
TASK 4: 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. Access the . . . Configure DSL IP Addr screen 8000-A2-GB21-20 Network Configuration Worksheets By .
Page 87
Network Configuration Worksheets Configure DSL IP Addr Screen Prompt 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. 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.
TASK 5: 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 . . . Static Routes screen Static Routes Screen Prompt...
Page 89
Network Configuration Worksheets Static Routes Screen Prompt 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. 6. Enter dst or press Return at the Source (Src)/ Destination(dst): prompt.
TASK 6: 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 Status prompt. NOTE: After resetting the MCC card, select a DSL card to continue with the management domain configuration.
Network Configuration Worksheets TASK 7: (When Using an 8546 DSL Card) Configure the HotWire 5446 RTU Management Domain IP Addresses On the IP Network screen, configure the HotWire 5446 RTU IP addresses on each 8546 DSL card, which are the RTU’s management domain IP addresses. Access the .
Page 92
IP Network Screen Prompt For DSL port 2 (s1d): 1. Enter the interface name at the Input Interface Name: prompt. 2. Enter the port 2 RTU’s IP address at the (nnn.nnn.nnn.nnn)or address-pool: prompt. 3. Enter route type HOST at the Route to peer (host/net): prompt.
On the Static Routes screen, create a static route to the NMS (on each DSL card). Use this screen to enable the management traffic from the 8540 DSL cards, or the 8546 DSL cards and their downstream 5446 RTUs to be routed back through the MCC card.
Page 94
Static Routes Screen Prompt 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. 3.
Network Configuration Worksheets Service Domain Configuration Worksheets For the service 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 . . . Assign IP addresses to the DSL card interface (e1a).
TASK 1: Assign IP Addresses to the DSL Card LAN Interface (e1a) On the IP Network screen, assign IP addresses to the DSL card LAN interface (e1a). Up to 16 ISP domains can be supported per DSL card. Access the . . . IP Network screen 8000-A2-GB21-20 Network Configuration Worksheets...
Page 97
Network Configuration Worksheets IP Network Screen Prompt 1. Enter the interface name at the Input Interface Name: prompt. 2. Enter the IP address at the (nnn.nnn.nnn.nnn): prompt. This address must be different than the management domain IP address. 3. Enter the subnet mask at the (nnn.nnn.nnn.nnn): prompt.
Network Configuration Worksheets TASK 2: Reset the DSL Card After configuring the e1a interface, reset the card. On the Card Reset screen ( Configuration Card Status Card Reset) , reset the DSL card by entering yes at the yes/no: prompt. 8000-A2-GB21-20 November 1997 A-19...
Each time you create a static route for an end-user system behind an RTU, you should also create a corresponding source-based input filter rule. See Chapter 7, Worksheets HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide for detailed information. Access the . . . Static Routes screen...
Page 100
255.255.255.255.) 4. Do one of the following at the Next Hop IP Address (nnn.nnn.nnn.nnn): prompt: – If using an 8540 DSL card, enter the DSL port number of the associated RTU. – If using an 8546 DSL card, enter the IP address of the associated 5446 RTU management IP address.
Network Configuration Worksheets TASK 4: Create a Default Route or Source Route On the Static Routes screen, create a default route or source route for each DSL card (upstream direction). If creating a default route, fill out one worksheet. If creating source routing, complete one worksheet per domain (up to 16 domains;...
Page 102
Static Routes Screen Prompt 3. Do one of the following: – To create a default route, enter 0.0.0.0 at the Subnet: (nnn.nnn.nnn.nnn): prompt, or – To create a source route, enter a host or subnet mask at the Subnet:(nnn.nnn.nnn.nnn): prompt. 4.
Network Configuration Worksheets TASK 5: Define DHCP Relay Features to Enable Dynamic IP Address Configuration NOTE: Perform this task only if you are planning to have IP addresses assigned to the end-user systems dynamically via a DHCP server. If you are assigning addresses statically, make sure you have completed the worksheets for Task 3: Create Static Routes to End-User Systems and Task 4: Create a Default Route or Source Route .
Page 104
Network Configuration Worksheets You will need to assign a set of domain names that correspond with the already configured Ethernet IP addresses (e1a interface) for the service domains on the Domain Names screen. The domain names are numbered 1 through 16 in the order in which they are entered on this screen.
Page 105
Network Configuration Worksheets A-26 November 1997 8000-A2-GB21-20...
Page 106
Servers 1- 8 Servers 9-16 Screen Prompt 1. Enter the IP address (nnn.nnn.nnn.nnn) of the DHCP server for this domain. NOTE: If you do not enter a value in this field (i.e., the field is null), then all DHCP requests (with domain name information) from this NSP domain’s end users will be dropped.
Page 107
Network Configuration Worksheets Servers 1- 8 Servers 9-16 Screen Prompt 7. (Optional) Enter E (enable) or D (disable) to turn on or turn off dynamic access control security. NOTE: If you choose to enable this feature, the system will automatically create filters that will validate end users accessing the NSP network.
For an explanation of the network model and IP filtering theory, review the chapters in this guide. For specific information about the user interface screens and fields, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide .
Page 109
IP Filtering Configuration Worksheets NOTE: In this release, you can configure up to two filters on the MCC card and up to eight filters on each DSL card. Also, up to 33 rules can be configured for each filter. Keep in mind that for each filter, you will need to configure the default filter action (either to forward or discard packets).
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.
Page 111
IP Filtering Configuration Worksheets Access the . . . IP Filter Configuration screen IP Filter Configuration Prompt 1. At the Action: (Add/Delete/Edit): prompt, type A to add a rule. 2. At the discard/forward: prompt, type the desired filter action. By . . . Entering the line number of the desired filter name on the Filters Table screen...
Page 112
IP Filter Configuration Prompt 3. 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. –...
Page 113
IP Filtering Configuration Worksheets IP Filter Configuration Prompt 4. 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...
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.
Page 115
IP Filtering Configuration Worksheets IP Network Screen Prompt 1. Enter the interface name at the Input Interface Name: prompt. 2. Enter one of the following: – For the Input Filter field, enter the desired filter name at the Filter Name (blank to disable filtering): prompt.
For an explanation of the network model and SNMP agent configuration theory, review Chapter 4, Model , and Chapter 8, interface screens and fields, see the HotWire DSLAM for 8540 and 8546 DSL Cards User’s Guide . Summarizing the General SNMP Agent Configuration...
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.
Page 118
SNMP Communities/Traps Prompt 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...
Page 119
SNMP Configuration Worksheets SNMP Communities/Traps Prompt 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.
Preventing Unauthorized Access Use the SNMP Security screen to enable SNMP security (i.e., prevent unauthorized managers from browsing or configuring 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 those DSL cards in the limited set.
Page 121
SNMP Configuration Worksheets NOTE: To completely disable SNMP access, do one of the following: — Set the IP Address Security field to enable and do not enter any IP addresses on the screen, or — Set the IP Address Security field to enable and make sure that the IP addresses entered on the screen are set to No Access.
Glossary 10BaseT An Ethernet LAN that works on twisted-pair wiring. Address Mask See Subnet Address Mask. 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).
Page 123
Glossary Filter A rule or set of rules applied to a specific interface to indicate whether a packet can be forwarded or discarded. File Transfer Protocol. Internet tool for accessing files linked to the Internet. gateway address The subnet that the end-user system is on. This address, which is the e1a address of the domain, is used as the return address when the authentication server responds.
Page 124
Network Access Provider. The NAP provides a transit network service permitting connection of service subscribers to Network Service Providers (NSPs). The NAP is typically the network provider (e.g., a Regional Bell Operating Company, an Alternate Local Exchange Carrier) that has access to the copper twisted pairs over which the DSLs operate.
Page 125
Glossary Interface name of a DSL card’s DSL port #2. Interface name of a DSL card’s DSL port #3. Interface name of a DSL card’s DSL port #4. Service Subscriber The service subscriber is the user (or set of users) that has contracted to receive networking services (e.g., Intranet access, remote LAN access) from one or more Network Service Providers (NSPs).
Page 126
Wire center A wire center is usually a local serving office where the DSLs from the service subscribers are terminated on the HotWire DSLAM. XTACACS See Authentication Server. 8000-A2-GB21-20 November 1997 Glossary GL-5...