How to Collect Logs from VM Bootup

Transcription

1 How to Collect Logs from VM Bootup Contents Introduction VM Bootup Introduction This document describes how to collect logs when a Virtual Machine (VM) of Virtualized Packet Core (VPC) in Cisco Ultra Services Platform (Ultra M) boots up and points to multiple boot ups. Contributed by Dennis Lanov, Cisco TAC Engineer. VM Bootup In order to boot a VM with Control Function (CF) or Service Function (SF), you can include multiple steps and checks that are covered here. When you monitor a VM, it has to be via Serial1 because that includes all debug logs. Identify Instance of VM to Monitor. Option 1. Via GUI log in to Dashboard. Navigate to Admin > Instances, find instance that for example, _c1 and find compute host, in the example here, C1 is on compute 1 and C2 is on compute 2. Navigate to the console side and check QEMU instance as shown in this image.

2 Option 2. Search for each instance from the 'virsh list' to find out instance name. source from undercloud: source stackrc identify compute node's control IP: nova list SSH to control plane of the compute node with heat-admin: ssh address>. Change to root: sudo su List all instances: virsh list Console to serial 1 of the instance: virsh console instance-<number> serial1 Logs here contain multiple major items at the time of boot up of CF in Slot 1. SF has very similar boot up process. This card was restarted manually: [ ] Restarting system. [ ] machine restart Identify card type: platform_get_card_info CARDTYPE Read in 0x > 0x Read disk and system parameters: "QEMU HARDDISK" Reading Boot priority. Notice ~7 seconds. If you see more than 30 seconds, then it has issues in order to fetch the image. Possible issues: image issue etc.

3 Indication: that compute does not compute access to the location where the image located. Septh or Cinder. Booting priority 1 image : /flash/qvpc-vchitlur.bin config: /flash/day-n.cfg flags : 0x0 Entry at 0x c8f66f ******************************************************************************** Total bytes read: in Sec (17797 KBytes/Sec) Fetch all information and start the boot process: Scale BootStrap RAM Image (32bit,SP,LE,X86) Start StarOS: Invoking StarOS Image... Set up environment: [ ] Linux version staros-v3-scale-64 (yuel@bxb-mitg6-dev10) (gcc version (GCC) ) #1 SMP PREEMPT Thu Feb 23 16:10:46 EST 2017 Boxer process gets instantiated: Boxer /etc/rc beginning. Identify this hosted environment QEMU and add DVD-ROM: [ ] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 2.3. PQ: 0 ANSI: 5 [ ] ata2.01: ATAPI: QEMU DVD-ROM, 2.3.0, max UDMA/100 [ ] ata2.01: configured for MWDMA2 [ ] sd 0:0:0:0: [sda] byte logical blocks: (4.29 GB/4.00 GiB) [ ] scsi 0:0:1:0: Direct-Access ATA QEMU HARDDISK 2.3. PQ: 0 ANSI: 5 [ ] sd 0:0:0:0: [sda] Write Protect is off [ ] sd 0:0:1:0: [sdb] byte logical blocks: (17.1 GB/16.0 GiB) [ ] sd 0:0:1:0: [sdb] Write Protect is off [ ] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ ] scsi 1:0:1:0: CD-ROM QEMU QEMU DVD-ROM 2.3. PQ: 0 ANSI: 5 Search for parameters file on configuration drive:

4 ...Looking for staros_param.cfg on config driveinitial card type is 64...Looking for param.cfg on boot1. [ ] usb 1-1: new full speed USB device using uhci_hcd and address 2 Map the file Parameters in staros_param.cfg file and take precedence if there are any conflicts with values stored in the /boot1/param.cfg: Found param.cfg in local disk Set 0x into sn_cardtype : Found staros_param.cfg in config drive Mount:...mounting /var/crash from tmpfs...detected KVM Guest...UUID DD2C2139-9E98-4C1B-B87F-83BBD9E8270B Add NIC cards:...loading networking kernel modules...virtio net [ ] Selected 1 Queues, Max-Queue = 1, Online CPUs=8 [ ] Selected 1 Queues, Max-Queue = 1, Online CPUs=8...vmxnet3 [ ] VMware vmxnet3 virtual NIC driver - version k-NAPI...e1000 [ ] e1000: Intel(R) PRO/1000 Network Driver - version k8-NAPI [ ] e1000: Copyright (c) Intel Corporation....e1000e [ ] e1000e: Intel(R) PRO/1000 Network Driver k2 [ ] e1000e: Copyright(c) Intel Corporation....mdio...ixgbe Set up Network Interfaces (NI):...setting up network interfaces DI Internal changing MTU size on VM, SR-IOV is supposed to be enabled: [ ] ixgbevf: cpeth1: ixgbevf_change_mtu: changing MTU from 1500 to 7020

5 ...create vlan interface cpeth Start iftask: waiting for iftask to start... waiting for iftask to start... Start masterd to decide master CF role: start masterd 1 to decide master CF role Broadcards to figure out Master/Standby mode:...broadcasting presence to master CF Check Jumbo Packets: First small size ping, mid size and jumbo: Pinging(size=56) master slot : card2 Pinging(size=1472) master slot : card2 Pinging(size=6992) master slot : card2 Virtual network connectivity OK!