Paradyne HotWire 8600, 8800 Digital Subscriber Line Access Multiplexer, HotWire 5446 Remote Termination Unit User’s Guide

AREA CODE CHANGE
Please note that the area code for
Paradyne Corporation in Largo, Florida
has changed from 813 to 727.
For any Paradyne telephone number that
appears in this manual with an 813 area
code, dial 727 instead.
HOTWIRE
DIGITAL SUBSCRIBER LINE
ACCESS MULTIPLEXER
(DSLAM)
USER’S GUIDE
Document No. 8000-A2-GB20-10
Copyright 1997 Paradyne Corporation.
All rights reserved.
Printed in U.S.A.
Notice
This publication is protected by federal copyright law. No part of this publication may be copied or distributed,
transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form
or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the
express written permission of Paradyne Corporation, 8545 126th Avenue North, P.O. Box 2826, Largo,
Florida 33779-2826.
Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically
disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporation
reserves the right to revise this publication and to make changes from time to time in the contents hereof without
obligation of Paradyne Corporation to notify any person of such revision or changes.
Changes and enhancements to the product and to the information herein will be documented and issued as a new
release to this manual.
Warranty, Sales, and Service Information
Contact your sales or service representative directly for any help needed. For additional information concerning
warranty, sales, service, repair, installation, documentation, or training, use one of the following methods:
Via the Internet: Visit the Paradyne World Wide Web site at http://www.paradyne.com
Via Telephone: Call our automated call system to receive current information via fax or to speak with a
company representative.
— Within the U.S.A., call 1-800-870-2221
— International, call 813-530-2340
Trademarks
All products and services mentioned herein are the trademarks, service marks, registered trademarks or registered
service marks of their respective owners.
Printed on recycled paper
A
June 1997
8000-A2-GB20-10
Contents
About This Guide
Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . vii
Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
1
HotWire DSLAM System Description
What is the HotWire 8600/8800 DSLAM? . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
HotWire DSLAM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Levels of Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
HotWire DSLAM Software Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Monitoring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Troubleshooting and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
2
HotWire Menus and Screens
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Menu and Screen Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Components of a HotWire Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Components of a HotWire Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Commonly Used Navigation Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
HotWire Menus: A Hierarchical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
HotWire Chassis Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
HotWire – MCC Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
HotWire – DSL Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Logging in to the System (After the System Has Been Configured) . . . . 2-11
Reviewing the Levels of Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Operator Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Card Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Accessing the HotWire — MCC Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Accessing the HotWire — DSL Menu
(and Selecting a Specific DSL Card) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Exiting From the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Manually Logging Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Automatically Logging Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
8000-A2-GB20-10
June 1997
i
Contents
3
Initial Setup Instructions
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Accessing the System for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Setting the Management IP Address and Subnet Mask on the MCC . . . 3-1
Additional Setup Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Chassis Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
4
Configuring the HotWire DSLAM
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Port Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Configuring MCC Cards, DSL Cards, and RTUs . . . . . . . . . . . . . . . . . . . . . 4-2
Setting Time and Date Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Assigning IP Addresses to the Backplane on the MCC Card . . . . . . 4-7
Assigning IP Addresses to the DSL Cards on the MCC Card . . . . . . 4-8
Creating the Default Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Resetting the MCC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Selecting a DSL Card to Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Configuring 5446 RTU IP Host Addresses on the DSL Card . . . . . . . 4-11
Configuring a Static Route to the Network Management System
on each DSL Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Assigning IP Addresses to the DSL Card LAN . . . . . . . . . . . . . . . . . . . 4-13
Configuring Static Routes to End Users on each DSL Card . . . . . . . 4-14
Creating Default Route or Source Route on the DSL . . . . . . . . . . . . . 4-15
Resetting the DSL Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
5
MCC Card Configuration
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
MCC Configuration Card Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
MCC Configuration Ports Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
MCC Configuration Interfaces Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
MCC Configuration Users Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
MCC Configuration IP Router Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
MCC Configuration SNMP Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
MCC DSL Cards Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
ii
June 1997
8000-A2-GB20-10
Contents
6
DSL Card Configuration
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
DSL Configuration Card Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
DSL Configuration Ports Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
DSL Configuration Interfaces Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
DSL Configuration Users Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
DSL Configuration IP Router Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
DSL Configuration SNMP Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
7
Monitoring the HotWire DSLAM
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
MCC Monitoring Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
MCC Monitoring Card Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
MCC Monitoring Physical Layer Screens . . . . . . . . . . . . . . . . . . . . . . . 7-3
MCC Monitoring Interfaces Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
MCC Network Protocol Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
MCC IP Router Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
DSL Monitoring Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
DSL Monitoring Card Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
DSL Monitoring Physical Layer Screens . . . . . . . . . . . . . . . . . . . . . . . . 7-16
DSL Monitoring Interfaces Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
DSL Network Protocol Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
DSL IP Router Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
8000-A2-GB20-10
June 1997
iii
Contents
8
Diagnostics and Troubleshooting
Applications Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Diagnostic Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Checking Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Major Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Minor Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Slow Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Excessive Collisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
No SNMP Connection Established . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Filters Not Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
IP Routing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Incorrect Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
No PPP Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
No Response at Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
System Does Not Recognize New DSL Cards . . . . . . . . . . . . . . . . . . . 8-12
Unusual Number of TRAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Cannot Communicate with Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Cannot Upload Configurations to a Unix Server . . . . . . . . . . . . . . . . . 8-13
Unexpected Sub-Net Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Cannot Communicate with HotWire 5446 from MCC Card . . . . . . . . 8-13
A
Checklist for Configuring the HotWire DSLAM
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Setting Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Assigning IP Addresses to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Assigning IP Addresses to the DSL Cards (Management Domain) . . . . . A-2
Creating the Default Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Resetting the MCC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Selecting a DSL Card to Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Configuring 5446 RTU IP Host Addresses on the DSL Card . . . . . . . . . . A-3
Configuring a Static Route to the Network Management System
(on each DSL Card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Assigning IP Addresses to the DSL Cards (Customer Domain) . . . . . . . . A-4
Creating Default Routes or Source Routes on the DSL . . . . . . . . . . . . . . . A-5
Resetting the DSL Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
iv
June 1997
8000-A2-GB20-10
Contents
B
Checklist for Setting Up User Accounts on the MCC and DSL
Cards
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
MCC User Accounts (For Telnet Terminal Access to MCC Card) . . . . . . B-1
Reboot Card (MCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
DSL User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Reboot Card (DSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
C
Checklist for Setting Up SNMP Features
Setting Up SNMP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Management System Source Validation for MCC . . . . . . . . . . . . . . . . C-1
MCC SNMP Community Strings and Authentication Failure Trap . . C-1
Management System Source Validation for DSL cards . . . . . . . . . . . C-2
DSL SNMP Community Strings and Authentication Failure Trap . . . C-2
Enable DSL Port Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
D
Download and Apply Code
Downloading Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Scenario One: Fully Operational System . . . . . . . . . . . . . . . . . . . . . . . D-1
Scenario Two: Download Only System . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Apply Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
E
Navigation Keys
F
Traps
8000-A2-GB20-10
June 1997
v
Contents
G
5446 RTU MIB Descriptions
MIB Description Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Configuring IP Address Information into a 5446 RTU . . . . . . . . . . . . . . . . . G-2
MIB Browser Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
IP Injection MIB (pdn-common 11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
Additional pdn-common MIBs Supported . . . . . . . . . . . . . . . . . . . . . . . G-4
MIB II Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-13
Standard Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-14
Enterprise-Specific Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-14
Glossary
Index
vi
June 1997
8000-A2-GB20-10
About This Guide
Document Purpose and Intended Audience
This guide describes how to operate and configure the software component of
the HotWire Digital Subscriber Line Access Multiplexer (DSLAM) system. It is
written for administrators and operators who maintain the networks that support
HotWire operation.
It is assumed that you have a basic understanding of internetworking protocols
and their features. Specifically, you should have a basic familiarity with Simple
Network Management Protocol (SNMP), Network Management Systems (NMSs),
and the following internetworking concepts:
TCP/IP applications
IP and subnet addressing
IP routing (also referred to as IP forwarding)
It is also assumed that you have already installed either the HotWire 8600 or
8800 DSLAM. If you have not done so already, refer to the appropriate HotWire
DSLAM Installation Guide for installation instructions.
NOTE:
It is highly recommended that you read the HotWire Digital Subscriber Line
Access Multiplexer (DSLAM) Network Configuration Guide before you begin
to use this guide and the HotWire software. The HotWire Digital Subscriber
Line Access Multiplexer (DSLAM) Network Configuration Guide provides
introductory information about the HotWire DSLAM network model and
theories.
8000-A2-GB20-10
June 1997
vii
About This Guide
Document Summary
viii
Section
Description
Chapter 1
HotWire DSLAM System Description. Provides an
overview of the HotWire 8600 and 8800 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
Initial Setup Instructions. Provides instructions on how
to access the system for the first time, as well as,
instructions on performing initial setup tasks.
Chapter 4
Configuring the HotWire DSLAM. Describes the
required procedures for configuring the HotWire
system.
Chapter 5
MCC Card Configuration. Describes the optional
procedures for configuring the MCC card on the
HotWire system.
Chapter 6
DSL Card Configuration. Describes the optional
procedures for configuring the DSL cards on the
HotWire system.
Chapter 7
Monitoring the HotWire DSLAM. Describes operator
programs that monitor the HotWire system.
Chapter 8
Diagnostics and Troubleshooting. Describes common
HotWire operational problems and solutions.
Appendix A
Checklist for Configuring the HotWire DSLAM.
Describes mandatory steps required to configure the
MCC cards, DSL cards, and RTUs for the HotWire
DSLAM.
Appendix B
Checklist for Setting Up User Accounts on the MCC
and DSL Cards. Describes user accounts and how to
set them up on the MCC and DSL cards.
Appendix C
Checklist for Setting Up SNMP Features. Describes
how to set up SNMP features.
Appendix D
Download and Apply Code. Describes how to work with
the Download and Apply download menus.
Appendix E
Navigation Keys. Describes the keys that are used to
navigate the HotWire system.
Appendix F
Traps. Describes the traps that are generated by the
HotWire system.
Appendix G
5446 RTU MIB Descriptions. Describes MIB details
including the Injection MIB and other enterprise MIBs.
Glossary
Defines acronyms and terms used in this document.
Index
Lists key terms, acronyms, concepts, and sections in
alphabetical order.
June 1997
8000-A2-GB20-10
About This Guide
Product-Related Documents
Document Number
Document Title
5020-A2-GN10
HotWire POTS Splitter Central Office Installation
Instructions
5030-A2-GN10
HotWire POTS Splitter Customer Premises
Installation Instructions
5446-A2-GN10
HotWire 5446 Remote Termination Unit (RTU)
Customer Premises Installation Instruction.
7700-A2-GB23
DCE Manager for HP OpenView for Windows
User’s Guide
7800-A2-GB23
DCE Manager for HP OpenView User’s Guide
8000-A2-GB21
HotWire Digital Subscriber Line Access Multiplexer
(DSLAM) Network Configuration Guide
8000-A2-GN11
HotWire Management Communications Controller
(MCC) Card Installation Instructions
8546-A2-GN10
HotWire 8546 Digital Subscriber Line (DSL) Card
Installation Instructions
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.
8000-A2-GB20-10
June 1997
ix
HotWire DSLAM System
Description
1
What is the HotWire 8600/8800 DSLAM?
The HotWire 8600 or 8800 Digital Subscriber Line Access Multiplexer (DSLAM)
provides high-speed Internet or Intranet access over traditional twisted-pair
telephone wiring. In addition, through the use of Rate Adaptive Digital Subscriber
Line (RADSL) technology, DSLAM provides simultaneous high-speed data
access (digital) and Plain Old Telephone Service (analog) over the same
twisted-pair telephone line. Support of this simultaneous access requires the
installation of Plain Old Telephone Service (POTS) splitters at both ends of the
line (i.e., at the Central Office and at the customer premises).
The corresponding HotWire 5446 Remote Termination Unit (RTU) installed at the
customer end of the telephone loop, allows users at remote locations to access
Internet Service Providers (ISPs) or corporate networks by means of the HotWire
DSLAM.
Internet
Service
Provider
Central Office (CO)
Data
Network
Router
POTS/
DSL
Ethernet
DSL
CARD
DSLAM
*CO
POTS
Splitter
MDF
CO
Switch
Legend: DSL - Digital Subscriber Line
MDF - Main Distribution Frame
Customer Premises (CP)
POTS/
DSL
HUB
RTU
HotWire
5446
POTS
*CP
POTS
Splitter
97-15490
RTU - Remote Termination Unit
POTS - Plain Old Telephone Service
* Optional
8000-A2-GB20-10
June 1997
1-1
HotWire DSLAM System Description
HotWire DSLAM Components
The HotWire DSLAM system consists of the following components:
HotWire DSLAM chassis
There are two types of chassis:
— Each HotWire 8600 DSLAM is an independent, stand-alone, system. The
stackable design provides for up to six systems to share management
access through a single Management Communications Controller (MCC)
card, which, in turn, allows an additional slot for a DSL card in each of up
to five additional systems.
A
B
4 5 6
1
..
DC PWR
ALM
A
STACK
POSITION
LINE
LAN/WAN SLOT
MANAGEMENT
RADSL
8546
RADSL
8546
4
3
D
ol
C
X
R
FAN
8000
D
RT
2
SL
1
PO
ol
C
X
N
ET
TX
N
.
.
MCC
4
3
2
PO
SL
1
RT
ET
ol
C
N
X
R
ER
H
ET
ET
R
TX
H
ET
3
2
48VDC CLASS 2 OR
LIMITED PWR SOURCE
ER
H
ET
DC FUSES
T4A, MIN. 48V
AC
INPUT
ER
EM
K
Alr
m
Te
st
O
ST
SY
EM
K
Alr
m
Te
st
ST
RTN
B A B
SY
48V
A
O
AC
T5A
250V
TX
K
Alr
m
Te
st
O
SY
ST
EM
In a stacked configuration, the first, or base chassis, must contain an
MCC card in Slot 1. In addition to the MCC card, the base chassis can
house up to two DSL cards. Each additional chassis in the stack houses
up to three DSL cards.
3
2
1
B
IN
OUT
SERIAL
MCC
1
2
3
97-15350-01
For more information about the HotWire 8600 DSLAM chassis, see the
HotWire 8600 Digital Subscriber Line Access Multiplexer (DSLAM)
Installation Guide.
1-2
June 1997
8000-A2-GB20-10
HotWire DSLAM System Description
— The HotWire 8800 DSLAM chassis 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.)
POWER
A
B
ALARMS
Fan Major Minor
SYST
SYST
EM
EM
OK
OK
Alm
Alm
Test
Test
ETHE
RNET
ETHE
RNET
TX
TX
RX
RX
Coll
DSL
Coll
PORT
1
2
3
4
RADSL
MCC
-48V INPUT
SLOTS 13-18
2
4
6
8
1
3
5
7
LAN/WAN SLOT
10
14
12
16
18
15
17
20
MGT
SERIAL
RET (B)
FR GND
RET (A)
SLOTS 1 - 6
-48V (B)
LINES
-48V (A)
SLOTS 7-12
11
9
LAN/WAN SLOT
13
19
MGT
10BT
ALARM
97-15280
For more information about the HotWire 8600 DSLAM chassis, see the
HotWire 8800 Digital Subscriber Line Access Multiplexer (DSLAM)
Installation Guide.
One Management Communications Controller (MCC) card
The chassis requires one MCC card, which is a processor card that
administers and provides diagnostic 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 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. It also has a serial port
for a local user interface to the DSLAM.
At least one Digital Subscriber Line (DSL) card
The chassis requires at least one DSL card, which is a circuit card that
contains four RADSL modem ports, an Ethernet interface to the ISP, and a
processor/packet forwarder. The processor/packet forwarder controls the
modems and forwards the packet traffic via the Ethernet and DSL interfaces.
When the 8600 DSLAM chassis is fully populated, it provides a total of
68 RADSL modem ports. When the 8800 DSLAM chassis is fully populated, it
provides a total of 72 RADSL modem ports.
8000-A2-GB20-10
June 1997
1-3
HotWire DSLAM System Description
Features
The HotWire DSLAM system provides the following features:
High speed Internet or Intranet access.
Rate adaptive Digital Subscriber Loop ports.
Security access and permission features that prevent users from accessing
another user’s PC files or LAN traffic.
Status polling, alarm indicators and logging, diagnostics, and performance
capabilities.
Primary network management support via SNMP agent for monitoring and
traps; telnet for configuration and diagnostics.
Levels of Access
There are two levels of diagnostic/administrative access in the HotWire DSLAM
system:
Administrator
The Administrator has complete read/write access to the DSLAM system.
With Administrator permission, you can set specific parameters and variables
to configure cards, ports, interfaces, user accounts, next hop routes, and
SNMP security.
Operator
The Operator has read-only access. With Operator permission, you can view
card status, physical layer status, interfaces, and Internet Protocol (IP)
routes, and run non-disruptive tests.
HotWire DSLAM Software Functionality
Depending upon your system permission, you can:
Configure the system,
Monitor the system, and/or
Run applications and diagnostic tests to troubleshoot the network
Configuring the System
The HotWire DSLAM software provides configuration submenu options to:
1-4
Configure the MCC card, DSL cards, and Remote Termination Units (RTUs)
Configure the interfaces and ports
Set up user accounts
June 1997
8000-A2-GB20-10
HotWire DSLAM System Description
Upload or download a copy of a card’s configuration data to or from a Trivial
File Transfer Protocol (TFPT) server
Download a new version of the DSLAM software
Define a routing table
Define and enable filters to prevent unauthorized network access
Configure the SNMP agent to send traps to a specific SNMP NMS manager
Note that you must have administrator permission to configure the system. For
more information about configuring the system, see Chapters 4, 5, and 6.
Monitoring the System
The HotWire DSLAM software provides submenu options to monitor the activity
of the HotWire MCC and DSL cards. The monitoring screens allow you to:
List the status of active ports and interfaces in a card, as well as display
statistics about other physical layers and interfaces
Display network protocol statistics, such as information about an application
program assigned to a specific socket number, UDP statistics, TCP data and
connection statistics, IP statistics, ICMP packet statistics, SNMP statistics
including SNMP authentication statistics, HDLC statistics, and PPP statistics.
Display information about the routing table and detailed information about
each routing entry
Display the current Address Resolution Protocol (ARP) table
Use the monitoring screens to help you gather pertinent information and isolate
potential problem areas. Note that you can monitor the system with either
administrator or operator permission. For more information about monitoring the
system, see Chapter 7.
Troubleshooting and Diagnostics
The HotWire DSLAM system provides diagnostic submenu options that:
Run selftests to check the status of CPU, memories, and ports
Perform ping tests and display results
Show major and minor alarms
Display or clear error logs
Enable or disable the A/B power supply alarm
Note that you must have administrator permission to perform most of the
troubleshooting and diagnostic activities. However, you can run non-disruptive
tests as a user with operator permission. For more information about
troubleshooting and diagnostics, see Chapter 8.
8000-A2-GB20-10
June 1997
1-5
HotWire Menus and Screens
2
Overview
The HotWire DSLAM has a menu- and screen-driven user interface system that
enables the user to configure and monitor the HotWire cards. This section
covers:
Menu and screen format
Commonly used navigation keys
Menu trees
— HotWire Chassis Main Menu
— HotWire – MCC Menu
— HotWire – DSL Menu
Logging in to the system
— Reviewing the Levels of Access
— Operator Login Screen
— Card Selection Screen
— Accessing the HotWire – MCC Menu
— Accessing the HotWire – DSL Menu
8000-A2-GB20-10
Exiting from the system
June 1997
2-1
HotWire Menus and Screens
Menu and Screen Formats
The HotWire DSLAM uses an ASCII-based text format for its menus and screens.
This section describes the components of a typical HotWire menu and screen.
Components of a HotWire Menu
A typical HotWire menu format looks like this:
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 bottom 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 (short cut) to select a menu item.
For example, from the HotWire – MCC menu illustrated above, you can
simply press the A key to select the Configuration menu item. The
Configuration menu appears. You can then press the F key to select the DSL
Cards menu item. This action displays the DSL Cards menu. (You can also
use the arrow keys on your keyboard to select a menu item. See Commonly
Used Navigation Keys on page 2-4 for more information.)
2-2
June 1997
8000-A2-GB20-10
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 three fields
that provide system login information.
— The first field displays the name of the system as defined in the System
Information screen. (Access the System Information screen by selecting
the appropriate card in the chassis and then follow this menu sequence:
Configuration → Card Status → Card Info.) If you do not define the
system name, the DSLAM user interface will display <no name>.
— The middle field displays the current login. This field will display either
L:<user_login> or R:<user_login> where L indicates a local login,
R indicates a remote login, and <user_login> is the login account of
the user currently accessing the system. For example, if a user with a
login account called admin logs into the system using the local console,
this field will display L:admin.
— The last field displays the previous login. This field will display either
L:<user_login> or R:<user_login> where L indicates a local login,
R indicates a remote login, and <user_login> is the login account of
the user currently accessing the system. For example, if a user with a
login account called admin logs into the system remotely via a telnet
session, this field will display R:admin.
2. Display Area is the top portion of the screen on which pertinent DSLAM
system information is displayed. This is also the portion of the screen on
which fields requiring input are displayed. However, you cannot enter values
for the fields in this portion of the screen. You must enter field values in the
Input Line of the screen (see below).
8000-A2-GB20-10
June 1997
2-3
HotWire Menus and Screens
3. Input Line is the area of the screen where you are prompted to enter values
for the specific field that is highlighted on the screen.
For example, in the Configure DSL IP Addr screen above, the DSL Card
Subnet Mask field is highlighted. If you want to change the subnet mask, you
must enter the new subnet mask at the (nnn.nnn.nnn.nnn): prompt at
the bottom of the screen.
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 8800:
MCC:
__ __ __ X
The first field indicates the chassis type. In this case, the system in use is the
HotWire 8800 DSLAM system. The second field indicates the card selected.
In this example, the MCC card is selected. The remaining fields indicate card
status information, such as status of Ethernet link and DSL links, and whether
or not an alarm is present. This is the same information displayed on the
Card Selection screen. For information about these fields, see Card Selection
Screen on page 2-13.
Commonly Used Navigation Keys
The following table lists the most commonly used navigation keys with their
definitions. These commands are used to move around the menus and screens.
For a complete list of keys, see Appendix E, Navigation Keys.
2-4
Keys
Definition
Ctrl-a
Moves Home or to the top of the menu.
Ctrl-k
Moves up to the previous menu selection or entry field.
Ctrl-l
Refreshes the screen.
Ctrl-p
Moves back a field.
Ctrl-t
Moves Home or to the top of the menu.
Ctrl-v
Displays a pop-up list of all interfaces on the IP Network screen.
Displays a pop-up list of all accounts in system on the Configure
Accounts screen.
Ctrl-z
Moves back one menu level or exits from screen.
Up arrow
Moves up to the previous menu selection or entry field.
Down arrow
Moves down to the next menu choice or entry field.
Left arrow
Moves left to the previous menu box or entry field.
Right arrow
Moves right to the next menu box or entry field.
Enter or Return
Accepts entry.
Tab
Moves down or to the next selection.
?
Displays Online help screens that correspond to the particular
menu or system screen displayed.
June 1997
8000-A2-GB20-10
HotWire Menus and Screens
HotWire Menus: A Hierarchical View
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
From the HotWire Chassis Main Menu, you can select:
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.
For more information, see Additional Setup Instructions in Chapter 3.
Card Selection to select a particular card in the chassis. This screen also
displays status information about all cards in the chassis. The card you select
determines which HotWire menu the system will display next (either the
HotWire – MCC menu or the HotWire – DSL menu).
For more information, see Card Selection screen on page 2-13.
Logout to exit from the current login session on the HotWire DSLAM.
For more information, see Exiting From the System on page 2-15.
8000-A2-GB20-10
June 1997
2-5
HotWire Menus and Screens
HotWire – MCC Menu
After selecting the MCC card from the Card Selection screen, the DSLAM system
displays the HotWire – MCC Menu.
HotWire-MCC
A. Configuration*
B. Monitoring
C. Applications
D. Diagnostics
E. Exit
See
Configuration
Menu Below*
See
Monitoring
Menu Below
Applications
A. Ping
B. Telnet
* The configuration menu item appears only if you have
administrator permission.
Diagnostics
A. Selftest
B. Alarms
97-15557
From this menu, you can configure, monitor, run applications, and troubleshoot
the MCC card.
2-6
June 1997
8000-A2-GB20-10
HotWire Menus and Screens
The following figure illustrates the complete Configuration menu hierarchy from
the HotWire – MCC menu.
NOTE:
The Configuration menu and its sub-menus appear only when logging in to
the system with a user account that has administrator permission.
Configuration
A. Card Status
B. Ports
C. Interfaces
D. Users
E. IP Router
F. SNMP
G. DSL Cards
(B) Ports
A. Ethernet Port
(A) Card Status
A. Card Info
B. DNS Setup
C. Time/Date
D. NVRAM Clear
E. NVRAM Cfg Loader
F. Card Reset
E. Download Code
(D) Users
A. Accounts
(C) Interfaces
A. General
B. IP Network
C. Control
(E) IP Router
A. Static Routes
B. Martian Networks
C. IP Router Filters
D. ARP
E. Host Table
(D) ARP
A. Parameters
B. Add Entry
C. Delete Entry
(E) Download Code
A. Download Code
B. Apply Download
8000-A2-GB20-10
(F) SNMP
A. Security
B. Logical Entities
C. Logical Entities 2
D. Communities/Traps
June 1997
(G) DSL Cards
A. Set IP Address
B. Reset Slot
97-15558
2-7
HotWire Menus and Screens
The following figure illustrates the complete Monitoring menu hierarchy from the
HotWire – MCC menu.
Monitoring
A. Card Status
B. Physical Layer
C.Interfaces
D.Network Protocol
E. IP Router
(A) Card 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
2-8
(E) IP Router
A. Routing Table
B. ARP Table
(D) Network Protocol
A.Socket Statistics
B.UDP Statistics
C.TCP Statistics
D.IP Statistics
E.ICMP Statistics
F. SNMP Statistics
G.HDLC Statistics
June 1997
97-15559
8000-A2-GB20-10
HotWire Menus and Screens
HotWire – DSL Menu
After selecting a specific DSL card from the Card Selection screen, the DSLAM
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
* The configuration menu item appears only if you have
admininstrator permission.
Diagnostics
A. Selftest
B. Alarms
97-15563
From this menu, you can configure, monitor, run applications, and troubleshoot a
specific DSL card.
8000-A2-GB20-10
June 1997
2-9
HotWire Menus and Screens
The following figure illustrates the complete Configuration menu hierarchy from
the HotWire – DSL menu.
NOTE:
The Configuration menu and its sub-menus appear only when logging in to
the system with a user account that has administrator permission.
Configuration
A. Card Status
B. Ports
C. Interfaces
D. Users
E. IP Router
F. SNMP
(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
E. Download Code
(C) Interfaces
A. General
B. IP Network
C Control
D. PPP
(E) Download Code
A. Download Code
B. Apply Download
2-10
(D) Users
A. Accounts
June 1997
( F) SNMP
A. Security
B. Logical Entities
C. Communities/Traps
(E) IP Router
A. Static Routes
B. Martian Networks
C. IP Router Filters
D. ARP
E. Host Table
(D) ARP
A. Parameters
B. Add Entry
C. Delete Entry
97-15564
8000-A2-GB20-10
HotWire Menus and Screens
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
(A) Card 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.DSL Xmit Stats
(E) IP Router
A. Routing Table
B. ARP Table
(D) Network Protocol
A.Socket Statistics
B.UDP Statistics
C.TCP Statistics
D.IP Statistics
E.ICMP Statistics
F. SNMP Statistics
G.HDLC Statistics
H.PPP Stats
(H) PPP Stats
A.General
B.LCP Stats
C.IPCP Stats
97-15565
Logging in to the System (After the System Has Been
Configured)
NOTE:
When you power on the system for the first time, the system displays the
Who Am I screen. This screen can be accessed only from the local console.
For information about this screen, see Accessing the System for the First
Time in Chapter 3.
This section describes how to log in to the HotWire DSLAM system after the
system has been configured for the first time.
8000-A2-GB20-10
June 1997
2-11
HotWire Menus and Screens
Reviewing the Levels of Access
There are two levels of privileges on the HotWire DSLAM system. Your user
accounts can be configured with a user name, password, and privilege of:
Administrator, giving you access to all of the features of the system including
configuration options, or
Operator, giving you read-only access.
For more information on creating user accounts, see Appendix B, Checklist For
Setting Up User Accounts on the MCC and DSL Cards.
Operator Login Screen
You can log in to the HotWire DSLAM system using either a local VT100 terminal
or a remote Telnet connection. However, the HotWire DSLAM system accepts
only one login session at a time.
At the Operator Login Screen, enter your login ID and password.
NOTE:
The login id and password are case sensitive; that is, the system recognizes
both upper- and lower-case letters. For example, if you enter your user name
and password information in upper case letters and your assigned user name
and password are in upper- and lower-case letters, the system won’t let you
log in.
After entering your login ID and password, the system displays the HotWire
Chassis Main Menu.
2-12
June 1997
8000-A2-GB20-10
HotWire Menus and Screens
Card Selection Screen
From the HotWire Chassis Main Menu select Card Selection to display the cards
present in the chassis by type and slot number. The Card Selection screen also
displays general and interface status for each card.
For the MCC card, the following information is displayed:
<card type> 1 2 3 4
97-15522
Position
8000-A2-GB20-10
Display
Description
<card type>
MCC
1
T (Test mode)
Card currently in test mode
2
M (Major alarm)
Major alarm present on card
3
R (Minor alarm)
Minor alarm present on card
4
e (Ethernet)
Status of Ethernet link (U=UP, D=Down, or
X=Disabled)
June 1997
2-13
HotWire Menus and Screens
For the DSL card, the following information is displayed:
<card type and slot #> 1 2 3 4 5 6 7 8
97-15493
Position
Display
Description
<card type and slot #>
DSL1–DSL18
1
T (Test mode)
Card currently in test mode
2
M (Major alarm)
Major alarm present on card
3
R (Minor alarm)
Minor alarm present on card
4
e (Ethernet)
Status of Ethernet link (U=Up, D=Down,
or X=Disabled)
5
d1 (DSL1)
Status of DSL link 1 (U=Up, D=Down,
X=Disabled, or H=Handshaking)
6
d2 (DSL 2)
Status of DSL link 2 (U=Up, D=Down,
X=Disabled, or H=Handshaking)
7
d3 (DSL 3)
Status of DSL link 3 (U=Up, D=Down,
X=Disabled, or H=Handshaking)
8
d4 (DSL 4)
Status of DSL link 4 (U=Up, D=Down,
X=Disabled, or H=Handshaking)
These are both positional displays. If an option is not active, an underscore is
shown in its place.
For more information about the statuses displayed on this screen, such as major
and minor alarms, see Troubleshooting in Chapter 8.
2-14
June 1997
8000-A2-GB20-10
HotWire Menus and Screens
Accessing the HotWire — MCC Menu
Procedure
To access the HotWire – MCC menu:
1. From the HotWire Chassis Main Menu, select Card Selection.
The Card Selection screen appears.
2. At the Goto Card (MCC or DSLnn): prompt, enter MCC.
The HotWire – MCC menu appears.
Accessing the HotWire — DSL Menu (and Selecting a Specific DSL
Card)
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-13 for more information.)
3. At the Goto Card (MCC or DSLnn): prompt, enter DSL and the number
of the slot. Then, press Return. For example, if you want to configure the DSL
card in slot 13, enter DSL13.
The HotWire – DSL menu appears.
Exiting From the System
You can manually log out of the system or after five minutes of inactivity, the
system will automatically log you out.
Manually Logging Off
Procedure
To exit from the HotWire DSLAM system:
1. Return to the HotWire Chassis Main Menu by selecting Exit from either the
HotWire – MCC menu or the HotWire – DSL menu.
The HotWire Chassis Main Menu appears.
2. From the HotWire Chassis Main Menu, select Logout.
The system exits from the current login session on the HotWire DSLAM.
8000-A2-GB20-10
June 1997
2-15
HotWire Menus and Screens
Automatically Logging Off
The DSLAM system has an automatic timeout feature that logs you out of the
system after five minutes of inactivity. You will need to log back in to continue
your work.
To log back in, press RETURN to display the Operator Login screen and log in.
2-16
June 1997
8000-A2-GB20-10
Initial Setup Instructions
3
Overview
This chapter provides instructions on how to access the system for the first time
and perform initial setup instructions.
NOTE:
It is highly recommended that you read the HotWire Digital Subscriber Line
Access Multiplexer (DSLAM) Network Configuration Guide before you
attempt to configure the system. The Network Configuration Guide provides
worksheets to help you plan and configure your network.
Accessing the System for the First Time
When you power on the HotWire DSLAM for the first time, the system displays
the Who Am I screen on the console terminal. On this screen, you must set the
management IP address and subnet mask for the MCC card. Follow the
instructions in the following section, Setting the Management IP Address and
Subnet Mask on the MCC.
Setting the Management IP Address and Subnet
Mask on the MCC
After powering on the system for the first time, set the management IP address
and subnet mask of the MCC card. This is a mandatory step and must be
completed before proceeding to Chapter 4, Configuring the HotWire DSLAM.
Procedure
To set the management IP address and subnet mask from the console terminal:
1. Power up the chassis.
After the self-test completes, the Who Am I screen appears.
8000-A2-GB20-10
June 1997
3-1
Initial Setup Instructions
2. From the Who Am I screen, enter the management domain IP address of the
MCC card and press the Return key. For example, if the IP address of the
MCC card is 198.152.110.1, type this value at the (nnn.nnn.nnn.nnn):
prompt on the Input Line at the bottom of the screen.
The system automatically calculates the subnet mask based on the IP
address you enter.
3. Do one of the following at the (nnn.nnn.nnn.nnn): prompt:
— To accept the subnet mask, press Return.
— To enter a different subnet mask, enter a new subnet mask and press
Return.
3-2
June 1997
8000-A2-GB20-10
Initial Setup Instructions
The system highlights the OK to restart?: prompt.
4. Type y at the yes/no: prompt to restart the card or n to decline the restart.
If you type y, the card restarts. The system displays the HotWire Chassis
Main Menu.
Additional Setup Instructions
This section describes additional setup instructions you should perform. On the
Chassis Information screen, you can enter pertinent chassis information, such as
the chassis name, name of person responsible for the system, and physical
location of the chassis.
8000-A2-GB20-10
June 1997
3-3
Initial Setup Instructions
Chassis Information Screen
Procedure
1. Choose Chassis Info from the HotWire Chassis Main Menu to enter or
display chassis configuration information.
The following table describes the information you should enter on the
Chassis Information screen. This information is used in the general section of
the SNMP MIB II.
Field
Input
Description
Chassis Name
16 alphanumeric characters Name for the equipment
Chassis Contact
32 alphanumeric characters Name and phone number of
individual responsible for the
equipment
Chassis Location
16 alphanumeric characters Physical location of the
equipment
Bay Number
16 alphanumeric characters Floor and/or bay number of the
equipment
Chassis Number
16 alphanumeric characters Chassis serial number (located
on the lower right side of
chassis)
2. When you have made the appropriate changes to the screen, a message
Configuration has been modified. Save (yes/no)? appears.
Enter yes to save changes and press Return to go back to the HotWire
Chassis Main Menu.
What’s Next?
Now you are ready to configure your HotWire DSLAM. Refer to Chapter 4,
Configuring the HotWire DSLAM, for instructions on how to configure the
mandatory minimum configurations; and Chapter 5, MCC Card Configuration,
and Chapter 6, DSL Card Configuration, for additional configuration instructions
when customizing your application.
After you have configured your system, you can monitor and troubleshoot
potential problems on the system. Refer to Chapter 7, Monitoring the HotWire
DSLAM, and Chapter 8, Diagnostics and Troubleshooting, for more information.
3-4
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
4
Overview
The HotWire DSLAM enables you to configure and manage the HotWire MCC
and DSL cards. This section describes the mandatory card configuration
instructions.
Port Naming Convention
The following is the naming convention used for the HotWire DSLAM interfaces:
NOTE:
Interfaces are sometimes referred to as ports. The term ports, however,
usually is reserved for referring to the physical layer attributes of an interface.
e1a — Interface name of the DSLAM system 10BaseT interface on the MCC
and DSL cards.
s1b — Interface name of the card’s interface to the DSLAM system
backplane bus.
s1c, s1d, s1e, and s1f — Interface names of the four DSL ports on a DSL
card.
NOTE:
These names are used throughout the remainder of this guide to reference
the HotWire DSLAM interfaces. These are also the names used in the
HotWire DSLAM software when configuring the HotWire DSLAM system.
8000-A2-GB20-10
June 1997
4-1
Configuring the HotWire DSLAM
Configuring MCC Cards, DSL Cards, and RTUs
Use the procedures in the following order to configure the MCC and DSL cards
for the basic setup for management and user data connectivity. For a quick
checklist of these procedures, see Appendix A, Checklist for Configuring the
HotWire DSLAM.
NOTE:
It is assumed that you have read the HotWire Digital Subscriber Line Access
Multiplexer (DSLAM) Network Configuration Guide and have assigned
customer and management domain IP addresses for all devices (MCC, DSL,
and RTUs). For your convenience, Appendix A of the Network Configuration
Guide contains worksheets to record your configuration settings.
The following tables lists the mandatory steps you need to configure the MCC
cards, DSL cards, and RTUs.
4-2
For the Management Domain,
perform task . . .
On the . . .
See . . .
1. Configure time and date.
MCC
Setting Time and Date Screen,
page 4-6.
2. Assign the IP address to the
backplane on the MCC card.
MCC
Assigning IP Addresses to the
Backplane on the MCC Card,
page 4-7.
3. Assign the IP addresses to the
DSL cards.
MCC
Assigning IP Addresses to the DSL
Cards on the MCC Card,
page 4-8.
4. Create default route.
MCC
Creating the Default Route,
page 4-9.
5. Reset the MCC Card.
MCC
Resetting the MCC Card,
page 4-10.
6. Select a DSL card to Configure.
DSL
Selecting a DSL Card to
Configure, page 4-10.
7. Configure 5446 RTU IP host
address.
DSL
Configuring 5446 RTU IP Host
Addresses on the DSL Card,
page 4-10.
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
8000-A2-GB20-10
For each Customer Domain,
perform task . . .
On the . . .
See . . .
1. Select a DSL card to configure.
DSL
Selecting a DSL Card to
Configure, page 4-10.
2. Configure 5446 RTU IP host
address.
DSL
Configuring 5446 RTU IP Host
Addresses on the DSL Card,
page 4-11.
3. Configure a static route to the
NMS.
DSL
Configuring a Static Route to the
Network Management System on
each DSL Card, page 4-12.
4. Assign IP addresses to the DSL
card LAN.
DSL
Assigning IP Addresses to the DSL
Card LAN , page 4-13.
5. Configure static routes to end
users on each DSL card.
DSL
Configuring Static Routes to End
Users on each DSL Card,
page 4-14.
6. Create default route or source
route on DSL.
DSL
Creating Default Route or Source
Route on the DSL, page 4-15.
7. Reset the DSL card.
DSL
Resetting the DSL Card,
page 4-15.
June 1997
4-3
Configuring the HotWire DSLAM
The following illustrates the Management Domain components that must be
configured and examples of the various naming conventions.
MANAGEMENT DOMAIN
DCE Manager
Server
IP Address
10BT
DCE Manager
Router
b1: 135.1.3.254/24
b2: 135.1.2.1/24
DSLAM
RTU
a: 135.1.3.3/32
e1a: 135.1.2.2/24
Task 7
MCC Card
Task 2
s1b: 135.1.3.1/24
Port Names
System Backplane
RTU
s1b: 135.1.3.2/24
Task 3
a: 135.1.3.4/32
Task 7
DSL Card
s1c
DSL
s1d
DSL
IP Interface
s1e
Notes:
132 = 255.255.255.255
124 = 255.255.255.00
116 = 255.255.00.00
4-4
s1f
DSL
DSL
RTU
RTU
97-15561
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
The following illustrates the Customer Domain components that must be
configured and examples of the various naming conventions.
CUSTOMER DOMAIN
DCE Manager
Server
DSLAM
DCE Manager
Router
RTU
b1: 155.1.3.3/24
b2: 156.1.3.3/24
b3: 157.1.3.3/24
b4: 158.1.3.3/24
MCC Card
10BT
ISP Router
System Backplane
a: 155.1.2.1/24
b1: 155.1.3.1/24
RTU
DSL Card
..
.
s1c
DSL
s1d
DSL
b16: 170.1.3.1/24
IP Interface
e1a: 155.1.3.2/24
156.1.3.2/24
..
.
Tasks 9, 10 & 11
10BT
170.1.3.2/24
s1e
s1f
DSL
DSL
b1: 159.1.3.3/24
b2: 160.1.3.3/24
b3: 161.1.3.3/24
b4: 162.1.3.3/24
10BT
RTU
RTU
97-15562
Notes:
132 = 255.255.255.255
124 = 255.255.255.00
116 = 255.255.00.00
8000-A2-GB20-10
June 1997
4-5
Configuring the HotWire DSLAM
Setting Time and Date Screen
When you select Time/Date from the Card Status menu, the Time/Date screen is
displayed. From this screen, you can configure the local time and date on the
card.
Procedure
To set the time and date on the MCC card:
1. Select Card Selection (B) from the HotWire Chassis Main Menu.
2. At the Goto Card (MCC or DSLnn): prompt, enter MCC.
3. Select Configuration → Card Status → Time/Date (A-A-C).
4. Enter values for the following fields and press Return after each entry:
Field
Description
Input
Local Time/Date
Current local time and date.
hh.mm (am or pm)
mm/dd/yy format
Client Network Time
Protocol (NTP) Mode
General time protocol
(Broadcast) or specific time
protocol with address
(Unicast).
Broadcast or Unicast
(Default = broadcast)
NTP Server
IP address of the NTP
server.
nnn.nnn.nnn.nnn format
Synchronized(hrs)
How often the system
1–24
should go out looking for the
time and date to
synchronize the system
time and date.
NOTE:
At system boot time, the time on the DSL card automatically syncs with
the MCC card. Therefore, it is usually not necessary to use this screen on
the DSL.
5. Press Ctrl-z to return to the Configuration → Card Status menu.
4-6
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
Assigning IP Addresses to the Backplane on the MCC Card
Use this procedure to create a separate and distinct network or subnetwork for
the DSL cards and 5446 RTUs.
Procedure
To assign IP addresss to the backplane:
1. Select Configuration → Interfaces → IP Network (A-C-B).
2. Enter values for the following mandatory fields and press Return after each
entry:
Field
Description
Input
IP Interface
Name of the interface.
s1b (backplane)
Base IP Addr
IP address of the
management domain.
nnn.nnn.nnn.nnn format
Base Subnet Mask
Associated subnet mask of
the base IP address.
nnn.nnn.nnn.nnn format
Peer IP Address
IP address associated with
the other end of the link.
nnn.nnn.nnn.nnn format *
Route to Peer
Routing method to use to get
to peer (i.e., host or net).
Net
* Enter the network/subnetwork portion of the Base IP address, with 0 for the
host portion so that the Peer is the entire subnet.
In addition, the following fields also appear on the screen. These fields can
be used to customize your application.
Field
Description
Input
Input Filter
Prevents packets from
entering the DSL card
through a specified interface.
Blank to disable.
Output Filter
Prevents packets from going Blank to disable.
out of the DSL card through a
specified interface.
3. Press Ctrl-z to return to the Configuration → Interfaces menu.
8000-A2-GB20-10
June 1997
4-7
Configuring the HotWire DSLAM
Assigning IP Addresses to the DSL Cards on the MCC Card
Use this procedure to define addresses within the management domain. These
are automatically assigned to the DSL cards when they are inserted in the
chassis.
Procedure
To assign IP addresses to the DSL cards:
1. Select Configuration → DSL Cards → Set IP Address (A-G-A).
2. Enter values for the following fields and press Return after each entry.
Field
Description
Input
DSL Card Subnet Mask
Subnet mask for the
backplane(s1b)
management subnet.
nnn.nnn.nnn.nnn
format
IP Address (for each DSL card)
Internet Protocol
address for each DSL
card in the system.
nnn.nnn.nnn.nnn
format. (Subnet is
predetermined – you
can enter the host
number.)
NOTE:
You must have assigned IP addresses to the backplane on the IP
Network screen for s1b before performing this procedure.
3. Press Ctrl-z to return to the Configuration → DSL Cards menu.
4-8
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
Creating the Default Route
Use this procedure to create the default route to the management domain next
hop router. This default route will be used when no other routes in the routing
table apply.
Procedure
To create the default route:
1. Select Configuration → IP Router→ Static Routes (A-E-A).
2. Press Return on the Item 0 field to add a new record.
3. Enter values for the following fields and press Return after each entry.
Field
Description
Input
Host/Net
Destination of the route.
0.0.0.0 to indicate the
default route
Subnet Mask
Associated subnet mask
for the specified
destination IP address.
nnn.nnn.nnn.nnn format
Next Hop
IP address of the next hop
device for the specified
destination.
nnn.nnn.nnn.nnn format
Pref (Preference)
Measure of how preferable
one route is to another, if
you have two routes going
to the same destination.
(The lower the number, the
more preferable the route.)
This route is compared to
other routes for the same
destination address.
1
S/D (Source/Destination)
Source or destination route Default = Dst
type.
PA (Proxy ARP)
Router answers ARP
requests intended for
another machine.
Default = No
4. Confirm the save and press Ctrl-z to return to the Configuration → IP Router
menu.
8000-A2-GB20-10
June 1997
4-9
Configuring the HotWire DSLAM
Resetting the MCC Card
After configuring the MCC card, reset the MCC card to install the configuration
settings.
Procedure
To reset the HotWire Chassis:
1. Select Configuration → Card Status→Card Reset (A-A-F).
2. Enter yes to verify MCC reset.
NOTE:
When you enter Y, all data connectivity is interrupted.
3. Wait for the MCC card to reboot.
4. Press Return.
5. The Operator Login screen is displayed.
6. Enter login information.
Selecting a DSL Card to Configure
All DSL cards that are present in the chassis and have had backplane addresses
assigned to them should appear on the Card Status screen. However, if one or
more do not appear, go to the MCC card, select Configuration → DSL
Cards→Reset Slot and reset the DSL card.
Use this procedure to select a specific DSL card to configure.
Procedure
To select a DSL card to configure:
1. From the HotWire Chassis Main Menu, select Card Selection (B).
2. Enter DSLnn, where nn is the number of the DSL card you want to configure,
and press Return.
The HotWire DSL menu is displayed.
3. Enter DSLnn, where nn is the number of the DSL card you want to configure,
and press Return.
The Configuration Menu is displayed.
4-10
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
Configuring 5446 RTU IP Host Addresses on the DSL Card
Use this procedure to assign an IP address within the management subnet to
each 5446 RTU.
Procedure
To configure IP host addresses on the DSL card:
1. Select Configuration → Interfaces→ IP Network (A-C-B).
2. Enter values for the following mandatory fields and press Return after each
entry:
Field
Description
Input
IP Interface
Name of the interface.
s1c (DSL port 1)
Peer IP Address
IP address associated with
the other end of the link; i.e.
the 5446 RTU.
nnn.nnn.nnn.nnn format *
Route to Peer
Routing method to use to
get to peer (i.e., host or
net).
Host
* The subnet mask can be changed for the corresponding 5446 RTU. Refer to
Appendix G, 5446 RTU MIB Descriptions.
NOTE:
Do not enter a local IP address. The DSL interface is “unnumbered,”
meaning it requires no IP address. (You cannot change this field.)
In addition, the following fields also appear on the screen. These fields can
be used to customize your application.
Field
Description
Input
Input Filter
Prevents packets from
entering the DSL card
through a specified interface.
Blank to disable.
Output Filter
Prevents packets from going Blank to disable.
out of the DSL card through a
specified interface.
3. Repeat the above procedure for interfaces s1d, s1e, and s1f (DSL ports 2, 3,
and 4, respectively).
4. Press Ctrl-z to return to the Configuration → Interfaces menu.
8000-A2-GB20-10
June 1997
4-11
Configuring the HotWire DSLAM
Configuring a Static Route to the Network Management System
on each DSL Card
Use this procedure to enable the management traffic from the DSL cards or
5446 RTUs to be routed back through the MCC.
Procedure
To configure a static route to the Network Management System (NMS) on each
DSL card:
1. Select Configuration → IP Router → Static_Routes (A-E-A).
2. Press Return on the Item 0 field to add a new record.
3. Enter values for the following fields and press Return after each entry:
Field
Description
Input
Host/Net
Destination of the route.
0.0.0.0 to indicate the
default route
Subnet Mask
Associated subnet mask
for the specified
destination IP address.
nnn.nnn.nnn.nnn format
Next Hop
IP address of the next hop
device for the specified
destination.
nnn.nnn.nnn.nnn format
Pref (Preference)
Measure of how preferable
one route is to another, if
you have two routes going
to the same destination.
(The lower the number, the
more preferable the route.)
This route is compared to
other routes for the same
destination address.
1
S/D (Source/Destination)
Source or destination route Default = Dst
type.
PA (Proxy ARP)
Router answers ARP
requests intended for
another machine.
Default = No
4. Confirm the save and press Ctrl-z to return to the Configuration → IP Router
menu.
4-12
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
Assigning IP Addresses to the DSL Card LAN
Use this procedure to give DSL cards a LAN Interface IP address in each Internet
Service Provider (ISP) domain supported by those cards.
Procedure
To assign IP addresses to the DSL Card LAN:
1. Select Configuration →Interfaces → IP Network (A-C-B).
2. Enter values for the following fields and press Return after each entry:
Field
Description
Input
IP Interface
Name of the interface.
e1a (Ethernet port)
IP Address (for
each DSL card)
IP address for each DSL card
in the system. This address
must be different that the
management domain IP
address.
nnn.nnn.nnn.nnn format.
(Subnet is predetermined –
you can enter the host
number.)
Peer IP Address
IP address associated with
the other end of the link.
nnn.nnn.nnn.nnn format *
Subnet Mask
Associated subnet mask for
the specified destination IP
address.
nnn.nnn.nnn.nnn format
Route to Peer
Routing method used to get
to peer (i.e., host or net).
Net
* Enter the network/subnetwork portion of the Base IP address, with 0 for the
host portion so that the Peer is the entire subnet.
In addition, the following fields also appear on the screen. These fields can
be used to customize your application.
Field
Description
Input
Input Filter
Prevents packets from
entering the DSL card
through a specified interface.
Blank to disable.
Output Filter
Prevents packets from going Blank to disable.
out of the DSL card through a
specified interface.
3. Press Ctrl-z to return to the Configuration →Interfaces menu.
8000-A2-GB20-10
June 1997
4-13
Configuring the HotWire DSLAM
Configuring Static Routes to End Users on each DSL Card
Use this procedure to enable the management traffic from the DSL cards to the
5446 RTU and attached end-user systems. Use SNMP to download the needed
enterprise MIBs and to configure static routes to end users attached to each 5446
RTU. Refer to Appendix G, 5446 RTU MIB Descriptions.
NOTE:
Each time you create a static route for an end-user system behind an RTU,
you should also create a corresponding source based input filter rule. See
Chapter 7, IP Filtering, of the HotWire Digital Subscriber Line Access
Multiplexer (DSLAM) Network Configuration Guide and Chapters 5 and 6, IP
Router Filters.
Procedure
To configure a static route to End Users:
1. Select Configuration → IP Router →Static Routes (A-E-A).
2. Press Return on the Item 0 field to add a new record.
3. Enter values for the following fields and press Return after each entry:
Field
Description
Input
Host/Net
Destination of the route.
0.0.0.0 to indicate the
default route
Subnet Mask
Associated subnet mask
for the specified
destination IP address.
nnn.nnn.nnn.nnn format
Next Hop
IP address of the next hop
device for the specified
destination.
nnn.nnn.nnn.nnn format
Pref (Preference)
Measure of how preferable
one route is to another, if
you have two routes going
to the same destination.
(The lower the number, the
more preferable the route.)
This route is compared to
other routes for the same
destination address.
1
S/D (Source/Destination)
Source or destination route Default = Dst
type.
PA (Proxy ARP)
Router answers ARP
requests intended for
another machine.
Default = No
4. Confirm the save and press Ctrl-z to return to the Configuration → IP Router
menu.
4-14
June 1997
8000-A2-GB20-10
Configuring the HotWire DSLAM
Creating Default Route or Source Route on the DSL
Use this procedure to create a default route or source route for each DSL card
(upstream direction).
Procedure
To create default routes or source routes on the DSL:
1. Select Configuration → IP Router → Static Routes (A-E-A).
2. Press Return on the Item 0 field to add a new record.
3. Enter values for the following fields and press Return after each entry.
Field
Description
Input
Host/Net
Destination of the route.
0.0.0.0 to indicate the
default route
Subnet Mask
Associated subnet mask
for the specified
destination IP address.
nnn.nnn.nnn.nnn format
Next Hop
IP address of the next hop
device for the specified
destination.
nnn.nnn.nnn.nnn format
Pref (Preference)
Measure of how preferable
one route is to another, if
you have two routes going
to the same destination.
(The lower the number, the
more preferable the route.)
This route is compared to
other routes for the same
destination address.
1
S/D (Source/Destination)
Source or destination route Default = Dst
type.
PA (Proxy ARP)
Router answers ARP
requests intended for
another machine.
Default = No
4. Confirm the save and press Ctrl-z to return to the Configuration → IP Router
menu.Resetting the DSL Card
8000-A2-GB20-10
June 1997
4-15
Configuring the HotWire DSLAM
Resetting the DSL Card
After configuring the DSL cards, reset the card.
Procedure
To reset the DSL Card:
1. Select Configuration → Card Status→ Card Reset (A-A-F).
2. Enter DSLnn, where nn is the slot number for the DSL card you just
configured.
3. Enter Y at the prompt to confirm.
NOTE:
When you enter Y, all data connectivity is interrupted.
4. If you have entered yes, verify that the LEDs on the DSL card go through
the reset sequence once, and then a second time after approximately
10 seconds (BOOTP).
4-16
June 1997
8000-A2-GB20-10
MCC Card Configuration
5
Overview
This chapter describes the non-mandatory configuration options on the MCC
card. Use these options to customize your applications.
MCC Configuration Card Status Screens
Use the system information sub-menu of the Card Status screens to configure
basic MCC card-level information.
NOTE:
Only a user who logs on to the HotWire DSLAM with Administrative
permission can configure the MCC card.
8000-A2-GB20-10
June 1997
5-1
MCC Card Configuration
Procedure
To configure card information, DNS setup, time/date, clear NVRAM, upload or
download configuration set, download new firmware, or reset card:
1. Follow this menu sequence:
Configuration → Card Status (A-A)
2. The Card Status menu appears. Enter the desired value on each selected
screen and field and press Return.
Table 5-1. Card Status Menu Options (1 of 4)
Card Info (System Information)
A-A-A
Gives the user the ability to configure basic card-level information.
System Name – 16 alphanumeric characters. Name assigned to the card.
System Contact – 32 alphanumeric characters. Name or number of party responsible
for card.
System Location – 16 alphanumeric characters. Location assigned to the system.
Router ID – nnn.nnn.nnn.nnn format. Diagnostic Domain IP address assigned to card.
Router Subnet Mask – nnn.nnn.nnn.nnn format.
Local Control Terminal Port Mode – Standard/Extended (Default = Standard).
Standard is for USA keyboards; Extended is for European keyboards.
Remote Control Terminal Port Mode – Standard/Extended (Default = Standard).
Standard is for USA keyboards; Extended is for European keyboards.
Telnet daemon tcp port – 0-65536 (Default = 23).
Alarm on loss of Redundant Power – Y if carrier has redundant power and you want
local and remote indications of the loss of one power source.
NOTE:
If you have made changes to the Router ID and Router Subnet Mask fields,
you must also change the Base IP Address and Base Subnet Mask on the
e1a (ethernet) interface (A-C-B) and do a card reset.
DNS Setup (Configure DNS)
A-A-B
Gives the user the ability to configure the access to DNS servers from which requests
are made.
DNS Servers – Three entry fields in nnn.nnn.nnn.nnn format. Enter the primary Domain
Name System Server address.
Default Domain Name – 40 characters. Domain used for queries that are not fully
qualified. For example, if the default domain name = paradyne.com and a telnet is
attempted to reach a system called gemini, the card would query the DNS server for
gemini.paradyne.com.
Time to wait for response (secs)– 1–300 seconds (Default = 5). Enter the time to wait
for a response.
Number of times to retry server – 1–10 times (Default = 2). Enter the number of times
to retry the server.
5-2
June 1997
8000-A2-GB20-10
MCC Card Configuration
Table 5-1. Card Status Menu Options (2 of 4)
Time/Date
A-A-C
Gives the user the ability to configure the local time and date on the DSL card.
Local Time/Date – Enter the time in hh.mm format (am or pm). Enter the date in
mm/dd/yy format.
Client NTP Mode – Broadcast/Unicast (Default = Broadcast). Select the Client Network
Time Protocol Mode.
NTP Server – nnn.nnn.nnn.nnn format. Enter the NTP Server IP address.
Synchronized(hrs) – 1–24 (Default = 1). Enter the hours between synchronization.
NVRAM Clear Screen (Clear NVRAM)
A-A-D
Gives the user the ability to clear out the Non-Volatile RAM (NVRAM) in order to reuse
the card or to reconfigure the current card.
NOTE:
8000-A2-GB20-10
If you select yes on this screen, you will permanently remove most of the
configuration information you have stored on this card and all IP addresses
and routing tables will have to be re-entered. The system will perform a
reset and return to the factory configuration.
June 1997
5-3
MCC Card Configuration
Table 5-1. Card Status Menu Options (3 of 4)
NVRAM Config Loader
A-A-E
Gives the user 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 pathname expression of
directory names separated by a forward slash (/) ending with the file name. The total
pathname length must be less than 40 characters. If the TFTP server is hosted by a
DOS machine, then directory and file names must follow the 8.3 naming convention
imposed by DOS.
DOS Machine
If your server is hosted by a DOS machine, you must name the file to be uploaded using
the DOS convention eight character length. The system will automatically upload the
configuration file and create directories and file names as needed.
UNIX Machine
If your server is hosted by a UNIX machine, the configuration file you name will not be
created on the UNIX system by the TFTP server. It is critical that you work with your
system administrator to plan the naming conventions for directories, filenames, and
permissions so that anyone using the system has read and write permissions. (This is a
UNIX system security feature.)
NOTE:
This must be done before you can upload files to a UNIX server.
TFTP Server IP Address – nnn.nnn.nnn.nnn format.
TFTP Transfer Direction – Upload/Download (Default = Upload). Select Upload to
store a copy of the card’s configuration on the server. Select Download to have the file
server send a new copy of the card’s configuration to the card.
Start Transfer – Yes/No (Default = no).
Packets Sent – Number of packets sent in download.
Bytes Sent – Number of bytes sent in download.
Bytes Received – Number of bytes received in download.
Transfer Status – Status of the upload or download transfer.
NOTE:
After a download, the card must be reset for the new configuration to take
effect.
Card Reset (Reset System)
A-A-F
Gives the user the ability to reset the card. This resets all counters and if a new
configuration or software version has been downloaded, the new code will then become
active.
Reset Card – Enter yes to reset card.
NOTE:
This action disrupts the data flow for at least 10 seconds.
Download Code (Download Code and Apply Download)
A-A-G
Gives the user the ability to download a new version of code and apply the downloaded
code. For further information on this feature, see Appendix D.
5-4
June 1997
8000-A2-GB20-10
MCC Card Configuration
Table 5-1. Card Status Menu Options (4 of 4)
Download Code
A
This screen is similar to the NVRAM Config Loader screen.
Image File Name – The file name may be a regular pathname expression of directory
names separated by a forward slash (/) ending with the file name. The total pathname
length must be less than 40 characters. If the TFTP server is hosted by a DOS
machine, then directory and file names must follow the 8.3 naming convention imposed
by DOS.
TFTP Server IP Address – nnn.nnn.nnn.nnn format.
Start Transfer – Yes/No (Default = no).
Packets Sent – Number of packets sent in download.
Packets Received – Number of packets received in download.
Bytes Sent – Number of bytes sent in download.
Bytes Received – Number of bytes received in download.
Transfer Status – Status of the download transfer.
Once the download is complete, press Ctrl-z to exit back to the Download Code
submenu and select Apply Download.
Apply Download
B
This selection applies the downloaded code and drops all connections by performing a
device reset. This screen is used to overlay the previously downloaded image for the
card. If you select yes at the Reset System prompt, the system goes through a system
restart and interrupts service on the card. For further information on this feature, see
Appendix D.
8000-A2-GB20-10
June 1997
5-5
MCC Card Configuration
MCC Configuration Ports Screens
Use the system information sub-menu of the Ports screens to display the
Ethernet Ports screen.
Procedure
To configure the Ethernet port:
1. Follow this menu sequence:
Configuration → Ports (A-B)
2. The Ports menu appears. Enter the desired value on each selected screen
and field and press Return.
Table 5-2. Ports Menu Options
Ethernet Ports
A-B-A
Gives the user the ability to configure the Ethernet (LAN) port on the card.
Function – Edit/Reset. Select Edit to configure the Ethernet port or Reset if you have
made changes.
Port Name – Seven alphanumeric characters (e1a is only valid selection).
SQE (Signal Quality Error) test – Enable/Disable (Default = Disable) the test.
NOTE:
5-6
If you have made changes to this screen, you must do a card reset or
restart the Ethernet Interface.
June 1997
8000-A2-GB20-10
MCC Card Configuration
MCC Configuration Interfaces Screens
Use the system information sub-menu of the Interfaces screens to configure
basic interface information.
Procedure
To configure general interfaces, IP networks, and control interfaces:
1. Follow this menu sequence:
Configuration → Interfaces (A-C)
2. The Interfaces menu appears. Enter the desired value on each selected
screen and field and press Return.
Table 5-3. Interfaces Menu Options (1 of 2)
General (Interfaces)
A-C-A
Gives the user the ability to configure basic information about a given interface.
Interface Name – 15 characters. s1b = backplane that connects all the cards,
e1a = ethernet port.
Type – Static.
Protocol – Type of protocol for an interface.
Port List – Name of the port.
MTU (max) (Maximum Transmission Unit)– 64-64000 (Default = 1500)
NOTE:
These are the only values you may enter. Do not change the MTU of s1b
from the default of 1500. Make certain that if you change from the default
value, the numbers are appropriate to your network. Do a card reset or
reset the interface.
IP Network
A-C-B
Gives the user the ability to configure up to 16 IP addresses for the LAN port.
IP Interface – 15 characters. s1b = backplane that connects all cards; e1a = ethernet
port.
Base IP Addr – nnn.nnn.nnn.nnn format.
Base Subnet Mask – nnn.nnn.nnn.nnn format.
IP Addr – nnn.nnn.nnn.nnn format. You may enter up to 16 addresses. Only appears if
e1a is the IP interface name.
Subnet Mask – nnn.nnn.nnn.nnn format. You may enter up to 16 addresses. Only
appears if e1a is the IP interface name.
Input Filter – Optional.
Output Filter – Optional.
Peer IP Address – nnn.nnn.nnn.nnn format. Only appears if s1b is the interface name.
Route to Peer – Net. Only appears of s1b is the interface name.
NOTE:
8000-A2-GB20-10
If you have made any changes to this screen, you must do a card reset or
restart the Ethernet interface.
June 1997
5-7
MCC Card Configuration
Table 5-3. Interfaces Menu Options (2 of 2)
Control (Control Interface)
A-C-C
Gives the user the ability to restart, stop, and monitor (up, down, or testing) the current
state of an interface.
This screen is populated depending on your entry in the Command and Interface Name
fields. For example, if you select Monitor mode and enter s1b for the Interface name,
the following information is displayed: Type, State, Link Protocol, IP State, Uptime,
Inactive, Connect Time, Port, Local IP Addr, and Peer IP Addr.
5-8
June 1997
8000-A2-GB20-10
MCC Card Configuration
MCC Configuration Users Screens
Use the system information sub-menu of the Users screens to configure login
accounts for local terminal and telnet sessions.
Procedure
1. Follow this menu sequence:
Configuration → Users (A-D)
2. The Users menu appears. Enter the desired values on this screen and fields
and press Return.
Table 5-4. Users Menu Options
Users (Configure Account)
A-D-A
Gives the user the ability 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.
User accounts provide security for the DSLAM by requiring that anyone who is trying to
log onto the system has a valid password to gain access. User accounts on the MCC
provide security to users accessing the system from the VT100 terminal interface and
via Telnet over the management domain LAN.
It is recommended that user accounts also be set up for each DSL card, even if you do
not intend to telnet directly to the DSL cards, so that no unauthorized telnet sessions
can be made. Each card will support up to 10 user accounts with either Operator (read
only) or Administrator (read/write) permissions.
If you configure an account on the MCC card, you have privileges on both the MCC and
DSL cards.
If you configure an account on the DSL card, you only have privileges for that specific
DSL card.
Action – Add/Edit/Delete.
Login ID – Enter your Login ID.
Password – Enter the password associated with the login ID.
Repeat Password – Re-enter the password.
Privilege – Operator/Administrator. Enter Operator for read only access; enter
Administrator for complete system access.
NOTE:
8000-A2-GB20-10
Use Ctrl-v to see a list of all user accounts at the Login ID prompt.
June 1997
5-9
MCC Card Configuration
MCC Configuration IP Router Screens
Use the system information sub-menu of the IP Router screens to configure static
routes to protocols and filters.
Procedure
To configure static routes, martian networks, and IP router filters:
1. Follow this menu sequence:
Configuration → IP Router (A-E)
2. The IP Router menu appears. Enter the desired values on this screen and
fields and press Return.
Table 5-5. IP Router Menu Options (1 of 3)
Static Routes
A-E-A
Gives the user the ability to add or delete static routes in the system.
Item – Press Return on 0 field to add entry.
Host/Net – nnn.nnn.nnn.nnn format or space to delete entry.
Subnet Mask – Associated subnet mask for the specified destination IP address.
Next Hop – nnn.nnn.nnn.nnn format.
Pref– Measure of how preferable one route is 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.
S/D (Source/Destination) – Source or destination IP address of the packet.
PA (Proxy ARP) – Router answers ARP requests intended for another machine.
NOTE:
When you define a source route, the Proxy ARP field is no longer
selectable.
Martian Networks
A-E-B
Gives the user the ability to configure addresses that the system recognizes as invalid.
Item – Press Return on 0 field to add 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. Enter IP mask of unwanted source.
NOTE:
5-10
The system is shipped with default martian networks. It is recommended
that you do not remove entries. If you have made changes to this screen,
you must do a card reset.
June 1997
8000-A2-GB20-10
MCC Card Configuration
Table 5-5. IP Router Menu Options (2 of 3)
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. The filter then performs the action specified by the
rule on that packet, which can be either to forward or discard the packet.
Rules apply to the source and destination ports going to the end-user system. You may
have up to 33 rules per filter, but the greater number of rules, the lesser the
performance of the router filter.
For additional information on IP Router filters, see Chapter 7, IP Filtering, of the HotWire
Digital Subscriber Line Access Multiplexer (DSLAM) Network Configuration Guide.
Action – Add/Delete/Edit.
Filter Name – Up to 16 characters (optional).
Rule # – Up to 33 rules can be configured for each filter. This number is automatically
assigned.
# of Rules – Number of rules that apply to this port.
Source Address – nnn.nnn.nnn.nnn format.
Source Address Mask – nnn.nnn.nnn.nnn format. If you specify a source subnet mask
of 0.0.0.0, the system skips the source address comparison.
Source Port No – 0–65536 (Default = 0). If the source port number is 0, the system
filters ICMP packets in addition to the packet types defined in the rule.
Comparison Type – Ignore – Do not do a comparison. To do a comparison on the port
number specified in the packet and the rule, specify one of the following: EQ – Equal to,
NRQ – Not Equal To, GT – Greater than, LT – Less than, In_Range – Witnin the
specified range, Out_Range – Outside of the specified range.
Destination Address – nnn.nnn.nnn.nnn format.
Destination Address Mask – nnn.nnn.nnn.nnn format. If you specify a destination
subnet mask of 0.0.0.0, the system skips the destination address comparison.
Destination Port No – 0–65536 (Default = 0). If the source port number is 0, the
system filters ICMP packets in addition to the packet types defined in the rule.
Comparison Type – Ignore – Ignore ports, EQ – Equal to, NRQ – Not Equal To, GT –
Greater than, LT – Less than, In_Range – Maximum source port, Out_Range –
Minimum source port.
Filter Action – Discard (Packet)/Forward (Packet).
Delete Rule – Yes/No.
Go to Next Rule – Yes/No.
NOTE:
8000-A2-GB20-10
You have to reset the IP Router (A-E-F) for any changes to take effect.
June 1997
5-11
MCC Card Configuration
Table 5-5. IP Router Menu Options (3 of 3)
ARP (Parameters, Add Entry, and Delete Entry)
A-E-D A,B, or C
Select:
Parameters (A)
Gives the user the ability to configure general Address Resolution Protocol (ARP) cache
parameters.
Complete Entry Timeout (minutes) – 1–200,000 (Default = 20).
Incomplete Entry Timeout (minutes) – 1–200,000 (Default = 20).
NOTE:
If you have made changes to this screen, you must do a card reset.
Add Entry (B)
Gives the user the ability to add entries into the ARP cache.
IP Address/Host Name – nnn.nnn.nnn.nnn format.
MAC Address – xx-xx-xx-xx-xx-xx format.
Trailers – Yes/No (Default = No).
Proxy – Yes/No (Default = No).
Add Entry? – Enter yes to add an entry or exit.
Add Another Entry? – Enter yes to add another entry.
Delete ARP Entry (C)
Gives the user the ability to delete entries line by line in the ARP cache. The screen
displays columns for Line, IP Address, Ethernet Address, Min, and Delete.
Select the line you want to delete, select yes and press Return.
NOTE:
For the Add and Delete Entry screens, any information entered is not
stored in the NV memory and will be lost when you reset the card.
Host Table (IP Host Table)
A-E-E
Gives the user the ability to define mappings between IP addresses and end user host
names (names of host devices located at the customer’s site).
Enter the IP Address and Host Name in nnn.nnn.nnn.nnn format and press Return after
each entry.
NOTE:
5-12
You have confirm the save for any changes to take effect.
June 1997
8000-A2-GB20-10
MCC Card Configuration
MCC Configuration SNMP Screens
Use the system information sub-menu of the SNMP screens to configure SNMP
security, logical entities, community names, and trap addresses.
" Procedure
To configure SNMP security, SNMP Logical entities, and SNMP
Communities/Traps:
1. Follow this menu sequence:
Configuration → SNMP (A-F)
2. The IP Router menu appears. Enter the desired values on this screen and
fields and press Return.
Table 5-6. SNMP Menu Options (1 of 2)
Security (SNMP Security)
A-F-A
Gives the user the ability to configure allowable NMS IP addresses and to configure
SNMP agent.
Although SNMP community strings (if they are changed from the defaults) provide a
measure of security for unauthorized managers, enabling IP address security and
entering the IP address of up to five authorized SNMP managers provides a much
higher level of security. When IP address security is enabled, the source address of any
SNMP message addressed to any of the card’s IP addresses (in either the management
or customer domain) will be chacked against the authorized list and will be disabled if
there is no match.
IP Address Security – Enable/Disable (Default = Disable).
H Enabling allows DSLAM to accept SNMP messages from SNMP managers whose
IP source addresses have been entered in the IP Address field. Enabling allows
SNMP agent an additional level of security besides community names.
H Disabling stops IP address checkingand allows the card to respond to a SNMP
query from any source..
IP Address – nnn.nnn.nnn.nnn format. Enter up to five IP source addresses of NMS
managers.
Access – ReadOnly(ro)/ReadWrite(rw)/NoAccess(na). Permissions to be granted to
NMS manager.
Logical Entities (SNMP Logical Entities)
A-F-B
This screen displays information on the logical table of the Entity MIB. Only the
Community Name field can be edited; others are read only.
H I (Index) column shows the index number of DSL ports two to five.
H T (Type) column shows “Remote”.
H Read Only Comm and Read Write Comm show the community strings of the
RTU attached to this port. It is used when the DSLAM downloads configuration
data to the RTU in a future release.
Logical Entities 2 (SNMP Logical Entities 2)
A-F-C
Continuation of previous screen.
8000-A2-GB20-10
June 1997
5-13
MCC Card Configuration
Table 5-6. SNMP Menu Options (2 of 2)
Communities/Traps (SNMP Communities/Traps)
A-F-D
Gives the user the ability to enable the Authentication Failure Trap Mechanism, stores
SNMP Community string names for the DSL card, and stores NMS host IP addresses to
which the DSLAM sends trap messages.
It also lets the user configure four communities with three trap destinations that can be
configured for each of those communities.
Authentication Failure Trap – Enable to send a trap when a SNMP request community
string does not match or when the password for a Telnet session is incorrect.
Community Name – 32 characters, up to four unique entries per screen. Default
names are public (ro), MCC (rw), NMS (rw), NMS-2 (ro).
Access – ReadOnly(ro)/ReadWrite(rw)/NoAccess(na), up to four entries per screen.
IP Address – nnn.nnn.nnn.nnn format. Enter NMS system host address.
Input Number (port) – nnn format. Enter NMS system port number.
Send Traps – Set to E to Enable. Set to D to disable.
5-14
June 1997
8000-A2-GB20-10
MCC Card Configuration
MCC DSL Cards Screen
Use the system information sub-menu of the DSL Cards screen to set IP
addresses and reset the DSL cards.
Procedure
To Configure DSL IP addresses and Reset DSL Slot:
1. Follow this menu sequence:
Configuration → DSL Cards (A-G)
2. The DSL Cards menu appears. Enter the desired values on this screen and
fields and press Return.
Table 5-7. DSL Options
Set IP Address (Configure DSL IP Addr)
A-G-A
Gives the user the ability to configure up to 18 IP addresses, one for each slot in the
DSLAM that has a DSL card. These are addresses for the s1b backplane interface on
each DSL card and will be automatically assigned to the DSL card when it is inserted in
a slot. All IP addresses must be on the same Management Domain Subnet as the
MCC’s IP address (entered on the MCC’s IP Network screen A-C-B).
DSL Card Subnet Mask – nnn.nnn.nnn.nnn format.
Slot – Slot number of the DSL card.
IP Address – nnn.nnn.nnn.nnn format. (Subnet is predetermined – you can enter the
host number.)
NOTE:
If you have made changes to this screen, you must do a card reset or
restart the s1b interface.
Reset Slot (Reset DSL Slot)
A-G-B
Gives the user the ability to perform a reset of a DSL card in any DSLAM slot. This reset
should be performed if there is a card in a slot but it does not appear on the DSLAM
card selection screen. (After entering the card number and confirming the reset, the
MCC sends a reset signal via the backplane to the selected card.)
NOTE:
8000-A2-GB20-10
If a DSL card has been reset but still does not appear on the screen, its
configuration may have been corrupted and the card should be reset again
this time answering yes at the Clear NVRAM prompt. If the card then
appears on the screen it will have to be reconfigured. If the card does not
appear on the screen, it should probably be replaced.
June 1997
5-15
DSL Card Configuration
6
Overview
This chapter describes the non-mandatory configuration options on the DSL card.
Use these options to customize your applications.
DSL Configuration Card Status Screens
Use the system information sub-menu of the Card Status screens to configure
basic DSL card-level information.
NOTE:
Only a user who logs on to the HotWire DSLAM with Administrative
permission can configure the DSL cards.
8000-A2-GB20-10
June 1997
6-1
DSL Card Configuration
Procedure
To configure card info, DNS setup, time/date, clear NVRAM, upload or download
configuration set, download new firmware, or reset card:
1. Follow this menu sequence:
Configuration → Card Status (A-A)
2. The Card Status menu appears. Enter the desired value on each selected
screen and field and press Return.
Table 6-1. Card Status Options (1 of 4)
Card Info (System Information)
A-A-A
Gives the user the ability to configure basic card-level information.
System Name – 16 alphanumeric characters. Name assigned to the card.
System Contact – 32 alphanumeric characters. Name or number of party responsible
for card.
System Location – 16 alphanumeric characters. Location assigned to the system.
Router ID – nnn.nnn.nnn.nnn format. (This field is read only.) Diagnostic Domain IP
address assigned to card.
Router Subnet Mask – nnn.nnn.nnn.nnn format. (This field is read only.)
Local Control Terminal Port Mode – Standard/Extended (Default = Standard).
Standard is for USA keyboards; Extended is for European keyboards.
Remote Control Terminal Port Mode – Standard/Extended (Default = Standard).
Standard is for USA keyboards; Extended is for European keyboards.
Telnet daemon top port – 0-65536 (Default = 0).
DNS Setup (Configure DNS)
A-A-B
Gives the user the ability to configure the access to DNS servers from which requests
are made.
DNS Servers – Three entry fields in nnn.nnn.nnn.nnn format. Enter the primary Domain
Name System Server address.
Default Domain Name – 40 characters. Domain used for queries that are not fully
qualified. For example, if the default domain name = paradyne.com and a telnet is
attempted to reach a system called gemini, the card would query the DNS server for
gemini.paradyne.com.
Time to wait for response – 1–300 seconds (Default = 5). Enter the time to wait for a
response.
Number of times to retry server – 1–10 times (Default = 2). Enter the number of times
to retry the server.
6-2
June 1997
8000-A2-GB20-10
DSL Card Configuration
Table 6-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 DSL card.
Local Time/Date – Enter the time in hh.mm format (am or pm). Enter the date in
mm/dd/yy format.
Client NTP Mode – Broadcast/Unicast (Default = Broadcast). Select the Client Network
Time Protocol (NTP) Mode.
NTP Server – nnn.nnn.nnn.nnn format. Enter the NTP Server IP address.
Synchronized(hrs) – 1–24 (Default = 1). Enter the hours between synchronization.
NOTE:
At system boot time, the time on the DSL cards automatically syncs with
the MCC card. Therefore it is usually not necessary to use this screen on
the DSL.
NVRAM Clear Screen (Clear NVRAM)
A-A-D
Gives the user the ability to clear out the Non-Volatile RAM (NVRAM) in order to reuse
the card or to reconfigure the current card.
NOTE:
8000-A2-GB20-10
If you select yes on this screen, you will permanently remove most of
the configuration information you have stored on this card and all IP
addresses and routing tables will have to be re-entered. The system will
perform a reset and return to the factory configuration.
June 1997
6-3
DSL Card Configuration
Table 6-1. Card Status Options (3 of 4)
NVRAM Config Loader
A-A-E
Gives the user 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 pathname expression of
directory names separated by a forward slash (/) ending with the file name. The total
pathname length must be less than 40 characters. If the TFTP server is hosted by a
DOS machine, then directory and file names must follow the 8.3 naming convention
imposed by DOS.
DOS Machine
If your server is hosted by a DOS machine, you must name the file to be uploaded using
the DOS convention eight character length. The system will automatically upload the
configuration file and create directories and file names as needed.
UNIX Machine
If your server is hosted by a UNIX machine, the configuration file you name will not be
created on the UNIX system by the TFTP server. It is critical that you work with your
system administrator to plan the naming conventions for directories, filenames, and
permissions so that anyone using the system has read and write permissions. (This is a
UNIX system security feature.)
NOTE:
This must be done before you can upload files to a UNIX server.
TFTP Server IP Address – nnn.nnn.nnn.nnn format.
TFTP Transfer Direction – Upload/Download (Default = Upload). Select Upload to
store a copy of the card’s configuration on the server. Select Download to have the file
server send a new copy of the card’s configuration to the card.
Start Transfer – Yes/No (Default = no).
Packets Sent – Number of packets sent in download.
Bytes Sent – Number of bytes sent in download.
Bytes Received – Number of bytes received in download.
Transfer Status – Status of the upload or download transfer.
NOTE:
After a download, the card must be reset for the new configuration to take
effect.
Card Reset (Reset System)
A-A-F
Gives the user the ability to reset the card. This resets all counters and if a new
configuration or software version has been downloaded, the new code will then become
active.
NOTE:
6-4
This action disrupts the data flow for at least 10 seconds.
June 1997
8000-A2-GB20-10
DSL Card Configuration
Table 6-1. Card Status Menu Options (4 of 4)
Download Code (Download Code and Apply Download)
A-A-G
Gives the user the ability to download a new version of code and apply the downloaded
code. For further information on this feature, see Appendix D.
Download Code
A
This screen is similar to the NVRAM Config Loader screen.
Image File Name – The file name may be a regular pathname expression of directory
names separated by a forward slash (/) ending with the file name. The total pathname
length must be less than 40 characters. If the TFTP server is hosted by a DOS
machine, then directory and file names must follow the 8.3 naming convention imposed
by DOS.
TFTP Server IP Address – nnn.nnn.nnn.nnn format.
Start Transfer – Yes/No (Default = no).
Packets Sent – Number of packets sent in download.
Packets Received – Number of packets received in download.
Bytes Sent – Number of bytes sent in download.
Bytes Received – Number of bytes received in download.
Transfer Status – Status of the download transfer.
Once the download is complete, press Ctrl-z to exit back to the Download Code
submenu and select Apply Download.
Apply Download
B
This selection applies the downloaded code and drops all connections by performing a
device reset. This screen is used to overlay the previously downloaded image for the
card. If you select yes at the Reset System prompt, the system goes through a system
restart and interrupts service on the card. For further information on this feature, see
Appendix D.
DSL Configuration Ports Screens
Use the system information sub-menu of the Ports screens to display the
Ethernet Ports and DSL Ports screens.
Procedure
To configure Ethernet ports and DSL interfaces:
1. Follow this menu sequence:
Configuration → Ports (A-B)
2. The Ports menu appears. Enter the desired value on each selected screen
and field and press Return.
8000-A2-GB20-10
June 1997
6-5
DSL Card Configuration
Table 6-2. Ports Options
Ethernet Ports
A-B-A
Gives the user the ability to configure the Ethernet (LAN) port on the card.
Action – Edit/Reset. Select Edit to configure the Ethernet port or Reset if you have
made changes.
Port Name – Seven alphanumeric characters (e1a is the only valid selection).
(SQE) Signal Quality Error test – Enable/Disable (Default = Disable).
NOTE:
If you have made changes to this screen, you must do a card reset or
restart the Ethernet Interface.
DSL Ports (DSL Parameters)
A-B-B
Action – Edit/Reset. Edit to configure the DSL ports, Reset to reset the port and make
changes active.
Port # –Enter port 1 to 4.
Port Desc – 40 characters (User Name, telephone number, etc.).
Startup Margin – Value between –3 and 9. In Adaptive Mode, if the margin falls below
SM, the DSL link will be restarted at a slower speed. If the margin increases above SM
by six db, the speed will increase.
Behavior – Fixed/Adaptive (Default = Fixed). In fixed mode, the DSL will operate at
only one set of up/down speeds. In rate adaptive mode, the rates will vary between the
min and max speed as the transmission characteristics of the loop change.
Fixed: Up Speed – 1088/952/816/680/544/408/272 (Default = 1088). Enter the fixed up
speed.
Fixed: Down Speed – 2560/2240/1920/1600/1280/960/640 (Default = 2560). Enter the
fixed down speed.
Adaptive: Max Up Speed – 1088/952/816/680/544/408/272 (Default = 1088). Enter the
maximum up speed.
Adaptive: Min Up Speed – 1088/952/816/680/544/408/272 (Default = 272). Enter the
minimum up speed.
Adaptive: Max Dn Speed – 2560/2240/1920/1600/1280/960/640 (Default = 2560).
Enter the maximum down speed.
Adaptive: Min Dn Speed – 2560/2240/1920/1600/1280/960/640 (Default = 640). Enter
the minimum down speed.
Margin Threshold: – Sends a trap message if margin falls below a selected value.
Enter a value for the margin threshold trap (–5 to +10 db) (Default = +3). Enter D to
disable trap.
Link Down Ct: – Sends a trap message if the number of DSL link down events in
15 minutes exceeds the selected value. Enter a value for the Link Down Count Trap (0
to 1000). Enter D to disable trap.
Error Rate (secs) – Sends a trap message if the Block Error Rate averaged over a
10-second period exceeds the selected value. Enter a value for the threshold (10 to
100,000 good blocks per block in error) (Default = 1,000 approximates bit error, rate of
10-6). Enter D to disable trap.
Error Rate (hr) – Sends a trap message if the Block Error Rate averaged over a one
hour period exceeds the selected value. Enter a value for the threshold (10 to 100,000
good blocks per block in error) (Default = 10,000 approximates bit error, rate of 10-7).
Enter D to disable trap.
NOTE:
6-6
If you have made changes to this screen, select Reset in the Action field to
make the change active.
June 1997
8000-A2-GB20-10
DSL Card Configuration
DSL Configuration Interfaces Screens
Use the system information sub-menu 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. Enter the desired value on each selected
screen and field and press Return.
Table 6-3. Interfaces Options (1 of 3)
General (Interfaces)
A-C-A
Gives the user the ability to view basic card interface information or to configure
Maximum Transfer Units (MTUs).
Interface Name – 15 characters. s1b = backplane that connects all the cards,
e1a = ethernet port, s1c, s1d, s1e and s1f = DSL ports. Depending on your selection in
this field, the following pre-populated fields appear:
Type – Static or dynamic.
Protocol – HDLC, PPP, or Ether.
Port List – e1a, s1b, s1c, s1d, s1e, s1f.
MTU (max) – 64-64000 (Default = 1500).
NOTE:
8000-A2-GB20-10
These are the only values you may enter. Do not change the MTU of s1b
from the default of 1500. Make certain that if you change from the default
value, the new numbers are appropriate to your network. Do a card reset or
reset the Ethernet interface.
June 1997
6-7
DSL Card Configuration
Table 6-3. Interfaces Options (2 of 3)
IP Network
A-C-B
Gives the user the ability to configure up to 16 IP addresses for a port.
IP Interface – 15 characters. s1b = backplane, e1a = ethernet port, s1c, s1d, s1e, and
s1f = DSL ports.
Base IP Addr – nnn.nnn.nnn.nnn format.
Base Subnet Mask – nnn.nnn.nnn.nnn format.
IP Addr – nnn.nnn.nnn.nnn format. (You may enter up to 16 addresses for LANs.) Only
appears if e1a is the IP interface name.
Subnet Mask – nnn.nnn.nnn.nnn format. (You may enter one for each address above.)
Only appears if e1a is the IP interface name.
Input Filter – Optional.
Output Filter – Optional.
Peer IP Address – nnn.nnn.nnn.nnn format. Doesn’t appear if e1a is the IP interface
name.
Route to Peer – Net or Host. Must be Net for s1b. Doesn’t appear if the IP interface
name is e1a.
NOTE:
If you have made any changes to this screen, you must do a card reset or
restart the Ethernet interface.
Control (Control Interface)
A-C-C
Gives the user the ability to restart, stop, and monitor (up, down, or testing) the current
state of an interface.
This screen is populated depending on your entry in the Command and Interface Name
fields. For example, if you select Monitor mode and enter s1b for the Interface name,
the following information is displayed: Type, State, Link Protocol, IP State, Uptime,
Inactive, Connect Time, Port, Local IP Addr, and Peer IP Addr.
6-8
June 1997
8000-A2-GB20-10
DSL Card Configuration
Table 6-3. Interfaces Options (3 of 3)
PPP
A-C-D
Gives the user the ability to configure parameters for the PPP links used for the DSL
connections.
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.
Max Naks – Maximum number of negative acknowledgments before PPP link goes
down.
Negotiate Options
MAU: no
ACCM: no
MAGIC: no
Quality: no
PFC: no
ACFC: no
Option Values
Local MRU (max) – 64-64000 bytes (Default = 1500)
ACCM: Default = ffffff
LQR Freq: Default = 10
Link Options
Trace: on/off/raw/decode (Default = off)
Echo Probe: yes/no (Default = no)
Option Values
Echo Freq: Default = 10
Echo Policy: Default = 5
NOTE:
8000-A2-GB20-10
Most of the fields on this screen are pre-populated.
June 1997
6-9
DSL Card Configuration
DSL Configuration Users Screens
Use the system information sub-menu of the Users screens to configure login
accounts for telnet sessions directly to the DSL cards.
Procedure
1. Follow this menu sequence:
Configuration → Users (A-D)
2. The Users menu appears. Enter the desired values on this screen and fields
and press Return.
Table 6-4. Users Options
Users (Configure Account)
A-D-A
Gives the user the ability 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.
User accounts provide security for the DSLAM by requiring that anyone who is trying to
log onto the system has a valid password to gain access. User accounts on the MCC
provide security to users accessing the system from the VT100 terminal interface and
via Telnet over the management domain LAN.
It is recommended that user accounts also be set up for each DSL card, even if you do
not intend to telnet directly to the DSL cards, so that no unauthorized telnet sessions
can be made. Each card will support up to 10 user accounts with either Operator (read
only) or Administrator (read/write) permissions.
If you configure an account on the MCC card, you have privileges on both the MCC and
DSL cards.
If you configure an account on the DSL card, you only have privileges for that specific
DSL card.
Action – Add/Edit/Delete.
Login ID – Enter your login ID.
Password – Enter the password associated with the login ID.
Repeat Password – Re-enter your password.
Privilege – Operator/Administrator. Enter Operator for read only access; enter
Administrator for complete system access.
NOTE:
6-10
Use Ctrl-v to see a list of all user accounts at the login ID prompt.
June 1997
8000-A2-GB20-10
DSL Card Configuration
DSL Configuration IP Router Screens
Use the system information sub-menu of the IP Router screens to configure static
routes to protocols and filters.
Procedure
To configure static routes, martian networks, and IP router filters:
1. Follow this menu sequence:
Configuration → IP Router (A-E)
2. The IP Router menu appears. Enter the desired values on this screen and
fields and press Return.
Table 6-5. IP Router Options (1 of 3)
Static Routes
A-E-A
Gives the user the ability to add or delete static routes in the system.
Item – Press Return on 0 field to add entry.
Host/Net – nnn.nnn.nnn.nnn format or space to delete entry.
Subnet Mask – Associated subnet mask for the specified destination IP address.
Next Hop – nnn.nnn.nnn.nnn format.
Pref – Measure of how preferable one route is 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.
S/D (Source/Destination) – Source or destination IP address of the packet.
PA (Proxy ARP) – Router answers ARP requests intended for another machine.
NOTE:
When you define a source route, the Proxy ARP field is no longer
selectable.
Martian Networks
A-E-B
Gives the user the ability to configure addresses that the system recognizes as invalid.
Item – Press Return on 0 field to add 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. Enter IP mask of unwanted source.
NOTE:
8000-A2-GB20-10
The system is shipped with default martian networks. It is recommended
that you do not remove entries. If you have made changes to this screen,
you must do a card reset.
June 1997
6-11
DSL Card Configuration
Table 6-5. IP Router Options (2 of 3)
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. The filter then performs the action specified by the
rule on that packet, which can be either to forward or discard the packet.
Rules apply to the source and destination ports going to the end-user system. You may
have up to 33 rules per filter, but the greater number of rules, the lesser the
performance of the router filter.
For additional information on IP Router filters, see Chapter 7, IP Filtering, of the HotWire
Digital Subscriber Line Access Multiplexer (DSLAM) Network Configuration Guide.
Action – Add/Delete/Edit.
Filter Name – Up to 16 characters (optional).
Rule # – Up to 33 rules can be configured for each filter. This number is automatically
assigned.
# of Rules – Number of rules that apply to this port.
Source Address – nnn.nnn.nnn.nnn format.
Source Address Mask – nnn.nnn.nnn.nnn format. If you specify a source subnet mask
of 0.0.0.0, the system skips the source address comparison.
Source Port No – 0–65536 (Default = 0). If the source port number is 0, the system
filters ICMP packets in addition to the packet types defined in the rule.
Comparison Type –Ignore – Do not do a comparison. To do a comparison on the port
number specified in the packet and the rule, specify one of the following: EQ – Equal to,
NRQ – Not Equal To, GT – Greater than, LT – Less than, In_Range – Witnin the
specified range, Out_Range – Outside of the specified range.
Destination Address – nnn.nnn.nnn.nnn format.
Destination Address Mask – nnn.nnn.nnn.nnn format. If you specify a destination
subnet mask of 0.0.0.0, the system skips the destination address comparison.
Destination Port No. – 0–65536 (Default = 0). If the source port number is 0, the
system filters ICMP packets in addition to the packet types defined in the rule.
Comparison Type – Ignore – Ignore ports, EQ – Equal to, NRQ – Not Equal To, GT –
Greater than, LT – Less than, In_Range – Maximum source port, Out_Range –
Minimum source port.
Filter Action – Discard (Packet)/Forward (Packet).
Delete Rule – Yes/No.
Go to Next Rule – Yes/No.
NOTE:
6-12
You have to reset the port interface (A-B-B) for any changes to take effect.
June 1997
8000-A2-GB20-10
DSL Card Configuration
Table 6-5. IP Router Options (3 of 3)
ARP (Parameters, Add Entry, and Delete Entry)
A-E-D A, B, or 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–200000 (Default = 20).
NOTE:
If you have made changes to this screen, you must do a card reset.
Add Entry (B)
Gives the user the ability to add entries into the ARP cache.
IP Address/Host Name – nnn.nnn.nnn.nnn format.
MAC Address – xx-xx-xx-xx-xx-xx format.
Trailers – Yes/No (Default = No).
Proxy – Yes/No (Default = No).
Add Entry – Enter yes to add an entry or exit.
Add Another Entry – Enter yes to add another entry.
Delete ARP Entry (C)
Gives the user the ability to delete entries line by line in the ARP cache. The screen
displays columns for Line, IP address, Ethernet Address, Min, and Delete.
Select the line you want to delete, select yes/no, and press Return.
NOTE:
For the Add and Delete ARP Entry screens, any information entered is not
stored in the NV memory and will be lost when you reset the card.
Host Table (IP Host Table)
A-E-E
Gives the user the ability to define mappings between IP addresses and end user host
names (names of host devices located at the customer’s site).
Enter the IP Address and Host Name in nnn.nnn.nnn.nnn format and press Return after
each entry.
NOTE:
8000-A2-GB20-10
You have to reset the port interface (A-B-B) for any changes to take effect.
June 1997
6-13
DSL Card Configuration
DSL Configuration SNMP Screens
Use the system information sub-menu of the SNMP screens to configureSNMP
security, SNMP Logical Entities, and SNMP Communities/Traps.
" Procedure
1. Follow this menu sequence:
Configuration → SNMP (A-F)
2. The IP Router menu appears. Enter the desired values on this screen and
fields and press Return.
Table 6-6. SNMP Options (1 of 2)
Security (SNMP Security)
A-F-A
Gives the user the ability to configure allowable NMS IP addresses and to configure
SNMP agent.
Although SNMP community strings (if they are changed from the defaults) provide a
measure of security for unauthorized managers, enabling IP address security and
entering the IP address of up to five authorized SNMP managers provides a much
higher level of security. When IP address security is enabled, the source address of any
SNMP message addressed to any of the card’s IP addresses (in either the management
or customer domain) will be chacked against the authorized list and will be disabled if
there is no match.
IP Address Security – Enable/Disable (Default = Disable).
H Enabling allows DSLAM to accept SNMP messages from SNMP managers whose
IP source addresses have been entered in IP Address field.
H Disabling stops this IP address checking and allows the card to respond to a
SNMP query from any source.
IP Address – nnn.nnn.nnn.nnn format. Enter up to five IP source addresses of NMS
managers.
Access – ReadOnly(ro)/ReadWrite(rw)/NoAccess(na). Permissions to be granted to
NMS manager.
Logical Entities (SNMP Logical Entities)
A-F-B
This screen displays information on the logical table of the Entity MIB.
H I (Index) column shows the index number of DSL ports two to five.
H T (Type) column shows “Remote.”
H Read Write Comm shows the community strings of the RTU attached to this port.
It is used when the DSLAM downloads configuration data to the RTU in a future
release.
6-14
June 1997
8000-A2-GB20-10
DSL Card Configuration
Table 6-6. SNMP Options (2 of 2)
Communities/Traps (SNMP Communities/Traps)
A-F-C
Gives the user the ability to enable the Authentication Failure Trap Mechanism, stores
SNMP Community string names for the DSL card, and stores NMS host IP addresses to
which the DSLAM sends trap messages.
It also lets the user configure four communities with three trap destinations that can be
configured for each of those communities.
Authentication Failure Trap – Enable to send a trap when a SNMP request community
string does not match or when the password for a Telnet session is incorrect.
Community Name – 32 characters, up to four unique entries per screen. Default
names are public (ro), MCC (rw), NMS (rw), NMS-2 (ro).
Access – ReadOnly(ro)/ReadWrite(rw)/NoAccess(na), up to four entries per screen.
IP Address – nnn.nnn.nnn.nnn format. Enter NMS system host address.
Input Number (port) – nnn format. Enter NMS system port number.
Send Traps – Set to E to enable. Set to D to disable.
8000-A2-GB20-10
June 1997
6-15
Monitoring the HotWire DSLAM
7
Overview
The HotWire DSLAM lets you to monitor the activity of the HotWire MCC and
DSL cards. When you select Monitoring from the HotWire MCC or 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. For
diagnostic tools and hardware and software troubleshooting techniques, see
Chapter 8, Diagnostics and Troubleshooting.
MCC Monitoring Menu Tree
8000-A2-GB20-10
June 1997
7-1
Monitoring the HotWire DSLAM
MCC Monitoring Card Status Screens
Use the system information sub-menu 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 sub-menu option and press
Return.
Table 7-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.
The General Card Information screen displays the following information:
H System Name – Name assigned to the card.
H System Location – Physical location of the system.
H System Contact – Name or number of the person responsible for the card.
H System Up Time – Length of time the system has been running.
H Available Buffers – Number of buffers not in use.
H Instruction Ram Size – Size of the Instruction Ram.
H Buffer Ram Size – Size of the Buffer Ram.
H Fast Data Ram Size – Total and Available Fast Data Ram.
H Card Type – Type of Card (MCC, DSL).
H Model Num – Model number of card.
H Serial Num – Serial number of card.
H Firmware – Version of firmware.
H Hardware Rev – Version of hardware.
Login History
B-A-B
Displays a list of information of the 10 most recent logins.
The Login History screen displays the following information:
H Most recent login – Time of the most recent login.
H User – User id.
H Remote – Local or Remote Connection.
H Least Recent Login – Time of the least recent login.
H Number of unsuccessful Console logins – Number of console logins that were
incorrect.
H Number of unsuccessful Telnet logins – Number of Telnet logins that were
incorrect.
Syslog
B-A-C
Displays a timestamp sequential list of operational type errors (such as invalid IP
addresses) by date and error. There is one logged error per line in a downward scrolling
list.
7-2
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
MCC Monitoring Physical Layer Screens
Use the system information sub-menu 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 sub-menu option and press
Return.
Table 7-2. Physical Layer Options (1 of 2)
Active List (Active Ports List)
B-B-A
Displays a list of the current status of all the active ports (e1a =ethernet, s1b =
backplane) in the card such as the port number, port name, port type, MAC address,
and status of the port (in use or disconnected).
The Active Ports List displays the following information:
H Num – Number of the port.
H Name – Name of the port.
H Description – Type of port.
H MAC Address – MAC address of the active port. (Internal dummy address is used
for non-ethernet ports.)
H Status – In-use or disconnected.
8000-A2-GB20-10
June 1997
7-3
Monitoring the HotWire DSLAM
Table 7-2. Physical Layer Options (2 of 2)
Ether Statistics (Ethernet Statistics)
B-B-B
Displays a list of the Ethernet statistics of the LAN port (e1a) such as port name, LAN
address, bytes (running account of how many bytes have been received since last
reset), packets (running account of how many packets have been received since last
reset) and errors received and transmitted, number of disconnects, number of fast
restarts, number of endless and startless packets, and amount of babble.
You may enter Ctrl-r at any time to reset counters.
The Ethernet Statistics screen displays the following information:
Port – Name of port (e1a).
Initialized Ethernet Ports – e1a (there is only one ethernet port on the card).
LAN Address – LAN (or MAC) address of the ethernet port.
Bytes received – Number of bytes received by the ethernet port.
Packets received – Number of packets received by the ethernet port and what
type (multicasts, broadcasts, flooded, filtered, discarded).
Errors – Number of errors received by the ethernet port and what type (overruns,
bad CRC, framing, jumbo-gram, overflow, buffer).
Bytes transmitted – Number of bytes transmitted by the ethernet port.
Packets transmitted – Number of packets transmitted by the ethernet port and
what type (multicasts, broadcasts, flooded, local origin, queued).
Errors – Number of errors transmitted by the ethernet port and what type
(collisions, M/L/E, deferrals, carrier loss, underflow, buffer).
Disconnects – Number of disconnects on the ethernet port and what type (disable,
MAU drop, Xmit fail).
Fast restarts – Number of fast restarts and what type (RX off, TX off, Mem err).
Endless Pkt – Number of endless packets received on the ethernet port.
Startless Pkt – Number of startless packets received on the ethernet port.
Babble – Number of garbled packets received due to crosstalk.
HDLC Bus Stats (HDLC Bus Statistics)
B-B-C
Displays a list of of the HDLC backplane port statistics for the s1b port (backplane),
bytes received and transmitted, packets received and transmitted, and errors received
and transmitted. (If a high number of errors have been received, the card may have to
be reset.)
You may enter Ctrl-r at any time to reset counters.
The HDLC Bus Statistics screen displays the following information:
Port name – Port name (s1b).
Bytes received – Number of bytes received on the backplane port.
Bytes transmitted – Number of bytes transmitted on the backplane port.
Packets received – Number of packets received on the backplane port.
Packets transmitted – Number of packets transmitted on the backplane port.
Errors – Number of other receive errors.
Lost – Number of packets not transmitted due to internal congestion.
7-4
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
MCC Monitoring Interfaces Screens
Use the system information sub-menu 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 Interfaces menu appears. Select the sub-menu option and press Return.
Table 7-3. 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.
The Active Interfaces List displays the following information:
H If – Number of the interface.
H Name – Name of the interface.
H Type – Interface type (static).
H Link – Name of the protocol on the interface.
H State – Current state of the interface.
H ll-state – Not applicable.
H Port – Port linked to this interface.
The only information that changes on this screen is the state (active or port-wait)
column.
Status (Interface Status)
B-C-B
Displays a list of additional information, after a specific interface (port) has been
selected, such as interface name, interface protocol, interface port, user name, interface
type, number of restarts and link-downs, interface state, and the interface timeout
inactivity.
The Interface Status screen displays the following information:
H Ifname – Enter the name of the desired interface (s1a, e1b).
H Protocol – Type of protocol for the entered interface name.
H Port – Port linked to this interface.
H Restarts – Number of times the interface has been restarted.
H User – NA or none.
H Type – Static.
H Link-downs – Number of times the link has gone down.
H State – Active or prtwait.
H Inactivity T/O – Number of times the interface has timed out.
8000-A2-GB20-10
June 1997
7-5
Monitoring the HotWire DSLAM
MCC Network Protocol Screens
Use the system sub-menu 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 sub-menu option and press
Return.
Table 7-4. Network Protocol Options (1 of 6)
Socket Statistics
B-D-A
Displays information on the active sockets such as socket name, socket family, socket
type (stream or datagram), input bytes and output bytes, and PDU and byte drops. Enter
the socket name from the active socket list to view information on the application
assigned to the specified socket number.
The Socket Statistics screen displays the following information:
H Start Socket – Enter the socket number to start the active socket list.
H Active Socket List – This is the heading information for the following fields. It lists
all the information about the currently selected socket.
In addition, the lower right-hand corner of the screen displays a Socket Statistics
window with detailed information about the selected destination. The Socket Statistics
window displays the following information:
H Socket – Socket number.
H Socket name – Internal name of the socket.
H Family – Family of this socket (DARPA Internet).
H Type – Socket type (stream or datagram).
H Local – Port number on this card.
H Remote – Port number on remote card.
H State – Current state of the socket.
H Input Bytes – Bytes waiting in the socket for the owning application to process (will
go to 0 when processed by the application).
H Send Bytes – Bytes waiting to be sent out to the remote machine.
H PDU Drops – Incoming packets dropped (usually due to a lack of space).
H Byte Drops – Outgoing packets dropped (usually due to a lack of space).
7-6
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-4. Network Protocol Options (2 of 6)
UDP Statistics
B-D-B]
Displays information on UDP statistics such as input packets, output packets, packets
with checksum errors, bad length packets, and other information on all interfaces.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The UDP Statistics screen displays the following information:
Output Packets – Number of UDP packets sent out of the card.
Input Packets – Number of UDP packets coming into the card.
No receive port – Number of UDP packets coming into the card that had no
receive port waiting for this packet.
Unchecksummed – Number of UDP packets coming into the card that had no
checksum.
Header Error – Number of UDP packets coming into card that had an error with the
packet header.
Incorrect Checksum – Number of UDP packets coming into the card that had a
bad checksum.
Bad length – Number of UDP packets coming into the card that are an illegal
length (too short).
Other Error – Number of UDP packets coming into the card that had an error, but
not one of the above.
8000-A2-GB20-10
June 1997
7-7
Monitoring the HotWire DSLAM
Table 7-4. Network Protocol Options (3 of 6)
TCP Data Stats (TCP Data Statistics)
B-D-C
Displays a summary of the TCP data activity (packets and bytes transmitted and
received) on all interfaces on the 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 enter Ctrl-r at any time to reset the
counters.
The TCP Data Statistics screen displays the following fields.
Left column:
Packets Received – Number of TCP packets received by the card.
Acks – Number of acknowledgements received for transmitted packets. (Also
shows the number of bytes that were acknowledged as received by the remote
system.)
Duplicate Acks – Number of duplicate acks received.
Acks For Unsent Data – Number of acks received for data that has not been sent
yet.
Pkts/Bytes Received in Sequence – Number of packets/bytes correctly received in
sequence for data that had to be split in multiple TCP packets.
Dupl Pkts/Bytes – Number of duplicate packets/bytes received.
Pkts/Bytes W. Some Dup. Data – Number of packets/bytes with some duplicated
data. (Duplicated data is discarded by TCP.)
Pkts Rcvd out-of-order – Packets received out of order.
Pkts of data after window. – Packets of data received after our receive window is
full.
Window Probes – Packets received looking for space in our receive window.
Window Update Pkts – Packets received from the remote system advertising a
new window size.
Pkts Rcv After Close – Packets received after the (our) TCP connection is shut
down.
Discarded for Bad Checksum – Packets that were discarded because the
checksum failed.
Discarded for Bad Header Offset Fields – Packets discarded because the TCP
header was corrupted.
Discarded because Packet Too Short – Packets discarded because the packet
was too short (not a complete TCP header).
Right column:
Packets Sent – Number of TCP packets sent by the card.
Data Pkts/Bytes – Number of the sent packets that were data packets instead of
TCP control packets.
Retransmit Pkts/Bytes – Number of packets/bytes that had to be transmitted.
Ack Only Packets – Number of sent packets that contained only an ack of a
received packet and no additional data.
URG only – Number of packets that contained only an Urgent flag and no data.
Window Probe Pkts – Number of packets that were window probes.
Window Update – Number of packets that were advertising our new window size.
Control Pkts – Number of control packets sent (SYN, FIN, or RST flag).
7-8
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-4. Network Protocol Options (4 of 6)
TCP Connection Statistics
B-D-C
Displays a summary of the TCP connection activity on all interfaces on the card.
The TCP Connection Statistics screen displays the following fields:
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.
Embryonic Connections Closed – Number of connections dropped before data
transfer.
Segments Updated RTT – Number of packets that updated the Round Trip Time
and the total number of times TCP attempted to update the RTT.
Retransmit Timeouts – Number of times a packet had to be transmitted because it
was not ack-ed and the number of times a connection was dropped because a
packet could not be transmitted.
Persist Timeout – Number of times the TCP persistence timer went off and sent a
probe to the remote system.
Keepalive Timeouts – Number of times a TCP keepalive request timed out.
Keepalive probes sent – Number of TCP keepalive probes sent.
Conn Dropped by Keepalive – Number of connections dropped because the
keepalive timer failed to get any responses.
IP Statistics
B-D-D
Displays a summary of the IP activity on all interfaces on the card.
The IP Statistics screen displays the following information:
Total Pkts Rev – Total number of IP packets received by this card, with errors
broken down on the right of the screen.
Fragments Rev – Number of packet fragments received, with dropped fragments
on the right of the screen.
Frag on Transmit – Number of packets that were fragmented on transmit and the
number of fragments that were created by those packets.
Packets Forwarded – Number of packets that were forwarded to another system.
Packets Not Forwardable – Number of packets that could not be forwarded.
(Usually due to packet errors or routing problems.)
Packet Redirects sent – Number of redirect messages sent to other systems
because they sent a packet that should not be sent to this card.
Network Broadcasts Received – Number of network broadcasts received for local
networks.
Network Broadcasts Forwarded – Number of network broadcasts for local
networks sent.
Network Broadcasts partially processed – Number of network broadcasts dropped
due to an error.
8000-A2-GB20-10
June 1997
7-9
Monitoring the HotWire DSLAM
Table 7-4. Network Protocol Options (5 of 6)
ICMP Statistics (ICMP Packet Statistics)
B-D-E
Displays a summary of the ICMP activity on all interfaces of the card such as echo
replies, source quench messages, and information requests with their output, input, and
status.
The columns show input and output packet counts. Note that the Status column is only
applicable for “routing redirect.”
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
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 Return, the SNMP Authentication
Statistics screen is displayed, giving you additional Community Administration
information.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The SNMP Statistics screen displays the following information:
In Packets – Total number of SNMP Protocol Data Units (PDUs) received by the
agent.
Get Requests – Total number of SNMP Get Request PDUs accepted and
processed by the SNMP agent.
Get Next Requests – Total number of SNMP Get Next PDUs accepted and
processed by the SNMP agent.
Total Requested Variables – Total number of Management Information Vase (MIB)
retrieved successfully by the SNMP agent as a result of receiving valid SNMP Get
Request and Get Next PDUs.
Set Requests – Total number of SNMP Set Requests PDUs accepted and
processed by the SNMP agent.
Total Set Variables – Total number of MIB objects modified successfully by the
SNMP agent as a result of receiving valid SNMP Set Requests PDUs.
ASN.1 – Total number of ASN.1 or BER errors encountered when decoding
received SNMP messages.
Out Packets – Total number of SNMP PDU responses sent by the agent.
Out Too Big Errors – Total Number of SNMP PDUs generated by the SNMP agent
for which the value of error status field is too big.
Out No Such Names – Total number of SNMP PDUs generated by the SNMP
agent for which the value of error status field is “no such name.”
Out Bad Values – Total number of SNMP PDUs generated by the SNMP agent for
which the value of the error status field is bad value.
Out General Errors – Total number of SNMP PDUs generated by the SNMP agent
for which the value of error status is Gen Err.
Read-only Errors – Total number of SNMP PDUs delivered by the SNMP agent for
which the value of the error status field is read-only.
Out Get Response – Total number of Get-Response PDUs sent out by the SNMP
agent.
Out Traps – Total number of SNMP Traps PDUs generated by the SNMP agent.
SNMP Status – Indicates the state of the SNMP Agent. The first byte=error code,
the second byte=sub-routine code.
7-10
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-4. Network Protocol Options (6 of 6)
SNMP Authentication Statistics
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.
Bad Community Name – Total number of SNMP messages delivered to the SNMP
agent that used an SNMP community name not known to the entity.
Bad Community Use – Total number of SNMP messages delivered to the SNMP
agent that represent an SNMP operation not allowed by the SNMP community
named in the message.
HDLC Stats (HDLC Statistics )
B-D-G
Displays information on High-Level Data Link Control statistics for the backplane bus
such as number of octets and frames transmitted, packet receive errors, and framing
errors.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The HDLC Statistics screen displays the following information:
Interface Name – Interface Name (s1b).
Totals Summary – This is the heading information for the following fields. There will
not be entries in this field.
Octets Transmitted and Received – Number of octets (8 bit bytes) transmitted and
received.
Frames Transmitted and Received – Number of frames (groups of data bits)
transmitted and received.
Alloc Failures on Send – Number of packets not transmitted because there was no
memory available to build the packet.
Output Errors – Number of other transmit errors (i.e., bad HDLC address).
8000-A2-GB20-10
June 1997
7-11
Monitoring the HotWire DSLAM
MCC IP Router Screens
Use the system information sub-menu 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 sub-menu option and press Return.
Table 7-5. IP Router Menu Options (1 of 2)
Routing Table
B-E-A
Displays information and statistics stored in the 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 <RET>]: prompt.
Routing Table Screen
The Routing Table displays the following columns of information:
H # – Displays the entry number in the routing table. Use this number to specify
which entry you want to display more information.
H Destination – Specifies the destination (or source) IP address of the packet.
H Subnet Mask – Indicates the associated subnet mask for the specified destination
IP address.
H Routes – Number of routes for Destination.
H Flags – Identifies the type of route: host, sub (subnetwork), or net (network).
7-12
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-5. IP Router Menu Options (2 of 2)
Routing Information Window
In addition, the lower right-hand corner of the screen displays a Route Information
window with detailed information about the selected destination. The Route Information
window displays the following information:
Route # – Displays the number of the route for the given destination. If more than
one route exists for the given destination, you may view subsequent routes by
entering the routing entry number at the [Route # or <RET>]: prompt.
Next Hop – Indicates the IP address of the next hop device for the specified
destination.
Protocol – Displays the type of routing protocol by which the route was learned
(i.e., static or direct).
Preference – Specifies the assigned preference number to this route. If more than
one route exists for the given destination, this number is compared to the
preference number of the other routes. The route with the lowest preference
number is the preferred route.
The value of 0 indicates the highest preference. The greater the number, the lower
the preference.
Flags – Indicates if a route is a Host and if the next hop is valid.
Interface – Displays the name of the interface associated with the destination
address.
State – Indicates the various state information about the route including
Permanent, Deleted, SRC, Host, Net, Subn.
Metric – Not applicable.
Age – Displays the length of time in seconds that a non-permanent route has been
active.
Revision # – Not applicable.
Max Age – Displays the maximum length of time in seconds before a
non-permanent route has been active.
Ref Count – Number of internal references for this route.
Displays the working routing table. Routes will appear only for interfaces that are up.
Details for the selected destinations are shown in the lower right corner. You may select
a different destination by entering a number at the “Destination #” prompt. If more than
one route exists for the given destination, you may view subsequent routes by entering
the number at the “Route #” prompt.
ARP Table
B-E-B
Displays the current Address Resolution Protocol (ARP) cache. Permanent entries show
an age of 0.
The ARP Table screen displays the following information:
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.
Interface – The interface on which this ARP request was answered.
Flags – Various flags associated with this entry. PERM = permanent, PUB =
publish this entry (respond for other hosts), PROX = proxy ARP (card will proxy
ARP for this IP address).
8000-A2-GB20-10
June 1997
7-13
Monitoring the HotWire DSLAM
DSL Monitoring Menu Tree
7-14
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
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 sub-menu option and press
Return.
Table 7-6. 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.
The General Card Information screen displays the following information:
H System Name – Name assigned to the card.
H System Location – Physical location of the system.
H System Contact – Name or number of the person responsible for the card.
H System Up Time – Length of time the system has been running.
H Available Buffers – Number of Buffers not in use.
H Instruction Ram Size – Size of the Instruction Ram.
H Buffer Ram Size – Size of the buffer Ram.
H Fast Data Ram Size – Total and Available Fast Data Ram.
H Card Type – Type of Card (MCC, DSL).
H Model Num – Model number of card.
H Serial Num – Serial number of card.
H Firmware – Version of firmware.
H CAP Firmware – Firmware for DSL chipset.
H Hardware Rev – Version of hardware.
Login History
B-A-B
Displays a list of information of the 10 most recent logins.
The Login History screen displays the following information:
H Most recent login – Time of the most recent login.
H User – User id.
H Remote – Local or Remote Connection.
H Least Recent Login – Time of the least recent login.
H Number of unsuccessful Console logins – Number of console logins that were
incorrect.
H Number of unsuccessful Telnet logins – Number of Telnet logins that were
incorrect.
Syslog
B-A-C
Displays a timestamp sequential list of operational type errors (such as invalid IP
addresses) by date and error. There is one logged error per line in a downward scrolling
list.
8000-A2-GB20-10
June 1997
7-15
Monitoring the HotWire DSLAM
DSL Monitoring Physical Layer Screens
Use the system information sub-menu 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 sub-menu option and press
Return.
Table 7-7. Physical Layer Options (1 of 4)
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).
The Active Ports List displays the following information:
H Num – Number of the port.
H Name – Name of the port.
H Description – Type of port.
H MAC Address – MAC address of the active port. (Internal dummy address used for
non-ethernet ports.)
H Status – Active or disconnected.
7-16
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-7. Physical Layer Options (2 of 4)
Ether Statistics (Ethernet Statistics)
B-B-B
Displays a list of the Ethernet statistics of the LAN port (e1a) such as port name, LAN
address, bytes (running account of how many bytes have been received since last
reset), packets (running account of how many packets have been received since last
reset) and errors received and transmitted, number of disconnects, number of fast
restarts, number of endless and startless packets, and amount of babble.
You may enter Ctrl-r at any time to reset counters.
The Ethernet Statistics screen displays the following information:
Port – Type of port (e1a).
Initialized Ethernet Ports – e1a (there is only one other net port on the card).
LAN Address – LAN (or MAC) address of the ethernet port.
Bytes received – Number of bytes received by the ethernet port.
Packets received – Number of packets received by the ethernet port and what
type (multicasts, broadcasts, flooded, filtered, discarded).
Errors – Number of errors received by the ethernet port and what type (overruns,
bad CRC, framing, jumbo-gram, overflow, buffer).
Bytes transmitted – Number of bytes transmitted by the ethernet port.
Packets transmitted – Number of packets transmitted by the ethernet port and
what type (multicasts, broadcasts, flooded, local origin, queued).
Errors – Number of errors transmitted by the ethernet port and what type
(collisions, M/L/E, deferrals, carrier loss, underflow, buffer).
Disconnects – Number of disconnects on the ethernet port and what type (disable,
MAU drop, Xmit fail).
Fast restarts – Number of fast restarts and what type (RX off, TX off, Mem err).
Endless Pkt – Number of endless packets received on the ethernet port.
Startless Pkt – Number of startless packets received on the ethernet port.
Babble – Number of garbled packets received due to crosstalk.
HDLC Bus Stats (HDLC Bus Statistics)
B-B-C
Displays a list of of the HDLC backplane port statistics for the s1b port (backplane),
bytes received and transmitted, packets received and transmitted, and errors received
and transmitted. (If a high number of errors have been received, the card may have to
be reset.)
You may enter Ctrl-r at any time to reset counters.
The HDLC Bus Statistics screen displays the following information:
Port name – Port name (s1b).
Bytes received – Number of bytes received on the backplane port.
Bytes transmitted – Number of bytes transmitted on the backplane port.
Packets received – Number of packets received on the backplane port.
Packets transmitted – Number of packets transmitted on the backplane port.
Errors – Number of other receive errors.
Lost – Number of packets not transmitted due to internal congestion.
8000-A2-GB20-10
June 1997
7-17
Monitoring the HotWire DSLAM
Table 7-7. Physical Layer Options (3 of 4)
DSL Link Perf (DSL Link Performance Summary)
B-B-D
Displays a summary of the link performance for each of the DSL ports.
Enter port number one to four to see the fields for current 15-min. period (real time count
of events during the past 0 to 15 minutes), previous 15-min. period (data updated every
15 minutes based on the card’s timer), previous one hour period (data updated every
hour based on the card’s timer), and 24 hour period (data bucket is updated every hour
based on the card’s timer).
Error Rate Definition:
Down error rate – This statistic is not available for this release and a NA appears for
each time period.
Up error rate – 0 indicates that no packet errors have occurred during the specified
period. If a value other than 0 is present, , then this number is the ratio of good packets
received to errored packets. For reference, a value of 10,000 is roughly equivalent to a
bit error rate of 10 7, assuming a packet size of 128 bytes.
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.
Enter port number one to four to see the fields for current 15-min. period (real time count
of events during the past 0 to 15 minutes), previous 15-min. period (data updated every
15 minutes based on the card’s timer), previous one hour period (data updated every
hour based on the card’s timer), and 24 hour period (data bucket updated every hour
based on the card’s timer).
Additional fields are link down count (number of times the DSL link has gone down), elp
link up (count in seconds of the elapsed time the link has been up), and 15m valid
(number of 15 minutes intervals in which downstream performance data (which is
measured by the 5446 RTU) has been received across the DSL link from the RTU).
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.
Enter port number one to four to see the fields for current
15-min. period (real time count of events during the past 0 to 15 minutes), previous
15-min. period (data updated every 15 minutes based on the card’s timer), previous one
hour period (data updated every hour based on the card’s timer), and 24 hour period
(data bucket updated every hour based on the card’s timer). A margin of 0 db equals a
bit error rate of 10-7. (The higher the margins, the fewer the errors.)
You may enter Ctrl-r at any time to reset counters.
Error Rate Definition:
Down error rate – This statistic is not available for this release and a NA appears for
each time period.
Up error rate – 0 indicates that no packet errors have occurred during the specified
period. If a value other than 0 is present, , then this number is the ratio of good packets
received to errored packets. For reference, a value of 10,000 is roughly equivalent to a
bit error rate of 10 7, assuming a packet size of 128 bytes.
7-18
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-7. Physical Layer Options (4 of 4)
DSL Xmit Status (DSL Transmit Stats)
B-B-G
Displays the transmit and receive statistics for each of the DSL ports after selecting a
specific DSL port number.
Enter port number one to four to see the fields for current
15-min. period (real time count of events during the past 0 to 15 minutes), previous
15-min. period (data updated every 15 minutes based on the card’s timer), previous one
hour period (data updated every hour based on the card’s timer), and 24 hour period
(data bucket updated every hour based on the card’s timer).
You may enter Ctrl-r at any time to reset counters.
8000-A2-GB20-10
June 1997
7-19
Monitoring the HotWire DSLAM
DSL Monitoring Interfaces Screens
Use the system sub-menu 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 Interfaces menu appears. Select the sub-menu option and press Return.
Table 7-8. 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.
The Active Interfaces List displays the following information:
H If – Number of the interface.
H Name – Name of the interface.
H Type – Interface type (static).
H Link – Name of the protocol on the interface.
H State – Current state of the interface.
H ll-state – Not applicable.
H Port – Port linked to this interface.
The only information that changes on this screen is the state (active or port-wait)
column.
Status (Interface Status)
B-C-B
Displays a list of additional information, after a specific interface (port) has been
selected, such as interface name, interface protocol, interface port, user name, interface
type, number of restarts and link-downs, interface state, and the interface timeout
inactivity.
The Interface Status screen displays the following information:
H Ifname – Enter the name of the desired interface (s1a, e1b).
H Protocol – Type of protocol for the entered interface name.
H Port – Port linked to this interface.
H Restarts – Number of times interface has been restarted.
H User – NA or none.
H Type – Static.
H Link-downs – Number of times the link has gone down.
H State – Active or prtwait.
H Inactivity T/O – Number of times the interface has timed out.
7-20
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
DSL Network Protocol Screens
Use the system sub-menu 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 sub-menu option and press
Return.
Table 7-9. Network Protocol Options (1 of 7)
Socket Statistics
B-D-A
Displays information on the active sockets such as socket name, socket family, socket
type (stream or datagram), input bytes and output bytes, and PDU and byte drops. Enter
the socket name from the active socket list to view information on the application
assigned to the specified socket number.
The Socket Statistics screen displays the following information:
H Start Socket – Enter the socket number to start the active socket list.
H Active Socket List – This is the heading information for the following fields. It lists
all the information about the currently selected socket.
In addition, the lower right-hand corner of the screen displays a Socket Statistics
window with detailed information about the selected destination. The Socket Statistics
window displays the following information:
H Socket – Socket number.
H Socket name – Internal name of the socket.
H Family – Family of this socket (DARPA Internet).
H Type – Socket type (stream or datagram).
H Local – Port number on this card.
H Remote – Port number on remote card.
H State – Current state of the socket.
H Input Bytes – Bytes waiting in the socket for the owning application to process (will
go to 0 when processed by the application).
H Send Bytes – Bytes waiting to be sent out to the remote machine.
H PDU Drops – Incoming packets dropped (usually due to a lack of space).
H Byte Drops – Outgoing packets dropped (usually due to a lack of space).
8000-A2-GB20-10
June 1997
7-21
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (2 of 7)
UDP Statistics
B-D-B
Displays information on UDP statistics such as input packets, output packets, packets
with checksum errors, bad length packets, and other information on all interfaces.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The UDP Statistics screen displays the following information:
Output Packets – Number of UDP packets sent out of the card.
Input Packets – Number of UDP packets coming into the card.
No receive port – Number of UDP packets coming into the card that had no
receive port waiting for this packet.
Unchecksummed – Number of UDP packets coming into the card that had no
checksum.
Header Error – Number of UDP packets coming into card that had an error with the
packet header.
Incorrect Checksum – Number of UDP packets coming into the card that had a
bad checksum.
Bad length – Number of UDP packets coming into the card that are an illegal
length (too short).
Other Error – Number of UDP packets coming into the card that had an error, but
not one of the above.
7-22
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (3 of 7)
TCP Data Stats (TCP Data Statistics)
B-D-C
Displays a summary of the TCP data activity (packets and bytes transmitted and
received) on all interfaces on the 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 enter Ctrl-r at any time to reset the
counters.
The TCP Data Statistics screen displays the following fields (left column):
Packets Received – Number of TCP packets received by the card.
Acks – Number of acknowledgements received for transmitted packets. (Also
shows the number of bytes that were acknowledged as received by the remote
system.)
Duplicate Acks – Number of duplicate acks received.
Acks For Unsent Data – Number of acks received for data that has not been sent
yet.
Pkts/Bytes Received in Sequence – Number of packets/bytes correctly received in
sequence for data that had to be split in multiple TCP packets.
Dupl Pkts/Bytes – Number of duplicate packets/bytes received.
Pkts/Bytes W. Some Dup. Data – Number of packets/bytes with some duplicated
data. (Duplicated data is discarded by TCP.)
Pkts rcvd out-of-order – Packets received out of order.
Pkts of data after window – Packets of data received after our receive window is
full.
Window Probes – Packets received looking for space in our receive window.
Window Update Pkts – Packets received from the remote system advertising a
new window size.
Pkts Rcv After Close – Packets received after the (our) TCP connection is shut
down.
Discarded for Bad Checksum – Packets that were discarded because the
checksum failed.
Discarded for Bad Header Offset Fields – Packets discarded because the TCP
header was corrupted.
Discarded because Packet Too Short – Packets discarded because the packet
was too short (not a complete TCP header).
Right column:
Packets sent – Number of TCP packets sent by the card.
Data Pkts/Bytes – Number of the sent packets that were data packets instead of
TCP control packets.
Retransmit Pkts/Bytes – Number of packets/bytes that had to be transmitted.
Ack Only Packets – Number of sent packets that contained only an ack of a
received packet and no additional data.
URG only – Number of packets that contained only an Urgent flag and no data.
Window Probe Pkts – Number of packets that were window probes.
Window Update – Number of packets that were advertising our new window size.
Control Pkts – Number of control packets sent (SYN, FIN, or RST flag).
8000-A2-GB20-10
June 1997
7-23
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (4 of 7)
TCP Connection Statistics
B-D-C
Displays a summary of the TCP connection activity on all interfaces on the card.
The TCP Connection Statistics screen displays the following fields:
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.
Embryonic Connections Closed – Number of connections dropped before data
transfer.
Segments Updated RTT – Number of packets that updated the Round Trip Time
and the total number of times TCP attempted to update the RTT.
Retransmit Timeouts – Number of times a packet had to be transmitted because it
was not ack-ed and the number of times a connection was dropped because a
packet could not be transmitted.
Persist Timeout – Number of times the TCP persistence timer went off and sent a
probe to the remote system.
Keepalive Timeouts – Number of times a TCP keepalive request timed out.
Keepalive probes sent – Number of TCP keepalive probes sent.
Conn Dropped by Keepalive – Number of connections dropped because the
keepalive timer failed to get any responses.
IP Statistics
B-D-D
Displays a summary of the IP activity on all interfaces on the card.
The IP Statistics screen displays the following information:
Total Pkts Rev – Total number of IP packets received by this card, with errors
broken down on the right of the screen.
Fragments Rev – Number of packet fragments received, with dropped fragments
on the right of the screen.
Frag on Transmit – Number of packets that were fragmented on transmit and the
number of fragments that were created by those packets.
Packets Forwarded – Number of packets that were forwarded to another system.
Packets Not Forwardable – Number of packets that could not be forwarded.
(Usually due to packet errors or routing problems.)
Packet Redirects sent – Number of redirect messages sent to other systems
because they sent a packet that should not be sent to this card.
Network Broadcasts Received – Number of network broadcasts received for local
networks.
Network Broadcasts Forwarded – Number of network broadcasts for local
networks sent.
Network Broadcasts partially processed – Number of network broadcasts dropped
due to an error.
7-24
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (5 of 7)
ICMP Statistics (ICMP Packet Statistics)
B-D-E
Displays a summary of the ICMP activity on all interfaces of the card such as echo
replies, source quench messages, and information requests with their output, input, and
status.
The columns show input and output packet counts. Note that the Status column is only
applicable for “routing redirect.”
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
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 Return, the SNMP Authentication
Statistics screen is displayed, giving you additional Community Administration
information.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The SNMP Statistics screen displays the following information:
In Packets – Total number of SNMP Protocol Data Units (PDUs) received by the
agent.
Get Requests – Total number of SNMP Get Request PDUs accepted and
processed by the SNMP agent.
Get Next Requests – Total number of SNMP Get Next PDUs accepted and
processed by the SNMP agent.
Total Requested Variables – Total number of Management Information Vase (MIB)
retrieved successfully by the SNMP agent as a result of receiving valid SNMP Get
Request and Get Next PDUs.
Set Requests – Total number of SNMP Set Requests PDUs accepted and
processed by the SNMP agent.
Total Set Variables – Total number of MIB objects modified successfully by the
SNMP agent as a result of receiving valid SNMP Set Requests PDUs.
ASN.1 – Total number of ASN.1 or BER errors encountered when decoding
received SNMP messages.
Out Packets – Total number of SNMP PDU responses sent by the agent.
Out Too Big Errors – Total Number of SNMP PDUs generated by the SNMP agent
for which the value of error status field is too big.
Out No Such Names – Total number of SNMP PDUs generated by the SNMP
agent for which the value of error status field is “no such name.”
Out Bad Values – Total number of SNMP PDUs generated by the SNMP agent for
which the value of the error status field is bad value.
Out General Errors – Total number of SNMP PDUs generated by the SNMP agent
for which the value of error status is Gen Err.
Read-only Errors – Total number of SNMP PDUs delivered by the SNMP agent for
which the value of the error status field is read-only.
Out Get Response – Total number of Get-Response PDUs sent out by the SNMP
agent.
Out Traps – Total number of SNMP Traps PDUs generated by the SNMP agent.
SNMP Status – Indicates the state of the SNMP Agent. The first byte=error code,
the second byte=sub-routine code.
8000-A2-GB20-10
June 1997
7-25
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (6 of 7)
SNMP Authentication Statistics
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.
Bad Community Name – Total number of SNMP messages delivered to the SNMP
agent that used an SNMP community name not known to the entity.
Bad Community Use – Total number of SNMP messages delivered to the SNMP
agent that represent an SNMP operation not allowed by the SNMP community
named in the message.
HDLC Statistics (HDLC Statistics )
B-D-G
Displays information on High-Level Data Link Control statistics for the backplane bus
such as number of octets and frames transmitted, packet receive errors, and framing
errors.
The counters increment in real time and you may enter Ctrl-r at any time to reset the
counters.
The HDLC Statistics screen displays the following information:
Interface Name – Interface Name (s1b).
Totals Summary – This is the heading information for the following fields. There will
not be entries in this field.
Octets Transmitted and Received – Number of octets (8 bit bytes) transmitted and
received.
Frames Transmitted and Received – Number of frames (groups of data bits)
transmitted and received.
Alloc Failures on Send – Number of packets not transmitted because there was no
memory available to build the packet.
Output Errors – Number of other transmit errors (i.e., bad HDLC address).
PPP Stats (General)
B-D-H
Displays a summary of the PPP activity on a selected interface on the card.
The PPP General Stats screen displays the following information:
Interface Name – Enter the name of the desired 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.
Frames Transmitted – Number of frames (groups of data bits) transmitted.
Octets Received – Number of octets received.
Frames received – Number of frames received.
Alloc failures on send – Number of packets not transmitted because there was no
memory available to build the packet.
Unknown Pkts Received – Packet with unknown received.
Bad Checksum Packets Received – Packet with a bad checksum received.
Frame Errors Received – Packet received with bad framing.
Other Pkt Errors Received– Packet received with an error not listed above.
Alloc failures Received – Card was unable to allocate enough memory to receive
the packet.
7-26
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-9. Network Protocol Options (7 of 7)
LCP Stats (PPP)
B-D-H
Displays a summary of the Link Control Protocol (LCP) activity on a selected interface
on the card. The screen is divided into two parts – the left side is for the local end of the
link; the right half is for the remote end of the link.
The LCP Stats screen displays the following information:
Interface name – Enter the name of the desired interface (s1c, s1d, s1e, s1f).
Link Phase – Current phase/state of this link (Init, Link Control).
Async Bit Map – Coding used to embed PPP control characters in the data section
of the packet.
Authentication – Authentication type required for the connect to be accepted
(usually none).
Magic number – Unique number associated with this end of the link, used to
ensure the link is not a loopback.
IPCP General Stats (PPP)
B-D-H
Displays a summary of the IP Control Protocol (IPCP) activity on a selected interface on
the card. The screen is divided into two parts – the left side is for the local end of the
link; the right half is for the remote end of the link.
The IPCP Stats screen displays the following information:
Interface name – Enter the name of the desired interface (s1c, s1d, s1e, s1f).
Link Phase – Current phase/state of this link (Init, Link Control).
LCP Configuration – Configuration of the link control protocol.
State – State of the IP link (Initial, Opened, Closed).
IP Address – IP address assigned to this end of the link.
8000-A2-GB20-10
June 1997
7-27
Monitoring the HotWire DSLAM
DSL IP Router Screens
Use the system sub-menu 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 sub-menu option and press Return.
Table 7-10. IP Router Options (1 of 2)
Routing Table
B-E-A
Displays information and statistics stored in the 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 <RET>]: prompt.
Routing Table Screen
The Routing Table displays the following columns of information:
H # – Displays the entry number in the routing table. Use this number to specify
which entry you want to display more information.
H Destination – Specifies the destination (or source) IP address of the packet.
H Subnet Mask – Indicates the associated subnet mask for the specified destination
IP address.
H Routes – Number of routes for Destination.
H Flags – Identifies the type of route: host, sub (subnetwork), or net (network).
7-28
June 1997
8000-A2-GB20-10
Monitoring the HotWire DSLAM
Table 7-10. IP Router Options (2 of 2)
Routing Information Window
In addition, the lower right-hand corner of the screen displays a Route Information
window with detailed information about the selected destination. The Route Information
window displays the following information:
Route # – Displays the number of the route for the given destination. If more than
one route exists for the given destination, you may view subsequent routes by
entering the routing entry number at the [Route # or <RET>]: prompt.
Next Hop – Indicates the IP address of the next hop device for the specified
destination.
Protocol – Displays the type of routing protocol by which the route was learned
(i.e., static or direct).
Preference – Specifies the assigned preference number to this route. If more than
one route exists for the given destination, this number is compared to the
preference number of the other routes. The route with the lowest preference
number is the preferred route.
The value of 0 indicates the highest preference. The greater the number, the lower
the preference.
Flags – Indicates if a route is a Host and if the next hop is valid.
Interface – Displays the name of the interface associated with the destination
address.
State – Indicates the various state information about the route including
Permanent, Deleted, SRC, Host, Net, Subn.
Metric – Not applicable.
Age – Displays the length of time in seconds that a non-permanent route has been
active.
Revision # – Not applicable.
Max Age – Displays the maximum length of time in seconds before a
non-permanent route has been active.
Ref Count – Number of internal references for this route.
Displays the working routing table. Routes will appear only for interfaces that are up.
Details for the selected destinations are shown in the lower right corner. You may select
a different destination by entering a number at the “Destination #” prompt. If more than
one route exists for the given destination, you may view subsequent routes by entering
the number at the “Route #” prompt.
ARP Table
B-E-B
Displays the current Address Resolution Protocol (ARP) cache. Permanent entries show
an age of 0.
The ARP Table screen displays the following information:
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.
Interface – The interface on which this ARP request was answered.
Flags – Various flags associated with this entry. PERM = permanent, PUB =
publish this entry (respond for other hosts), PROX = proxy ARP (card will proxy
ARP for this IP address).
8000-A2-GB20-10
June 1997
7-29
Diagnostics and Troubleshooting
8
Applications Screens
Use the Applications submenu to perform a Ping test or Telnet to a remote host
or client.
Procedure
To use the Ping and Telnet functions:
1. Follow this menu sequence:
Applications → Ping (C-A)
Applications → Telnet (C-B)
2. Select Applications from the HotWire MCC or DSL main menu.
3. The Applications menu appears. Select the sub-menu option and enter the
desired value on each screen and field and press Return.
Table 8-1. Applications Options
Ping (MCC and DSL)
C-A
Gives the user the ability to conduct a non-disruptive packet loopback test between the
MCC or DSL card and any IP-aware device with network connectivity. Downstream
devices include HotWire RTUs and user host computers; upstream devices include
Network Service Provider routers and Network Management System (NMS) stations.
IP Address – nnn.nnn.nnn.nnn format.
Packet – 12 to 1600 bytes (Default = 64).
Timeout (wait time for return packet before next try) – one to 30 seconds (Default = 5).
The results of this test include packets sent, received, and a scrolling list of timeouts,
along with the minimum, maximum, and average round trip times of the packets.
NOTE:
The test will continue until you exit the screen.
Telnet (MCC Card only)
C-B
Gives the user the ability to connect with a remote host. Enter the host name or the
Internet Protocol address for the destination to which you wish to connect.
8000-A2-GB20-10
June 1997
8-1
Diagnostics and Troubleshooting
Diagnostic Screens
Use the Diagnostics submenu to perform self-tests or view alarm status.
Procedure
To view selftest, card alarm, and packet test information:
1. Follow this menu sequence:
Diagnostics → Selftest (D-A)
Diagnostics → Alarms (D-B)
2. The Diagnostics menu appears. Select the sub-menu option and enter the
desired value on each screen and field and press Return.
Table 8-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) report pass or fail. If all subsystems pass, the
card has passed selftest. If a subsystem fails, reset or replace the card.
You can determine when the selftest occurred by reading the elapsed time since the last
reset on the card. Follow the menu sequence Monitor → Card Status → Card Info
(B-A-A) and check data in System Up Time.
Alarms (Card Alarms)
D-B
Displays all active card alarm conditions. Major alarms include Selftest failure,
Processor failure (sanity timer), and DSL or Ethernet port failures. Minor alarms include
Config Error (configuration has been corrupted) and threshold exceed for DSL margin,
Error Rate, or Link Down events.
8-2
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
Troubleshooting
The status of each card in the HotWire DSLAM is indicated on the Card Selection
screen (see Chapter 2). Choose Card Selection from the HotWire Chassis Main
Menu.
The status of each DSL card is indicated by codes being displayed in any of eight
positions to the right of the card selected. For example, if you select DSL card in
Slot 4, the following may be displayed:
DSL04: _ M _ _ U U X X
Pos: 1 2 3 4 5 6 7 8
This display indicates that there is a Major Alarm on the DSL card in Slot 4, and
that, while Ethernet and DSL Ports 1 and 2 are up, DSL Ports 3 and 4 are
disabled.
The following table explains the codes by position.
Pos
Explanation
1
Test in progress
2
Major Alarm
3
MinoR Alarm
4
Ethernet (Up or Down)
5
DSL Port 1 (Up, Down, Handshaking, Disabled (X))
6
DSL Port 2 (Up, Down, Handshaking, Disabled (X))
7
DSL Port 3 (Up, Down, Handshaking, Disabled (X))
8
DSL Port 4 (Up, Down, Handshaking, Disabled (X))
The status of DSL ports indicated in the table above is explained as follows:
8000-A2-GB20-10
Up – the DSL link is connected
Down – the DSL link is not connected
Handshaking – the port is handshaking or training
Disabled – the port has never tried to come up, or the port has been turned
off
June 1997
8-3
Diagnostics and Troubleshooting
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.
NOTE:
If a DSL card does not appear on the Card Selection screen because the
MCC card can no longer communicate with it, the MCC card will generate a
trap message. You should go to the MCC’s Monitor → Card Status → Syslog
(A-A-C) and view the event on its system log.
Major Alarms
Use the following table to determine the appropriate action to take for each Major
Alarm.
Table 8-3. Major Alarms (1 of 2)
Selftest
failure:
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 the results are the same as the first selftest, the card should be
replaced. If only one port on a DSL card is bad, that port can be
disabled. You may continue to use the card until it is convenient
to replace it.
Processor
failure (Sanity
timer):
8-4
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 the results are the same as the first selftest, the card should be
replaced.
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
Table 8-3. Major Alarms (2 of 2)
Ethernet port
failure
1. Check cable connections to the DSLAM.
– 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. Check the Activity/Status LED at the Ethernet Hub or Switch.
– If Activity/Status LED does not indicate a problem, go to Step 4.
– If Activity/Status LED indicates a problem, take appropriate
action.
4. Disconnect the Ethernet cable. and replace it with a working cable
from a spare port on the Hub.
– If the replacement cable works, the original is bad and should be
permanently replaced.
– If the replacement cable does not work, reconnect the original
cable and go to Step 5.
5. Move the DSL card and cable to another (spare) slot.
– If this solves the problem, the connector or interface panel
connections for the original slot are bad. Schedule maintenance
for the chassis and try to use the spare slot temporarily.
– If this does not solve the problem, the DSL card is probably bad
and should be replaced.
DSL port
failure
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 the results are the same as the first selftest, the card should be
replaced. If only one port on a DSL card is bad, that port can be
disabled. You may continue to use the card until it is convenient
to replace it.
8000-A2-GB20-10
June 1997
8-5
Diagnostics and Troubleshooting
Minor Alarms
Use the following table to determine the appropriate action to take for each Minor
Alarm.
Table 8-4. Minor Alarms (1 of 2)
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. The card’s non-volatile RAM should be erased and
the configuration reentered. Perform a configuration download.
– If the configuration has not been saved, use reset and erase
NVRAM to force the card to the factory default. Enter the basic
default route to the MCC and reconfigure the card manually.
NOTE:
The following are minor alarms where thresholds have been exceeded and
are primarily indications of degraded quality on the DSL loop. They are not
necessarily related to problems with the DSL card.
Margin
Threshold
(A trap
message sent if
margin falls
below selected
value.)
If DSL speed is set to a Fixed Rate, you may choose to lower the
speed in the direction indicated by the threshold alarm (Fixed Up
Speed or Fixed Down Speed) to get a better Margin and improved
error performance.
If DSL speed is set to Rate Adaptive and the Margin Threshold is
> 0, then this alarm is a warning that the loop has degraded. The
actual bit rate should still be above 10 -7. This condition may be
temporary due to high temperature or humidity/rain, or it may be
permanent due to high noise from additional digital circuits installed
in the same cable bundle.
If DSL speed is set to Rate Adaptive and the Margin Threshold is
< 0, then this alarm is a warning that the loop has seriusly
degraded. The actual bit rate may be below 10 -7. This condition
may be temporary or permanent. However, if it persists, the loop
may have to be reengineered for better performance by performing
one of the following:
– Remove bridge taps
– Change cable gauge on a cable section
– Run new cable
– Remove other noise generating digital circuits from the cable
bundle
8-6
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
Table 8-4. Minor Alarms (2 of 2)
Error Rate
Threshold
(A trap
message sent if
the Block Error
Rate averaged
over a period of
time exceeds
the selected
value.)
If the Error Rate Threshold is < 10,000, 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.)
If the threshold is set low (1–4), and the link is currently down, then
that the loop has degraded. The actual bit rate should still be above
10 -7. This condition may be temporary due to high temperature or
humidity/rain. It may be permanent due to high noise from
additional digital circuits installed in the same cable bundle.
If the Error Rate Threshold is >10,000, then this alarm is a warning
that the loop has degraded. The actual bit rate may be below 10 -7.
This condition may be temporary or permanent. However, if it
persists, the loop may have to be reengineered for better
performance by performing one of the following:
– Remove bridge taps
– Change cable gauge on a cable section
– Run new cable
– Remove other noise generating digital circuits from the cable
bundle
there may be a loop or RTU problem. Check both.
– Verify that the RTU is powered up, is connected to the loop, and
has passed its Selftest.
– Check the loop for continuity
If the threshold is set low (1–4), and the link is currently up, then an
event had occurred to temporarily knock out the connection. Log
the event and continue normal operation.
If the threshold is set high (> 4), and the link is currently down, then
check the Margin statistics over the past hour and day. If the
numbers are low, there may be a situation where the DSL modems
cannot train. This condition may be temporary or permanent.
However, if it persists, the loop may have to be reengineered for
better performance by performing one of the following:
– Remove bridge taps
– Change cable gauge on a cable section
– Run new cable
– Remove other noise generating digital circuits from the cable
bundle
If the threshold is set high (> 4) and the link is currently up, then
there may be a loose connection in the loop plant, or the loop is
barely usable. Check the Margin. If the Margin is normal, there may
be a loose connection. If the Margin is low, try reducing the speed
of the DSL port.
8000-A2-GB20-10
June 1997
8-7
Diagnostics and Troubleshooting
Network Problems
Review the following symptoms and possible solutions to help in solving any
problems you may encounter on the HotWire DSLAM.
PROBLEM:
Intranetworking communication problems.
ACTION:
1. Verify that the internetworking network cables meet IEEE
standards for local Ethernet networks.
2. Check cable connections to other computers in the network.
3. Determine whether or not your system is the only one in the
network with a problem.
PROBLEM:
Cannot PING or Telnet after entering IP address.
ACTION:
1. Restart the interface (see Configuration → Interfaces (A–C)
Chapter 6).
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, Chapter 4).
4. Check to see that the IP address is unique and matches the
class of the subnet. (For example, if using a Class B
address, make sure the first two numbers match.)
5. Check to see that the sub-net mask is set correctly. If in
doubt, leave the default sub-net mask (see Who Am I
screen, Chapter 4).
6. Check to see that the IP next-hop address matches that of
the router (if communicating through IP router) (see
Configuration → IP Router (A–E) Chapter 5).
7. Verify that your address, port, or IP protocol is not being
filtered from the port or bridge. (Turn off the filters if you are
not sure.)
8. Check to see that the port in question is forwarding traffic.
9. Check received packets (see Monitoring → Network
Protocol (B–D) Chapter 7).
8-8
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
Slow Performance
PROBLEM:
Performance is slow.
ACTION:
1. Verify that there are enough buffers on the System Info
screen (see Monitoring → Card Status (B–A) Chapter 7).
2. Check the Ethernet Statistics screen for excessive Cycle
Redundancy Check (CRC) errors (see Monitoring →
Physical Layer (B–B) Chapter 7).
Excessive Collisions
PROBLEM:
Excessive collisions on an Ethernet port.
ACTION:
1. Determine if your network is too large or long (single
Ethernet cable or end-to-end cable).
2. Check to see if there are too many repeaters.
3. Check to see if there are too many users on a single
Ethernet.
8000-A2-GB20-10
June 1997
8-9
Diagnostics and Troubleshooting
No SNMP Connection Established
PROBLEM:
Cannot establish an SNMP session/connection.
ACTION:
1. Try to ping the MCC card and/or DSL card.
2. If you cannot, then check the routing tables in the MCC card
and DSL card.
3. If you can, check to see that you have entered an IP
address (see Who Am I screen, Chapter 4).
4. Check to see if the communiity string is correct.
5. If IP Address Security is enabled, check to see that Network
Management’s IP address has been entered correctly in the
MCC card’s and DSL card’s permission list and that it has
proper access.
6. Check to see if you have properly configured the SNMP
parameters (see Monitoring → Network Protocol (B–D)
Chapter 5, especially SNMP Security: Configuration →
SNMP (A–P) Chapter 6).
7. Enable an SNMP, then reset the software or power the
router.
Filters Not Working
PROBLEM:
Filters are not working properly.
ACTION:
1. Check to see that filters have been configured properly (see
Configuration → Interfaces (A–C) Chapters 4 and 5).
2. Check to see if there is a conflict with the order of the filter
tests. They should perform in the following order:
Port-to-Port (PTOP), Host-to-Port (HTOP), Host-to-Host
(HTOH), Protocol Type (PROTOCOL), Bit Filtering.
3. Check to see interface has been restarted since filters were
added, deleted, or changed.
8-10
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
IP Routing Problems
PROBLEM:
Stations cannot communicate through the router.
Incorrect IP address.
ACTION:
1. Check to see that IP addresses have been configured
correctly (see Who Am I screen Chapter 4, and
Configuration → Interfaces (A–C) Chapters 5 and 6).
2. Go to: Configuration → Interface → Control and check the
state of the system for e1a Bridge Up (forwarding).
Incorrect Subnet Mask
PROBLEM:
Stations cannot communicate.
ACTION:
1. Check to see that IP addresses have been configured
correctly (see Who Am I screen Chapter 4, and
Configuration → Interfaces (A–C) Chapters 5 and 6).
2. Go to: Configuration → Interface → Control and check the
state of the system for e1a Bridge Up (forwarding).
No PPP Traffic
PROBLEM:
PPP circuit is forwarding no traffic.
ACTION:
1. Verify that the DSL link is up.
2. Go to: Configuration → Interface → Control and check the
state of the system.
3. If the IP state is up and the local and peer IP addresses are
displayed, IPCP is completed.
4. If the IP state is missing from the screen, check that the port
has an IP address assigned.
5. If the IP state is missing from the screen, check that the port
has an IP address assigned.
8000-A2-GB20-10
June 1997
8-11
Diagnostics and Troubleshooting
No Response at Start Up
PROBLEM:
DSL cards do not respond at start-up after rebooting chassis.
ACTION:
1. Reset the MCC card.
2. Be sure LEDs go through the reset sequence once. Then, a
second time after 15–20 seconds.
3. Reconfigure each DSL card (see Configuration → Card
Status (A–A) Chapter 4).
System Does Not Recognize New DSL Cards
PROBLEM:
System does not recognize new DSL cards with new
addresses (Addresses not pre-configured on MCC card).
ACTION:
1. Configure new DSL cards from MCC screen.
2. Restart s1b interface (see Configuration → DSL Cards
(G–A,B) Chapter 4).
3. Reset DSL card from the MCC screen (see Configuration →
DSL Cards (G–A,B) Chapter 4).
4. Pull the card out and push it back in.
Unusual Number of TRAPS
PROBLEM:
DSL cards not using MCC Router ID as source address for
traps.
ACTION:
1. In standard configuration, MCC and DPS are in separate
sub-nets and Router ID is the same as IP Base Address of
MCC’s LAN (e1a) interface. Set the Router ID to the mgt. IP
address on MCC’s LAN interface.
2. Set this as “Base IP Address” for LAN interface.
3. Reset MCC and all cards (see Configuration → DSL Cards
(G–A,B) Chapter 4 ).
8-12
June 1997
8000-A2-GB20-10
Diagnostics and Troubleshooting
Cannot Communicate with Interface
PROBLEM:
Cannot communicate with Ethernet or other interface after
adding, changing, or deleting IP addresses on DSL or MCC
card.
ACTION:
1. When you add, change, or delete addresses on a DSL card,
you must restart that interface (see Configuration →
Interfaces (A–B) Chapter 6).
Cannot Upload Configurations to a Unix Server
PROBLEM:
TFTP server denies write permission (Message is “TFTP recv
failure”).
ACTION:
1. Before uploading configurations, create a dummy file and
give it global Read-Write permissions.
2. Configure TFTP host to have Write permissions is specified
directory.
Unexpected Sub-Net Data
PROBLEM:
Proxy ARP not properly set for HotWire 5446 RTU.
ACTION:
1. Reconfigure DSL cards affected.
2. Set Proxy ARP only for HotWire 5446 RTU, not entire
subnet.
Cannot Communicate with HotWire 5446 from MCC Card
8000-A2-GB20-10
PROBLEM:
Error in setting peer address on s1b.
ACTION:
1. Set peer host address to 0. For example, where MCC’s s1b
address is 198.152.180.10. and local sub-net is “180”, peer
address must be set to 198.152.180.0.
June 1997
8-13
Checklist for Configuring the
HotWire DSLAM
A
Overview
This appendix provides a checklist of the mandatory steps required to configure
the MCC cards, DSL cards, and RTUs for the HotWire DSLAM. Use this checklist
as a quick reference for configuring your system.
For specific information on mandatory configuration procedures, see Chapter 4,
Configuring the HotWire DSLAM.
Setting Time and Date
To set the time and date on the MCC card:
Select Configuration → Card Status → Time/Date (A-A-C).
Enter time at the hh.mm (am or pm) prompt.
Enter Broadcast or Unicast at the Client NTP Mode prompt.
Enter the NTP server address at the (nnn.nnn.nnn.nnn) prompt.
Enter 1–24 at the Input Number prompt.
Press Ctrl-z and save changes.
8000-A2-GB20-10
June 1997
A-1
Checklist for Configuring the HotWire DSLAM
Assigning IP Addresses to the Backplane
To assign an IP address to the backplane (s1b):
Select Configuration → Interfaces → IP Network (A-C-B).
Enter the interface name at the Input Interface Name prompt.
Enter the base IP address at the (nnn.nnn.nnn.nnn) prompt.
Enter the base subnet mask at the (nnn.nnn.nnn.nnn) prompt.
Enter the peer IP address at the (nnn.nnn.nnn.nnn) or address pool
prompt.
Enter route type NET (for network) at the Route to peer (host/net):
prompt.
Press Ctrl-z and save changes.
Assigning IP Addresses to the DSL Cards
(Management Domain)
To assign IP addresses to the DSL cards:
Select Configuration → DSL Cards→ Set IP Addresses (A-F-A).
Enter the DSL card subnet mask at the (nnn.nnn.nnn.nnn) prompt. This
is the subnet mask for the backplane (s1b) management subnet.
Enter the IP address for each DSL card at the (nnn.nnn.nnn.nnn)
prompt.
Press Ctrl-z and save changes.
Creating the Default Route
To create the default route:
Select Configuration → IP Router→ Static Routes (A-E-A).
Enter 0 or press Return at the Item Number prompt.
Enter 0.0.0.0 at the Destination (or space to delete route):
prompt.
Press Return at the subnet (nnn.nnn.nnn.nnn) prompt.
Enter the IP address of the default route to the next hop address at the Next
Hop IP Address (nnn.nnn.nnn.nnn) prompt.
Enter 1 at the Input Number prompt.
Press Return at the S/D prompt (Default = Dst).
Press Return at the PA prompt (Default = No).
Confirm the save and Press Ctrl-z.
A-2
June 1997
8000-A2-GB20-10
Checklist for Configuring the HotWire DSLAM
Resetting the MCC Card
After configuring the MCC card, reset the MCC card to install the configuration
settings.
Select Configuration →Card Status → Card Reset (A-A-F).
Enter yes to verify MCC reset.
Wait for the MCC card to reboot.
Press Return.
The Operator Login screen is displayed.
Enter login information.
Selecting a DSL Card to Configure
To select a DSL card to configure:
From the HotWire Chassis Main Menu, select Card Selection.
Enter DSLnn where nn is the number of the DSL card you want to configure
and press Return.
The HotWire DSL menu is displayed.
Select Configuration.
The Configuration Menu is displayed.
Configuring 5446 RTU IP Host Addresses on the
DSL Card
To configure 5446 RTU IP Host Addresses on the DSL cards:
Select Configuration → Interfaces→ IP Network (A-C-B).
Enter the interface name at the Input Interface Name prompt (s1c).
Enter the peer IP address at the (nnn.nnn.nnn.nnn) or address pool
prompt.
Enter route type Host at the Route to peer prompt.
Press Ctrl-z and save changes to exit.
Repeat the above procedure for interfaces s1d, s1e, and s1f (DSL ports 2, 3,
and 4, respectively).
8000-A2-GB20-10
June 1997
A-3
Checklist for Configuring the HotWire DSLAM
Configuring a Static Route to the Network
Management System (on each DSL Card)
To configure a static route to the Network Management System:
Select Configuration → IP Router→ Static Routes (A-E-A).
Enter 0 or press Return at the Item Number (0 to add new record):
prompt to add a new record.
Enter the address of the NMS (nnn.nnn.nnn.nnn) at the Destination
prompt.
At the Subnet prompt, enter either 255.255.255.255 for the host route or
255.255.255.0 for the subnet route.
Enter the backplane IP address of the MCC card (s1b) at the Next Hop IP
Address (nnn.nnn.nnn.nnn) prompt.
Enter 1 at the Input Number prompt to specify the preference.
Confirm the save and Press Ctrl-z.
Assigning IP Addresses to the DSL Cards
(Customer Domain)
To assign IP addresses to the DSL cards:
Select Configuration → Interfaces→ IP Network→ (A-C-B).
Enter the interface name at the Input Interface Name: prompt (e1a).
Enter the IP address at the (nnn.nnn.nnn.nnn) prompt. This address
must be different than the management domain IP address.
Enter the subnet mask at the(nnn.nnn.nnn.nnn) prompt.
Up to 16 IP addresses and subnet masks can be entered. Enter the IP
addresses and subnet masks for each ISP domain supported by the specified
DSL card.
Press Ctrl-z and save changes.
A-4
June 1997
8000-A2-GB20-10
Checklist for Configuring the HotWire DSLAM
Creating Default Routes or Source Routes on the DSL
To create the default route:
Select Configuration → IP Router→ Static Routes (A-E-A).
Enter 0 or press Return at the Item Number prompt.
To create a default route, enter 0.0.0.0 at the Destination (or space to
delete route): prompt.
To create a static route, enter the source route address at the Destination
(or space to delete route) prompt.
Press Return at the subnet (nnn.nnn.nnn.nnn) prompt.
To create a default route, enter the IP address of the default route at the
Next Hop IP Address (nnn.nnn.nnn.nnn) prompt.
To create a source route, enter the IP address of the source route at the
Next Hop IP Address (nnn.nnn.nnn.nnn) prompt.
Enter 1 at the Input Number prompt.
Enter src or dst at the Source (Src)/Destination (dst) prompt.
Press Return at the PA prompt (Default = No).
Confirm the save and Press Ctrl-z.
Resetting the DSL Card
To reset the DSL card:
Type Ctrl-t or Ctrl-a to go to the HotWire DSL menu.
Select Card Selection.
Enter MCC.
Select Configuration → DSL Cards→ Reset Slot→ (A-G-B).
Enter dslnn, where nn is the slot number for the DSL card you just
configured.
Enter Y at the prompt to confirm.
If you have entered yes, verify that the LEDs on the DSL card go through the
reset sequence once, and then a second time after approximately
15–20 seconds.
8000-A2-GB20-10
June 1997
A-5
Checklist for Setting Up User
Accounts on the MCC and DSL Cards
B
Overview
User accounts provide security for the DSLAM by requiring that anyone who is
trying to log onto the system has a valid password to gain access. User accounts
on the MCC provide security to users accessing the system from the VT100
terminal interface and via Telnet over the management domain LAN.
It is recommended that user accounts also be set up for each DSL card, even if
you do not intend to telnet directly to the DSL cards, so that no unauthorized
telnet sessions can be made. Each card will support up to 10 user accounts with
either Operator (read only) or Administrator (read/write) permissions.
MCC User Accounts (For Telnet Terminal Access to
MCC Card)
Use the following checklist when configuring MCC user accounts.
From the MCC Main menu select Configuration → Users → Accounts
(A-D-A).
Enter the login name (up to 15 characters). This field is case sensitive.
Enter the password for this account (up to 15 characters). This field is case
sensitive.
Re-enter the password.
Enter the privilege level (operator for read only access, administrator for
read/write access).
Enter Y to save changes and Ctrl-z to return to the HotWire Chassis Main
Menu tree.
8000-A2-GB20-10
June 1997
B-1
Checklist for Setting Up User Accounts on the MCC and DSL Cards
Reboot Card (MCC)
Use the following checklist to reboot MCC card after changes have been made.
From the MCC Main menu select Configuration → Card Status → Card Reset
(A-A-F).
Enter Y at the yes/no prompt.
At the initial screen display after reboot, press Return.
Enter Operator ID.
Enter Operator Password.
The HotWire Chassis Main Menu is displayed.
DSL User Accounts
Use the following checklist when configuring DSL user accounts (if telneting
directly to the DSL card).
From the DSL Main menu select Configuration → Users → Accounts (A-D-A).
Enter the login name (up to 15 characters). This field is case sensitive.
Enter the password for this account (up to 15 characters). This field is case
sensitive.
Re-enter the password.
Enter the privilege level (operator for read only access, administrator for
read/write access).
Enter Y to save changes and Ctrl-z to return to the HotWire Chassis Main
Menu tree.
Reboot Card (DSL)
Use the following checklist to reboot DSL cards after changes have been made.
At the Card Selection screen, enter DSLnn.
From the DSL Main menu select Configuration → Card Status → Card Reset
(A-A-F).
Enter Y at the yes/no prompt.
After reboot, enter MCC at the Card Selection screen.
Select Applications → Telnet (C-B).
Enter the Host Name of IP Address of Ethernet card and verify that you can
telnet there.
Enter Operator ID.
Enter Operator Password.
The HotWire Chassis Main Menu is displayed.
B-2
June 1997
8000-A2-GB20-10
Checklist for Setting Up SNMP
Features
C
Setting Up SNMP Features
Use the following checklist when setting up SNMP features.
Management System Source Validation for MCC
From the MCC Main menu select Configuration → SNMP → Security (A-F-A).
Enable IP address security validation.
Enter the IP address of up to five NMS managers that will be permitted
access to the MCC card.
Enter access permission to be granted to each NMS system
(ReadOnly(ro)/Read/Write(rw)/NoAccess(na).
MCC SNMP Community Strings and Authentication Failure Trap
While optional, it is recommended for additional security that source validation is
enabled.
From the MCC Main menu select Configuration →SNMP → Communities/Traps
(A-F-C).
Enter Read Only community string name(s).
Enter Read Write community string name(s).
If desired, enable the Authentication Failure Trap.
Enter the IP address of addresses of the NMS.
8000-A2-GB20-10
June 1997
C-1
Checklist for Setting Up SNMP Features
Management System Source Validation for DSL cards
From the DSL Main menu select Configuration → SNMP → Security (A-F-A).
Enable IP address security validation.
Enter the IP addresses of up to five NMS managers that will permitted access
to this DSL card.
Each card does not have to have the same set of managers as any other
card or as the MCC.
Enter access permission to be granted each NMS system
(ReadOnly(ro)/Read/Write(rw)/NoAccess(na).
DSL SNMP Community Strings and Authentication Failure Trap
From the DSL Main menu select Configuration → SNMP→ Communities/Traps
(A-F-C).
Enter Read Only community string name(s).
Enter Read/Write community string name(s).
If desired, enable the Authentication Failure trap.
Enable DSL Port Traps
From the DSL Main menu select Configuration → Ports → DSL Ports (A-B-B).
Select a DSL port.
If desired, enter a value for the Margin Threshold.
If desired, enter a value for the Link Down Count Threshold.
If desired, enter a value for the Error Rate (minute) Threshold.
If desired, enter a value for the Error Rate (hour) Threshold.
Reset the port.
C-2
June 1997
8000-A2-GB20-10
Download and Apply Code
D
The Download code menu option on the HotWire DSLAM 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 can’t, 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 DSL cards in
your system. When a software upgrade affects both the MCC and the DSL cards,
you must download and apply a new version of code into each of the DSL cards
before you download and apply a new version of code into the MCC.
Downloading Code
From the MCC or DSL Configuration main menu select Configuration → Card
Status → Download Code (A-A-G). This selection brings you to the Download
submenu. Select Download Code.
Scenario One: Fully Operational System
Enter the path and image file name and the TFTP Server IP address and select
yes to begin the file transfer. When you are downloading the new firmware, this
does not impact service or the operation of the system. Depending on the
network traffic, this download may take a minimum of 10 minutes. You may apply
the newly acquired firmware load at any time following the successful transfer.
CAUTION:
When the download is completed, if you elect to apply the code, service
will be disrupted while the card restarts and the new code is installed.
8000-A2-GB20-10
June 1997
D-1
Download and Apply Code
Scenario Two: Download Only System
In order for the system to become fully functional again, you must start the
Download Code file transfer procedure. Enter the image file name and the TFTP
Service IP address and select yes to begin the file transfer. When the file transfer
has successfully completed, the system will automatically restart and become
fully functional with the newly acquired firmware.
Apply Code
From the MCC or DSL COnfiguration Main Menu select Configuration → Card
Status → Download Code (A-A-G). This selection brings you to the Download
submenu. Select Apply Code.
D-2
June 1997
8000-A2-GB20-10
Navigation Keys
E
The following table lists navigation keys and their definitions. These commands
are used to move around the HotWire DSLAM menus and screens.
8000-A2-GB20-10
Keys
Definition
Ctrl-a
Moves Home or to the top of the menu
Ctrl-b
Moves left
Ctrl-c
Moves Home or to the top of the current menu
Ctrl-f
Moves right
Ctrl-k
Moves up to the previous menu selection or entry field
Ctrl-l
Refreshes the screen
Ctrl-n
Moves down or to the next selection
Ctrl-p
Moves up or to the next selection
Ctrl-r
Resets counters (on monitoring statistics displays)
Ctrl-t
Moves Home or to the top of the menu
Ctrl-u
Clears the current input or prompt line
Ctrl-v
Displays a pop-up list of all interfaces on IP Network screen.
Displays a pop-up list of all accounts in system on Configure
Accounts screen.
Ctrl-y
Moves Home or to the top of the menu
Ctrl-z
Moves back or exits from screen
Up arrow
Moves up to the previous menu selection or entry field
Down arrow
Moves down to the next menu choice or entry field
Left arrow
Moves left to the previous menu box or entry field
Right arrow
Moves right to the next menu box or entry field
Enter or Return
Accepts entry
Tab
Moves down or to the next selection
?
Displays the Online help screen
June 1997
E-1
Traps
F
Traps are configured via a Telnet or terminal session. The addition or removal of
a card or another hardware component within the HotWire DSLAM 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).
The DSL card sends the following traps.
Event
Trap Class
Comment
CCN (Configuration
Change Notice)
warning
Configuration changed or software upgraded
DSL link up or down
minor
Number of link down events above
threshold. This rate is limited to once every
15 minutes.
Authentication failure
minor
SNMP community string, Telnet passwords
Port speed
warning
DSL port speed is outside of the specified
range
Transitions threshold
exceeded
Decrease to lower bound
8000-A2-GB20-10
—
Ethernet link down
major
—
Ethernet link up
normal
—
DSL margin low
minor
Margin estimate below customer set
threshold
DSL error rate high
minor
Error rate estimate above customer set
threshold
Cold start
warning
—
Test start
normal
(Future release)
Test clear
normal
warning
Test over
June 1997
F-1
Traps
The MCC card sends the following traps.
F-2
Event
Trap Class
Comment
CCN (Configuration
Change Notice)
warning
Configuration changed or software upgraded
Authentication failure
minor
SNMP community string, Telnet and terminal
passwords
Fan module failure
minor
Fan module reporting subnormal
performance
Fan module restored
normal
Fan module back to normal operation
Power source switch
over/source failure
minor
One of the power sources has failed and the
system is now operating off one source
Power source normal
normal
Both power sources are operating normally
Ethernet link down
major
—
Ethernet link up
normal
—
No response to slot poll
major
Card is there but not functioning
New card detected on poll
warning
—
Cold start
warning
MCC card is being powered up
Warm start
warning
Power on reset
Test start
normal
Test started
Test clear
normal
Test over
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
G
MIB Description Overview
The network service provider for the RTU provisions the IP address into the 5446
RTU host routes. The SNMP agent in the 5446 RTU is used to manage IP
address and subnet mask information.
An NMS communicates via SNMP to obtain or set variables within the SNMP
agent’s control. The 5446 RTU supports MIB objects relative to their RFC
description.
The following sections explain:
Configuring IP Address Information into a 5446 RTU
Using Enterprise MIBs supported by the RTU
Using Standard MIBs (MIB II)
SNMP Traps supported by the RTU
The IP Injection Enterprise MIB must be used to finalize the 5446 RTU setup. The
Enterprise MIBs are available on the World Wide Web site listed on Page A
(the reverse side of this document’s title page).
8000-A2-GB20-10
June 1997
G-1
5446 RTU MIB Descriptions
The OID (Object ID) for the Enterprise IP Injection MIB is 1.3.6.1.1795.2.24.2.11.
From an SNMP workstation, access, download, and compile the Enterprise MIB
(pdndce.mib).
IP Injection MIB OID
iso (1)
org (3)
dod (6)
internet (1)
private (4)
mgmt (2)
experimental (3)
enterprises (1)
mib-2 (1)
thenewpdn (1795)
thenewpdn-products (1)
thenewpdn-mgmt (2)
paradyne (24)
pdn-common (2)
pdn-ipinjection (11)
97-15568
Configuring IP Address Information into a 5446 RTU
This section covers host routes and customer domain IDs.
Host routes use the IP address information pertaining to the end users supported
by the 5446 RTU.
Customer domain IDs use the IP address information pertaining to the 5446 RTU
within the customer domain. Refer to the HotWire 5446 Remote Termination Unit
(RTU) Installation Instructions for additional end user information.
MIB Browser Techniques
There are two MIB browser techniques. The IP Injection MIB allows the use of a
null entry or a table index. Use a MIB browser to access the ipInjectionTable.
Refer to the Assigning IP Addresses to the DSL Card LAN (Customer Domain)
section, Chapter 4, for additional IP address information.
From a MIB browser, do a single set with a unique entry containing the required
fields. Refer to Table G-1 for IP injection group objects.
G-2
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Using the null entry:
" Procedure
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. Do a Get or Query before continuing to the next entry.
Using the table index:
" Procedure
1. Enter the three fields into the Index:
— ipInjectionType
— ipInjectionAddress
— ipInjectionMask
2. Enter the status value:
— ipInjectionStatus
3. Select Set.
IP Injection MIB (pdn-common 11)
The following pdn-IP Injection Objects (pdn-common 11) contain IP address
information. Information built from this table:
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.
IP Injection Table supports:
H
One NAP IP Address injected as the Peer IP Address from the DSLAM. The
NAP IP Address cannot be added, deleted, or changed from SNMP.
H
Four Customer Domain IDs
H
Thirty-two Host Routes and/or Subnets
If a null entry does not appear, the table is full.
Delete entries from the table by setting the ipInjectionStatus to invalid.
8000-A2-GB20-10
June 1997
G-3
5446 RTU MIB Descriptions
Table G-1. IP Injection Group Objects (ipInjectionTable 1)
Object
Description
Setting/Contents
ipInjectionType
(ipInjectionEntry 1)
Type of address for each entry.
null(1) – Use to add a row. Factory defaults:
Changing the NAP IP address
resets the database and an
entry of serviceProvider(3) or
host(4) is cleared.
– Address: 0.0.0.0
– Mask: 255.255.255.255
– Status: static
nap(2) – Network Access Provider IP entry. Cannot be
added, modified, or deleted from SNMP.
serviceProvider(3) – Network Service Provider IP
entry.
host(4) – Host IP entry.
ipInjectionAddress
(ipInjectionEntry 2)
IP address information.
IP address for Customer Domain ID, and NAP IP
address:
nnn.255.255.255 – Range for the first byte nnn is 001
to 223, with the exception of 127. Range for the
remaining three bytes is 000 to 255.
IP address for Host Route:
nnn.255.255.255 – Range for the first byte nnn is 001
to 239, with the exception of 127. Range for the
remaining three bytes is 000 to 255.
ipInjectionMask
(ipInjectionEntry 3)
Subnet mask.
Subnet mask cannot be 0.0.0.0.
ipInjectionStatus
(ipInjectionEntry 4)
Status of each entry.
Specify address status. When the RTU is reset, the static
addresses are saved and dynamic addresses are not
saved. Default is static(1).
static(1) – Static addresses are assigned for the
duration of the service subscription.
dynamic(2) – Dynamic addresses are only assigned
for the duration of the application session.
invalid(3) – Used to delete an entry from the table.
Additional pdn-common MIBs Supported
The RTU also supports the following pdn-common MIBs:
G-4
Device Status Group, pdn-common 4
Device Traps Manager Group, pdn-common 9
Device Control Group, pdn-common 10
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Device Status Group (pdn-common 4)
The pdn-devStatus is supported. The status information is lost if the RTU is
reset. The RTU supports:
devHealthAndStatus (pdn-devStatus 1) stores the RTU health and status
information. Used by some traps to send device failure information to an
NMS. Format:
— Customer Information Field:Development Information Field
The Customer Information field will contain one or more of the following
separated by a semi-colon.
— Device Operational
— Device Failure
— Selftest Failed
— Test in Progress – BERT
devSelfTestResults (pdn-devStatus 2) stores the results of a self test.
Format:
— Customer Information Field:Development Information Field
The Customer Information field will contain one or more of the following
separated by a semi-colon.
— PASS
— EEPROM Failure
— General Device Failure
Either device failure will display a failure code. Call your service
representative with the failure code.
Device Traps Manager Group, pdn-traps (pdn-common 9)
Controls the SNMP managers to which the RTU reports traps. Fully supported by
the unit. Factory default is no table entry. Maximum number of Traps Manager
table entries is six.
devTrapMgrCircuit (devTrapMgrEntry 3) supported as read only. The RTU
allows one circuit and sets this object to 0.
devTrapMgrSubCircuit (devTrapMgrEntry 3) supported as read only. The
RTU allows one subcircuit and sets this object to 0 (zero).
Device Control Group, pdn-control (pdn-common 10)
The devHWControlReset object is supported for resetting the RTU: Reset(2).
The value of noOp(1) is reserved for software download mode.
8000-A2-GB20-10
June 1997
G-5
5446 RTU MIB Descriptions
XDSL Interface Group
The DSLAM is the primary source for statistics and DSL statistics are provided for
the RTU DSL link. Statistics for longer intervals are available from the DSLAM as
remote statistics. The following hot_xdsl (xdsl 3) objects are provided to support
the remote site xDSL interface. They are read only.
The specific DSL statistics entry is indexed in xdslDevIfStatsTable 1 as:
xdslDevIfIndex
xdslDevIfStatsInterval
Table G-2. XDSL Device Group Objects (xdslDevice 1)
Object
Description
Setting/Contents
xdslDevIfStatsIfIndex
(xdslDevIfIntervalStatsEntry 1)
Provides the DSL interface as
described in the ifTable.
2
xdslDevIfStatsIfInterval
(xdslDevIfIntervalStatsEntry 2)
Provides the DSL link statistics.
Supports only: current15Minutes
(6).
xdslDevIfStatsUpStreamSpeed
(xdslDevIfIntervalStatsEntry 6)
Provides the speed upstream
from the RTU to the central site.
Refer to ifTable ifSpeed for the
downstream speed.
Supported as read only.
xdslDevIfStatsRemoteReceiverGain
(xdslDevIfIntervalStatsEntry 14)
Provides the receiver gain for
the RTU.
Supported as read only.
xdslDevIfStatsRemoteRecMargin
(xdslDevIfIntervalStatsEntry 15)
Provides the receiver SNR
margin for the RTU.
Supported as read only.
xdslDevIfStatsRemoteRecTransmit Power
(xdslDevIfIntervalStatsEntry 17)
Provides the transmit power for
the RTU.
Supported as read only.
xdslDevIfStatsRemoteRecErroredSeconds
(xdslDevIfIntervalStatsEntry 19)
Provides the errored seconds
for the RTU.
Supported as read only.
xdslDevIfStatsRemoteRecSeverlyErrored
Seconds (xdslDevIfIntervalStatsEntry 20)
Provides the severely errored
seconds for the RTU.
Supported as read only.
xdslDevIfStatsRemoteOctetsCorrected
(xdslDevIfIntervalStatsEntry 21)
Provides the Reed Solomon
Supported as read only if Reed
number of bytes corrected at the Solomon is turned on.
RTU.
xdslDevIfStatsRemoteOctetsNotCorrected
(xdslDevIfIntervalStatsEntry 22)
Provides the Reed Solomon
Supported as read only.
number of bytes not corrected at
the RTU.
xdslDevIfStatsRemoteReceivedOctets
(xdslDevIfIntervalStatsEntry 23)
Provides the number of octets
received by the RTU.
Supported as read only.
xdslDevIfStatsRemoteReceivedPkts
(xdslDevIfIntervalStatsEntry 24)
Provides the number of packets
received the RTU.
Supported as read only.
xdslDevIfStatsRemoteTransmittedOctets
(xdslDevIfIntervalStatsEntry 27)
Provides the number of octets
transmitted by the RTU.
Supported as read only.
xdslDevIfStatsRemoteTransmittedPkts
(xdslDevIfIntervalStatsEntry 28)
Provides the number of packets
transmitted by the RTU.
Supported as read only.
G-6
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Community Table
The following Community table ent-8800 (pdn-xdsl 3) MIB objects are supported
by the RTU. This table allows four entries. When a new NAP IP address is
detected, the Community table resets to factory defaults.
Table G-3. Enterprise 8800 Group Objects (xdslDevice 1)
Object
Description
Setting/Contents
communityName
(CommunityTableEntry 1)
Corresponds to the SNMP
community.
Two community name default values:
NOTE:
Any change to the
RTU community
name by an NMS
must also be made
at the DSLAM.
private – Read/write access for all objects.
public – Read only for all objects.
The community name entry restrictions are:
– Must have 1 – 32 characters
– No blanks
– Printable ASCII characters only
– No duplicate entries
If the community string used by your MIB browser
is read-only access, you will not be able to query
read/write entries in this table.
MIB II Groups
There are several standard MIB II groups supported by the RTU.
8000-A2-GB20-10
June 1997
G-7
5446 RTU MIB Descriptions
System Group
System Group MIB II objects are fully supported by the RTU.
Table G-4. System Group Objects
Object
Description
Setting/Contents
sysDescr
( system 1)
Provides a full name and version identification for the
system’s hardware and software.
PARADYNE RADSL
Model: nnnn-xn-nnn;
S/W Release: yy.yy.yy;
H/W Revision: zzzz-zzz;
Serial Number: sssssss
sysObjectID
( system 2)
Identifies the network management subsystem.
1.3.6.1.4.1.1795.1.14.9.9.1
sysContact
(system 4)
Provides the textual identification of the contact person
for this managed unit.1
ASCII character string. Set by the
user. When the NAP IP address is
reset, this field is cleared.
sysName
(system 5)
Provides an administratively-assigned name for this
managed unit.1
ASCII character string. Set by the
user. When the NAP IP address is
reset, this field is cleared.
sysLocation
(system 6)
Provides the physical location for this managed unit.1
ASCII character string. Set by the
user. When the NAP IP address is
reset, this field is cleared.
sysServices
( system 7)
Functionality supported:
Object is set to 1+2+4+8 (15).
physical (1 ) – Layer 1 functionality for DSL and
Ethernet interfaces.
datalink/subnetwork ( 2 ) – Layer 2 functionality PPP
for DSL interface and LLC for Ethernet.
internet ( 4 ) – Layer 3 functionality ( IP ) for all
management links.
end-to-end ( 8 ) – Layer 4 functionality ( UDP ) for all
management links.
1
The unit supports a 16-character string for this object. The error code BadValue(3) is sent to the NMS if an
attempt is made to write (set) more than 16 characters.
G-8
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Interfaces Group
The Interfaces Group as defined in RFC 1573 consists of an object indicating the
number of interfaces supported by the RTU and an interface table containing an
entry for each interface. Since RFC 1573 is an SNMPv2 MIB, it is converted to
SNMPv1 for support by the RTU.
The following table provides clarification for objects contained in the Interfaces
group when it is not clear how the object definition in RFC 1573 is supported by
the RTU.
Table G-5. Interfaces Group Objects (1 of 2)
Object
Description
Setting/Contents
ifNumber
( interfaces 1)
Specifies the number of interfaces
for this unit in the ifTable.
2
ifIndex
( ifEntry 1)
Provides the index to the interface
table ( ifTable ) and to other tables
as well.
Indexes and values:
When an unsupported index is
entered, noSuchName is returned.
ifDescr
( ifEntry 2)
1 – Ethernet port
2 – RADSL network interface
Supplies text for each Interface:
Text Strings for each interface:
Ethernet
Ethernet Interface:
PARADYNE RADSL
S/W Release: yy.yy.yy;
H/W Revision: zzzz-zzz
RADSL Network
RADSL Network:
PARADYNE RADSL
S/W Release: yy.yy.yy;
H/W Revision: zzzz-zzz
ifType
( ifEntry 3 )
Identifies the interface type based
on the physical/link protocol(s),
right below the network layer.
Supported values:
ethernetCsmacd(6) – Used for Ethernet.
radsl( 95 ) – Used for RADSL network
interface.
ifSpeed
( ifEntry 5 )
Provides the current downstream
speed for the RADSL interface.
Display of DSL service provider to RTU
downstream speed.
ifPhysAddress
( ifEntry 6)
Identifies the MAC address for the
Ethernet interface.
RTU’s MAC address for the Ethernet interface.
ifAdminStatus
( ifEntry 7 )
Provides interface status.
up(1) – The interface is enabled.
down(2) – The interface is disabled.
Supported as read only.
8000-A2-GB20-10
June 1997
G-9
5446 RTU MIB Descriptions
Table G-5. Interfaces Group Objects (2 of 2)
Object
Description
Setting/Contents
ifOperStatus
( ifEntry 8 )
Specifies the current operational
state of the interface.
Ethernet Interface:
– up(1) – Physical connection
– down(2) – No physical connection
RADSL Network Interface:
– up(1) – DSL/PPP link is established
– down(2) – DSL/PPP link is not
established
– testing(3) – Test active on RADSL
network interface
ifInOctets (ifEntry 10)
Collects input statistics on data
received by the interface.
interface
An integer number.
ifInUcastPkts (ifEntry 11)
ifInNUcastPkts (ifEntry 12)
ifInDiscards (ifEntry 13)
ifInErrors (ifEntry 14)
ifInUnknownProtos
(ifEntry 15)
ifOutOctets (ifEntry 16)
Collects output statistics on data
received by the interface.
interface
ifOutUcastPkts(ifEntry 17)
ifOutNUcastPkts (ifEntry 18)
ifOutDiscards (ifEntry 19)
ARP messages discarded after
address resolution are counted in
ifOutDiscards.
ifOutErrors (ifEntry 20)
Collects output statistics on data
received by the interface.
ifSpecfic
(ifEntry 22)
Displays 0.0, Not in Service.
G-10
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Extension to Interface Group
This extension contains additional objects for the Interface table as defined in
RFC 1123. Supports only the following objects.
Table G-6. Extension to Interface Group Objects (ifXTable)
Object
Description
Setting/Contents
ifName
(ifXEntry 1)
Provides name of the interface.
Interface text strings:
Ethernet Interface
RADSL Network
ifHighSpeed
(ifXEntry 15)
Reflects the ifSpeed setting for the interface.
This object is supported as read
only.
ifConnectorPresent
(ifXEntry 17)
Indicates whether there is a physical connector for the
interface.
true(1) – Will always have this
value.
IP Group
The Internet Protocol Group objects are supported by the RTU for all data paths
that are currently configured to carry IP data to/from the RTU. All of the objects in
the IP Group, except for the IP Address Translation table, are fully supported.
The following table provides clarification for objects contained in the IP group
when it is not clear how the object definition in MIB II is supported by the RTU.
Table G-7. IP Group Objects (1 of 2)
Object
Description
Setting/Contents
ipForwarding
(ip1)
Specifies whether the RTU is acting as a next-hop IP
address for forwarding of datagram received by, but not
addressed to, the RTU.
Supports only the following value:
ipDefaultTTL
(ip2)
The table value is set by the SNMP manager.
64 is the default. The number must
be between 15 and 255 or the RTU
sends SNMP error code
badValue(3).
ipAddrTable
(ip20)
The address table displays Service Domain and NAP
Domain IP addresses.
Supported. One ifIndex displayed
for each IP address support by the
RTU. One subnet mask is
displayed. An unique address can
have different subnet masks in
different Customer Domains.
Supported as read only.
8000-A2-GB20-10
June 1997
forwarding(1) – The RTU is
acting as a next hop router.
G-11
5446 RTU MIB Descriptions
Table G-7. IP Group Objects (2 of 2)
Object
Description
Setting/Contents
ipRouteTable
(ip21)
Due to indexing, not all entries into the IP Injection table
will appear in the IP Route table.
ipRouteMetric1 – Defaults to
Supported as read only.
ipRouteNextHop – Defaults to
1 hop.
0.0.0.0.
ipRouteType – Defaults to
i di
indirect.
t
ipRouteProto – Route added or
changed by SNMP set. Set to
netmgmt(3) by the software.
May also have the following
value:
– other(1)
th (1) – Temporary
T
route
t
added by IP.
ipRouteAge – Reflects the value
of the time-to-live for the route (in
seconds). Defaults to 999
(permanent route).
ICMP Group
The ICMP (Internet Control Management Protocol) Group objects are fully
supported.
UDP Group
The UDP (User Datagram Protocol) Group objects are fully supported.
SNMP Group
The SNMP Group objects that apply to an SNMP management agent are fully
supported. The following objects apply only to an NMS and return a (0) zero
value if accessed.
G-12
snmpInTooBig (snmp 8)
snmpInNoSuchNames (snmp 9)
snmpInBadValues (snmp 10)
snmpInReadOnlys (snmp 11)
snmpInGenErrs (snmp 12)
snmpInGetResponses (snmp 18)
snmpInTraps (snmp 19)
snmpOutGetRequests (snmp 25)
snmpOutGetNexts (snmp 26)
snmpOutSetRequests (snmp 27)
snmpEnableAuthenTraps (snmp 30)
June 1997
8000-A2-GB20-10
5446 RTU MIB Descriptions
Transmission Group
The RTU also supports the Ethernet-like MIB, RFC 1643. Objects in the
Transmission Group are supported for the Ethernet interface. These objects are
defined through other Internet-standard MIB definitions rather than within MIB II.
Table G-8. Transmission Group Objects
Object
Description
dot3
( transmission 7 )
For the Ethernet-like MIB, supported on the Ethernet Interface:
dot3StatsIndex
dot3StatsAlignment Errors
dot3StatsFCSErrors
dot3StatsSingleCollisionFrames
dot3StatsMultipleCollisionFrames
dot3StatsDeferredTransmissions
dot3StatsLateCollisions
dot3StatsExcessiveCollisions
dot3StatsInternalMacTransmitErrors
dot3StatsFrameTooLongs
dot3StatsInternalMacReceiverErrors
The following MIB II groups are not supported:
Address Translation Group
Exterior Gateway Protocol ( EGP) Group
Interfaces Group
— Interface Test
— Generic Receive Address
TCP Group
SNMP Traps
This section describes the RTU’s compliance with SNMP standards and any
special operational features for the SNMP traps supported. The RTU supports the
following user interface traps.
8000-A2-GB20-10
authenticationFailure
warmStart
Enterprise-specific traps
June 1997
G-13
5446 RTU MIB Descriptions
Standard Traps
Standard Trap
Description
authenticationFailure Failed attempts to
access the RTU.
Variable-bindings sent.
Possible Cause
Community string used is not in the
Community Table.
Use of real only community string for
Set PDU.
warmStart
The RTU has been
resetiby an NMS.
An NMS sent a Reset command
through the devHWControlReset object.
Enterprise-Specific Traps
The Enterprise-Specific traps indicate that an enterprise-specific event has
occurred. The following table lists the enterprise-specific traps supported by the
RTU.
G-14
Enterprise-Specific Trap
Description
Possible Cause
enterpriseDeviceFailure(2)
An internal device failure.
Variable-bindings contains
devHealthandStatus from
pdn-devStatus group.
Operating software has
detected an internal device
failure. The RTU is still
operating.
enterpriseSelfTestFailure(3)
A hardware failure of the
unit is detected during the
unit’s self-test. The trap is
generated after the RTU
completes power-on
self-test.
Failure of the RTU’s
hardware components. This
trap is only sent if the
hardware failure still allows
sending traps.
enterpriseFatalReset(7)
Failure occurs and the RTU
resets.
Variable-bindings field
contains device failure
code.
June 1997
8000-A2-GB20-10
Glossary
Address
A symbol (usually numeric) that identifies the interface attached to a network.
Alarm System
Consists of an audible or visual alarm in the central office indicating the rack with an alarm
condition.
ARP
Address Resolution Protocol. The TCP/IP protocol used to dynamically bind a high-level IP
address to a low-level physical hardware address. ARP is only across a single physical
network and is limited to networks that support hardware broadcast.
Backplane
A common bus at the rear of the HotWire 8800 DSL Access System chassis connecting
each DSL card to the MCC card for diagnostic and network management. It also
distributes dc power to each slot.
Bandwidth
The range of frequencies that a circuit can pass. The greater the bandwidth, the more
information that can be sent in a given amount of time.
Bit
Binary digit. The smallest unit of information, representing a choice between a one or a
zero (sometimes called mark or space).
BOOTP
Bootstrap Protocol. Protocol a host uses to obtain startup information , including its IP
address, from a server.
bps
Bits per second. Indicates the speed at which bits are transmitted across a data
connection.
byte
A sequence of successive bits (usually eight) handled as a unit in data transmission.
Central Office
The physical building where all local telephone service wiring is distributed to a
surrounding area.
DNS
Domain Name System. An online distributed database that maps machine names into IP
addresses.
Downstream
In extended networks, the direction in which diagnostic messages flow from the diagnostic
control site to any intermediate links and then to the final tributary modem.
DSL
Digital Subscriber Line.
DSLAM
Digital Subscriber Line Access Multiplexer.
Ethernet
A type of network that supports high-speed communication among systems. It is a 10-Mb/s
standard for LANs. All hosts are connected to a coaxial cable where they contend for
network access using a Carrier Sence 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). This number identifies the Ethernet communications board installed in a PC
and is used to identify the PC as a member of the network.
FTP
File Transfer Protocol. A protocol that allows a user on one host to access, and transfer
files to and from, another host over a network. The FTP application is used to provide file
transfer services across a wide variety of systems through the use of the File Transfer
Protocol (FTP). Usually implemented as application level programs, FTP uses the
TELNET and TCP protocols. The server side requires a client to supply a login identifier
and password before it will honor requests.
8000-A2-GB20-10
June 1997
GL-1
Glossary
HDLC
High-Level Data Link Control. A communications protocol defined by the International
Standards Organization (ISO).
ICMP
Internet Control Management Protocol. Internet protocol that allows for the generation of
error messages, tests packets, and information messages related to IP.
Internet
Worldwide interconnected networks that predominantly use the TCP/IP protocol. The
Internet is a three level hierarchy composed of backbone networks, mid-level networks,
and sub networks.
Intranet
Private network that uses internet software and internet standards. The Intranet is
reserved for use by people who have been given the authority and passwords necessary
to use that network.
IP
Internet Protocol. The TCP/IP standard protocol that defines the IP as a unit of information
passed across an Internet and provides the basis for packet delivery service. IP includes
the ICMP control and error message protocol as an integral part. The entire protocol suite
is often referred to as TCP/IP because TCP and IP are the two most fundamental
protocols.
IP Address
Internet Protocol address. This is a 32-bit address assigned to host on a TCP/IP Internet.
The IP address has a host component and a network component.
ISN
Interservice Network.
ISP
Internet Service Provider.
LAN
Local Area Network. A network that spans a small geographic area (e.g., a building).
MAC Address
Areas of memory your CPU uses to distinguish between the various peripheral devices
connected to your system when transferring or receiving data.
margin
DSL margin is defined as the additional noise measured in db that would be added to (or if
the margin is negative, subtracted from) the existing noise present on a given DSL loop to
bring the Bit Error Rate (Ber) to IE-7 (10 7) . Unless the noise source is defined (such as 24
BRI disturbers or 24 DSL disturbers, it is assumed to be Noise Model A (white noise).
MCC
Management Communications Controller.
Multiplex
Combine many low-speed data sources into a single, high speed serial data stream. The
data is coded at transmission, and decoded at reception. Interleave or simultaneously
transmit two or more messages on a single circuit. Some multiplexing techniques include
Frequency Division Multiplexing (FDM), Time Division Multiplexing (TDM), and Statistical
Multiplexing (Stat MUX).
Multiplexing
A method for interleaving several access channels onto a single circuit for transmission
over the network.
Node
A connection or switching point on the network.
Packet
A set of control (header) and data characters (data and control signals) that are treated as
one block or packet within a communications network.
Packet Forwarder
Functional capability of DSL and MCC cards to forward packets to proper I/O ports..
POTS
Plain Old Telephone Service.
PPP
Point-to-Point Protocol. Serial protocol used for operation in a TCP/IP network.
Point-to-Point Protocol. A link layer protocol used by SNMP.
Point-to-Point Protocol, as defined in Internet RFC 1661.
RADSL
Rate Adaptive Digital Subscriber Line. The RADSL design guide 2.0 currently specifies
rates up to 2.240M/952K bps. The RADSL downstream rates are planned to exceed
7.1 Mbps in future releases.
GL-2
June 1997
8000-A2-GB20-10
Glossary
RTU
Remote Termination Unit.
SNMP
Simple Network Management Protocol. A software program housed within a device to
provide SNMP functionality. Each agent stores management information and responds to
the manager’s request for this information.
SNMP Agent
A software program housed within a device to provide SNMP functionality. Each agent
stores management information and responds to the manager’s request for this
information.
SNMP Trap
A notification message to the SNMP manager when an unusual event occurs on a network
device, such as a reinitialization.
Synchronous data
Data transmission that is synchronized by timing signals. Characters are sent at a fixed
rate.
Synchronous
transmission
Transmission in which the data characters and bits are transmitted at a fixed rate with
transmitter and receiver synchronized. This eliminates the need for start and stop bits as
used in asynchronous transmission, and is thus faster and more efficient.
TCP
Transmission Control Protocol. An Internet standard transport layer protocol defined in
STD 7, RFC 793. It is connection-oriented and stream-oriented.
TCP/IP
Transmission Control Protocol/Internet Protocol. The dominant protocol in the worldwide
Internet, TCP allows a process on one machine to send data to a process on another
machine using the IP protocol. TCP can be used as a full-duplex or one-way simplex
connection.
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 for that
host.
Terminal Emulation
Software that allows a session to work as if it was running a specific type of terminal; e.g.,
VT100 or 3270 to logically connect your terminal to a mainframe computer.
TFTP
Trivial File Transfer application. A standard TCP/IP protocol that allows simple file transfer
to and from a remote system without directory or file listing.
T1
A term for a digital carrier facility used to transmit a DS1 formatted digital signal at
1.544 Mbps.
Upstream
In extended networks, the direction in which diagnostic messages flow from the final
tributary diagnostic modem to the intermediate links to the diagnostic control site.
VT100
Terminal emulation mode used for asynchronous communications.
8000-A2-GB20-10
June 1997
GL-3
Index
Configuring a Static Route to the Network Management
System (on each DSL Card), A-4
Control Interface screen, 5-8, 6-8
Control screen, 5-8, 6-8
Creating Default Routes, A-5
Creating the Default Route , A-2
Numbers
10BaseT interface on the MCC and DSL cards (e1a),
4-1
A
Active Interfaces List screen, 7-5, 7-20
Active List screen, 7-3, 7-5, 7-16, 7-20
Active Ports List screen, 7-3, 7-16
Add ARP Entry screen, 5-12, 6-13
Administrator access, 1-4
Administrators Overview, 4-1
Alarms screen, 8-2
Alarms, Major, 8-4
Alarms, Minor, 8-6
Apply Code , D-2
**Apply Download, 5-4, 6-5
Apply Download screen, 5-4, 6-5
ARP Parameters screen, 5-12, 6-13
ARP Table screen, 7-13, 7-29
Assigning IP Addresses to the Backplane, A-2
Assigning IP Addresses to the DSL Cards (Customer
Domain), A-4
Assigning IP Addresses to the DSL Cards
(Management Domain), A-2
D
Delete ARP Entry screen, 5-12, 6-13
Digital Subscriber Line Access Multiplexer, 1-1
DNS Setup screen, 5-2, 6-2
Download Code screen, 5-4, 6-5
Downloading Code , D-1
DSL card, 1-3
DSL Error Stats screen, 7-18
DSL Link Perf screen, 7-18
DSL Link Performance Summary screen, 7-18
DSL Parameters screen, 6-6
DSL Perf Stats screen, 7-18
DSL Performance Stats screen, 7-18
DSL ports (s1c, s1d, s1e, and s1f), naming convention
of ports on the DSL card, 4-1
DSL Ports screen, 6-6
DSL Transmit Stats screen, 7-19
DSL User Accounts, B-2
DSL Xmit Status screen, 7-19
DSLAM, system backplane interface (s1b), 4-1
C
Card Info screen, 5-2, 6-2, 7-2, 7-15
Card Reset screen, 5-4, 6-4
Card Selection screen, 2-13
Chassis Information screen, 3-4
Clear NVRAM screen, 5-3, 6-3
Communities/Traps screen, 5-14, 6-15
Configure Account screen, 5-9, 6-10
Configure DNS screen, 5-2, 6-2
Configuring 5446 RTU IP Host Addresses on the DSL
Card, A-3
E
e1a, 4-1
enterprise, SNMP traps, G-14– G-15
Ether Statistics screen, 7-4, 7-17
Ethernet Ports screen, 5-6, 6-6
Ethernet Statistics screen, 7-4, 7-17
G
General Card Information screen, 7-2, 7-15
General screen, 5-7, 6-7
8000-A2-GB20-10
June 1997
IN-1
Index
H
P
HDLC Bus Statistics screen, 7-4, 7-11, 7-17, 7-26
HDLC Bus Stats screen, 7-4, 7-17
HDLC Statistics screen, 7-11, 7-26
Host Table screen, 5-12, 6-13
HotWire 8800, 1-2
Ping screen, 8-1
Plain Old Telephone Service, 1-1
port naming convention, 4-1
POTS, 1-1
PPP screen, 6-9
I
R
initial setup instructions, 3-1
interface naming convention, 4-1
Interface Status screen, 7-5, 7-20
Interfaces screen, 5-7, 6-7
IP Filter Configuration screen, 5-11, 6-12
IP Host Table screen, 5-12, 6-13
IP Network screen, 5-7, 6-8
IP Router Filters screen, 5-11, 6-12
Reboot Card (DSL), B-2
Reboot Card (MCC), B-2
Remote Termination Unit (RTU), 1-1
Reset DSL Slot screen, 5-15
Reset Slot screen, 5-15
Reset System screen, 5-4, 6-4
Resetting the DSL Card, A-5
Resetting the System, A-3
RFCs, MIB descriptions, G-2– G-18
L
S
Logical Entities screen, 5-13, 6-14
M
Management Communications Controller
card**Empty**, 1-3
Martian Networks screen, 5-10, 6-11
MCC , 1-3
MCC card, 1-3
MCC User Accounts (For Telnet terminal access to
MCC Card), B-1
MIB, descriptions, G-1– G-19
N
navigation keys, 2-1, 2-4
network interface options, 5-7, 5-9, 5-13, 5-15, 6-2,
6-6, 6-7, 6-10, 6-11, 6-14, 7-2, 7-3, 7-5, 7-6,
7-12, 7-15, 7-16, 7-20, 7-21, 7-28, 8-1, 8-2
NVRAM Clear screen, 5-3, 6-3
NVRAM Config Loader screen, 5-4, 6-4
O
objects for MIBs, G-1– G-19
Operator access, 1-4
IN-2
s1b, 4-1
Security screen, 5-13, 6-14
Selecting a DSL Card to Configure , A-3
Selftest screen, 8-2
Set IP Address screen, 5-15
Setting Time and Date , A-1
Setting Up SNMP Features, Enable DSL Port Traps,
C-2
setup instructions (optional), 3-3
Simple Network Management Protocol, 1-3
SNMP, traps, G-13– G-16
SNMP Communities/TRaps screen, 5-14
SNMP Communities/Traps screen, 5-14, 6-15
SNMP Features
Strings and Authentication Failure Trap, C-2
Management System Source Validation for DSL
cards, C-1, C-2
SNMP Features , C-1
SNMP Logical Entities screen, 5-13, 6-14
SNMP Security screen, 5-13, 6-14
Source Routes, A-5
Static Routes screen, 5-10, 6-11
Status screen, 7-5, 7-20
system backplane interface (s1b), 4-1
System Information screen, 5-2, 6-2
June 1997
8000-A2-GB20-10
Index
T
U
Telnet screen, 8-1
Time/Date screen, 4-6, 5-3, 6-3
Traps, F-1
traps, SNMP, G-14– G-17
Troubleshooting, 8-3
Cannot Communicate with HotWire 5446 from MCC
Card, 8-13
Cannot Communicate with Interface, 8-13
Cannot Upload Configurations to a Unix Server,
8-13
Excessive Collisions, 8-9
Filters not Working, 8-10
Incorrect Subnet Mask, 8-11
IP Routing Problems, 8-11
Network Problems, 8-8
No PPP Traffic, 8-11
No Response at Start Up, 8-12
No SNMP Connection Established, 8-10
Slow Performance, 8-9
System Does Not Recognize New DSL Cards, 8-12
Unusual Number of TRAPS, 8-12
Users screen, 5-9, 6-10
8000-A2-GB20-10
W
Who Am I screen, 3-1
June 1997
IN-3