OpenLane SLM Reports Reference Guide -...

OpenLane® SLMReports Reference Guide

Document No. 7800-A2-GB30-10

April 2001

A April 2001 7800-A2-GB30-10

Copyright © 2001 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 [email protected]. 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. 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.

7800-A2-GB30-10 April 2001 i

Contents

About This Guide

� Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . iii

� Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

1 Generating Reports

� OpenLane Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

� Preparing the OpenLane System for Reports . . . . . . . . . . . . . . . . . . . 1-1

� Network Inventory and Connectivity Reports . . . . . . . . . . . . . . . . . . . . 1-2

Inventory Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Connectivity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

� Scheduled Reports Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Report Titles by Report Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

� Generating Scheduled FrameSaver SLV Reports . . . . . . . . . . . . . . . . 1-4

Automating the Generation of Scheduled Reports . . . . . . . . . . . . 1-5

Using Cron Under Solaris to Automate Reports . . . . . . . . . . . . . . 1-5

� Using AT under Windows to Automate Reports. . . . . . . . . . . . . . . . . . 1-6

� Accessing Scheduled Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2 Sample Reports and Descriptions

� Help Files and Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Overview of OpenLane Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

FrameSaver Device Inventory Report . . . . . . . . . . . . . . . . . . . . . . 2-4

FrameSaver and CSU/DSU Device Inventory Report . . . . . . . . . . 2-5

DSLAM Inventory Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

DSLAM Slot Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

DSLAM Slot and Port Inventory Report . . . . . . . . . . . . . . . . . . . . . 2-12

Network Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Network Connectivity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Frame Delivery Ratio Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Frame Transfer Delay Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Availability Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Network Capacity and Throughout (Tx) Detail. . . . . . . . . . . . . . . . 2-24

Network Capacity and Throughput (Rx) Detail . . . . . . . . . . . . . . . 2-26

Contents

ii April 2001 7800-A2-GB30-10

PVC Tx Activity (by % CIR) Detail . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

Protocol Distribution Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Top 6 IP Communicator Distribution . . . . . . . . . . . . . . . . . . . . . . . 2-32

PVC Congestion Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

DTE Port Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Network Port Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Port Trend Analysis (Transmitted Bits) . . . . . . . . . . . . . . . . . . . . . 2-40

Port Trend Analysis (Received Bits) . . . . . . . . . . . . . . . . . . . . . . . 2-42

PVC Trend Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

SLV Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

SLV Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

15-Minute Raw Throughput and Latency Data . . . . . . . . . . . . . . . 2-50

Site Availability Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52

Glossary

Index

7800-A2-GB30-10 April 2001 iii

About This Guide

Document Purpose and Intended Audience

This guide contains text and examples from the OpenLane Service Level Management online Help system. It is intended as a demonstration aid and reference on the subject of OpenLane SLM reports for the use of current and prospective users of OpenLane.

Document Summary

A master glossary of terms and acronyms used in Paradyne documents is available online at www.paradyne.com. Select Library → Technical Manuals → Technical Glossary.

Section Description

Chapter 1, Generating Reports Describes how to create and view OpenLane reports.

Chapter 2, Sample Reports and Descriptions

Contains screen prints from the OpenLane Help system.

Glossary Defines terms and acronyms used in this document.

Index Lists key terms, concepts, and sections in alphabetical order.

About This Guide

iv April 2001 7800-A2-GB30-10

7800-A2-GB30-10 April 2001 1-1

1Generating Reports

OpenLane Reports

OpenLane reports are of three basic types:

� Network Inventory Reports

� Network Connectivity Report

� FrameSaver SLV (Network Service) Reports

The Network Inventory and Connectivity Reports are created on demand. FrameSaver SLV reports may be created on demand or optionally scheduled for automated generation.

Preparing the OpenLane System for Reports

Before generating reports, you must:

1. Add all devices to the Network Navigator database.

If data collection was set up on a device and the device is then deleted from Network Navigator, the display for the PVCs and interfaces starts with Old. There also will be no remote device information available and NA (Not Available) will appear for some fields.

2. Create Customer Profiles.

3. Administer Data Collection.

See the OpenLane online Help for information.

1. Generating Reports

1-2 April 2001 7800-A2-GB30-10

Network Inventory and Connectivity Reports

There are four Inventory Reports and one Connectivity Report.

Inventory Reports

To generate a Network Inventory Report, click on Network Inventory Report on the initial customer screen. The following options are displayed:

� FrameSaver Device Inventory Report

� DSLAM Inventory Report

� DSLAM Slot Inventory Report

� DSLAM Slot and Port Inventory Report

Select a report type and click on OK to produce the report in a new window.

Connectivity Report

To generate a Network Connectivity Report, click on Network Connectivity Report on the initial customer screen. The report is displayed in a new window.


7800-A2-GB30-10 April 2001 1-3

Scheduled Reports Summary

FrameSaver SLV Reports are set up by an administrator from the Report Scheduler page. After login, select Customer Profiles from the OpenLane Administration Main Menu. Enter a new Customer ID or select a Customer ID. From the Customer Profile Administration page, select Modify scheduled reports.

The following reports are available as daily, weekly, or monthly and are based on the devices assigned to the Customer ID.

Report Titles by Report Code

1. Frame Delivery Ratio Detail

2. Frame Transfer Delay Detail

3. Availability Detail

4. Network Capacity and Throughput (Tx) Detail

5. Network Capacity and Throughput (Rx) Detail

6. PVC Tx Activity (by % CIR) Detail

7. Protocol Distribution Detail

8. Top 6 IP Communicator Distribution

9. PVC Congestion Detail

10. DTE Port Errors

11. Network Port Errors

12. Port Trend Analysis (Tx)

13. Port Trend Analysis (Rx)

14. PVC Trend Analysis

15. SLV Detail

16. SLV Summary

17. 15-Minute Raw Throughput and Latency Data

18. Site Availability

Scheduled reports can be set up to include and exclude specified periods:

� The Summary Period defines the hours and days to be included in report summary totals.

� Maintenance Periods are set time slots that are excluded from scheduled FrameSaver SLV report calculations. For example, a Maintenance Period can be defined to omit statistics during a weekly time period set aside for regular maintenance.

� Exception periods are time slots that are excluded from scheduled FrameSaver SLV report calculations only once. For example, an Exception Period can be defined to omit statistics during a period a link was known to be down due to a power outage.


1-4 April 2001 7800-A2-GB30-10

Generating Scheduled FrameSaver SLV Reports

To generate scheduled reports, run the processreports function of OLCmd from the main directory where OpenLane was installed.

ProcessReports can generate reports based on a date range. This allows several days’ worth of reports or more to be generated at once. Reports can be generated for one customer, a list of customers, or all customers.

Format:

UNIX:OLCmd processreports ' [-date date] [-enddate enddate][-customer customer_id] [-customerlist list_file] '

Windows:OLCmd.bat processreports " [-date date] [-enddate enddate] [-customer customer_id] [-customerlist list_file] "

Where:

Example:

The following command generates scheduled reports for all customers:

OLCmd processreports

The following command generates scheduled reports for customer Exact_Corp using 13 May 2000 as a start date:

OLCmd processreports -date 05/13/2001 -customer Exact_Corp

The following command generates scheduled reports for a list of customers in a file called la_west.txt:

OLCmd processreports -customerlist la_west.txt

-date date Is the optional starting date of the reports. If -date is not specified, the current date is used.

-enddate enddate Is the optional end date of the reports, creating a date range between -date and -enddate. If -enddate is not specified, there is no date range.

-customer customer_id Is the optional customer for whom reports are to be generated. If neither -customer nor -customerlist is specified, scheduled reports for all customers are generated.

-customerlist list_file Is the optional list of customers for whom reports are to be generated. list_file is the pathname of a text file with one Customer ID per line.


7800-A2-GB30-10 April 2001 1-5

Automating the Generation of Scheduled Reports

To automate running scheduled reports, use the scheduler for the platform where OpenLane was installed. This is typically cron for Solaris platforms and at for Windows NT. The scheduler runs the processreports function of OLCmd at the times and/or intervals specified by the scheduler. It is recommended that the scheduler be run twice a day, which allows daily reports to be generated reliably every day.

Using Cron Under Solaris to Automate Reports

Procedure

1. Using a text editor, create a shell script that contains the commands you would ordinarily use to generate reports. For example, to create reports for all customers, add the following commands:

cd /opt/pdn/OpenLane

./OLCmd processreports

2. Save the script. In this example, the script is called MyReports.sh.

3. Make the file executable:

chmod 777 MyReports.sh

4. Open the crontab for edit:

crontab -e

5. Add a line to the end of the crontab file for the shell script. Each line of the crontab consists of six fields:

— Minute (0–59)

— Hour (0–23)

— Day of Month (1–31)

— Month (1–12)

— Day of Week (0–6, where 0 is Sunday and 6 is Saturday)

— Command to be executed

Lists, ranges, and asterisks (meaning all legal values) are allowed.

For example, to execute MyReports.sh every weekday at midnight and noon, a correct crontab entry is:

0 0,12 * * 1-5 /opt/pdn/OpenLane/MyReports.sh


1-6 April 2001 7800-A2-GB30-10

Using AT under Windows to Automate Reports

Procedure

1. Using a text editor, create a batch script that contains the commands you would ordinarily use to generate reports. For example, to create reports for all customers, add the following commands:

c:

cd \opt\pdn\OpenLane

OLCmd processreports

2. Save the script. In this example, the script is called Myreports.bat.

3. Open an MS-DOS prompt window. Type the AT command required to schedule your batch script. The AT command has the following fields:

— \\computername – A remote host on which the command will be executed (optional).

— ID – An identification number for the scheduled command (optional).

— /delete – Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled.

— /yes – Used with cancel all jobs command when no further confirmation is desired.

— time – Specifies the time when command is to run.

— /interactive – Allows the job to interact with the desktop of the user who is logged on at the time the job runs.

— /every:date[,...] – Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed.

— /next:date[,...] – Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed.

— Command – Is the Windows NT command, or batch program to be run.

For example, to execute MyReports.sh every weekday at midnight and noon on the same computer as the AT command is executed, the correct commands are:

at 00:00 /every:Monday,Tuesday,Wednesday,Thursday,Friday c:\opt\pdn\OpenLane\Myreports.bat

at 12:00 /every:Monday,Tuesday,Wednesday,Thursday,Friday c:\opt\pdn\OpenLane\Myreports.bat


7800-A2-GB30-10 April 2001 1-7

Accessing Scheduled Reports

Scheduled reports can be accessed by all users from the Scheduled Network Service Reports screen. This is available from the SLV Reports menu, which is displayed when any user without Administrator authority logs in to OpenLane.

Reports can also be accessed directly on the OpenLane server. Generated scheduled reports are stored in the customer's directories. The report filenames have the following format:

CustomerId_Date_ReportCode_ReportPeriod.html for HTML reportsCustomerId_Date_ReportCode_ReportPeriod.csv for CSV reports

Where:

CustomerId is the Customer ID.

Date is the starting date of the report data, in the format: 'yyyy-mm-dd'

ReportCode is the report number.

ReportPeriod is one of the following:

d – Daily w – Weeklym – Monthly

For example, Xtelco_2001-06-05_13_m.


1-8 April 2001 7800-A2-GB30-10

7800-A2-GB30-10 April 2001 2-1

2Sample Reports and Descriptions

Help Files and ReportsThis chapter shows the Help files and sample reports provided with OpenLane. SLV reports are listed in order by report code; inventory and connectivity reports are unnumbered.

FrameSaver Device Inventory Report on page 2-4

FrameSaver and CSU/DSU Device Inventory Report on page 2-5

DSLAM Inventory Report on page 2-8

DSLAM Slot Inventory Report on page 2-10

DSLAM Slot and Port Inventory Report on page 2-12

Network Connectivity Report on page 2-16

1. Frame Delivery Ratio Detail on page 2-18

2. Frame Transfer Delay Detail on page 2-20

3. Availability Detail on page 2-22

4. Network Capacity and Throughout (Tx) Detail on page 2-24

5. Network Capacity and Throughput (Rx) Detail on page 2-26

6. PVC Tx Activity (by % CIR) Detail on page 2-28

7. Protocol Distribution Detail on page 2-30

8. Top 6 IP Communicator Distribution on page 2-32

9. PVC Congestion Detail on page 2-34

10. DTE Port Errors on page 2-36

11. Network Port Errors on page 2-38

12. Port Trend Analysis (Transmitted Bits) on page 2-40

13. Port Trend Analysis (Received Bits) on page 2-42

14. PVC Trend Analysis on page 2-44

15. SLV Detail on page 2-46

16. SLV Summary on page 2-48

17. 15-Minute Raw Throughput and Latency Data on page 2-50

18. Site Availability Detail on page 2-52

2. Sample Reports and Descriptions

2-2 April 2001 7800-A2-GB30-10

Overview of OpenLane Reports


7800-A2-GB30-10 April 2001 2-3


2-4 April 2001 7800-A2-GB30-10

FrameSaver Device Inventory Report


7800-A2-GB30-10 April 2001 2-5


2-6 April 2001 7800-A2-GB30-10

FrameSaver and CSU/DSU Device Inventory Report


7800-A2-GB30-10 April 2001 2-7


2-8 April 2001 7800-A2-GB30-10

DSLAM Inventory Report


7800-A2-GB30-10 April 2001 2-9


2-10 April 2001 7800-A2-GB30-10

DSLAM Slot Inventory Report


7800-A2-GB30-10 April 2001 2-11


2-12 April 2001 7800-A2-GB30-10

DSLAM Slot and Port Inventory Report


7800-A2-GB30-10 April 2001 2-13


2-14 April 2001 7800-A2-GB30-10

Network Inventory Report


7800-A2-GB30-10 April 2001 2-15


2-16 April 2001 7800-A2-GB30-10

Network Connectivity Report


7800-A2-GB30-10 April 2001 2-17


2-18 April 2001 7800-A2-GB30-10

Frame Delivery Ratio Detail


7800-A2-GB30-10 April 2001 2-19


2-20 April 2001 7800-A2-GB30-10

Frame Transfer Delay Detail


7800-A2-GB30-10 April 2001 2-21


2-22 April 2001 7800-A2-GB30-10

Availability Detail


7800-A2-GB30-10 April 2001 2-23


2-24 April 2001 7800-A2-GB30-10

Network Capacity and Throughout (Tx) Detail


7800-A2-GB30-10 April 2001 2-25


2-26 April 2001 7800-A2-GB30-10

Network Capacity and Throughput (Rx) Detail


7800-A2-GB30-10 April 2001 2-27


2-28 April 2001 7800-A2-GB30-10

PVC Tx Activity (by % CIR) Detail


7800-A2-GB30-10 April 2001 2-29


2-30 April 2001 7800-A2-GB30-10

Protocol Distribution Detail


7800-A2-GB30-10 April 2001 2-31


2-32 April 2001 7800-A2-GB30-10

Top 6 IP Communicator Distribution


7800-A2-GB30-10 April 2001 2-33


2-34 April 2001 7800-A2-GB30-10

PVC Congestion Detail


7800-A2-GB30-10 April 2001 2-35


2-36 April 2001 7800-A2-GB30-10

DTE Port Errors


7800-A2-GB30-10 April 2001 2-37


2-38 April 2001 7800-A2-GB30-10

Network Port Errors


7800-A2-GB30-10 April 2001 2-39


2-40 April 2001 7800-A2-GB30-10

Port Trend Analysis (Transmitted Bits)


7800-A2-GB30-10 April 2001 2-41


2-42 April 2001 7800-A2-GB30-10

Port Trend Analysis (Received Bits)


7800-A2-GB30-10 April 2001 2-43


2-44 April 2001 7800-A2-GB30-10

PVC Trend Analysis


7800-A2-GB30-10 April 2001 2-45


2-46 April 2001 7800-A2-GB30-10

SLV Detail


7800-A2-GB30-10 April 2001 2-47


2-48 April 2001 7800-A2-GB30-10

SLV Summary


7800-A2-GB30-10 April 2001 2-49


2-50 April 2001 7800-A2-GB30-10

15-Minute Raw Throughput and Latency Data


7800-A2-GB30-10 April 2001 2-51


2-52 April 2001 7800-A2-GB30-10

Site Availability Detail


7800-A2-GB30-10 April 2001 2-53


2-54 April 2001 7800-A2-GB30-10

7800-A2-GB30-10 April 2001 GL-1

Glossary

BECN Backward Explicit Congestion Notification. A bit set and forwarded by the network to notify users of data traffic congestion, sent in the opposite direction of the frame carrying the BECN indicator or bit. Outbound frames may encounter congestion and be dropped.

CIR Committed Information Rate. Less than or equal to the access rate, the CIR is used by the service provider for rate enforcement when the network allocates bandwidth. When rates exceed the CIR, frames may be discarded.

CRC Cyclic Redundancy Check. A mathematical method of confirming the integrity of received digital data.

DLCI Data Link Connection Identifier. The virtual circuit number corresponding to a particular connection between two destinations. This number is used as part of the frame relay header. The total number of DLCIs between endpoints make up the PVC. DLCIs are a local means of identifying a PVC.

DSL Digital Subscriber Line. The non-loaded, local-loop copper connection between the customer and the first node within the network.

DSLAM Digital Subscriber Line Access Multiplexer. A platform for DSL modems that provides high-speed data transmission over traditional twisted-pair wiring.

DTE Data Terminal Equipment. The equipment, such as a computer or terminal, that provides data in the form of digital signals for transmission.

EIR Excess Information Rate. In frame relay networks, the rate of transmission above the insured rate, calculated as the maximum information rate less the Committed Information Rate.

FECN Forward Explicit Congestion Notification. A bit set and forwarded by the network to notify users of data traffic congestion, sent in the same direction of the frame carrying the FECN indicator or bit. Inbound frames may encounter congestion and be dropped.

GranDSLAM A high-density DSLAM supporting a variety of DSL transport types and network services.

IP address Internet Protocol address. The address assigned to an internet host.

LMI Local Management Interface. In frame relay, the standard set of procedures and messages for link-management signaling (information exchange) between a DTE and the network.

PVC Permanent Virtual Circuit. The logical link, identified by a DLCI, used for routing frames over the network from their source to their destination.

QoS Quality of Service. In ATM, a level of service dependent on Cell Loss Ratio (CLR), Cell Transfer Delay (CTD), and Cell Delay Variation (CDV).

SLA Service Level Agreement. A contract between a frame relay service provider and a customer in which the service provider guarantees a certain level or quality of service to the customer. Level of service is defined by a set of measurable parameters, each having thresholds that are negotiated by the service provider and customer.

SLM Service Level Management. Managing and monitoring of network parameters to ensure Quality Of Service as defined in a Service Level Agreement between a network service provider and an end user. Includes monitoring, diagnostics, and reporting of critical network parameters such as availability, latency and throughput.

Glossary

GL-2 April 2001 7800-A2-GB30-10

SLV Service Level Verifier. A feature that monitors and ensures frame relay network service levels.

UNI User-Network Interface.

7800-A2-GB30-10 April 2001 IN-1

Index

Numerics15-Minute Raw Throughput and Latency Data, 2-50

AAvailability Detail Report, 2-22

Ccapacity planning, 2-2connectivity report

description, 2-15generating, 1-2

CSU/DSU inventory, 2-5CSV data, 2-50

DDevice Inventory Report, 2-4DSLAM, 2-12DSLAM Inventory Report, 2-8DSLAM slot

inventory report, 2-10DSLAM Slot and Port Inventory Report, 2-12DSLAM Slot Inventory Report, 2-10DSU/CSU inventory, 2-5DTE (User) Port Errors Report, 2-36

Ffailure analysis reports

description, 2-2Frame Delivery Ratio Detail Report, 2-18Frame Transfer Delay Detail Report, 2-20FrameSaver and CSU/DSU Device Inventory Report, 2-5FrameSaver Device Inventory Report, 2-4

GGranDSLAM

inventory, 2-8

Iinventory report

all devices, 2-14DSLAM slot and port, 2-12DSLAM slots, 2-10DSLAMs, 2-8DSU/CSUs, 2-5FrameSaver devices, 2-4generating, 1-2

NNetwork Capacity and Throughput (Rx) Detail Report,

2-26Network Capacity and Throughput (Tx) Detail Report,

2-24Network Connectivity Report, 2-15Network Inventory Report, 2-14Network Port Errors Report, 2-38network topology reports

description, 2-2network tuning, 2-2

Ooverview of report types, 2-2

PPort Errors Report, 2-36, 2-38Port Trend Analysis Report (Rx), 2-42Port Trend Analysis Report (Tx), 2-40ports

DSLAM slot and port inventory, 2-12preparing OpenLane for reports, 1-1processreports command, 1-4Protocol Distribution Detail Report, 2-30PVC Congestion Detail Report, 2-34PVC Trend Analysis Report, 2-44PVC Tx Activity Detail Report, 2-28

Index

IN-2 April 2001 7800-A2-GB30-10

RRaw Throughput and Latency Data, 2-50reports

list of all, 2-1OpenLane preparation, 1-1types of, 1-1, 2-2

Sscheduled reports

accessing, 1-7generating, 1-4list of, 1-3

Site Availability Report, 2-52slot and port

DSLAM inventory report, 2-12SLV Detail Report, 2-46SLV reports

description, 2-2SLV Summary Report, 2-48

TTop 6 IP Communicator Distribution Report, 2-32trend analysis reports

description, 2-2Port Trend Analysis (Rx), 2-42Port Trend Analysis (Tx), 2-40PVC Trend Analysis, 2-44

types of reports, 1-1

UUser (DTE) Port Errors Report, 2-36

OpenLane SLM Reports Reference Guide -...

Documents

Transcript of OpenLane SLM Reports Reference Guide -...