HOTWIREr 8540 AND 8546 RADSL CARDS USER’S GUIDE Document No.
Copyright E 2000 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Avenue North, P.
Contents About This Guide H Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . v H Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi 1 Hotwire DSL System Description H What is the Hotwire DSL System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Hotwire DSL Chassis . . . . . . .
Contents 3 RADSL Card Configuration H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 H Port Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 H Configuring the MCC Card, DSL Cards, and RTUs . . . . . . . . . . . . . . . . . . 3-2 H DSL Configuration Card Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 H DSL Configuration Ports Screens . . . . . . . . . . .
Contents A Download Code H Download Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Fully Operational System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Scenario Two: Download Only System . . . . . . . . . . . . . . . . . . . . . . . . . A-2 H Apply Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 B SNMP Traps H Setting Up SNMP Trap Features . . . . . .
Contents This page intentionally left blank.
About This Guide Document Purpose and Intended Audience This guide describes how to configure and operate the software component of the Hotwire Digital Subscriber Line Access Multiplexer (DSLAM) system. Specifically, this document addresses the use of the following cards in the DSLAM: H 8540 Rate Adaptive Digital Subscriber Line (RADSL) card. H 8546 Rate Adaptive Digital Subscriber Line (RADSL) card.
About This Guide Document Summary Section Description Chapter 1 Hotwire DSL System Description. Provides an overview of the Hotwire DSLAM and GranDSLAM systems. Chapter 2 Hotwire Menus and Screens. Describes the operation of Hotwire menus, screens, and commonly used navigation keys. Also provides instructions on how to log in and log out of the system. Chapter 3 RADSL Card Configuration. Describes the optional procedures for configuring the DSL cards on the Hotwire system.
About This Guide Document Number Document Title 7700-A2-GB23 OpenLane DCE Manager for HP OpenView for Windows User’s Guide 7800-A2-GB26 OpenLane DCE Manager User’s Guide 7800-A2-GB28 OpenLane Performance Wizard User’s Guide 8000-A2-GB21 Hotwire 8540 and 8546 RADSL Cards Network Configuration Guide 8000-A2-GB25 Hotwire 8100/8200 Interworking Packet Concentrator (IPC) Network Configuration Guide 8000-A2-GB29 Hotwire Management Communications Controller (MCC) Card User’s Guide 8000-A2-GB90 Hotw
About This Guide This page intentionally left blank.
Hotwire DSL System Description 1 What is the Hotwire DSL System? The Hotwirer Digital Subscriber Line (DSL) system is a set of central site products that terminate and consolidate packet data traffic from many customers in a serving area. The DSL card(s) then forwards the traffic to one or more network access provider networks. High-speed Internet and intranet access is bridged on the DSL port cards and multiplexed over backbone networks.
Hotwire DSL System Description The following illustration shows a typical Hotwire configuration.
Hotwire DSL System Description Hotwire DSL Chassis There are four types of chassis: 1 A .. ALM RADSL 8546 RADSL 8546 8000 3 2 1 4 PO RT MCC 3 2 1 4 ol X D SL X ol C R 3 2 1 LINE LAN/WAN SLOT B A STACK POSITION B PO RT C R ol C X D SL TX ET H ER N ET R TX ET H ER N ET . . MANAGEMENT PWR FAN 4 5 6 3 2 48VDC CLASS 2 OR LIMITED PWR SOURCE ET H ER N ET K Alr m Te st DC FUSES T4A, MIN.
Hotwire DSL System Description 1-4 H The Hotwire 8800 DSLAM chassis is a 20-slot chassis designed to house up to 18 4-port DSL cards and one MCC card. (The remaining slot is reserved for the future use of a redundant MCC card.) For more information, see the Hotwire 8800 Digital Subscriber Line Access Multiplexer (DSLAM) Installation Guide. H The Hotwire 8810 DSLAM chassis is a higher density carrier, for use with future high-density port cards, as well as lower density cards (4 ports or less).
Hotwire DSL System Description H The Hotwire 8820 GranDSLAM is a 20-slot chassis with integral power, alarm, cooling, and interface subsystems designed to house up to 17 DSL cards, as well as an SCM card for aggregating DSL traffic to an ATM uplink and an MCP card. Layer 3 systems do not use SCM card functionality. Also for Layer 3 systems, the 8820 GranDSLAM houses 8546 cards only, not 8540 cards. For more information, see the Hotwire GranDSLAM Installation Guide.
Hotwire DSL System Description MCC Card The DSLAM and GranDSLAM chassis require one MCC card, which is a processor card that administers and provides management connectivity to the DSL cards. It acts as a mid-level manager and works in conjunction with a Simple Network Management Protocol (SNMP) system, such as Paradyne’s OpenLanet DCE Manager for HP OpenView, via its LAN port. It gathers operational status for each of the DSL cards and responds to the SNMP requests.
Hotwire DSL System Description Features The Hotwire DSL system provides the following features: H High-speed Internet or intranet access. H Rate Adaptive Digital Subscriber Line ports. H Subscriber authentication, security access, and permission features that prevent users from accessing unauthorized services. H Status polling, alarm indicators and logging, diagnostics, and performance capabilities.
Hotwire DSL System Description Configuring the DSL Cards The Hotwire DSL software provides DSL configuration options to: H Configure the DSL cards and RTU connectivity H Configure the interfaces and ports H Set up user accounts H Upload or download a copy of a card’s configuration data to or from a Trivial File Transfer Protocol (TFTP) server H Download a new version of the DSL and RTU software H Define an IP routing table H Define and enable filters to prevent unauthorized network access H
Hotwire DSL System Description Troubleshooting and Diagnostics The Hotwire DSL system provides DSL diagnostic submenu options that: H Perform PING tests and display results H Perform a BERT test H Display selftest results for CPU, memories, and ports H Show major alarms such as Selftest Failure, Processor Failure, and DSL or Ethernet port failure H Show minor alarms such as Config Error and thresholds exceeded for DSL Margin and Error Rate or Link Down events H Perform a trace route to an IP add
Hotwire DSL System Description 1-10 April 2000 8000-A2-GB20-50
Hotwire Menus and Screens 2 Menu and Screen Formats The Hotwire DSL System has an ASCII-based menu- and screen-driven user interface system that enables the user to configure and monitor the Hotwire cards. This section describes the components of a typical Hotwire menu and screen.
Hotwire Menus and Screens Components of a Hotwire Menu A typical Hotwire menu format is shown below: 1 2 3 1. Menu Title is the top line of the menu window that displays the title of the menu or submenu. 2. Menu List is the portion of the menu window that displays the list of menu options. When selected, a menu option displays a submenu window or screen. 3. Letter Navigation Keys are provided within a menu list. These keys provide a convenient way (shortcut) to select a menu item.
Hotwire Menus and Screens Components of a Hotwire Screen A typical Hotwire screen looks like this: 1 2 3 4 1. System Header Line is the top line of the screen. This line has two fields that provide system login information. — The first field displays the chassis name or the individual card name. (Access the System Information screen by selecting the appropriate card in the chassis and then follow this menu sequence: Configuration → Card Status → Card Info.
Hotwire Menus and Screens 4. Status Line is the last line on the screen. This line displays status information about the selected card. For example, in the above illustration, the following line is displayed: Hotwire 8610: DSL01: 8546: __ M __ D XXXX The first field indicates the chassis type. In this case, the system in use is the Hotwire 8610 DSLAM system. The second field indicates the card selected. In this example, the DSL01 card is selected.
Hotwire Menus and Screens Levels of Access There are two levels of privileges on the Hotwire DSL system. Your user accounts can be configured with a user name, password, and privilege of: H Administrator. The Administrator has complete read/write access to the DSL system. With Administrator permission, you can set specific parameters and variables to configure cards, ports, interfaces, and endpoint selection. H Operator.
Hotwire Menus and Screens User Login Screen You can log in to the Hotwire DSL system using either a local VT100- compatible terminal or a remote Telnet connection. However, each card in the Hotwire DSL system accepts only one login session at a time. NOTE: The User Login screen only appears if one or more users have been defined on the MCC. At the User Login screen, enter your login ID and password. You must wait until your login is verified, anywhere from two seconds to 12 minutes.
Hotwire Menus and Screens Hotwire Menu Hierarchy This section describes the menu structure of the Hotwire user interface. Hotwire Chassis Main Menu The following illustration shows the Hotwire Chassis Main Menu. Hotwire Chassis A. Chassis Info B. Card Selection C. Logout 97-15566-01 From the Hotwire Chassis Main Menu, you can select: H A. Chassis Info to enter or display chassis information, such as the chassis name, name of person responsible for the system, and physical location of the chassis.
Hotwire Menus and Screens Hotwire – DSL Menu After selecting a specific DSL card from the Card Selection screen, the DSL system displays the Hotwire – DSL Menu. Hotwire – DSL A. Configuration* B. Monitoring C. Applications D. Diagnostics E. Exit See Configuration Menu Below* See Monitoring Menu Below Applications A. Ping B. Trace Route * The Configuration menu item appears only if you have Administrator permission. Diagnostics A. Selftest B. Alarms C. Packet Echo D.
Hotwire Menus and Screens DSL Card Configuration Menu The following figure illustrates the complete Configuration menu hierarchy from the Hotwire – DSL menu. Configuration A. Card Status B. Ports C. Interfaces D. Users1 E. IP Router F. SNMP G. DHCP Relay H. RTU (B) Ports A. Ethernet Port B. DSL Ports (A) Card Status A. Card Info B. DNS Setup C. Time/Date D. NVRAM Clear E. NVRAM Cfg Loader F. Card Reset G. Download Code (D) Users A. Accounts (C) Interfaces A. General B. IP Network C Control D.
Hotwire Menus and Screens DSL Card Monitoring Menu The following figure illustrates the complete Monitoring menu hierarchy from the Hotwire – DSL menu. Monitoring A. Card Status B. Physical Layer C. Interfaces D. Network Protocol E. IP Router F. RTU (A) Card/CPE Status A. Card Info B. Login History C. Syslog (C) Interfaces A. Active List B. Status (B) Physical Layer A. Active List B. Ether Statistics C. HDLC Bus Stats D. DSL Link Perf E. DSL Perf Stats F. DSL Error Stats G.
Hotwire Menus and Screens Card Selection Screen From the Hotwire Chassis Main Menu, select Card Selection to display the status of any of the 18 DSL cards installed in the 8800/8810 chassis (or 17 DSL cards installed in the 8820 GranDSLAM chassis) by type and slot number. The Card Selection screen also displays general and interface status for each card. NOTE: The Card Selection screen for the Hotwire 8600/8610 chassis displays the same information, but the slot order is different.
Hotwire Menus and Screens The status of each DSL card is indicated by codes being displayed in any of eight positions to the right of the card selected. NOTE: If an option is not active, an underscore is shown in its place. Column Heading Position Slt M = MCC, MCP or MCC Plus card 1–18 = slot number for DSL card Mdl # First four digits of the card model number: 8540 = 8540 RADSL card 8546 = 8546 RADSL card 8000 = MCC/MCP/MCC Plus card Stat 1 T or _ Test mode.
Hotwire Menus and Screens Accessing the Hotwire – DSL Menu " Procedure To access the Hotwire – DSL menu: 1. From the Hotwire Chassis Main Menu, select Card Selection. The Card Selection screen appears. 2. Verify that the DSL card you want to access appears on the Card Selection screen. (See Card Selection Screen on page 2-11 for more information.) 3. At the Goto Card (MCC or DSLnn): prompt, type the number of the slot. Then, press Enter.
Hotwire Menus and Screens This page intentionally left blank.
RADSL Card Configuration 3 Overview This chapter describes configuration options on the 8540/8546 RADSL cards. Use these options to customize your applications. For information on customizing the MCC card, see the Hotwire Management Communications Controller (MCC) Card User’s Guide. NOTE: Certain parameters such as speeds are dependent on the settings on the RTU Configuration screen.
RADSL Card Configuration Configuring the MCC Card, DSL Cards, and RTUs Use the procedures in the following order to configure the MCC card and RADSL cards for the basic setup for terminal management and user data connectivity. NOTE: It is assumed that you have read the Hotwire 8540 and 8546 RADSL Cards Network Configuration Guide and have assigned service and management domain IP addresses for all devices (MCC, DSL, and RTUs).
RADSL Card Configuration The following illustrates the management domain components that must be configured and examples of the various naming conventions for the 8546 card. Tasks refer to those listed in the table on page 3-2. MANAGEMENT DOMAIN DCE Manager Server IP Address 10BT DCE Manager Router b1: 135.1.3.254/ 255.255.255.0 b2: 135.1.2.1/ 255.255.255.0 Port Names DSLAM RTU* a: 135.1.3.3/ 255.255.255.255 e1a: 135.1.2.2/ 255.255.255.0 MCC Card s1b: 135.1.3.1/ 255.255.255.
RADSL Card Configuration The following illustrates the management domain components that must be configured and examples of the various naming conventions for the 8540 card. Tasks refer to those listed in the table on page 3-2. MANAGEMENT DOMAIN DCE Manager Server IP Address 10BT DCE Manager Router b1: 135.1.3.254/ 255.255.255.0 b2: 135.1.2.1/ 255.255.255.0 DSLAM e1a: 135.1.2.2/ 255.255.255.0 MCC Card s1b: 135.1.3.1/ 255.255.255.0 Task 2 System Backplane Port Names s1b: 135.1.3.2/ 255.255.255.
RADSL Card Configuration The following illustrates the service domain components that must be configured and examples of the various naming conventions for the 8546 card. Tasks refer to those listed in the table on page 3-2. SERVICE DOMAIN DSLAM RTU* b1: 155.1.3.3/ b2: 156.1.3.3/ b3: 157.1.3.3/ b4: 158.1.3.3/ 255.255.255.0 MCC Card ISP Router a: 155.1.2.1/ 255.255.255.0 b1: 155.1.3.1/24 .. . System Backplane RTU* 8546 RADSL Card b16: 170.1.3.1/ 255.255.255.0 IP Interface e1a: 155.1.3.2/ 156.1.3.2/ .
RADSL Card Configuration The following illustrates the service domain components that must be configured and examples of the various naming conventions for the 8540 card. Tasks refer to those listed in the table on page 3-2. SERVICE DOMAIN DSLAM MCC Card System Backplane ISP Router a: 155.1.2.1/ 255.255.255.0 8540 RADSL Card b1: 155.1.3.1/24 .. . b16: 170.1.3.1/ 255.255.255.0 IP Interface e1a: 155.1.3.2/ 156.1.3.2/ .. . s1c s1d s1e 170.1.3.2/ 255.255.255.
RADSL Card Configuration DSL Configuration Card Status Screens Use the system information submenu of the Card Status screens to configure basic DSL card-level information. NOTE: Only a user who logs on to the Hotwire DSL system with Administrator permission can configure the DSL card. " Procedure To configure card information, DNS setup, time/date, clear NVRAM, upload or download configuration sets, download new firmware, or reset card: 1. Follow this menu sequence: Configuration → Card Status (A-A) 2.
RADSL Card Configuration Table 3-1. Card Status Options (1 of 4) Card Info (System Information) A-A-A Allows you to configure basic card-level information. Card Name – 16 alphanumeric characters. Name assigned to the card. Card Contact – 32 alphanumeric characters. Name or number of party responsible for card. Card Location – 16 alphanumeric characters. Location assigned to the card. Router ID – nnn.nnn.nnn.nnn format. (This field is read-only.) Diagnostic Domain IP address assigned to card by the MCC.
RADSL Card Configuration Table 3-1. Card Status Options (2 of 4) Time/Date A-A-C Gives the user the ability to configure the local time and date on the 8540 RADSL card with network time and to synchronize the DSL system’s clock via a Network Time Protocol (NTP) server. On the 8546 card, displays the time zone, local time, and date on the DSL card as received from the MCC card. NOTE: At system boot time, the time on the DSL cards automatically synchronizes with the MCC card.
RADSL Card Configuration Table 3-1. Card Status Options (3 of 4) NVRAM Config Loader A-A-E Provides the ability to upload or download a copy of the card’s binary configuration data to or from a Trivial File Transfer Protocol (TFTP) server. Configuration File Name –The file name may be a regular path name expression of directory names separated by a forward slash (/) ending with the file name. The total path name length must be less than 40 characters.
RADSL Card Configuration Table 3-1. Card Status Menu Options (4 of 4) Download Code (Download Code and Apply Download) A-A-G Provides the ability to download a new version of code and apply the downloaded code. For further information on this feature, see Appendix A, Download Code. Select Download Code (A) or Apply Download (B). You must exit this screen and use the Apply Download screen. Download Code A Allows code download. This screen is similar to the NVRAM Config Loader screen.
RADSL Card Configuration DSL Configuration Ports Screens Use the system information submenu of the Ports screens to display the DSL Ports screen. " Procedure To configure DSL ports: 1. Follow this menu sequence: Configuration → Ports (A-B) 2. The Ports menu appears. Enter the desired value on each selected screen and field as shown in Table 3-2 and press Enter. Table 3-2. Ports Options (1 of 3) Ethernet Port A-B-A Allows you to configure the Ethernet Port for full or half-duplex mode.
RADSL Card Configuration Table 3-2. Ports Options (2 of 3) DSL Ports (DSL Parameters) A-B-B Allows configuration of the operational and alarm parameters of the DSL ports. Each DSL port is configured separately. Action – Edit to configure the DSL ports. Reset the port to make changes active. Port # – Enter port 1 to 4 (Default = 0). RTU Type – Model number of the service node. For Model 8540, selections are 5246/5216 (Default = 5216). For Model 8546, selections are 5446r1/5446r2 (Default = 5446r2).
RADSL Card Configuration Table 3-2. Ports Options (3 of 3) DSL Ports (DSL Parameters) (cont’d) A-B-B Adaptive: Max Up Speed* – 1088/952/816/680/544/476/408/340/272/204/136/119/102/90.6/85/68/51/45.3/34/11.3 (Default = 1088 kbps). Enter the maximum upstream speed. Thresholds for Trap Messages: Adaptive: Min Dn Speed* – 7168/6272/5120/4480/3200/2688/2560/2240/1920/1600/ 1280/1024/960/896/768/640/512/384/256 or d for Disable (Default = 256). Enter the thresholds to cause traps to occur.
RADSL Card Configuration DSL Configuration Interfaces Screens Use the system information submenu of the Interfaces screens to configure basic interface information. " Procedure To configure interface names and MTU settings, IP addresses on the Ethernet port, PPP settings on the DSL ports, or restart, stop, or monitor an interface: 1. Follow this menu sequence: Configuration → Interfaces (A-C) 2. The Interfaces menu appears.
RADSL Card Configuration Table 3-3. Interfaces Options (2 of 3) IP Network A-C-B Allows you to configure up to 16 IP addresses for a port. Configure one IP address for each service domain on the DSL card. IP Interface – Name of the interface. Enter up to 15 characters. s1b = backplane; e1a = Ethernet port; s1c, s1d, s1e, and s1f = DSL ports. Base IP Addr – nnn.nnn.nnn.nnn format. (This field is read-only.) Base Subnet Mask – nnn.nnn.nnn.nnn format. (This field is read-only.) IP Addr – nnn.nnn.nnn.
RADSL Card Configuration Table 3-3. Interfaces Options (3 of 3) PPP A-C-D Allows configuration of parameters for the PPP links used for the DSL connections. For the 8540, there is no PPP submenu. Interface Name – s1c, s1d, s1e, or s1f. Restart Timer – 1–10000 in seconds (Default = 3). Max Terminates – (Default = 2). Max Configures – Maximum number of PPP links (Default = 10). Max Naks – Maximum number of negative acknowledgments before PPP link goes down (Default = 10).
RADSL Card Configuration DSL Configuration Users Screens Use the system information submenu of the Users screens to configure user login accounts for Telnet sessions directly to the DSL cards. User accounts provide security for the DSL system by requiring that anyone who is trying to log on to the system has a valid password to gain access.
RADSL Card Configuration 5. To verify that a RADSL card account has been set up, go to the MCC card and follow this menu sequence: Applications → Telnet (C-B) See the Hotwire Management Communications Controller (MCC) Card User’s Guide for more information. Table 3-4. Users Options Users* (Configure Account) A-D-A For Model 8540 only. Allows you to add, edit, or delete a user from a system account and to edit user passwords and privileges. Up to 10 active users can be supported.
RADSL Card Configuration DSL Configuration IP Router Screens Use the system information submenu of the IP Router screens to configure static routes to protocols and filters. " Procedure To configure static routes, martian networks, IP router filters, ARP and Host tables: 1. Follow this menu sequence: Configuration → IP Router (A-E) 2. The IP Router menu appears. Enter the desired value on each selected screen and field as shown in Table 3-5 and press Enter.
RADSL Card Configuration The following table lists warnings and error messages displayed on the Static Routes screen (A-E-A). 8000-A2-GB20-50 Message Meaning Routing Table: Route not added Route was saved into NVRAM but not added to the active routing table. Routing Table: Route limit reached for interface Route was saved into NVRAM but not added to the active routing table because there are already 32 routes for the interface.
RADSL Card Configuration Table 3-5. IP Router Options (1 of 4) Static Routes A-E-A Allows you to add or delete static routes in the system. For the management domain, static routes must be provided to the MCC and the RTUs. For the service domain, static routes must be provided upstream to the next hop router and downstream to those hosts that require static routes. Item – Press Enter on 0 field to add entry. You cannot select dynamic routes or routes identified as rmt s1x on the location field.
RADSL Card Configuration Table 3-5. IP Router Options (2 of 4) Martian Networks A-E-B Gives the user the ability to configure addresses that the system recognizes as invalid (addresses from which the RADSL card will not accept routing information). Item – Press Enter on 0 field to add entry, or enter the item number to change an entry. Martian Net ID – nnn.nnn.nnn.nnn format or space to delete entry. Enter IP address of unwanted source. Martian Net Mask – nnn.nnn.nnn.nnn format.
RADSL Card Configuration Table 3-5. IP Router Options (3 of 4) IP Router Filters (IP Filter Configuration) A-E-C Gives the user the ability to build name sets of filter rules. A filter is a rule (or set of rules) that is applied to a specific interface to indicate whether a packet can be forwarded or discarded. You can add, edit, or delete router filter rules within a named set. A filter works by successively applying the rules to the information obtained from the packet header until a match is found.
RADSL Card Configuration Table 3-5. IP Router Options (4 of 4) ARP (Parameters, Add Entry, and Delete Entry) A-E-D (A-E-A to A-E-C) Select: Parameters (A) Gives the user the ability to configure general Address Resolution Protocol (ARP) cache parameters. Complete Entry Timeout (minutes) – 1–200000 (Default = 20). Incomplete Entry Timeout (minutes) – 1–255 (Default = 3). Default Route Entry Timeout (minutes) – 1–20 (Default = 1).
RADSL Card Configuration DSL Configuration SNMP Screens Use the system information submenu of the SNMP screens to configure SNMP security, community names, and trap addresses. " Procedure 1. Follow this menu sequence: Configuration → SNMP (A-F) 2. The SNMP menu appears. Enter the desired value on the selected screen and field as shown in Table 3-6 and press Enter. Management System Source Validation for RADSL Cards " Procedure To set up management System source validation for RADSL cards: 1.
RADSL Card Configuration Table 3-6. SNMP Options Security (SNMP Security) A-F-A Enables you to configure security for the RTU SNMP agent. CAUTION: Endpoint cookies must be kept confidential. Endpoint Cookie – Security string for endpoint. Enter up to eight alphanumeric characters (Default = nosets). This cookie replaces the RTU RW community string when SNMP SET is restricted at the RTU.
RADSL Card Configuration DSL Configuration DHCP Relay Screens Use the system information sub-menu of the DHCP screens to configure ISP names and DHCP Authentication servers. " Procedure 1. Follow this menu sequence: Configuration → DHCP Relay (A-G) 2. The DHCP Relay menu appears. Enter the desired value on the selected screen and field as shown in Table 3-7 and press Enter.
RADSL Card Configuration Configuring DHCP Relay Agent (dynamic addressing) Use this procedure to provide dynamic Service Domain IP address allocation to the end-user systems attached to the DSL RTUs. " Procedure To configure relay agent: 1. Make certain that the Next Hop Router address used in relaying DHCP requests is configured as an e1a address (A-C-B). 2. Select Configuration → DHCP Relay → Domain Names (A-G-A). 3. Enter the ISP domain names in the Domain Name field, and press Enter after each entry.
RADSL Card Configuration Table 3-7. DHCP Relay Options Domain Names A-G-A This screen is used for creating the DHCP Relay agent. The gateway address is used in relaying DHCP requests is configured as an e1a address on the IP Network screen (A-C-B). The interface IP address will be inserted into the Gateway Address field of all DHCP requests before relaying to the associated DHCP server. Interface IP Address – Read-only. ISP Domain Name – Enter the corresponding domain name (32 nonnull characters).
RADSL Card Configuration DSL Configuration RTU Screens Use the system information submenu of the RTU screens to configure RTU information. " Procedure 1. Follow this menu sequence: Configuration → RTU (A-H). 2. The RTU menu appears. Enter the desired value on the selected screen and field as shown in Table 3-8 and press Enter.
RADSL Card Configuration Table 3-8. RTU Options RTU Selection A-H-A Displays RTU information such as RTU type, system, location, contact, model number, serial number, version of firmware, and version of hardware. Port # – Enter the RTU port number. RTU Type – Model number of endpoint. For Model 8540, possible endpoints are 5246/5216. For Model 8546, possible endpoints are 5446r1/5446r2. System Name – 16 alphanumeric characters. Name assigned to the RTU. System Contact – 32 alphanumeric characters.
Monitoring the Hotwire DSL System 4 Overview The Hotwire DSL system lets you to monitor the activity of the Hotwire DSL cards. When you select Monitoring from the Hotwire DSL Main Menu, a menu tree of selections on history and error logs, performance statistics, card status, and physical and logical interface status information is presented. Most of the Monitoring screens are read only; that is, the information displayed is to help you gather pertinent information and isolate potential problem areas.
Monitoring the Hotwire DSL System DSL Monitoring Card Status Screens Use the system information submenu of the Card Status screens to display read-only system information. " Procedure To view general card information, login history, and the syslog: 1. Follow this menu sequence: Monitoring → Card Status (B-A) 2. The Card Status menu appears. Select the submenu option as shown in Table 4-1 and press Enter.
Monitoring the Hotwire DSL System Table 4-1. Card Status Options Card Info (General Card Information) B-A-A Displays card information such as system name, location and contact, system up time, available buffers, instruction RAM size, buffer RAM size, fast data RAM size, card type, model and serial number, and firmware, CAP, and hardware release number. Card Name – Name assigned to the card. Card Location – Physical location of the system.
Monitoring the Hotwire DSL System DSL Monitoring Physical Layer Screens Use the system information submenu of the Physical Layer screens to display read-only system information about physical ports. " Procedure To view the active ports list, Ethernet statistics, and HDLC bus statistics: 1. Follow this menu sequence: Monitoring → Physical Layer (B-B) 2. The Physical Layer menu appears. Select the submenu option as shown in Table 4-2 and press Enter.
Monitoring the Hotwire DSL System Table 4-2. Physical Layer Options (1 of 5) Active List (Active Ports List) B-B-A Displays a list of the current status of all the active ports (e1a = Ethernet; s1b = backplane; s1c, s1d, s1e, and s1f = DSL cards) in the card such as the port number, port name, port type, MAC address, and status of the port (in use or disconnected). Num – SNMP ID number. Name – System name. Description – Type of port. MAC Address – MAC address of the active port.
Monitoring the Hotwire DSL System Table 4-2. Physical Layer Options (2 of 5) Ether Statistics (Ethernet Statistics) (continued) B-B-B Bytes Transmitted – Number of bytes transmitted on the Ethernet port. Packets Transmitted – Number of packets transmitted by the Ethernet port and what type. H Multicasts – Single packets copied to a specific subset of network addresses. H Broadcasts – Messages sent to all network destinations. H Flooded – Information received, then sent out to each of the interfaces.
Monitoring the Hotwire DSL System Table 4-2. Physical Layer Options (3 of 5) DSL Link Perf (DSL Link Performance Summary) B-B-D Displays a summary of the link performance for each of the DSL ports. Tells you the number of times the link has been down and the elapsed time the link has been up.
Monitoring the Hotwire DSL System Table 4-2. Physical Layer Options (4 of 5) DSL Perf Stats (DSL Performance Stats) B-B-E Displays the link performance for each of the DSL ports. Tells you the number of times the link has been down and the elapsed time the link has been up.
Monitoring the Hotwire DSL System Table 4-2. Physical Layer Options (5 of 5) DSL Error Stats B-B-F Displays the error performance (margin) rates for each of the DSL ports after selecting a specific DSL port number. Margin is a measure of performance.
Monitoring the Hotwire DSL System DSL Monitoring Interfaces Screens Use the system submenu information of the Interfaces screens to display read-only system information about interfaces. " Procedure To view the active interfaces list, and interface status list: 1. Follow this menu sequence: Monitoring → Interfaces (B-C) 2. The Monitor Interfaces menu appears. Select the submenu option as shown in Table 4-3 and press Enter.
Monitoring the Hotwire DSL System Table 4-3. Monitor Interfaces Options Active List (Active Interfaces List) B-C-A Displays a list of the current status of all of the active interfaces in the card. if – Number of the interface. name – Name of the interface. type – Interface type (static). link – Name of the protocol on the interface. state – Current state of the interface. ll-state – Not applicable. port – Port linked to this interface.
Monitoring the Hotwire DSL System DSL Network Protocol Screens Use the system submenu information of the Network Protocol screens to display read-only system information. " Procedure To view socket statistics, UDCP statistics, TCP data and connection statistics, IP statistics, ICMP statistics, SNMP statistics, and HDLC statistics: 1. Follow this menu sequence: Monitoring → Network Protocol (B-D) 2. The Network Protocol menu appears. Select the submenu option as shown in Table 4-4 and press Enter.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (1 of 7) Socket Statistics B-D-A Displays information on the active sockets. Enter the socket name from the active socket list to view information on the application assigned to the specified socket number. Start Socket – Enter the socket number to start the active socket list. Active Socket List – This is the heading information for the following fields. It lists all the information about the currently selected socket.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (2 of 7) TCP Data Stats (TCP Data Statistics) B-D-C Displays a summary of the Transmission Control Protocol (TCP) data activity (packets and bytes transmitted and received) on all interfaces on the RADSL card. The left column is for received data and the right column is for transmitted data. The counters increment in real time and you may press Ctrl-r at any time to reset the counters.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (3 of 7) TCP Connection Statistics B-D-C Displays a summary of the TCP connection activity on all interfaces on the card. Connection Requests – Number of TCP connections initiated by a process on this card. Connection Accepts – Number of TCP connections accepted by this card. Connections Established – Number of connections established. Connections closed/dropped – Number of connections closed (normally) including those dropped.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (4 of 7) ICMP Statistics (ICMP Packet Statistics) B-D-E Displays a summary of the Internet Control Message Protocol (ICMP) activity on the backplane that terminates on the DSL card, such as echo replies. The columns show output and input packet counts. The counters increment in real time and you may press Ctrl-r at any time to reset the counters. Press Enter to see more ICMP statistics.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (5 of 7) SNMP Statistics B-D-F Displays information on SNMP statistics such as number of set packets, number of get requests, and parsing errors. When you press Enter, the SNMP Authentication Statistics screen is displayed, giving you additional Community Administration information. The counters increment in real time and you may press Ctrl-r at any time to reset the counters.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (6 of 7) SNMP Authentication Statistics (continuation of previous screen) B-D-F The SNMP Authentication Statistics screen displays the following information: Community Administration – Number of SNMP PDUs with community based authentication. Bad Versions – Total number of SNMP messages delivered to the SNMP agent for an unsupported SNMP version.
Monitoring the Hotwire DSL System Table 4-4. Network Protocol Options (7 of 7) PPP Stats (General) B-D-H (A) Displays a summary of the PPP activity on a selected interface on the card. Interface Name – Enter the name of the desired DSL interface (s1c, s1d, s1e, s1f). Link Phase – Current phase/state of this link (Init, Link Control). Octets Transmitted – Number of octets (8 bit bytes) transmitted. Octets Received – Number of octets received.
Monitoring the Hotwire DSL System DSL IP Router Screens Use the system submenu information of the IP Router screens to display read-only system information. " Procedure To view routing and ARP tables: 1. Follow this menu sequence: Monitoring → IP Router (B-E) 2. The IP Router menu appears. Select the submenu option as shown in Table 4-5 and press Enter.
Monitoring the Hotwire DSL System Table 4-5. IP Router Options (1 of 2) Routing Table B-E-A Displays information and statistics stored in the IP routing table. Note that routes will appear only for interfaces that are up. The information and statistics are listed by route and destination number. To display information for a specific destination, enter the destination IP address at the [Destination # or ]: prompt.
Monitoring the Hotwire DSL System Table 4-5. IP Router Options (2 of 2) ARP Table B-E-B Displays the current Address Resolution Protocol (ARP) cache. Permanent entries show PERM PUB PROX. (See Flags.) Line – Sequential number of line. IP Address – Internet Protocol Address. Ethernet Address – Ethernet address associated with the IP address. (An incomplete can be shown in this column for some internal entries such as the backplane.) Min – Number of minutes since this entry was last used.
Monitoring the Hotwire DSL System DSL Configuration RTU Screens Use the system information submenu of the RTU screens to display read-only RTU information. " Procedure 1. Follow this menu sequence: Monitoring → RTU (B-F) 2. The RTU menu appears. Select the submenu option as shown in Table 4-6 and press Enter. NOTE: For Model 8540, only menu items Information (B-F-A) and Static Routes (B-F-B) appear.
Monitoring the Hotwire DSL System Table 4-6. RTU Options RTU Information B-F-A Displays RTU information such as RTU type, system, location, and contact, model number, serial number, version of firmware, and version of hardware. Port # – Enter the RTU port number. RTU Type – Model number of endpoint. For Model 8540, possible endpoints are 5246/5216. For Model 8546, possible endpoints are 5446r1/5446r2). System Name – Name assigned to the RTU.
Diagnostics and Troubleshooting 5 Overview Diagnostics for the system are available through the following: H Applications menu (C) – For a Ping or TraceRoute. H Diagnostics menu (D) – To display the results of a selftest or alarm conditions, and to conduct a nondisruptive packet test. H SYSLOG (B-A-C) – To display SYSLOG messages. Applications Screens Use the Applications submenu to perform a Ping or TraceRoute.
Diagnostics and Troubleshooting " Procedure To use the Ping or TraceRoute function: 1. Follow these menu sequences: Applications → Ping (C-A) Applications → TraceRoute (C-B) 2. Select Applications from the Hotwire DSL main menu. 3. The Applications menu appears. Select the submenu option and enter the desired value on each screen and field as shown on Table 5-1 and press Enter. Table 5-1.
Diagnostics and Troubleshooting Diagnostic Screens Use the Diagnostics submenu to perform selftests or view alarm status. " Procedure To view selftest, card alarm, and packet test information: 1. Follow these menu sequences: Diagnostics → Selftest (D-A) Diagnostics → Alarms (D-B) Diagnostics → Packet Echo Test (D-C) 2. The Diagnostics menu appears. Select the submenu option and enter the desired value on each screen and field as shown in Table 5-2 and press Enter.
Diagnostics and Troubleshooting Table 5-2. Diagnostics Options Selftest D-A Displays the results of the last disruptive selftest of the DSL card. This selftest is only performed on power up of the system or a reset of the card. Each subsystem (processors, memory, and interfaces) reports pass or fail. If all subsystems pass, the card has passed selftest. If a subsystem fails, reset or replace the card.
Diagnostics and Troubleshooting Troubleshooting The status of each card in the Hotwire DSL chassis is indicated on the Card Selection screen (see Chapter 2, Hotwire Menus and Screens). Choose Card Selection from the Hotwire Chassis Main Menu. Checking Alarms If the Card Selection screen indicates that a Major or Minor Alarm is on a card, follow the menu sequence Diagnostics → Alarms (D-B) to determine the cause of the alarm.
Diagnostics and Troubleshooting Table 5-3. Major Alarms (2 of 2) Failure Type Action Ethernet port 1. Check cable connections to the DSL chassis. failure – If cables are terminated properly, go to Step 2. – If cables are not terminated properly, terminate them correctly. 2. Check cable connections to the hub or Ethernet switch. – If cables are terminated properly, go to Step 3. – If cables are not terminated properly, terminate them correctly. 3.
Diagnostics and Troubleshooting Minor Alarms Use Table 5-4 to determine the appropriate action to take for each Minor Alarm. Table 5-4. Minor Alarms (1 of 2) Failure Type Action Config Error: 1. Check the Selftest Results display by following the menu sequence: Diagnostics → Selftest. 2. Do another Selftest (Reset) and check results. – If the results are normal, the problem was transient. Log the results. – If Selftest results still show configuration corruption, there is a card problem.
Diagnostics and Troubleshooting Table 5-4. Minor Alarms (2 of 2) Failure Type Action Error Rate Threshold (A trap message sent if the Block Error Rate averaged over a period of time exceeds the selected value.) H If the Error Rate Threshold is < 10-4, then this alarm is a warning Link Down Threshold (A trap message sent if the number of DSL link down events in 15 minutes exceeds the selected value.) H If the threshold is set low (1– 4), and the link is currently down, then that the loop has degraded.
Diagnostics and Troubleshooting SYSLOG Messages The SYSLOG contains an historical list of special system messages which serves as a log of certain significant events that occur in the DSL network. SYSLOG messages consist of a date and timestamp, followed by the message. To view SYSLOG messages, access the SYSLOG menu entry (B-A-C). Example SYSLOG Messages Interpreting SYSLOG messages sometimes involves viewing a series of messages to determine the problem.
Diagnostics and Troubleshooting Example 3. System Status Message The following SYSLOG message have been received: Fri Apr 9 11:13:15 1999 Link Transition Threshold Exceeded, port DSL2 Meaning: The number of DSL retrains (transitions) has exceeded the Link Down Count configured on the DSL Parameters screen (A-B-B). This is checked every 15 minutes when the current 15-minute bucket is shifted to the previous 15-minute bucket. There will never be more than one SYSLOG message for each 15-minute period.
Diagnostics and Troubleshooting Network Problems Review Table 5-5 for symptoms and possible solutions to help in solving any network problems you may encounter in the Hotwire DSL system. Table 5-5. Network Problems (1 of 3) Problem Action Cannot When you add, change, or delete addresses on a DSL card, you must communicate restart that interface (see Configuration → Interfaces (A-C) in with Ethernet or Chapter 3, RADSL Card Configuration).
Diagnostics and Troubleshooting Table 5-5. Network Problems (2 of 3) Problem Action Cannot Ping or Telnet after entering IP address. 1. Restart the interface (see Configuration → Interfaces (A-C) in Chapter 3, RADSL Card Configuration). 2. Reset or power cycle before the IP address changes take effect. 3. Check to see if you entered the correct IP address (see Who Am I screen in the Hotwire Management Communications Controller User’s Guide). 4.
Diagnostics and Troubleshooting Table 5-5. Network Problems (3 of 3) Problem Action Intranetworking communication problems. 1. Verify that the internetworking network cables meet IEEE standards for local Ethernet networks. 2. Check cable connections to DSL chassis and other devices in the network. 3. Determine whether or not your system is the only one in the network with a problem. Performance is slow. 1.
Diagnostics and Troubleshooting 5-14 April 2000 8000-A2-GB20-50
Download Code A The Hotwire DSL system’s Download Code menu option gives you the ability to upgrade your software with a new version of code and then apply this code to your system. NOTE: Before attempting a download, verify that you can Ping or Telnet to the TFTP server. If you cannot, do not proceed with the download. Also, make certain that the files that you are going to download from exist in the system. New firmware releases are typically applied to either the MCC or RADSL cards in your system.
Download Code Download Code When you are attempting to download to the RADSL cards, refer to Table 3-1, Card Status Options, in Chapter 3, RADSL Card Configuration. In general, the following describes what to expect when you have initiated a download from the configuration menu. From the DSL Configuration Main Menu, select: Configuration → Card Status → Download Code (A-A-G). This selection brings you to the Download submenu. Select Download Code (A).
SNMP Traps B Traps are configured via a Telnet or terminal session. The addition or removal of a card or another hardware component within the Hotwire DSL system causes a trap to be generated. These traps indicate a configuration change notification (CCN) of a card (a hardware replacement or a software upgrade). Setting Up SNMP Trap Features Use the following procedures for setting up SNMP trap features.
SNMP Traps Enable DSL Port Traps " Procedure To enable DSL Port Traps: 1. Follow this menu sequence from the DSL Main Menu: Configuration → Ports → DSL Ports (A-B-B) 2. Select a DSL port. 3. If desired, enter a value for the following:. — Margin Threshold — Link Down Count Threshold — Error Rate (minute) Threshold. — Error Rate (hour) Threshold. See Table 3-2, Port Options, in Chapter 3, RADSL Card Configuration, for more information. 4. Reset the port following this menu sequence:.
SNMP Traps DSL Card Traps The DSL card sends the following traps. Table B-1. DSL Card Traps (1 of 4) Event Severity Comment Trap # MIB Authentication failure minor SNMP community string. 4 MIBII (RFC 1213) Telnet passwords. This trap may be overloaded for Telnet based authentication failures. In these cases, the following will also be sent along with the trap PDU: 8 hot_sys.mib (Hotwire system) 7 hot_sys.
SNMP Traps Table B-1. DSL Card Traps (2 of 4) Event Severity Comment Trap # MIB Device failure major Access Node’s operating software has detected an internal device failure. 15 hot_sys.mib (Hotwire system) DHCP filter security failure minor Cannot add new route to route table because maximum number of stored rules reached. 11 hot_dhcp.
SNMP Traps Table B-1. DSL Card Traps (3 of 4) 8000-A2-GB20-50 Event Severity Comment Trap # MIB xDSL margin low minor Margin estimate below customer set threshold. 3 hot_xdsl.mib (Hotwire XDSL Interface) xDSL margin normal normal Margin estimate above customer set threshold. 103 hot_xdsl.mib (Hotwire XDSL Interface) xDSL port failure major Processor detected bad DSL modem chip set. 5 hot_xdsl.
SNMP Traps Table B-1. DSL Card Traps (4 of 4) B-6 Event Severity Comment Trap # MIB RTU device mismatch clear normal RTU identified on port N now matches device described in port configuration table. 107 hot_xdsl.mib (Hotwire XDSL Interface) RTU community name deletion failure warning Deletion of RTU community name failed. RTU remote service domain deletion failure warning Deletion of RTU remote service domain failed.
SNMP Traps RTU Related Traps The RTUs send the following traps. For a listing of Paradyne Enterprise MIBS, see SNMP Agent in the Hotwire 8540 and 8546 RADSL Cards Network Configuration Guide. Standard Traps Table B-2. Standard Traps Event Trap Class Comment Authentication Failure minor H Community string used is not in the Community Table. H Use of read-only community string for Set PDU. Warm start warning RTU has been reset by an NMS. Enterprise-Specific Traps Table B-3.
SNMP Traps This page intentionally left blank.
5446 RTU Setup C Hotwire 5446 RTU Setup Overview The Hotwire 5446 RTU supports various customer premises distribution networks that contain IP forwarding devices or routers, in addition to locally attached hosts or subnets. The Hotwire 5446 RTU has an IP Routing Table that is updated through an SNMP agent. The configuration table contains IP address and subnet mask information. The network service provider for the 5446 RTU provisions the IP address information into the 5446 RTU’s configuration table.
5446 RTU Setup Customer Premises (CP) End-user Systems 120.26.7.1 End-user Systems 120.26.7.2 130.26.7.1 120.26.7.3 End-user Systems 130.26.7.2 DSL/POTS 5446 RTU TM PWR ALM TST DSL ETHERNET Hub 120.26.7.100 140.26.7.1 Hub Router 130.26.7.3 140.26.7.2 120.26.7.200 Default Gateway Hub 140.26.7.3 98-16098a IP Injection Type IP Address Network Mask Next Hop Router Host 120.26.7.1 255.255.255.255 0.0.0.0 Host 120.26.7.2 255.255.255.255 0.0.0.0 Host 120.26.7.3 255.255.255.
5446 RTU Setup Accessing the Hotwire 5446 RTU IP Injection MIB The IP Injection Tool provides the ability to use the SNMP agent in the 5446 RTU to manage IP address, subnet mask, and community string information. There are three methods available to update the 5446 RTU IP configuration table: H Paradyne’s IP Injection Tool H NMS DCE Manager H MIB Browser The IP Injection Enterprise MIB must be used to finalize the 5446 RTU setup.
5446 RTU Setup Accessing the IP Injection Tool Once the program is successfully installed, an icon labeled IP Injection Tool is created. The Paradyne IP Injection Tool input screen appears when the tool is accessed. Access the online Help file for further information. NOTES: — Before using this tool, you must know the RTU Network Access Provider (NAP) and have established an active DSL link to the RTU.
5446 RTU Setup Community String Entries The Community String Selection fields are located before the selection buttons near the bottom of the screen and can display a read-only and a read-write community string. The read-write Community Name defaults to ‘private’. The read-write Community Name is used by the IP Injection tool to send SNMP messages to the 5446 RTU. The IP Injection tool and the 5446 RTU also use the private Community Name to make changes to the 5446 RTU configuration.
5446 RTU Setup IP and Device MIBs Supported The IP Injection MIB provides the capability to inject IP address information for hosts, applications, networks, or a local device. The following pdn-IP Injection Objects (pdn-common 11) contain IP address information. Information built from this table includes: H Host IP Routing. Displayed in the MIB II IP Route Table as read-only. H Service IP Address. Displayed in the MIB II IP Address Table as read-only.
5446 RTU Setup Configuration Requirements Host routes use the IP address assigned to the end-user systems supported by the 5446 RTU. Service domain IDs use the IP address information pertaining to the 5446 RTU within the service domain. Refer to IP Injection Tool Group Objects Table on page C-11 for IP Injection group object details. The first three Route Type entries must be entered in the 5446 RTU IP configuration table: H NAP address.
5446 RTU Setup Network Management Systems OpenLane DCE Manager, one of Paradyne’s Network Management Systems, communicates via SNMP to the RTU to update the IP configuration table. Display of the remote RTU and the use of the injection tool are features of this product. The NMS workstation is typically connected to a router and the NMS can easily access devices on other subnets.
5446 RTU Setup Using a MIB Browser Use a MIB browser to access the ipInjectionTable. The Enterprise IP Injection MIB OID (Object ID) is 1.3.6.1.4.1.1795.2.24.2.11. From an SNMP workstation: 1. To load the IP Injection MIB, access the Paradyne World Wide Web site at www.paradyne.com. 2. Select the Paradyne Enterprise MIB: Service & Support ! MIBs ! Hotwire DSL 3. After the pdndce.
5446 RTU Setup MIB Browser Techniques There are two MIB browser techniques. The Enterprise MIB allows the use of a null entry or a table index. Use a MIB browser to access the ipInjectionTable. " Procedures Using the null entry: 1. Change the Null entry by entering the IP address (ipInjectionAddress). 2. Change the mask by entering a subnet mask (ipInjectionMask). 3. Change the Type to Service Provider or Host (ipInjectionType). 4. Select Set. 5.
5446 RTU Setup IP Injection Tool Group Objects Table Table C-1. IP Injection Group Objects (ipInjectionTable 1) (1 of 2) Object Description Setting/Contents ipInjectionType (ipInjectionEntry 1) Indicates the type of IP address for each entry. H null(1) – Use to add a new row. Defaults: Changing the NAP IP address resets the database and any of the following entries are cleared: H serviceProvider(3) – Address: 0.0.0.0 – Mask: 255.255.255.
5446 RTU Setup Table C-1. IP Injection Group Objects (ipInjectionTable 1) (2 of 2) Object Description Setting/Contents ipInjectionStatus (ipInjectionEntry 4) Specifies the address status of static or dynamic. When the 5446 RTU is reset, static addresses are saved and dynamic addresses are not saved. Type of static or dynamic addressing for each entry. The default is static(1). H static(1) – Static addresses are assigned for the duration of the service subscription.
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 A server whose function is to authenticate and log an end-user’s access location.
Glossary 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. OpenLane DCE Manager A proprietary network management program used with HP OpenView that helps a network administrator manage SNMP devices. packet A group of control and data characters that are switched as a unit within a communications network. PING Packet InterNet Groper. A program that is useful for testing and debugging networks.
Glossary TCP Transmission Control Protocol. An Internet standard transport layer protocol defined in STD 7, RFC 793. It is connection-oriented and stream-oriented. Telnet Virtual terminal protocol in the Internet suite of protocols. Allows the user of one host computer to log into a remote host computer and interact as a normal terminal user of the remote host.
Index Numbers D 10BaseT interface on the MCC and DSL cards (e1a), 3-1 8820, 1-5 Delete ARP Entry screen, 3-25 display area, 2-3 DNS Setup screen, 3-8 Domain Names screen, 3-30 Download Code screen, 3-11 Downloading Code , A-2 DSL, traps, B-3 DSL card, 1-6 DSL Error Stats screen, 4-9 DSL Link Perf screen, 4-7 DSL Link Performance Summary screen, 4-7 DSL Parameters screen, 3-13, 3-14 DSL Perf Stats screen, 4-8 DSL Performance Stats screen, 4-8 DSL ports (s1c, s1d, s1e, and s1f), naming convention of ports
Index I S input line, 2-3 interface naming convention, 3-1 Interface Status screen, 4-11 Interfaces screen, 3-15 IP Filter Configuration screen, 3-24 IP Host Table screen, 3-25 IP injection, C-1 IP Network screen, 3-16 IP Router Filters screen, 3-24 s1b, 3-1 Security screen, 3-27 Selftest screen, 5-4 Setting Up SNMP Features, Enable DSL Port Traps, B-2 Simple Network Management Protocol (SNMP), 1-6 SNMP Communities/Traps screen, 3-27 SNMP Features Community Strings and Authentication Failure Trap, B-1 M
