Professional Documents
Culture Documents
The following example would assign one cryptographic resource to the control domain, primary. This leaves the
remainder of the cryptographic resources available to a guest domain.
# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 16 32GB 20% 20% 2d 23h 21m
Note: Our system have two PIC card one is pci_0 and one is pci_1. pci_0 we will use for control domain
and pci_1 we will use for Secondary domain.
Install and configure your root filesystem for your primary domain on the controllers based on PCI_0.
This leaves you PCI_1 to map to the second or secondary IO domain
Now that we have a freshly booted IO domain named secondary, we can add the disk service and the
network switch device and service
We We now add the PCI_1 bus to the secondary domain, which is the new additional IO domain.
We now add the boot ISO image so we can boot and install the LDOM we created, again its called
secondary.
# ldm add-vdsdev /root/sol-10-u10-ga2-sparc-dvd.iso iso@primary-vds0
# ldm add-vdisk vdisk_iso iso@pri-root-vds secondary
# ldm add-spconfig secondary-new1
Lets see what our hardware buses look like now. The PCI_0 and PCI_1 buses should be splint in half.
Here is a long and brief listing of the io subsystem of the T4-4 system.
# ldm list-io -l
# ldm bind-domain secondary
# ldm start-domain secondary
From the control domain, you need to create the second virtual switch for the secondary or second IO
domain first NIC net0 which was carved off and mapped to the PCI_1 bus. That was the NIC we moved
over to the IO domain when we split the PCI buses. From the control and service domain (primary), we
have to create secondary vsw that uses the first logical NIC from the secondary (second IO domain).
Here we create a new switch.
Creating guest domain ldom using both service and io domains for storage and network services
Export the virtual disk back end from the primary service domain.
Note - two different domains (primary and secondary) using the same virtual disk (emcpower105c) back end.
Note - Although the virtual disk back end is exported several times through different service domains, you assign only
one virtual disk to the guest domain and associate it with the virtual disk back end through any of the service domains.
Remove a virtual disk from a guest domain by using the following command.
# ldm rm-vdisk disk_name ldom
Stop exporting the corresponding backend from the service domain by using the following command.
# ldm rm-vdsdev volume_name@service_name
Assign the network service from the switches being hosted from both domains
Public Network
# ldm add-vnet linkprop=phys-state net0 pri-public-vsw node1
# ldm add-vnet linkprop=phys-state net1 sec-public-vsw node1
Backup Network
# ldm add-vnet linkprop=phys-state net2 pri-backup-vsw node1
# ldm add-vnet linkprop=phys-state net3 sec-backup-vsw node1
Note - The virtual switch must have a physical network device assigned for the domain to successfully
bind. If the domain is already bound and the virtual switch does not have a physical network device
assigned, the ldm add-vnet commands will fail.
# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 16 32G 20% 20% 2d 23h 21m
secondary active -n--v- 5000 8 16G 0.0% 0.0% 3d 19h 29m
node1 active -t---- 5001 8 8G 2.7% 2.7% 1s