Powerpath upgrade with SVM disksets


 
Thread Tools Search this Thread
Operating Systems Solaris Powerpath upgrade with SVM disksets
# 1  
Old 09-29-2013
Powerpath upgrade with SVM disksets

Hi all
I am running the following hardware:
2 SUN Solaris 10 machines
They are connected to EMC clarion LUNs
We are running a Sun Cluster 3.2 managing both nodes
We are using Solaris Volume Manager to handle the shared storage for the cluster. It is using a number of named disk sets that is shared among both hosts.

Now the situation is as follows:
We are upgrading the storage from Clarion to VMax. The storage admin will handle data replication so that the new luns are exactly the same. The only problem at hand is that the PowerPath software will be updated which means that the luns will have new IDs.
I need to change the hardware IDs of the diskset disks to reflect the new hardware address provided that they still have their same DID.
How can i do that? can i edit some file and change the hardware address or should i attach the new disk and remove the old one? and if so how can i retain the same DID?
thanks a lot in advance
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. 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

2. Solaris

Problem in SVM after live upgrade

Hi I am new to live upgrade. I would like to tell you about my new setup, where my boot disk(c0d0) is mirrored with secondary disk(c0d1). I have remove the secondary whole disk(C0d1) from the mirror, so that I can do live upgrade on this secondary disk. I have done live upgrade on s0 partition... (3 Replies)
Discussion started by: amity
3 Replies

3. 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

4. Emergency UNIX and Linux Support

Mapping between "Pseudo name" and "Logical device ID" in powerpath with SVM changed....

Dear All, I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output : root # powermt display dev=all Pseudo name=emcpower3a CLARiiON ID=CK200073400372 Logical device ID=60060160685D1E004DD97FB647BFDC11 state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies

5. Solaris

Migrate from MPXIO to Powerpath

Here is the issue: I am building a database server using Solaris 10x86 U8. The system is jumpstarted with mpxio enabled and booting from the san. We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies

6. 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

7. 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

8. AIX

Cannot uninstall powerpath - bosboot issues

Hi Guys, I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one. I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors: ... (4 Replies)
Discussion started by: zxmaus
4 Replies

9. Solaris

change SP value in powerpath

How to change the following values in power path from SP B to SP A ? Owner: default=SP B, current=SP B this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies
Login or Register to Ask a Question
clvxvm(1CL)						 Sun Cluster Maintenance Commands					       clvxvm(1CL)

NAME
clvxvm - configure VERITAS Volume Manager for Sun Cluster SYNOPSIS
/usr/cluster/bin/clvxvm -V /usr/cluster/bin/clvxvm [subcommand] -? /usr/cluster/bin/clvxvm subcommand -v /usr/cluster/bin/clvxvm encapsulate /usr/cluster/bin/clvxvm initialize DESCRIPTION
The clvxvm utility initializes VERITAS Volume Manager (VxVM) on a Sun Cluster node and optionally performs root-disk encapsulation. There is no short form of this command name. You can only use this utility with VxVM versions 4.1 or later. For older versions of VxVM, instead use the scvxinstall(1M) utility. The general form of this command is as follows: clvxvm [subcommand] [options] You can omit subcommand only if options specifies the -? option or the -V option. Each option of this command has a long form and a short form. Both forms of each option are given with the description of the option in the OPTIONS section of this man page. You can only use this command from a node that is booted in cluster mode. All nodes in the cluster configuration must be current cluster members. All nodes must be added to the node authentication list. You can use this command only in the global zone. SUBCOMMANDS
The following subcommands are supported: encapsulate Encapsulates the root disk and performs other Sun Cluster-specific tasks. The encapsulate subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Runs several VxVM commands to prepare for root-disk encapsulation. o Modifies the global-devices entry in the /etc/vfstab file that is specified for the /global/.devices/node@n file system, where n is the node ID number. The clvxvm utility replaces the existing device path /dev/did/{r}dsk with /dev/{r}dsk. This change ensures that VxVM recognizes that the global-devices file system resides on the root disk. o Twice reboots each node that is running clvxvm. The first reboot allows VxVM to complete the encapsulation process. The sec- ond reboot resumes normal operation. The clvxvm utility includes a synchronization mechanism to ensure that the utility reboots only one node at a time, to prevent loss of quorum. o Unmounts the global-devices file system. The file system is automatically remounted after the encapsulation process is com- plete. o Recreates the special files for the root-disk volumes with a unique minor number on each node. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Each root disk that you encapsulate must have at least two free (unassigned) partitions. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. initialize Initializes VxVM and performs other Sun Cluster-specific tasks. The initialize subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Instructs the user to reboot the node to resume operation with the new vxio major number in effect, in case the number had to be changed. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. OPTIONS
The following options are supported: -? ---help Displays help information. You can use this option either alone or with a subcommand. o If you use this option alone, the list of available subcommands is printed. o If you use this option with a subcommand, the usage options for that subcommand are printed. When you use this option, no other processing is performed. -V ---version Displays the version of the command. Do not specify this option with subcommands, operands, or other options. The subcommands, operands, or other options are ignored. The -V option only displays the version of the command. No other operations are performed. -v ---verbose Displays verbose information to standard output. You can use this option with any form of the command. OPERANDS
No form of this command accepts an operand. EXIT STATUS
The complete set of exit status codes for all commands in this command set are listed on the Intro(1CL) man page. This command returns the following exit status codes: 0 CL_NOERR No error 1 CL_ENOMEM Not enough swap space 3 CL_EINVAL Invalid argument 6 CL_EACCESS Permission denied 35 CL_EIO I/O error EXAMPLES
Example 1 Initializing VxVM on a Cluster Node The following example shows how to initialize VxVM the cluster node from which the command is issued. # clvxvm initialize Example 2 Initializing VxVM on a Cluster Node and Encapsulating the Root Disk The following example shows how to initialize VxVM and encapsulate the root disk on the cluster node from which the command is issued. # clvxvm encapsulate ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ FILES
/var/cluster/cmvxvm/* Location of temporary files that are used by the clvxvm utility. /var/cluster/logs/install/clvxvm.log.pid Log file that is created by the scvxinstall utility. SEE ALSO
Intro(1CL), cldevice(1CL), cldevicegroup(1CL), clsetup(1CL), cluster(1CL), scinstall(1M), scvxinstall(1M), rbac(5) Sun Cluster Software Installation Guide for Solaris OS NOTES
The superuser can run any forms of this command. Any user can also run this command with the following options: o -? (help) option o -V (version) option To run this command with other subcommands, users other than superuser require RBAC authorizations. See the following table. +------------+---------------------------------------------------------+ |Subcommand | RBAC Authorization | +------------+---------------------------------------------------------+ |encapsulate | solaris.cluster.modify | +------------+---------------------------------------------------------+ |initialize | solaris.cluster.modify | +------------+---------------------------------------------------------+ Sun Cluster 3.2 19 Jul 2006 clvxvm(1CL)