Sponsored Content
Operating Systems Solaris How to identify if disk is attached to SAN and assist in migration.? Post 303002631 by Peasant on Tuesday 29th of August 2017 11:23:59 AM
Old 08-29-2017
Identify the new luns attached to hypervisor (echo | format ).
Label the new luns and partition them per your choosing or requirements via format command.

First, you assign new luns to hypervisors virtual disk service (vds).
In your case that is primary-vds0
Code:
ldm add-vdsdev /dev/rdsk/.... <name>@primary-vds0

Check the current configuration of virtual machine :
Code:
ldm list -l <name of virtual machine, returned from ldm list, not primary>

Then, add the disk to virtual machine (ldom), where id is optional, it will choose next number available if not specified.
Code:
ldm add-vdisk [id=N] <name> <name>@primary-vds0 <name of virtual machine>

After that, login to that virtual machine via telnet from hypervisor or network, check dmesg for devices created at the time, and format output.
If you specified the ID of of new disk(s), those will be (probably) c1d<ID>s2 in the LDOM or the next available number.
Either c1, c2.. depending on the devices present during initial install.

Work is now being done inside the virtual machine, you must determine which volume manager is used (vx, zfs, ufs ?).
continue by documentation regarding that subject taking into consideration that this is a clustered environment.
Probably the disks will need to be added to other members of the cluster.

This is not a trivial task, so test it first in some test environment, if you are unsure of the outcome.

Hope that helps
Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any... (0 Replies)
Discussion started by: Hils
0 Replies

2. Solaris

SAN connection - configuring fibre attached hard drive

Hi All, I recently got a connection to the SAN through a fibre channel on my solaris box: #luxadm -e port /devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:devctl CONNECTED #ls -l /dev/cfg lrwxrwxrwx 1 root root 48 Feb 23 12:31 c4 -> ../../devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:fc I then... (2 Replies)
Discussion started by: dede
2 Replies

3. Red Hat

Identify SAN disks not in use

Hello, How can I identify SAN disks not in use by the OS? Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies

4. Solaris

Identify Boot from SAN

How to identify the server is BOOT FROM SAN. Also how one can find from which device it is booted? Thanks Rahul Double post, continued here (0 Replies)
Discussion started by: rahul.kurumkar
0 Replies

5. Red Hat

Identify Boot from SAN

Hi, I have many servers all of these are boot from SAN. Can anybody let me know that how to identify the server is Boot fron SAN and from which device? Thanks Rahul (1 Reply)
Discussion started by: rahul.kurumkar
1 Replies

6. HP-UX

SAN Migration of HP-UX hosts

Hello gurus, I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place. Environment: Migrating from CX4 to VMAX - using OR/Hot Pull. Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies

7. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

8. HP-UX

SAN Migration question

Hi, I am very new to HP-UX, and we're going to be doing a SAN migration. We're going to take down the machine, and zone it to the new SAN. My question is, will the device names change and will that interfere with the LVM? If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

10. Linux

Identify newly attached LUN from NetApp

Hi I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o GNU/Linux I have first run the df -h and got the following: df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_outsystemdb-lv_root 50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
DEVICE(9)						   BSD Kernel Developer's Manual						 DEVICE(9)

NAME
device -- an abstract representation of a device SYNOPSIS
typedef struct device *device_t; DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into, disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and other devices will be added as children of their relevant bus. The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and device_delete_child(9)). A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe- cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)). Devices can be in one of several states: DS_NOTPRESENT the device has not been probed for existence or the probe failed DS_ALIVE the device probe succeeded but not yet attached DS_ATTACHED the device has been successfully attached DS_BUSY the device is currently open The current state of the device can be determined by calling device_get_state(9). SEE ALSO
devclass(9), driver(9) AUTHORS
This manual page was written by Doug Rabson. BSD
June 16, 1998 BSD
All times are GMT -4. The time now is 06:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy