You can connect to the console port of the VM to see the installation logs.
Create the VM using GUI App virt-manager
If your host server has Ubuntu Desktop and virt-manager installed you can use it to deploy the VM. Make sure you can start the Virtual Machine Manager and that it connects successfully to the local hypervisor.
Creating a VM with virt-manager is very straightforward, Use the following steps to deploy the FTAS VM
File -> New Virtual Machine -> Import existing disk image -> Forward
Browse to the FTAS disk image location and select Ubuntu as the OS name
Click "Forward" and select vCPU (min 2 cores) and Memory (4GB) for the VM
Click "Forward", give your VM a name and check "Customize configuration before install"
Select "NIC ...", in the "Network source" select the Linux bridge you created on the host machine
Apply the configuration and start the VM
Create the VM using XML configuration
Create an XML configuration file from the following template
#Execute the below command to attach the VM to the Linux Bridge sonic@sonic-39:~$virshnet-definebridged-network.xmlsonic@sonic-39:~$virshnet-startbr0sonic@sonic-39:~$virshnet-autostartbr0sonic@sonic-39:~$virshnet-listNameStateAutostartPersistent----------------------------------------------------------br0activeyesyessonic@sonic-39:~$
Start the VM
virshcreate<VMXMLconfigurationfile>#sonic@sonic-39:~$ virsh create ftas.xml #Domain FTAS_VM01 created from ftas.xml#sonic@sonic-39:~$
If you see a permission error run the virsh command with sudo may fix the issue
The default username is 'oper' with the default password 'oper@123'
Check connections and devices
sudonmcliconshowoper@ftasvm:~$sudonmcliconshowNAMEUUIDTYPEDEVICEWiredconnection1782de6d4-3867-3c5e-95fb-061ae39e5faeetherneteth0oper@ftasvm:~$# Capture the connection NAME of eth0 device
#verify the IP addressipaoper@ftasvm:~$ipa<..>2:eth0:<BROADCAST,MULTICAST,UP,LOWER_UP>mtu1500qdiscfq_codelstateUPgroupdefaultqlen1000link/ether52:54:00:37:3c:5cbrdff:ff:ff:ff:ff:ffinet192.168.0.37/25brd192.168.0.255scopeglobalnoprefixrouteeth0valid_lftforeverpreferred_lftforeverinet6fe80::70a4:9f2e:658c:4d29/64scopelinknoprefixroutevalid_lftforeverpreferred_lftforever<..>oper@ftasvm:~$#Verify IP methodoper@ftasvm:~$sudonmcli-fipv4.methodconshow"Wired connection 1"ipv4.method:manualoper@ftasvm:~$
Test FTAS VM reachability from outside the VM, if the VM is not reachable please check the access rule at the below location,
There are some scaling scripts that require multiple network service servers (NTP, SYSLOG, TACACS+, etc.). In order to simulate this, we can add a secondary IP address to the VM NIC.
To add a secondary IP address, use the command
FTAS VM
sudonmcliconmod"<con_name>"+ipv4.addresses<ipaddress>/<prefix>#Example - sudo nmcli con mod "Wired connection 1" ipv4.addresses 192.168.0.42/24# Reapply configsudonmclidevicereapply<dev_name>#Example - sudo nmcli device reapply eth0# Show IP address to verifyipa# Restart docker containers so their services can listen on new IP addresses
Network services containers
The FTAS VM has docker containers running and the following docker images installed:
ztp_dhcp(DHCP) services are not run by default as it might conflict with DHCP running in the DC infra.
Net Services container image netservices:v1 (NTP, SYSLOG, TACACS+ services). This container is run with the "--network=host" option. If you need to change the configurations of the services please find them in the following configuration files.
