Found on installation procedures

Complete the procedures outlined in this section before moving on to the Install Procedures section. OCCNE installation procedures require certain artifacts and information to be made available prior to executing installation procedures. Refer to Configure Artifact Acquisition and Hosting for the prerequisites.

OCCNE deployment environments are not expected to have direct internet access. This section will address the artifacts list needed to be in these repositories.

For an accounting of third party artifacts needed for this installation, refer to the Artifact Acquisition and Hosting. In the first step of the installation, a minimal bootstrapping environment is established that is to support the automated installation of the CNE environment.

The steps in this section provide the details necessary to establish this minimal bootstrap environment on the Installer Bootstrap Host using a Keyboard, Video, Mouse KVM connection. It is re-paved as a Database Host in a later procedure. Limitations and Expectations. Bootstrap Install Procedure. Since Installer notebook may be Windows or Linux OS, and the Customer repository location may vary so the user executing this procedure determines the appropriate detail to execute this task.

Since the installer's notebook may be Windows or Linux OS-based, the user executing this procedure determines the appropriate detail to execute this task. For a Linux based notebook, insert a USB Flash Drive of the appropriate size into a Laptop or some other linux host where the iso can be copied to , and run the dd command to create a bootable USB drive with the Oracle Linux 7 iso. Select the first HDD drive in this case that would be the first one listed or the 1. If the server has already been installed a red banner at the bottom of the page may indicate there is an error condition.

Selecting that banner causes a dialog to appear indicating there is not enough free space which might mean an OS has already been installed.

In the dialog it may show both 1. If the disk selection dialog appears after selecting the red banner at the bottom of the page , this implies a full installation of the RMS has already been performed usually this is because the procedure had to be restarted after it was successfully completed. In this case select the Modify Disk Selection. This will return to the disk selection page.

Select both HDDs and hit done. The red banner should now indicate the space must be reclaimed. The same steps to reclaim the space can be performed. Enter a root password appropriate for this installation. It is good practice to use a customer provided secure password to minimize the host being compromised during installation. Some of the procedures in this document require a reboot of the system and are indicated in the procedure. Once the remote console has been exposed, the system must be reset to force it through the restart process.

When the initial window is displayed, hit the F9 key repeatedly. Once the F9 is highlighted at the lower left corner of the remote console, it should eventually bring up the main System Utility. Note : The server reset must go through an attempt to boot before the changes will actually apply. This page defines the legacy BIOS boot order. When the server begins the scan for the response, it scans down this list until it receives the response.

To move an entry, select that entry, hold down the first mouse button and move the entry up in the list below the entry it must reside under. The default values for each option is Enabled. The actual configuration may be different. The secondary bootable device is left as Not Set. Configuration Procedure. Modify these values with the following sed commands, or use an editor such as vi etc.

Once this is complete, the ToR Switches will attempt to boot from the tftpboot files automatically. Eventually the verification steps can be executed below. It may take about 5 minutes for this to complete. When SNMPv2c configuration is needed, ssh to the two switches, run the following commands:.

After that, the username and password can be used to access OAs. This procedure provides the steps required to enable virtualization on a given Bare Metal Server. Virtualization can be configured using the default settings or via the default Workload Profiles. This step provides the steps required to enable virtualization on a given Bare Metal Server.

Virtualization can be configured using the default settings or via the Workload Profiles. This procedure should be repeated for any RAID configuration. This steps provide necessary to configure the primary and secondary bootable devices for a Gen10 Server. If the boot devices are not set then Not Set is displayed for the primary and secondary devices. When trying to save the config, the following prompt is received: [HPE] [HPE] save The current configuration will be written to the device.

Are you sure? The cfg file will be used for next reboot. Run the following commands:. This hosts. This is the. It needs to be in two places, one for the local system, and one for the target systems. The iso file must be accessible from a Customer Site Specific repository. The example below uses OracleLinux If this file was copied to the Utility USB, it can be copied from there into the same directory on the Bootstrap Host.

Run the following commands using sudo nfs-utils has already been installed in previous steps. This command generates a private and public key for the cluster. These keys are passed to the Bastion Host and used to communicate to other nodes from that Bastion Host. The public key is passed to each node on OS install.

Do not supply a passphrase when it asks for one. Click Enter. This section details the steps required to execute the automated configuration of the Bastion Host VM. This consists of two main section:. This is the process of uploading the qcow2 image to an openstack environment. The image is provided at OSDC. A qcow2 image was provided as part of the OSDC download and should be available on the users OpenStack Environment as per the previous section of this document.

This file exports a number of environment variables on the Bootstrap Host for the given user which directs the OpenStack Client commands towards the particular OpenStack Environment. It must be copied to the users home directory on the Bootstrap Host so that the OpenStack Client commands can be executed.

This will download a openrc. These files must be copied to the directories listed using scp or some other means ie. MetalLB Configuration. The peer pool names are user specific, defined in any order, there is no limitation on the number of peer pools, and they should all be lowercase chars. It will start with the first indicated IP and apply them sequentially.

For example: The user must guarantee these addresses are available. If the field avoid-buggy-ips: true is added to the peer address-pool, then MetalLB will skip addresses. Updating cluster. The cluster. The fields in the cluster. The steps below detail how to collect and set the fields that must be changed. These instructions may vary depending on whether the user is deploying the cluster using floating IPs or using fixed IP. Differences are noted below when needed.

This field defaults to true and should remain as set if the user is configuring their system to use floating IPs allocated from existing DHCP enabled networks defined within their Openstack Provider. If the user wishes to use fixed IPs, this field must be set to false. Note : All fields in the cluster. Note : This field is used to create each of the nodes contained within the cluster.

Kubespray does not allow upper case alphanumeric characters to be used in the node hostname. Do not use any uppercase characters when defining this cluster-name field. Note : The fields below also includes the openstack command used to retrieve the necessary information. It is possible for a network to be defined that does not include a Name value assigned to it.

It is important that the network and subnet include a Name value assigned to it. This section describes the procedure to deploy the VMs in the OpenStack Environment, configure the Bastion Host, and deploy and configure the Kubernetes clusters. Deploying Using Fixed IPs. If the script detects any incorrect configurations within the fixed IP specific fields, it will produce an error explaining why and stop execution before the VMs are instantiated on the Openstack Provider using terraform.

Deploy Command Execution. Change MySQL root user password. Previous Next JavaScript must be enabled to correctly display this content. ApplyOperatingSystem 0x The error efe means that the connection with the server was terminated abnormally.

Check the network configuration for random client-server connection issues happening on the remote VLAN. If you enable update synchronization before you install hotfix , WSUS doesn't recognize the Upgrades classification and instead treats the upgrade like a regular update. You can prevent this by installing hotfix before you enable update synchronization.

However, if you have already run into this problem, do the following: Disable the Upgrades classification. Install hotfix Delete previously synched updates.

Enable the Upgrades classification. Perform a full synch. Specifically, the CopyToCache operation fails on clients that have already downloaded the upgrade because Windows Server Update Services has bad metadata related to the upgrade.

Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadata before you installed the hotfix. Stop the Windows Update service. Sign in as a user with administrative privileges, and then do the following: Open Administrative Tools from the Control Panel. Double-click Services.

Find the Windows Update service, right-click it, and then select Stop. If prompted, enter your credentials. Restart the Windows Update service. Verify device drivers on the computer, and analyze log files to determine the problem driver. This can be caused by an outdated driver or disk corruption. Run checkdisk to repair the file system.

For more information, see the quick fixes section in this guide. Update drivers on the computer, and select "Download and install updates recommended " during the upgrade process. Disconnect devices other than the mouse, keyboard and display.

See Windows 10 Specifications and verify the computer meets minimum requirements. Review logs for compatibility information. Review logs for Windows 10 Specifications.

There are multiple possible causes. Analyze log files to determine the issue. This is a generic error that occurs during the OOBE phase of setup. See the 0xC section of this guide and review general troubleshooting procedures described in that section. This error indicates that access was denied while attempting to migrate data.

Analyze log files to determine the data point that is reporting access denied. Analyze log files to determine the data point that is reporting access problems. If there is not enough space, attempt to free up drive space before proceeding with the upgrade.

Note: If your device allows it, you can use an external USB drive for the upgrade process. Windows setup will back up the previous version of Windows to a USB external drive. The external drive must be at least 8GB 16GB is recommended.

The external drive should be formatted using NTFS. Modern setup errors Also see the following sequential list of modern setup mosetup error codes with a brief description of the cause. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback?

Note This is a level topic moderate. Submit and view feedback for This product This page. View all page feedback. In this article. Uninstall antivirus applications. Remove all unused SATA devices. Remove all unused devices and drivers. Update drivers and BIOS. This is generally caused by out-of-date drivers. Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.

Ensure that all that drivers are updated. In addition, you should also install any Geant4 helper you wish to use, especially OpenGL if required, before installing Geant4 itself. You can either download the source codes and compile the libraries or download precompiled packages which are available for a number of platform-compiler. If you choose to or have to compile the packages, you will need:. The ROOT data analysis package may also be needed for post-processing or for using the GATE online plotter enabling the visualization of various simulation parameters and results in real time.

If your gcc compiler is version 6 or newer, then you should use a recent ROOT 6 release. They offer the possibility to have different output formats for your simulations. With newer compilers you may have to do some minor hacking for ECAT you may need to add compiler flags to select the C90 standard, for instance. Compiling software usually requires certain system libraries and compilation tools. Currently lists have been created for Ubuntu Visit the Package Requirements page for detailed package lists.

However, before you do any research, it is highly recommended that you validate your installation. See Validating Installation for benchmarks and further information.

Navigation Getting started 1. Introduction 2. Installation Guide V9. Package Requirements 4. Validating Installation 6. GateRT 7. Introduction Next: 3.