You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Related articles:

Perform the following steps to deploy the OAM with N+1 I-SBC on a KVM instance.

Note

Each VM has the following configuration:

  • RAM = 10 GB
  • vCPU = 4
  • Disk = 50 GB


StepAction
1

Ensure that the Host networking setup is complete:

2

Download the qcow2 image and the config drive creation tool and then copy it to your KVM host, using scp.

  • qcow2 image: sbc-V10.01.01R000-connexip-os_10.00.01-R000_269_amd64.qcow2
  • config_drive creation tool: createConfigDrive-1.0.0.tar.gz
3

Untar the config drive creation tool and create the config drive for the OAM and the I-SBC. 

    1. Create Config Drive for active OAM:

      [root@DEVAGIRI createConfigDrive-1.0.0]# python3 createConfigDrive.py --cli
INFO:__main__:##################################################################
INFO:__main__:  Executing Command : createConfigDrive.py --cli
INFO:__main__:##################################################################
Enter the Product Type [1 - SBC , 2 - OAM]: 2
Enter the SBC CE Role [1- Active, 2- Standby]: 1
Enter the System Name: OAMACTIVE
Enter the Ce Name: oamactive
Enter the Type of mgt IP[1- V4, 2- V6, 3- V4+v6]: 1
Enter the V4 mgt IP of the Active server: 10.54.221.118
Enter the V4 mgt Prefix for Active server: 24
Enter the V4 mgt GW for the Active server: 10.54.221.1
Enter the ha IP for Active server[V4]: 10.54.222.160
Enter the ha Prefix for Active server: 24
Enter the V4 RG IP address one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG): 10.54.222.161
Enter HA fault detection mode[1- Normal, 2- Sensitive]: 1
Enter the ntp IP for the server: 10.128.254.67
Enter the Timezone ID [Check README for the ID(1-595)]: 27
Enter the SBC Type[isbc,ssbc,msbc,mrfp,slb]: isbc
Do you want SSH Public Key based authentication for 'admin' and 'linuxadmin' user [1- Yes, 2-No ]: 2
Do you want to enter EMS settings [1- Yes, 2-No ]: 1
Enter EMS User Name: restuser
Enter EMS Password =
Confirm Password =
Enter EMS IP 1: 10.54.12.221
Do you want to enter 2nd EMS IP[1- Yes, 2-No ]: 2
Cluster/VNF ID value from EMS Cluster Mgmt.: OAMCLUSTER
Download Configuration from EMS [1- True, 2-False ]: 2
Enable or Disable EMA REST module? [1- enable, 2- disable]: 2
Enable or Disable EMA Core module? [1- enable, 2- disable]: 2
Enable or Disable EMA Troubleshooting module? [1- enable, 2- disable]: 2
INFO:__main__:Non HA setup..
INFO:__main__:Cleared old JSON files : Done
INFO:__main__:Creating Extra config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/extraConfig.json under output dir
INFO:__main__:Created OAM config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/oamConfig.json under output dir
INFO:__main__:Created EMS config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/emsConfig.json under output dir
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 671
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
179 extents written (0 MB)
INFO:__main__:Created the active server config drive name : config_drive_oamactive.iso under output dir

    2. Create Config drive for standby OAM:

      [root@DEVAGIRI createConfigDrive-1.0.0]# python3 createConfigDrive.py --cli
INFO:__main__:##################################################################
INFO:__main__:  Executing Command : createConfigDrive.py --cli
INFO:__main__:##################################################################
Enter the Product Type [1 - SBC , 2 - OAM]: 2
Enter the SBC CE Role [1- Active, 2- Standby]: 2
Enter the System Name: OAMSTANDBY
Enter the Ce Name: oamstandby
Enter the Type of mgt IP[1- V4, 2- V6, 3- V4+v6]: 1
Enter the V4 mgt IP of the Active server: 10.54.221.119
Enter the V4 mgt Prefix for Active server: 24
Enter the V4 mgt GW for the Active server: 10.54.221.1
Enter the ha IP for Standby server[V4]: 10.54.222.161
Enter the ha Prefix for Standby server: 24
Enter the V4 RG IP address one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG): 10.54.222.160
Enter HA fault detection mode[1- Normal, 2- Sensitive]: 1
Enter the ntp IP for the server: 10.128.254.67
Enter the Timezone ID [Check README for the ID(1-595)]: 27
Enter the SBC Type[isbc,ssbc,msbc,mrfp,slb]: isbc
Do you want SSH Public Key based authentication for 'admin' and 'linuxadmin' user [1- Yes, 2-No ]: 2
Do you want to enter EMS settings [1- Yes, 2-No ]: 1
Enter EMS User Name: restuser
Enter EMS Password =
Confirm Password =
Enter EMS IP 1: 10.54.12.221
Do you want to enter 2nd EMS IP[1- Yes, 2-No ]: 2
Cluster/VNF ID value from EMS Cluster Mgmt.: OAMCLUSTER
Download Configuration from EMS [1- True, 2-False ]: 2
Enable or Disable EMA REST module? [1- enable, 2- disable]: 2
Enable or Disable EMA Core module? [1- enable, 2- disable]: 2
Enable or Disable EMA Troubleshooting module? [1- enable, 2- disable]: 2
INFO:__main__:Non HA setup..
INFO:__main__:Cleared old JSON files : Done
INFO:__main__:Creating Extra config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/extraConfig.json under output dir
INFO:__main__:Created OAM config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/oamConfig.json under output dir
INFO:__main__:Created EMS config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/emsConfig.json under output dir
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 671
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
179 extents written (0 MB)
INFO:__main__:Created the standby server config drive name : config_drive_oamstandby.iso under output dir

    3. Create config drive for first active I-SBC:

      [root@DEVAGIRI createConfigDrive-1.0.0]# python3 createConfigDrive.py --cli
INFO:__main__:##################################################################
INFO:__main__:  Executing Command : createConfigDrive.py --cli
INFO:__main__:##################################################################
Enter the Product Type [1 - SBC , 2 - OAM]: 1
Enter the SBC HA Mode Type [1 - 1:1 , 2 - N:1]: 2
Enter the SBC CE Role [1- Active, 2- Standby]: 1
Enter the System Name: Isbcsetup
Enter the Ce Name: isbcactive1
Enter the Type of mgt IP[1- V4, 2- V6, 3- V4+v6]: 1
Enter the V4 mgt IP of the Active server: 10.54.221.220
Enter the V4 mgt Prefix for Active server: 24
Enter the V4 mgt GW for the Active server: 10.54.221.1
Do you want to configure second management port (mgt1) [1- Yes, 2-No ]: 2
Enter the ha IP for Active server[V4]: 10.54.222.164
Enter the ha Prefix for Active server: 24
Enter the V4 RG IP address one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG): 10.54.222.164
Enter HA fault detection mode[1- Normal, 2- Sensitive]: 1
Enter the ntp IP for the server: 10.128.254.67
Enter the Timezone ID [Check README for the ID(1-595)]: 27
Enter the SBC Type[isbc,ssbc,msbc,mrfp]: isbc
Do you want SSH Public Key based authentication for 'admin' and 'linuxadmin' user [1- Yes, 2-No ]: 2
Do you want to enter EMS settings [1- Yes, 2-No ]: 1
Enter EMS User Name: restuser
Enter EMS Password =
Confirm Password =
Enter EMS IP 1: 10.54.12.221
Do you want to enter 2nd EMS IP[1- Yes, 2-No ]: 2
Cluster/VNF ID value from EMS Cluster Mgmt.: Isbccluster
Download Configuration from EMS [1- True, 2-False ]: 2
Enable or Disable EMA REST module? [1- enable, 2- disable]: 2
Enable or Disable EMA Core module? [1- enable, 2- disable]: 2
Enable or Disable EMA Troubleshooting module? [1- enable, 2- disable]: 2
Do you want to enter OAM settings [1- Yes, 2-No ]: 1
Enter OAM IP 1: 10.54.222.160
Enter OAM IP 2: 10.54.222.161
Do you want to enter TSBC settings [1- Yes, 2-No ]: 2
INFO:__main__:Non HA setup..
INFO:__main__:Cleared old JSON files : Done
INFO:__main__:Creating Extra config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/extraConfig.json under output dir
INFO:__main__:Created OAM config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/oamConfig.json under output dir
INFO:__main__:Created EMS config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/emsConfig.json under output dir
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 671
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
179 extents written (0 MB)
INFO:__main__:Created the active server config drive name : config_drive_isbcactive1.iso under output dir

    4. Creating config drive for second active I-SBC.

      [root@DEVAGIRI createConfigDrive-1.0.0]# python3 createConfigDrive.py --cli
