On Ubuntu 18.04 right click in the bottom right area no longer works .

So just tap on Touchpad using 2 fingers and you will see the open dialog box.

Example you select copy , and then you can paste it  with same metode , tap with 2 fingers on Touchpad.

Open terminal with press Ctrl + Alt + t

:~$ sudo add-apt-repository ppa:webupd8team/java
[sudo] password for yourusername:
Oracle Java (JDK) Installer (automatically downloads and installs Oracle JDK8). There are no actual Java files in this PPA.

Important -> Why Oracle Java 7 And 6 Installers No Longer Work: http://www.webupd8.org/2017/06/why-oracle-java-7-and-6-installers-no.html

Update: Oracle Java 9 has reached end of life: http://www.oracle.com/technetwork/java/javase/downloads/jdk9-downloads-3848520.html

The PPA supports Ubuntu 18.04, 17.10, 16.04, 14.04 and 12.04.

More info (and Ubuntu installation instructions):
– for Oracle Java 8: http://www.webupd8.org/2012/09/install-oracle-java-8-in-ubuntu-via-ppa.html

Debian installation instructions:
– Oracle Java 8: http://www.webupd8.org/2014/03/how-to-install-oracle-java-8-in-debian.html

For Oracle Java 10, see a different PPA: https://www.linuxuprising.com/2018/04/install-oracle-java-10-in-ubuntu-or.html
More info: https://launchpad.net/~webupd8team/+archive/ubuntu/java
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Hit:1 http://id.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://id.archive.ubuntu.com/ubuntu bionic-updates InRelease [83,2 kB]

…

:~$ sudo apt-get update
[sudo] password for yourusername:
Hit:1 http://id.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://id.archive.ubuntu.com/ubuntu bionic-updates InRelease [83,2 kB]

…

:~$ sudo apt-get install -y oracle-java8-installer

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following additional packages will be installed:
gsfonts-x11 java-common oracle-java8-set-default
Suggested packages:
binfmt-support visualvm ttf-baekmuk | ttf-unfonts | ttf-unfonts-core ttf-kochi-gothic | ttf-sazanami-gothic ttf-kochi-mincho
| ttf-sazanami-mincho ttf-arphic-uming
The following NEW packages will be installed:
gsfonts-x11 java-common oracle-java8-installer oracle-java8-set-default

…

Connecting to download.oracle.com (download.oracle.com)|104.69.165.90|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 190890122 (182M) [application/x-gzip]
Saving to: ‘jdk-8u171-linux-x64.tar.gz’

…

#####Important########
To set Oracle JDK8 as default, install the “oracle-java8-set-default” package.
E.g.: sudo apt install oracle-java8-set-default
On Ubuntu systems, oracle-java8-set-default is most probably installed
automatically with this package.
######################

…

:~$ java -version
java version “1.8.0_171”
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)

:~# nano /etc/environment

Add or put  JAVA_HOME and JRE_HOME

JAVA_HOME=/usr/lib/jvm/java-8-oracle
JRE_HOME=/usr/lib/jvm/java-8-oracle/jre

On your Ubuntu desktop click show applications , and you will found :

Java Monitoring & Management Console

Oracle Java Mission Control

Java Control Panel

Policy Tool

Java VisualVM

Java Cache Viewer

If you want to open file with extension  .jnlp  , select that file , tap anywhere on Touchpad  using 2 fingers  ,  click open with Oracle Java 8 Web Start.  Follow each  instruction guide to access your remote server , and you can  manage remotely your server  , example : reinstall with custom iso file , etc.

PuTTY is an SSH and telnet client, developed originally by Simon Tatham for the Windows platform. PuTTY is open source software that is available with source code and is developed and supported by a group of volunteers.

You can download PuTTY here.

After finished download , click PuTTY in the left sidebar menu windows.

Type yourremoteIP in the box Host Name (or IP address ) then click Open

Click Yes , and type your username and password.

From your remote host generate key pair using ssh-keygen.

:~$ ssh-keygen -b 4096 -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/helloiamnewuser/.ssh/id_rsa):
Created directory ‘/home/helloiamnewuser/.ssh’.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/helloiamnewuser/.ssh/id_rsa.
Your public key has been saved in /home/helloiamnewuser/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:WhlZ7/YpQlaZyqlnmhjrFZdHPkE7B8GhXzX/a1J0fk0 helloiamnewuser@f674
The key’s randomart image is:
+—[RSA 4096]—-+
| . o=+.|
| o . ++o+|
| o *+ooE|
| +.=o.=*+|
| S Boo..o=|
| + O.. …o|
| o +.. ..oo |
| .. . .o |
| .o. |
+—-[SHA256]—–+

:~$ cd /home/helloiamnewuser/.ssh

:~/.ssh$ echo “$(cat id_rsa.pub)” > authorized_keys

:~/.ssh$ ls -ahl

total 20K
drwx—— 2 helloiamnewuser helloiamnewuser 4.0K May 19 07:09 .
drwxr-xr-x 4 helloiamnewuser helloiamnewuser 4.0K May 19 06:41 ..
-rw-rw-r– 1 helloiamnewuser helloiamnewuser 746 May 19 07:09 authorized_keys
-rw——- 1 helloiamnewuser helloiamnewuser 3.2K May 19 06:41 id_rsa
-rw-r–r– 1 helloiamnewuser helloiamnewuser 746 May 19 06:41 id_rsa.pub

To view the content of authorized_keys type cat authorized_keys

:~/.ssh$ cat authorized_keys

Next , download private key to localhost computer.

From your localhost computer type this command :

:~$ scp helloiamnewuser@yourremoteIP:/home/helloiamnewuser/.ssh/id_rsa /home/yourpathdirectory/Downloads
helloiamnewuser@yourremoteIP’s password:
id_rsa 100% 3247 7.7KB/s 00:00

Now you have a private key id_rsa , and try to connect your remote host

:~$ ssh -i /home/yourpathdirectory/Downloads/id_rsa helloiamnewuser@youremoteIP 
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 3.13.0-147-generic x86_64)

If you use windows you can use PuTTy to make a connection to your server ( VPS or Dedicated Server  ) .

This example below use Ubuntu terminal.

Open your localhost terminal with press Ctrl + Alt +  t

:~# ssh root@yourremoteIP
The authenticity of host ‘yourremoteIP (yourremoteIP)’ can’t be established.
ECDSA key fingerprint is SHA256:oqWPHYbSHWQ0TGtNu4Ndxg23/fJ2GfhgUjgGkmo40G0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘yourremoteIP’ (ECDSA) to the list of known hosts.
root@yourremoteIP’s password:
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 3.13.0-147-generic x86_64)

…

For security reason use root via ssh is not recommend.

Before change file sshd_config you should create a new user to access your server.

Username uses the small character , and change username ” helloiamnewuser” with your own.

:~# adduser helloiamnewuser

If you got error connection from localhost to remote host such as below :

~$ ssh root@yourIP
ssh: connect to host yourIP port 22: Connection timed out

Inside Server  Management click button Start Rescue Mode

Your server will be rebooted and boot the rescue image from the network

If the boot process finished, you can connect to the server via SSH (any possible error messages from your SSH client can be ignored).

Reload your web page and you can see :

Try to connect to host again via SSH

~$ ssh root@yourIP
The authenticity of host ‘yourIP (yourIP)’ can’t be established.
ECDSA key fingerprint is SHA256:lZ+8QbqFQeX5XWrWCIRcJiQNA6OK9oRCHBorX+2/CJU.
Are you sure you want to continue connecting (yes/no)? yes

The rescue system does not mount your drives automatically – You will have to do it manually; This happens via the “mount” command. Normally the system is located on the second partition on the first hard drive, Linux specific it would be named /dev/hda2 or /dev/sda2 , the command would be:
mount /dev/hda2 /mnt
or
mount /dev/sda2 /mnt

The software raid device is normally called /dev/md0 . If the raid is degraded, the devices splits into /dev/md126 and /dev/md127 .

The hard drives content can be found in the /mnt directory. You can do changes on the system or download files via SCP (for example with WinSCP).

Please notice that the rescue mode will be active as long as you deactivate it.

The rescue mode use operating system Debian

root@grml ~ # fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0006948f

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 4095 2048 1M 83 Linux
/dev/sda2 4096 16005119 16001024 7.6G fd Linux raid autodetect
/dev/sda3 * 16005120 18006015 2000896 977M fd Linux raid autodetect
/dev/sda4 18006016 1953523711 1935517696 922.9G fd Linux raid autodetect

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0007233d

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 4095 2048 1M 82 Linux swap / Solaris
/dev/sdb2 4096 16005119 16001024 7.6G fd Linux raid autodetect
/dev/sdb3 * 16005120 18006015 2000896 977M fd Linux raid autodetect
/dev/sdb4 18006016 1953523711 1935517696 922.9G fd Linux raid autodetect

Disk /dev/loop0: 420.8 MiB, 441192448 bytes, 861704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md127: 976.4 MiB, 1023868928 bytes, 1999744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md126: 15.3 GiB, 16384000000 bytes, 32000000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/md125: 922.8 GiB, 990850646016 bytes, 1935255168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@grml ~ # mount /dev/md125 /mnt
root@grml ~ # ls /mnt -ahl
total 104K
drwxr-xr-x 22 root root 4.0K May 15 10:55 .
drwxr-xr-x 33 root root 280 May 15 14:07 ..
drwxr-xr-x 2 root root 4.0K May 15 10:26 bin
drwxr-xr-x 2 root root 4.0K May 14 23:17 boot
drwxr-xr-x 3 root root 4.0K May 14 23:19 dev
drwxr-xr-x 90 root root 4.0K May 15 12:24 etc
drwxr-xr-x 2 root root 4.0K Apr 10 2014 home
lrwxrwxrwx 1 root root 34 May 14 23:22 initrd.img.old -> boot/initrd.img-3.13.0-147-generic
drwxr-xr-x 23 root root 4.0K May 15 10:55 lib
drwxr-xr-x 2 root root 4.0K May 15 10:16 lib64
drwx—— 2 root root 16K May 14 23:17 lost+found
drwxr-xr-x 2 root root 4.0K May 14 23:17 media
drwxr-xr-x 2 root root 4.0K May 15 10:15 mnt
drwxr-xr-x 2 root root 4.0K May 14 23:17 opt
drwxr-xr-x 2 root root 4.0K Apr 10 2014 proc
drwx—— 4 root root 4.0K May 15 13:16 root
drwxr-xr-x 2 root root 4.0K May 14 23:33 run
drwxr-xr-x 2 root root 12K May 15 10:27 sbin
drwxr-xr-x 2 root root 4.0K May 14 23:17 srv
drwxr-xr-x 2 root root 4.0K Mar 13 2014 sys
drwxrwxrwt 8 root root 4.0K May 15 13:45 tmp
drwxr-xr-x 10 root root 4.0K May 14 23:17 usr
drwxr-xr-x 11 root root 4.0K May 14 23:17 var
lrwxrwxrwx 1 root root 31 May 14 23:22 vmlinuz.old -> boot/vmlinuz-3.13.0-147-generic
root@grml ~ # vi /mnt/etc/network/interfaces

Edit your interfaces file to fix your  network error connection. Save file with press :wq    Enter

root@grml ~ # umount /dev/md125 /mnt
umount: /mnt: not mounted
32 root@grml ~ # ls /mnt -ahl
total 0
drwxr-xr-x 2 root root 3 Apr 26 2015 .
drwxr-xr-x 33 root root 280 May 15 14:07 ..
root@grml ~ #

Go to Server Management and click Stop Rescue Mode

After click  restart button try to connect to host again via SSH.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

~$ ssh-keygen -f “/home/yourlocaldirectory/.ssh/known_hosts” -R “yourIP”
# Host yourIP found: line 15
/home/yourlocaldirectory/.ssh/known_hosts updated.
Original contents retained as /home/yourlocaldirectory/.ssh/known_hosts.old

