08-28-2017
This is a vmhost and the host has veritas cluster on it. I need to understand how can I migrate it to the new storage.
HTML Code:
root@vmhost> ldm list-services |more
VCC
NAME LDOM PORT-RANGE
primary-vcc0 primary 5000-5031
VSW
NAME LDOM MAC NET-DEV DEVICE DEFAULT-VLAN-ID PVID VID MODE
vlan090-vsw0 primary 00:14:4f:fa:97:6e e1000g3 switch@2 1 1
vlan090-vsw1 primary 00:14:4f:fb:e3:e8 nxge3 switch@3 1 1
private-vsw0 primary 00:14:4f:fa:b2:4d e1000g2 switch@4 1 1
private-vsw1 primary 00:14:4f:fa:b8:8e nxge2 switch@5 1 1
vlan050-vsw0 primary 00:14:4f:fa:23:5e e1000g0 switch@0 1 1
vlan050-vsw1 primary 00:14:4f:f9:a8:ac nxge0 switch@1 1 1
VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 primary lb001-server1 /dev/rdsk/c3t60060480000290101499533031303738d0s
2
la050-jetstart /dev/rdsk/c3t60060480000290101499533031303030d0s2
la051-jetstart /dev/rdsk/c3t60060480000290101499533031303035d0s2
la052-jetstart /dev/rdsk/c3t60060480000290101499533031303041d0s2
la061-slavedns /dev/rdsk/c3t60060480000290101499533031333135d0s2
la056-masterdns /dev/rdsk/c3t60060480000290101499533031333044d0s2
la078-sunadmin /dev/rdsk/c3t60060480000290101499533031333435d0s2
la064-sunadmin /dev/rdsk/c3t60060480000290101499533031333141d0s2
10 More Discussions You Might Find Interesting
1. HP-UX
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT PHP
volrmmount
volrmmount(1) User Commands volrmmount(1)
NAME
volrmmount - call rmmount to mount or unmount media
SYNOPSIS
volrmmount [-i | -e] [name | nickname]
volrmmount [-d]
DESCRIPTION
The volrmmount utility calls rmmount(1M) to, in effect, simulate an insertion (-i) or an ejection (-e). Simulating an insertion often
means that rmmount will mount the media. Conversely, simulating an ejection often means that rmmount will unmount the media. However,
these actions can vary depending on the rmmount configuration and media type (see rmmount.conf(4)).
For example, if you use the default /etc/rmmount.conf and insert a music CD, it will not be mounted. However, you can configure rmmount so
that it calls workman whenever a music CD is inserted.
This command allows you to override Volume Management's usual handling of media (see EXAMPLES below).
OPTIONS
The following options are supported:
-i Simulates an insertion of the specified media by calling rmmount.
-e Simulates an ejection of the specified media by calling rmmount.
-d Displays the name of the default device for volrmmount to handle. This device is used if no name or nickname is supplied.
OPERANDS
The following operands are supported:
name The name that Volume Management recognizes as the device's name. See volfs(7FS).
nickname A shortened version of the device's name. Following is the list of recognized nicknames:
+-----------------------------+-----------------------------+
| Nickname | Path |
+-----------------------------+-----------------------------+
|fd |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd0 |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|diskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|diskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|diskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|rdiskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|rdiskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|rdiskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|floppy |/dev/rdiskette |
+-----------------------------+-----------------------------+
|floppy0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|floppy1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|cdrom0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|zip0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|jaz0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|rmdisk0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
EXAMPLES
Example 1: Using the volrmmount command
When Volume Management finds a floppy that contains a filesystem, it calls rmmount to mount it. If you wish to run tar(1) or cpio(1) on
that floppy, it must first be unmounted. To unmount the floppy use:
example% volrmmount -e floppy0
After volrmmount unmounts the floppy, if you wish to re-mount it (rather than ejecting it and reinserting it) use:
example% volrmmount -i floppy0
Notice that if you are using a named floppy, you can use its name in place of floppy0.
FILES
/dev/volctl Volume Management control port
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWvolu |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), eject(1), tar(1), rmmount(1M), vold(1M), rmmount.conf(4), attributes(5), volfs(7FS)
NOTES
Volume Management (vold) must be running to use this command.
SunOS 5.10 30 Aug 2000 volrmmount(1)