Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Can Veritas DMP & EMC PowerPath coexist? Post 302076862 by pressy on Friday 16th of June 2006 07:27:21 AM
Old 06-16-2006
it could, but makes no sense. if you are using PowerPath the multi-ways to the storage are hidden and converted to one virtual path, before DMP is loaded. (same with VxDMP and MPxIO). You will see the result with " vxdmpadm listctlr all"

regards pressy
 

10 More Discussions You Might Find Interesting

1. Solaris

Need some E-Labs for solaris 10 & veritas volume manager

Hello friends, I need to test some of the solaris 10 concepts and veritas volume manager.i want to know ,where i get the testing labs or E-labs(online) for this practice.i ready to pay for this labs.pls kindly help me to get the details or website names...Thanks in Advance -Jay (6 Replies)
Discussion started by: rjay.com
6 Replies

2. AIX

AIX 5.3 & Veritas Backup with Tape Library

hello, I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup: Veritas Software is not able to communicate properly with our tape library When we tried to run these commands here's the output # cfgmgr -l fscsi0 # cfgmgr -l fscsi2 # cfgmgr -l fscsi1 cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies

3. Red Hat

Configure EMC Powerpath?

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

Configure Veritas DMP

I am looking forward to configure Veritas DMP on Solaris-10. All pointers appreciated. Thanks, (3 Replies)
Discussion started by: menonk
3 Replies

5. Solaris

Solaris 10 with Veritas and PowerPath

Hello, I have an issue with veritas volume manager version 5.0 in combination with EMC powerpath version 5.2.0 running on Solaris10(Sparc). This server is fiber connected to a EMC Clariion CX3-40 SAN. This is the situation : Server is a SUN Enterprise M5000 OS = Solaris10 Sparc Veritas... (1 Reply)
Discussion started by: chipke2005
1 Replies

6. UNIX for Advanced & Expert Users

Veritas VxVM & Vxfs to SVM and UFS

Hi, I have 2 hosts with Veritas VxVM and VxFS (5.0 MP3_RP2). I need to use the application filesystem's luns from these 2 hosts and mount it on another 2 hosts that are running Solaris 9 09/05 and SVM. Is there resources online or has someone tried this? (0 Replies)
Discussion started by: xor
0 Replies

7. Solaris

Veritas VxVM & Vxfs to SVM and UFS

Hi, I have 2 hosts with Veritas VxVM and VxFS (5.0 MP3_RP2). I need to use the application filesystem's luns from these 2 hosts and mount it on another 2 hosts that are running Solaris 9 09/05 and SVM. Is there resources online or has someone tried this? (4 Replies)
Discussion started by: xor
4 Replies

8. Linux

EMC, PowerPath and issue on using LUN

Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3. I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process: echo "1" > /sys/class/fc_host/host<n>/issue_lip and echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies

9. Solaris

One emc powerpath failed

It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies

10. Solaris

Emc powerpath device & zfs query

Hi, We're trying out a SAN migration from HP EVA to EMC VMAX, and run into a bit of an issue with powerpath and zfs. The method we're currently using to migrate is to export the HP EVA luns from our sun server, replicate using SAN based method, and then present the new luns to our Sun server... (7 Replies)
Discussion started by: badoshi
7 Replies
vxddladm(1M)															      vxddladm(1M)

NAME
vxddladm - Device Discovery Layer subsystem administration SYNOPSIS
/etc/vx/bin/vxddladm keyword [attribute[=value] ...] vxddladm [-a | -f | -n] addforeign {dir=pathname | path=pathname} vxddladm [-a | -f | -n] addforeign {dirname=pathname | pathname=pathname} vxddladm [-a | -f | -n] addforeign blockdir=pathname chardir=pathname vxddladm [-a | -f | -n] addforeign blockpath=pathname charpath=pathname vxddladm addjbod vid=vendor-id [pid=product-id] [opcode=scsi_opcode] [pagecode=page_code] [offset=page_offset] [length=sno_length] [policy={aa|ap}] vxddladm disablescsi3 vxddladm enablescsi3 [policy={aa|ap}] vxddladm excludearray libname=libname vxddladm excludearray vid=vendor-id pid=product-id vxddladm excludearray vid=vendor-id vxddladm excludearray pid=product-id vxddladm excludearray all vxddladm get namingscheme vxddladm gettune {all | tunable} vxddladm includearray libname=libname vxddladm includearray vid=vendor-id pid=product-id vxddladm includearray vid=vendor-id vxddladm includearray pid=product-id vxddladm includearray all vxddladm listexclude [all] vxddladm listforeign vxddladm listjbod [vid=vendor-id [pid=product-id]] vxddladm listsupport [all | libname=libname] vxddladm listversion [all | libname=libname] vxddladm modescsi3 vxddladm rmforeign {dir=pathname | path=pathname} vxddladm rmforeign {dirname=pathname | pathname=pathname} vxddladm rmforeign blockdir=pathname chardir=pathname vxddladm rmforeign blockpath=pathname charpath=pathname vxddladm rmjbod vid=vendor-id [pid=product-id] vxddladm set namingscheme={ebn|osn} [persistence={yes|no}] [mode={default|legacy|new}] vxddladm settune tunable=value vxddladm start eventsource vxddladm stop eventsource DESCRIPTION
The vxddladm utility is an administrative interface to the dynamic array support facility of the Device Discovery Layer (DDL). This util- ity lists the types of arrays supported, adds or removes array support from DDL, and allows dynamic addition of JBOD support for disks from different vendors. It additionally lists supported JBODs, and allows addition or removal of JBOD support. The vxddladm utility is also used to customize the set of array libraries that can participate in device discovery. DDL cannot discover some devices that are controlled by third-party drivers (for example, EMC PowerPath and RAM disks). Additionally, it may be preferable to use the multipathing capability that is provided by the third-party drivers for some arrays rather than use the Veri- tas Dynamic Multipathing (DMP) feature. Such foreign devices can be made available as simple disks to VxVM by using the vxddladm addfor- eign command. This command also has the effect of bypassing DMP for the specified devices. If a foreign device has alias devices in the OS-maintained device tree, DDL/DMP creates additional disk access records that point to the same physical device. As such additional records are usually not required, you can specify the -a option to prevent them from being cre- ated. After adding or removing foreign device entries, use either the vxdisk scandisks command or the vxdctl enable command to discover the for- eign devices as simple disks. These disks then behave in the same way as autoconfigured disks. KEYWORDS
addforeign Adds an entry to the list of foreign devices that are not autoconfigurable by VxVM. See the ATTRIBUTES section for a description of the attributes that can be used with addforeign: blockdir, blockpath, chardir, charpath, dir, dirname, path and pathname. All directory and device arguments to these attributes must be specified as absolute pathnames. Device paths may include the * wildcard. One of the following options may also be specified to define how alternate device entries that are discovered by VxVM are to be treated: -a Suppresses any entries for matching devices in the OS-maintained device tree that are found by the VxVM autodiscovery mecha- nism. This is the default action if no option is specified to addforeign. -f Retains any entries for matching devices found by the VxVM autodiscovery mechanism, and suppresses any foreign device entries that are defined. -n Does not suppress any entries. Duplicate entries for foreign devices are allowed. addjbod Adds disks having the specified VID and PID in the JBOD category (DISKS). The policy option may be specified to handle JBOD arrays in either active/active (aa) or active/passive (ap) mode. By default, JBOD disks are handled as active/active arrays. disablescsi3 Disables the discovery of SCSI3 disks in the JBOD category. enablescsi3 Initiates the method to discover SCSI3-conformant disks. Such disks, if found, are categorized in the JBOD category. The method comes into effect when the discovery operation is subsequently invoked. The policy option may be specified to discover devices in active/active (aa) or active/passive (ap) mode. By default, devices are discovered in active/active mode. excludearray Excludes the specified array libraries from participating in device discovery. This does not remove the specified libraries from the system. As a result, vxddladm listsupport displays the corresponding disk arrays. get namingscheme Returns the current setting of the disk device naming scheme. gettune Returns the value of a specified DDL tunable parameter. If all is specified, a list of all the DDL tunables and their values is displayed. includearray Includes the array libraries previously excluded by excludearray. These can be used for device discovery operations. listexclude Lists information about the disk array libraries excluded from device discovery functionality. listforeign Lists information about foreign devices that have been defined to VxVM. listjbod Lists information about the types of disks supported in JBOD category (DISKS). listsupport Lists summary information about supported disk arrays. The libname attribute can be used to display a detailed list of attributes for a specified library. listversion Lists the version numbers of array support libraries and the minimum VxVM release that is required for each library. The libname attribute can be used to request that the information is to be displayed only for the specified library. modescsi3 Displays the mode for SCSI3 disk discovery. By default, devices are discovered in active/active mode. rmforeign Removes a matching entry from the list of foreign directories and devices. See the ATTRIBUTES section for a description of the attributes that can be used with rmforeign: blockdir, blockpath, chardir, charpath, dir, dirname, path and pathname. rmjbod Removes disk with the specified VID and PID from the JBOD category (DISKS). These disks are categorized as OTHER_DISKS and are not multipathed. set namingscheme={ebn|osn} [persistence={yes|no}] Bases the name of a device on the enclosure name (ebn), or on the device name that is used by the operating system (osn). The change is immediate, and does not require vxconfigd to be restarted. The optional persistence argument allows you to select whether the names of disk devices that are displayed by VxVM remain unchanged after disk hardware has been reconfigured and the system rebooted. By default, enclosure-based naming and operating system-based naming are persistent (yes). VxVM commands display device names according the current naming scheme. If operating system-based naming is selected, all VxVM commands that list DMP node devices will display device names according to the mode that is specified: default The same format is used as in the input to the command (if this can be determined). Otherwise, legacy names are used. This is the default mode. legacy Only legacy names (in c#t#d# format) are displayed. new Only new (agile) names (in disk## format) are displayed. settune Sets the value of the specified DDL tunable parameter. This value takes precedence over any value that is set using the method provided by the operating system. The changed value is persistent across reboots of the system. The following tunable parameter may be changed for DDL: monitor_fabric Controls whether the Event Source daemon (vxesd) uses the Storage Networking Industry Association (SNIA) HBA API. This API allows DDL to improve the performance of failover by collecting information about the SAN topology and by monitor- ing fabric events. If set to on, DDL uses the SNIA HBA API. (Note that the vendor-provided ASL must also support the use of the SNIA HBA API.) If set to off, the SNIA HBA API is not used. The default setting is off for releases prior to 5.0 that have been patched to support this DDL feature. The default setting is on for 5.0 and later releases. start eventsource stop eventsource Starts or stops the event source daemon. This daemon passes disk-related events to DDL. For example, if a disk is added, removed, or changed, DDL invokes the device discovery actions that are related to that disk event. ATTRIBUTES
The attribute all selects all objects for an operation. Other attributes are specified using the format attribute=value. blockdir Absolute pathname of a directory that contains block device entries for foreign devices. blockpath Absolute pathname of the block device for a foreign device. chardir Absolute pathname of a directory that contains character device entries for foreign devices. charpath Absolute pathname of of a character device for a foreign device. dir Absolute pathname of a directory that contains character and block device entries for foreign devices. dirname Equivalent to dir. length Size of the field containing unique disk serial number. libname Name of the array library on which the operation is to be performed. offset Offset on the page code. opcode SCSI opcode. pagecode Page code for SCSI command. path Absolute pathname of a single character or block device for a foreign device. pathname Equivalent to path. pid Product ID of the disk array. policy Sets the policy of the specified device to aa (active/active) or ap (active/passive). vid Vendor ID of the disk array. NOTES
If you specify values for vid or pid to the excludearray or includearray operations, this excludes or includes all arrays that are sup- ported by the corresponding array library. The value for vid and pid should be taken from the output of the vxddladm listsupport command. These values may be different from the actual vid and pid values of the disks within an array. See the vxdiskadm(1M) manual page for information on using the vxdiskadm command to suppress or unsuppress individual devices from the view of VxVM, or to disable or enable multipathing for these devices. FILES
/etc/vx/darecs Used to store records for foreign devices. SEE ALSO
vxconfigd(1M), vxdctl(1M), vxdisk(1M), vxdiskadm(1M), vxdmpadm(1M) VxVM 5.0.31.1 24 Mar 2008 vxddladm(1M)
All times are GMT -4. The time now is 02:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy