2020.04.26 – Ubuntu Server Problem: Failed to obtain SCST version information. Are the SCST modules loaded?

This page is abut a problem into Ubuntu server 18.04. Same problem, same preparation that cause the problem and in different Ubuntu 18.04 and.

All happen when working to chapter of Building a VMware vSphere Virtual Lab with VMware Fusion – Part 5: Create a Ubuntu iSCSI Target and Configure Multipathing

Case 1. After Upgrading Ubuntu Server 16.04 to 18.04 LTS in 2020.04.11

Problem:

silvia@silvia:~$ sudo scstadmin -config /etc/scst.conf
Failed to obtain SCST version information. Are the SCST modules loaded?

I try restarting scst and running the config command again:

silvia@silvia:~$ sudo /etc/init.d/scst stop
[ ok ] Stopping scst (via systemctl): scst.service.
silvia@silvia:~$ sudo /etc/init.d/scst start
[ ok ] Starting scst (via systemctl): scst.service.
silvia@silvia:~$ sudo scstadmin -config /etc/scst.conf
Failed to obtain SCST version information. Are the SCST modules loaded?

What does dkms status show?

silvia@silvia:~$ dkms status
scst, 3.4.0, 4.15.0-96-generic, x86_64: installed

Case 2. After installing Linux (Ubuntu Server 18.04) on a Mac with VMware Fusion in 2020.04.13

At the and of chapter Building a VMware vSphere Virtual Lab with VMware Fusion – Part 5: Create a Ubuntu iSCSI Target and Configure Multipathing it is a problem. To solve the problem I apply again all from the chapter of Step 4.2. Installing SCST on Ubuntu 18.04.

The same problem appears at Step 4.6. Export the disk image as an iSCSI LUN:

silvia@silvia:~/scst-build/scst$ sudo scstadmin -config /etc/scst.conf
Failed to obtain SCST version information. Are the SCST modules loaded?

I don’t know a solution to solve this problem.

2020.04.10 – Building a VMware vSphere Virtual Lab with VMware Fusion – Part 5: Create a Ubuntu iSCSI Target and Configure Multipathing – major problem and not finished

I will try to do Part 5 using These idea: I’d recommend using FreeNAS instead of Ubuntu. I’ve just done a test and managed to set up a FreeNAS VM with 2 GB of RAM and managed to create a volume and connect it to ESXi using iSCSI. 

Importanta photos need for understanding are here: https://photos.app.goo.gl/Zd3BCChctkx88MRr7

Before stating I need to get an answer about “What is Ubuntu iSCSI?”

Read more

2018.02.27 – The VMware Tools installation after Easy Install Ubuntu 14.4.1

Components:

  • MacBook Pro with Sierra 10.12.6 as Host
  • VMWare Fusion PRO 10.1.1
  • Ubuntu Desktop 64-bits 14.4.1 LST as Guest

Problem description:
I have installed Ubuntu using Easy Install. After powering on the VM I can’t install VMware Tools. The option is grey/unavailable.

Observation:
The CD-ROM can not be connected because of one error.

Solution:
Open VMware Fusion application > right click on the corresponding VM > Show in Finder > right click on the corresponding .vmwarevm file > Show Package Contents:

  • If you have autoinst.flp in the VM directory – rename
  • If you have autoinst.iso in the VM directory – rename

Where these files are present and/or configured in the vmx – the virtual machine will be launched in automatic installation mode that prevents the connection files iso vmware-tools

VMware Tools Installation

From VMware Fusion application Menu > Virtual Machine > Reinstall VMware Tools > Install
Follow install window indications for further installation inside Ubuntu OS.

Enjoy!

2017.12.13 – Install FreeRadius on Ubuntu VM

Before starting

Install Free Radius

  • Update Ubuntu VM
silvia@ubuntu :~$ sudo apt-get update
  • Install freeradius. I will install also freeradius-mysql to play with mysql later.
silvia@ubuntu :~$ sudo apt-get install freeradius freeradius-mysql
  • Get into root mode
silvia@ubuntu:~$ sudo -i
root@ubuntu:~#
  • I like vim
root@ubuntu:~# vim /etc/freeradius/users 
The program 'vim' can be found in the following packages:
* vim
* vim-gnome
* vim-tiny
* vim-athena
* vim-gtk
* vim-nox
Try: apt-get install <selected package>
root@ubuntu:~# apt-get install vim

[...]

root@ubuntu:~#

Test PAP subscriber

The first step to getting any authentication working in FreeRADIUS is to configure PAP, or clear-text passwords. Even though many deployments will end up using additional authentication protocols, PAP is the simplest and easiest to configure. And as we will see later, once PAP is configured, many other authentication protocols become simple, too.

In this example, we will configure PAP using the users file. The users file is a flat-text file that allows many common policies to be implemented. It is simple to use, easy to edit, and does not require any additional effort to configure databases like LDAP or SQL. It is therefore the ideal configuration file to use when starting to deploy a new server.

To configure PAP authentication, we must tell the server about a particular user, in this case bob. We must also tell the server what the users “known good” password is, in this case hello. This “known good” password will be used to validate the password entered by the user, and sent to FreeRADIUS by the NAS or AP. If the passwords match, then FreeRADIUS will return an Access-Accept packet. If the passwords do not match, then FreeRADIUS will return an Access-Reject packet.

  • Add a test user
root@ubuntu:~# vim /etc/freeradius/users 
silvia Cleartext-Password := "password"

#
# Please read the documentation file ../doc/processing_users_file,
# or 'man 5 users' (after installing the server) for more information.
#
# This file contains authentication security and configuration
# information for each user. Accounting requests are NOT processed
# through this file. Instead, see 'acct_users', in this directory.
#
# The first field is the user's name and can be up to
# 253 characters in length. This is followed (on the same line) with
# the list of authentication requirements for that user. This can
# include password, comm server name, comm server port number, protocol
# type (perhaps set by the "hints" file), and huntgroup name (set by
# the "huntgroups" file).
#
# If you are not sure why a particular reply is being sent by the
# server, then run the server in debugging mode (radiusd -X), and
# you will see which entries in this file are matched.
#
[...]
  • Enter debug mode
root@ubuntu:~# freeradius -X
FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built on Jul 26 2017 at 15:30:42
Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. 
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

[...]

radiusd: #### Opening IP addresses and Ports ####
listen {
 type = "auth"
 ipaddr = *
 port = 0
Failed binding to authentication address * port 1812: Address already in use 
/etc/freeradius/radiusd.conf[240]: Error binding to port for 0.0.0.0 port 1812

Obs: Get normal error as the service is already running

root@ubuntu:~# netstat -unpl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:7682 0.0.0.0:* 929/dhclient 
udp 0 0 127.0.0.1:18120 0.0.0.0:* 50902/freeradius
udp 0 0 0.0.0.0:1812 0.0.0.0:* 50902/freeradius
udp 0 0 0.0.0.0:1813 0.0.0.0:* 50902/freeradius
udp 0 0 0.0.0.0:1814 0.0.0.0:* 50902/freeradius
udp 0 0 0.0.0.0:68 0.0.0.0:* 929/dhclient 
udp 0 0 0.0.0.0:47222 0.0.0.0:* 50902/freeradius
udp6 0 0 :::23210 :::* 929/dhclient
  • Test the created user
root@ubuntu:~# radtest silvia password localhost 0 testing123
Sending Access-Request of id 231 to 127.0.0.1 port 1812
 User-Name = "silvia"
 User-Password = "password"
 NAS-IP-Address = 127.0.1.1
 NAS-Port = 0
 Message-Authenticator = 0x00000000000000000000000000000000
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=231, length=20
  ^---- This text means that authentication succeeded.

 OBS: With the default configuration in Version 2.x, and the above users file entry, the following authentication types will just work:

  • PAP
  • CHAP
  • MS-CHAP
  • EAP-MD5
  • EAP-MSCHAPv2
  • Cisco LEAP

2017.11.16 – Ubuntu VM Network Configuration for vMX

At the moment, my Ubuntu VM is already created with default configuration. Next, I will have to make some changes and connect the Ubuntu VM to the following networks:

Network Connected Device Device Port Info IP
vmnet3 vMX – Ubuntu Server eth0 OoB MNG Net 192.168.83.10
vmnet4 vMX – Ubuntu Server eth1 Intelink with VLANs 172.16.109.10
vmnet5 vMX – Ubuntu Server eth2 Intelink with VLANs 192.168.50.10

Continue reading