...
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
...
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
| Div | ||
|---|---|---|
| ||
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:
# yum install rsh |
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):
# echo "ceres root" >>~/.rhosts |
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):
# rsh pluto date |
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:
# yum install rsh |
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):
$ tcpip add proxy system /remote="root" /host=ceres |
If the Charon server name is not known to the TCPIP database, use the following command to add it.
Example:
$ tcpip set host ceres /address=1.2.3.4 |
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):
# rsh -l system vms084 "show time" |
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:
# firewall-cmd --permanent --new-service=Charon# firewall-cmd --permanent --service=Charon --add-port=113/tcp# firewall-cmd --permanent --service=Charon --add-port=1022/tcp# firewall-cmd --get-active-zonespublic interfaces: ens34 ens35# firewall-cmd --zone=public --permanent --add-service=Charon# firewall-cmd --reload |
| Div | ||
|---|---|---|
| ||
Shutdown guests with Expect tool
...
| Warning |
|---|
Console locked: Any active session to the console must be killed before the "
|
...
- 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
- Expect: "
- 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 (see examples in . Using the "/opt/charon/utils/charon_gstart.stop.example" file)_expect" script file the necessary operations will be performed.
- Expect: ‘
| Div | ||
|---|---|---|
| ||
Script usage
...
| Parameter | Description |
|---|---|
| <port> | telnet port number (example: 10003) |
| <user> | username for login (must be able to perform shutdown) |
| <password> | password |
| <prompt> | shell prompt (including end space) or last characters of the prompt |
| <opsys> | VMS or UNIX |
Example:
Examples are given in the /opt/charon/utils/charon_gstart.stop.example file
How to restart CHARON-VAX/AXP on Linux automatically on failure
...
- Update the service and server boot parameters as described in the appendix How to restart CHARONCharon-VAX/AXP on Linux automatically on failure
...