Table of contents

‘vi’ and 'vim' text editors

Notes:

• When typing text, press <ESC> once finished. In case you’re blocked, press also <ESC> before executing commands described below
• both editors use case sensitive commands

‘gedit’ graphical editor

‘gedit’ is a graphical text editor, users familiar with Windows notepad should not encounter difficulties to use it.

‘nano’ text editor

‘nano’ is a basic text editor, very simple to use and displaying available commands at the bottom of the screen. For example, to leave ‘nano’ , use ^X (press CTRL + X)

How to setup ‘ssh’ trusts between Linux and Tru64

• Generate the key

• Copy the linuxhost.pub file, or use copy/paste, in the /.ssh2 folder on the Tru64 host
  
  
• Define the authorization file:

• Initialize the first ssh connection (answer 'yes' to confirm)

then retry the same command to verify the trust is working.

If an error occurs, you can check and clean the /root/.ssh/known_host file on the Linux host

If trying to execute a remote command on the Tru64 system, a message telling "no matching cipher found" is displayed, the cipher has to be setup on the Linux server side in the /root/.ssh/config file:

How to setup ‘ssh’ trusts between Linux and VMS

• Enable SSH on the VMS server:
  
  

  VMS$ SET DEF SYS$LOGIN VMS$ @TCPIP$CONFIG

• Select then:
  • Option 3 - Server components then enable and start service SSH, option 19

  • then Option 2 - Enable & Start service on this node
    
    

    ... * Create a new default server host key? YES: YES      Creating private key file: TCPIP$SSH_DEVICE:TCPIP$SSH.SSH2]HOSTKEY      Creating public key file: TCPIP$SSH_DEVICE:TCPIP$SSH.SSH2]HOSTKEY.PUB ...

• Generate the key on the Linux server and convert it to be readable by VMS
  
  

  Linux# ssh-keygen -t rsa → Do not specify a passphrase Linux# ssh-keygen -e -f /root/.ssh/id_rsa.pub > /root/.ssh/linuxserver.pub

• Copy the generated file /root/.ssh/linuxserver.pub (or use copy/paste between putty session for example) to the VMS system in the SYS$SYSROOT:[SYSMGR.SSH2] directory
  If this folder does not exist, create it using the following command: $ CREATE /DIRECTORY SYS$SYSROOT:[SYSMGR.SSH2]

• On the VMS system add the Linux server key to the authorized keys:
  
  

  VMS$ SET DEF SYS$SYSLOGIN VMS$ SET DEF SYS$SYSROOT:[.SSH2] VMS$ OPEN/WRITE TMP AUTHORIZATION. If the file already exists, use /APPEND instead of /WRITE VMS$ WRITE TMP "KEY LINUXSERVER.PUB" VMS$ CLOSE TMP

  Do not forget the dot at the end of the authorization file name

• Perform some tests (examples)
  Charon server name "charon", vms system name "pluto":
  
  

  charon# ssh system@pluto "show system /noproc" OpenVMS V7.3-2 on node PLUTO 27-SEP-2013 11:50:14.37 Uptime 0 19:20:07

How to setup ‘rsh’ trusts between Linux and Tru64

Introduction

RSH executes commands on a remote host. It can be used to issue a shutdown on the Charon Tru64 virtual machine.

Pre-requisites

The RSH method requires the 'rsh' package. It can be installed using the following command:

Notes

On the Tru64 system issuing the shutdown, create a proxy between the root user of the Charon server and the user.

Example ('ceres' is the Charon server name):

If the Charon server name is not known to the TCPIP database, edit the /etc/hosts file and add the server ip address and its name.

Ensure manual commands can be passed to the Tru64 system from the Charon server.

Example ('pluto' is the Tru64 hostname):

If a "poll: protocol failure in circuit setup" is returned, the firewall settings have to be set to open ports 113 and 1022.

Please always refer to your network administrator when changing the firewall rules, commands below are given as example only.

Example for Red Hat Enterprise Linux 6.x servers:

Example for Red Hat Enterprise Linux 7.x and CentOS 7.x servers:

How to setup ‘rsh’ trusts between Linux and OpenVMS

Introduction

RSH executes commands on a remote host. It can be used to issue a shutdown on the Charon OpenVMS virtual machine.

Pre-requisites

The RSH method requires the 'rsh' package. It can be installed using the following command:

Notes

RSH and REXEC services must be available on the OpenVMS virtual machine. This depends on the OpenVMS version and a valid UCX license is required.

To enable these services, run @SYS$MANAGER:TCPIP$CONFIG, select the "Client components" and then enable and start "REXEC and RSH" services.

Create a proxy between the root user of the Charon server and the user on the OpenVMS system issuing the shutdown.

Example ('ceres' is the Charon server name):

If the Charon server name is not known to the TCPIP database, use the following command to add it.

Example:

Copy charon_shutdown.com script located in the /opt/charon/utils folder to SYS$MANAGER:CHARON_SHUTDOWN.COM on the OpenVMS system (using copy/paste for example). This is required as if the shutdown is executed directly from the 'rsh' command directly, 'rsh' will not timeout when the shutdown will be completed and the virtual machine will not be stopped cleanly, it will timeout depending on the service settings.

Ensure manual commands can be passed to the OpenVMS system from the Charon server.

Example ('vms084' is the OpenVMS hostname):

If a "poll: protocol failure in circuit setup" is returned, the firewall settings have to be set to open ports 113 and 1022.

Please always refer to your network administrator when changing the firewall rules, commands below are given as example only.

Example for Red Hat Enterprise Linux 6.x servers:

Example for Red Hat Enterprise Linux 7.x and CentOS 7.x servers:

Shutdown guests with Expect tool

Introduction

In case SSH cannot be used to perform clean shutdown of the guests, the "expect" tool can be used to connect to the console, perform the login operation and execute the shutdown command depending on the console status (at login prompt, shell prompt or SRM prompt)

 In this case the password is sent without encryption.

To facilitate use of "expect" for shutdown, an example is provided in the "guest_shutdown.exp" script located in the /opt/charon/utils folder. If you plan to customize the script, you'll have to create a copy and not use it directly as it will be overwritten in case of Toolkit upgrade.

This script can handle the following situations:

• No user connected on the console:
  
  • Expect: "Username: " (VMS) or "login: " (Tru64)
  • Action: An interactive session will be initiated based on <user> and <password> provided in the parameters
• A user is connected on the console:
  
  • Expect: <prompt> provided in the parameters
  • This user must have privileges to perform shutdown as no logout will be issued
  • Action: Depending on the Operating system parameter (see <opsys> below), the shutdown command will be sent
• Console is at SRM prompt:
  
  • Expect: ‘>>>’ (so works with VAX and Alpha with "P00>>>")
  • Action: A 'power off' command will be issued. If the command is not recognized, the F6 key will be sent (this must be enabled within the configuration file). If the F6 key did not stop the emulator, the script will exit with error code 9 meaning you will have to kill the emulator process yourself. Using the "/opt/charon/utils/charon_gstart_expect" script file the necessary operations will be performed.

Script usage

Usage:

# path/script <port> <user> <password> <prompt> <opsys>

Parameters:

Example:

How to restart CHARON-VAX/AXP on Linux automatically on failure

This part only applies to Linux distributions using systemd thus Red Hat Enterprise Linux 6.x versions are not concerned.

• Edit the service configuration file and add the following parameters using the "VM Management" option from the menu then "Manage 'systemd services".

• Update the service and server boot parameters as described in the appendix How to restart Charon-VAX/AXP on Linux automatically on failure