CHARON-AXP V4.8 Build 183-02 for Windows 64 bit - Release Notes
Table of Contents
- 1 Products included in the CHARON-AXP version 4.8 build 183-02 for Windows 64 bit
- 2 Supported software platforms
- 3 Hosting hardware requirements and configuration recommendations
- 4 New functionalities introduced in build 183-02 since previous release (build 171-01)
- 5 Problems fixed in build 183-02 since build 171-01
- 6 Configuration changes required when upgrading from previous versions of CHARON-AXP to build 183-02
- 7 Known restrictions of build 183-02
- 8 New functionalities introduced in previous builds
- 8.1 New functionalities introduced in version 4.7 build 171-01
- 8.2 New functionalities introduced in version 4.6 build 163-03
- 8.3 New functionalities introduced in version 4.5 build 153-07
- 8.4 New functionalities introduced in version 4.4 build 148-02
- 8.5 New functionalities introduced in version 4.2 build 142-02
- 8.6 New functionalities introduced in version 4.1 build 129-04
- 8.7 New functionalities introduced in version 2.4 build 118-05
- 8.8 New functionalities introduced in version 2.3 build 108-00
- 8.9 New functionalities introduced in version 2.2 build 104-00
- 9 Problems fixed in previous builds
- 10 Distribution and Installation
- 11 Related documents
Please review this document before proceeding with installation of CHARON-AXP
Products included in the CHARON-AXP version 4.8 build 183-02 for Windows 64 bit
In this document the terms CHARON and CHARON-AXP are used to refer to the products below:
CHARON-AXP/400 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/2000 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/4100 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/DS10 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/DS20 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/ES40 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/GS80 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/GS160 version 4.8 build 183-02 for Windows 64bit
CHARON-AXP/GS320 version 4.8 build 183-02 for Windows 64bit
Supported software platforms
Microsoft Windows Server 2016 Standard and Datacenter Editions, 64 bit version
Microsoft Windows Server 2012 R2 Standard and Datacenter Editions, 64 bit version (please notice that only R2 revision is supported)
Microsoft Windows Server 2008 R2 (SP1) Standard and Enterprise Editions, 64 bit version (please notice that only R2 revision is supported)
Microsoft Windows 7 Professional and Ultimate (SP1) Editions, 64 bit version
Windows 8.1 Professional Edition, 64 bit version
Windows 10 Professional and Enterprise Editions, 64 bit version
VMware ESXi 5.5 and 6.x up to 6.5 (requires a supported Windows operating system on top of a ESXi virtual machine)
Microsoft Hyper-V (requires a supported Windows operating system on top of a Hyper-V virtual machine)
Hosting hardware requirements and configuration recommendations
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 v3 generation and above (E3 v3, E5 v3, E7 v3), CPUs with a clock frequency of 3GHz and higher are recommended for optimal CHARON performance.
DDR4 RAM 1866 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.
Hosting server should always run at full speed. Power management and the screen saver should be disabled on the hosting server.
Windows UAC should be disabled.
On VMware, E1000 network adapters must be used for CHARON.
The Port Group Security Tab containing the CHARON network adapter(s) must be set to Promiscuous mode, MAC Address Change and Forged Transmit=Accept.
New functionalities introduced in build 183-02 since previous release (build 171-01)
New platform support
Windows 10 Professional and Enterprise Editions, 64 bit version
Performance improvements
Performance is improved (ID#2381, ID#3144)
HASP libraries have been upgraded (ID#4709, ID#4450)
Instruction scheduling is updated with Ivy Bridge and Haswell tables (ID#4619)
Preserving console saved state across product upgrades is implemented (ID#4782)
New configuration options and configuration changes
CHARON must be installed as a Virtual Machine service using the new "CHARON VM Manager" utility. This utility also provides a central point to access all CHARON utilities (ID#4870, ID#4872)
PCI I/O Bypass controller is available. It allows to specify disk controllers as DI<x>, DR<x> and DU<x>, where x is selected according to VMS naming scheme (ID#4786)
The default log mode has been set to "append" in the configuration templates (ID#4752)
Updated CFG template files copyright message to year 2016 (ID#4720)
CFG template files are updated to provide correct examples for "hw_model", "system_name", "architecture" and "dsrdb" parameters (ID#4697)
Windows Registry path for CHARON products is updated to "HKLM:\Software\CHARON" (ID#4746)
New licensing options.
Field Test and Production builds offer identical functionality (ID#4552)
One license can serve CHARON instances on one host or different hosts by choice (ID#4884)
A special utility "License Alert" is added. It monitors CHARON license expiration date and warns user about it (ID#4903). Jul 20, 2017 Note: automatic installation removed when installing Charon-AXP. It has now to be installed manually
Software License transfer feature is disabled (ID#4787)
Installation improvements
New installation procedure is introduced starting from this version. It is not compatible with old CHARON installations, so the previous versions of CHARON must be uninstalled first.
Installation procedure is able to collect logs from executables it runs during installation/deinstallation (ID#4756)
New icons for utilities are introduced (ID#4973)
CHARON utilities
New CHARON Virtual Machine Manager is introduced (ID#4836)
Tape Utilities package is added (ID#3589)
Network Control Center is not allowed anymore to change the configuration of a disabled network adapter (ID#4725)
MkDisk utility graphics have been updated (ID#4743)
Network Control Center is able to save log (ID#4755)
MTD utility supports CHARON-SMA format (ID#4842)
LOGMOND utility provides sample scripts (ID#4902)
Problems fixed in build 183-02 since build 171-01
Fixed an auto-negotiation mode error leading to Tru64 inability to access network in VMware configurations (ID#4839, ID#4866)
Fixed AdvFS I/O error while running Tru64 Cluster setup (ID#3844)
Fixed DS20 intermittent boot failures %SYSBOOT-F-LDFAIL error 54 ("Unable to locate SYS$PUBLIC_VECTORS.EXE") (ID#4827, Case #00028604)
Fixed the logmond utility issue - it did not accept "-" symbols in log prefix (ID#4825, Case #00028633)
Fixed DS20 inability to survive SAN controller failure test (ID#4812, Case #00028599)
Fixed a VMS crash booting AXP models DS15, DS25, ES45 from SAN (ID#3976, Cases #00023850 and #00028131)
Fixed a hang of a CHARON instance if another CHARON instance, wrongly configured to use the same Emulex Pass Through device, is started (ID#4757, Case #00026541)
Fixed a multihost SCSI cluster quorum recalculation IPC interrupt issue, "DEPOSIT SIRR C" command now supported (ID#4758, Case #00028145)
Rolled back a DIT optimization which caused VMS crashes in Fortran debugger and RDB. This optimization will be fixed and applied in the next patch kit or release (ID#4781)
Fixed a wrong SRM console behavior which ignored invalid parameter(s) and executed incomplete commands entered. Now SRM console would report an error (ID#4795)
Fixed "Disable TCP chimney offload for CHARON" functionality (which caused CHARON to lose access to its license) (ID#4298)
Fixed wrong error message in log if no core is available for reservation (ID#4867, Case #00028768)
Fixed HASP View utility problem: it now reports that no license keys are available (ID#4896)
Fixed a problem leading to a situation when Cluster Alias vMAC does not work with virtual DE500(BA) (ID#4900)
Fixed a problem with TruCluster's Cluster Alias vMAC and legacy_mode parameter, preventing communication via DE602 adapter (ID#4904)
Fixed a negative value in CHARON log displayed in the case of long ID some Software Licenses (SL) may have (ID#4913)
Fixed HASP View crash on NetTime expired license (ID#4702)
Fixed "Exception (C0000005) at 000000000071EF9E: Segmentation violation" case (ID#4732, Case #00027809, Case #00027751)
Fixed Network Control Center failure to install NDIS driver if the log option is specified as a first parameter (ID#4864)
Fixed inability for Network Control Center to create log on successful installation of NDIS driver (ID#4865)
Fixed crash on each time when a specific Cobol module is compiled (ID#5010, Case #00029412)
Fixed crash with C++ exception from deep inside of MS Networking Stack (ID#4987)
Fixed "%EIA0, Auto Negotiation detected link down" and hanging on OpenVMS 7.2-1 (ID#4921)
Fixed mis-function of "Refresh" button in "HASP View" utility (ID#4971)
Fixed INCONSTATE Bugcheck on REBOOT in a specific customer configuration (ID#4921, Case #00028897)
Fixed bugcheck during installation of VMS 7.3-2 on as1000, as1200, as4000, as4100 and as800 models (ID#4930)
Configuration changes required when upgrading from previous versions of CHARON-AXP to build 183-02
A 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 CHARON installation procedure update, it is required to uninstall all CHARON products before installing CHARON-AXP version 4.8. Use Windows Control Panel for that.
The following Microsoft Windows update has to be installed on Windows 7, Server 2008 R2 and 2016 in order to support new CHARON drivers signed with SHA2 signature:
https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929If VMware is used, it must be upgraded to version 5.x or 6.0
The Tru64 kernel might require a rebuild for some emulated AXP models that are included in the CHARON-AXP/4100 product
It's 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" (Network Control Center) 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 and screen saver should be switched off on the hosting server
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 \\.\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:and
can be replaced with:
For the emulated network adapters the communication speed and mode is recommended to be commented out (set to automatic). If it is necessary, the example is below:
On VMware, legacy_mode should be set in CHARON configuration for emulated AXP network adapters if Promiscuous mode cannot be set (this solution does not work in multi-instance configurations)
Known restrictions of build 183-02
Network and tape booting are not supported.
The total number of devices (both controllers and units, including disks) displayed by CHARON SRM console is limited to 48. Note that it does not affect the actual number of configured devices provided to CHARON guest OS.
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 SRM console. This problem does not affect CHARON functionality (ID#4729)
CHARON cannot correctly define the total number of available CPUs on mutli 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" from 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
SRM console shows the configured virtual disk names differently for same *.vdisk containers on each CHARON start (ID#4498)
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 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-AXP does not emulate LSI 53C810 SCSI controller. CHARON-AXP emulates Qlogic KZPBA SCSI controller, which is the reason for the earliest supported VMS version to be 6.2-1H3, earliest supported Tru64 version to be 3.2. (ID#2291).
If the driver for KZPBA is installed on an earlier version of VMS or Tru64 before system transfer to CHARON-AXP, it will function on CHARON-AXP.
OPA0 console of CHARON service does not appear if non "Administrator" user is starting the service (ID#3209)
DS20 initialization might take long time on Windows Server 2008 R2 (ID#3194)
Digital UNIX 4.0g fails to install on AS4100 if FC is configured. Specific Tru64 patches and firmware versions might be required. SAN device should be set to SCSI-2 mode (ID#3191)
DE500BA device error count after boot is not 0 on OpenVMS 8.2/8.3 (ID#2963). There are no negative side effects
Direct SCSI access only supports Windows SCSI devices which use a SCSIport driver. These include most of the device drivers on Windows XP and Windows Server 2003 (R2), but does not work on Windows 7 and Server 2008 (R2). If SCSIport is not supported (and Storport method is used instead), direct SCSI access cannot be used.
This is most likely to be the case for Windows 7 and Windows Server 2008 (R2) platforms.Performance tests could hang VMS 6.2-1H3 on emulated AS400.
CHARON-AXP does not emulate VGA adapters, thus OPA0 is always a system console. Applications hardcoded to use OPA0 and TTA0 as their own interfaces may not function correctly.
Network speed auto negotiation works with some restrictions (see the table below). It is always recommended to use full duplex mode on the hosting server.
The virtual Alpha firmware is designed to show a maximum of 48 devices. However more devices are available to VMS and Tru64
The firmware does not support the command recall using the up/down arrow keys.
The VMS 7.x Monitor utility shows the maximum CPU quantity instead of actually configured quantity. It does not apply to VMS 8.x
Running Alpha Linux on the virtual Alpha is not supported
Use of IDE is limited to ATAPI CDROM on the host machine. No iSCSI support is planned for IDE. UETP may produce error messages if IDE emulation is used.
A Telnet session from OpenVMS running on emulated host freezes console output. The console output can hang when the virtual serial line sends XOFF/XON sequence. The TELNET client sends XOFF to the remote node's TELNET server to suspend output, but for unknown reason XON is discarded and remote node's TELNET server is unable to resume output. The console remains "frozen" as the remote site is not sending any output to it. When that happens, the local node is reachable over network, and can be unlocked by typing the 'break' character - usually "Ctrl-]" and exiting telnet session by typing "exit" at "TELNET>" prompt.
Emacs hangs if the OPA0 console is used. Emacs works fine over an SSH connection.
CHARON-AXP does not support Microsoft virtual network adapters (i.e. MS bridges, etc.).
CHARON-AXP has limited support for teamed network adapters. They can be used only if the MAC address of the virtual VMS or Tru64 network adapter is not changed during CHARON-AXP session. In which case the desired MAC address should not be set manually in the properties of the network team or in the CHARON-AXP configuration file using the "station_address=XX-XX-XX-XX-XX-XX" configuration option.
VMS 7.2-1 should be patched to the latest level in order to use Emulex FC adapters in pass-through mode.
Please note that CHARON-AXP has not been tested with SAN attached storage over 2TB per disk in size.
Tru64 temperature monitoring should be disabled. It could cause Tru64 version 5.x shutdown with the message: "system fan has failed, system is shutting down now". If installing Tru64 from scratch, do not install envmon package. If it is already installed, disable automatic startup by booting into SINGE USER mode and issue the following commands:
then "exit" (Ctrl-D) to multi user mode.
A "CRC error" appears while "
$ BACKUP/LIST/REW MKA100:..." on OpenVMS Alpha Version 8.4 (ID#2925)
New functionalities introduced in previous builds
New functionalities introduced in version 4.7 build 171-01
New platform support
Microsoft Windows Server 2012 R2 (please notice Server 2012 is not supported)
VMware ESXi 6.0
Microsoft Hyper-V on Server 2012 R2
Please notice Microsoft Windows XP and Windows Server 2003 are not supported (ID#4498)
CHARON product packaging
All emulated AXP models are installed by default. Allowed AXP models are controlled by CHARON license (ID#4711)
New icons and graphical design for CHARON executables, utilities and installation procedure (ID#4586, 4587, 4588, 4688)
Performance improvements
General performance improvement up to 10% for some usage scenarios (ID#4474)
Deep I/O queuing is implemented for virtual SCSI adapters. Using up to 8 parallel I/O threads per disk and up to 16 per controller can significantly improve I/O performance if guest applications can benefit form multi threaded I/O (ID#3144)
Internal CHARON-AXP performance counters for various subsystems (CPU, DIT, Network I/O, and Disk I/O) may be streamed to the CHARON log file. The log has to be sent to Stromasys for analysis (ID#4141)
Stability in FC Presentation mode has been improved (ID#4294)
New configuration options and configuration changes
MPIO storage path support is implemented (ID#4328)
Write-through caching of virtual disks is implemented; it can be set with a parameter "use_io_file_buffering = write-through". By default it is switched off. (ID#4613)
VLANs are supported (ID#4401)
Sample configuration files are updated with correct values for "hw_model", "system_name", "architecture" and "dsrdb" parameters (ID#4697)
The log file language is set to English (ID#4509)
CARON log file format switched to UTF-8 (ID#4188)
Rotating log file switch can be configured to be triggered by maximum file size and time period (ID#4639)
CHARON console log rotation has been implemented (ID#4639)
New licensing options. Please refer to User Manual and online Knowledge Base for details, technical restrictions, and best practices (ID#2856, #4137, #4285)
Software licensing (SL) is available. Software license is bound to physical system hardware components or virtual machine hardware components (ID#4344)
Network licensing is available, for both hardware dongles (requires special dongle) and software licensing
CHARON instance counter on a Network license switched to instance mode from station/instance mode, which allows CHARON instances to be spread around the network at user convenience. For example, a Network license with 6 CHARON instances allows to run 3 instances on a first hosting server, 2 instances on a second hosting server, and one instance in a third hosting server. In the previous versions of CHARON Network license controlled number of hosting systems and CHARON instances per host system.
CHARON license check order can be managed via configuration file, Production and Backup license IDs can be specified (ID#4249)
Software License can be relocated to another host
New parameter "license_key_lookup_retry" has been introduced allowing to set a number of license retries with specified time interval for the license checks on CHARON startup (ID#4399)
License protection run time package (Sentinel) has been upgraded to the current stable version (ID#4209, 4711)
Please notice that CHARON HASP runtime environment is customized by Stromasys. Environment downloaded directly form SafeNet would not provide full functionality (specifically, Software Licensing will not work). Stromasys will maintain and distribute HASP environment updates as CHARON product patches if necessary
CHARON utilities
Logmond supports multi instance and rotating log configurations
MTD utility supports SCSI Passthrough mode for tapes without Windows driver (ID#3927)
DE602 network adapter is added to Network Control Center configuration page (ID#4655)
Network Control Center (Network Control Center) performs CHARON network driver cleanup on request (ID#4610)
CHARON utilities fully support mixed encoding in log files (ID#4642, 4646)
mkdskcmd utility does not allow to reduce vdisk size (ID#4506)
New functionalities introduced in version 4.6 build 163-03
New "HASP View" utility is able to show all the available license keys and the content of the license they contain (ID#4461)
CHARON log is created in English language only, the rest of localization are disabled (ID#4509)
DS10 emulator is added to CHARON-AXP/DS10 product (ID#4176)
EI device support - DE602 (Compaq NC3131) network adapter is added (ID#4185)
Sentinel Software Licensing (SL) is fully supported (ID#4344)
HASP View utility is able to display the multi site configuration license parameters and it is improved (ID#4059, 4165)
PCI device multifunction is fully supported (ID#4007)
CPU IDLEing is enabled for all Alpha emulators on OpenVMS (ID#4090)
CHARON licenses can be controlled via CFG file now: it is possible to specify main and backup key (ID#4249)
PCI-to-PCI bridges are supported (ID#4428)
"license_key_lookup_retry" parameter is introduced. It allows for a number of retries with specified interval while accessing CHARON license at guest startup before CHARON stops. (ID#4399)
CHARON supports disabling network offload features with a special option in Network Control Center (Network Control Center) (ID#4298)
CHARON can be monitored by specific counters with a help of an external diagnostic data collection (ID#4385)
Since this release CHARON uses UNICODE for its log files (ID#4188)
CHARON license protection has been significantly improved (ID#4209)
Statistics counters for storage and network subsystems are implemented (ID#4141)
Log file messages are extended with indications of CPU "Halt"/"Run" transitions (ID#4264)
New parameter "sync_to_host" is implemented. It allows to keep TOY time always synchronized with the host's time and disable undesirable updates to the TOY from guest OS. (ID#4144)
CHARON-AXP SRM console "halt" command is implemented (ID#4239)
CFG templates have been corrected and updated (ID#4240, 4369, 4377)
MkDisk utility is able to extend the existing disk container size without destroying its content (ID#4329)
EIx0_MODE environment variables of DE602 (Compaq NC3131) are implemented (ID#4366)
HASP driverless mode is supported (ID#4455)
"logmond" utility is significantly improved. Now it supports CHARON rotating log and multi-instances configurations - it is able to monitor log files of all CHARON instances running as services on host.
Networking part (carrier sense logic) is improved (ID#4339)
Network Control Center supports VLAN (ID#4453)
Physical PCI Fiber Channel Presentation Mode is supported (ID#4294)
The performance improvement package included into the kit is updated (ID#4424)
New functionalities introduced in version 4.5 build 153-07
CHARON-AXP is supported on VMware ESXi from version 4.1 Update 1 up to version 5.5
New emulated models AlphaServer DS15, AlphaServer DS25 and AlphaServer ES45 have been added to corresponding products CHARON-AXP/DS10, CHARON-AXP/DS20, and CHARON-AXP/ES40 (ID#3523)
Configurable WWID for virtual KGPSA adapter (ID#3875)
DG devices may contain up to 5 digits in their names, for example DGA15000 (ID#3790)
SRM Console version, OpenVMS PALcode version and Tru64 UNIX PALcode version can be explicitly set (ID#3870)
All the help files have been converted to CHM format (ID#3818)
"PhysicalDrive" specification may include drive number, serial number or WWID (ID#3667)
"system_serial_number" setting is introduced to set AlphaServer's serial number (ID#4096)
Command line version of the Mkdisk utility is able to report progress of disk creation (ID#3793)
PCI board (HBA) model is logged in CHARON log file (ID#3801)
InstallShell is able to upgrade old NDIS5/6 driver installed by other CHARON kit (ID#3819)
"hasp_view" utility has been improved for Sentinel SL (EMS) HASP AdminMode license (ID#3847)
New functionalities introduced in version 4.4 build 148-02
CHARON-AXP version changed to 4.5. A license update is required (ID#3701)
CHARON-AXP is supported on VMware ESXi 5.1
CHARON Production license dongle could be replaced with Backup or Spare dongle, and vice versa, without stopping CHARON. The backup/spare dongle is only accepted if CHARON instance configuration parameters remain unchanged (ID#3690)
CHARON license expiration date can be updated without stopping CHARON. Please notice that CHARON instance configuration parameters for active instances should remain unchanged (amount of CPU's etc.) (ID #2966, #3206)
Network license protection is supported by CHARON-AXP. Network licensing is available from Stromasys as a service (ID#3095, 3546)
HASP_View utility is improved in order not to decrease Backup license counter (for Sentinel HASP section only), to detect Remote Desktop sessions and to view Network licenses (ID#3310, 3742, 3757, 3539, 3637)
Log rotation mechanism and improved log filtering is implemented. New log file is created once a week (ID#2281, 2608, 2989)
Missing license on startup is now logged (ID#3116, 3775)
Console log can be stored in a separate file (ID#3587)
Console variable "date" is implemented in order to read date and time from the host OS (ID#2743)
"geometry" CFG file option is introduced to specify size of tape image and, optionally, size of "early-warning" area at the end of tape image (ID#2561)
\\Changer device class has been implemented to provide access to tape changer devices on Windows Server 2008 R2 and Windows 7 (ID#3369)
Installation procedure is improved, silent (batch) mode is implemented (ID#3618, 3532, 3388)
CHARON Emulex PassThrough driver supports HP 82E 8Gb Dual-port PCI-e FC HBA (ID#3739)
Configuration templates are updated; CPU architecture, AXP model, system ID, and LURT could be set in the config file. CHARON rejects illegal set of parameters (ID#3260, 3307, 3511, 3541)
Network Control Center reports critical issues even in silent mode (ID#3617)
New functionalities introduced in version 4.2 build 142-02
CHARON-AXP version changed to 4.2.
CHARON-AXP is supported on VMware ESXi 5.0
Emulated DEC-KGPSA-CA (Emulex LP8000 FC PCI) controller is introduced, providing users with ability to access container files and physical drives/LUNs as virtual SAN disks. Please refer to the user manual for the configuration details
Shared storage clustering support based on shared physical SCSI storage is introduced for Tru64
Shared storage clustering support based on emulated SAN disks/LUNs is introduced. VMS and Tru64 5.1 shared storage clusters are supported. Tru64 4.x shared disk clusters are not supported in the current release.
NetApp SAN storage support is introduced
"geometry" option has been added to the KZPBA controller (ID#3330)
Disk I/O performance is improved by deep queueing of I/O requests
TL891 hardware tape library support is introduced
Virtual tape size could be limited through CHARON-AXP configuration file
Virtual CDROM container file can be replaced without stopping CHARON
SRM console variable "date" is introduced. Accessing this variable from VMS/Tru64 provides them with the time read from the hosting server
CHARON-AXP automatically replaces the old .ROM file with a new one on the first run after CHARON-AXP upgrade. Please notice that ROM parameters have to be reconfigured
CHARON-AXP installation and uninstallation does not require CHARON-AXP license to be present
CHARON-AXP Spare license is supported (limited by support contract expiration date and execution counter). License viewing utility is updated
Some CHARON-AXP DIT cache parameters are configurable. Those options are available under Stromasys field engineering supervision only
A standalone utility to monitor CHARON log file and trigger an external batch in case of CHARON-AXP license failure is introduced (ID#2415)
CHARON-AXP configuration templates are updated to reflect new configuration options
New functionalities introduced in version 4.1 build 129-04
CHARON-AXP version changed to 4.1.
CHARON-AXP is supported on VMware ESXi 4.1 update 1.
CHARON-AXP comes with the maximum amount of RAM allowed by emulated model. Please refer to the product SPDs for the details.
The following license information could be updated without stopping CHARON-AXP: expiration date and backup time counter. This change allows CHARON evaluation or annual licenses to be updated "on the fly" to the permanent production licenses or to the next year annual licenses. Please notice that other CHARON configuration parameters should remain unchanged.
Additional CHARON-AXP instances and products could be added to the license "on the fly".
New Alpha emulated models are added to CHARON-AXP/4100 product:
AlphaServer 800 (single AXP CPU)
AlphaServer 1000 (single AXP CPU)
AlphaServer 1000A (single AXP CPU)
© Stromasys, 1999-2025 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
Need fast, reliable migration? We have done it countless times. Talk to an expert