HOTWIRE DSLAM FOR 8540 AND 8546 DSL CARDS NETWORK CONFIGURATION GUIDE Document No.
Copyright 1998 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
Contents About This Guide H Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . v H Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 1 Introduction to the Hotwire DSLAM H What is the Hotwire DSLAM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3 Management Domain Features H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 H Network Management Systems – SNMP and DCE Manager . . . . . . . . . . 3-1 H Applications for Management Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 TraceRoute . . . . . . . . . . . . . . . . . . . . . .
Contents 6 IP Routing H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 H Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 H Static Routes for Static IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 MCC Card Static Route Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 DSL Card Static Route Example . . . . . . . .
Contents A Network Configuration Worksheets H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 H Summarizing the Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 H Management Domain Configuration Worksheets . . . . . . . . . . . . . . . . . . . . A-2 TASK 1: Assign an IP Address to the MCC Card . . . . . . . . . . . . . . . . . A-3 TASK 2: Clear NVRAM . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 supports the Hotwire 8540 and 8546 Digital Subscriber Line (DSL) cards. It also provides information on what you need to know before planning your network.
About This xxxx 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 Service Domain Features. Describes the features that are supported in the service 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 8000-A2-GB21-30 Document Number Document Title 5020-A2-GN10 Hotwire 5020 POTS Splitter Central Office Installation Instructions 5030-A2-GN10 Hotwire 5030 POTS Splitter Customer Premises Installation Instructions 5034-A2-GN10 Hotwire 5034 Indoor POTS Splitter Customer Premises Installation Instructions 5100-A2-GB21 Hotwire 5171 Remote PC Network Interface Card User’s Guide 5100-A2-GB22 Hotwire 5170 Remote Termination Unit User’s Guide 5216-A2-GN10 Ho
About This Guide Document Number Document Title 8600-A2-GN20 Hotwire 8600 Digital Subscriber Line Access Multiplexer (DSLAM) Installation Guide 8800-A2-GN21 Hotwire 8800 Digital Subscriber Line Access Multiplexer (DSLAM) Installation Guide Contact your sales or service representative to order additional product documentation. Paradyne documents are also available on the World Wide Web at: http://www.paradyne.
Introduction to the Hotwire DSLAM 1 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.
Introduction to the Hotwire DSLAM The following illustration shows a high-level view of a Hotwire configuration: NOTE: The cable connection from a DSL card to a Main Distribution Frame (MDF) can either be a direct connection to the MDF or a connection through a POTS splitter to an MDF, but not both. Refer to the appropriate Hotwire DSLAM Installation Guide for more information.
Introduction to the Hotwire DSLAM When using an 8546 DSL card with the 5446 RTU in the DSLAM, the DSLAM can be configured to interoperate with up to four 5446 RTUs. The 5446 RTU operates as an IP forwarder at speeds up to 7 Mbps. This RTU supports up to 32 end-user systems with individual IP addresses or subnets. When using an 8546 DSL card with the 5546 RTU in the DSLAM, the DSLAM can be configured to allow an end-user to utilize an external router with a V.35/EIA-530 interface.
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: H Hotwire DSLAM chassis H MCC card H DSL cards In addition, optional POTS splitters can be installed at the CO. For information about a CO POTS Splitter, see the Hotwire 5020 POTS Splitter Central Office Installation Instructions. Hotwire DSLAM Chassis There are two types of chassis: H Hotwire 8600 DSLAM chassis ..
Introduction to the Hotwire DSLAM H 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.
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 RTU from any one of the following: H SNMP management systems, such as HP OpenView with Paradyne’s OpenLanet DCE Manager (via the MCC card’s Ethernet port), H Remote telnet sessions (via the MCC card’s Ethernet port), H Local asynchronous terminal (via the MCC card’s VT100 serial port), or H Remote asynchronous terminal connec
Introduction to the Hotwire DSLAM 5170 RTU The Hotwire 5170 RTU is a standalone unit designed for the home-office users with a LAN. The RTU communicates with any computer equipment or router using its Ethernet network interface card (NIC). Control of the 5170 RTU is supplied by a windows-based diagnostics utility which enables users to check RTU status, network transmission status, and run diagnostic tests. You can connect the 5170 RTU directly to your PC using an 8-pin modular Ethernet cable.
Introduction to the Hotwire DSLAM 5171 Remote PC NIC The Hotwire 5171 PC Network Interface Card (NIC) is a 16-bit ISA, add-on card with a 6-pin telephone modular jack connector used for the DSL network connection. The 5171 PC NIC edge connector plugs into a 16-bit expansion slot in an IBM-compatible 80486 (or higher) system board and conforms to ISA bus standards. The following illustration shows a PC with an internal Hotwire 5171 PC NIC.
Introduction to the Hotwire DSLAM The Hotwire 5246 RTU is designed for small office or home office (SOHO) applications and supports up to 32 end-user systems with a LAN. The Hotwire 5246 supports full speed DSL line rates and filters local LAN traffic from traversing the DSL link by incorporating learning bridge functionality.
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.
Introduction to the Hotwire DSLAM End-user System 1 Optional POTS POTS Splitter POTS POTS/DSL NID From Network Access Provider DSL End-user System 2 5446 RTU 10BaseT HUB . . . NID = Network Interface Device End-user System 32 97-15456b For more information about the 5446 RTU, see the Hotwire 5446 Remote Termination Unit (RTU) Customer Premises Installation Instructions.
Introduction to the Hotwire DSLAM 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. This means that the downstream rate (from the DSLAM to the RTU) is faster than the upstream rate (from the RTU to the DSLAM). You can manually set the speed (providing the line you are using can support the specified speed) or set the mode to rate adaptive.
Introduction to the Hotwire DSLAM The network model for these examples can be partitioned into the following building blocks: H Network Service Provider (NSP) H Network Access Provider (NAP) H Service Subscriber Network Service Provider Network Access Provider Service Subscriber 97-15457 The following illustration shows a detailed view of the network model: Network Service Provider ISP Router Network Access Provider Wire Center Access to Point-ofPresence RTU WAN Wire Center Access to Point
Introduction to the Hotwire DSLAM H 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). Service Subscribers may be: — Residential users connected to public network services (e.g., the Internet) — Work-at-home users connected to their corporate Intranet LAN — Commercial users at corporate locations (e.g.
Introduction to the Hotwire DSLAM One or more Hotwire DSLAMs are connected to a Wide Area Network Concentrator (WAN-C) via a LAN. The WAN-C concentrates data traffic from one or more DSLAMs into facilities providing access to the WAN. The WAN-C can be either a router (a layer 3 networking device) or a VLAN switch (a layer 2 networking device). H If WAN-C is a router, the WAN must be a routed IP network (i.e., a network of interconnected IP routers).
Introduction to the Hotwire DSLAM — A different next-hop router is specified for each NSP address domain in contrast to the routed network case where a single next-hop router was specified for all NSP domains. If the DSLAM does not know the MAC address of the NSP premises router, it uses ARP to obtain the MAC address from the NSP premises router prior to forwarding the packet (i.e., the wire center VLAN switch forwards an ARP request over the WAN to the NSP router).
Service Domain Features 2 Overview This chapter describes the following features that are supported in the service domain: H Protocols H Address Resolution Protocol (ARP) with Proxy ARP H Filtering Protocols The Hotwire DSLAM and Hotwire RTUs forward IP packets between the end-user system and the Network Service Provider using the following protocols: H 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
Service Domain Features H 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). The Hotwire DSLAM does, however, pass the packet with the options field to the next hop if the DSLAM is not specified as the destination address.
Service Domain Features Workstation 1 (WS1) needs to send a packet to workstation 2 (WS2). For the packet to arrive successfully at WS2: H There is a static route on Router A for WS2. The next hop is Router B and the destination is WS2. H WS1 sends a packet to Router A. H 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).
Service Domain Features Therefore, when WS1 needs to send a packet to WS2, this is the sequence of events: H WS1 sends a packet to Router A. H Router A invokes ARP to map the WS2’s IP address into a MAC address, because WS2 appears to Router A to be on the same 135.1 subnet. H Router B running proxy ARP software receives the broadcast ARP request from Router A, knows that WS2 is on LAN B, and responds to Router A’s ARP request with its own MAC address.
Management Domain Features 3 Overview This chapter describes the following features that are supported in the management domain: H Network Management Systems (NMSs) H 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.
Management Domain Features These SNMP capabilities provided by Paradyne’s OpenLane DCE Manager provide access to MIB II, Entity MIB, and private-enterprise MIB extensions to monitor information. The DSLAM uses a processor card called the MCC card in conjunction with DCE Manager. The MCC card provides the single management interface to the Hotwire DSLAM cards and RTUs.
Management Domain Features TraceRoute The TraceRoute program is a TCP/IP diagnostic tool that allows you to learn the path a packet takes from its 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 links (destinations up to 64 hops) between the DSL card and an RTU as well as which device is not forwarding the ping message.
Management Domain Features This page intentionally left blank.
Components of the Network Model 4 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).
Components of the Network Model WAN NSP End-user System 10BaseT Router or VLAN Switch DSL DSL/POTS Card DSL/ POTS 5446 RTU 5546 RTU Router 10BaseT End-user LAN System End-user System End-user System 97-15461-03 4-2 April 1998 8000-A2-GB21-30
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, IP Address Allocation. NOTE: This illustration does not apply to the 5171 PC NIC and 5216 RTU. The 5171 PC NIC and 5216 RTU are for single end-user system configurations only.
Components of the Network Model 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. NOTE: The following illustration does not apply to the 5171 PC NIC and 5216 RTU. The 5171 PC NIC and 5216 RTU are for single end-user system configurations only.
Components of the Network Model Proxy ARP Proxy ARP is supported by the DSL cards and the Hotwire 5446 RTU. It allows the end users to appear to be directly connected to the router providing access to the NSP network. This is an advantage because routers connected to a device running proxy ARP require less configuration. The following scenarios show why this is an advantage.
Components of the Network Model 5446 RTU Proxy ARP The Hotwire 5446 RTU utilizes proxy ARP to enable connectivity between end systems that are attached to separate RTUs, but reside on the same subnetwork. The Hotwire 5446 RTU will proxy ARP for the end-user system that is physically connected to another Hotwire 5446 RTU where the destination end-user system is logically connected to the same subnetwork as the sender end-user system.
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 RTUs from remote network management workstations by means of SNMP, telnet, or by local access through its VT100-serial interface.
Components of the Network Model To facilitate management of the DSL cards and Hotwire RTUs through the MCC card: H Assign IP addresses from the management domain to the internal backplane interfaces of each DSL card and 5446 RTU interface in the same subnet as the MCC card’s backplane interface (as shown in the previous illustration). This is a separate subnetwork from the MCC card’s 10BaseT port.
Components of the Network Model MCC Card DSL Card 1 RTU RTU DSL Card 2 RTU RTU RTU RTU 97-15492 NOTE: It is not recommended that the DCE Manager access a DSL card via its Ethernet port because the Entity MIB on the DSL card does not reflect a view of the entire Hotwire DSLAM system. It reflects only the view of the DSL card discovered. Also, in a fully configured DSLAM, 18 additional devices will be discovered and appear on your network map.
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 DCE Manager 135.1.1.1/ 255.255.0.0 DCE Manager: Sends packet to Local Router MCC Card 135.1.2.1/ 255.255.255.0 e1a:135.1.2.2/ 255.255.255.0 s1b:135.1.3.1/ 255.255.255.0 135.1.3.254 8546 DSL Card 5446 RTU s1b:135.1.3.2/ 255.255.255.0 135.1.3.
IP Address Allocation 5 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.
IP Address Allocation Host Addressing Host addresses within the service domain are assigned to end-user systems. Because they are host addresses, they have a subnet mask of 255.255.255.255 and can be geographically dispersed. (When structured subnet addressing is discussed in the next section, you will see how IP addresses are allocated to certain areas.) This conserves address space, but may not scale well to large numbers of end-user systems.
IP Address Allocation Structured Subnet Addressing As an alternative to using host routes for end-user systems, structured subnetting can be used. It scales better and performs better, but it does not allow geographically dispersed subnets. 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. For 5546 RTUs, the router attached to the RTU must be configured with structured subnets.
IP Address Allocation In the previous illustration: H Each of the four DSL ports is on a different subnetwork of size 16, and the subnet mask for the four ports is 255.255.255.240. H The LAN port (10BaseT port) IP address is 200.200.200.n (where n can be any valid IP address, but cannot be an IP address within the other subnets), and its subnet mask is 255.255.255.0.
5-6 NSP Router 155.1.3.1/ 255.255.255.0 155.1.2.1/ 255.255.255.0 April 1998 IP Interface e1a: 155.1.3.2/ 255.255.255.0 DSL Card* s1b: 135.1.3.2/ 255.255.255.0 s1f s1e s1d s1c DSL DSL DSL DSL RTU* RTU 155.1.3.36/ 255.255.255.0 135.1.3.4/ 255.255.255.255 RTU* 155.1.3.3/ 255.255.255.0 135.1.3.3/ 255.255.255.255 10BaseT ES32 .. . ES4 ES3 ES2 ES1 97-15475a-01 ES32 .. . ES4 ES3 ES2 ES1 ES32: 155.1.3.68/255.255.255.0 .. . ES4: 155.1.3.40/255.255.255.0 ES3: 155.1.3.39/255.255.
8000-A2-GB21-30 April 1998 NSP16 170.1.1.1/ 255.255.0.0 .. . 170.1.3.1/ 255.255.255.0 .. . 155.1.3.1/ 255.255.255.0 170.1.3.2/ 255.255.255.0 .. . s1d s1c s1f IP Interface e1a: 155.1.3.2/ 255.255.255.0 s1e 156.1.3.2/ 255.255.255.0 DSL Card s1b: 135.1.3.2/ 255.255.255.0 DSL DSL DSL DSL RTU RTU 159.1.3.3/ 255.255.255.0 160.1.3.3/ 255.255.255.0 161.1.3.3/ 255.255.255.0 162.1.3.3/ 255.255.255.0 135.1.3.4/ 255.255.255.255 RTU 155.1.3.3/ 255.255.255.0 156.1.3.3/ 255.255.255.0 157.1.3.
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 an NMS and MCC card. Component IP Address Requirement MCC Card The MCC card must have two IP addresses: H 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 To configure the MCC card, the DSL card management IP addresses, and the 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. Peer IP Addresses The s1b backplane ports are configured with peer IP addresses. Peer IP addresses are used to indicate directly-connected systems.
IP Address Allocation H For the DSL card’s s1c through s1f interfaces, the peer IP address should be set to indicate the management IP address of the directly connected 5446 RTU. In the case of a 5546 RTU, the peer IP address should match the IP address of the router interface connected to the RTU. (Peer IP addresses need to be set for 5446 and 5546 RTUs only. They do not apply to any other RTU type.
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 IP Address Requirement Service Domain Router The router that routes NSP traffic to the Hotwire DSLAM DSL cards must have one IP address in each service domain. The router should be multihomed on its LAN port connection to the Hotwire DSLAM.
IP Address Allocation Dynamic IP Addressing The Hotwire DSLAM system allows the use of Dynamic Host Configuration Protocol (DHCP) to facilitate the automatic assignment of end-user system IP addresses. With the dynamic IP addressing feature, NSPs can administer IP addresses to the end users dynamically (automatically) rather than statically (manually). An IP address can be reused once the end user no longer requires the address (i.e.
IP Routing 6 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. It also identifies the next hop address to which to send the packet.
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: H Host route address (that is, a specific destination IP address) e.g., 135.1.3.5, or H Subnet route, e.g., 135.1.3.0, or H Network route, e.g., 135.1.0.0.
IP Routing H Pref indicates the measurement of preference of one route to another, if you have two routes going to the same destination. (The lower the number the more preferable.) This route is compared to others for the same address. H S/D indicates if the address in the Host/Net field is a source address or a destination address. H PA (proxy ARP) indicates whether or not the DSLAM card or RTU answers ARP requests intended for another machine.
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: NMS Ethernet Interface 155.1.2.2/ 255.255.0.0 MCC Card 135.1.3.1/ 255.255.0.0 Router NSP 135.1.2.2/ 255.255.0.0 155.1.2.1/ 255.255.0.0 DSL Card* Unnumbered DSL RTU* Interface s1c 135.1.3.3 155.1.3.1/ 255.255.255.0 155.1.3.2/ 255.255.0.0 ES 155.1.3.4 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address.
IP Routing 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: H 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 H 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. This feature enhances security by preventing an end user from spoofing the IP address of another user on a different DSL port. The DSLAM checks the end-user’s IP address.
IP Routing 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. At this point, the following events occur: A. The DHCP relay within the DSLAM intercepts the end user’s DHCP request for an address. B.
IP Routing NOTE: If an end user has a static configuration (that is, the user manually enters an IP address and the DSLAM and the RTU have a static host route), then the end user will not be allowed to obtain the same IP address via DHCP. If an end user obtains an IP address via DHCP, then that IP address is bound to a particular DSL port (behind which the end user resides) on the DSLAM.
IP Routing Notes to the Authentication Server Administrator If the authentication process is to be invoked as part of dynamic addressing, the authentication request from the DSLAM must be in either RADIUS or XTACACS format. The authentication server will receive an authentication request from the Hotwire DSLAM before the end-user’s request for an address is relayed to the DHCP server. NOTE: The IP source address for these requests will be the e1a interface IP address associated with the domain.
IP Routing XTACACS Authentication If the authentication server is an XTACACS server, a Login message will have the following format: H 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. H The password will be the e1a IP address (gateway address) associated with this domain in ASCII dotted decimal format.
IP Routing Without Source-Based Routing The following illustration shows that with destination routing ES1 can send packets to ES2 based on the static route table. That is, when ES1 sends a packet to ES2, the destination route is 155.1.3.5 and the next hop address for this destination is 135.1.3.4 (RTU 2). DSL Card* RTU 1* s1c ES1 155.1.3.4 135.1.3.3 Packet Flow Router 155.1.3.1 RTU 2* 135.1.3.4 s1d ES2 155.1.3.5 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address.
IP Routing With Source-Based Routing With source-based routing, the source address of upstream packets sent from an ES are compared to the source address listed in the static route table. If a match is found, the packet is sent to the next-hop address specified for that source address. The following illustration shows the packet flow when ES1 sends to ES2, and when source-based routes are defined for ES1 and ES2 (indicated by the S/D flag). DSL Card* Router RTU 1* s1c ES1 155.1.3.4 135.1.3.
IP Routing The following illustration shows the packet flow when ES1 sends to ES3, ES1 and ES3 are in different service domains, and source-based routes are defined for ES1 and ES2 (indicated by the S/D flag). ES1 155.1.3.4 NSP1 155.1.2.2 DSL Card* 155.1.2.1 s1c Router Packet Flow RTU 1* 135.1.3.3 ES2 155.1.3.5 Network 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.2 NSP2 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address.
IP Routing This page intentionally left blank.
IP Filtering 7 Overview A filter is a useful mechanism and can be used to: H Secure a network by implementing security rules (policies). H 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: If your system is set up for dynamic IP addressing and you have enabled the dynamic access control feature, you do not need to configure filters because this is done automatically. However, you will need to bind the filters to the appropriate interface if you have unbound them. The dynamic access control feature is configurable on the DHCP Relay Servers screen. See Chapter 5, DSL Card Configuration, of the Hotwire DSLAM for 8540 and 8546 DSL Cards User’s Guide for more information.
IP Filtering H A socket address rule type to limit certain applications. This rule type is used primarily when filtering TCP or UDP packets, and may be used in conjunction with a network address rule type or a host address rule type. The destination (socket) port number specified in the Destination Port No. field and source (socket) port number specified in the Source Port No.
IP Filtering Management Traffic Leakage Filtering can be used to prevent unwanted traffic from leaking into the management domain. That is, filtering prevents NSP packets with management IP destinations from being accepted for local delivery or routing. For example, if the NSP network is 155.1.00.00 and the management network is 135.1.00.00, filters can be defined that would prevent any traffic entering from the 10BaseT port from being forwarded to the 135.1.00.00 network through the DSL card.
IP Filtering Service Security Filtering Scenario The following is an example of filtering to ensure service security: 155.1.2.2 DSL Card* Router NSP1 s1c 155.1.2.1 RTU 1* 135.1.3.3 ES1 155.1.3.4 155.1.3.2 155.1.3.1 RTU 2* s1d 135.1.3.5 ES2 155.1.3.6 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. DSL Routing Table Host/Net Subnet Mask 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.
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 NSP1 155.1.2.2 DSL Card* RTU 1* s1c 135.1.3.3 155.1.2.1 ES1 155.1.3.4 155.1.3.2 155.1.3.1 RTU 2* s1d 135.1.3.5 *If DSL card is an 8540 DSL card, associated RTU will not have an IP address. ES2 155.1.3.4 ES2 spoofing ES1’s address DSL Routing Table Host/Net Subnet Mask 8540 DSL Card Next-Hop Address 1) 155.1.3.4 2) 155.1.3.4 3) 155.1.3.6 4) 155.1.3.6 255.
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 OpenLane DCE Manager, communicates to an SNMP agent via SNMP in order to obtain (get) specific parameters or variables within control of the SNMP agent. When DCE Manager is configured properly, it can communicate with the Hotwire DSLAM SNMP agent.
SNMP Agent 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. This collection of information is called a Management Information Base (MIB). The basic definitions of the content of an SNMP agent’s MIB are defined within various Internet Request for Comments (RFC) documents.
SNMP Agent 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). The specific-trap field of enterprise-specific messages defines the trap.
SNMP Agent General SNMP Agent Configuration Depending on your specific network configuration, various aspects of the Hotwire DSLAM SNMP agent may need to be configured. For example, you may want to set up your system to send SNMP traps to a specific SNMP NMS manager. The Hotwire DSLAM system provides four default community names (two read/write community names and two read-only community names) per MCC or DSL card. These community names are similar to passwords.
Packet Walk-Throughs 9 Overview 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.
Packet Walk-Throughs The following illustration shows how data packets flow through the service domain. In this illustration ES1 is connected to the same LAN as the Hotwire RTU. 6 7 Router NSP1 155.1.2.2 155.1.2.1 155.1.3.1 1 2 3 4 ES1 pings NSP1 4 3 2 1 5 Unnumbered 8540 DSL DSL Card Interface s1c 155.1.3.2 5 6 7 ES1 155.1.3.4 RTU* 8 NSP1 issues reply to ping * The RTU can be a 5170, 5171, 5216, or 5246 RTU.
Packet Walk-Throughs NSP1 then issues a reply to the ping. 1. The NSP sends the ping reply packet addressed to 155.1.3.4. 2. By normal means, the packet arrives at the router. 3. Because the router has an interface with an address 155.1.3.1 (on 155.1.3 subnet), it ARPs for 155.1.3.4. 4. Because the 8540 DSL card has a host route (marked PA=y) for 155.1.3.4, it responds to the ARP request with its own MAC address (proxy ARP). 5. Then, the ping reply is sent directly to the 8540 DSL card. 6.
Packet Walk-Throughs The following illustration shows how data packets flow through the service domain. In this illustration ES1 is connected to the same LAN as the Hotwire RTU. 155.1.2.2 155.1.2.1 155.1.3.1 1 Unnumbered DSL Interface 8546 DSL Card Router NSP1 2 3 4 ES1 pings NSP1 4 3 2 1 5 6 7 155.1.3.2 5 6 RTU 135.1.3.3 ES1 155.1.3.4 8 7 NSP1 issues reply to ping Partial DSL Routing Table Host/Net Subnet Mask Next-Hop Address S/D (Source/Destination) 1) 155.1.3.4 2) 155.1.3.
Packet Walk-Throughs NSP1 then issues a reply to the ping. 1. The NSP sends the ping reply packet addressed to 155.1.3.4. 2. By normal means, the packet arrives at the router. 3. Because the router has an interface with an address 155.1.3.1 (on 155.1.3 subnet), it ARPs for 155.1.3.4. 4. Because the 8546 DSL card has a host route (marked PA=y) for 155.1.3.4, it responds to the ARP request with its own MAC address (proxy ARP). 5. Then, the ping reply is sent directly to the 8546 DSL card. 6.
Packet Walk-Throughs 5 4 RTU issues reply to ping 1 2 MCC Card Router DCE Manager WS1 135.1.1.1 3 8546 DSL Card 135.1.1.2 135.1.2.1 135.1.3.254 e1a:135.1.2.2 s1b:135.1.3.1 RTU s1b:135.1.3.2 135.1.3.4 Unnumbered Interface 1 2 3 4 5 6 7 8 WS1 pings the RTU MCC Routing Table Host/Net 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.2 135.1.2.
Packet Walk-Throughs The Hotwire RTU then issues a ping reply to IP address 135.1.1.1. 1. The RTU forwards the ping reply to the 8546 DSL card. 2. The 8546 DSL card consults its routing table to identify how to forward the reply. Route #2 is used because the destination address (135.1.1.1) is the 135.1.1 subnet. Therefore, the next-hop address is the MCC card’s s1b interface (135.1.3.1). 3. Similarly, upon receiving the packet, the MCC card consults its routing table to identify how to forward the packet.
Packet Walk-Throughs This page intentionally left blank.
Network Configuration Worksheets A Overview This appendix summarizes the 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 and 5546 RTUs as follows: Perform this task . . . On this screen . . . To access the screen . . . 1. Assign an IP address to the MCC card. (See page A-3.) Who Am I Power on the Hotwire DSLAM system. 2. Clear NVRAM if the Who Am I screen does not appear in Task 1. (See page A-5.
Network Configuration Worksheets TASK 1: Assign an IP Address to the MCC Card On the Who Am I screen, assign an IP address to the MCC card. 8000-A2-GB21-30 Access the . . . By . . . Who Am I screen Powering on the Hotwire DSLAM system.
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. NOTE: If you enter two consecutive dots (.) in the IP address, the system will interpret this as dot-zero-dot (.0.). 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.
Network Configuration Worksheets 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. 8000-A2-GB21-30 Access the . . . By . . .
Network Configuration Worksheets TASK 3: Assign an IP Address to the Backplane (s1b) On the IP Network screen, assign an IP address to the backplane (s1b). NOTE: 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 are not included in the network. Also, if you enter two consecutive dots (.) in the IP address, the system will interpret this as dot-zero-dot (.0.). Access the .
Network Configuration Worksheets 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. NOTE: If you enter two consecutive dots (.) in the IP address, the system will interpret this as dot-zero-dot (.0.). 8000-A2-GB21-30 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. DSL Card Subnet Mask = (Read-only in future release.) This must be the same as 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.
Network Configuration Worksheets 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 . . . 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 50 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= 50 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 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 → 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 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 . . . 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): A-12 1.
Network Configuration Worksheets IP Network Screen A-C-B Prompt Your Configuration Setting For DSL port 2 (s1d): 1. Enter the interface name at the Input Interface Name: prompt. IP Interface = s1d 2. Enter the port 2 5446 RTU’s IP address or the IP address of the router connected to the 5546 RTU at the (nnn) prompt. Peer IP Address = 3. Enter route type HOST at the Route to peer (host/net): prompt. Route to Peer= HOST For DSL port 3 (s1e): 1.
Network Configuration Worksheets TASK 8: Create a Static Route to an NMS 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. A-14 Access the . . . By . . . Static Routes screen Selecting Configuration → IP Router → Static Routes from the Hotwire – DSL menu.
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. 1) Host/Net = 2) Host/Net = 3) Host/Net = 4) Host/Net = 5) Host/Net = 6) Host/Net = 7) Host/Net = 8) Host/Net = 9) Host/Net = 10) Host/Net = 11) Host/Net = 12) Host/Net = 3. Do one of the following at the Subnet:(nnn.nnn.
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 . . . On this screen . . . To access the screen . . . 1. Assign IP addresses to the DSL card LAN interface (e1a). (See page A-17.) (Hotwire – DSL) IP Network From the Hotwire – DSL menu, select: Configuration → Interfaces → IP Network 2. Reset the DSL card.
Network Configuration Worksheets 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. 8000-A2-GB21-30 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 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.
Network Configuration Worksheets TASK 3: 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; four domains per port). Access the . . . By . . . Static Routes screen Selecting Configuration → IP Router → Static Routes from the Hotwire – DSL menu.
Network Configuration Worksheets Static Routes Screen A-E-A Prompt Your Configuration Setting 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. Subnet Mask = 4. Enter the IP address of the next hop at the Next Hop IP Address (nnn.nnn.nnn.nnn): prompt. Next Hop = 5.
Network Configuration Worksheets TASK 4: Select RTU Type On the RTU Selection screen, select the RTU type. Access the . . . By . . . Selection screen Selecting Configuration → RTU → Selection from the Hotwire – DSL menu. RTU Selection Screen A-H-A Prompt Your Configuration Setting 1. Enter 1 to 4 at the Port # prompt. Port number = 2. Enter the RTU type of the endpoint. For Model 8540: For Model 8540, selections are 5170, 5171, 5246, or 5216.
Network Configuration Worksheets RTU Selection Screen Prompt A-H-A Your Configuration Setting 6. Model number, serial number, firmware revision, hardware revision, and CAP release fields will appear. These fields are read only. 7. When the system highlights Save Changes?, enter yes at the yes/no: prompt.
Network Configuration Worksheets TASK 5: Configure RTU Information On the RTU Information screen, configure RTU information only if the RTU type is 5446r1 or 5446r2.. Access the . . . By . . . Configuration screen Selecting Configuration → RTU → Configuration from the Hotwire – DSL menu. RTU Configuration Screen A-24 A-H-B Prompt Your Configuration Setting 1. Enter the interface name at the DSL Interface Name (s1a, s1d, s1e, or s1f): prompt. Interface name = 2.
Network Configuration Worksheets RTU Configuration Screen A-H-B Prompt Your Configuration Setting 6. Enter the Destination Interface name at the Destination Interface: (DSL/Ether): prompt. Destination Interface Name = 7. When the system highlights Save Changes?, enter yes at the yes/no: prompt.
Network Configuration Worksheets TASK 6: Add or remove a static route to the RTU On the RTU Static Routes screen, add and remove static routes to the RTU. Access the . . . By . . . Configuration screen Selecting Configuration → RTU → Static Routes from the Hotwire – DSL menu. RTU Static Routes Screen A-26 A-H-C Prompt Your Configuration Setting 1. Enter the interface name at the DSL Interface Name (s1a, s1d, s1e, or s1f): prompt. Interface name = 2.
Network Configuration Worksheets RTU Static Routes Screen A-H-C Prompt Your Configuration Setting 4. Do one of the following at the at the DSLAM yes/no: prompt. – Enter yes to automatically create the corresponding DSLAM route for the end system. – Enter no to not automatically create the corresponding DSLAM route for the end-system. DSLAM = Yes 5. When the system highlights Save Changes?, enter yes at the yes/no: prompt.
Network Configuration Worksheets TASK 7: 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 by a DHCP server. If you are assigning addresses statically, make sure you have completed the worksheets for Task 3: Create a Default or Source Route. On the Domain Names screen, assign a domain name to each service domain IP address.
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. Search for the domain name you want to configure for dynamic IP addressing. Remember the number (1–16) for the specific domain name you want to configure.
Network Configuration Worksheets A-30 April 1998 8000-A2-GB21-30
Network Configuration Worksheets 8000-A2-GB21-30 April 1998 A-31
Network Configuration Worksheets Servers 1- 4, 5-8, 9-12, and 13-16 screens A-G-B, A-G-C, A-G-D, or A-G-E Prompt Your Configuration Setting 1. Enter the IP addresses (nnn.nnn.nnn.nnn) of the DHCP servers for this domain. NOTE: If you do not enter a value in these fields (i.e., the field is null), then all DHCP requests (with domain name information) from this NSP domain’s end users will be dropped. DHCP Server = 2. (Optional) Enter the IP addresses Authen Server = (nnn.nnn.nnn.
Network Configuration Worksheets Servers 1- 4, 5-8, 9-12, and 13-16 screens 8000-A2-GB21-30 A-G-B, A-G-C, A-G-D, or A-G-E Prompt Your Configuration Setting 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. Dynamic access control security = 8.
Network Configuration Worksheets This page intentionally left blank.
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: 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).
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.
IP Filtering Configuration Worksheets Access the . . . By . . . IP Filter Configuration screen Entering the line number of the desired filter name on the Filters Table screen (see page B-3). IP Filter Configuration Prompt A-E-C Your Configuration Setting 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.
IP Filtering Configuration Worksheets IP Filter Configuration Prompt A-E-C Your Configuration Setting 3. Enter the name of the filter for which Filter Name = 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. – For the DSL port #3 interface, enter dsl3.
IP Filtering Configuration Worksheets IP Filter Configuration A-E-C Prompt Your Configuration Setting 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 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 NOTE: Remember, if you are using the filtering): prompt.
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. 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. All traps will go to the specified port. – At the Enable/Disable: prompt, indicate whether or not you want to enable or disable the generation of traps.
SNMP Configuration Worksheets 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). H If address security is to be activated, it should be activated on the MCC and all DSL cards. H 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. Access the . . . By . . .
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. SNMP Security Prompt Your Configuration Setting 1.
Glossary 10BaseT A 10-Mbps Ethernet LAN that works on twisted-pair wiring. address A symbol (usually numeric) that identifies the interface attached to a network. ARP Address Resolution Protocol. Part of the TCP/IP suite, ARP dynamically links an IP address with a physical hardware address. authentication server An authentication server can either be a RADIUS server or an XTACACS server and can be used to confirm an end-user system’s access location.
Glossary e1a Name of the DSL card’s and MCC card’s 10BaseT (Ethernet) interface. Ethernet A type of network that supports high-speed communication among systems. It is a widely-implemented standard for LANs. All hosts are connected to a coaxial cable where they contend for network access using a Carrier Sense, Multiple Access with Collision Detection (CSMA/CD) paradigm. Ethernet address A six-part hexadecimal number in which a colon separates each part (for example, 8:0:20:1:2f:0).
Glossary NSP Network Service Provider. A local telephone company or ISP that provides network services to subscribers. packet A group of control and data characters that are switched as a unit within a communications network. PING An IP-based application used to test reachability of destinations by sending an ICMP echo request and waiting for a reply. The ping program is supported from both the DSL and MCC cards. POTS Plain Old Telephone Service.
Glossary terminal emulation Software that allows a PC to mimic the signals of a specific type of terminal, such as a VT100 or 3270, to communicate with a device requiring that terminal interface. TFTP Trivial File Transfer Protocol. A standard TCP/IP protocol that allows simple file transfer to and from a remote system without directory or file listing. TFTP is used when FTP is not available. TraceRoute A program that lists the hosts in the path to a specified destination.
Index Numbers B 10BaseT interface on the MCC and DSL cards (e1a), 5-1 5170 RTU, 1-7 5171 Remote PC NIC, 1-8 5216 RTU, 1-8 5246 RTU, 1-8 5446 RTU configuring the management domain IP addresses, A-12 description, 1-10 proxy ARP, 4-6 5546 RTU, 4-6 8600 DSLAM, 1-4 8800 DSLAM, 1-5 binding a filter, B-7 A address allocation schemes host addressing, 5-3 structured subnet addressing, 5-4 Address Resolution Protocol (ARP), 1-15 address types in routing table, 6-2 applications for management ping, 3-2 telnet, 3-
Index D F DCE Manager, 3-1, 8-1 default route, 6-2, A-9, A-20 defining a community, C-2 a filter, B-3 destination-based routing, 6-1 DHCP relay agent, 6-5 directed broadcasts, 2-1 discovering devices on the network, 4-8 discovery, 4-8 document purpose, v summary, vi domain types, 1-16 DSL card assigning IP addresses, A-17 assigning IP addresses to the DSL cards, A-7 description, 1-6 proxy ARP, 4-5 resetting the card, A-19 static route example, 6-4 DSL ports (s1c, s1d, s1e, and s1f) naming convention of p
Index L local host route injection, 6-5 M MAC, 2-1 MAC address, 1-15 management domain assigning an IP address to the MCC card, A-3 assigning IP address to the backplane (s1b), A-6 assigning IP addresses to the DSL cards, A-7 components, 4-7 configuration worksheets, A-2 configuring the 5446 RTU management domain IP addresses, A-12 creating a default route, A-9 creating a static route to the NMS, A-14 discovering devices on the network, 4-8 IP address allocation, 5-8 MCC card proxy ARP, 4-9 packet walk-th
Index resetting the DSL card, A-19 the MCC card, A-11 routing destination-based, 6-1 dynamic routes, 6-5 source-based, 6-10 static routes, 6-2 routing table, 6-1 description, 6-1 types of addresses, 6-2 rule types host address, 7-2 network address, 7-2 socket address, 7-3 S s1b, 5-1, 5-9, A-6 service domain 5446 RTU proxy ARP, 4-6 assigning IP addresses to the DSL card LAN Interface (e1a), A-17 components, 4-1 configuration worksheets, A-16 configuring the DHCP relay agent, A-28 creating a default route o
