If you’re booting from the ISO, you should see a menu like the following when you first boot:
         lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
          x         Select kernel options and boot kernel          x
          tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
          x Standard Controller Configuration                    > x
          x                                                        x
          x All-in-one Controller Configuration                  > x
          x                                                        x
          x All-in-one (lowlatency) Controller Configuration     > x
          x                                                        x
          x                                                        x
          x                                                        x
          x                                                        x
          x                                                        x
          x                                                        x
          x                                                        x
          mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
  Press [Tab] to edit, [Return] to select, [ESC] to return to previous menu
Here is where you’d select the AIO option.
From: Babu R <babu.r@hotmail.com> 
Sent: Thursday, April 15, 2021 1:07 PM
To: Sullivan, David <David.Sullivan@windriver.com>; Penney, Don <Don.Penney@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] Error while installing simplex virtual AIO-SX
[Please note: This e-mail is from an EXTERNAL e-mail address]
Thanks for the pointer, when I try to install the host there is no option to select All-in-one Controller:
Starting installer, one moment...
anaconda 21.48.22.147-1 for CentOS 7 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* when reporting a bug add logs from /tmp as separate text/plain attachments
16:50:25 Running pre-installation scripts
16:50:29 Not asking for VNC because of an automated install
16:50:29 Not asking for VNC because we don't have a network
Starting automated install.............
Is there a way to control it  by some other means? Please let me know
Sent from 
Mail for Windows 10
From: Sullivan, David <David.Sullivan@windriver.com>
Sent: Thursday, April 15, 2021 10:17:50 PM
To: Penney, Don <Don.Penney@windriver.com>; Babu R <babu.r@hotmail.com>;
starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io>
Subject: RE: [Starlingx-discuss] Error while installing simplex virtual AIO-SX
 
The system type is standard. Only duplex is supported with a standard install. If you want a simplex install you’ll need to reinstall the host and specify ‘All-in-one Controller Configuration’ in the boot menu.
 
From: Penney, Don <Don.Penney@windriver.com>
Sent: Thursday, April 15, 2021 10:58 AM
To: Babu R <babu.r@hotmail.com>; 
starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Error while installing simplex virtual AIO-SX
 
The default “system_mode” value is “simplex”, as far as I know, so I think the only way it would get set to duplex is if that was set in the localhost.yml used. I would double check the file on your system and
 the ansible.log to ensure you don’t have it set twice, maybe, or inadvertently used the wrong localhost.yml file.
 
 
From: Babu R <babu.r@hotmail.com>
Sent: Thursday, April 15, 2021 10:51 AM
To: Penney, Don <Don.Penney@windriver.com>;
starlingx-discuss@lists.starlingx.io
Subject: RE: Error while installing simplex virtual AIO-SX
 
[Please note: This e-mail is from an EXTERNAL e-mail address]
 
This is the value in localhost.yaml:
 
system_mode: simplex
distributed_cloud_role: none
timezone: UTC
 
dns_servers:
- 8.8.8.8
- 8.8.4.4
 
external_oam_subnet: 10.10.10.0/24
external_oam_gateway_address: 10.10.10.1
external_oam_floating_address: 10.10.10.2
 
 
[sysadmin@controller-0 ~(keystone_admin)]$ system show
+----------------------+--------------------------------------+
| Property             | Value                                |
+----------------------+--------------------------------------+
| contact              | None                                 |
| created_at           | 2021-04-15T09:17:31.777303+00:00     |
| description          | None                                 |
| https_enabled        | False                                |
| location             | None                                 |
| name                 | 11cd7071-1a70-4925-b5ba-721bcd51028e |
| region_name          | RegionOne                            |
| sdn_enabled          | False                                |
| security_feature     | spectre_meltdown_v1                  |
| service_project_name | services                             |
| software_version     | 20.06                                |
| system_mode          | duplex                               |
| system_type          | Standard                             |
| timezone             | UTC                                  |
| updated_at           | 2021-04-15T09:19:53.507043+00:00     |
| uuid                 | 371ea48f-df33-4251-9908-6b3646300ec2 |
| vswitch_type         | none                                 |
+----------------------+--------------------------------------+
[sysadmin@controller-0 ~(keystone_admin)]$
 
