9000-A2-GB33
iMarc™ SLV
Operations Guide
Document No. 9000-A2-GB33-30
October 2003
Copyright © 2003 Paradyne Corporation.
All rights reserved.
Printed in U.S.A.
Notice
This publication is protected by federal copyright law. No part of this publication may be copied or distributed,
transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or
by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express
written permission of Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773.
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, Service, and Training Information
Contact your local sales representative, service representative, or distributor directly for any help needed. For additional
information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or
Paradyne worldwide office locations, use one of the following methods:
„
„
Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at
www.paradyne.com/warranty.)
Telephone: Call our automated system to receive current information by fax or to speak with a company
representative.
—
Within the U.S.A., call 1-800-870-2221
—
Outside the U.S.A., call 1-727-530-2340
Document Feedback
We welcome your comments and suggestions about this document. Please mail them to Technical Publications,
Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to userdoc@paradyne.com. Include the
number and title of this document in your correspondence. Please include your name and phone number if you are
willing to provide additional clarification.
Trademarks
ACCULINK, COMSPHERE, FrameSaver, Hotwire, MVL, NextEDGE, OpenLane, and Performance Wizard are
registered trademarks of Paradyne Corporation. GranDSLAM, GrandVIEW, iMarc, ReachDSL, and TruePut are
trademarks of Paradyne Corporation. All other products and services mentioned herein are the trademarks, service
marks, registered trademarks, or registered service marks of their respective owners.
Patent Notification
iMarc products are protected by U.S. Patents: 5,550,700 and 5,654,966. Other patents are pending.
A
October 2003
9000-A2-GB33-30
Contents
About This Guide
1
„
Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
v
„
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
v
„
Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
„
Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
User Interface and Basic Operation
„
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
„
Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4
„
Screen Work Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5
„
Navigating the Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6
„
2
Keyboard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6
Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-7
Selecting an Entry from a Menu . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
Switching Between Screen Areas . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
Selecting a Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-9
Entering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-9
Screen Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-9
Navigating the Router’s CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-10
CLI Keyboard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-10
Security and Logins
„
Limiting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
„
Controlling Asynchronous Terminal Access. . . . . . . . . . . . . . . . . . . . .
2-2
„
Limiting Dial-In Access via the Modem Port. . . . . . . . . . . . . . . . . . . . .
2-4
„
Controlling ISDN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
ISDN Call Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
„
Disabling ISDN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
Controlling Telnet or FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
Limiting Telnet Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
Limiting FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-7
Limiting Telnet or FTP Access Over the TS Access Management Link
2-8
9000-A2-GB33-30
October 2003
i
Contents
„
3
Controlling SNMP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9
Disabling SNMP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9
Assigning SNMP Community Names and Access Levels . . . . . . .
2-10
Limiting SNMP Access Through IP Addresses . . . . . . . . . . . . . . .
2-11
„
Creating a Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-12
„
Modifying a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13
„
Deleting a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13
„
Controlling Router CLI Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-14
Access Levels (Command Modes) . . . . . . . . . . . . . . . . . . . . . . . .
2-14
Changing Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-15
Status and Statistics
„
Displaying System Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
„
Viewing LEDs and Control Leads . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4
LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-15
Power Module LEDs (Models 9520, 9520-ILM, 9820-45M). . . . . .
3-19
Display LEDs and Control Leads Screen Descriptions . . . . . . . . .
3-20
„
Device Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-24
„
Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-30
System and Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . .
3-31
Network LMI-Reported DLCIs Status . . . . . . . . . . . . . . . . . . . . . .
3-41
IP Path Connection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-43
PVC Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-45
Time Slot Assignment Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-48
DBM Interface Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-50
„
IP Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-60
„
Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-62
Clearing Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . .
3-63
Service Level Verification Performance Statistics . . . . . . . . . . . . .
3-64
DLCI Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-70
Additional Performance Statistics for IP Enabled DLCI . . . . . . . . .
3-72
Frame Relay Performance Statistics . . . . . . . . . . . . . . . . . . . . . . .
3-73
ATM Performance Statistics (9783, 9788). . . . . . . . . . . . . . . . . . .
3-76
VCC Performance Statistics (9783, 9788). . . . . . . . . . . . . . . . . . .
3-77
ESF Line Performance Statistics (9123, 9126, 9128) . . . . . . . . . .
3-79
DDS Line Performance Statistics (9623, 9626) . . . . . . . . . . . . . . .
3-82
T3 Network Line Performance Statistics (9520, 9520-ILM) . . . . . .
3-83
„
ii
3-2
SHDSL Line Performance Statistics (9788). . . . . . . . . . . . . . . . . .
3-86
DBM Call Performance Statistics. . . . . . . . . . . . . . . . . . . . . . . . . .
3-87
Ethernet Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . .
3-88
Trap Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-89
October 2003
9000-A2-GB33-30
Contents
4
Operation and Maintenance
„
„
4-2
Activating the Modem PassThru Feature . . . . . . . . . . . . . . . . . . .
4-2
Canceling Modem PassThru Operation. . . . . . . . . . . . . . . . . . . . .
4-2
Manually Disconnecting the Modem . . . . . . . . . . . . . . . . . . . . . . .
4-3
Verifying Modem Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3
ISDN DBM Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
Forcing Backup (Disruptive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
Placing a Test Call (Nondisruptive) . . . . . . . . . . . . . . . . . . . . . . . .
4-5
Verifying ISDN Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
Verifying That Backup Can Take Place . . . . . . . . . . . . . . . . . . . . .
4-6
FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7
Upgrading System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-9
Upgrading ISDN BRI DBM Software . . . . . . . . . . . . . . . . . . . . . . .
4-10
Determining Whether a Download Is Completed. . . . . . . . . . . . . .
4-11
Changing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-11
Transferring Collected Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-12
„
Turning Off the System Alarm Relay . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13
„
Hardware Maintenance for Models 9520, 9520-ILM, and 9820-45M . .
4-14
Cleaning the Front Panel Assembly . . . . . . . . . . . . . . . . . . . . . . .
4-14
Replacing the Front Panel Assembly. . . . . . . . . . . . . . . . . . . . . . .
4-15
Replacing a Power Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-16
„
5
Modem Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting
„
Problem Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
„
Resetting the Unit and Restoring Communication . . . . . . . . . . . . . . . .
5-3
Resetting the Unit from the Control Menu . . . . . . . . . . . . . . . . . . .
5-3
Resetting the Unit By Cycling the Power . . . . . . . . . . . . . . . . . . . .
5-3
Restoring Communication with an Improperly Configured Unit . . .
5-4
„
Troubleshooting Management Link Feature . . . . . . . . . . . . . . . . . . . .
5-5
„
LMI Packet Capture Utility Feature . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-5
Viewing Captured Packets from the Menu-Driven User Interface .
5-6
„
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-7
„
Viewing the Trap Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-15
„
Troubleshooting Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-15
Device Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-15
Frame Relay PVC Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-17
„
9000-A2-GB33-30
ISDN DBM Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-18
Tests Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-19
Test Timeout Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-20
DBM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-20
October 2003
iii
Contents
„
Starting and Stopping a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aborting All Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-22
„
PVC Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-23
PVC Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-24
Send Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-25
5-21
Monitor Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-25
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-26
Test Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-26
„
Network ATM Loopback (9783, 9788) . . . . . . . . . . . . . . . . . . . . . . . . .
5-27
„
Physical Tests (9123, 9126, 9128). . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-29
Line Loopback (9123, 9126, 9128) . . . . . . . . . . . . . . . . . . . . . . . .
5-30
Payload Loopback (9123, 9126, 9128) . . . . . . . . . . . . . . . . . . . . .
5-31
Repeater Loopback (9123, 9126, 9128) . . . . . . . . . . . . . . . . . . . .
5-32
DTE Loopback (9123, 9126, 9128) . . . . . . . . . . . . . . . . . . . . . . . .
5-33
Send Line Loopback (9123, 9126, 9128). . . . . . . . . . . . . . . . . . . .
5-34
Data Channel Loopbacks on a Frame Relay Link (9123, 9126, 9128)
35
Send Remote Line Loopback (9123, 9126, 9128) . . . . . . . . . . . . .
5-
5-36
Send and Monitor Pattern Tests (9123, 9126, 9128). . . . . . . . . . .
5-37
Physical Tests (9520, 9520-ILM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-38
Line Loopback (Network or 9520-ILM T3 User Port) . . . . . . . . . . .
5-40
DTE Loopback (9520 Data Port) . . . . . . . . . . . . . . . . . . . . . . . . . .
5-41
Physical Tests (9623, 9626). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-42
CSU (External) Network Loopback (9623, 9626) . . . . . . . . . . . . .
5-43
DSU (Internal) Network Loopback (9623, 9626) . . . . . . . . . . . . . .
5-43
Latching Loopback (9623, 9626) . . . . . . . . . . . . . . . . . . . . . . . . . .
5-44
Send 511 (9623, 9626) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-44
Monitor 511 (9623, 9626) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-45
DTE Loopback (9623, 9626) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-45
„
Physical Tests (9720, 9783, 9788 CSU/DSUs) . . . . . . . . . . . . . . . . . .
5-46
DTE Loopback (9720, 9783, 9788 CSU/DSUs). . . . . . . . . . . . . . .
5-46
„
Physical Tests (9820-2M, 9820-8M, 9820-45M) . . . . . . . . . . . . . . . . .
5-47
DTE Loopback (9820-2M, 9820-8M, 9820-45M) . . . . . . . . . . . . . .
5-47
IP Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-48
IP Ping Test – Procedure 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-53
IP Ping Test – Procedure 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-54
„
Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-54
„
Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-55
„
„
„
Index
iv
October 2003
9000-A2-GB33-30
About This Guide
Purpose and Intended Audience
This document describes the operation and maintenance of the following
iMarc SLV CSU/DSUs and routers: 9123, 9126, 9128 standalone,
9128 carrier-mount, 9520, 9520-ILM, 9623, 9626, 9720, 9783, 9788, 9820-2M,
9820-8M, and 9820-45M.
Features introduced in firmware release 2.2 are described in this manual but may
not be available in all models.
Document Organization
Section
Description
Chapter 1, User Interface and
Basic Operation
Shows how to navigate the menu-driven user
interface.
Chapter 2, Security and Logins
Provides procedures for controlling access to the
iMarc SLV and setting up logins.
Chapter 3, Status and Statistics
Describes the ways you can determine device and
network status and obtain statistics.
Chapter 4, Operation and
Maintenance
Describes model-specific operating and maintenance
procedures.
Chapter 5, Troubleshooting
Provides device problem resolution, alarm, and other
information, as well as troubleshooting and test
procedures.
Index
Lists key terms, acronyms, concepts, and sections.
A master glossary of terms and acronyms used in Paradyne documents is
available on the World Wide Web at www.paradyne.com. Select Support →
Technical Manuals → Technical Glossary.
9000-A2-GB33-30
October 2003
v
About This Guide
Product-Related Documents
Complete Paradyne documentation for this product is available at
www.paradyne.com. Select Support →Technical Manuals →iMarc IP/Frame
Relay Devices.
Document
Number
Document Title
The iMarc SLV reference library contains:
9000-A2-GB30
iMarc SLV Technical Description
Describes the features, interfaces, and cables for iMarc SLV
CSU/DSUs and routers.
9000-A2-GB31
iMarc SLV Configuration Reference
Lists and describes the configuration options available for
iMarc SLV CSU/DSUs and routers.
9000-A2-GB32
iMarc SLV SNMP Reference
Describes MIB details, SNMP traps, and RMON data collection
used for iMarc SLV CSU/DSUs and routers.
9000-A2-GB33
iMarc SLV Operations Guide
Explains how to operate and troubleshoot iMarc SLV CSU/DSUs
and routers.
9000-A2-GB34
iMarc SLV Router Command Line Interface
Describes special configuration procedures and the command line
interface for iMarc SLV routers.
Other iMarc model-specific documentation includes:
vi
9000-A2-GN19
iMarc SLV ISDN Installation Instructions
9000-A2-GN1D
9000 Series Access Carrier Installation Instructions
9123-A2-GN10
iMarc FLEX 9123 Installation Instructions
9123-A2-GN11
iMarc FLEX 9123 Router Installation Instructions
9126-A2-GN11
iMarc SLV 9126-II 1-Slot Unit Installation Instructions
9126-A2-GN12
iMarc SLV 9126-II Router Installation Instructions
9128-A2-GN10
iMarc SLV 9128 1-Slot Housing-to-9000 Series Access Carrier
Upgrade Instructions
9128-A2-GN11
iMarc SLV 9128/9128-II Network Access Module (NAM) Installation
Instructions
9128-A2-GN12
iMarc SLV 9128/9128-II 1-Slot Unit Installation Instruction
9520-A2-GN10
iMarc SLV 9520 Installation Instructions
9520-A2-GN11
iMarc SLV 9520-ILM Installation Instructions
9623-A2-GN10
iMarc FLEX 9623 Installation Instruction
9623-A2-GN11
iMarc FLEX 9623 Router Installation Instruction
October 2003
9000-A2-GB33-30
About This Guide
Document
Number
Document Title
9626-A2-GN10
iMarc SLV 9626 Installation Instructions
9720-A2-GN10
iMarc DSL 9720 CSU/DSU Installation Instructions
9720-A2-GN11
iMarc DSL 9720 Router Installation Instructions
9783-A2-GN10
iMarc DSL 9783 CSU/DSU Installation Instructions
9783-A2-GN11
iMarc DSL 9783 Router Installation Instructions
9788-A2-GN10
iMarc DSL 9788 CSU/DSU Installation Instructions
9788-A2-GN11
iMarc DSL 9788 Router Installation Instructions
9820-A2-GN10
iMarc SLV, Models 9820-2M and 9820-8M, Installation Instructions
9820-A2-GN11
iMarc SLV, Model 9820-45M, Installation Instructions
To order a paper copy of a Paradyne document, or to speak with a sales
representative, please call 1-727-530-2000.
9000-A2-GB33-30
October 2003
vii
About This Guide
Conventions Used
Convention Used
When Used
Italic
To indicate variable information (for example, DLCI nnnn,
where nnnn denotes a 4-digit number).
Menu sequence:
To provide an abbreviated method for indicating the
selections to be made from a menu or selections from within
a menu before performing a procedural step.
For example,
Main Menu →Status →System and Test Status indicates
that you should select Status from the Main Menu, then
select System and Test Status.
viii
(Path:)
To provide a check point that coincides with the menu path
shown at the top of the screen. Always shown within
parentheses so you can verify that you are referencing the
correct table (e.g., Path: main/config/alarm).
Brackets [ ]
To indicate multiple selection choices when more than one
selection is available (e.g., Performance
Statistics→Status→[Network/Port-1]).
Text highlighted in blue
To indicate a hyperlink to additional information when viewing
this manual online. Click on the highlighted text.
October 2003
9000-A2-GB33-30
User Interface and Basic Operation
1
This chapter contains information about how to access, use, and navigate the
menu-driven user interface and the Router’s Command Line Interface (CLI). It
includes the following:
„
Logging In on page 1-2
„
Main Menu on page 1-4
„
Screen Work Areas on page 1-5
„
Navigating the Screens on page 1-6
— Keyboard Keys
— Function Keys
— Selecting an Entry from a Menu
— Switching Between Screen Areas
— Selecting a Field
— Entering Information
— Screen Contents
„
Navigating the Router’s CLI on page 1-10
— CLI Keyboard Keys
9000-A2-GB33-30
October 2003
1-1
1. User Interface and Basic Operation
Logging In
Start a session using one of the following methods:
„
Telnet session via:
— An in-band management channel through the frame relay network.
— A local in-band management channel configured on the DTE port between
the iMarc unit and the router.
„
Dial-in connection using the internal modem.
„
Direct terminal connection over the COM port.
When logging in, the User Interface Idle screen appears.
„
If no security was set up or security was disabled, the Main Menu screen
appears (see Main Menu on page 1-4). You can begin your session.
„
If security was set up and is enabled, you are prompted for a login. Enter your
login ID and password.
When the user interface has been idle, a session is automatically ended and the
screen goes blank when the unit times out. Press Enter to reactivate the interface.
Procedure
To log in when security is being enforced:
1. Type your assigned Login ID and press Enter.
2. Type your Password and press Enter.
— Valid characters – All printable ASCII characters
— Number of characters – Up to 10 characters can be entered in the Login
ID and Password fields
— Case-sensitive – Yes
An asterisk (*) appears in the password field for each character entered.
1-2
October 2003
9000-A2-GB33-30
1. User Interface and Basic Operation
If your login was . . .
Then the . . .
Valid
Main Menu appears. Begin your session.
NOTE: If your login is valid, but access is denied, there are
two currently active sessions.
Invalid
Message, Invalid Password, appears on line 24, and
the Login screen is redisplayed.
After three unsuccessful attempts:
„
„
„
„
A Telnet session is closed.
The User Interface Idle screen appears for a directly
connected terminal.
The internal modem connection is disconnected.
An SNMP trap is generated.
Access is denied.
See your system administrator to verify your login (Login
ID/Password combination).
iMarc units support two sessions simultaneously. If two sessions are currently
active, wait and try again.
„
If two sessions are currently active and you are attempting to access the unit
through Telnet, the local Telnet client process returns a Connection
refused: message at the bottom of the screen.
„
If two sessions are currently active and you are attempting to access the unit
over the COM port or modem port, not via Telnet, the User Interface Already In
Use screen is redisplayed. In addition, the type of connection (Telnet
Connection, Direct COM Port Connection, or Direct Modem Port Connection)
for each current user is identified, along with the user’s login ID.
Procedure
To end the session:
1. Press Ctrl-a to switch to the function keys area of the screen.
2. Type e (Exit) and press Enter.
— For a terminal-connected to the COM port, the session is ended.
— For a terminal-connected to the modem port, the session is ended and the
modem is disconnected.
— For a Telnet connection, the session is closed and, if no other Telnet or
FTP session is occurring over the connection, the modem is
disconnected.
If ending a session from the Configuration branch, see the iMarc SLV
Configuration Reference.
9000-A2-GB33-30
October 2003
1-3
1. User Interface and Basic Operation
Main Menu
Entry to all of the iMarc unit’s tasks begins at the Main Menu, which has six menus
or branches. The Access Level at the top of the screen only appears when security
has been set up.
main
Device Name: Node A
Slot: 1 Type: T1 FR NAM
Access Level: 1
9128-II
05/26/2000 23:32
MAIN MENU
Status
Test
Configuration
Auto-Configuration
Control
Easy Install
------------------------------------------------------------------------------Ctrl-a to access these functions
Exit
Select . . .
To . . .
Status
View diagnostic tests, interfaces, PVC connections, and
statistics. You can also display LEDs and iMarc unit identity
information.
Test
Select and cancel test for the iMarc unit’s interfaces.
Configuration
Display and edit the configuration options.
Auto-Configuration
Configure basic access unit setup automatically based upon a
selected application. You can also automatically populate
network and (for CSU/DSUs) data port DLCI configuration
options with numeric settings.
Control
Control the asynchronous user interface for call directories,
device naming, login administration, and selecting software
releases. You can also initiate a power-on reset of the iMarc unit.
Easy Install
Configure minimal options for a quick installation.
See the unit’s installation instructions for a pictorial view of the menu hierarchy,
which represents the organization of the iMarc unit’s menus and screens.
1-4
October 2003
9000-A2-GB33-30
1. User Interface and Basic Operation
Screen Work Areas
There are two user work areas:
„
Screen area – Where you input information into fields.
„
Function keys area – Where you perform specific screen functions.
Below is a sample configuration screen.
Model Number
Date and Time
Menu Path
main
/config/system/slv
Device Name: Node A
9xxx-SLV
08/23/2002 10:59
SERVICE LEVEL VERIFICATION SYSTEM OPTIONS
Device Name
SLV Sample Interval (secs):
SLV Synchronization Role:
60
Tributary
SLV Type: Standard
SLV Delivery Ratio:
Disable
DLCI Down on SLV Timeout:
Enable
SLV Timeout Error Event Threshold:
3
SLV Timeout Clearing Event Threshold:
1
SLV Round Trip Latency Error Threshold (ms): 10000
SLV Latency Clearing Event Threshold:
2
SLV Packet Size (bytes):
64
Screen Area
Function Keys Area
------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
Save
Message Area
Screen Format
Description
Menu Path
Menu selections made to reach the current screen.
Device Name
Customer-assigned identification of the iMarc unit.
9xxx-SLV
iMarc unit’s model number (for example, 9126-IIRSLV).
Screen Area
Selection, display, and input fields for monitoring and
maintaining the iMarc unit.
Function Keys Area
Specific functions that can be performed by pressing a
specified key, then pressing Enter.
Message Area
System-related information and valid settings for input
fields are in the lower left corner.
System and Test Status messages are in the lower right
corner.
9000-A2-GB33-30
October 2003
1-5
1. User Interface and Basic Operation
Navigating the Screens
You can navigate the screens by:
„
Using keyboard keys.
„
Switching between the two screen work areas using function keys.
Keyboard Keys
Use the following keyboard keys to navigate within the screen area:
1-6
Press . . .
To . . .
Ctrl-a
Move cursor between the screen area and the
screen function keys area.
Esc
Return to the previous screen.
Right Arrow (on same screen row), or
Tab (on any screen row)
Move cursor to the next field.
Left Arrow (on same screen row), or
Ctrl-k
Move cursor to the previous field.
Backspace
Move cursor one position to the left or to the last
character of the previous field.
Spacebar
Select the next valid value for the field.
Delete (Del)
Delete character that the cursor is on.
Up Arrow or Ctrl-u
Move cursor up one field within a column on the
same screen.
Down Arrow or Ctrl-d
Move cursor down one field within a column on
the same screen.
Right Arrow or Ctrl-f
Move cursor one character to the right if in edit
mode.
Left Arrow or Ctrl-b
Move cursor one character to the left if in edit
mode.
Ctrl-l
Redraw the screen display, clearing information
typed in but not yet entered.
Enter (Return)
Accept entry or, when pressed before entering
data or after entering invalid data, display valid
options on the last row of the screen.
October 2003
9000-A2-GB33-30
1. User Interface and Basic Operation
Function Keys
All function keys (located in the lower part of the screen; see the example in
Screen Work Areas on page 1-5) operate the same way throughout the screens.
They are not case-sensitive, so upper- or lowercase letters can be used
interchangeably.
These keys use the following conventions:
Select . . .
For the screen
function . . .
And press Enter to . . .
M or m
MainMenu
Return to the Main Menu screen.
E or e
Exit
Terminate the asynchronous terminal session.
N or n
New
Enter new data.
O or o
Modify
Modify existing data.
L or l
Delete
Delete data.
S or s
Save
Save information.
R or r
Refresh
Update screen with current information.
C or c
ClrStats
Clear network performance statistics and refresh the
screen.
Variations include:
„
„
„
9000-A2-GB33-30
ClrSLV&DLCIStats for clearing SLV and DLCI
statistics.
ClrLinkStats for clearing frame relay link statistics.
ClrDBMStats for clearing DBM call statistics.
U or u
PgUp
Display the previous page.
D or d
PgDn
Display the next page.
October 2003
1-7
1. User Interface and Basic Operation
Selecting an Entry from a Menu
Procedure
To select an entry from a menu:
1. Tab or press the down arrow key to position the cursor on a menu selection, or
press the up arrow key to move the cursor to the bottom of the menu list.
Each menu selection is highlighted as you press the key to move the cursor
from position to position.
2. Press Enter. The selected menu or screen appears.
Procedure
To return to a previous screen, press the Escape (Esc) key until you reach the
desired screen.
Switching Between Screen Areas
Use Ctrl-a to switch between screen areas (see the example in Main Menu on
page 1-4).
Procedure
To switch to the function keys area:
1. Press Ctrl-a to switch from the screen area to the function keys area.
2. Select either the function’s designated (underlined) character or Tab to the
desired function key.
3. Press Enter. The function is performed.
To return to the screen area, press Ctrl-a again.
1-8
October 2003
9000-A2-GB33-30
1. User Interface and Basic Operation
Selecting a Field
Once you reach the desired menu or screen, select a field to view or change, or
issue a command.
Press the Tab or right arrow key to move the cursor from one field to another. The
current setting or value appears to the right of the field.
Entering Information
You can enter information in one of three ways. Select the field, then:
„
Manually type in (enter) the field value or command.
Example:
Entering bjk as a user’s Login ID on the Administer Logins screen (from the
Control menu/branch).
„
Type in (enter) the first letter(s) of a field value or command, using the unit’s
character-matching feature.
Example:
When configuring a port’s physical characteristics with the Port (DTE) Initiated
Loopbacks configuration option/field selected (possible settings include
Disable, Local, DTPLB, DCLB, and Both), entering d or D displays the first
value starting with d – Disable. In this example, entering dt or DT would
display DTPLB as the selection.
„
Switch to the function keys area and select or enter a designated function key.
Example:
To save a configuration option change, select Save. S or s is the designated
function key.
If a field is blank and the Message area displays valid selections, press the
spacebar; the first valid setting for the field appears. Continue pressing the
spacebar to scroll through other possible settings.
Screen Contents
What appears on the screens depends on:
9000-A2-GB33-30
„
Current configuration – How your network is currently configured.
„
Security access level – The security level set by the system administrator for
each user.
„
Data selection criteria – What you entered in previous screens.
October 2003
1-9
1. User Interface and Basic Operation
Navigating the Router’s CLI
Access the iMarc DSL Router’s Command Line Interface by pressing the Shift-r
function key from the Main Menu. There is no need to press Ctrl-a first to access
the function keys area of the screen.
Once the CLI is accessed, you can use keyboard keys to navigate within the
interface. Using the router’s CLI, you can display and edit router configuration
settings, view router status, and access router tests.
For details of all CLI commands and the conventions used when entering
commands, see the iMarc SLV Router Command Line Interface. That document
also contains a summary of abbreviated (minimal) command entries and their
default settings.
CLI Keyboard Keys
Use the following keyboard keys to navigate within the router’s CLI. Most terminal
emulation programs use these same keys.
Press . . .
To . . .
Enter (Return)
Accept the current command line input.
Ctrl-c
1-10
„
„
„
Clear the current command line entry.
Abort a command line prompt without answering.
Exit a command in progress.
Ctrl-z
Exit Configuration mode and returns to Standard mode. A prompt
appears to save any unsaved changes.
Backspace
Erase the character to the left of the cursor.
Delete
Erase the character the cursor is on.
Down Arrow
Recall command line history buffer with the most recent
command displaying first. Buffer contains ten lines of history.
Up Arrow
Scroll to the last valid command for editing.
Right Arrow
Move the cursor one position to the right.
Left Arrow
Move the cursor one position to the left.
q
(or any key but
Spacebar or
Enter/Return)
Abort a Move display and return to the command line prompt.
October 2003
9000-A2-GB33-30
Security and Logins
2
This chapter includes the following:
„
Limiting Access on page 2-2
„
Controlling Asynchronous Terminal Access on page 2-2
„
Limiting Dial-In Access via the Modem Port on page 2-4
„
Controlling ISDN Access on page 2-5
— ISDN Call Security
— Disabling ISDN Access
„
Controlling Telnet or FTP Access on page 2-6
— Limiting Telnet Access
— Limiting FTP Access
— Limiting Telnet or FTP Access Over the TS Access Management Link
„
Controlling SNMP Access on page 2-9
— Disabling SNMP Access
— Assigning SNMP Community Names and Access Levels
— Limiting SNMP Access Through IP Addresses
9000-A2-GB33-30
„
Creating a Login on page 2-12
„
Modifying a Login on page 2-13
„
Deleting a Login on page 2-13
„
Controlling Router CLI Access on page 2-14
October 2003
2-1
2. Security and Logins
Limiting Access
The iMarc unit provides access security on the following interfaces:
„
Asynchronous terminal
„
Telnet
„
FTP
„
SNMP
Up to two direct or Telnet sessions can be active at any given time; that is, you can
have two simultaneous Telnet sessions, or one Telnet session and one active
asynchronous terminal session, or two simultaneous asynchronous terminal
sessions.
Controlling Asynchronous Terminal Access
Direct asynchronous terminal access to the menu-driven user interface can be
limited by:
„
Requiring a login.
„
Assigning an access level to the port or interface.
An asynchronous terminal can be connected to the unit’s COM (communications)
port or its modem port.
2-2
October 2003
9000-A2-GB33-30
2. Security and Logins
Procedure
To limit asynchronous terminal access to the menu-driven user interface:
1. Select the appropriate port options.
Main Menu→Configuration→Management and Communication→
Communication Port
Main Menu→Configuration→Management and Communication→
Modem Port
2. Set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Require a login
Login Required to Enable.
NOTE: User ID and password combinations must
be defined. See Creating a Login on page 2-12.
Limit the effective access level
to Level-3 or Level-2
Port Access Level to Level-2 or Level-3.
NOTE: Regardless of a user’s login access level, a
user cannot operate at a level higher than the
access level specified for the port (e.g., if a user has
a Level-1 login and Level-2 port access has been
set, the Level-1 user can only operate as a Level-2
user).
If you are going to allow Level-1 users to configure
the unit, keep the access at Level-1.
NOTE:
See Resetting the Unit and Restoring Communication in Chapter 5,
Troubleshooting, should you be locked out inadvertently.
3. Save your changes.
If connecting an asynchronous terminal to the unit’s:
9000-A2-GB33-30
„
COM port – See the iMarc SLV Configuration Reference for more information
about the communication (COM) port.
„
Modem port – See Setting Up Call Directories for Trap Dial-Out and
Configuring the Modem Port in iMarc SLV Configuration Reference for
additional information.
October 2003
2-3
2. Security and Logins
Limiting Dial-In Access via the Modem Port
The modem port is already configured for dial-in and asynchronous terminal
access; these are the default settings.
To limit dial-in access via the modem port, disable the Dial-In Access configuration
option.
Main Menu→Configuration→Management and Communication→
Modem Port
See Configuring the Modem Port in the iMarc SLV Configuration Reference for
more information about modem port options.
2-4
October 2003
9000-A2-GB33-30
2. Security and Logins
Controlling ISDN Access
iMarc units with a DBM can limit access through the following methods:
„
ISDN Call Security
„
Disabling ISDN Access
ISDN Call Security
The iMarc unit uses the Caller Identification Method to screen calls and avoid
accidental or intentional disruption of network traffic. The answering DBM only
accepts calls with valid calling number identifiers or phone numbers.
When the ISDN DBM interface is enabled and Caller Identification Method is set to
Caller ID, the DBM takes advantage of ISDN services for network backup and
Calling Number Identification Service (CNIS) to provide backup security. ISDN
assures the integrity of calling party identifiers. The DBM uses the calling party
identifier to identify the calling unit and switches PVC connections as specified by
the user. No additional security is required.
When the ISDN DBM interface is enabled and Caller Identification Method is set to
Proprietary, the DBM queries the originating unit for its Local Phone Number to
identify the calling unit. If the returned number is in one of the unit’s Inbound
Calling IDs, the call is accepted. If not, or if the queried unit does not respond
within five seconds, the unit drops the call.
See Caller Identification Method in the iMarc SLV Configuration Reference for
additional information.
Disabling ISDN Access
Procedure
To disable ISDN access:
1. Select the ISDN Physical options.
Main Menu→Configuration→ISDN→Physical
2. Set Interface Status to Disable.
3. Save your change.
See Configuring the ISDN DBM Interface in the iMarc SLV Configuration
Reference for more information about ISDN BRI or PRI DBM configuration
options.
9000-A2-GB33-30
October 2003
2-5
2. Security and Logins
Controlling Telnet or FTP Access
The iMarc unit provides several methods for limiting access via a Telnet or FTP
session. Telnet or FTP access can be on a standard management link or on a
service provider’s troubleshooting (TS) management link.
Limiting Telnet Access
Telnet access can be limited by:
„
Disabling Telnet access completely.
„
Requiring a login for Telnet sessions that are not on the TS Access
Management Link.
„
Assigning an access level for Telnet sessions.
„
Disabling TS Access Management Link access.
To limit Telnet access via a service provider’s troubleshooting management link,
see Limiting Telnet or FTP Access Over the TS Access Management Link on
page 2-8.
Procedure
To limit Telnet access when the session is not on the TS Access Management
Link:
1. Select the Telnet and FTP Session options.
Main Menu→Configuration→Management and Communication→
Telnet and FTP Sessions
2. Set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Disable Telnet access
Telnet Session to Disable.
Require a login
Login Required to Enable.
NOTE: User ID and password combinations must
be defined. See Creating a Login on page 2-12.
Assign an access level
Session Access Level to Level-2 or Level-3.
NOTE: Regardless of a user’s login access level, a
user cannot operate at a level higher than the
access level specified for the Telnet session (e.g., if
a user has a Level-1 login and Level-2 telnet access
has been set, the Level-1 user can only operate as
a Level-2 user).
If you are going to allow users to configure the unit,
keep the access at Level-1.
3. Save your changes.
2-6
October 2003
9000-A2-GB33-30
2. Security and Logins
See Configuring Telnet and/or FTP Session Support in the iMarc SLV
Configuration Reference for more information about setting Telnet configuration
options.
Limiting FTP Access
FTP access can be limited by:
„
Disabling FTP access completely.
„
Requiring a user ID and password to login.
„
Limiting FTP bandwidth.
Procedure
To limit FTP access when the session is not on the TS Access Management Link:
1. Select the Telnet and FTP Session options.
Main Menu→Configuration→Management and Communication→
Telnet and FTP Sessions
2. Set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Disable FTP
FTP Session to Disable.
Require a login
Login Required to Enable.
NOTE: User ID and password combinations must
be defined. See Creating a Login on page 2-12.
If you want to allow users to configure the unit or
perform file transfers, including downloads, keep
the access at Level-1.
Level-1 access is required to download software to
the unit, or to upload or download configuration
files. Level-3 is sufficient for NMS access for SLV
historical information.
Limit bandwidth for FTP
FTP Max Transfer Rate to a rate less than the
network line speed, typically less than or equal to
the CIR.
This method is not recommended if SLV reports are
desired since FTP is required to generate the
reports.
3. Save your changes.
See Configuring Telnet and/or FTP Session Support in the iMarc SLV
Configuration Reference for more information about setting FTP configuration
options.
9000-A2-GB33-30
October 2003
2-7
2. Security and Logins
Limiting Telnet or FTP Access Over the TS Access Management Link
Procedure
To limit Telnet or FTP access when the session is on the TS Access Management
Link:
1. Select the Telnet and FTP Session options.
Main Menu→Configuration→Management and Communication→
Telnet and FTP Sessions
2. Disable Telnet Session and/or FTP Session, as appropriate.
3. Return to the Management and Communication menu, and select Node IP.
4. Set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Disable access via the TS
Access Management Link
TS Access Management Link to None.
Assign an access level to the
TS Access Management Link
TS Access Management Link’s Access Level to
Level-2 or Level-3.
NOTE: Regardless of a user’s login access level, a
user cannot operate at a level higher than the
access level specified for the session (e.g., if a user
has a Level-1 login and Level-2 telnet access has
been set, the Level-1 user can only operate as a
Level-2 user).
If you are going to allow users to configure the unit,
keep the access at Level-1.
5. Save your changes.
See Configuring Telnet and/or FTP Session Support or Configuring Node IP
Information in the iMarc SLV Configuration Reference for more information about
these configuration options.
2-8
October 2003
9000-A2-GB33-30
2. Security and Logins
Controlling SNMP Access
The iMarc unit supports SNMP Version 1, which provides limited security through
the use of community names. There are three methods for limiting SNMP access:
„
Disabling SNMP access.
„
Assigning SNMP community names and the access type.
„
Assigning IP addresses of those NMSs that can access the unit.
Disabling SNMP Access
When the SNMP access is disabled, the iMarc unit will not respond to SNMP
messages.
Procedure
To disable SNMP access:
1. Select the General SNMP Management options.
Main Menu→Configuration→Management and Communication→
General SNMP Management
2. Disable the SNMP Management option.
3. Save your change.
See Configuring General SNMP Management in the iMarc SLV Configuration
Reference for more information about General SNMP Management configuration
options.
9000-A2-GB33-30
October 2003
2-9
2. Security and Logins
Assigning SNMP Community Names and Access Levels
The iMarc unit supports the SNMP protocol and can be managed by an SNMP
manager. SNMP manager access can be limited by:
„
Assigning the SNMP community names that are allowed to access the iMarc
unit’s Management Information Base (MIB).
„
Specifying the type of access allowed for each SNMP community name.
Whenever an SNMP manager attempts to access an object in the MIB, the
community name must be supplied.
Procedure
To assign SNMP community names and access types:
1. Select the General SNMP Management options.
Main Menu→Configuration→Management and Communication→
General SNMP Management
2. Set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Assign SNMP community
names
Community Name 1 and Community Name 2 to a
community name text, up to 255 characters in length.
Assign the type of access
allowed for the SNMP
community names
Name 1 Access and Name 2 Access to Read or
Read/Write.
3. Save your changes.
See Configuring General SNMP Management in the iMarc SLV Configuration
Reference for more information about General SNMP Management configuration
options.
2-10
October 2003
9000-A2-GB33-30
2. Security and Logins
Limiting SNMP Access Through IP Addresses
An additional level of security is provided by:
„
Limiting the IP addresses of NMSs that can access the iMarc unit.
„
Performing validation checks on the IP address of SNMP management
systems attempting to access the iMarc unit.
„
Specifying the access allowed for the authorized NMS when IP address
validation is performed.
The SNMP NMS Security Options screen provides the configuration options that
determine whether security checking is performed on the IP address of SNMP
management systems attempting to communicate with the unit.
Make sure that SNMP Management is set to Enable.
Menu selection sequence:
Main Menu →Configuration →Management and Communication →
General SNMP Management → SNMP Management: Enable
See Configuring General SNMP Management in the iMarc SLV Configuration
Reference for more information about SNMP management configuration options.
Procedure
To limit SNMP access through IP addresses:
1. Select the SNMP NMS Security options:
Main Menu→Configuration→Management and Communication→ SNMP
NMS Security
2. Select and set the following configuration options, as appropriate.
To . . .
Set the configuration option . . .
Enable IP address checking
NMS IP Validation to Enable.
Specify the number (between 1 and 10) of
SNMP management systems that are
authorized to send SNMP messages to the
iMarc unit
Number of Managers to the desired
number.
Specify the IP address(es) that identifies the
SNMP manager(s) authorized to send
SNMP messages to the unit
NMS n IP Address to the appropriate
IP address.
Specify the access allowed for an authorized
NMS when IP address validates is
performed
Access Level to Read or Read/Write.
3. Save your changes.
See Configuring SNMP NMS Security in the iMarc SLV Configuration Reference
for more information about SNMP NMS Security configuration options.
9000-A2-GB33-30
October 2003
2-11
2. Security and Logins
Creating a Login
A login is required if security is enabled. Security is enabled by the configuration
options Login Required for the communication port, modem port, and Telnet Login
Required or FTP Login Required for a Telnet or FTP Session.
Up to six login ID/password combinations can be created using ASCII text, and
each login must have a specified access level. Logins must be unique and they are
case-sensitive.
Procedure
To create a login record:
1. Select Administer Logins.
Main Menu→Control→Administer Logins
2. Select New, and set the following configuration options, as appropriate.
In the field . . .
Enter the . . .
Login ID
ID of 1 to 10 characters.
Password
Password from 1 to 10 characters.
Re-enter password
Password again to verify that you entered the correct
password into the device.
Access Level
Access level: 1, 2, or 3.
„
„
„
Level-1 – User can add, change, and display
configuration options, save, and perform device
testing.
Level-2 – User can monitor and perform
diagnostics, display status and configuration option
information.
Level-3 – User can only monitor and display status
and configuration screens.
CAUTION: Make sure at least one login is set up for
Level-1 access or you may be inadvertently locked out.
NOTE:
See Resetting the Unit and Restoring Communication in Chapter 5,
Troubleshooting, should you be locked out inadvertently.
3. Save your changes.
When Save is complete, the cursor is repositioned at the Login ID field, ready
for another entry.
See Configuring SNMP NMS Security in the iMarc SLV Configuration Reference
for more information about security configuration options.
2-12
October 2003
9000-A2-GB33-30
2. Security and Logins
Modifying a Login
Logins are modified by deleting the incorrect login and creating a new one.
Deleting a Login
Procedure
To delete a login record:
1. Select Administer Logins.
Main Menu→Control→Administer Logins
2. Page through login pages/records using the PgUp or PgDn function keys until
the login to be deleted is displayed.
3. Select Delete.
4. Save your deletion.
When the deletion is complete, the number of login pages/records reflects
one less record, and the record before the deleted record reappears.
Example:
Page 2 of 4 is changed to Page 2 of 3.
9000-A2-GB33-30
October 2003
2-13
2. Security and Logins
Controlling Router CLI Access
iMarc SLV Routers can be managed from an NMS using SNMP, or from the
router’s command line interface (CLI). There are two methods to access the
command line interface:
„
Local access at the router through the COM port, or
„
Access via a Telnet session.
Telnet access defaults to Administrator level. If the current login is at the
Operator level, only Operator level access is available for the session. Telnet
access is always enabled.
The router accepts one CLI login session at a time and is configured at the factory
without a default login ID and password. To provide login security to the system,
configure a login ID and password.
When a local console connection is first established, a login prompt appears. If the
Device Name field has been configured via the Control menu
(Control Menu→System Information), the login prompt displays the device name.
For example, a device name of Largo is shown as:
Largo>
See Creating a Login on page 2-12 for security information for each Login ID.
Access Levels (Command Modes)
There is one login ID and several levels of privileges for the router’s CLI. Your user
account can be configured with one user name and different passwords for:
„
Operator. The Operator has read-only access to display device information
with no modification permission and limited access to diagnostic functions.
With a device name of Largo, the prompt appears as Largo>.
„
Administrator. The Administrator has several levels of access to the router’s
CLI. The # sign in the following prompts indicates Administrator access level.
Display Prompt with Device Name of Largo Administrator Access Levels
Largo #>
Standard (same as Operator)
Largo(config) #
Configuration
Largo(config-if) #
Configuration Interface
Largo(config-subif) #
Configuration Sub-Interface
Largo(config-dhcp) #
Configuration DHCP Pool
Refer to the iMarc SLV Router Command Line Interface for access level details for
each command line entry.
2-14
October 2003
9000-A2-GB33-30
2. Security and Logins
Changing Access Levels
The Operator and Administrator have the same Login ID with different passwords
for their access level. To determine the level of access for a session, refer to
Access Levels (Command Modes) on page 2-14.
After accessing the router’s CLI:
„
You can access the Administrator access level by entering:
enable
„
The router’s defaults to no password required. To require a password to
access the Administrator access level, enter:
enable password password
Once saved, the router responds with a prompt to enter a password for
Administrator access. This command is in effect until no enable password
[ password ] is entered and saved.
„
You can end the current Administrator access level by entering:
exit
This command results in ending the current Administrator access level
session. Exit may need to be entered several times to reach Operator level
and/or end the session.
„
You can end the Administrator access level by entering:
end
This command results in ending the Administrator access level session and
returning immediately to Operator level.
For further details, refer to the iMarc SLV Configuration Reference and iMarc SLV
Router Command Line Interface.
9000-A2-GB33-30
October 2003
2-15
2. Security and Logins
2-16
October 2003
9000-A2-GB33-30
Status and Statistics
3
This chapter describes the ways you can determine device and network status and
obtain statistics.
„
Displaying System Information on page 3-2
„
Viewing LEDs and Control Leads on page 3-4
— LED Descriptions
— Power Module LEDs (Models 9520, 9520-ILM, 9820-45M)
— Display LEDs and Control Leads Screen Descriptions
„
Device Messages on page 3-24
„
Status Information on page 3-30
— System and Test Status Messages
— Network LMI-Reported DLCIs Status
— IP Path Connection Status
— PVC Connection Status
— Time Slot Assignment Status
— DBM Interface Status
„
IP Routing Table on page 3-60
„
Performance Statistics on page 3-62
— Clearing Performance Statistics
— Service Level Verification Performance Statistics
— DLCI Performance Statistics
— Frame Relay Performance Statistics
— ATM Performance Statistics (9783, 9788)
— VCC Performance Statistics (9783, 9788)
— ESF Line Performance Statistics (9123, 9126, 9128)
— DDS Line Performance Statistics (9623, 9626)
9000-A2-GB33-30
October 2003
3-1
3. Status and Statistics
— T3 Network Line Performance Statistics (9520, 9520-ILM)
— SHDSL Line Performance Statistics (9788)
— DBM Call Performance Statistics
— Ethernet Performance Statistics
„
Trap Event Log on page 3-89
Displaying System Information
Use the Identity screen to view identification information about the iMarc unit. This
information is useful if you are purchasing additional or replacement units and/or
making firmware upgrades.
Main Menu→Status→Identity
View this field . . .
To find the . . .
System Name
Domain name for this SNMP-managed node (up to 255
ASCII characters).
System Contact
Contact person for this SNMP-managed node.
System Location
Physical location for this SNMP-managed node.
NAM
NAM Type
Type of unit installed, referred to as a network access
module, or NAM (i.e., T1 FR NAM). This card type is
supported by the SNMP SysDescr Object.
Hardware Revision
Unit’s hardware version. Format nnnn-nnx consists of a
4-digit number, followed by two digits and one alphabetic
character.
Current Software Revision
Software version currently being used by the unit. Format
nn.nn.nn consists of a 6-digit number that represents the
major and minor revision levels.
Alternate Software Revision Software version that has been downloaded into the unit,
but has not yet been implemented. Format is the same as
for the Current Software Revision.
„
„
3-2
In Progress indicates that the flash memory is
currently being downloaded.
Invalid indicates that no download has occurred or
the download was not successful
Serial Number
Unit’s 7-character serial number.
Ethernet MAC Address
Media Access Control (MAC) address assigned to the
Ethernet port during manufacturing.
October 2003
9000-A2-GB33-30
3. Status and Statistics
View this field . . .
To find the . . .
ISDN DBM
Card Type
The type of dial backup module installed, ISDN-BRI or
ISDN-PRI, if applicable.
„
„
Software Revision
If an unsupported DBM is installed, Unsupport
displays.
If the DBM has failed, Failed displays.
Software version currently being used by the iMarc unit’s
DBM. Format nn.nn.nn consists of a 6-digit number that
represents the major and minor revision levels.
For an ISDN-PRI DBM, None displays because the DBM
does not have loaded software; it runs from the NAM’s
software.
Hardware Revision
9000-A2-GB33-30
iMarc DBM’s hardware version. Format nnnn-nnx consists
of a 4-digit number, followed by 2 digits and 1 alphabetic
character.
October 2003
3-3
3. Status and Statistics
Viewing LEDs and Control Leads
iMarc SLV faceplates include LEDs (light-emitting diodes) that provide status on
the unit and its interfaces.
The Display LEDs and Control Leads feature allows you to monitor a remote unit;
it is useful when troubleshooting control lead problems. The Display LEDs and
Control Leads screen shows the status of the unit and its interfaces.
To access the Display LEDs and Control Leads screen:
Main Menu →Status →Display LEDs and Control Leads
The following illustrations compare front panel LEDs and the Display LEDs and
Control Leads screens for each model type.
Model 9123
K
O
M
F
O
G
AL
O
SI
ST
FR
M
AL
TE
O
K
9123-C
FLEX SLV
System
Network
Port
03-17386
Model 9123 Display LEDs and Control Leads Screen
3-4
October 2003
9000-A2-GB33-30
3. Status and Statistics
Model 9126-A2-201
NETWORK
DSX
K
O
O
F
AL
M
O
SI
G
O
F
AL
M
O
SI
G
T
TS
K
O
SLV
AL
M
9126
PORT
03-17409
Model 9126-A2-202
NETWORK
DSX
K
O
O
F
AL
M
O
SI
G
AL
M
F
O
O
P
SI
G
T
BK
TS
SLV
AL
M
O
K
9126
PORT
03-17410
Model 9126 Display LEDs and Control Leads Screen
9000-A2-GB33-30
October 2003
3-5
3. Status and Statistics
Model 9128
NETWORK
DSX/PRI
K
O
F
AL
M
G
O
O
SI
O
F
AL
M
SI
G
O
P
FR
T
BK
TS
K
SLV
O
SLV
AL
M
9128
PORT
03-17399
Model 9128 Display LEDs and Control Leads Screen
3-6
October 2003
9000-A2-GB33-30
3. Status and Statistics
Model 9520
9520
SYSTEM
NETWORK
PORT 1
PORT 2
OK
TD
TD
TD
ALM
RD
RD
RD
TST
LMI
DSR
DSR
FAN
OOF
DTR
DTR
PWR
LOS
AIS
YEL
iM
arc
SYS
TEM
OK
ALM
TST
TM
SLV
952
NE
TW
0
OR
K
TD
FAN
RD
PO
RT
PW
R
LM
I
OO
F
LO
S
AIS
TD
YEL
1
RD
OO
F
LO
S
AIS
YEL
03-17387
Model 9520 Display LEDs and Control Leads Screen
9000-A2-GB33-30
October 2003
3-7
3. Status and Statistics
Model 9520-ILM
9520-ILM
SYSTEM
NETWORK
PORT 1
OK
TD
TD
ALM
RD
RD
TST
LMI
FAN
OOF
OOF
PWR
LOS
LOS
AIS
AIS
YEL
YEL
iM
arc
SYS
TEM
OK
ALM
TST
®
SLV
952
NE
0-I
TW
LM
OR
K
TD
FAN
RD
PW
R
LM
I
OO
F
LO
S
AIS
YEL
PO
RT
TD
1
RD
OO
F
LO
S
AIS
YEL
03-17391
Model 9520-ILM Display LEDs and Control Leads Screen
3-8
October 2003
9000-A2-GB33-30
3. Status and Statistics
Model 9623
O
K
O
O
F/
N
S
D
M
O
O
S
T
FR
TE
S
AL
O
K
M
9623
FLEX SLV
FrameSaver
TM
System
Port
Network
03-17384
Model 9626
NETWORK
K
K
O
2-
1O
S
F/
O
O
O
O
P
M
D
T
BK
M
TS
SLV
AL
SLV
O
K
N
S
9626
PORT
03-17385
Model 9626 Display LEDs and Control Leads Screen
9000-A2-GB33-30
October 2003
3-9
3. Status and Statistics
Model 9720 CSU/DSU and Router
K
O
FR
D
SL
K
AL
M
O
TE
ST
9720
R
DSL
IDSL
System
Network
Port
03-17411
Model 9720 Display LEDs and Control Leads Screen
3-10
October 2003
9000-A2-GB33-30
3. Status and Statistics
Model 9783
O
K
SL
D
T
M
AL
TE
S
O
K
AT
M
9783-C
R
DSL SLV
FrameSaver
TM
SDSL
System
Network
Port
03-17407
Model 9788
O
K
SL
D
T
M
AL
TE
S
O
K
AT
M
9788 CSU/DSU
R
DSL SLV
FrameSaver
TM
SHDSL
System
Network
Port
03-17408
Model 9783 Display LEDs and Control Leads Screen
9000-A2-GB33-30
October 2003
3-11
3. Status and Statistics
Model 9783 Router
K
O
AT
M
D
SL
K
AL
M
O
TE
ST
9783 ROUTER
R
DSL SLV
SDSL
System
Network
Port
03-17405
Model 9788 Router
K
O
D
SL
AT
M
AL
M
K
O
TE
ST
9788 ROUTER
R
DSL
SHDSL
System
Network
Port
03-17406
Model 9783 Router Display LEDs and Control Leads Screen
3-12
October 2003
9000-A2-GB33-30
3. Status and Statistics
Model 9820-2M and 9820-8M
NETWORK
K
O
O
K
T
TS
K
SLV
O
SLV
AL
M
9820-2M
PORT
03-17383
Model 9820-2M Display LEDs and Control Leads Screen
9000-A2-GB33-30
October 2003
3-13
3. Status and Statistics
Model 9820-45M
9820-45M
SYSTEM
NETWORK
PORT 1
TD
TD
ALM
RD
RD
TST
DTR
DSR
FAN
DSR
DTR
OK
LMI
PWR
iM
arc
TM
SLV
SYS
TEM
OK
982
0-4
ALM
TST
FAN
PW
R
LM
I
5M
NE
TW
OR
K
TD
RD
DTR
DS
R
PO
RT
TD
1
RD
DTR
DS
R
03-17388
Model 9820-45M Display LEDs and Control Leads Screen
Refresh the screen to view control lead transitions. LED and control lead
descriptions are in the sections that follow.
3-14
October 2003
9000-A2-GB33-30
3. Status and Statistics
LED Descriptions
Table 3-1, Front Panel LEDs, decribes the LEDs found on the faceplates of iMarc
devices.
Table 3-1.
Label
Front Panel LEDs (1 of 4)
Indication
Color
What It Means
Power and
Operational
Status
Green
ON – iMarc unit has power and it is
operational.
Operational
Alarm (Fail)
Red
General and System
OK
ALM
OFF – iMarc unit is in a power-on self-test, or
there is a failure.
ON – iMarc unit has just been reset, or an error
or fault has been detected.
Alarms appear on the System and Test Status
screen. See Table 3-6, Health and Status
Messages, for additional information.
TST
Test Mode
Yellow
ON – Loopback or test pattern is in progress,
initiated locally, remotely, or from the network.
OFF – No tests are active.
Models 9126, 9128, 9626 with ISDN Backup:
BKP
Backup
Yellow
ON – iMarc unit is in Backup mode; that is, the
backup link has been established, and backup
is in progress through the specified Alternate
Destination Link.
OFF – iMarc unit is not in Backup mode.
Blinking ON and OFF – Alternate Destination
Link is being established, but no data has been
passed.
Models 9520, 9520-ILM, 9820-45M:
FAN
Fan Status
Yellow
ON – One or more of the four system fans has
failed.
OFF – All fans are operational.
PWR
Power Supply
Status
Yellow
ON – One of the two installed power modules
has failed. See Power Module LEDs (Models
9520, 9520-ILM, 9820-45M) on page 3-19.
OFF – Both power modules are operational or
a redundant power supply is not installed.
Network
Models 9123, 9128, 9623, 9720:
Link
or
FR
Mode and Link
Status
Multicolored
Yellow – LMI is down.
Green – LMI is up.
OFF – Leased line mode is active (9123 and
9623), or the link is down.
9000-A2-GB33-30
October 2003
3-15
3. Status and Statistics
Table 3-1.
Label
Front Panel LEDs (2 of 4)
Indication
Color
What It Means
Multicolored
Yellow – ATM is down.
Models 9783, 9788:
ATM
ATM Status
Green – ATM is up.
Models 9520, 9520-ILM, 9820-45M:
TD
Transmit Data
Green
ON – At least one non-idle cell was transmitted
to the network during the sampling period.
OFF – No non-idle cell was transmitted to the
network during the sampling period.
RD
Receive Data
Green
ON – At least one non-idle cell was received
from the network during the sampling period.
OFF – No non-idle cell was received from the
network during the sampling period.
LMI
LMI Status
Green
ON – LMI is operating successfully on the
frame relay link.
OFF – LMI is not operating successfully.
Models 9520, 9520-ILM:
OOF
Out Of Frame
Green
ON – At least one OOF error was detected on
the network during the sampling period.
OFF – No OOF error was detected on the
network during the sampling period.
LOS
Loss Of Signal
Green
ON – An LOS error was detected on the
network during the sampling period.
OFF – No LOS error was detected on the
network during the sampling period.
AIS
Alarm Indication
Signal
Green
ON – An AIS was received during the sampling
period.
OFF – No AIS was received during the
sampling period.
YEL
Yellow Alarm
Green
ON – A Yellow Alarm condition existed during
the sampling period (meaning that the far-end
equipment reported an OOF or LOF error).
OFF – No Yellow Alarm condition was detected
during the sampling period.
Network, continued
Model 9820-45M:
DTR
DSR
Data Terminal
Ready
Green
Data Set Ready
Green
ON – The DTR lead is asserted.
OFF – The DTR lead is not asserted.
ON – The DSR lead is asserted.
OFF – The DSR lead is not asserted.
3-16
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-1.
Label
Front Panel LEDs (3 of 4)
Indication
Color
What It Means
Network, DSX-1, or ISDN PRI DBM
Models 9123, 9126, 9128:
SIG
T1 Signal
Green
ON – A recoverable signal is present on the
Network/DSX/PRI interface.
OFF – The signal cannot be recovered from
the Network/DSX/PRI interface. An LOS
condition exists.
OOF
Out of Frame
Yellow
ON – At least one OOF was detected during
the sampling period.
OFF – No OOFs were detected during the
sampling period.
ALM
Alarm
Yellow
ON – An alarm condition is present on the
network/DSX/PRI interface.
OFF – No alarm condition is present on the
Network/DSX/PRI interface.
Port
OK
Operational
Status
Green
ON – The interchange circuits for the port are
in the correct state to transmit and receive
data. For 9128 units (which have two data
ports but one related LED), at least one of the
ports is enabled and active.
OFF – The port is idle. Occurs if the port is
disabled, or if the port is configured to monitor
DTR and/or RTS and the lead(s) is not
asserted. For 9128 units, both ports are
enabled and at least one is inactive.
Models 9520, 9520-ILM, 9820-45M:
TD
Transmit Data
Green
ON – At least one transmit frame was received
from the DTE during the sampling period.
OFF – No transmit frame was received from
the DTE during the sampling period.
RD
Receive Data
Green
ON – At least receive frame was transmitted to
the DTE during the sampling period.
OFF – No receive frame was transmitted to the
DTE during the sampling period.
Port, continued
Models 9520, 9820-45M:
DTR
DSR
Data Terminal
Ready
Green
Data Set Ready
Green
ON – The DTR lead is asserted.
OFF – The DTR lead is not asserted.
ON – The DSR lead is asserted.
OFF – The DSR lead is not asserted.
9000-A2-GB33-30
October 2003
3-17
3. Status and Statistics
Table 3-1.
Label
Front Panel LEDs (4 of 4)
Indication
Color
What It Means
Green
ON – At least one OOF error was detected on
the network during the sampling period.
Model 9520-ILM:
OOF
Out Of Frame
OFF – No OOF error was detected on the
network during the sampling period.
LOS
Loss Of Signal
Green
ON – An LOS error was detected on the
network during the sampling period.
OFF – No LOS error was detected on the
network during the sampling period.
AIS
Alarm Indication
Signal
Green
ON – An AIS was received during the sampling
period.
OFF – No AIS was received during the
sampling period.
YEL
Yellow Alarm
Green
ON – A Yellow Alarm condition existed during
the sampling period (meaning that the far-end
equipment reported an OOF or LOF error).
OFF – No Yellow Alarm condition was detected
during the sampling period.
3-18
October 2003
9000-A2-GB33-30
3. Status and Statistics
Power Module LEDs (Models 9520, 9520-ILM, 9820-45M)
Each power module has a green LED which remains lit while power is applied and
the power module is functioning.
When the yellow front panel System PWR LED is lit, one of the power modules
has failed. The failed power module can be identified from the back of the DSU by
its unlit LED.
Table 3-2.
Power Module Troubleshooting
Configuration Symptom
What to Do
(in order, if problem persists)
One Power
Module
1. Verify that the receptacle in use provides
120 Vac.
No front panel
LEDs are lit.
2. Verify that the power module switch is in the On
position.
3. Replace the power module. See Replacing a
Power Module in Chapter 4, Operation and
Maintenance.
4. Call your service representative.
Two Power
Modules
No front panel
LEDs are lit.
1. Verify that the receptacles in use provide
120 Vac.
2. Verify that the power module switches are in
the On position.
3. Replace the power modules. See Replacing a
Power Module in Chapter 4, Operation and
Maintenance.
4. Call your service representative.
The front panel
System PWR LED
is lit.
1. Check the power module LEDs from the back
of the unit and replace the failed power module
(the one whose LED is off). See Replacing a
Power Module in Chapter 4, Operation and
Maintenance.
2. Call your service representative.
9000-A2-GB33-30
October 2003
3-19
3. Status and Statistics
Display LEDs and Control Leads Screen Descriptions
Table 3-3, Display LEDs and Control Leads Screen Labels, explains the notations
on the Display LEDs and Control Leads screens. An ON condition is denoted by
inverse text and an OFF condition by normal text. See the screen examples in
Viewing LEDs and Control Leads on page 3-4.
Table 3-3.
Label
Display LEDs and Control Leads Screen Labels (1 of 4)
Indication
What It Means
Power and
Operational
Status
ON – iMarc unit has power and it is operational.
Operational
Alarm (Fail)
ON – iMarc unit has just been reset, or an error or fault
has been detected.
General
OK
Alarm
OFF – iMarc unit is in a power-on self-test, or there is a
failure.
Alarms appear on the System and Test Status screen.
See Table 3-6, Health and Status Messages, for
additional information.
Test
Test Mode
ON – Loopback or test pattern is in progress, initiated
locally, remotely, or from the network.
OFF – No tests are active.
Models 9126, 9128, 9626 with ISDN Backup:
Backup
Backup
ON – iMarc unit is in Backup mode; that is, the backup
link has been established, and backup is in progress
through the specified Alternate Destination Link.
OFF – iMarc unit is not in Backup mode.
Blinking ON and OFF – Alternate Destination Link is
being established, but no data has been passed.
Models 9520, 9520-ILM, 9820-45M:
Fan Fail
Fan Status
ON – One or more of the four system fans has failed.
OFF – All fans are operational.
Pwr Fail
Power Supply
Status
ON – One of the two installed power modules has failed.
See Power Module LEDs (Models 9520, 9520-ILM,
9820-45M) on page 3-19.
OFF – Both power modules are operational or a
redundant power supply is not installed.
All models except 9783, 9788:
FR Mode
Service Mode
ON – The unit is in frame relay mode.
Models 9123, 9623:
LL Mode
3-20
Service Mode
ON – The unit is in leased line mode.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-3.
Label
Display LEDs and Control Leads Screen Labels (2 of 4)
Indication
What It Means
General, continued
Models 9783 and 9788 CSU/DSUs and Routers:
ATM Mode
ATM Status
ON – ATM is up.
Network Status
ON – The IDSL network interface is operational.
Network1
Model 9720:
OK
OFF – The IDSL network interface is not operational.
Models 9520, 9520-ILM, 9820-45M:
TD
Transmit Data
ON – At least one non-idle cell was transmitted to the
network during the sampling period.
OFF – No non-idle cell was transmitted to the network
during the sampling period.
RD
Receive Data
ON – At least one non-idle cell was received from the
network during the sampling period.
OFF – No non-idle cell was received from the network
during the sampling period.
Models 9520, 9520-ILM, 9720, 9820-45M:
LMI OK
LMI Status
ON – LMI is operating successfully on the frame relay
link.
OFF – LMI is not operating successfully.
Models 9520, 9520-ILM:
OOF
Out Of Frame
ON – At least one OOF error was detected on the
network during the sampling period.
OFF – No OOF error was detected on the network
during the sampling period.
LOS
Loss Of Signal
ON – An LOS error was detected on the network during
the sampling period.
OFF – No LOS error was detected on the network
during the sampling period.
AIS
YEL
Alarm Indication
Signal
ON – An AIS was received during the sampling period.
Yellow Alarm
ON – A Yellow Alarm condition existed during the
sampling period (meaning that the far-end equipment
reported an OOF or LOF error).
OFF – No AIS was received during the sampling period.
OFF – No Yellow Alarm condition was detected during
the sampling period.
9000-A2-GB33-30
October 2003
3-21
3. Status and Statistics
Table 3-3.
Label
Display LEDs and Control Leads Screen Labels (3 of 4)
Indication
What It Means
Network1, continued
Models 9783 and 9788 CSU/DSUs and Routers:
Data Mode
Data Mode
Active
ON – The unit has trained up and is operating in normal
data mode. The front panel DSL LED is on.
OFF – The unit has not trained up.
LOS
Loss Of Signal
ON – An LOS condition has been detected on the
network. The front panel ALM LED is on.
OFF – No LOS condition is detected.
Training
LCD
Training in
Progress
ON – The unit is training and the DSL LED is flashing.
Loss of Cell
Delineation
ON – An LCD alarm condition has been detected. On
the 9783, the front panel ATM LED is yellow.
OFF – The unit is not training.
OFF – No LCD condition is detected.
Model 9820-45M:
DTR
DSR
Data Terminal
Ready
ON – The DTR lead is asserted.
Data Set Ready
ON – The DSR lead is asserted.
OFF – The DTR lead is not asserted.
OFF – The DSR lead is not asserted.
Models 9123, 9126, 9128:
SIG
T1 Signal
ON – A recoverable signal is present on the
Network/DSX/PRI interface.
OFF – The signal cannot be recovered from the
Network/DSX/PRI interface. An LOS condition exists.
OOF
Out of Frame
ON – At least one OOF was detected during the
sampling period.
OFF – No OOFs were detected during the sampling
period.
ALM
Alarm
ON – An alarm condition is present on the
network/DSX/PRI interface.
OFF – No alarm condition is present on the
Network/DSX/PRI interface.
Port-n
Models 9123, 9126, 9128, 9623, 9626, 9720, 9783, 9788:
OK
Operational
Status
ON – The interchange circuits for the port are in the
correct state to transmit and receive data.
OFF – The port is idle. Occurs if the port is disabled, or
if the port is configured to monitor DTR and/or RTS and
the lead(s) is not asserted.
3-22
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-3.
Label
Display LEDs and Control Leads Screen Labels (4 of 4)
Indication
What It Means
Port, continued
Models 9520, 9520-ILM, 9820-45M:
TD
Transmit Data
ON – At least one transmit frame was received from the
DTE during the sampling period.
OFF – No transmit frame was received from the DTE
during the sampling period.
RD
Receive Data
ON – At least receive frame was transmitted to the DTE
during the sampling period.
OFF – No receive frame was transmitted to the DTE
during the sampling period.
Models 9520, 9820-45M:
DTR
DSR
Data Terminal
Ready
ON – The DTR lead is asserted.
Data Set Ready
ON – The DSR lead is asserted.
OFF – The DTR lead is not asserted.
OFF – The DSR lead is not asserted.
Model 9520-ILM:
OOF
Out Of Frame
ON – At least one OOF error was detected on the
network during the sampling period.
OFF – No OOF error was detected on the network
during the sampling period.
LOS
Loss Of Signal
ON – An LOS error was detected on the network during
the sampling period.
OFF – No LOS error was detected on the network
during the sampling period.
AIS
YEL
Alarm Indication
Signal
ON – An AIS was received during the sampling period.
Yellow Alarm
ON – A Yellow Alarm condition existed during the
sampling period (meaning that the far-end equipment
reported an OOF or LOF error).
OFF – No AIS was received during the sampling period.
OFF – No Yellow Alarm condition was detected during
the sampling period.
Ethernet
Models 9126, 9783, and 9788 Routers:
OK
9000-A2-GB33-30
Operational
Status
ON – The Ethernet interface is operational.
OFF – The Ethermet interface is not operational.
October 2003
3-23
3. Status and Statistics
Device Messages
These messages appear in the messages area at the bottom of the screens. All
device messages are listed in alphabetical order.
Table 3-4.
3-24
Device Messages (1 of 6)
Message
What It Indicates
What To Do
Access level is n,
Read-only.
User’s access level is 2 or
3; user is not authorized to
change configurations.
No action needed.
Already Active
Test selected is already
running.
„
„
„
„
„
Allow test to continue.
Select another test.
Stop the test.
No action needed.
Blank Entries
Removed
New had been selected
from the Administer Logins
screen, no entry was made,
then Save was selected.
Cannot Delete Trap
Manager
Delete was selected from
the Management PVCs
Options screen, but the
PVC had been defined as a
trap destination.
No action needed, or configure
another path for traps and try
again.
Cannot Save – no
Level 1 Login IDs
Security was being set up,
but all the logins were
assigned either Level-2 or
Level-3 access.
Set up at least one login with
Access Level-1 so the unit can be
configured.
Command Complete
Configuration has been
saved or all tests have been
aborted.
No action needed.
Connection Refused
Wait and try again.
(Seen at an FTP
terminal.)
Two menu-driven user
interface sessions are
already in use when a
Telnet session was
attempted.
Destination Not
Unique
Destination entered is
already being used.
Enter another destination
indicator.
DLCI in connection.
Delete connection first
User tried to delete a DLCI
that was part of a
connection.
„
„
DLCI Number Already
Exists
The DLCI number entered
on the DLCI Record Entry
screen has already been
created so is not unique.
Enter another DLCI number.
DLCI Number
Reserved
User tried to designate a
special troubleshooting
DLCI.
No action is needed.
October 2003
Reenter the Login ID,
Password, and Access Level.
No action needed, or
Delete the connection, then
delete the DLCI.
9000-A2-GB33-30
3. Status and Statistics
Table 3-4.
Device Messages (2 of 6)
Message
What It Indicates
What To Do
Duplicate DLCI
Number
DLCI number entered is not
unique for the frame relay
link.
No action needed; previous
contents of the DLCI number field
is restored.
File Transfer Complete A file transfer was
performed successfully.
(Seen at an FTP
terminal.)
File Transfer Failed –
Invalid file
(Seen at an FTP
terminal.)
A file transfer was
attempted, but it was not
successful.
Switch to the newly downloaded
software.
See Changing Software in
Chapter 4, Operation and
Maintenance.
„
„
Try again, making sure you
type the filename correctly.
Exit the FTP session, or
download another file.
See Changing Software in
Chapter 4, Operation and
Maintenance.
9000-A2-GB33-30
Invalid – Already
Active
A test was already in
progress when it was
selected.
No action needed.
Invalid – Link Already
Active
Start was selected for a
Test Call, but the selected
frame relay link is currently
in use.
Wait until the link is available and
try again.
Invalid – No ISDN
Channels Available
Start was selected for a
Test Call, but all supported
ISDN channels are
currently in use.
Wait until a channel is available
and try again.
Invalid – No Test Call
Active
Stop was selected for a Test
Call and no test call is
active on the selected link.
This can occur when the
test is ended because the
link is needed for an active
connection, but the PVC
Test screen has not yet
been updated to Start.
Start the Test Call again when the
connection is Inactive again.
Invalid Character (x)
A non-valid printable ASCII
character has been
entered.
Reenter information using valid
characters.
Invalid date: must be
mm/dd/yyyy
A non-valid date was
entered on the System
Information screen.
Reenter the date in the
month/day/4-digit year format.
Invalid date and/or
time
A non-valid date or time
was entered on the System
Information screen. The
date does not exist (e.g.,
February 30th).
Reenter the date in the
month/day/4-digit year format
and/or time in the
hour:minutes:seconds format.
October 2003
3-25
3. Status and Statistics
Table 3-4.
Device Messages (3 of 6)
Message
What It Indicates
What To Do
Invalid Password
Login is required and an
incorrect password was
entered; access is denied.
„
„
Invalid Test
Combination
Invalid time: must be
hh:mm:ss
A non-valid system time
was entered on the System
Information screen.
Limit of Mgmt PVCs
reached
New was selected from the
PVC Connection Table and
the maximum number of
management PVCs has
already been created.
Limit of PVC
Connections reached
Limit of six Login IDs
reached
3-26
A conflicting loopback or
pattern test was in progress
when Start was selected to
start another test, or was
active on the same or
another interface when
Start was selected.
New was selected from the
PVC Connection Table and
the maximum number of
PVCs has already been
created.
An attempt to enter a new
login ID was made, and the
limit of six login/password
combinations has been
reached.
„
„
„
Try again.
Contact your system
administrator to verify your
password.
Wait until other test ends and
message clears.
Cancel all tests from the Test
screen (Path: main/test).
Stop the test from the same
screen the test was started
from.
Reenter the time in the
hour:minutes:seconds format.
„
„
„
„
„
„
Do not create the management
PVC.
Delete another management
PVC, and try again.
Do not create the PVC
connection.
Delete another PVC
connection, and try again.
Delete another login/password
combination.
Reenter the new login ID.
Name Must be Unique
Name entered for a
management PVC has
been used previously.
Enter another 4-character name
for the logical/management link.
No Destination Link
DLCIs Available
New was selected from the
PVC Connection Table, but
even though DLCIs are
available to form a
connection, no DLCIs are
available on the network
link, which is a suitable PVC
Destination.
Configure additional DLCIs for the
network link and try again.
No DLCIs available for
connection
New was selected from the
PVC Connection Table, but
all configured DLCIs have
been connected.
No action needed, or configure
more DLCIs and try again.
New was selected from the
Management PVCs option
screen, but all Link/DLCI
pairs have been connected.
Configure more network and/or
Port-1 Links/DLCIs pairs and try
again.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-4.
9000-A2-GB33-30
Device Messages (4 of 6)
Message
What It Indicates
What To Do
No DLCIs Available for
Mgmt PVC
New was selected from the
Management PVCs option
screen, but all configured
DLCIs have been
connected.
Configure more network and/or
Port-1 DLCIs and try again.
No DLCIs Defined
DLCI Records was selected
from an interface’s
Configuration Edit/Display
menu, and no DLCI
Records have been created
for this interface.
Select New and create a DLCI
record.
No more DLCIs
allowed
New or CopyFrom was
selected from an interface’s
DLCI Records configuration
screen, and the maximum
number of DLCI Records
had already been reached.
Delete a DLCI, then create the
new DLCI Record.
No Primary
Destination Link DLCIs
Available
New or Modify was selected
from the PVC Connection
Table, but even though
DLCIs are available to form
a connection, no DLCIs are
available on the network
link, which is a suitable
Primary PVC Destination.
Configure additional DLCIs for the
network link and try again.
No Security Records
to Delete
Delete was selected from
the Administer Login
screen, and no security
records had been defined.
Password Matching
Error – Re-enter
Password
Password entered in the
Re-enter Password field of
the Administer Logins
screen does not match what
was entered in the
Password field.
October 2003
If a network DLCI has been
entered as a Source DLCI:
1. Change the Source DLCI to a
user data port DLCI.
2. Enter the network DLCI as the
PVC’s Primary Destination.
„
„
„
„
No action needed.
Enter a security record.
Try again.
Contact your system
administrator to verify your
password.
3-27
3. Status and Statistics
Table 3-4.
Device Messages (5 of 6)
Message
What It Indicates
Permission Denied
A file transfer was
attempted, but the:
(Seen at an FTP
terminal.)
„
„
„
User did not have Level
1 security.
Wrong file was specified
when the put command
was entered.
User attempted to
upload a program file
from the unit.
What To Do
„
„
„
Try again, entering the correct
file with the put command.
Enter the put command
instead of a get command; you
can only transfer files to the
unit, not from it.
See Upgrading System
Software in Chapter 4,
Operation and Maintenance.
Please Wait
Command takes longer
than 5 seconds.
Wait until message clears.
Port Inactive
The port is disabled, or it
supports synchronous data
when a DTE Loopback was
started.
No action is needed.
Resetting Device,
Please Wait ...
Yes (or y) was entered in
the Reset COM Port usage
field of the System Paused
menu.
No action needed.
Save Cancelled
Changes were made on the
Easy Install screen, but
when it came to saving the
changes, the Esc key was
pressed or No was entered
in response to the Save
Changes? prompt.
No action is needed.
(iMarc SLV 9128-II
only)
(iMarc SLV 9128-II
only)
Test Active
No higher priority System
and Test Status messages
exist, and a test is running.
„
„
„
„
3-28
See your system administrator
to get your security level
changed.
October 2003
Contact service provider if test
initiated by the network.
Wait until the test ends and
message clears.
Cancel all tests from the Test
screen (Path: main/test).
Stop the test from the same
screen the test was started
from.
9000-A2-GB33-30
3. Status and Statistics
Table 3-4.
Device Messages (6 of 6)
Message
What It Indicates
User Interface Already
in Use
Two Telnet sessions are
already in use when an
attempt to access the
menu-driven user interface
through the COM port is
made.
What To Do
„
„
Wait and try again.
Contact one of the IP address
user and request that they log
off.
IP addresses and logins of
the users currently
accessing the interface are
also provided.
User Interface Idle
Value Out of Range
9000-A2-GB33-30
Previously active session is
now ended, and access via
the COM port is now
available.
Log on to the iMarc unit.
Session has been ended
due to timeout.
No action needed.
The value entered is greater
or smaller than the range
allowed.
Enter a valid value.
October 2003
3-29
3. Status and Statistics
Status Information
Status information is useful when monitoring the iMarc unit. The following
illustration shows the Status menu for a iMarc SLV 9128-II with the ISDN DBM
feature installed.
Status Menu Example
main/status
Device Name: Node A
9128-II
5/26/2000 23:32
STATUS
System and Test Status
LMI Reported DLCIs
PVC Connection Status
Timeslot Assignment Status
DBM Interface Status
IP Routing Table
Performance Statistics
Trap Event Log
Display LEDs and Control Leads
Identity
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
DBM Interface Status will not appear on the menu if the unit does not have the
optional ISDN DBM feature.
NOTE:
Status messages contained in the following sections are in alphabetical order.
3-30
October 2003
9000-A2-GB33-30
3. Status and Statistics
System and Test Status Messages
System and test status information is selected from the Status menu.
Main Menu→Status →System and Test Status
The following information is included on this screen:
„
Self-Test Results Messages (Table 3-5)
„
Last System Reset Date and Time
„
Health and Status Messages (Table 3-6)
„
Test Status Messages (Table 3-7)
Self-Test Results Messages
One of these self-test result messages appears in the Self-Test Results field at the
top of the System and Test Status screen.
Table 3-5.
Self-Test Results Messages
Message
What It Indicates
What To Do
Failure xxxxxxxx
An internal failure occurred
(xxxxxxxx represents an
8-digit hexadecimal failure
code used by service
personnel).
1. Record the failure code.
2. Reset the unit.
3. Contact your service
representative.
Record the failure code
before resetting the unit;
otherwise, the error
information will be lost.
Passed
No problems were found
during power-on or reset.
No action needed.
Last System Reset Date and Time
This field indicates the last time the iMarc unit was reset. It appears after the
Self-Test Results field at the top of the System and Test Status screen.
9000-A2-GB33-30
„
Date is in mm/dd/yyyy format (month/day/year).
„
Time is in mm:ss format (minutes:seconds).
October 2003
3-31
3. Status and Statistics
Health and Status Messages
The following table describes all possible Health and Status messages.
Table 3-6.
Health and Status Messages (1 of 7)
Message
What It Indicates
AIS at DSX-1
An Alarm Indication Signal (AIS) is received by the
DSX-1 interface. AIS is an unframed, all ones signal.
AIS at ISDN PRI (Active/Idle)
An Alarm Indication Signal (AIS) is received by the
ISDN PRI interface. AIS is an unframed, all ones
signal.
(ISDN PRI DBM only)
Only appears when a PRI dial backup module (DBM)
is installed.
„
„
Active – Backup call was in progress.
Idle – DBM was in Idle mode.
The ISDN network is transmitting an AIS.
AIS at Network 1
An Alarm Indication Signal (AIS) is received by the
network interface. AIS is an unframed, all ones
signal. Possible reasons include:
„
„
Upstream iMarc unit is transmitting AIS
(keep-alive signal).
The network is transmitting an AIS.
AIS at T3 User, Port n
An Alarm Indication Signal (AIS) is being received on
the T3 user port interface.
Auto-Configuration Active
Auto-Configuration feature is active, which allows
automatic configuration and cross-connection of
DLCIs as they are reported by the network LMI.
Back-to-Back Mode Active
The operating mode has been configured for
back-to-back operation (Main Menu→ Control →
Change Operating Mode).
The iMarc unit can be connected to another iMarc
unit without a frame relay switch between them.
This feature is useful for product demonstrations or
for a point-to-point configuration using a leased line.
3-32
Backup Active
Backup has been established and data is flowing
over the alternate DLCI.
Cable Mismatch, Port-n
The presence or absence of an adapter cable on
Port n is inconsistent with the Port Type setting.
COSnDownPathIP_Address,
interface[DLCInnnn]
The class of service associated with the path is
unavailable.
Cross Pair Detection
The TX pair and RX pair are reversed on the DDS
network interface.
Clock Out of Range at Network 1
The clock rate detected on the network interface is
not within the range supported by the device.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-6.
Health and Status Messages (2 of 7)
Message
What It Indicates
CTS down to Port-1 Device
The user data port CTS control lead on the iMarc unit
is off.
DBM BRI Card Failed
One or more of the access unit’s integrated circuit
chips has failed to internally loop data through the
dial backup unit BRI circuit.
(ISDN BRI DBM only)
DBM Download Required
(ISDN BRI DBM only)
A download attempt was interrupted and failed to
complete.
The NAM software and DBM software are
incompatible.
DCLB Active, [Interface]
A V.54 Loopback is active on the specified interface.
DLCI nnnn Down,
frame relay link
The DLCI for the specified frame relay link is down.
DSL Line Training Alarm at
Network 1
The DSL interface is training.
DTE External LB Active, Port-n
A Data Terminal Loopback is running on the
specified user data port.
DTE Init. Ext LB Active, Port-n
The DTE has initiated an external DTE Loopback on
the specified user data port.
DTPLB Active, Port-2
A Data Terminal Payload Loopback (DTPLB) is
active on the synchronous user data port.
DTR Down from Port-1 Device
The DTR control lead from the device connected to
the user data port is deasserted.
EER at ISDN PRI (Active/Idle)
The error rate of the received ISDN network signal
exceeds the currently configured threshold. This
condition only occurs if the network interface is
configured for ESF framing and a PRI dial backup
module (DBM) is installed.
(ISDN PRI DBM only)
„
„
Active – Backup call was in progress.
Idle – DBM was in Idle mode.
This condition clears when the error rate falls below
the threshold value, which may take up to
15 minutes.
EER at Network 1
The error rate of the received network signal
exceeds the currently configured threshold. This
condition only occurs if the network interface is
configured for ESF framing.
This condition clears when the error rate falls below
the threshold value, which may take up to
15 minutes.
9000-A2-GB33-30
Ethernet Mgmt Down
The Ethernet port is enabled, but communication
between the management system and the unit is not
currently possible on the port.
Ethernet Port Down
The Ethernet data link is down.
October 2003
3-33
3. Status and Statistics
Table 3-6.
Health and Status Messages (3 of 7)
Message
What It Indicates
Excessive BPVs at Network 1
An Excessive Bipolar Violations condition is detected
on the DDS network interface.
Fan Failure
At least one of the system fans has failed.
Internal Modem Failed
The unit’s internal modem failed to pass the self-test.
ISDN Active
An ISDN call is active.
ISDN Link Profile Disabled
ISDN Link Name
An ISDN backup call could not be made because the
ISDN link profile specified Link Name is disabled
(Main Menu→ Configuration→ ISDN→
Link Profiles).
ISDN Link Profile Invalid,
ISDN Link Name
No phone numbers have been specified in the ISDN
link profile (specified by ISDN Link Name).
ISDN Network Failed (Active/Idle)
An ISDN network failure was detected when:
„
„
Idle – DBM was in Idle mode.
LatencyIP_ Address,
COSx,interface[DLCInnnn]
An IP SLV Latency Threshold has been exceeded for
the specified COS of the path. IP_Address is the IP
address of the path endpoint, COSx is the Class of
Service ID associated with the path, and nnnn is the
DLCI which contains the path.
Lease Line Active
The service type is Leased Line.
Link Layer Down, interface
The link layer is down on the specified interface.
Link Down Administratively, link
The specified frame relaylink has been disabled by
the unit due to a dependent relationship in the device
configuration, such as LMI behavior conditions.
Link Profile Disabled,
ISDN Link Name
An ISDN backup call could not be made because the
specified link profile was disabled.
LLB Active, [Interface]
A network Line Loopback (LLB) is active on the
specified interface.
LMI Discovery in Progress, frame
relay link
Local Management Interface protocol discovery is in
progress to determine which protocol will be used on
the specified frame relay link.
LMI Down, frame relay link
The Local Management Interface(s) has been
declared down for the specified frame relay link.
„
„
3-34
Active – Backup call was in progress.
For an individual ISDN link, the message appears
when LMI has been declared down on the link.
For a multilink aggregate link, the message
appears when LMI has been declared down on all
constituent links of the frame relay multilink.
LOF at Network 1
A Loss Of Frame condition has occurred on the T3
network interface.
LOF at T3 User, Port n
A Loss Of Frame condition has occurred on the T3
user port interface.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-6.
Health and Status Messages (4 of 7)
Message
What It Indicates
Loop Attenuation Defect at
Network 1
Loop attenuation is at a level higher than the
configured threshold.
LOS at DSX-1
A Loss of Signal (LOS) condition is detected on the
DSX-1 interface. Clears when the ratio of ones to
zeros received is greater than or equal to 12.5%.
Possible reasons include:
„
„
LOS at ISDN PRI (Active/Idle)
(ISDN PRI DBM only)
DSX-1 cable problem.
No signal being transmitted from the DTE.
A Loss of Signal (LOS) condition is detected on the
ISDN PRI interface. Clears when the ratio of ones to
zeros received is greater than or equal to 12.5%.
„
„
Active – Backup call was in progress.
Idle – DBM was in Idle mode.
Only appears when a dial backup module (DBM) is
installed. Possible reasons include:
„
„
LOS at Network 1
DBM cable problem.
T1 facility problem.
A Loss of Signal (LOS) condition is detected on the
network interface. Clears when the ratio of ones to
zeros received is greater than or equal to 12.5%.
Possible reasons include:
„
„
„
Network cable problem.
No signal is being transmitted at the far-end iMarc
unit.
T1 facility problem.
LOS at T3 User, Port n
A Loss of Signal (LOS) condition is detected on the
T3 user port interface. Clears when there is an
average pulse density of at least 33 percent over a
period of 175±75 contiguous pulse positions starting
with the receipt of a pulse.
Loss of Cell Delineation, atm link
Cell synchronization has been lost on the ATM link.
LOSW Failure at Network 1
-hhh:mm:ss
A Loss of Sync Word condition has existed on the
network interface for the number of hours, minutes,
and seconds shown.
Monitor Pttn. Active, DLCI nnnn,
frame_relay_link 1,2
The unit is monitoring a test pattern on the specified
DLCI on the specified frame relay link.
Monitor Pttn Active, [Interface]
A Monitor Pattern test is active on the specified
interface using a selected pattern.
This test cannot be activated on user data ports that
have Port Use set to Frame Relay.
No Signal at Network 1
-hhh:mm:ss
9000-A2-GB33-30
A No Signal condition has existed on the DDS
network interface for the number of hours, minutes,
and seconds shown.
October 2003
3-35
3. Status and Statistics
Table 3-6.
Health and Status Messages (5 of 7)
Message
What It Indicates
Network Com Link Down
The communication link for the COM port is down,
and the COM port is configured for Net Link.
Network Initiated ISDN BRI Test
Active
An ISDN test has been initiated by the ISDN BRI
network and it is currently active.
(ISDN BRI DBM only)
OOF at DSX-1
An Out of Frame (OOF) condition is detected on the
DSX-1 interface. Possible reasons include:
„
„
OOF at ISDN PRI (Active/Idle)
(ISDN PRI DBM only)
Incompatible framing format between the DTE
and the iMarc unit.
DSX-1 cabling problem.
An Out of Frame (OOF) condition is detected on the
ISDN PRI interface. An OOF is declared when two
out of four frame synchronization bits are in error.
„
„
Active – Backup call was in progress.
Idle – DBM was in Idle mode.
Possible reasons include:
„
„
„
OOF at Network 1 [-hhh.mm.ss]
ISDN network cabling problem.
ISDN network problem.
An Out of Frame (OOF) condition is detected on the
T1 or DDS network interface. For DDS, the duration
of the condition is displayed. Possible reasons
include:
„
„
„
Incompatible framing format between the network
and the iMarc unit.
Network cabling problem.
Facility problem.
OOS at Network 1 -hhh:mm:ss
An Out Of Service condition has existed on the DDS
network interface for the number of hours, minutes,
and seconds shown.
PathIP_ Address Down, interface
[DLCInnnn]
A path on the network interface is unavailable.
IP_Address is the IP address of the path endpoint,
and nnnn is the DLCI which contains the path.
PLB Active, interface
A Payload Loopback (PLB) is active on the specified
interface.
Power Supply Failure
The power supply output voltage has dropped below
the specified tolerance level required for the system.
(Models 9520, 9520-ILM, and
9820-45M)
Power Supply/Fan Failure
(9000 Series Access Carrier only)
3-36
Incompatible framing format between the ISDN
network and the iMarc unit.
The power supply output voltage has dropped below
the specified tolerance level required for the system,
or the fan tray is not operating properly.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-6.
Health and Status Messages (6 of 7)
Message
What It Indicates
Primary Clock Failed
A failure of the primary clock source configured for
the unit is detected and the secondary clock is
providing the timing for the unit.
This condition clears when the configured primary
clock is restored.
Primary & Secondary Clocks
Failed
A failure of the primary and secondary clock sources
configured for the unit are detected and the internal
clock is providing timing for the unit.
The clock source will not automatically switch from
internal until the primary clock source returns.
PVC Loopback Active, DLCInnnn,
frame_relay_link
A PVC Loopback is active on the specified DLCI on
the frame relay link.
RLB Active, [Interface]
A network Repeater Loopback (RLB) is active on the
specified interface.
Secondary Clock Failed
A failure of the secondary clock source configured for
the unit is detected and the internal clock is providing
the timing for the unit.
The clock source will not automatically switch from
internal until the primary clock source returns.
Send Pattern Active, DLCInnnn,
frame_relay_link
A Send Pattern test is currently active on the
specified DLCI on the specified frame relay link.
Send Pttn Active, [Interface]
A Send Pattern test is active on the specified
interface using a selected test pattern.
This test cannot be activated on user data ports that
have Port Use set to Frame Relay.
SLV Latency Exceeded,
DLCInnnn, frame relay link
The measured latency of SLV communication
responses from the remote unit on this DLCI is
excessive, so the DLCI has been declared unsuitable
for normal multiplexed PVC operation (DLCI Type is
set to Multiplexed).
SLV Timeout, DLCInnnn,
frame relay link
An excessive number of SLV communication
responses from the remote iMarc SLV unit have
been missed on the specified multiplexed DLCI; the
DLCI is not suitable for user data.
When a hardware bypass capable device has been
detected at the other end of the PVC and this
condition occurs, only user data for EDLCI 0 will be
transmitted while this condition exists.
When an ISDN DBM is present, this message only
appears for individual and aggregate multilink frame
relay links, not constituent links of a frame relay
multilink.
9000-A2-GB33-30
SNR Margin Defect at Network 1
The observed SNR Margin is lower than the
configured threshold.
SNR Margin Threshold Exceed,
Network 1
The observed SNR Margin has exceeded the
configured threshold.
October 2003
3-37
3. Status and Statistics
Table 3-6.
Health and Status Messages (7 of 7)
Message
What It Indicates
Suboptimal Link Rate,
frame relay link 2
The specified frame relay multilink has failed to
achieve the configured Maximum Link Rate for the
link.
(ISDN DBM only)
This message appears for multilink aggregate frame
relay links if LMI is down on any of its constituent
links.
Timeslot Discovery in Progress,
Network 1
Time slot discovery is currently taking place to
determine the time slots that will be used for frame
relay traffic on the network interface.
This message only appears when the Time Slot
Discovery option is enabled (Main Menu→
Configuration→ Time Slot Assignment→Frame
Relay Network Assignments) and an LMI failure is
detected on the network interface’s frame relay link.
Two Level-1 Users Accessing
Device
Two Level 1 users are already using the menudriven user interface; only two sessions can be
active at one time.
Test Call Active, ISDN Link Name
A test call is active on the specified frame relay link,
the link being the ISDN Link Name assigned in the
ISDN Link Profile.
This message would only appear for models with the
built-in DBM.
Yellow at DSX-1
A yellow alarm signal is received on the DSX-1
interface. DTE has detected a LOS or OOF
condition.
Yellow at ISDN PRI (Active/Idle)
A yellow alarm signal is received on the ISDN
network interface.
(ISDN PRI DBM only)
„
„
Active – Backup call was in progress.
Idle – DBM was in Idle mode.
Indicates a possible cable problem.
Yellow at Network 1
A yellow alarm signal is received on the network
interface. Possible reasons include:
„
„
Yellow at T3 User, Port n
3-38
Network cable problem.
T1 facility problem.
A yellow alarm signal is received on the T3 user port
interface.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Test Status Messages
These test messages appear in the right column of the System and Test Status
screen. You have the option of allowing the test to continue or aborting the test.
See Chapter 5, Troubleshooting, for more information on tests, including how to
start and stop them.
Table 3-7.
Test Status Messages (1 of 2)
Message
What It Indicates
511 Pattern Test Active, Network n
A 511 Pattern test is active on the specified SHDSL
network interface.
BER Loopback Active, Network n
A BER Loopback is active on the specified DSL
interface.
CSU Loopback Active, Network n
A CSU Loopback is active on the specified DDS
interface.
DCLB Active, link
A Data Channel V.54 Loopback (DCLB) is active on
the specified frame relay link, or Port-2.
DCLB Active, Port-2
DSU Loopback Active, Network n
A DSU Loopback is active on the specified DDS
interface.
DTE External LB Active, Port-n
An external DTE Loopback is active on the user
data port.
DTE Init. Ext LB Active, Port-n
An external DTE Loopback is active on the user
data port.
DTPLB Active, Port-n
A Data Terminal Payload Loopback (DTPLB) is
active on the user data port.
Lamp Test Active
The Lamp Test is active, causing the LEDs on the
faceplate to flash on and off.
Latching DSU LB Active, Network n A DSU Loopback is active on the specified DDS
interface.
LLB Active, Interface
A Line Loopback (LLB) is active on the specified
user port, network, DSX-1, or ISDN PRI interface.
Monitor Pttn Active, DLCI nnnn,
frame_relay_link
A selected Monitor Pattern test is active on the
specified DLCI for the specified frame relay link.
Monitor Pttn Active, Interface 2
A Monitor Pattern test is active on the specified
interface.
This test cannot be activated on user data ports that
have Port Use set to Frame Relay.
9000-A2-GB33-30
Net Initiated CSU Loopback Active,
Network n
A network-initiated CSU Loopback is active on the
specified DDS interface.
Network Initiated ISDN BRI Test
Active
An ISDN test has been started by the ISDN BRI
network and it is currently active.
No Test Active
No tests are currently running.
NonLatching DSU LB Active,
Network n
A DSU Loopback is active on the specified DDS
interface.
October 2003
3-39
3. Status and Statistics
Table 3-7.
Test Status Messages (2 of 2)
Message
What It Indicates
Packet Mode Loopback Active,
Network n
A Packet Mode Loopback is active on the specified
DSL interface.
PLB Active, Interface
A Payload Loopback (PLB) is active on the
specified network, DSX-1, or ISDN PRI interface.
PVC Loopback Active, DLCI nnnn,
frame_relay_link
A PVC Loopback is active on the specified DLCI for
the frame relay link.
RLB Active, Interface
A network Repeater Loopback (RLB) is active on
the specified network or DSX-1 interface.
Send Pttn Active, DLCI nnnn,
frame_relay_link
A selected Send Pattern test is active on the
specified DLCI for the specified frame relay link.
Send Pttn Active, Interface
A Send Pattern test is active on the specified
interface.
This test cannot be activated on user data ports that
have Port Use set to Frame Relay.
Test Call Active, ISDN Link Name
A test call is active on the specified frame relay link,
the link being the ISDN Link Name assigned in the
ISDN Link Profile.
This message would only appear for units with the
ISDN DBM feature.
Tran. Pass-Thru Test Active,
Network n
3-40
A Transparent Pass-Through Loopback test is
active on the specified SHDSL network interface.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Network LMI-Reported DLCIs Status
Network LMI-reported DLCI statuses are selected from the Status menu.
Main Menu→Status→LMI Reported DLCIs
The LMI Reported DLCIs screen displays the status and CIR (if supported by the
switch) for each DLCI, whether the DLCI is configured or not.
LMI-Reported DLCIs Status Screen Example
main/status/lmi_dlcis
Device Name: Node A
9128-II
5/26/2000 23:32
frame relay link LMI REPORTED DLCIs
*
*
*
*
DLCI
300
305
400
410
411
420
430
501
511
520
STATUS
Active
Inactive
Deleted
Inactive
Inactive
Inactive
Active
Inactive
Active
Active
CIR (bps)
16000
32000
*
*
*
*
*
*
DLCI
622
624
625
713
822
1002
STATUS
Active
Active
Deleted
Active
Active
Active
Page 1 of 2
CIR (bps)
32000
32000
32000
32000
32000
256000
64000
* – DLCI is configured on the Frame Relay Link.
-------------------------------------------------------------------------------Exit
ESC for previous menu
MainMenu
PgUp
PgDn
NextLink
PrevLink
Refresh
An asterisk (*) next to the DLCI indicates that the DLCI has been configured for the
link.
DLCIs without an asterisk have not been configured in the unit. These DLCIs pass
through the unit transparently, without being monitored and with no
demultiplexing/multiplexing of management diagnostics or user data being
performed. Only DLCIs on the Net1-FR1 and Port-1 frame relay links appear on
this screen; nonconfigured DLCIs on other links are discarded.
9000-A2-GB33-30
October 2003
3-41
3. Status and Statistics
Table 3-8.
Network LMI-Reported DLCIs Status
Field
Status
What It Indicates
DLCI
16 through 1007
Identifies the Local Management
Interface-reported DLCI numbers
assigned to the selected interface – the
identifying number assigned to the path
between two frame relay iMarc units’
ports.
DLCI statuses are listed in ascending
order (i.e., lowest number first).
Status
CIR (bps)
LMI-reported status of the DLCI:
Active
„
Inactive
„
Deleted 1
„
New1
„
0–1536000
Displays the committed information rate
reported by the Stratacom switch. CIR
information only appears in this column
when LMI Protocol is set to Standard.
Whether the DLCI is active (capable of
carrying data) in the frame relay
network,
Whether it is inactive in the frame relay
network,
Whether it has been deleted by the
frame relay network, or
Whether it has been created by the
frame relay network.
If blank, the switch does not support this
feature.
1
3-42
Appears for 10 seconds only, before the network changes Deleted to Inactive
and New to Active.
October 2003
9000-A2-GB33-30
3. Status and Statistics
IP Path Connection Status
IP Path Connection Status is selected from the Status menu.
Main Menu→Status→IP Path Connection Status
The IP Path Connection Status screen displays the IP Path List, a list of devices
that can be reached by their IP addresses for Service Level Management
purposes.
The list is displayed in IP address order and includes both static addresses
entered using the IP Path List (Static) configuration screen (see Configuring the IP
Path List in the iMarc SLV Configuration Reference) and paths discovered as
packets are received from other iMarc units
This screen only appears when Service Type is set to Frame Relay.
IP Path Connection Status Screen Example
main/status/path
Device Name: Node A
9128-II
03/12/2002 05:00
Net1_FR1 IP PATH CONNECTION STATUS
Page 1 of 2
DLCI: 201
Device Name IP Address
Status
Discovery Source
Poughkeepsie 135.026.002.001 Active
135.026.002.005
New York 135.026.002.002 InActive 135.026.002.005
Boston 135.026.002.003 Active
135.026.002.005
Los Angeles 135.026.002.004 Active
135.026.002.005
Chicago 135.026.002.005 Active
135.026.002.005
San Francisco 135.026.002.006 Active
135.026.002.005
Milwaukee 135.026.002.007 Active
135.026.002.005
Unknown 137.010.010.001 Active
Static
Miami 137.010.010.002 Active
Static
Orlando 137.010.010.003 Active
Static
-------------------------------------------------------------------------------ESC for previous menu
MainMenu
Exit
PgUp
PgDn
NextDLCI
PrevDLCI
Refresh
9000-A2-GB33-30
October 2003
3-43
3. Status and Statistics
Table 3-9.
IP Path Connection Status
Field
Value
What It Indicates
Link
DSX-1
Net1-FR1
Net1
Port-n
Interface on which the IP enabled circuit
exists.
DLCI
16 through 1007
The IP Enabled DLCI.
Device Name
Up to 20 ASCII
characters
The name of the device configured using
the System Information screen of the
Control branch, or Unknown if the device
is not an iMarc unit.
IP Address
000.000.000.001 –
255.255.255.255
The IP address of the unit at the far end
of the path.
Status
The status of the path:
Active
Inactive
The path is operational.
The path is not operational.
The source of the path definition:
Discovery Source
„
„
3-44
„
„
Static
000.000.000.001 –
255.255.255.255
October 2003
„
„
The path was entered using the IP
Path List (Static) screen
This is the IP address of the iMarc unit
that provided the path.
9000-A2-GB33-30
3. Status and Statistics
PVC Connection Status
PVC connection statuses are selected from the Status menu.
Main Menu→Status→PVC Connection Status
The PVC Connection Status screen shows all PVC connections and management
links configured for the unit. The source and primary destination are shown, along
with an alternate destination for backup. When a primary destination DLCI was
assigned to a Backup Group, the Backup Group designation appears next to the
DLCI number. In the example below, DLCIs 502 and 504 had been assigned to
Backup Group A.
PVC Connection Status Screen Example
main/status/connections
Device Name: Node A
9128-II
5/13/2001 23:32
Page 1 of 2
Link
Source
DLCI EDLCI
Port-1 201
Port-2 202
Port-1 100
Port-2 204
Mgmt PVC Tampa
Port-2 206
Port-1 207
Port-1 208
Port-1 209
Port-1 210
Port-1 214
PVC CONNECTION STATUS
Primary Destination
Link
DLCI
EDLCI
Status
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
300
1001
1001
1001
1001
1001
1001
502A
504A
505
506
PM
1
4
2
5
3
Alternate Destination
Link
DLCI EDLCI Status
Active
Active
Active
Active
Active
Active
Active
Active
Colorado
Inactive Colorado
Inactive Tampa
Active
400
302
304
Inactive
Active
Active
-------------------------------------------------------------------------------Exit
ESC for previous menu
MainMenu
PgUp
PgDn
Refresh
For units with ISDN backup capability, the DBM provides backup support through
the unit’s ISDN DBM interface. For units without ISDN backup capability, an
alternate network DLCI can be used to backup user data. For additional
information about the Alternate Destination fields, see Configuring PVC
Connections in the iMarc SLV Configuration Reference.
If the No PVC Connections message appears instead of a list of PVC
connections, no PVC connections have been configured yet.
9000-A2-GB33-30
October 2003
3-45
3. Status and Statistics
Table 3-10. PVC Connection Status (1 of 2)
Field
Value
Link
DLCI
What It Indicates
Identifies the cross-connection of
DLCIs configured for the unit.
DSX-1
„
Net1-FR1
„
Port-1, or Port-2
„
MgmtPVCName
„
16 to 1007
For standard DLCIs.
Source/destination is the DSX-1
interface, configured as a user
data port (9126 only).
Source/destination is frame relay
link 1 on Network 1
User data port – Port-1, or Port-2
if an iMarc SLV 9128/9128-II
Virtual circuit is a management
link that terminates in the unit,
where Name is the link name
Identifies an individual link/
connection embedded within a DLCI.
EDLCI
0 to 62
IP
PM
3-46
October 2003
For multiplexed DLCIs, a number
from 0 to 62 identifies an individual
link embedded within a DLCI.
For IP Enabled DLCIs, IP is
displayed. For payload managed
DLCIs not IP Enabled, PM is
displayed.
9000-A2-GB33-30
3. Status and Statistics
Table 3-10. PVC Connection Status (2 of 2)
Field
Value
Status
What It Indicates
Identifies whether the physical
interfaces, LMIs, and DLCIs are all
enabled and active for this PVC
connection.
Active *
„
Inactive
„
The PVC is currently active.
The PVC is inactive because:
– Alarm conditions and network
and SLV communication
status indicate that data
cannot be successfully
passed.
– The unit has disabled the
interface or frame relay link
due to internal operating
conventions.
– Activation of an alternate
virtual circuit is not warranted;
that is, no alarm condition on
the primary destination link
has been detected.
Disabled
„
The PVC cannot be activated and
is essentially disabled as a result
of how the unit was configured.
Possible causes:
– The physical interface at one
or both ends of the PVC is/are
disabled.
– The frame relay link on one or
both ends of the PVC is/are
disabled.
Invalid
„
Some portion of the PVC
connection is not fully configured.
* For the circuit to be active, both Source and Destination Statuses must be Active.
9000-A2-GB33-30
October 2003
3-47
3. Status and Statistics
Time Slot Assignment Status
Time slot assignments are made using the Time Slot Assignment configuration
option. See Assigning Time Slots/Cross Connections in the iMarc SLV
Configuration Reference for making time slot assignments. Use the Timeslot
Assignment Status screen to display time slot assignments for the network
channels and the DSX-1 channels.
Displaying Network Time Slot Assignments
Use the Network Timeslot Assignment Status screen to display DS0 assignments
for each DS0 on the network interface.
Main Menu→Status→Timeslot Assignment Status →Network
The Network Timeslot Assignment Status screen displays 24 two-field entries in
three rows. Together, each two-field entry defines the assignment for one network
interface time slot. The top field represents the timeslot of the network interface.
The bottom field represents the cross-connect status of the associated (top field)
network time slot.
Network Timeslot Assignment Status Screen Example
main/status/timeslot/net_display
Device Name: Node A
9128-II
5/26/2000 23:32
NETWORK 1 TIMESLOT ASSIGNMENT STATUS
N01
D5-1/01r
N02
D5-1/02r
N03
D5-1/03r
N04
S1P01
N05
S1P01
N06
S1P01
N07
S1P01
N08
S1P01
N09
N10
N11
N12
N13
N14
N15
N16
FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1
N17
N18
Unassign Unassign
N19
Unassign
N20
Unassign
N21
Unassign
N22
Unassign
N23
N24
Unassign Unassign
Slot 1 - T1 FR NAM
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
Refresh
3-48
October 2003
9000-A2-GB33-30
3. Status and Statistics
The following information is available for network interface time slots (N01– N24).
The Cross Connect
Status Field (bottom) . . .
Indicates . . .
Unassgn
The time slot is unassigned.
FrameRly1
The time slot is assigned to the network frame relay link.
Port-2
The synchronous data port (Port-2) is assigned to the
network interface time slot (01 to 24).
Ds-p/tt
The DSX-1 time slot tt is assigned to the network interface
time slot (01 to 24).
Ds-p/ttr
The DSX-1 time slot tt is assigned to the network interface
time slot (01 to 24), using Robbed Bit Signaling (r).
Displaying DSX-1 Time Slot Assignments
Use the DSX-1 Timeslot Assignments Status screen to display all of the DS0
assignments for each DS0 on the DSX-1 interface.
Main Menu→Status→Timeslot Assignment Status→DSX-1
The DSX-1 Timeslot Assignment Status screen displays 24 two-field entries in
three rows. Together, each two-field entry defines the assignment for one DSX-1
interface time slot. The top field represents the time slot of the DSX-1 Interface.
The bottom field represents the cross-connect status of the associated (top field)
DSX-1 time slot.
DSX-1 Timeslot Assignment Status Screen Example
main/status/timeslot/dsx_display
Device Name: Node A
9128-II
5/26/2000 23:32
DSX-1 TIMESLOT ASSIGNMENT STATUS
D01
D02
D03
D05-1/01r D05-1/02r D05-1/03r
D04
S1P01
D05
S1P01
D06
S1P01
D07
S1P01
D08
S1P01
D09
D10
D11
D12
D13
D14
D15
D16
FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1 FrameRly1
D17
D18
Unassign Unassign
D19
Unassign
D20
Unassign
D21
Unassign
D22
Unassign
D23
D24
Unassign Unassign
Slot 1 - T1 FR NAM
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
Refresh
9000-A2-GB33-30
October 2003
3-49
3. Status and Statistics
The following information is available for DSX-1 interface time slots (D01– D24):
The Cross Connect
Status Field (bottom) . . .
Indicates the . . .
blank
The time slot is unassigned.
Net1/tt
Network interface 1, time slot (tt) is assigned to DSX-1 time
slot (01 to 24) using Clear Channel.
Net1/ttr
Network interface 1, time slot (tt) is assigned to DSX-1 time
slot (01 to 24) using Robbed Bit Signaling (r).
DBM Interface Status
When an ISDN DBM is installed, these interface statuses appear when DBM
Interface Status is selected from the Status menu.
Main Menu→Status→DBM Interface Status
DBM Interface Status Screen Example
main/status/dbm
Device Name: Node A
9128-II
5/26/2000 23:32
DBM INTERFACE STATUS
Line Status:
Call Rejected - HQ_Site: Disabled
Link:
Multilink Constituent Link:
Link Operating Mode:
Call Status:
Most Recent Cause Value:
Previous Cause Value 1:
2:
3:
4:
Maximum Link Rate (Kbps):
Negotiated Rate (Kbps):
ISDN Channel:
Remote Call ID:
Colorado
Colorado-1
Active
Connected
Call Awarded and Being Delivered In Est Chnl-7
None
None
None
None
64K
(Configured)
64K
B1
8135302000
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
NextLink
PrevLink
ConstLinkStatus
Refresh
Select the NextLink and PrevLink function keys to move forward or backward
through the frame relay link that can be selected. If the selected frame relay link is
a multilink aggregate link, select the ConstLinkStatus function key to see the
status for selected constituent links.
For a multilink aggregate link, Multilink Constituent Link appears under Link so a
specific constituent link can be selected. Otherwise, the line is blank. In addition,
the Most Recent Cause Value, Previous Cause Values, and Remote Call ID do not
appear for a multilink aggregate frame relay link.
3-50
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-11. DBM Interface Status (1 of 3)
Field
Status
Line Status
What It Indicates
The overall status of the ISDN line.
Active
„
Disabled
„
Inactive
„
Invalid SPID
„
Invalid Local Number
„
Call Rejected – Invalid
ID: Caller ID
„
The ISDN line is active and no
error conditions exist.
The ISDN interface has been
disabled.
Main Menu→Configuration→
ISDN→Physical
The ISDN line is disconnected or
an ISDN network alarm condition
exists.
The switch has rejected one of
the configured SPIDs
(ISDN BRI DBM only).
The phone number configured for
a B-channel is an invalid local
number.
The incoming call was rejected
because the Caller ID or local
phone number received from the
switch did not match any
configured Link Profiles.
If provided by the switch, the
rejected Caller ID is displayed
after the status. Otherwise,
Invalid Call ID is displayed.
Call Rejected – No
Far-End ID
„
„
Call Rejected – ISDN
Link Name: Busy
„
The incoming call was rejected
because no Caller ID was
received from the switch (COM
port’s Port Use option is set to
Caller ID).
No local phone number was
received from the far-end device
during the call validation process
(COM port’s Port Use option is
set to Proprietary).
The incoming call was rejected
because the enabled ISDN Link
Name associated with the
incoming Caller1 ID or local
phone number was busy.
The ISDN Link Name associated
with the incoming call is
displayed.
1
2
3
9000-A2-GB33-30
Only appears for a constituent frame relay link.
If Link Operating Mode is Disabled or Idle, the Remote Call ID, ISDN Channel, and
Negotiated Rate fields will not appear.
Appears for frame relay links with only one constituent and for all constituent frame
relay links.
October 2003
3-51
3. Status and Statistics
Table 3-11. DBM Interface Status (2 of 3)
Field
Status
Line Status
Call Rejected – ISDN
Link Name: Disabled
(continued)
What It Indicates
„
The incoming call was rejected
because the enabled ISDN Link
Name associated with the
incoming Caller1 ID or local
phone number was disabled.
The ISDN Link Name associated
with the incoming call is
displayed.
Link
ISDN Link Name
The selected ISDN backup link for
which status will be displayed.
Multilink Constituent
Link 1
ISDN Link Name
The selected multilink constituent
link for which status will be
displayed.
Link Operating Mode
The status of the ISDN DBM.
Idle 2
„
„
Active
„
Disabled 2
Call Status
An ISDN link is not currently
needed, so there is no ISDN
connection.
The ISDN link is required for
frame relay traffic and needs an
active ISDN connection.
The overall status of the ISDN frame
relay link.
Not Connected – Invalid
Link Profile
„
Not Connected
„
Connected
„
Connected – Incoming
Call 1
3-52
The ISDN Link Profile is disabled.
„
No calls are currently connected
on the selected link because the
ISDN Link Profile is incomplete.
No calls are currently connected
on the selected link.
At least one call is actively
connected and available for data
transfer on the selected ISDN
frame relay link (when the Most
Recent Cause Value is Call
Awarded and Being
Delivered In Est Chnl-7).
An incoming call has been
answered and is actively
connected and available for data
transfer on the selected multilink
constituent link (when the Most
Recent Cause Value is Call
Awarded and Being
Delivered In Est Chnl-7).
1
Only appears for a constituent frame relay link.
2
If Link Operating Mode is Disabled or Idle, the Remote Call ID, ISDN Channel, and
Negotiated Rate fields will not appear.
3
Appears for frame relay links with only one constituent and for all constituent frame
relay links.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-11. DBM Interface Status (3 of 3)
Field
Status
Call Status
Connected – Outbound
Call 1
(continued)
Most Recent Cause
Value 3
An outbound call has been placed
and is actively connected and
available for data transfer on the
selected multilink constituent link
(when the Most Recent Cause
Value is Call Awarded and
Being Delivered In Est
Chnl-7).
Refer to Table 3-12, Most Recent
and Previous Cause Value
Messages, for additional information.
BRI DBM:
64K, 128K
The maximum link rate that was
configured for the selected link. This
is the maximum rate the link will
attempt to achieve when activated.
PRI DBM:
64K, 128K, . . . 1472
Negotiated Rate
(Kbps)
„
Various ITU cause
messages
Previous Cause
Values 3
Maximum Link Rate
(Kbps)
What It Indicates
64K per B-channel
56K per B-channel
The negotiated rate of the
connection/link.
For a multilink aggregate frame relay
link, the negotiated rate will be the
sum of the negotiated rates on all
connected constituent links.
ISDN Channel
BRI DBM:
B1, B2
The ISDN B-channel being used for
the call on this link.
PRI DBM:
B1, B2, . . . B23
Remote Call ID 3
9000-A2-GB33-30
None
Backup has never been active on
the link.
Remote device’s ID
Remote call origination – Last
Calling ID of the remote backup
device received for the B-channel. If
the remote device initiated the call,
this is the Inbound Call ID. If this
device originated the call, this is the
Outbound Phone Number.
1
Only appears for a constituent frame relay link.
2
If Link Operating Mode is Disabled or Idle, the Remote Call ID, ISDN Channel, and
Negotiated Rate fields will not appear.
3
Appears for frame relay links with only one constituent and for all constituent frame
relay links.
October 2003
3-53
3. Status and Statistics
Most Recent and Previous Cause Value Messages
The following Cause Value Messages are presented in alphabetical order. The
Cause Number is also provided if you need to convert the message to its
corresponding ITU number for your service provider.
Table 3-12. Most Recent and Previous Cause Value Messages (1 of 6)
Message
3-54
Cause
No.
What It Indicates
What To Do
Bearer Capability
Not Authorized
57
User has requested a
bearer capability that the
user is not authorized to
use.
Arrange for the desired
capability.
Bearer Capability
not Implemented
65
Device sending this cause
does not support the bearer
capability (i.e., channel
type) requested.
Arrange for the desired
capability.
Bearer Capability
Presently Not
Available
58
Bearer capability requested
is supported by the device
generating the cause, but it
is not available at this time.
Arrange for the desired
capability.
Call Awarded and
Being Delivered in
Est Chnl-7
7
An incoming call is being
connected to an already
established channel that is
used for similar calls.
No action is needed.
Call Rejected
21
Equipment sending the
cause does not want to
receive the call at this time.
No action is needed.
Call Terminated by
Remote End
130
Remote DBM rejected or
terminated the call.
1. Retry the call.
Call With Requested
Call ID Has Been
Cleared
86
Network has received a call
resume request, but the call
had been cleared after it
was suspended.
No action is needed.
Channel Type Not
Implemented
66
Device sending this cause
does not support the
requested channel type.
Arrange for the desired
capability.
Channel
Unacceptable
6
Channel identified for the
call is not acceptable to the
receiving device.
Arrange for the desired
capability.
Destination Out of
Order
27
Destination interface
specified is not functioning
correctly so the signalling
message could not be
delivered (e.g., physical or
data-link layer failure at the
remote end, user
equipment is offline).
Verify that the remote
DBM’s link profile is correct.
October 2003
2. Verify that the remote
DBM’s link profile is
correct.
9000-A2-GB33-30
3. Status and Statistics
Table 3-12. Most Recent and Previous Cause Value Messages (2 of 6)
Message
Cause
No.
What It Indicates
What To Do
Facility Rejected
29
Requested facility is not
provided by the network.
No action is needed.
Incoming Calls
Barred
54
Called user is not permitted
to accept the call.
Turn off network call
screening.
Incompatible
Destination
88
Request to establish a call
has been received, but
low-layer, high-layer, or
another compatibility
attribute (e.g., data rate)
cannot be provided.
Arrange for the desired
capability.
Incorrect format of the
destination link.
9000-A2-GB33-30
Identified Channel
Does Not Exist
82
Channel requested for a call
is not activated on the
interface.
Make sure the network is
configured for 2B service, if
a BRI DBM. Contact your
service provider to verify
that your service is
provisioned for two
B-channels.
Info Element
Nonexistent or
Nonimplemented
99
Device sending this cause
has received a message it
does not recognize.
1. Verify that the Inbound
Calling ID has been
defined.
This cause will not prevent
the message from being
precessed.
2. Verify that the Inbound
Calling ID is part of your
service.
Interworking,
Unspecified
127
Precise cause of a
message cannot be
determined because the
interworking network does
not provide causes.
No action is needed.
Invalid Call
Reference Value
81
Call reference used is not
currently in use on the
user-network interface.
Contact your service
representative.
Invalid Info Element
Contents
100
Device sending this cause
has received and
implemented an information
element, but one or more
fields in the element cannot
be processed.
Contact your service
representative.
Invalid Message,
Unspecified
95
No other cause in the
invalid message class
applies for this invalid
message event.
Contact your service
representative.
Invalid Number
Format – Incomplete
Address
28
Call cannot be completed
because the phone number
is incorrect or incomplete.
Check your ISDN link
profile, and correct the
number.
October 2003
3-55
3. Status and Statistics
Table 3-12. Most Recent and Previous Cause Value Messages (3 of 6)
Message
Cause
No.
What It Indicates
What To Do
Invalid Transit
Network Selection
91
Incorrect format of transit
network identification.
Contact your service
representative.
Mandatory
Information Element
Missing
96
Required data is missing
from a mandatory
information element.
Contact your service
representative.
Message Not
Compatible with Call
State
101
Device sending this cause
has received a message
that is not permissible while
in the call state.
Contact your service
representative.
Msg Nonexistent
98
An unexpected message
was received in a state
other than Null.
Retry the call.
Msg Type
Nonexistent or
Unimplemented
97
Device sending this cause
has received a nonexistent
or not implemented
message type while in the
call state.
Contact your service
representative.
Device sending this cause
has received a status
message that indicates an
incompatible call state.
3-56
Network Out of
Order
38
Network is not functioning
correctly, and the condition
is expected to continue.
Contact your service
representative.
No Call Suspended
85
A call resume has been
issued, but no calls have
been suspended.
No action is needed.
No Circuit/Channel
Available
34
No circuit/channel is
currently available to handle
the call.
Wait and try again.
No Destination
Route
3
Network through which call
has been routed does not
serve the destination area
or device.
Contact your service
representative.
None
—
No causes have been
generated.
No action is needed.
Non-selected User
Clearing
26
User has not been awarded
the incoming call.
No action is needed.
No Route to Specify
Transit Network
2
The device sending or
receiving this cause does
not recognize the transit
network that the call is
being/has been routed
through.
1. Verify that the network
exists.
October 2003
2. Verify that the network
serves the device
sending the cause.
9000-A2-GB33-30
3. Status and Statistics
Table 3-12. Most Recent and Previous Cause Value Messages (4 of 6)
Cause
No.
What It Indicates
What To Do
Normal Call
Clearing
16
Call is being cleared
because either the caller or
receiver has requested that
it be cleared.
No action is needed.
Normal, Unspecified
31
Remote user has sent a
release message to the
network.
No action is needed.
Message
No other cause in the
normal class applies for this
normal event.
No User
Responding
18
Called device does not
respond to the call with an
alert or connect indication
within the prescribed period
of time.
Contact the network
provider if the cause
continues.
Internal network timers may
be a cause.
9000-A2-GB33-30
Number Changed
22
Called number is no longer
assigned.
Look in the diagnostic field
for the new number, then
change the phone number
in your ISDN link profile.
Only Restricted
Bearer Capability
Available
70
An unrestricted bearer
service has been
requested, but the device
sending the cause only
supports the restricted
version.
Arrange for the desired
capability.
Outgoing Calls
Barred
52
Network is using Call
Screening.
Contact the network
provider to turn Call
Screening off.
Pre-empted
45
Call has been pre-empted.
Contact the network
provider.
Protocol Error,
Unspecified
111
No other cause in the
protocol error class applies
for this protocol error event.
Contact your service
representative.
Quality of Service
Unavailable
49
Requested Quality of
Service requested cannot
be provided (e.g.,
throughput cannot be
supported).
No action is needed.
Recovery of Timer
Expired
102
Error-handling procedure
has been initiated as a
result of the expiration of a
timer.
Retry the call.
October 2003
3-57
3. Status and Statistics
Table 3-12. Most Recent and Previous Cause Value Messages (5 of 6)
Message
Cause
No.
What It Indicates
What To Do
Requested Channel
Not Available
44
Circuit or channel
requested cannot be
provided by the other side
of the interface.
Allow the DBM to
automatically call using the
alternate link if Auto Backup
is enabled, or manually
select an alternate path for
the call.
Requested Facility
Not Implemented
69
Supplemental service
requested is not supported
by this device.
No action is needed.
Requested Facility
Not Subscribed
50
The supplementary service
requested cannot be
provided by the network
until user completes
arrangement with its
supporting networks.
Arrange for the desired
capability.
Resource
Unavailable,
Unspecified
47
No other cause in the
resource unavailable class
applies for this resource
unavailable event.
No action is needed.
Response to
STATus ENQuiry
30
Status enquiry message
received, generating this
message.
No action is needed.
Service/Option Not
Implemented
79
No other cause in the
service or option not
available class applies for
this not implemented event.
No action is needed.
Service/Option
Unavailable,
Unspecified
63
No other cause in the
service or option not
available class applies for
this not available event.
Wait and try again.
Switching
Equipment
Congestion
42
Switching equipment
sending the cause is
experiencing heavy traffic.
Wait and try again.
Suspended Call
Exists, But Not Call
ID
83
A call resume has been
attempted, but no
suspended call exists for
this phone number.
1. Verify the number in the
Inbound Calling ID #
field for the suspended
call.
2. Reissue the Call
Resume command using
the correct number.
Temporary Failure
3-58
41
Network is not functioning
correctly, but the condition
is not expected to continue
for long.
October 2003
Wait and try again.
9000-A2-GB33-30
3. Status and Statistics
Table 3-12. Most Recent and Previous Cause Value Messages (6 of 6)
Message
Cause
No.
What It Indicates
What To Do
Unallocated Number 1
Destination requested
cannot be reached because
the Inbound Calling ID
number is not assigned or
allocated.
Assign the Inbound Calling
ID.
User Access
Information
Discarded
43
Network was unable to
deliver the access
information when trying to
establish the call.
No action is needed.
User Alerting, No
Answer
19
During call establishment,
an alerting was received but
a connection was not.
1. Verify that the remote
device is operational and
configured to answer.
2. Retry the call.
User Busy
9000-A2-GB33-30
17
Called number cannot
receive the call.
October 2003
Wait and try again.
3-59
3. Status and Statistics
IP Routing Table
The IP Routing Table shows all the routes configured in the iMarc unit.
Main Menu→Status→IP Routing Table
IP Routing Table Screen Example
main/status/ip_route
Device Name: Node A
9128-II
5/26/2000 23:32
Page 1 of 2
IP ROUTING TABLE
Destination
Mask
Gateway
Hop
Type Interface
TTL
135.001.001.000
135.001.002.111
135.001.220.000
135.001.221.000
135.001.220.000
135.001.222.111
135.001.222.113
135.001.002.111
135.001.002.111
135.001.002.111
255.255.255.000
FFF.FFF.FFF.FFF
255.255.255.00
255.255.255.000
255.255.255.000
255.255.255.000
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
135.026.001.254
135.026.001.254
135.042.001.254
135.042.001.254
135.042.001.254
135.026.001.254
135.026.001.254
135.026.001.254
135.026.001.254
135.026.001.254
1
1
1
1
1
1
1
1
1
1
Tmp PVCMgmt1001
NMS PVCMgmt1002
Loc Ethernet
Loc Modem
Loc COM
RIP Modem
RIP PVCMgmt1003
NMS PVCMgmt1004
NMS PVCMgmt1005
NMS CMgmt1006
130
130
999
999
999
30
30
2
48
21
-------------------------------------------------------------------------------Exit
ESC for previous menu
MainMenu
PgDn
PgUp
Refresh
The table is sorted by the Destination IP address, from the lowest number to the
highest. If no routes exist, the No Routes message appears instead of routing
information.
Table 3-13. IP Routing Table Values (1 of 2)
Column
What It Indicates
Destination
The Destination IP Address for the route: 001.000.000.000 –
223.255.255.255
Mask
The Destination Subnet Mask for the route:
„
„
„
3-60
000.000.000.000 – 255.255.255.255 for network routes
FFF.FFF.FFF.FFF for host routes
127 may appear as well. It is a reserved number.
Gateway
The Gateway IP Address for the route: 001.000.000.000 –
223.255.255.255
Hop
The number of hops in the route to the destination (1–15). If
16 appears, the route is in the process of being aged out.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-13. IP Routing Table Values (2 of 2)
Column
What It Indicates
Type
The method used to add the route to the table.
„
RIP: The route was discovered through Routing Information
Protocol.
The route remains until its TTL (Time to Live) expires, a better
route is provided via RIP, or there is a power reset.
„
„
Loc: The route was added due to the iMarc unit’s local
configuration; a Default IP Address or an SNMP Manager Initial
Route Destination have been configured.
The route remains until the unit’s configuration changes.
NMS: The route was added by a Network Management System
using SNMP (Simple Network Management Protocol).
The route remains until there is a power reset of the unit.
„
„
Interface
9000-A2-GB33-30
Tmp: The route was added as a temporary route in order to
respond to an IP packet that was received.
The route remains until its TTL expires or there is a power reset.
Specifies the interface to be used to reach the destination.
„
„
„
TTL
ICMP: The route was added because an ICMP (Internet Control
Management Protocol) redirect message was received from a
router indicating a better route to the destination. That is, a
datagram was sent to a router and the router is informing the
datagram source through an ICMP redirect message of a better
route.
COM: Communications port
PVCname: Name of the management PVC (e.g., PVCMgmt1001)
Internal: The interface to be used for software loopbacks or internal
device functions in order to reach the destination.
The Time to Live that was set for the route, in seconds: 1 – 999. If
999 appears, the route is a permanent one.
October 2003
3-61
3. Status and Statistics
Performance Statistics
Use the Performance Statistics menu to display statistical information for a
selected interface. Statistical information is useful when trying to determine the
severity and frequency or duration of a condition.
Main Menu→Status→Performance Statistics
Physical and link layer statistics (Layers 1 and 2) are collected on the port. The
following menu shows all the performance statistics that can be selected. The
actual selections available depend on the model, its features and interfaces, and
configuration settings.
Performance Statistics Menu
main/status/performance
Device Name: Node A
9xxx
11/26/2002 15:32
PERFORMANCE STATISTICS
Service Level Verification
DLCI
Frame Relay
ATM
VCC
ESF Line
DDS Line
T3 Line
xDSL Line
DBM Call
Ethernet
Clear All Statistics
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
3-62
October 2003
9000-A2-GB33-30
3. Status and Statistics
Clearing Performance Statistics
Performance statistics counters can be reset to the baseline when using a
directly-connected asynchronous terminal and your security Access Level is
Level-1. This feature is useful when troubleshooting problems.
Statistic counters are not actually cleared using this feature. True statistic counts
are always maintained so SLAs can be verified, and they can be viewed from an
SNMP NMS. However, since statistics can be cleared locally, the statistics viewed
via the menu-driven user interface may be different from those viewed from the
NMS.
Procedure
To clear all statistics:
Performance Statistics →Clear All Statistics
Procedure
To clear specific sets of statistics:
„
Use the ClrSLV&DLCIStats function key to reset the SLV and DLCI
performance statistic counters for the currently displayed DLCI from one of the
following screens:
Performance Statistics→Service Level Verification
Performance Statistics→DLCI
„
Use the ClrLinkStats function key to reset the frame relay link performance
statistics.
Performance Statistics→Frame Relay
„
Use the ClrNearStats or ClrFarStats function key to reset all near-end or all
far-end Extended SuperFrame (ESF) line performance statistics.
Performance Statistics→ESF Line
„
Use the ClrDBMStats function key to reset the DBM call performance
statistics.
Performance Statistics→DBM Call
„
Use the ClrStats function key to reset all Ethernet port performance statistics.
Performance Statistics→Ethernet
9000-A2-GB33-30
October 2003
3-63
3. Status and Statistics
Service Level Verification Performance Statistics
These statistics appear when Service Level Verification (SLV) is selected from the
Performance Statistics menu.
Main Menu →Status →Performance Statistics→Service Level Verification
They only appear for the network interface and only if DLCIs are multiplexed or IP
Enabled.
Information displayed on the SLV Performance Statistics screen depends on DLCI
type. See Table 3-14, SLV Performance Statistics for Multiplexed DLCI or
Table 3-15, SLV Performance Statistics for IP Enabled DLCI.
If service type is Frame Relay, you can select PrevDLCI or NextDLCI to view
statistics for the previous or next DLCI on the link. On the IP Enabled DLCI screen,
select PrevPath or NextPath to view statistics for the previous or next path
associated with the DLCI.
For standard or multiplexed DLCIs, the statistics collected by the unit depend upon
the device at the far end of the connection. If the far-end device is an iMarc SLV
unit, frame relay, latency, and FDR/DDR performance statistics are collected. The
Frame Relay Delivery Ratio is the number of delivered frames/offered frames; the
Data Delivery Ratio is the number of delivered octets/offered octets.
If the far-end device is a non-iMarc device, or an iMarc 9120 or 9620, only frame
relay statistics are collected.
Examples of the SLV Performance Statistics screens follow.
SLV Performance Statistics – Applications
main/status/performance/slv
Device Name: stvII a7 d223
Net1-FR1 SLV PERFORMANCE STATISTICS
DLCI: 670
Display: Applications
Name
Non-IPv4
Other-IPv4
COS:1234567
------x
PARADYNE 9126-IIAPL
09/03/2003 07:34
Scope: Circuit
Tx Packets
250507
30807
Tx Characters
17531258
12989714
Rx Packets
263114
35513
Rx Characters
21416038
12877880
------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
Refresh PrevDLCI
NextDLCI
ClrApplicationStats
Applications >
The Applications display option is available only on devices which have the SLM
with Application Monitoring feature set enabled.
3-64
October 2003
9000-A2-GB33-30
3. Status and Statistics
SLV Performance Statistics – Circuit Latency and Throughput
main/status/performance/slv
Device Name: stvII a7 d223
Net1-FR1 SLV PERFORMANCE STATISTICS
DLCI: 670
Display: Circuit Latency & Throughput
Far End Circuit:
Dropped SLV Responses:
Inbound Dropped Frames:
Within CIR:
Above CIR:
Between CIR&EIR:
Above EIR:
Latest RdTrip Latency(ms)[ 71]:
Avg RdTrip Latency(ms)[ 71]:
Max RdTrip Latency(ms)[
71]:
PARADYNE 9126-IIAPL
09/03/2003 07:26
Far End IP Addr:
670
0
0
0
0
0
0
18
18
010.109.091.006
Inbound Dropped Chars:
Within CIR:
Above CIR:
Between CIR&EIR:
Above EIR:
0
0
0
0
0
32
------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
Refresh PrevDLCI
NextDLCI
ClrSLV&DLCIStats
< Circuit Latency & Throughput.
SLV Performance Statistics – Path Latency
main/status/performance/slv
Device Name: stvII a7 d223
Net1-FR1 SLV PERFORMANCE STATISTICS
DLCI: 470
Display: Path Latency
Far End Circuit:
Far End Name:
Far End Type:
COS Name:
COS ID:
Last RdTrip(ms):
Min RdTrip(ms):
Avg RdTrip(ms):
Max RdTrip(ms):
Dropped SLV Rsp:
Far End IP Address: 010.109.070.004
470
cuba a4 d223
9623-APL
1_one
1
39
35
46
164
1
PARADYNE 9126-IIAPL
09/03/2003 07:37
2_two
2
36
35
90
826
0
3_three
3
36
36
40
97
0
Path Up Time:
SLM Poll Type:
COS Type Mismatches:
4_four
4*
37
36
93
893
0
5_five
5
41
36
78
638
0
12d 19:45:26
Initiator
0
6_six
6
50
37
39
50
0
default
7
60
38
96
873
0
------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
Refresh PrevDLCI
NextDLCI
ClrLatencyStats
< Path Latency, Path Throughput.
9000-A2-GB33-30
October 2003
3-65
3. Status and Statistics
Table 3-14. SLV Performance Statistics for Multiplexed DLCI (1 of 2)
Statistic
What It Indicates
link
All enabled individual and multilink parent frame relay links with
at least one multiplexed DLCI are displayed in the option list:
DSX-1
Net1-FR1
Net1
Port-n
DLCI: xxxx (atm link,
vpi, vci)
If Service Type is FrameRelay, all multiplexed DLCIs configured
on the specified link appear in the option list. If the DLCI is
configured on a VCC, the ATM link and VPI,VCI are displayed
with the DLCI.
Far End Circuit
Number of the multiplexed DLCI or VPI/VCI (Virtual Path
Identifier/Virtual Channel Identifier) at the other end of the
connection.
If the far-end circuit is a DLCI, the DLCI number (16–1007)
appears. If a VPI/VCI, the number is displayed as xx,yyy, xx
being the VPI number (0 –15) and yyy being the VCI number
(32–2047).
None appears if the unit has not communicated with the other
end.
Far End IP Addr
IP Address of the device at the other end of the multiplexed
DLCI connection.
None appears if the iMarc unit has not communicated with the
other end, or if the device at the other end of the multiplexed
DLCI does not have an IP Address configured.
Dropped SLV
Responses
The number of SLV inband sample messages sent for which a
response from the far-end device has not been received.
Inbound Dropped
Frames *
Total number of frames transmitted by the far-end device that
were dropped in transit.
The counts continue to increment until the maximum value is
reached (232 –2), then the count starts over.
The SLV Delivery Ratio option (see the iMarc SLV Configuration
Reference) must be enabled for these statistics to appear.
„
Above CIR*
„
„
Within CIR *
„
„
Between CIR&EIR *
„
The number of frames transmitted by the far-end device that
were above the committed information rate and were
dropped in transit.
The number of frames transmitted by the far-end device that
were within the committed information rate, but were dropped
in transit.
The number of frames transmitted by the far-end device that
were between the committed information rate and excess
information rate, and were dropped in transit.
* Only appears for iMarc units when the SLV Delivery Ratio option is enabled.
3-66
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-14. SLV Performance Statistics for Multiplexed DLCI (2 of 2)
Statistic
What It Indicates
„
„
Above EIR *
Inbound Dropped
Characters *
The number of frames transmitted by the far-end device that
were above the excess information rate and were dropped in
transit.
Total number of bytes transmitted by the far-end device that
were dropped in transit.
The counts continue to increment until the maximum value is
reached (232 –2), then the count starts over.
The SLV Delivery Ratio option (see the iMarc SLV Configuration
Reference,) must be enabled for these statistics to appear. NA
appears instead of a statistical count if FDR/DDR (Frame
Delivery Ratio/Data Delivery Ratio) information is not being
received from the far-end device.
„
Above CIR *
„
„
Within CIR *
„
„
Between CIR&EIR *
„
„
Above EIR*
„
Latest RdTrip Latency
The number of bytes transmitted by the far-end device that
were above the committed information rate and were
dropped in transit.
The number of bytes transmitted by the far-end device that
were within the committed information rate, but were dropped
in transit.
The number of bytes transmitted by the far-end device that
were between the committed information rate and excess
information rate, and were dropped in transit.
The number of bytes transmitted by the far-end device that
were above the excess information rate and were dropped in
transit.
Current round trip latency, measured in milliseconds, between
the iMarc unit and the device at the other end of the multiplexed
DLCI connection.
“--” appears if communication with the far-end device is not
successful.
Avg RdTrip Latency
Average round trip latency, measured in milliseconds, between
the iMarc unit and the device at the other end of the multiplexed
DLCI connection.
Average round trip latency is measured every SLV sampling
interval and the average is computed (using packets with the
configured SLV Packet Size (bytes), iMarc SLV Configuration
Reference) over the previous 15 samples. If SLV Packet Size is
changed, a new average is not available until a new sample has
been received.
“--” appears if communication with the far-end device over the
last 15 samples has not been successful.
Max RdTrip Latency
Same as average (Avg RdTrip Latency), but storing the
maximum value of latency over the previous 15 samples.
“--” appears if communication with the far-end device over the
last 15 samples has not been successful.
* Only appears for iMarc units when the SLV Delivery Ratio option is enabled.
9000-A2-GB33-30
October 2003
3-67
3. Status and Statistics
For an IP Enabled DLCI, statistics are shown for last, minimum, average, and
maximum round trips, and for dropped SLV responses, for each of the seven
classes of service.
Table 3-15. SLV Performance Statistics for IP Enabled DLCI (1 of 2)
Statistic
What It Indicates
link
All frame relay links with at least one IP Enabled DLCI are
displayed in the option list:
All enabled individual and multilink parent frame relay links with
at least one multiplexed DLCI are displayed in the option list:
DSX-1
Net1-FR1
Net1
Port-n
DLCI: xxxx (atm link,
vpi, vci)
If Service Type is FrameRelay, all IP enabled DLCIs configured
on the specified link appear in the option list. If the DLCI is
configured on a VCC, the ATM link and VPI,VCI are displayed
with the DLCI.
Far End IP Addr
IP Address of the device at the other end of the DLCI
connection.
None appears if the iMarc unit has not communicated with the
other end, or if the device at the other end of the DLCI does not
have an IP Address configured.
Path Up Time
The number of days, hours, minutes, and seconds since the last
transition of this DLCI from Inactive to Active.
Far End Circuit
Number of the DLCI at the other end of the connection.
None appears if the unit has not communicated with the other
end.
SLM Poll Type
The role played by the far-end iMarc in the collection of latency
and availability statistics.
Initiator – The far-end iMarc initiates the SLV packet used for
statistics collection.
Responder – The far-end iMarc returns the SLV packet sent by
the Initiator.
3-68
Far End Name
The system name configured for the far-end iMarc device,
obtained using its IP address. Unknown appears if the far end
device is not an iMarc or if no response has been received since
the last reset.
COS Type
Mismatches
The number of SLV packets received that indicate a mismatch
between the Class of Service definitions in the near-end and
far-end devices.
Far End Type
The model type of the far-end iMarc device, obtained using its IP
address. Unknown appears if the far end device is not an iMarc
or if no response has been received since the last reset.
COS Name
The names for different Classes of Service defined using the
Class of Service Definitions screen. See Configuring Class of
Service Definitions in the iMarc SLV Configuration Reference.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-15. SLV Performance Statistics for IP Enabled DLCI (2 of 2)
Statistic
What It Indicates
COS ID
The ID numbers (1–7) of the Class of Service definitions.
Last RdTrip
Current round trip latency, measured in milliseconds, between
the iMarc unit and the device at the other end of the DLCI
connection.
Unknown appears if communication with the far-end device is
not successful.
Min RdTrip
Minimum round trip latency measured over the last 15 samples
between the iMarc unit and the device at the other end of the
DLCI connection.
“--” appears if communication with the far-end device over the
last 15 samples has not been successful.
Avg RdTrip
Average round trip latency between the iMarc unit and the
device at the other end of the DLCI connection.
Average round trip latency is measured every SLV sampling
interval and the average is computed (using packets with the
configured SLV Packet Size (bytes), iMarc SLV Configuration
Reference) over the previous 15 samples. If SLV Packet Size is
changed, a new average is not available until a new sample has
been received.
“--” appears if communication with the far-end device over the
last 15 samples has not been successful.
Max RdTrip
Same as average (Avg RdTrip), but storing the maximum value
of latency over the previous 15 samples.
“--” appears if communication with the far-end device over the
last 15 samples has not been successful.
Dropped SLV
Responses
9000-A2-GB33-30
The number of SLV inband sample messages sent for which no
response from the far-end device has been received.
October 2003
3-69
3. Status and Statistics
DLCI Performance Statistics
These statistics appear when DLCI is selected from the Performance Statistics
menu.
Main Menu →Status →Performance Statistics→DLCI
Table 3-16. DLCI Performance Statistics (1 of 2)
Statistic
What It Indicates
link
All enabled individual and multilink parent frame relay links with
at least one DLCI are displayed in the option list:
DSX-1
Net1-FR1
Net1
Port-n
Rtr-S0
DLCI: xxxx (atm link,
vpi, vci)
All DLCIs configured on the specified link appear in the option
list. If the DLCI is configured on a VCC, the ATM link and
VPI,VCI are displayed with the DLCI.
DLCI Up Since *
Date and time that the DLCI was last declared Active after a
period of inactivity. Down is displayed if the DLCI is inactive.
If the DLCI was Down, this is the time that the DLCI recovered.
If the DLCI was never Down, this is the first time the unit
discovered that the DLCI was active in the network.
DLCI Up Time *
Days, hours, minutes, and seconds since the DLCI was last
declared Active after a period of inactivity. Down is displayed if
the DLCI is inactive.
If the DLCI was Down, this is the amount of time since the DLCI
recovered.
If the DLCI was never Down, this is the amount of time since the
unit discovered that the DLCI was active in the network.
Total Tx Frames/
Tx Octets
Total number of data frames and octets (8-bit bytes) transmitted
for the selected DLCI on the frame relay link.
„
Within CIR
„
„
Between CIR&EIR
„
„
Above EIR
„
„
With DE Set
„
The number of frames and octets sent by the far-end device
for on the selected DLCI of the frame relay link that were
within the committed information rate.
The number of frames and octets sent by the far-end device
on the selected DLCI of the frame relay link that were
between the committed information rate and excess
information rate.
The number of frames and octets sent by the far-end device
on the selected DLCI of the frame relay link that were above
the excess information rate.
The number of frames and octets sent on the selected DLCI
of the frame relay link with the discard eligible bit set.
* Only appears for the network interface.
3-70
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-16. DLCI Performance Statistics (2 of 2)
Statistic
What It Indicates
„
„
With BECN Set
The number of frames and octets sent on the selected DLCI
of the frame relay link with backward explicit congestion
notifications.
BECNs are sent to notify users of data traffic congestion in
the opposite direction of the frame carrying the BECN
indicator.
Total Rx Frames/
Rx Octets
Total number of data frames and octets (8-bit bytes) received for
the selected DLCI on the frame relay link.
„
Within CIR
„
„
Between CIR&EIR
„
„
Above EIR
„
„
With DE Set
„
„
With BECN Set
„
The number of frames and octets received on the selected
DLCI of the frame relay link that were within the committed
information rate.
The number of frames and octets received on the selected
DLCI of the frame relay link that were between the committed
information rate and excess information rate.
The number of frames and octets received on the selected
DLCI of the frame relay link that were above the excess
information rate.
The number of frames and octets received on the selected
DLCI of the frame relay link with the discard eligible bit set.
The number of frames and octets received on the selected
DLCI of the frame relay link with backward explicit congestion
notifications.
BECNs are sent to notify users of data traffic congestion in
the opposite direction of the frame carrying the BECN
indicator.
„
With FECN Set
„
The number of frames and octets received on the selected
DLCI of the frame relay link with forward explicit congestion
notifications.
The network sends FECNs to notify users of data traffic
congestion in the same direction of the frame carrying the
FECN indicator.
* Only appears for the network interface.
9000-A2-GB33-30
October 2003
3-71
3. Status and Statistics
Additional Performance Statistics for IP Enabled DLCI
If the selected DLCI is IP Enabled, the DLCI Performance Statistics screen has a
second page listing statistics by Class of Service. On the first DLCI Performance
Statistics page for an IP Enabled DLCI, PgUp and PgDn are shown as available
commands in the function keys area of the screen. Select PgUp or PgDn to display
the second page.
Table 3-17. Additional Performance Statistics for IP Enabled DLCI
Statistic
What It Indicates
Class of Svc Name
The names for different Classes of Service defined using the
Class of Service Definitions screen. See Configuring Class of
Service Definitions in the iMarc SLV Configuration Reference.
Class of Svc ID
The ID numbers (1–7) of the Class of Service definitions.
The following IP statistics are shown for:
„
„
„
„
3-72
The seven Classes of Service
Unknown COS – IP packets whose Type of Service values do not match those
defined for any Class of Service
Non-IP – Packets that were not IP Version 4
Total – The total for all packets
Tx Packets
The number of packets transmitted
Tx Octets
The number of octets in the packets transmitted
Rx Packets
The number of packets received
Rx Octets
The number of octets in the packets received
Rx Errors
The number of packets received in error
October 2003
9000-A2-GB33-30
3. Status and Statistics
Frame Relay Performance Statistics
The following statistics appear when Frame Relay is selected from the
Performance Statistics menu.
Main Menu →Status →Performance Statistics→Frame Relay
All counts continue to increment until the maximum value is reached (232 –2), then
the count starts over. The NextLink and PrevLink function keys only appear when
multiple frame relay links have been configured.
For iMarc units with an ISDN DBM:
All enabled multilink aggregate links are available for selection from the Frame
Relay Performance Statistics screen. The multilink aggregate link must be enabled
if statistics are to be collected for this frame relay link. When the frame relay link is
the multilink aggregate link, statistics for its related constituent links can be viewed.
To view the statistics for a multilink constituent link, select the ConstLinkStats
function key. All enabled multilink constituent links become available for selection.
Select the desired constituent link from the Multilink Constituent Link field.
The frame relay performance statistics collected for any frame relay link are
collected for multilink frame relay links, unless the link is a multilink aggregate link.
In this case, statistics for Frame Relay LMI and Frame Relay HDLC Errors are not
collected; these statistics are available for multilink constituent links only.
Table 3-18. Frame Relay Performance Statistics (1 of 3)
Statistic
What It Indicates
frame relay link
All enabled individual and multilink parent frame relay links are
displayed in the option list:
DSX-1
Net1-FR1
Net1
Port-n
Rtr-S0
Frame Relay Link
Frames Sent
The number of frames sent over the interface.
Frames Received
The number of frames received over the interface.
Characters Sent
The number of data octets (bytes) sent over the interface.
Characters Received
The number of data octets (bytes) received over the interface.
FECNs Received
The number of forward explicit congestion notifications received
over the interface.
The network sends FECNs to notify users of data traffic
congestion in the same direction of the frame carrying the FECN
indicator.
9000-A2-GB33-30
October 2003
3-73
3. Status and Statistics
Table 3-18. Frame Relay Performance Statistics (2 of 3)
Statistic
What It Indicates
BECNs Received
The number of backward explicit congestion notifications
received over the interface.
The network sends BECNs to notify users of data traffic
congestion in the opposite direction of the frame carrying the
BECN indicator.
Frame Relay Errors
Total Errors
The number of total frame relay errors, excluding LMI errors.
Short frames, long frames, invalid DLCIs, unknown DLCIs, and
unknown errors are included in this total.
Indicates that there may be a non-frame relay device on the
other end of the link, or the units at either the far end or both
ends of the link may be configured incorrectly.
Invalid Rx Frames
The number of invalid frames received over the Network or
Port-1 interface.
There is a non-frame relay device on the other end of the link.
Short Rx Frames
The number of frames received over the Network or Port-1
interface that were less than 5-octets (five 8-bit bytes) in length.
There may be a non-frame relay device on the other end of the
link.
Long Rx Frames
The number of frames received over the Network or Port-1
interface that were more than 8192-octets in length.
The device on the far end of the link may be configured
incorrectly.
Invalid DLCI
The number of frames received over the interface that were
addressed to DLCIs outside the valid range; that is, a number
less than 16 or greater than 1007.
The device on the far end of the circuit may have been
configured incorrectly, or the DLCIs configured for the iMarc unit
may not match the DLCIs supplied by the service provider.
Unknown DLCI
The number of frames received over the interface that were
addressed to unknown DLCIs.
The DLCI may not have been configured, or it has been
configured to be Inactive.
Indicates that the iMarc units or devices at both or either end of
the circuit have been configured incorrectly.
Unknown Error
The number of frames received over the interface that do not fall
into one of the other statistic categories.
Indicates that the error is not one that the unit can recognize.
3-74
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-18. Frame Relay Performance Statistics (3 of 3)
Statistic
What It Indicates
Frame Relay LMI
LMI Protocol
The LMI protocol configured for the frame relay link.
Normal condition.
Status Msg Received
The number of LMI status messages received over the interface.
Normal condition.
Total LMI Errors
The number of LMI errors. Reliability errors, protocol errors,
unknown report types, unknown information elements, and
sequence errors are included in this total.
Network problems.
Number of Inactives
The number of times the LMI has declared the frame relay link
Inactive.
Network problems.
Frame Relay HDLC Errors
Rx Total Errors
The number of receiver errors on the interface. The following are
included in this count:
„
„
„
Rx Total Discards
Rx Total Discards
Receive errors (non-octet aligned frames, frames with CRC
errors, and Rx Overruns)
The number of receiver discards on the interface. The following
are included in this count:
„
„
„
„
„
„
9000-A2-GB33-30
Receive invalid frames (short frames, long frames, invalid
DLCIs, unknown DLCIs, and unknown errors)
Resource errors
Rx Overruns
Frames received when the link was down
Inactive and disconnected DLCIs
Inactive destination DLCIs
Unknown EDLCIs
Rx Overruns
The number of receiver overruns (too many bits) on the
interface.
Rx Non-Octet Frames
The number of non-octet frames received on the interface.
Rx CRC Errors
The number of received CRC (cycle redundancy check) errors.
Tx Total Errors
The total number of transmit errors on the interface, including
transmits discards and transmit overruns.
Tx Total Discards
The total number of transmit discards on the interface, including
underrun flushes.
Tx Underruns
The number of transmitter underruns (too few bits) on the
interface.
October 2003
3-75
3. Status and Statistics
ATM Performance Statistics (9783, 9788)
Asynchronous Transfer Mode (ATM) statistics are available for Models 9783 and
9788 CSU/DSUs and Routers.
Main Menu →Status →Performance Statistics→ATM
The ATM link, Net1-ATM, must be enabled for these statistics to appear.
Table 3-19. ATM Performance Statistics (1 of 2)
Statistic
What It Indicates
AAL5 (ATM Adaption Layer)
Tx PDUs
Number of AAL5 Common Part Convergence Sublayer (CPCS)
Protocol Data Units (PDUs) passed to the lower layer for
transmission.
Rx PDUs
Number of AAL5 PDUs received and passed to a higher layer.
Tx Octets
Number of AAL5 octets (bytes) passed to the lower layer for
transmission.
Rx Octets
Number of AAL5 octets (bytes) received and passed to a higher
layer.
Errored Tx PDUs
Number of AAL5 PDUs that could not be transmitted due to
errors.
Errored Rx PDUs
Number of AAL5 CPCS PDUs received that contained errors.
OAM (Operations, Administration, and Maintenance)
Total Tx OAM Cells
Number of OAM cells transmitted.
Total Rx OAM Cells
Number of OAM cells received.
TC (Transmission Convergence) Sublayer
Total Tx Cells
Number of cells transmitted.
Total Rx Cells
Number of cells received.
Total Rx Cells
Dropped
Number of cells received and dropped due to errors.
Rx HEC Errors
Number of cells received with HEC field errors.
Unknown Rx Cells
Number of cells received and discarded during cell header
validation. These include cells with:
„
„
„
3-76
Unrecognized VPI/VCI values.
Invalid cell header patterns.
Undefined Payload Type Indicators.
Last Unknown
VPI,VCI
The VPI,VCI of the last cell discarded due to an unrecognized
VPI,VCI. If no such cells have been discarded, None appears.
OCD Events
Number of times OCD events have been detected (when seven
consecutive cells with HEC violations are detected).
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-19. ATM Performance Statistics (2 of 2)
Statistic
What It Indicates
Cell Delineation
State
Synchronization value (In Sync or Out of Sync) of the last cell
received.
VCC Performance Statistics (9783, 9788)
Virtual Channel Connection (VCC) statistics are available for models that support
ATM.
Main Menu →Status →Performance Statistics→VCC
The ATM link, Net1-ATM, must be enabled and have at least one VCC for these
statistics to appear.
Select a VPI,VCI. Format: VPI,VCI (Netn-FRn, DLCI)
„
VPI: 0–15,
VCI: 32–255
„
Netn-FRn: frame relay link
„
16–1007: DLCI number
Table 3-20. VCC Performance Statistics (1 of 2)
Statistic
What It Indicates
VCC (Virtual Channel Connection)
Tx Cells
Number of cells transmitted on the link for the VCC.
Rx Cells
Number of cells received on the link for the VCC.
Tx PDUs
Number of AAL5 Common Part Convergence Sublayer (CPCS)
Protocol Data Units (PDUs) received from a higher layer for
transmission.
Rx PDUs
Number of AAL5 PDUs received and passed to a higher layer.
Tx Octets
Number of AAL5 octets transmitted on the VCC.
Rx Octets
Number of AAL5 octets received on the VCC.
Errored Rx PDUs
Number of AAL5 PDUs received that contained errors. Errors
include CRC-32 errors, SAR timeout errors, and oversized errors.
OAM (Operations, Administration, and Maintenance)
9000-A2-GB33-30
Total Tx OAM Cells
Number of OAM cells transmitted on the VCC.
Total Rx OAM Cells
Number of OAM cells received on the VCC.
Tx Segment
Loopback Cells
Number of OAM segment loopback cells transmitted on the VCC.
Rx Segment
Loopback Cells
Number of OAM segment loopback cells received on the VCC.
October 2003
3-77
3. Status and Statistics
Table 3-20. VCC Performance Statistics (2 of 2)
3-78
Statistic
What It Indicates
Tx EndToEnd
Loopback Cells
Number of OAM end to end cells transmitted on the VCC.
Rx EndToEnd
Loopback Cells
Number of OAM end to end cells received on the VCC.
Tx AIS Cells
Number of OAM F5 Alarm Indication Signal (AIS) cells transmitted
on the VCC.
Rx AIS Cells
Number of OAM F5 AIS cells received on the VCC.
Tx RDI Cells
Number of OAM F5 Remote Defect Indication (RDI) cells
transmitted on the VCC.
Rx RDI Cells
Number of OAM F5 RDI cells received on the VCC.
October 2003
9000-A2-GB33-30
3. Status and Statistics
ESF Line Performance Statistics (9123, 9126, 9128)
These statistics appear when ESF Line is selected from the Performance Statistics
menu for the network interface.
Main Menu →Status →Performance Statistics→ESF Line
Only seven T1 network statistical intervals appear on the screen at any one time.
You can choose which intervals to display on your screen by entering:
„
Interval Number (01–96)
– or –
„
Time (Hours and Minutes)
NOTES:
— Interval 01 is the interval occurring just prior to the current one;
Interval 02 is 2 intervals prior to the current one, etc.
— Selecting a specific time is useful when the approximate time at which a
specific event occurred is known.
Edit any of the interval or time fields on lines 10, 13, or 16. When Enter is pressed,
the values change to the selected range.
9000-A2-GB33-30
To select intervals . . .
You must enter an interval or time on . . .
Occurring on and before a
selected interval or time
Line 10. The display will include the selected interval plus
the 6 intervals recorded before it.
Bracketing a selected
interval or time
Line 13. The display will include the selected interval plus
the 3 intervals recorded before it and the 3 intervals
recorded after it.
Occurring on and after a
selected interval or time
Line 16. The display will include the selected interval plus
the 6 intervals recorded after it.
October 2003
3-79
3. Status and Statistics
ESF Line Performance Statistics Screen Example
main/status/performance/esf
9128-II
Device Name: Node A
05/26/2000 23:32
Network 1 ESF LINE PERFORMANCE STATISTICS
Current Interval Timer
ESF Error Events
Near=123
Far = 124
Near = 15
Far = 12
---ES-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
--UAS-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
--SES-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
--BES-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Worst Interval:
24 24
Near Tot(valid 96): 00010
Far Tot(valid 96): 00010
14 14
00000
00000
14 14
00000
00000
09 09
00000
00000
Current:
Int 01:
Int 02:
Int 03:
Int 04:
Int 05:
Int 06:
Int 07:
Line 10
Line 13
Line 16
Time
10:37
10:35
10:20
10:05
09:50
09:35
09:20
09:05
--CSS-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
18
16
002
002
-LOFC-Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
44
44
003
003
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
PgDn
PgUp
ClrFarStats
ClrNearStats
Refresh
Select: 01, 02, 03, 04, 05, 06, 07, 08, 09 ...
For the ESF line performance statistics, the following performance statistics are
kept for each 15-minute interval over the past 24-hour period. A Near set and a Far
set are kept for each statistic. The Far set is based on information kept by the unit
at the other end of the local loop and is only available when ANSI performance
report messages are enabled in the unit.
Summary information that appears near the top of the screen includes:
3-80
„
Near/Far Current Interval Timer – Contains the number of seconds that have
elapsed in the current 15-minute interval for the near or far information, which
can show a value up to 900 seconds.
„
Near/Far ESF Error Events – Maintains a count of ESF error events, as
specified by AT&T TR 54016, which counts CRC and OOF events. A
maximum of 65,535 error events can be counted. Once 65535 is reached, it
stays at that number until the network issues a reset command.
October 2003
9000-A2-GB33-30
3. Status and Statistics
The following performance statistics are collected for ESF line conditions.
Table 3-21. ESF Line Condition Performance Statistics
Statistic
What It Indicates
Errored Seconds (ES)
Any second with one or more ESF Error events.
Unavailable Seconds
(UAS)
Any second in which service is unavailable. Begins incrementing
at the onset of 10 consecutive seconds of severely errored
seconds (SES), and stops incrementing after 10 consecutive
seconds of no SESs.
Severely Errored
Seconds (SES)
Any second with 320 or more CRC errors or one or more Out Of
Frame (OOF) events.
Bursty Errored
Seconds (BES)
Any second with more than one, but less than 320 CRC errors.
Controlled Slip
Seconds (CSS)
Any second with one or more controlled slips (a replication or
deletion of a DS1 frame by the receiving device). This is
collected for network performance statistics only.
Loss of Frame Count
(LOFC)
The number of Loss of Frame conditions.
Worst Interval
The largest number of seconds for either ES, UAS, SES, BES,
or CSS, or the greatest Loss of Frame Count (LOFC).
If more than one interval contains the same worst value, then the
oldest interval is displayed.
9000-A2-GB33-30
October 2003
3-81
3. Status and Statistics
DDS Line Performance Statistics (9623, 9626)
In addition to the statistics collected for all interfaces, these additional network line
statistics appear when DDS Line is selected from the Performance Statistics
menu.
Main Menu→Status→Performance Statistics→DDS Line
Table 3-22. DDS Line Performance Statistics
Statistic
What It Indicates
No Signal Count
Number of times a No Signal (NS) condition has occurred.
Out of Service Count
Number of times an Out-of-Service (OOS) condition has
occurred.
Out of Frame Count
Number of times an Out-of-Frame (OOF) condition has
occurred.
Excessive BPV Count
Number of times an excessive bipolar violation (BPV) condition
has occurred. This is a count of BPVs that qualify as being
excessive.
The count is incremented when at least one invalid BPV occurs
every 20 ms over a 2-second period.
BPV Count*
Number of errors received when a BPV condition has occurred.
This is a total count of invalid BPV errors.
* Elapsed time is also shown for all statistics except the BPV Count in the
hours:minutes:seconds format. This is the total amount of time that the iMarc unit
has experienced the condition since the unit’s last power cycle.
3-82
October 2003
9000-A2-GB33-30
3. Status and Statistics
T3 Network Line Performance Statistics (9520, 9520-ILM)
These statistics appear when T3 Network Line is selected from the Performance
Statistics menu.
Main Menu→ Status→ Performance Statistics → T3 Network Line
Only seven statistical intervals appear on the screen at any one time. You can
choose which intervals to display on your screen by entering:
„
Interval Number (01–96). Interval 01 is the most recent complete 15-minute
interval; intervals 02–96 are the preceding 15-minute intervals.
– or –
„
Time (Hours and Minutes). Selecting a specific time is useful when the
approximate time at which a specific event occurred is known.
Edit any of the interval or time fields on lines 10, 13, or 16. When Enter is pressed,
the values change to the selected range.
To select intervals . . .
You must enter an interval or time on . . .
Occurring on and before a
selected interval or time
Line 10. The display will include the selected interval plus
the 6 intervals recorded before it.
Bracketing a selected
interval or time
Line 13. The display will include the selected interval plus
the 3 intervals recorded before it and the 3 intervals
recorded after it.
Occurring on and after a
selected interval or time
Line 16. The display will include the selected interval plus
the 6 intervals recorded after it.
T3 Network Line Performance Statistics Screen Example
main/status/performance/t3
Device Name: Node A
Network 1 T3 LINE PERFORMANCE STATISTICS
9520
05/13/2000 05:08
Current Interval Timer = 75
Line 10
Line 13
Line 16
Current:
Int 01:
Int 02:
Int 03:
Int 04:
Int 05:
Int 06:
Int 07:
Time
10:37
10:35
10:20
10:05
09:50
09:35
09:20
09:05
PES PSES SEFS
000 000 000
000 000 000
000 000 000
000 000 000
000 000 000
000 000 000
000 000 000
000 000 000
Tot(valid 96):00000
Worst Interval:
UAS
000
000
000
000
000
000
000
000
LCV
0000000
0000000
0000000
0000000
0000000
0000000
0000000
0000000
PCV
0000000
0000000
0000000
0000000
0000000
0000000
0000000
0000000
LES
000
000
000
000
000
000
000
000
CCV
0000000
0000000
0000000
0000000
0000000
0000000
0000000
0000000
CES CSES
000 000
000 000
000 000
000 000
000 000
000 000
000 000
000 000
Status
Y
none
none
none
none
none
none
none
00000
00000
24
24
00000000
0000
0000
00000
00000000
00000000
00000
14
14
14
14 09
14 24
14
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
PgDn
PgUp
ClrStats
Refresh
Select: 01, 02, 03, 04, 05, 06, 07, 08, 09 ...
9000-A2-GB33-30
October 2003
3-83
3. Status and Statistics
For the T3 network line performance statistics, the following performance statistics
are kept for each 15-minute interval over the past 24-hour period.
Table 3-23. T3 Network Line Performance Statistics (1 of 2)
3-84
Field or Statistic
What It Indicates
Current Interval Timer
The number of seconds that have elapsed in the current
15-minute interval.
PES
The number of P-bit Errored Seconds in the interval. A PES is a
second during which one or more P-bit Coding Violations
(PCVs) or one or more Out Of Frame (OOF) defects or an
incoming Alarm Indication Signal (AIS) is detected.
PSES
The number of P-bit Severely Errored Seconds in the interval. A
PSES is a second during which 44 or more PCVs or one or
more OOF defects or an incoming AIS is detected.
SEFS
The number of Severely Errored Frame Seconds in the interval.
A SEFS is a second during which one or more OOF defects or
an incoming AIS is detected.
UAS
The number of UnAvailable Seconds in the interval. The DS3
interface is deemed unavailable after 10 contiguous PSESs, or
when Loss Of Signal (LOS), OOF, or AIS exists for two or more
seconds. UAS is the only DS3 counter incremented while the
interface is deemed unavailable.
LCV
The number of Line Coding Violations in the interval. LVCs are
BiPolar Violations (BPVs) and EXcessive Zeros (EXZs) errors.
PCV
The number of P-bit Coding Violations in the interval. A PCV is
declared when the P-bit code on the DS3 M-frame does not
equal the code calculated locally.
LES
The number of Line Errored Seconds in the interval. An LES is
a second during which one or more Coding Violations (CVs) or
LOSs occurred.
CCV
The number of C-bit Coding Violations in the interval. A CCV is
a CP-bit parity error.
CES
The number of C-bit Errored Seconds in the interval. A CES is a
second during which one or more CCVs or one or more OOF
defects or an incoming AIS is detected.
CSES
The number of C-bit Severely Errored Seconds in the interval. A
CSES is a second during which 44 or more CCVs or one or
more OOF defects or an incoming AIS is detected.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Table 3-23. T3 Network Line Performance Statistics (2 of 2)
Field or Statistic
What It Indicates
Status
The contents of the Status Events Register, which maintains a
history of events which have occurred at least once during an
interval. One or more of:
Y – A Yellow Alarm signal was detected during the interval.
S – A Loss Of Signal occurred during the interval.
O – An Out Of Frame defect occurred during the interval.
F – A Loss Of Frame occurred during the interval.
A – An Alarm Indication Signal was received during the interval.
none – No error event was stored in the Status Events Register.
9000-A2-GB33-30
Tot (valid nn)
The number of valid intervals in the previous 24 hours. If a
power cycle has occurred within that time, 96 intervals are not
available.
Worst Interval
The interval number during which the largest number of each
kind of error was detected.
October 2003
3-85
3. Status and Statistics
SHDSL Line Performance Statistics (9788)
Access SHDSL statistics from the Performance Statistics menu.
Main Menu →Status →Performance Statistics→xDSL Line
These statistics account for all traffic on the DSL line.
Table 3-24. SHDSL Line Performance Statistics
Statistic
What It Indicates
CRC Anomalies (CV) The number of CRC errors, also known as Code Violations (CVs),
that occurred during the accumulation period.
3-86
Errored Seconds
(ES)
Number of one-second intervals during which at least one CRC
anomaly or LOSW defect is declared.
Severely Errored
Seconds (SES)
Number of one-second intervals during which at least 50 CRC
anomalies are declared or at least one LOSW defect is declared.
LOSW Seconds
(LOSWS)
Number of one-second intervals during which at least one SHDSL
Loss of Synchronization Word (LOSW) defects is declared.
Unavailable Seconds
(UAS)
Number of one-second intervals during which the SHDSL line is
unavailable. The line is declared unavailable after 10 contiguous
Severely Errored Seconds, and declared available after
10 contiguous seconds with no SES.
October 2003
9000-A2-GB33-30
3. Status and Statistics
DBM Call Performance Statistics
When an ISDN DBM is installed, these statistics are available for ISDN calls and
call attempts.
You can clear these statistics by selecting the ClrDBMStats function key, or you
can clear all performance statistics for the system.
Main Menu→Status→Performance Statistics→Clear All Statistics
Clearing these statistics will not affect performance statistics stored in user history
for the system. The statistics are only cleared locally.
Table 3-25. DBM Call Performance Statistics
9000-A2-GB33-30
Statistic
What It Indicates
Total Call Attempts
Number of call attempts made by the DBM.
Total Calls Originated
Number of successful calls made by the DBM.
Total Calls Answered
Number of successful calls answered by the DBM.
Total Calls Rejected (Security)
Number of calls rejected by the DBM due to security.
Total Calls Rejected (Other)
Number of calls rejected by the DBM due to reasons
other than security, like incoming voice call requests.
Average Call Duration (mins)
Average amount of time, in minutes, that successful calls
take.
Longest Call Duration (mins)
Amount of time spent, in minutes, during the longest
successful call.
Total Call Duration (mins)
Sum of all successful calls in minutes.
October 2003
3-87
3. Status and Statistics
Ethernet Performance Statistics
The following statistics appear when Ethernet is selected from the Performance
Statistics menu.
Main Menu →Status →Performance Statistics→Ethernet
Table 3-26. Ethernet Performance Statistics
Statistic
What It Indicates
Port Rate (Mbps)
The operating rate as detected on the Ethernet port. One of the
following may appear for this statistic:
„
„
„
Duplex
10 Mbps or 100 Mbps – The Ethernet port is operating at this
rate.
Disabled – The Ethernet port has been disabled.
The duplex mode detected on the Ethernet port. One of the
following may appear for this statistic:
„
„
„
„
Disconnected – The line is not connected.
Full – The Ethernet port is operating in full duplex mode
(4-wire).
Half – The Ethernet port is operating in half duplex mode
(2-wire).
Disabled – The Ethernet port has been disabled.
Frames Transmitted
The number of successfully transmitted frames on the port.
Frames Received
The number of frames received on the port.
Errored Frames
The number of errors detected on the port. Possible errors
include:
„
„
„
„
„
3-88
Disconnected – The line is not connected.
Internal transmit and receive errors
Transmitter and receiver overruns
Receive checksum errors
Alignment errors
Long frames
Excessive Collisions
The number of failed frame transmissions due to excessive
collisions.
Carrier Sense Errors
The number of times the carrier sense condition was lost, or was
never asserted, during frame transmissions.
Deferred
Transmissions
The number of delayed first transmissions due to the line being
busy.
October 2003
9000-A2-GB33-30
3. Status and Statistics
Trap Event Log
The Trap Event Log displays all traps stored in the SNMP trap event log. The
following log example describes the alarm conditions that will generate an SNMP
trap for a physical interface, and for the frame relay LMIs and DLCIs. These alarm
conditions also generate Health and Status messages seen on the Health and
Status Messages on page 3-32.
Main Menu→Status →Trap Event Log
Trap Event Log Screen Example
main/status/event_log
Device Name: Node A
9128-II
12/11/2002 09:13
TRAP EVENT LOG
Total Trap Events:
Time of Day
12/11/02 08:22:41
12/11/02 08:21:48
12/11/02 08:21:48
12/11/02 08:21:48
12/11/02 08:21:46
12/11/02 08:21:46
12/11/02 08:21:46
12/11/02 08:21:46
12/11/02 08:21:46
12/11/02 08:21:46
12/11/02 08:21:46
11
Event
Device configuration change.
Ethernet up.
Sync Data Port S01P1 link up.
Network T1 link up.
Sync Data Port S01P1 link down.
Network T1 link down.
RMON database reset to defaults.
Ethernet link down.
Network T1 up.
Network T1 down due to OOF.
Unit Reset.
-------------------------------------------------------------------------------Exit
ESC for previous menu
MainMenu
PgUp
PgDn
Refresh
Up to 12 trap events can be displayed on a screen, the most current first. Page
down (PgDn) to view less current trap events. When no trap events have been
logged, No Events in Log. appears in the Event column.
ASCII trap strings used to describe trap events are provided in the tables
contained in Standards Compliance for SNMP Traps in the iMarc SLV SNMP
Reference.
9000-A2-GB33-30
October 2003
3-89
3. Status and Statistics
3-90
October 2003
9000-A2-GB33-30
Operation and Maintenance
4
This chapter includes miscellaneous operating and maintenance procedures,
including:
„
Modem Operation on page 4-2
— Activating the Modem PassThru Feature
— Canceling Modem PassThru Operation
— Manually Disconnecting the Modem
— Verifying Modem Operation
„
ISDN DBM Operation on page 4-4
— Forcing Backup (Disruptive)
— Placing a Test Call (Nondisruptive)
— Verifying ISDN Lines
— Verifying That Backup Can Take Place
„
FTP File Transfers on page 4-7
— Upgrading System Software
— Upgrading ISDN BRI DBM Software
— Determining Whether a Download Is Completed
— Changing Software
— Changing Software
„
Turning Off the System Alarm Relay on page 4-13
„
Hardware Maintenance for Models 9520, 9520-ILM, and 9820-45M on
page 4-14
— Cleaning the Front Panel Assembly
— Replacing the Front Panel Assembly
— Replacing a Power Module
9000-A2-GB33-30
October 2003
4-1
4. Operation and Maintenance
Modem Operation
This section includes the following:
„
Activating the Modem PassThru Feature
„
Canceling Modem PassThru Operationn
„
Manually Disconnecting the Modem
„
Verifying Modem Operation
See Setting Up the Modem in the iMarc SLV Configuration Reference for
additional information.
Activating the Modem PassThru Feature
Access to the router’s VT100-compatible user interface is provided through the
iMarc unit’s Modem PassThru feature, also known as Router Assist. A dial-up
connection to the iMarc unit is used to access the router when the unit is set up for
this use. See Setting Up to Use the Modem PassThru Feature in the iMarc SLV
Configuration Reference to configure the unit for Modem PassThru operation.
Once the unit is set up to use this feature, each time access to the router is
needed, the feature is activated from the Control menu.
Main Menu→Control→Enable Modem PassThru to COM
When this feature is active, a logical connection between the unit’s modem and
COM ports is made, and data received over the modem port is transmitted out the
COM port to the router’s AUX or console port, and data received from the router
on the COM port is transmitted out the modem port. While Modem PassThru is
active, normal access to the iMarc unit through either its modem or COM port is
suspended.
When an escape sequence (minus, minus, minus, with a minimum of 50 ms
between each) is detected, the iMarc unit switches back to normal user interface
operation.
Canceling Modem PassThru Operation
When Modem PassThru is active, but access to the iMarc unit’s menu-driven user
interface is needed, Modem PassThru can be cancelled from the Control menu.
Main Menu→Control→Disable Modem PassThru to COM
4-2
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
Manually Disconnecting the Modem
If Trap Disconnect is disabled, a modem connection remains until it is manually
disconnected. Select Disconnect Modem from the Control menu.
Main Menu→Control→Disconnect Modem
Respond yes to the Are you sure? prompt.
Verifying Modem Operation
Procedure
If Port Use is set to Terminal (dial-in access):
1. Dial the modem’s phone number using a remote VT100-compatible
asynchronous terminal or PC.
2. Verify that the Main Menu appears.
Procedure
If Port Use is set to Net Link (SNMP, Telnet, FTP, and trap dial-out):
1. Dial the modem’s phone number using a PC running PPP or SLIP link
protocol.
2. From the PC, run an IP Ping test to the modem interface.
If your results using either method are unsuccessful, make sure both ends of the
modem cable are properly seated and secured. Then, verify that the modem was
configured correctly (see Setting Up the Modem in the iMarc SLV Configuration
Reference).
9000-A2-GB33-30
October 2003
4-3
4. Operation and Maintenance
ISDN DBM Operation
The following sections only apply to units with an ISDN DBM:
„
Forcing Backup (Disruptive)
„
Placing a Test Call (Nondisruptive)
„
Verifying ISDN Lines
„
Verifying That Backup Can Take Place
Forcing Backup (Disruptive)
Use this procedure to force backup when network maintenance is planned, when
equipment problems are reported, or when testing the backup path – whenever
data needs to be forced from the primary destination interface to the alternate
destination, typically from the T1 network to the ISDN.
Procedure
1. Make sure the ISDN Link Profiles are set up correctly, Auto Backup is enabled,
and the ISDN interface is enabled (see Setting Up Dial Backup in the iMarc
SLV Configuration Reference).
2. Have someone at the far end disconnect the network cable to initiate backup.
3. Verify that backup is taking place.
See Verifying That Backup Can Take Place on page 4-6.
NOTE:
When an alarm requiring backup is received, backup can be manually
controlled by enabling or disabling the Auto Backup option (see Step 2).
4. Have the far-end network cable reconnected to return to standard operation.
4-4
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
Placing a Test Call (Nondisruptive)
Use this procedure to test the ISDN path to each remote site. This procedure will
not put the system into backup.
Procedure
1. Make sure the ISDN Link Profiles and DLCIs are set up correctly for the DBMs
at each end (see Modifying ISDN Link Profiles in the iMarc SLV Configuration
Reference.
Main Menu→Configuration→ISDN→Link Profiles
Main Menu→Configuration→ISDN→DLCI Records
2. Place a Test Call from one of the devices.
Main Menu→Test→ISDN Call/PVC Tests
— Select the link to be tested.
— Start a Test Call. The Status should be Active.
If the Result is . . .
Then . . .
Frame Relay Link Up
The call was successful.
Frame Relay Link Down
The call was not successful. Verify the configuration and
Link Status in the ISDN Link Profile.
— Select Stop to end the Test Call.
Use this procedure to test the ISDN path to each remote site. This procedure will
not put the unit into backup.
9000-A2-GB33-30
October 2003
4-5
4. Operation and Maintenance
Verifying ISDN Lines
Use either of the following methods to verify operation of the ISDN lines.
„
Check the status of the DBM interface:
Main Menu→Status→DBM Interface Status
Line Status should display Active. If an invalid (Inv) status appears (e.g., Inv
SPID for an ISDN BRI DBM) in the Line Status field, verify that you entered
ISDN physical options correctly.
„
Check the status of the unit:
Main Menu→Status→System and Test Status→
Health and Status column
System Operational should appear.
If ISDN Network Failed appears, check that both ends of the ISDN cable
are seated properly for a good physical connection. If that does not clear the
message, verify that you entered ISDN physical option information correctly,
then contact the network service provider.
See DBM Interface Status in Chapter 3, Status and Statistics, and Table 3-6,
Health and Status Messages, in Chapter 3, Status and Statistics, for additional
status information.
Verifying That Backup Can Take Place
As each remote site is installed, verify its backup operation by unplugging the
network cable so the system is forced into backup.
„
Verify the ISDN lines by checking the DBM Interface Status.
Main Menu→Status→DBM Interface Status
Line Status should be Active. If an invalid (Inv) status (e.g., Inv SPID) is
displayed, verify that you entered ISDN physical options correctly.
„
Check backup setup and that data can be passed between DBMs.
„
Reconnect the network cable.
See Table 3-6, Health and Status Messages, in Chapter 3, Status and Statistics,
Viewing LEDs and Control Leads in Chapter 3, Status and Statistics, and DBM
Call Performance Statistics in Chapter 3, Status and Statistics, for additional
information.
4-6
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
FTP File Transfers
The iMarc unit supports a standard File Transfer Protocol (FTP) server over
Transmission Control Protocol (TCP). A complete binary image of the
configuration files can be copied to a host to provide a backup. To use this feature,
the unit must be configured to support Telnet and FTP Sessions.
Using this feature, you can transfer configuration files to/from an iMarc node,
program files to an iMarc node, and User History data from an iMarc node through
a user data port or the network interface using a management PVC, or through the
COM port.
Be aware of the following rules when doing a file transfer:
„
You must have Access Level 1 permission to use the put and get commands,
and to access the LMI packet capture data. However, you can retrieve the
data file for the user history reports regardless of access level.
„
You cannot put a configuration file to the factory.cfg or current.cfg files under
the system directory. Configuration files should be put to a customer file
(cust1.cfg or cust2.cfg), then loaded into the downloaded unit’s Current
Configuration via the menu-driven user interface.
„
You can only put a NAM program file (nam.ocd) into an iMarc unit. You cannot
get a program file from the iMarc unit to a host.
„
Before putting a download file, you must use the bin binary command to place
the data connection in binary transfer mode.
„
When transferring SLV user history information to the NMS, you can only get a
uhbcfull.dat file. It is recommended that you use the NMS application to get
this information (see Transferring Collected Data on page 4-12).
„
A data file (such as uhbcfull.dat or lmitrace.syc) cannot be put into an iMarc
node.
„
LMI packet capture data (lmitrace.syc) is not readable when the LMI Packet
Capture Utility is active.
iMarc SLV units provide an additional feature that allows new software to be
downloaded in the background, using the selected bandwidth and without
interfering with normal operation. Downloads can be performed quickly, using the
full line speed, or at a slower rate over an extended period of time.
You initiate an FTP session to an iMarc node in the same way as you would initiate
an FTP to any other IP-addressable device.
NOTE:
Loading a configuration with many DLCIs from a unit’s Customer
Configuration 1 or 2 option area into its Current Configuration area may take
time. Allow a minute or more for the downloaded file to be put into the unit’s
currently active configuration.
9000-A2-GB33-30
October 2003
4-7
4. Operation and Maintenance
Procedure
To initiate an FTP session:
1. Start the FTP client program on your host. For example, on a UNIX host,
type ftp, followed by the iMarc unit’s IP address.
2. If a login and password are required (see Creating a Login in Chapter 2,
Security and Logins), you are prompted to enter them. If not, press Enter.
The FTP prompt appears.
The starting directory is the root directory (/). Use standard FTP commands
during the FTP session, as well as the following remote FTP commands.
4-8
Command
Definition
cd directory
Change the current directory on the iMarc node to the specified
directory.
dir [directory]
Print a listing of the directory contents in the specified directory.
If no directory is specified, the current one is used.
get file1 [file2]
Copy a file from the remote directory of the iMarc node to the
local directory on the host (for configuration files only).
remotehelp
[command]
Print the meaning of the command. If no argument is given, a
list of all known commands is printed.
ls [directory]
Print an abbreviated list of the specified directory’s contents. If
no directory is specified, the current one is used.
put file1 [file2]
Copy file1 from a local directory on the host to file 2 in the
current directory of the iMarc node. If file2 is not specified, the
file will be named file1 on the iMarc node.
recv file1 [file 2]
Same as a get.
send file1 [file 2]
Same as a put.
pwd
Print the name of the current directory of the iMarc unit node.
bin
Places the FTP session in binary-transfer mode.
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
Upgrading System Software
If you need to upgrade the iMarc unit’s program code, you must transfer the
upgrade of the nam.ocd file in the system memory directory using the put
command.
NOTE:
Upgrades can be performed through the network using a Management PVC,
or through the COM port if Port Use is set to Net Link (see the iMarc SLV
Configuration Reference).
Procedure
To download software:
1. Initiate an FTP session to the device that you are upgrading.
2. Type bin to enter binary transfer mode.
3. Type hash to enter hash mode if you want to monitor the progress of the
upgrade, provided this function is supported by your equipment.
4. Type cd system to change to the system directory.
5. Perform a put of Rxxxxxx.ocd (xxxxxx being the software release number) to
the nam.ocd file to start the upgrade.
If the message displayed is . . .
Then . . .
nam.ocd: File Transfer Complete
The download was successful. The file is loaded
into system memory.
nam.ocd: File Transfer Failed –
Invalid file
The file is not valid for this iMarc unit.
A different Rxxxxxx.ocd file will need to be
downloaded. Repeat the step or end the FTP
session.
NOTE:
During the download, a series of hash marks (#) appear. When the hash
marks stop appearing, there is a pause of about 30 seconds before the
nam.ocd: File Transfer Complete message appears. Please be
patient. Do not exit from FTP at this time.
See Changing Software on page 4-11 to activate the newly downloaded
software.
9000-A2-GB33-30
October 2003
4-9
4. Operation and Maintenance
Upgrading ISDN BRI DBM Software
A separate download to update PRI DBM functionality is not necessary; a PRI
upgrade is incorporated in the unit’s program code. However, if the iMarc unit has
a BRI DBM, the program code must be upgraded separately.
To upgrade an iMarc unit’s BRI DBM program code, you must transfer the
dbmprog.ocd file in the Dial Backup Module directory using the put command.
Procedure
To perform a BRI DBM upgrade:
1. Initiate an FTP session to the device that you are upgrading.
2. Type bin to enter binary transfer mode.
3. Type cd dbm to change to the Dial Backup Module directory.
NOTE:
If the iMarc unit is not equipped with a DBM or the DBM does not contain
any downloadable software, the message dbm: no such file or
directory appears.
4. Perform a put of Rxxxxxx.ocd (xxxxxx being the software release number) to
the dbmprog.ocd file to start the upgrade.
If the message displayed is . . .
Then . . .
DBM Download Required
Errors were detected during the DBM
download.
The dbmprog.ocd file will need to be
downloaded again.
dbmprog.ocd: File Transfer Complete The download was successful.
dbmprog.ocd: File Transfer Failed
The download was not successful.
Possible cause: A bad or invalid file, or the
wrong checksum.
A different dbmprog.ocd file will need to be
downloaded for the DBM to become
operational. Repeat the step or end the FTP
session.
5. Close the FTP session.
6. Verify that the new software release was successfully installed as the DBM
Software Revision.
Main Menu→Status→Identity
4-10
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
Determining Whether a Download Is Completed
To see whether a download has completed, check the Identity screen.
Main Menu→Status→Identity
Check Alternate Software Rev. under the NAM Identity column.
„
If a software revision number appears, the file transfer is complete.
„
If In Progress appears, the file is still being transferred.
„
If Invalid appears, no download has occurred or the download was not
successful.
Changing Software
Once a software upgrade is downloaded, it needs to be activated. When activated,
the unit resets, then executes the downloaded software. With this feature, you
control when the upgrade software is implemented.
Procedure
To switch to the new software:
1. Go to the Control menu, and select Select Software Release.
Main Menu→Control→Select Software Release
The currently loaded software version and the new release that was just
transferred are shown.
If the download failed, Invalid appears in the Alternate Release field
instead of the new release number. Repeat the procedure Upgrading System
Software if this occurs.
2. Select Switch&Reset.
3. Enter Yes to the Are you sure? prompt. The unit resets and begins
installing the newly transferred software.
4. Verify that the new software release was successfully installed as the Current
Software Revision.
Main Menu→Status→Identity
NOTE:
If someone opens a Telnet session and accesses the unit’s Identity screen
while the unit is downloading software, the In Progress... message
appears in the Alternate Software Revision field.
See Displaying System Information in Chapter 3, Status and Statistics to see
what is included on the unit’s Identity screen.
9000-A2-GB33-30
October 2003
4-11
4. Operation and Maintenance
Transferring Collected Data
SLV user history statistics and LMI packet capture data can be uploaded to an
NMS or a Network Associates Sniffer using FTP, which is faster than other
methods. The rate at which the data file is transferred is the rate set by the FTP
Max Transfer Rate (Kbps) option (see the iMarc SLV Configuration Reference).
Use your NMS application to FTP and view transferred statistics and packet data;
the data files are not in user-readable format. LMI packet capture data can also be
viewed via the LMI Trace Log (see Viewing Captured Packets from the
Menu-Driven User Interface in Chapter 5, Troubleshooting, for additional
information).
The system and trap logs can also be obtained from an iMarc unit.
Procedure
To retrieve data:
1. Initiate an FTP session to the device from which SLV statistics or packet data
will be retrieved.
2. Type bin to enter binary transfer mode.
3. Type hash to enter hash mode if you want to monitor the progress of the
upgrade, provided this function is supported by your equipment.
4. Type cd data to change to the data directory.
If retrieving . . .
Then . . .
LMI packet capture data
1. Stop the LMI Packet Capture Utility.
Main Menu→Control→LMI Packet Capture Utility
LMI packet capture data is not readable when the LMI
Packet Capture Utility is Active.
2. Perform a get of the lmitrace.syc file.
SLV statistics
Perform a get of the uhbcfull.dat file.
System Log
Perform a get of the syslog.dat file.
Trap Log
Perform a get of the traplog.dat file.
One of the following will appear:
—
File Transfer Complete – The transfer was successful.
—
File Transfer Failed – The transfer was unsuccessful. Try again or
end the session.
— Permission Denied – The LMI Packet Capture Utility was not
readable. Stop the LMI Packet Capture Utility and try again.
5. Close the FTP session.
4-12
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
Turning Off the System Alarm Relay
For carrier-mounted iMarc units, an alarm system relay is provided by the 9000
Series Access Carrier. This relay activates a light or buzzer when an alarm
condition is detected in one of the iMarc units.
Once the alarm relay is connected, enabling the System Alarm Relay option
activates this feature (see the iMarc SLV Configuration Reference).
Once activated, the relay is turned off in one of the following ways:
„
The alarm condition that activated the relay no longer exists. The relay stays
on until all alarm conditions have been corrected.
„
The System Alarm Relay option can be disabled.
Main Menu→Configuration→System→General
„
System Alarm Relay Cut-Off can be selected.
Main Menu→Control→System Alarm Relay Cut-Off
See Alarm Relay Connector in the 9000 Series Access Carrier Installation
Instructions for information about connecting the alarm relay.
9000-A2-GB33-30
October 2003
4-13
4. Operation and Maintenance
Hardware Maintenance for Models 9520, 9520-ILM, and 9820-45M
iMarc SLV rack-mounted units are designed for years of trouble-free service.
There are actions you can take to further reduce the likelihood and amount of
down time:
Area of Concern
Action
Front Panel Assembly
1. Vacuum dust from air vents whenever a buildup is visible. See
Cleaning the Front Panel Assembly on page 4-14.
2. Monitor LEDs for fan failures. Replace the front panel
assembly immediately upon failure. See Replacing the Front
Panel Assembly on page 4-15.
3. Test LEDs periodically. Replace the front panel assembly
immediately upon failure. See Replacing the Front Panel
Assembly on page 4-15.
Power Modules
Monitor LEDs for power module failures. Replace a failed power
module immediately. See Replacing a Power Module on
page 4-16.
Cleaning the Front Panel Assembly
The substantial airflow through the iMarc unit’s four fans may cause dust to collect
on the outside of the front air vents. When dust becomes visible at the air vents,
run the brush attachment of a vacuum cleaner gently over the front panel to
remove it.
In extremely dusty environments it may be necessary to remove the front panel
assembly to clean the blades of the fans. Refer all service to qualified personnel.
The procedure may be performed while the unit is running.
Procedure
To clean the fans:
1. Loosen the captive screws holding on the front panel.
! WARNING:
The fans continue to run until the fan power cable is removed. Keep your
hair and clothes away from the fan blades.
2. Carefully pull the front panel toward you.
3. Remove the fan power cable and LED ribbon cable.
4. Lay the front panel face-down on a flat surface.
5. Vacuum the fan blades and cages with the brush attachment of a vacuum
cleaner.
4-14
October 2003
9000-A2-GB33-30
4. Operation and Maintenance
! WARNING:
Each fan starts spinning as soon as the fan power cable is reconnected.
Keep your hair and clothes away from the fan blades.
6. Reconnect the LED ribbon cable, then reconnect the fan power cable. Verify
that all four fans are running.
7. Replace the front panel and tighten the captive screws.
CAUTION:
Do not leave the front panel assembly off the DSU for extended periods,
or the DSU will overheat.
Replacing the Front Panel Assembly
The System FAN LED on the front panel turns on when one or more of the front
panel fans has failed. Replace the front panel assembly as soon as possible after
this occurs. Refer all service to qualified personnel.
The procedure may be performed while the unit is running.
Procedure
To replace the front panel:
1. Loosen the captive screws holding on the front panel.
! WARNING:
The fans continue to run until the fan power cable is removed. Keep your
hair and clothes away from the fan blades.
2. Carefully pull the front panel toward you. Verify that at least one of the fans
has failed.
3. Remove the fan power cable and LED ribbon cable, and set the old front panel
assembly aside.
! WARNING:
Each fan starts spinning as soon as the fan power cable is reconnected.
Keep your hair and clothes away from the fan blades.
4. Take the new front panel and connect the LED cable, then connect the fan
power cable. Verify that all four fans are running.
5. Replace the front panel and tighten the captive screws. Verify that the FAN
LED is turned off.
9000-A2-GB33-30
October 2003
4-15
4. Operation and Maintenance
CAUTION:
Do not leave the front panel assembly off the iMarc SLV unit for extended
periods, or the unit will overheat.
Replacing a Power Module
A power module requires replacement in an iMarc unit when:
„
The front panel System PWR LED is lit. This means that one of the power
modules has failed.
„
Power is applied to a power module and it is switched on, but the power
module LED does not light.
Refer all service to qualified personnel.
Procedure
To replace a power module:
1. For a system with redundant power, determine which power module still has
its power LED lit. This is the functional power supply.
! WARNING:
Do not pull out a power module until the power cord has been removed.
2. Remove the power cord from the failed power module.
3. Unscrew the captive screw holding the failed power module in place.
4. Pull out the power module and set it aside.
5. Slide in the new power module until it seats in its connector. Verify that the
switch is in the Off position.
6. Tighten the captive screw.
7. Replace the power cord. Move the power module switch to the On position.
8. Verify that the power module LED is lit and that the front panel System PWR
LED is off.
4-16
October 2003
9000-A2-GB33-30
Troubleshooting
5
This chapter includes the following:
9000-A2-GB33-30
„
Problem Indicators on page 5-2
„
Resetting the Unit and Restoring Communication on page 5-3
„
Troubleshooting Management Link Feature on page 5-5
„
LMI Packet Capture Utility Feature on page 5-5
„
Alarms on page 5-7
„
Viewing the Trap Event Log on page 5-15
„
Troubleshooting Tables on page 5-15
„
Tests Available on page 5-19
„
Starting and Stopping a Test on page 5-21
„
PVC Tests on page 5-23
„
Network ATM Loopback (9783, 9788) on page 5-27
„
Physical Tests (9123, 9126, 9128) on page 5-29
„
Physical Tests (9520, 9520-ILM) on page 5-38
„
Physical Tests (9623, 9626) on page 5-42
„
Physical Tests (9720, 9783, 9788 CSU/DSUs) on page 5-46
„
Physical Tests (9820-2M, 9820-8M, 9820-45M) on page 5-47
„
IP Ping Test on page 5-48
„
Lamp Test on page 5-54
October 2003
5-1
5. Troubleshooting
Problem Indicators
The unit provides a number of indicators to alert you to possible problems:
Indicators . . .
See . . .
LEDs
Viewing LEDs and Control Leads and LED Descriptions in
Chapter 3, Status and Statistics, as well as the user
interface screen.
Main Menu→Status→
Display LEDs and Control LEDs
Health and Status
Table 3-6, Health and Status Messages, in Chapter 3,
Status and Statistics.
Main Menu→Status→System and Test Status
Messages also appear at the bottom of any menu-driven
user interface screen.
Performance statistics
Performance Statistics in Chapter 3, Status and Statistics,
to help you determine how long a problem has existed.
Alarm conditions that will
generate an SNMP trap
Alarms on page 5-7.
SNMP traps
iMarc SLV SNMP Reference.
Traps supported include warm-start, authentication-failure,
enterprise-specific (those specific to the unit), link-up, and
link-down.
5-2
October 2003
9000-A2-GB33-30
5. Troubleshooting
Resetting the Unit and Restoring Communication
You can reset the unit in one of four ways:
„
Reset it from the Control menu.
„
Cycle the power.
„
Reset the configuration options for the COM port, or reload the factory default
settings.
„
Set the appropriate MIB object from NMS (see your NMS documentation).
The unit performs a self-test when it is reset.
Resetting the Unit from the Control Menu
Use this procedure to initiate a reset and power-on self-test of the unit.
Procedure
To reset the unit from the Control menu:
1. From the Main Menu screen, select Control.
2. Select Reset Device and press Enter. The Are You Sure? prompt appears.
3. Type y ( Yes) and press Enter. The unit reinitializes itself, performing a self-test.
Resetting the Unit By Cycling the Power
Disconnecting, then reconnecting the power cord resets the unit.
9000-A2-GB33-30
October 2003
5-3
5. Troubleshooting
Restoring Communication with an Improperly Configured Unit
Configuring the unit improperly could render the menu-driven user interface
inaccessible. If this occurs, connectivity to the unit can be restored via a directly
connected asynchronous terminal.
Procedure
To reset COM port settings:
1. Configure the asynchronous terminal to operate at 19.2 Kbps, using character
length of 8 bits, with one stop-bit, and no parity. In addition, set Flow Control to
None.
2. Reset the unit, then hold the Enter key down until the System Paused screen
appears. (See Resetting the Unit and Restoring Communication on page 5-3
for other methods of resetting the unit.)
3. Tab to the desired prompt, and type y (Yes) at one of the prompts.
If selecting . . .
The following occurs . . .
Reset COM Port usage
„
„
„
Reload Factory Defaults
„
„
Port Use is set to Terminal so the asynchronous
terminal can be used.
Data Rate (Kbps), Character Length, Stop Bits, and
Parity are reset to the factory defaults.
Unit resets itself.
All configuration and control settings are reset to the
Default Factory Configuration, overwriting the
current configuration.
Unit resets itself.
CAUTION: This causes the current configuration to be
destroyed and a self-test to be performed.
If no selection is made within 30 seconds, or if No (n) is entered, the unit
resets itself and no configuration changes are made.
Once the unit resets itself, connectivity is restored and the Main Menu screen
appears.
5-4
October 2003
9000-A2-GB33-30
5. Troubleshooting
Troubleshooting Management Link Feature
A dedicated troubleshooting management link is available to help service
providers isolate device problems within their networks. This feature allows Telnet
or FTP access to the unit on this link and troubleshooting over this link is
essentially transparent to customer operations. No alarms or SNMP traps are
generated to create nuisance alarms for the customer.
See Configuring Node IP Information in the iMarc SLV Configuration Reference for
additional information about this feature.
LMI Packet Capture Utility Feature
A packet capture utility has been provided to aid with problem isolation when LMI
errors are detected. Using this utility, any enabled frame relay link on the user data
port or network interface can be selected. The utility captures any LMI packets
sent or received and writes them to a data file called lmitrace.syc in the system’s
data directory so the data can be uploaded and transferred to a Network
Associates Sniffer for analysis.
The LMI Trace Log also provides access to captured packet information. See
Viewing Captured Packets from the Menu-Driven User Interface on page 5-6 for
additional information on this feature.
Procedure
To use this utility:
1. Select the LMI Packet Capture Utility. Select an enabled frame relay link.
Main Menu→Control→LMI Packet Capture Utility
2. Select a Capture Interface from the list of enabled frame relay links: Net1-FR1
Port-1, Port-2, DSX-1 (if defined as the user data port), or an ISDN Link Name
(if a DBM is present).
3. Start packet capture.
While capturing data, the status is Active. Packets in Buffer indicates the
number of packets that have been captured. Up to 8000 packets can be held.
When the buffer is full, the oldest packets will be overwritten.
4. To stop the utility, press Enter. The field toggles back to Start.
5. Upload the data file holding the collected packets to a diskette so the
information can be transferred to a Network Associates Sniffer for
debugging/decoding.
See Transferring Collected Data in Chapter 4, Operation and Maintenance, for
additional information about this feature.
9000-A2-GB33-30
October 2003
5-5
5. Troubleshooting
Viewing Captured Packets from the Menu-Driven User Interface
The twelve most recent LMI events are stored in the trace log. Once the capture
buffer or trace log is full, the oldest packets are overwritten. To view the most
recently captured packets using the menu-driven user interface:
LMI Packet Capture Utility→Display LMI Trace Log
LMI Trace Log Example
main/control/lmi_capture/display_log
Device Name: Node A
9128-II
5/26/2000 23:32
LMI TRACE LOG
Packets Transmitted to Net1-FR!
LMI Record #1 at 0 s
Status Enquiry Message, 13 bytes
LMI Type is Standard on DLCI 1023
Sequence Number Exchange
Send Seq #181, Rcv Seq #177
Page 1 of 3
Packets Received from Net1-FR1
LMI Record #2 at 0 s
Status Enquiry Message, 13 bytes
LMI Type is Standard on DLCI 1023
Sequence Number Exchange
Send Seq #181, Rcv Seq #177
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
PgUp
PgDn
Refresh
Select Refresh to update the screen with the twelve most recently collected LMI
messages.
The following information is provided:
„
The internal LMI record number assigned to the packet (1–8000), and the
amount of time the utility was running when the packet was captured.
The maximum amount of time displayed is 4,294,967 seconds (s), which is
reset to 1 second when this amount of time is exceeded.
5-6
„
The type of message, either Status or Status Enquiry, from the captured
packet, and the number of bytes in the packet.
„
The LMI Type identified in the Protocol Discriminator portion of the captured
packet, and the DLCI number for the packet.
„
The type of information contained in the captured packet, either Sequence
Number Exchange or Full Status Report.
„
The send and receive (rcv) sequence numbers from the captured packet
(0–255).
„
On the Packets Received side of the screen, PVC status for up to ten DLCIs
can be shown. It shows the DLCI number, its active bit status, and if Standard
LMI is running, the DLCI’s CIR value.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Alarms
The following table describes the alarm conditions that will generate an SNMP trap
for a physical interface, and the frame relay LMIs and DLCIs. These alarm
conditions also generate Health and Status messages seen on the System and
Test Status screen.
Main Menu→Status →System and Test Status
Table 5-1.
Alarm Conditions (1 of 8)
Alarm Condition
What It Indicates
What To Do
AIS at DSX-1
For the DSX-1 interface, the
attached DTE is
transmitting an AIS.
For the DSX-1 interface, check the
DTE attached to the interface.
AIS at Network 1
An Alarm Indication Signal
(AIS) is being received by
the interface. AIS is an
unframed, all ones signal.
For the network interface, report
the problem to your service
provider.
Cross Pair Detected
The TX and RX pairs are
reversed on a DDS network
connection.
Reverse the TX and RX pairs.
CTS down to
Port-1 Device
The CTS control lead on the
device’s interface is off.
Check DTR and RTS from Port-1.
AIS at T3 User,
Port-1 (9520-ILM)
DBM BRI Card Failed
The ISDN BRI DBM failed
to pass the self-test.
„
„
Verify that the port is enabled.
Check DTR from the user data
port.
Reset the iMarc unit (Main
Menu→ Control→ Reset Device).
If the DBM fails again, contact
your service representative.
DLCI nnnn Down,
frame relay link 1,2
The DLCI for the specified
frame relay link is down.
Verify that the network LMI is up. If
it is, contact your network
provider, or your ISDN service
provider if an ISDN Link Name is
the link.
DTR Down from Port-1
Device
The DTR control lead on
the device connected to
Port-n is disasserted.
Examine the attached DTE and
cable connected to the system’s
port.
The DTR control lead on
the device connected to the
specified port is off. This
message applies to data
ports that act as DCEs.
1
2
3
9000-A2-GB33-30
„
„
Check that the port cable is
securely attached at both ends.
Check the status of the
attached equipment.
nnnn indicates a DLCI number of 16 through 1007.
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
Does not apply to a TS Access Management Link DLCI.
October 2003
5-7
5. Troubleshooting
Table 5-1.
Alarm Conditions (2 of 8)
Alarm Condition
What It Indicates
EER at Network 1
The error rate of the
received network signal
exceeds the currently
configured threshold. This
condition only occurs if the
network interface is
configured for ESF framing.
What To Do
„
„
Verify that the network cable is
securely attached at the
network interface.
Contact your network provider.
This condition clears when
the error rate falls below the
threshold value, which may
take up to 15 minutes.
Ethernet Link Down
The communication link for
the Ethernet port is down
and the Interface Status for
the port is enabled.
Excessive BPVs at
Network 1 –
hhh:mm:ss 3
An excessive number of
bipolar violations has been
detected on the DDS
network interface, followed
by the period of time that
the condition has existed.
Check the LAN connected to the
Ethernet port.
„
„
Verify that the network cable is
securely attached at both ends.
Contact your network provider.
Caused when at least one
invalid BPV has occurred
every 20 ms for 2 seconds.
Fan Failure
One of the fans has failed.
Notify your service representative.
Have the front panel assembly
replaced as soon as possible. See
Replacing the Front Panel
Assembly in Chapter 4, Operation
and Maintenance.
Internal Modem Failed
The unit’s internal modem
failed to pass the self-test.
Reset the iMarc unit (Main
Menu→ Control→ Reset Device).
If the modem fails again, contact
your service representative.
ISDN Link Profile
Disabled ISDN Link
Name
1
2
3
5-8
An ISDN backup call could
not be made because the
ISDN link profile specified
Link Name is disabled
(Main
Menu→ Configuration→
ISDN→ Link Profiles).
Enable the ISDN link profile if you
want to make a call.
nnnn indicates a DLCI number of 16 through 1007.
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
Does not apply to a TS Access Management Link DLCI.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Table 5-1.
9000-A2-GB33-30
Alarm Conditions (3 of 8)
Alarm Condition
What It Indicates
What To Do
ISDN Link Profile
Invalid,
ISDN Link Name
An ISDN backup call could Check that the phone number is
not be made because the
correct.
ISDN link profile specified
(ISDN Link Name) is invalid.
ISDN Network Failed
(Active/Idle)
An ISDN network failure
was detected when a
backup call was in progress
or the DBM was in Idle
mode.
Contact your network provider if
the problem persists.
LatExceedIP_Address,
COSx,DLCInnnn1
An IP SLV Latency
Threshold has been
exceeded for the specified
Class Of Service of the
path.
Contact your service provider.
Link Profile Disabled,
ISDN Link Name
An ISDN backup call could
not be made because the
specified link profile was
disabled.
Change the ISDN Link Profile’s
Link Status to Auto (Main
Menu→ Configuration→
ISDN→Link Profiles).
1
nnnn indicates a DLCI number of 16 through 1007.
2
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
3
Does not apply to a TS Access Management Link DLCI.
October 2003
5-9
5. Troubleshooting
Table 5-1.
Alarm Conditions (4 of 8)
Alarm Condition
What It Indicates
What To Do
LMI Down, frame relay
link 2
The Local Management
Interface is down for the
specified frame relay link.
For the network interface:
„
„
If LMI was never up, verify that
the LMI Protocol setting
reflects the LMI type being
used.
If LMI was never up:
– Verify that the proper time
slots have been configured.
– Verify that the LMI Protocol
setting reflects the LMI type
being used.
„
Verify that Frame Relay
Performance Statistics show
LMI frames being transmitted.
If all of the above have been
verified and the physical link is not
in Alarm, contact your network
provider.
For user data port:
„
„
„
Check that the DTE cable is
securely attached at both ends.
Verify that Transmit Clock
Source and Invert Transmit
Clock options are properly
configured.
Verify that Frame Relay
Performance Statistics show
LMI frames being received. If
no frames are being received:
– Check the attached device.
– Verify that the LMI Protocol
setting reflects the LMI type
being used.
LOF at Network 1
LOF at T3 User,
Port-1 (9520-ILM)
5-10
Loss Of Frame occurred on
the specified interface. An
Out Of Frame (OOF)
condition has persisted for
2.5 seconds.
The condition is cleared when
there are no OOF errors over a
10-second period. If the problem
persists, contact your network
provider.
1
nnnn indicates a DLCI number of 16 through 1007.
2
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
3
Does not apply to a TS Access Management Link DLCI.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Table 5-1.
Alarm Conditions (5 of 8)
Alarm Condition
What It Indicates
LOS at DSX-1
A Loss of Signal (LOS)
condition is detected on the
DSX-1 interface. Clears
when the ratio of ones to
zeros received is greater
than or equal to 12.5%.
„
„
LOS at Network 1
LOS at T3 User, Port-1
(9520-ILM)
No signal being
transmitted from the
DTE.
„
„
Network cable problem.
No signal is being
transmitted at the
far-end iMarc unit.
Facility problem.
Network Com Link
Down
The communication link for
the COM port is down and
the COM port is configured
for Net Link.
No Signal at Network 1
– hhh:mm:ss 3
A No Signal (NS) condition
has been detected on the
DDS network interface,
followed by the period of
time that the condition has
existed.
OOF at DSX-1
„
2
3
„
Check that the DSX-1 cable is
securely attached at both ends.
Check the DTE status.
„
„
„
Check that the network cable is
securely attached at both ends.
Check far-end iMarc unit
status.
Contact your network provider.
Check the router connected to the
COM port.
„
„
„
Check for a cross-pair
condition.
Verify that the network cable is
securely attached at both ends.
Contact your network provider.
An Out of Frame (OOF)
condition is detected on the
DSX-1 interface.
„
1
„
A Loss of Signal (LOS)
condition is detected on the
network interface. Clears
when the ratio of ones to
zeros received is greater
than or equal to 12.5%.
„
9000-A2-GB33-30
DSX-1 cable problem.
What To Do
Incompatible framing
format between the DTE
and the iMarc unit.
DSX-1 cabling problem.
„
„
Check that the framing format
for the DSX-1 (DTE) interface
is correct.
Check that the DSX-1 cable is
securely attached at both ends.
nnnn indicates a DLCI number of 16 through 1007.
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
Does not apply to a TS Access Management Link DLCI.
October 2003
5-11
5. Troubleshooting
Table 5-1.
Alarm Conditions (6 of 8)
Alarm Condition
What It Indicates
OOF at Network 1
An Out of Frame (OOF)
condition is detected on the
network interface.
„
Incompatible framing
format between the
network and the iMarc
unit.
What To Do
„
Check that the framing format
for the network interface is
correct (T1).
Verify that the Line Rate option
is configured correctly (DDS).
„
„
OOS at Network 1 –
hhh:mm:ss 3
5-12
Network cabling
problem.
Facility problem.
An Out of Service condition
has been detected on the
DDS network interface,
followed by the period of
time that the condition has
existed.
„
„
„
„
„
Check that the network cable is
securely attached at both ends.
Contact your network provider.
Check for a cross-pair
condition.
Verify that the network cable is
securely attached at both ends.
Contact your network provider.
PathIP_ Address
Down, DLCInnnn1
A path on the network
interface is unavailable.
Determine why the path went
down.
Power Supply Failure
(9520, 9520-ILM,
9820-45M)
The power supply output
voltage has dropped below
the specified tolerance
level.
Notify your service representative.
Have the power supply replaced.
See Replacing a Power Module in
Chapter 4, Operation and
Maintenance.
Power Supply/Fan
Alarm (9000 Series
Carrier)
The power supply output
voltage has dropped below
the specified tolerance level
required for the system, or
one or both fan trays are not
operating properly.
Check the LEDs on the power
supply and fan trays to determine
which may have failed, then
replace the failed component.
1
nnnn indicates a DLCI number of 16 through 1007.
2
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
3
Does not apply to a TS Access Management Link DLCI.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Table 5-1.
Alarm Conditions (7 of 8)
Alarm Condition
What It Indicates
Primary Clock Failed
A failure of the configured
primary clock source for the
unit was detected and the
secondary clock is
providing the timing for the
unit.
What To Do
„
„
Check that the network cable is
securely attached at both ends.
Contact your network provider.
This condition clears when
the configured primary
clock is restored.
Primary & Secondary
Clocks Failed
A failure of both clock
sources configured for the
unit was detected.
This condition only applies
to T1 network and DSX-1
interfaces. It clears when
the configured primary
clock is restored.
Secondary Clock
Failed
A failure of the configured
secondary clock source for
the unit was detected and
the internal clock is
providing the timing for the
unit.
The clock source will not
automatically switch from
internal until the primary
clock source returns.
Self-Test Failure
SLV Latency
Exceeded, DLCI nnnn,
frame relay link 1, 2, 3
1
2
3
9000-A2-GB33-30
The unit did not pass its
basic verification tests when
it was powered on or reset.
The measured latency of
SLV communication
responses from the remote
unit on this DLCI is
excessive, so the DLCI has
been declared unsuitable
for normal multiplexed PVC
operation (DLCI Type is set
to Multiplexed).
„
„
Reset the unit.
Contact your service
representative.
Wait until the DLCI is declared
operational again.
If the unit has ISDN backup
capability, this condition will
initiate backup.
nnnn indicates a DLCI number of 16 through 1007.
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
Does not apply to a TS Access Management Link DLCI.
October 2003
5-13
5. Troubleshooting
Table 5-1.
Alarm Conditions (8 of 8)
Alarm Condition
What It Indicates
SLV Timeout, DLCI
nnnn, frame relay
link 1, 2, 3
An excessive number of
SLV communication
responses from the remote
system have been missed
on the specified multiplexed
DLCI and link.
What To Do
„
„
Verify that the network LMI is
up. If it is, contact your network
service provider.
If a DBM is present and Auto
Backup is enabled, backup is
initiated automatically.
If the frame relay link is
Net1-FR1, the timeout is on
the network FrameRly1
timeslot assignment.
When a hardware bypasscapable device has been
detected at the other end of
the PVC and this condition
occurs, only user data for
EDLCI 0 will be transmitted
as long as the condition
exists.
Suboptimal Link Rate,
frame relay link 2
The specified frame relay
multilink has failed to
achieve the configured
Maximum Link Rate for the
link.
No action required.
This message appears for
multilink aggregate frame
relay links if LMI is down on
any of its constituent links.
Two Level-1 Users
Accessing Device
Another user with Level-1
security access is currently
accessing the unit.
Wait until no other Level-1 users
are accessing the unit if testing or
configuration will be performed.
Be aware that actions of the
other user may override
your test commands and
configuration changes.
Yellow at DSX-1
Yellow at Network 1
Yellow at T3 User,
Port-1 (9520-ILM)
1
2
3
5-14
A yellow alarm signal is
received on the DSX-1
interface. DTE has detected
a LOS or OOF condition.
„
„
Check that the DSX-1 cable is
securely attached at both ends.
Check the status of the
attached equipment.
A yellow alarm signal is
received on the interface.
„
Cable problem.
„
„
Facility problem.
„
Check that your cable is
securely attached at both ends.
Contact your network provider.
nnnn indicates a DLCI number of 16 through 1007.
frame relay link is one of the following:
– Net1-FR1. The frame relay link specified for the network interface, Network 1.
– Port-n. The frame relay link associated with a user data port.
– ISDN Link Name on a non-network ISDN DBM interface.
Does not apply to a TS Access Management Link DLCI.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Viewing the Trap Event Log
The Trap Event Log displays all traps stored in the SNMP trap event log. ASCII
trap strings used to describe trap events are provided in the tables contained in
Standards Compliance for SNMP Traps (see the iMarc SLV SNMP Reference).
See Trap Event Log in Chapter 3, Status and Statistics, for a screen example and
additional information.
Troubleshooting Tables
The unit is designed to provide many years of trouble-free service. However, if a
problem occurs, refer to the appropriate table in the following sections for possible
solutions.
Device Problems
Table 5-2.
Device Problems (1 of 2)
Symptom
Possible Cause
Solutions
No power, or the LEDs
are not lit.
The power cord is not
securely plugged into the
wall receptacle to rear panel
connection.
Check that the power cord is
securely attached at both ends.
The wall receptacle has no
power.
„
„
„
Power-On Self-Test
fails. Only Alarm LED
is on after power-on.
The unit has detected an
internal hardware failure.
„
„
„
9000-A2-GB33-30
October 2003
Check the wall receptacle
power by plugging in some
equipment that is known to be
working.
Check the circuit breaker.
Verify that your site is not on an
energy management program.
Reset the unit and try again.
Contact your service
representative.
Return the unit to the factory
(refer to Warranty, Sales,
Service, and Training
Information on page A of this
document).
5-15
5. Troubleshooting
Table 5-2.
Device Problems (2 of 2)
Symptom
Possible Cause
Cannot access the unit
or the menu-driven
user interface.
Login or password is
incorrect, COM port is
misconfigured, or the unit is
otherwise configured so it
prevents access.
Failure xxxxxxxx
appears at the top of
the System and Test
Status screen, at
Self-Test Results.
The unit detects an internal
software failure.
Solutions
„
„
„
„
„
An LED appears
dysfunctional.
LED is burned out.
Not receiving data.
Network cable loose or
broken.
Receiving data errors
Frame Relay Discovery is
on a multiplexed DLCI, being used for automatic
but frame relay is okay. DLCI and PVC
configuration.
Reset the unit (see Restoring
Communication with an
Improperly Configured Unit on
page 5-4).
Contact your service
representative.
Record the 8-digit code from
the System and Test Status
screen.
Reset the unit and try again.
Contact your service
representative and provide the
8-digit failure code.
Run the Lamp Test. If the LED in
question does not flash with the
other LEDs, then contact your
service representative.
„
„
Reconnect or repair the cable.
Call the network service
provider.
Change the DLCI Type for each
network DLCI from Multiplexed to
Standard, turning off multiplexing.
The equipment at the other
end is not frame relay
RFC 1490-compliant.
5-16
October 2003
9000-A2-GB33-30
5. Troubleshooting
Frame Relay PVC Problems
Table 5-3.
Frame Relay PVC Problems
Symptom
Possible Cause
Solutions
No receipt or
transmission of data
Cross Connection of the
DLCIs are configured
incorrectly.
Verify the PVC connections and
DLCIs by checking the
network-discovered DLCIs on the
LMI Reported DLCIs screen.
DLCI is inactive on the
frame relay network.
„
„
Verify the LMI Reported DLCI
field on the Interface Status
screen.
DTE is configured
incorrectly.
Check the DTE’s configuration.
LMI is not configured
properly for the DTE or
network.
Configure LMI characteristics to
match those of the DTE or
network.
LMI link is inactive.
Verify that the LMI link is active on
the network; the Status Msg
Received counter on the Network
Frame Relay Performance
Statistics screen increments.
Losing Data
Frame relay network is
experiencing problems.
Run PVC Loopback and Pattern
tests to isolate the problem, then
contact the service provider.
Out of Sync
If Monitor Pattern was
selected, it means the test
pattern generator and
receiver have not yet
synchronized.
CIR settings for the units at
each end are mismatched.
If the message persists, it
means that 5 packets out
of 25 are missing or are out
of sequence.
9000-A2-GB33-30
Verify that the DLCI(s) is active
on the LMI Reported DLCIs
screen. If the DLCI(s) is not
active, contact the service
provider.
October 2003
„
„
„
Verify that the unit at the other
end is configured to Send
Pattern.
Correct unit configurations.
Correct the CIR setting so both
units are configured the same.
Check the line’s error rate – the
physical line quality.
Contact the service provider.
5-17
5. Troubleshooting
ISDN DBM Problems
Table 5-4.
ISDN DBM Problems
Symptom
Possible Cause
Solutions
Cannot connect to the
remote unit
Misconfiguration
„
„
„
„
„
DBM LMI comes up,
but no data is
transferred
Misconfiguration
Verify that the link profiles are
correct in both units, both the
area codes and phone or ID
numbers (see Setting Up ISDN
Link Profiles in the iMarc SLV
Configuration Reference).
For a BRI DBM, verify that the
SPIDs and local area codes
and phone numbers are
correct (see Configuring the
ISDN DBM Interface in the
iMarc SLV Configuration
Reference).
Verify that the unit at one end is
configured to originate and the
unit at the other end is
configured to answer a call.
Verify that the ISDN interface is
enabled.
Verify that Auto Backup is
enabled and no time
restrictions apply.
Check that the DLCI numbers are
correct and are the same at both
ends.
See Table 3-12, Most Recent and Previous Cause Value Messages, in Chapter 3,
Status and Statistics, for additional information about ISDN problems. Last Cause
Value messages appear on the DBM Interface Status screen.
Main Menu→Status →DBM Interface Status
See Configuring the ISDN DBM Interface and Setting Up ISDN Link Profiles in the
iMarc SLV Configuration Reference for more information about ISDN DBM
configuration.
5-18
October 2003
9000-A2-GB33-30
5. Troubleshooting
Tests Available
The following are all the tests available to iMarc SLV units. Which tests are
available on a particular unit depend on the model and its interfaces. For example,
if the unit does not have the ISDN DBM feature, ISDN Call does not appear with
the ISDN PVC Tests; PRI Physical Tests only appears when an ISDN PRI
DBM is installed.
Test Menu Example
main/test
Device Name: Node A
9xxx
09/03/2003 05:19
TEST
Network PVC Tests
Data Port PVC Tests
DSX-1 PVC Tests
T3 User Port PVC Tests
ISDN Call/PVC Tests
Network ATM Loopback Tests
Network Physical Tests
Data Port Physical Tests
T3 User Port Physical Tests
DSX-1 Physical Tests
PRI Physical Tests
IP Ping
Lamp Test
Abort All Tests
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
PVC Tests menu selections are suppressed when no PVCs have been configured
on the interface. Check that both ends of the cables are properly seated and
secured.
Tests can be commanded from the OpenLane 5.x management system using its
Diagnostic Troubleshooting graphical interface, as well as from the menu-driven
user interface.
9000-A2-GB33-30
October 2003
5-19
5. Troubleshooting
Test Timeout Feature
A Test Timeout feature is available to automatically terminate a test (as opposed to
manually terminating a test) after it has been running a specified period of time.
It is recommended that this feature be used when the iMarc unit is remotely
managed through an inband data stream (PVC). If a test is accidently commanded
to execute on the interface providing management access, control is regained
when the specified time period expires, automatically terminating the test.
To use this feature, enable the Test Timeout configuration option, and set a
duration for the test to run in the Test Duration (min) configuration option (see
Configuring General System Options in the iMarc SLV Configuration Reference).
NOTE:
These configuration options do not pertain to tests commanded by the DTE,
like a DTE-initiated External Loopback.
DBM Tests
The Test menu allows you to run PVC loopbacks and test patterns on the unit and
its DBM interface. It is available to users with a security access level of 1 or 2.
Currently, there are no physical tests for a BRI DBM interface.
DBM tests are started and monitored the same as the network tests. See System
and Test Status Messages in Chapter 3, Status and Statistics, for ISDN
backup-related test messages appearing on the System and Test Status screen.
See PVC Tests on page 5-23 on for additional information.
5-20
October 2003
9000-A2-GB33-30
5. Troubleshooting
Starting and Stopping a Test
Use this procedure to start, monitor, or abort specific tests. To abort all active tests
on all interfaces, see Aborting All Tests on page 5-22.
When the status of a test is . . .
The only command available is . . .
Inactive
Start
Active
Stop
Start or stop an individual test using the same procedure.
Procedure
To start and stop a loopback or a send-pattern test:
1. Follow this menu selection sequence:
Main Menu→Test
2. Select an interface and test (e.g., Network, Data Port, or ISDN PVC Tests) and
press Enter.
The selected test screen appears. Start appears in the Command column.
Inactive appears in the Status column.
3. Select the Port number and press Enter.
4. Select the DLCI number and press Enter if a PVC test has been selected.
The cursor is positioned at Start in the Command column of the first available
test and is highlighted.
5. To start the test, highlight Start under Command for the test you want to run
and press Enter. Stop now appears and is highlighted, and the status of the
test changes to Active.
The length of time that the test has been running is shown in the Result
column.
6. To stop the test, press Enter to send the Stop command. Start reappears
and the status of the test changes back to Inactive.
9000-A2-GB33-30
October 2003
5-21
5. Troubleshooting
Aborting All Tests
Use the Abort All Tests selection from the Test menu to abort all tests running on
all interfaces, with exception to DTE-initiated loopbacks. To abort individual tests
that are active, see Starting and Stopping a Test on page 5-21.
Procedure
To abort all tests on all interfaces:
1. Follow this menu selection sequence:
Main Menu→Test
2. Select Abort All Tests and press Enter.
Command Complete appears when all tests on all interfaces have been
stopped.
NOTE:
Abort All Tests does not interrupt DTE-initiated loopbacks.
5-22
October 2003
9000-A2-GB33-30
5. Troubleshooting
PVC Tests
PVC tests can be run on a requested DLCI for a selected interface.
„
When PVC tests are on a multiplexed DLCI between iMarc devices, they are
nondisruptive to data, so user data can continue to be sent during a test.
„
If the device at one end of the circuit is not an iMarc device, PVC tests are on
a standard DLCI and are disruptive to data. Also, the Connectivity test would
not appear.
Loopback, and send/monitor pattern tests are available for each interface on the
selected DLCI. iMarc devices should be at each end of the circuit. If a PVC
Loopback is started at one end of the circuit, the other end can send and monitor
pattern tests.
The example below shows a PVC Test screen for an iMarc unit with ISDN backup
capability, with the multiplexed DLCI 550 selected. If a standard DLCI was
selected, (Disruptive), rather than (Non-Disruptive), would be displayed
after Test. Also, the Connectivity test would not appear.
PVC Tests Screen Example
main/test/network_pvc
Device Name: Node A
9128-II
5/26/2000 23:32
NETWORK PVC TESTS
DLCI Number: 550
Test (Non-Disruptive)
Command
Status
Result
PVC Loopback:
Send Pattern:
Monitor Pattern:
Start
Start
Start
Inactive
Inactive
Inactive
Connectivity:
Start
Inactive
0:00:00
0:00:00
0:00:00
Sequence Errors
99999+
Data Errors
99999+
RndTrip Time (ms) 99999
Test Call:
Stop
Active
Frame Relay Link Up
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
If the unit does not have the ISDN DBM feature, or if the ISDN Link Profile’s Link
Status is disabled, Test Call does not appear. An Outbound Phone Number
must be configured for Test Call to appear.
NOTE:
Errors encountered during these tests may be caused by mismatched CIRs in
the two iMarc units. If errors are detected, verify the CIR configuration and
retest.
9000-A2-GB33-30
October 2003
5-23
5. Troubleshooting
PVC Loopback
The PVC Loopback loops frames back to the selected interface on a per-PVC
basis. This test logically (not physically) loops back frames received from another
iMarc device through the selected frame relay PVC to the same device.
Main Menu→Test→Network PVC Test
Network PVC Loopback
DTE
PVC #x
Network
PVC #x
98-16186
Main Menu→Test→Data Port PVC Tests
Main Menu→Test→T3 User Port PVC Tests
Main Menu→Test→DSX-1 PVC Tests
Port PVC Loopback
DTE
PVC #x
Network
PVC #x
98-16187
Main Menu→Test→ISDN Call/PVC Tests
ISDN PVC Loopback
PVC #x
DTE
ISDN
ISDN DBM
PVC #x
Network
98-16188
5-24
October 2003
9000-A2-GB33-30
5. Troubleshooting
Send Pattern
This test sends packets filled with a hexadecimal 55 test pattern and sequence
number over the selected interface and DLCI to another iMarc device.
To send a pattern test on a link:
Main Menu→Test→[Network PVC Tests/Data Port PVC Tests/
T3 User Port PVC Tests/ISDN Call/PVC Tests]
If the selected DLCI is
configured as . . .
Then . . .
And the default
Rate (Kbps) setting is . . .
Standard or IP Enabled
(Disruptive) appears
after Test
100% of CIR
Multiplexed
(Non-Disruptive)
appears after Test
10% of CIR
If the CIR is zero, the pattern will be sent at a rate of 1000 bps.
Monitor Pattern
This test monitors packets filled with a hexadecimal 55 test pattern and sequence
number over the selected interface and DLCI to another iMarc device.
To monitor a pattern test on a link:
Main Menu→Test→[Network PVC Tests/Data Port PVC Tests/
T3 User Port PVC Tests/ISDN Call/PVC Tests]
The current number of sequence and data errors are shown under the Result
column when the iMarc unit is in sync. An Out of Sync message appears when
5 frames out of 25 are missing or out of sequence.
These error counts are updated every second. If the maximum count is reached,
99999+ appears in these fields.
9000-A2-GB33-30
October 2003
5-25
5. Troubleshooting
Connectivity
Connectivity is a proprietary method that determines whether the iMarc device at
the other end of the frame relay PVC is active. This test stops automatically and
can only be executed for circuit multiplexed PVCs.
To run a connectivity test on a link:
Main Menu→Test→[Network PVC Tests/Data Port PVC Tests/
ISDN Call/PVC Tests]
Selecting Connectivity sends a frame to the iMarc unit at the other end of the PVC.
A RndTrip Time(ms) message appears in the Result column when a response
is received within 5 seconds, indicating that the iMarc unit at the remote end is
alive (operational and connected), and the round trip (RT) time is shown in
milliseconds (ms), with a resolution of 1 ms. If a response is not received within 5
seconds, No Response appears in the Result column.
Test Call
Test Call tests the device’s ability to place a call. It allows an alternate means of
controlling the activation or deactivation of an ISDN link. This test only appears for
an iMarc device with a DBM that is configured to originate backup calls (typically,
the remote site) and has its ISDN Link Status option set to Auto.
To place a test call:
Main Menu→Test→ISDN Call/PVC Tests
When a test call is started, Active appears in the Status column. While the call is
Active, the status of the call connection and the link appears in the Results
column.
„
A Frame Relay Link Up message indicates that the required calls have
been made and the link is successfully passing LMI data.
„
A Frame Relay Link Suboptimal message indicates that at least one
call has been made on the link, the link is successfully passing LMI data, but
the Maximum Link Rate configured in the ISDN Link Profile has not been
achieved for the link.
„
A Frame Relay Link Down message indicates that the call attempts were
not successful.
NOTE:
Primary network data is not affected by a test call. If there is a network failure
while a test call is active, the test call is terminated and the call is automatically
converted to a backup call.
5-26
October 2003
9000-A2-GB33-30
5. Troubleshooting
Network ATM Loopback (9783, 9788)
A Network ATM Loopback is a nondisruptive test that can be run on a Virtual
Channel Connection (VCC) for an ATM link on the network interface.
Select an enabled ATM link so available VCCs can be selected for testing on the
link.
Network ATM Loopback Tests Screen Example
main/test/network_atm
Device Name: Node A
9783-C-SLV
2/26/2001 08:03
Net1-ATM LOOPBACK TESTS
VPI,VCI: 0,35
Loopback Type: Segment
Destination Segment ID: FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF.FF
Test
ATM Ping:
Command
Start
Status
Inactive
Result
RndTrip Time(ms)
Reset
99999
-------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
The ATM Loopback causes the iMarc device to send either a segment or
end-to-end loopback packet toward the network on the selected VCC, then wait for
a response.
A RndTrip Time(ms) message appears in the Result column when a response
is received within 5 seconds, indicating that the iMarc unit at the remote end is
alive (operational and connected), and the round trip (RT) time is shown in
milliseconds (ms), with a resolution of 1 ms. If a response is not received within
5 seconds, No Response appears in the Result column and the test is
automatically stopped.
9000-A2-GB33-30
October 2003
5-27
5. Troubleshooting
The following fields are explained below.
For . . .
Select or Enter . . .
VPI,VCI
From the VCCs configured for the ATM link.
Loopback Type
„
„
Destination Segment ID
„
EndtoEnd – For Operations, Administration, and
Maintenance (OAM) functions.
The device defaults to this type of loopback.
Segment – For OAM functions, a segment loopback will
be performed on the selected VCC on the link.
ATM Segment ID for the loopback destination – The ID
must be entered in 16 byte values, 2 hexadecimal
characters each, separated by colons.
– The first byte must be 00, 01, 02, 03, or FF.
– If the first octet is FF, octets 2–16 must also be FF.
– If the first octet is 00, octets 2–16 must also be 00.
„
Reset – Resets the ATM Destination Segment ID for the
VCC. When selected, all octets in this segment are set
to FF, as shown in the screen example.
NOTE: Destination Segment ID and Reset do not appear if
Loopback Type is EndtoEnd instead of Segment.
ATM Ping
Start or Stop commands begin or end the test.
The following messages can appear on line 24:
„
If an ATM Location ID has not yet been configured, Loopback Type is set to
Segment, an ATM Ping is started, and an ATM Location ID must be
configured message is displayed.
„
If the device is already performing an ATM Ping, an Invalid – Was
Already Active message is displayed.
„
If any physical test is active on the interface when the ATM Ping was started,
the Invalid Test Combination message is displayed.
„
If the ATM link is not active when the ATM Ping is started, the Link
Inactive message is displayed.
This test cannot be run when a physical test is already active on the interface, and
no physical test can be run on the interface when the ATM Loopback is active on
the interface.
5-28
October 2003
9000-A2-GB33-30
5. Troubleshooting
Physical Tests (9123, 9126, 9128)
Physical tests require the participation of your network service provider.
Main Menu→Test→[Network Physical Tests/Data Port Physical Tests/
DSX-1 Physical Tests/PRI Physical Tests]
If the unit does not have the ISDN PRI DBM feature, PRI Physical Tests does not
appear.
An iMarc unit’s physical tests screen for the network interface is shown below.
Physical Tests Screen Example
main/test/network
Device Name: Node A
9128-II
5/26/2000 23:32
NETWORK 1 PHYSICAL TESTS
Test
Command
Status
Results
Start
Start
Start
Inactive
Inactive
Inactive
0:00:00
0:00:00
0:00:00
Remote Loopbacks
Send Line Loopback: Down
Send
Inactive
0:00:00
Pattern Tests
Send:
user-defined 0a0a
Monitor: user-defined0a0a
Stop
Stop
Active
Active
Local Loopbacks
Line Loopback:
Payload Loopback:
Repeater Loopback:
0:00:00 - Errors 99999+
0:00:00 - Errors 99999+
-------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
ResetMon
InjectErr
The InjectErr function key at the bottom of the screen only appears when a Send
Pattern Test is Active. Select InjectErr to inject a single bit error into the pattern
being sent.
The ResetMon function key at the bottom of the screen only appears when a
Monitor 511 test pattern is Active. Select ResetMon to reset the monitor pattern
error counter.
CAUTION:
You should not run these tests with frame relay equipment attached;
you must disconnect the frame relay equipment and use external test
equipment.
9000-A2-GB33-30
October 2003
5-29
5. Troubleshooting
Line Loopback (9123, 9126, 9128)
The Line Loopback (LLB) loops the information received on the selected interface
back to the source of the loopback. When used with a pattern test at the remote
node, LLB determines whether the problem is with the sending device or the T1
facility.
Main Menu→Test→Network Physical Tests
Framer
Other
T1
Interface
LLB
All
1s
The T1
Interface
97-15336
CAUTION:
This test may affect operation of frame relay PVCs assigned to the
selected port. While in loopback, the frame relay link will be down so any
IP data being sent while this test is active will be disrupted.
An LLB cannot be started when one of the following tests is active:
5-30
„
Payload Loopback, Send Remote Line Loopback, or an active Monitor Pattern
on this network interface.
„
Repeater Loopback on any other T1 interface with DS0s assigned to this
network interface.
„
Send Pattern Test on this network interface or any synchronous data port (Port
Use set to Synchronous) assigned to this interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) assigned to this network interface.
October 2003
9000-A2-GB33-30
5. Troubleshooting
Payload Loopback (9123, 9126, 9128)
The Payload Loopback (PLB) loops the information received on the selected
interface back to the network after it has passed through the receive and transmit
framing section of the device. Use the PLB to determine whether the problem is
with the T1 facility or in the circuitry of the remote device.
Main Menu→Test→Network Physical Tests
Other
T1
Interface
Framer
All
1s
PLB
The T1
Interface
97-15337
CAUTION:
This test may affect operation of frame relay PVCs assigned to the
selected interface. While in loopback, the frame relay link will be down
so any IP data being sent while this test is active will be disrupted.
A PLB cannot be started when one of the following tests is active:
9000-A2-GB33-30
„
Line Loopback, Repeater Loopback, Send Remote Line Loopback, or an
active Monitor Pattern on this network interface.
„
Payload or Repeater Loopback on any other T1 interface with DS0s assigned
to this network interface.
„
Send Pattern Test on this network interface or any synchronous data port (Port
Use set to Synchronous) assigned to this interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) and assigned to this network
interface.
October 2003
5-31
5. Troubleshooting
Repeater Loopback (9123, 9126, 9128)
The Repeater Loopback (RLB) loops data received from the data ports and the
DSX-1 interface after the signal has passed through the framing circuitry. Use RLB
to ensure that all of the data is correct up to the point where it is sent over the
interface. This helps to indicate that the iMarc unit is operational.
Main Menu→Test→Network Physical Tests
An attached device or test equipment should generate and monitor data to be
looped back.
Other
T1
Interface
Framer
RLB
AIS
The T1
Interface
97-15338
The iMarc unit will not respond to any messages from the network during this test.
CAUTION:
This test may affect operation of frame relay PVCs assigned to the
selected interface. While in loopback, the frame relay link will be down
so any IP data being sent while this test is active will be disrupted.
An RLB cannot be started when one of the following tests is active:
5-32
„
Payload Loopback, Send Remote Line Loopback, or an active Monitor Pattern
on this network interface.
„
All loopbacks on any other T1 interface with DS0s assigned to this network
interface.
„
Send Pattern Test on this network interface or any synchronous data port (Port
Use set to Synchronous) assigned to this interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) assigned to this network interface.
October 2003
9000-A2-GB33-30
5. Troubleshooting
DTE Loopback (9123, 9126, 9128)
The DTE external Loopback (DTLB) test loops the received signal on a DTE
interface back to the DTE without affecting the operation of the remaining ports.
Use this test for isolating problems on the DTE interface.
Main Menu→Test→Data Port Physical Tests
An attached device or test equipment must generate data to be looped back.
DSX
Interface
Network
Interface
All 1s
DTLB
DTE
Port 2
DTLB
DTE
Port 1
98-16190
CAUTION:
This test may affect operation of frame relay PVCs assigned to the
selected port. Any IP data being sent while this test is active will be
disrupted.
9000-A2-GB33-30
October 2003
5-33
5. Troubleshooting
Send Line Loopback (9123, 9126, 9128)
The remote Line Loopback (LLB) up and down codes are in-band codes that allow
control of a remote device. The LLB Up code invokes a line loopback in the remote
unit while the LLB Down code terminates the remote line loopback. Network
loopbacks are defined in AT&T TR 62411.
A remote LLB cannot be started when one of the following tests is active:
„
Any Loopback on the same interface.
„
Send Pattern Test on this network interface or any synchronous data port (Port
Use set to Synchronous) assigned to this interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) and assigned to this network
interface.
„
Data Channel Loopback on the frame relay link on this network interface.
Procedure
To start and stop a Line Loopback:
1. Follow this menu selection sequence:
Main Menu→Test→Network Physical Tests
2. Select the Up code in the Send Line Loopback row to put a remote device in
loopback.
3. To start the test, highlight Send under Command in the Send Line Loopback
row and press Enter. The code is sent for up to 10 seconds, or until an
acknowledgement is received from the remote end. The length of time that the
test has been running is shown in the Results column.
4. To stop the test, send the Down code to take the remote device out of
loopback.
5-34
October 2003
9000-A2-GB33-30
5. Troubleshooting
Data Channel Loopbacks on a Frame Relay Link (9123, 9126, 9128)
A network-initiated Data Channel Loopback (DCLB) loops data over the frame
relay link (DS0s) received on the network interface through the iMarc unit’s
framing circuitry and back to the same interface.
A DCLB can be controlled over the frame relay link using one of the following
in-band methods:
„
V.54 Loopback.
„
ANSI T1.403 Annex B Fractional T1 (FT1) Channel Loopback.
The frame relay service provider can use DCLB to verify the integrity of the frame
relay circuit.
Framer
Other
T1
Interface
The T1
DCLB Interface
All
1s
98-16223
CAUTION:
V.54 and FT1 Loopbacks may affect operation of frame relay PVCs
assigned to the selected port. While in loopback, the frame relay link will
be down so any IP data being sent while this test is active will be
disrupted.
9000-A2-GB33-30
October 2003
5-35
5. Troubleshooting
Send Remote Line Loopback (9123, 9126, 9128)
The remote Line Loopback (LLB) up and down codes are in-band codes that allow
control of a remote device. The LLB Up code invokes a line loopback in the remote
unit while the LLB Down code terminates the remote line loopback. Network
loopbacks are defined in AT&T TR 62411.
A remote LLB cannot be started when one of the following tests is active:
„
Any Loopback on the same interface.
„
Send Pattern Test on this network interface or any synchronous data port (Port
Use set to Synchronous) assigned to this interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) and assigned to this network
interface.
„
Data Channel Loopback on the frame relay link on this network interface.
Procedure
To start and stop a Remote Line Loopback:
1. Follow this menu selection sequence:
Main Menu→Test→[Network Physical Tests/PRI Physical Tests]
2. Select the desired network interface (shown in the screen title).
3. Select the Up code in the Remote Line Loopback row to put a remote device
into loopback.
4. To start the test, highlight Send under Command in the Remote Line
Loopback row and press Enter. The code is sent for up to 10 seconds, or until
an acknowledgement is received from the remote end. The length of time that
the test has been running is shown in the Results column.
5. To stop the test, send the Down code to take the remote device out of
loopback.
5-36
October 2003
9000-A2-GB33-30
5. Troubleshooting
Send and Monitor Pattern Tests (9123, 9126, 9128)
The pattern tests enable an iMarc unit to either send or monitor a known bit
pattern. These tests generate industry-standard bit patterns that can be used to
determine whether information is being correctly transmitted across a circuit.
The following test patterns are available:
— QRSS
— 511
— All-zeros
— 2047
— All-ones
— 2E15-1 (215-1)
— 1-in-8
— 2E20-1 (220-1)
— 3-in-24
— User-defined 2-byte test pattern (a0a0)
— 63
A Send Pattern test cannot be started when the following tests are running:
„
Any Loopback on the same interface.
„
Send Pattern Test on any port assigned to this network interface.
„
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) and assigned to this network
interface.
Procedure
To send and monitor a Pattern Test:
1. Follow this menu selection sequence:
Main Menu→Test→[Network Physical Tests/DSX-1 Physical Tests]
2. Select the desired pattern in the Send or Monitor field. If sending/monitoring a
user-defined pattern, enter the the desired 2-byte hexadecimal value in the
field next to Send or Monitor.
When sending a pattern, the InjectERR function key appears. Use InjectERR
if you want to inject a bit error in the transmitted bit pattern.
3. To send a pattern, highlight the Send command to send a pattern and press
Enter.
To monitor the test, highlight the Start command and press Enter.
The length of time that the test has been running is shown in the Result
column. An error count is also displayed. When monitoring a pattern, the
ResetMon function key appears. ResetMon resets the error count to zero.
4. To stop the test, press Enter to send the Stop command. Start reappears
and the status of the test changes back to Inactive.
9000-A2-GB33-30
October 2003
5-37
5. Troubleshooting
Physical Tests (9520, 9520-ILM)
Physical tests screens for the different interfaces are shown below.
Main Menu → Test → Network Physical Tests
Main Menu → Test → Data Port Physical Tests
Main Menu → Test → T3 User Port Physical Tests
Network Physical Tests Screen Example
main/test/network
Device Name: Node A
9520
05/13/2000 08:04
NETWORK 1 PHYSICAL TESTS
Test
Local Loopbacks
Line Loopback:
Command
Start
Status
Results
Inactive
0:00:00
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
Data Port Physical Tests Screen Example (9520)
main/test/network
Device Name: Node A
9520
05/13/2000 08:05
DATA PORT PHYSICAL TESTS
Test
Local Loopbacks
Line Loopback:
Command
Start
Status
Results
Inactive
0:00:00
PORT 1
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
5-38
October 2003
9000-A2-GB33-30
5. Troubleshooting
T3 User Port Physical Tests Screen Example (9520-ILM)
main/test/network
Device Name: Node A
9520-ILM
05/13/2000 08:06
T3 USER PORT PHYSICAL TESTS
Test
Local Loopbacks
Line Loopback:
Command
Start
Status
Results
Inactive
0:00:00
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
CAUTION:
You should not run these tests with frame relay equipment attached; you
must disconnect the frame relay equipment and use external test
equipment.
9000-A2-GB33-30
October 2003
5-39
5. Troubleshooting
Line Loopback (Network or 9520-ILM T3 User Port)
The Line Loopback (LLB) loops the information received on the selected interface
back to the source of the loopback. When used with a pattern test at the remote
node, LLB determines whether the problem is with the sending device or the T3
facility.
Main Menu → Test → Network Physical Tests → Line Loopback
Main Menu → Test → T3 User Port Physical Tests → Line Loopback
Framer
LLB
Network
Interface
00-16790
CAUTION:
This test may affect the operation of the frame relay PVCs assigned to
the selected port. While in loopback, the frame relay link will be down so
any IP data being sent while this test is active will be disrupted.
5-40
October 2003
9000-A2-GB33-30
5. Troubleshooting
DTE Loopback (9520 Data Port)
The DTE external Loopback (DTLB) test loops the received signal on a DTE
interface back to the DTE without affecting the operation of the remaining port.
Use this test for isolating problems on the DTE interface.
Main Menu → Test → Data Port Physical Tests → DTE Loopback
An attached device or test equipment must generate data to be looped back.
User
Port 1
DTLB
Network
Interface
User
Port 2
DTLB
00-16791
CAUTION:
This test may affect the operation of the frame relay PVCs assigned to
the selected port. Any IP data being sent while this test is active will be
disrupted.
9000-A2-GB33-30
October 2003
5-41
5. Troubleshooting
Physical Tests (9623, 9626)
An iMarc unit’s physical tests screen for the network interface is shown below. For
the user data port, only the DTE Loopback is available.
Main Menu→Test→[Network Physical Tests/Data Port Physical Tests]
Physical Tests Screen Example
main/test/network
Device Name: Node A
9626
5/26/2000 23:32
NETWORK 1 PHYSICAL TESTS
Test
Command
Status
Results
Local Loopbacks
CSU Loopback:
DSU Loopback:
Start
Start
Inactive
Inactive
0:00:00
0:00:00
Pattern Tests
Send 511:
Monitor 511:
Start
Start
Inactive
Active
0:00:00
0:00:00 - Errors 99999+
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
ResetMon
The ResetMon function key at the bottom of the screen only appears when a
Monitor 511 test pattern is Active. Select ResetMon to reset the monitor pattern
error counter.
CAUTION:
You should not run these tests with frame relay equipment attached;
you must disconnect the frame relay equipment and use external test
equipment.
5-42
October 2003
9000-A2-GB33-30
5. Troubleshooting
CSU (External) Network Loopback (9623, 9626)
CSU Loopback loops the received signal on the network interface back to the
network. This loopback is an external loopback that is located as close as possible
to the network interface.
Main Menu→Test→Network Physical Tests→CSU Loopback
DSU
DTE
Port
DTE
Interface
CSU
DDS
Network
Port
Aggregate
iMarc Access Unit
03-17414
CAUTION:
This test may affect the operation of the PVCs assigned to the network
interface. In addition, IP data sent over the PVC will be disrupted while
this test is active.
DSU (Internal) Network Loopback (9623, 9626)
DSU loopback loops the received signal on the network interface back to the
network without affecting operation of other ports. The signal is looped on the DTE
side of the iMarc unit. This loopback is an internal loopback that is located as close
as possible to the customer interface serving the DTE.
Main Menu→Test→Network Physical Tests→DSU Loopback
DSU
CSU
Aggregate
DTE
Port
DDS
Network
Port
DTE
Interface
iMarc Access Unit
03-17415
CAUTION:
This test may affect the operation of the PVCs assigned to the network
interface. In addition, IP data sent over the PVC will be disrupted while
this test is active.
9000-A2-GB33-30
October 2003
5-43
5. Troubleshooting
Latching Loopback (9623, 9626)
A latching loopback is a network-initiated DSU Loopback. Once a DSU Loopback
is started, the iMarc unit remains in loopback until it receives the loopback-release
sequence from the network.
The latching loopback code is a control sequence (as opposed to a bipolar
violation sequence); therefore, user data may cause the iMarc unit to activate the
loopback.
Main Menu→Configuration→Network→Physical
Disable the DSU Latching Loopback configuration option to stop the latching
loopback when the network did not command the test.
Send 511 (9623, 9626)
This test sends the 511 test pattern over the selected interface. The 511 test
pattern is a pseudo-random bit sequence (PRBS) that is 511 bits long (on the data
ports only). This is a PRBS 29 –1 test.
Main Menu→Test→[Network Physical Tests/Data Port Physical Tests]→
Send 511
When sending or monitoring a 511 test pattern using an external loopback
connector on the network or DTE port, you must follow the sequence below for
these tests to run correctly.
Procedure
To send a 511 test pattern using an external loopback connector:
1. Remove the network cable so that a No Signal (NS) condition occurs.
2. Start the Send Pattern test.
3. Place the loopback cable on the network or DTE port interface.
4. Start the Monitor 511 test.
5-44
October 2003
9000-A2-GB33-30
5. Troubleshooting
Monitor 511 (9623, 9626)
For Monitor 511, a 511 test pattern being sent over the network or DTE port
interface can be monitored. To view the test results, see the Network or Port-n
Physical Tests screen.
Main Menu→Test→[Network Physical Tests/Data Port Physical Tests]→
Monitor 511
The current number of bit errors is shown under the Result column when the iMarc
unit is in sync. An Out of Sync message appears when the test pattern generator
and receiver have not yet synchronized.
This error count is updated every second. If the maximum count is reached,
99999+ is shown in the field.
NOTE:
The 511 monitor expects external equipment to provide the clock for the 511
pattern for timing the incoming pattern on interchange circuit DA (ITU 113) –
Transmit Signal Element Timing (XTXC), with the DTE as the source.
DTE Loopback (9623, 9626)
The DTE external Loopback (DTLB) test loops the received signal on a DTE
interface back to the DTE without affecting the operation of the remaining ports.
Use this test for isolating problems on the DTE interface.
Main Menu→Test→Data Port Physical Tests→DTE Loopback
An attached device or test equipment must generate data to be looped back.
DSU
DTE
Port
DTE
Interface
Aggregate
iMarc Access Unit
CSU
DDS
Network
Interface
03-17416
CAUTION:
This test may affect the operation of the frame relay PVCs assigned to
the selected port. Any IP data being sent while this test is active will be
disrupted.
9000-A2-GB33-30
October 2003
5-45
5. Troubleshooting
Physical Tests (9720, 9783, 9788 CSU/DSUs)
iMarc DSL CSU/DSUs support a single physical test for the data port, the
DTE Loopback. This test does not appear for the routers.
DTE Loopback (9720, 9783, 9788 CSU/DSUs)
The local DTE external Loopback (DTLB) loops the received signal on the DTE
interface back to the DTE without affecting the operation of the remaining ports.
Use this test to isolate problems on the user data port.
Main Menu→Test→Data Port Physical Tests
User
Data
Port
Network
Port
DTLB
99-16284
An attached device or test equipment must generate the data to be looped back,
and the Port (DTE) Initiated Loopback option must be enabled. Refer to the iMarc
SLV Configuration Reference.
CAUTION:
This test may affect operation of frame relay PVCs for the port. Any data
being sent while this test is active will be disrupted.
5-46
October 2003
9000-A2-GB33-30
5. Troubleshooting
Physical Tests (9820-2M, 9820-8M, 9820-45M)
Physical Tests can be commanded for the user data port.
CAUTION:
You should not run these tests with frame relay equipment attached; you
must disconnect the frame relay equipment and use external test
equipment.
DTE Loopback (9820-2M, 9820-8M, 9820-45M)
The DTE external Loopback (DTLB) test loops the received signal on a user data
port back to the DTE. Use this test for isolating problems on the user data port.
An attached device or test equipment must generate data to be looped back.
User
Data
Port
Network
Port
DTLB
99-16284
CAUTION:
DTE Loopback will affect the operation of the frame relay PVCs assigned
to the user data port. Any IP data being sent while this test is active will
be disrupted.
To start and stop a DTE Loopback, follow this menu selection sequence:
Main Menu→Test→Data Port Physical Tests
View the length of time that the test has been running in the Result column.
9000-A2-GB33-30
October 2003
5-47
5. Troubleshooting
IP Ping Test
An IP Ping test can be run to test connectivity between the iMarc unit and any
iMarc unit, router, or NMS to which it has a route.
Times when you might want to run an IP Ping test are:
„
To test connectivity between the iMarc unit and any iMarc unit in the network
to verify that the path is operational. Select IP Ping Test – Procedure 1 on
page 5-53 to ping any far-end iMarc unit.
„
To verify the entire path between a newly installed remote site iMarc unit and
the central site NMS. During a remote-site installation, an IP Ping test is
typically run from the remote site to ping the NMS at the central site. The
remote iMarc unit must have SNMP trap managers configured, and one of
those trap managers must be the central site NMS. Select IP Ping Test –
Procedure 2 on page 5-54 to ping the NMS at the central site.
„
To test the path to the NMS trap managers during installation of the central site
iMarc unit. The remote iMarc unit must have configured the SNMP trap
managers to be sent the ping. Select IP Ping Test – Procedure 2 on page 5-54
to ping SNMP trap managers.
Ping Screen Example
main/test/ping
Device Name: Node A
9128-II
12/05/2002 06:02
IP PING
Target IP Address:
000.000.000.000
Destination Interface: Use Internal Route DLCI: 100 (Net1-ATM 15,255)
135.90.25.1
Source IP Address:
Special
Encapsulation:
Routed
TOS Byte
User Defined 001101
Packet Size:
64
Iteration Count:
1
Inter-ping Delay (sec): 5
Response Timeout (sec): 2
Start
--------------------------------------------------Status:
Alive
Transmit Receive
Lost
Loss Ratio
Pings:
000000 000000
000000
0000 %
Current Minimum Maximum Average
Roundtrip Delay (ms):
0000
0000
0000
0000
-------------------------------------------------------------------------------Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
5-48
October 2003
9000-A2-GB33-30
5. Troubleshooting
Table 5-5.
Ping Options (1 of 3)
Target IP Address
Possible Settings: 000.000.000.001–126.000.000.000,
128.000.000.000–223.255.255.255
Default Setting: 000.000.000.000
Specifies the IP address to which a ping will be sent.
000.000.000.001–126.000.000.000, 128.000.000.000–223.255.255.255 – Specifies the
IP address.
Destination Interface
Possible Settings: Use_Internal_Route, Port-n, Net1-FR1, DSX-1
Default Setting: Use_Internal_Route
Specifies the routing method or destination interface for the ping.
Use_Internal_Route – When choosing which interface to send the ping, the unit first
consults its routing table. If the address or subnet does not appear in the routing table, the
ping will be sent to the Default IP Destination, if defined. (See Configuring Node IP
Information in the iMarc SLV Configuration Reference.)
Port-n, Net1-FR1, DSX-1 – The ping is sent out the specified destination regardless of
the internal route configuration.
DLCI
Possible Settings: 16–1007
Default Setting: [Lowest assigned DLCI on the selected interface]
Specifies the DLCI to be used for the ping.
If the DLCI is configured on a Virtual Channel Connection (VCC), the VCI and VPI are
displayed next to the DLCI.
Display Conditions – This setting does not appear when Destination Interface is set to
Use_Internal_Route.
16–1007 – Specifies the DLCI.
EDLCI
Possible Settings: 0
Default Setting: 0
Specifies the EDLCI to be used for the ping.
Display Conditions – This setting does not appear when Destination Interface is set to
Use_Internal_Route, and then appears only if the specified DLCI is multiplexed.
0 – Specifies the EDLCI. The field cannot be modified.
9000-A2-GB33-30
October 2003
5-49
5. Troubleshooting
Table 5-5.
Ping Options (2 of 3)
Source IP Address
Available Settings: Automatic, Special
Default Setting: Automatic
Specifies the source IP address to be identified with the ping.
Display Conditions – This setting does not appear when Destination Interface is set to
Use_Internal_Route.
Automatic – The source IP address is:
– The interface IP address, if one exists, else
– The node IP address if one exists, else
– The first available address in the address table
Special – The entered IP address is shown as the source. When Special is specified, and
additional field is displayed that allows you to enter an IP address
000.000.000.001–126.255.255.255, or 128.000.000.000–223.255.255.255.
Encapsulation
Available Settings: Routed
Default Setting: Routed
Specifies the IP encapsulation used by the data stream. This read-only field specifies that
the IP encapsulation used is RFC 1490/RFC 2427 routed Network Level Protocol
IDentifier (NLPID) encapsulation, and not SubNetwork Attachment Point (SNAP)
encapsulation.
Display Conditions – This setting does not appear when Destination Interface is set to
Use_Internal_Route.
Routed – The encapsulation is routed NLPID.
TOS Byte
Available Settings: A predefined COS ID, or a user-defined binary value 0000–1111
Default Setting: User Defined – 000000
(Release 2.1.) Specifies the TOS (Terms Of Service) byte to be used with the ping packet.
Select from COS (Class Of Service) definitions, if any exist, or specify a binary value.
When a COS definition is selected, the TOS byte value is read-only. If you select a COS
definition that has multiple COS IDs, the lowest value is used as the TOS byte. See
Configuring Class of Service Definitions in the iMarc SLV Configuration Reference.
0000–1111 – The value of the TOS byte.
Packet Size
Available Settings: 36–4096
Default Setting: 100
Specifies the size of the ping packet including the IP header (20 bytes) and the ICMP
header (8 bytes).
1–4096 – Packet size.
5-50
October 2003
9000-A2-GB33-30
5. Troubleshooting
Table 5-5.
Ping Options (3 of 3)
Iteration Count
Available Settings: 1–999999
Default Setting: 5
Specifies the number of pings to send.
1–999999 – Number of pings.
Inter-Ping Delay
Available Settings: 1–900
Default Setting: 1
Specifies, in seconds, the amount of time to wait between pings.
1–900 – The ping wait time.
Response Timeout
Available Settings: 1–60
Default Setting: 2
Specifies the amount of time, in seconds, to wait before a host that has not responded to a
ping is declared unreachable.
1–60 – The response timeout period.
When the ping has completed normally, timed out, or been stopped using the Stop
command, informational fields are displayed as shown in Table 5-6, Ping
Responses.
Table 5-6.
Ping Responses (1 of 2)
Field
Status
Possible Values
Description
„
„
„
„
„
„
„
„
9000-A2-GB33-30
In Progress
Alive
Destination
Unreachable
Ping Timed Out
No route in this
device
„
„
Ping has been sent.
Ping was successful.
The host could not be reached. See
RFC 792 for possible causes.
There was no response in the period
specified in Response Timeout.
The IP address is not in the routing
table, and no Default IP Destination is
configured.
Ping Loss Ratio (%)
0–100
The ratio of pings received to pings
transmitted.
Pings Transmitted
1–999999
The number of pings transmitted.
Pings Received
1–999999
The number of pings received.
Pings Lost
1–999999
The number of pings transmitted less the
number of pings received.
October 2003
5-51
5. Troubleshooting
Table 5-6.
5-52
Ping Responses (2 of 2)
Field
Possible Values
Description
Current Roundtrip
Delay
„
„
„
„
Minimum Roundtrip
Delay
„
„
Maximum Roundtrip
Delay
„
„
Average Roundtrip
Delay
„
„
0
1–9999
0
1–9999
0
1–9999
0
1–9999
October 2003
„
„
„
„
„
„
No measurement exists.
The time in milliseconds that it took to
complete the latest ping.
No measurement exists.
The least time in milliseconds that it
took to complete a ping during this test.
No measurement exists.
The most time in milliseconds that it
took to complete a ping during this test.
No measurement exists.
The average time in milliseconds that it
took to complete a ping during this test.
9000-A2-GB33-30
5. Troubleshooting
IP Ping Test – Procedure 1
Procedure
To ping any far-end iMarc unit:
1. Select the IP Ping test.
Main Menu→Test→IP Ping
2. Enter the IP Address of the device the ping is being sent to, then select Start.
NOTE:
If the iMarc unit has just initialized, or the far-end unit has just initialized, it
may take about a minute for the units to learn the routes via the
proprietary RIP.
3. Verify the results of the IP Ping test.
— While the test is running, In Progress... appears in the Status field.
— When the test is finished, Alive should appear as the Status. If any
other message is displayed, additional testing is required.
9000-A2-GB33-30
October 2003
5-53
5. Troubleshooting
IP Ping Test – Procedure 2
Procedure
To ping the NMS at the central site:
1. Verify that the central site NMS has the iMarc unit’s IP address in its routing
table so it can communicate with the iMarc unit.
2. Verify that the central site NMS’s router has the iMarc unit’s IP address in its
routing table so it can communicate with the iMarc unit.
3. Verify that the central site NMS has been configured as an SNMP Trap
Manager if the router is to route data, so a route has been configured within
the iMarc unit.
Main Menu→Configuration→Management and Communication→
SNMP Traps
Or, for a local DLCI between the central site iMarc unit and its router, verify
that a Default IP Destination route has been configured.
Main Menu→Configuration→Management and Communication→
Node IP→Default IP Destination
Configure both SNMP Traps and a Default IP Destination when PVC
Multiplexing is used, as when using the Auto-Configuration feature.
4. Select the IP Ping test.
Main Menu→Test→IP Ping
5. Enter the IP Address of the central site NMS, then select Start.
6. Verify the results of the IP Ping test.
— While the test is running, In Progress... appears in the Status field.
— When the test is finished, Alive should appear as the Status. If any
other message is displayed, additional testing is required.
Lamp Test
The iMarc unit supports a Lamp Test to verify that all LEDs are lighting and
functioning properly. All LEDs flash or blink on and off at the same time every 1/2
second during execution of the test. When the test is stopped, the LEDs are
restored to their normal condition.
Main Menu→Test→Lamp Test
If the Test Timeout configuration option is enabled and a Test Duration is set, the
Lamp Test stops when the test duration expires. See Test Timeout Feature on
page 5-20, for additional information.
5-54
October 2003
9000-A2-GB33-30
5. Troubleshooting
Telnet
The Telnet feature allows you to initiate a Telnet session with a Telnet server on an
IP aware device. Telnet is available with firmware release 2.1 and above:
Control→Telnet
Telnet Example
main/control/telnet
Device Name: Node A
9720
09/12/2002 13:37
TELNET
Target IP Address:
000.000.000.000 Clear
Destination Interface: Net1-FR1
DLCI: 1002
--------------------------------------------------Start
Escape Character is Shift-Ctrl-6 x
Status: Idle
-------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu
MainMenu
Exit
PgUp
PgDn
Refresh
Procedure
To initiate a Telnet session from the iMarc device:
1. Enter an IP address. A subnet broadcast address is not valid.
Clicking on Clear resets the IP address to 000.000.000.000.
2. Select Use_Internal_Route, or select a destination interface (Net1-FR1,
Port-1, or DSX-1).
3. Enter a DLCI, or, for ATM links, a VPI and VCI.
4. Click on Start. The prompt changes to Stop and the Telnet session is initiated.
5. The outbound data path is monitored for Shift-Ctrl-6 x (the Shift key pressed
simultaneously with the Ctrl key and the 6 key, followed by an x). When you
type the escape secquence, the Telnet session is ended.
9000-A2-GB33-30
October 2003
5-55
5. Troubleshooting
5-56
October 2003
9000-A2-GB33-30
Index
Numerics
511
test pattern, 5-44
55 hexadecimal
test pattern, 5-25
9123
faceplate, 3-4
physical tests, 5-29
9126
faceplate, 3-5
physical tests, 5-29
9128
faceplate, 3-6
physical tests, 5-29
9520
faceplate, 3-7
physical tests, 5-38
power module LEDs, 3-19
9520-ILM
faceplate, 3-8
physical tests, 5-38
power module LEDs, 3-19
9623
faceplate, 3-9
physical tests, 5-42
9626
faceplate, 3-9
physical tests, 5-42
9720
faceplate, 3-10
physical tests, 5-46
9783
faceplate, 3-11
Network ATM Loopback, 5-27
physical tests, 5-46
9783 Router
faceplate, 3-12
9788
Network ATM Loopback, 5-27
physical tests, 5-46
9788 Router
faceplate, 3-12
9820-2M
faceplate, 3-13
physical tests, 5-47
9000-A2-GB33-30
9820-45M
faceplate, 3-14
physical tests, 5-47
power module LEDs, 3-19
9820-8M
faceplate, 3-13
physical tests, 5-47
A
aborting tests, 5-22
Access
controlling CLI, 2-14
Dial-In, 2-4
to another device, 4-2
Access Level
assigning, 2-10
changing, 2-15
CLI command modes, 2-14
effect on screen contents, 1-9
login record, 2-12
NMS, 2-11
on screen, 1-4
activating Modem PassThru, 4-2
Administrator
changing access levels, 2-15
CLI Access Level, 2-14
AIS
alarm condition, 5-7
at DSX-1, 3-32
at ISDN PRI, 3-32
at Network, 3-32
at T3 User, 3-32
LED, 3-18
status, data port, 3-23
status, network, 3-21
Alarm
conditions, 5-2, 5-7
Fail, 3-20
LED, 3-15
turning off relay, 4-13
ALM LED, 3-15, 3-17, 3-20, 3-22
only LED on, 5-15
Alternate Software Revision, 3-2
ANSI T1.403 Annex B FT1 Channel Loopback, 5-35
Application Monitoring, 3-64
arrow keys, 1-6, 1-10
assigning community names and access levels, 2-10
October 2003
IN-1
Index
ATM
Loopback on the network interface, 5-27
performance statistics, 3-76
status, 3-21
Auto-Configuration
Active, 3-32
menu branch, 1-4
B
back door access when locked out, 5-4
Backspace, 1-6, 1-10
Back-to-Back Mode Active, 3-32
Backup
Active, 3-32
manually forcing, 4-4
verifying setup, 4-6
BECNs Received, 3-74
BKP LED, 3-15, 3-20
blank field value, 1-9
branches of menu, 1-4
C
Call Status, 3-52
Caller
ID, 2-5
Identification Method, 2-5
canceling Modem PassThru, 4-2
Cause Value messages, 3-54
CCV, Network DS3 Line, 3-84
changing
Access Levels, 2-15
software release, 4-11
Channel Loopback, 5-35
Character matching, 1-9
CIR
statistics, 3-66
circuit multiplexed PVCs, 5-26
Class of Service performance statistics, 3-72
Clearing statistics, 3-63
CLI
keyboard keys, 1-10
limiting access, 2-14
CNIS, 2-5
Community Name, assigning, 2-10
Configuration
Auto, Active, 3-32
menu branch, 1-4
Connectivity test, 5-26
IN-2
Control
keys, 1-6
leads
description, 3-20
displaying, 3-4
menu branch, 1-4
Telnet, 5-55
controlling
asynchronous terminal access, 2-2
dial-in access, 2-4
FTP access, 2-6
ISDN access, 2-5
SNMP access, 2-9
Telnet access, 2-6
copyrights, A
COS performance statistics, 3-72
CRC errors, 3-75
creating a login, 2-12
Cross Pair Detected, 5-7
CSES, Network DS3 Line, 3-84
CSU Loopback, 5-43
Ctrl keys, 1-6
CTS
down to Port Device, 3-33
down to Port Device alarm, 5-7
current software revision, 3-2
D
Data
Channel Loopback, 3-33, 5-35
Mode, control lead, 3-22
selection criteria, 1-9
uploading SLV and packet capture, 4-12
DBM
BRI Card Failed, 3-33, 5-7
call performance statistics, 3-87
changing BRI software, 4-10
Download Required, 3-33
forcing backup and placing a call, 4-4
hardware revision, 3-3
Health and Status messages, 3-32
interface status, 3-50
ISDN problems, 5-18
most recent cause values, 3-54
test status messages, 3-39
tests, 5-20
verifying setup, 4-6
DCLB, 5-35
DDS Line statistics, 3-82
Delete key, 1-6, 1-10
deleting
a login, 2-13
statistics, 3-63
October 2003
9000-A2-GB33-30
Index
Device
messages, 3-24
troubleshooting problems, 5-15
Dial-In Access, controlling, 2-4
disabling
SNMP access, 2-9
system alarm relay, 4-13
Disconnect Modem, 4-3
displaying
identity information, 3-2
LEDs and control leads, 3-4
DLCI
Down, 3-33, 5-7
interface status, 3-42
LMI-reported status, 3-44
statistics, 3-70
status, 3-41
downloading
determining when completed, 4-11
software, 4-7, 4-9
DSL statistics, 3-86
DSR
LED, 3-17
status, data port, 3-23
status, network, 3-22
DSU Loopback, 5-43
DSX-1
LEDs, 3-17
timeslot assignments, 3-49
DTE Loopback, 5-33, 5-41, 5-45–5-47
DTLB, 5-33, 5-41, 5-45–5-47
DTR
down, 5-7
down from Port-1 Device, 3-33
LED, 3-17
status, data port, 3-23
status, network, 3-22
E
EER
at ISDN PRI, 3-33
at Network, 3-33, 5-8
EIR statistics, 3-67
ending
a session, 1-3
a test, 5-21
Enter (Return) key, 1-6
Errors, frame relay statistics, 3-74
Esc key, 1-6
ESF Line statistics, 3-79
9000-A2-GB33-30
Ethernet
Link Down, 3-33, 5-8
performance statistics, 3-88
port MAC address, 3-2
Event Log Trap, 3-89, 5-15
Excessive BPVs status, 5-8
External network loopback, 5-43
F
faceplates, 3-4
Fan
assembly
cleaning, 4-14
replacing, 4-15
failure, 5-8
status, 3-20
FECNs Received, 3-73
field is blank, 1-9
file transfer, 4-7
FR Mode LED, 3-15
Frame Relay
Mode LED, 3-15
statistics, 3-72
troubleshooting PVC problems, 5-17
front panel assembly
cleaning, 4-14
replacing, 4-15
FTP, 4-7
file transfers, 4-7
initiating a session, 4-7
limiting access, 2-6–2-7
retrieving syslog.dat, 4-12
retrieving traplog.dat, 4-12
Session, 2-7
function keys, 1-5, 1-7
G
G.shdsl statistics, 3-86
Gateway, 3-60
General
LEDs, 3-20
General LEDs, 3-15, 3-20–3-21
glossary, v
H
hardware revision
DBM, 3-3
NAM, 3-2
HDLC errors
frame relay statistics, 3-75
Health and Status, 5-2
messages, 3-32
October 2003
IN-3
Index
Hop, 3-60
hyperlink to more information, viii
I
ICMP, IP routing table type, 3-61
Identity, displaying, 3-2
initiating a test, 5-21
interface
DBM status, 3-50
status, 2-5
user, 1-1
Internal Modem Failed, 5-8
Internal Network Loopback, 5-43
Invalid
ID, 3-51
Local Number, 3-51
IP
address of NMS, 2-11
addressing, limiting SNMP access with, 2-11
Path Connection Status, 3-43
ping test, 5-48
Routing Table, 3-60
SLV performance statistics for IP Enabled DLCI,
3-68
IP Enabled DLCI performance statistics, 3-72
ISDN
Active, 3-34
BRI DBM troubleshooting problems, 5-18
Cause Value Messages, 3-54
controlling access, 2-5
DBM operation, 4-4
Link Profile Disabled, 3-34
Link Profile Invalid, 3-34, 5-9
Network Failed, 3-34, 5-9
PRI DBM LEDs, 3-17
updating software, 4-10
verifying line, 4-6
K
keyboard keys, 1-6
keys
CLI navigation, 1-10
keyboard, 1-6
screen function, 1-5, 1-7
Leased Line
active, 3-34
LEDs, 5-2
AIS, 3-18
Alarm, 3-15, 3-17
ALM, 3-15, 3-17
BKP, 3-15
descriptions, 3-15
displaying, 3-4
DSR, 3-17
DSX-1, 3-17
DTR, 3-17
FR Mode, 3-15
General, 3-15, 3-20
ISDN PRI DBM, 3-17
LOS, 3-18
Network, 3-15–3-17, 3-21–3-22
not lit, 5-15
OK, 3-15, 3-17
OOF, 3-17–3-18
Port, 3-17, 3-22–3-23
SIG, 3-17
System, 3-15
test, 5-54
TST, 3-15
YEL, 3-18
LES, Network DS3 Line, 3-84
limiting
asynchronous terminal access, 2-2
dial-in access, 2-4
FTP access, 2-7
SNMP access, 2-9
through IP addresses, 2-11
Telnet access, 2-6
Line
ISDN Status, 3-51
Loopback, 5-30, 5-34, 5-36, 5-40
Link
Down Administratively, 3-34
frame relay statistics, 3-73
Layer Down, 3-34
Operating Mode, 3-52
Profile Disabled, 3-34, 5-8
troubleshooting management, 5-5
LLB, 5-30, 5-34, 5-36, 5-40
Active, 3-34
L
Lamp Test, 3-39, 5-54
last reset, 3-31
Latching Loopback, 5-44
Latency Exceeded, 3-34, 5-9
LCD status, network, 3-22
LCV, Network DS3 Line, 3-84
IN-4
October 2003
9000-A2-GB33-30
Index
LMI
Discovery in Progress, 3-34
Down, 3-34, 5-10
frame relay statistics, 3-75
packet utility, 5-5
status display, 3-21
total errors, 3-75
trace log, 5-6
uploading packet capture data, 4-12
locked out, 2-3, 2-12, 5-4
LOF
at Network, 3-34
at T3 User Port, 3-34, 5-10
Log
LMI Trace, 5-6
Trap Event, 3-89
Login, 2-1
creating, 2-12
ID, 2-12
logging in, 1-2
logging out, 1-3
modifying and deleting, 2-13
Required, 2-3, 2-6–2-7
Logout, 1-3
Loop Attenuation Defect, 3-35
Loopback
ATM, 5-27
CSU, 5-43
Data Channel, 5-35
DSU, 5-43
DTE, 5-33, 5-41, 5-45–5-47
latching, 5-44
Line, 5-30, 5-40
Payload, 5-31
PVC, 5-24
Remote, 5-34, 5-36
Repeater, 5-32
V.54, 5-35
LOS
at DSX-1, 3-35, 5-11
at ISDN PRI, 3-35
at Network, 3-35, 5-11
at T3 User, 5-11
LED, 3-18
status, data port, 3-23
status, network, 3-21–3-22
M
MAC address, Ethernet port, 3-2
Main Menu, 1-4
maintenance, 4-1
making input selections, 1-9
Management, troubleshooting link, 5-5
9000-A2-GB33-30
menu
branches, 1-4
main, 1-4
path, 1-5
selecting entry from, 1-8
messages
area at bottom of screen, 3-24
Cause Values, 3-54
Device, 3-24
Health and Status, 3-32
Self-Test Results, 3-31
system, 1-5
System and Test Status, 3-31
Test Status
DBM, 3-39
MIB access, 2-10
Mode
CLI command, 2-14
Operating, 3-52
Test, 3-15, 3-20
model number, 1-5
modem
failed alarm, 5-8
Health and Status messages, 3-32
manually disconnecting, 4-3
operation, 4-2
PassThru feature, 4-2
verifying setup and operation, 4-3
modifying
a login, 2-13
Access Levels, 2-15
Monitor
511 test pattern, 5-45
Pattern, 5-25
monitoring
iMarc unit, 3-30
LEDs and control leads, 3-4
Multilink Constituent Link, 3-52
Multiplexed PVCs, 5-26
N
Name 1 or 2 access, 2-10
navigating the screens, 1-6
navigation keys, 1-10
Network
ATM Loopback, 5-27
Com Link Down, 3-36, 5-11
CSU or external Loopback, 5-43
DSU or internal loopback, 5-43
Initiated ISDN BRI Test Active, 3-36
LEDs, 3-15–3-17, 3-21–3-22
physical tests, 5-46
timeslot assignments, 3-48
October 2003
IN-5
Index
NMS
IP Address, 2-11
IP Validation, 2-11
No Signal status, 5-11
Number of Managers, 2-11
O
OK LED, 3-15, 3-17, 3-20
Ethernet, 3-23
IDSL Network, 3-21
Port, 3-22
OOF
at DSX-1, 3-36, 5-11
at ISDN PRI, 3-36
at Network, 5-12
LED, 3-17–3-18
status, data port, 3-23
status, network, 3-21–3-22
OOS, 5-12
operation, 1-1, 4-1
Operator, CLI Access Level, 2-14
organization of this document, v
Out Of Frame
at DSX-1, 5-11
at Network, 5-12
Out Of Service, 5-12
Out of Sync, 5-45
message, 5-17, 5-25
P
packet capture
uploading data, 4-12
utility, 5-5
PassThru, modem feature, 4-2
Password, 2-12
patents, A
path connection status, 3-43
path down, 5-12
pattern
send/monitor interior, 5-25
tests, 5-37
Payload Loopback, 5-31
PCV, Network DS3 Line, 3-84
performance statistics, 5-2
application, 3-64
ATM, 3-76
clearing, 3-63
Ethernet, 3-88
for Class of Service, 3-72
for DLCI, 3-70
for IP Enabled DLCI, 3-68
Frame Relay, 3-73
menu, 3-62
T3 network, 3-83
VCC, 3-77
xDSL Line, 3-86
PES, Network DS3 Line, 3-84
physical
tests, 5-29, 5-38, 5-42, 5-47
tests, network, 5-46
ping
IP ping test options, 5-49
responses, 5-51
test, 5-48
placing a test call, 4-5
PLB, 5-31
Port
Access Level, 2-3
LEDs, 3-17, 3-22–3-23
Power Module
LEDs, 3-19
replacing, 4-16
status display, 3-20
troubleshooting, 3-19
Power Supply Failure, 5-12
Power Supply/Fan Failure message, 3-36
PRI DBM LEDs, 3-17
Primary and Secondary Clocks Failed, 5-13
Primary Clock
Failed, 3-37
Primary Clock Failed, 3-37, 5-13
problem indicators, 5-2
product-related documents, vi
Proprietary Caller Identification Method, 2-5
PSES, Network DS3 Line, 3-84
PVC
connection status, 3-43, 3-45
Loopback, 5-24
tests, 5-23
troubleshooting problems, 5-17
R
RD
status, data port, 3-23
status, network, 3-21
remote loopbacks, 5-34, 5-36
IN-6
October 2003
9000-A2-GB33-30
Index
Repeater Loopback, 5-32
reset date and time, 3-31
resetting
statistics, 3-63
the unit, 5-3
unit default configuration options, 5-4
restoring communication with improperly configured unit,
5-4
retrieving statistics, 4-12
Return (Enter) key, 1-6
revision
level, 3-2
software and hardware, 3-3
right arrow key, 1-6
RIP, 3-61
RLB, 5-32
router
assist feature, 4-2
controlling CLI access, 2-14
Routing, IP table, 3-60
S
screen
area, 1-5
function keys area, 1-5
how to navigate, 1-6
scrolling through valid selections, 1-9
Secondary Clock
Failed, 3-37
Secondary Clock Failed, 3-37, 5-13
security, 1-2, 2-1
effect on screen contents, 1-9
SEFS, Network DS3 Line, 3-84
selecting
a field, 1-9
entry from a menu, 1-8
Self-Test Results messages, 3-31
Send
511 test pattern, 5-44
and monitor test pattern, 5-37
Pattern, 5-25
serial number, 3-2
Service, A
Service Level Verification statistics, 3-64
Session
Access Level, 2-6, 2-8
ending, 1-3
starting, 1-2
Telnet to remote device, 5-55
SHDSL
statistics, 3-86
tests, 5-46
9000-A2-GB33-30
SIG
LED, 3-17
status, network, 3-22
SLV
Latency Exceeded, 5-13
performance statistics, 3-64
performance statistics for IP Enabled DLCI, 3-68
Timeout, 5-14
SNMP
assigning community names and access levels,
2-10
limiting access, 2-9, 2-11
Management, 2-9
trap event log, 3-89, 5-15
traps supported, 5-2
SNR Margin Threshold Exceeded, 3-37
software
changing, 4-11
ISDN BRI DBM, 4-10
downloading, 4-7
revision
DBM, 3-3
NAM, 3-2
Spacebar, 1-6
starting
a session, 1-2
a test, 5-21
statistics, 3-1, 3-62
ATM, 3-76
DBM call performance, 3-87
DDS line, 3-82
ESF line, 3-79
Ethernet, 3-88
selecting performance intervals for display, 3-79,
3-83
T3 network, 3-83
uploading to an NMS, 4-12
VCC, 3-77
xDSL Line, 3-86
Status, 3-1
Call, 3-52
DBM interface, 3-50
DLCI, 3-41
Health and Status screen, 3-32
ISDN Line, 3-51
LED, 3-15
LEDs, 3-20
menu branch, 1-4, 3-30
Network DS3 Line, 3-85
ping, 5-51
PVC connection, 3-45, 3-47
test messages, 3-39
timeslot assignment, 3-48
ways of determining, 3-1
October 2003
IN-7
Index
stopping a test, 5-21
Suboptimal Link Rate, 3-38, 5-14
suggestions, user documentation, A
switching
between screen areas, 1-8
to new software, 4-11
System
Alarm Relay, 4-13
and test status messages, 3-31
displaying information, 3-2
last reset, 3-31
LEDs, 3-15
Log, retrieving with FTP, 4-12
messages, 1-5
Name, Contact, and Location, 3-2
T
T3 Network Line Performance Statistics, 3-83
Tab key, 1-6
TCP, 4-7
TD
status, data port, 3-23
status, network, 3-21
Telnet
from iMarc device, 5-55
limiting access, 2-6
session, 2-6
to remote device, 5-55
Test
Call, 5-26
Call Active, 3-38
menu branch, 1-4
Mode, 3-20
Mode LED, 3-15
Status messages
DBM, 3-39
IN-8
Tests
aborting, 5-22
available, 5-19
Connectivity, 5-26
Data Channel Loopback, 5-35
DBM, 5-20
DTE Loopback, 5-33, 5-41, 5-45–5-47
IP Ping, 5-48
ISDN BRI, 3-36
Lamp, 5-54
Line Loopback, 5-30, 5-40
Network ATM Loopback, 5-27
Network Physical, 5-46
pattern, 5-37
Payload Loopback, 5-31
physical, 5-29, 5-38, 5-42, 5-47
ping, 5-48
PVC, 5-23
PVC Loopback, 5-24
Remote Line Loopback, 5-34, 5-36
Repeater Loopback, 5-32
Send/Monitor Pattern, 5-25
SHDSL, 5-46
starting or stopping, 5-21
Telnet to remote device, 5-55
Test Call, 5-26
Timeout, 5-20
Timeout, for tests, 5-20
timeslot assignments
DSX-1, 3-49
network, 3-48
status, 3-48
Timeslot Discovery in Progress, 3-38
TOS Byte, 5-50
Total Errors, 3-74
Trace Log LMI, 5-6
trademarks, A
Training, A
control lead, 3-22
transferring data, 4-12
Trap Event Log, 3-89, 5-15
retrieving with FTP, 4-12
Traps, supported, 5-2
troubleshooting, 5-1
device problems, 5-15
frame relay PVC problems, 5-17
ISDN BRI DBM problems, 5-18
management link, 5-5
power supply problems, 3-19
tables, 5-15
TS Access Management Link
Access Level, 2-8
limiting Telnet access, 2-6, 2-8
TST LED, 3-15, 3-20
October 2003
9000-A2-GB33-30
Index
TTL, 3-61
turning off system alarm relay, 4-13
Two Level-1 Users Accessing Device, 3-38, 5-14
U
UAS, Network DS3 Line, 3-84
upgrade
ISDN BRI DBM, 4-10
system software, 4-9
uploading data, 4-12
user interface, 1-1
cannot be accessed, 5-16
restoring access, 5-4
V
V.54 Loopback, 3-33, 3-39, 5-35
VCC performance statistics, 3-77
verifying
DBM setup, 4-6
ISDN lines, 4-6
modem setup, 4-3
9000-A2-GB33-30
viewing packet capture results, 5-6
W
warranty, A
Web-site
access to documentation, vi
glossary, v
X
xDSL Line performance statistics, 3-86
Y
YEL LED, 3-18
Yellow
alarm status, data port, 3-23
alarm status, network, 3-21
at DSX-1, 5-14
at DSX-1 or Network, 3-38
at ISDN PRI, 3-38
at Network, 5-14
at T3 User, 5-14
October 2003
IN-9
Index
IN-10
October 2003
9000-A2-GB33-30
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising