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. |
...
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 and above | The version 4.11 can be installed without uninstalling the previous version(s).
|
Div | ||
---|---|---|
| ||
Distribution preparation
Extract the content of the distribution archive to the current directory or copy the content of the provided distribution directory to the current directory.
The kit folder must not be the same as the target installation folder (Example: C:\Program Files\CHARON\Build_20410) otherwise the installation procedure may report "Charon is in use".
Run the "InstallShell.exe" file:
...
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 |
NCC | Contains the Charon Network Control Center executable |
Redistributables | Contains the redistributables needed for CHARON running (already installed, except the license alert script) |
Virtual Machine Manager | Contains the most up-to-date version of CHARON Virtual Machine Manager |
Virtual Machine Templates | Contains templates for creating CHARON virtual machines |
Virtual Machines | Contains the CHARON virtual machines |
Virtual Disk Images | Contains CHARON virtual disk images. For example "charoncp013.vdisk" and some OpenVMS tools (ovms_tools.vdisk) used for debugging plus the PCI I/O Bypass controller |
...
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.
...