I see that the system mode is set to duplex
 
From: Penney, Don
Sent: 15 April 2021 20:17
To: Babu R; 
starlingx-discuss@lists.starlingx.io
Subject: RE: Error while installing simplex virtual AIO-SX
 
Please double-check your localhost.yml that you haven’t set “system_mode: duplex”. I don’t think you should see this error message on simplex.
 
Please do “system show”
 
From: Babu R <babu.r@hotmail.com>
Sent: Thursday, April 15, 2021 10:37 AM
To: Penney, Don <Don.Penney@windriver.com>;
starlingx-discuss@lists.starlingx.io
Subject: RE: Error while installing simplex virtual AIO-SX
 
[Please note: This e-mail is from an EXTERNAL e-mail address]
 
ler-0dmin@controller-0 ~(keystone_admin)]$ system interface-network-list control
+--------------+--------------------------------------+--------+--------------+
| hostname     | uuid                                 | ifname | network_name |
+--------------+--------------------------------------+--------+--------------+
| controller-0 | 2ea52872-593a-438e-a560-b314e0726fb4 | enp2s1 | oam          |
| controller-0 | 82313dc8-7ce5-4d7f-ae92-b123580b0295 | lo     | cluster-host |
| controller-0 | e190565d-12c6-4f11-9277-2aef932c6b2c | lo     | mgmt         |
+--------------+--------------------------------------+--------+--------------+
 
 
 
+--------------+--------------------------------------+
| Property     | Value                                |
+--------------+--------------------------------------+
| hostname     | controller-0                         |
| uuid         | e190565d-12c6-4f11-9277-2aef932c6b2c |
| ifname       | lo                                   |
| network_name | mgmt                                 |
+--------------+--------------------------------------+
[sysadmin@controller-0 ~(keystone_admin)]$
 
Please find the mgmt. Interface config. As described in the document it is attached to loopback interface only
 
From: Penney, Don
Sent: 15 April 2021 18:52
To: Babu R; 
starlingx-discuss@lists.starlingx.io
Subject: RE: Error while installing simplex virtual AIO-SX
 
Your error is referring to the management interface, but you’ve included your oam interface config for reference.
 
 
From: Babu R <babu.r@hotmail.com>
Sent: Thursday, April 15, 2021 3:40 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Error while installing simplex virtual AIO-SX
 
[Please note: This e-mail is from an EXTERNAL e-mail address]
I’m getting error while trying to install the virtual AIO-SX. I have installed the ansible playbook
 
ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml
 
Ran these commands
source /etc/platform/openrc
 
OAM_IF=enp2s1
system host-if-modify controller-0 $OAM_IF -c platform
system interface-network-assign controller-0 $OAM_IF oam
system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org
 
[root@localhost ~(keystone_admin)]# system host-unlock controller-0
Cannot unlock host controller-0 when management interface is configured on a virtual interface
 
 
$OAM_IF oamost ~(keystone_admin)]# system interface-network-assign controller-0
+--------------+--------------------------------------+
| Property     | Value                                |
+--------------+--------------------------------------+
| hostname     | controller-0                         |
| uuid         | da172ef6-6e46-4ca2-a81f-93d482e79814 |
| ifname       | enp2s1                               |
| network_name | oam                                  |
+--------------+--------------------------------------+
 
 
enp2s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.10.3  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::5054:ff:fe1f:51fb  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:1f:51:fb  txqueuelen 1000  (Ethernet)
        RX packets 1328682  bytes 1981399747 (1.8 GiB)
        RX errors 444  dropped 0  overruns 0  frame 444
        TX packets 399465  bytes 28981363 (27.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
enp2s2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5054:ff:fe30:f2cb  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:30:f2:cb  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 517  bytes 161254 (157.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
eth1000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5054:ff:fe0d:8c00  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:0d:8c:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 544  bytes 158549 (154.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
eth1001: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5054:ff:fe91:cf78  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:91:cf:78  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 507  bytes 158767 (155.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0                        
 
Any inputs on how to resolve this?
 
Thanks,
Babu