sA
Agilent Technologies
Signaling Analyzer and Network Analyzer
Release Notes for the 6.50.103 Patch
This document provides the release notes for the Signaling Analyzer 6.50.103.005 and Network Analyzer 6.50.103.002 patch. The sections below provide installation instructions and a list of the software issues this patch addresses.Installing the Patch
The Signaling Analyzer 6.50.103.005 patch is intended to be installed over Signaling Analyzer 6.50.102.006, 6.50.101.001, or 6.50.100.108. The Network Analyzer 6.50.103.002 patch is intended to be installed over Network Analyzer 6.50.102.002, 6.50.101.001 or 6.50.100.040. Refer to the Network Analysis and Troubleshooting Setup Guide for general installation and setup information.
Note: When the Signaling Analyzer and Network Analyzer software applications are to be used together (for example, when using the Signaling Analyzer to analyze network traffic captured using DNAs / LIMs), the version of the software must be Signaling Analyzer 6.50.103.005 and Network Analyzer 6.50.103.002.
Installing/Upgrading Software on a PC
Obtain the Signaling Analyzer 6.50.103.005 software or Network Analyzer 6.50.103.002 software, or their locations, from your Agilent Representative.
To install/upgrade this software, follow these steps:
1. Unzip the sart6.50.103.005patch.zip file or the na6.50.103.002patch.zip file to a convenient location on your PC.
2. Double-click the sart6.50.103.005patch.exe file or the na6.50.103.002patch.exe file. 3. Start the Signaling Analyzer or Network Analyzer application and use Help | About to
verify that your software version is 6.50.103.005 and 6.50.103.002 respectively when the installation has completed.
Firmware Update on DNAs
Remember to update the firmware on any Distributed Network Analyzers (DNAs) connected to your PC to match the Network Analyzer software version for proper operation. If you connect to a DNA after a software update, the Network Analyzer application automatically performs a file synchronization to update the firmware on the DNA. Refer to your Network Analyzer online Help for more information about updating firmware.
Installing/Upgrading Software on a DNA PRO and DNA MX
The DNA PRO or DNA MX image must be 5.00.100 or greater. If it is not, you must re-image the DNA PRO or DNA MX prior to installing the patch. The version of Network Analyzer must be 6.50.102.002, 6.50.101.001 or 6.50.100.040 in order to install the 6.50.103.002patch. The version of Signaling Analyzer must be 6.50.102.006, 6.50.101.001 or 6.50.100.108 in order to install the 6.50.103.005patch. The Network Analyzer and Signaling Analyzer software may be installed by using the Instrument Manager.
Obtain the Signaling Analyzer software version 6.50.103.005 or its location, and Network Analyzer software version 6.50.103.002 or its location from your Agilent Representative.
sA
To upgrade the DNA MX or DNA PRO, use Instrument Manager:
1. Unzip the sart6.50.103.005patch.zip file or the na6.50.103.002patch.zip file to a convenient location on the PC on which the Agilent Instrument Manager is installed. 2. Start Instrument Manager and add the instrument using the Add Instrument button. 3. Select the instrument from the main view and click the SW Update button. You can
upgrade software on multiple instruments by pressing Ctrl + click. 4. Click the Browse button to find the .exe file that you placed on your PC. 5. Click OK to apply the software update.
Firmware Update on DNAs
When you have daisy-chained DNAs or DNA HDs that are connected to a DNA MX or DNA PRO, the firmware update of those DNAs will happen automatically at the time of
installation.
CAUTION: While this firmware update is occurring, DO NOT turn off power to these devices or remove any of their LIMs until these devices are visible in the Select LIM dialog box in the Network Analyzer software.
sA
Issues Addressed in this Patch
Signaling Analyzer
The issues listed below are addressed by the 6.50.103.005 patch.
Issue ID Description
26335 The Signaling Analyzer now decodes SINAP InitialDP message correctly.
26978 The iusse of Utran over IP call trace has been corrected. The NBAP RL Deletion messages are now grouped properly and IubIuIur call trace displays the Interface Type correctly for paging procedures.
27165 Signaling Analyzer works properly when browsing messages from the last to the first in the Traffic Overview after
creating a View Filter on MAP.
27329 Segmented SCCP message over XUDT is reassembled properly prior to decoding.
27370 The issue of CS paging message on Gb flagged as parse error has been fixed.
27445 Problem with sub-session and accessing the call trace results has been fixed.
27470 The issue of MU filtering in the Signaling Analyzer is corrected.
When using the “Store Control Plane (Suppress User Plane)” in the MU Filter, the Signaling Analyzer would filter out some of the Control Plane messages, which are supposed to pass through.
27509 The sub-session feature works correctly regardless the regional settings of the PC.
27778 The location of the DMT log file is retained when the DMT feed session is automatically recovered.
Network Analyzer
The issues listed below are addressed by the 6.50.103.002 patch.
Issue ID Description
27559 The IP Multi-Segment Packet Loss Jitter Analysis measurement now supports GTP tunneled IP traffic.
sA
Issues and Known Problems
The issues described below are from previous GA and patch releases and still exist after applying this patch release.
Signaling Analyzer
● Title: High memory usage when running Signaling Analyzer without UMTS Auto-deciphering
Description: When running Signaling Analyzer Real Time, with Traffic Overview, UMTS RLC/MAC Reassembly enabled (from Tools -> Options -> Reassembly), the memory usage will be high and this is not released until session is closed. If you stop the capture and try to run Call Trace, you will get error: "System Error: CL 0004"
Workaround: 1. Run with UMTS Auto-deciphering. Or 2. Once you see the CL 0004 error, save the session and close current Signaling Analyzer. Then open Session again in Signaling Analyzer Offline.
Primary/Related TTI: 24971
● Title: Date format in Traffic Overview and Call Trace View are using different formats
Description: In Timestamp column of Traffic Overview, the date format is the following: DD/MM/YYYY. But in StartTime column of CallTrace View, the format is MM/DD/YYYY.
Workaround: None
Primary/Related TTI: 25038
● Title: Optimizer has listed extra DNAs which do not belong to session
Description: In DNA combo box, you will see other DNAs which do not belong to current open session.
Workaround: Open Bearer view to check the correct DNA
Primary/Related TTI: 24633
● Title: PDFs launched from the Help window sometimes will not open
Description: If you install the Signaling Analyzer software to a non-default location, links to a number of PDF files that are included with the product will not be displayed.
Workaround: Most of the PDFs that are not displayed are also available in the main Documentation Library that can be started from the desktop.
Primary / Related TTI: 25944
● Title: Unexpected behavior associated with lockName argument in contextDrill API command on Vista or Windows 2008 computers.
Description: When using the contextDrill command in the Signaling Analyzer API, and the "lockName" argument is either not specified or not specified as the user currently logged in, the Signaling Analyzer application will be launched in the background under the username "SYSTEM" or the other lockName (as seen in the Processes tab of the Windows Task Manager.)
Workaround: None.
Primary / Related TTI: None.
Network Analyzer
● When running an 8-Port T1/E1 LIM in channelized mode, the Signaling Analyzer, Multi-User Server, or the Network Analyzer Multi-Multi-User Client may stop receiving frames shortly after starting if Jumbo Frames is not configured properly. This may happen if the DNA has been configured to use Jumbo Frames (the MTU on the GigE RTSM port has been set to 9000), but the PC NIC card has not been configured to use Jumbo
sA
Frames (or does not support Jumbo Frames). Older versions of software would work in some cases even if Jumbo Frames was mis-configured.
● CSV measurement logging does not work properly on Microsoft Vista computers. However, saving measurement data to .dat file does work properly on Microsoft Vista computers.
● When using a J6801B, saving a file after the measurement run has been stopped and when the capture buffer is full may result in a corrupted .dat file.
Agilent Technologies Product Support: For a local support contact number, access
http://www.home.agilent.com.
Click the Select a Country or Area link in the upper right corner, select the desired country, select Yes or No to remember your selected country, and click Submit. You will return to the main page. Click the Contact Us link in the upper right corner and the next page will list the contact phone numbers for the selected country.
Trademark: See the Network Analysis and Troubleshooting Solutions Setup Guide for all trademark and copyright notifications and acknowledgements.
November 2009