~$ ssh root@yourIP
The authenticity of host ‘yourIP (yourIP)’ can’t be established.
ECDSA key fingerprint is SHA256:oqWPHDRSHWQ0TGtNhgw2xg23/fJ2GsecRjgGkmo40G0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘yourIP’ (ECDSA) to the list of known hosts.
root@yourIP’s password:
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 3.13.0-147-generic x86_64)

What is IPMI ?

IPMI (  Intelligent Platform Management Interface )  is a hardware level interface specification that is ‘management software neutral’ providing monitoring and control functions that can be exposed through standard management software interfaces such as DMI, WMI, CIM, SNMP, etc. As a hardware level interface, it sits at the bottom of a typical management software stack.

IPMI is best used in conjunction with system management software running under the operating system. This provides an enhanced level of manageability by providing in-band access to the IPMI management information and integrating IPMI with the additional management functions provided by management applications and the OS. System management software and the OS can provide a more sophisticated control, error handling and alerting, than can be directly provided by the platform management subsystem.

Enhanced Authentication

Extensions to the protocols for IPMI over IP, collectively referred to as “RMCP+”, support new algorithms that provide more robust key exchange process for establishing sessions and authenticating users. These steps more closely align with those used for the DMTF ASF 2.0 specification (see [ASF2.0]), making it simpler to create applications that can connect to both ASF and IPMI-based system.

VLAN Support

Configuration options have been added to support IEEE 802.1q VLAN (virtual LAN) headers for IPMI over IP sessions on IEEE 802.3 Ethernet. VLAN works with VLAN-aware routers and switches to allow a physical network to be partitioned into ‘virtual’ networks where a group of devices on different physical LAN segments which can communicate with each other as if they were all on the same physical LAN segment. This can be used to isolate classes of network membership at the Ethernet Packet level rather than at the IP level, as might be done with a router. This can be used to set up a ‘management VLAN’ where only devices that are members of that VLAN will receive packets related to management, and, conversely, will be isolated from the need to process network traffic for other VLANs.

Serial Over LAN (SOL)

Serial Over LAN provides a mechanism that enables the serial controller of a managed system to be redirected over an IPMI session over IP. This enables remote console applications to provide access to text-based interfaces for BIOS, utilities, operating systems, and applications while simultaneously providing access to IPMI platform management functions. SOL is implemented as a payload type under the new payload capability in RMCP+.

Payloads

RMCP+ adds the ability to enable IPMI over IP sessions to other types of traffic in addition to IPMI messages. This includes both standard payload types defined in the IPMI specification (such as SOL), and OEM ‘value-added’ payload types.

Encryption Support

IPMI messages and other payloads carried over RMCP+ can be encrypted. This enables confidential remote configuration of parameters such as user passwords and transfer of sensitive payload data over SOL.

Extended User Login Options

New options support “Role Only” logins for simple environments where it is desirable to just enable logins according to a given privilege level, without the need to assign or configure usernames. Support for “two-key” logins enables a BMC to be configured for a very robust environment, where both a user-specific and BMC-specific key are required to connect to a given BMC.

Firmware Firewall

Firmware Firewall is the name for a collection of commands that enable a BMC implementation to restrict the ability to execute certain commands or functions from a given interface. This can be used to protect against operations that errant or malicious software may use to affect the managed system or other systems. For example, this enables a BMC to block the ability for local software to send a Chassis Control command to reset another blade in a modular server implementation where BMCs on individual blades share a common management bus across the blade backplane. Firmware Firewall includes a set of commands that enable software to discover which commands and functions are present and enabled on a given management controller. These commands can be used by themselves to provide a more efficient way for software and conformance tests to discover which features are available.

SMBus System Interface (SSIF)

The SMBus System Interface (SSIF) is a new, low pin-count, option for the hardware interface that provides local access to the BMC via a connection to the system’s SMBus host controller. SSIF helps support lower-cost BMC implementations by enabling an interface that can be used on low-cost microcontrollers in low pin-count packages.

IPMI Hardware Components

IPMI provides very few specifications for the actual hardware components used to implement the platform management hardware. IPMI seeks to ‘standardize the interface, not the implementation’. IPMI was designed so that it can be implemented with ‘off-the-shelf’ components. Thus, IPMI does not require specific microcontrollers to be used for management controllers, nor special ASICs or proprietary logic devices. As long as the interface, timing and (in the case of IPMB and ICMB) electrical specifications are met, the choice of components is up to the implementer. It is mandatory to implement a system interface that is compatible with one of the three specified system interfaces.

Source from https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-intelligent-platform-mgt-interface-spec-2nd-gen-v2-0-spec-update.html

HP Integrated Lights-Out (iLO)

iLO is a kind of remote control interface, using which administrator can control the server below the operating system layer, and even below the physical console, BIOS/UEFI etc.

The Advanced iLO is Lic. for One server to advance the remote management feature as: GUI , Virtual Media…

iLO provides more features :
– remote scripting
– directory integration
– virtual media
– encrypted data streams
– agent and SIM integration
– terminal services

The HP iLO management processor is the core foundation and intelligence of all HP ProLiant servers. HP iLO functions out-of-the-box without additional software installation and functions regardless of the servers’ state of operation. HP iLO can be accessed from any location via a web browser and works hand-in-hand with HP Systems Insight Manager, HP Insight Control, and Matrix Operating Environment, helping customers unleash the value of the HP ProLiant platform and deliver the highest possible quality of IT service to the business. HP iLO management processors for HP ProLiant Gen8 servers help simplify server setup, engage health monitoring and power and thermal control, and promote remote administration. Building on the legendary HP iLO technology, key elements like HP Agentless Management and HP Active Health System, are standard features found within the next generation of iLO (iLO4) under the HP iLO Management Engine portfolio and all HP ProLiant Gen8 servers.

Example configuration

In the following examples we assume that the following IPs are used:

IP Host: 10.0.1.100/24
IP Gateway: 10.0.1.1
IP VM: 10.0.2.100/32

Host-configuration

In your virtualizing software you need to create a bridged setup for your virtual machine. On VMware vSphere your vSwitch needs to be “connected” to the NIC of your server. When using most other virtualization environments, like Proxmox or Solus VM, this is default when you chose bridged-setup.

VM-configuration

the base-installation needs to be done offline from an installation-medium, because installers usually do not allow the setup which is needed. After installation hostrouting can be configured using configuration-files:

Debian/Ubuntu

On Debian or Ubuntu you need to setup the NIC of your virtual machine as follows:

/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
	address 10.0.2.100
	netmask 255.255.255.255	pointopoint 10.0.1.1
        gateway 10.0.1.1

CentOS

On CentOS network is configured in /etc/sysconfig/network-scripts. Two files need to be created here. Notice, that also the MAC-address of your NIC (see “ifconfig”)

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE="eth0"
BOOTPROTO="static"
HWADDR="00:11:22:33:44:55"
IPADDR=10.0.2.100
NETMASK=255.255.255.255
NM_CONTROLLED="no"
ONBOOT="yes"
SCOPE="peer 10.0.1.1"
GATEWAY="10.0.1.1"

/etc/sysconfig/network-scripts/route-eth0

default via 10.0.1.1 dev eth0

openSUSE

on openSUSE two files need to be created as well,

/etc/sysconfig/network/ifcfg-eth0

BOOTPROTO='static'
STARTMODE='auto'
NAME='82540EM Gigabit Ethernet Controller'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='10.0.2.100/32'
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'

/etc/sysconfig/network/routes

10.0.1.1 - 255.255.255.255 eth0 
default 10.0.1.1 - eth0

FreeBSD

sorry, for explaiOn FreeBSD, everything can be setup in /etc/rc.conf:

/etc/rc.conf

interface_re0="inet 10.0.2.100 netmask 255.255.255.255"
static_routes="gateway default"
route_gateway="10.0.1.1 -iface re0"
route_default="default 10.0.1.1"

Windows

Windows saves the right configuration after issuing the following command (notice, that “Local Area Network” might be localized):

netsh interface ip set address name=“Local Area Network“ static 10.0.2.100 255.255.255.255 10.0.1.1 1

You can also use the configuration-assistant, but you will get a warning when applying configuration – this warning can be ignored, setup will work.