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
scprivipadm(1M) 					  System Administration Commands					   scprivipadm(1M)

NAME
scprivipadm - administer the private IP address range SYNOPSIS
scprivipadm -c netaddr=netaddr[,netmask=netmask] scprivipadm -c netaddr=netaddr[,maxnodes=nodes,maxprivatenets=privnets] scprivipadm -c netaddr=netaddr[,netmask=netmask,maxnodes=nodes,maxprivatenets=privnets] scprivipadm -p scprivipadm -R DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scprivipadm command modifies the current IP address range that is assigned to the Sun Cluster private interconnect. All nodes in the cluster must be in noncluster mode before you run any form of this command. Run this command from one node in the cluster. The scprivipadm command takes as input the private network address. Optionally, the command also takes one or both of the following: o The netmask o The maximum number of nodes and the maximum number of private networks that are ever expected to be in the cluster The command then performs the IP address assignment for the physical adapters and the per-node IP addresses. You can use this command only in the global zone. OPTIONS
The following options are supported: -c Modifies the IP address range that is currently assigned to the cluster. Run the -c option on each node of the cluster. You can use this option only in the global zone. The -c option supports the following suboptions: netaddr=netaddr Specifies the private network address netmask=netmask Specifies the netmask maxnodes=nodes Specifies the maximum expected number of nodes in the cluster maxprivatenets=privnets Specifies the maximum expected number of private networks in the cluster The -c option performs the following tasks for each combination of suboptions: o If you specify the netaddr suboption alone, the command assigns the default netmask, 255.255.248.0, to the private interconnect. The default IP address range accommodates a maximum of 64 nodes and 10 private networks. o If you also specify the netmask suboption, the value that you specify must be equal to or greater than the default netmask. If the specified netmask is less than the default netmask, the command fails and exits with an error. If the specified netmask is equal to or greater than the default netmask, the command assigns the specified netmask to the private interconnect. The resulting IP address range can accommodate a maximum of 64 nodes and 10 private net- works. To assign a smaller IP address range than the default, specify the maxnodes and maxprivatenets suboptions. o If you also specify the maxnodes and maxprivatenets suboptions, the command calculates the minimum netmask to sup- port the specified number of nodes and private networks. The command then assigns the calculated netmask to the private interconnect. The maximum value for nodes is 64 and the minimum value is 2. The maximum value for privnets is 128 and the minimum value is 2. o If you also specify the netmask suboption as well as the maxnodes and maxprivatenets suboptions, the command calcu- lates the minimum netmask that supports the specified number of nodes and private networks. The command compares that calculation to the specified netmask. If the specified netmask is less than the calculated netmask, the com- mand fails and exits with an error. If the specified netmask is equal to or greater than the calculated netmask, the command assigns the specified netmask to the private interconnect. The maximum value for nodes is 64 and the minimum value is 2. The maximum value for privnets is 128 and the minimum value is 2. If the -c option fails, you must run the -R option on each node to repair the configuration before you rerun the -c option. Users other than superuser require solaris.cluster.modify Role-Based Access Control (RBAC) authorization to use this subcom- mand. See the rbac(5) man page. -R Repairs the cluster configuration. Use this option if the command fails while modifying the IP address range on the cluster nodes and the failure results in inconsistent cluster configuration on the nodes. You can use this option only in the global zone. Run the -R option on each node of the cluster. The -R option repairs the cluster configuration and removes any inconsistencies that were caused by a failure to modify the IP address range on all nodes. If you attempt to rerun the -c option without first running the -R option, the configuration change might again fail. Users other than superuser require solaris.cluster.modify Role-Based Access Control (RBAC) authorization to use this subcom- mand. See the rbac(5) man page. -p Displays the current private network address that is assigned to the private interconnect. Run the -p option from any node. You can use this option only in the global zone. The -p option prints the following information: o The private network address o The IP address range in the form of a netmask o The maximum number of nodes and the maximum number of private networks that can be supported by the IP address range Users other than superuser require solaris.cluster.read Role-Based Access Control (RBAC) authorization to use this subcommand. See the rbac(5) man page. To display the current private network address from a node that is in cluster mode, instead run the scconf -p command or the cluster show-netprops command. EXAMPLES
Example 1 Calculating a Custom Private IP Address Range The following command specifies the private network address 172.16.0.0 and calculates the netmask. The command specifies that the calcu- lated netmask must support up to sixteen nodes and up to four private networks in the cluster. # scprivipadm -c netaddr=172.16.0.0,maxnodes=16,maxprivatenets=4 Example 2 Specifying a Private Network Address and Netmask The following command specifies the private network address 172.16.0.0 and the netmask 255.255.248.0. # scprivipadm -c netaddr=172.16.0.0,netmask=255.255.248.0 EXIT STATUS
The scprivipadm command returns with a non-zero value if either of the following conditions occur: o Invalid arguments were provided. o The command was unable to successfully modify the IP address range on all nodes of the cluster. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cluster(1CL), scconf(1M), scinstall(1M), netmasks(4), networks(4), rbac(5) Sun Cluster Software Installation Guide for Solaris OS, Sun Cluster System Administration Guide for Solaris OS, System Administration Guide: IP Services NOTES
The superuser can run all forms of this command. Users other than superuser require RBAC authorizations. See the following table. +-------+---------------------------------------------------------+ |Option | RBAC Authorization | +-------+---------------------------------------------------------+ |-c | solaris.cluster.modify | +-------+---------------------------------------------------------+ |-R | solaris.cluster.modify | +-------+---------------------------------------------------------+ |-p | solaris.cluster.read | +-------+---------------------------------------------------------+ Sun Cluster 3.2 23 Jun 2006 scprivipadm(1M)