Agilent Technologies 622Vu Advisor User Manual
  1. Manuals
  2. Brands
  3. Agilent Technologies Manuals
  4. Measuring Instruments
  5. 622Vu Advisor
  6. User manual
Agilent Technologies 622Vu Advisor User Manual

Agilent Technologies 622Vu Advisor User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Agilent Technologies
622Vu Advisor
User's Guide

Advertisement

Table of Contents
loading

Related Manuals for Agilent Technologies 622Vu Advisor

Summary of Contents for Agilent Technologies 622Vu Advisor

  • Page 1 Agilent Technologies 622Vu Advisor User’s Guide...
  • Page 2 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Agilent Technologies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • Page 3: Table Of Contents

    Contents Chapter 1..........................9 Installation and Configuration ..................9 1.1 622Vu Undercradle Description..............10 1.2 Installing 622Vu Advisor ................11 1.3 Configuring 622Vu Advisor................20 1.4 Testing the Installation and Configuration ..........22 1.5 Troubleshooting...................23 Chapter 2...........................37 Introduction .......................37 2.1 Overview of Processing................38 2.2 Specific Capabilities..................40 2.3 How Does It Work?..................41...
  • Page 4 7.4 Creating A FilterSet That Captures Specific VCCs........127 Chapter 8.........................131 Filtering Captures ....................131 8.1 Understanding Filters.................131 8.2 Looking at Filter Definitions ..............134 8.3 Defining FilterSets..................137 8.4 Defining Filter Buffers................143 8.5 Defining Filter Entries ................147 8.6 Advanced Filtering Mode ................149 Chapter 9.........................153 Editing Transmit Sequences ..................153 9.1 Inheriting Cell Characteristics ..............155 9.2 Creating or Editing a Sequence..............157...
  • Page 5 Figures Figure 1. 622Vu Advisor’s Component Architecture ............41 Figure 2. LEDs Indicating Current Operation Mode ............61 Figure 3. Channel Indicators for a 622Vu Advisor............70 Figure 4. Logical Hierarchy of Cells, Sequences, and Scripts........156 Tables Table 1. Device Manager Menu Commands and Toolbar Buttons........57 Table 2.
  • Page 7 ⇒ Use toolbars. Technical Requirements 622Vu Advisor is designed to run on any "C" model of the Agilent Advisor. Related Materials Refer to the following manuals or online documents for more information about 622Vu Advisor: In addition, a PDF (Portable Document Format) version of this...
  • Page 8 Windows Help If you haven’t used Microsoft Windows or Windows-based appli- cations before, work through the Windows Tutorial before using 622Vu Advisor. You might also want to browse through the Help topics available from Windows. These topics explain general Windows concepts.

  • Page 9: Chapter 1

    This chapter describes the physical appearance of the 622Vu undercradle. In addition, installation and configuration instructions describe the steps you need to do prior to using the Agilent Technologies 622Vu Advisor application. To operate the 622Vu Advisor, the OC-12c/STM-4c application software must be loaded in an Agilent Advisor "C or newer"...

  • Page 10: 622Vu Undercradle Description

    Sys OK 622Vu Advisor software is running when light flashes. There is a hardware or firmware problem. Fault The 622Vu Advisor application is talking to the undercradle. Active The undercradle is receiving ATM cells on Port 1. Port 1 (Dark indicates loss of cell delineation on that port.) The undercradle is receiving ATM cells on Port 2.

  • Page 11: Installing 622Vu Advisor

    1.2 Installing 622Vu Advisor 1.2 Installing 622Vu Advisor Two different conditions can exist for installing 622Vu Advisor. When you have a new 622Vu undercradle with a new Advisor mainframe. The undercradle is already attached to the mainframe at the factory.
  • Page 12 1: Installation and Configuration 1.2 Installing 622Vu Advisor If you are Do These Installation Steps in This Order Page installing a new Step 1.- Install 622Vu Advisor Software 622Vu undercradle with an existing Agilent Advisor Step 2. - Install 622Vu Undercradle mainframe.
  • Page 13 1. Use Section 4, in the Agilent Advisor Software Installation Guide, to add the software if: 622Vu Advisor application software to the Agilent Advisor. 2. If you want to install only the 622Vu Advisor application, in the Agilent Advisor Software Installation Guide procedure: •...
  • Page 14 1: Installation and Configuration 1.2 Installing 622Vu Advisor Step 2. - Install 622Vu Undercradle To attach the 622Vu undercradle to your Agilent Advisor: 1. Turn the Advisor off and disconnect the power cord. 2. Align the undercradle with the Advisor so the connector slots match.
  • Page 15 1: Installation and Configuration 1.2 Installing 622Vu Advisor Step 4. - Ensure CardBus Controllers Are Enabled The 622Vu undercradle communicates with the Advisor via an Ethernet interface card in the PC CardBus slots. The following procedure verifies that the card slots are enabled.
  • Page 16 1.2 Installing 622Vu Advisor Step 5. - Ensure TCP/IP Stack Is Installed If you have just installed Windows and/or the Agilent 622Vu Advisor application, use the following steps to verify that the TCP/IP stack is enabled. 1. Select Start | Settings | Control Panel and then click the Network icon.
  • Page 17 The Xircom RealPort CardBus Ethernet 10/100 Network Interface Card (NIC) is supplied and supported for operation with the Agilent 622Vu Advisor. Use the following steps to install the card. 1. Turn the Advisor on and wait for the Windows desktop to display.
  • Page 18 1: Installation and Configuration 1.2 Installing 622Vu Advisor If this item is not listed, see The CardBus NIC Card Is Not Detected During Installation on page 28 in the troubleshooting section. 9. Click OK to close the Socket Status window.
  • Page 19 1: Installation and Configuration 1.2 Installing 622Vu Advisor Step 8. - Apply DC Power to the 622Vu Undercradle Connect the power supply module output to the Power connector on the Connect the undercradle. Y cord power jumper to the power supply...

  • Page 20: Configuring 622Vu Advisor

    1: Installation and Configuration 1.3 Configuring 622Vu Advisor 1.3 Configuring 622Vu Advisor Step 9. - Set IP Addresses The first time you install the Xircom CardBus Ethernet card, you must set its IP address and Subnet Mask. The 622Vu undercradle and the Advisor default...
  • Page 21 1: Installation and Configuration 1.3 Configuring 622Vu Advisor The following figure provides explanations about the screen’s contents and controls. IP Address of undercradle with Agilent Advisor IP address Default Internet which 622Vu and Subnet Mask address Advisor IP Address Advisor is currently in the Registry.

  • Page 22: Testing The Installation And Configuration

    1.4 Testing the Installation and Configuration 1.4 Testing the Installation and Configuration Use this section to verify that the 622Vu Advisor application and undercradle are correctly installed and configured. Step 10. - Test the Installation and Configuration 1. Use the Start menu to start the application; a toolbar is displayed.

  • Page 23: Troubleshooting

    • The NIC Is Not Detected During Installation • Problems With Console Useful Troubleshooting Tools Several tools are provided with the 622Vu Advisor application to help you test and configure the 622Vu Advisor. These tools include: • Ping • Configure Registry •...
  • Page 24 1: Installation and Configuration 1.5 Troubleshooting Configure Standard Modem In the 622Vu Advisor’s start menu, the Console selection runs the Hyper- Terminal application so you can view and configure the 622Vu undercradle’s parameters. Even though the connection from the Advisor to the 622Vu undercradle is a direct serial connection, the Hyper-Terminal application requires a default modem to be configured.
  • Page 25 Troubleshooting Problems Undercradle Not Detected by the 622Vu Application When you try to start the 622Vu Advisor’s Device Manager and a message displays, "Sorry - no cell cards have been detected. Please check your configuration and try again." displays, try the following steps: 1.
  • Page 26 Note: The Console application requires that a default modem is configured. See Configure Standard Modem on page 24. c. Close the 622Vu Advisor application and disconnect power from the 622Vu undercradle. d. Connect power to the 622Vu undercradle and observe Console messages.
  • Page 27 10. The section Useful Troubleshooting Tools on page 31 describes how to use Ping to see if the Advisor can find the undercradle. If you still have problems, call 1-800-698-0061 for support or contact your local Agilent Technologies Sales and Service Office.
  • Page 28 1: Installation and Configuration 1.5 Troubleshooting The CardBus NIC Card Is Not Detected During Installation undercradle communicates with the Agilent Advisor via an Ethernet 622Vu NIC card in the PC CardBus slot. If you have trouble installing the provided NIC card, you may be having a conflict between the Xircom CardBus NIC card drivers and other installed NIC card drivers.
  • Page 29 1: Installation and Configuration 1.5 Troubleshooting d. Repeat steps 9 thru 11 until all devices have been removed from the “Other devices” list. Remember, the devices listed in the Note above should not be deleted. 13. Use the Tab key to highlight the Close button and press Enter. 14.
  • Page 30 1: Installation and Configuration 1.5 Troubleshooting Problems With Console The Console application provides a remote terminal to view and edit parameters in the undercradle. If the Console application is not communicating with 622Vu the undercradle, try the following steps. 1. Use the provided cable to connect between the Console connector on the undercradle and the Serial port on the left side of the Advisor.
  • Page 31 1: Installation and Configuration 1.5 Troubleshooting Useful Troubleshooting Tools Several tools are available to troubleshoot the Advisor operation with the 622Vu undercradle. Each of these tools is described below. 622Vu Ping You can use the Ping function to test if the Advisor can reach the 622Vu undercradle.
  • Page 32 1: Installation and Configuration 1.5 Troubleshooting 3. If you make any changes that allow Ping to operate successfully, try the Advisor application again to see if it now can retrieve undercradle 622Vu information. Registry Generation and Command File Generation Tool The Config Tool application lets you view and edit the registry for addresses currently being used by the Advisor.
  • Page 33 1: Installation and Configuration 1.5 Troubleshooting 2. You can use the Console application in conjunction with the generated OC12_CMD.TXT file to configure the undercradle’s IP, Subnet Mask, 622Vu and gateway addresses. See the topic "Use of Generated File" later in this troubleshooting section. Note: In the Advisor’s Device Manager view, use the Tools | Configure 622Vu...
  • Page 34 1: Installation and Configuration 1.5 Troubleshooting 5. For example, the "show" and "set" commands are useful to view existing parameters and to edit the parameters to new values. Command Action / Default set ipaddr n.n.n.n Set the IP address of the 622Vu undercradle to n.n.n.n Default = 15.21.191.201 set mask n.n.n.n Set the subnet mask to n.n.n.n.
  • Page 35 1: Installation and Configuration 1.5 Troubleshooting 7. Use the set ipaddr command to set the 622Vu undercradle’s address. For example: set ipaddr 15.21.191.201 8. Use the set mask command to set the 622Vu undercradle subnet mask. For example: set mask 255.0.0.0 9.
  • Page 36 "Generate File" button in the Config Tools application. The Generate File button takes the information contained in the Advisor’s registry and the 622Vu Advisor application’s configuration file and generates a text file of console commands. The generated file is OC12_CMD.TXT...

  • Page 37: Chapter 2

    CAUTION: 622Vu Advisor is very powerful! It allows extensive analysis of any problem that might occur during ATM transmissions. Because of this, 622Vu Advisor lets you transmit anything; it assumes that any bad or broken data introduced into cells or packets is being introduced intentionally. (From the analysis standpoint, a corrupted cell may be what you want.) It’s important, then,...

  • Page 38: Overview Of Processing

    • In end-station mode, the 622Vu Advisor is a known, visible end station on the network, capable of transmitting ATM cells, ping messages, and QoSMeter tests, as well as monitoring and capturing traffic as it’s received.
  • Page 39 2: Introduction 2.1 Overview of Processing problem while monitoring the statistics, you can begin capturing any particular VCC(s). Scripts While in end-station mode, you can send out transmission scripts over the network. Each script comprises a predefined, specific pattern of standard ATM transmissions (i.e., transmit sequences and timed pauses).

  • Page 40: Specific Capabilities

    2: Introduction 2.2 Specific Capabilities 2.2 Specific Capabilities 622Vu lets you: • Configure analysis devices. • Monitor physical ATM ports while they send/receive traffic, allowing you to observe the characteristics of the physical interface to ATM devices. • Capture and examine traffic as it enters the analysis device. You can capture all traffic or only selected traffic, as controlled by 622Vu’s optional filtering capability.

  • Page 41: How Does It Work

    (active) at any given time. 2.4 Where To Go From Here Other chapters in this manual describe how to use 622Vu Advisor to perform specific tasks, and how to use the ping-message generation tool: For Instructions to…...
  • Page 42 2.4 Where To Go From Here For Instructions to… Chapter… Page Get started with 622Vu Advisor, including use of its menus, toolbars, user profiles, and general processing information. Instructions to configure analysis device(s). Includes specifics related to the physical interface (OC-12c/STM-4c).

  • Page 43: Chapter 3

    3: Getting Started Chapter 3 Getting Started To start 622Vu Advisor, either double-click its shortcut icon (shown to the left), or choose it from the Agilent Advisor Windows Start menu. 622Vu startup icon 622Vu Advisor opens its main toolbar: Main menu. These pulldown...
  • Page 44 Enable Toolbar Help, toggles the system toolbar’s Help feature on and off. With this feature enabled, 622Vu Advisor’s bubble Help describes each toolbar button as you point to it: All 622Vu Advisor processing requires that you have an active cell library. Any The Active Cell Library changes you make during processing are saved in the active cell library immediately.

  • Page 45: Summary Of Menu Commands

    Load User Profile Load a user profile, configuring 622Vu Advisor according to that profile’s settings. profile toolbar Exit Exit 622Vu Advisor.
  • Page 46 PDU, and computes the end-of-datagram automatically. Window Minimize All Windows — Minimize all 622Vu Advisor windows. Restore All Windows — Restore any 622Vu Advisor windows that were minimized previously. title of each open window — Make the window you choose active. Help Contents —...

  • Page 47: Connecting To The Atm Network

    3: Getting Started 3.2 Connecting to the ATM Network 3.2 Connecting to the ATM Network When you are ready to connect your 622Vu undercradle to your ATM network use the following steps: 1. Insert the 622Vu undercradle between two ATM devices by attaching ATM cables (not supplied) from the two devices to Ports 1 and 2 on the 622Vu undercradle’s right-side connector panel.

  • Page 48: Managing Cell Libraries

    Windows documentation for instructions to use this dialog box. Note: When you open a cell library, 622Vu Advisor automatically closes the old library for you. If you always work with a particular library, make sure to specify that library in...

  • Page 49: Setting Up User Profiles

    Click the toolbar’s New Library button to define a new cell library (or choose New Library from the File menu). 622Vu Advisor opens a dialog box that prompts for the name of the new library (similar to the one shown above for open-library processing). Specify the filename you want, using the format name.lib.
  • Page 50 User Profile button on the profile toolbar (or choose the corresponding command from the File menu). 622Vu Advisor opens a window you can use to modify the profile. Tab to each category of setting, in turn, making changes as necessary. When you’re through: •...
  • Page 51 Click Save As to save the changes under a new name then load the new profile. Use the standard Save dialog box to assign a name to the profile, using the format name.prf. If you omit the suffix, 622Vu Advisor assigns it correctly. Profiles can be stored anywhere, but typically reside in 622Vu Advisor’s \profile directory.
  • Page 52 Remove button to shift a script back to the unselected area. When a user profile loads, 622Vu Advisor assigns buttons across the toolbar in the same order as the scripts are listed in the lefthand box: the first script is the...
  • Page 53 3: Getting Started 3.4 Setting Up User Profiles left-most button on the profile toolbar, the second script is the next button, and so forth. The bubble Help identifies the script associated with each button: If the order of the scripts is important to you, use the Up and Down buttons to position the script names correctly in the selected list.
  • Page 54 3: Getting Started 3.4 Setting Up User Profiles...

  • Page 55: Chapter 4

    Chapter 4 Configuring Analysis Devices 622Vu Advisor’s Device Manager lets you configure analysis devices, and/or monitor the physical interface between an analysis device and the ATM device under test. This chapter describes how to configure analysis devices. Refer to Chapter 5 for instructions to monitor the physical interface.
  • Page 56 Description Device Name System name to identify each device, followed by a number (always 1). Style Type of device (always 622Vu Advisor). Serial No Analysis device’s identifying serial number. Network IP Address Internet Protocol address to identify the analysis device.

  • Page 57: Table 1. Device Manager Menu Commands And Toolbar Buttons

    Upgrade when you are through. 622Vu Advisor displays a progress bar during the upgrade, then asks you to reboot the device (necessary after an upgrade, before you can access the device): Table 1. Device Manager Menu Commands and Toolbar Buttons...
  • Page 58 Define which analysis devices are available to your List system. Refer to page 59 for details about this feature. Reboot Device — Reboot the selected device. 622Vu Advisor verifies your request before rebooting the hardware. Window Close All — Close all Device Manager windows.
  • Page 59 (The device list is maintained in config.ini.) To do this, choose Configure Server List from the Tools menu. 622Vu Advisor opens a list of devices currently configured for your use: •...
  • Page 60 4: Configuring Analysis Devices • To change a device name or IP address, first select the device from the list, then click Edit. 622Vu Advisor prompts for the changes using a window similar to the one described above for an add. •...

  • Page 61: Configuring The Operation Mode

    • An end station is known across the network, and can send and receive data. In this mode, 622Vu Advisor lets you monitor traffic coming in on either of the analysis device’s two channels; you select the channel you want.
  • Page 62 Table 2. In that table, the Configuration # (5 or 6) indicates the number used internally by 622Vu Advisor to identify the particular configuration setting. This number shows up on the window used to monitor the ATM network (described in Chapter 5).

  • Page 63: Table 2. Possible Configurations For An End Station

    Channel 1 without being monitored. Incoming traffic on Channel 2 goes into the framer chip on the analysis device and is monitored by 622Vu Advisor (and option- ally captured). The analysis device transmits traffic over Channel 2. Setting up a Monitor-Only Station...
  • Page 64 The internal Configuration # is always 10 for monitor-mode devices, and is used by 622Vu Advisor to identify this particular configuration. The configuration number shows up on the window used to monitor the ATM network (Chapter 5).

  • Page 65: Configuring An Oc-12C/Stm-4C Device

    4: Configuring Analysis Devices 4.2 Configuring an OC-12c/STM-4c Device 4.2 Configuring an OC-12c/STM-4c Device Configuration of an OC-12c/STM-4c device involves setting options specific to the physical interface. The Options tab looks like this: Indicate the type of framing the card should recognize on input, and use when sending traffic.
  • Page 66 4: Configuring Analysis Devices 4.2 Configuring an OC-12c/STM-4c Device...

  • Page 67: Chapter 5

    Click the Manage Devices button on the toolbar to initiate the Device Manager. 622Vu Advisor builds a device list, then displays the Device Manager window. Refer to page 55 for a description of this window and the information shown, and Manage Devices for a description of each menu command available during processing.
  • Page 68 5: Monitoring the ATM Network The Physical and ATM tabs let Current configuration you monitor both channels at once. for the analysis device. Active channel Heartbeat lights (correspond light. to the channel lights on the device hardware). Refresh rate (seconds). Click to reset statistics to zero (0).
  • Page 69 1) a good physical connection; and 2) that the channel is being reported by the ATM 622Vu Advisor. The indicators here correspond to the LEDs between the channel connectors on the 622Vu undercradle hardware:...

  • Page 70: Figure 3. Channel Indicators For A 622Vu Advisor

    Channel 1 is active when the top indicator is lit. Channel 2 is active when the bottom indicator is lit. Figure 3. Channel Indicators for a 622Vu Advisor One or both of the channels are highlighted, indicating the channel(s) configured...
  • Page 71 • Request Help text describing the information shown. The Update Delay controls how often 622Vu Advisor refreshes the information displayed. Specify this field as a number of seconds (in the range 1–3600), or use the spin-control arrows to increase or decrease the value shown. 622Vu Advisor will begin refreshing the information at the requested frequency.

  • Page 72: The Atm Tab

    5: Monitoring the ATM Network 5.1 The ATM Tab 5.1 The ATM Tab The ATM tab shows the following information for OC-12c/STM-4c physical- interface type. The indicators to the left count various receiver/transmitter conditions, as well as instances of a bad HEC: •...
  • Page 73 5: Monitoring the ATM Network 5.1 The ATM Tab Counter Increments by 1 when: Corrected A HEC error is corrected by the framer chip (which automatically corrects single-bit errors). Not Corrected A HEC error can’t be corrected by the framer. Total Both of the above.

  • Page 74: Monitoring An Oc-12C/Stm-4C Interface

    5: Monitoring the ATM Network 5.2 Monitoring an OC-12c/STM-4c Interface 5.2 Monitoring an OC-12c/STM-4c Interface This section describes the physical indicators for an analysis device configured to support OC-12c/STM-4c. You can obtain a different view of this same information through the Channel tab, described on page 68. The ATM tab is described on page 72.
  • Page 75 5: Monitoring the ATM Network 5.2 Monitoring an OC-12c/STM-4c Interface Alarms The first two alarms indicate major problems, and should remain clear when running with a good connection. The other alarms may light during processing, and indicate various physical events: Alarm Lights when this event occurs: Loss of Signal...
  • Page 76 5: Monitoring the ATM Network 5.2 Monitoring an OC-12c/STM-4c Interface Alarm Lights when this event occurs: Line FEBE Far End Block Error on the line, indicating a valid non-zero FEBE value (1–24) in the Z2 octet of the STS-12c/STM-4c overhead. (MS-REI = equivalent SDH term) Errors The Errors counters indicate the number of occurrences of various events,...

  • Page 77: Chapter 6

    Chapter 6 Capturing Incoming Traffic 622Vu Advisor lets you capture and monitor the traffic coming in over one or both channels of an analysis device. You can save the captured cells, either to review them later or to use them as a script (or as the basis for a script).

  • Page 78: Starting A New Capture

    Chapter 8 if you’re not familiar with filtering. As the first step to filtering a capture, you must define (i.e., establish) the filtering criteria to use. There are three ways to do this: through 622Vu Advisor’s standard filterset processor (detailed in Chapter 8), while monitoring real-time statistics (detailed in Chapter 7), or using the capture facility’s filterset wizard...

  • Page 79: Table 3. Summary Of Filtering Capabilities

    6: Capturing Incoming Traffic 6.1 Starting a New Capture single use. The approaches offer slightly different filtering capabilities, as follows: Table 3. Summary of Filtering Capabilities Can be defined in: Standard Real-Time FilterSet Filtering Capability FilterSets Stats Filters Wizard ¥ Limit the size of the buffer used (and therefore the traffic —...
  • Page 80 Using the Capture All Option After you start a new Capture All capture, 622Vu Advisor displays the captured traffic in a Browser window. As described on page 113 (see Switching...
  • Page 81 Amount of time the capture has been running. uploaded to the Advisor Number of PDUs/cells captured so far. already. The Auto Update Display button controls which of two options 622Vu Advisor uses for the display: Auto Update • With Auto Update Display OFF, 622Vu Advisor stops updating the...
  • Page 82 6: Capturing Incoming Traffic 6.1 Starting a New Capture Stopping the Capture The toolbar’s Stop Capture button is activated during a new capture, allowing you to terminate the capture at any time. After you stop the capture: Start (left) and Stop 1.

  • Page 83: Table 4. Vcc Statistics

    If the Buffers Wrap… If you’re using a capture filter that wraps its buffers (described on page 140), 622Vu Advisor won’t display any cells until the capture is stopped, at which time it displays the first traffic captured. In this case, you’ll see the message wrapped instead of a PDU/cell count in the Captured field.
  • Page 84 Criteria are ANDed between tabs, but ORed within any particular tab. Thus, when 622Vu Advisor uses the new filter, it captures all traffic having any of the VCC(s) specified, and any of the IP address(es) specified, and any of...
  • Page 85 6.1 Starting a New Capture the decodes specified, limited to the traffic coming in over the channel(s) specified. When you’re through defining the filterset, 622Vu Advisor displays the new- capture specifications for verification (including what filterset you’re using, as described on page 80): Then the new-capture session proceeds as described above under Capturing Using an Existing Filter (page 82).
  • Page 86 Click OK when you’re through, to add the VCC to the list. • To change a VCC, select the VCC in the list and click Edit. 622Vu Advisor prompts for the changes using a dialog similar to the one described above for an add.
  • Page 87 • To change an address (or pair of addresses), first select the address(es) from the list, then click Edit. 622Vu Advisor prompts for the changes using a window similar to the one described above for an add. •...
  • Page 88 6: Capturing Incoming Traffic 6.1 Starting a New Capture Using the Other Tab Use the Other tab to limit the capture to only those cells/PDUs coming into the analysis device on a particular channel. Select Channel (Ch) 1 and/or Channel (Ch) 2, then click OK to save the settings.

  • Page 89: Opening A Capture File

    6.2 Opening a Capture File 6.2 Opening a Capture File When you open an existing capture file, 622Vu Advisor uses the standard file- open dialog box to prompt for the name of the (.cap) file you want to see. Open Captures can be stored anywhere, but by default reside in 622Vu Advisor’s...

  • Page 90: Viewing Captured Traffic

    6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic 6.3 Viewing Captured Traffic This section describes the tools available for analyzing the captured data, first presenting a description of the basic display and all menu commands: • Description of the Basic Display (page 90) describes the basic data displayed in the Capture File Browser window.
  • Page 91 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Depending on whether you’re in PDU Summary Mode (see page 113), each row displays either cell- or PDU-level information (and the title of the window is Cell Browser or PDU Browser, respectively). The traffic displays in order according to the time that it was captured, with the following information for each PDU or cell: Column...
  • Page 92 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Controlling the Color Used 622Vu Advisor uses color to highlight the captured traffic. You can control the colors used through your profile definition. Choose the User Profile command from the Options menu to change the color(s) in the display.

  • Page 93: Table 5. Capture-Facility Menu Commands And Toolbar Buttons

    Print command. Applicable when the Print command would print the entire capture (i.e., when the PDU is not displayed and/or does not have focus). 622Vu Advisor opens a window that lets you scroll through the document, zoom in and out, and print, as necessary:...
  • Page 94 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Available from: Toolbar Active Stopped Saved Menu Command Equivalent Used to… Page Capture Capture Capture ¥ ¥ ¥ Print Setup — Open your standard print-setup dialog box. — ¥ ¥ ¥ Exit Close the Capture utility.
  • Page 95 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Available from: Toolbar Active Stopped Saved Menu Command Equivalent Used to… Page Capture Capture Capture View Detail Display Toggle display of a more detailed view of the ¥ ¥ ¥ cell or PDU data. ¥...
  • Page 96 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Available from: Toolbar Active Stopped Saved Menu Command Equivalent Used to… Page Capture Capture Capture ¥ ¥ ¥ PDU Cell List — Toggle display of a list of cells in the PDU displayed (applicable only when PDU decode is displayed and has focus).
  • Page 97 Save As to save the file under a different name. In the latter case, 622Vu Advisor opens a standard dialog box that you’ll use to assign a name to the capture file (name.cap format). If you omit the suffix, 622Vu Advisor assigns it correctly.
  • Page 98 If you’re looking at a PDU-level display, 622Vu Advisor highlights the currently selected PDU. • If you’re looking at a cell-level display, 622Vu Advisor highlights all cells in the same packet as the cell that’s currently selected. Scroll through the decode window to see the full PDU display. 622Vu Advisor decodes as much of the PDU as it can, and displays this information in a logical form.
  • Page 99 PDU window shows information corresponding to that line — even as you jump to different PDUs in the main display. The most recently opened window is reserved for tracking purposes, however; 622Vu Advisor always displays the decode for the currently selected cell/PDU using this window.
  • Page 100 (respectively, to add a new VCC, edit an existing specification, or delete the selected VCC). For add/edit processing, 622Vu Advisor opens this dialog box: Specify the VCC you want using the top three boxes, then use the drop-down list to select the type of decode you want to associate with that VCC.
  • Page 101 Identify the new file to which you want to export the capture (format varies by type), then click OK to proceed. 622Vu Advisor displays its progress as it creates the file, then issues a message telling you that it’s through. (You can hide the progress dialog box by clicking the Hide button, or stop the process altogether by clicking Abort.)
  • Page 102 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic and then when the ATM is proven to be reliable evaluate the same traffic with the Advisor LAN to find existing LAN problems. To use the Advisor LAN on your ATM 622 traffic you will need to do the following steps: 1.
  • Page 103 VCC, source or destination IP Find addresses, and/or the type of decode used. When you request a Find, 622Vu Advisor opens a window through which you can qualify the PDU/cell you want. This window has three tabs: •...
  • Page 104 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Using the General Find Criteria Tab The General Find Criteria tab lets you describe the basic search criteria: Search string (value to locate in the payload). Type of value represented by the search string (ASCII or hex).
  • Page 105 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic of the capture file. 622Vu Advisor only displays those options that are appropriate to the level of detail shown in the main display (PDU or cell). 4. In the Source area, indicate whether to search traffic captured on Channel 1, Channel 2, or both.
  • Page 106 • To change an address (or pair of addresses), first select the address(es) from the list, then click Edit. 622Vu Advisor prompts for the changes using a window similar to the one described above for an add. •...
  • Page 107 If you specify a type of decode that isn’t in the drop-down list, 622Vu Advisor accepts (and uses) it as entered. 622Vu Advisor does not try to verify user-specified values. 2. Click All to add all the decodes available in the drop-down list.
  • Page 108 You can nest subsets by creating increasingly restrictive criteria, basing each Nesting Subsets subset on the results of the prior subset. 622Vu Advisor keeps track of the entire hierarchy of subsets, and lets you undo subsetting to any level. Choose Undo...
  • Page 109 HEC. Any of the PDU/CRC values request a search by PDU. The cell/HEC values request a cell-by-cell search of the capture file. 622Vu Advisor only displays those options that are appropriate to the level of detail shown in the main display (PDU or cell).
  • Page 110 ON bits in the mask. For example, if you specify a hex 03 (binary 0000 0011) in the search string, fixed at offset 15, 622Vu Advisor looks for traffic whose payload has either of the low-order two bits set.
  • Page 111 By default, the subset includes all decodes. 1. Click Add to add a specific type of decode to the list. 622Vu Advisor opens a dialog box that lets you enter a decode directly, or select one from the drop- down list.
  • Page 112 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic Requesting More Detail For a PDU or Cell You can toggle display of a more detailed view using the Detail Display button. When you toggle the detail on, a panel opens above the cell/PDU list that contains detailed information about the cell or PDU that’s selected currently: Detail Display •...
  • Page 113 Note: If you want to edit any of the cells or the script itself, use 622Vu Advisor’s script editor to view the script (including a list of sequences defined within the script), then use the...
  • Page 114 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic information about browsing and editing a script, and to Chapter 9 for details about sequence processing. Click the Create Script button to build a script from a capture file. 622Vu Advisor opens a dialog box used to define the details of the script: Create Script 1-20 character name for the new script.
  • Page 115 GFC/VPI, VPI, and/or VCI header fields. (You might have performed this reduction in cells already, by creating a subset of the cells/PDUs you want.) 622Vu Advisor uses the values you enter as a filter, and only includes those cells that match the hex bits specified.
  • Page 116 6: Capturing Incoming Traffic 6.3 Viewing Captured Traffic...

  • Page 117: Chapter 7

    Log Data To File box. This opens a standard file-open dialog box that you’ll use to navigate to the log file you want. Click OK when you’re through. 622Vu Advisor opens a display of statistics for traffic on the link attached to the Overview of the Display...
  • Page 118 7: Monitoring Real-Time Statistics times indicate the date and time the statistics were started, and the amount of time the statistics have been accumulating. The VCC field indicates the number of different VCCs for which statistics are displayed. Device where you’re monitoring real-time stats. Statistics display, with one row per VCC.
  • Page 119 7: Monitoring Real-Time Statistics The rest of this chapter describes these features further, and is broken down as follows: • Section 7.1 Real-Time Statistics For Each VCC (page 120) describes each available statistic, and the use of the Columns feature to control the information displayed.

  • Page 120: Real-Time Statistics For Each Vcc

    Table 6. Available Real-Time Statistics Column Description of Content Number to identify a particular VCC. Each time 622Vu Advisor detects a new connection on a channel (1 or 2), it displays the corresponding VP/VC identifiers and begins tracking statistics for that connection.

  • Page 121: Menu Commands & Toolbar Buttons

    If you want to save the currently selected set of statistics as the default, mark the Save as Default box. 622Vu Advisor will display the same information in all subsequent real-time statistics displays until you change it, and will reset the same set of statistics when you click the Default button (below).
  • Page 122 7: Monitoring Real-Time Statistics 7.2 Menu Commands & Toolbar Buttons Menu Toolbar Command Equivalent Used to… Page Exit Close the Real-Time Statistics application. — View — Display the IP Connectivity window, used when there is Connectivity TCP/IP traffic on a particular VCC to track the source and destination addresses for that traffic.
  • Page 123 7: Monitoring Real-Time Statistics 7.2 Menu Commands & Toolbar Buttons Menu Toolbar Command Equivalent Used to… Page Describe Display information about the analysis device where — Device you’re collecting real-time statistics (applicable only when statistics are running): device identification, network information, hardware specifications, and available memory.

  • Page 124: Graphing Real-Time Statistics

    (line or bar graph). Click the Real-Time Graph button to start a new graph. 622Vu Advisor uses these two panels to prompt for the new graph properties:...
  • Page 125 • The X-axis tracks the time elapsed, marked at five-minute intervals. When you reach the limit of the time displayed, 622Vu Advisor shifts the graph to allow for additional data to the right. (Be careful if you stop real-time statistics then start them again, and restart a graph whose X-axis has shifted.
  • Page 126 7: Monitoring Real-Time Statistics 7.3 Graphing Real-Time Statistics 622Vu Advisor continues to update the graph until you Stop the session (or close the graphing window). If you restart the real-time statistics, make sure to start the graph again if desired.

  • Page 127: Creating A Filterset That Captures Specific Vccs

    If you mark this box, 622Vu Advisor defines a buffer in the filterset that’s dedicated to storing idle cells. By default, a cell is considered idle if it has zeros in every bit position of the first five header fields.
  • Page 128 7.4 Creating A FilterSet That Captures Specific VCCs Saving the Filter 622Vu Advisor automatically saves each filter you define, assigning it the name you specified above. It defines a buffer for cells having a bad HEC, a buffer for idle cells (as appropriate to your specifications), and a buffer (called Traffic) to store the selected VCCs.
  • Page 129 7: Monitoring Real-Time Statistics 7.4 Creating A FilterSet That Captures Specific VCCs Using the Saved Filter The filtersets you create from the Real-Time Statistics window are available whenever you start a new capture (or real-time stats session), from this window of the wizard (right):...
  • Page 130 7: Monitoring Real-Time Statistics 7.4 Creating A FilterSet That Captures Specific VCCs...

  • Page 131: Chapter 8

    When you initiate a capture (see page 77), 622Vu Advisor lets you specify a filter to use to control the content of the capture file. The filter you specify operates in real time during the capture, at full bandwidth and at the hardware level.
  • Page 132 It keeps each cell that matches the criteria specified by any filter entry, storing that cell in the buffer corresponding to the first filter entry it matches. 622Vu Advisor discards cells that don’t match the criteria for any of the buffers. This is illustrated here for a filterset having three buffers:...
  • Page 133 8: Filtering Captures 8.1 Understanding Filters TM traffic feeding into the 622Vu undercradle 622Vu's Capture Mechanism ATM cells coming through the connection Buffer 1 Buffer 2 Buffer 3 FilterSet Used for the Capture No Match If a cell matches the criteria for a particular filter entry but the corresponding buffer is full (and doesn’t wrap), then that cell is dropped;...

  • Page 134: Looking At Filter Definitions

    8: Filtering Captures 8.2 Looking at Filter Definitions 8.2 Looking at Filter Definitions Click the Capture Filters button on the toolbar to display a list of filtersets defined in the active cell library (or choose Capture Filters from the Activities menu).
  • Page 135 8: Filtering Captures 8.2 Looking at Filter Definitions positioned on a filterset, filter buffer, or filter entry in the left-hand panel. Use the pulldown menus or toolbars to direct your processing. When you’re through, choose the Exit command from the File menu. The rest of this chapter is broken down as follows: •...

  • Page 136: Table 8. Filterset Pulldown Menus - Summary Of Functions Available

    8: Filtering Captures 8.2 Looking at Filter Definitions Table 8. FilterSet Pulldown Menus — Summary of Functions Available Menu Toolbar Level Used At: Command Ent Used to… Page Equivalent File ¥ ¥ ¥ New FilterSet Define a new filterset. ¥ ¥...

  • Page 137: Defining Filtersets

    8: Filtering Captures 8.3 Defining FilterSets 8.3 Defining FilterSets Use the FilterSet commands from the File menu to add a new filterset (either from scratch or by cloning a filterset that exists already then changing it), to remove a filterset, or to modify a filterset’s definition. Adding a New FilterSet To add a new filterset, click the toolbar’s Add FilterSet button (or choose New FilterSet from the File menu).
  • Page 138 — including all component buffers and filter entries. Note: Regardless of the level of definition selected when you request the delete, 622Vu Advisor removes the entire filterset, not just the selected component (e.g., buffer or filter entry).
  • Page 139 8: Filtering Captures 8.3 Defining FilterSets Modifying a FilterSet Definition The filterset definition window looks like this: These values are predefined based on the initial add-filterset settings. 100% The filterset name and type were defined when you first added the definition, and can’t be changed.
  • Page 140 (This feature isn’t applicable for everything-type filtersets; i.e., CaptureAll buffers.) By default (without using advanced filtering), 622Vu Advisor lets you select cells based on bit settings in the first three header fields (GFC, VPI, and VCI). Collectively, these fields comprise the cell’s address (path).
  • Page 141 The Idle Cell Mask indicates those bits you want to look at when searching for idle cells. By default, 622Vu Advisor looks at all the header bits, so each masking field contains a hexadecimal F (i.e., all 1s). The hexadecimal fields...
  • Page 142 By default, a cell is considered idle if it has zeros in every bit position of the first five header fields. If you’re using a mask, 622Vu Advisor only looks at the bit positions you’ve enabled (set to 1) via the mask, regardless of the match characters you specify.

  • Page 143: Defining Filter Buffers

    8: Filtering Captures 8.4 Defining Filter Buffers For purposes of illustration, as- sume we want to specify idle cells as those having zeros in the last five bits of the VCI, and a 1 in the first bit of the PTI. Our match settings look like this.
  • Page 144 Add processing. Fill in the name you want and click OK. 622Vu Advisor makes a complete copy of the buffer, including all filter entries (with their original names and definitions).
  • Page 145 • Automatic instructs 622Vu Advisor to take all the buffers for which no explicit size is specified (i.e., all the Automatic buffers), then to divide the available (unspecified) space equally among these buffers. This is the initial setting for all new buffers.
  • Page 146 Note: Captured cells are blocked when they’re stored in the filterset buffers, using a blocking factor of 512 cells (for 32 MB RAM). Because of this, 622Vu Advisor may make minor adjustments to your specifications to distribute the buffer space as precisely as possible.

  • Page 147: Defining Filter Entries

    Add processing. Fill in the name you want and click OK. 622Vu Advisor copies the filter entry and stores it under the new name, placing it directly under the definition you copied.
  • Page 148 8: Filtering Captures 8.5 Defining Filter Entries The system verifies that you really want to remove the entry, then deletes it from the library. Modifying a Filter Entry The filter-entry definition window looks like this: Filter entry name and description. Specific values to look for.

  • Page 149: Advanced Filtering Mode

    8.6 Advanced Filtering Mode 8.6 Advanced Filtering Mode 622Vu Advisor’s advanced filtering features let you define a filterset-level mask that's combined with all other selection criteria when choosing the cells to include. This lets you specify a particular characteristic that you want across all...
  • Page 150 Ignore all the bits in this field. If you use Xs in a field, the entire field must specify By default (i.e., if you’re not using advanced masking), 622Vu Advisor looks at the first 28 bit positions of each header (the GFC, VPI, and VCI fields). With advanced masking, it examines the first 48 bits (also the PTI, CLP, HEC, and first byte of the payload).
  • Page 151 622Vu Advisor searches for when comparing incoming cells to this filter entry’s selection criteria. 622Vu Advisor combines (ANDs) the mask and filter-entry settings to compute a final match pattern.
  • Page 152 8: Filtering Captures 8.6 Advanced Filtering Mode...

  • Page 153: Chapter 9

    9: Editing Transmit Sequences Chapter 9 Editing Transmit Sequences 622Vu Advisor lets you define and transmit sequences of cells used to analyze ATM equipment. You can create a transmit sequence in three ways: • By defining a sequence explicitly. •...
  • Page 154 Define a new sequence. Edit Edit the selected sequence, or any cells defined in that sequence. Remove Delete the selected sequence. 622Vu Advisor displays a verification window before completing the request. Close Close the window. Alternatively, choose Cell Sequence AAL Wizards - AAL5 from the Tools menu to initiate the AAL wizard, which lets you create a new sequence that contains AAL5 PDUs, or add an AAL5 PDU to an existing sequence.

  • Page 155: Inheriting Cell Characteristics

    9.1 Inheriting Cell Characteristics The basis of 622Vu Advisor’s ATM analysis involves transmitting and monitor- ing traffic at the cell level. 622Vu Advisor uses two entities to group and process cells: • A sequence combines one or more individual cell definitions (and in- formation telling it how to use those definitions).

  • Page 156: Figure 4. Logical Hierarchy Of Cells, Sequences, And Scripts

    You’ll see how to define and undefine properties when you set up sequence and script definitions. Table 9 describes those properties that can be set from within 622Vu Advisor. Table 9. Cell Header Properties That Can Be Inherited Inheritable Property Description Generic Flow Control.

  • Page 157: Creating Or Editing A Sequence

    9: Editing Transmit Sequences 9.2 Creating or Editing a Sequence • A property that’s undefined in a sequence definition is inherited from the containing script (then propagates down to any cells for which the property is undefined). Put another way, when a property is defined in a sequence, that definition provides a master value that applies for any cells that are included in the sequence and for which the property isn’t defined specifically for the cell.
  • Page 158 9: Editing Transmit Sequences 9.2 Creating or Editing a Sequence Identifying the Sequence Use the area at the top to identify the sequence. The sequence name (1–31 characters) is required when adding a new sequence, but is dimmed (not modifi- able) when editing.
  • Page 159 Change the definition of a cell. As an alternative to clicking the Edit button, double- click the cell you want. 622Vu Advisor opens a window similar to that used for New processing, but with the cell’s name and framing type grayed out; you can only...

  • Page 160: Using The Aal5 Wizard

    SAR and CPCS settings, and without having to compute the CRC. From 622Vu Advisor’s main menu, choose Cell Sequence AAL Wizards - AAL5 from the Tools menu to start the wizard: Sequence where you want to store the new AAL5 PDU.
  • Page 161 (decimal or hexadecimal), and to indicate whether the force-HEC-state property is defined. If you’re generating a new sequence, 622Vu Advisor assigns the header values at the sequence level, and sets up the individual cells to inherit header properties. If you’re appending PDUs to an existing sequence, the header values specified here...
  • Page 162 9: Editing Transmit Sequences 9.3 Using the AAL5 Wizard Cell you’re working on, within the PDU. Use this area to define the 48-byte cell payload. You can enter the payload here as ASCII text, as long as all the characters are printable. This area is disabled if you enter unprintable characters.

  • Page 163: Defining The Cells In A Sequence

    9.4 Defining the Cells In a Sequence When you use the sequence editor (page 159) to add a cell to a sequence, or to edit a cell that’s already defined in a sequence, 622Vu Advisor uses the following window to prompt for the cell’s content: Cell name.
  • Page 164 Identifying the Type of Framing Used When you define a new cell, 622Vu Advisor lets you pick the type of framing you want to use. The lower right corner of the dialog box changes to provide a mini- wizard(s) appropriate to your selection, for use in constructing the reserved portions of the payload (nothing for Raw framing).
  • Page 165 The bottom left area of the window provides 48 character positions, allowing you to specify the cell’s 48-byte payload. Unless you’ve selected Raw framing, however, some of the payload may be reserved. 622Vu Advisor provides mini- wizards to the right of the payload to assist in constructing the reserved portions...
  • Page 166 (.). Raw Framing If you select raw cell framing, 622Vu Advisor lets you specify any cell data you want, in any position. Raw cell framing is particularly useful for non-standard transmissions, as for a device that uses a proprietary signalling code.
  • Page 167 CRC and Parity values individually. AAL5 Framing If you select AAL5 cell framing, 622Vu Advisor provides mini-wizards to assist you in formatting the cell’s Segmentation and Reassembly (SAR), CPCS (Common Part Convergence Sublayer), and time-stamp (Special) information correctly.
  • Page 168 Specify zero (0) if the cell is not the last cell of the PDU; 1 to include the end-of- datagram signal. A zero value doesn’t affect the payload. If you specify 1: • 622Vu Advisor reserves the last eight bytes of payload. Click the CPCS tab to assign the value you want for each reserved field. •...
  • Page 169 There’s one Special field, used to specify whether in-payload-timestamp- generation is on or off for the cell. With this property on (the check box marked), 622Vu Advisor places a timestamp in the cell payload before it’s transmitted, overriding bytes 8–10 and 12–14 for this purpose:...
  • Page 170 9: Editing Transmit Sequences 9.4 Defining the Cells In a Sequence Saving Cell Changes When you’re through with the cell definition, click OK. Here’s the sequence display with one cell added: Use to increase or decrease the number of times the cell is transmitted.

  • Page 171: Chapter 10

    10: Running & Editing Scripts Chapter 10 Running & Editing Scripts A script defines a specific ATM-cell traffic pattern, including timed pauses, that can be sent from an analysis device across an ATM network to test its transmission capabilities. At any point in time, you can have one transmission script running from each analysis device that’s accessible to your system.

  • Page 172: Running A Script

    10.1 Running a Script To initiate a script, select the script you want and click Run (or double-click the script). 622Vu Advisor asks you to define the script’s master header properties, and to identify the device from which to transmit the test.
  • Page 173 If you expect to see a device that isn’t here, click the Refresh button to reevaluate its status. After you select an analysis device and click OK, 622Vu Advisor opens a Monitor Script window, through which you’ll control and monitor the actual...
  • Page 174 10: Running & Editing Scripts 10.1 Running a Script Name of the script you’re running, and the analysis device where you’re running it. Toolbar. Script-level statistics. There are two parts to this display: • The toolbar lets you control the actual script execution. •...

  • Page 175: Table 10. Script Execution Menu Commands And Toolbar Buttons

    10: Running & Editing Scripts 10.1 Running a Script Using the Toolbar Buttons Use the toolbar to direct script processing, referring to Table 10 for instructions. Click to start (transmit) the script. Depress before running the script, to set the script to run repeatedly until you stop it (vs.
  • Page 176 10: Running & Editing Scripts 10.1 Running a Script If you interrupt the script, the elapsed-time field stops counting and changes from green to red. You can rerun the script any number of times by simply clicking the Start button. The elapsed-time field resets itself after a restart, as do the statistics and graph (as applicable to the script you’re running).

  • Page 177: Creating Or Editing A Script

    10: Running & Editing Scripts 10.2 Creating or Editing a Script 10.2 Creating or Editing a Script When you create or modify a script, your working window looks like this (shown below for creating Script 03): Script name and description. Master property values (inherited by any cells for which the corresponding property is...
  • Page 178 Add a new step to the script, positioning it just after the currently selected step. Update Revise the definition of the currently selected step. Remove Remove the selected step. 622Vu Advisor verifies your request before deleting the step. Shift the currently selected step up one position in the script. Down Shift the currently selected step down one position in the script.
  • Page 179 10: Running & Editing Scripts 10.2 Creating or Editing a Script Type of step (Transmit or Pause). Number of times to repeat this step (consecutively at this point in the script). Delay between each cell (for Transmit steps), Applicable for or length of pause Transmit steps;...
  • Page 180 10: Running & Editing Scripts 10.2 Creating or Editing a Script...

  • Page 181: Chapter 11

    11: Using the Ping Generation Tool Chapter 11 Using the Ping Generation Tool The Ping Generation tool lets you transmit standard ping messages through an ATM network, targeting a specific destination address. You control the packet size and the number of packets sent. This feature is available for use with devices configured in end-station mode.
  • Page 182 11: Using the Ping Generation Tool Protocol Description RFC 1483 Multiprotocol Support over ATM AAL5. • Specify the VPI/VCI over which to transmit the ping message(s). Then select the Options tab and specify the: • Packet Size of each message sent (4096 bytes maximum).
  • Page 183 11: Using the Ping Generation Tool Running a Ping Test After you specify the properties you want, click OK to run the test. 622Vu Advisor opens this ping-test monitoring window: Messages sent, responses received, and timeout counts. Ping packets sent per second, and data Measured round-trip transmitted per second...

  • Page 184: Table 11. Ping Generation Menu Commands And Toolbar Buttons

    11: Using the Ping Generation Tool Menu Commands As necessary, use the menu commands as follows: Table 11. Ping Generation Menu Commands and Toolbar Buttons Menu Command Button Used to… File — Exit Exit from the Ping Generation test window. View —...

  • Page 185: Chapter 12

    12: Using QoSMeter Chapter 12 Using QoSMeter QoSMeter is an analysis tool designed to test the quality of service on a particular virtual circuit. Using QoSMeter, you first define the set of tests you want to run. Each set of tests comprises a session. The tests in a session are identical, and are defined in terms of the amount of data to send (test size), the percent of bandwidth to use when transmitting the test, and the percent of bandwidth committed to background traffic.

  • Page 186: Getting Started

    12: Using QoSMeter 12.1 Getting Started When you run the session, QoSMeter lets you monitor the results as it proceeds. There are three tabs in the monitor display, respectively used to: 1. Summarize the results of the session (current, average, best, and worst for each of several statistics).

  • Page 187: Table 12. Qosmeter Menu Commands And Toolbar Buttons

    12: Using QoSMeter 12.1 Getting Started Menu and Toolbar Commands At any point, you can return to the main QoSMeter display and use the menus/ toolbar as described below. Shaded items apply only when running a session. Table 12. QoSMeter Menu Commands and Toolbar Buttons. Menu Command Button...

  • Page 188: Defining A Constant Bit Rate (Cbr) Session

    12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session 12.2 Defining a Constant Bit Rate (CBR) Session With a Constant Bit Rate (CBR) session, the data travels out through the virtual circuit, then back to either the same analysis device or a different analysis device. QoSMeter measures various statistics, including the number of cells sent and received, the number whose data is good or bad, and variations in cell delay.
  • Page 189 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session General Tab Settings The General tab looks like this: Click to specify device properties. Device from which to transmit the session. Click the different tabs to define specifications VCC over which to relating to session transmit the session.
  • Page 190 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session traffic coming in over the same VCC as the one you’re using to transmit; otherwise (to use a different VCC), unmark the check box. If you mark this box, QoSMeter disables all fields on the Analysis tab (described next).
  • Page 191 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session Selection Receives Data Over… Channel 1. Channel 2. Auto Detect Channel determined automatically by the analysis device. Traffic Pattern Settings The Traffic Pattern tab looks like this: Size of each test. Click the different tabs Bandwidth to use for test traffic, to define specifications...
  • Page 192 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session Mark if you want 622Vu Advisor to identify test traffic automatically If you mark this field (it defaults to marked), all other fields on the tab are disabled, for both test and background information. QoSMeter auto-detects the test traffic in this case.
  • Page 193 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session • Click the Add button to add a new VCC. This opens the window shown to the right: Fill in the VPI/VCI to specify the channel over which to transmit background traffic, and the bandwidth to commit to traffic sent over that VCC.
  • Page 194 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session • The number of acceptable failures; that is, the number of failures after which QoSMeter should discontinue testing. This field is used for long-term testing, and refers only to internal failures on transmission. Analysis (only) Mode Settings When running in Analysis mode, both tabs in the Options panel (Execution and Analysis) establish settings used to analyze the data received.
  • Page 195 12: Using QoSMeter 12.2 Defining a Constant Bit Rate (CBR) Session Analysis Tab Use the Analysis tab to specify: • The maximum acceptable percentage of errored cells. This is the highest percent of cells that can show up as errored in any single block, before the block is marked as severely errored.

  • Page 196: Defining A Round-Trip Delay (Rtd) Session

    12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session 12.3 Defining a Round-Trip Delay (RTD) Session Type of session (select Round Trip Delay in this case). With a Round-Trip Delay (RTD) session, data travels from the sending device, out through the network over a preconfigured VPI/VCI, then back to the same analysis device.
  • Page 197 12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session General Tab Settings The General tab looks like this: Device from which to transmit the session. Click the different tabs to define specifications VCC over which to relating to session transmit the session.
  • Page 198 12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session Analysis Settings Device over which to receive and analyze the session data. VCC over which to receive the session data. Click when you’re through with the definition (including the Traffic Pattern and Options), to run the session. Click the Analysis tab and specify the VPI/VCI over which to receive the incoming session data.
  • Page 199 12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session device calculates session results based only on the test traffic, and the Test Size refers to the traffic transmitted via the bandwidth assigned for test traffic. Any background traffic you define simply adds to the load, making the test more realistic.
  • Page 200 12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session • Click the Add button to add a new VCC. This opens the window shown to the right: Fill in the VPI/VCI to specify the channel over which to transmit background traffic, and the bandwidth to commit to traffic sent over that VCC.
  • Page 201 12: Using QoSMeter 12.3 Defining a Round-Trip Delay (RTD) Session Use the Analysis tab to specify: • The maximum acceptable percentage of errored cells. This is the highest percent of cells that can show up as errored in any single block, before the block is marked as severely errored.

  • Page 202: Running A Session

    12: Using QoSMeter 12.4 Running a Session 12.4 Running a Session The session monitoring window looks like this (shown for a Round-Trip Delay session): Device used to transmit Count of test iterations that the test, and the type of succeeded and failed thus far. test you’re monitoring.
  • Page 203 12: Using QoSMeter 12.4 Running a Session ⇒ Select those tests you want to graph from the Details display, then choose Graph Selected Tests from the View menu. This results in a graph of only the selected tests, plus one set of results showing the average of all the selected tests (or, if you only select one test, the average of all tests run so far in the session).
  • Page 204 12: Using QoSMeter 12.4 Running a Session Constant Bit Rate (CBR) Sessions The following sections describe the Summary, Details, and Graph tabs for CBR sessions. Summary Tab The CBR Summary display gives an overview of the tests run so far: It shows the average, best, worst, and current test results for the following statistics: Statistic...
  • Page 205 12: Using QoSMeter 12.4 Running a Session Statistic Description Cells Succeeded Number of non-errored cells received by the test (can include late cells). Cells Errored Number of cells arriving with a bad CRC (checksum). Cell Error Ratio Ratio of Cells Errored / Cells Received. Cells Misinserted Number of times a cell arrived in an unexpected sequence.
  • Page 206 12: Using QoSMeter 12.4 Running a Session columns show the same statistics (in the same order) as described for the Summary tab. These statistics are described starting on page 204. Graph Tab The Graph looks like this for a CBR session: Each different color corresponds to a single test, with the left-most bar (within each set) showing the average for all tests shown.
  • Page 207 12: Using QoSMeter 12.4 Running a Session Round-Trip Delay (RTD) Sessions The following sections describe the Summary, Details, and Graph tabs for Round-Trip Delay sessions. Summary Tab The Round-Trip Delay Summary display gives an overview of the tests run so far: It shows the average, best, worst, and current test results for the following statistics:...
  • Page 208 12: Using QoSMeter 12.4 Running a Session Statistic Description • Cells CRC (cell contains good data). • unscrambling (unscrambled successfully). • integrity (cell retains its original signature after unscrambling). Late Cells Number of cells received late (can include errored cells). This is the number of cells that exceeded the CDV Tolerance specified in the session properties (Options tab).
  • Page 209 12: Using QoSMeter 12.4 Running a Session Details Tab The Round-Trip Delay Details tab looks like this: It shows one line for each test, for the most recent execution of the session. The first five columns are described below. Statistic Description Test Number to identify this test within the session.
  • Page 210 12: Using QoSMeter 12.4 Running a Session Graph Tab The Graph looks like this for a Round-Trip Delay session: Each different color corresponds to a test, with the left-most bar (within each set) showing the average for all tests shown. Here we’re looking at four different tests.

  • Page 211: Glossary

    Glossary 622Vu Advisor The user interface to the CellCommand OLE Automation server. This interface program provides all the capabilities outlined in this Agilent 622Vu Advisor User’s Guide. 622Vu Undercradle The Agilent Advisor undercradle analysis device. Comprises the logic used to send, receive, and analyze ATM traffic as directed by your scripts, ping messages, and QoSMeter sessions.
  • Page 212 See filter buffer. capture Feature of 622Vu Advisor that lets you actually capture the traffic that comes in over one or both channels of an analysis device, optionally saving the captured traffic on your PC. You might save a capture to review or process it later, or you may want to use the capture as a script (or as the basis for a script).
  • Page 213 Any changes made during processing are saved in the active cell library immediately. All 622Vu Advisor processing requires that you have an active cell library. Each library is a complete entity, containing all the sequence and script definitions, filter buffers, filter entries, etc., which are used together during processing.
  • Page 214 A: Glossary Force-HEC-state property — Indication of whether to force a HEC value before cell transmission. If a property is undefined at a particular level, its value is inherited from the containing object: • A property that’s undefined in a cell definition is inherited from the containing sequence (if defined there) or script (if not defined at the sequence level).
  • Page 215 A: Glossary config.ini .ini file used by 622Vu Advisor to configure the system at startup, and to determine various processing preferences. configuration #5 One of the possible configurations you can establish for a full-end station analysis device, wherein incoming traffic on Channel 1 goes into the framer chip on the analysis device and is monitored by 622Vu Advisor (and optionally captured).
  • Page 216 There’s a separate filter entry for each different type of cell you want to capture in that buffer, and that entry provides specific instructions to 622Vu Advisor as to the characteristics of the cell(s) you want to save (specific VCCs, specific GFC values, etc.).
  • Page 217 Layer 2 rather than forwarding them at Layer 3. 622Vu Advisor lets you identify specific VCCs that should always be interpreted (i.e., decoded) as IFMP traffic, as detailed under Specifying Decode Preferences on page 100.
  • Page 218 One of two ways you can configure an analysis device (contrast end-station mode). In monitor mode, the 622Vu Advisor passively observes the traffic flow coming through it, optionally capturing some or all traffic for further analysis. network One or more ATM switching platforms under the same administration.
  • Page 219 Payload Type Indicator See PTI. For purposes of Agilent Technologies' product line, any "C or newer" model of the Agilent Advisor. Protocol Data Unit — The information unit of a particular communications protocol; in the case of ATM traffic, the collection of cells that make up a packet.
  • Page 220 A: Glossary See Physical Media Dependent sublayer. PNNI Private Network-to-Network Interface. A switch-to-switch signalling protocol. 622Vu Advisor lets you identify specific VCCs that should always be interpreted (i.e., decoded) as using PNNI signalling or routing, as detailed under Specifying Decode Preferences on page 100.
  • Page 221 Also used to refer to the host user or application responsible for sending the cell. sequence Within 622Vu Advisor, a named set of cells that can be referenced as a single entity by using the sequence name. Each entry in the sequence comprises a: •...
  • Page 222 Default user profile. Active when you first start 622Vu Advisor, and used until you add your own profile. On subsequent startups, 622Vu Advisor is initialized with the last profile used. SSCOP Service Specific Connection Oriented Protocol.
  • Page 223 • Reuse each buffer continually until the capture is stopped, essentially creating a circular buffer (box is marked). With this selection, 622Vu Advisor writes over cells that have already been stored on the analysis device after the buffer is full.
  • Page 224 A: Glossary • • •...

  • Page 225: Config.ini File

    Appendix B config.ini File This appendix contains the text of 622Vu Advisor’s basic initialization (.ini) file. While the .ini file rarely requires modification, you might be asked to change it for your installation. If this is the case at your site, open the config.ini file, then edit the file using the standard Windows Notepad application.
  • Page 226 B: config.ini File Identification and security information. Environment variables (user profile). Current settings for various processing options. Capture preferences. Devices accessible via 622Vu.

  • Page 227: Summary Of Libraries

    Appendix C Summary of Libraries 622Vu Advisor is shipped with several cell libraries that are designed to help with specific types of ATM analysis, as detailed in this appendix. You can use these libraries for your own purposes, or modify them as needed.
  • Page 228 C: Summary of Libraries...

  • Page 229: Cell Library Structure

    622Vu Advisor’s cell libraries serve as repositories for various information: sequence definitions (groups of cells), script definitions (groups of sequences), filterset definitions, etc. 622Vu Advisor can manage any number of cell libraries, but only one library is open (active) at any given time.

  • Page 231: Regulatory Information

    Appendix E Regulatory Information Laser Safety Statements The OC-12c/SMT-4c single mode fiber-optic interface contains Class 1 laser devices. Class 1 laser devices are considered to be safe based upon current medical knowledge. A laser safety warning label is attached to the individual modules where necessary.
  • Page 232 1550 ________________________________________________________________ WARNING You must return modules with malfunctioning lasers to an Agilent Technologies Service Center for repair and calibration. Under no circumstances look into the module connector or the end of an optical cable attached to the optical output when the device is operational.

  • Page 233: Declaration Of Conformity

    Declaration of Conformity...

  • Page 235: Index

    Index end-station mode, 38, 216 firmware, use of, 216 622Vu Advisor monitor mode, 38, 218 configure, 20 monitoring a single channel, 61–63, 70 IP address configure, 20 monitoring ATM interfaces during script modem installation, 24 runs, 67, 173 software installation, 13 monitoring both channels, 63–64, 63, 68,...
  • Page 236 controlling idle cell capture. See filtering, 79. See also filter processing. filtersets, defining; idle cells. highlighting cells in current packet, 97 controlling size and wrapping of. See limiting captures to specific cells, 79 filtersets, defining. memory allocation for, 131, 143, 145–46, defining, 135, 143–46.
  • Page 237 See scripts. See also analysis devices. sequences, managing. See sequences. monitoring both channels, 63, 68, 69 standard, supplied with 622Vu Advisor, use in transmissions, 62. See also capture processing; analysis devices. summary of 622Vu Advisor-supplied, 42, VCI field, 156. See also header data.
  • Page 238 See also AAL5 wizard; sequences. installation, 17 settings for cell framing, 164, 167, 168. troubleshoot installation, 28 See also sequences. exiting 622Vu Advisor, 45, 113 CRC field exiting QoSMeter processing, 187 as AAL1 SAR setting, 167. See also export AAL protocols, defining framing for file to Expert Analysis, 102 sequences.
  • Page 239 156. See also capture processing. also cells; scripts; sequences. defining, 135, 137–43. See also filter hierarchy of 622Vu Advisor components, 41 processing. defining from the capture window, 84, 96 idle cells defining with Advanced Filtering Mode, capturing, 79, 137, 139–40.
  • Page 240 Installation and Configuration, 9 opening a QoSMeter session, 187 IP address overview of QoSMeter processing, 7 622Vu Advisor, 20 Parity field, as AAL1 SAR setting, 167. See also AAL protocols, defining framing save file to Expert Analyzer, 102 for sequences.
  • Page 241 instructions to use, 181–84 menu and toolbar commands, 187 toolbar buttons described, 184 overview of tab use, 196 processing overview, 7 starting and stopping, 203 profile toolbar statistics described, 207–9. See also defining script buttons, 49, 51–53. See monitoring session results. also scripts;...
  • Page 242 Segmentation and Reassembly sublayer. See standard.prf file, 44, 49. See also user SAR sublayer. profiles. sequences, 39, 42. See also processing starting 622Vu Advisor, 41, 42, 43 overview; scripts. library opened when first, 48. See also adding PDUs to, 46, 153, 160–63 cell library.
  • Page 243 Transmit Step. See scripts, defining steps in. defining decode methods, 98, 113 troubleshoot defining filtersets based on, 96 622Vu Advisor installation, 23 established via GSMPdl-anyotherhere?, Console tool, 30, 33 NIC card installation, 28 library inclusion of, 227 Ping, 31 limiting captures to particular, 79.

Table of Contents