|
Description
In a network license configuration using the SuperPro type license implementation, a server computer hosts the SuperPro USB dongle containing the FRED license(s). There is no requirement that FRED be installed on the license server itself, though some SuperPro specific license services will need to be installed on the server computer to allow proper communication between the network license and the remote FRED client. On the client PC, the FRED software needs to be installed and then additional configuration parameters need to be specified that instruct FRED where to look on the network for the server computer hosting the network license. This Help topic describes the setup procedures required on both the server and client computers to enable proper functionality of a SuperPro type FRED Network license.
Preparation of the License Server
The following steps should be taken to configure the server computer hosting the SuperPro type FRED Network dongle, where the assumption is that there are no existing SuperPro products being hosted on the license server. If there are existing products using the SuperPro type implementation being hosted on the license server then it may be the case that the server is already properly configured and you may skip to step 4.
|
1.
|
Make sure that the SuperPro USB dongle is NOT plugged into the server computer.
|
|
2.
|
Run the Sentinel Protection Installer executable file with administrative privileges. The installer package can be accessed in the following ways:
•Download from the Thales website: Sentinel Protection Installer 7.7.1
•Retrieved from a PC with a current FRED installation. The installer is located in the <FRED install dir>\Utilities directory.
|
|
3.
|
Proceed through the Sentinel Protection Installer and choose the "Complete" setup option when prompted. This will install three services required to host the network USB dongle; the Sentinel Keys Server, Sentinel Protection Server and the Sentinel Security Runtime.
|
|
4.
|
Verify that the services from (3) above are running on the license server by checking the Windows services list as shown below.
.png)
|
|
5.
|
Check that one of the following ports is open for network communication:
•For TCP/IP protocol, UDP port 6001
•For IPX/SPX protocol, SAP messages are sent over 361 Hex
System administrators should verify that no other applications are using port 6001 by issuing the "netstat -a -b" command. The network key communication will fail if any software other than the sentinel software is using that port.
|
|
6.
|
Plug the USB dongle into the license server.
|
|
7.
|
Open the Windows Device Manager and check the Universal Serial Bus Controllers group for a device labeled "SafeNet USB SuperPro/UltraPro"
.png)
|
Preparation of a Client Computer
By default, a FRED installation will look on its local computer for a SuperPro license. In a network license configuration, additional settings must be applied on the client computer so that FRED looks to the license server when attempting to acquire an available FRED license. The following steps should be taken to prepare a client computer for running FRED in a network license configuration.
|
1.
|
Install the FRED software using the procedure described in the FRED Installation and Licensing help topic. During step 6, none of the optional components need to be installed on the client computer (though doing so will not adversely affect the network configuration).
|
|
2. (Option A)
|
Define a system environment variable named NSP_HOST whose variable value is specified using one of the following options:
|
Variable Value
|
Description
|
|
servername or IP address
|
The server, designated by its server name or IP address, is searched for an available license.
|
|
RNBO_SPN_BROADCAST
|
The client computer broadcasts a request over the local subnet to find a server with an available license.
|
|
RNBO_SPN_LOCAL
|
Searches for a license on the local computer (operates in stand-alone mode using a local server).
|
|
RNBO_SPN_DRIVER
|
Searches for a license on the local computer (operates in stand-alone mode using the driver instead of going through the server).
|
|
RNBO_SPN_SERVER_MODES
|
Searches first using RNBO_SPN_LOCAL followed by RNBO_SPN_BROADCAST
|
|
RNBO_SPN_ALL_MODES
|
Searches using all local modes followed by RNBO_SPN_BROADCAST
|
In Windows 10, the system environment variables can be accessed by typing "Environment Variables" into the Windows search bar. Otherwise, they can be accessed through the Systems group in the Control Panel and then choosing the "Advanced Settings" option.
|
|
2. (Option B)
|
Define a system environment variable named NSP_HOST_CONFIG whose variable value is the full file path to a configuration XML file (ex. "C:\MyDocuments\sntlconfig.xml").
The example below, in which LIC-SERVER-01, will be contacted through server port 6001, can be used as a template for defining an appropriate XML file.
<?xml version="1.0" encoding="UTF-8"?>
<!--
This is the configuration file for the applications run
using a Sentinel key. You can set the values prescribed
below or contact your software vendor for details.
Notes for using this file:
1. It is not necessary to set all the tag values.
2. Remove this file if you do not want to apply these settings.
-->
<SentinelConfiguration>
<SuperPro>
<!-- To discard the values set in this file, remove the comment signs from the following tag -->
<!-- <ConfigDiscard/> -->
<!-- Type the following constant between the Protocol tag: NSPRO_TCP_PROTOCOL -->
<Protocol>
NSPRO_TCP_PROTOCOL
</Protocol>
<!-- Type the workstation name/IP address (of the system where the key is attached or installed)
or an access mode (as specified by your software vendor) between the AccessMode tag -->
<AccessMode>
LIC-SERVER-01
</AccessMode>
<!-- Type a value ranging between 60 and 2,592,000 seconds, or type 0xFFFFFFFF (or -1) for an infinite
heartbeat interval -->
<HeartBeat>
</HeartBeat>
<!-- Type a value for the server port, the default port is 6001 -->
<ServerPort>
6001
</ServerPort>
<!-- Type SP_USBONLY between the SearchMode tag if you want to access SuperPro hardware key of USB form
factor and SuperPro software key. SuperPro hardware key of parallel form factor shall not be accessed if
this option is set.
Note: SP_USBONLY option is for RNBO_STANDALONE and RNBO_SPN_DRIVER access modes only. It will be ignored
for other access modes. -->
<SearchMode>
</SearchMode>
</SuperPro>
</SentinelConfiguration>
|
Additional SuperPro License Search Options
Search for a specific SuperPro key serial number
There are two methods for specifying that a license should be acquired from a specific SuperPro license based on the license serial number. The serial number for a FRED license can be determined in the following ways:
1.Use the Sentinel License Monitor to view the serial number of the available keys (last non-zero digits) in HEX.
2.Contact fredsupport@photonengr.com
The first method is to add a new system environment variable called NSP_HOSTKEYSERNUM whose value is the license serial number in decimal format.
Variable Name: NSP_HOSTKEYSERNUM
Variable Value: Key serial number in decimal form (ex. "1B2" in hex = 2*160 + 11*161 + 1*162 = 434)
NOTE: Specifying key serial number using NSP_HOSTKEYNUM takes precedence over key type specification using NSP_HOSTKEYTYPE.
The second method is to use a software startup parameter option, /HostKeySerNum=XXX, to indicate the preferred license serial number (in decimal format) to be used. The startup parameter can be used at at the Windows command line (ex. C:\Program Files\Photon Engineering\FRED 18.61\Bin\fred.exe /HostKeySerNum=434 ) or by modifying the "Target" entry of the FRED icon on the Windows desktop. No spaces are permitted in the startup parameter string.
Search for a specific FRED version
Licenses may be authorized for different FRED versions; Standard, Optimum, or MPC. In the event that multiple FRED licenses authorizing different FRED versions are available, the client computer can be configured to access licenses of a specific FRED version. There are two methods for specifying a FRED version specific license search.
The first method is to add a new system environment variable called NSP_HOSTKEYTYPE whose value is a string indicating the FRED version type.
Variable Name: NSP_HOSTKEYTYPE
Variable Value: standard, optimum or mpc
NOTE: Specifying key type using NSP_HOSTKEYTYPE is overridden by the key serial number specification using NSP_HOSTKEYSERNUM.
The second method is to use a software startup parameter option, /HostKeyType=type, to indicate the preferred FRED license type to be used. The startup parameter can be used at at the Windows command line (ex. C:\Program Files\Photon Engineering\FRED 18.61\Bin\fred.exe /HostKeyType=mpc ) or by modifying the "Target" entry of the FRED icon on the Windows desktop. No spaces are permitted in the startup parameter string.
|
Copyright © Photon Engineering, LLC
|
|