NCP Monitoring Guide - IBMpublib.boulder.ibm.com/tividd/td/ITOMEGAIIfVTAM/GC32-9288-00/en_US/...Appendix C. NCP Monitor Navigation from Statistics Summary 119 ... 4 OMEGAMON II for

NCP Monitoring GuideOMEGAMON II for VTAM

Version 500

GC32-9288-00

August 1999

Candle Corporation201 North Douglas Street

El Segundo, California 90245

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER,AF/REMOTE, Availability Command Center, Candle Command Center, Candle Electronic Customer Support,Candle Logo, Candle Management Server, Candle Management Workstation, Candle Technologies,CL/CONFERENCE, CL/SUPERSESSION, CT, CT/Data Server, CT/DS, DB Logo, DB/QUICKCHANGE,DELTAMON, ETEWatch, IntelliWatch, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e,OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, Solutions for NetworkedBusinesses, and Transplex.

Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS,Amsys, AUTOMATED FACILITIES, Availability Management Systems, Candle Business Partner Logo, CandleDirect Logo, CandleLight, CCC, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW,Command & Control, CommandWatch, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services,CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench,CT/Workstation Server, CT/WS, DB/DASD, DB/EXPLAIN, DB/MIGRATOR, DB/QUICKCOMPARE, DB/SMU,DB/Tools, DB/WORKBENCH, Design Network, DEXAN, eBA*ServiceMonitor, End-to-End, Enterprise CandleCommand Center, Enterprise Candle Management Workstation, EPILOG, ERPNet, ESRA, HostBridge, IntelliWatchPinnacle, Lava Console, Messaging Mastered, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, OMA, OMCGateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER StatusManager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ,PQConfiguration, PQEdit, PQScope, Response Time Network, Roma, Roma Broker, Roma BSP, Roma Connector,Roma Developer, Roma FS/A, Roma FS/Access, Roma Network, Roma Systems Manager, RTA, RTN,SentinalManager, Solutions for Networked Applications, Status Monitor, Tracer, Unified Directory Services andVolcano.

Trademarks and registered trademarks of other companies: AIX, DB2, and MQSeries are registeredtrademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademarkof SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/OpenCompany Ltd. HU-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems,Inc.

All other company and product names used herein are trademarks or registered trademarks of their respectivecompanies.

ProtoView Development Corp. - Contains DataTable Version 3.0 Copyright 1989—1996 by ProtoViewDevelopment Corp. and distributed under license by Candle Corporation.

Copyright 1999, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Testsin Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Usingthe XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring,Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment forComputer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility,Patent No. 5,848,234; Communications on a Network, Patent Pending; End-to-End Response Time Measurement forComputer Programs, Patent Pending; Improved Message Queuing Based Network Computing Architecture, PatentPending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by theGovernment is subject to restrictions set forth in the applicable license agreement and/or the applicable governmentrights clause.

This documentation contains confidential, proprietary information of Candle Corporation that is licensed for yourinternal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents

List of Illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Read This First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1. Introduction to the NCP Monitor . . . . . . . . . . . . . . . 15Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Definition of an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17NCP Resources Illustration. . . . . . . . . . . . . . . . . . . . . . . . . 18NCP Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Statistics Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Single-threaded NPALU . . . . . . . . . . . . . . . . . . . . . . . . . . . 21OMEGAMON II Dynamic Configuration . . . . . . . . . . . . . . . 21NCP Monitor Component Overview. . . . . . . . . . . . . . . . . . . 22NCP Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Problems Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Status Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Varying Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Chapters that Follow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2. Monitoring at the NCP Level . . . . . . . . . . . . . . . . . . 27NCP Main Status Light . . . . . . . . . . . . . . . . . . . . . . . . . . . 28NCP Status Lights Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 29NCP Status Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . 30Interpreting Status Lights . . . . . . . . . . . . . . . . . . . . . . . . . . 31NCP Statistics Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 32NCP Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3. Line-Level Resources . . . . . . . . . . . . . . . . . . . . . . .35Line-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36SDLC/BSC/CA Line Status . . . . . . . . . . . . . . . . . . . . . . . . 37SDLC Line Resource Summary. . . . . . . . . . . . . . . . . . . . . . 39TIC3 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Token-Ring Physical Link Status. . . . . . . . . . . . . . . . . . . . . 41Token-Ring Physical Link Summary . . . . . . . . . . . . . . . . . . 43Token-Ring Logical Link Status . . . . . . . . . . . . . . . . . . . . . 44Token-Ring Logical Link Summary . . . . . . . . . . . . . . . . . . . 46X.25 Multichannel Link Status . . . . . . . . . . . . . . . . . . . . . . 47X.25 Multichannel Link Resource Summary. . . . . . . . . . . . . 48

Contents 3

Chapter 4. PU-Level Resources . . . . . . . . . . . . . . . . . . . . . . . .49PU-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50PU Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 51X.25 Virtual Circuit Status . . . . . . . . . . . . . . . . . . . . . . . . . 52X.25 Virtual Circuit Resource Summary. . . . . . . . . . . . . . . . 53

Chapter 5. LU-Level Resources . . . . . . . . . . . . . . . . . . . . . . . .55LU-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56LU Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Resource Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59LU Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 60X.25 LU Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 6. Setting NCP Monitoring Options . . . . . . . . . . . . . . . 63Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Performance Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Monitoring Options Pull-down . . . . . . . . . . . . . . . . . . . . . . 66NCP Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 7. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Recommended Monitoring Scope. . . . . . . . . . . . . . . . . . . . . 90Case Study 1: LU Reporting Poor Response Time. . . . . . . . . 91Case Study 2: Identifying Line Problem Before Users Report. 93Case Study 3: Is Additional Line Capacity Required?. . . . . . . 95Case Study 4: NCP Storage Shortage. . . . . . . . . . . . . . . . . 97

Appendix A. Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100NCP CCU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 101SDLC Line Statistics Calculations. . . . . . . . . . . . . . . . . . . 102SDLC PU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 104SDLC LU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 106Token-Ring Physical Link Statistics Calculations. . . . . . . . . 107Token-Ring Logical Link Statistics Calculations. . . . . . . . . . 109X.25 MCH Link Statistics Calculations. . . . . . . . . . . . . . . . 111X.25 VC Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 113X.25 LU Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 115

Appendix B. NCP Monitor Navigation from Status Lights . . . . 117Navigation from Status Lights. . . . . . . . . . . . . . . . . . . . . . 118

Appendix C. NCP Monitor Navigation from Statistics Summary 119Navigation from Statistics Summary. . . . . . . . . . . . . . . . . . 120

Appendix D. Candle Customer Support . . . . . . . . . . . . . . . . . 121

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

4 OMEGAMON II for VTAM NCP Monitoring Guide Version 500

List of Illustrations

1. NCP Resources Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . 182. Main Status Panel with NCP Monitor Status Light. . . . . . . . . . . 283. NCP Status Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . . . 304. NCP Statistics Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . 325. NCP Resource Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . 336. Line Type Selection Pop-up. . . . . . . . . . . . . . . . . . . . . . . . . . 367. SDLC Line Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378. SDLC Line Resource Summary Panel. . . . . . . . . . . . . . . . . . . 399. Token-Ring Physical Link Status Panel. . . . . . . . . . . . . . . . . . 41

10. TRPL Resource Summary Panel. . . . . . . . . . . . . . . . . . . . . . . 4311. Token-Ring Logical Link Status Panel. . . . . . . . . . . . . . . . . . . 4412. TRLL Resource Summary Panel. . . . . . . . . . . . . . . . . . . . . . . 4613. Multichannel Link Status Panel 1 - Utilization. . . . . . . . . . . . . 4714. X.25 Multichannel Link Resource Summary Panel. . . . . . . . . . . 4815. PU Status Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5016. PU Resource Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . . 5117. X.25 Virtual Circuit Status Panel 1 - Utilization. . . . . . . . . . . . 5218. X.25 Virtual Circuit Summary Panel. . . . . . . . . . . . . . . . . . . . 5319. LU Status Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5720. Resource Analysis for Terminal Panel. . . . . . . . . . . . . . . . . . . 5921. LU Resource Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . . 6022. Monitoring Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 6623. NCP Default Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . . 6824. Default Options for NCPs . . . . . . . . . . . . . . . . . . . . . . . . . . . 7025. Default Options for SDLC Lines. . . . . . . . . . . . . . . . . . . . . . . 7026. Default Options for SDLC PUs . . . . . . . . . . . . . . . . . . . . . . . 7127. Default Options for SDLC LUs . . . . . . . . . . . . . . . . . . . . . . . 71

| 28. Default Options for Token-Ring Physical Links. . . . . . . . . . . . . 72| 29. Default Options for Token-Ring Logical Links. . . . . . . . . . . . . 72

30. X.25 Multichannel Links Default Options Panel. . . . . . . . . . . . 7331. X.25 Virtual Circuits Default Options Panel. . . . . . . . . . . . . . . 7432. X.25 Virtual Circuits Default Options Panel. . . . . . . . . . . . . . . 7433. NCP Site Monitor List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7634. NCP Site Monitor List with Subordinate Resources. . . . . . . . . . 7935. NCP Site Monitor List View Menu. . . . . . . . . . . . . . . . . . . . . 8036. NCP Site Monitor List View Some. . . . . . . . . . . . . . . . . . . . . 8137. Change Options for an SDLC Line. . . . . . . . . . . . . . . . . . . . . 8238. Change Options for SDLC PUs Attached to a Line. . . . . . . . . . 8339. Change Options for SDLC LUs Attached to a Line. . . . . . . . . . 8340. Start Options for an SDLC Line. . . . . . . . . . . . . . . . . . . . . . . 8541. Confirm Delete from Site Monitor List . . . . . . . . . . . . . . . . . . 8642. How Product Administrator Maintains NCP Options. . . . . . . . . 8743. NCP Site Profile Hierarchy of Settings. . . . . . . . . . . . . . . . . . 8844. Case Study 1: Utilization Analysis for Line. . . . . . . . . . . . . . . 9245. Case Study 2: Retransmission Error Analysis for Line. . . . . . . . 9446. Case Study 3: Line Utilization Trending. . . . . . . . . . . . . . . . . 95

List of Illustrations 5

47. Case Study 4: NCP Resource Summary. . . . . . . . . . . . . . . . . 98


List of Tables

1. OMEGAMON II for VTAM Documentation . . . . . . . . . . . . . . 142. NCP CCU Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 1013. SDLC Line Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 1024. SDLC PU Statistics Calculations. . . . . . . . . . . . . . . . . . . . . . 1045. SDLC LU Statistics Calculations . . . . . . . . . . . . . . . . . . . . . 1066. Token-Ring Physical Link Statistics Calculations. . . . . . . . . . . 1077. Token-Ring Logical Link Statistics Calculations. . . . . . . . . . . 1098. X.25 MCH Link Statistics Calculations . . . . . . . . . . . . . . . . . 1119. X.25 VC Statistics Calculations . . . . . . . . . . . . . . . . . . . . . . 113

10. X.25 LU Statistics Calculations . . . . . . . . . . . . . . . . . . . . . . 115

List of Tables 7


Read This First

Preface

About this document

This manual explains how to use the NCP Monitor component ofOMEGAMON II for VTAM (hereafter referred to as OMEGAMON II).You use this component to monitor and tune your NCP network, includingthe NCPs and the lines, PUs, and LUs connected to them. This guide alsodescribes how to set NCP monitoring options and thresholds.

See the OMEGAMON II for VTAM User's Guidefor information about:

Á OMEGAMON II as a whole

Á the CUA interface

Á the NCP TNSTATs component

Á setting NCP monitoring options

Á setting user authorities

Á using the other main status components of OMEGAMON II

Version 500 of OMEGAMON II contains several new features andenhancements. Please see the OMEGAMON II for VTAM Version 500Release Guide for a brief description of each feature.

If you are interested in historical reporting or SMF record layouts, pleaserefer to the OMEGAMON II for VTAM Historical Reporting Guide.

Read This First 9

Adobe Portable Document Format

Introduction

Candle supplies documentation in the Adobe Portable Document Format(PDF). The Adobe Acrobat Reader prints PDF documents with the fonts,formatting, and graphics in the original document. To print a Candledocument, do the following:

1. Specify the print options for your system. From the Acrobat ReaderMenu bar, select File > Print Setup... and make your selections. Asetting of 300 dpi is highly recommended as is duplex printing if yourprinter supports it.

2. To start printing, select File > Print on the Acrobat Reader Menu bar.

3. On the Print popup, select one of the Print Range options for

Á a single pageÁ a range of pagesÁ all of the document

4. (Optional) To fit oversize pages to the paper size currently loaded onyour printer, select the Shrink to Fit option.

Printing problems?

Your printer ultimately determines the print quality of your output.Sometimes printing problems can occur. If you experience printingproblems, potential areas to check are:

Á settings for your printer and printer driver. (The dpi settings for bothyour driver and printer should be the same. A setting of 300 dpi isrecommended.)

Á the printer driver you are using. (You may need a different printer driveror the Universal Printer driver from Adobe. This free printer driver isavailable at www.adobe.com.)

Á the halftone/graphics color adjustment for printing color on black andwhite printers. (Check the printer properties underStart > Settings >Printer. For more information, see the online help for the AcrobatReader.)

Á the amount of available memory in your printer. (Insufficient memorycan cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentationfor your printer or contact your printer manufacturer.


Documentation Conventions

Introduction

Candle documentation adheres to accepted typographical conventions forcommand syntax. Conventions specific to Candle documentation arediscussed in the following sections.

Panels and figures

The panels and figures in this document are representations. Actual productpanels may differ.

Revision bars

Revision bars (|) may appear in the left margin to identify new or updatedmaterial.

Variables and literals

In examples of command syntax, uppercase letters are actual values (literals)that the user should type; lowercase letters are used for variables thatrepresent data supplied by the user. Default values are underscored.

LOGON APPLID(cccccccc)

In the above example, you type LOGON APPLID followed by an applicationidentifier (represented bycccccccc) within parentheses. The number ofcharacters indicates the maximum allowable length of the variable.

Note: In ordinary text, variable names appear in italics.

Read This First 11

Symbols

The following symbols may appear in command syntax.

Symbol Usage

| The 'or' symbol is used to denote a choice. Eitherthe argument on the left or the argument on the rightmay be used. Example:

YES | NO

In this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments notenclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]

In this example, DEST is a required argument andALTDEST is optional.

{ } Some documents use braces to denote requiredarguments, or to group arguments for clarity.Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORTkeyword must be specified with a value ofSUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile -[COMPRESS={YES | NO}]

In this example, the COMPRESS keyword isoptional. If specified, the only valid values are YESor NO. If omitted, the default is YES.

␣ The symbol ␣ indicates a blank space, when neededfor clarity.


Documentation Set

Introduction

Candle provides a complete set of documentation for OMEGAMON II forVTAM. Each manual in this documentation set contains a specific type ofinformation to help you use the product.

Candle welcomes your comments and suggestions for changes or additions tothe documentation set. A user comment form, located at the back of eachmanual, provides simple instructions for communicating with Candle'sInformation Development department. You can also send email [email protected]. Please include the product name, version, and booktitle in the subject line. To order additional manuals, contact CandleCustomer Support.

Online documentation

The following documents in the OMEGAMON II for VTAM Version 500documentation set are available online in BookManager format:

Á OMEGAMON II for VTAM Version 500 Release Guide

Á OMEGAMON II for VTAM Configuration and Customization Guide

Á OMEGAMON II for VTAM User's Guide

Á OMEGAMON II for VTAM NCP Monitoring Guide

Á OMEGAMON II for VTAM Historical Reporting Guide

Á OMEGAMON II for VTAM Messages Manual

Á End-to-End Response Time Feature (ETE) Reference Manual

Printed documentation

The documentation listed in the following table is available forOMEGAMON II for VTAM. To order additional product manuals, contactyour Candle Customer Support representative.

Read This First 13

Table 1. OMEGAMON II for VTAM Documentation

DocumentNumber

Document Name Description

ON60-5384 OMEGAMON II for VTAMVersion 500 Release Guide

Lists new features, enhancements, andchanges for this release.

IC51-5811 Installing Candle Productson MVS

Provides instructions for installingOMEGAMON II

ON51-5385 OMEGAMON II for VTAMConfiguration andCustomization Guide

Shows how to configure, verify, andcustomize OMEGAMON II for VTAMto your site's requirements.

ON54-5386 OMEGAMON II for VTAMUser's Guide

Shows how to use OMEGAMON II forVTAM to monitor and tune yournetwork.

ON99-5389 OMEGAMON II for VTAMNCP Monitoring Guide

Shows how to use OMEGAMON II forVTAM to monitor and tune your NCPresources.

ON54-5387 OMEGAMON II for VTAMHistorical Reporting Guide

Shows how to produce reports and graphsfrom SMF records generated byOMEGAMON II and provides recordlayouts.

ON52-5388 OMEGAMON II for VTAMMessages Manual

Lists messages issued, their explanations,and suggested responses.

ET53-5586 End-to-End Response TimeFeature (ETE) ReferenceManual

Describes ETE and its commands, andlists error messages, return codes, andsense codes.

Carnegie Mellon University Copyright and Permission

Candle's OMEGAMON II for VTAM product employs a subset of the Carnegie Mellon University (CMU) SNMP Library indata collection for versions of TCP/IP greater than V3.2. Such software is subject to the following: Copyright (C) 1998 byCarnegie Mellon University. All Rights Reserved.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is herebygranted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permissionnotice appear in supporting documentation, and that the name of CMU not be used in advertising or publicity pertaining todistribution of the software without specific, written prior permission.

CMU disclaims all warranties with regard to this software, including all implied warranties or merchantability and fitness. Inno event shall CMU be liable for any special, indirect or consequential damages or any damages whatsoever resulting from lossof use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection withthe use or performance of this software.


Chapter 1.Introduction to the NCP Monitor

Chapter Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Definition of an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17NCP Resources Illustration. . . . . . . . . . . . . . . . . . . . . . . . . 18

NCP Resources Supported. . . . . . . . . . . . . . . . . . . . . . . 19NCP Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Statistics Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Single-threaded NPALU . . . . . . . . . . . . . . . . . . . . . . . . . . . 21OMEGAMON II Dynamic Configuration . . . . . . . . . . . . . . . 21NCP Monitor Component Overview. . . . . . . . . . . . . . . . . . . 22NCP Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Problems Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Status Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Varying Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Chapters that Follow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 1. Introduction to the NCP Monitor 15

Introduction

This guide describes how you can use the NCP Monitor component ofOMEGAMON II for VTAM to monitor and tune your NCP resources.

See the OMEGAMON II for VTAM User's Guide for information about:

Á OMEGAMON II as a whole

Á the CUA interface

Á the NCP TNSTATs component

Á setting user authorities

Á using the other components of OMEGAMON II


Definition of an NCP

An Network Control Program (NCP) is resident control software thatexecutes within the IBM 37x5 family of communication controllers. AnNCP, under the direction and control of the VTAM host, provides for thetransport and management of numerous communication resources within itssubarea. The term NCP often refers to both the Communications ControlUnit (CCU) and the software that runs within it. Many larger networksinclude a number of NCPs.

An NCP is a set of load modules running in the CCU device. The programis generated on the host from selected modules in the IBM-provided NCPlibrary to reflect your site's network configuration when loaded into the CCU.

An NCP communicates with VTAM and performs network management andcommunications functions on behalf of VTAM, such as

Á route selectionÁ data switchingÁ message sequencingÁ pacingÁ data flow control

This relieves the host processor and VTAM from processing overhead andmakes network management and data communications run more efficiently.An NCP can be channel- or link-attached to the host and can communicate

Á to the host via channel adapter (CA) lines

Á to other NCPs

Á to physical units or clusters (PUs) and logical units or terminals (LUs)via attached SDLC or BSC lines (links)

Á to a token-ring network via a TIC connection

Á to an X.25 network via multichannel (MCH) links and virtual circuits(VCs)

Á to other types of network connections such as frame-relay and Ethernet.(These connections are not yet supported by OMEGAMON II.)

The following figure illustrates the NCP network resources supported.


NCP Resources Illustration

Figure 1. NCP Resources Supported


NCP Resources Supported

An NCP can support various combinations of channels, transmission lines,and token-ring attachments.

The OMEGAMON II NCP monitor component monitors these NCP-relatedresources, from the NCP's point of view:

Á CCU including the NCP's view of the channel to the host

Á SDLC lines attached to the NCPÁ PUs attached to the SDLC linesÁ LUs attached to the SDLC PUs

Á BSC lines attached to the NCPÁ cluster controllers attached to the BSC linesÁ terminals attached to the BSC cluster controllers

Á channel adapter (CA) links attached to the NCPÁ PUs attached to the channel adaptersÁ LUs attached to the channel adapters

Á token-ring physical links attached to the NCPÁ token-ring logical links, mapped to the token-ring physical links

Á X.25 MCH links attached to the NCPÁ X.25 virtual circuits mapped to the MCH linksÁ X.25 logical units

For VTAM's view of the channel and the NCP, use the OMEGAMON IINCP TNSTATs component described in theOMEGAMON II for VTAMUser's Guide.


NCP Data Sources

A single OMEGAMON II includes an NCP collector which connects to thenetwork performance analysis logical unit (NPALU) in the NCP via anLU-to-LU session (LU 0).

You can run multiple copies of OMEGAMON II, but there can only be oneNCP collector. In this case, the other OMEGAMON II address spacesconnect to the OMEGAMON II address space containing the NCP collectorthrough an APPC connection.

The NCP monitor component obtains data from the following sources:

Á the NPALU via the NCP collector

Á your NCP NEWDEFN generated source in VTAMLST assigned toddname KONSRC

Á your resource resolution table (RRT) definitions in a PDS assigned toddname KONRRT

For NCP monitor data to be available, the following are required:

Á The NCP collector must be available.Á The NCP must be active.Á The NCP collector and the NPALU must be connected.Á The RRT must be available.Á The NCP generation NDF source must be in VTAMLST.

A single NCP collector can monitor the following NCP configurations:

Á locally attached NCPs

Á remote NCPs managed by the local VTAM domain

Á remote NCPs managed by other VTAM domains that are available bycross-domain session

For more information about NCP monitor component requirements, see theConfiguration Planning and NCP Data Collection Requirements chapters inthe OMEGAMON II for VTAM Configuration and Customization Guide.


Statistics Calculations

For the formulas OMEGAMON II uses to calculate NCP performancestatistics, see “Calculations” on page 99.

Single-threaded NPALU

Because the NPALU is a single-thread logical unit (only one VTAM sessionis allowed), the NCP monitor component cannot coexist with otherperformance monitors that use the NPALU (such as NPM or NETSPY).

Multiple copies of OMEGAMON II can obtain their NCP data only from theone OMEGAMON II that contains the NCP collector.

OMEGAMON II Dynamic Configuration

You do not have to define your NCP configuration to OMEGAMON II.OMEGAMON II checks for an active NPALU session and then obtains yourNCP topology from the the RRT. Both currently and previously active NCPsare displayed on the NCP Site Monitor List under the Options pull-down.OMEGAMON II saves active NCPs and user-specified monitoring options ina persistent table. It is your product administrator's responsibility to deleteobsolete, inactive NCPs from your Site Monitor List. For more information,see “Setting NCP Monitoring Options” on page 63.


NCP Monitor Component Overview

The OMEGAMON II NCP Monitor component provides the following kindsof information about NCPs and the lines, PUs, LUs, token-rings, and X.25resources attached to them:

Á status lights and conditions for each monitored resourceÁ lists of subordinate resources for each resourceÁ descriptive information from the RRT and the VTAMLST sourceÁ performance statistics for each monitored resourceÁ exceptions for each monitored resourceÁ recent trends of pertinent performance statistics

This information can be used by

Á network help desk staff for troubleshooting and problem analysisÁ network capacity planners for network traffic and load analysisÁ the data center command center for network problem alerts

NCP Releases

NCP releases 4.3 and above are supported.


Problems Detected

The following types of problems can degrade the performance of an NCP orits subordinate resources. The NCP monitor component shows you theindications of problems such as:

NCP cycle shortage Indicated by high CCU utilization.

NCP storage shortage Indicated by high NCP buffer utilization.

Insufficient bandwidth Indicated by high bandwidth utilization forindividual lines. This may be associated with higherror rates or overconfiguration of the line. Usuallyisolated to an individual transmission link.

High non-productive pollsUsually a symptom of low line utilization.

Error retransmissions Transient line errors may induce highretransmission rates, which can reduce the amountof line capacity available for normal transmission.

VC connection count High virtual circuit connection count can impactCCU cycle utilization, storage utilization, andbandwidth on the MCH link.

D-Bit rate High D-Bit rate can adversely affect user responsetimes and generate unnecessary network traffic.

TIC congestion Indicated by high TIC utilization and token-ringreported congestion counts.

Status Lights

NCP performance is indicated by a status light on the main status display andreflects the highest threshold level exceeded by any monitored NCP resource.If you select this light, you access the NCP Status Summary panel, whichshows you status lights for all the active NCPs that you are monitoring andtheir subordinate resources.

To highlight problem resources, status lights on the NCP Status Summarypanel display in decreasing order of severity: critical, then warning, thennormal.


Navigation

From the NCP Status Summary panel, you can toggle with F4 (NCP List) toan NCP Statistics Summary panel, or with F22 (TNSTATs) to the NCPTNSTATs component. Within the NCP monitor component, you can displayNCP monitor data for a specific resource or for a list of resources attached toa selected resource.

When an NCP resource is in a critical or warning condition, you can navigatedirectly from the NCP Status Summary panel to a resource summary panelthat summarizes utilization data for the resource.

If you want to list or compare the utilization of resources of the same type,you can navigate from the NCP Statistics Summary panel to anywhere in theNCP-to-LU hierarchy.

On any display panel in the NCP monitor component, the return functionkeys operate as follows:

Á F12 (Cancel) returns you to the previous panel in the current navigationpath.

Á F3 (Exit) returns you to the NCP summary panel from which youoriginated: NCP Status Summary (see Figure 3 on page 30) or NCPStatistics Summary (see Figure 4 on page 32).

You can navigate between the NCP monitor component and otherOMEGAMON II functions in several different ways:

Á Use F22 to toggle between the NCP Status or Statistics Summary paneland the NCP TNSTATs - List of NCPs panel.

Á Use an action code or the Goto pull-down menu to navigate between LUpanels and the Average Response Times panel.

Á Use an action code or the Goto pull-down menu to access resourceanalysis panels for a selected LU.

A substantial amount of data is available from the NPALU. Often there istoo much resource utilization data to fit on a single panel. Use the scrollingfunction keys to display additional data. Scroll right and left with F20 andF19 to view additional data about the same resource or the same list ofresources.

More than one kind of line-level resource is supported, such asSDLC/BSC/CA lines, token-ring physical and logical links, and X.25multichannel links. Scroll to the next or previous type of line resource withF22 and F21.


Varying Views

Panels that display lists of resources include the View selection on the actionbar. You can use the View pull-down menu to alter the current display ofresources and their performance statistics in two different ways:

1. You can sort on significant fields, in ascending or descending order.These are some examples:

Á Sort on condition so that resources in critical condition appear first.

Á Sort on utilization so that resources with the highest utilizationappear first.

2. You can display only those resources that match the criteria you specify.These are some examples:

Á Display only those resources that are in critical condition.

Á Display only those resources with utilization over a certainpercentage.

Á Display only those resources whose names start with the charactersyou specify (a generic filter).

Trending

Use action code T to select Trends. Trend panels show trend records for theresource or performance statistic selected. A trend record is written to theVSAM log file at every recording interval. The trend panels show you themost recent record first, and go backward in time for as many trend recordsas reside in the log file. Trend panels show you the highest occurrence ofthe performance statistic, as well as relative percentages. Some trends areshown in pairs, such as inbound and outbound PIUs. For an example of atrend panel, see Figure 46 on page 95.


Exceptions

Use action code X to select Exceptions. Exception messages are displayedfor the resource or performance statistic selected. If a threshold is exceeded,an exception record is written to the VSAM log file at the sampling interval.For NCP resources, the sampling interval is the NCP collection intervalspecified during CICAT configuration of OMEGAMON II. The exceptionpanels show you the most recent exception message first and go backward intime for as many exception records as reside in the log file.

An NCP exception occurs when an NCP-related resource exceeds itsthreshold. Under the Options pull-down, you specify

Á recording interval on the Global Options panel

Á exception thresholds on the NCP Options panels

You can view the NCP collection interval on the NCP Default MonitoringOptions panel. For more information about NCP settings, see “Setting NCPMonitoring Options” on page 63.

F1When you are using OMEGAMON II, you can press F1 if you need help.Helps include comprehensive field descriptions and detailed technicalinformation. If your cursor is on an input or display field when you pressF1, you get help for that field; otherwise, you get help for the panel.

Chapters that Follow

The following chapters guide you through representative panels in the NCPmonitor component in this order:

1. NCP-level panels2. Line-level panels3. PU-level panels4. LU-level panels

To illustrate how the NCP monitor component can help detect, prevent, andsolve network problems, see the four usage scenarios, starting with “CaseStudy 1: LU Reporting Poor Response Time” on page 91.

You can find the formulas OMEGAMON II uses to calculate performancestatistics for NCP resources in “Calculations” on page 99.

This guide ends with NCP monitor component navigation charts starting onpage 118.


Chapter 2.Monitoring at the NCP Level

Chapter Contents

NCP Main Status Light . . . . . . . . . . . . . . . . . . . . . . . . . . . 28NCP Status Lights Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 29NCP Status Summary Panel. . . . . . . . . . . . . . . . . . . . . . . . 30Interpreting Status Lights . . . . . . . . . . . . . . . . . . . . . . . . . . 31NCP Statistics Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 32NCP Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 2. Monitoring at the NCP Level 27

NCP Main Status Light

The NCP monitor status light appears at the bottom left of theOMEGAMON II main status panel, as shown in the following figure.

à ð ____ Actions Goto Options Help

-------------------------------------------------------------16:22:37 1ð/ð6/98

KONDMAIN OMEGAMON II for VTAM Status Display System: SYSG

Select with a "/" or an action code.

S=Show details X=Exceptions

+----------------------------+-----------------------------+----------------+

| _ Buffer Pools Critical | _ Response Times Normal | _ VTAM Apps |

| | | |

| _ Virtual Routes Warning | _ VTAM Trace Normal | _ Historical |

| | | |

| _ TNSTATS: CTCs Warning | _ VTAM Addr Space Warning | |

| | | |

| _ TNSTATS: NCPs Normal | _ TCP/IP Critical | |

| | | |

| _ TNSTATS: Locals Normal | _ LU 6.2 Critical | |

| | | |

| _ NCP Monitor Warning | | |

+----------------------------+-----------------------------+----------------+

Command ===>

F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F9=Retrieve F1ð=Action Bar

F11=Print

á ñ

Figure 2. Main Status Panel with NCP Monitor Status Light

On the main status panel, the NCP monitor status light represents the worstcondition of any NCP-related resource being monitored:

Á If any monitored NCP, line, PU, or LU is in critical condition, the NCPstatus light is red.

Á If no NCP resources are critical, but at least one NCP resource is inwarning condition, the NCP status light is yellow.

Á If all NCP resources are in normal condition, the NCP light is green.

The specifications in the NCP monitoring options panels under the Optionspull-down determine which resources are monitored and the criteria forraising exceptions. See “Setting NCP Monitoring Options” on page 63.

If you enter action code X (Exceptions) next to the NCP monitor light, allNCP monitor exceptions on the VSAM log file display in reversechronological order. On the Exceptions panel, you can use action code S(Show recommendations) to display an explanation, background information,and recommendations for dealing with the exception condition in yournetwork.


NCP Status Lights Hierarchy

status lights summary, NCP An NCP is considered the highest level in theNCP-to-LU hierarchy of resources. Subordinate resources are considered asfollows:

Line-level

Á SDLC linesÁ BSC linesÁ channel adapter linesÁ token-ring physical linksÁ token-ring logical linksÁ X.25 MCH links

PU-level

Á SDLC physical unitsÁ BSC clustersÁ channel adapter physical unitsÁ X.25 virtual circuits

LU-level

Á SDLC logical unitsÁ BSC terminalsÁ channel adapter logical unitsÁ X.25 logical units

If you enter action code S (Show details) next to the NCP monitor light onthe main status panel (see previous figure) the NCP Status Summary panelappears.

When you arrive at this panel from the main status panel, only NCPs arelisted. To display subordinate resources on this panel, do the following:

1. Enter action code L (List) next to an NCP.

Result: The lines attached to the selected NCP are listed below the NCP.

2. Enter action code L next to a line.

Result: The PUs attached to the selected line are listed below the line.

3. Enter action code L next to a PU.

Result: The LUs attached to the selected PU are listed below the PU.


NCP Status Summary Panel

The following figure is an example of an NCP Status Summary wheresubordinate resources have been listed.

à ð____ Actions Goto View Options Help

---------------------------------------------------------------ð2:45:22 ð5/25/96

KONDNNMD NCP Status Summary System: SYSA

More:

Select with a / or an action code Lines 1 to 15 of 15

X=Exceptions S=Show details L=List U=Unlist

+---------------------+-------------+-------------+-------------+--------------+

| | NCP | Line | PU | LU |

| Resource Type | Condition | Condition | Condition | Condition |

+---------------------+-------------+-------------+-------------+--------------+

| _ NCP1ð NCP | Critical | Warning | Critical | Warning |

| _ J1ð11111 TRLL | | Warning | | |

| _ TRPL2 TRPL | | Warning | | |

| _ L6ðð SDLC | | Warning | Critical | Warning |

| _ L6ððA PU | | | Warning | Warning |

| _ L6ððB PU | | | Critical | Warning |

| _ L6ððBðð1 LU | | | | Warning |

| _ NCP11 NCP | Warning | Normal | Normal | Critical |

| _ R6ðð SDLC | | Normal | Normal | Critical |

| _ R62ð SDLC | | | Normal | Normal |

| _ R8ððX X25L | | Warning | Normal | Normal |

| _ R8ððXV1 SVC | | | Warning | Warning |

| _ R8ððXV2 PVC | | | Critical | Warning |

| _ L8ððV2ð1 LU | | | | Warning |

| _ NCP2ð NCP | Normal | Warning | Warning | Critical |

+---------------------+-------------+-------------+-------------+--------------+

Command ===> __________________________________________________________________

F1=Help F2=Keys F3=Exit F4=NCP List F5=Refresh F6=Console **=Bkwd **=Fwd

F9=Retrieve F1ð=Action Bar F11=Print F12=Cancel F14=Find

F15=Status_Display F22=TNSTATs

á ñ

Figure 3. NCP Status Summary Panel

The Status Summary panel shows status lights for every NCP resource level,so that you can see the status of your entire network at a glance. A statuslight represents the highest threshold level exceeded for that group ofresources. The lights displayed next to an NCP mean the following:

NCP Condition Represents the status of the NCP itself.

Line Condition Represents the worst case status of the lines attached tothe NCP.

PU Condition Represents the worst case status of the PUs attached to theNCP.

LU Condition Represents the worst case status of the LUs connected tothe NCP.


Interpreting Status Lights

The status lights that appear next to subordinate resources on this panel meanthe following:

Á The lights next to a line represent the status of the line itself, and theworst case status of the PUs and LUs attached to the line.

Á The lights next to a PU represent the status of the PU itself, and theworst case status of the LUs attached to the PU.

Á The lights next to an LU represent the worst case status of the LU itself.

To bring you attention to problem resources, status lights display indescending severity order:

Á Higher severity NCPs display before lower severity NCPs.

Á Higher severity lines attached to an NCP display before lower severitylines.

Á Higher severity PUs attached to a line display before lower severity PUs.

Á Higher severity LUs attached to a PU display before lower severity LUs.

Use action code X (Exceptions) to display the exceptions raised for a selectedresource.

Use action code S (Show details) next to a resource exhibiting a problemcondition. A resource summary panel shows utilization data for the selectedresource to help you detect the cause of the problem.

Two toggle keys are available on this panel:

F4 Takes you to the NCP Statistics Summary panel, which shows youutilization data about your NCPs. From there, you can navigate toadditional NCP statistics or down the NCP-to-LU hierarchy to seeutilization data for subordinate resources.

F22 Takes you to the NCP TNSTATs Summary panel, which is thebeginning of the NCP TNSTATs component.


NCP Statistics Summary

When you press F4 (NCP List) on the NCP Status Summary panel (seeFigure 3 on page 30), the NCP Statistics Summary appears as shown in thefollowing figure.


-------------------------------------------------------------17:56:52 11/14/94

KONDNNAD NCP Statistics Summary System: SYSA

More: <

Select with a "/" or an action code. Lines 1 to 3 of 3

X=Exceptions S=Show details K=Lines P=PUs L=LUs V-VCs

T=Trends

+------------+------+--------------------+---------------+-------------+------+

| | CCU | Free Buffers | Channel | Slowdown | |

| NCP Name | Util | Avail High Low | INTQ HOLD | Time Pct | Cond |

+------------+------+------+------+------+-------+-------+------+------+------+

| S NCPð1 | 99% | 1ðð% | 1ðð% | 1ðð% | 5 | 5 | 3.8s| 8% | Idle |

| _ NCP11 | 1% | 24% | 34% | 45% | 5 | 6 | ð.3s| 1ð% | Norm |

| _ NCP12 | 75% | 11% | 26% | 21% | 4 | 5 | 1.5s| 5% | Crit |

+------------+------+-------------+------+-------+-------+------+------+------+

Command ===> __________________________________________________________________

F1=Help F2=Keys F3=Exit F4=NCP Status F5=Refresh F6=Console **=Bkwd

**=Fwd F9=Retrieve F1ð=Action Bar F11=Print F12=Cancel F14=Find

F15=Status_Display F22=TNSTATs

á ñ

Figure 4. NCP Statistics Summary Panel

Active monitored NCP major nodes are listed on this panel. Summaryperformance statistics and a status light are shown for each NCP. To listsubordinate resources and their utilization data, use theK (Lines), P (PUs), V(VCs), or L (LUs) action codes.

Use the X and T action codes to display Exceptions and Trends for a selectedNCP. Trends are available for the following performance data:

Á CCU utilizationÁ free buffers lowÁ channel queuesÁ slowdown percentage

Two toggle keys are available:

F4 Returns you to the NCP Status Summary panel, which displays NCPstatus lights.

F22 Takes you to the NCP TNSTATs Summary panel, which is thebeginning of the NCP TNSTATs component.


NCP Resource Summary

You can enter action code S (Show details) next to an NCP either on theNCP Statistics Summary (see previous figure) or on the NCP StatusSummary (see Figure 3 on page 30). The NCP Resource Summary panelappears as shown in the following panel.

à ð____ Actions Goto Options Help

-------------------------------------------------------------12:12:ðð 11/14/94

KONDNNND Resource Summary for NCP: NCPð1 System: SYSA

More:


X=Exceptions S=Show details T=Trends

+--------------------------+------------------------+-------------------------+

| Name . . . . .: NCPð1 | MAXCOLL . . .: 4ðð | Connect. . . : LOCAL |

| Subarea. . . .: 25 | Lines . . . .: 76 | Total buffers: 991 |