INFO:__main__:##################################################################
INFO:__main__:  Executing Command : createConfigDrive.py --cli
INFO:__main__:##################################################################
Enter the Product Type [1 - SBC , 2 - OAM]: 1
Enter the SBC HA Mode Type [1 - 1:1 , 2 - N:1]: 2
Enter the SBC CE Role [1- Active, 2- Standby]: 1
Enter the System Name: Isbcsetup
Enter the Ce Name: isbcactive2
Enter the Type of mgt IP[1- V4, 2- V6, 3- V4+v6]: 1
Enter the V4 mgt IP of the Active server: 10.54.221.224
Enter the V4 mgt Prefix for Active server: 24
Enter the V4 mgt GW for the Active server: 10.54.221.1
Do you want to configure second management port (mgt1) [1- Yes, 2-No ]: 2
Enter the ha IP for Active server[V4]: 10.54.221.165
Enter the ha Prefix for Active server: 24
Enter the V4 RG IP address one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG): 10.54.222.164
Enter HA fault detection mode[1- Normal, 2- Sensitive]: 1
Enter the ntp IP for the server: 10.128.254.67
Enter the Timezone ID [Check README for the ID(1-595)]: 27
Enter the SBC Type[isbc,ssbc,msbc,mrfp]: isbc
Do you want SSH Public Key based authentication for 'admin' and 'linuxadmin' user [1- Yes, 2-No ]: 2
Do you want to enter EMS settings [1- Yes, 2-No ]: 1
Enter EMS User Name: restuser
Enter EMS Password =
Confirm Password =
Enter EMS IP 1: 10.54.12.221
Do you want to enter 2nd EMS IP[1- Yes, 2-No ]: 2
Cluster/VNF ID value from EMS Cluster Mgmt.: Isbccluster
Download Configuration from EMS [1- True, 2-False ]: 2
Enable or Disable EMA REST module? [1- enable, 2- disable]: 2
Enable or Disable EMA Core module? [1- enable, 2- disable]: 2
Enable or Disable EMA Troubleshooting module? [1- enable, 2- disable]: 2
Do you want to enter OAM settings [1- Yes, 2-No ]: 1
Enter OAM IP 1: 10.54.222.160
Enter OAM IP 2: 10.54.222.161
Do you want to enter TSBC settings [1- Yes, 2-No ]: 2
INFO:__main__:Non HA setup..
INFO:__main__:Cleared old JSON files : Done
INFO:__main__:Creating Extra config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/extraConfig.json under output dir
INFO:__main__:Created OAM config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/oamConfig.json under output dir
INFO:__main__:Created EMS config JSON file : /root/ANB/createConfigDrive-1.0.0/conf/emsConfig.json under output dir
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 671
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
179 extents written (0 MB)
INFO:__main__:Created the active server config drive name : config_drive_isbcactive2.iso under output dir

    5. Create config drive for standby I-SBC.

      [root@DEOMALI createConfigDrive-1.0.0]# python3 createConfigDrive.py --cli                                                               INFO:__main__:##################################################################
INFO:__main__:  Executing Command : createConfigDrive.py --cli
INFO:__main__:##################################################################
Enter the Product Type [1 - SBC , 2 - OAM]: 1
Enter the SBC HA Mode Type [1 - 1:1 , 2 - N:1]: 2
Enter the SBC CE Role [1- Active, 2- Standby]: 2
Enter the System Name: Isbcsetup
Enter the Ce Name: isbcstandby
Enter the Type of mgt IP[1- V4, 2- V6, 3- V4+v6]: 1
Enter the V4 mgt IP of the Active server: 10.54.221.222
Enter the V4 mgt Prefix for Active server: 24
Enter the V4 mgt GW for the Active server: 10.54.221.1
Do you want to configure second management port (mgt1) [1- Yes, 2-No ]: 2
Enter the ha IP for Standby server[V4]: 10.54.222.166
Enter the ha Prefix for Standby server: 24
Enter the V4 RG IP address one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG): 10.54.222.164
Enter HA fault detection mode[1- Normal, 2- Sensitive]: 1
Enter the ntp IP for the server: 10.128.254.67
Enter the Timezone ID [Check README for the ID(1-595)]: 27
Enter the SBC Type[isbc,ssbc,msbc,mrfp]: isbc
Do you want SSH Public Key based authentication for 'admin' and 'linuxadmin' user [1- Yes, 2-No ]: 2
Do you want to enter EMS settings [1- Yes, 2-No ]: 1
Enter EMS User Name: restuser
Enter EMS Password =
Confirm Password =
Invalid EMS Password. Please re-enter.
Enter EMS Password =
Confirm Password =
Enter EMS IP 1: 10.54.12.221
Do you want to enter 2nd EMS IP[1- Yes, 2-No ]: 2
Cluster/VNF ID value from EMS Cluster Mgmt.: Isbccluster
Download Configuration from EMS [1- True, 2-False ]: 2
Enable or Disable EMA REST module? [1- enable, 2- disable]: 2
Enable or Disable EMA Core module? [1- enable, 2- disable]: 2
Enable or Disable EMA Troubleshooting module? [1- enable, 2- disable]: 2
Do you want to enter OAM settings [1- Yes, 2-No ]: 1
Enter OAM IP 1: 10.54.222.160
Enter OAM IP 2: 10.54.222.161
Do you want to enter TSBC settings [1- Yes, 2-No ]: 2
INFO:__main__:Non HA setup..
INFO:__main__:Cleared old JSON files : Done
INFO:__main__:Creating Extra config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/extraConfig.json under output dir
INFO:__main__:Created OAM config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/oamConfig.json under output dir
INFO:__main__:Created EMS config JSON file : /root/ASB/createConfigDrive-1.0.0/conf/emsConfig.json under output dir
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 671
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
179 extents written (0 MB)
INFO:__main__:Created the standby server config drive name : config_drive_isbcstandby.iso under output dir

NOTE:HA IPs are routable.
4

Rename the qcow2 file with the OAM instance name. Copy the config drive and the qcow2 file to the /var/lib/libvirt/images/ directory of the KVM host.

Example for copying qcow2 file: cp sbc-V10.01.01R000-connexip-os_10.00.01-R000_269_amd64.qcow2 /var/lib/libvirt/images/OAMACTIVE.qcow2

Example for copying the config drive: cp config_drive_oamactive.iso /var/lib/libvirt/images

Note

Ensure to repeat the step for the SBC.

5

Log in to the KVM host. Change the directory to /var/lib/libvirt/images/. Check the qcow2 image size and resize the image disk size to the required capacity.

Note

The default qcow2 image size is 35 GB. Expand the image size based on account log storage requirements and other criteria.


Example: Resize Image disk 
/var/lib/libvirt/images/

#### Check for the virtual size of the image disk. By default, the size size will be 35GB.
qemu-img info <qcow2_image> | grep "virtual size"

#### Resize image disk size to the required size
#### If the current disk is 35GB, and the image disk needs to be 65GB then resize by +30GB(65-35)
# qemu-img resize <qcow2_image> +<required size - current size>G
6

If the HA mode is N:1, you can optionally attach a secondary disk. The secondary disk helps in preserving logs during an upgrade. It also saves space during an image replacement-based upgrade.
Create a secondary disk in the /var/lib/libvirt/images directory:

qemu-img create /var/lib/libvirt/images/<vm_name>Secondary.qcow2 +<disk_size>G -f qcow2
7

Attach the disk and launch the VM:

If you are attaching a mirror disk, use this step and skip the next step.


Example: Attach Mirror Disk and Launch OAM VM
virt-install --name=OAMACTIVE --ram=10240 --memorybacking hugepages=yes --vcpus sockets=1,cores=2,threads=2/
--cpu host-passthrough --disk path=/var/lib/libvirt/images/OAMACTIVE.qcow2,device=disk,bus=virtio,format=qcow2,size=50/
--disk path=/var/lib/libvirt/images/config_drive_oamactive.iso,device=disk,bus=virtio,serial=RIBBON_CONFIG_DRIVE/
--disk path=/var/lib/libvirt/images/OAMACTIVEMirror.qcow2,device=disk,bus=virtio,serial=RIBBON_MIRROR_DRIVE/
--network=bridge:MGT0,model=virtio --network=bridge:HA0,model=virtio/
--cputune=vcpupin0.vcpu=0,vcpupin0.cpuset=2,vcpupin1.vcpu=1,vcpupin1.cpuset=10,
vcpupin2.vcpu=2,vcpupin2.cpuset=3,vcpupin3.vcpu=3,vcpupin3.cpuset=11 --numatune=0,mode=strict/
--import --os-type=linux --os-variant=debianwheezy --arch=x86_64 --autostart --noautoconsole --vnc --virt-type kvm


Example: Attach Mirror Disk and Launch SBC VM
virt-install --name=ISBC-Active --ram=10240 --memorybacking hugepages=yes --vcpus sockets=1,cores=2,threads=2/
--cpu host-passthrough --disk path=/var/lib/libvirt/images/ISBCActive.qcow2,device=disk,bus=virtio,format=qcow2,size=50/
--disk path=/var/lib/libvirt/images/config_drive_isbcactive1.iso,device=disk,bus=virtio,serial=RIBBON_CONFIG_DRIVE/
--disk path=/var/lib/libvirt/images/ISBC-ActiveMirror.qcow2,device=disk,bus=virtio,serial=RIBBON_MIRROR_DRIVE/
--network=bridge:MGT0,model=virtio --network=bridge:HA0,model=virtio --network=bridge:PKT0,model=virtio --network=bridge:PKT1,model=virtio/
--cputune=vcpupin0.vcpu=0,vcpupin0.cpuset=8,vcpupin1.vcpu=1,vcpupin1.cpuset=44,
vcpupin2.vcpu=2,vcpupin2.cpuset=10,vcpupin3.vcpu=3,vcpupin3.cpuset=46 --numatune=0,mode=strict/
--import --os-type=linux --os-variant=debianwheezy --arch=x86_64 --autostart --noautoconsole --vnc --virt-type kvm
8

Launch the instance using virt-install command and immediately stop it (using virsh shutdown), to edit the XML file created during the launching of the instance.

Note

Use this step if you are not attaching a mirror disk.


 a. An example to create a VM with 4VCPU, 10GB memory, and using Linux bridges (you must provide the bridge names created at the start) for networking is shown below along with pinning the guest CPUs to Host VCPUs.
         i. Ensure the virtio network is in MGT0 and HA0, in that order. If the PKT network is also virtio, then the order is MGT0, HA0, PKT0, PKT1.
         ii. If the second management interface is used, provide the mgt1 network after the PKT networks.
         iii. For the OAM, packet interfaces are not required.

Example for Launching Active OAM
virt-install --name=OAMACTIVE --ram=10240 --memorybacking hugepages=yes --vcpus sockets=1,cores=2,threads=2
--cpu host-passthrough --disk path=/var/lib/libvirt/images/OAMACTIVE.qcow2,device=disk,bus=virtio,format=qcow2,size=50 
--disk path=/var/lib/libvirt/images/config_drive_oamactive.iso,device=disk,bus=virtio,serial=RIBBON_CONFIG_DRIVE 
--network=bridge:MGT0,model=virtio --network=bridge:HA0,model=virtio 
--cputune=vcpupin0.vcpu=0,vcpupin0.cpuset=2,vcpupin1.vcpu=1,vcpupin1.cpuset=10,
vcpupin2.vcpu=2,vcpupin2.cpuset=3,vcpupin3.vcpu=3,vcpupin3.cpuset=11 --numatune=0,mode=strict
--import --os-type=linux --os-variant=debianwheezy 
--arch=x86_64 --autostart --noautoconsole --vnc --virt-type kvm


Example for Launching Active SBC
virt-install --name=SBCactive --ram=10240 --memorybacking hugepages=yes 
--vcpus sockets=1,cores=2,threads=2 --cpu host-passthrough 
--disk path=/var/lib/libvirt/images/ISBCActive.qcow2,device=disk,bus=virtio,format=qcow2,size=50 
--disk path=/var/lib/libvirt/images/config_drive_isbcactive1.iso,device=disk,bus=virtio,serial=RIBBON_CONFIG_DRIVE 
--network=bridge:MGT0,model=virtio --network=bridge:HA0,model=virtio 
--network=bridge:PKT0-540,model=virtio --network=bridge:PKT1-540,model=virtio  
--cputune=vcpupin0.vcpu=0,vcpupin0.cpuset=2,vcpupin1.vcpu=1,vcpupin1.cpuset=10,vcpupin2.vcpu=2,
vcpupin2.cpuset=3,vcpupin3.vcpu=3,vcpupin3.cpuset=11 --numatune=0, mode=strict  
--import --os-type=linux --os-variant=debianwheezy --arch=x86_64 --autostart --noautoconsole --vnc --virt-type kvm

b. To use SRIOV Virtual Functions (VFs) for PKT networks, follow prerequisites and steps 1 to 4 on the page Creating a New SBC SWe Instance on KVM Hypervisor - SRIOV.

9

Edit the XML definition of the VM ("virsh edit <VM name>") by adding the sysinfo element entry to XML and then save the XML.

Note

In the example below, the VM name is OAMACTIVE.


    1. Configure the emulatorpin cpuset to avoid landing the emulator threads on to the guest pinned vCPUs. Refer to the section, Using <emulatorpin> Tag on the page KVM Performance Tuning.

      1. Manually provide the comma-separated host vCPUs to utilize them for guest emulator threads.

      2. Include the following sub-element in the cputune element:
        <emulatorpin cpuset='0,8'/>

        <emulatorpin cpuset='0,8'/> is intended as an example. It is not the same for all hosts. Update according to the set up you are using.

Refer to the following example for a completed XML definition:

[root@DEVAGIRI ~]# virsh dumpxml OAMACTIVE
<domain type='kvm' id='146'>
  <name>OAMACTIVE</name>
  <uuid>e0a4588f-cde6-487c-9f8c-14d0c6ebea24</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo=http://libosinfo.org/xmlns/libvirt/domain/1.0>
      <libosinfo:os id=http://debian.org/debian/7/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit='KiB'>10485760</memory>
  <currentMemory unit='KiB'>10485760</currentMemory>
  <memoryBacking>
    <hugepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='10'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='11'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='0'/>
  </numatune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' dies='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/OAMACTIVE.qcow2' index='2'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/config_drive_oamactive.iso' index='1'/>
      <backingStore/>
      <target dev='vdb' bus='virtio'/>
      <serial>RIBBON_CONFIG_DRIVE</serial>
      <alias name='virtio-disk1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:94:52:e1'/>
      <source bridge='mgt0'/>
      <target dev='vnet537'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <interface type='bridge'>
      <mac address='52:54:00:28:b4:02'/>
      <source bridge='ha0'/>
      <target dev='vnet538'/>
      <model type='virtio'/>
      <alias name='net1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/3'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/3'>
      <source path='/dev/pts/3'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-146-OAMACTIVE/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5902' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+107:+107</label>
    <imagelabel>+107:+107</imagelabel>
  </seclabel>
</domain>
10

Start the VM by using the "virsh start" command. Log in to the VM console with "virsh console" command.

Note

Allow linuxadmin user to log in by executing enableSsh in the console. Refer to For Troubleshooting Only - How to Enable ssh Access, for details.

11

The VM automatically reboots after start. After reboot is complete, verify if the OAM/I-SBC is up and running. See the example below of the CLI output of the OAM instance running on a KVM instance.

Status example - swinfo output
[root@OAMACTIVE linuxadmin]# swinfo
===================================================
SERVER:          OAMACTIVE
OS:              V10.00.02-R002
EMA:             V10.01.03-A002
SBC:             V10.01.03-A002
SBC Type:        isbc
HA mode:         Nto1
Build Number:    16
===================================================
Installed host role:   active
Current   host role:   active
=================================================== 
[root@OAMACTIVE linuxadmin]# sbxstatus 
safplus_watchdog (pid 8229) is running...
safplus_amf (pid 8219) is running...
CE_2N_Comp_ChmProcess (pid 8865) is running...
CE_2N_Comp_FmMasterProcess (pid 9819) is running...
CE_2N_Comp_CpxAppProc (pid 9833) is running...
CE_2N_Comp_SmProcess (pid 9879) is running...
CE_2N_Comp_EnmProcessMain (pid 9923) is running...
CE_2N_Comp_PrsProcess (pid 9946) is running...
CE_2N_Comp_CcsProcess (pid 10002) is running...
CE_2N_Comp_RtmProcess (pid 10023) is running...
CE_2N_Comp_VnfrProcess (pid 10042) is running...
CE_2N_Comp_EmaProcess (pid 10119) is running...

        ** Service running [active] **
12End of procedure
  • No labels