| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
...
The Charon-PAR/PA3 functionality of Charon-PAR emulates historic PA-RISC systems for MPE/iX. This section shows a sample installation of an MPE/iX guest system
Emulator Licensing Considerations
| Excerpt | ||
|---|---|---|
| ||
The emulator needs a valid license to run. The license can be a Sentinel HASP license or a Virtual Environment (VE) license. Please refer to Initial Emulator License Configuration for the basic license configuration steps of both options. The license(s) to be used are defined in the configuration file. If running in a cloud environment, a VE license is strongly recommended (supported from Charon-PAR version 3.0.6). |
Downloading and Unpacking the Provided MPE/IX Disk Container
If not already done, please download the image with the preconfigured MPE/IX 7.5 disk container from Stromasys. Contact your Stromasys representative or your VAR for download instructions. The preconfigured LDev1 image allows the emulated system to boot without having to separately install or update MPE/iX.
...
After this step, if the image is not needed for other systems, you can delete the compressed image to save disk space.
| Div | ||
|---|---|---|
| ||
Adapting the Configuration File Template
The configuration file template must be adapted to the customer environment and the required guest system characteristics. This section describes the minimum number of changes required to configure a Charon-PAR/PA3 emulator instance. Please refer to Configuration File Reference for a detailed description of the configuration file options.
...
| Step | Description (configuration file settings are examples!) | |
|---|---|---|
| 1 | Create a copy of the configuration file template. | Example:
|
| 2 | Open the configuration file in a text editor. |
or
|
| 3 | Configure the system model. | model "A400-100-110" |
| 4 | Configure the RAM for the emulated system. | memory 2G |
| 5 | Configure LDEV 1 (preconfigured system disk). | Change definition of DKA0 to:
|
| 6 | Configure a tape devices. | Change definition of MKAx to:
|
| 7 | Configure a network card based on a physical host NIC. This NIC is dedicated to the guest operating system and cannot be used for network communication by the host system. To share an interface, a virtual bridge would have to be used (see Ethernet configuration sections in this document). | In the configuration file template, comment out the dummy interface and the tap interface configuration. Then uncomment the interface configuration of the physical interface example. Change the definition of EWA0 to the interface that is assigned to the emulated system (example: eth1) and disable the offload parameters for the interface:
Depending on the capabilities of the Ethernet device, not all offload parameters maybe be available. This will create a warning message. The variable IFACE is set by the system before executing the initialize command. For cloud environments, please note:
|
| 8 | Save the configuration file. |
| Div | ||
|---|---|---|
| ||
Starting the Charon-PAR/PA3 Emulator Instance
Please note: The examples in this section assume that a graphical interface is used, on which a PuTTY session can be run. Should this not be possible, you can access the console of the emulated system by using, for example, a telnet client and pointing it to the TCP port on the Charon host defined for the serial console port in the configuration file. The default port is 30000 (sample command to connect to an emulator on the local system: $ telnet localhost 30000). In this case, do not start the PuTTY program automatically from the emulator configuration.
...
The image below shows how to use the HELLO command to log into the booted guest system:
Basic Network Configuration
Default configuration
The preconfigured MPE/iX disk also includes preconfigured network settings:
...
| Excerpt |
|---|
Stromasys provides a special command file (SETIP.CHARON.SYS) in the preconfigured MPE image. This command file enables the user to configure the network without using a block-mode terminal that would otherwise be required to access the relevant MPE utility (NMMGR). The command file takes three parameters: host IP address, default gateway address, and netmask. The image below shows a sample:
After changing the configuration, the command file will automatically restart the network to activate the changes. For cloud environments, please note: in case of a dedicated Ethernet interface, the IP address of the emulator must be set to the value assigned by the cloud provider to the corresponding host NIC. |
| Div | ||
|---|---|---|
| ||
Stopping the Emulator
In order to stop the emulator in an orderly manner, perform the following steps:
...