| Release. . . .: V6R2 | PUs . . . . .: 18 | SLOWDOWN lim.: 12.31% |

| NPALU. . . . .: NPALUð1 | LUs . . . . .: 38 | Cycle speed .: 4ð.69K |

+--------------------------+-----------+------------+-------------------------+

| Generation Date .: ð1/ð6/94 11:39:ð7 | Generation Level.: ð5-12-88 23:59:59 |

+----------------+---------+-----------+------------+-------------------------+

| S CCU Cycles | Normal | Utilization.: 17.ðð% | Cycles used. : 2ð.26M|

| _ Channel | Warning | HOLDQ length: 1 | INTQ length. : 1 |

| _ Slowdown | Warning | Percent. . .: 3.32% | Time (secs). : 2.ðs|

| _ Buffer Util | Normal | Utilization.: 25.53% | Max free buff: 748 |

+----------------+---------+------------------------+-------------------------+

Command ===> __________________________________________________________________


F11=Print F12=Cancel F15=Status_Display

á ñ

Figure 5. NCP Resource Summary Panel

The upper portion of the panel displays VTAM configuration data for theNCP. The lower portion provides statistics for the NCP controller and astatus light for each type of statistic.

Exceptions, trends, and a Utilization Detail panel are available for each ofthese performance statistics:

Á CCU cyclesÁ channel utilizationÁ slowdown percentÁ buffer utilization



Chapter 3. Line-Level Resources

Chapter Contents

Line-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36SDLC/BSC/CA Line Status . . . . . . . . . . . . . . . . . . . . . . . . 37

Line Status Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . 38SDLC Line Resource Summary. . . . . . . . . . . . . . . . . . . . . . 39TIC3 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Token-Ring Physical Link Status. . . . . . . . . . . . . . . . . . . . . 41

Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Token-Ring Physical Link Summary . . . . . . . . . . . . . . . . . . 43Token-Ring Logical Link Status . . . . . . . . . . . . . . . . . . . . . 44

Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Token-Ring Logical Link Summary . . . . . . . . . . . . . . . . . . . 46X.25 Multichannel Link Status . . . . . . . . . . . . . . . . . . . . . . 47X.25 Multichannel Link Resource Summary. . . . . . . . . . . . . 48

Chapter 3. Line-Level Resources 35

Line-level Panels

Line-level resources are considered subordinate to NCPs in the NCP-to-LUhierarchy of resources. Several different line types are supported. When youenter action codeK (Lines) on the NCP Statistics Summary (see Figure 4 onpage 32), a pop-up appears prompting you to select from a list of supportedline types.

à ð

KONDN35P Lines Selection

_ 1. SDLC/BSC/CA line (S)

2. Token-ring physical link (P)

3. Token-ring logical link (L)

4. X.25 multichannel link (X)

F1=Help F12=Cancel

á ñ

Figure 6. Line Type Selection Pop-up

When you select a line type, a list of lines of the selected type displays. Forexample, if you select SDLC/BSC/CA line from the prompt list, theSDLC/BSC/CA Line Status appears as shown in Figure 7 on page 37.

You can specify a default line type in the Default NCP Monitoring Optionspanel under the Options pull-down. If a default line type is specified, then aLine Status panel for the default line type displays immediately without youhaving to select a type from the prompt list.

Performance statistics are unique for each line type. Once you select aline-type you can use F22 (Next) and F21 (Previous) to navigate betweenlistings of the various line types connected to the same NCP. The order ofaccess is the same as listed in the line type prompt menu above. When youget to the last line type, F22 (Next) returns you to the first line type.


SDLC/BSC/CA Line Status

When you specify SDLC as your line type, the SDLC/BSC/CA Line Statuspanel lists the SDLC, BSC, and channel adapter lines attached to the selectedNCP.


-------------------------------------------------------------18:51:41 11/14/94

KONDNNKD SDLC/BSC/CA Line Status for NCP: NCPð1 System: SYSA

More: >


X=Exceptions S=Show details P=PUs L=LUs T=Trends

+------------+------+-------+-----+---------------+--------------------+------+

| | Line | Line | Que | Non-Productve | Polling | |

| Line Name | Util | Speed | Len | Polls Pct | Total Positive | Cond |

+------------+------+-------+-----+--------+------+----------+---------+------+

| S LS96ððA | 26% | 56K | 1 | 1,327 | 88% | 1,5ðð | 173 | Warn |

| _ LS56K | 52% | 56K | 1 | 1,365 | 91% | 1,5ðð | 135 | Warn |

| _ LSDLC1 | 7% | 96ðð | 1 | 1,395 | 93% | 1,5ðð | 1ð5 | Norm |

| _ BSC1 | 18% | 96ðð | 1 | 1,35ð | 9ð% | 1,5ðð | 15ð | Norm |

+------------+------+-------+-----+--------+------+----------+---------+------+

Command ===> __________________________________________________________________

F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F9=Retrieve

F1ð=Action Bar F11=Print F12=Cancel F14=Find F15=Status_Display **=Left

F2ð=Right F21=Prev F22=Next

á ñ

Figure 7. SDLC Line Status Panel

This panel displays performance statistics and a status light for eachmonitored SDLC/BSC/CA line connected to the NCP. Action codes areavailable as follows:

X Provides exceptions for a selected line.S Displays a Resource Summary panel for a line.P Lists all the PUs attached to a line.L Lists all the LUs attached to a line.T Provides utilization, non-productive poll, or outbound queue length

trends for a line.


Line Status Scrolling

Scrolling is available on this panel as follows:

Á There are five more SDLC line list panels providing retransmission,traffic, and high-, medium-, and low-priority frame statistics for the linesattached to the specified NCP. Use F20 (Right) and F19 (Left) to scrollbetween them. A frame is the vehicle for commands, responses, and allinformation that is transmitted using SDLC protocal.

Á Token-rings may be attached to the NCP through the TIC. Use F22(Next) to scroll to panels listing the token-ring physical links andtoken-ring logical links attached to the NCP. F21 (Previous) scrolls tothe line-type previously displayed.


SDLC Line Resource Summary

When you enter action code S (Show details) next to an SDLC, BSC, orchannel adapter line either on the NCP Status Summary (see Figure 3 onpage 30) or on the SDLC/BSC/CA Line Status panel (see previous figure), aline resource summary appears.


-------------------------------------------------------------18:3ð:ð1 11/14/94

KONDNNLD Resource Summary for SDLC Line: LS96ððA System: SYSA

More:


X=Exceptions S=Show details A=Analysis T=Trends

+-------------------------+-------------------------+-------------------------+

| Line name: LS96ððA | PU entries. . .: 14 | PIUs In. .: 9ð7 |

| SPEED . .: 96ðð/96ðð | LU entries. . .: 24 | PIUs Out .: 34ð |

| DUPLEX. .: FULL | Reply timeouts.: 3 | Bytes In .: 44.29K |

| NCP name.: NCPð1 | RETRIES: 5,5,6 | Bytes Out.: 66.44K |

| Subarea .: 9 | PAUSE .: ð.2 SERVLIM. .: ð |

+----------------+--------+-------------------------+-------------------------+

| A Utilization | Normal | Inbound . . .: 12.6ð% | Outbound . .: 18.9ð% |

| _ Retransmits | Normal | PIUs. . . . .: 1.76% | Bytes. . . .: ð.83% |

| _ Polling | Normal | Total polls .: 1,5ðð | Non-prod . .: 9ð.ðð% |

| _ Errors | Normal | Rate per kbyt: ð | Total error.: 2 |

| _ QLength | Normal | Length (PIUs): 1 | |

+----------------+--------+-------------------------+-------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 8. SDLC Line Resource Summary Panel

The upper portion of the panel shows VTAM configuration data for theSDLC, BSC, or channel adapter line. The lower portion of the panel showsstatistics and status lights for each category of data: utilization,retransmissions, and polling.

For the selected category, you can use the following action codes:

X Gives you the exceptions that have been raised.S Provides more details.A Displays an analysis panel.T Gives you recent trends.


TIC3 Data Collection

There is an important difference between TIC3 data collection and collectionfor all other NCP resource types. You specify the NCP collection intervalfor monitoring NCP resources during OMEGAMON II CICAT configuration.However, the sample interval for TIC3 resources attached to a 3746-M900expansion frame is fixed. It is hardcoded in the 3746 as 225 seconds andcannot be modified.

Here is how OMEGAMON II resolves the difference between NCP andTIC3 intervals. There are three possibilities:

TIC3 interval equals NCP interval.TIC3 data displays at the end of the NCP interval in which theTIC3 interval expires.

TIC3 interval is less than NCP interval.If there is more than one TIC3 interval within the NCP interval,TIC3 data is accumulated. TIC3 data from one or more expiredTIC3 samples displays at the end of the NCP interval.

For example, if the NCP interval is 5 minutes (300 seconds) atleast one but possibly two TIC3 intervals may elapse during theNCP interval.

TIC3 interval is greater than NCP interval.When the TIC3 interval expires within the NCP interval, TIC3 datadisplays at the end of the NCP interval. When no TIC3 intervalexpires within the NCP interval, TIC3 data appears as zeros.


Token-Ring Physical Link Status

There are two different ways to reach the panel shown in the followingfigure:

Á Enter action code K (Lines) next to an NCP on the NCP StatisticsSummary panel (see Figure 4 on page 32) and then select TRPL as yourline type (see Figure 6 on page 36).

Á Press F22 (Next) on the list of SDLC/BSC/CA lines (see Figure 7 onpage 37).


--------------------------------------------------------------18:51:41 11/14/94

KONDNNWD Token-Ring Physical Link Status for NCP: NCPð1 System: SYSA

More: >



+------------+--------+--------+----------------------+--------+--------+------+

| | TIC | Ring | Rate per Minute | Queue | Active | |

| Link Name | Util | Speed | Frames Bytes | Length | Connct | Cond |

+------------+--------+--------+----------------------+--------+--------+------+

| S RING1 | 56% | 4M | 9K 3,456K | 1 | 3 | Crit |

| _ RING2 | 64% | 4M | 16K 5,999K | 1 | 3 | Crit |

| _ RING3 | 45% | 4M | 12K 568K | ð | 4 | Crit |

| _ RING4 | 13% | 4M | 18K 74ðK | 1 | 3 | Crit |

+------------+--------+--------+----------------------+--------+--------+------+

Command ===> __________________________________________________________________




á ñ

Figure 9. Token-Ring Physical Link Status Panel


Panel Description

The Token_Ring Physical Link Status for NCP panel lists the token-ringphysical links (TRPLs) attached to the selected NCP. It shows performancestatistics and a status light for each TRPL. For TIC3, queue length andactive connects are unavailable and display as zeros.

Exceptions and trends are available for a selected line. You can displayrecent trends of the following performance data:

Á TIC utilizationÁ rate per minuteÁ queue lengthÁ active connects

Show details (S) displays a resource summary panel for a selected line.

Scrolling is available on this panel:

Á Two more panels provide error and traffic statistics for the TRPLsattached to the specified NCP. Use F20 (Right) and F19 (Left) to scrollbetween them.

Á Use F22 (Next) to scroll to the panel listing the token-ring logical linksattached to the NCP and then to the list of SDLC/BSC lines. F21(Previous) scrolls to the line type previously displayed.


Token-Ring Physical Link Summary

When you enter action code S (Show details) next to an TRPL either on theNCP Status Summary (see Figure 3 on page 30) or on the TRPL statuspanel (see previous figure), an TRPL resource summary appears as shown inthe following figure.


--------------------------------------------------------------18:3ð:ð1 11/14/94

KONDNNVD Resource Summary for Token-Ring Physical Link: RING1 System: SYSA

More:



+-------------------------+-------------------------+--------------------------+

| NCP name.: NCPð1 | TRSPEED(Mbps): 4 | PASSLIM. . . .: 2 |

| ADAPTER .: TIC2 | MAXTSL. . . .: 4ð4ð | Bytes in . . .: 12.ððM |

| ECLTYPE .: PHY,ANY | RCVBUFC . . .: 31.25K | Bytes out. . .: 18.ððM |

| LOCADD. .: 4ððððððð4ð7ð | PORTADD . . .: ð | Frames in. . .: 61.44K |

| DYNWIND .: N/A | LSPRI . . . .: N/A | Frames out . .: 23.ð4K |

+----------------+--------+-------------------------+--------------------------+

| _ Utilization | Critic | Inbound . . .: 8.4ð% | Outbound . . .: 12.6ð% |

| _ Congestion | Critic | Percent . . .: 13.52% | Count. . . . .: 8,5ð5 |

| _ Retransmits | Warnin | IFrames . . .: 7.7ð% | Bytes. . . . .: 3.33% |

| _ Rates | Normal | Frames/min. .: 61.47K | Bytes/minute .: 6144.ððK |

| _ Connects | Normal | Active. . . .: 3 | |

| _ QLength | Normal | Length (IFrm): 1 | |

+----------------+--------+-------------------------+--------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 10. TRPL Resource Summary Panel

On this panel, OMEGAMON II is measuring the inbound and outboundtraffic on the TIC. The Utilization field shows the NCP's contribution to thetoken-ring's utilization. The remainder of the ring may be contributing moreto its utilization.

The upper portion of the panel shows VTAM configuration data for theTRPL. The lower portion of the panel shows performance statistics and astatus light for each type of statistic. For TIC3, retransmitted IFrames, activeconnects, queue length, and congestion are unavailable and display as zeros.

For each category of statistics: utilization, retransmissions, and traffic, youcan use the following action codes:

X Gives you the exceptions that have been raised.S Provides more utilization or error details.T Gives you recent trends.


Token-Ring Logical Link Status

Token-ring logical links (TRLLs) represent logical connections to the otherdevices that are attached to the token-ring that the NCP is attached to. Thereare two ways to reach the panel shown in the following figure.

Á Enter action code K (Lines) next to an NCP on the NCP StatisticsSummary panel (see Figure 4 on page 32) and then select TRLL as yourline type (see Figure 6 on page 36).

Á Press F22 (Next) on the list of TRPLs (see Figure 9 on page 41).


-------------------------------------------------------------18:51:41 11/14/94

KONDN1UD Token-Ring Logical Link Status for NCP: NCPð1 System: SYSG

More: >



+------------+-------------------+-------------------+---------+-----------+

| | Total Frames | Total Bytes | Queue | |

| Link Name | Inbound Outbound | Inbound Outbound | Length | Condition |

+------------+---------+---------+---------+---------+---------+-----------+

| S Jððð9ðð7 | 123,456 | 123,456 | 456K | 456K | 1 | Normal |

| _ Jððð9ðð6 | 2,966 | 5,999 | 366K | 399K | 4 | Normal |

| _ Jððð9ðð3 | 2.ð92 | 2,568 | 92K | 568K | 3 | Normal |

| _ Jððð9ðð3 | 3,678 | 2,55ð | 1,678K | 4ððK | 1 | Normal |

+------------+---------+---------+---------+---------+---------+-----------+

Command ===> __________________________________________________________________




á ñ

Figure 11. Token-Ring Logical Link Status Panel


Panel Description

The Token-Ring Logical Link Status panel lists the TRLLs attached to thespecified NCP. It shows inbound and outbound frames and bytes, and astatus light for each TRLL. For TIC3, queue length is unavailable anddisplays as zeros.

Exceptions and trends are available for a selected link. You can displaytrends for the following performance data:

Á total framesÁ total bytesÁ outbound queue length

Show details displays a Resource Summary panel for a selected link.

Scrolling is available on this panel:

Á Two more panels provide traffic and retransmission statistics for thelisted TRLLs. Use F20 (Right) and F19 (Left) to scroll between them.

Á F22 (Next) scrolls to the list of SDLC/BSC lines, and F21 (Previous)scrolls to the list of TRPLs.


Token-Ring Logical Link Summary

When you enter action code S (Show details) next to an TRLL either on theNCP Status Summary (see Figure 3 on page 30) or on the TRLL statuspanel (see previous figure), an TRLL resource summary appears as shown inthe following figure.


-------------------------------------------------------------18:3ð:ð1 11/14/94

KONDNNRD Resource Summary for Token-Ring Logical Link: Jððð9ðð1 System: SYSA

More:



+-------------------------+-------------------------+--------------------------+

| Name. . .: Jððð9ðð1 | PU Name . .: | Bytes inbound.: 58.59K |

| ECLTYPE .: LOG,PER | RNRLIMIT. .: N/A | Bytes outbound: 234.37K |

| PHYPORT .: ð | RETRIES: 4,6,3,1ð | Frames inbound: 1,2ðð |

| NCP name.: NCPð1E | T2TIMER: N/A | Frames outbnd.: 1,2ðð |

+----------------+--------+-------------------------+--------------------------+

| _ Retransmits | Normal | IFrames . . : ð.18% | Bytes . . . .: ð.13% |

| _ Timeouts | Warnin | Timeout rate: 3.3ð% | Timeout count: 36 |

| _ Rates | Critic | Frames/min. : 2,4ðð | Bytes/minute.: 292.96K |

| _ QLength | Normal | Length(PIUs): ð | |

+----------------+--------+-------------------------+--------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 12. TRLL Resource Summary Panel

The upper portion of this panel shows VTAM configuration data for theTRLL. The lower portion summarizes the TRLL's performance statistics andprovides a status light for each category of statistics: retransmits, timeouts,rates, or queue length. For TIC3, retransmitted IFrames, timeouts, and queuelength are unavailable and display as zeros.

For each category, you can use the following action codes:

X Gives you exceptions.S Displays utilization or error details.T Gives you trends.


X.25 Multichannel Link Status

When you select X.25 Multichannel Links from the Lines Selection menu,the first of five X.25 Multichannel Link Status panels displays.


-------------------------------------------------------------18:51:41 ð5/25/96

KONDNNCD X.25 Multichannel Link Status for NCP: NCPð1 System: SYSA

More: >


X=Exceptions S=Show details V=VCs L=LUs T=Trends

+------------+------+-------+------------------+----------------------+------+

| MCH | Link | Link | Total Bytes | Virtual Circuits | |

| Link Name | Util | Speed | Inbound Outbound | Max Curr New Util | Cond |

+------------+------+-------+------------------+----------------------+------+

| _ X259ðð1A | 1ðð% | 96ðð | 32,ð45K 34,656K| 4ð96 4ð96 56 1ðð% | Crit |

| _ R9ð1 | 34% | 56K| 457K 346K| 1ððð 2ðð 33 2ð% | Norm |

| _ R9ð2 | 18% | 56K| 65K 67K| 2ððð 1ððð 345 5ð% | Warn |

| _ R9ð3 | 87% | 96ðð | 11K 23K| 3ððð 1ððð 782 33% | Crit |

+------------+------+-------+------------------+----------------------+------+

Command ===> __________________________________________________________________




á ñ

Figure 13. Multichannel Link Status Panel 1 - Utilization

This panel shows you utilization statistics for the MCH links attached to theselected NCP. You can use the following action codes:

X Provides exceptions for an MCH link.

S Shows a Resource Summary panel for a link.

V Lists the virtual circuits using the link.

L LIsts the logical units attached to the link.

T Provides recent trends for link utilization, total bytes, current VCs, newVCs, and VC utilization.

There are four more MCH Link Status panels that show you retransmission,traffic, polling, and connection statistics for the listed links. Use F20 (Right)and F19 (Left) to scroll between them.


X.25 Multichannel Link Resource Summary

When you use action code S (Show Details) next to a link on an X.25Multichannel Link Status panel (see Figure 13 on page 47) or on the NCPStatus Summary panel (see Figure 3 on page 30), the X.25 Link ResourceSummary panel appears.


--------------------------------------------------------------18:3ð:ð1 ð5/25/96

KONDNNED Resource Summary for X.25 MCH Link: X259ðð1A System: SYSA



+---------------------------+----------------------+--------------------------+

| MCH link name: X259ðð1A | MMODULO .: 8 | ANS. . . . . .:CONTINUE |

| NCP name. . .: NCPð1 | MWINDOW .: 7 | DBIT . . . . .: NO |

| SPEED . . . .: 96ðð/96ðð | FRMLGTH .: 131 | Tot RNR frames: 3ðð |

| LLCLIST . . .: (ð,4,5) | PKTMODL .: 8 | Tot data pkts.: 15ð |

| FTPI. . . . .: N/A | PLPIGGYB .: Yes | Total bytes. .: 263K |

+----------------+----------+----------------------+--------------------------+

| _ Utilization | Warning | Inbound .: 24.97% | Outbound . . .: 49.93% |

| _ Retransmits | Critical | IFrames .: 1ð.ðð% | Bytes. . . . .: ð.1ð% |

| _ RNRs | Critical | Received .: 11.11% | Sent . . . . .: 11.11% |

| _ Virt Circs | Critical | Active VCs: 66.67% | Maximum VCs. .: 3 |

| _ Errors | Normal | Rate/Kbyte: N/A | Total errors .: N/A |

| _ QLength | Critical | IFrames . : 2 | |

+----------------+----------+----------------------+--------------------------+

Command ===> _________________________________________________________________



á ñ

Figure 14. X.25 Multichannel Link Resource Summary Panel

The upper portion of the panel shows configuration data for the MCH link.The lower portion shows performance statistics and a status light for eachstatistical category: utilization, retransmissions, and polling. For each ofthese categories, you can use the following action codes:

X Gives you exceptions.S Shows more details.A Displays an analysis panel.T Provides recent trends.


Chapter 4. PU-Level Resources

Chapter Contents

PU-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50PU Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 51X.25 Virtual Circuit Status . . . . . . . . . . . . . . . . . . . . . . . . . 52X.25 Virtual Circuit Resource Summary. . . . . . . . . . . . . . . . 53

Chapter 4. PU-Level Resources 49

PU-level Panels

PUs are considered subordinate to SDLC/BSC/CA lines in the NCP-to-LUhierarchy of resources. A PU may be an SDLC or channel adapter physicalunit, or a BSC cluster controller.

You can enter action code P (PUs) next to a specific SDLC/BSC/CA lineeither on the NCP Statistics Summary panel (see Figure 4 on page 32) or onthe SDLC/BSC/CA Line Status panel (see Figure 7 on page 37). The PUStatus panel lists the PUs for a specific line.


-------------------------------------------------------------17:51:12 11/14/94

KONDNNHD PU Status for SDLC Line: LS96ððA System: SYSA

More: >


X=Exceptions S=Show details L=LUs T=Trends

+------------+------+-------+-----+---------------+--------------------+------+

| | Line | Line | Que | Non-Productve | Polling | |

| PU Name | Util | Speed | Len | Polls Pct | Total Positive | Cond |

+------------+------+-------+-----+--------+------+----------+---------+------+

| S PS96ððA | 56% | 96ðð | 1 | 444 | 33% | 4,567 | 455 | Norm |

| _ PS96ððB | 1% | 96ðð | 2 | 777 | 37% | 7,545 | 431 | Norm |

| _ PS96ððC | 3% | 96ðð | 1 | 88 | 18% | 943 | 543 | Norm |

| _ PS96ððD | 25% | 96ðð | 1 | 9 | 32% | 677 | 613 | Norm |

+------------+------+-------+-----+--------+------+----------+---------+------+

Command ===> __________________________________________________________________



F2ð=Right

á ñ

Figure 15. PU Status Panel

This panel shows performance data and a status light for each PU connectedto the line. You can use the following action codes:

X Displays exceptions for a selected PU.S Displays a Resource Summary panel for a PU.L Lists the LUs for a PU.T Provides line utilization or non-productive poll trends for a PU.

Five more panels provide error, traffic, and high-, medium-, and low-priorityframe statistics for the listed PUs. Use F20 (Right) and F19 (Left) to scrollbetween them.


PU Resource Summary

When you enter action code S (Show details) next to an SDLC, BSC, orchannel adapter PU either on the NCP Status Summary panel (see Figure 3on page 30) or on the PU Status panel (see previous figure), a PU ResourceSummary panel appears.

à ð ____ Actions Goto Options Help

-------------------------------------------------------------ð9:16:24 11/14/94

KONDNNSD Resource Summary for PU: PS96ððA System: SYSA

More:



+-------------------------+-------------------------+-------------------------+

| PU name .: PS96ððA | PUTYPE.: 2 | MAXOUT . . .: 7 |

| Subarea .: 1ð | DUPLEX.: FULL | MAXDATA. . .: 265 |

| Element .: 2ð8 | IRETRY.: NO | PIUs In. . .: 1,528 |

| NCP . . .: NCPð1 | RETRIES: 5,5,6 | PIUs Out . .: 5,46ð |

| Line name: LS56K | REPLYTO: 3 | Bytes In . .: 44.4ðK |

| SPEED . .: 96ðð/96ðð | PASSLIM: 254 | Bytes Out. .: 66.ððK |

+----------------+--------+-------------------------+-------------------------+

| A Utilization | Normal | Inbound . . .: 21.23% | Outbound . .: 52.ðð% |

| _ Retransmits | Normal | PIUs. . . . .: 34.76% | Bytes. . . .: ð.34% |

| _ Polling | Normal | Total polls .: 1,499 | Non-prod . .: 9ð.93% |

| _ Errors | Normal | Rate per kbyt: ð | Total error.: 2 |


+----------------+--------+-------------------------+-------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 16. PU Resource Summary Panel

The upper portion of the panel shows VTAM configuration data for the PU.The lower portion shows performance statistics and a status light for eachcategory of statistics. For each category, you can use the following actioncodes:

X Gives you the exceptions that have been raised.S Provides more details.A Displays an analysis panel.T Gives you recent trends.


X.25 Virtual Circuit Status

When you use action code V (Virtual Circuits) on the NCP StatisticsSummary panel (see Figure 4 on page 32), or on a X.25 Multichannel LinkStatus Panel (for example, Figure 13 on page 47), the first of three X.25Virtual Circuit Status panels displays.


--------------------------------------------------------------18:51:41 ð5/25/96

KONDNNGD X.25 Virtual Circuit Status for MCH Link: X259ðð1A System: SYSA

More: >


X=Exceptions S=Show details L=LUs T=Trends

+------------+----------+------+-------+---------------+---------------+------+

| | | Link | Link | Total Bytes | Total IFrames | |

| VC Name | VC Type | Util | Speed | In Out | In Out | Cond |

+------------+----------+------+-------+---------------+---------------+------+

| _ RV56A123 | SVC | 1ðð% | 56K | 234K 456T| 456M 456M| Crit |

| _ RV96AA | PVC | 96% | 56K | 12K 14K| 745K 45K| Norm |

| _ RV96AB | SVC | 9% | 56K | 999 457| 11K 9K| Warn |

| _ XVCðð1 | SVC | 14% | 56K | 365 456| 8K 7K| Crit |

+------------+----------+------+-----------------------+---------------+------+

Command ===> __________________________________________________________________



F2ð=Right

á ñ

Figure 17. X.25 Virtual Circuit Status Panel 1 - Utilization

This panel displays VC utilization statistics, network type, and a status lightfor each VC using the specified MCH link. Depending on the originatingpanel, you see the multichannel link name or the network type (PVC, SVC,or SVC subarea node). You can use the following action codes:

X Displays exceptions for a VC.

S Displays a Resource Summary panel for a VC.

L Lists the LUs attached to a VC.

T Provides utilization, total IFrame, and total byte trends for a VC.

Two more panels provide retransmission and traffic statistics for the listedVCs. Use F20 (Right) and F19 (Left) to scroll between them.


X.25 Virtual Circuit Resource Summary

When you use action code S (Show Details) next to a virtual circuit on aVirtual Circuit Status panel (see Figure 17 on page 52) or on the NCPStatus Summary panel (see Figure 3 on page 30), the X.25 Virtual CircuitResource Summary panel appears.


--------------------------------------------------------------18:3ð:ð1 ð5/25/96

KONDNNID Resource Summary for X.25 Virtual Circuit: R9ðð System: SYSA



+-----------------------+-------------------------+----------------------------+

| SVC name. : R9ðð | Logical Chnl.: 1/1 | ANS . . . . . .: CONTINUE |

| MCH link. : X259ðð1A | INSLOW. . . .: (25,ð) | DBIT . . . . .: YES |

| NCP name. : NCPð1 | MAXPKTL. . . : 256 | LU count. . . .: 4 |

| LLC type. : ð | VWINDOW. . . : 2 +----------------------------+

| PUTYPE. . : 1 | MAXDATA . . .: 256 | Total bytes . .: 14.ððK |

| CALL. . . : INOUT | MAXOUT. . . .: 6 | Total data pkts: 3,658 |

| ID. . . . : 1/ððð2 | INACTO. . . .: N/A | Total IFrames .: 4ð233 |

+----------------+------+-------------------------+----------------------------+

| _ Utilization | Norm | Inbound . . .: 21.ð5% | Outbound . . .: 79.ð9% |

| _ Retransmits | Crit | IFrames . . .: 34.ð6% | Bytes . . . . .: 56.6ð% |

| _ D-Bits | Crit | Inbound . . .: 15.43% | Outbound. . . .: 41.3ð% |

| _ Errors | Crit | Rate/Kbyte. .: ð | Total errors. .: ð |

| _ QLength | Crit | IFrames . . .: 2 | |

+----------------+------+-------------------------+----------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 18. X.25 Virtual Circuit Summary Panel

The upper portion of this panel shows configuration data for the VC. Thelower portion shows statistics and a status light for each performancecategory: utilization, retransmissions, and D-Bit usage. For each category,you can use the following action codes:

X Displays exceptions.

S Shows more details.

A Displays an analysis panel.

T Provides recent trends.



Chapter 5. LU-Level Resources

Chapter Contents

LU-level Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56LU Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Resource Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59LU Resource Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 60X.25 LU Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5. LU-Level Resources 55

LU-level Panels

LUs are considered subordinate to PUs in the NCP-to-LU hierarchy ofresources. An LU may be an SDLC or channel adapter logical unit, a BSCterminal, or a logical unit device in an X.25 network.


LU Status Panel

You can enter action code L (LUs) next to a specific PU or VC on the NCPStatistics Summary panel (see Figure 4 on page 32), on the PU Status panel(see Figure 15 on page 50), or on the VC Status panel (see Figure 17 onpage 52). An LU Status panel lists the LUs attached to a specific PU orVC.


-------------------------------------------------------------17:51:11 11/14/94

KONDNNQD LU Status for PU: PS96ððA System: SYSA

More: >


X=Exceptions S=Show details E=RTA R=Resource analysis T=Trends

+------------+------+--------+--------+--------------------------------+------+

| | LU | Line | Queue | Line | Rate per Minute | |

| LU Name | Type | Util | Length | Speed | PIUs Byte | Cond |

+------------+------+--------+--------+--------+------------+----------+------+

| _ LS96ððAB | LU | 1ð% | 1 | 96ðð | 1,423 | 1,623 | Crit |

| _ LS96ððA2 | LU | 21% | 2 | 96ðð | 345 | 789 | Warn |

| _ LS96ððA6 | LU | 6% | 3 | 96ðð | 34 | 45 | Norm |

| R LS96ððA8 | LU | 16% | 1 | 96ðð | 235 | 217 | Crit |

+------------+------+--------+--------+--------+------------+----------+------+

Command ===> ________________________________________________________________


F1ð=Actiod Bar F11=Print F12=Cancel F14=Find F15=Status_Display **=Left

F2ð=Right

á ñ

Figure 19. LU Status Panel


Panel Description

The LU Status for PU panel shows performance statistics and a status lightfor each LU attached to the PU or VC. You can use the following actioncodes on this panel:

X Displays exceptions for a selected LU.

S Displays a Resource Summary panel for an LU.

E Takes you directly to the OMEGAMON II Response Times componentwhere the Average Response Times panel shows you response times forthe LU. This action is available for full SNA resources. Therefore, it isnot available for X.25 resources.

R Goes to a Resource Analysis panel for an LU.

T Provides line utilization or rate per minute trends for an LU.

Use F20 (Right) to scroll to a panel showing traffic data for the LUs attachedto the PU and and F19 (Left) to return to this panel.


Resource Analysis

If you enter action code R (Resource analysis) next to an LU on an LU Statuspanel (see previous figure), an analysis of the LU appears.

à ð____ Goto Options Help

-------------------------------------------------------------12:24:18 11/14/94

KONDARAD Resource Analysis for Terminal LS96ððAB System: SYSA

Network Address 25:2ð

+----------------------------+----------+--------------------------+----------+

| LU activation date . . . . | ð8/3ð/94 | Network ID . . . . . . . | CACOWLA1 |

| LU activation time . . . . | ð7:52:45 | Owning NCP name. . . . . | NCP1ðY |

| State. . . . . . . . . . . | ACTIVE | Owning line name . . . . | L9ðð |

| Desired state. . . . . . . | ACTIVE | Owning PU name . . . . . | L9ððA |

| LOGON mode table . . . . . | MODETAB1 | Subarea. . . . . . . . . | 25 |

| Default LOGMODE entry. . . | L32793B | Element address. . . . . | 2ð |

| Vary LOGON LOGMODE entry . | | | |

| Active PLU sessions. . . . | ð | USSTAB table name. . . . | USSTAB1 |

| Active SLU sessions. . . . | 1 | Major node name. . . . . | LOC66ð |

| Pending sessions . . . . . | ð | Major node type. . . . . | LCLNSNA |

| Pacing n-count . . . . . . | ð | VPacing n-count. . . . . | ð |

| Pacing m-count . . . . . . | ð | VPacing m-count. . . . . | ð |

+----------------------------+----------+--------------------------+----------+

Command ===> _________________________________________________________________


F11=Print F12=Cancel F15=Status Display

á ñ

Figure 20. Resource Analysis for Terminal Panel

This panel displays identifying information as well as details about activation,state, sessions, and pacing.

You can use the Sessions selection on the Goto pull-down menu to accessmore information about this LU's sessions.


LU Resource Summary

When you enter action code S (Show details) next to an LU either on theNCP Status Summary panel (see Figure 3 on page 30) or on the LU Statuspanel (see Figure 19 on page 57), an LU Resource Summary panel appears.


---------------------------------------------------------------:53:11 11/14/94

KONDNNUD Resource Summary for LU: LS96ððAB System: SYSA

More:



+-------------------------+------------------------+-------------------------+

| LU name. : LS96ððAB | XDOMAIN. .: N/A | PACING. .: ð |

| Subarea. : 25 | DLOGMOD. .: D4A32783 | VPACING .: ð |

| Element. : 3467 | PLU. . . .: N/A | PIUs In .: 58 |

| NCP name : NCPð1 | Line speed: 96ðð/96ðð | PIUs Out.: 22 |

| Line name: LS96ððA | TERM . . .: N/A | Bytes In.: 2,88ð |

| PU name. : PS96ððA | | Bytes Out: 4,32ð |

+----------------+--------+------------------------+-------------------------+

| S Utilization | Normal | Inbound . . .: ð.8ð% | Outbound . . : 1.2ð% |

| _ Rates | Critic | PIUs per min.: 16 | Bytes per min: 1,44ð |


+----------------+--------+------------------------+-------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 21. LU Resource Summary Panel

The upper portion of the panel shows VTAM configuration data for the LU.The lower portion shows performance statistics and a status light for eachcategory of statistics.

Action code X (Exceptions) gives you utilization, PIU rate, or queue lengthexceptions.

Action code T (Trends) displays utilization, PIU rate, or queue length trends.

Action code S (Show details) displays a Utilization Detail panel.

On this panel you access the Resource Analysis panel from the Gotopull-down menu.


X.25 LU Panels

There are no special X.25 logical unit panels. They look the same as SDLClogical unit panels, except for the title which tells you whether the LU isconnected to an X.25 link or virtual circuit.

When you use action code L (LUs) next to an NCP on the NCP StatisticsSummary panel (see Figure 4 on page 32), the Logical Unit Status panelsshow all attached logical units including X.25 logical units. Subsequentresource summary, analysis, and detail panels are available for X.25 as wellas SDLC logical units.

Likewise, when you use action code L (LUs) next to a link on an X.25Multichannel Link Status panel (see Figure 13 on page 47) or next to avirtual circuit on an X.25 Virtual Circuit Status panel (see Figure 17 onpage 52), all attached X.25 logical units appear. Subsequent X.25 LUresource summary, analysis, and detail panels are available.

There is no RTA action on X.25 logical unit panels because X.25 devices donot use full SNA capabilities. The End-to-End Response Time Featurerequires full SNA to generate response time statistics.



Chapter 6.Setting NCP Monitoring Options

Chapter Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Performance Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Warning and Critical Numeric Thresholds. . . . . . . . . . . . 65Warning and Critical Status. . . . . . . . . . . . . . . . . . . . . . 65Determining the Status Lights . . . . . . . . . . . . . . . . . . . . 65

Monitoring Options Pull-down . . . . . . . . . . . . . . . . . . . . . . 66NCP Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . 67

Default NCP Monitor Options . . . . . . . . . . . . . . . . . . . . 68NCP Site Monitor List . . . . . . . . . . . . . . . . . . . . . . . . . 76Summary of NCP Product Administrator Actions. . . . . . . . 87How Settings Are Determined When Monitoring NCPs. . . 88

Chapter 6. Setting NCP Monitoring Options 63

Overview

The Monitoring Options pull-down includes selections for setting exceptionthresholds and global product defaults, logging exceptions, writing trendrecords to the VSAM log file and SMF, selecting NCP resources to monitor,and other important options.

Only users with administrator authority can alter settings within theMonitoring Options selections. However, any user may view the currentsettings for these selections. A system administrator may grant authorizationduring an OMEGAMON II session via the User Authorities selection (see“User Authorities” in the OMEGAMON II for VTAM User's Guide.

OMEGAMON II provides an initial set of default values for MonitoringOptions. However, since the characteristics of NCP networks vary widely,you probably want to tailor the values to your specific network configuration.

Changes to NCP monitoring options take effect at the next sampling interval.

F1When you are using OMEGAMON II, you can press F1 if you need help.Helps include comprehensive field descriptions and detailed technicalinformation. If your cursor is on an input or display field when you pressF1, you get help for that field; otherwise, you get help for the panel.


Performance Objectives

OMEGAMON II enables you to set your own performance objectives bysetting thresholds. A threshold is a value that indicates an unsatisfactorylevel of performance. A critical threshold indicates a more unsatisfactory ormore severe condition than awarning threshold.

OMEGAMON II exception monitoring supports warning and criticalconditions for all exceptions.

Warning and Critical Numeric Thresholds

For those exceptions where you specify numeric or percentage thresholds,you can specify both warning and critical values. We recommend settingboth so that you are warned of an impending problem and also alerted whenthe problem needs immediate attention.

Warning and Critical Status

For those exceptions that monitor for the presence or absence of a specificactivity, you can decide how severe the condition is (warning or critical)when it occurs at your site.

Determining the Status Lights

The thresholds and conditions that you specify with the Monitoring Optionspop-ups determine the color of the status lights on OMEGAMON IIperformance displays. When OMEGAMON II detects that thresholds orconditions have been reached, status lights change from green (normal) toyellow (warning) to red (critical).

Be aware that exception recording must be active for normal, warning, andcritical status lights and exception messages to display. Otherwise, the statuslights are turquoise (idle).


Monitoring Options Pull-down

Select Monitoring Options from the Options pull-down to display the menushown in the following figure. The rest of this chapter describes the NCPPerformance selection on the Monitoring Options menu.

à ð KONDOMOD Monitoring Options

Select a choice by number, by mnemonic,

or with the cursor.

__ 1. Global options (O)...

2. Buffer pool options (B)...

3. Virtual route options (V)...

4. VTAM environment options (E)...

5. Response time options (R)...

6. NCP performance options (P)...

7. TNSTATS NCP options (N)...

8. TNSTATS CTC options (C)...

9. TNSTATS LOCAL options (L)...

1ð. Log file utilization (U)...

11. TCP/IP options (T)...

12. LU 6.2 options (X)...

F1=Help F12=Cancel

á ñ

Figure 22. Monitoring Options Menu


NCP Performance Options

The NCP Performance Options selection on the Monitoring Options menudisplays a menu with two selections:

Default Monitor Options Use to set site defaults for NCPs, line-level,PU-level, and LU-level resources.

Site Monitor List Use to list your NCPs and their subordinateresources. From this list, you can select specificNCPs or subordinate resources to changemonitor options, start monitoring, and stopmonitoring.

On the NCP options panels and throughout OMEGAMON II, we areassuming a hierarchy of NCP resources. In this manual, in the NCPMonitoring Guide, as well as in the product, NCP resource options andperformance statistics are presented in the following hierarchical order:

Highest level of the NCP hierarchy. |

| Network Control Program CCU (NCP)| Line-level resource (SDLC/BSC/CA line, MCH link, TRPL, TRLL)| PU-level resource (PU, cluster, virtual circuit)| Logical unit (LU, terminal, X.25 LU)

VLowest level of the NCP hierarchy.


Default NCP Monitor Options

When you select NCP Default Monitor Options on the NCP PerformanceOptions menu, the following menu appears.

à ðKONDOððD NCP Default Options

_ 1. NCP CCU options (A)...

2. Lines (SDLC/BSC/CA (B)...

3. PUs (PUs/clusters) (C)...

4. LUs (LUs/terminals) (D)...

5. Token-ring physical links (E)...

6. Token-ring logical links (F)...

7. X.25 multichannel links (G)...

8. X.25 virtual circuits (H)...

9. X.25 logical units (I)...

F1=Help F12=Cancel

á ñ

Figure 23. NCP Default Options Menu

This menu lists the types of NCP resources for which you can set defaultmonitoring options. The settings you specify are for all resources of thattype at your site. You can override the settings for specific resources usingthe Site Monitor List (see Figure 33 on page 76). The default settingsremain in effect for all other resources of that type. When you modify sitedefault options, the changes take effect the next sampling interval for thoseresources using the site defaults.

The panels you use to specify default options for each type of resource areshown below. For an explanation of any option, place the cursor in the inputfield and press F1 (Help).


| Default Monitor Options for NCPs

| Use the upper portion of the NCP default options panel shown in the| following figure to specify global NCP options. Global options apply to all| NCP resources monitored. However, you can override the Start level,| Autostart, and Monitor or Collect options for specific resources (see “NCP| Site Monitor List” on page 76). The NCP Collection Interval is read-only.

| NCP Collection Interval| How often the NCP collector queries your monitored NCPs for| performance data and OMEGAMON II updates the data in NCP| performance panels. This interval is specified during CICAT| configuration of OMEGAMON II and cannot be changed using this| panel.

| For information about how OMEGAMON II synchronizes the NCP| collection interval with the hardcoded TIC3 sample interval in the| 3746-M900, see “TIC3 Data Collection” on page 40.

Topology Update IntervalHow often to query the NCP collector for the current NCP topology,including resources dynamically added or deleted, and newly activatedNCPs. If you have a network that changes often, specify a smallerinterval to keep the topology current. If you have a fairly staticnetwork, specify a larger interval which conserves system resources.

Exception/Trend RecordingWhether to record exceptions or trends on the VSAM log file orSMF.

Line-type DefaultWhich type of line to display first when specifying options or viewingresource utilization data. You can select the other line types from aprompt menu.

Start Options Pop-upWhether you want to view the current monitor options when you startmonitoring a selected resource. You can use the pop-up to confirm orchange options.

Start levelWhen you start monitoring, how far down the NCP-to-LU hierarchyto perform the start. For example, if you start monitoring an NCPand specify Line, then the NCP and all its lines are started.

AutostartWhether monitoring starts during OMEGAMON II initialization orwhen the NPALU goes into session with the NCP collector, orwhether you use the R (Start) action code on the Site Monitor List tostart monitoring a specific resource.


Monitor or CollectWhether to monitor the resource and record exception and trend data,or merely collect trend data for recording on the log file or SMF.

à ðKONDOð1D Default Monitor Options for NCPs

NCP collection interval . 3ðð Seconds

Topology update interval. 1 H + (M-Min/H-Hours)

Exception recording . . . N + (N-None/L-Log/S-SMF/B-Both)

Trend recording . . . . . N + (N-None/L-Log/S-SMF/B-Both)

Line-type default . . . . None + (none,SDLC,TRPL,TRLL,X.25)

Start options pop-up. . . Yes + (Yes/No)

Start level . . . . . . . N + (N-NCPs/K-Lines/P-PUs/L-LUs)

Autostart . . . . . . . . Yes + (Yes/No)

Monitor or Collect. . . . M + (M-Monitor/C-Collect)

Exceptions Y/N Warning Critical

--------------------------- --- ------- --------

CCU cycle utilization . . . Yes + 75_ 9ð_ %

Buffer utilization. . . . . Yes + 75_ 88_ %

Slowdown. . . . . . . . . . Yes + 1__ 1ð_ %

PIUs on channel hold queue. No_ + _______ _______

PIUs on intermediate queue. No_ + _______ _______

NPALU failure . . . . . . . Yes + W + (W-Warning/C-Critical)

F1=Help F4=Prompt F12=Cancel F21=Prev F22=Next

á ñ

Figure 24. Default Options for NCPs

Use the lower portion of this panel to specify site default exceptionconditions, thresholds, and severities for NCP communication control units(CCUs).

Default Options for SDLC Lines

à ðKONDOð2D Default Options for SDLC/BSC/CA Lines


------------------------- --- ------- --------

Line utilization. . . . . Yes + 35_ 5ð_ %

Retransmitted bytes . . . Yes + 2__ 5__ %

Retransmitted PIUs. . . . Yes + 2__ 5__ %

Temporary errors. . . . . Yes + 2__ 5__ %

Non-productive polls. . . No_ + 95_ 1ðð %

PIUs on outbound queue. . No_ + _______ _______

Idle detection. . . . . . No_ + W + (W=Warning/C=Critical)


á ñ

Figure 25. Default Options for SDLC Lines


Use this panel to specify site default exception settings for SDLC, BSC, andchannel adapter (CA) communication links.

Default Options for SDLC PUs

à ðKONDOð3D Default Options for PUs/Clusters


------------------------ --- ------- --------

Line utilization. . . . . No + ___ ___ %

Retransmitted bytes . . . No + ___ ___ %

Retransmitted PIUs. . . . No + ___ ___ %

Temporary errors. . . . . No + ___ ___ %

Non-productive polls. . . No + ___ ___ %

PIUs on outbound queue. . No + _______ _______



á ñ

Figure 26. Default Options for SDLC PUs

Use this panel to specify site default exception settings for SDLC andchannel adapter physical units, and BSC cluster controllers.

Default Options for SDLC LUs

à ðKONDOð4D Default Options for LUs/Terminals


------------------------ --- -------- --------

Line utilization. . . . . No_ + ___ ___ %

PIUs per minute . . . . . No_ + ________ ________

PIUs on outbound queue. . No_ + ________ ________



á ñ

Figure 27. Default Options for SDLC LUs

Use this panel to specify site default exception settings for SDLC logicalunits, programmed resource virtual logical units, BSC logical units(terminals), and channel adapter logical units.


| Default Options for Token-Ring Physical Links

| à| ð| KONDOð5D Default Options for Token-Ring Physical Links

| Exceptions Y/N Warning Critical

| -------------------------- --- ------- --------

| TIC utilization. . . . . . Yes + 2ð_ 3ð_ %

| Congestion . . . . . . . . Yes + 1__ 5__ %

| Retransmitted bytes. . . . Yes + 2__ 5__ %

| Retransmitted IFrames. . . Yes + 2__ 5__ %

| Frames per minute. . . . . No_ + ________ ________

| Connection count . . . . . No_ + ________ ________

| IFrames on outbound queue. No_ + ________ ________

| Idle detection . . . . . . No_ + W + (W=Warning/C=Critical)

| F1=Help F4=Prompt F12=Cancel F21=Prev F22=Next

| á| ñ

| Figure 28. Default Options for Token-Ring Physical Links

| Use this panel to specify default exception settings for token-ring physical| links (TRPLs).

| Default Options for Token-Ring Logical Links

| à| ð| KONDOð6D Default Options for Token-Ring Logical Links

| Exceptions Y/N Warning Critical

| ------------------------- --- ------- --------

| Retransmitted bytes . . . Yes + 2__ 5__ %

| Retransmitted IFrames . . Yes + 2__ 5__ %

| Reply timeouts. . . . . . Yes + 2__ 5__ %

| Frames per minute . . . . No_ + ________ ________

| IFrames on outbound queue No_ + ________ ________

| Idle detection. . . . . . No_ + W + (W=Warning/C=Critical)

| F1=Help F4=Prompt F12=Cancel F21=Prev F22=Next

| á| ñ

| Figure 29. Default Options for Token-Ring Logical Links

| Use this panel to specify default exception settings for token-ring logical| links (TRLLs).


| TIC3 Exceptions

| Because TIC3 data for the following fields is unavailabe, the corresponding| exceptions for TIC3 resources are ignored:

| Á retransmitted IFrames| Á IFrames on outbound queue| Á connection count| Á reply timeouts| Á congestion count

X.25 Multichannel Link Default Options

Use this panel to specify default exception and threshold settings for X.25multichannel (MCH) links.

à ð KONDO1ðD Default Options for X.25 Multichannel Links


------------------------- --- ------- --------

Link utilization . . . . . Yes + 45_ 55_ %

Retransmitted bytes. . . . Yes + 2__ 5__ %

Retransmitted IFrames. . . Yes + 2__ 5__ %

RNR frames . . . . . . . . No_ + ___ ___ %

VC utilization . . . . . . Yes + 9ð_ 95_ %

Error rate/kbyte . . . . . Yes + 2_______ 5_______

IFrames on outbound queue. No_ + ________ ________

Idle detection . . . . . . No_ + W + (W-Warning/C-Critical)


á ñ

Figure 30. X.25 Multichannel Links Default Options Panel


X.25 Virtual Circuits Default Options

Use this panel to specify default exception and threshold settings for X.25virtual circuits.

à ð KONDO11D Default Options for X.25 Virtual Circuits


------------------------- --- ------- --------

Link utilization . . . . . No_ + ___ ___ %

Retransmitted bytes. . . . Yes + 2__ 5__ %

Retransmitted IFrames. . . Yes + 2__ 5__ %

D-bit packets. . . . . . . No_ + ___ ___ %

Error rate/kbyte . . . . . Yes + 2_______ 5_______

IFrames on outbound queue. No_ + ________ ________

Idle detection. . . . . . No_ + W + (W-Warning/C-Critical)


á ñ

Figure 31. X.25 Virtual Circuits Default Options Panel

X.25 Logical Units Options

The exception and threshold settings you specify on this panel affect X.25logical units only. Use this panel to specify your site's defaults for X.25LUs.

à ð KONDO12D Default Options for X.25 LUs


------------------------- --- ------- --------

Link utilization . . . . . No_ + ___ ___ %

PIUs per minute. . . . . . No_ + ___ ___ %

PIUs on outbound queue . . No_ + ________ ________

Idle detection. . . . . . No_ + W + (W-Warning/C-Critical)


á ñ

Figure 32. X.25 Virtual Circuits Default Options Panel


Guidelines

When setting NCP-resource thresholds, consider the following generalguidelines:

Á SDLC line utilization thresholds may be slightly higher than BSC lineutilization thresholds.

Á Set retransmission and error rates for all line-types low.

Á Set TRPL congestion thresholds low.

Á Set non-productive polling thresholds high.

Á To calculate PU line utilization thresholds, divide total line utilizationamong the number of attached PUs, giving more weight to more heavilyused PUs.

Á File and graphics transfers can generate high PIU rates to an LU. SetPIU thresholds for LUs accordingly.

Á Refer to the Calculations chapter in the OMEGAMON II for VTAM NCPMonitoring Guide, for the formulas used to calculate the NCPperformance statistics on which exceptions are based.

Navigation

The default options panels include F21 (Prev) and F22 (Next). Thesefunction keys provide a quick way to navigate to the next or previous defaultoptions panel. It is an alternative to returning to the NCP Default Optionsmenu and then selecting another resource. The panels appear in the sameorder that the selections appear on the menu. (See the menu in “DefaultNCP Monitor Options” on page 68.)

For example, when you are on the SDLC PUs options panel,

Á F21 (Prev) takes you directly to SDLC LinesÁ F22 (Next) takes you directly to SDLC LUs


NCP Site Monitor List

When you select Site Monitor List on the NCP Performance Options menu,a list of your NCPs appears as shown in the following figure.

à ð KONDOLLD NCP Site Monitor List

More:

Enter one of the following action codes. Lines 1 to 6 of 6

R=Start P=Stop L=List U=Unlist C=Change D=Delete T=Reset

M=Mark O=Copy V=View

+---------------------------+------+---------+------------+-------------+

| NCP Generation | | | Mon Opts | Start |

| Resource Date Time | Type | Status | Mode Level | Mode Level |

+---------------------------+------+---------+-----+------+------+------+

| _ NCPð1 ð1/24/96 23:ð4 | NCP | Started | Mon | NCP | Auto | Line |

| _ NCPð1 ð1/2ð/96 15:3ð | NCP | Stopped | Mon | NCP | Auto | NCP |

| _ NCPð2 ð8/26/96 17:25 | NCP | Started | Mon | NCP | Auto | NCP |

| _ NCPð3 ð1/11/96 13:24 | NCP | Started | Mon | NCP | Auto | Line |

| _ NCPð4 ð1/ð6/96 12:13 | NCP | Started | Mon | NCP | Auto | PU |

| _ NCPð4 ð7/24/95 23:ð4 | NCP | Stopped | Mon | NCP | Auto | Line |

+---------------------------+------+---------+-----+------+------+------+

F1=Help F4=View F5=Refresh **=Bkwd **=Fwd F12=Cancel F14=Find

á ñ

Figure 33. NCP Site Monitor List

This panel lists your currently and previously active NCPs. You can use thislist to

Á enumerate the NCPs and their subordinate resources at your siteÁ view the type, gen date, and monitoring status of NCP resourcesÁ control (start or stop) monitoring of specific resourcesÁ view or modify monitoring options for specific resources

The following fields on this panel describe the monitoring status of eachNCP resource:

Status Whether monitoring of this resource is started, stopped,pending, not applicable (NA), or NPALU collection wasspecified as NO in the NCP generation.

Mon Mode Whether you are monitoring and logging exception and trenddata for this resource (Mon) or merely logging trend data(Col).

Opts Level What level in the NCP-to-LU hierarchy determines the optionsfor this resource. For example, if the resource is an SDLCline and Opts Level is NCP, then the options for this line arethose specified for all the SDLC lines connected to this NCP.If the resource is a line and Opts Level is Line, then theoptions are specific to this line.


Start Mode Whether this resource is autostarted at OMEGAMON IIinitialization or when the NPALU goes into session with theNCP collector (Auto), or whether you must use the start actionto manually start monitoring (Manu).

Start Level How far down the NCP-to-LU hierarchy monitoring begins.For example, when you start monitoring an NCP, if the startlevel is NCP, only NCP monitoring starts. If the start level isPU, then monitoring begins for the NCP, its lines, and its PUs.

The changes to options that you make via the Site Monitor List override thesite default options. Using the Site Monitor List, you can change optionsonly when monitoring of the resource is stopped.

You can revert to monitoring with the site defaults whenever necessary.

Dynamic Configuration

OMEGAMON II dynamically maintains an NCP topology table from theNCP resource resolution table (RRT) when the following are true:

Á The NPALU is available.Á The RRT is available.Á The NPALU and the NCP collector are connected.Á The NCP generation source is in VTAMLST.

The RRT is a load module produced by an NCP generation process. Itdescribes the NCP resources that are defined in the NCP macro sourcedefinitions. For more information about the NPALU and the NCP collector,see the OMEGAMON II for VTAM Configuration and Customization Guide.

The NCP topology table is the source of the resources listed on the SiteMonitor List panel. If a resource becomes inactive it remains on the SiteMonitor List. It is the responsibility of the OMEGAMON II productadministrator to remove inactive NCPs from the Site Monitor List when youno longer need them.


Resource Types

On the Site Monitor List, the VTAM Type field indicates the type ofresource displayed. The following resource types are supported:

NCP local or remote 37x5 SDLC SDLC lineBSC BSC lineCA channel adapter lineX25L X.25 multichannel linkTRPL token-ring physical linkTRLL token-ring logical link PU SDLC or channel adapter physical unitCLST BSC clusterPVC X.25 permanent virtual circuitSVC X.25 switched virtual circuitSVCS X.25 switched virtual circuit subarea node LU SDLC, channel adapter, or X.25 MCH logical unitTERM BSC terminal

Listing and Unlisting Resources

Use the L (List) action on the Site Monitor List to list the next level ofsubordinate resources for a selected resource. For example:

1. If you enter action codeL (List) next to an NCP, you see all the linesattached to that NCP.

2. If you enter action code L (List) next to an SDLC line, you see all thePUs attached to the line.


à ð KONDOLLD NCP Site Monitor List

More: -+

Enter one of the following action codes. Lines 14 to 28 of 246

R=Start P=Stop L=List U=Unlist C=Change D=Delete T=Reset

M=Mark O=Copy V=View

+---------------------------+------+---------+------------+-------------+

| NCP Generation | | | Mon Opt | Start |

| Resource Date Time | Type | Status | Mode Level | Mode Level |

+---------------------------+------+---------+-----+------+------+------+

| XLðð2P | X25L | Started | Mon | Line | Auto | Line |

| PPðð24ð2 | SVC | Started | Mon | VC | Manu | VC |

| XLUðð23 | LU | Stopped | Mon | Site | | |

| XLUðð22 | LU | Started | Mon | LU | Auto | LU |

| XLUðð21 | LU | Stopped | Mon | LU | Manu | LU |

| PPðð24ð1 | SVC | Stopped | Mon | VC | Manu | VC |

| PPðð24ðð | SVC | Stopped | Mon | VC | Manu | VC |

| NCPð2 ð8/26/96 17:25 | NCP | Started | Mon | Site | Auto | NCP |

| ACADLððð | SDLC | Started | Mon | Site | | |

| ACADCU3P | PU | Pending | Mon | Site | | |

| ACADB3Pð | LU | Stopped | Mon | Site | | |

| ACADB3P1 | LU | Stopped | Mon | Site | | |




+---------------------------+------+---------+-----+------+------+------+

Command ===> ____________________________________________________________

F1=Help F4=View F5=Refresh F7=Bkwd F8=Fwd F9=Retrieve F12=Cancel

F14=Find F17=Topology update

á ñ

Figure 34. NCP Site Monitor List with Subordinate Resources

You can use the U (Unlist) action to remove listed resources from theSite Monitor List. Continuing with the example above:

3. If you enter action code U (Unlist) next to the listed SDLC line, its PUsare removed from the Site Monitor List.

4. If you enter action code U (Unlist) next to the NCP, its lines are removedfrom the Site Monitor List.

Although the List and Unlist actions add and delete subordinate resourcesfrom the Site Monitor List panel, the NCPs and all their subordinateresources remain in the NCP topology table so that they can be monitored.

Updating NCP Topology on Demand

If you are a system administrator, you can use F17 (Topology Update) torequest an update of your NCP topology when required. You specify yoursite's topology update interval on the NCP Default Options panel. (See“Default NCP Monitor Options” on page 68.) You can use F17 to updateyour topology instead of waiting for your site's topology update interval toelapse. The topology update may take several minutes. During that timeyour session is locked.


Scrolling through the Site Monitor List

When you use the L (List) action to display subordinate resources, the SiteMonitor List can become quite long. There are several different ways toscroll through the list:

Á To scroll to the next page, press F8 (Fwd).

Á To scroll to the previous page, press F7 (Bkwd).

Á To scroll to a specific resource, press F14 (Find) and then enter theresource name.

Á To scroll to the bottom of the display, enter M in the command line andpress F8 (Fwd).

Á To scroll to the top of the display, enter M in the command line and pressF7 (Bkwd).

Á To scroll forward a number of lines, enter the number in the commandline and press F8 (Fwd).

Á To scroll backward a number of lines, enter the number in the commandline and press F7 (Bkwd).

Á To scroll to a line number, enter the number after Lines at the upperright.

Sorting and Filtering the Site Monitor List

When you press F4 (View) on the Site Monitor List panel, the View menushown in the following figure appears so that you can filter or sort theresources currently listed.

à ð

1 1. All (A)

2. Some (S)...

1 1. Unsorted in list order (L)

2. Sort by NCP name, date, and time (N)...

3. Sort by date and time (D)...

F1=Help F12=Cancel

á ñ

Figure 35. NCP Site Monitor List View Menu

The default view is all resources in list order. You have the option to sort byNCP name, generation date, and time or just gen date and time.


If you select Some from the View menu, the following panel appears.

à ð KONDOLLS View Some

Type view criteria and press Enter.

Field Operator Value

-------------- -------- --------

Resource name EQ + ________ (* for generics)

Resource type EQ + ____ + (NCP/LINK....)

VTAM status EQ + _____ + (ACTIV/INACT)

Monitor status EQ + _____ + (ACTIV/INACT/UNDEF)

Mode EQ + ___ + (Mon/Col)

Options EQ + ____ + (Def/Spec)

Autostart EQ + ___ + (Yes/No)

F1=Help F4=Prompt F12=Cancel

á ñ

Figure 36. NCP Site Monitor List View Some

You specify view criteria in the View Some panel. Only those resources onthe Site Monitor List that match your criteria will be displayed. You canprovide criteria for any or all of the fields shown. You can use a specific orgeneric resource name. Use an asterisk (*) to specify a generic name. Enterspecific values in the remaining fields. F4 (Prompt) prompts you with a listof valid values for the field in which your cursor is positioned.

The filtered or sorted view of the Site Monitor List remains in effect for thecurrent display of the list. The next time you select the Site Monitor Listfrom the NCP Performance Options menu, the default view appears.

Viewing Current Settings

Monitoring options for a resource may be the site defaults, defaults for theowning resource, or specific to the particular resource. To view the settingsthat are currently in effect, enter action code V (View) next to the resource.

Overriding Default Options

The site default monitoring options apply to all NCPs and their subordinateresources unless you specifically override them on the Site Monitor List.The Opt Level field on the Site Monitor List displays Site, Line, VC, PU,or LU. This field tells you from what resource level the monitoring optionsfor the resource were derived, or whether the site defaults apply (Site). Thefollowing sections show you the various ways to override site default optionsand also how to revert to the site defaults.


Changing Options for a Specific Resource

Use action code C (Change) next to a selected resource on the Site MonitorList to view the monitoring options currently in effect and to modify them asyou wish. You can use the Change action only when monitoring of theresource is stopped. A Change Options panel appears showing you thecurrent options in effect. They may be specific to that resource or the sitedefaults.

à ðKONDO19D Change Options for SDLC/BSC Line: L616A3ð

Start level. . . . . . . K + (K-Lines/P-PUs/L-LUs)

Autostart. . . . . . . . Yes + (Yes/No)

Monitor or Collect . . . M + (M-Monitor/C-Collect)


------------------------ --- ------- --------


Restransmitted bytes. . . Yes + 2__ 5__ %

Figure 37. Change Options for an SDLC Line

The Change Options panel names the specific resource you selected from theSite Monitor List. You can modify any of the options in this panel. Theoptions apply only to the selected resource. The values you specify on theChange Options panel become overrides for monitoring that particularresource.

Changing Options for Subordinate Resources

If you use the Change action to override monitoring options for a selectedresource that has subordinate resources, you can specify overrides for thesubordinates as well. Resources that have subordinates are NCPs, SDLC,BSC, or channel adapter lines, and PUs. Remember that you can use theChange action only when monitoring of the resource is stoppeed.

The F21 (Prev) and F22 (Next) keys provide direct navigation between theChange Options panel for a selected resource and the Change Options panelsfor its subordinates. The following example illustrates how you can changemonitoring options for subordinates:

1. If you use the Change action to change options for line L616A30 andthen press F22 (Next), a Change PUs Options panel appears. Use thispanel to override the monitoring options for all the PUs connected to theline.


à ð KONDO23D Change Options for SDLC PUs/Clusters

Attached to Line: L616A3ð


------------------------- --- ------- --------


Retransmitted bytes . . . No_ + ___ ___ %

Figure 38. Change Options for SDLC PUs Attached to a Line

2. If you press F22 (Next) again, you can use the Change LUs Optionspanel to override the default monitoring options for all the LUsconnected to the line.

à ð KONDO24D Change Options for SDLC LUs/Terminals

Attached to Line L616A3ð


------------------------- --- ------- --------


PIUs per minute . . . . . No_ + ________ ________

Figure 39. Change Options for SDLC LUs Attached to a Line

3. If you press F21 (Prev), the Change PUs Options panel reappears.

4. If you press F21 (Prev) again, the Change Line Options panel reappears.

If you want to change the monitoring options for only one PU attached to theline, use the Change action next to the specific PU on the Site Monitor List.Likewise, if you want to change monitoring options for one LU, use theChange action next to the specific LU on the Site Monitor List.

Copying Options

If you specified options for a particular resource on the Site Monitor List andyou want to use the same options for one or several other resources of thesame type, use the M (Mark) and C (Copy) action codes. Enter the Markaction next to the resource whose options you want to use (the source). Thenenter the Copy action next to the resource(s) for which you want the sameoptions (the targets). For each occurrence of the Copy action, a pop-up asksyou to specify which of the two following options you want:

Single Copies the options for the marked resource to the targetresource only.

Propagate Copies the options for the marked resource and itssubordinates to the target resource and its subordinates.

The options for any resources subordinate to the target but not subordinate tothe source resource are set to site default values.


Resetting Options

After specifying monitor options for an NCP resource on the Site MonitorList, you may decide to revert to default values. Enter action code T (Reset)next to the resource on the Site Monitor List. Specific monitoring optionsfor the selected resource are deleted. Options for this resource revert to anyexisting defaults that are in effect for its owning resources, or if none to thesite defaults.

For example, if you use the Reset action on a specific PU, the followinghappens:

1. Options specific to the PU are deleted.

2. If options were specified for the PUs attached to the owning line, thoseoptions take effect.

3. Otherwise, if options were specified for the PUs attached to the owningNCP, those options take effect.

4. Otherwise, the site defaults for PUs take effect.

For a graphical depiction, see “How Settings Are Determined WhenMonitoring NCPs” on page 88.

When you enter the Reset action, a pop-up asks you if you also want to resetoptions for the resources subordinate to the selected resource. If you specifyYes, OMEGAMON II determines default settings for the subordinateresources in the same manner that it determines defaults for the owningresource.

Start Monitoring

On the Site Monitor List, you can use the R (Start) action code next to aspecific NCP or subordinate resource to start monitoring. Monitoring willbegin for the selected resource, its owning resources, and optionally for itssubordinates.

Note: After you specify Start, you will not see any data for the startedresource until at least one full NCP collection interval has elapsed.

When you start monitoring a resource, each of its owning resources is startedautomatically. For example, if you specify the Start action for an SDLC PU,monitoring is also started for the owning line and the owning NCP.


In addition, you specify start level on the options panel for the resource. Thestart propagatesdown the NCP-to-LU hierarchy to the specified start level.For example:

Á If you enter action code R (Start) next to an NCP and the start level isNCP, only the selected NCP is monitored.

Á If you enter action code R (Start) next to an NCP and the start level isPUs, the NCP, its lines, and its PUs are monitored.

When you start monitoring a resource, you have the option to change thesettings that will be in effect following a successful start. This is an optionyou specify on the NCP Default Options panel. (See “Default MonitorOptions for NCPs” on page 69.) If you specified Yes in the Start OptionsPop-up field, a Start Options panel showing the current monitoring optionsfor the selected resource appears when you start monitoring the resource, asshown below. The options in effect may be specific to that resource or theymay be the site defaults. You use the Start Options panel to confirm ormodify the options under which monitoring is to proceed.

à ðKONDO19D Start Options for SDLC Line L616A3ð

Start level. . . . . . . K + (K-Lines/P-PUs/L-LUs)

Autostart. . . . . . . . Yes + (Yes/No)

Monitor or Collect . . . M + (M-Monitor/C-Collect)


------------------------- --- ------- --------


Restransmitted bytes. . . Yes + 2__ 5__ %

Figure 40. Start Options for an SDLC Line

The Start Options panel looks like the Change Options panel for thatresource type. It includes F21(Prev) and F22(Next) for confirming ormodifying options for the resources subordinate to the selected resource.

If you specified Autostart on the NCP Default Options panel, monitoringstarts during OMEGAMON II initialization and the Start Options panel doesnot appear.

When you change monitoring options for a resource, if the new set of optionsincludes Yes for Autostart, monitoring of the resource is automaticallyrestarted.


Stop Monitoring

Use the P (Stop) action code next to a resource on the Site Monitor List tostop monitoring the resource. If you specified Autostart on the NCP DefaultOptions panel, you can use the Stop action to stop monitoring selectedresources.

When you request to stop monitoring a resource, monitoring of itssubordinate resources is also stopped. When subordinate resources areeffected, a confirmation pop-up enables you to cancel the Stop.

Deleting Inactive NCPs

OMEGAMON II derives the NCP resources in the Site Monitor List fromthe NCP topology table, which it constructed from the NCP RRT.OMEGAMON II dynamically adds new resources as the NCP topologychanges. OMEGAMON II does not automatically delete NCPs when theybecome inactive. It is possible that they may become active again at a latertime.

If an NCP is obsolete and therefore no longer requires monitoring, youshould delete the NCP from the Site Monitor List. Enter theD (Delete)action code next to the obsolete NCP on the Site Monitor List. The NCPand all of its subordinate resources are removed from both the Site MonitorList panel and the persistent NCP topology table.

For optimum OMEGAMON II performance, we recommend that youmaintain a current NCP Site Monitor List that includes only the NCPs thatyou require.

When you request NCP deletion, a confirmation pop-up appears as shown inthe following figure.

à ð

You asked to delete NCP NCPA6 and

all monitoring options for resources

belonging to this NCP from the Site

Monitor List.

To confirm press Enter.

To cancel press F12.

F1=Help F12=Cancel

á ñ

Figure 41. Confirm Delete from Site Monitor List


Summary of NCP Product Administrator Actions

The following diagram summarizes how an OMEGAMON II productadministrator sets NCP monitoring options.

┌───────────┐ │Product │ │Admin: │ │ │

│ ADMIN=YES │ │ │ └─────┬─────┘ │

Using │ Options Pull─down ┌────────────────────────────┼ │ │ 6 6 ┌───────────┐ ┌───────────┐

│ Update NCP│ │ Update │ │ default │ │ Site │ │ monitoring│ │ Monitor │ │ options │ │ List │ │ │ │ │ └───────────┘ └─────┬─────┘ │ │ │ ┌────────┬──────────────┬──────────────┬─────┴────────┬──────────────┬──────────────┬────────┐ │ D │ R │ P │ C │ C │ C │ C │ M/C

│ 6 6 6 NCP 6 Line 6 PU 6 LU ││ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ │

│ │Start │ │Stop │ │ Change │ │ Change │ │ Change │ │ Change │ │ │ │monitoring │ │monitoring │ │ options │ │ options │ │ options │ │ options │ │ │ │selected │ │selected │ │ for │ │ for │ │ for │ │ for │ │

│ │resource & │ │resource & │ │ selected │ │ selected │ │ selected │ │ selected │ │ │ │owning res.│ │owning res.│ │ NCP │ │ line │ │ PU │ │ LU │ │

│ └───────────┘ └───────────┘ └─────┬─────┘ └──────┬────┘ └─────┬─────┘ └───────────┘ │ │ │ │ │ │ │ ┌──────────────┬────────┴─────┐ │ │ │

│ │ │ │ │ │ │ │ 6 Lines 6 PUs 6 LUs │ 6 LUs │

│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │ ┌───────────┐ │ │ │Change │ │Change │ │Change │ │ │Change │ │ │ │options for│ │options for│ │options for│ │ │options for│ │

│ │all lines │ │all PUs │ │all LUs │ │ │all LUs │ │ │ │in selected│ │in selected│ │in selected│ │ │in selected│ ┌────────┘

│ │NCP │ │NCP │ │NCP │ │ │PU │ ││ └───────────┘ └───────────┘ └───────────┘ │ └───────────┘ │

6 │ 6 ┌───────────┐ ┌─────┴─────────┐ ┌───────────┐ │ Delete │ ┌───────┐ │ │ │ Copy │ │ inactive │ │Confirm│ 6 PUs 6 LUs │ options │ │ NCP & all │%────5│delete │ ┌───────────┐ ┌───────────┐ │ to like │ │ associated│ └───────┘ │Change │ │Change │ │ resource │ │ options │ │options for│ │options for│ │ & subords.│ └───────────┘ │all PUs │ │all LUs │ └───────────┘ │in selected│ │in selected│ │line │ │line │ └───────────┘ └───────────┘

Figure 42. How Product Administrator Maintains NCP Options


How Settings Are Determined When Monitoring NCPs

The following diagram illustrates how OMEGAMON II determinesmonitoring options and exceptions settings when monitoring NCP resources.

┌───────────────┐ │ │

│ How ││ NCP settings ││ are │

│ determined │ │ │ └───────┬───────┘ │ ┌───────────────────────┬───────────┴───────────┬───────────────────────┐

│ if LU │ if PU │ if Line │ if NCP6 6 6 6

┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐ │ Settings │ │ Settings │ │ Settings │ │ Settings │ │ for specific LU │ │ for specific PU │ │ for specific line │ │ for specific NCP │ │ │ │ │ │ │ │ │ └──────────┬──────────┘ └──────────┬──────────┘ └──────────┬──────────┘ └──────────┬──────────┘ │ otherwise │ otherwise │ otherwise │ otherwise

6 │ │ │┌─────────────────────┐ │ │ ││ Settings │ │ │ ││ for LUs │ │ │ │ │ in owning PU │ │ │ │└──────────┬──────────┘ │ │ │

│ otherwise │ │ │6 6 │ │

┌─────────────────────┐ ┌─────────────────────┐ │ │ │ Settings │ │ Settings │ │ │ │ for LUs │ │ for PUs │ │ │ │ in owning line │ │ in owning line │ │ │ └──────────┬──────────┘ └──────────┬──────────┘ │ │ │ otherwise │ otherwise │ │

6 6 6 │ ┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐ │ │ Settings │ │ Settings │ │ Settings │ │ │ for LUs │ │ for PUs │ │ for lines │ │ │ in owning NCP │ │ in owning NCP │ │ in owning NCP │ │ └──────────┬──────────┘ └──────────┬──────────┘ └──────────┬──────────┘ │ │ otherwise │ otherwise │ otherwise │

6 6 6 6 ┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐ │ Site default │ │ Site default │ │ Site default │ │ Site default │ │ settings for LUs │ │ settings for PUs │ │ dettings for lines │ │ settings for NCPs │ │ │ │ │ │ │ │ │ └─────────────────────┘ └─────────────────────┘ └─────────────────────┘ └─────────────────────┘

Figure 43. NCP Site Profile Hierarchy of Settings

When monitoring occurs, OMEGAMON II determines the settings by thehierarchy shown, following the diagram downward.

When you use action code T (Reset) on the Site Monitor List,OMEGAMON II resets monitoring options to the next higher level in thehierarchy, following the diagram upward.


Chapter 7. Scenarios

Chapter Contents

Recommended Monitoring Scope. . . . . . . . . . . . . . . . . . . . . 90Case Study 1: LU Reporting Poor Response Time. . . . . . . . . 91Case Study 2: Identifying Line Problem Before Users Report. 93Case Study 3: Is Additional Line Capacity Required?. . . . . . . 95Case Study 4: NCP Storage Shortage. . . . . . . . . . . . . . . . . 97

Chapter 7. Scenarios 89

Recommended Monitoring Scope

This chapter presents four scenarios using the NCP monitor component. Inthese cases, we are assuming that you are already monitoring all NCP-relatedresources.

In a real situation, we recommend that you continually monitor only yourNCPs and lines. For your multi-drop lines, monitor the PUs continually aswell. When a problem arises, use the NCP Site Monitor List under theOptions pull-down to start monitoring PUs and LUs as needed. Dependingon the NCP collection interval displayed on the NCP Default MonitoringOptions panel, it may take a little time to gather statistics after you startmonitoring.


Case Study 1: LU Reporting Poor Response Time

This scenario illustrates a case in which the user at LU R617A20 reportspoor LU response time.

Step Action Result

1 Select Response Times on themain status panel.

The Average Response Timepanel displays.

2 Use action code A and fill in theAdd Resource panel to startmonitoring response time for LUR617A20.

The Average Response Timepanel shows that networkresponse time for the LU ishigh.

3 Enter action code S next to LUname R617A20.

The Resource Analysis panelshows that the name of theowning line is R617.

4 Return to the Average ResponseTime panel and start monitoringline R617.

Response times are shown as anaverage for all LUs attached tothe line.

5 Enter action code L next to theline to list all the attached LUs.

You notice that all the attachedLUs are experiencing poornetwork response time.

6 Enter action code N (NCPMonitor) next to line R617 to goto the NCP component.

The Line Resource Summarypanel shows that the conditionfor outbound utilization iscritical while the otherconditions are normal.

7 Enter action code A next toUtilization.

The Utilization Analysis panellists two PUs attached to theline. Outbound utilization isnormal for one PU but high forthe other.

8 Enter action code L next to thePU name with high utilization.

The LUs attached to the PU arelisted as in the following figure.



-------------------------------------------------------------17:22:48 11/14/94

KONDN5ðD Utilization Analysis for SDLC Line: R9ðð System: SYSA

More: >


X=Exceptions S=Show details L=List U=Unlist R=Resource analysis T=Trends

++-------------------+--------------------+--------------------+-------+------+

| | Inbound Traffic | Outbound Traffic | Queue | |

| Resource Type | Pct ð.2.4.6.8.M | Pct ð.2.4.6.8.M | Lngth | Cond |

+--------------------+------+-------------+------+-------------+-------+------+

| _ R9ðð SDLC | 5% | > . . . . . | 62% | ======> . . | 5 | Crit |

| _ R9ððA PU | 1% | > . . . . . | 12% | =>. . . . . | 1 | Norm |

| _ R9ððB PU | 4% | > . . . . . | 5ð% | =====>. . . | 4 | Crit |

| _ R9ððBðð LU | 1% | > . . . . . | 2% | > . . . . . | ð | Norm |

| _ R9ððBð1 LU | 1% | > . . . . . | 3% | > . . . . . | 4 | Norm |

| _ R9ððBð2 LU | 2% | > . . . . . | 45% | ====> . . . | 4 | Crit |

+--------------------+------+-------------+------+-------------+-------+------+

Command ===> ___________________________________________________________________



F2ð=Right

á ñ

Figure 44. Case Study 1: Utilization Analysis for Line

Step Action Result

9 Examine the performancestatistics for the LUs.

You notice that one LU has highoutbound traffic.

10 Contact the user of the LU withhigh outbound traffic.

You learn that the LU is a PC inthe process of downloading afile from the host. This iscausing poor response times forthe other LUs attached to theline.

11 Examine tuning parameters andperform tuning or ask the user toperform file transfers outside ofnormal business hours.

The LUs attached to the lineregain reasonable response time.


Case Study 2: Identifying Line Problem Before Users Report

In this scenario, we use the NCP component to identify a problem before it isreported by users.

Step Action Result

1 Select NCP Monitor on the mainstatus panel.

The NCP Status Summary panelshows that the line and PUconditions for an NCP arecritical.

2 Use action code L next to theNCP name in question to list itslines.

You see which line is in criticalcondition.

3 Use action code S next to thename of the critical line to showdetails about the line.

On the Line Resource Summarypanel you see that whileutilization is normal, retransmitsand errors have exceeded theircritical thresholds.

4 Use action code A next to Errors. The Retransmission ErrorAnalysis panel shows the lineand two PUs. One PU has ahigh percentage of errors and isin critical condition, as in thefollowing figure.



-------------------------------------------------------------17:33:59 11/14/94

KONDN51D Retransmission Error Analysis for SDLC Line: R9ðð System: SYSA

More: < >



+-------------------+-----+---------------------+----------------------+------+

| | Err | Retransmitted PIUs | Retransmitted Byte | |

| Resource Type | Pct | Pct ð.2.4.6.8.M | Pct ð.2.4.6.8.M | Cond |

+-------------------+-----+-------+-------------+-------+--------------+------+

| _ R9ðð SDLC | 21% | 21% | ==> . . . . | 17% | =>. . . . . | Crit |

| _ R9ððA123 PU | 1% | 1% | > . . . . . | 2% | > . . . . . | Norm |

| X R9ððB PU | 2ð% | 2ð% | ==> . . . . | 15% | =>. . . . . | Crit |

+-------------------+-----+-------+-------------+-------+--------------+------+

Command ===> ___________________________________________________________________


F1ð=Action Bar F11=Print F12=Cancel F14=Find F15=Status_Display F19=Left

F2ð=Right

á ñ

Figure 45. Case Study 2: Retransmission Error Analysis for Line

Step Action Result

5 Use action code X next to thename of the critical PU todisplay exceptions.

You see that the PU has beenexceeding critical thresholds forerrors and retransmits during thepast hour.

6 Request modem/circuit tests onthe portions of the circuit thatattach to the PU generating thehigh percentage of errors.

You have identified the problemarea and you can begin circuitrepair before users start reportingproblems.


Case Study 3: Is Additional Line Capacity Required?

Your user is planning to double the number of transactions using a particularline. You want to determine whether the line can handle twice its currentvolume or whether additional line capacity is required.

Step Action Result


The NCP Status Summarydisplays the status of all NCPs.

2 Use action code L next to thename of the NCP owning theline in question.

The lines attached to the NCPappear under the NCP on thispanel.

3 Use action code S next to thename of the line in question toshow details.

The Line Resource Summarypanel shows several performancestatistics.

4 Enter action code T next toUtilization.

The Line Utilization trendingpanel displays trends for recentintervals, as shown in thefollowing figure.

à ð____ Goto Options Help

-------------------------------------------------------------11:14:22 11/14/94

KONDNððD Trend: Line Utilization System: SYSA

for SDLC Line: R9ðð More:

Lines 1 to 7 of 7

The maximum line utilization was 9.3%

+-----------------------------------------------------------------------------+

| Date | Time | Percent | ð..1ð..2ð..3ð..4ð..5ð..6ð..7ð..8ð..9ð..1ðð |

]----------+----------+---------+---------------------------------------------]

