Goal

Solution

• Backup of the ldom environment before hardware replacement.

• Identify the ldom names using the ldm list-domain command

Example:

• Capture the LDOM environment

• Log in as an authorized user or superuser

• Use each of the following methods to ensure the required information is captured

• Run the command ldm ls -e -p

• Run the command ldm list-constraints -x ldom > ldom.xml for each of the ldom names identified earlier

• If this is not available then the system configuration can be obtained from the file /var/opt/SUNWldm/ldom-db.xml

*See the Appendix to this document for examples of the outputs from these commands. These examples are used in this procedure.

• Shutdown all the domains and power off the system

• Replace the motherboard or SC following the procedures shown in the appropriate service guide. See http://download.oracle.com/docs/cd/E19608-01/821-1485/index.html .
  

• Boot the operating system.

The system will display an errors similar to the following:

Oct 14 12:15:18 svc.startd[7]: svc:/network/physical:default: Method "/lib/svc/method/net-physical" failed with exit status 96.
Oct 14 12:15:18 svc.startd[7]: network/physical:default misconfigured: transitioned to maintenance (see 'svcs -xv' for details)
Oct 14 12:15:34 svc.startd[7]: svc:/ldoms/vntsd:default: Method "/lib/svc/method/svc-vntsd" failed with exit status 1.
Oct 14 12:15:34 svc.startd[7]: svc:/ldoms/vntsd:default: Method "/lib/svc/method/svc-vntsd" failed with exit status 1.
Oct 14 12:15:35 svc.startd[7]: svc:/ldoms/vntsd:default: Method "/lib/svc/method/svc-vntsd" failed with exit status 1.
Oct 14 12:15:35 svc.startd[7]: ldoms/vntsd:default failed: transitioned to maintenance (see 'svcs -xv' for details)

It will still be possible to login to the system, however there will be no network access.

• Login to the system as root

• Move the virtual network interface from /etc/hostname.vsw0 to the physical network interface.
  In this example the physical interface is e1000g0

# mv /etc/hostname.vsw0 /etc/hostname.e1000g0

• Configure the physical network interface

# ifconfig e1000g0 plumb

# ifconfig e1000g0 ip_of_e1000g0 netmask netmask_of_e1000g0 broadcast + up

• Reboot the system and then login again.

In some instances the previous svc-vntsd failure messages may still be displayed. However, it will still be possible to login.

• Manually re-create the Primary Domain.

The following examples of the commands use the parameters from the example files in the Appendix.
Substitute the true values from the saved files.

• Recreate the Virtual Disk Server (vds)

<ldom>
<ldom_name>primary</ldom_name>
-
-
-
<vds>
<vds_instance>
<service_name>primary-vds0</service_name>
<vds_volumes>
<vds_volume>

# ldm add-vds primary-vds0 primary

• Re-create the Virtual Console Concentrator service (vcc)
  

 

<vcc>
<vcc_instance>
<service_name>primary-vcc0</service_name>
<min_port>5000</min_port>
<max_port>5100</max_port>
</vcc_instance>
</vcc>

# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

• Re-create the cryptographic resource

<mau>
<number>1</number>
</mau>

# ldm set-mau 1 primary

• Re-create the Virtual CPUs

<cpu>
<number>8</number>
</cpu>

# ldm set-vcpu 8 primary

• Re-create the memory

<memory>
<size>4294967296</size>
</memory>

# ldm set-memory 4G primary

• Save the configuration to the service controller

# ldm add-config initial

• List the saved configs

# ldm list-config

factory-default [current]
initial [next]

• Perform a re-configuration boot of the system

# touch /reconfigure
# shutdown -y -g0 -i6

• Power off and then power on the platform and allow the system to boot

• Restore the virtual network

Please remember the following are examples , your system may be using different names and values.

# ifconfig -a
# ifconfig vsw0 plumb
# ifconfig e1000g0 down unplumb
# ifconfig vsw0 ip_of_e1000g0 netmask netamsk_of_e1000g0 broadcast + up
# mv /etc/hostname.e1000g0 /etc/hostname.vsw0

• Check the virtual network terminal server daemon is enabled.

# svcs -l vntsd

fmri svc:/ldoms/vntsd:default
name virtual network terminal server
enabled true
state online
next_state none
state_time Wed Oct 15 16:03:54 2008
logfile /var/svc/log/ldoms-vntsd:default.log
restarter svc:/system/svc/restarter:default
contract_id 57
dependency optional_all/error svc:/milestone/network (online)
dependency optional_all/none svc:/system/system-log (online)

If this is not enabled use the following command

# svcadm enable vntsd

• Restore the virtual disk server to the guest domains

Please remember the following are examples. Your system may be using different values and names.

<vds>
<vds_instance>
<service_name>primary-vds0</service_name>
<vds_volumes>
<vds_volume>
<block_dev>/dev/dsk/c1t1d0s2</block_dev>
<vol_name>vol1</vol_name>
<vol_opts/>
</vds_volume>
</vds_volumes>
</vds_instance>
</vds>

# ldm add-vdsdev /dev/dsk/c1t1d0s2 vol1@primary-vds0

• Finally Bind and Start the remaining domains.

In this example the guest domain is named guest1.

# ldm bind-domain guest1
# ldm start-domain guest1

 

Appendix:

Output from command ldm ls -e -p

Output from ldm list-constraints command for control/primary domain

ldm list-constraints -x ldom

<?xml version="1.0"?>
<LDM_interface version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="./schemas/combined-v3.xsd" xmlns:ovf="./schemas/envelope" xmlns:rasd="./schemas/CIM_ResourceAllocationSettingData" xmlns:vssd="./schemas/CIM_VirtualSystemSettingData" xmlns:gprop="./schemas/GenericProperty" xmlns:bind="./schemas/Binding">
<data version="3.0">
<Envelope>
<References/>
<Content xsi:type="ovf:VirtualSystem_Type" ovf:id="primary">
<Section xsi:type="ovf:ResourceAllocationSection_Type">
<Item>
<rasd:OtherResourceType>ldom_info</rasd:OtherResourceType>
<rasd:Address>00:14:4f:ab:e3:16</rasd:Address>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>cpu</rasd:OtherResourceType>
<rasd:AllocationUnits>8</rasd:AllocationUnits>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>mau</rasd:OtherResourceType>
<rasd:AllocationUnits>1</rasd:AllocationUnits>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>memory</rasd:OtherResourceType>
<rasd:AllocationUnits>4G</rasd:AllocationUnits>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>physio_device</rasd:OtherResourceType>
<gprop:GenericProperty key="name">pci@0</gprop:GenericProperty>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>physio_device</rasd:OtherResourceType>
<gprop:GenericProperty key="name">niu@80</gprop:GenericProperty>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>vsw</rasd:OtherResourceType>
<rasd:Address>auto-allocated</rasd:Address>
<gprop:GenericProperty key="service_name">primary-vsw0</gprop:GenericProperty>
<gprop:GenericProperty key="dev_path">e1000g0</gprop:GenericProperty>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>vcc</rasd:OtherResourceType>
<gprop:GenericProperty key="service_name">primary-vcc0</gprop:GenericProperty>
<gprop:GenericProperty key="min_port">5000</gprop:GenericProperty>
<gprop:GenericProperty key="max_port">5100</gprop:GenericProperty>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>vds</rasd:OtherResourceType>
<gprop:GenericProperty key="service_name">primary-vds0</gprop:GenericProperty>
</Item>
</Section>
<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Item>
<rasd:OtherResourceType>vds_volume</rasd:OtherResourceType>
<gprop:GenericProperty key="vol_name">vol1</gprop:GenericProperty>
<gprop:GenericProperty key="block_dev">/dev/dsk/c1t1d0s2</gprop:GenericProperty>
<gprop:GenericProperty key="service_name">primary-vds0</gprop:GenericProperty>
</Item>
</Section>
</Content>
</Envelope>
</data>
</LDM_interface>

Output from the file /var/opt/SUNWldm/ldom-db.xml

<?xml version="1.0"?>
<ldom_database version="3.0">
<ldom>
<ldom_name>primary</ldom_name>
<cpu>
<number>8</number>
</cpu>
<mau>
<number>1</number>
</mau>
<memory>
<size>4294967296</size>
</memory>
<io>
<io_instance>
<iodevice>pci@0</iodevice>
<bypass_mode>0</bypass_mode>
</io_instance>
<io_instance>
<iodevice>niu@80</iodevice>
<bypass_mode>0</bypass_mode>
</io_instance>
</io>
<mac_address>0x00144fabe316</mac_address>
<vsw>
<vsw_instance>
<service_name>primary-vsw0</service_name>
<mac_address>0x00144ffb6ff9</mac_address>
<dev_path>e1000g0</dev_path>
<mode/>
</vsw_instance>
</vsw>
<network/>
<vds>
<vds_instance>
<service_name>primary-vds0</service_name>
<vds_volumes>
<vds_volume>
<block_dev>/dev/dsk/c1t1d0s2</block_dev>
<vol_name>vol1</vol_name>
<vol_opts/>
</vds_volume>
</vds_volumes>
</vds_instance>
</vds>
<disk/>
<vcc>
<vcc_instance>
<service_name>primary-vcc0</service_name>
<min_port>5000</min_port>
<max_port>5100</max_port>
</vcc_instance>
</vcc>
<console/>
<vdpcs/>
<vdpcc/>
<variables/>
<options/>
</ldom>
<ldom>
<ldom_name>guest1</ldom_name>
<cpu>
<number>8</number>
</cpu>
<mau><number>0</number>
</mau>
<memory>
<size>4294967296</size>
</memory>
<io/>
<mac_address>0x00144ffab8f0</mac_address>
<vsw/>
<network>
<network_instance>
<vnet_name>vnet1</vnet_name>
<service_name>primary-vsw0</service_name>
<mac_address>0x00144ff9159e</mac_address>
<mtu>1500</mtu>
</network_instance>
</network>
<vds/>
<disk>
<disk_instance>
<vdisk_name>vdisk1</vdisk_name>
<service_name>primary-vds0</service_name>
<vol_name>vol1</vol_name>
<timeout>-1</timeout>
</disk_instance>
</disk>
<vcc/>
<console>
<console_instance>
<service_name>primary-vcc0</service_name>
<group>guest1</group>
<port>5000</port>
</console_instance>
</console>
<vdpcs/>
<vdpcc/>
<variables>
<var>
<name>auto-boot?</name>
<value>true</value>
</var>
<var>
<name>boot-device</name>
<value>vdisk1</value>
</var>
<var>
<name>keyboard-layout</name>
<value>US-English</value>
</var>
</variables>
<options/>
</ldom>
</ldom_database>

This solution has no attachment