![when to change motherboard when to change motherboard](https://i5.walmartimages.com/asr/3c99121a-5cec-4c51-b48b-5293d19c6b52_1.98c3ef3c95851c8398c7753df72b3ba4.jpeg)
Stop the SF VM with the use of its VM Name. esc_nc_cli get esc_datamodel | egrep -color "|||" Log in to the ESC node that corresponds to the VNF and check the status of the SF VM: ~]$ cd esc-cli]$. If the card is in the active state, move the card to standby state: VNF2# card migrate from 8 to 10 UUID/Serial Number : 49AC5F22-469E-4B84-BADC-031083DB0533Ĭheck the status of the card: VNF2# show card tableġ: CFC Control Function Virtual Card Active NoĢ: CFC Control Function Virtual Card Standby -ģ: FC 4-Port Service Function Virtual Card Active NoĤ: FC 4-Port Service Function Virtual Card Active Noĥ: FC 4-Port Service Function Virtual Card Active NoĦ: FC 4-Port Service Function Virtual Card Active Noħ: FC 4-Port Service Function Virtual Card Active NoĨ: FC 4-Port Service Function Virtual Card Active Noĩ: FC 4-Port Service Function Virtual Card Active Noġ0: FC 4-Port Service Function Virtual Card Standby. Use the UUID of the SF VM identified from the section Identify the VMs hosted in the Compute Node, and identify the card that corresponds to the UUID: VNF2# show card hardwareĬard Type : 4-Port Service Function Virtual CardĬPU Packages : 26 Log in to the StarOS VNF and identify the card that corresponds to the SF VM. The parameters from this output will be used in the subsequent sections. Note: In the output shown here, the first column corresponds to the UUID, the second column is the VM name and the third column is the hostname where the VM is present.
![when to change motherboard when to change motherboard](https://i.ebayimg.com/images/g/i-8AAOSwLstfmFwB/s-l300.jpg)
The Compute Server contains CF/ESC/EM/UAS combination of VMs: ~]$ nova list -field name,host | grep compute-8 The Compute Server contains only SF VM: ~]$ nova list -field name,host | grep compute-10 Identify the VMs that are hosted on the Compute Server. Identify the VMs Hosted in the Compute Node Once the Motherboard has been replaced, the VMs are restored back. Motherboard Replacement in Compute Nodeīefore the activity, the VMs hosted in the Compute node are gracefully shutoff.
![when to change motherboard when to change motherboard](https://i.ytimg.com/vi/nOu7k9wDwoo/maxresdefault.jpg)
Once the server is powered On after the replacement activity, it would enrol itself back to the overcloud stack. Hence, there is no requirement to add the node back to overcloud. Note: The boot disks with the OpenStack installation are replaced after the replacement of the motherboard takes place. In an Ultra-M setup, there can be scenarios where a motherboard replacement is required in these server types: Compute, OSD-Compute and Controller. Highlevel Workflow of the Replacement Procedure Motherboard Replacement in Ultra-M Setup Note: Ultra M 5.1.x release is considered in order to define the procedures in this document. This document is intended for Cisco personnel who are familiar with Cisco Ultra-M platform and it details the steps that are required to be carried out at OpenStack and StarOS VNF level at the time of the Motherboard Replacement in a server. The high-level architecture of Ultra-M and the components involved are depicted in this image: