...
After copying the packages to the Charon-SSP AWS instance, install the packages as described below. For details, please refer to the relevant man-pages on Linux.
Step | Details |
|---|---|
| 1 | Log in to the Charon-SSP AWS via SSH to the sshuser and become the root user ( |
| 2 | Go to the directory where the packages have been stored:
|
| 3 | Run upgrade command: |
For systems with RPM package management (Red Hat, CentOS): |
Upgrading Charon Manager on the Management Linux System
There are two ways to upgrade the Charon Manager on the management Linux system.
Standard Linux Package Update
Step | Details |
|---|---|
| 1 | Log in as the root user. |
| 2 | Go to the directory where the packages have been stored:
|
| 3 | Run upgrade command: |
For systems with RPM package management (Red Hat, CentOS): | |
For systems with Debian package management (Debian, Ubuntu): |
| Div | ||
|---|---|---|
| ||
Automatic Update upon First Connection to Updated Charon Host System
New feature in Charon-SSP 4.0.x.
If you connect to a Charon host system using an older version of the Charon Manager than the one used on the host system, you will be offered an automatic update to the version of the Charon host system.
The following image shows a sample:
Confirm the upgrade by clicking on Yes. This will initiate the download and installation of the new version. If you work as a non-privileged user, you will be prompted for your password. To decline the automatic update, click on Cancel.
This mechanism also works for downgrades (i.e., if the Charon Manager version is newer than the version of the Charon host system it connects to, it can be automatically downgraded to the version of the target system).
...
Steps (only meant for illustration - the details could vary depending on the customer environment):
- Create new an instance with the new Charon-SSP version in the same subnet as the old instance . Use the (same security group and key pair as in the old instance).
- Backup emulated SPARC disks and configuration data on the old instance to the separate EBS volume.
- If applicable, backup important system configuration files to the separate EBS volume.
- Shut down guest systems and stop running emulator instances on the old host system.
- Stop the old instance.
- Copy the Charon Manager kit from the new instance and install it on your local Linux system, or connect to the new instance via Charon Manager to initiate the automatic Charon Manager update.
- Move the EBS volume(s) and (if applicable) network interfaces with elastic IP addresses to the new instance.
- Import the virtual SPARC configurations on the new system.
- Adapt the host system configuration as needed.
- Start the guest systems.
- If everything works, terminate the old instance.
...