Document number: 55-16-001-002 CHARON-SSP for Linux - User's Guide April, 2015 1 / 122
Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document number: 55-16-001-002 About This Guide This preface describes the conventions and organisation of this user's guide. It also describes its intended audience and how to obtain further copies of this guide, related documentation and further support. Intended Audience This user guide is targeted at anyone attempting to install, configure or manage the CHARON-SSP line of SPARC system virtual machines.
Document number: 55-16-001-002 Europe, Middle-East and Africa emea.sales@stromasys.com +41 22 794 1070 Avenue Louis-Casai 84 8 a.m. - 5 p.m. 5th Floor 1216 Cointrin Switzerland Alternatively, the support centre can be contacted by email at support@stromasys.com. If you have purchased CHARON-SSP via a Value Added Reseller (VAR) then please contact them directly.
Document number: 55-16-001-002 Introduction In 1987 Sun Microsystems released the SPARC V7 processor. A 32-bit RISC processor featuring the unique Berkeley RISC designed register-window. This was followed soon after in 1990 with the SPARC V8. This was a revision of the original SPARC V7, with the most notable inclusion of hardware divide and multiply instructions. The SPARC V8 processors were the basis for a number of Sun Microsystems servers and workstations such as the SAPRCstation 5, 10 and 20.
Document number: 55-16-001-002 Host System Requirements To ensure maximum performance when emulating an SPARC-based system it is important to follow some guidelines regarding the set up of the host system. These are described in the following sections. Hardware Requirements To run the CHARON-SSP virtual machine products the host system must have at least two CPUs (or cores) and must be either an Intel 64 or AMD64 based processor.
Document number: 55-16-001-002 Supported Virtual Hardware The different classes of CHARON-SSP virtual machine support a number of different hardware devices. The table below describes the device features, and where relevant, the quantity supported by different CHARON-SSP virtual machines. CHARON-SSP Supported Virtual Hardware CHARON-SSP/4M SPARC V8 (32-bit) Y SPARC V9 (64-bit) No.
Document number: 55-16-001-002 Installation The CHARON-SSP for Linux suite of products provides much more than just a SPARC virtual machine. The software is available in four parts: CHARON-SSP/4M – 32-bit SPARC V8, sun4m architecture CHARON-SSP/4U – 64-bit SPARC V9 sun4u architecture CHARON-SSP Manager – A remote GUI virtual machine manager, and CHARON-SSP Agent – Bridge for communication between CHARON-SSP virtual machine and CHARON-SSP Manager.
Document number: 55-16-001-002 Installing the Sentinel HASP Software The Sentinel HASP runtime is a necessary software component used to license the CHARON-SSP for Linux virtual machine software. Without this package it is not possible to run the CHARON-SSP virtual machine software. The RPM package is included as part of the tar, gzip CHARON-SSP distribution. The CHARON-SSP for Linux software comes in two separate install packages.
Document number: 55-16-001-002 i686 glibc Installation Output Loaded plugins: langpacks Resolving Dependencies --> Running transaction check ---> Package glibc.i686 0:2.17-78.0.1.el7 will be installed --> Processing Dependency: libfreebl3.so for package: glibc-2.17-78.0.1.el7.i686 --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-78.0.1.el7.i686 --> Running transaction check ---> Package nss-softokn-freebl.i686 0:3.16.2.3-9.
Document number: 55-16-001-002 Sentinel HASP Installation Output Loaded plugins: langpacks Examining aksusbd-2.2.1-1.x86_64.rpm: aksusbd-2.2.1-1.x86_64 Marking aksusbd-2.2.1-1.x86_64.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package aksusbd.x86_64 0:2.2.
Document number: 55-16-001-002 Instructions for Securing Sentinel HASP GUI Step Description 1. Open a web browser and navigate the http://localhost:1947. For CHARON-SSP Virtual Environment users, double-click the Web Browser icon under the System sections of the System Utilities window. 2. Click on the left-hand menu item labelled Configuration. 3. Click the Basic Settings tab. 4. Under the entry labelled Password Protection, click the button labelled Change Password. 5.
Document number: 55-16-001-002 Sentinel HASP Uninstall Output Loaded plugins: langpacks Resolving Dependencies --> Running transaction check ---> Package aksusbd.x86_64 0:2.2.1-1 will be erased --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: aksusbd x86_64 2.2.1-1 @/aksusbd-2.2.1-1.x86_64 4.
Document number: 55-16-001-002 Installing the CHARON-SSP Software The CHARON-SSP for Linux virtual machine software is shipped as a tar, gzip distribution package. To begin the installation you must first obtain the package archive. This can be downloaded from Stromasys or distributed by read-only media, such as a CD-ROM. If you do not have the software package, then please contact either Stromasys or your Value Added Reseller for further help.
Document number: 55-16-001-002 CHARON-SSP/4M for GNU/Linux Install Output # yum localinstall charon-ssp-4m-1.0.22-x86_64.rpm Examining charon-ssp-4m-1.0.22-x86_64.rpm: charon-ssp-4m-1.0.22-1.x86_64 Marking charon-ssp-4m-1.0.22-x86_64.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package charon-ssp-4m.x86_64 0:1.0.
Document number: 55-16-001-002 Removing the CHARON-SSP Software To install the CHARON-SSP for Linux virtual machine software, execute the relevant yum command for the specific package, shown in the table below. CHARON-SSP for GNU/Linux Installation Commands Product Name Installation Command CHARON-SSP/4M yum remove charon-ssp-4m CHARON-SSP/4U yum remove charon-ssp-4u The following shows the removal of the CHARON-SSP/4M for Linux software.
Document number: 55-16-001-002 Upgrading CHARON-SSP for Linux To upgrade the CHARON-SSP for Linux software, simply follow the instructions described in the section Installing the CHARON-SSP Software. The terminal output below shows an upgrade from CHARON-SSP/4M for Linux v1.0.18 to v1.0.22. Upgrading CHARON-SSP/4M for GNU/Linux # yum localinstall charon-ssp-4m-1.0.22-x86_64.rpm Examining charon-ssp-4m-1.0.22-x86_64.rpm: charon-ssp-4m-1.0.2-1.x86_64 Marking charon-ssp-4m-1.0.22-x86_64.
Document number: 55-16-001-002 Installing the CHARON-SSP Manager The CHARON-SSP Manager client software is available for both Windows and Linux. Both packages can be downloaded from Stromasys or distributed on read-only media, such as CD-ROM. If you do not have the software package, then please contact either Stromasys or your Value Added Reseller (VAR) for further help. The following sections describe the procedures for installing, upgrading and removing CHARON-SSP Manager for Windows and Linux.
Document number: 55-16-001-002 Installing CHARON-SSP Manager for Windows The following sections cover the procedures for installing, removing and upgrading the CHARON-SSP Manager for Windows software.
Document number: 55-16-001-002 Installing CHARON-SSP Manager for Windows Step Description 1. Right-click the zip archive, SSP-Manager for Windows.zip and select Extract All... 2. A window titled Extract Compressed (Zipped) Folders will display. On this window: Click the checkbox labelled Show extracted files when complete. Click the button labelled Extract. 3. A new Windows Explorer window will open showing the extracted packages. 4. Double-click the setup.exe executable to begin the installation.
Document number: 55-16-001-002 It is also recommended by Stromasys that Windows Update is checked for any critical Microsoft .NET Framework updates and that if any are available, they are installed. Running CHARON-SSP Manager as an Administrator To run the CHARON-SSP Manager for Windows correctly, it is necessary to run as the Administrator user. To configure this to be on by default, follow the steps described below. Instructions for Running CHARON-SSP Manager as an Administrator Step Description 1.
Document number: 55-16-001-002 Microsoft Windows XP and Server 2003 Removing CHARON-SSP Manager from Microsoft Windows XP and Server 2003 Step Task 1 Click Start, then click Control Panel. 2 Double-click Add or Remove Programs. 3 Select SSP-Manager from the installed software list. Click Remove. Upgrading the CHARON-SSP Manager for Windows To upgrade the CHARON-SSP Manager for Windows software, it is necessary to first remove the existing package, then install the new version.
Document number: 55-16-001-002 Installing the CHARON-SSP Manager for Linux The following sections cover the procedures for installing, removing and upgrading the CHARON-SSP for Linux software.
Document number: 55-16-001-002 CHARON-SSP Manager for Linux Install Output Loaded plugins: langpacks Examining charon-manager-ssp-1.0.22.rpm: charon-manager-ssp-1.0.22-1.x86_64 Marking charon-manager-ssp-1.0.22.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package charon-manager-ssp.x86_64 0:1.0.
Document number: 55-16-001-002 2. Add the following text to the file created in step 1 and save it. [Desktop Entry] Version=1.0.22 Name=CHARON-SSP Manager Exec=/opt/charon-manager/ssp-manager/ssp-manager Icon=/opt/charon-manager/ssp-manager/resource/charon.png Terminal=false Type=Application StartupNotify=true Categories=System; 3. Set the file protections and ownership appropriately: # chmod 0644 /usr/local/share/applications/charon-ssp-manager.
Document number: 55-16-001-002 CHARON-SSP Manager for Linux Uninstall Output Loaded plugins: langpacks Resolving Dependencies --> Running transaction check ---> Package charon-manager-ssp.x86_64 0:1.0.
Document number: 55-16-001-002 Upgrading CHARON-SSP Manager for Linux To upgrade the CHARON-SSP Manager for Linux software, simply follow the instructions described in the section Installing the CHARON-SSP Manager for Linux. The terminal output below shows an upgrade from CHARON-SSP Manager for Linux v1.0.18 to v1.0.22. Upgrading CHARON-SSP/4M for Linux # yum localinstall charon-manager-ssp-1.0.22.rpm Loaded plugins: langpacks Examining charon-manager-ssp-1.0.22.rpm: charon-manager-ssp-1.0.22-1.
Document number: 55-16-001-002 Installing the CHARON-SSP Agent The CHARON-SSP Agent for Linux software is shipped as a tar, gzip distribution package. To begin the installation you must first obtain the package archive. This can be downloaded from Stromasys or distributed by read-only media, such as a CD-ROM. If you do not have the software package, then please contact either Stromasys or your Value Added Reseller for further help.
Document number: 55-16-001-002 CHARON-SSP Agent for Linux Install Output Loaded plugins: langpacks Examining charon-agent-ssp-1.0.22-x86_64.rpm: charon-agent-ssp-1.0.22-1.x86_64 Marking charon-agent-ssp-1.0.22-x86_64.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package charon-agent-ssp.x86_64 0:1.0.
Document number: 55-16-001-002 Removing the CHARON-SSP Agent Software To remove the CHARON-SSP Agent for Linux software, execute the following command: CHARON-SSP Agent for Linux Uninstall Command # yum remove charon-agent-ssp Executing the command above should generate output similar to the following. When asked "Is this ok?" Check the list of software to ensure it only includes the charon-agent-ssp package and answer y(es) to proceed.
Document number: 55-16-001-002 Upgrading CHARON-SSP/4M for Linux # yum localinstall charon-agent-ssp-1.0.22-x86_64.rpm Loaded plugins: langpacks Examining charon-agent-ssp-1.0.22-x86_64.rpm: charon-agent-ssp-1.0.22-1.x86_64 Marking charon-agent-ssp-1.0.22-x86_64.rpm as an update to charon-agent-ssp-1.0.18-1.x86_64 Resolving Dependencies --> Running transaction check ---> Package charon-agent-ssp.x86_64 0:1.0.18-1 will be updated ---> Package charon-agent-ssp.x86_64 0:1.0.
Document number: 55-16-001-002 Installing the CHARON-SSP Virtual Environment The CHARON-SSP Virtual Environment is an appliance version of the CHARON-SSP for Linux virtual machine and associated utilities. Distribution of this software is either via an ISO image or physical read-only media, such as a CD-ROM or DVD. If you do not have a copy of the CHARON-SSP Virtual Environment, then please contact either Stromasys or you Value Added Reseller for further help.
Document number: 55-16-001-002 Installation Tasks CHARON-SSP Installation Tasks Step Description 1. If the host system is a virtual machine: Configure for a Linux kernel 2.4.x x86-64 environment. Use the requirements laid out in Host System Requirements to configure the virtual hardware. Attach the CHARON-SSP Virtual Environment ISO or physical CD to the VM. Power up the VM and boot from the CD. If the host system is a physical machine: Load the CHARON-SSP CD. Boot the system from the CD. 2.
Document number: 55-16-001-002 3. When presented with the following screen: Select Finish partitioning and write changes to disk and press Return. 4. © Stromasys, 2015 When asked to confirm the changes, select Yes and press Return.
Document number: 55-16-001-002 4. 5. The base installation will now continue. At completion the system will reboot. Ensure that the CD media is ejected to prevent booting the CHARON-SSP Virtual Environment installer again. Following successful installation, you should be presented with the following screen: Post Installation Tasks The following post installations task are not required. However, for improved security they are highly recommended.
Document number: 55-16-001-002 CHARON-SSP Manager Password Change Instructions Step Description 1. Log in to the CHARON-SSP Manager using the default password of 123456 and click Connect. 2. Click the Virtual Machine menu. 3. From the Virtual Machine drop-down menu, click Preferences... 4. At the label Do you want to change the password?, click YES. 5. 6. © Stromasys, 2015 Enter the existing password in the field, Current password.
Document number: 55-16-001-002 Change CHARON-SSP Virtual Environment Password The CHARON-SSP Virtual Environment runs under the charon-ssp user account. For improved security it is highly recommended that the default password of foxandtree is changed. The following instructions describe the necessary steps to change this password. CHARON-SSP Virtual Environment Password Change Instructions Step Description 1. Press Ctrl+Winkey+F12 to start a shell. 2. Execute the command passwd. 3.
Document number: 55-16-001-002 CHARON-SSP Virtual Evnrionment Upgrade Instructions Step Description 1. Double-click the icon labelled CHARON-SSP Upgrade on the System Settings window. 2. A window titled Preparation will pop-up prompting for the insertion of the USB memory stick. Insert the USB stick into a free port on the system and click the button labelled Next.
Document number: 55-16-001-002 Using the CHARON-SSP Software The following sections describe in detail each of the individual parts of CHARON-SSP for Linux and how to use them: For the CHARON-SSP Virtual Environment appliance the most relevant documentation is Using the CHARON-SSP Manager. This describes the primary interface used to manage the hosted virtual machines.
Document number: 55-16-001-002 Using the CHARON-SSP Manager The CHARON-SSP Manager is a GUI management interface for the CHARON-SSP for Linux virtual machine. Using this management utility it is possible to manage multiple virtual machines, licenses and virtual networks across a number of remote hosts. It is also the interface presented on the console of a system running the CHARON-SSP Virtual Environment appliance.
Document number: 55-16-001-002 © Stromasys, 2015 41 / 122
Document number: 55-16-001-002 Managing Virtual Machines The following sections describe the different aspects of managing a CHARON-SSP virtual machine.
Document number: 55-16-001-002 CHARON-SSP Manager Opening Screen The initial creation of the virtual machine is very sparse. To complete the configuration it is important to continue on to Modifying the Virtual Machine.
Document number: 55-16-001-002 Edit Virtual Machine Settings Window The following section describes each part of the Virtual Machine Settings window For any changes to take effect, the virtual machine must be restarted. However, it is also recommended that before making any configuration changes the virtual machine is shutdown correctly. Model Configuration To view or change the virtual machine model, select Model in the Device column of the left hand pane.
Document number: 55-16-001-002 Virtual Machine Model Configuration Window The models currently supported by CHARON-SSP/4M for Linux are: Sun SPARCstation 20 The models currently supported by CHARON-SSP/4U for Linux are: Sun Enterprise 450 CPU Configuration To view or change the current virtual machine CPU configuration, select CPU in the Device column of the left-hand pane.
Document number: 55-16-001-002 Virtual Machine CPU Configuration Window The following table lists each of the fields in the CPU configuration window and describes their operation.
Document number: 55-16-001-002 Virtual Machine CPU Configuration Fields Field Description Number of CPU Configure the number of CPUs attached to the virtual machine. Not all virtual SPARC systems support the configuration of multiple CPUs.
Document number: 55-16-001-002 Virtual Machine Memory Configuration Widows The following table lists each of the fields in the memory configuration window and describes their operation. Virtual Machine Memory Configuration Fields Field Description Memory for this virtual machine Set the amount of RAM allocated to the virtual machine. Memory can only be allocated in certain increments. The table below describes the allocation rules for each virtual machine model.
Document number: 55-16-001-002 Virtual Machine SCSI Configuration Window From this window it is possible to create virtual disk and tape container files as well as attach virtual storage devices (both physical and container files) to the virtual machine. Creating Container Files Often it is convenient to use container files for virtual disk and tape devices. The following sections describes creating both disk and tape container files.
Document number: 55-16-001-002 Create New Virtual Disk Window To create a virtual disk container file, follow the instructions listed below. Steps for Creating a New Virtual Disk Container File Step Description 1. Specify a name for the virtual disk container file in the field Virtual disk name. 2. Select the location on the host file system for the container file by clicking the button Location and navigating to the correct path. 3.
Document number: 55-16-001-002 Create New Virtual Tape Windows To create a virtual tape container file, follow the instructions listed below. Steps for Creating a New Virtual Tape Container File Step Description 1. Specify a name for the virtual tape container file in the field Virtual tape name 2. Select the location on the host file system for the container file by clicking the button Location and navigating to the correct path. 3.
Document number: 55-16-001-002 Add/Edit Virtual Disk Device Window (CHARON-SSP/4M shown) The following table lists each of the fields in the Add/Edit SCSI Device configuration window and describes their operation.
Document number: 55-16-001-002 Add/Edit Virtual Disk Device Configuration Fields Field Description SCSI device type Drop-down list of configurable device types. The table below describes the available device types: SCSI device type Description Virtual Disk Virtual disk device backed by a container file. Virtual CDROM Virtual CDROM device, backed by a container file. Virtual Tape Virtual tape device backed by a container file.
Document number: 55-16-001-002 Virtual Machine TTYA Configuration Window It is possible to configure the virtual console device in one of three ways by selecting one of three options described below from the drop-down list labelled Type. Virtual Machine Console Types Type Description TCP Configure the console device as a network device. Physical Configure the console device as physical terminal directly attached to the host system. Disable Disable the virtual console device entirely.
Document number: 55-16-001-002 Virtual Machine TTYA Physical Device Configuration Window The only option for the physical terminal is Device. This is a drop-down list of all directly attached serial ports available on the host system. Network Console Device The image below shows the network console device configuration window.
Document number: 55-16-001-002 Virtual Machine TTYA Network Device Configuration Window The following table lists each of the fields in the network console device configuration window and describes their operation. Virtual Machine TTYA Network Device Configuration Fields Field Description Port This option specifies the TCP/IP port to user when listening for incoming console client connections. A different port must be specified for each network console or serial port.
Document number: 55-16-001-002 to TTYA. For further details related to configuring this device, consult the section TTYA Configuration. Ethernet Configuration To view or change the virtual machine Ethernet configuration, select Ethernet in the Device column of the left-hand pane. Virtual Machine Ethernet Configuration Window To remove an existing virtual Ethernet adapter, select the adapter from the list of configured devices and click the button labelled Remove...
Document number: 55-16-001-002 Virtual Ethernet Configuration Fields Field Description Interface Select the host attached Ethernet device to be connected to the virtual device. This field is a drop-down list of all the network adapters available on the host system. Set MAC Address To force the MAC address of the virtual Ethernet device to a specific value, select the checkbox and enter the address as size groups of two character hexadecimal digits, separated by a colon, e.g. 08:00:2b:aa:bb:cc.
Document number: 55-16-001-002 Virtual Machine Logging Configuration Fields Field Description Log path Specify the path name for the log file. Severity Set the minimum level of messages that should be reported. Legal values are debug, info, warning, error and fatal. The default is info. Output to Indicate where virtual machine logging information should be written to. The default is file. Option Description file Output virtual machine logging information only to the file configured in Log path.
Document number: 55-16-001-002 Renaming a Virtual Machine Step Description 1. Click the virtual machine to rename in the left hand pane. 2. Take note of the name of the configuration file in the field Config file. This will be needed later in step 5. 3. Right-click the virtual machine name and select Remove VM from the List. This action will not ask for any confirmation and the virtual machine will be immediately removed from the list. 4.
Document number: 55-16-001-002 Removing a Virtual Machine The complete removal of a virtual machine must be performed in a number of steps. Each of these steps is detailed below. Steps to Remove a Virtual Machine Step Description 1. Click the name of the virtual machine that is to be removed in the left hand pane of the management console. 2. Right-click the name of the virtual machine in the left hand pane of the management console. Select Delete VM from Disk.
Document number: 55-16-001-002 Managing Virtual Networks Using the CHARON-SSP Agent in conjunction with the CHARON-SSP Manager it is possible to configure a collection of virtual network tap (TAP) devices that constitute a host-attached virtual LAN. These interfaces are bridged with a physical network device on the host system that allows the virtual LAN to connect to the physical LAN. Creating a Virtual Network To create a new virtual network, follow the instructions listed below.
Document number: 55-16-001-002 Instructions for Deleting a Virtual Network Step Description 1. Follow the menu path Tools > Virtual Network > Delete Virtual Network to open the Delete Virtual Network window, shown below. 2. Select the physical interface serving the bridge from the Virtual bridge interface drop-down box. 3. To delete all virtual network interfaces associated with this bridge, click the button labelled OK.
Document number: 55-16-001-002 Managing Licenses The process of managing CHARON-SSP for Linux is described in full detail in the section Managing Licenses with CHARON-SSP Manager. For further complete information on additional command-line utilities and the SafeNet Sentinel Admin Control Center web-interface, see the section Li cense Management.
Document number: 55-16-001-002 Miscellaneous Management Tasks The following sections describe some other miscellaneous functionality provided by the CHARON-SSP Manager interface that may be useful in certain instances. Gathering Host Information Determining the CHARON-SSP Manager Version Modifying the CHARON-SSP Agent Preferences Gathering Host Information To view the details of the system hosting the CHARON-SSP instance, follow the menu path Tools > Host Information...
Document number: 55-16-001-002 About CHARON Manager Windows The example above shows the About CHARON Manager window for CHARON-SSP Manager version V1.0.13. Modifying the CHARON-SSP Agent Preferences To modify the preferences maintained by the CHARON-SSP Agent software, follow the menu path Virtual Machine > Preferences... to open a window similar to the one shown below.
Document number: 55-16-001-002 Using CHARON-SSP from the Command Line Name ss20 – CHARON-SSP/4M 32-bit SPARC V8, sun4m Architecture Virtual Machine e450 – CHARON-SSP/4U 64-bit SPARC V9, sun4u Architecture Virtual Machine Synopsis ss20 | e450 [ [ -a alias_name ] [ -d ] -f config_file [ -s ] ] [ -h ] [ -k pid ] [ -l ] Description The sma utility is the lowest level access to the CHARON-SSP virtual machine software.
Document number: 55-16-001-002 sma Command Line Utility Options Option Description -a alias_n ame Assign alias_name to the new virtual machine instances. This option can be very useful when attempting to locate a specific instance in the list reported by the -l option. If this option is not specified, a name of the form instance-%02d will be assigned by the sma utility. -d Run the virtual machine as a daemon. This option cannot be specified with -s.
Document number: 55-16-001-002 The following command reference describes the syntax and operation of the commands supported in this version of CHARON-SSP for Linux. Interactive Mode Command Reference Command Description help [ comma nd ] Display command line help. Arguments command d [ address size ] Specify a command name to return more specific help. This argument is optional. Display a region of memory within the virtual machine.
Document number: 55-16-001-002 Example SPARCstation 20 Configuration [system] model = "SPARCstation_20" [ram] size = 64 [nvram] path = ./vm.nvram [ethernet] interface = eth0 [ttya] type = socket port = 9000 [log] severity = info destination = console path = vm.log Assuming the configuration file above is stored in vm.config the following commands can be used to start the virtual machine and connect to the console. # /opt/charon-spk-ss20/ss20 -f vm.
Document number: 55-16-001-002 Open Boot Console Ouptut SMCC SPARCstation 20 Emulator by Stromasys CPU_#0 TI, TMS390Z50(3.x) 0Mb External cache CPU_#1 CPU_#1 CPU_#1 ****** NOT installed ****** ****** NOT installed ****** ****** NOT installed ****** >>>>> Power On Self Test (POST) is running .... <<<<< SPARCstation 20 (1 X 390Z50), No Keyboard Emulate OBP Rev. 2.25, 64 MB memory installed, Serial #12648430. Ethernet address 2:c:29:4a:d3:29, Host ID: 72c0ffee.
Document number: 55-16-001-002 Using the CHARON-SSP Agent The CHARON-SSP Agent is a Linux service that runs on a system that will be managed by the CHARON-SSP Manager. This service provides the interface between the CHARON-SSP Management GUI and the virtual machine software. A prerequisite of installing the CHARON-SSP Agent is that the CHARON-SSP for Linux virtual machine software must already be installed. The following sections describe how to manipulate the CHARON-SSP Agent software.
Document number: 55-16-001-002 Accessing the Console Depending on how the virtual machine console device has been configured, it is possible to access the console in a number of different ways. The sections listed below describe example configurations and other useful notes detailing how set up and use the different console access methods. Physical Console Access Console Access from CHARON-SSP Manager Console Access from the Network Graphical Console Access Enabling XDMCP Solaris 2.
Document number: 55-16-001-002 CHARON-SSP Manager Console Tab To configure the serial console to be accessed from the CHARON-SSP Manager, use a configuration for the TTYA section similar to the one below.
Document number: 55-16-001-002 Console Access from the Network The serial console can also be configured for remote access across the network. The configuration extra below demonstrates configuring the guest console, ttya to accept incoming connections from port 9000/tcp on the host. Configuring ttya for Network Console Access # SPARCstation 20 serial console redirected to network # port 9000/tcp.
Document number: 55-16-001-002 Enabling XDMCP Before switching to the Xserver, it is first necessary to ensure that XDMCP is enabled on the guest system. The actions for enabling XDMCP are different, depending on the version of Solaris or SunOS installed on the guest. Follow the relevant sub-section below to configure XDMCP on your guest. Solaris 2.5 and higher Use the following instructions to enable remote login over XDMCP on Solaris 9 and lower.
Document number: 55-16-001-002 Instructions for Starting the X11 Server Step Description 1. Open the Start X11 Xserver window (shown below) from CHARON-SSP Manager by following the menu path, Tools > X11 Server > Start X11 Server. 2. Configure the X11 Server by completing the fields: Enter the address or name of the guest in the field IP address. Select the X11 session resolutions from the Resolution drop down box. 3. Click the button labelled Start to start the X11 server.
Document number: 55-16-001-002 License Management All Stromasys CHARON virtual machine software products are licensed using a Sentinel HASP (Hardware Against Software Piracy) key. To use these products you must have both the physical key and a valid license file loaded on to it.
Document number: 55-16-001-002 Managing Licenses with CHARON-SSP Manager The CHARON-SSP Manager provides a friendly graphical interface for the management of licenses. The following sections describe how to use these tools: Viewing the License Details Gathering Customer to Vendor (C2V) Detail Applying Vendor to Customer (V2C) License Update Viewing the License Details To view the license details of the attached USB HASP click the menu path Tools > License Viewer...
Document number: 55-16-001-002 Gathering Customer to Vendor (C2V) Detail The following steps describe the process of gathering the customer to vendor (C2V) data file. This information is used by Stromasys to generate a license data file Instructions for Gathering Customer to Vendor (C2V) Data Step Description 1. Open the License Update window, click the menu path Tools > License Update. 2. Click the tab labelled Export C2V File. . Select the type of license in License type drop-down box.
Document number: 55-16-001-002 Applying Vendor to Customer (V2C) License Update After sending the C2V (customer to vendor) file to Stromasys Orders Administration (see Gathering Customer to Vendor (C2V) Detail) a response will be generated and returned. Depending on certain factors there may be one or two files attached to the response.
Document number: 55-16-001-002 Managing Licensing from the Command Line The CHARON-SSP Agent provides two command line utilities for the management of licenses. The following sections describe how to use these tools: Viewing the License Details Gathering Customer to Vendor (C2V) Detail Applying Vendor to Customer (V2C) License Updates Complete documentation for the two utilities used in this section can be found in the section Command Line Utilities Reference.
Document number: 55-16-001-002 Command to Gather Customer to Vendor Data File $ hasp_srm_view -c2v /path/to/keydata.c2v The resulting file should then be sent to Stromasys Orders Administration via email, orders@stromasys.com. Applying Vendor to Customer (V2C) License Updates License keys received from Stromasys Orders Administration can be applied using the hasp_update command line utility. In some cases, depending on the license type there maybe one or two files to apply. 1.
Document number: 55-16-001-002 Using the SafeNet Sentinel Admin Control Center The SafeNet Sentinel Admin Control Center (ACC) provides a simple web interface for the query and management of both hardware and software Sentinel license keys. It is installed and enabled as part of the Sentinel HASP Software isntallation, described in the section Installing the Sentinel HASP Software. The following sections describe some of the common tasks associated with the SafeNet Sentinel ACC.
Document number: 55-16-001-002 SafeNet Sentinel Admin Control Center - Sentinel Keys Applying V2C (Vendor to Customer) License Files License keys received from Stromasys Orders Administration can be applied through the Safenet Sentinel ACC Update/Attach form. The screenshot below shows this form. SafeNet Sentinel Admin Control Center - Update/Attach To load a license key using the SafeNet Sentinel ACC Update/Attach form, follow the instructions below.
Document number: 55-16-001-002 Applying a License Key File with SafeNet Sentinel ACC Step Description 1. Save the V2C (vendor to customer) files received from Stromasys Orders Administration. Depending on the license type, this may be one or two 1. A license file to format the key (optional, for hardware licenses only). The file name is of the format *_fmt.v2c. 2. The license key file. The file name is of the format *.v2c. Steps 2. and 3.
Document number: 55-16-001-002 Configuration Reference The CHARON-SSP virtual machines can be configured using a text-based configuration file or the CHARON-SSP Manager GUI. This section describes the format and content of the text-based configuration file. The configuration file is made up of a number of sections that describe various aspects of the virtual machine environment. The remaining sections describes the different sections and their syntax.
Document number: 55-16-001-002 Reference The following sections describe how to manipulate the configuration objects and their members to set up a virtual SPARC machine: © Stromasys, 2015 88 / 122
Document number: 55-16-001-002 [cpu] Section This section controls options related to the operation of the virtual machines CPUs. The following list each of the available options: dit – Enable/disable Dynamic Instruction Translation. number – Specify number of virtual CPUs. dit Enable/disable Dynamic Instruction Translation. Syntax dit = on | off Description This option enables of disables the Dynamic Instruction Translation (DIT) mode. This can provide significant performance increase if enabled.
Document number: 55-16-001-002 [ethernet] Section This section describes the virtual Ethernet adapters attached to the virtual machine. The following list describes the available options: interface – Attach virtual Ethernet interface to host attached adapter. mac – Specify virtual Ethernet adapter MAC address. For virtual models that support the feature, it is possible to configure multiple Ethernet controllers. For an example configuration and details on section naming, see [ethernet_n] Section.
Document number: 55-16-001-002 [ethernet_n] Section This section is used for virtual machine configurations where there are multiple Ethernet controllers. The properties are the same as those described in the [ethernet] Section. However, the section naming is slightly different in that the names are suffixed with an underscore and the controller number. The configuration example below demonstrates the configuration of two virtual Ethernet adapters.
Document number: 55-16-001-002 [log] Section This section describes the configuration of the CHARON-SSP for Linux virtual machine logging facility. The following lists the properties supported by this section: destination – Logging facility output destination. path – Logging output path. severity – Logging severity level. It is important to note that all properties in this section must be configured correctly to ensure that the virtual machine will start.
Document number: 55-16-001-002 severity Logging severity level. Syntax severity = level Description Virtual machine logging messages are arranged into levels to make messages more relevant and reduce log file size. The severity property controls which level messages are included in the logging output. The list below lists these levels from most to least verbose. Setting logging to a specific level also includes all levels below it.
Document number: 55-16-001-002 [nvram] Section This section is used to configure the location of the NVRAM backing file store as well as some other NVRAM options. The list below describes the options that can be set: hostid – Set Sun Host ID. path – Specify location of console NVRAM file. hostid Set Sun Host ID. Syntax hostid = hex-hostid Description This optional property can be used to configure the Sun Host ID of the virtual machine. The value of hex-path is of the format 0xnnnnnnnn.
Document number: 55-16-001-002 [ram] Section This section controls the virtual machine memory environment. The following list describes these options: allocator – Virtual machine memory allocator. size-- Virtual machine memory size. allocator Virtual machine memory allocator. Syntax allocator = memory-allocator Description The allocator option is used to indicate to the virtual machine which memory allocation method the host system will use to allocate the virtual memory environment.
Document number: 55-16-001-002 [scsi_n] Section This section describes the virtual SCSI storage device configuration. Each device requires a separate section heading, where n is replaced with a SCSI ID number between 0 and 15. The example below shows the configuration entries for a physical tape device attached at SCSI ID 5. All devices are attached to the internal bus of the SPARC virtual machine.
Document number: 55-16-001-002 Virtual Storage Device Types Device Type Description Example Path cdrom Physical optical device. /dev/cdrom disk Physical disk device. /dev/sda iso Virtual CD-ROM ISO container file. /usr/local/share/iso/suns-4.1.4.iso tape Physical tape device. /dev/tape vdisk Virtual disk container file. /usr/local/vm/bender/disk0.vdisk vtape Virtual tape container file. /usr/local/vm/leela/tape0.
Document number: 55-16-001-002 [scsix_n] Section These sections are used for virtual machine configurations that support the external (although not necessarily physically external) SCSI controller, such as the Sun Enterprise 450. Each device requires a separate section heading, where n is replaced with a SCSI ID number between 0 and 15. The example below demonstrates a configuration of three devices (two CD-ROMs backed by ISO container files and one physical disk) attached to the external SCSI bus.
Document number: 55-16-001-002 [system] Section The system section is used to configure "system-wide" properties of the virtual machine. The list below describes the options that can be set: cpu_affinity – Assign virtual CPU processing to a specific host CPU. io_affinity – Assign virtual machine I/O processing to a specific host CPU. io_cpus – Number of host CPUs reserved for virtual machine I/O processing. machine – Specify the Alpha system model of the virtual machine.
Document number: 55-16-001-002 Syntax machine = "model-name" Description The model keyword is used to indicate the specific model of the SPARC-based system to emulate. The following table lists the possible values of model-name and the systems they represent. Virtual Machine Model Names Model name System Name Enterprise_450 Sun Enterprise 450 SPARCstation_20 Sun SPARCstation 20 The model-name specified here must correspond to what is configured on the HASP license dongle.
Document number: 55-16-001-002 [ttya] Section The ttya section is used to configure the first serial port (sometimes used as the console) on the SPARC virtual machine. Using these options it is possible to attach the virtual serial port to a network socket or a physical serial port attached to the host. The list below describes the options that can be configured: port – Virtual serial port specification. start_console – Start PuTTY at virtual machine boot. type – Virtual serial port type.
Document number: 55-16-001-002 Description This option configures how the serial console port will be connected. The table below lists the possible values for port-type and their purpose. Virtual Serial Port Types Port Type Description physical The virtual serial port will be connected to a physical, host-attached serial port. socket The virtual serial port is to be connected to a network socket. terminal For details of the port specification, see the port section.
Document number: 55-16-001-002 [ttyb] Section The ttya section is used to configure the first serial port (sometimes used as the console) on the SPARC virtual machine. Using these options it is possible to attach the virtual serial port to a network socket or a physical serial port attached to the host. The list below describes the options that can be configured: port – Virtual serial port specification. type – Virtual serial port type. port Virtual serial port specification.
Document number: 55-16-001-002 © Stromasys, 2015 104 / 122
Document number: 55-16-001-002 Console Reference The CHARON-SSP SPARC virtual machines use a subset of the Sun OpenBoot console found on native Sun workstations and servers. The figure below shows the initial console screen at boot on a virtual SPARCstation 20. SPARCstation 20 OpenBoot Console SMCC SPARCstation 20 Emulator by Stromasys CPU_#0 TI, TMS390Z50(3.
Document number: 55-16-001-002 banner Display power-on banner. Syntax banner Description Use this command to display the power-on banner. Example The following example demonstrates the output of the banner command on CHARON-SSP/L10 configured as a SPARCstation 20. Example banner Command Output ok banner banner SPARCstation 20 (1 X 390Z50), No Keyboard Emulate OBP Rev. 2.25, 64 MB memory installed, Serial #12648430. Ethernet address 2:c:29:4a:d3:29, Host ID: 72c0ffee.
Document number: 55-16-001-002 boot Load operating system. Syntax boot [ device-alias ] [ boot-args ] Description This commands boots the specified device-alias passing any optional boot-args to the kernel. For a complete list of device aliases, see the devalias command. Example The following example demonstrates the output of the boot command on CHARON-SSP/L10 configured as a SPARCstation 20 and booting SunOS 4.1.4 from CD-ROM.
Document number: 55-16-001-002 devalias Display device aliases. Syntax devalias Description This commands display the current device aliases. This shows the link between the aliases, such as cdrom and the devices shown in the device tree, listed by show-devs . Example The following example demonstrates the output of the devalias command.
Document number: 55-16-001-002 help Display OpenBoot console help. Syntax help [ command ] Description Use this command to display the list of commands supported by the OpenBoot console. For brief help on individual commands specify the comma nd parameter. Example The following example demonstrates the output of the help command.
Document number: 55-16-001-002 history Display console command history. Syntax history Description This command displays a list of all commands previously entered at the OpenBoot Console. Example The following example demonstrates the output of the history command.
Document number: 55-16-001-002 printenv Display environment variables. Syntax printenv Description Use this command to print the current and default values of OpenBoot console variables. Example The following example demonstrates the output of the printenv command.
Document number: 55-16-001-002 probe-scsi Scan SCSI bus for attached devices. Syntax probe-scsi Description This command scan the SCSI bus to locate attached devices. Example The following example demonstrates the output of the probe-scsi command on system with a single virtual CD-ROM..
Document number: 55-16-001-002 quit Shutdown virtual machine. Syntax quit Description Use this command to shutdown the virtual machine. Example The following example demonstrates the output of the quit command on CHARON-SSP configured as a SPARCstation 20. Example banner Command Output ok quit quit The system will be shutdown soon...
Document number: 55-16-001-002 reset Restart the system. Syntax reset Description This command restarts the SPARC virtual machine. Example The following example demonstrates the output of the reset command on CHARON-SSP/L10 configured as a SPARCstation 20. Example reset Command Output ok reset reset SMCC SPARCstation 20 Emulator by Stromasys CPU_#0 TI, TMS390Z50(3.
Document number: 55-16-001-002 setenv Set console environment variables. Syntax setenv variable value setenv variable -- Description This command sets the console configuration variable to value. For a complete list of possible variable names and details, see the table below. To restore variable to its default value, specify -- in place of value. setenv Variables Variable Default Value Description auto-boot? false If true, boots automatically after power on or reset.
Document number: 55-16-001-002 show-devs Display device tree. Syntax show-devs Description This command displays the tree of devices visible from the console. Example The following example demonstrates the output of the show-devs command.
Document number: 55-16-001-002 Command Line Utilities Reference In many cases it may be preferrable to be able to perform maintenance and management tasks for the command line of the Linux host system. This sections describes how to set up the PATH environment variable to use these utilities as well as a comprehensive reference. Prerequisites The utilities described in this reference section are installed as a part of the CHARON-SSP Agent for Linux software.
Document number: 55-16-001-002 hasp_srm_view Name hasp_srm_view –CHARON Sentinel HASP Utility Synopsis hasp_srm_view [OPTION] Description The hasp_srm_view utility provides a simple command line utility for gathering Sentinel license information. If no options are specified, -l, is specified by default. -?, -h, -help Display the utility usage message. -c2v FILENAME Collect the Sentinel HASP key status information and write it to FILENAME.
Document number: 55-16-001-002 License Manager running at host: localhost.localdomain License Manager IP address: 127.0.0.1 The Physical KeyId: 663427931 CHARON Sentinel HASP License key section Reading 4032 bytes License Manager running at host: localhost.localdomain License Manager IP address: 127.0.0.
Document number: 55-16-001-002 hasp_update Name hasp_update –Sentinel HASP Update and Transfer Utility Synopsis hasp_update u filename Description The hasp_update utility provides a simple command-line interface for manipulating the HASP License Key. u Apply the HASP key update found in filename. Exit Status The hasp_update virtual machine exits 0 on success and 255 if an error occurs. Examples The following example demonstrates the application of a V2C (vendor-to-customer) license key file.
Document number: 55-16-001-002 mkdskcmd Name mkdskcmd –CHARON virtual disk container creation utility. Synopsis mkdskcmd [OPTION] ... Description Create virtual disk container files for use the the CHARON family of virtual machines. By default, this utility will display a usage message. Mandatory arguments to long options are mandatory for short options too. -a, --avtable PATHNAME Use this option to specify an alternate location, PATHNAME, of the known disk device table.
Document number: 55-16-001-002 This example creates a virtual disk container file, /usr/local/vm/bender/disk0.vdisk, using a block size of 4,096 bytes and a total of 16,384 blocks. mkdskcmd -o /usr/local/vm/bender/disk0.