| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
CHARON-AXP models | Minimum number of host CPU cores | Recommended number of host CPU cores |
|---|---|---|
HP AlphaServer 400 - HP AlphaServer 4100 | 2 | 2 |
HP AlphaServer DS10/DS10L/DS15 | 2 | 2 |
HP AlphaServer DS20/DS25 | 4 | 4 |
HP AlphaServer ES40/ES45 | 6 | 8 |
HP AlphaServer GS80 | 10 | 16 |
HP AlphaServer GS160 | 18 | 32 |
HP AlphaServer GS320 | 34 | 48 |
When starting, the CHARON-AXP software checks the available number of host CPU cores. This check is based on the maximum number of AXP CPUs that can be emulated if this number is not restricted by the "n_of_cpus" parameter. If the available number of host CPU cores is below this number, CHARON-AXP will issue a warning message even if the requirements for the configured number of AXP CPUs are fulfilled. The CHARON-AXP software will work despite this warning if the requirements for the configured number of AXP CPUs are fulfilled.
| Note |
|---|
Hyperthreading must be switched off completely. Disable hyperthreading 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 Hyperthreaded Core Sharing mode to None. |
...
| Info |
|---|
Starting with ESXi 6.5, it is not possible to select E1000 adapter when a new virtual machine is created using Windows 10, Windows Server 2012 and 2016 templates. The following workarounds are available:
|
...
| Note |
|---|
All antivirus, screen saver, automatic (scheduled) backup and any other CPU consuming software as well as software that is able to temporarily lock CHARON files (such as automatic indexing) must be turned off, uninstalled and disabled. Alternatively it is also possible to exclude all CHARON executables and material folders from scanning for viruses, but please note that scanning slows down CHARON host anyway - it may be critical for some installations requiring maximum performance. The power scheme must be set to "High Performance" with all the "Sleep" and "Standby" modes turned off. The automatic installation of Microsoft updates must be disabled. MS updates to the CHARON host must be done only in specific service maintenance periods established by the system administrator. Before applying new updates one must shutdown the operating system running on CHARON and stop all the running CHARON instances and services. |
| Note |
|---|
Save Secure boot is not supported by CHARON at the moment since in this case host OS will not accept signature of distributed NDIS drivers needed for CHARON networking. Disable save secure boot or use CHARON without networking (select "Ignore" when installation procedure reports that NDIS driver is not signed). |
If a network-wide license (red dongle or software license) is going to be used, do the following:
- On server side (where the network license will reside): open port 1947 for both TCP and UDP
- On the client side, if broadcast search for remote licenses is to be used, UDP traffic from port 1947 of the license server to ports 30000-65535 of the client must be permitted.
- Both on server and client sides: set default gateway
Please consult with Windows online documentation for details.
| Info |
|---|
If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "Sentinel HASP License Manager" (hasplms.exe) service (installed by CHARON-AXP ). |
...
Login as the local system administrator ("Administrator") on the host system.
Create a special user for running CHARON-AXP (optional). This user must have all the administrative privileges. Please consult with Windows online documentation for details.
Note The CHARON installation procedure will create a special group called CHARON-GRP and the current user will be automatically included to this group. Do not remove this group and do not remove any CHARON user from it, otherwise a problem with virtual memory allocation may appear on CHARON startup.
The created user may belong to some domain, but please note that in this case you have to add this user to the CHARON-GRP manually as described in this article, and then reboot the CHARON host.
Stay logged in as local system administrator ("Administrator") or log off and login as the CHARON-AXP user having administrative privileges (if this option has been chosen).
Create a special directory for the CHARON-AXP distribution kit and copy the provided files there.
Upgrade cases:
| From version | Action |
|---|---|
| 4.7 and below | First uninstall all CHARON products. |
| 4.8 | The version 4.9 can be installed directly.
|
| Include Page | ||||
|---|---|---|---|---|
|
...
Directory | Description |
Build_XXX\x64 | Contains product executables and libraries |
Drivers | Contains the CHARON drivers |
InstallShell | Contains the CHARON installation procedure executables |
Logs | Contains the CHARON installation log |
| Redistributables | Contains the redistributables needed for CHARON running (already installed, except the license alert script) |
| Virtual Machines Manager | Contains the most up-to-date version of CHARON Virtual Machines Manager |
| Virtual Machine Templates | Contains templates for creating CHARON Virtual Machines |
| Virtual Machines | Contains the CHARON Virtual Machines |
| Virtual Disk Images | Contains the CHARON virtual disk images, for example "idle_vms_pkg_v3.0" |
...
Software licenses can also be uninstalled using the method, described in the "Removing CHARON-AXP Software Licenses" chapter of this Guide
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.
...
Login as the local system administrator ("Administrator") on the host system.
Create a special user for running CHARON-AXP. This user must have administrative or standard privileges (in this case login as Administrator for manging NDIS drivers and running NCC utility). Please consult with Windows online documentation for details.
Add this user to the CHARON-GRP group as it is described in this article and then reboot CHARON host.
Login as the created user.
...