| 11/14/94 | ð7:ðð:ðð | 2.6% | > . . . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð6:ðð:ðð | 4.3% | =>. . . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð5:ðð:ðð | 5.ð% | =>. . . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð4:ðð:ðð | 9.3% | ===>. . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð3:ðð:ðð | 7.8% | ==> . . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð2:ðð:ðð | 5.6% | =>. . . . . . . . . . . . . . . . . . . . . |

| 11/14/94 | ð1:ðð:ðð | 2.9% | > . . . . . . . . . . . . . . . . . . . . . |

+-----------------------------------------------------------------------------+

Command ===> __________________________________________________________________


F1ð=Action Bar F11=Print F12=Cancel F15=Status_Display

á ñ

Figure 46. Case Study 3: Line Utilization Trending


Step Action Result

5 Review the inbound andoutbound utilization percentagesdisplayed.

You see that utilization isrelatively low and no oneinterval exceeds 10%.

6 Confirm your findings byexamining historical utilizationtrend data for the line.

You validate that utilization isconsistently low over time.

7 You can double the traffic onthis line without having toupgrade.

You have saved your companythe unnecessary cost ofupgrading the line.


Case Study 4: NCP Storage Shortage

An NCP in slowdown is a serious problem: the NCP buffers are full and theNCP can accept new data only when the slowdown condition ends.

Even when NCP storage shortages are not severe enough to cause slowdown,they can still cause performance problems in the network by restrictinglow-priority traffic. These kinds of shortages are not indicated at the VTAMconsole, as a slowdown is.

In this scenario, you have an NCP in which the attached terminals areexperiencing good response time and the traffic is usually steady. However,you receive reports that the attached printers are pausing at a particular timeof the day. The printers are on various lines attached to the NCP.

Step Action Result


The NCP Status Summary panelshows that one of your NCPs isin a warning condition.

2 Enter action code S next to theNCP name to show details.

The NCP Resource Summarypanel shows that bufferutilization is in a warningcondition while the otherperformance statistics are innormal condition. See thefollowing figure.



-------------------------------------------------------------12:12:ðð 11/14/94

KONDNNND Resource Summary for NCP: NCP1ð System: SYSA

More:



+--------------------------+------------------------+-------------------------+

| Name . . . . .: NCP1ð | MAXCOLL . . .: 4ðð | Connect. . . .: XDOMAIN |

| Subarea. . . .: 25 | Lines . . . .: 76 | Total buffers.: 991 |

| Release. . . .: V6.2 | PUs . . . . .: 18 | SLOWDOWN limit: 122 |

| NPALU. . . . .: NPALUð1 | LUs . . . . .: 38 | Cycle speed. .: 64K |

+--------------------------+-----------+------------+-------------------------+

| Generation Date .: 11/ð6/94 11:39:ð7 | Generation Level.: ð5/12/93 23:59:59 |

+----------------+---------+-----------+------------+-------------------------+

| _ CCU Cycles | Normal | Utilization.: 3ð.34% | Cycles used. : 21.25M |

| _ Channel | Normal | HOLDQ length: 1 | INTQ length. : 1 |

| _ Slowdown | Normal | Percent. . .: ð.ðð% | Time (secs). : ð |

| T Buffer Util | Warning | Utilization.: 83.22% | Max free buff: 748 |

+----------------+---------+------------------------+-------------------------+

Command ===> __________________________________________________________________



á ñ

Figure 47. Case Study 4: NCP Resource Summary

Step Action Result

3 Enter action code T next toBuffer Util to show recenttrends.

You see that at the reported timeof day, buffer utilization ishigher than normal (around80%).

4 Consider the followingrecommendations:

Á Examine the use ofparameters such as thefollowing for theirappropriateness:

– VPacing– transmission priority– class of service– buffer size

Á You may need to upgradeyour 37x5 storage to preventshortages that couldeventually lead to NCPslowdown.

The NCP storage shortage isrelieved before a serious networkproblem occurs.


Appendix A. Calculations

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100NCP CCU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 101SDLC Line Statistics Calculations. . . . . . . . . . . . . . . . . . . 102SDLC PU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 104SDLC LU Statistics Calculations. . . . . . . . . . . . . . . . . . . . 106Token-Ring Physical Link Statistics Calculations. . . . . . . . . 107Token-Ring Logical Link Statistics Calculations. . . . . . . . . . 109X.25 MCH Link Statistics Calculations. . . . . . . . . . . . . . . . 111X.25 VC Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 113X.25 LU Statistics Calculations. . . . . . . . . . . . . . . . . . . . . 115

Appendix A. Calculations 99

Introduction

OMEGAMON II uses the calculations in the following tables to generateNCP monitor statistics.


NCP CCU Statistics Calculations

Table 2. NCP CCU Statistics Calculations

CCU Value Formula

CCU

UtilizationPercent

(Sample Interval in tenths of a second - (Free Cycles / Speed)) x 100

-------------------------------------------------------Sample Interval in tenths of a second

OR

(Used Cycle / Speed) x 100-----------------------------------

Sample Interval in tenths of a second

Buffer

UtilizationPercent

(Maximum Buffers − Free Buffers Low-Water-Mark) x 100

-------------------------------------------------------------------Maximum Buffers

Time in

SlowdownPercent

(Time in Slowdown in tenths of a second) x 100

------------------------------------Sample Interval in tenths of a second

Free BufferUtilization

Percent

(Max Available Buffers − Free Buffers Low-Water-Mark) x 100

-------------------------------------------------------------------Max Available Buffers

Seconds inSlowdown

Time in Slowdown------------------------

10

Idle

Detection

If (Bytes Received + Bytes Sent) = 0


SDLC Line Statistics Calculations

Table 3 (Page 1 of 2). SDLC Line Statistics Calculations

Line Value Formula

Inbound

UtilizationPercent

(Bytes Received) x 100

------------------------------------------------(Sample Interval in seconds) x (Line Speed / 8)

OutboundUtilization

Percent

(Bytes Sent) x 100


Half-Duplex

LineUtilization

Percent

(Bytes Sent + Bytes Received) x 100

-----------------------------------------------=(Sample Interval in seconds) x (Line Speed / 8)

Full-Duplex

LineUtilization

Percent

The largest of {Bytes Sent or Bytes Received} x 100----------------------------------------------------------------

(Sample Interval in seconds) x (Line Speed / 8)

Retransmit

BytesPercent

(Bytes Retransmitted) x 100

-----------------------------------------Bytes Transmitted

Retransmit

PIUsPercent

(PIUs Retransmitted) x 100

-----------------------------------------PIUs Transmitted

Temporary

ErrorRate

Error Count

---------------------------------------Total Bytes Sent / 1024


Table 3 (Page 2 of 2). SDLC Line Statistics Calculations

Line Value Formula

Negative

PollsPercent

(Total − Positive) x 100------------------------------

Total Polls

High-

PriorityIFramesPercent

(High-Priority IFrames) x 100

-----------------------------------------Total IFrames

Medium-PriorityIFramesPercent

(Medium-Priority IFrames) x 100

-------------------------------------------Total IFrames

Low-


(Low-Priority IFrames) x 100

----------------------------------------Total IFrames

Negative

Polls

Total Polls − Positive Polls

Idle

Detection



SDLC PU Statistics Calculations

Table 4 (Page 1 of 2). SDLC PU Statistics Calculations

PU Value Formula

Inbound

UtilizationPercent


-------------------------------------------------(Sample Interval in seconds) x (Line Speed / 8)

OutboundUtilization

Percent

(Bytes Sent) x 100


Half-Duplex

LineUtilization

Percent



Full-Duplex

LineUtilization

Percent

The largest of {Bytes Sent or Bytes Received} x 100------------------------------------------------------------------


Retransmit

BytesPercent


---------------------------------------Bytes Transmitted

Retransmit

PIUsPercent

(PIUs Retransmitted) x 100

---------------------------------------PIUs Transmitted

Temporary

ErrorRate

Error Count

-----------------------------------Total Bytes Sent / 1024


Table 4 (Page 2 of 2). SDLC PU Statistics Calculations

PU Value Formula

Negative

PollsPercent

(Total − Positive) x 100

--------------------------------------Total Polls

High-


(High-Priority IFrames) x 100

-----------------------------------------Total IFrames

Medium-PriorityIFramesPercent

(Medium-Priority IFrames) x 100

-------------------------------------------Total IFrames

Low-


(Low-Priority IFrames) x 100

-----------------------------------------Total IFrames

Negative

Polls

Total Polls − Positive Polls

Idle

Detection



SDLC LU Statistics Calculations

Table 5. SDLC LU Statistics Calculations

LU Value Formula

Inbound

UtilizationPercent



OutboundUtilization

Percent

(Bytes Sent) x 100


Half-Duplex

LineUtilization

Percent



Full-Duplex

LineUtilization

Percent



Bytes perMinute

(Bytes Received + Bytes Sent) x 60---------------------------------------------

Sample Interval in seconds

PIUs perMinute

(PIUs Received + PIUs Sent) x 60-------------------------------------------


Idle

Detection



Token-Ring Physical Link Statistics Calculations

Table 6 (Page 1 of 2). Token-Ring Physical Link Statistics Calculations

TRPL Value Formula

Inbound

UtilizationPercent

(Bytes Received x Nanoseconds per Byte)

-------------------------------------------------------------------Sample Interval in tenths of a second x 1,000,000

PLUS

(Frames Received x Milliseconds per Frame)

-------------------------------------------------------------------Sample Interval in tenths of a second x 1,000

OutboundUtilization

Percent

(Bytes Sent x Nanoseconds per Byte)

-------------------------------------------------------------------Sample Interval in tenths of a second x 1,000,000

PLUS

(Frames Sent x Milliseconds per Frame)

-------------------------------------------------------------------Sample Interval in tenths of a second x 1,000

TIC

UtilizationPercent

(Bytes Received x Nanosecs per Byte) + (Bytes Sent x Nanosecs per Byte)

------------------------------------------------------------------------Sample Interval in tenths of a second x 1,000,000

PLUS

(Frames Received x Msecs per Frame) + (Frames Sent x Msecs per Frame)

------------------------------------------------------------------------Sample Interval in tenths of a second x 1,000

TIC

CongestionPercent

(Congestion Count) x 100

----------------------------------Frames Received


Table 6 (Page 2 of 2). Token-Ring Physical Link Statistics Calculations

TRPL Value Formula

Retransmit

BytesPercent


----------------------------------------Bytes Transmitted

Retransmit

IFramesPercent

(IFrames Retransmitted) x 100

-------------------------------------------IFrames Transmitted

Bytes perMinute

(Bytes Received + Bytes Sent) x 60-------------------------------------------


Frames per

Minute

(Frames Received + Frames Sent) x 60------------------------------------------------


IFrames per

Minute

(IFrames Received + IFrames Sent) x 60-------------------------------------------------


Idle

Detection



Token-Ring Logical Link Statistics Calculations

Table 7 (Page 1 of 2). Token-Ring Logical Link Statistics Calculations

TRLL Value Formula

Inbound

UtilizationPercent



OutboundUtilization

Percent

(Bytes Sent) x 100


Retransmit

BytesPercent


----------------------------------------Bytes Transmitted

Retransmit

IFramesPercent


--------------------------------------------IFrames Transmitted

Reply

TimeoutsPercent

(Reply Timeouts) x 100

---------------------------------------------IFrames Received + Reply Timeouts

Bytes perMinute



Frames per

Minute

(Frames Received + Frames Sent) x 60-----------------------------------------------



Table 7 (Page 2 of 2). Token-Ring Logical Link Statistics Calculations

TRLL Value Formula

IFrames per

Minute

(IFrames Received + IFrames Sent) x 60------------------------------------------------


Idle

Detection

If Bytes Received + Bytes Sent = 0


X.25 MCH Link Statistics Calculations

Table 8 (Page 1 of 2). X.25 MCH Link Statistics Calculations

Link Value Formula

Inbound

UtilizationPercent


------------------------------------------(Sample Interval in seconds) x (Line Speed / 8)

OutboundUtilization

Percent

(Bytes Sent) x 100


Full-Duplex

LineUtilization

Percent



Retransmit

BytesPercent

(Bytes Retransmitted) x 100-----------------------------------

Bytes Transmitted

Retransmit

IFramesPercent

(IFrames Retransmitted) x 100-------------------------------------

IFrames Transmitted

ErrorRate

Error Count

---------------------------------------(Total Bytes Sent) / 1024

VC

UtilizationPercent

(VCs in Use) x 100

--------------------------------------Maximum PVCs + SVCs


Table 8 (Page 2 of 2). X.25 MCH Link Statistics Calculations

Link Value Formula

RNR

FramesSent

Percent

(RNR Frames Sent) x 100

-------------------------------------IFrames Received

RNR

FramesReceivedPercent

(RNR Frames Received) x 100---------------------------------------

IFrames Sent

Inbound

ConnectionsPercent

(Inbound Connections) x 100

----------------------------------------------------------Inbound Connections + Outbound Connections

Outbound

ConnectionPercent

(Outbound Connections) x 100

----------------------------------------------------------Inbound Connections + Outbound Connections

Idle

Detection



X.25 VC Statistics Calculations

Table 9 (Page 1 of 2). X.25 VC Statistics Calculations

VC Value Formula

Inbound

UtilizationPercent



OutboundUtilization

Percent

(Bytes Sent) x 100


Full-Duplex

LineUtilization

Percent

The largest of {Bytes Sent or Bytes Received} x 100------------------------------------------------------------------


Retransmit

BytesPercent


---------------------------------------Bytes Transmitted

Retransmit

IFramesPercent


-------------------------------------------IFrames Transmitted

ErrorRate

Error Count

-----------------------------------(Total Bytes Sent) / 1024

Data Packets

Receivedwith D-Bit

Percent

(Data Packets Received with D-Bit) x 100

--------------------------------------------------------Total Data Packets Received


Table 9 (Page 2 of 2). X.25 VC Statistics Calculations

VC Value Formula

Data Packets

Sentwith D-BIt

Percent

(Data Packets Sent with D-Bit) x 100

---------------------------------------------------Total Data Packets Sent

Packets

with D-BitPercent

(D-Bit Packets Sent + D-Bit Packets Received) x 100

------------------------------------------------------------------------Data Packets Sent + Data Packets Received

Packets

with M-BitPercent

(M-Bit Packets Sent + M-Bit Packets Received) x 100-------------------------------------------------------------------

Data Packets Sent + Data Packets Received

Idle

Detection



X.25 LU Statistics Calculations

Table 10. X.25 LU Statistics Calculations

LU Value Formula

Inbound

UtilizationPercent



OutboundUtilization

Percent

(Bytes Sent) x 100


Full-Duplex

LineUtilization

Percent



Bytes perMinute



PIUs perMinute

(PIUs Received + PIUs Sent) x 60-------------------------------------------


Idle

Detection




Appendix B.NCP Monitor Navigation from Status Lights

The following chart illustrates navigating through the NCP monitorcomponent when you start from the NCP Status Lights Summary panel.

Appendix B. NCP Monitor Navigation from Status Lights 117

Navigation from Status Lights

NCP ┌──KONDNNND──┐ ┌──KONDN7ðD──┐┌─────┐ │ NCP │ S │ NCP │

┌───5│ 1 ├───5│ Resource ├─────5│ Utilization││ └─────┘ │ Summary │ │ Detail ││ & └────────────┘ └────────────┘

│ │ N │ ┌──┴──┐

│ │ RTA │ ┌──KONDN59D──┐ & F19│ └─────┘ S │ TRPL │ ││ ┌──5│ Utilization│ │

│TRPL ┌──KONDNNVD──┐ │ │ Detail │ ││ ┌─────┐ │ TRPL │ │ └────────────┘ │├───5│ 2 ├───5│ Resource ├──┤ ││ └─────┘ │ Summary │ │ ┌──KONDN6ðD──┐ ││ └────────────┘ │ S │ TRPL │ │

│ └──5│ Error │ │ │ │ Detail │ │ │ └────────────┘ 6F2ð │ ┌──KONDNCMD──┐ │

│ NCP │ │ S ┌──KONDN57D──┐ & F19 │ TNSTATs │ │ ┌──5│ TRLL │ │ │ │ │ │ │ Traffic │ │ └────────────┘ │TRLL ┌──KONDNNRD──┐ │ │ Detail │ │

& │ ┌─────┐ │ TRLL │ │ └────────────┘ ││ ├───5│ 3 ├───5│ Resource ├──┤ ││ F22 │ └─────┘ │ Summary │ │ ┌──KONDN58D──┐ │

│ │ └────────────┘ │ │ TRLL │ ││ │ │ S │ Error │ │

6 │ └──5│ Detail │ │ ┌────────┐ ┌──KONDNNMD──┐ │ └────────────┘ 6F2ð │ Main │ │ NCP │ │ │ Status ├───5│ Status ├─────┤│ │ │ Lights │ │ ┌──KONDN5ðD──┐ ┌──KONDN53D──┐ & F19 └────────┘ └────────────┘ │ A │ Line │ S │ Line │ │

& │ ┌─────┐ ┌──5│ Utilization├──┬──5│ Utilization│ ││ F4 │ │ RTA │ │ │ Analysis │ │ │ Detail │ ││ │ └──┬──┘ │ S └────────────┘ │ └────────────┘ │

│ │ │ N ├───────────────────┘ │ │ │SDLC 6 ┌──KONDNNLD──┐ │ ┌──KONDN51D──┐ ┌──KONDN54D──┐ │

6 │ ┌─────┐ │ SDLC/BSC │ │ A │ Retransmit │ S │ Error │ 6 F2ð┌──KONDNNAD──┐ ├───5│ 4 ├───5│ Resource ├──┼──5│ Error ├──┬──5│ Detail ││ NCP │ │ └─────┘ │ Summary │ │ │ Analysis │ │ │ │ & F19│ Statistics │ │ └────────────┘ │ S └────────────┘ │ └────────────┘ │

│ Summary │ │ ├───────────────────┘ │ └──────┬─────┘ │ │ ┌──KONDN52D──┐ ┌──KONDN55D──┐ │

│ │ │ A │ Polling │ S │ Polling │ │ │ │ ├──5│ Analysis ├──┬──5│ Detail │ │ 6 │ │ │ │ │ │ │ │

See │ │ S └────────────┘ │ └────────────┘ 6 F2ð Next │ └───────────────────┘ Page │ │

│ ┌──KONDN5ðD──┐ ┌──KONDN53D──┐ & F19│ A │ PU │ S │ PU │ ││ ┌─────┐ ┌──5│ Utilization├──┬──5│ Utilization│ ││ │ RTA │ │ │ Analysis │ │ │ Detail │ ││ └─────┘ │ S └────────────┘ │ └────────────┘ │

│ │ N ├───────────────────┘ │ │PU 6 ┌──KONDNNSD───┐ │ ┌──KONDN51D──┐ ┌──KONDN54D──┐ │

│ ┌─────┐ │ PU │ │ A │ Retransmit │ S │ Error │ 6 F2ð├──5│ 5 ├───5│ Resource ├──┼──5│ Error ├──┬──5│ Detail ││ └─────┘ │ Summary │ │ │ Analysis │ │ │ │ & F19│ └─────────────┘ │ S └────────────┘ │ └────────────┘ │

│ ├───────────────────┘ │ │ │ ┌──KONDN52D──┐ ┌──KONDN55D──┐ │

│ │ A │ Polling │ S │ Polling │ │ │ ├──5│ Analysis ├──┬──5│ Detail │ │ │ │ │ │ │ │ │ │

│ ┌─────┐ │ S └────────────┘ │ └────────────┘ 6 F2ð│ │ RTA │ └───────────────────┘

│ └─────┘ │ │ N

│LU 6 ┌──KONDNNUD──┐ ┌──KONDN56D──┐ ┌──KONDARAD──┐│ ┌─────┐ │ LU │ S │ LU │ Goto │ Resource │

Note: └───5│ 6 ├───5│ Resource ├─────5│ Utilization├─────5│ Analysis │ └─────┘ │ Summary │ │ Detail │ │ │ Exceptions and Trends └──────┬─────┘ └────────────┘ └────────────┘ are available on all │ & Goto NCP statistics panels. └───────────────────────────────────────┘


Appendix C.NCP Monitor Navigation from Statistics Summary

The following chart illustrates navigating through the NCP monitorcomponent when you start from the NCP Statistics Summary panel.

Appendix C. NCP Monitor Navigation from Statistics Summary 119

Navigation from Statistics Summary

┌─────┐S ┌───────────────────────────────────────────5│ 1 ├──5Previous

│ └─────┘ Page NCP │ │ ┌──KONDN2GD──┐ ─────┐

│ │ Traffic │ & F2ð ││ ┌─┴KONDNNYD──┐ │ │ │

│ │ Errors ├─┘ │ │ S ┌─────┐│ ┌─┴KONDNNWD──┐ │ │ ├────────5│ 2 ├──5Previous

│ │ List ├─┘ │ │ └─────┘ Page K ├─────5│ of │ 6 F19 │ │ │ TRPLs ├──────────────┘ TRPLs │ └────────────┘

│ & F21 │ │ │ │ ┌──KONDNNTD──┐ ─────┐

│ │ │ Traffic │ & F2ð ││ 6 F22 ┌─┴KONDN2FD──┐ │ │ │

│ │ Errors ├─┘ │ │ S ┌─────┐ ┌──KONDNCMD──┐ │ ┌─┴KONDN1UD──┐ │ │ ├────────5│ 3 ├──5Previous │ NCP │ K │ │ List ├─┘ │ │ └─────┘ Page │ TNSTATs │ ├─────5│ of │ 6 F19 │ │ │ TRLLs │ │ TRLLs ├──────────────┘ └────────────┘ │ └────────────┘

& │ & F21 │ F22 │ │ │ │ │ ┌──KONDN2BD──┐ ─────┐

│ │ │ │ Lo─Priority│ & F2ð │6 │ │ ┌─┴KONDN2AD──┐ │ │ │

┌──KONDNNAD──┐ │ │ │ Med.─Pri. ├─┘ │ │ │ NCP │ │ │ ┌─┴KONDN1ZD──┐ │ │ ││ Statistics ├──────────────────────┤ │ │ Hi─Priority├─┘ │ │ S ┌─────┐

│ Summary │ │ │ ┌─┴KONDN2HD──┐ │ │ ├──5│ 4 ├──5Previous └────────────┘ │ │ │ Traffic ├─┘ │ │ └─────┘ Page

& │ 6 F22 ┌─┴KONDNNOD──┐ │ │ │ L │ │ │ Errors ├─┘ │ ├───────────────────┐ │ F4 │ ┌─┴KONDNNKD──┐ │ │ │ P │ │ K │ │ List ├─┘ 6 F19 ├──────┐ │ │ ├─────5│ of ├────────────────────┘ │ │ 6 SDLCs │ │ SDLCs │ │ │ ┌──KONDNNMD──┐ │ └────────────┘ │ │ │ NCP │ │ │ │ │ Status │ │ ┌──────────────────────────────────────────┘ │ │ Lights │ │ │ ┌──KONDN2ED──┐ ─────┐ │└──────┬─────┘ │ │ │ Lo─Priority│ & F2ð │ │

│ │ │ ┌─┴KONDN2DD──┐ │ │ │ │ │ │ │ │ Med─Pri. ├─┘ │ │ │ 6 │ │ ┌─┴KONDN2CD──┐ │ │ │ │

See │ │ │ Hi─Priority├─┘ │ │ S ┌─────┐ │Previous │ │ ┌─┴KONDN2ID──┐ │ │ ├──5│ 5 ├──5Prev. │Page │ │ │ Traffic ├─┘ │ │ └─────┘ Page │

│ │ ┌─┴KONDNNJD──┐ │ │ │ │ │ │ │ Errors ├─┘ │ │ L │

│ │ ┌─┴KONDNNHD──┐ │ │ ├──────┐ │P │ 6 │ List ├─┘ 6 F19 │ │ │

├─────5│ of ├────────────────────┘ │ │ PUs │ │ PUs │ │ │ │ └────────────┘ │ │ │ ┌──────────────────────────────────────────┴────────────┘ │ │

│ │ ─────┐ S ┌─────┐ Previous│ │ ┌──KONDN2JD──┐ & F2ð │──5│ 6 ├─5Page

│ │ │ Traffic │ │ │ └─────┘ R ┌──KONDARAD──┐│ │ ┌─┴KONDNNQD──┐ │ │ ├─────────────────5│ Resource │

L │ 6 │ List ├─┘ │ │ E ┌─────┐ │ Analysis │└─────5│ of │ 6 F19 ├──5│ RTA │ │ │

LUs │ LUs ├─────────┘ └─────┘ └────────────┘ └────────────┘


Appendix D.Candle Customer Support

Introduction

Candle Corporation offers a comprehensive maintenance and support plan toensure you realize the greatest value possible from your Candle softwareinvestments. We have more than 200 technicians worldwide, committed toproviding you with prompt resolutions to your support requests.

Customer Support hours of operation are from 5:30 A.M. to 5:00 P.M.,Pacific Time. In the event of an after-hours or weekend emergency, Candle'scomputerized call management system ensures that a technician will returnyour call within one hour. For customers located outside of North America,after-hours and weekend support is provided by Candle Customer Supportlocations in the United States.

Electronic Support

Candle provides information and support services using

Á Candle's home page at www.candle.com. You can use the Candle Website to

– open problem records– access maintenance information– order products or maintenance– access IBM compatibility information– download fix packs for distributed products– read news and alerts– scan a list of scheduled Candle education classes

Á Candle Electronic Customer Support (CECS), an electronic customersupport facility. You can access this facility through the IBM GlobalNetwork. You can use CECS to

– open problem records– search our database for solutions to known problems– look for answers to commonly asked questions– read news and alerts– scan a list of scheduled Candle education classes

Both CECS and the Candle Web site are available 24 hours a day, 7 days perweek.

Appendix D. Candle Customer Support 121

Telephone Support

Our support network consists of product specialists who work with you tosolve your problem.

Candle uses an online problem management system to log and track allsupport requests. Your request is immediately routed to the appropriatetechnical resource.

When you call to report a problem, please have the following information:

Á your Candle personal ID (PID) number

Á the release level of the Candle product

Á the release level of IBM or other vendor software

Á identifying information and dates of recently applied maintenance to yourCandle product or IBM product

Á a detailed description of the problem (including the error message) andthe events preceding the problem

Á a description of any unusual events that occurred before the problem


Customer Support Phone Numbers

Telephone Fax

North America (800) 328-1811

(310) 535-3636 (310) 727-4204

Europe

Belgium/Luxembourg +32 (0) 3 270 95 60 +32 (0) 3 270 95 41

France +33 (0) 1 53 61 60 60 +33 (0) 1 53 61 06 16

Germany/Switzerland/Austria +49 (0) 89 54 554 333 +49 (0) 89 54 554 170

Italy - Freephone 800 80992

Netherlands +31 (0) 30 600 35 50 +31 (0) 30 600 35 10

Scandinavia +46 (0)8 444 5940 +46 (0)8 623 1855

U.K. +44 (0)161 437 5224 +44 (0)161 437 5225

(Southern Europe, Middle East and South Africa Agents call U.K.)

Asia Pacific - English Hub +61 2 9954 1818

Australia +61 2 8912 9898

Hong Kong 800 908 457

India +61 2 8912 9898

Indonesia 0018 03061 2061

Malaysia 1800 803 459

New Zealand 0800 449 596

Philippines 1800 1612 0096

Singapore 800 616 2075

Thailand 0018 00612 1045

Asia-Pacific - Japanese Hub +81 3 5562 6992 +81 3 5562 6995

Asia Pacific - Korean Hub +82 2 552 8744 +82 2 552 8746

Asia Pacific - Mandarin Hub +88 62 2739 3223 +88 62 2378 5993

Asia Pacific e-mail address: [email protected]

When your local support office is unavailable, you can contact Candle'sNorth America support center. If USADirect service is available in yourcountry, use the 800 telephone number. If USADirect service is notavailable, ask your international operator for assistance in calling Candle'slocal (310) number.

Appendix D. Candle Customer Support 123

Incident Documentation

You may be asked to send incident documentation to the Candle CustomerSupport Center. On the outside of all packages you send, please write theincident number given to you by the Customer Support representative.

Send tapes containing the incident information to the following address,unless directed otherwise by your Customer Support representative:

Candle Customer SupportCandle Support Center, Incident number2ð1 North Douglas StreetEl Segundo, CA 9ð245

Send all other relevant documentation, such as diskettes or paperdocumentation, to the address provided by your Customer Supportrepresentative.

Ensuring Your Satisfaction with Customer Support

Candle Customer Support is committed to achieving high customersatisfaction ratings in all areas. These include

Á connecting you to a support representative promptlyÁ providing you with the appropriate fixesÁ answering support questionsÁ filling your shipping ordersÁ supplying documentation

If you have a concern that has not been resolved to your satisfaction, you canopen a complaint ticket. All tickets are logged and tracked to ensureresponsiveness and closure. Using the ticket information, a manager willcontact you promptly to resolve your problem.


Index

A

activation, LU 59administrator functions

monitoring options 88NCP performance 87

Adobe portable document format 10audiences 22autostart, NCP 69

B

binary synchronous communicationSee BSC line

BSC line 37See also SDLC linedefault options 70status panel 37

buffers 32, 33bytes, token-ring logical link 44

C

calculations 99–115Candle Electronic Customer Support

(CECS) 121case studies

line capacity 95line problem 93LU reporting poor response time 91NCP storage shortage 97

CCU 17buffers 32, 33utilization 32, 33

changing options, NCPspecific resource 82subordinate resources 82

channelqueues 32utilization 33

channel adapter lines 37cluster controller

See PUcollection interval, NCP 69collector 20conditions, connected NCP resources 30configuration data

NCP 33SDLC line 39VTAM 33

connects, token-ring physical link 41conventions, documentation 11copying options, NCP 83critical thresholds, performance objectives 65current settings, NCP 81customer support 121

D

data sources 20default options

LUs 71NCPs 69overriding, NCP 81PUs 71SDLC/BSC lines 70token-ring logical links 72token-ring physical links 72

definition, NCP 17deleting NCPs, Site Monitor List 86determining settings, NCP 88documentation conventions 11documentation set 13dynamic configuration 21, 77

E

electronic customer support 121errors

PU 50token-ring logical link 46

examplesSee case studies

Index 125

exceptions 26monitoring options 64

exception/trend recording, NCP 69

F

framesPU 50SDLC line 37token-ring logical link 44token-ring physical link 43

function keys 24NCP options 75

H

hierarchy of NCP resources 67

I

IFrames, token-ring physical link 43introduction 15–26

K

KONRRT dataset 20KONSRC dataset 20

L

line 35–48See also SDLC lineLU utilization 56multi-drop 90panels 36PU utilization 50resources supported 24selection 36

line-type default, NCP 69link

See token-ringLU 55–61

default options 71line utilization 56panels 56queue length 60

LU (continued)rates 56, 60resource analysis 56, 59resource summary 60response time toggle 56response time, case study 91status panel 56utilization 60VTAM configuration data 60

M

main status light 28monitor/collect option, NCP 69monitoring options 63–88

administrator authority 64menu 66NCP performance 67–88restrictions 64

monitoring scope, recommended 90multi-drop lines 90

N

navigation 24navigation charts 118, 120NCP

autostart 69changing options

specific resource 82subordinate resources 82

collection interval 69collector 77copying options 83default options 69

See also default optionsdynamic configuration 77function keys, options 75hierarchy of resources 67line-type default 69monitor/collect 69monitoring options 67–88product administrator functions 87resetting options 84resource types 78sampling interval 69settings determination 88Site Monitor List 76

deleting NCPs 86listing/unlisting resources 78


NCP (continued)Site Monitor List(continued)

sorting/filtering 80start level 69start monitoring 84start options 69stop monitoring 86viewing current settings 81

NCP-level resources 27–33NDF source library 20Network Control Program

See NCPnon-productive polls

PU 50SDLC line 37

NPALU 20, 77

O

overriding default NCP options 81

P

pacing, LU 59physical unit

See PUportable document format, Adobe 10positive polling, SDLC line 37problems detected 23product administrator functions, NCP 87PU 49–53

default options 71performance statistics 50resource summary 51status panel 50VTAM configuration data 51

Q

queue lengthLU 60token-ring logical link 44, 46token-ring physical link 41

R

ratesLU 56, 60token-ring logical link 46token-ring physical link 41

recommended monitoring scope 90resetting options, NCP 84resource analysis, LU 56, 59

activation 59pacing 59sessions 59state 59

Resource Resolution TableSee RRT

resource summaryLU 60NCP 33PU 51SDLC line 39token-ring logical link 46token-ring physical link 43

resources, NCPhierarchy 67monitored 19types 78

response time, LU 56retransmissions, token-ring logical link 45, 46RRT 20, 77

S

sample interval, TIC3 40samples

See case studiesscenarios 89–98

See also case studiesscope, recommended monitoring 90SDLC line

additional line capacity, case study 95default options 70identifying line problem, case study 93performance statistics 37resource summary 39status panel 37VTAM configuration data 39

selecting line type 36session, LU 59

Index 127

settingglobal defaults 64thresholds 64

settings determination, NCP 88shortage, storage 97Site Monitor List, NCP 76

deleting NCPs 86listing/unlisting resources 78sorting/filtering 80

slowdown 32, 33start

level 69NCP monitoring 84options 69

statisticscalculations 99–115PU performance 50SDLC line performance 37summary 32token-ring logical link performance 44, 45,

46token-ring physical link performance 41, 43

status lightdetermination 65main 23NCP resources 30

status panelLU 56PU 50SDLC/BSC line 37token-ring logical link 44token-ring physical link 41

stop monitoring 86stoppingstorage 97subordinate resources, changing options 82symbols, use of 12synchronous data link control

See SDLC line

T

telephone support 122terminal

See LUthresholds, NCP performance 67–88TIC 19

token-ring physical link 41utilization 41

TIC3 sample interval 40timeouts, token-ring logical link 46toggles 24token-ring

logical linkdefault options 72performance statistics 44, 45, 46resource summary 46status panel 44VTAM configuration data 46

physical linkdefault options 72performance statistics 41, 43resource summary 43status panel 41VTAM configuration data 43

Token-Ring Interface CouplerSee TIC

topology table 21, 77traffic

inbound, token-ring physical link 43outbound, token-ring physical link 43PU 50SDLC line 37token-ring logical link 45

trends 25TRLL

Seetoken-ring logical linkTRPL

Seetoken-ring physical link

U

utilizationLU 56, 60PU 50SDLC line 37, 39token-ring logical link 46token-ring physical link 43

V

varying views 25viewing current settings, NCP 81VTAM configuration data

LU 60NCP 33PU 51SDLC line 39


VTAM configuration data(continued)token-ring logical link 46token-ring physical link 43

W

warning thresholds, performance objectives 65

Index 129

Documents

NCP Monitoring Guide - IBMpublib.boulder.ibm.com/tividd/td/ITOMEGAIIfVTAM/GC32-9288-00/en_US/...Appendix C. NCP Monitor Navigation from Statistics Summary 119 ... 4 OMEGAMON II for