AZURE LINUX

 1) Console GUI enable serial console enable or blank serial screen

systemctl enable --now getty@ttyS0

systemctl enable getty@ttyS0 --now

systemctl status serial-getty@ttyS0.service

systemctl start serial-getty@ttyS0.service

systemctl enable --now cockpit.socket

2) Special Disk Vs  General Disk in Azure

Special Disk - Created from DISK SNAPSHOT

General Disk - CX customized disk , like they will install whatever they need in one OS and make it generalize then whenever they need same configuration they will create VM from the Generalized Disk/VM

3) How to map Azure portal LUNs to OS disk , 4 data disk added and each disk shows below

ls -lrt /dev/block ==> shows output with increment number

lrwxrwxrwx. 1 root root 6 Jan  5 05:49 8:0 -> ../sda

lrwxrwxrwx. 1 root root 7 Jan  5 05:49 8:1 -> ../sda1

lrwxrwxrwx. 1 root root 8 Jan  5 05:49 8:15 -> ../sda15

lrwxrwxrwx. 1 root root 7 Jan  5 05:49 8:2 -> ../sda2

lrwxrwxrwx. 1 root root 8 Jan  5 05:49 8:14 -> ../sda14

lrwxrwxrwx. 1 root root 6 Jan  5 05:49 8:16 -> ../sdb

lrwxrwxrwx. 1 root root 7 Jan  5 05:49 8:17 -> ../sdb1

lrwxrwxrwx. 1 root root 6 Jan  5 06:41 8:32 -> ../sdc

lrwxrwxrwx. 1 root root 7 Jan  5 06:41 8:33 -> ../sdc1

lrwxrwxrwx. 1 root root 6 Jan  5 06:42 8:48 -> ../sdd

lrwxrwxrwx. 1 root root 6 Jan  5 06:43 8:64 -> ../sde

lrwxrwxrwx. 1 root root 6 Jan  5 06:54 8:80 -> ../sdf

Observation : 8:0 to 8:15 allocated to sda

8:16 to 8:31 allocated to sdb

8:32 to 8:47 allocated to sdc

8:48 - sdd

8:64 - sde

8:80 - sdf 

which means increment of 16 number for new disk

[root@centos scsi1]# pwd

/dev/disk/azure/scsi1

[root@centos scsi1]# ls -lrt

total 0

lrwxrwxrwx. 1 root root 12 Jan  5 06:41 lun0 -> ../../../sdc

lrwxrwxrwx. 1 root root 13 Jan  5 06:41 lun0-part1 -> ../../../sdc1

lrwxrwxrwx. 1 root root 12 Jan  5 06:42 lun2 -> ../../../sdd

lrwxrwxrwx. 1 root root 12 Jan  5 06:43 lun3 -> ../../../sde

lrwxrwxrwx. 1 root root 12 Jan  5 06:54 lun1 -> ../../../sdf

These LUNS are matching with Azure portal LUN's

4)VM not booting post migration 

In this case we created the following file manually and added the required drivers for Hyper V

#vi /etc/dracut.conf.d/01-azure.conf

add_drivers+=" hv_vmbus hv_netvsc hv_storvsc "

Then we regenerate the inird with the command :   #dracut --verbose --force  

5)Basic main outputs and logs collecting during the OS troubleshoot

1) date;uptime;uname -a;free -m;nproc;cat /etc/*-release;last | grep -i boot;

2) df -hTP; lsblk; lsblk -f; blkid; fdisk -l; ls -lrt /dev/disk/azure/scsi1;

3) cat /etc/fstab;

4) curl -s https://checkip.amazonaws.com; ip addr; ip route; ifconfig -a; route -n; 

5) ufw status ; systemctl status firewalld; sestatus; iptables -L

6) systemctl status walinuxagent -l ; systemctl status waagent -l

7) systemctl list-unit-files | egrep "waagent|cloud"

8) waagent --version

9) telnet 168.63.129.16 80

10) telnet 168.63.129.16 32526

11) curl http://168.63.129.16/?comp=versions

12) curl www.google.com

LVM Outputs

1) pvs; vgs; lvs; lvdisplay

2) attach lvm.conf file

SAR logs and SOS report 

8) zip and attach /var/log/sa directory logs 

9) run “sosreport --all-logs”  ( Redhat/CentOS/OracleLinux/Ubuntu) 

10) run “supportconfig -l” ( SUSE)

Cluster logs

11) hb_report -f "2019/11/02 08:00" -t "2019/11/02 10:00" /tmp/hb_report_log-$(date +"%Y%m%d-%H%M") - SUSE    OR

      hb_report -u root -f "2019/11/02 08:00" -t "2019/11/02 10:00" /tmp/hb_report_log-$(date +"%Y%m%d-%H%M") - SUSE

12) crm_report -f "YYYY-M-D HQ:MQ:S" -t "YYYY-M-D HQ:MQ:S" -o /tmp/crm_report_log-$(date +"%Y%m%d-%H%M") -  RHEL

dd