Versions Compared

Old Version 81

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version 82

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Linux server reboot operations added for upgrade

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

CHARON-VAX modelMinimal number of CPU coresRecommended 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 models22

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.

...

Warning
titleWARNING
  • If you plan to install CHARON-AXP on the same server, both products, CHARON-AXP and CHARON-VAX, will have to be the same build number.
  • If you upgrade from a previous version of CHARON-VAX, please stop all running CHARON virtual machines and , uninstall CHARON products and reboot the Linux server before proceeding with the installation steps described below.

...

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.

...

  1. 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
  2. Prepare the new kit RPM files as it is described in "Before installation" and "Distribution preparation" sections.
  3. Stop all running CHARON-VAX instances.
  4. 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.
  5. Login as "root" user.
  6. Remove the old CHARON-VAX version as described in the "CHARON-VAX for Linux deinstallation" chapter and reboot the Linux server.
  7. Proceed with the same instructions on the new kit installation as described in the "Installation" section.
  8. Once installation is completed, it is recommended to reboot the Linux server (possible issues with licenses detection could occur).

  9. Install the license for the new CHARON-VAX as described in the "License installation" section.

  10. 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 license detection. To solve this problem run the following command:

# systemctl enable aksusbd   (for Linux 7 and 8)

and reboot your Linux server.


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc