Hawkeye 2.4-EA-SP3 Release Notes
Hawkeye 2.4-EA-SP3 Release Notes
Hawkeye 2.4-EA-SP3 Release Notes
52
Installation Notes
- Hawkeye 2.4 management system has a web user interface, and requires no client side installation.
- The management server is distributed as a virtual image in OVA and can be deployed to a VMware hypervisor.
- Migration from an existing Hawkeye 1.0 or 1.1 requires careful planning, please be sure to read and fully
understand the steps outlined in the migration guide.
- Contact Ixia support if you prefer our technical support staff’s assistance in migrating your system.
The Hawkeye virtual image requires 64-bit support from the host operating system or from the hypervisor. The
CPU virtualization instructions (e.g. Intel VT-x, AMD-V) must be supported and enabled.
While importing the virtual image, it is possible to get compatibility warning messages. If this happens, please
ignore them and continue the import operation.
Supported Browsers
Hawkeye 2.4 EA-SP3 user interface can be accessed from most browsers that support HTML5 on Windows, OS X
and Linux platforms:
A newly created Hawkeye 2.4 EA-SP3 virtual machine will attempt to obtain an IP address through DHCP. If a DHCP
server is not available in your environment or does not respond within 30 seconds, Hawkeye 2.4 EA-SP3 will use a
static IP address: 192.168.0.200.
If a DHCP server is not available and the predefined static IP is not reachable from your network, you will need to
set a new IP address manually by following these steps:
1. Gain access to the CentOS CLI, by using the VMware console to the Hawkeye server VM, or by connecting with
SSH.
2. Login to CentOS as root. The default root password is "ixia123".
3. Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set a valid IP address
BOOTPROTO=None
IPADDR=a.b.c.d
NETMASK=g.h.i.j
GATEWAY=k.l.m.n
4. Edit /etc/resolv.conf and enter one or more nameservers
nameserver a.b.c.d
5. Restart the Hawkeye system network: service network restart
6. After the server is restarted, you can use the web interface (accessible on the new IP address) to manage the
networking part of the system. Change the Hawkeye server hostname by using ssh to server and enter the
following command:
cd /home/ixia/Hawkeye
./ixia_network_config.sh -fh <yourHawkeyeServerHostname>
Upgrade Hawkeye
Hawkeye upgrade from 6.80 to 2.<latest version>
To upgrade Hawkeye 6.80 or IxChariot Pro contact Ixia Customer Support. Also contact Ixia Customer support for
upgrading XR2000 and XRPi containing images older than 9.10k.
You can upgrade only if you have Hawkeye installed previously and are upgrading to the next version on the Linux
platform.
If you do not follow the database backup procedure you will lose all the data. The steps below uses a utility included in
2.x release but run while 1.x Hawkeye Server is running to backup your 1.x database.
The backup may take some time. The time taken to create a backup depends on the size of your database. This
generates a file called Hawkeye_full_backup.sql.gz which is stored in the /root directory.
It is recommended to update the CentOS version on Hawkeye Server to the latest version, for the latest security updates.
Follow the prompts on each step and make your selection. Note use -v on end of command for verbose output.
It is important to choose option to delete all data in database. This ensures no database corruption occurs. If option to
delete data in database is not selected the results and probe information is lost or corrupted.
Restore database
You can optionally restore your database by using the commands below.
1. Run the ./restore_db script to restore the previously backed up Hawkeye 1.x database.
2. Restore db also updates the MySQL from 5.1 to 5.7 for better and optimized SQL performance. It is important to
restore into an empty database.
If you decide to create a new system the existing data configuration and test history will be lost.
Ensure you have disk space equivalent to the space taken by mysql data.
2. Navigate to the directory that contains the installation files (For example, cd /tmp/Hawkeye_Install_Files).
3. Run the ./backup_db script, this creates a back up your entire Hawkeye database in the /root directory.
To restore or recover the database backup on the same machine or another Hawkeye server (which must be on the
same release or version) do the following:
a. Run the ./restore_db script ( located in /tmp/Hawkeye_Install_Files) to restore the database that was
backed up. This accesses the backed up database zip file in /root.
This takes some time to restore. The restore overwrites and deletes the existing tables.
A database backup or restore can be performed from and to the same version of a release. The release must be the
same in case any internal database or tables have changed from one version of Hawkeye server to the next. Once a
database restore is complete a software upgrade to a higher release can be safely performed. Then backup the
database on the latest release for a new baseline backup.
Hawkeye software upgrade brings in required CentOS updates compatible with Hawkeye server.
Note: User should not run 'yum update' on a Hawkeye server. If user has a specific
requirement to update a particular package, he should contact Ixia customer support.
Hawkeye 2.4 EA-SP3 uses Ixia Licensing Utility (ILU) and License Server Plus (LS+). This licensing system was first
introduced in Hawkeye 1.0.
You should have received an email with your Activation Codes. If you have not received it yet, please contact your
sales manager or Ixia Support. Once the installation is done and you can access the Hawkeye server using the
assigned IP address you will be taken to a screen to activate the license. Refer to License Installation Guidelines
below for details or contact Ixia Customer support for how to do this.
Ensure Hawkeye server hostname is correct. Do NOT change hostname of server after applying the license. Change
the Hawkeye server hostname by using ssh to server and enter the following command:
cd /home/ixia/Hawkeye
./ixia_network_config.sh -fh <yourHawkeyeServerHostname>
If issues encountered with generating/applying license with IE, recommended to use Chrome as web browser.
Following installation in a web browser access the Hawkeye server using the assigned IP address. Screen will
provide a licensing link to register using the activation codes previously emailed.
Using a device on the internet, in a web browser enter “fulfillment.ixiacom.com/activation”. This is the Ixia offline
registration tool that can be used to generate a license file. Enter host ID of Hawkeye server and activation codes
from email. Select “Load Data” then select “Activate All” and then click “Activate”. On next web screen select
“Download License File”. In a web browser enter the Hawkeye server assigned IP address. As Hawkeye server has
not had a license applied it will go to a license Screen. Select “import license file” and select “BROWSE” and open
the generated .bin license file. Then select “OK” to activate licenses.
Additional Documentation
Hawkeye 2.4 EA-SP3 includes user guides (Hawkeye User Guide). The user guides can be accessed from the web
interface under the Information section.
What’s New
No new features are added in SP3 Release. Please look at Hawkeye 2.4 EA release notes for features in 2.4
Release stream.
BUG 1488417: XRPi: Wi-Fi Connect Test: using hostname for Hawkeye Server registration causes
nameserver lookup issues.
BUG 1489334: XRPi: If ONLY eth0 configured, running WIFI Connect test does not restore eth0
nameservers.
Large systems may consume large amounts of disk space for logging with default settings.
Recommend enabling compression on Hawkeye Server (uncomment line for log files compression
in /etc/logrotate.conf) and removing uncompressed log files.
XR2000/XRPi probes cannot be downgraded from Hawkeye 2.4 back to Hawkeye 1.1. Refrain from
connecting a 2.4 XR2000/XRPi device to 1.1 Hawkeye system, your device may end up in unrecoverable
situation. Please contact Ixia Support if need arises.
The Raspbian XRPi has a known issue with its USB ports which can cause the Wi-Fi dongle to intermittently
enter a locked-up state, requiring a physical reboot of the XRPi to recover. The use of a non-powered “2.0
USB hub” (performing protocol conversion) between the XRPi and the Wi-Fi dongle resolves this issue. If a
User experiences this stability issue referred to as “XRPi Wi-Fi lockup”, please contact Ixia Customer
Support so the necessary non-powered “2.0 USB hub” can be shipped to resolve the stability issue. Note, all
new shipped XRPi will contain a 2.0 non-powered USB hub.
Main Dashboard uses the aggregation methods by default, All the results shown in the dashboard are
aggregated on hourly, 3hourly and daily basis. Test results page on the other hand does not use
aggregation. There may not be one to one correlation between the main dashboard and test results page
on the amounts of test run during the period (as aggregated periods do not start synced to the hour/day).
ICMP destination port is used as offset (not destination port) in path discovery.
For the XRPi Wi-Fi endpoint. In the Web client for Probe management, user may not be able to identify Wi-
Fi or eth interface. Default traffic will be transmitted on wlan0 and received on eth0 (if available).
If user selects the proper IP (drop down) the traffic will be routed (TX/RX) to that selected interface.
An endpoint with multiple interfaces (e.g. XRPi with eth0 and wlan0) needs to have each interface on a
different subnetwork to avoid routing issues.
For Mesh and Real Services tests the Interface options (e.g. to select Wi-Fi IP) are not provided in web
client.
Wi-Fi test types are only supported for Automatic probes using DHCP
While doing installation Hawkeye service is stopped. If you disagree with any changes in installer,
installation will stop and exit out without restarting Hawkeye service. If that is the case then please restart
the Hawkeye service by typing following command. "service Hawkeye start".
Minimal qualification of IPV6 is done for Hawkeye 2.4. All test types and options for ipv6 haven’t been fully
qualified.
XRPi Wi-Fi endpoint is not supported to perform tests running from eth0 to Wlan0 interface on the same
XRPi.
XRPi Wi-Fi Scan may not show SSID if frequency or channel Info is not available (some older APs (80211.a)
do not provide this information).
Any browser update on (chrome or IE) needs a restart of the browser before using it as a Hawkeye web-
client
Using MySQL external database not qualified for current release
Range selection under the test results may return full range data if the query is made on a nonexistent data
time frame.
Filter values on top of table rows require hitting 'Enter' to get affected. Exiting field wouldn’t apply the
filter anymore.
Exceeding Hawkeye Server VM disk space will cause all tests stuck in 'queuing'
If Hawkeye server enabled to run both N2N and real service test at the same time. User needs to be aware
the Real Service test “Wi-Fi connect” will bring down and re-establish the Wi-Fi interface to a different Wi-
Fi access point. If a no other N2N test is scheduled to run at the same time, TCP errors may be seen.
The OVA/QCOW2 distribution mode doesn’t come with an uninstall option. To uninstall Hawkeye removing
the VM from the Hypervisor is the only option.
User must not perform ‘yum update’ to update packages on Hawkeye server as break dependencies.
A connection test will bring up the default connection (if any) upon completion, but any
previously defined non-default connection will not (i.e. previous conn test that does not reset the
interface)
To Use Wi-Fi Connect Test Type and use the CLI WiFiConnect.Py the SSID information from the AP
has to be broadcasted. Hidden SSID's are not supported in 2.4 Release
After restoring dB, and/or upgrading system from 2.1->2.4, some auto probe entries may be
duplicated with no IP. User can manually delete those entries
If the server has no connectivity to internet, the login authentication mode is forced to 0 (local)
Only system admin level user can configure Test Template. And user can assign these test
templates to various groups - where users can only execute them
Wi-Fi tests on XRPi will not support specific BSSID selection for this release.
XR2000 and XR Docker endpoint names cannot have a space in the name.
Bug ID Description
BUG1445178 Real Service: HTTP Server Test: Incorrect download time
BUG1445382 FTP download test: incorrect error message for login authentication failure
BUG1467546 Customer: Real service: FTP Multi-Stream Download: multiple streams report inaccurate
download rate
BUG1471225 Customer: Audit Trail: Not capturing changes to Preferences Test Controller
BUG1471651 Hawkeye - Hawkeye Test Case "Http Server Test" - Handle Error 403 better
BUG1474874 Customer: XR Docker: When XR Docker is hub of large Mesh Test - some test pairs missing -
on one shot test
BUG1475326 Hawkeye - Test Template - Multiple Add test clicks results in gui issues.
BUG1478072 Customer: Path discovery: test yields no results for certain URL's due to geo-location special
characters returned
BUG1479743 Customer: XR Docker: HTTP Server Test: time to first byte always zero
BUG1481303 Customer: Email test: Missing metric status and metric graph for "Email receive Delay" and
"Email send response time" metrics
BUG1481321 Customer: Email test alters password if special characters are used (Hawkeye server precedes
with backstroke)
BUG1481962 Customer: YouTube test always show "Total Video Rebuffering Events" as 0
BUG1482974 Hawkeye - Skype Network Connectivity Performance test metric names are different from
ICMP test
BUG1482975 Hawkeye - Skype Network Connectivity Performance test needs to use Destination URL not IP
BUG1485940 Customer: Reverse DNS in path discovery is broken. IP Address not supported.
BUG1481019 Customer: Wi-Fi Connect: Threshold for Wi-Fi Signal Level will not accept negative values
BUG1487057 Customer: POC: Security Issue: non admin users can gain access and change system
configurations from the webui
BUG1484707 Customer: HTTP Response time Error when go to URL not supporting SSLv3 (requires
echoping upgrade)
BUG1489124 Customer: Test Templates – cannot add additional tests to existing templates
BUG1437078 Customer: Security: XR2000 VM + XR2000: not packaged with latest openssl RPM needed for
Customer specific cipher
INF1488111 Customer: XRPi static IP address: User Guide updated: User needs to manually edit ifstate file
if only eth0 configured
INF1487671 Customer: Security: User guide updated: steps to generate SSL Certificate Request for
Hawkeye Server updated for SAN information required by some browsers.
BUG 1481019 Customer: Wi-Fi Connect: Threshold for Wi-Fi Signal Level will not accept negative values
Hours: 09:00 - 18:00 local time (Beijing time), Monday through Friday
Email: [email protected]
China Customer Support
Phone: 400-898-0598 (Greater China region)
Phone: +86-10-5732-3932 (Hong Kong customers)
Fax: +86-10-8454-9198