COPYRIGHTS AND DISCLAIMERS

Transcription

1 CXMon User Guide

2 COPYRIGHTS AND DISCLAIMERS Published Date: April 13th, 2010 This publication contains information proprietary and confidential to Memotec Inc. Any reproduction, disclosure or unauthorized use of this publication is expressly prohibited except as Memotec Inc. may otherwise authorize in writing. Memotec Inc. reserves the right to make changes without notice in product or component design as warranted by evolution in user needs or progress in engineering or manufacturing technology. Changes which affect the operation of the unit will be documented in the next revision of the manual. We have made every effort to ensure the accuracy of the information presented in our documentation. However, Memotec assumes no responsibility for the accuracy of the information published. Product documentation is subject to change without notice. Changes, if any, will be incorporated in new editions of these documents. Memotec may make improvements or changes in the products or programs described within the documents at any time without notice. Mention of products or services not manufactured or sold by Memotec is for informational purposes only and constitutes neither an endorsement nor a recommendation for such products or services. Memotec Inc. is a wholly owned subsidiary of Comtech EF Data Corp., and its parent company Comtech Telecommunications Corp (NASDAQ: CMTL). CXMon, CXTool, CX-U Series, CX-UA Series, and AbisXpress are either registered trademarks or trademarks of Memotec Inc.in Canada, the United States of America, and in other countries. Belden is a registered trademark of Belden Inc.in the United States of America and in other countries. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Whatsup and WhatsupGold are registered trademarks of Ipswitch Inc. in the United States and other countries. Any other trademarks are the property of their respective companies. Copyright 2010 Memotec Inc. Memotec Inc Henri Bourassa Blvd. West Montreal, Quebec Canada H4S 1P7 Tel.: (514) FAX: (514)

3 Contents Chapter 1: Overview of CXMon Monitoring CX Equiment with CXMon What CXMon Delivers How to Work with CXMon Organization of this User Guide Feedback on the Documentation CXMon System Requirements System Limitations Chapter 2: Installing CXMon Preparing your PC to run CXMon Installing and Configuring WhatsUp The CXMon Installer Process Upgrading from a previous CXMon version Remove CXMon (pre-windows Vista) Remove CXMon (Windows Vista) Launching the Installation Program Registering the Memotec MIBs (optional) Windows Vista Operation Configuring CXMon Configuring the Data Acquisition Parameters Configuring the WAN Ratio Graph Configuring the Data/Log Storage Options Configuring the Graph Display Options CXMon Authorization Key Management Transferring the CXMon License Key Chapter 3: Monitoring a CX Device Configuring CX Devices Vpstats index values Vpstats wandix values Vpstats vrsr index values Discovering CX Devices in WhatsUp iii

4 CXMon User Guide 3. 3 Starting the CXMon Application Monitoring Device Data Device Information Voice/GSM Traffic System Savings SNMP Traps T1 Port/E1 Port Monitors WAN Port Monitor WAN Port Details Viewing the Log Usage Statistics Reading the Traffic Map Viewing Detailed Information on a User Port Displaying Ratio of Traffic Types on a Port Displaying the ratio of duplicated silence packets Displaying the Ratio of Voice Packets Displaying the ratio of TRAU/TCH Channels Displaying the Ratio of Traffic Compression Displaying the ratio of discarded voice packets Displaying the Current Discard Level Logging Traffic Data to a CSV File Viewing the Log Usage Statistics Savings log file WAN log file BWSavings log file Traffic log file Voice Silence log file Discard Level log file PktDiscards log file Traps log file Chapter 4: Troubleshooting Installation/Launching Issues SNMP Trap Issues Device Information Issues WAN Port Monitor Issues Index Index-1 iv

5 List of Tables Table 1-1: Topic Structure of the User Guide Table 1-2: Firmware supported by CXMon Table 2-1: Different modes for handling traps Table 2-2: SNMP Settings Table 2-3: Meter Bar Settings Table 2-4: Log Settings dialog box parameters Table 2-5: Graph Settings parameters Table 3-1: CXTool version supporting CXMon Table 3-2: vpstats index values Table 3-3: vpstats wanidx values Table 3-4: vpstats vrsridx values Table 3-5: Device information fields Table 3-6: Voice/GSM Traffic System Savings Information Table 3-7: SNMP Traps fields Table 3-8: Port LED color description Table 3-9: WAN Port Monitor Fields Table 3-10: WAN Port Details fields Table 3-11: Log Status parameters Table 3-12: Traffic Mapping dialog box Table 3-13: Traffic Types Table 3-14: Counters in Traffic Mapping dialog box Table 3-15: Different Mode supported by User Port Details window Table 3-16: Discard Level legend Table 3-17: Port Error Counters in User Port Details Table 3-18: Packet Counters in EDGEPlus Mode Table 3-19: Packet Counters in DCME Mode Table 3-20: Packet Counters in GSM Abis/Ater Mode Table 3-21: Packet Counters in AbixXpress Mode Table 3-22: Packet Counters in ATM/TDM/IMA Mode v

6 CXMon User Guide Table 3-23: Log Status parameters Table 4-1: Solutions to installation or launching problems Table 4-2: Solutions to SNMP Trap Problems Table 4-3: Solutions to Device Information Problems Table 4-4: Solutions to WAN Port Monitor Problems vi

7 List of Figures Figure 1-1: The CXMon main window Figure 2-1: Windows Components Wizard Figure 2-2: Enabling the Simple Network Management Protocol Figure 2-3: Start of the CXMon installation process Figure 2-4: Memotec MIBs file location Figure 2-5: Registration batch file location Figure 2-6: MIBs registration in WUP Figure 2-7: SNMP Setting dialog box Figure 2-8: Meter Bar Settings dialog box Figure 2-9: Graph Settings dialog box Figure 2-10: Overview of CXMon Licensing Process Figure 2-11: CXMon Application Splash Screen Figure 2-12: License Configuration dialog box Figure 2-13: License Configuration dialog box Figure 2-14: Unauthorized Program running on PC Figure 2-15: Step 2 of the Transfer License wizard Figure 2-16: Transfer in Progress Wizard Figure 3-1: SNMP configuration in CXTool Figure 3-2: Vista Addresses in CXTool Figure 3-3: Launching device discovery in WUP/WUG Figure 3-4: WUP Map with discovered Memotec CX/CX-U devices Figure 3-5: Logging into the CXMon device Figure 3-6: CXMon main window Figure 3-7: Device information panel Figure 3-8: Voice/GSM Traffic System Savings panel Figure 3-9: SNMP Traps panel Figure 3-10: Resizing the Trap Columns Figure 3-11: T1 Port/E1 Port Monitors panel Figure 3-12: WAN Port Monitor panel vii

8 CXMon User Guide Figure 3-13: WAN Port Details panel Figure 3-14: Log Status dialog box Figure 3-15: User Port Details for EDGEPlus Mode Figure 3-16: T1/E1 Port Monitor buttons Figure 3-17: User Port Details: Traffic graph Figure 3-18: User Port Details: Silence within Voice Traffic Ratio graph Figure 3-19: User Port Details: Traffic Optimization Ratio graph Figure 3-20: WAN Discards Level Distribution graph Figure 3-21: Current Discard Level graph Figure 3-22: Example of a Log file as a spreadsheet Figure 3-23: Log Status dialog box viii

9 1 Overview of CXMon This chapter provides a high-level overview of the CXMon product, information on how to get started with the application, and overview of its documentation set. 1-1

10 CXMon User Guide 1.1 Monitoring CX Equiment with CXMon CXMon provides a graphic interface for monitoring CX equipment in GSM Abis/Ater and DCME networks. The Windows based user interface makes it easy to use and its integration with the WhatsUp Professional (WUP) and WhatsUp Gold (WUG) applications provides many added features. Once CXMon is installed, it can be launched directly from the Map view of WhatsUp Professional/Gold, by right clicking on a CX device in the Map. Once it is started, CXMon will begin acquiring statistics from the selected CX device. Statistics from the WAN interface and from the various DIM ports will be presented in two different panels. Statistics are either displayed as counters or in a group What CXMon Delivers The CXMon monitoring tool makes it easy to observe the status of Memotec equipment and the general health of GSM Abis/Ater or DCME applications. The main information windows are: Figure 1-1: The CXMon main window Device information (top left): Provides quick access to the device type, uptime, and configured alias to easily differentiate the various CX devices in the network. 1-2

11 Overview of CXMon Voice/GSM Traffic System Savings: Displays the evolution over time of the GSM Abis optimization performed by the CX device. WAN information (bottom right/left): Displays WAN link usage status information and error counters. T1/E1 Port information (middle): Provides visual indication of the presence of alarms on a port and information on the type of traffic present. Trap information (top right): Displays SNMP Traps collected from a CX device How to Work with CXMon In a typical CXMon session, you will perform the following workflow steps: 1. Launch WhatsUp Pro. 2. Log into the CX device to be monitored. 3. Configure how the device statistics are to be monitored. 4. Monitor the high-level data for the device (the main window). 5. View the Port Monitor data (T1/E1 Port Monitors) 6. View the traffic mapping on the ports Organization of this User Guide This user guide includes the following sections: Chapter 1: Overview Chapter2: Installing CXMon Chapter 3: Monitoring a CX Device Chapter 4: Troubleshooting Provides a list of the requirements for running CXMon and the installation steps. Launching CXMon from WhatsUp Professional/Gold is included. Explains how to install CXMon and setup WUP to start monitoring the CX in your network. Explains how to use the CXMon user interface, the various graphics, the counters, the menus and sub-menu and the different configuration settings. Provides solutions for the common problems encountered with CXMon and WhatsUp. Table 1-1: Topic Structure of the User Guide Feedback on the Documentation Our Technical Publications group welcomes your feedback. Please help us improve future releases of this document by sending us your comments and suggestions. You can communicate with us by at [email protected]. 1-3

12 CXMon User Guide 1.2 CXMon System Requirements To successfully install and run CXMon, the following system requirements must be met: Pentium 3 class processor PC, running at 450 MHz or more Recommended: Pentium 4-2 GHz or more for more than 10 simultaneous CXMon sessions The following versions of MS Windows: - Windows Server 2008 R2 - Windows Vista - Windows 2003 R2 Server - Windows XP SP1 or later - Windows 2000 SP4 or later Microsoft SNMP Service must be installed IpSwitch s WhatsUp Professional 2005/2006 or WhatsUp Gold 11/12 (or higher) must be installed Graphics card that displays a minimum of 65K (16 bit) colors. Minimum screen resolution of 1024 x 768 WARNING: The main window is designed to be viewed as maximized. If you launch the application in a screen resolution greater than 1024 x 768, then lower the resolution, and re-maximize the window, parts of the window may not appear. When you launch the application on a desktop, you should not change the screen s resolution and resize the main window. 500 MB or more of free disk space Logging the data acquired by CXMon will occupy between 1 MB and 4 MB of disk space per day, for each CXMon session 512 MB or more of RAM Recommended: 1024 MB or higher for more than 10 simultaneous CXMon sessions NOTE: Windows Vista and Windows Server 2008 R2 are supported only with WhatsUp Gold 12 or higher. 1-4

13 Overview of CXMon System Limitations Under any Windows OS, the user must have administrator rights to install or run CXMon. It is possible to run more than one CXMon session at the same time, allowing for simultaneous monitoring of more than one CX device. The maximum number of CXMon sessions that can run at the same time is limited by the software license needed for CXMon and the system resources. Only one application on the PC may listen for SNMP Traps. In order to use the CXMon SNMP Trap collection function, other applications that collect trap information must have this function disabled. There is a special mode that allows both WUP/WUG and CXMon to receive SNMP traps (see Configuring the Data Acquisition Parameters on page 2-11). CXMon makes use of SNMP objects in the CX to help monitor the traffic. These new objects are automatically configured when using the correct CXTool revision (see Configuring CX Devices on page 3-2). To use these new objects in CXMon, you must upgrade from an older configuration to a minimum firmware revision for all CX devices being monitored. The following table lists the minimum firmware supported for each application. Abis/Ater on CX Application Minimum firmware required for CXMon support 0435H DCME on CX Abis/Ater with EDGEPlus on CX Abis/Ater with EDGEPlus and DCME on CX-U EDGEPlus/DCME on C flavor (CX/CX-U) ATM/TDM/IMA (CX-U) Abis/Ater with AbisXpress (CX-U) 0510R 0520T 0210A 0210A Table 1-2: Firmware supported by CXMon Only the CX900s, CX960e, CX2000, and the CX-U1000 series of products work with CXMon. In order for CXMon to be able to receive traps from the CX device being monitored, the Windows firewall application must be disabled for all supported Windows versions. To do this, follow these steps: - Open the Windows Control Panel and open the Firewall option. - Select the radio button that disables the firewall and click OK. 1-5

