Sponsored Content
Operating Systems Solaris How can I install Solaris 10 on an LDom using an iso? Post 302816403 by bstring on Monday 3rd of June 2013 10:07:03 PM
Old 06-03-2013
How can I install Solaris 10 on an LDom using an iso?

Hello,

I am trying to install Solaris 10 on a newly created LDom. Here are the commands I ran to create the LDom:
Code:
ldm add-domain ldg2
ldm add-vcpu 8 ldg2
ldm add-memory 2g ldg2
ldm add-vnet vnet2 primary-vsw0 ldg2
ldm add-vdsdev /dev/dsk/c0t5000CCA01535E20Cd0s0 vol2@primary-vds0 
ldm add-vdisk vdisk2 vol2@primary-vds0 ldg2
ldm set-var auto-boot\?=true ldg2
ldm set-var boot-device=vdisk2 ldg2
ldm add-vdisk vdisk_iso iso_vol@primary-vds0 ldg2

Here is my binding info:
Code:
VDS
    NAME             VOLUME         OPTIONS          MPGROUP        DEVICE
    primary-vds0     iso_vol                                        /data/iso/sol-10-u11-ga-sparc-dvd.iso
                     vol2                                           /dev/dsk/c0t5000CCA01535E20Cd0s0

DISK
    NAME             VOLUME                      TOUT ID   DEVICE  SERVER         MPGROUP
    vdisk2           vol2@primary-vds0                0    disk@0  primary      
    vdisk_iso        iso_vol@primary-vds0             1    disk@1  primary

When I start the LDom and run devalias, this is the output:
Code:
{0} ok devalias
vdisk_iso                /virtual-devices@100/channel-devices@200/disk@1
vdisk2                   /virtual-devices@100/channel-devices@200/disk@0
vnet2                    /virtual-devices@100/channel-devices@200/network@0
net                      /virtual-devices@100/channel-devices@200/network@0
disk                     /virtual-devices@100/channel-devices@200/disk@0
virtual-console          /virtual-devices/console@1
name                     aliases

I ran the command boot vdisk_iso:f to launch the installation process, and I am running into a problem when it asks me to "Choose Media." I am not sure if I am supposed to choose CD/DVD or Network File System, because both of them seem incorrect. If I choose CD/DVD, I get this error:
Code:
ERROR: The disc you inserted is not a Solaris OS CD/DVD.

And when I select Network File System, it asks me to supply a path to the ISO. I tried entering localhost:/virtual-devices@100/channel-devices@200/disk@1 and localhost:/vdisk_iso but I get
Code:
 ERROR: Unable to mount image

I used this same ISO file a while back to create an LDom on this same system, so I believe the ISO file is not the problem. I don't remember having to enter any media information the last time I installed Solaris on an LDom but I am not positive.

Any help would be appreciated.
 

9 More Discussions You Might Find Interesting

1. AIX

How do I install bos.loc.iso.en_GB?

Hi, I need to install the package bos.loc.iso.en_GB on an AIX 5.3 server but try as I might I cannot find the file which contains this package. I have all the AIX 5.3 CDs and also the majority of the packages installed locally on the server. If I create a .toc file from the local packages I... (3 Replies)
Discussion started by: m223464
3 Replies

2. Solaris

Fresh install of solaris 10 using an ISO

Hi all Im rebuilding an 6800 domain with solaris 10. Server is located in a different town and cant be bothered to drive down and install a dvd into its drive. So, apart from jumpstarting it and using a local DVD, is there a way I can an ISO image to build a new client ?? eg. mount an ISO... (2 Replies)
Discussion started by: sbk1972
2 Replies

3. Solaris

Install Solaris 10 by using the ISO file

Hi Gurus Recently i had download the ISO installer (sol-10-u8-ga-sparc-dvd.iso) for Solaris 10. And i ftp to a Server. May i know is it possible to install the Solaris by using this ISO file directly (not using network)? (8 Replies)
Discussion started by: SmartAntz
8 Replies

4. Solaris

Installing Solaris into LDom using DVD

Hi, I have issues installing Solaris into a LDom using a Solaris10u5/08 DVD. I have been troubleshooting for the past 2 days and I still cannot get it up. Here is the logs: root@eld-app2# ldm add-vdsdev /cdrom/sol_10_508_sparc/s0 cdrom0@primary-vds0 root@eld-app2# ldm add-vdisk cdrom0... (4 Replies)
Discussion started by: bolasutra
4 Replies

5. Solaris

ZFS LDOM problem on Solaris 10

Apologies if this is the wrong forum.. I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies

6. SCO

Sco 5.0.6 Install ISO needed

Trying to restore a 5.0.6 server to a new server but the owner doesnt have their install media. Saw that many people have this. Please let me know of anyone that has a download link. Much appreciation! (1 Reply)
Discussion started by: gavinseabrook
1 Replies

7. Solaris

Virtual Switch in Solaris LDOM

Hi, Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image. Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch. So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies

8. Solaris

Make .iso mountable in LDOM

used mkisofs -lJR -o output_image.iso directory_name to create an iso on the primary domain of a server. mounted it locally in the primary using lofiadm -a /path/to/cd.iso mount -o ro -F hsfs /dev/lofi/1 /mnt verified that I could read the disk correctly. then created a vdsdev using... (2 Replies)
Discussion started by: os2mac
2 Replies

9. Solaris

Solaris LDOM IP conflict

I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
scconf_dg_rawdisk(1M)					  System Administration Commands				     scconf_dg_rawdisk(1M)

NAME
scconf_dg_rawdisk - add, change or update raw-disk device group configuration SYNOPSIS
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true] scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true | false] scconf -c -D name=diskgroup,autogen=true scconf -r -D device_service_name [,nodelist=node[:node]...] [,globaldev=gdev1,...] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_rawdisk utility adds, changes or updates raw-disk device group configuration A raw disk is a disk that is not being used as part of a volume manager volume or metadevice. Raw-disk device groups allow you to define a set of disks within a disk device group. At system boot, by default, a raw-disk device group is created for every Disk ID pseudo driver (DID) device in the configuration. By con- vention, the raw-disk device group names are assigned at initialization and are derived from the DID names. For every node added to a raw- disk disk device group, the scconf utility verifies that every device in the group is physically ported to the node. The scconf -a (add) command can be used to create a raw-disk device group with multiple disk devices configured in it. A raw-disk device group is created for every disk device in the cluster at boot time. Before you can add a new raw-disk device group, devices to be used in the new group must be removed from the device group created at boot time. Then a new raw-disk device group can be created containing these devices. This is accomplished by creating a list of these devices in the globaldev option of scconf along with a potential primary node preference list in the nodelist option. If the device group already exists, only new nodes and global devices will be added and nodes or devices which are part of an existing device group will be ignored. If the preferenced suboption is not given with the-a option to create a new device group, then it is, by default, false. However, if the preferenced suboption is specified for the existing device group with a value of true or false, an error is returned. This is done in order to maintain the existing nodelist preference state. If a device group should be mastered by only a particular node then it should be configured with the otheroption set to localonly=true. Only one node can be specified in the node list to create a localonly device group. The scconf -c (change) command is used to change the order of the potential primary node preference, to enable or disable failback, to set the desired number of secondaries, and to add more global devices to the device group. If you want to change the order of node preference list, then all the nodes currently existing in the device group must be specified in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If the preferenced suboption is not specified with the change, the already established true or false setting is used. New nodes cannot be added using the change form of the command. Change option can also be used for changing a device group to localonly device group and vice-versa. To change a device group to a localonly device group, set otheroption to localonly=true. Specify localonly=false to set it back to not the localonly device group. nodelist must already be set to a list of one node, or an error results. It is legal to specify a nodelist with the change form of the command, when you set localonly to true. This is, however, redundant, since the list can only contain the single node that is already configured. It would be an error to specify any other than the node that is already configured. The scconf -r (remove) command can be used to remove the nodes, global devices, and the device group name from the cluster device-group configuration. If nodes or global devices are specified with the device-group name, they are removed from the device group first. After the last device and node are removed from the device group, the device group is also removed from cluster configuration. If only the name of the device group is given (no nodes or devices at all), the entire device group is removed. If a raw-disk device name is registered in a raw-disk device group, then it cannot be registered in a Solaris Volume Manager device group or a VERITAS Volume Manager device group. OPTIONS
See the scconf(1M) man page for the list of supported generic options. The following action options are used to describe the actions performed by the command. Only one action option is allowed in the command. The following action options are supported: -a Add a new raw-disk device group to the cluster configuration. You can also use this option to change the device group configuration. -c Change the ordering of the node preference list, change preference and failback policy, change the desired number of secondaries, and also add more devices to the device group with the globaldev option. It is also used to set a device group as local only. -r Remove the raw-disk device group name from the cluster. The autogen flag is an indicator of the scconf command. This command does not list devices with the autogen property unless the -v command line option is used. When a device is used with the change form of the scconf command, the device's autogen property is reset, or set to false, unless autogen=true is also specified. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a raw-disk device group, change the order of the potential primary nodes, change preference and fail- back policy, change the desired number of secondaries, and remove the raw-disk device group from the cluster configuration. host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1:host2:host3,preferenced=false,failback=enabled, numsecondaries=,globaldev=d1,globaldev=d2 host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1,globaldev=d1,globaldev=d2,localonly=true, globaldev=d1,globaldev=d2 host1# scconf -c -D name=rawdisk_groupname, nodelist=host3:host2:host1,preferenced=true,failback=disabled, numsecondaries=2,globaldev=d4,globaldev=d5 host1# scconf -c -D name=rawdisk_groupname,localonly=true host1# scconf -r -D name=rawdisk_groupname host1# scconf -r -D name=rawdisk_groupname,nodelist=host1,host2 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 13 Aug 2007 scconf_dg_rawdisk(1M)
All times are GMT -4. The time now is 09:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy