| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
| CHARON-VAX model | Minimal number of CPU cores | Recommended number of CPU cores |
|---|---|---|
VAX 6610 | 2 | 4 |
VAX 6620 | 3 | 4 |
VAX 6630 | 4 | 6 |
VAX 6640 | 6 | 8 |
VAX 6650 | 8 | 12 |
VAX 6660 | 8 | 12 |
| Other models | 2 | 2 |
When starting, the CHARON-VAX software checks the available number of host CPU cores. This check is based on the maximum number of VAX CPUs that can be emulated. Therefore the number of host CPU cores recommended for the maximum number of emulated CPUs - as shown in the right column of the table above - must be available. If the available number of host CPU cores is below this number, CHARON-VAX will issue a warning message. The CHARON-VAX software will work despite this warning.
| Note |
|---|
Hyper-threading must be switched off completely. Disable hyper-threading in the BIOS settings of the physical host or, for a VMware virtual machine, edit the virtual machine properties, select the Resources tab then select Advanced CPU. Set the Hyper-threaded Core Sharing mode to None. |
...
- Invoke the system default web browser and enter the URL http://localhost:1947 to display the "Sentinel Admin Control Center" (ACC) web interface.
- Click on "Sentinel Keys" link to open the corresponding page.
- Make sure that one and only one CHARON HASP or SL license is present.
To facilitate troubleshooting, Stromasys recommends to enable logging from the Sentinel Admin Control Center as described in this article: Enabling logging in Sentinel Admin Control Center.
| Div | ||
|---|---|---|
| ||
| Problem | Action |
|---|---|
| No license is displayed | Make sure that all the recommendations above about remote access to the host are fulfilled (if remote access takes place), that the HASP USB key is not broken and its LED indicator is lit (meaning that it is used by the host). |
| Only one License key / SL is seen and its content is incorrect | Contact STROMASYS to request a new license update. |
| Several License keys / SLs are displayed | Remove all of them except the one provided by STROMASYS for the just installed version of CHARON. |
Removing licenses can be done by physical disconnection of the corresponding USB HASP keys from CHARON host and physical disconnection of the network HASP keys from all hosts on the local network (or by disabling remote access to network licenses from the CHARON host - see detailed explanations below).
For license servers accessible only via non-broadcast search it is also possible to disable access to network licenses if only a local license is to be used: Click on the "Configuration" link to open the "Configuration for Sentinel Manager" page.
Uncheck the "Allow Access to Remote Licenses" checkbox from the "Access to Remote License Managers" tab then press the "Submit" button to apply changes.
...
- Ensure your license allows you to upgrade to that version. If not, please generate a C2V file and send it to STROMASYS for update. See CHARON-VAX for Linux utilities - 'hasp_srm_view' utility
- Prepare the new kit RPM files as it is described in "Before installation695426244" and "Distribution preparation695426244" sections.
- Stop all running CHARON-VAX instances.
- Make sure that no template files (i.e. "mv3k6.cfg.template") have been used for your specific configuration otherwise copy those files to a dedicated folder.
- Login as "root" user.
- Remove the old CHARON-VAX version as described in the "CHARON-VAX for Linux deinstallation" chapter and reboot the Linux server (recommended).
- Proceed with the same instructions on the new kit installation as described in the "Installation695426244" section.
- Once installation is completed, it is recommended to reboot the Linux server (possible issues with licenses detection could occur).
Install the license for the new CHARON-VAX as described in the "License installation695426244" section.
- Start all the CHARON-VAX services stopped at step #3.
| Note | |
|---|---|
If you did not reboot your Linux server at step 6, you may experience issues with 'aksusbd' service installation and then license detection. Example:
To solve this problem, remove all Charon installed product and restart from step 6 above. |
...