Versions Compared

Old Version 5

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

...

WORK IN PROGRESS

Stromasys  Charon-AXP

Version: 1 - Published: 20  

Table of Contents

Table of Contents
excludeTable of Contents

...

  • CPU requirements:
    • The number of available x86/x64 compatible (Intel or AMD) CPU cores in the hosting server should be at least 150% of the number of emulated CPU cores.
    • The recommended number of available (Intel or AMD) CPU cores in the hosting server is twice the number of emulated CPU cores.
    • Intel Xeon E-series v3 and above with a CPU clock frequency from 3GHz; to achieve the best performance use the latest Intel Xeon CPUs from the Scalable Processors family.
  • Memory requirements:
    • DDR4 RAM 2133 MHz and above is recommended for optimal Charon performance.
    • The minimum host memory size depends on the amount of emulated AXP memory and on the number of Charon instances running on one host. The minimum host memory = (2Gb +  the amount of HP Alpha memory emulated) per Charon-AXP instance.
  • Mid range and high end RAID controllers with at least 1GB cache with write-back enabled and battery backup option is recommended.
    (Using low-end RAID controllers may cause significant performance degradation and Charon-AXP crash. RAID5 and similar configurations are not recommended.)
  • Intel HT (Hyper-Threading Technology) should be disabled on the hosting server.
  • The hosting server should always run at full speed. Power management, USB power saving management and the screen saver should be disabled on the hosting server.
  • Windows UAC should be disabled.

  • The Port Group Security Tab containing the Charon network adapter(s) must be set to Promiscuous mode, MAC Address Change and Forged Transmit=Accept.

...

  • Charon license update is required before upgrading. Stromasys might request a HASP dongle state (c2v file) or a host fingerprint taken by HASP Update Service (which is included in the Charon kit) in order to issue a license update. Please refer to License Update Service for details
  • Due to a Charon installation procedure update, if you upgrade from a version older than 4.8, it is required to uninstall all Charon products before installing Charon-AXP version 4.11. Please use the Windows Control Panel to perform the operation.
  • (warning) If you upgrade from version 4.8, 4.9, 4.10 or 4.11 (previous build):
    • It is not necessary to save boot parameters at the SRM level (console). Parameters will be kept.
    • It is mandatory to update all existing Charon Virtual Machines to make them run the latest version using the Virtual Machines Manager, VM Configuration tab.
  • The following Microsoft Windows update has to be installed on Windows 7, Server 2008 R2 in order to support new Charon drivers signed with SHA2 signature:
    https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
  • If VMware is used, it must be upgraded to version 5.5, 6.0, 6.5 or 6.7.
  • The Tru64 kernel might require a rebuild for some emulated AXP models that are included in the Charon-AXP/4100 product.
  • It is recommended to archive the old Charon logs before starting the new version in order to avoid mixing character encoding in the log files.
  • Intelligent packet processing should be switched off for the network adapters dedicated to Charon with "Network Control Center" (NCC) utility. Please refer to FTP, NFS, and general network issues with CHARON-AXP and CHARON-VAX on Windows for details.
  • The user that runs Charon-AXP must have local administrator privileges and be a member of Charon-GRP group (which is created during the Charon installation).
  • Charon executables, libraries and data (disk container files) files should be excluded from all the antivirus checks, including on-the-fly checks and scheduled scans.
  • HT (Hyper-Threading Technology) should be disabled on the hosting server.
  • Power management, USB power saving management and screen saver should be switched off on the hosting server.
  • The Charon-AXP configuration file should be reviewed if migrating from Charon-AXP for Linux. Linux specific configuration parameters (for example, network adapter references) should be changed to Windows specific parameters. Please refer to the user manual for details.
  • Please note that the actual network communication speed and mode are determined by the Windows network speed and mode settings.

  • If Charon-AXP is being moved to another hosting platform and direct SCSI access method is used to access some SCSI devices, the new hosting platform SCSI drivers should support the SCSIport method. If drivers supporting SCSIport method are not available, direct SCSI access cannot be used. This is a case for all Windows Server 2012 (R2) and Windows 8.1 systems, and is often seen for Windows 7 and Windows Server 2008 (R2) systems. The recommended workaround for disk access is to use the \\.\PhysicalDriveX method.
    If any other SCSI device is involved, please contact Stromasys. Charon-AXP for Linux can be considered to work around the limitation.

  • For network connections, interface="connection:..." syntax is preferred in the Charon configuration file.

  • The packet_port keyword in the Charon configuration file can be used on any hosting platform instead of the platform specific keywords ndis5_chpack_port and ndis6_chpack_port.
    For example, the Charon configuration file lines:

    load ndis5_chpack_port/chnetwrk EWA0 interface="..."

    and

    load ndis6_chpack_port/chnetwrk EWA0 interface="..."

    can be replaced with:

    load packet_port/chnetwrk EWA0 interface="..."


  • For the emulated network adapters the communication speed and mode is recommended to be commented out (set to automatic). If it is necessary, see the example below:

    load DE500BA/dec21x4x EWA interface=EWA0
    load packet_port/chnetwrk EWA0 interface="..."
    set EWA adapter_mode="100BaseT-FD"


  • On VMware, legacy_mode should be set in the Charon configuration for emulated AXP network adapters if Promiscuous mode cannot be set (this solution does not work in multi-instance configurations).
  • The console definition syntax has been changed in the configuration file starting with v4.9. Please read the User's Guide for instructions on how to apply it if you currently use a Charon version prior to v4.9.

  • If "IDLE" utility is going to be used, perform the following commands after its installation:


    $ @sys$startup:charoncp_startup
$ charoncp set idle /enable


...

  1. Enlarging ACE cache size

    Try this solution first. It is recommended to enlarge the ACE cache size at least in 2 times as it is shown in the following example:


    set ace cache_size = 2048

    If this solution does not work for the specific guest OS tasks, apply also the next solution.

  2. Setting specific ACE host options

    Set the following set of options in the configuration file:


    set session n_of_io_cpus = <N>
    set ace num_translators = <N>
    set ace host_options = "--fixed-variant=0 --x64-nooptimize"

    where <N> is number of the I/O CPUs dedicated to Charon.

Other restrictions:

  • Network and tape booting is not currently supported.
  • The total number of devices (both controllers and units, including disks) displayed by Charon SRM console is limited to 48. However more devices are available to VMS and Tru64. Note that it does not affect the actual number of configured devices provided to Charon guest OS.
  • It is impossible to mount physical tape on some new physical devices (ID#5488),
  • The Charon installation may fail with the error message "The installation process cannot replace hasplms.exe because the file is in use". It is known problem of the Sentinel HASP driver installer included in the Charon installation procedure as a 3rd party software. If you face this issue stop the hasplms.exe process manually and re-run Charon installation procedure. See the Installation chapter below for more information.
  • In certain situations, mapping to a SAN using the Pass Through method may not be possible. In that case use the presentation mode instead (ID#5424).

  • The Charon emulated console supports only 80 symbols in one line.

  • In some situations, the virtual disks descriptions can be displayed as "Virtual SCSI Disk (C)SRI" in the SRM console. This problem does not affect the Charon functionality (ID#4729).
  • Charon cannot correctly define the total number of available CPUs on multi CPU groups systems (NUMA architecture, etc) - it reports only a number of the CPUs found in its first group. This problem will be fixed in future releases.
    As a workaround, enable "Node interleaving" in the BIOS (if available) to make the BIOS report the total number of available CPUs (as a part of one consolidated NUMA group) to the operating system.
    For example, on HP Proliant servers, the configuration sequence is the following:
    - Boot the server, press F9 and enter BIOS setup.
    - Select "Advanced Options" -> "Advance Performance Tuning Options" -> "Node Interleaving", set it to "Enabled".
    - Boot Windows.
  • Hardware partitioning is not supported by Charon. However the same hardware layout can be emulated with multiple Charon instances on the same host.
  • The SRM console shows the configured virtual disk names differently for the same *.vdisk containers on each Charon start (ID#4498).
  • The OpenVMS/AXP Version 8.4 installation CD media is not mountable under VMS V7.2-1H1. It is a VMS version restriction (ID#4054).
  • Older AMD and Intel CPUs without support of the CMPXCHG16B instruction could run Charon-AXP translated code incorrectly. It is recommended not to use those CPUs. If such CPUs are detected on the hosting server, Charon-AXP writes the following message in its log file:

...

  • Charon stability is improved (ID#5483, 5331).
  • Support of modern SAN (MSA-2050) is improved over Emulex PT (ID#5421).
  • Log is flushed regularly and asynchronously to facilitate online LOG monitoring by third-party tools (ID#5532).
  • Correct installation of x64 HostPrint utility in all Charon products is implemented (in the folder beside the corresponding executables) (ID#5570).
  • VMware Ethernet adapters: in addition to the E1000, E1000E and VMXNETx adapters are now fully supported.
  • Copyright notes are updated in all sample configuration files (ID#5399).
  • EXE/DLL copyright is updated (ID#5503).
  • The value of "log_repeat_filter" parameter is "off" by default (ID#5405).
  • Licensing mechanism is improved (ID#5375, 5458, 5459).
  • Network License management processing changes (ID#4631).
  • Redistributable Visual C++ runtime is upgraded (ID#5385).
  • Installation procedure detects inconsistent and/or damaged installation and deals with it properly (ID#5476).
  • In "Repair" mode installation, the procedure keeps the current Charon installation in case of errors (ID#5477).
  • All Charon components are installed independently for every build (ID#5504).
  • Patches to Charon kits are able to keep all the previous executables independent from each other (ID#5506).
  • Backup patch scripts are installed for each build independently (ID#5517).
  • Virtual Machines renaming feature is disabled (ID#5394).
  • "hasp_view" command line mode is extended to output all available licenses details to a file (ID#5442).
  • NCC utility is improved (ID#5497).

...

  • Fixed a problem where BUGCHECK (and emulator crash) happened while performing BACKUP from bypass-enabled disk to vtape under OpenVMS Alpha (Support Case 00031622, ID#5521)
  • Fixed failures on scan/rescan on PGB with Passthrough (Support Case 00031595, ID#5527)
  • Fixed a problem where patch script created incorrect backup directories (ID#5516)
  • Fixed a problem where Charon-AXP (AlphaServer GS320), V 4.9 B 19403 crashed at start in certain configurations (ID#5495)
  • Fixed HOSTprint working on Windows 10 (ID#5054)
  • Fixed broken "license_key_lookup_retry" option functionality (ID#5538)
  • Fixed a problem with incorrect selection of default product while creating VM with Charon Manager (ID#5530)
  • Fixed a problem where Charon VMs (services) lost dependency on HASPLMS (ID#5529)
  • Fixed a problem where core dump occurs while accessing PBXGA window over network connection (ID#5449)
  • Fixed a problem with panic in cpu (0) when trying to migrate from charon 4.7 to 4.9 (Support Case 00031586, ID#5512)
  • Fixed an error during installation on Windows Server 2016: "NDIS Packet driver is not installed" (ID#5544)
  • Correct Charon service dependencies persist now when upgrading existing Charon VMs (ID#5546)
  • InstallShell graphics is updated for correct slogan (ID#5558)
  • MkDisk utility graphics is updated for correct slogan (ID#5562)
  • Fixed a problem where HOSTprint stays running when emulator process terminates (ID#5505)
  • Fixed a problem where InstallShell defined versions of VC redistributives installed incorrectly (ID#5494)
  • Fixed a problem with a situation when interval timer interrupts are missed and lost on new 4.00 GHz hosts (ID#4446)
  • Fixed a problem with timer loses on VMware (ID#4492)
  • Fixed a problem where sometimes network does not work with PMAD-AA (ID#5067)
  • Fixed a problem with long duration of Charon-AXP installation (ID#5360)
  • Fixed a problem where multiport serial card does not work on multiprocessing AXP models (ID#5406)
  • Fixed a problem with incorrect behaviour of action for Edit Configuration in VM Manager (ID#5413)
  • Fixed a problem where host NIC dedicated to Charon is shown as dedicated to host in the Network Control Center (ID#5415, 5429)
  • Fixed a problem where there is no network connection when "packet_port" is in legacy mode (ID#5427)
  • Fixed a problem where virtual PBXDA looses bytes (TXA0 is not able to receive 0xFF and next 1 character) on input (ID#5436)
  • Fixed a problem where Charon reports "Can not change current ethernet address... Dynamic change of ethernet address is disabled or is not supported" if port_enable_mac_addr_change is set to false (error code 00000113) as an error instead of a warning (ID#5443)
  • Fixed a problem with unexpected forced Windows reboot during Charon installation (ID#5455)
  • Fixed a problem where in "Repair" mode (only) Installation, the procedure processes running "logmond" incorrectly (ID#5479)
  • Fixed a problem where Installation procedure detects versions of installed VC++ redistributives incorrectly (ID#5494)
  • Fixed problem where Emacs hangs OPA0 console by introducing new console implementation (ID#2033)
  • Fixed problem where NCC fails to install NDIS driver (ID#5177)
  • Fixed problem where CharonCP fails to install on OpenVMS 6.2-1H3 (ID#5329). 
  • Fixed problem where sometimes VMS 7.3-2 hangs on booting from DGA disk (ID#5377).
  • Fixed problem where Charon crashes when emulated NIC is bound to a teamed host NIC on VMWare (ID#5380).

  • Fixed problem where Virtual Machine Manager does not pick up changes in log file specification and configuration names if the VM name contains spaces (ID#5390).

  • Fixed problem where no RDP warning is displayed in local license key environment (ID#5400).

  • Fixed problem where Telnet negotiation does not work correctly on serial console

  • HALT is not available (disabled, greyed out) on emulator's system tray menu (ID#5437 and ID#5451)
  • HOSTprint did not work on Windows 10 (ID#5054)
  • Did not detect "no power" status correctly (ID#5458, 5459)

...

  • Unpack Charon kit into a temporary (installation) folder.
  • Run the "InstallShell.exe" file in the installation folder.
  • Choose the products to install and proceed with suggested steps.
  • Please note that the media may contain more products than allowed by your license.

(warning) Charon installation may fail with an error message "The installation process cannot replace hasplms.exe because the file is in use". It is known problem of the Sentinel HASP driver installer included to Charon installation procedure as a 3rd party software.

In this case follow the procedure recommended by Sentinel:

  1. Login as an user having Administrator Rights.
  2. Use the Sentinel HASP Runtime Environment Removal tool (https://sentinelcustomer.gemalto.com/sentineldownloads/?s=removal&c=#)
  3. Stop any antivirus or firewall available on the system.
  4. Stop and remove "hasplms.exe" manually. This file is available under "C:\Windows\System32". In case if "hasplms.exe" is read only or hidden change the file properties accordingly.
  5. Restart the system
  6. Run Charon installation again

...