8 More Discussions You Might Find Interesting
1. Solaris
Hi All!
I have a two x6270 solaris 10, blade, connected to a EMC x4 storage appliance via fibre.
I have little knowledge of veritasfile system, and EMC x4, storage device, but I found out that one DG is in shared mode.
I need to split the configuration, to use only one server (blade).
The EMC... (1 Reply)
Discussion started by: fretagi
1 Replies
2. AIX
I'm trying to auto-mount EMC Symmetrix BCV device at boot.
but having problem making BCV available.
I put script called mkbcv to the inittab and engineer suggested to add
120 sec sleep between cfgmgr so I did that also.
My mkbcv script seems to be working fine, it says "hdisk4 Available" ... (1 Reply)
Discussion started by: shuhei365
1 Replies
3. Red Hat
Hi ,
I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 Replies
4. Solaris
Hi guys,
I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external.
The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks.
Any hints on how to configure powerpath in order to... (4 Replies)
Discussion started by: glenioborges
4 Replies
5. UNIX for Advanced & Expert Users
We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies
6. Solaris
Dear gentelmen
kindly please update me me how can i know disks on EMC and get size for
all disks on EMC? (1 Reply)
Discussion started by: magasem
1 Replies
7. HP-UX
Hello,
I'm looking for reference sites using HP-UX and EMC symmetrix disk.
Then, May I ask you questions? (6 Replies)
Discussion started by: cooldugong
6 Replies
8. UNIX for Advanced & Expert Users
does anybody know what the bcb feature is in EMC? (5 Replies)
Discussion started by: jigarlakhani
5 Replies
LEARN ABOUT HPUX
vxdiskadd
vxdiskadd(1M) vxdiskadd(1M)
NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager
SYNOPSIS
vxdiskadd disk_address_pattern_list
DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd
prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned
replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for
the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the
disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or
allows the user to ask to make the decision for each disk individually.
One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of
this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to
specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case
of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the
specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify
all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more
examples:
all: all disks
c3 c4t2: all disks on controller 3 and controller 4, target 2
c3t4d2: a single disk (in the c#t#d# naming scheme)
xyz_0 : a single disk (in the enclosure based naming scheme)
xyz_ : all disks on the enclosure whose name is xyz
The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by
vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec-
ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0.
All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate.
Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message.
OPERATIONS
Reconnecting a drive that was temporarily inaccessible
This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the vxrecover utility.
Initialization of a disk with reserved regions
Initialization of the disk is performed by calling vxdisksetup.
Adding a disk to an existing disk group
This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so
that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free
space.
Creation of new disk groups in which to import a new disk
If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is
offered.
Hardware-Specific Note
Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM
follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the
force option. The force option ignores any such storage-specific guidelines.
FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations.
/etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations.
/etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations.
NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted
as CDS disks.
SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)