cna administration guide - jim...

CNA Administration Guide Release 2.2

i

Table Of Contents

CNA Administration Guide 1

Legal Notices 1

Notice 1 Disclaimer 1 Warranty 1 License 2 Copyright 3 Security and virus disclaimer 3 Trademarks 4

Telecommunications Security 5

Preventing Toll Fraud 5 Avaya Fraud Intervention 5 How to Get Help 5 Providing Telecommunications Security 5 Responsibility for Your Company’s Telecommunications Security 6

Document Copies 7

Converged Network Analyzer Overview 8

What Is the Converged Network Analyzer? 8 How Does CNA Work? 10 CNA Fault Tolerance 11 CNA System Summary 12

Intended Audience (Full Access) 13

Quick Start Guide 14

Table Of Contents

ii

Installing Chatterboxes 16

Installing a Chatterbox Using Dynamic (DHCP) Addressing 16 Installing a Chatterbox Using Fixed IP Addressing 16 Generating a Configuration File using the CNA Client 17 Troubleshooting 18

Running CNA Client (First Time Procedures) 19

First Time Procedures 20

CNA User Interface (Full Access) 22

Administering Users 36

Assigning User Login IDs, Passwords and User Privileges 36

Administering Chatterboxes 39

Edit > Add a Chatterbox 40 Edit > Remove a Chatterbox (View List) 41 Chatterbox Status 42 Edit > Change Security Keys 42 Performance Tuning 42 File > Upgrade Software 43 Resetting a Chatterbox to Factory Default Settings 46 File > Static Configuration 47 Determining Chatterbox IP Address 47 Moving a Hive 48

Registering Endpoints 49

Chatterbox Test Plugs 49 Secure Gateway Test Plugs 50

Configuring the Zone Hierarchy 51

Zone Management Functions 52 Assigning Endpoints 54

Table Of Contents

iii

Test Setup 55

Parameters Common Among All Tests 57 RTP Parameters 59 Traceroute Parameters 60 Ping Parameters 61 TCP Connect Parameters 62

Alarm Setup 63

Alarm Templates 65 Alarm State 66 Managing Alarm Templates 67 Assigning Links and Zones to an Alarm Template 69 Alarm Destination Settings 71 Template Tests 74 Other Test Parameters 75 Stale Data (Link or Cell Down) Alarms 75 Finding the Alarm Template for a Link or Zone 76 Troubleshooting Alarms 79

Using the End-to-End Matrix 80

Moving Through the Zone Hierarchy 81 Viewing Cell Data (Tests Tab, Interactive Data Display) 82

Using the Link Topology Map (Full Access) 84

Symbols and Labels 86 Assigning Node Names 87 Assigning Endpoint Names 88 Links 89 Button Bar Controls 90 Saving the Link Topology Map 91 Viewing Link Data (Alarms Tab) 91 Viewing Link Data (Tests Tab, Interactive Data Display) 92

Merging and Unmerging Nodes 94

Table Of Contents

iv

Manual Paths 95

CSV Format for Manual Paths 95

Interpreting Test Results (Interactive Data Display) 96

Alarms: Control and Tolerance Views 99 Minimum, Median and Maximum Views 101 Stale Data 103 Flash Link/Cell Button 104 Mouse Actions 104 Interacting With the Data Display 105 Zooming In on Data 106

Other Administrative Tasks 108

File > Load (system) 108 File > Load (local) 108 File > Save (system) 108 File > Save (local) 108 File > Find a Node 109 Edit > Change Password 109 View > [label options] 110 View > Color Legend 110 View > Flash Tests 110 Alarms > Heartbeat Strikes 111 Alarms >Chart Strikes 111 Refreshing Data 111 Help 112 Enable and Disable Alarms 112

Index 113

1

CNA Administration Guide

Legal Notices

Copyright © 2004, Avaya, Inc. All rights reserved.

This document contains information related to the Avaya Converged Network Analyzer (as defined below) and Documentation (“Product”). “Documentation” means this document and Avaya’s information manuals in printed or electronic form containing operating instructions and performance specifications that Avaya or its suppliers generally make available to users of its products, and which Avaya delivers to End User with the Products. “End User” means any customer of Avaya or its authorized resellers, or any end user of the Product. See the Software and Documentation DVD/CD inserts for additional legal and licensing information.

Notice

Changes and corrections to the information in this document may be incorporated in future releases.

Disclaimer

Avaya, its affiliates or subsidiaries (“Avaya”) are not responsible for any modifications, additions or deletions to the original published version of the Documentation unless such modifications, additions or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants, directors, officers, and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to the Documentation to the extent made by the End User.

Warranty

Avaya provides a limited warranty on the Product. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support.


2

License

USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT: [http://www.avaya.com/support] (“GENERAL LICENSE TERMS”). DO NOT USE THE PRODUCT IF YOU DO NOT WISH TO BE BOUND BY THE GENERAL LICENSE TERMS. IN ADDITION TO THE GENERAL LICENSE TERMS, THE FOLLOWING LICENSE TERMS AND RESTRICTIONS WILL APPLY TO THE PRODUCT.

Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. “Designated Processor” means a single stand-alone computing device. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users. “Software” means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. “Hardware” means the standard hardware products, originally sold by Avaya and ultimately utilized by End User.

Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.

Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.


3

Named User License (NU). Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. “Named User,” means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya’s sole discretion, a “Named User” may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product.

Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End user may install and use the Software in accordance with the terms and conditions of the “shrinkwrap” or “clickwrap” license accompanying the Software (“Shrinkwrap License”). The text of the Shrinkwrap License will be available from Avaya upon End User’s request (see “Copyright” below for more information).

Copyright

Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Certain Software programs or portions thereof included in the Product may contain software distributed under third party agreements (“Third Party Components”), which may contain terms that expand or limit rights to use certain portions of the Product (“Third Party Terms”). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya’s web site at [http://www.avaya.com/support].

The disclaimers of warranties and limitations of liability set forth in the Third Party Terms do not affect any express warranty or limitation of liability that may be provided to you by Avaya pursuant to the license terms covering the Product contained in a separate written agreement between you and Avaya. To the extent there is a conflict between the General License Terms or your customer sales agreement and any Third Party Terms, the Third Party Terms shall prevail solely for such Third Party Components.

Security and virus disclaimer

End User's decision to acquire products from third parties is End User's sole responsibility, even if Avaya helps End User identify, evaluate or select them. Avaya is not responsible for, and will not be liable for, the quality or performance of such third party products or their suppliers.


4

ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO END USER’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Avaya does not warrant that this Product is immune from or will prevent unauthorized use of telecommunication services or facilities accessed through or connected to it. Avaya is not responsible for any damages or charges that result from either unauthorized uses or from incorrect installations of the security patches that are made available from time to time. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to [email protected].

Trademarks

All trademarks identified by ® and TM are registered trademarks or trademarks of Avaya Inc. All other trademarks are the property of their respective owners.

©2004 Avaya Inc. All rights reserved. Last modified 28 November, 2004


5

Telecommunications Security

Preventing Toll Fraud

“Toll fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need technical assistance or support, in the United States and Canada, call the Technical Service Center's Toll Fraud Intervention Hotline at 1-800-643-2353.

How to Get Help

For additional support telephone numbers, go to the Avaya support Web site: http://www.avaya.com/support. If you are:

Within the United States, click the Escalation Management link. Then click the appropriate link for the type of support you need.

Outside the United States, click the Escalation Management link. Then click the International Services link that includes telephone numbers for the international Centers of Excellence.

Providing Telecommunications Security

Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of) your company's telecommunications equipment by some party.

Your company's “telecommunications equipment” includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, “networked equipment”).

An “outside party” is anyone who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf. Whereas, a “malicious party” is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent.


6

Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of:

Utilization (of capabilities special to the accessed equipment)

Theft (such as, of intellectual property, financial assets, or toll facility access)

Eavesdropping (privacy invasions to humans)

Mischief (troubling, but apparently innocuous, tampering)

Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent)

Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs).

Responsibility for Your Company’s Telecommunications Security

The final responsibility for securing both this system and its networked equipment rests with you - Avaya’s customer system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to:

Installation documents

System administration documents

Security documents

Hardware-/software-based security tools

Shared information between you and your peers

Telecommunications security experts

To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure:

Your Avaya-provided telecommunications systems and their interfaces

Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces

Any other equipment networked to your Avaya products


7

Document Copies

To order copies of this and other documents:

Call: Avaya Publications Center Voice 1.800.457.1235 or 1.207.866.6701 FAX 1.800.457.1764 or 1.207.626.7269

Write: Globalware Solutions 200 Ward Hill Avenue Haverhill, MA 01835 USA Attention: Avaya Account Management

E-mail: [email protected]

For the most current versions of documentation, go to the Avaya support Web site: http://www.avaya.com/support.


8

Converged Network Analyzer Overview

What Is the Converged Network Analyzer?

The Converged Network Analyzer (CNA) is an immensely powerful performance monitoring and testing toolkit. The Converged Network Analyzer has both hardware and software elements.

Single board computers called "Chatterboxes" are distributed anywhere in the network to form a scalable grid-computing network (called a hive) with software for scheduling tests, collecting and analyzing data, and reporting network status.

Software "Test Plugs," are embedded in network hardware elements such as Secure Gateways, Media Gateways, IP phones, and Chatterboxes. Each software "Test Plug" is capable of initiating and receiving tests, and reporting test performance to the Chatterbox hive.

Within each Chatterbox hive, a hierarchy of zones is defined based on the organization's structure, or functional elements, or both. The zone hierarchy defines the location of each Test Plug, and therefore, where network performance can be monitored. The zone hierarchy defines the schema of how tests are placed between Test Plugs and "tunes" CNA to the specific customer network monitored.

Test plugs in secure gateways provide the unique ability to measure network performance "inside" VPN (Virtual Private Network) tunnels between secure gateways. Systems without this capability can only measure the overall performance between the endpoints of the tunnel. With this capability, performance can be measured over every link within the tunnel.

Test plugs in media gateways provide the ability to measure end-to-end service to the edge of the Public Service Telephone Network (PSTN), or at points where codec changes are required for interworking between high (LAN) and low (WAN) speed links.

The "CNA Client" presents a graphical user interface to the functions necessary to monitor the network, and to administer the Chatterbox hive.

A network may be monitored by more than one "hive" of Chatterboxes. Hives may not share Test Plugs or Chatterboxes.

CNA monitors the converged network:

• Test plugs, embedded in new Avaya IP phones, Secure Gateways, Media Gateways and Single Board Computers called "Chatterboxes" are distributed throughout the converged network.

• Each Test Plug can run tests with another Test Plug, or with a specified IP address.


9

• The Chatterboxes in the network automatically synchronize themselves into a computer grid or "hive" to share the load of administering user defined testing, analysis, and alarm notification; selecting endpoints (Test Plugs) and scheduling tests; and analyzing and reporting test results to users.

• The Chatterboxes and the Test Plugs provide continuous, proactive testing, based on realistic end-to-end tests.

• A user-defined zone hierarchy relates end-to-end test results to geographic areas, organizational structure, or both.

• All communication between Test Plugs, Chatterboxes, and users is encrypted to prevent unauthorized use of network resources.

• External alarm notifications can be combinations of email (with attached data), system logs, and SNMP traps for external alarm monitoring systems.

• All topologically related analysis and end-to-end analysis is available for viewing by multiple users. Multiple users can work with the same network map or with different customized maps.

• Real-time displays of test results and multiple analysis views assist network troubleshooting and fault isolation.

CNA is a completely distributed system. There is no central server controlling the endpoints.

• Single board computers (Chatterboxes):

• Plug in anywhere in the network

• Act as administrator, scheduler, analyzer, and Test Plug

• Configure with dynamic (DHCP) or static IP address

• Self synchronize into a grid or hive

• Provide highly scalable, decentralized architecture

• Have little or no impact on customer network performance

• Have no single point of failure.

• Test plugs:

• Configure with dynamic or static IP address (according to the device containing them)

• Can make end-to-end tests with other Test Plugs or IP addresses

• Report test results to Chatterbox hive

• Are embedded in new Avaya IP phones, Secure Gateways, Media Gateways and Chatterboxes.


10

How Does CNA Work?

Test Plugs are assigned to a hierarchy of zones.

• The zone hierarchy represents the structure of your company rather than the structure of your network. It identifies places where end users need services so that these services can be measured and analyzed realistically on an end-to-end basis. The zone hierarchy defines how tests will be made so that the test results are meaningfully related to what you want to measure.

• Zones may be structured by geography to measure Quality of Service (QoS) over Wide Area Networks (WAN), or they may be structured functionally to measure QoS between internal organizations, or both, at different levels.

Chatterboxes distribute operations, storage and analysis.

The Converged Network Analyzer automatically and continuously places tests between every pair of zones at the same level of the zone hierarchy to determine real time QoS data.

• The frequency of testing is configured by the CNA Network Administrator.

• For a test between two zones, Test Plugs are chosen at random from among any of those assigned to each zone or its sub-zones.

• All communication is encrypted to protect from outside attacks.

• Test Plugs participating in a test report the test results to the Chatterbox hive.

• Tests measure network parameters that affect QoS:

RTP (Real Time Protocol) is used for media streams such as voice, audio, and video that have a time-dependent relationship between packets. The RTP test echoes a media stream between two endpoints.

• Delay – How long (in milliseconds one-way) it takes the UDP packet stream to reach its destination

• Jitter – Unevenness in packet delay (in milliseconds)

• Loss – Percentage of packets lost in transit

Ping or echo-check is used to establish connectivity and measure basic connection characteristics between two endpoints.

• RTT (Round Trip Time) in milliseconds (ICMP both directions)



11

Traceroute collects routing information by identifying each node in succession until the destination is reached.

• Hop RTT – Round Trip Time (RTT) in milliseconds for each "hop" along the route (UDP outbound and ICMP inbound)

Transmission Control Protocol (TCP) Connect is used for media streams that do not have a time dependent relationship, but that must be transmitted accurately – data streams.

• Cerror – Connection success/failure

• Delay – How long (in milliseconds) it takes the connection to complete

There is an additional Inter Arrival Time variable for each test. It monitors the time between tests, and can be used to trigger an alarm when a link is down or a set of endpoints becomes isolated.

A Link Topology Map showing discovered nodes and links is generated automatically from paths taken by packets during testing. Alarms can be applied to individual links as well as to end-to-end communications between zones.

CNA Fault Tolerance

The Chatterbox hive continues to function when there are Chatterbox failures or network problems. The remaining Chatterboxes continue to run the tests administered (within system capacity, and using all Test Plugs that are still accessible). The test injection rate is scaled down proportionally to the number of Chatterboxes lost from the hive. If network connectivity is re-established, or the Chatterbox problem rectified, the lost Chatterboxes automatically rejoin the hive.

The ability of the system to continue running the tests set-up before the failure is limited by the resources available on the remaining Chatterboxes.

When a hive is split, certain administrative user commands will not be available (for example, re-keying the security keys, adding new Chatterboxes, etc.). This restriction is to prevent potential problems when the hive rejoins.

Test plug registration are shared among the whole Chatterbox hive, so any Chatterbox knows about all Test Plugs in the system and therefore can use any Test Plug in the system to perform tests.


12

CNA System Summary

Provides proactive, real-time monitoring 24/7 with instantaneous alarming

Is a lightweight system

• Runs entirely on a distributed system of Single Board Computers (Chatterboxes)

• Uses Test Plugs embedded in Avaya phones, secure gateways, and media gateways

Allows end-to-end testing

Is scalable due to distribution of operations, storage and analysis

Discovers network topology

Is configurable

• Test definition

• Statistical process control

• Alarm notification

Monitors a multi-vendor network


13

Intended Audience (Full Access)

There are two types of CNA users:

CNA Network Administrators have full access to CNA: and can configure the system, start tests, set up logins for other users, and save node positions and information so that all users have a common view. Even though numerous users can have administrator privileges only one administrator can be logged in at a time.

CNA Network Managers have view-only access to CNA. View-only access facilitates troubleshooting and maintaining the network. Up to 16 users can be logged in at the same time.

This document is intended for the CNA Network Administrators responsible for the deployment of the Converged Network Analyzer. This document covers the full-access mode of the CNA Client. The full-access mode of the CNA Client allows the CNA Network Administrator to:

Add Chatterboxes and test plugs to the system

Upgrade Chatterbox software

Change Chatterbox security keys

Administer user accounts and privileges

Define the Zone hierarchy

Assign Test Plugs to zones

Define Alarm Templates

Merge and unmerge nodes

Save and upload manual paths

Assign links and zones to Alarm Templates

Define alarm notifications

Create and save system and local Link Topology Maps.

All of the information provided in this document is directed at these specific tasks.

CNA Network Managers should see the CNA User Guide for information on using the CNA Client view-only mode for maintaining and troubleshooting the converged network.

There is one "super user" who assigns user accounts, passwords, and privileges for the other users of the system.


14

Quick Start Guide

Description Comments See Section

1 Install Chatterboxes on the network.

Chatterbox may have Fixed IP Address or Dynamic (DHCP) IP Address.

Installing Chatterboxes

2 Install the CNA Client.

Windows 2000 Pro, SP4 or Windows XP Pro, SP2.

The software is provided on an installation CD. Insert the CD and follow the directions provided.

3 Run the CNA Client.

First time operation - Add users

Running CNA Client

Administering Users

4 Add each Chatterbox to the Converged Network Analyzer hive.

Manually adding Chatterboxes prevents rogue devices from accessing the Chatterbox secure control mesh.

Administering Chatterboxes

5 Force registration of endpoints.

For security reasons, the endpoints (Test Plugs) find the Chatterbox hive. It is necessary to tell the endpoints where to find the Chatterboxes.

Registering Endpoints

6 Create the Zone hierarchy.

Defines which measurements are meaningful to return network performance data related to owning organization's communication patterns.

Configuring the Zone Hierarchy


15

Description Comments See Section

7 Assign Test Plugs to zones.

Locates endpoints in zones so that tests can be made between endpoints to measure network performance between zones at the same level.

Assigning Endpoints

8 Specify tests to run and configure test parameters.

Voice and media protocol (RTP), data protocol (TCP), delay (traceroute), and propagation delay (ping) tests.

Test Setup

9 Define alarm notification addresses.

Up to four each for Email, SNMP, and Syslog protocols.

Alarm Destination Settings

10 Configure Alarm Templates.

Define alarm types and parameters

Select notifications on alarm

Assign links and zones to template

Alarm Setup


16

Installing Chatterboxes

caution: Before installing a Chatterbox, be sure you have the correct external power supply for the available local voltage (120vac or 220vac).

note:

A USB storage key is sometimes used to provide a Chatterbox configuration file. The Chatterboxes do not work with all USB sticks. If the Chatterbox does not come up with the desired setup, try a different USB storage key. See Troubleshooting below.

Installing a Chatterbox Using Dynamic (DHCP) Addressing

New Chatterboxes are already set up to use DHCP addressing.

Verify the external power supply voltage. Separate models of external power supply are provided for 120vac and 220vac.

Record the MAC address. The Chatterbox's MAC address is listed as the Serial Number on the silver plate on the underside of the box.

Connect to the network with a Cat 5e or better cable. Connect to the port marked eth0.

Plug in the external power supply.

Connect the external power supply to the Chatterbox.

A new Chatterbox will automatically use DHCP addressing. If a Chatterbox has been previously installed using a fixed IP address, and you wish to change it back to dynamic addressing, generate the appropriate file on your notebook. Then save the file on a USB storage key with the default name: net_eth0 (no file-type extension). Insert the storage key in the Chatterbox before booting or power cycling.

Installing a Chatterbox Using Fixed IP Addressing

To install a Chatterbox with a fixed IP Address, generate the appropriate file on your notebook. Then save the file on a USB storage key with the default name: net_eth0 (no file-type extension). Insert the storage key in the Chatterbox before booting or power cycling.


17

Generating a Configuration File using the CNA Client

Use CNA Client to generate the Chatterbox configuration file:

Double-click the CNA Client icon. The Chatter Login dialog box appears.

Click Configure. The Chatterbox Network Configuration dialog box appears.

• To create a boot file for a Chatterbox with a fixed IP address, make sure that Use DHCP is not checked. Fill in the IP Address, Subnet Mask, and Default Gateway. Then press Save Configuration File. Specify the USB storage key as the location to save the file.

• To create a boot file to change an existing Chatterbox from fixed IP address to dynamic IP address (DHCP), check the Use DHCP checkbox and leave the rest of the form blank. Then press Save Configuration File. Specify the USB storage key as the location to save the file. Do not change the file name.


18

Troubleshooting

The Chatterbox will not accept configuration from the USB storage key:

USB storage keys are sometimes formatted in ways that are not recognized by the Chatterbox. The Chatterbox requires the formatting be FAT or FAT32. If the Chatterbox will not accept the configuration information, try reformatting the USB stick on a Windows PC.

• Plug the stick into a windows PC.

• Back up any data on the stick since formatting will erase it.

• Open Windows Explorer by double-clicking "My Computer."

• Find the icon for the "Removable" device corresponding to the USB stick.

• Right-click on the icon and select Format.

• In most cases, the default formatting options will be correct, but make sure that the file system is set to FAT or FAT32.

• Be absolutely sure you have the correct device selected for the USB memory stick.

• After formatting the stick, recreate the net_eth0 file on it and try again.

An endpoint will not register with the Chatter Hive.

If either the date on the Chatter hive or the date on the endpoint are not valid at the time of registration, the endpoint will not be allowed to register since the Chatterbox certificate cannot be authenticated. It is possible to check the dates on the Secure Gateway and Media Gateway and the administrator should verify that they are the current date.


19

Running CNA Client (First Time Procedures)

Double-click the CNA Client icon to launch the application.

The first time that CNA Client runs on a machine, the system will request the IP address of any known Chatterbox (within the hive) to connect.

If you are the first CNA Network Administrator on a new system, you must determine this IP address and supply it to other users. See First Time Procedures below and Determining Chatterbox IP Address for more information.

After the first successful connection, the CNA Client will maintain a list of Chatterbox IP addresses for the current hive and will automatically pre-populate the IP Address field for future connections. (You can log in to a different hive by changing the IP Address before clicking Login.

When your login is accepted, you will have full-access privileges if you are a CNA Network Administrator. CNA Network Managers have view-only access.


20

First Time Procedures

For a new system, the following procedures are necessary or desirable during the first login:

The first time you log in, you must supply the IP address of any known Chatterbox. If any Chatterbox was installed with a fixed IP address, you can use that address. Otherwise, see Determining Chatterbox IP Address for information on finding the IP address of a Chatterbox that uses dynamic (DHCP) addressing.

The first time you log in, use the special "super user" User name and Password provided with the installation CD.

For a new system, when you login as the "super user" you will be asked to change your password immediately upon successful login.

A new password must:

• be 8 to 16 characters in length

• Include at least one character from each of the following three groups:

• letters

• digits

• specials `-=\[];',./~!@#$%^&*()_+|{}:"?

As soon as the password is changed, you will be asked to login again using the new password.


21

For a new system, the first time you log in, you should concentrate on the following tasks:

• Administering other user's accounts and privileges. See Administering Users.

• Adding Chatterboxes to the system. See Administering Chatterboxes.

• Forcing registration of Test Plugs. See Registering Endpoints.

This completes the identification and authorization of users, and the identification and connection of the hardware elements of the Converged Network Analyzer.

Zones, tests, and alarm templates are the tuning parameters of the software elements of the Converged Network Analyzer. Many of the tuning decisions were made at the time the hardware was deployed in specific planned zones. This information should be reviewed and adjusted to fit the deployed hardware where necessary. The same CNA Client is used to input the tuning information.


22

CNA User Interface (Full Access)

Reference Card/Feature Introduction: CNA Administration The Converged Network Analyzer (CNA) is an immensely powerful performance monitoring and testing toolkit. The Converged Network Analyzer has both hardware and software elements.

Single-board computers called "Chatterboxes" are distributed anywhere in the network to form a scalable grid-computing network (called a hive) with software for scheduling tests, collecting and analyzing data, and reporting network status.

Software "Test Plugs" are embedded in network hardware elements such as Secure Gateways, Media Gateways, IP phones, and Chatterboxes. Each software "Test Plug" is capable of initiating and receiving tests, and reporting test performance to the Chatterbox hive.

The "CNA Client" presents a graphical user interface to the functions necessary to monitor the network.

The CNA Client window contains the following areas:


23

Titlebar: Identifies the running program as Avaya Converged Network Analyzer. Has the standard Windows Minimize, Restore/Maximize, and Close buttons.

Menubar: Holds the menus.

Button Bar:

The Button Bar is described after the Function Tabs.


24

Function Tabs:

• Tests tab: Displays the results of monitoring the network as color-coded links on the Link Topology Map, or as color-coded cells on the End-to-End Matrix.

The tests that are currently running are listed in the Tests tree. Selecting the test variable in the branch under the test name determines the data that is displayed in the info window and display pane. Selecting the analysis view from the drop down list on the button bar determines the color coding.

• Tests tab with Link Topology Map selected ( ). Text size and map arrangement buttons are enabled.

The info window below the Tests tree displays node identification or link performance information (for the selected test/variable and analysis view) when the user holds the mouse over a node or a link.

Clicking on a link opens an interactive display of test results for that link. See Interactive Data Display.

Clicking on a node opens a dialog box that displays node information and allows the node name to be customized. See Assigning Node Names.


25

• Tests tab with End-to-End Matrix selected ( ). Text size buttons remain enabled, but map arrangement buttons are disabled.

The info window below the Tests tree displays information about end-to-end status (for the selected test/variable and analysis view)when the user holds the mouse over a cell.

Clicking on a cell opens an interactive display of test results. See Interactive Data Display.

Clicking on an underlined link at the left of the cells moves down the zone hierarchy. Clicking on an underlined link in the Path above the cells moves up the zone hierarchy.


26

• Tests tab with Chatterbox tree expanded.

When the Chatterboxes tree is expanded, it is color coded to show the status of each Chatterbox:

o Black indicates that the Chatterbox is in service.

o Gray indicates that the Chatterbox is in the process of being added to the hive.

o Red indicates that the Chatterbox has dropped out of the hive and is unreachable or unresponsive.

• Zones tab: Select Zones tab to edit or view the zone hierarchy. Endpoint IP addresses (with endpoint names if defined) display at the lowest level in the Zones tree. Select the Assign Endpoints tab and double-click on an endpoint to open a dialog box that displays node information and allows the node name to be specified. All buttons except Refresh are disabled.

Within each Chatterbox hive, a hierarchy of zones is defined based on the organization's structure, or functional elements, or both. The zone hierarchy defines the location of each Test Plug, and therefore, where network performance can be monitored. The zone hierarchy defines the schema of how tests are placed between Test Plugs and "tunes" CNA to the specific customer network monitored.


27

• Zones tab with Add Zones subtab selected:

To add a zone, click on the parent zone in the Zones tree (the Parent Zone field will fill), fill in the New Subzone Name, and then click Add.

• Zones tab with Remove Zones subtab selected:

To remove a zone, click on the zone in the Zones tree (the Selected Zone field will fill), and then click Remove.


28

• Zones tab with Rename Zones subtab selected:

To rename a zone, click on the zone in the Zones tree (the Current Zone Name field will fill), fill in the New Zone Name, and then click Rename.

• Zones tab with Assign Endpoints subtab selected:


29

Select a zone. Select an Available Endpoint and use the right arrow button (>) to add the endpoint to the zone. Select from the Endpoints in Selected Zone and use the left arrow button (<) to remove the endpoint from the zone and return it to the list of Available Endpoints.

• Alarms tab: Select Alarms tab to edit or view the descriptions of the alarm templates and which links or zones are assigned to each template.

Alarm Templates allow multiple test parameters and multiple alarm notification actions to be defined for many links or zones simultaneously.

Color indicates template membership, not link or zone status.

Links option button selected ( ).


30

Zones option button selected ( ).

• Click on the template name to select an Alarm Template. All links and zones that are not assigned to a user defined alarm template are assigned to the SYSTEM DEFAULT template.

• Click New to create a new user defined alarm template.

• Click Rename to rename the selected user defined alarm template. The SYSTEM DEFAULT alarm template cannot be renamed.

• Click Delete to delete the selected user defined alarm template. The SYSTEM DEFAULT alarm template cannot be deleted. Links and zones assigned to the deleted template are reassigned automatically to the SYSTEM DEFAULT template.


31

• Click Links or Zones to display the links or zones view.

• When a user defined template is selected, click any link or zone to assign it to the selected template. Click the link or zone a second time to cancel the assignment. If you leave the template for any reason, assignments are automatically saved and cannot be canceled. You must go to the SYSTEM DEFAULT template and select the link or zone to remove it from the user template.

• To find the template to which a link or zone is assigned:

o Switch to the Tests tab. Hold the mouse over the link or zone. The assigned template displays in the Info window below the Tests tree. Switch back to the Alarms tab and select the assigned template.

or

o Switch to the Alarms tab. By default, all links and zones are assigned to the SYSTEM DEFAULT template until they are assigned to a user-defined template.

o If the link or zone is green, the link or zone is assigned to the currently selected (highlighted) template, including the SYSTEM DEFAULT template.

o If the link or zone is black, a user-defined template is selected and the link or zone is assigned to the SYSTEM DEFAULT template.

o If the link or zone is red, it is assigned to a different template. Click each defined template until the link or zone you are interested in turns green.

• Green links and zones are in the selected (highlighted) template. Black links or zones are assigned to the system default template (if not selected), and red links or zones are assigned to a different user-defined template.

• Each of the notification actions (four each of SNMP, Email, and Syslog) selected for the Alarm Template is checked or unchecked. See Alarm Destination Settings.


32

• Select Test and Variable (using spinner buttons) to show or set the threshold limit for tolerance alarms for each test/variable as it applies to all links and zones assigned to the template.

• Checkboxes for each Test and Variable indicate whether Tolerance alarms (based on specified threshold) and/or Control alarms (stability), for each link and zone assigned to the template generate notifications, and whether to include a CSV (spreadsheet) file of test results with Email notifications.

Button Bar (buttons enabled when applicable):

• Refresh: Refreshes the display.

• Font Increase/Decrease: Increases or decreases the label font size for all nodes on the Link Topology Map and for all row/column labels on the End-to-End Matrix. This setting applies only during the current session. It is not saved.


33

• Line Thickness Increase/Decrease: Increases or decreases the line thickness for all links on the Link Topology Map. This setting applies only during current session. It is not saved.

• Map Rotate Left/Right: The Link Topological Map (or selected region) is rotated a few degrees left (counterclockwise) or right (clockwise) for each click. Holding either button down will result in continuous rotation in the selected direction. Rotate Left and Rotate Right apply to the whole Link Topological Map display if no selection marquee rectangle is present, or only to the selected area when a marquee rectangle is present. The position of nodes is saved only if the user selects File > Save (System) or File > Save (local).

• Map Center/Map Expand/Map Arrange: Map Arrange redraws the entire topological map (if no selection marquee is present, or only the selected area when a marquee is present) based on a statistical algorithm to lay out the nodes in a more readable fashion. This may provide a better starting point for positioning the nodes in a logical fashion. (Reload the system or local positions if you don't like the result of Map Arrange.) Map Center and Map Expand apply to the whole Link Topological Map display if no selection marquee is present, or only to the selected area when a marquee is present. The position of nodes is saved only if the user selects File > Save (System) or File > Save (local).

You can also reposition individual nodes by dragging to a new location.


34

• Link Topological Map/End-2-End Matrix: Available only on the Tests tab. Displays either the Link Topological Map, or the End-to-End Matrix.

• Analysis View Drop Down: Available only on the Tests tab. Selects an analysis view on the Link Topological Map or End-to-End Matrix. Each view is based on the same underlying data associated with each half (one-way) link or cell, but the analysis view chosen determines the coloring for the half link or cell. Each half link or cell can retain up to 150 test data points.

• Tolerance is one of the two alarm definitions. The links are colored depending on whether the most recent series of data points are above the threshold (red) or below the threshold (green). The Threshold value can be checked on the alarm template. The number of consecutive data points above the threshold to trigger the alarm can be checked at Alarms > Chart Strikes. A single data point below the threshold clears the alarm.

• Control is the other alarm definition. Green means steady (as the link has been performing in the past); red means an abrupt increase; blue means an abrupt decrease. These are self adjusting thresholds based on a statistical technique. The number of consecutive data points outside the established thresholds to trigger the alarm can be checked at Alarms > Chart Strikes. A single data point between the current thresholds clears the alarm. Control alarms clear automatically when the thresholds adjust.


35

• Minimum, Median, and Maximum—colors the links according to the Upper and Lower Thresholds set in the tool bar. The link is summarized by the Minimum, Median (middle value) or Maximum value as selected in the drop-down list. Then the half link or cell summary value is used to determine the color of the link as specified by the thresholds in the tool bar.

• Threshold Lower/Upper:

• When enabled, the Lower Threshold and Upper Threshold values adjust the link or cell colors.

• Those links or cells whose Minimum, Median, or Maximum is below the lower threshold are colored green, those above the upper threshold are colored red, and between the two are colored a gradation from white to pink to red.

• The thresholds can be manipulated to isolate the lowest or highest values on the Link Topology Map or End-to-End Matrix.

• The links or cells with the highest values are not necessarily the “worse problems.” For example, globe spanning RTP tests tend to have higher delays than shorter distance tests.

Status Bar:

• Status Message: (First Field) Status of most recent event.

• Current Test or Tab:

• Tests Tab: the name of the test selected in the Tests tree.

• Zones Tab: "Zone Configuration."

• Alarms Tab: "Alarm Configuration."

• Heartbeat:

The heartbeat shows data transfer to the CNA Client and connectivity of the CNA Client to the Chatterboxes. As long as this display is moving, the CNA client is receiving data.


36

Administering Users

Any CNA Network Administrator can assign logins, passwords, and user privileges. For security reasons:

You must change the password for the default administrative user immediately after you login the first time.




• letters

• digits

• specials `-=\[];',./~!@#$%^&*()_+|{}:"?

Unused login accounts should be closed immediately.

Only the necessary level of privilege should be granted to each user.

Assigning User Login IDs, Passwords and User Privileges

To administer users, select Edit > Manage Users

When the Manage Users dialog box opens, the Add Users tab is selected.


37

To add a user:

1. Select the Add Users tab if it is not already selected.

2. Enter the User Login ID (6-12 letters and digits).

3. Set User Type to Full Access (CNA Network Administrators) or View Only (CNA Network Managers).

4. Enter and confirm the Password. A new password must:



• letters

• digits

• specials `-=\[];',./~!@#$%^&*()_+|{}:"<>?

5. Click Add User.

The user is added and the form is cleared for the next entry.

6. When finished, click the Remove Users tab to see a list of users or to remove users, or click Done to close the dialog box.

A maximum of 64 users can be defined. A maximum of 16 users can be logged in at the same time. Only one full-access user can be logged in at a time.


38

To display a list of users and/or delete a user:

1. Select the Remove Users tab if it is not already selected.

All users are displayed with their access level.

2. Click any user to highlight.

3. Click Remove User to remove highlighted user.

4. When finished, click the Add Users tab to add more users or click Done to close the dialog box.

To reset a password:

1. Find the user on the list.

2. Note the user's access level.

3. Delete the user.

4. Add the user back with appropriate access level and agreed upon password.

Passwords must:



• letters

• digits

• specials `-=\[];',./~!@#$%^&*()_+|{}:"?


39

Administering Chatterboxes

Administering Chatterboxes has two main functions:

Identifying the hardware pieces of the hive so that they can find each other on the network.

Managing the security and status of the hive.

The Chatterbox management functions are on the File and Edit menus.


40

Edit > Add a Chatterbox

Chatterboxes are added to the hive manually to maintain security. Rogue devices cannot access the hive.

To add a Chatterbox, specify the IP Address and the default password, then click OK. This dialog box closes after adding a Chatterbox unless you check the Add more Chatterboxes now? checkbox.

Note:

You cannot add a Chatterbox when one of the existing Chatterboxes is unreachable or unresponsive (red in the Chatterbox tree), or when another Chatterbox is still being added to or removed from the hive (grey in the Chatterbox tree). You can remove a Chatterbox that is red and then add a new one.

After the Chatterbox has been successfully added, its password is the CNA system password set by the first CNA Administrator when he or she changed the password from default on first login.

When a Chatterbox is removed, it goes back to factory default password. The next time you add the Chatterbox, you use the default password originally provided by Avaya support.

An hour after adding one or more Chatterboxes, use Edit > Defragment to re-optimize the hive.


41

Edit > Remove a Chatterbox (View List)

To view a list of Chatterboxes, select Edit > Remove a Chatterbox.

To remove a Chatterbox, click the name or IP address to highlight it. Then click OK to remove the Chatterbox. This dialog box closes after removing a Chatterbox unless you check the Remove more Chatterboxes now? checkbox.

Note:

The format of each entry is <Chatterbox name>(<IP Address>). Depending on whether and how you name Chatterboxes, this sometimes results in the IP address followed by the same IP address in parentheses.

Note:

You cannot remove a Chatterbox when another Chatterbox is still being added to or removed from the hive (grey in the Chatterbox tree). You can remove a Chatterbox that is unreachable or unresponsive (red in the Chatterbox tree) as long as any previous adds or removes have completed.


42

Chatterbox Status

You can determine the Chatterbox status at any time by expanding the Chatterboxes tree on the Tests tab.

Black indicates that the Chatterbox is in service.

Gray indicates that the Chatterbox is in the process of being added to or removed from the hive.

Red indicates that the Chatterbox is unreachable or unresponsive.

Edit > Change Security Keys

Selecting Edit > Change Security Keys generates new security keys for encrypting messages between CNA components. The keys are generated automatically and distributed to all CNA components. You should change security keys:

On a regular monthly basis

Whenever you feel that the network may have been compromised in any way

Performance Tuning

The Memory Usage display provides guidance on sizing the Chatterbox hive to the zones, endpoints, and tests in the network. The Defragment... command consolidates and redistributes operations so that the scheduling, analysis, and storage are optimized for the hive.


43

Edit > Show Memory Usage

Displays a message box that tells the user how close the system is getting to maximum capacity.

You can use these numbers to determine whether the distributed system of Chatterboxes is reaching capacity for the number of zones, tests, etc. that it is performing.

If Required is greater than Available, the Chatterbox hive is not processing/analyzing some of the links, cells, or tests requested, and the hive requires at least one additional Chatterbox to share the load.

If Required is less than but close to Available, the Chatterbox hive is nearing capacity. Adding zones or tests could cause the system to start dropping analyses.

About an hour or so after adding the Chatterbox, when the system has had time to stabilize, you can select Edit > Defragment to optimize the system performance.

Edit > Defragment

Consolidates and redistributes operations so that the scheduling, analysis, and storage are optimized for the hive.

Defragmentation should be done:

Whenever one or more Chatterboxes are added to, or deleted from the hive (after an hour or so for stabilization)

to rebalance the hive when a Chatterbox goes out of service (turns red in the Tests tab tree) or returns to service (after an hour or so for stabilization)

File > Upgrade Software

Occasionally, new software is provided to fix problems and enhance operation and security.

To upgrade Chatterboxes and the CNA Client to the latest release:


44

1. Login using the current version of the CNA client.

2. On the Tests tab, click the "+" sign in front of the Chatterboxes list.

3. Copy the IP address of the first Chatterbox in the list for later use.

4. On the Zones tab, expand all zones and take a screen dump of the expanded tree. (Press Alt-PrtScn to capture screen to clipboard.) On the Tests tab, expand the Chatterboxes entry and take a screen dump of the list of Chatterboxes. On the Alarms tab, record all the alarm settings for each of the templates. In the Alarms menu, Alarm Destinations, take a screen dump of each of the three destination tabs. Depending on the upgrade, it may be necessary to reconfigure the system.

5. Select File->Upgrade Software.

6. Enter the URL of the software update. This information will be supplied by Avaya

support.

7. Enter the md5sum value. This value will usually be available to you as the contents of a specific file provided by Avaya support. Copy the file contents exactly without any extra characters.

8. Click Upgrade. The Chatterboxes will reboot and upgrade.

9. Logoff.

10. Download the revised CNA Client zip file from the URL provided by Avaya support.

11. Locate the Chatterbox directory and unzip the CNA Client files into that directory.

When you login again, the CNA Client will be updated. It may be necessary to indicate the IP address of the Chatterbox to log into. (This address was saved earlier.)

Determining That an Upgrade Completed

The Chatterbox software and the CNA Client have an interface version number determined at build time. All Chatterboxes and CNA Clients must have the same version number to be able to talk to each other. In an upgrade in which the interface number change was incomplete, some of the Chatterboxes will not be able to communicate with the rest of the Chatterboxes and the CNA Client. This shows up on the CNA Client screen — Chatterboxes that have not been properly updated turn red. (They all turn red if the CNA Client hasn't been updated.)


45

Recovering From a Failed Upgrade

Once it is determined that one or more Chatterboxes did not get upgraded, you can connect to any Chatterbox that did not upgrade using the old CNA Client, and performing the upgrade on it again. When you connect to a Chatterbox that did not upgrade, it will still show the other Chatterboxes as being in the hive. You will have to remove the already upgraded Chatterboxes from the hive so that only the Chatterboxes that did not upgrade remain in the hive. Then perform the upgrade again.

If the upgrade failed in such a manner that you are not able to connect to the Chatterbox using either the new or old CNA Client, you should reset the Chatterbox to factory default (See Resetting a Chatterbox to Factory Default Settings). This will ensure that the Chatterbox runs the original version of CNA with which it was shipped by Avaya. You can then connect to the Chatterbox using the original CNA Client software and upgrade to the latest software.


46

Resetting a Chatterbox to Factory Default Settings

It may be useful to reset a Chatterbox to a well known state (for example, if the CNA software is not functioning, or an upgrade fails). You can reset a Chatterbox to the state it was in when it was obtained from Avaya.

To reset the Chatterbox to the factory default, press the reset pin (accessible through the hole on the face place where the serial ports are) while rebooting the Chatterbox. Release the pin about 5 seconds after the Chatterbox has powered up. The reset process takes about 60 seconds, during which time the Eth1 LED glows solid amber. After the process is complete, the LED will go off for a few seconds and then come on permanently as usual.

After the reset, the state of the box is as follows:

The Chatterbox will retain the IP address last configured or obtain an IP address from a DHCP server if last configured for DHCP.

The CNA software running on the Chatterbox is the version the Chatterbox was shipped with. Any upgrades that were performed after obtaining the Chatterbox are lost.

The running configuration of the Chatterbox (hive members, zones, Test Plugs, tests, etc.) will be empty.


47

File > Static Configuration

There are two ways to generate the file for the Chatterbox boot sequence.

Selecting File > Static Configuration opens the Chatterbox Network Configuration dialog box.

• To create a boot file for a Chatterbox with a fixed IP address, make sure that Use DHCP is not checked. Fill in the IP Address, Subnet Mask, and Default Gateway. Then press Save Configuration File. Specify the USB storage key as the location to save the file.

• To create a boot file to change an existing Chatterbox from fixed IP address to dynamic IP address (DHCP), check the Use DHCP checkbox and leave the rest of the form blank. Then press Save Configuration File. Specify the USB storage key as the location to save the file.

Determining Chatterbox IP Address

Chatterboxes can be configured for network connectivity in two ways:

Static IP Address — In this case, the address is already known.

Dynamic IP Address (DHCP) — The system administrator must provide this information via some suitable mechanism.

For example, a standard Linux DHCP server has a dhcpd.leases file that contains MAC addresses of DHCP clients with the corresponding IP address. The IP address of a Chatterbox can be determined by locating the correct entry in this table. The Chatterbox's MAC address is listed as the Serial Number on the silver plate on the underside of the box.


48

Moving a Hive

You may need to move a hive to a new set of IP addresses occasionally. The most frequent reason for moving a hive is to set it up in a lab first, and then move it to the real network. The general procedure is:

1. Remove all but one Chatterbox from the hive.

2. Move the remaining Chatterbox to its new IP address (database remains intact).

3. Start CNA Client using the new IP address of this Chatterbox in the first login screen. Use the password from the previous hive.

4. Add the other Chatterboxes back to the hive.

The detailed procedure is as follows:

1. Stop all tests.

2. Select Edit > Remove a Chatterbox.

3. Click on each Chatterbox IP address, one at a time, and click OK in the Remove Chatterbox dialog.

4. When there is a single Chatterbox left, exit CNA Client.

5. Move the "last" Chatterbox to new location and determine its IP address. The database remains intact since the Chatterbox hasn't been removed from the hive, even though it has been moved.

6. Delete the CNAGUI directory in the directory where you unzipped CNAGUI.zip.

7. Extract CNAGUI.zip back into that directory.

8. Double click CNA Client icon.

9. login using the new IP address, any administrative User ID, and the previous password for that account.

10. Select Edit > Add a Chatterbox.

11. Add back each Chatterbox that was removed. The database will propagate throughout the hive. Use the factory default password to add each Chatterbox.

12. Start the desired tests.

13. Edit > Defragment should be run after the system has stabilized for an hour.


49

Registering Endpoints

A Chatterbox hive consists of one or more Chatterboxes and a collection of registered endpoints or Test Plugs. The IP address of the Test Plug is registered with the hive so that the hive can schedule tests and receive reports. The location of the Test Plugs (described by the zone hierarchy) determines where it is possible to measure network performance on an end-to-end basis. The end-to-end results are then extended to links along the path.

To prevent endpoint hijacking, endpoints or Test Plugs find the Chatterbox hive. They receive the Chatterbox IP address through a direct interface. The registration protocol prevents registration of rogue endpoints.

A maximum of 100 endpoints (per system, at all levels) is allowed

• A maximum of 70 endpoints may be IP phones

• To allow more than 30 network elements, endpoint devices should be configured in the following order:

• Add all Chatterboxes to the hive

• Register Security Gateways and Media Gateways

• Register IP Phones

Configure the IP phone DHCP servers so that the IP phones know the addresses of at least one Chatterbox each. Not all phones need to register with the Converged Network Analyzer. We recommend at least 2 or 3 candidates on each LAN segment of interest, but a maximum of 2 can be assigned to the LAN segment's subzone. Reboot the relevant phones to force them to reregister with the DHCP servers, and then with the Converged Network Analyzer.

A subzone that contains endpoints (usually a LAN) can have no more than 2 endpoints registered

For Release 2.2, there are two types of endpoints or Test Plugs:

Chatterbox Test Plugs

Secure Gateway Test Plugs

Chatterbox Test Plugs

Chatterbox Test Plugs automatically register when the Chatterbox is added to a hive. They are particularly useful for measuring network performance between Network Operations Centers or similar hubs where the Chatterboxes are usually placed.


50

Secure Gateway Test Plugs

Test plugs in secure gateways provide the unique ability to measure network performance "inside" VPN (Virtual Private Network) tunnels between secure gateways. Systems without this capability can only measure the overall performance of the tunnel. With this capability, performance can be measured over every link within the tunnel.

Use VPN Manager 3.6 to configure the Secure Gateway test plugs. (If you must use VPN Manager 3.5, contact Avaya support for instructions. VPN Manager 3.5 requires individual access to each Secure Gateway GUI.) See VPN Manager documentation for additional details.

1. Define the IP address to be used for registration.

2. Propagate the IP address for registration to all Secure Gateways in the domain.


51

Configuring the Zone Hierarchy

Within each Chatterbox hive, a hierarchy of zones is defined based on the organization's communication structure, geographic structure, functional elements, or in any other meaningful way. The zone hierarchy declares where Test Plugs exist, and therefore, along which paths network performance can be monitored.

Of all the possible combinations of two endpoints, the zone hierarchy defines which combinations are meaningful to the organization for monitoring end-to-end network performance. Specifically, the Converged Network Analyzer measures end-to-end network performance between zones defined at the same level. Test plugs for each test are selected randomly from any level within each zone and its subzones.

The definition of the zone hierarchy is a "tuning" parameter that adapts and optimizes the Converged Network Analyzer to the specific customer network being monitored. The hierarchy of zones determines the specific end-to-end paths to be monitored (by defining zones at the same level) and therefore, how the results are analyzed and presented. The hierarchy of zones can be arranged geographically to help track long-distance link performance, functionally to help track inter-department communication performance, or in any other way that is meaningful for defining the end-to-end paths to be monitored.

It is absolutely essential that the zone hierarchy be planned at the same time that Test Plug deployment is planned. The Test Plugs have to be in the proper physical place to measure the network performance to that place. The actual configuration of the zone hierarchy is a matter of defining relationships between endpoints so that tests can measure end-to-end performance in meaningful ways.

Here is one of many possible ways to set up the hierarchy:

1. Imagine your organization as a cloud of bright stars (LANs) that need to communicate with each other. Link each little group of stars to other little groups with a lighted line. Make the width of the lighted line (link or pipe) proportional to the traffic that flows across it. Now back away and identify where groups of two to five of the brightest (highest traffic) pipes come together. This is a good place to put the first level in the zone hierarchy. It defines the destination endpoints of the most active links. If there are too many active links to use this strategy, move up a level and get five new subzones to expand the hierarchy and reduce the count to no more than five subzones in any zone. (More than five subzones per level makes testing inefficient.)

2. Identify each little group of two or more LANs that go through a common router or switch. This becomes a subzone at the lowest level. (The "leaf" node. The endpoints in the LANs are the "leaves.")

3. Work upward from the bottom (groups of LANs) and downward from the top (endpoints of high traffic links). Eventually, the bottom and the top will meet, sometimes with a different number of levels in each branch.


52

4. If communication between two endpoints requires a VPN, you can use either the Secure Gateway test plug or another Test Plug beyond the secure gateway for each endpoint. Tests originating in the Secure Gateway Test Plug measure each link in the tunnel. Test originating from Test Plugs behind the Secure Gateway treat the tunnel as a single hop.

5. The main reason for grouping at each level is to be able to specify monitoring of network performance between same-level zones.

Zone Management Functions

You can edit or view the tree structure of the hierarchy by choosing the Zones tab.

The Zones tab shows the hierarchy tree below the function tabs. By clicking on the plus sign to the left of each level, you can expand the level. By clicking on the minus sign to the left of an expanded level, you can collapse it again. At the lowest level, the expansion shows individual Test Plugs.

A zone can contain either subzones or endpoints (Test Plugs), but not both.

Endpoints cannot be assigned to the first level (parent or root) zone. Their should be at least 2 levels in the zone hierarchy.

A maximum of five subzones can be defined in one parent zone.

A maximum of 50 zones (per system, at all levels) is allowed.

Zone names must be unique within the Chatterbox hive.

Zone names should be selected to describe the zones geographically, functionally, or any other way that makes the data meaningful.


53

To configure the zones:

1. Select a starting point by clicking in the hierarchy tree.

2. Click the tabbed form for what you want to do:

• Add Zones adds the new sub-zone under the selected zone.

• Remove Zones removes the selected zone.

• Rename Zones renames the selected zone.

• Assign Endpoints allows assignment of Test Plugs to zones.


54

Assigning Endpoints

A maximum of 100 endpoints (per system, at all levels) is allowed.

• A maximum of 70 endpoints may be IP phones.

• To allow more than 30 network elements, endpoint devices should be configured in the following order:

• Add all Chatterboxes to the hive.

• Register Security Gateways and Media Gateways.

• Register IP Phones

A subzone that contains endpoints can have no more than 2 endpoints.

1. Select the zone in the hierarchy tree.

2. Each Test Plug can be assigned to one and only one zone. To add a Test Plug to the selected zone, click the endpoint in the Available Endpoints list, then click the right arrow button to add (or move) the test plug from that list to the Endpoints in Selected Zone list.

3. Similarly, to remove a Test Plug, select it from the Endpoints in Selected Zone list, then click the left arrow button to move it back to the Available Endpoints list.


55

Test Setup

CNA provides a number of tests that the CNA Network Administrator can choose to run. You can see the running tests listed in the Tests tree. You can see the complete test parameters using the Test menu.

Note:

The Tests menu for the CNA Network Administrator shows all tests (none are grayed out). Use the Tests tree on the Tests tab to determine which tests are running.

Clicking on a test name opens a dialog box:

If the test is running, the test setup displays, the frequency can be changed (and the test restarted), and the test can be stopped.

If the test is not running, test parameters can be entered and the test can be started.

Currently the Converged Network Analyzer provides four tests:


• Delay – How long (in milliseconds one-way) it takes the UDP packet stream to reach its destination







• Hop RTT – Round Trip Time (RTT) in milliseconds for each "hop" along the route (UDP outbound and ICMP inbound).


56


• Cerror – Connection success/failure

• Delay – How long (in milliseconds) it takes the connection to complete


Each test can run between one Test Plug and an IP address, or between two Test Plugs.

Unary tests (between a Test Plug and a designated IP address) for each level of the hierarchy tree are run by randomly choosing a Test Plug from anywhere in the zone to represent the zone. The other endpoint is a specific IP address specified by the CNA Network Administrator.

Binary tests (between two Test Plugs) for each level of the hierarchy tree are run as follows:

• If a zone has sub-zones, then tests are run between each pair of sub-zones in each direction. The Frequency parameter for each test determines how many of these tests run each minute including all levels of the hierarchy. A random Test Plug is chosen from anywhere in each of the two sub-zones to participate in the test.

• Tests are run between pairs for each level of the hierarchy.

• An empty zone (no sub-zones, no Test Plugs) will not participate in any tests. A zone that does not lead to Test Plugs at some node will not participate in any tests.

The parameters for each running test can be viewed using the Tests menu.

Different dialog boxes are used for running and stopped tests:

For running tests, the test setup displays, the frequency can be changed (and the test restarted), and the test can be stopped.

If the test is not running, test parameters can be entered and the test can be started.


57

Parameters Common Among All Tests

Frequency (per minute): This designates how often tests are conducted between zones. The specified frequency applies to all tests of the type indicated and the number of tests is distributed appropriately to test the entire network.

There is a trade-off between setting the frequency for a specific test higher to detect down links and other problems faster, and setting the frequency low enough so that all of the tests together do not generate a load that exceeds Chatterbox hive or endpoint capacity.

In the ideal case, with unlimited capacity, set the frequency based on the zone hierarchy as follows:

• Follow down the levels of the hierarchy. At each branch point add the number of paths as follows:

• For each two-way branch, add 2 paths.

• For each three-way branch, add 6 paths.

• For each four-way branch, add 12 paths.

• For each five-way branch, add 20 paths.

• Don't add any for zones which contain endpoints instead of subzones.

• Divide the total number of paths by the number of minutes desired between tests. For example, one hundred paths to be checked every minute means a frequency of 100 tests per minute. If two minutes between tests is acceptable, then 50 tests per minute is sufficient.

Avaya suggests tuning the system as follows:

• Start the system with the default setting (5 tests per minute).

• Wait a while and then look at several links and note the Inter Arrival Time (time between tests).

• If the Inter Arrival Time is too long, restart the system with a higher frequency. Look at the link test spacing and the drops to see if tests are being dropped. If tests are being dropped, the total frequencies (for all types of tests) is too high.

• Raise the frequency if the system can handle it.

Setting the frequency is an interactive and iterative process.

Repeats (0 if forever): The number of times the test will repeat. “0” indicates that testing will continue until the CNA Network Administrator manually stops the test.

Remote IP or Host: For the single-ended (unary) test, indicates the destination IP address.


58

Topological analysis: Indicates whether the test results are associated with the links on the paths between the pair of endpoints involved in the test in the network topology map, or only end-to-end for the End-to-End Matrix. Not included for Traceroute which is always reported by link in the network topology map.


59

RTP Parameters

Common Parameters: Frequency, Repeats, Remote IP or Host, Topological analysis.

Number of packets: Number of packets sent in the RTP stream

Period (ms): The time between sending out successive RTP packets

Payload length: Number of bytes in the payload of the packets

Lingering (milliseconds): Number of milliseconds (round trip) before a packet is treated as lost

TOS byte: TOS byte value in the header of the test packet. Typically, a TOS value of 0 indicates no special treatment, while higher TOS values would potentially give the packets priority through the network.


60

Traceroute Parameters

Common Parameters: Frequency, Repeats, Remote IP or Host.

Number of packets: Number of packets sent in each traceroute request.

Period (ms): The time between sending out successive UDP packets with increasing time-to-live (TTL) from one to the maximum number of "hops."

Timeout (seconds): Total amount of time to wait for ICMP packets to come back.

Maximum TTL: Maximum time-to-live in "hops" over links between nodes.



61

Ping Parameters


Number of packets: Number of packets in the test message

Period (ms): The time between sending successive ping packets

Timeout (seconds): Time (round trip) before a packet is declared lost

Length (bytes): Length of the packets in bytes



62

TCP Connect Parameters


Port: Port for the TCP connection

Timeout (seconds): Timeout for the connection attempt to complete


63

Alarm Setup

The Converged Network Analyzer monitors individual links and end-to-end paths (represented as cells). Two types of alarms can be specified for each variable in each of the four test types. An additional Inter Arrival Time variable in each test monitors the time between tests, and can be used to trigger an alarm when a link is down or a set of endpoints becomes isolated. Alarm Templates simplify the specification of test parameters and notification destinations for large numbers of links and cells.

Test Types and Variables

Currently the Converged Network Analyzer provides four tests:


• Delay – How long (in milliseconds one-way) it takes the UDP packet stream to reach its destination.







• Hop RTT – Round Trip Time (RTT) in milliseconds for each "hop" along the route (UDP outbound and ICMP inbound).


• Cerror – Connection success/failure.

• Delay – How long (in milliseconds) it takes the connection to complete.



64

Alarm Types

The Converged Network Analyzer provides two types of alarms:

Tolerance Alarms — The links are colored (and notifications are sent) depending on whether the most recent series of data points are above the threshold (red) or below the threshold (green). The Threshold value for each specific test and variable can be set on the alarm template. The number of consecutive data points above the threshold to trigger the alarm can be set at Alarms > Chart Strikes. For the alarm to clear only takes a single point below the threshold.

Control Alarms — The links are colored (and notifications are sent) depending on whether the most recent series of data points reflect a steady state or a change in the variable values for a test. Green means steady (as the link or cell has been performing in the past); red means an abrupt increase; blue means an abrupt decrease. These are self adjusting thresholds based on a statistical technique. Note that if the variable remains near or outside the thresholds value the limit will adjust to reflect this changed norm and then the alarm will clear even though there is no change in the value of the metric, but now the steady state is now the higher value. The number of consecutive data points outside the established thresholds to trigger the alarm can be set at Alarms > Chart Strikes. For the alarm to clear or for the link to be considered returned to the steady state only takes a single point.

Alarm Templates

In most communications systems, there are hundreds or thousands of links. To assign alarm conditions and actions to each link individually is not practical. The Converged Network Analyzer uses a template system to define common alarm conditions and actions, and then associate links or zones with the appropriate template.


65

Alarm Templates

An Alarm Template specifies the following parameters and actions for all links and all zones assigned to it:

Notification destinations:

• Selection of any or all four SNMP trap locations for communication with external alarm monitoring systems.

• Selection of any or all four Email notification destinations for communication with specific personnel.

• Selection of any or all four Syslog notification destinations for communication with systems that require this protocol.

The same notification destinations are used for all alarms defined in a template.

Alarm parameters:

• Specify Threshold parameter for each test/variable for use in Tolerance alarm.

• Send selected notifications (and change link and cell colors) when analysis of test results causes a Control alarm.

• Send selected notifications (and change link and cell colors) when analysis of test results causes a Tolerance alarm.

• Attach CSV file of test data to Email notifications.

Alarm parameters are specified separately for each test/variable.

A single Alarm Template can have any number of links and any number of zones assigned to it. The notification destinations will be the same when any zone or link goes into alarm state. The coloring of the link for the tolerance view is governed by the threshold values set for the particular test/variable. Change of color for any alarm condition does not indicate that a notification has been sent. Notification is controlled by the three checkboxes at the bottom left of the alarm tab screen and by the notification destinations selected.


66

Alarm State

A fault condition must be consistent for some period of time to generate an alarm. The alarm process works as follows:

A good test result (below the Threshold for a Tolerance alarm or between the self adjusting limits for a Control alarm) ends the current alarm state for the specific test/variable and the links or zones associated with that alarm.

A series of out-of-bounds test values for the same test/variable is necessary to raise an alarm. The number of sequential out-of-bounds "strikes" can be set using Alarms > Chart Strikes.

There is a tradeoff between frequency of testing and responsiveness of alarming. For example, if the tests occur once a minute and chart strikes are 10 then it would take 10 minutes before an alarm could be raised. If the alarm is needed within 2 minutes, then the tests would need to occur every 12 seconds (10 in 2 minutes). It is a good idea set chart strikes to be a number larger than 5 to prevent a few spurious points from setting off an alarm. Generally an alarm should indicate a persistent condition.


67

Managing Alarm Templates

Initially all links and zones are assigned to the SYSTEM DEFAULT Alarm Template.

All templates are listed in a window at the top of the Alarms tab.

A maximum of 19 user defined alarm templates are allowed.

To define a new template:

1. Click New...

2. Enter the New Template Name.

3. Click OK.


68

To delete a template:

1. Click on one of the templates listed to highlight it.

2. Click Delete...

3. Click OK.

To rename a template:

1. Click on one of the templates listed to highlight it.

2. Click Rename...

3. Enter the Rename Template To name.

4. Click OK.


69

Assigning Links and Zones to an Alarm Template

Links option button selected.


70

Zones option button selected.

1. Select a user defined Alarm Template.

2. Click a Link or Zone to assign it to the selected Alarm Template. When the link or zone is clicked its color will change to green to indicate that it now is assigned to that user defined template. If the user goes back to the SYSTEM DEFAULT template or to a different user defined template, that link or zone will change to red to indicate that it does not belong to the newly selected template.

• A second click on the link or zone will return it to the system default template if the changes have not been automatically saved.

• The template settings are automatically saved when the user chooses a different template or goes to the Tests or Zones tab. After that point go to the SYSTEM DEFAULT template and click on the link or zone to return it to the SYSTEM DEFAULT template.


71

• Only links and zones that are assigned to the SYSTEM DEFAULT template can be assigned to a user defined template. To move a link or zone from one user defined template to another, the link or zone first must be returned to the SYSTEM DEFAULT template and then assigned to the second user defined template.

Alarm Destination Settings

CNA allows twelve alarm destinations. Each Alarm Template can select which of the twelve destinations receive alarms notification. (The Checkbox for an alarm destination is enabled when the notification destination has been defined.) In the screen section below, no notification destinations have been defined. The user needs to go to Alarms > Destination Settings to define the destinations. Once a destination is defined then the checkbox is enabled and can be chosen as the notification destination for an alarm template. The selected alarm notification destinations apply to all alarms generated for the template.

The actual destinations can be set or seen by selecting Alarms > Destination Settings. The destinations are displayed in a three tab layout with four destination forms on each tab.


72

Clicking the Test button on any tab will cause test messages to be sent to all destinations on that tab that have been filled in.


73

Troubleshooting Email Notifications

Email notifications may fail for a number of reasons. If email notification is not received on clicking Test:

Make sure the information is filled into the form correctly:

• The IP Address and Port point to an SMTP mail server.

• The Sender Host field contains only the domain name.

• The Sender field contains only the user name.

• The recipient email address is valid

When the email goes to a user outside the domains served by the SMTP mail server, make sure that the SMTP server and forwards mail to the other domain. (Some servers may be configured not to forward mail.)

For example:

• The email server used is smtpserver.domain1.com

• The email is sent to [email protected]

Make sure that smtpserver.domain1.com can forward email to domain2.com.

Authentication is not supported in Release 2.2. If authentication is required, the email will not be accepted by the SMTP server.

Some email servers may do some form of confirmation (such as a reverse DNS lookup) to make sure that the sender's domain is valid. Make sure that Sending Host is a valid domain name.

The Network Administrator for your email server should be able to help you with the above.


74

Template Tests

Each alarm template provides the ability of notifying selected destinations of the alarm state for each variable. Some tests have multiple variables, and alarms can be defined on each.

The available combinations are:

Test Variables (Alarmable)

RTP Delay Jitter Loss Inter Arrival Time

Ping RTT Loss Inter Arrival Time

TCP Connect Delay Cerror Inter Arrival Time

Traceroute Hop Rtt Inter Arrival Time

Inter Arrival Time indicates the time between successive tests. See Stale Data (Link or Cell Down) Alarms below for additional information.

The Alarm Settings area allows setting the Threshold for the Tolerance test. The threshold can be set independently for each variable. Use the spinner buttons to cycle through Test and Variable.

The notification checkboxes can be set independently for each variable. Use the checkboxes to specify whether an alarm notification should be sent based on Tolerance, or Control, or both, and to indicate that a spreadsheet file of data (CSV) should be attached to email notifications.

Note:

Selecting Notify on Tolerance Alarms and/or Notify on Control Alarms will cause link and/or cell colors to indicate alarm state even when no alarm notification destinations have been selected.


75

Other Test Parameters

Other test parameters can be set and viewed through the Tests menu. See Test Setup for more information.

Stale Data (Link or Cell Down) Alarms

A communication failure anywhere in the network is of immediate concern to Network Managers. The distributed testing of the Converged Network Analyzer ensures that all links and end-to-end paths (cells) are tested regularly. The failure to receive test results in a timely manner can indicate that a link has failed or that a group of endpoints has become isolated (path has failed).

When a link goes down, the inter-arrival time of test results on that link increases. Tests involving the failed link are lost. The measurement of the time between receipt of test results allows fixed and adaptive alarm notifications:

Fixed Rule — The Notify on Tolerance checkbox is checked and the Notify on Control checkbox is not checked

The link or cell will remain green as long as the Inter Arrival Time is below the tolerance Threshold configured by the user. If the Inter Arrival Time exceeds the threshold the link will turn yellow (stale) and selected alarm notifications will be sent. Note that the link or cell turns yellow on all displays, regardless of test or variable.

The link or cell turns green again as soon as a new test result is received for the link or cell.

Adaptive Rule — The Notify on Control checkbox is checked and the Notify on Tolerance checkbox is not checked

There must be at least 5 test results for a link or cell before an adaptive threshold can be determined.

The link or cell will turn yellow (and cause selected alarm notifications to be sent) when the Inter Arrival Time is greater than the number of Chart Strikes times the 75th percentile value of previously accumulated Inter Arrival Times. Chart Strikes is configured using Alarms->Chart Strikes. Note that the link or cell turns yellow on all displays, regardless of test or variable.

The link or cell turns green again as soon as a new test result is received for the link or cell.

Adaptive Rule with Fixed Rule — Both the Notify on Control checkbox and the Notify on Tolerance checkbox are checked

Has the effect of using the lesser of the adaptive threshold and the fixed threshold.


76

No Alarms — Both checkboxes are unchecked. The link or cell never turns stale, and an alarm can never be sent.

The fixed rule is used when the Network Administrator has a reasonably good idea how the network uses its links, and can estimate an expected Inter Arrival Time based on configured test Frequency and the zone hierarchy.

The adaptive rule is used to let the system learn on its own what to expect for each link and cell.

The safest option is to use the adaptive with fixed rules, as this allows the user to set a reasonable tolerance threshold that can override a possibly large adaptive one.

Finding the Alarm Template for a Link or Zone

Before you can view the alarm setup for a specific link or zone, you have to find the Alarm Template to which the link or zone is assigned.

You can determine the Alarm Template associated with a link or cell by holding the mouse over the link or cell and looking in the information window. You can then select the Alarm Template on the Alarms tab.


77

Starting from the Alarms tab, it's more complicated:

Alarms tab Links option button selected.


78

Alarms tab Zones option button selected.

• Find the link or cell you are interested in on the Link Topology Map or the zone in the Zones tree. To find the template to which a link or zone is assigned:

• By default, all links and zones are assigned to the SYSTEM DEFAULT template until they are assigned to a user-defined template.

• If the link or zone is green, the link or zone is assigned to the currently selected (highlighted) template, including the SYSTEM DEFAULT template.

• If the link or zone is black, a user-defined template is selected and the link or zone is assigned to the SYSTEM DEFAULT template.

• If the link or zone is red, it is assigned to a different template. Click each defined template until the link or zone you are interested in turns green.

• Other green links and zones are in the same Alarm Template. Black links or zones are unassigned, and red links or zones are assigned to a different Alarm Template.

• The notification destinations selected for the Alarm Template are checked and apply to all alarms resulting from the template.


79

• Use the Test and Variable spinner buttons to see or set the threshold limit for each test/variable.

• The checkboxes at the bottom indicate whether notification actions are based on Tolerance alarm (specified threshold), Control alarm (stability), and whether to include a CSV (spreadsheet) file of test results with Email notifications. The checkboxes can be set specifically for each Test and Variable.

Troubleshooting Alarms

If you have trouble getting alarms to operate properly, follow this checklist:

On the Alarms menu, make sure that Alarms > Disable Tolerance Alarms is unchecked.

On the Alarms menu, make sure that Alarms > Disable Control Alarms is unchecked.

On the Alarms menu, (Alarms > Destination Settings) make sure that some alarms destinations are configured.

On the Alarm Template, make sure that the Notify on Control and/or Notify on Tolerance checkbox is checked for the variable in question.

On the Alarm Template, make sure that some alarms destinations are selected. When no alarm destinations are selected, the only notification will be a color change of the link or cell.


80

Using the End-to-End Matrix

The RTP, Ping, and TCP Connect tests lend themselves to viewing end-to-end results using the zone hierarchy. A matrix of colored cells shows the measured quality of communications between zones at the same level on a specific branch of the zone hierarchy.

The cell at the intersection of each row and column contains the one-way test results from the subzone listed on the left to the subzone listed at the top. (Match the number at the top to the number at the left to identify the destination subzone.)

Each selection from the Analysis View drop-down list in the button bar displays the same basic test/variable result data with different color schemes. You can adjust the Analysis View and Thresholds (for Minimum, Median, and Maximum views) in the button bar to help identify near alarm conditions.


81

For the tolerance and control view there is no access to the thresholds on the button bar. For Minimum, Median, and Maximum views, adjusting the upper and lower thresholds enables the user to view the values across the topology or in the zone hierarchy. This helps the user find links or cells that have similar values for a given matrix or to quickly look for where loss is occurring across the network.

Holding the mouse over any cell shows the associated values in the info window.

Moving Through the Zone Hierarchy

To move downward within the zone hierarchy, you can click any underlined subzone name at the left end of the row. To move up one or more zone levels, click any level shown in the Path.


82

Viewing Cell Data (Tests Tab, Interactive Data Display)

To view cell (end-to-end) test results as an interactive display (scatter plot over time), click on a cell.

The data displayed corresponds to the specific test/variable selected in the Tests tree. Changing the test/variable selection will not change the display. You must select the test/variable before clicking the cell to display the results of that test/variable.

The Chart name indicates the plotted test/variable and (in parentheses) indicates the scale for the vertical axis.

The Cell identifies the subzones (at the same level) between which the test results apply.

The horizontal axis is always time, and runs from the time of the oldest test on the left to "now (local time-of-day)" on the right. The label at each tick-mark indicates the time of the tests. Each cell retains a maximum of 150 data points for each test/variable.

The data points are colored as follows:

When Control is selected on the Analysis View drop-down list, color indicates points that are outside the automatically adjusted thresholds. Select Alarms > Color Legend to pop-up the definition.


83

When Tolerance is selected on the Analysis View drop-down list, color indicates each data point's relation to the threshold specified for the test/variable in the alarm template. Select Alarms > Color Legend to pop-up the definition.

When Minimum, Median, or Maximum is selected on the Analysis View drop-down list, the upper and lower thresholds set in the button bar control the coloring of the cells. Black indicates no data collected for that cell and yellow indicates stale data (the tests are no longer being conducted for that cell).

The Included Endpoint Pairs are all the endpoint pairs through which tests have been placed that resulted in data moving between the subzones indicated by the selected cell. You may uncheck endpoint pairs to exclude their data from the display.

For additional information on using the dynamic display, see Interpreting Test Results (Interactive Data Display).


84

Using the Link Topology Map (Full Access)

Note:

The Converged Network Analyzer uses background tests to automatically map the nodes. The Link Topology Map is built over time. Initially, it will be blank or show only parts of the network. As the background tests collect mapping data, the Link Topology Map is filled in. After the Link Topology Map is filled in, use the button bar controls to make it more readable. See Button Bar Controls below for additional information.

The Link Topology Map appears in the display pane of the main window when:

The Tests tab is selected and the Link Topology Map button ( ) is

selected rather than the End-to-End Matrix button ( ).


85

The Alarms tab is selected and the Links option button is selected rather than the Zones option button..

The meanings of the colors are entirely different. The Link Topology Map shows different information for the Tests and Alarms tabs:

When the Tests tab is selected, the Link Topology Map shows link status based on the test/variable selected in the Tests Tree, and on the Analysis View settings in the button bar.

When the Alarms tab is selected, the Link Topology Map shows link association with the selected Alarm Template. Green links are assigned to the currently selected Alarm Template (including the system default template). Red links are assigned to a different user-defined template. Black links are assigned to the system default template (they show as green when the system default template is selected).

Other than the color coding, most map editing functions are the same.


86

Symbols and Labels

The topology map shows each switch, router, Chatterbox and Phone Subnet as a node and the links between them as lines.

Chatterbox Test Plugs are shown as triangles ( ).

Routers are shown as circles ( ).

Routing switches are shown as squares ( ).

Security Gateway Test Plugs are shown as rectangles ( ).

Phone subnets are shown as .

Links are shown as lines connecting nodes

You may indicate your preferred labeling for nodes using the View menu. This setting is not saved after the current session.

The No Labels and Zones selections show only defined Test Plug labels. This results in fewer, more readable labels than the IP Addresses or Device Names options (which also label nodes). For the No labels view only the names associated with Test Plugs are shown. For the Zones view, the zone that the Test Plug is assigned to is shown.


87

Assigning Node Names

To change the name assigned to a node, click on the node:

Any node name already assigned to the node displays in the Name box. You can change the name for this specific map by inserting a different name. You must select File > Save (system) or File > Save (local) to save the profile. To return to a different profile, select File > Load (system) or File > Load (local).

Click Get FQDN to display the fully qualified domain name if it is available and not already displayed. This is a convenient way of assigning names to the routers.

Click Get SNMP to display the SNMP parameters if they are available and not already displayed.

Click Flash Node to briefly flash the node associated with this dialog box. (You may need to move the dialog box to see the node on the topology map.)


88

Assigning Endpoint Names

To change the name assigned to an endpoint, click on the endpoint:

Any name already assigned to the endpoint displays in the Name box. You can change the name for this specific map by inserting a different name. You must select File > Save (system) or File > Save (local) to save the profile. To return to a different profile, select File > Load (system) or File > Load (local).

Device Type may be IP Phone, Security Gateway, Media Gateway, or Chatterbox.

Click Get FQDN to display the fully qualified domain name if it is available and not already displayed.

Click Flash Node to briefly flash the node associated with this dialog box. (You may need to move the dialog box to see the node on the topology map.)


89

Links

Links are shown as lines connecting nodes.

One-way links are shown as a solid line joining the origin and destination.

Two-way links are treated as two half (one-way) links. A dot at the center of the line divides the line into two segments, each of which points away from the center and toward the nodes on opposite ends. The half-links are analyzed and alarmed separately. (Note that when the lines are colored black one way versus two way links are indistinguishable since one cannot see the black dot separating them.)

On the Tests Tab, the color of the line indicates the link status:

• The ends of a two-way link may be different colors

• Color indicates the performance of the half-link for the test/variable and the analytic view selected.

• Select View > Color Legend for a pop-up showing the current color legend.

On the Alarms Tab, the color of the line indicates the link association with an Alarm Template:

• The ends of a two-way link may be different colors

• Color indicates whether the link is assigned to the selected template. Green links are assigned to the currently selected template (including the system default template). Red links are assigned to a different user-defined template. Links assigned to the system default template display as black when a different template is selected.


90

Button Bar Controls

Font Increase/Decrease: Increases or decreases the label font size for all nodes on the Link Topology Map and for all row/column labels on the End-to-End Matrix. This setting applies only during current session. It is not saved.

Line Thickness Increase/Decrease: Increases or decreases the line thickness for all links on the Link Topology Map. This setting applies only during current session. It is not saved.

Map Rotate Left/Right: The Link Topological Map (or selected region) is rotated a few degrees left (counterclockwise) or right (clockwise) for each click. Holding either button down will result in continuous rotation in the selected direction. Rotate Left and Rotate Right apply to the whole Link Topological Map display if no selection marquee rectangle is present, or only to the selected area when a marquee rectangle is present. The position of nodes is saved only if the user selects File > Save (System) or File > Save (local).

Map Center/Map Expand/Map Arrange: Map Arrange redraws the entire topological map based on a statistical algorithm to lay out the nodes in a more readable fashion. This may provide a better starting point for positioning the nodes in a logical fashion for a local map. (Reload the system or local positions if you don't like the result of Map Arrange.) Map Center and Map Expand apply to the whole Link Topological Map display if no selection marquee is present, or only to the selected area when a marquee is present. The position of nodes is saved only if the user selects File > Save (System) or File > Save (local).


91

Saving the Link Topology Map

The administrator defines a standard layout for the Link Topological Map for all users. In addition, each user may define one personal layout of the Link Topology Map.

To load the standard topological map, select File > Load (system). Note that by default the local topological map is loaded.

To save a topological map, alter the displayed map by dragging nodes or by using the rotation, expand, and center functions. Then save the map by selecting File > Save (system) or File > Save (local) . Only node positions and node names are saved.

To reload the map, select File > Load (system) or File > Load (local).

Viewing Link Data (Alarms Tab)

Alarm notification destinations for links are available only on the Alarms tab. Use the Tests tab for all other information.


92

Viewing Link Data (Tests Tab, Interactive Data Display)

Link test results are available only on the Tests tab. They are not available on the Alarms tab.

To view link test results as a interactive display (scatter plot over time), click on a half-link:

The data displayed corresponds to the specific test/variable selected in the Tests tree. Changing the test/variable selection will not change the display. You must select the test/variable before clicking the half-link to display the results of that test/variable.

The Chart name indicates the plotted test/variable and (in parentheses) indicates the scale for the vertical axis.

The Link identifies the end points of the link (the node on each end).




93


When Tolerance is selected on the Analysis View drop-down list, color indicates each data point's relation to the thresholds specified for the test/variable in the Alarm Template to which the link being viewed is assigned. Select Alarms > Color Legend to pop-up the definition.

When Minimum, Median, or Maximum is selected on the Analysis View drop-down list, all data is plotted in black.

The Included Endpoint Pairs are all the endpoint pairs through which tests have been placed that resulted in data transiting the selected link. You may uncheck endpoint pairs to exclude their data from the display.

For additional information on using the dynamic display, see Interpreting Test Results (Interactive Data Display).


94

Merging and Unmerging Nodes

The Converged Network Analyzer automatically maps the nodes and links between the endpoints of some tests. The Converged Network Analyzer automatically identifies which IP addresses belong to a single network node. Sometimes, this automatic mapping may fail, and a node with multiple IP addresses may show up as more than one node.

If you notice that a single node with multiple IP addresses has been mapped as multiple nodes, you can select the separate nodes by dragging the mouse diagonally to include them in a marquee rectangle. (Drag one of the nodes closer if you cannot get a rectangle that doesn't include other nodes.) Then use Topology > Merge Selected Nodes to merge the selected nodes together into one node with multiple IP addresses.

Use Topology > Unmerge Selected Nodes to reverse the effect of merging nodes.

Note:

Topology > Unmerge Selected Nodes may not be useful to separate merged nodes that were automatically merged by the algorithm. The automatic merging algorithm may merge them again if it determines that they are the same device.


95

Manual Paths

The Converged Network Analyzer automatically maps the nodes and links between the endpoints of some tests. Sometimes, it is desirable to specify the exact path that should be used between two endpoints. Any number of manual paths can be entered into a spreadsheet or text file using the comma separated variable (.CSV) format.

Specifying manual paths is necessary when networking functions such as ICMP are disabled by network administrators for security reasons. This prevents automatic determination of paths. If the topology of the network is already known, it may be entered using manual paths.

To upload a series of manual paths, use Topology > Upload Manual Paths Use the Open dialog box to specify the file containing the manual paths.

To save a series of manual paths, use Topology > Save Manual Paths Use the Save dialog box to specify the name and location for the file containing the manual paths.

CSV Format for Manual Paths

In the CSV format, a series of IP addresses on each line specifies a path. The first IP address is always the beginning endpoint (Test Plug) IP address. Each additional entry on the same line contains the IP address of subsequent nodes on the message path, ending with the IP address of the other endpoint (Test Plug). The IP addresses must be separated by commas, and there must not be a comma after the last IP address.

Entering data in notepad will generate this file, but you must remember to specify ".csv" as the file type extension. (Notepad defaults to ".txt".)

Entering data in a spreadsheet and selecting to save in CSV format will generate this file with the proper extension.

Generating this file by saving path information will create a CSV file that can be opened in Notepad or Excel.


96

Interpreting Test Results (Interactive Data Display)

Test results are shown by color coding the links in the Link Topology Map or the cells in the End-to-End Matrix.

Each link on the Link Topology Map is associated with test results for all tests that transit that link.

Each cell in the End-to-End Matrix is associated with test results for all tests that go between the row subzone and the column subzone.

To view the test results, you must first select the test/variable of interest from the Tests tree and the analysis view from the analysis view drop-down list in the button bar.

Click on a link or cell to pop-up the Interactive Data Display.

Use the Link Topology Map to view test results for individual links.


97

Use the End-to-End Matrix to view test results for communication between zones.

The interactive data display shows a time series scatter plot of the currently selected test/variable.

The Chart name indicates the test/variable and indicates the scale for the vertical axis.

The Cell identifies the subzones (at the same level) between which the test results apply.

The Link identifies the end points of the link (the node on each end).





98

When Tolerance is selected on the Analysis View drop-down list, color indicates each data point's relation to the thresholds specified for the test/variable in the Alarm Template to which the link being viewed is assigned. Select Alarms > Color Legend to pop-up the definition.

When Minimum, Median, or Maximum is selected on the Analysis View drop-down list, all data is plotted in black.

The Included Endpoint Pairs are:

For links, the Included Endpoint Pairs are all the endpoint pairs through which tests have been placed that resulted in data transiting the selected link. You may uncheck endpoint pairs to exclude their data from the display.

For cells, the Included Endpoint Pairs are all the endpoint pairs through which tests have been placed that resulted in data moving between the subzones indicated by the selected cell. You may uncheck endpoint pairs to exclude their data from the display.


99

Alarms: Control and Tolerance Views

The control and tolerance views are linked to alarm definitions. In either case, red or blue indicates that an alarm condition exists on the link or somewhere between the zones represented by the cell. but that does not mean that any particular link actually sent a trap or other notification about the condition. Whether a notification is sent is governed by the settings chosen by the CNA Network Administrator when defining the Alarm Template in the Alarms tab

The alarm state is controlled by assigning each link or zone to an Alarm Template and configuring group alarm parameters for all assigned links or zones in the template. Alarm parameters include notification addresses, thresholds for each test/variable combination, and checkboxes for control or tolerance reporting.

Sometimes the CNA Network Administrator does not provide alarm notification on every template. If there are no alarm notifications, alarm indications will still show up in the colors displayed on the Tests tab.

There are two methods by which alarms can be generated by the system:

Control charts compare current test results for a link (or current end-to-end test results between zones) to recent past behavior. Control charts measure stability. An alarm occurs when there have been abrupt changes from the previous norm. The threshold limits of control charts are adaptive. If a particular link or cell has a long delay as its normal behavior, it will be colored green unless there is an abrupt increase or decrease in the delay. Then it will be colored red or blue correspondingly.

Tolerance charts compare current test results for a link (or current end-to-end test results between zones) to a fixed threshold. The link or cell will be colored green if the test results are below the threshold or red if the test results are above the threshold. The user can mouse over the link and the threshold value set for that test/variable in the alarm tab will be shown in the info window.

In both the control and tolerance charts a single point out of bounds will not trigger an alarm. There must be a number of consecutive points above the upper limit or below the lower limit to trigger the condition. These are called strikes and the default value is 10 strikes to generate an alarm.

You can view or set the current alarm strikes parameter by selecting Alarms > Chart Strikes.

When there is no data to for a link or cell, the link or cell is colored dark grey. When the data is stale, the link or cell is colored yellow. (See Stale Data.)

When the user hovers over a link or cell, a summary displays in the info window.


100

Link Topology Map color coded for the RTP delay test, in the Control view.


101

End-to-End Matrix color coded for the RTP delay test, in the Control view.

For all settings of the Analysis View, you may display the color legend by selecting View > Color Legend.

Clicking the left mouse button on a link or cell displays a time scatter plot of the test results associated with the link or cell.

Minimum, Median and Maximum Views

By choosing Minimum, Median, or Maximum in the analysis view drop-down on the button bar, you can set your own viewing thresholds.

The minimum, median or maximum value in the stored test results for the selected test/variable for each link or cell is compared to the values set in Lower Threshold (green) and Upper Threshold (red) on the button bar.

These thresholds have nothing to do with alarm thresholds. They are just for viewing the raw data values.


102

Each link or cell is colored as follows:

Red if the data point is above the upper threshold.

Red to pink to white as the data point compares near the upper and lower thresholds.

Green if the data point is below the lower threshold.

Note that on the Link Topology Map some links are bidirectional as indicated by a black dot in the middle of the link, and thus can be colored differently in each direction. The coloring for the half of the link between the dot and the destination end shows the data for packets traveling in the direction of the destination.


103

Stale Data

A Tolerance or Control alarm (or both) based on Inter Arrival Time determines when a link or cell turns yellow and notifications are sent. If no alarm notification is specified for Inter Arrival Time, the link or cell will not turn yellow. The yellow stale data color overrides all other test/variable colors.

A Tolerance or Control alarm (or both) based on Inter Arrival Time generally indicates that a Test Plug has become inoperative; or for some other reason, test data is not flowing across a link or between two zones. (This situation also occurs temporarily if the CNA Network Administrator changes the frequency of testing.)

The user can left click on a yellow link or cell to see the time scatter plot of the data associated with that link or cell. In the example below, data stopped flowing on this link about 30-40 minutes ago. The horizontal axis plots the time of day with the newest results entering from the right. The points move to the left until 150 data points are displayed, at which time the oldest data points are discarded first.


104

Flash Link/Cell Button

The Flash Link or Flash Cell button will force the half link or cell associated with the data to flash.

Mouse Actions

Use the mouse to get additional information from the Link Topology Map and the End-to-End Matrix:

Holding the mouse over a link or cell: Info window displays most recently collected data for the selected test/variable for that link or cell.

Left click on a link or cell: Pop-up displays Interactive Data Display showing time scatter plots of test results for the selected test/variable for the clicked link or cell.

For the Link Topology Map only:

Holding the mouse over a node: Info window displays the name of the node specified by the current system or local map and all of the IP address associated with the node.

Left drag on a node moves the node to a new position.

Diagonal drag will form a marquee rectangle surrounding one or more nodes. Place the cursor inside the marquee rectangle to move all the nodes included in the marquee rectangle at the same time. When the marquee rectangle is present the Rotate, Center, and Expand buttons operate within the marquee rather than on the whole map.


105

Interacting With the Data Display

Clicking the left mouse button on a link or cell opens a pop-up window containing a time scatter plot for the test/variable selected in the Tests tree.

The points colored in pink or red are those that were determined to be above the control or tolerance threshold. As consecutive test results occurred, the strike count was increasing to the value at which it would alarm. This condition is depicted in the scatter plot by the fact that the pink coloring of the points intensifies to red. The points that are red correspond to the strike count above its set value, and the link turns red on the topology map, or the cell turns red on the End-to-End Matrix. If alarm notification was configured for that link or cell, the alarm notice would be sent. (Not all alarm setups include notification.) The scatter plot above shows that the jitter for this link began increasing from about 40 to about 60 milliseconds around 11:05.

The color is permanently associated with each dot. When the alarm condition clears you could see evidence of more than one alarm time period on the same scatter plot.


106

Check boxes show the pairs of endpoints involved in all the tests that traversed the link or were used in End-to-End communication between the zones. You can use these check boxes to subset the plotted points to help focus on where in the network the problem occurred.

Zooming In on Data

To get a closer look at any region of the scatter plot, you can zoom in by drawing a rectangle that includes the area of interest.

Drag the mouse diagonally to define a selection marquee rectangle.

• For each point inside the selection marquee, the associated endpoint pair is selected.

• The chart re-displays showing only the data from the endpoints selected.

• The vertical axis is resized and labeled to show a range bounded by the top and bottom of the selection marquee.

• The horizontal axis is resized and labeled to show a range bounded by the left and right sides of the selection marquee.

• Points that do not fall in the vertical range of the box are indicated as red arrows along the bottom and top of the new chart.

The check boxes will automatically be checked or unchecked to reflect which pairs of endpoints were involved in the tests shown on the subset plot.

One useful question is whether a subset of the pairs might be the only ones participating in the alarm condition. By boxing the red points and looking at which pairs remain checked (the check boxes show which pairs are involved in the test represented by the points on the current scatter plot) the user might see that only some of the Test Plugs were involved in the above threshold condition.

The user can also select a subset of the points shown on the plot by checking or unchecking the pairs of Test Plugs of interest. This action will add or remove data points from the current chart, but will not alter the axis labeling nor re-plot the other data points.

The user can also move the mouse over a plotted point and the endpoint pairs associated with that point, the time of the test, and the value of the selected variable are shown at the bottom of the scatter plot.

The Show All Datapoints button causes the chart to show all the data and check all endpoint pairs. You must click Show All Datapoints before you can refresh data if any endpoint pairs have been hidden.


107

Banding

You may notice distinct bands in some scatter plots. You can hold the mouse over individual points to see the endpoint names for that data point, you can manipulate the check boxes, or you can box the band and then see what check boxes remain checked when the selected subset of data points is re-plotted.

Which Link or Cell?

Sometimes after clicking a link or cell and looking at the scatter plots you need to be reminded of which link or cell this data is associated with. Clicking the Flash Link or Flash Cell button flashes the link on the Link Topology Map or the cell in the End-to-End Matrix whose data is shown in the scatter plot.

Refresh

Clicking the Refresh button will redraw the scatter plot with the newest available data. (If you have boxed the data and zoomed in, the Refresh button is disabled. To refresh from a subset plot, click Show All Datapoints and then Refresh.)

Show All Datapoints

Clicking Show All Datapoints redisplays any hidden data points. The scatter plot redraws all data points with the newest available data.


108

Other Administrative Tasks

File > Load (system)

The CNA Network Administrator defines the node positions and names for common Link Topological Maps. Loading a system map gives all CNA Network Managers the same starting picture so that they can discuss network problems using common language.

File > Load (local)

Each user can save local versions of the Link Topological Map. Loading a local map usually makes it easier to work with a specific section of the network as an enlarged part of the Link Topological Map.

note:

The local node positions and come up when the CNA Client is first opened. If no local positions are specified, the node positions will be jumbled until the user loads the system Link Topological Map.

File > Save (system)

Full access users can save system-wide versions of the Link Topological Map. After moving and renaming nodes, the user must save the system map.

File > Save (local)

Each user can save local versions of the Link Topological Map. After moving and renaming nodes, the user must save the local map. Using a local map usually makes it easier to work with a specific section of the network as an enlarged part of the Link Topological Map. When both the system map and a local map exist, CNA Client starts with the local map.


109

File > Find a Node

To find a node:

3. Select File > Find a Node

4. Fill in the node IP address.

5. Click Flash Node. The node will flash briefly.

Edit > Change Password

To change your password, select Edit > Change Password.


be 8 to 16 characters in length

Include at least one character from each of the following three groups:

• letters

• digits

• specials `-=\[];',./~!@#$%^&*()_+|{}:"?


110

View > [label options]

No Labels - labels only endpoints by the name specified in the current system or local map. If no name has been assigned then no identification is shown.

IP Addresses - labels all nodes (including endpoints) by IP addresses.

Device Names - labels all nodes (including endpoints) by the device name specified in the most recently loaded system or local map.

Zones - labels only endpoints by their zones.

View > Color Legend

View > Color Legend displays a pop-up showing the color legend for the currently displayed data. (One sample is shown below.)

(Other pop-ups similar.)

View > Flash Tests

When checked, each link flashes briefly whenever a test transits the link. This generates a fair amount of network traffic and should be used sparingly. It is most useful for demos or in a Network Operations Center display screen, but it is not useful for any kind of analysis since the flash is quite fast.


111

Alarms > Heartbeat Strikes

Opens a message box showing how many times in a row a Chatterbox may miss contact with other Chatterboxes before it will be assumed out-of-communication. The load for an out-of-communication Chatterbox is distributed to the remaining Chatterboxes (up to system capacity).

When a Chatterbox goes out of service, it turns red in the list of active Chatterboxes in the tree on the Tests tab.

Alarms >Chart Strikes

Opens a message box showing how many times in a row a data point must be outside limits before it will cause an alarm notification.

Refreshing Data

CNA pushes any changes to the window being viewed by each CNA user when a change occurs such as a link color change.

CNA will also refresh the data for the display any time the user switches from one view to another.

The Refresh button forces CNA to send the latest values for the particular view that the user is inspecting. Using this button insures that the colors have all been updated. It is particularly useful to refresh the screen any time the user wants to be sure that the data are as up to date as possible.

CNA automatically requests a refresh periodically from the Chatterboxes.


112

Help

Use the Help menu to obtain online and printed user manuals and for information about the Converged Network Analyzer.

Enable and Disable Alarms

Tolerance alarms and Control alarms can be enabled or disabled as a group using the Alarms menu. The menu entries change to indicate the operation that is possible (Enable or Disable). This setting overrides any notification settings that were set on any of the alarm templates. It provides a way to turn Tolerance and Control alarms on or off on a system-wide basis.

113

Index

A Adaptive Rule..................................... 63 Add Chatterboxes .............................. 13 Add Users .......................................... 36 Add Zones.......................................... 51 Add Zones subtab.............................. 22 Administering

Chatterbox ........................................ 8 Users .............................................. 36

Administering ........................... 8, 36, 39 Alarm Configuration ........................... 22 Alarm Destination Settings................. 63 Alarm Destinations ............................. 39 Alarm Settings.................................... 63 Alarm Setup ....................................... 63 Alarm State ........................................ 63 Alarm Template

defining ........................................... 96 Finding ............................................ 63 Managing ........................................ 63 zone ................................................ 96 Zones.............................................. 63

Alarm Template.......... 13, 22, 63, 84, 96 Alarm Types....................................... 63 Alarms

Troubleshooting .............................. 63 Alarms........................ 22, 39, 63, 84, 96 Alarms > Heartbeat Strikes .............. 108 Alarms >Chart Strikes ................ 63, 108 Alarms menu........................ 39, 63, 108 Alarms Tab................................... 22, 84 Analysis View......................... 80, 84, 96 Analysis View Drop Down.................. 22 Assign Endpoints ......................... 22, 51 Assign Endpoints subtab.................... 22

Assigning Endpoint Names..............................84 Endpoints ........................................51 Links ................................................63 Node Names ...................................84

Assigning ................................51, 63, 84 Available Endpoints list.................22, 51

B Button Bar...........................................22

C CD ......................................................19 Cell ...............................................80, 96 Cell Data

Viewing............................................80 Cell Data.............................................80 Cell Down ...........................................63 Cerror .......................................8, 55, 63 Change Password ............................108 Change Security Keys ........................39 Changing

IP Address.......................................19 Changing ............................................19 Chart.......................................80, 84, 96 Chart Strikes

number ............................................63 Chart Strikes...........................22, 63, 96 Chatter Login dialog ...........................16 Chatterbox IP Address

Determining .....................................39 Chatterbox IP Address .......................39 Chatterbox Network Configuration

dialog.........................................16, 39 Chatterbox Status...............................39 Chatterbox Test Plugs ........................49 Chatterbox Using Dynamic IP

Addressing ......................................16


114

Chatterbox Using Fixed IP Addressing........................................................ 16

Chatterboxes add.................................................. 39 Adding....................................... 14, 19 Administering .............................. 8, 39 Edit > Add ....................................... 39 Edit > Remove ................................ 39 remove............................................ 39 Resetting......................................... 39

Chatterboxes... 8, 14, 16, 19, 39, 49, 51, 55, 84, 108

Chatterboxes list ................................ 39 Chatterbox's MAC .............................. 39 CNA Client

Running .......................................... 19 CNA Client ....................... 8, 13, 19, 108 CNA Fault Tolerance............................ 8 CNAGUI ............................................. 39 CNAGUI.zip........................................ 39 Codec............................................. 8, 49 Color Legend.......................... 80, 84, 96 Common Parameters ......................... 55 Configuration File ............................... 16 Configure Alarm Templates ............... 14 Connection success/failure ................ 63 Control............................ 80, 84, 96, 108 Control Alarms ................................... 63 Control checkbox ............................... 63 Converged Network Analyzer Overview

.......................................................... 8 Covariate.............................................. 8 CSV file

include ............................................ 63 CSV file .................................. 22, 63, 95 CSV Format

Manual Paths.................................. 95 CSV Format ....................................... 95 Current Test ....................................... 22 Current Zone Name ........................... 22

D Data

Refreshing .....................................108 Data ..................................................108 Default Gateway ...........................16, 39 Define

Zone ................................................13 Define .................................................13 Define Alarm Templates .....................13 Defragmentation .................................39 Destination Settings............................63 Device Names ............................84, 108 Device Type........................................84 DHCP ..................... 8, 14, 16, 19, 39, 49 Disable Alarms .................................108 Disable Control Alarms.......................63 Disable Tolerance Alarms ..................63 DNS ................................................8, 63 Dynamic IP Address ...........................39

E Edit > Add Chatterbox ........................39 Edit > Change Password ..................108 Edit > Change Security Keys..............39 Edit > Defragment...............................39 Edit > Remove Chatterbox .................39 Edit > Show Memory Usage ...............39 Email...............................................8, 22 Email Notifications

Troubleshooting...............................63 Email Notifications ..............................63 Endpoint IP .........................................22 Endpoint Names

Assigning.........................................84 Endpoint Names .................................84 Endpoints

Assigning.........................................51 Registering ......................................49

Endpoints................................22, 49, 51 End-to-End Matrix....... 22, 55, 80, 84, 96

Index

115

F Factory Default Settings..................... 39 Failed Upgrade................................... 39 FAT .................................................... 16 FAT32 ................................................ 16 Finding

Alarm Template .............................. 63 IP .................................................... 19 Node ............................................. 108

Finding ................................. 19, 63, 108 First Time Procedures........................ 19 Fixed IP Address................................ 14 Fixed Rule.......................................... 63 Flash Cell ........................................... 96 Flash Link........................................... 96 Flash Node................................. 84, 108 Flash Tests....................................... 108 Font Increase/Decrease............... 22, 84 Frequency .................................... 55, 63 Full Access................................... 13, 36 Function Tabs .................................... 22

G Get FQDN .......................................... 84 Get SNMP.......................................... 84

H Help menu........................................ 108 Hive

Moving ............................................ 39 Hive.................................................... 39 Hop RTT................................... 8, 55, 63 Host.................................................... 55

I Included Endpoint Pairs ......... 80, 84, 96 Install Chatterboxes ........................... 14 Installing

Chatterboxes .................................. 16 CNA Client ...................................... 14

Installing....................................... 14, 16 Intended Audience ............................. 13

Inter Arrival Time ................ 8, 55, 63, 96 Interactive Data Display..........80, 84, 96 Interpreting

Test Results ....................................96 Interpreting .........................................96 IP Address

changing..........................................19 Define ..............................................49 finding..............................................19 Propagate........................................49

IP Address ..... 14, 16, 19, 39, 49, 63, 84, 108

IP Phone.............................................84

J Jitter – Unevenness..................8, 55, 63

L Labels .........................................84, 108 LAN...........................................8, 49, 51 Line Thickness Increase/Decrease....22,

84 Link Data

Viewing............................................84 Link Data ............................................84 Link Topological Map..................22, 108 Link Topological Map/End-2-End Matrix

........................................................22 Link Topology Map

Saving .............................................84 Using ...............................................84

Link Topology Map .8, 13, 22, 63, 84, 96 Links

Assigning.........................................63 Links ...................................................63 Load............................................84, 108 Login................................. 13, 19, 36, 39 Logoff..................................................39 Loss – Percentage....................8, 55, 63 Lower Threshold...........................22, 96

M MAC..............................................16, 39 Manage Users dialog..........................36


116

Managing Alarm Templates............................. 63

Managing ........................................... 63 Manual Paths ..................................... 95 Map Arrange ................................ 22, 84 Map Center .................................. 22, 84 Map Expand................................. 22, 84 Map Rotate Left/Right .................. 22, 84 Maximum.......................... 22, 80, 84, 96 Maximum TTL .................................... 55 Media Gateway ............ 8, 22, 49, 51, 84 Media Gateway Test Plugs ................ 49 Median ............................. 22, 80, 84, 96 Memory Usage................................... 39 Menubar ............................................. 22 Merge Selected Nodes....................... 94 Minimum........................... 22, 80, 84, 96 Mouse Actions.................................... 96

N Network Operations Centers...... 49, 108 New Template Name ......................... 63 No Labels ........................................... 84 Node Names

Assigning ........................................ 84 Node Names ...................................... 84 Notify .................................................. 63 Notify on Control checkbox ................ 63 Notify on Tolerance checkbox............ 63

O Open dialog........................................ 95

P Parameters Common Among All Tests

........................................................ 55 Parent Zone ....................................... 22 Password ..................................... 19, 36 Path.............................................. 22, 80 Performance Tuning........................... 39 Phone subnets ................................... 84 Ping.................................................... 80

Ping Parameters.................................55 Plot

test/variable .....................................96 Plot .....................................................96 Port .....................................................63 Processing/analyzing..........................39 PSTN ..............................................8, 49 Public Service Telephone Network.......8

Q QoS ......................................................8 Quick Start Guide ...............................14

R Real Time Protocol ...................8, 55, 63 Rebalance ..........................................39 Reference Card/Feature Introduction .22 Reformatting

USB.................................................16 Reformatting .......................................16 Refreshing

Data...............................................108 Refreshing ..................................96, 108 Register IP Phones.......................49, 51 Register Security Gateways .........49, 51 Registering

Endpoints ........................................49 Registering .........................................49 Remote IP...........................................55 Remove Chatterbox............................39 Remove Chatterbox dialog .................39 Remove Users....................................36 Remove Zones ...................................51 Remove Zones subtab .......................22 Rename Template ..............................63 Rename Zones ...................................51 Rename Zones subtab .......................22 Resetting Chatterbox..........................39 Round Trip Time.......................8, 55, 63 RTP .................. 8, 14, 22, 55, 63, 80, 96 RTP Parameters.................................55

Index

117

RTT .......................................... 8, 55, 63

S Save Configuration File...................... 16 Save dialog ........................................ 95 Save Link Topology Map.................... 84 Save Manual Paths ............................ 95 Secure Gateway Test Plugs............... 49 Secure Gateways......... 8, 22, 49, 51, 84 Serial Number .............................. 16, 39 Service

Quality............................................... 8 Service ................................................. 8 Show All Datapoints ........................... 96 Single Board Computers ...................... 8 SMTP ................................................. 63 SNMP........................... 8, 14, 22, 63, 84 Stale Data .................................... 63, 96 Static Configuration............................ 39 Static IP Address................................ 39 Status Bar .......................................... 22 Status Message ................................. 22 Subnet Mask ................................ 16, 39 Subzones ............................... 51, 55, 96 Syslog .................................... 14, 22, 63 SYSTEM DEFAULT..................... 22, 63

T TCP.................................... 8, 14, 55, 63 TCP Connect................................ 63, 80 TCP Connect Parameters .................. 55 Telecommunications Security .............. 5 Template Tests .................................. 63 Test menu .................................... 55, 63 Test Plug........................................ 8, 51 Test Results

Interpreting...................................... 96 Test Results ....................................... 96 Test Setup.......................................... 55 Test Types ......................................... 63

Test/variable Changing ...................................80, 84 plot...................................................96 select .........................................80, 84

Test/variable ............... 22, 63, 80, 84, 96 Tests............................... 39, 80, 96, 108 Tests Tab................................22, 80, 84 Tests Tree ..........................................84 Threshold Lower/Upper ......................22 Thresholds

setting..............................................63 Tolerance ........................................63

Thresholds..............................22, 63, 80 Titlebar................................................22 Tolerance.................. 22, 80, 84, 96, 108 Tolerance Alarms ...............................63 Tolerance checkbox ...........................63 Tolerance Views .................................96 Toll Fraud

Preventing .........................................5 Toll Fraud .............................................5 Topology > Unmerge Selected Nodes 94 TOS ....................................................55 Traceroute .......................... 8, 14, 55, 63 Traceroute Parameters.......................55 Transmission Control Protocol .8, 55, 63 Troubleshooting

Alarms .............................................63 Email Notifications...........................63

Troubleshooting..................................63 TTL .....................................................55

U Unary tests .........................................55 Unmerge.............................................13 Unmerge Selected Nodes ..................94 Unmerging Nodes...............................94 Upgrade Chatterbox ...........................13 Upgrade Completed ...........................39 Upgrade Software...............................39 Upload Manual Paths .........................95


118

Upper Threshold .......................... 22, 96 USB

reformatting..................................... 16 USB.................................................... 16 User ID............................................... 39 User Login IDs

Assigning ........................................ 36 User Login IDs ................................... 36 User Privileges................................... 36 Users

Administering .................................. 36 Users.................................................. 36

V Variables ............................................ 63 View > Color Legend........................ 108 View menu ......................................... 84

Viewing Cell Data..........................................80

Viewing ...............................................80 Virtual Private Network ...................8, 49 VPN ..........................................8, 49, 51 VPN Manager 3.5 ...............................49

W WAN ...............................................8, 49 Wide Area Networks.............................8

Z Zone Configuration .............................22 Zone Hierarchy .............................51, 80 Zone Management Functions.............51 Zones

Alarm Templates .......................13, 63 Define ..............................................13

Zones.............. 13, 14, 39, 51, 63, 84, 96 Zones Tab ..........................................22

cna administration guide - jim...

Documents