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
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)
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)
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)
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)
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)
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)
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)
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)
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)
claccess(1CL) Sun Cluster Maintenance Commands claccess(1CL)NAME
claccess - manage Sun Cluster access policies for nodes
SYNOPSIS
/usr/cluster/bin/claccess -V
/usr/cluster/bin/claccess [subcommand]
-?
/usr/cluster/bin/claccess subcommand
[options] -v [hostname[,...]]
/usr/cluster/bin/claccess allow -h hostname[,...]
/usr/cluster/bin/claccess allow-all
/usr/cluster/bin/claccess deny -h hostname[,...]
/usr/cluster/bin/claccess deny-all
/usr/cluster/bin/claccess list
/usr/cluster/bin/claccess set -p protocol=authprotocol
/usr/cluster/bin/claccess show
DESCRIPTION
The claccess command controls the network access policies for machines that attempt to access the cluster configuration. The claccess com-
mand has no short form.
The cluster maintains a list of machines that can access the cluster configuration. The cluster also stores the name of the authentication
protocol that is used for these nodes to access the cluster configuration.
When a machine attempts to access the cluster configuration, for example when it asks to be added to the cluster configuration (see cln-
ode(1CL)), the cluster checks this list to determine whether the node has access permission. If the node has permission, the node is
authenticated and allowed access to the cluster configuration.
You can use the claccess command for the following tasks:
o To allow any new machines to add themselves to the cluster configuration and remove themselves from the cluster configuration
o To prevent any nodes from adding themselves to the cluster configuration and removing themselves from the cluster configuration
o To control the authentication type to check
You can use this command only in the global zone.
The general form of the claccess command is as follows:
claccess [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 provided with the description of the option in
the "OPTIONS" section of this man page.
SUBCOMMANDS
The following subcommands are supported:
allow
Allows the specified machine or machines to access the cluster configuration.
Users other than superuser require solaris.cluster.modify role-based access control (RBAC) authorization to use this subcommand. See
rbac(5).
See also the description of the deny and the allow-all subcommands.
allow-all
Allows all machines to add themselves to access the cluster configuration.
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See rbac(5).
See also the description of the deny-all and the allow subcommands.
deny
Prevents the specified machine or machines from accessing the cluster configuration.
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See rbac(5).
See also the description of the allow and the deny-all subcommands.
deny-all
Prevents all machines from accessing the cluster configuration.
No access for any node is the default setting after the cluster is configured the first time.
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See rbac(5).
See also the description of the allow-all and the deny subcommands.
list
Displays the names of the machines that have authorization to access the cluster configuration. To see the authentication protocol as
well, use the show subcommand.
Users other than superuser require solaris.cluster.read RBAC authorization to use this subcommand. See rbac(5).
set
Sets the authentication protocol to the value that you specify with the -p option. By default, the system uses sys as the authentica-
tion protocol. See the -p option in "OPTIONS".
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See rbac(5).
show
Displays the names of the machines that have permission to access the cluster configuration. Also displays the authentication protocol.
Users other than superuser require solaris.cluster.read RBAC authorization to use this subcommand. See rbac(5).
OPTIONS
The following options are supported:
-?
--help
Displays help information. When you use this option, no other processing is performed.
You can specify this option without a subcommand or with a subcommand. If you specify this option without a subcommand, the list of
subcommands of this command is displayed. If you specify this option with a subcommand, the usage options for the subcommand are dis-
played.
-h hostname
--host=hostname
--host hostname
Specifies the name of the node being granted or denied access.
-p protocol=authprotocol
--authprotocol=authentication_protocol
--authprotocol authentication_protocol
Specifies the authentication protocol that is used to check whether a machine has access to the cluster configuration.
Supported protocols are des and sys (or unix). The default authentication type is sys, which provides the least amount of secure
authentication. For more information on adding and removing nodes, see Adding a Cluster Node in Sun Cluster System Administration Guide
for Solaris OS. For more information on these authentication types, see Chapter 16, Using Authentication Services (Tasks), in System
Administration Guide: Security Services.
-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 displays only the version of the command. No other processing is performed.
-v
--verbose
Displays verbose information to standard output (stdout).
EXIT STATUS
If the command is successful for all specified operands, it returns zero (CL_NOERR). If an error occurs for an operand, the command pro-
cesses the next operand in the operand list. The returned exit code always reflects the error that occurred first.
The following exit codes can be returned:
0 CL_NOERR
No error
The command that you issued completed successfully.
1 CL_ENOMEM
Not enough swap space
A cluster node ran out of swap memory or ran out of other operating system resources.
3 CL_EINVAL
Invalid argument
You typed the command incorrectly, or the syntax of the cluster configuration information that you supplied with the -i option was
incorrect.
6 CL_EACCESS
Permission denied
The object that you specified is inaccessible. You might need superuser or RBAC access to issue the command. See the su(1M) and rbac(5)
man pages for more information.
18 CL_EINTERNAL
Internal error was encountered
An internal error indicates a software defect or other defect.
39 CL_EEXIST
Object exists
The device, device group, cluster interconnect component, node, cluster, resource, resource type, or resource group that you specified
already exists.
EXAMPLES
Example 1 Allow a New Host Access
The following claccess command allows a new host to access the cluster configuration.
# claccess allow -h phys-schost-1
Example 2 Set the Authentication Type
The following claccess command sets the current authentication type to des.
# claccess set -p protocol=des
Example 3 Deny Access to All Hosts
The following claccess command denies all hosts access to the cluster configuration.
# claccess deny-all
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO Intro(1CL), clnode(1CL), cluster(1CL)NOTES
The superuser user can run all forms of this command.
Any user can run this command with the following subcommands and options:
o -? option
o -V option
To run this command with other subcommands, users other than superuser require RBAC authorizations. See the following table.
+-----------+---------------------------------------------------------+
|Subcommand | RBAC Authorization |
+-----------+---------------------------------------------------------+
|allow | solaris.cluster.modify |
+-----------+---------------------------------------------------------+
|allow-all | solaris.cluster.modify |
+-----------+---------------------------------------------------------+
|deny | solaris.cluster.modify |
+-----------+---------------------------------------------------------+
|deny-all | solaris.cluster.modify |
+-----------+---------------------------------------------------------+
|list | solaris.cluster.read |
+-----------+---------------------------------------------------------+
|set | solaris.cluster.modify |
+-----------+---------------------------------------------------------+
|show | solaris.cluster.read |
+-----------+---------------------------------------------------------+
Sun Cluster 3.2 22 Jul 2005 claccess(1CL)