...
- Requirements for direct ESXi host binding:
- The VE license server must run in one of the VMs on the ESXi server.
- ESXi/vSphere version 6.5 and above.
- Valid license that supports the vSphere API feature.
- Ports 443 and 902 must be accessible to the VE license server host.
- 100 MB of free disk space to be used by the VE license server host.
- Administrative user (and password) on the ESXi/vSphere host used for the binding between license server and ESXi/vSphere host.
- Requirements for vCenter Server binding:
- The VE license server must run in a VM on one of the ESXi systems managed by the vCenter server.
- Ports 443 and 902 must be accessible to the VE license server host.
- 100 MB of free disk space to be used by the VE license server host.
- Administrative user (and password) on the vCenter server used for the binding between license server and vCenter server.
Please note: vMotion cannot be used for the virtual machine running the VE license server can only be used if the license server binds to the vCenter Server.
Linux Host Requirements for the VE License Server
...
Below, you find the sample output of an installation (RHEL/CentOS 8.x, assuming that the RPM is in the current working directory):
Code Block | ||
---|---|---|
| ||
# yumdnf install license-server-1.01.355.rpm Loaded plugins:Last fastestmirror,metadata langpacksexpiration Examining license-server-1.0.35.rpm: license-server-1.0.35-1.x86_64 Marking license-server-1.0.35.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package license-server.x86_64 0:1.0.35-1 will be installed --> Finished Dependency Resolution Dependencies Resolved =check: 1:14:52 ago on Fr 29 Jan 2021 09:46:32 CET. Dependencies resolved. ==================================================================================== Package Arch Architecture Version Version Repository Size ================================================================================ Installing: license-server x86_64 1.01.355-1 /license-server-1.0.35 @commandline 7952 M Transaction Summary ================================================================================ Install 1 Package Total size: 7952 M Installed size: 79 M Is this ok [y/d/N]: y Downloading packagesPackages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction InstallingPreparing : license-server-1.0.35-1.x86_64 1/1 VerifyingRunning scriptlet: license-server-1.01.355-1.x86_64 1/1 Installing 1/1 Installed: : license-server.x86_64 0:-1.1.0.355-1.x86_64 1/1 Running scriptlet: license-server-1.1.5-1.x86_64 Complete! | ||
Div | ||
|
Charon-SSP VE-Capable Emulator Software Installation
General Information
The Charon-SSP packages are RPM packages that are installed using the yum (Linux 7.x), dnf (Linux 8.x), or rpm command. They can be copied to the Charon host system using SFTP as shown in the example for copying the license server RPM.
At least the required emulator packages (charon-ssp-4*.rpm) and the agent (charon-agent*.rpm) must be installed for the system to run emulated SPARC systems and to allow remote management by the Charon Manager. If local management with graphical tools is required, then the Charon Manager and the Charon Director packages must also be installed.
For detailed host system requirements and for the management of the Charon-SSP software, please refer to the regular Charon-SSP documentation on the Stromasys Product Documentation and Knowledge Base pages.
Please note: To use the graphical user interface (Charon Manager for SSP) the Charon Manager package typically is installed on your local Linux or Windows PC that will be used for management purposes. Running the Charon Manager in a non-graphical cloud instance and export it via X11-Forwarding is possible, but will require additional configuration and installation steps (with access to a package repository) - this is outside the scope of this document. It is also possible to manage Charon-SSP via the command-line only. This is described in the general Charon-SSP user's guide.
Possible Additional Requirements
Many Linux server instances are missing packages that are typically available on workstation installations. Such packages may have to be installed, for example, if Charon-SSP graphics device emulation or audio emulation are to be used. The same applies to the Charon-SSP Manager, the Server JIT feature, and some non-critical functions of the Charon Agent. On prepackaged Charon-SSP cloud marketplace images, the necessary packages are preinstalled.
The following table provides an overview of the packages that may be missing:
...
* If you install the Charon Manager with the yum (or dnf) command, these packages (except for xorg-x11-xauth) and any dependencies that these packages themselves may have, are resolved automatically if a package repository is available.
If you suspect problems caused by missing packages and the emulator was started via the Charon Manager, check the emulator crash-log file in addition to the emulator log file. If starting the emulator from the command-line, review the command-line output.
The packages above have their own dependencies. Install the above packages with the yum (or dnf) command in order to have their dependencies automatically installed. If your server does not have access to the standard operating system repositories, refer to this document for instructions on setting up a local repositories.
...
class | pagebreak |
---|
Sample Installation
Only the Charon-SSP emulator packages (4M, 4U(+), 4V(+)) are specific to the license model used. The packages required for managing Charon-SSP (Charon Agent, Manager, and Director) are the same as in the conventional product of the same version.
For detailed host system requirements and for the management of the Charon-SSP software, please refer to the regular Charon-SSP documentation on the Stromasys Product Documentation and Knowledge Base pages.
The log output below shows a sample Charon-SSP emulator and management package installation on a Linux 7 system:
Code Block | ||
---|---|---|
| ||
# yum install charon*.rpm (lines removed) Resolving Dependencies --> Running transaction check (lines removed)1/1 Created symlink /etc/systemd/system/multi-user.target.wants/licensed.service → /etc/systemd/system/licensed.service. Verifying : license-server-1.1.5-1.x86_64 1/1 Installed: license-server-1.1.5-1.x86_64 Complete! |
Div | ||
---|---|---|
| ||
Charon-SSP VE-Capable Emulator Software Installation
General Information
The Charon-SSP packages are RPM packages that are installed using the yum (Linux 7.x), dnf (Linux 8.x), or rpm command. They can be copied to the Charon host system using SFTP as shown in the example for copying the license server RPM.
At least the required emulator packages (charon-ssp-4*.rpm) and the agent (charon-agent*.rpm) must be installed for the system to run emulated SPARC systems and to allow remote management by the Charon Manager. If local management with graphical tools is required, then the Charon Manager and the Charon Director packages must also be installed.
For detailed host system requirements and for the management of the Charon-SSP software, please refer to the regular Charon-SSP documentation on the Stromasys Product Documentation and Knowledge Base pages.
Please note: To use the graphical user interface (Charon Manager for SSP) the Charon Manager package typically is installed on your local Linux or Windows PC that will be used for management purposes. Running the Charon Manager in a non-graphical cloud instance and export it via X11-Forwarding is possible, but will require additional configuration and installation steps (with access to a package repository) - this is outside the scope of this document. It is also possible to manage Charon-SSP via the command-line only. This is described in the general Charon-SSP user's guide.
Possible Additional Requirements
Many Linux server instances are missing packages that are typically available on workstation installations. Such packages may have to be installed, for example, if Charon-SSP graphics device emulation or audio emulation are to be used. The same applies to the Charon-SSP Manager, the Server JIT feature, and some non-critical functions of the Charon Agent. On prepackaged Charon-SSP cloud marketplace images, the necessary packages are preinstalled.
The following table provides an overview of the packages that may be missing:
RPM Package | Graphics and audio emulation | Charon Manager* | Server JIT feature | Charon Agent |
---|---|---|---|---|
libX11 | x | x | ||
xorg-x11-server-utils | x | x | ||
alsa-plugins-pulseaudio | x | |||
gtk2 | x | |||
xorg-x11-xauth (only required for X11-Forwarding) | x | |||
libicu (version 50 for Linux 7.x, version 60 for Linux 8.x) | x | |||
pciutils | x |
* If you install the Charon Manager with the yum (or dnf) command, these packages (except for xorg-x11-xauth) and any dependencies that these packages themselves may have, are resolved automatically if a package repository is available.
If you suspect problems caused by missing packages and the emulator was started via the Charon Manager, check the emulator crash-log file in addition to the emulator log file. If starting the emulator from the command-line, review the command-line output.
The packages above have their own dependencies. Install the above packages with the yum (or dnf) command in order to have their dependencies automatically installed. If your server does not have access to the standard operating system repositories, refer to this document for instructions on setting up a local repositories.
Div | ||
---|---|---|
| ||
Sample Installation
Only the Charon-SSP emulator packages (4M, 4U(+), 4V(+)) are specific to the license model used. The packages required for managing Charon-SSP (Charon Agent, Manager, and Director) are the same as in the conventional product of the same version.
For detailed host system requirements and for the management of the Charon-SSP software, please refer to the regular Charon-SSP documentation on the Stromasys Product Documentation and Knowledge Base pages.
The log output below shows a sample Charon-SSP emulator and management package installation on a Linux 7 system:
Code Block | ||
---|---|---|
| ||
# yum install charon*.rpm Loaded plugins: fastestmirror <lines removed> Resolving Dependencies --> Running transaction check ---> Package charon-agent-ssp.x86_64 0:4.3.5-1 will be installed ---> Package charon-director-ssp.x86_64 0:4.3.5-1 will be installed ---> Package charon-manager-ssp.x86_64 0:4.3.5-1 will be installed ---> Package charon-ssp-4m.x86_64 0:4.3.5.el7-1 will be installed ---> Package charon-ssp-4u.x86_64 0:4.3.5.el7-1 will be installed ---> Package charon-ssp-4v.x86_64 0:4.3.5.el7-1 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Arch Version Repository Repository Size ================================================================================ Installing: charon-agent-ssp x86_64 4.23.5-1 /charon-agent-ssp-4.23.5-x86_64 32 M charon-director-ssp x86_64 4.23.5-1 /charon-director-ssp-4.23.5 287 k charon-manager-ssp x86_64 4.23.5-1 /charon-manager-ssp-4.23.5 5 6.80 M charon-ssp-4m x86_64 4.23.5.ve.el7-1 /charon-ssp-4m-4.23.5.ve.el7-x86_64 6.1 M charon-ssp-4u+ x86_64 4.23.5.ve.el7-1 /charon-ssp-4u+-4.23.5.ve.el7-x86_64 5424 M charon-ssp-4v+ x86_64 4.23.5.ve.el7-1 /charon-ssp-4v+-4.23.5.ve.el7-x86_64 5424 M Installing for dependencies: (lines removed) Transaction Summary ================================================================================ Install 6 Packages (+32 Dependent packages) Total size: 161 M Total download size: 8.9 92 M Installed size: 18392 M Is this ok [y/d/N]: y Downloading packages: (lines removed) packages: Running transaction check Running transaction test Transaction test succeeded Running transaction (lines<lines removed)removed> Installed: charon-agent-ssp.x86_64 0:4.23.5-1 charon-director-ssp.x86_64 0:4.23.5-1 charon-manager-ssp.x86_64 0:4.23.5-1 charon-ssp-4m.x86_64 0:4.23.5.ve.el7-1 charon-ssp-4u+.x86_64 0:4.23.5.ve.el7-1 charon-ssp-4v+.x86_64 0:4.23.5.ve.el7-1 (lines removed) Complete! |
Include Page | ||||
---|---|---|---|---|
|