guide line tems discovery 3.1 hasp licese

•

NT11-11578, 4.0, 6/1/2011 1

Guide line – TEMS Discovery 3.1 HASP Licensing

•

NT11-11578, 4.0, 6/1/2011 2

Contents

1 Licensing 3

1.1 Local vs. Network Licenses .................................................................................. 3

1.2 License Requirements .......................................................................................... 3

1.3 Drivers for HASP Key ........................................................................................... 3

1.4 Inspecting the Scope of Your License .................................................................. 3

2 Installation and using HASP licensing 7

2.1 HASP HL Local License Installation ..................................................................... 7

2.2 HASP HL Network License Installation ................................................................ 7

2.2.1 Using HASP HL Network Licenses ....................................................... 7

2.2.2 Restrictions and limitations ................................................................... 7

2.3 Updating HASP Keys (HL/SL) .............................................................................. 8

2.4 Updating HASP HL Keys...................................................................................... 8

2.5 Sentinel HASP Runtime Network Activity ............................................................ 9

2.5.1 Local Communications........................................................................ 10

2.5.2 Remote Communications ................................................................... 10

•

NT11-11578, 4.0, 6/1/2011 3

1 Licensing

Licensing for TEMS Discovery is based on the HASP technology. Both hardware-based (HASP HL) and software-based (HASP SL) licensing can be used. See sections 2.1.

Further, licenses associated with TEMS Discovery can be either local or network licenses.

• A local license is embodied

o (HASP HL) in a hardware key which is inserted into the PC, or

o (HASP SL) in a software key that is installed on it.

• A network license is obtained on the client machine

o (HASP HL) by connecting to a license server where a hardware key is inserted, or

Note: HASP SL is only used for the TEMS Discovery trials versions.

1.1 Local vs. Network Licenses

• Local licensing require that the HASP HL hardware key (black) is connected the a USB port on the computer hosting TEMS Discovery

• Network licensing requires that the HASP HL hardware key is connected to a computer on the network. On computer where the hardware key is installed the HASP SRM driver need to be installed. The HASP SRM driver is installed automatically on the PC along with TEMS Discovery, so install TEMS Discovery on the computer where the HAP HL hardware key is connected then it is also easy to verify that the license key is correct and working if trouble shooting is needed.

1.2 License Requirements

A license is always required to run TEMS Discovery. Without a license you cannot launch the application.

1.3 Drivers for HASP Key

The HASP key drivers (for HASP HL and SL alike) are installed automatically along with TEMS Discovery. If you are going to use HASP HL network licensing, you must install the HASP driver on the license server PC; see section 0 for instructions.

1.4 Inspecting the Scope of Your License

You can check what is covered by your (local or network) license in the HASP Admin Control Center, accessed from the start menu Ascom -> TEMS Programs -> Utilities->TEMS License Control Center or (http://127.0.0.1:1947).

The meanings of the HASP key Feature Ids used by TEMS Investigation are given in the table that follows.

Feature Id Release/Option

500 Reserved

•

NT11-11578, 4.0, 6/1/2011 4


18 Reserved

501 TEMS Discovery 1.0

502 TEMS Discovery 1.0 Professional

503 TEMS Discovery 1.0 Professional (Trial)

504 Technology option GSM

505 Technology option GSM/WCDMA

506 Technology option GSM/WCDMA/HSPA+

507 Technology option CDMA

508 Technology option CDMA/EVDO Rev 0, A

510 Technology option LTE

511 Technology option TD-SCDMA

512 Technology option WiMAX

513 Reserved

514 Reserved

515 Reserved

516 Nemo logfile support

517 TEMS Discovery 2.0



520 Automated data processing option

521 Google Earth

522 Bing Map,

523 Import plug-in API

524 Reserved

525 Reserved

526 Qualcomm log file format

527 Reserved

528 TEMS Discovery 2.1 Standard

•

NT11-11578, 4.0, 6/1/2011 5




531 TEMS Discovery 2.1 Replay (option 1)



534 Ericsson UETR/BULK CM

535 JDSU log file support

536 Reserved

537 Report & Script Builder

538 IP Analysis

539 Reserved

540 TD Standard - TEMS Investigation bundled




544 TEMS Discovery 3.0 Standard - TEMS Investigation bundled



547 Reserved

548 Reserved

549 Reserved

550 TD 3.0 Standard - Standalone

551 Reserved

552 TEMS Discovery 3.0 Standard (Trial)

553 ZK Celltest Logfile format

554 LG LTE Diagnostic Monitor logfile format



•

NT11-11578, 4.0, 6/1/2011 6



558 TEMS Discovery 3.1 (TI Bundled)

559 TEMS Discovery 3.1 Standard

560 TEMS Discovery 3.1 Standard (Trial)


•

NT11-11578, 4.0, 6/1/2011 7

2 Installation and using HASP licensing This chapter covers in detail how HASP software protection is applied to TEMS Discovery and how to handle it in practice.

2.1 HASP HL Local License Installation

Here is how to install a local HASP HL local license on a client machine.

• Install TEMS Discovery. In the process, the HASP SRM driver is installed automatically on the PC.

• Plug in HASP HL hardware key in a USB port on the computer.

2.2 HASP HL Network License Installation

Here is how to install a local HASP HL network license on a client machine.

• Install TEMS Discovery on the computer where the HASP HL Network hardware key shall be hosted. . In the process, the HASP SRM driver is installed automatically on the computer.

• Plug in HASP HL hardware key in a USB port on the computer.

2.2.1 Using HASP HL Network Licenses

TEMS Discovery will automatically identify the license servers connected to the network and fetch a license when it is started.

By default, TCP port 1947 is used between server and client. Due to firewall restrictions or other issues, you might need to change this port. If necessary, do so by creating the following registry entry on both server and client:

HKLM\SYSTEM\CurrentControlSet\Services\hasplms\Parameters

Name: Port

Type: REG_DWORD or REG_SZ

REG_SZ is preferred since the default display of REG_DWORD is hexadecimal, which may be misleading. Restart the LLM Server (Sentinel HASP License Manager) or reboot the machine. Assigned port can be verified with the command netstat –a.

If applicable, substitute your own port number for “1947” when following the instructions below.

Installing the HASP SRM driver always installs both client and server software.) Furthermore, depending on the network topology and license server setup, clients may require special configuration. For both servers and clients, HASP SRM is configured through an “Admin Control Center” web page interface accessed from the start menu, Ascom -> TEMS Programs -> Utilities->TEMS License Control Center or (http://127.0.0.1:1947)

2.2.2 Restrictions and limitations

It is not possible to have different license options for a product on the same HASP HL hardware key. If different option configuration is needed multiple license servers need to be setup

•

NT11-11578, 4.0, 6/1/2011 8

The license server and TEMS Discovery need to be connected to the network when using network licensing

The license server cannot run as a Virtual Machine, TEMS Discovery can be installed on a Virtual machine but the HASP HL network hardware key need to be connected to a physical machine.

2.3 Updating HASP Keys (HL/SL)

When updating a HASP key of any type (i.e. whether HL or SL), you proceed much in the same way as when first obtaining a HASP SL (software-based) key. HL and SL are described separately below for maximum clarity. For further information, see the document “TEMS HASP SRM Key Information” which is found on the installation CD in the subdirectory User Manuals.

2.4 Updating HASP HL Keys

1. Make sure you have installed TEMS Discovery.

2. Plug your HASP HL key into the PC.

3. Navigate to the Application folder beneath the TEMS Discovery installation directory and run the file TEMS Discovery HASP SRM Remote Update. This dialog box opens:

4. Now collect the key information by clicking the Collect information button.

5. If you also have a HASP SRM SL (i.e. software-based) key installed on the machine, a dialog will appear at this point prompting you to choose which key to update. Select the HASP HL key

•

NT11-11578, 4.0, 6/1/2011 9

6. A file with extension .c2v is created. Choose a suitable file name and save the file.

7. E-mail the .c2v file to customer support. Contact information is found at www.ascom.com/networktesting under the link “TEMS Support”.

8. From customer support you will receive a file with extension .v2c. Once you have that file, navigate to the TEMS Discovery folder and run the file hasprus.exe. The Remote Update System dialog opens.

9. Select the Apply License Update tab.

10. Browse to locate the .v2c file, and click the Apply update button:

11. The result of the operation will be displayed in the main window of the dialog. When you have successfully applied the HASP license, exit the Remote Update System application.

2.5 Sentinel HASP Runtime Network Activity

This chapter describes the type of network activity that occurs in the communication between:

• an application (protected using Sentinel HASP) and the local HASP License Manager (referred to as “local communications”).

• the local HASP License Manager and one or more remote HASP License Managers (referred to as “remote communications”).

Details regarding local communications and remote communications are provided on the pages that follow.

This chapter is intended to assist IT managers who want to understand how runtime activity on the network may impact the way they set up their network rules and policies.

This information is reproduced from SafeNet’s Sentinel HASP documentation.

Sentinel HASP communicates via TCP and UDP on socket 1947.This socket is IANA-registered exclusively for this purpose.

This information is reproduced from SafeNet’s Sentinel HASP documentation

•

NT11-11578, 4.0, 6/1/2011 10

2.5.1 Local Communications

This section describes communication between a protected application and the local HASP License Manager Service.

A protected application communicates only with HASP License Manager on the computer where the application is running, regardless of whether the HASP HL or SL Key is located on the same computer or on a remote computer.

HASP License Manager service opens socket 1947 for listening (both for UDP packets and TCP packets).

• IPv4 sockets are always opened (HASP License Manager currently does not work without IPv4 installed).

• IPv6 sockets are opened if IPv6 is available.

A protected application tries to connect to 127.0.0.1:1947 TCP to communicate with HASP License Manager. If an application uses multiple sessions, multiple concurrent TCP connections may exist. If a session is unused for a certain number of minutes (at least seven minutes, but the exact number depends on several factors), the session may be closed and automatically re-opened later in order to limit resources used by the application.

These local communications currently use IPv4 only.

The communication uses binary data blocks of varying size.

2.5.2 Remote Communications

This section describes communication between the local HASP License Manager service and a remote HASP License Manager service.

This type of communication occurs when the protected application is running on a different computer from the computer where the HASP HL or SL Key is installed.

The protected application communicates only with the local HASP License Manager on the computer where the application is running, as described in section 2.5.1. The local HASP License

Note: Under Windows, HASP License Manager is a service that is launched automatically by hasplms.exe. Under Mac OS and Linux, the HASP License Manager is a process launched automatically by hasplmd.

•

NT11-11578, 4.0, 6/1/2011 11

Manager discovers and communicates with the License Manager on the computer containing the HASP Key using one of the following methods:

• The local HASP License Manager issues a UDP broadcast to local subnets on port 1947 using:

– IPv4 (always)

– IPv6 (if available)

You can disable this broadcast by clearing the Broadcast Search for Remote Licenses checkbox in the Admin Control Center Configuration screen.

• The local License Manager issues a UDP “ping” packet to port 1947 for all addresses specified in the Admin Control Center field Specify Search Parameters. These addresses may be individual machine addresses or broadcast addresses.

All License Managers found by the discovery process are then connected via TCP port 1947, using IPv4 or IPv6 as detected during discovery, and data regarding the remote HASP Keys are transferred.

This discovery process is repeated at certain intervals. (The interval size depends on a number of factors, but it is generally not less than five minutes.)

UDP packets sent and received in the discovery process contain the License Manager GUID (40 bytes of payload data).

When starting or stopping a License Manager, and when adding or removing a HASP Key, a UDP notification packet is sent, containing the License Manager GUID and a description of the changes encountered. This is done to allow other License Managers to update their data before the next scheduled discovery process.

TCP packets between two License Managers on different computers use HTTP with base-64 encoded data in the body section.

2.6 Supported operating systems

The license server are using very limited resources and can be hosted on any laptop/PC or server connected to the network. The license server can be installed on the following operating systems.

- Windows 2000 (SP4)

- Windows XP (SP3)

- Windows XP x64 Edition (SP2)

- Windows XP Embedded

- Windows Embedded Standard 2009

- Windows Embedded Standard 7

- Windows Server 2003 R2 (SP2) *

- Windows Server 2008 (SP2)*

- Windows Server 2008 R2 *

- Windows Vista (SP2) *

- Windows 7 *

- SuSE ES 10 SP2 *

- SuSE ES 11 *

•

NT11-11578, 4.0, 6/1/2011 12

- Open SuSE 11.2 *

- RedHat EL5.4 *

- Ubuntu Desktop 8.04 *

- Ubuntu Desktop 10.04 *

- Ubuntu LTS Server 10.04 *

- Debian 5.04 *

*includes 32- & 64-bit versions

Virtual Machine Supported Platforms:

- VMware 7.x

- VMware ESXi 4.0

- Parallels 4.x (Windows)