Version: 1 - Published: Feb 24, 2021 

Table of Contents

Please review this document before proceeding with installation of CHARON-VAX for Linux

Products included in the CHARON-VAX version 4.11 build 204-10 for Linux

In this document the terms CHARON and CHARON-VAX are used to refer to all the products below:

• CHARON-VAX/XM version 4.11 build 204-10 for Linux

• CHARON-VAX/XM PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/XK PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/XL version 4.11 build 204-10 for Linux

• CHARON-VAX/XL PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/6610 PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/6620 PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/6630 PLUS version 4.11 build 204-10 for Linux

• CHARON-VAX/6660 PLUS version 4.11 build 204-10 for Linux

Supported software platforms

• Red Hat Enterprise Linux 8.x - 64bit

• Red Hat Enterprise Linux 7.x - 64bit

• Red Hat Enterprise Linux 6.5 to 6.10 - 64bit

• Linux Centos 8.x - 64bit

• Linux Centos 7.x - 64bit

• VMware ESXi 5.5 and 6.0 up to 6.7 (requires a supported Linux operating system on top of a ESXi 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 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.

• DDR4 RAM 2133 MHz and above is recommended for optimal CHARON performance.

• The minimum host memory size depends on the amount of emulated VAX memory and on the number of CHARON instances running on one host. The minimum host memory = (2Gb +  the amount of VAX memory emulated) per CHARON-VAX 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-VAX 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.

• 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

New functionalities introduced in build 204-10 since previous release (build 204-09)

• None, used to match build number of Charon-AXP in case both products are installed on the same server.

New functionalities introduced in build 204-09 since previous release (build 202-03)

• Sentinel Runtime upgraded to version 8.13.

• Special version of NCU (Network Configuration Utility) is included with Linux products for RHEL8

• Remote management console feature added. Its purpose is to let the emulator trigger actions on the Charon host to properly unload and save a vtape container while the guest operating system is running.

• To facilitate online log monitoring by third-party tools, the log file (session or OPA0) is flushed on disk regularly. Interval for periodic flush to be supplied through configuration file (optionally) (ID#5532)

• New version of PuTTY, supporting "-title" option (ID#5590)

• The parameter "port_enable_mac_addr_change" is available on Linux version of Charon as well (ID#5594)

• Charon executable files print a summary of options on "-h" or "--help" command line option (ID#5578)

• Sample configuration files are updated (ID#5246, #5622)

Problems fixed

Problems fixed in build 204-10 since build 204-09

• None, used to match build number of Charon-AXP in case both products are installed on the same server.

Problems fixed in build 204-09 since build 202-02

• Fixed DEMNA implementation to prevent VAX 6000 Model 6x0 from hang while joining NI cluster on boot.

• Very new SCSI tape drives may fail if they are addressed via "physical_scsi_device" instance (as it is recommended). In this case their support is provided via "virtual_scsi_tape" instance (ID #5488)

• Fixed a problem leading to repeating "circuit down" situation immediately followed by STARTNET if DEMNA network interface is used (ID #5641

• Fixed a problem when specification of "log_rotation_period = 0" ("never") worked not correctly (ID#5580, Support Case 00031938)

• Fixed a problem with fast growing "Unrecognized frame destination" counter of DEMNA with customer application on VAX 6000 Model 610 (ID#5617)

• Fixed a problem when negotiated line speed is reported incorrectly at DECnet startup (ID#5626)

• Fixed a problem when sometimes PT.EXE (performance tool) may freeze (ID#5614)

• Fixed a problem with CPUSPINWAIT bugcheck of VAX 6620 (ID#5551)

• DEMNA logging mechanism is corrected (ID #5646)

• Serial lines logging is corrected (ID #5647)