14 CXMon User Guide 1-6

15 2 Installing CXMon This chapter explains how to install and register CXMon, how to activate your license, and how to configure your devices to work with CXMon. 2-1

16 CXMon User Guide 2.1 Preparing your PC to run CXMon WARNING: This procedure applies to all versions of MS Windows EXCEPT MS Windows Vista and Windows Server 2008R2. If you have Vista, you can skip ahead to Installing and Configuring WhatsUp on page 2-4. Before installing CXMon, make sure that the SNMP service is available on the system. This section is not required for users who have Windows Vista installed, since SNMP traps are enabled by default. To verify that it is installed, follow these steps: 1. Select Start > Settings > Control Panel. 2. Select Add /Remove Programs. 3. On the left side on the panel select Add/Remove Windows Components. 4. Scroll the list until you see, Management and Monitoring tools. Figure 2-1: Windows Components Wizard NOTE: If the checkbox is not enabled, the service is not installed. 5. If the checkbox is not set, enable the checkbox and click the Details button. 2-2

17 Installing CXMon 6. Verify that Simple Network Management Protocol is set. Figure 2-2: Enabling the Simple Network Management Protocol 7. If this subcomponent is not selected, select it and click OK. 8. Click Next and follow the installation instructions. NOTE: A PC restart is normally required at the end of the installation. Windows may ask for your Windows CD and Windows may reject your request because of insufficient rights to perform this operation. If you have any problems, contact your network administrator. 2-3

18 CXMon User Guide 2.2 Installing and Configuring WhatsUp The WhatsUp application (Ipswitch Inc.) monitors critical network devices and services, allowing you to quickly identify problems and increase your understanding of your network performance and availability. If not already installed, complete the steps to install WhatsUp Gold since CXMon is designed to work in conjunction with WhatsUp Gold. A 30-day evaluation version is available on the CD-ROM provided by Memotec. In order to prevent SNMP trap collection conflicts with CXMon, exercise caution when setting up WhatsUp and CXMon. CXMon v5.0 and higher support three modes of handling the traps (see table below) CXMon Trap Handling mode Trap Configuration in WhatsUp Professional/ Gold Results CXMon only Disabled CXMon is listening to the traps and only CXMon can receive them. The default UDP port 162 is used. Traps are displayed in CXMon only. From WUP Enabled Traps are forwarded to a common port (usually UDP port 3000) WhatsUp (WUP or WUG) is listening to the traps on the default UDP port 162 and is forwarding them to CXMon on a common UDP port (usually UDP port 3000). Traps are displayed in CXMon and WhatsUp. The common port is set to 3000 by default when installing CXMon. Disabled Enabled Traps are displayed in WhatsUp only. To disable traps in WhatsUp, launch WhatsUp and perform the following steps: 1. Select Configure > Program Options 2. Select Passive Monitor Listeners. 3. Highlight the SNMP Trap entry. 4. Click Configure. Table 2-1: Different modes for handling traps 5. De-select Listen for messages on port 162. For more information on setting the Trap handling mode in CXMon, see Configuring the Data Acquisition Parameters on page

19 Installing CXMon 2.3 The CXMon Installer Process Once you have prepared your PC and configured it (see Preparing your PC to run CXMon on page 2-2 and Installing and Configuring WhatsUp on page 2-4), you can now install CXMon. Installing CXMon will make the following modifications to your WhatsUp installation: Add discovery support for all CX device types (including CX900s, CX960e, CX2000, and the CX-U1000 series), when performing device discovery. Integrate CXMon into the WhatsUp user interface, allowing users to start CXMon by right-clicking a CX device in the Map view. Optional: Integrate the Memotec MIBs into WhatsUp, making it possible to browse the different counters present in the CX, using WhatsUp s SNMPView. If this step is performed, the CXMon installation program will require some files located on the CD-ROM provided by Memotec. The files needed are: - Memotec MIBs file: you must uncompress this file in a local folder (ex: c:\mibs) - memotec.bat file: this is available for supported WhatsUp versions, except WhatsUp Gold 12. For WhatsUp 12 Standard Edition, the user only needs to take the extracted Memotec MIBs files and copy them into the \Data\mibs folder of WhatsUp Gold. 2-5

20 CXMon User Guide 2.4 Upgrading from a previous CXMon version If you already have CXMon installed, you must remove the previous version before installing the new one. Uninstalling the previous CXMon version will not remove the license files you have already purchased. If you install the new CXMon in the same folder, the new CXMon will be able to use the same license files. If you didn t install CXMon in the default path, take note of its current install path so that you can select the same path when you install the latest version of CXMon. WARNING: Do not manually delete any files in the CXMon folder as it may affect the license files and cause CXMon to stop functionning Remove CXMon (pre-windows Vista) To remove the previous CXMon for all supported Windows versions (Windows XP, Windows 2000, Windows 2003 Server), follow these steps: 1. Select Settings > Control Panel > Add/Remove Programs. 2. From the list of installed applications, select CXMon (or Memotec CXMon for previous versions). 3. Click Remove. When the previous version of CXMon is removed, you can install the newer version Remove CXMon (Windows Vista) To remove the previous CXMon on Windows Vista, follow these steps: 1. Open the Control Panel and select Program and Features. 2. From the list of installed applications shown, select Memotec CXMon. 3. Click Uninstall. When the previous CXMon is removed, you can install the newer version. 2-6

21 Installing CXMon 2.5 Launching the Installation Program 1. From the Memotec CD-ROM, run the setup.exe program in the \CXMon folder. Figure 2-3: Start of the CXMon installation process 2. Click Next. The License Agreement screen for CXMon appears. 3. If you agree with the License Agreement, select I accept and click Next. If you disagree with the License, click No and the installation will stop. 4. Enter your name and the name of your organization and click Next. 5. Specify the destination folder where CXMon will be installed and click Next. By default, the installation program will install itself in the following directory: C:\Program Files\Memotec\CXMon\ NOTE: If you had a valid CXMon license, you should install CXMon in the same path as the previous version to reuse the same license. 6. Type the UDP port number to allow trap handling and click Next. Unless you have a customized UDP port for this purpose, the default value of 3000 should be correct. To be able to receive traps in both WhatsUp and CXMon, WhatsUp must be configured to forward the traps to CXMon, using a common UDP port number. 7. Optional: the installation process will prompt you to register the MIBs. 2-7

22 CXMon User Guide To register the MIBS, make sure you have the Memotec CD in hand and click YES. See Registering the Memotec MIBs (optional) on page 2-8. If you select NO, the installation proces will begin immediately. When the installation is over, select Finish to terminate the installation program. Your next step should be to configure your CX devices, so refer to Configuring CX Devices on page 3-2. NOTE: CXMon is provided as a trial program that is valid for 30 days only. To continue using this program after the trial period is over, you must input a valid license key, which can be obtain by purchasing CXMon. Refer to CXMon Authorization Key Management on page 2-18 for more information on obtaining a license key Registering the Memotec MIBs (optional) When you register the MIBs, you will be able to use them from inside WUP/ WUG, with the SNMP Viewer tool (a MIB browser) or when defining new monitors for a device. This registration process only applies to computers that have WhatsUp Gold version 11 or WhatsUp Professional 2005/2006 installed since WhatsUp Gold 12 uses a different method. For WhatsUp Gold 12, you only need to extract the Memotec MIBs files and copy them into the WhatsUp MIBs directory. If WhatsUp Gold 12 is installed in the default location then it can be found at this location: C:\Program Files\Ipswitch\WhatsUp\Data\Mibs After this step is completed, you can proceed to Configuring CX Devices on page 3-2. This step is not needed for CXMon to work correctly. NOTE: For Windows Vista users, proceed directly to Windows Vista Operation on page To register the Memotec MIBs, follow these steps: 1. Double-click the self-extracting file in the \CXProductMibs folder on the Memotec CD. Extract the file to a a local path (ex: C:\Mibs). 2. When the MIBS are extracted to a local folder, click OK to go to the next step. 2-8

23 Installing CXMon 3. Specify the path where you extracted the Memotec MIBS locally (in the first two steps) by either typing the path in the field or using Browse. When done, click OK. Figure 2-4: Memotec MIBs file location 4. Type the location of the memotec.bat file in the Location field, or use Browse to select it, and click OK. This batch file copies the Memotec MIBs to the right location and calls the command line tools provided by WhatsUp to register the new MIBs. This file is located on the Memotec CD, in the \WhatsUp\Customizing WhatsUp\ folder. Figure 2-5: Registration batch file location NOTE: The memotec.bat file is different for each firmware release. Be sure to select the version that corresponds to the software revision in the CX device. 2-9

24 CXMon User Guide Figure 2-6: MIBs registration in WUP When the registering process is completed, you will be prompted to restart your PC to finalize the CXMon installation. The registration process can take anywhere from ten seconds to two minutes to complete Windows Vista Operation NOTE: This note applies only to older versions of CXMon (before version 6.0). For Windows Vista, the CXMon.exe executable file must be given administrator rights for it to run correctly. To do this, follow these steps: 1. Right-click the CXMon.exe file and select Properties. 2. Select the Compatibility tab and enable the Run this program as an administrator checkbox 3. Click OK. This will enable the CXMon application to run correctly in Windows Vista. 2-10

25 Installing CXMon 2.6 Configuring CXMon Four configuration areas are available, from the Settings menu: SNMP Settings Meter Bar Settings Log Settings Graph Settings Configuring the Data Acquisition Parameters You can configure data acquisition parameters for CXMon using the SNMP settings dialog box. To access these parameters select Settings > SNMP Settings. Figure 2-7: SNMP Setting dialog box Parameter Default Description Timeout 1000 ms Defines the time to wait, in milliseconds, for a response to an SNMP request. Table 2-2: SNMP Settings 2-11

26 CXMon User Guide Parameter Default Description Retry Count 3 Defines the number of times an SNMP request will be made before the request is abandoned. Requests are repeated when the Timeout value is reached. Read Community public Displays the community string used to read values from a CX device. This value is only configurable from WhatsUp. Write Community private Displays the community string used to write values to a CX device. This value is only configurable from WhatsUp. Refresh Rate 5 secs Displays the Global refresh rate used to plot graphs and to update all status information and counters. Choices are: 5, 10, 30 and 60 seconds. CXMon will update each graphs/counters at this rate. This value can be overridden for a particular graph by changing the refresh rate in the Graph Settings. Display period 15 min Sets the Global visible period, when plotting graphs. When the Display period is greater than the default value for the current Refresh rate, CXMon will average as many graph points needed to show the desired display period. Choices are: Refresh Rate of 5 secs: 15 mins, 1 hour, 4 hours, 12 hours and 24 hours. Refresh Rate of 10 secs: 30 mins, 1 hour, 4 hours, 12 hours and 24 hours. Refresh Rate of 30 secs: 90 mins, 3 hours, 6 hours, 12 hours and 24 hours. Refresh Rate of 60 secs: 3 hours, 6 hours, 9 hours, 12 hours and 24 hours. Table 2-2: SNMP Settings 2-12

27 Installing CXMon Parameter Default Description Trap Options --- Sets the way traps are handled on the PC. The choices are: CXMon only: Traps are received by CXMon only. Any other application on the PC that tries to collect the traps will fail or will prevent CXMon from collecting them. CXMon will monitor the UDP port 162 for traps. From WUP/WUG: Traps are received by WUP/ WUG and forwarded to CXMon, using forwarding UDP port (3000 by default). Disable: Traps are not collected by CXMon. Other applications (like WUP/WUG) can collect them. All CXMon session running on a PC share these settings. When the trap options are changed in CXMon, CXMon itself will change the configuration of WUP, so it matches the one in CXMon. Changes to the trap handling usually require restarting WUP. Sometime, restarting the PC is necessary. Trap Reception port 162 Identifies the port from which CXMon expects to get the traps. The value of this read-only field depends on the Trap Options value: CXMon only: UDP port 162, the default SNMP port for traps. From WUP: UDP port 3000, the default port set by CXMon at installation time. This field can only be change by installing CXMon. Table 2-2: SNMP Settings 2-13

28 CXMon User Guide Configuring the WAN Ratio Graph For Serial and Ethernet based WAN, CXMon will get a reference value from the CX device in order to calculate the ratio of the WAN that is used. This ratio is shown in the meter bar, next to the WAN graph. Sometimes, the reference value is too high for the amount of traffic (ex: A fast Ethernet card uses a reference value of 100 Mbps). For VR WAN, there are no reference values so the user always needs to enter custom values. The meter bar settings panel is used to configure custom bandwidth reference, for the meter bar in the WAN port monitor. To access these parameters, select Settings > Meter Bar Settings. Figure 2-8: Meter Bar Settings dialog box Parameter Default Description WAN Index --- Select the WAN index (Port or VR) to customize Custom Bandwidth Reference uncheck To customize the reference value for the selected WAN index, select this checkbox Tx 0 Reference bandwidth (kbps) values to use for Tx direction. Default value is the value read from the CX device (for Ethernet and Serial). For VR, the default value is 0. Rx 0 Reference bandwidth (kbps) values to use for Rx direction. Default value is the value read from the CX device (for Ethernet and Serial). For VR, the default value is 0. Table 2-3: Meter Bar Settings 2-14

29 Installing CXMon Because the reference bandwidth for the VR entry is 0, CXMon will not be able to correctly display the Meter Bar until the user sets the reference values. For this reason, CXMon will alert you shortly after launching CXMon that a VR entry has no reference value with the following message: The Bandwidth Reference of VRSR:1 is zero. Configure Speed Value in Meter Bar Settings dialog and then press OK HINT: When this warning message is displayed, do not click OK immediately because CXMon will display the same message in a few seconds. Instead, leave the message on the screen and go to the Meter Bar settings dialog box to set the reference values for the specified VRSR entry. When this is done, you should then click OK Configuring the Data/Log Storage Options The log settings are used to set the parameters for data storage. To access the Log Setting options, select Settings > Log Settings: Graph Log: Indicates that Graph information (of all graphics) will be stored. The default is unchecked. Trap Log: Indicates that SNMP Trap information will be stored. The default is unchecked. Other Settings: displays the Log Settings dialog box which offers the following options: Parameter Single file per day Limit file size to 1 MB Description Graph data are saved in a different file each day. The file name contains the date in numerical format. Graph data files are never overwritten. Note that traps are always saved in a single file per day format Graph data are saved in a file until it reaches 1 Mbytes. The file name contains an index from 1 to the value of Max history files per Graph. Graph data files are overwritten after reaching the Max history files per Graph index value. Table 2-4: Log Settings dialog box parameters 2-15

30 CXMon User Guide Parameter Max history files per Graph Min free disk space Set log path Description The maximum number of files that will be created for each graph. Each file is limited to 1 MB. The time it takes to reach the 1 MB limit depends on the Refresh rate configured. When the Refresh Rate is set to 5 seconds, each 1 MB file has around 2 days of data. All logging will automatically stop when the minimum free disk space value is reached. Used to define the location of log files. NOTE: The path is changed immediately for the current CXMon session. Delete logs Used to delete log files. NOTE: Only the logs for the current CXMon session will be deleted. Table 2-4: Log Settings dialog box parameters 2-16

31 Installing CXMon Configuring the Graph Display Options For each graph (with the exception of the Discards graph), it is possible to customize some fields. To clear the graph of its data, right-click the graph and select Clear Graph. This command clears the contents of the current graph. The next value will be plotted at the far left of the graph and the time (X-Axis) will be updated so that the current time is placed at the far left. To access the settings dialog box, right-click the graph and select Graph Settings. Figure 2-9: Graph Settings dialog box Parameter Grid Display Refresh Rate Display period Description Enable or disable the display of the grid for the selected graph. Defines the graph refresh rate in seconds for the selected graph, overriding the Global Refresh Rate. Choices are: 5 secs (default value), 10 secs, 30 secs and 60 secs. This parameter sets the visible period, when plotting the selected graph. When the Display period is greater than the default value for the current Refresh rate, CXMon will average as many graph points needed to show the desired display period. Choices are: Refresh Rate of 5 secs: 15 mins, 1 hour, 4 hours, 12 hours and 24 hours. Refresh Rate of 10 secs: 30 mins, 1 hour, 4 hours, 12 hours and 24 hours. Refresh Rate of 30 secs: 90 mins, 3 hours, 6 hours, 12 hours and 24 hours. Refresh Rate of 60 secs: 3 hours, 6 hours, 9 hours, 12 hours and 24 hours. Table 2-5: Graph Settings parameters 2-17

32 CXMon User Guide 2.7 CXMon Authorization Key Management The CXMon application is supplied as a trial program that can be tested for a fixed duration. During this trial period, the software is fully functional and can monitor the maximum allowed CX devices (remember that in the CX2000, each CPU is considered a device of its own). After installing CXMon, you must switch the trial version of CXMon to the valid licensed version. The figure below presents an overview of these steps: Customer opens CXMon on a trial basis. CXMon can be use for the duration of the trial (30 days) (1) Trial ends or Customer buys CXMon.Customer obtains site code from Licensing Configuration Window. (2) Customer sends site code to Memotec, requesting license authorization to use CXMon. Memotec generates site key. (3) 4) Customer enters site key into CXMon License Configuration Window and receives license authorization message. Memotec sends site key to customer. Figure 2-10: Overview of CXMon Licensing Process The following procedure assumes that the trial period has expired and you have purchased a full version of CXMon: 1. When you launch the CXMon application, the splash screen appears. Figure 2-11: CXMon Application Splash Screen 2-18

33 Installing CXMon 2. Press Enter while the splash screen is visible to access the License Configuration dialog box. The License Configuration dialog box also appears when the trial license has expired. Figure 2-12: License Configuration dialog box The License Configuration dialog box provides the user with a site code, which is based on a special internal hardware signature that is unique to the computer on which CXMon is installed. Memotec generates a site key from the site code. This site key is only valid for the PC where the site code was generated and the key is then sent to the customer. NOTE: If you do not have a Site Key, send an with your Site Code to [email protected]. 3. Enter the authorization key for your product in the Site Key field and click Validate. WARNING: CXMon automatically tracks restrictions in terms of days and/or number of CX devices to be monitored. The license is uniquely specific to the computer on which the application runs. If you try to copy the program and its license files to another computer, the license becomes invalid on that machine and does not allow access. A mechanism is provided to allow the transfer of a license from one PC to 2-19

34 CXMon User Guide another. For more information, see Transferring the CXMon License Key on page The registered keys remain on the system and are maintained through CXMon un-installation, as long as you do not modify the files remaining in the installation directory in any way Transferring the CXMon License Key You can transfer CXMon licenses using either of the following methods: Direct License Transfer: move a license from a local or networked directory to another area. For more information, see Direct License Transfers on page Removable memory media: move a license from one PC to another using a floppy disk, USB memory device, or Flash card reader. For more information, see Removable Memory Media License Transfers on page Direct License Transfers Direct license transfers move any type of license from one location on your PC to another. The Transfer To Directory command requests a directory path to an existing, unlicensed copy of the same product on your client s hard drive before transferring the license from the source directory to the target. This target directory must either be local to the source directory or connected through a network drive. For example, you may want to move a program with a valid fixed license from C:\Program Files\Memotec\CXMon to D:\Memotec\Application. To directly transfer a licence between workstations, follow these steps: 1. Install the CXMon application to D:\Memotec\Application and launch it. 2-20

35 Installing CXMon 2. When the CXMon splash screen appears, press Enter to display the License Configuration dialog box. Figure 2-13: License Configuration dialog box 3. From the License Configuration dialog box, select the License > Transfer to directory command. A wizard launches to help you to transfer the CXMon license to another location. 4. Click Next to continue. A file browser dialog box appears. 5. Navigate to the D:\Memotec\Application folder, select the new CXMon.EXE program filename, and press Enter. The CXMon application in D:\Memotec\Application now has the license that was previously assigned to the original program in C:\Program Files\Memotec\CXMon. Removable Memory Media License Transfers This type of operation transfers a license from an existing authorized copy of an application on one computer to an unauthorized copy of the product on a second computer. The transfer process does not jeopardize your license in any way and is completely secure because the removable memory media is registered to a specific PC in a specific location. This ensures the license can only be transferred to the target PC you specify. For example, you want to transfer the license for Memotec CXMon program from PC-1 to PC-2. In this example, a floppy disk is used. To transfer a license using removable media, follow these steps: 2-21

36 CXMon User Guide NOTE: In this procedure, the source workstation is called PC-1 and the destination workstation is called PC Ensure that you have an authorized copy of the application on PC-1, an unauthorized copy of the application on PC-2, and a removable storage device connected to PC Start the CXMon appplication on PC-2 and press Enter when the CXMon splash screen appears. The License Configuration dialog box appears: Figure 2-14: Unauthorized Program running on PC-2 3. Select the License > Transfer in from another computer command. The Transfer License In wizard dialog appears prompting you for a path (the first step of three). 4. Type the path to your removable storage device, or use the Browse button to select it, and click Next. The program imprints its registration on the removable storage device and the system displays the following window: 2-22

37 Installing CXMon S Figure 2-15: Step 2 of the Transfer License wizard If you can leave the program running, go to Step 5. to continue. If you need to close the PC-2 program while you work with the PC-1 program, click the Continue Transfer Later button. The system displays a popup message. Click OK to acknowledge the above popup and the wizard terminates. 5. Remove the removable storage device from PC-2 and connect it to PC Start the CXMon appplication on PC-2 and press Enter when the CXMon splash screen appears. 7. Select the License > Transfer out to another computer command. The Transfer License Out wizard dialog appears prompting you for a path (the first step of two). 8. Type the path to your removable storage device, or use the Browse button to select it, and click Next. The program reads the registration imprint file and then writes a matching file to the removable storage device, decrementing the license count at the source or discontinuing it (if it is a single user license). 9. Remove the removable storage device from PC-1, reconnect it to PC-2, and relaunch the CXMon appplication on PC-2. If you did not exit from the program in Step 4., the wizard process is complete and you can click Finish. 2-23

38 CXMon User Guide If you exited the program in Step 4., the following window appears when you relaunch the CXMon appplication: 10. To continue this operation, click Continue existing transfer. 11. Type the path to your removable storage device, or use Browse to select it, and click Next. 12. Click Finish to complete the process. Figure 2-16: Transfer in Progress Wizard The License Configuration window on PC-2 appears, showing that you are authorized to use it. 2-24

39 3 Monitoring a CX Device This chapter explains how to launch and configure CXMon. It also explains how to add CX devices to CXMon and how to monitor these devices. 3-1

40 CXMon User Guide 3.1 Configuring CX Devices The CX devices that are monitored by CXMon require some basic configuration. You can use Memotec s CXTool application to perform this configuration. The table below summarizes the minimum CXTool version required for each type of application. Application Minimum CXTool required for CXMon support Abis/Ater on CX CXTool 4.3.5B DCME on CX CXTool Abis/Ater with EDGEPlus on CX CXTool 5.0.0u Abis/Ater with EDGEPlus and DCME on CX-U CXTool EDGEPlus/DCME on C flavor (CX/CX-U) ATM/TDM/IMA (CX-U) Abis/Ater with AbisXpress (CX-U) CXTool 5.2.0k CXTool k CXTool k Table 3-1: CXTool version supporting CXMon NOTE: CXMon is not supported on all the devices supported by CXTool. See the System Limitations on page 1-5 for the list of device types supported by CXMon. For more information about using CXTool, refer to the CXTool User Guide and CXTool Online Help. You must have at least one new or existing configuration file to configure your CX device. To configure your CX devices with CXTool, follow these steps: 1. Launch CXTool and open the profile for your CX device. 2. Using the panel on the left, open System folder, double-click one of the icons, and select Modify from the pop-up menu. The System Information dialog box appears. 3-2

41 Monitoring a CX Device 3. Select the SNMP tab and check that the CXMon Enabled is checked. Collect SNMP traps with Trap Host Define the source IP address for all SNMP packets. Figure 3-1: SNMP configuration in CXTool 4. In order to collect SNMP Traps, you must create a Trap Host entry with the IP address of the PC that has CXMon installed. This parameter defines the destination IP address for all SNMP trap packets from this CX. You can configure multiple destinations if you are using multiple SNMP Monitoring systems. 5. Configure the SNMP Source Address with the required IP address. This parameter defines the source IP address for all SNMP packets originating from this CX device. Normally the IP address with the shortest path to the monitoring PC is configured. To set the source IP address, select the right IP interface (usually the one on the same network as the monitoring PC) from the list. NOTE: The next step only applies to the CX2000 device, so if you do not have this device, skip to the next step. 3-3

42 CXMon User Guide 6. The CX2000 requires that a unique IP address be assigned to each CPU. If you cannot have an Ethernet card in each CPU, you can configure virtual IP addresses. This is accomplished by configuring a Vista Address for each CPU. Figure 3-2: Vista Addresses in CXTool The Vista Address will define the source address for all SNMP packets originating from this CX. This serves the same function as the Agent Interface Alias. All SNMP requests should match one of the configured Vista Address entries. 7. CXTool will automatically define the WAN Index for all DIM ports when configuration is made using either the FR WAN Trunk, IP WAN Trunk, or MLPPP WAN Trunk panels. But if the WAN is configured without using one of these panels then the WAN Index must be added manually (in the panel on the left, double-click the Advanced folder and double-click the Add-On Scripts message on the right panel) using the following command for each DIM interface: vpstats:15 wanidx=11, vrsridx=1 In this example the DIM interface is located in slot 8, port 1 (15) and the WAN interface is located in slot 1, port 1 (11). The VRSR used by the DIM traffic is VRSR:1. The vpstats and wanidx values identify the slot and port of the corresponding WAN interface used by the DIM port for transport to the remote location. 3-4

43 Monitoring a CX Device NOTE: The WAN interface must be on the same CPU as the DIM Port. For more information about CXTool configuration, refer to the following Memotec documents: CXTool User Guide CXTool Online Help Vpstats index values The vpstats values identify the slot and port of the corresponding WAN interface used by the DIM port for transport to the remote location. Vpstats index DIM Card on CX T1/E1 ports on CX-U 1 & 2 Slot 1, Port 1 & 2 Port 1 & 2 3 & 4 Slot 2, Port 1& 2 Port 3 & 4 5 & 6 Slot 3, Port 1& 2 Port 5 & 6 (CX-U1220/1240/1280) 7 & 8 Slot 4, Port 1& 2 Port 7 & 8 (CX-U1220/1240/1280) 9 & 10 Slot 5, Port 1& 2 Port 9 & 10 (CX-U1220/1240/1280) 11 & 12 Slot 6, Port 1& 2 Port 11 & 12 (CX-U1220/1240/1280) 13 & 14 Slot 7, Port 1& 2 N/A 15 & 16 Slot 8, Port 1& 2 N/A Table 3-2: vpstats index values 3-5

44 CXMon User Guide Vpstats wandix values The wanidx values identify the slot and port of the corresponding WAN interface used by the DIM port for transport to the remote location. Wanidx values Location (CX only) Location (CX-U only) 11 to 15 Slot 1, Port 1 to 5 11: onboard V35 card 21 to 25 Slot 2, Port 1 to 5 21: can be connected to any T1/ E1 interface (ports 1 to 12) 31 to 35 Slot 3, Port 1 to 5 31: can be connected to any T1/ E1 interface (ports 1 to 12) 41 to 45 Slot 4, Port 1 to 5 41: can be connected to any T1/ E1 interface (ports 1 to 12) 51 to 55 Slot 5, Port 1 to 5 N/A 61 to 65 Slot 6, Port 1 to 5 N/A 71 to 75 Slot 7, Port 1 to 5 N/A 81 to 85 Slot 8, Port 1 to 5 N/A 91 CX2000 Primary Bus Ethernet connection 92 Front Panel Ethernet connection N/A Fast Ethernet connection (Ethernet ports 1 to 5) Table 3-3: vpstats wanidx values Vpstats vrsr index values The vrsridx value identifies the VRSR entry used by this port, when over the WAN interface. It has the same value as the VRSR index value in the CX/CX-U configuration. vrsridx values Vrsr entry on CX Vrsr entry on CX-U 1 to 255 VRSR :1 to VRSR :256 VRSR :1 to VRSR :256 Table 3-4: vpstats vrsridx values 3-6

45 Monitoring a CX Device 3.2 Discovering CX Devices in WhatsUp Once you complete the installation process, you must add the CX devices in your network to the WhatsUp monitoring Map. To add the CX devices to the WhatsUp monitoring Map, follow these steps: 1. From the WhatsUp application, launch the New Device Discovery Wizard in one of two ways: Right-click the Map View and select New > New Device. Select File > Discover Devices. When prompted, enter/select the device s IP address. You should click the Advanced button to make sure that the SNMP monitor is selected. Figure 3-3: Launching device discovery in WUP/WUG 2. Select the IP range scan radio button and click Next. 3. Define the range of IP addresses to scan by typing the Start and End addresses and click Next. 4. Select Identify devices via SNMP, change the SNMP Read Communities to memotec, and click Next. NOTE: This step is necessary for WhatsUp to recognize the discovered devices as belonging to the created device type. 3-7

46 CXMon User Guide 5. From the Active Monitors to Scan dialog box, enable Interface and Ping checkboxes and click Next. The device discovery process will begin and can take several minutes to complete. When completed, a summary of the discovery process appears. 6. Using the checkboxes, enable or disable the devices that you intend to monitor and click Next. 7. In the Action Policy Selection dialog box, select Do not apply an action policy and click Next. 8. When the last dialog box displays a summary of the devices found, click Finish. The discovered devices should now be visible in the Map View. Figure 3-4: WUP Map with discovered Memotec CX/CX-U devices 3-8

47 Monitoring a CX Device 3.3 Starting the CXMon Application There are two ways to launch the CXMon application: From the Windows Start > Programs > Memotec menu From within the WhatsUp application The advantage to launching CXMon from within the WhatsUp application is that when you select a device and launch a CXMon session, the device s IP address is loaded automatically. If you launch a CXMon session from the Windows Start menu, you must enter the IP address manually in the CXMon - CX Device Information dialog box. To start a new CXMon session, follow these steps: 1. To start using CXMon, you can launch it in one of two ways: To launch CXMon from the Map View of WhatsUp, right-click a CX device and select CXMon from the pop-up menu. To launch CXMon as an independent application, select Start > Memotec > CXMon > CXMon. The CXMon - CX Device Information dialog box appears. Figure 3-5: Logging into the CXMon device 2. Enter the IP address and the SNMP Community information for the CX device and click OK. If this information appears by default, verify that it is accurate and click OK. 3-9

48 CXMon User Guide HINT: When you type the IP address, press the Spacebar to move from field to field. If you press Tab, the Read Community field will become selected, even if you have not finished entering the IP address. Normally this information does not require modification by the user. When you select OK, CXMon will connect to the CX device. If a problem occurs (device is not reachable), the Status panel displays an error message stating that there has been a connection timeout. 3-10

49 Monitoring a CX Device 3.4 Monitoring Device Data Once you launch CXMon (see Starting the CXMon Application on page 3-9), the main window displays the data coming in from our CX devices. Figure 3-6: CXMon main window The main CXMon panel is separated in six distinct sections: Device Information (see Device Information on page 3-12) Voice/GSM Traffic System Savings (see Voice/GSM Traffic System Savings on page 3-12) SNMP Traps (see SNMP Traps on page 3-13) User/E1 Port Monitor (see T1 Port/E1 Port Monitors on page 3-15) WAN Port Monitor (see WAN Port Monitor on page 3-16) WAN Port Details (see WAN Port Details on page 3-18) NOTE: To clear all the graphs in the CXMon window, select Settings > Clear All Graphs. All the graphs in the window will be reset and wiped clean. However, the recorded log data will be unaffected. 3-11

50 CXMon User Guide Device Information This section identifies the device being monitored. The following information is displayed: Figure 3-7: Device information panel Parameter IP Uptime Type Name Software Description Displays the IP address of the CX device that is used for monitoring. The IP address is also present in the application title. Displays the time elapsed since the last power up or restart of the CX device. The format is Day(s) Hours : Minutes : Seconds. Displays the CX device type (ex: CX900S Access Switch) Displays the name assigned to the CX device when configured. Displays the software revision currently running on the CX device. Table 3-5: Device information fields Voice/GSM Traffic System Savings The Global Device Savings graph gives you a real-time indication of the optimization performed by the CX device. Figure 3-8: Voice/GSM Traffic System Savings panel 3-12

51 Monitoring a CX Device Parameter Graph Legend Description The graph of the global savings displays the bandwidth saving over the WAN traffic compared to the DIM traffic. A value of 0% indicates that no bandwidth saving is realized (possible when the traffic detected can not be optimized by the CX). Larger values indicate a bandwidth saving. The TX values are graphed using a blue line while the RX values are graphed using a green area. The current Global Savings values for both the transmit and receive directions are displayed at the top-right of the graph. The TX values are blue while the RX values are green. Table 3-6: Voice/GSM Traffic System Savings Information You can right-click the graph to change the graph settings or clear the graph (see Configuring the Graph Display Options on page 2-17 for more details) SNMP Traps The SNMP Traps section lists all traps that have been received from the CX device being monitored. Each field is a MIB object name followed by its value. For more information on the meaning of each value, you can search for the object name in the Command line help (provided on the Memotec CD in the \CommandLineHelp folder). Figure 3-9: SNMP Traps panel 3-13

52 CXMon User Guide For each trap, the following fields are present: Parameter Date Time Trap Data Description The date the trap was recorded. Format is MM/DD/YYYY The time the trap was recorded. Format is HH:MM:SS, using a 24-hour format Name of the specific trap (as defined in the Memotec MIB files). A description of the activity recorded by the trap. Table 3-7: SNMP Traps fields Each field (column) in the SNMP traps window can be resized by clicking on the column border in the header (mouse pointer will change to ) and dragging the column delimiter to the new position. NOTE: The most recent traps appear at the bottom of the list. Drag the column border left or right. Figure 3-10: Resizing the Trap Columns HINT: If a column is too narrow to display all the trap information, you can doubleclick the column border (on the right side) to reset the display width. To clear the list of traps, select Settings > Clear SNMP Traps. 3-14

53 Monitoring a CX Device T1 Port/E1 Port Monitors The port status, shown as a round LED, displays its statistics using the colors listed in Table 3-8. Up to 16 ports can be displayed. Figure 3-11: T1 Port/E1 Port Monitors panel Port LED Color White Gray Green Yellow Blue Red Description The port is not configured or not present. When a CX device is no longer reachable by CXMon, the port status will change to white. The port is present and not configured or not enabled The port is up and synchronized Yellow alarm. Indicates a Far end Loss of Framing. Blue alarm. Indicates an AIS failure Red alarm. Applies to all other situations Table 3-8: Port LED color description If you click a port LED (ex: ) when it is Green, Yellow, Blue, or Red, the User Port Details dialog box appears to display more detailed information on the selected port. For more information on the User Port Details panel, see Viewing Detailed Information on a User Port on page NOTE: The User Port Details panel cannot be open for T1/E1 ports used as a WAN or ATM port. When the monitored CX device is an EDGEPlus product used for Abis/Ater optimization, a special MAP button ( ) will appear next to the port LED. By clicking this button, you can open the Traffic Mapping dialog box. For more information on the Traffic Mapping dialog box, see Reading the Traffic Map on page

54 CXMon User Guide WAN Port Monitor This graph displays the number of kilobytes that are sent and received across the selected Wide Area Network (WAN) port. You can view a summary of this information on the WAN Port Details panel (see WAN Port Details on page 3-18). Figure 3-12: WAN Port Monitor panel Parameter WAN Selector Description The user can select the WAN interface to monitor using a drop-down list. The bandwidth present on the selected interface is graphed. There are two types of WAN available: Ports: the ports are represented by 2 digits, the first being equal to the slot number and the second being equal to the port on the slot (normally 1). For example, 11 is the card in slot 1 while 92 is the onboard Ethernet port. Because the CX-U doesn t have any slots, the meaning of the port value is a little different: while 92 is also the onboard Ethernet port, the ports 21, 31 and 41 represents internal resources used to carry data from any T1/E1 ports. For more information, see Vpstats wandix values on page 3-6. VRSR: the VRSR are represented by the string VR followed by the VRSR index. For example, VR:1 will select the VRSR:1 in the CX. NOTE: The VRSR entry will show only the voice traffic coming from the DSPs (speech, HDLC, fax/modem, etc). The port entry will show all the traffic on that port, including voice traffic coming from the DSPs but also the traffic routed using a BOP, IP traffic, traffic from another card, etc. Table 3-9: WAN Port Monitor Fields 3-16

55 Monitoring a CX Device Parameter WAN Graph Legend WAN Utilization Meter bar Description This graph displays the bandwidth (in kbps) over the WAN, for the selected WAN (port or VRSR). The TX values are graphed using a blue line while the RX values are graphed using a green area. The legend on the top-right of the graph displays the current WAN utilization percentage. This is equal to the current values for Rx/Tx in the Meter Bar. A meter bar, located at the right of the graph, displays a ratio of the current bandwidth compared to the maximum bandwidth possible on the interface. As the value nears the maximum speed, the color of the bar will go from green to yellow (between 80% and 90%) and to red (above 90%), to show when there is congestion. The maximum possible bandwidth on the interface will be determined by CXMon itself, for WAN entry representing a port. For VRSR entry, the user will need to enter the maximum possible bandwidth using the Meter Bar Settings dialog box. NOTE: The Meter Bar Settings dialog box can also be used to customize the maximum possible bandwidth of a port entry. Buffer Free Displays the number of available I/O buffers as a percentage. This value will go down when there is a burst of traffic or during periods of congestion. Table 3-9: WAN Port Monitor Fields 3-17

56 CXMon User Guide WAN Port Details This panel displays a summary of the various counters that apply to the selected Wide Area Network (WAN) interface. This information tracks the amount of sent/received data, as well as the number of sent/received packets that are discarded or that are in error. The following information is displayed: Figure 3-13: WAN Port Details panel Parameter Interface Description Port State Port State Change Serial Port, Ethernet Port, VR Serial Port Serial Port Displays the current port status. portup: Port is up portdown: Port is down portshutdown: For backup, port has been shut down by software PortDownBadConfiguration: Port is down due to a configuration conflict portoutoforder: Port is out of order due to a hardware problem Displays the total number of times that the port state has changed. Clock State Serial Port txclockdown: Transmit clock is down txclockup: Transmit clock is up Clock State Change Serial Port Displays the total number of times that the clock state has changed. Tx Kbps Serial & Ethernet Port Displays current average Kilobit per second rate of transmission for the port. Table 3-10: WAN Port Details fields 3-18

57 Monitoring a CX Device Parameter Interface Description Rx Kbps Serial & Ethernet Port, VR Displays current average Kilobit per second rate of reception for the port. Tx bps max Serial & Ethernet Port, VR Displays maximum average Kilobit per second rate of transmission for the port. Rx bps max Serial & Ethernet Port, VR Displays maximum average Kilobit per second rate of reception for the port. Rx Bad NIB frames Rx Bad CRC frames Serial Port Serial Port Displays the total number of frames received that did not have eight bits per byte. Poor clocking normally causes non-integral Byte frames. Displays the total number of bad CRC frames received by the port. Cyclic Redundancy Check errors are normally caused by poor line conditions. Tx RST Discard Serial Port Displays the total number of frames discarded by this port due to loss of clocking, congestion or hardware failure. In Discard Ethernet Port Displays the total number of frames received and discarded due to an error condition. i.e. port busy, lack of receive buffers, frames received while port not bound to an upper layer. In Errors Ethernet Port Displays the total number of error frames received by this port. Errors include overruns, non-octet errors, and CRC errors. Out Discard Ethernet Port Displays the total number of frames which were unsuccessfully transmitted due to a lack of transmit buffers. Out Errors Ethernet Port Displays the total number of transmit errors on this port. Includes Transmitter Underuns, Carrier sense Lost during frame transmission, Attempts Limits Expires and Late Collisions. Table 3-10: WAN Port Details fields 3-19

58 CXMon User Guide Parameter Interface Description Serial & Ethernet Port, VR Clear the statistics in the CX device itself. The field Last Cleared at will then indicate the exact time the statistics were cleared. Because the CX device itself clears the statistics, there is a small delay before the cleared statistics appear. Table 3-10: WAN Port Details fields Viewing the Log Usage Statistics The Log Status dialog box displays the current log usage. To open it, select Settings > Log Status. Figure 3-14: Log Status dialog box Parameter Current log path Description Displays the full directory path for all log files. NOTE: It is possible to see the full path by clicking it and using the arrow keys. Free disk space Displays the amount of free disk space for the drive defined in the log path. NOTE: All logging will stop when this value reaches the Min free disk space setting. Size of log folder Current device log size Displays the total size of the log folder. This size includes all logs that have been created for all devices. Displays the total size of all logs for the device being monitored for the CXMon session. Table 3-11: Log Status parameters 3-20

59 Monitoring a CX Device Reading the Traffic Map The Traffic Mapping dialog box displays the current traffic type of each timeslot on the selected port. The information is showed graphically, to make it easier to see the traffic present. The traffic present is read from the CX device when you open the window. To open the Traffic Mapping dialog box, click the map button next to the port in the T1/ E1 Port Monitors panel. To update the map, click Refresh. Table 3-12: Traffic Mapping dialog box The upper portion of the window shows all the port s timeslots, using a unique color for each type of traffic. The Timeslot #1 is the first one at the top while timeslot #31 is the last one, at the bottom. Each line represents a timeslot and each timeslot can be subdivided in 16k TCH or in 8K TCH, depending on the traffic present. NOTE: The appearance of this dialog box can change depending on active port mode. The supported modes are EDGEPlus and AbisXpress. 3-21

60 CXMon User Guide Traffic Type Description Mode This TCH has no traffic present and is in Idle. A single 16K TCH and two 8K TCH in Idle will have the same representation. Four 16k TCH: Eight 8k TCH: HDLC traffic is present on this TCH (16k) or on this timeslot (64k). 64k HDLC: Two 32k HDLC: Four 16k HDLC: When 16k HDLC is detected, the other 16k TCH on the same timeslot could have a different traffic type. Ex: (Single 16k HDLC TCH, others are Idle) 16k Speech traffic is present. The type of speech encoding present can be: FR, EFR, HR-16k and AMR- 16k. Ex: (Two 16k Speech TCH, two Idle TCH) All modes EDGEPlus AbisXpress EDGEPlus AbisXpress 8k Speech traffic is present. The type of speech encoding present can be: HR-8k and AMR-8k. When a single 8k TCH within a 16k TCH is in HR speech, the Traffic Mapping dialog box displays as: (Half of a 16k is in HR) If two consecutive 8k TCH are in speech, the Traffic Mapping dialog box displays as: EDGEPlus AbisXpress NOTE: The 8k TCH are not visually separated (there are no lines in the middle of the dark green area). The dark green color indicates that this is 8k speech, not 16k speech. The 8K speech traffic identified in this timeslot was switched locally to save WAN bandwidth. The 16K speech traffic identified in this timeslot was switched locally to save WAN bandwidth. EDGEPlus EDGEPlus Table 3-13: Traffic Types 3-22

61 Monitoring a CX Device Traffic Type Description Mode Traffic in this timeslot was identified as Edge traffic. Only the entire timeslot can be identified as Edge pool. Ex: Unrecognized traffic is present in this timeslot. It can also apply to a 16k or an 8k TCH. 64k Others: 16k Others: 8k Others: When the CX device does not recognize any traffic, the timeslot appears as gray. Ex: This can happen when the port is down or disconnected, the timeslot is not configured or when the CX device is mis-configured. EDGEPlus EDGEPlus AbisXpress All modes Table 3-13: Traffic Types The lower portion of the Traffic Mapping dialog box summarizes the different types of traffic present on a specific port. The availability of each counter depends on the active mode. Counter 16k Speech tch 8k Speech tch 16k IDLE tch 8k IDLE tch 64k Others tch 8k Local SW. 16k Local SW. 16k Others tch 8k Others tch 16k Sig tch 32k Sig tch Description Number of 16k TCH with speech traffic (FR, EFR, HR-16k and AMR-16k). Number of 16k TCH with speech traffic (HR-8k and AMR-8k). Number of 16k TCH with Idle traffic (no traffic). Number of 8k TCH with Idle traffic (no traffic). Number of 64k timeslots with unrecognized traffic. Number of 8k TCH (speech traffic) with locally switched traffic. Number of 16k TCH (speech traffic) with locally switched traffic. Number of 16k TCH with unrecognized traffic. Number of 8k TCH with unrecognized traffic. Number of 16k TCH with HDLC traffic. Number of 32k TCH with HDLC traffic. Table 3-14: Counters in Traffic Mapping dialog box 3-23

62 CXMon User Guide Counter 64k Sig tch 64k Edge Pool Description Number of 64k timeslots with HDLC traffic. Number of 64k timeslots with Edge traffic present. Note that the traffic type present in each TCH of a timeslot with Edge detection will cause the other TCH counters to increase. Example: when one timeslot with one 16k Others TCH and three 16k Idle TCH is identified as part of a 64k Edge Pool, it produces the following results: 16k Others TCH=1, 16k IDLE TCH=3 and 64k Edge Pool=1. Table 3-14: Counters in Traffic Mapping dialog box 3-24

63 Monitoring a CX Device 3.5 Viewing Detailed Information on a User Port The User Port Details dialog box displays more detailed traffic and alarm information on a specific port on you CX device. You can display this dialog box appears when you click one of the T1/E1 Port Monitor buttons from the main window (see T1 Port/E1 Port Monitors on page 3-15). The port number is displayed in the window title. Figure 3-15: User Port Details for EDGEPlus Mode What appears in this dialog box will depend on the type of application running on the port. The table below lists the five different application modes: Application Description Port Type GSM Abis/Ater EDGEPlus GSM Abis or Ater link with software revision below 5.0 GSM Abis or Ater link with software revision 5.0 or above Legacy Abis EDGEPlus DCME DCME link DCME ATM/TDM/IMA ATM/IMA link ATM/TDM/IMA Table 3-15: Different Mode supported by User Port Details window 3-25

64 CXMon User Guide Application Description Port Type AbisXpress GSM Abis or Ater link with U2.0 software or higher. AbisXpress Table 3-15: Different Mode supported by User Port Details window Click an active port (in green or red) to display the User Port Graphs. The map button launches the Traffic Mapping dialog box (see Reading the Traffic Map on page 3-21). Figure 3-16: T1/E1 Port Monitor buttons The following graphs are displayed for the selected port: Traffic: see Displaying Ratio of Traffic Types on a Port on page Silence within Voice: see Displaying the ratio of duplicated silence packets on page Voice within Abis Traffic: see Displaying the Ratio of Voice Packets on page Abis Interface Utilization: see Displaying the ratio of TRAU/TCH Channels on page Traffic Optimization: see Displaying the Ratio of Traffic Compression on page WAN Discards Level Distribution: see Displaying the ratio of discarded voice packets on page Discard Level: see Displaying the Current Discard Level on page

65 Monitoring a CX Device Displaying Ratio of Traffic Types on a Port Th Traffic graph displays the ratio of traffic types detected on the current port. This graph stacks each traffic type on top of each other, identifying each type using a unique color. Unused portion of the port. Sum of all traffic type = utilization ratio Figure 3-17: User Port Details: Traffic graph The thickness of the region for a given traffic type depends on the number of timeslots or TCH with this traffic. The sum of all traffic types is equal to the amount that the port has in use. The utilization ratio represents the ratio of the port currently in use. It represents the ratio of non-idle TCH on the port, in EDGEPlus mode. In DCME mode, the utilization ratio represents the ratio of configured timeslots and is always 100%. NOTE: Non-configured timeslots are NOT included in the ratio. The traffic types for EDGEPlus mode are as follows: Sig: HDLC traffic (16k, 32k and 64k) traffic 16k speech: FR, EFR, HR-16k, AMR-16k traffic 8k speech: HR-8k, AMR-8k traffic Edge: Timeslots with Edge traffic Others: Not optimized traffic The traffic types for DCME mode are as follows: Data: Fax/Modem/V.110 traffic High BW: speech traffic, G729 (8 kbps) and all AMR codec with rates greater than 8kbps Low BW: speech traffic, G /5.3 kbps and all AMR codec with rates less than 8kbps 3-27

66 CXMon User Guide NOTE: This graph doesn t represent the bandwidth used by each traffic type. It represents the ratio of timeslots (or TCH) with the specified traffic type. The results of the Traffic Graph do not apply to GSM Abis Ater mode. The traffic types for AbisXpress mode are as follows: Sig: HDLC traffic (16k, 32k and 64k) traffic 16k speech: FR, EFR, HR-16k, AMR-16k traffic 8k speech: HR-8k, AMR-8k traffic Others: Not optimized traffic The traffic type for ATM/TDM/IMA mode is Non-idle cell traffic Displaying the ratio of duplicated silence packets This graph displays the ratio, as a percentage, of duplicate silence packets on the current port compared to the total number of speech packets. Figure 3-18: User Port Details: Silence within Voice Traffic Ratio graph A higher ratio will result in higher bandwidth savings because duplicate silence packets have the highest compression ratio. NOTE: The Silence within Voice Graph does not apply to ATM/TDM/IMA mode. 3-28

67 Monitoring a CX Device Displaying the Ratio of Voice Packets This graph displays the ratio, as a percentage, of voice packets (speech, silence and duplicate silence) on the current port compared to the total number of packets (all types except idle packets). A higher ratio will result in higher bandwidth savings because voice packets have a high compression ratio. NOTE: The Voice within Abis Traffic Graph applies only to the GSM Abis/Ater modes. GSM Abis/Ater only applies to CX devices with firmware to 5.1. In EdgePlus or AbisXpress mode, this graph is replaced by the Traffic graph (see Displaying Ratio of Traffic Types on a Port on page 3-27) Displaying the ratio of TRAU/TCH Channels This graph displays the ratio, as a percentage, of TRAU/TCH channels that are in use on the current port compared to the total number of TRAU/TCH channels. A TRAU/TCH channel that is transmitting or receiving non-idle packets is said to be transmitting. A high ratio indicates that most TRAU/TCH channels are used. NOTE: The Abis Interface Utilization Graph applies only to the GSM Abis/Ater modes. GSM Abis/Ater only applies to CX devices with firmware to 5.1. In EdgePlus or AbisXpress mode, this graph is replaced by the Traffic graph (see Displaying Ratio of Traffic Types on a Port on page 3-27). 3-29

68 CXMon User Guide Displaying the Ratio of Traffic Compression This graph displays the traffic compression ratio, as a percentage, of the GSM Abis traffic optimization made by the CX device on the current port versus the traffic without any optimization. Figure 3-19: User Port Details: Traffic Optimization Ratio graph A value of 0% indicates that no compression is made. Higher values indicate a reduction in bandwidth. NOTE: The Traffic Optimization Graph applies to all modes Displaying the ratio of discarded voice packets This graph displays the ratio of voice packets that have been discarded by the bandwidth management mechanism for each of the levels of congestion. A large percentage of discards for levels 6 and 7 indicate that the WAN bandwidth is insufficient. Figure 3-20: WAN Discards Level Distribution graph 3-30

69 Monitoring a CX Device NOTE: The WAN Discards Level Distribution Graph applies to all modes. Congestion Level 1 Level 2 Description The first three discard levels do not have a significant impact on the voice quality and are therefore displayed in green. Level 3 Level 4 Level 5 Level 6 Level 7 Discard level 4 and 5 have a noticeable impact on voice quality and are therefore displayed in yellow. The last two discard levels significantly reduce the voice quality and are therefore displayed in red. Table 3-16: Discard Level legend Displaying the Current Discard Level This graph displays the current discard level used by the bandwidth management mechanism. Figure 3-21: Current Discard Level graph 0: No discard performed or bandwidth management is disabled. 1: 2.5% of speech packets are discarded. 2: 5% of speech packets are discarded. 3: 10% of speech packets are discarded. 4: 14% of speech packets are discarded. 5: 20% of speech packets are discarded. 6: 25% of speech packets are discarded. 7: 33% of speech packets are discarded. 3-31

70 CXMon User Guide Error Counters This window displays the following error counters for the selected port: Parameter Loss Sync count Description Displays the number of seconds that synchronization was lost on this line interface, since power-up or since the statistics were cleared. Loss of carrier count Displays the number of seconds that the carrier was lost on this line interface, since power-up or since the statistics were cleared. Clock Slip count Loss of Tx clock count Delay Drift Count Displays the number of times that the clock slipped when the elastic store was disabled on the receive side. Otherwise, it displays the number of times that a frame slip had occurred, since power-up or since the statistics were cleared. Displays the number of seconds that the transmit clock was lost on this line interface, since power-up or since the statistics were cleared. Displays the number of jitter buffer adjustments that are made when the buffer level exceeds the threshold. Table 3-17: Port Error Counters in User Port Details Statistics in EDGEPlus mode In the EDGEPlus mode, some slightly different statistics will be displayed: Parameter Description Speech Pkts Tx Speech Pkts Rx Silence Pkts Tx Silence Pkts Rx Dup (Duplicate) Silence Pkts Tx Dup (Duplicate) Silence Pkts Rx Displays the number of speech packets transmitted by the T1/E1 port. The 16k column includes all FR, EFR, HR-16k and AMR-16k traffic while the 8k column includes HR-8k and AMR-8k traffic. Displays the number of speech packets received by the T1/E1 port. The 16k column includes all FR, EFR, HR-16k and AMR-16k traffic while the 8k column includes HR-8k and AMR-8k traffic. Displays the number of silence packets transmitted by the T1/E1 port. The 16k column includes all FR, EFR, HR-16k and AMR-16k traffic while the 8k column includes HR-8k and AMR-8k traffic. Displays the number of silence packets received by the T1/E1 port. The 16k column includes all FR, EFR, HR-16k and AMR-16k traffic while the 8k column includes HR-8k and AMR-8k traffic. Displays the number of duplicate silence packets transmitted by the T1/E1 port. (See note 1 below) Displays the number of duplicate silence packets received by the T1/ E1 port. (See note 1 below) Table 3-18: Packet Counters in EDGEPlus Mode 3-32

71 Monitoring a CX Device Parameter Edge Pkts Tx Edge Pkts Rx Others Pkts Tx 8k/16k/64k Others Pkts Rx 8k/16k/64k Sig Pkts Tx 16k/32k/64k Sig Pkts Rx 16k/32k/64k Description Displays the number of Others packets (both 16k and 64k) transmitted by the T1/E1 port, on timeslots identify as having Edge data traffic. Displays the number of Others packets (both 16k and 64k) received by the T1/E1 port, on timeslots identify as having Edge data traffic. Displays the number of Others packets (with unrecognized packet traffic) transmitted by the T1/E1 port. (See note 2 below). Packets in 8k, 16k and 64k format are included. Number of packets of Others packets (with unrecognized packet traffic) received from the T1/E1 port. This traffic type has no optimization. (See note 2 below). Packets in 8k, 16k and 64k format are included. Displays the number of HDLC 16kbps, 32 kbps and 64kbps packets transmitted by the T1/E1 port. Displays the number of HDLC 16kbps, 32 kbps and 64kbps packets received by the T1/E1 port. Table 3-18: Packet Counters in EDGEPlus Mode NOTE: When two or more silence packets are detected, a duplicate silence packet is used in place of silence packets to reduce bandwidth. The first silence packet in each sequence is preserved. GPRS (General Packet Radio Service) and EGPRS (GPRS over EDGE, Enhanced Data for Global Evolution) are counted as unknown packets. In addition, channels that are configured for the wrong traffic type will produce unknown packets. For example, signaling packets that are transmitted on a channel that is configured for voice and 16K signaling on a 64K signaling channel, will both be counted as unknown packets. Statistics in DCME mode In DCME mode, some slightly different statistics will be displayed: Parameter Description High BW Speech Tx Displays the number of G.729 8kbps, G kbps, AMR 10.2kbps and AMR 12.2kbps speech packets transmitted by the T1/E1 port. Table 3-19: Packet Counters in DCME Mode 3-33

72 CXMon User Guide Parameter High BW Speech Rx Low BW Speech Tx Low BW Speech Rx High BW Silence Tx High BW Silence Rx Low BW Silence Tx Low BW Silence Rx Data pkts Tx Data pkts Rx Description Displays the number of G.729 8kbps, G kbps, AMR 10.2kbps and AMR 12.2kbps speech packets received by the T1/E1 port. Displays the number of G kbps, G kbps, AMR 4.75kbps, AMR 5.15kbps, AMR 5.90kbps, AMR 6.7kbps, AMR 7.4kbps and AMR 7.95kbps speech packets transmitted by the T1/E1 port. Displays the number of G kbps, G kbps, AMR 4.75kbps, AMR 5.15kbps, AMR 5.90kbps, AMR 6.7kbps, AMR 7.4kbps and AMR 7.95kbps speech packets received by the T1/E1 port. Displays the number of G.729 8kbps, G kbps, AMR 10.2kbps and AMR 12.2kbps silence packets transmitted by the T1/E1 port. Displays the number of G.729 8kbps, G kbps, AMR 10.2kbps and AMR 12.2kbps silence packets received by the T1/E1 port. Displays the number of G kbps, G kbps, AMR 4.75kbps, AMR 5.15kbps, AMR 5.90kbps, AMR 6.7kbps, AMR 7.4kbps and AMR 7.95kbps silence packets transmitted by the T1/E1 port. Displays the number of G kbps, G kbps, AMR 4.75kbps, AMR 5.15kbps, AMR 5.90kbps, AMR 6.7kbps, AMR 7.4kbps and AMR 7.95kbps silence packets received by the T1/E1 port. Displays the number of Data packets (Fax, modem and V.110) transmitted by the T1/E1 port. Displays the number of Data packets (Fax, modem and V.110) received by the T1/E1 port. Table 3-19: Packet Counters in DCME Mode 3-34

73 Monitoring a CX Device Statistic counters in GSM Abis/Ater mode This window displays the following statistics counters for the selected port (GSM Abis/ Ater Mode only) Counter Description Speech Tx Speech Rx Idle Tx Idle Rx Silence Tx Silence Rx Dup (Duplicate) Silence Tx Dup (Duplicate) Silence Rx HDLC Tx HDLC Rx Unknown Tx Unknown Rx Displays the number of speech (GSM FR and EFR) packets transmitted by the DIM card. Displays the number of speech (GSM FR and EFR) packets received by the DIM card. Displays the number of idle packets transmitted by the DIM card. Displays the number of idle packets received by the DIM card. Displays the number of silence packets transmitted by the DIM card. Displays the number of silence packets received by the DIM card. Displays the number of duplicate silence packets transmitted by the DIM card. (See note below) Displays the number of duplicate silence packets received by the DIM card. (See note below) Displays the number of HDLC 16kbps and 64kbps packets transmitted by the DIM card. Displays the number of HDLC 16kbps and 64kbps packets received by the DIM card. Displays the number of unknown packets (with unrecognized packet type) transmitted by the DIM card. (See note 4 below) Number of packets with unknown traffic received from the DIM card. This packet type has no optimization. (See note 4 below) Table 3-20: Packet Counters in GSM Abis/Ater Mode NOTE: When two or more silence packets are detected, a duplicate silence packet is used in place of silence packets to reduce bandwidth. The first silence packet in each sequence is preserved. GSM HR (Half Rate), GSM AMR (Adaptive Multi Rate), GPRS (General Packet Radio Service) and EGPRS (GPRS over EDGE, Enhanced Data for Global Evolution) are counted as unknown packets when in GSM Abis/Ater mode. In addition, channels that are configured for the wrong traffic type will produce unknown packets. For example, signaling packets that are transmitted on a channel that is configured for voice and 16K signaling on a 64K signaling channel will both be 3-35

74 CXMon User Guide counted as unknown packets. Statistics in AbisXpress mode This window displays the following statistics counters for the selected port (AbisXpress only) Counter Description Stream Pkts Tx Stream Pkts Rx Stream2 Pkts Tx Stream2 Pkts Rx Stream3 Pkts Tx Stream3 Pkts Rx Displays the number of packets transmitted to the first WAN stream. Displays the number of packets received from the first WAN stream. Displays the number of packets transmitted to the second WAN stream. Displays the number of packets received from the second WAN stream. Displays the number of packets transmitted to the third WAN stream. Displays the number of packets received from the third WAN stream. Table 3-21: Packet Counters in AbixXpress Mode Statistics in ATM/TDM/IMA mode This window displays the following statistics counters for the selected port (ATM/TDM/ IMA only) Counter Description Stream Pkts Tx Stream Pkts Rx Stream2 Pkts Tx Stream2 Pkts Rx Stream3 Pkts Tx Stream3 Pkts Rx Displays the number of packets transmitted to the first WAN stream. Displays the number of packets received from the first WAN stream. Displays the number of packets transmitted to the second WAN stream. Displays the number of packets received from the second WAN stream. Displays the number of packets transmitted to the third WAN stream. Displays the number of packets received from the third WAN stream. Table 3-22: Packet Counters in ATM/TDM/IMA Mode 3-36

75 Monitoring a CX Device 3.6 Logging Traffic Data to a CSV File In addtion to viewing the traffic data in CXMon, you can also log the traffic to a log file in CSV format. You can then open this file in any spreadsheet application or text file to compile the statistics on a device. Figure 3-22: Example of a Log file as a spreadsheet To see where CXMon is storing your log files, select Settings > Log Status. The Log Status dialog box appears (see Viewing the Log Usage Statistics on page 3-38). To configure how CXMon logs your data, select Settings > Log Settings > Other Settings (see Configuring the Data/Log Storage Options on page 2-15). There are eight types of log files you can generate: Savings: logs the amount of kilobytes that have been saved due to the optimized traffic on the CX device (see Savings log file on page 3-39) WAN: logs the amount of data that is sent and received, as well as the number of sent/received packets that are discarded or that are in error. (see WAN log file on page 3-39). BWSavings: logs the difference (as a percentage) between optimized traffic and non-optimized traffic on a port (see BWSavings log file on page 3-40) Traffic: logs the ratio of traffic types detected on the current port. (see Traffic log file on page 3-40) Voice Silence: logs the percentage of duplicate silence packets on the current port compared to the total number of speech packets (see Voice Silence log file on page 3-41) Discard Level: logs the ratio of discarded voice packets by the bandwidth management mechanism for each level of congestion (see Discard Level log file on page 3-41) PktDiscards: logs the number of discarded voice packets per congestion level (see PktDiscards log file on page 3-41) 3-37

76 CXMon User Guide Traps: logs the traps that have been recorded for the selected port (see Traps log file on page 3-42) Each log file contains the same header information at the top, which is then followed by the specific data types for that log. The common information is as follows: Device Name: the name of the device being tracked Dirty flag: for internal use by Memotec Inc. (please ignore) Log ID: for internal use by Memotec Inc. (please ignore) Port ID: the number of the port being logged (not included in the Savings and WAN log files) Date: the date the log entry was recorded Time: the time the log entry was recorded Viewing the Log Usage Statistics The Log Status dialog box displays the current log usage. To open it, select Settings > Log Status. To configure how CXMon logs your data, select Settings > Log Settings > Other Settings (see Configuring the Data/Log Storage Options on page 2-15). Figure 3-23: Log Status dialog box Parameter Current log path Description Displays the full directory path for all log files. NOTE: It is possible to see the full path by clicking it and using the arrow keys. Table 3-23: Log Status parameters 3-38

77 Monitoring a CX Device Parameter Free disk space Description Displays the amount of free disk space for the drive defined in the log path. NOTE: All logging will stop when this value reaches the Min free disk space setting. Size of log folder Current device log size Displays the total size of the log folder. This size includes all logs that have been created for all devices. Displays the total size of all logs for the device being monitored for the CXMon session. Table 3-23: Log Status parameters Savings log file The Savings log file records the amount of kilobytes that have been saved due to the optimized traffic on the CX device. This log includes the following log data from the Voice/GSM Traffic System Savings graph (see Voice/GSM Traffic System Savings on page 3-12): Tx % value: the percentage of transmitted data that was saved due to the optimization. Rx % value: the percentage of received data that was saved due to the optimization WAN log file The WAN (Wide Area Network) log file records the amount of data that is sent and received, as well as the number of sent/received packets that are discarded or that are in error. This log includes the following log data from the WAN Port monitor graph (see WAN Port Monitor on page 3-16): Tx value (Kbps): the percentage of transmitted data on the WAN Port monitor graph for T1/E1 or VR port (units are kilobit per second). Rx value (Kbps): the percentage of received data on the WAN Port monitor graph for T1/E1 or VR port (units are kilobit per second). 3-39

78 CXMon User Guide BWSavings log file The BWSavings (Bandwidth savings) log file records the ratio (as a percentage) of optimized traffic and non-optimized traffic on a port. This log includes the following log data from the Traffic Optimization Ratio graph (see Displaying the Ratio of Traffic Compression on page 3-30): Tx % value: the ratio (as a percentage) of transmitted data. Rx % value: the ratio (as a percentage) of received data Traffic log file The Traffic log file records the ratio of traffic types detected on the current port. It displays the number of TCH in use for each type of optimized traffic. This log file includes the following log data from the Traffic Optimization Ratio graph (see Displaying Ratio of Traffic Types on a Port on page 3-27). Depending on the type of port configuration that you have, different types of data will be logged: For AbisXpress port configuration: 16k Speech %: the percentage of 16k speech data in the traffic flow (values are normalized to 16k). 8k Speech %: the percentage of 8k speech data in the traffic flow (values are normalized to 8k). Sig Ratio %: the percentage of signal data in the traffic flow (values are normalized to 16k). Others Ratio %: the percentage of miscellaneous data (not 16k, 8k, nor signal) in the traffic flow (values are normalized to 8k). For EDGEPlus port configuration: 16k Speech %: the percentage of 16k speech data in the traffic flow (values are normalized to 16k). 8k Speech %: the percentage of 8k speech data in the traffic flow (values are normalized to 8k). Sig Ratio %: the percentage of signal data in the traffic flow (values are normalized to 16k). EDGE Ratio %: the percentage of EDGE speech data in the traffic flow (values are normalized to 8k). Others Ratio %: the percentage of miscellaneous data (not 16k, 8k, EDGE, nor signal) in the traffic flow (values are normalized to 8k). 3-40

79 Monitoring a CX Device For DCME port configuration: High BW Speech %: the percentage of high-quality speech data occupying bandwidth in the traffic flow (values are not normalized). Low BW Speech %: the percentage of low-quality (< 8 kbps %) speech data occupying bandwidth in the traffic flow (values are not normalized). Data %: the percentage of digital data in the traffic flow (values are not normalized). For ATM/TDM/IMA port configuration: Non-Idle Cells: the number of non-idle cells in the traffic flow Voice Silence log file The Voice Silence log file records the percentage of duplicate silence packets on the current port compared to the total number of speech packets. This log file includes the following log data: Tx % value: the percentage of transmited silence in the Voice Traffic Ratio graph. Rx % value: the percentage of received silence in thevoice Traffic Ratio graph Discard Level log file The Discard Level log file records the ratio of discarded voice packets by the bandwidth management mechanism for each level of congestion. This log file includes the Discard Level log data, which is used by the bandwidth management mechanism (as shown in the Discard Level graph) PktDiscards log file The Traffic log file records the number of discarded voice packets per congestion level. This log includes the following log data: Level 1: the amount of discarded level 1 packets. Level 2: the amount of discarded level 2 packets. Level 3: the amount of discarded level 3 packets. Level 4: the amount of discarded level 4 packets. Level 5: the amount of discarded level 5 packets. Level 6: the amount of discarded level 6 packets. Level 7: the amount of discarded level 7 packets. 3-41

80 CXMon User Guide Traps log file The Traps log file records the traps for the selected port. This log includes the following log data: Trap Name: name of trap Trap data: description of the trap 3-42

81 4 Troubleshooting This chapter provides solutions to common problems encountered when installing or using CXMon. 4-1

82 CXMon User Guide 4.1 Installation/Launching Issues s Problem Solution Launching CXMon produces the message MGMTAPI.DLL not found. The SNMP service is not installed. For more information on how to install it, see Preparing your PC to run CXMon on page 2-2. Problem Solution After you click OK in the CX Device Information dialog box, the main panel does not appear, although the OK button still appears. Even if you continue to click OK, nothing happens. The file mib.bin (located in the Windows SYSTEM32 folder) is missing or corrupted. You must reinstall CXMon. Problem Solution Launching CXMon produces any of the following messages to appear: mfc71.dll not found mfc71u.dll not found msvcr71.dll not found 3dbapi.dll not found ChartFX.ClientServer.Borders.dll not found ChartFX.ClientServer.Core.dll not found MMS3DABM.DLL not found The CXMon installation is missing a file or is corrupted. You must reinstall CXMon. Problem Solution This message is displayed: Log Path not found. Cannot proceed with Logging. The CXMon installation is missing the \logs folder in the CXMon install directory. You must reinstall CXMon or manually create this folder. The installation process starts when launching CXMon. Problem Table 4-1: Solutions to installation or launching problems 4-2

83 Troubleshooting Solution The CXMon installation is corrupted. You will need to reinstall CXMon. Problem Solution You cannot run more that ten instances of CXMon at the same time Because CXMon uses a graphical interface to present its data to the user, the limited graphical resources that Windows OS has available can decrease overall system performance. This problem is explained in this knowledge base article from Microsoft: You can improve performance by allocating more resources (called desktop heap) for graphical applications. To change the desktop heap, you need to edit the system registry. Before editing the registry, make sure you make a backup copy. See for help on this procedure. The steps to increase the desktop heap are: 1. Click Start > Run and type Regedit. 2. Navigate within the Registry editor to the key: HKeyLocalMachine\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems 3. Double-click the Windows value. 4. Scroll within the value and find SharedSection= 5. Edit the section of the string that may read: SharedSection=1024, 3072, 512 to the following: SharedSection=1024,8192, Close the Regedit window. 7. Restart your PC. You should now be able to run more instances of CXMon. Problem Solution The following warning message appears when launching CXMon: Environment variable not found. Please set the environment variable Some environment variables used by CXMon were lost. You must reinstall CXMon. Table 4-1: Solutions to installation or launching problems 4-3

84 CXMon User Guide 4.2 SNMP Trap Issues Problem No traps appear in the SNMP Trap section when the CX device generates traps. There are several possible causes for this problem. Solution The CX/CXU usually doesn t generate traps by default; they must be enabled explicitly. Check that the needed traps are enabled in the CXTool configuration. If CXMon s SNMP setting for traps is set to CXMon Only, make sure that CXMon is the only application listening to SNMP traps. For example, WhatsUp Professional/Gold should have its Trap mode disabled (see Preparing your PC to run CXMon on page 2-2). If CXMon is configured to receive traps from WUP/WUG, make sure that the forwarding ports match (in WUP/WUG and in CXMon). Make sure that: > the CX device is configured to send traps to the CXMon PC > the hosttrap entry to the monitoring PC is present > the admin agentifalias is set to the correct port alias (this should be the same IP address as the one monitored by CXMon. See Configuring CX Devices on page 3-2 for more information). Check that the object snmpouttraps is configured to increase each time a trap is generated (the snmp command in the CX/CXU). If it doesn t, ensure that the traps generation is enabled in the CX/CXU configuration. Record the IP traffic received by the CXMon PC to validate that the traps are received. If SNMP traps are received, make sure the Agent Address field within the trap is set to the IP address monitored by CXMon. If not, then the CX/CXU configuration is incorrect. Note that firmware release has a bug where this address is always This is fixed in release 435Z3 and above. An excellent tool to record this IP traffic is WireShark, freely available from The DOS command netstat a is a helpful tool for monitoring SNMP messages from the CXMon PC. You should see a line UDP???:snmptrap *:* where??? is the computer name. Problem Solution Traps are displayed in the Trap section but they appear as a sequence of numbers (ex: ). The DATA section also has no field name, only numbers (ex: 1=15. 10=1. 3-1). The file mib.bin located in the Windows SYSTEM32 folder is missing or corrupted. You must reinstall CXMon. Table 4-2: Solutions to SNMP Trap Problems 4-4

85 Troubleshooting 4.3 Device Information Issues Problem Solution Only the IP address appears; the other fields are empty. The device being monitored is not a CX device or is a device that is not supported by CXMon. You may also see the message Not a CX Device in the status bar at the bottom of the window. NOTE: CXMon only supports CX devices with firmware release 0435H and above. Table 4-3: Solutions to Device Information Problems 4.4 WAN Port Monitor Issues Problem Solution The interface drop-down list is empty. The WAN Graphics are different and static. The CX device being monitored is missing the WAN Index in its configuration. Table 4-4: Solutions to WAN Port Monitor Problems 4-5

86 CXMon User Guide 4-6

87 Index Numerics 16k IDLE tch k Local SW k Others tch k Sig tch k Speech tch k Speech traffic type k Sig tch dbapi.dll not found k Edge Pool k Edge Pool traffic type k Others tch k Sig tch k IDLE tch k Local SW tch k Others tch k Speech tch k Speech traffic type A Abis Traffic Optimization Ratio Abis Interface Utilization graph AbisXpress User Port Details Add-On Scripts AIS failure Ater ATM User Port Details B Blue port E1 Port Monitor T1 Port Monitor Buffer Free WAN Port Monitor BWSavings log file C ChartFX.ClientServer.Borders.dll ChartFX.ClientServer.Core.dll Clear All Graphs Clear button WAN Port Details Clear Graph button Clear SNMP Traps Clock Slip count Clock State WAN Port Details Clock State Change WAN Port Details comma separated value file compatibility Windows Vista configuring CX devices CXMon PC Windows Vista Control Panel preparing PC counters 16k IDLE tch k Local SW k Sig tch k Speech tch k Sig tch k EdgePool tch k Others tch k Sig tch k IDLE tch k Local SW tch k Others tch k Speech tch errors CSV file Current device log size , 3-39 Current log path , 3-38 CXMon User Guide Index-1

88 Custom Bandwidth Reference CX devices Abis supported AbisXpress supported AIS failure Ater supported ATM supported authorization key configuring DCME supported Device information panel DIM Port information panel direct license transfer discovering Edge traffic EDGEPlus supported Far end Loss of Framing firewall firmware key management limitations Map button memotec.bat MIB registration monitoring No traffic removable media license transfer2-21 restrictions site key SNMP restrictions SNMP traps starting CXMon TDM supported Traffic Mapping dialog box Traffic Optimization graph Traffic Optimization Ratio panel1-3 transfer license Trap information panel User Port graphs Vista Address vpstats index values vpstats vrsr index values vpstats vrsridx values vpstats wandix values WAN information panel WAN Port Details WAN Port Monitor CX2000 configuration CX2000 firmware CX900 firmware CX960e firmware CXMon Abis supported AbisXpress supported about Add-On Scripts Ater supported ATM supported authorization key configuring configuring CX devices configuring WhatsUp CX2000 configuration Data Acquisition Parameters Data Storage Options DCME supported Device Information Device information DIM Port information direct license transfer discovering CX devices EDGEPlus supported features firewall firmware Global Device Savings Graph configuration installer installing installing WhatsUp key management launch installer limitations Log configuration main window memotec.bat Meter Bar configuration Meter Bar Settings MIB registration monitoring devices overview preparing PC removable media license transfer2-21 removing restrictions setup.exe site key SNMP configuration SNMP limitations SNMP settings SNMP Source Address SNMP traps starting system requirements TDM supported Traffic Optimization Ratio transfer license trap handling Trap information Trap limitations trial license UDP port upgrading User Port Details Index-2 CXMon User Guide

89 Voice/GSM Traffic System Savings3-12 WAN Index WAN information Windows Vista CXTool Abis AbisXpress Add-On Scripts Ater ATM CX devices CX DCME EDGEPlus SNMP SNMP Source Address TDM Trap Host Vista Address WAN Index CX-U1000 firmware D data CSV Data Acquisition parameters Data pkts Rx Data pkts Tx Data Storage Options Graph Log Other Settings Trap Log Date log file DCME Traffic graph User Port Details DCME Mode Data pkts Rx Data pkts Tx High BW Silence High BW Silence Rx High BW Speech , 3-34 Low BW Silence Rx Low BW Silence Tx Low BW Speech Low BW Speech Rx Decreased system performance Delete logs Device Information IP Name Software Type Uptime Device information about Device information issues Device Name log file DIM Add-On Scripts DIM port vpstats index values vpstats vrsr index values vpstats vrsridx values vpstats wandix values DIM Port information about DIM ports FR WAN Trunk IP WAN Trunk MLPPP WAN Trunk WAN Index Dirty flag log file Discard Level log file Discard Level graph Clock Slip count Data pkts Rx Data pkts Tx Dup Silence Rx , 3-35 Dup Silence Tx , 3-35 Edge Pkts Rx Edge Pkts Tx EDGEPlus Mode HDLC Rx HDLC Tx High BW Silence High BW Silence Rx High BW Speech , 3-34 Idle Rx Idle Tx Loss of carrier count Loss of Tx clock count Loss Sync count Low BW Silence Rx Low BW Silence Tx Low BW Speech Others Pkts Rx Others Pkts Tx Sig Pkts Rx Sig Pkts Tx Silence Pkts Rx Silence Pkts Tx Silence Rx Silence Tx Speech Pkts Rx Speech Pkts Tx Speech Rx Speech Tx Unknown Rx Unknown Tx CXMon User Guide Index-3

90 Display period , 2-17 documentation topic structure Dup Silence Rx , 3-35 Dup Silence Tx , 3-35 E E1 Port Monitor AIS failure colored ports Far end Loss of Framing Map button Edge Pkts Rx Edge Pkts Tx Edge traffic EDGEPlus Traffic graph User Port Details EDGEPlus Mode Discard Level Graph Dup Silence Rx Dup Silence Tx Edge Pkts Rx Edge Pkts Tx Others Pkts Rx Others Pkts Tx Sig Pkts Rx Sig Pkts Tx Silence Pkts Rx Silence Pkts Tx Speech Pkts Rx Speech Pkts Tx Environment variable not found error counters about WAN information F Far end Loss of Framing firewall limitations firmware CX CX CX960e CX-U FR WAN Trunk Free disk space , 3-39 G Getting started Global Global Device Savings Graph Legend Graph Global Device Savings Voice/GSM Traffic System Savings3-12 Graph configuration Graph data Limit file size to 1 MB Max history files per Graph Single file per day Graph display options Graph Log Graph Settings dialog box Display period listbox Grid Display checkbox Refresh Rate listbox Graphic resources are low Graphs Clear All Graphs Gray port E1 Port Monitor T1 Port Monitor Green port E1 Port Monitor T1 Port Monitor Grid Display GSM Traffic Optimization graph Traffic Optimization Ratio panel1-3 GSM Abis/Ater User Port Details GSM Abis/Ater Mode Dup Silence Rx Dup Silence Tx HDLC Rx HDLC Tx Idle Rx Idle Tx Silence Rx Silence Tx Speech Rx Speech Tx Unknown Tx Unkown Rx H HDLC Sig traffic type HDLC Rx HDLC Tx High High BW Silence Rx High BW Silence Tx High BW Speech Rx High BW Speech Tx I Idle traffic type Index-4 CXMon User Guide

91 Idle Rx Idle Tx IMA User Port Details In Discard WAN Port Details In Error WAN Port Details installation Add-On Scripts CX launching memotec.bat MIB registration remove CXMon setup.exe Trap Host UDP port upgrading WhatsUp modifications installation issues installation process mis-start IP WAN Trunk K key management L launching issues Legend Global Device Savings Voice/GSM Traffic System Savings3-12 WAN Port Monitor license authorization key direct transfer key management removable media license transfer2-21 site key transfer trial trial period Limit file size to 1 MB limitations firewall Log configuration Log data Delete logs Min free disk space Set log path log file BWSavings CSV Date Device Name Dirty flag Discard Level header information Log ID PktDiscards Port ID Savings Time Traffic Traps Voice Silence WAN Log ID log file Log Path not found Log Settings dialog box Delete logs Limit file size to 1 MB Max history files per Graph Min free disk space Set log path Single file per day Log Status dialog box Current device log size , 3-39 Current log path , 3-38 Free disk space , 3-39 Settings Log Status3-20, 3-38 Size of log folder , 3-39 Log Usage Statistics , 3-38 Loss of carrier count Loss of Tx clock count Loss Sync Count Low BW Silence Rx Low BW Silence Tx Low BW Speech Rx Low BW Speech Tx M main panel does not appear Map button Max history files per Graph memotec.bat Meter Bar configuration Meter Bar Settings , 2-14 Meter Bar Settings dialog box Custom Bandwidth Reference Rx Tx WAN Index mfc71.dll not found mfc71u.dll not found MGMTAPI.DLL not found MIB installation memotec.bat registration Min free disk space CXMon User Guide Index-5

92 MLPPP WAN Trunk MMS3DABM.DLL not found monitoring CX devices msvcr71.dll not found N network discovering CX devices No traffic No traps appear SNMP Trap section not found ChartFX.ClientServer.Borders.dll4-2 ChartFX.ClientServer.Core.dll Not Used traffic type O Only the IP address appears Other Settings (Log) Others (traffic type) Others Pkts Rx Others Pkts Tx Out Discard WAN Port Details Out Errors WAN Port Details Overview P packet statistics packets DCME Mode EDGEPlus Mode error counters PC configuration configuring SNMP preparing SNMP configuration transfer license PktDiscards log file port error counters Port ID log file Port State WAN Port Details Port State Change WAN Port Details R Read Community Red port E1 Port Monitor T1 Port Monitor Refresh Rate , 2-17 remove CXMon restrictions Retry Count Rx Rx Bad CRC frames WAN Port Details Rx Bad NIB frames WAN Port Details Rx bps max WAN Port Details Rx Kpbs WAN Port Details S Savings log file Set log path Settings Clear All Graphs Clear SNMP Traps Log Settings Settings menu Meter Bar Settings setup.exe Sig Pkts Rx Sig Pkts Tx Sig traffic type Silence Pkts Rx Silence Pkts Tx Silence Rx Silence Tx Silence within Voice graph Single file per day site key Size of log folder , 3-39 SNMP Clear Traps configuring , 2-11 CXMon Enabled Display period limitations Read Community Refresh Rate restrictions Retry Count Source Address Timeout Trap Host Trap information Trap Options Trap Reception port Vista address WhatsUp Write Community Index-6 CXMon User Guide

93 SNMP Settings dialog box Display period Read Community Refresh Rate Retry Count Timeout Trap Options Trap Reception port Write Community SNMP Trap Issues SNMP traps Data Date Time Trap speech packets DCME Mode EDGEPlus Mode Speech Pkts Rx Speech Pkts Tx Speech Rx Speech Tx statistics CSV error counters packets system requirements firmware limitations T TCH 16k IDLE k Local SW k Others k Sig k Speech , k Sig k Edge Pool k EdgePool k Others k Sig k IDLE k Local SW k Speech , 3-23 Idle No traffic Not Used Others Sig TCH channel Abis Interface Utilization graph 3-29 TDM User Port Details The DATA section has only numbers4-4 Time log file Timeout Traffic log file traffic CSV Traffic graph Traffic Mapping dialog box , k IDLE tch k Local SW k Others tch k Sig tch k Speech traffic type k Sig tch k Edge Pool k Egde Pool k Others tch k Sig tch k IDLE tch k Local SW k Others tch k Speech tch k Speech traffic type Edge traffic Idle traffic Not Used traffic type Others (traffic type) Sig traffic type Traffic Optimization graph Traffic Optimization Ratio about Traffic Type 16k Speech k Edge Pool k Speech Idle No traffic Not Used Others Sig transfer direct license removable media license transfer2-21 Trap Host Trap information about Trap Log Trap Options Trap Reception port Traps log file traps limitations SNMP SNMP configuration supported CXMon User Guide Index-7

94 Trap Host entry UDP port WhatsUp Traps are displayed as numbers TRAU channel Abis Interface Utilization graph.3-29 trial license Tx Tx bps max WAN Port Details Tx Kpbs WAN Port Details Tx RST Discard WAN Port Details U UDP port User Datagram Protocol uninstalling CXMon Unknown Rx Unknown Tx upgrading site key transfer license trial license User Guide structure User Port AIS failure User Port Details AbisXpress ATM DCME EDGEPlus GSM Abis/Ater IMA TDM User Port Graphs Abis Interface Utili. graph Discard Level graph Silence within Voice graph Traffic graph Traffic Optimization graph Voice within Abis Traffic graph.3-29 WAN Discards Level Distrib. graph3-31 User Port Monitor colored ports Far end Loss of Framing Map button V versions upgrading Vista Address Voice Silence log file Voice within Abis Traffic graph Voice/GSM Traffic System Savings Graph Legend vpstats index values vpstats vrsr index values vpstats vrsridx values vpstats wandix values W WAN log file vpstats index values vpstats vrsr index values vpstats vrsridx values vpstats wandix values WAN Discards Level Distrib. graph.3-31 WAN graph WAN Port Monitor WAN graphics are static WAN Index , 3-4 WAN information about error counters WAN Port Details Clear button Clock State Change In Discard In Error Our Errors Out Discard Port State Port State Change Rx Bad CRC frames Rx Bad NIB frames Rx bps max Rx Kbps Tx bps max Tx Kbps Tx RST Discard WAN Port Monitor , 3-17 Buffer Free Legend WAN graph WAN Selector WAN Port Monitor field is empty WAN Port Monitor Issues WAN Selector WAN Port Monitor WAN Utilization Meter bar WAN Port Monitor WhatsUp configuring CX devices (discover) discovering CX devices install memotec.bat Index-8 CXMon User Guide

95 MIB registration modifications (install) starting CXMon WhatsUp Gold system requirements White port E1 Port Monitor T1 Port Monitor window main Windows Vista compatibility configuring system requirements WireShark Write Community WUP traps Y Yellow port E1 Port Monitor T1 Port Monitor CXMon User Guide Index-9

96 Index-10 CXMon User Guide

97 Glossary A Abis the internal interface that links the BSC and a BTS and allows control of the radio equipment and radio frequency allocation in the BTS. B BSC the Base Station Controller manages the radio interface. BTS Base Transceiver Station. The BTS includes radio transmission devices, reception devices, and the signal processing. C CXMon provides a graphic interface for monitoring CX equipment in GSM Abis/Ater and DCME networks. CXTool provides a graphic interface for configuring CX devices for GSM Abis/Ater and DCME networks. CX-U1000 the series of CX devices that include CX-U1010, CX-U1220, CX-U1240, and CX-U1280. Glossary-1

98 CXMon User Guide D DCME Digital Circuit Multiplication Equipment EDGEPlus transports and optimizes the bandwidth for GSM data services at the Abis interface. E GSM Global System for Mobile Communications G MIB Management Information Base M SNMP Simple Network Management Protocol S WAN Wide Area Network W WhatsUp (Ipswitch Inc.) an application that monitors critical network devices and services, allowing you to quickly identify problems and increase your understanding of your network performance and availability. Glossary-2

99 WUG WhatsUp Gold WUP WhatsUp Professional Glossary-3

100 REACH FURTHER. OFFER MORE. Contact Memotec: tel.: Henri Bourassa Blvd. West Montreal, Quebec Canada H4S 1P7