Resetting your VCS admin Password with root
Created: 04 Nov 2011 | 5 comments
If you've manged to get locked out of your Veritas Cluster Server Cluster Manager, but you have root access to the server, you can reset your password using the following procedure.
#su - root
#hauser -list
admin
#hauser -update admin
If you receive the following error when running this command:
VCS WARNING V-16-1-11309 Configuration must be ReadWrite then, you need to put the configuration into ReadWrite mode.
#haconf -makerw
You should now be able to set password.
Blog Entry Filed Under:
About Storage & Clustering Community Blog
The Storage & Clustering Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Storage & Clustering community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Storage Foundation Cluster Server Management Solutions (CommandCentral, SORT, VOM, VOM Advanced) Storage Foundation for Windows ApplicationHA Dynamic Multi-Pathing and Dynamic Multi-Pathing for VMware Veritas Replicator FileStore Tip/How to New Release Features #DR #BCM Basics Best Practice #symantecstorage Data Insight Storage and Clustering Documentation Upgrade Installing NetBackup high availability disaster recovery #risk #datacenter
Comments 5 Comments • Jump to latest comment
]# ./hauser -list
admin
# who am i
root pts/0 2013-02-14 16:27
# ./hauser -update admin
VCS WARNING V-16-1-10603 Unknown option: -update
VCS INFO V-16-1-10601 Usage:
hauser -add <name> [-priv <Administrator|Operator|Guest> [-group <group(s)>]]
hauser -addpriv <name> <Administrator|Operator|Guest> [-group <group(s)>]
hauser -delpriv <name> <Administrator|Operator|Guest> [-group <group(s)>]
hauser -addpriv <name> <AdministratorGroup|OperatorGroup> [-group <group(s)>]
hauser -delpriv <name> <AdministratorGroup|OperatorGroup> [-group <group(s)>]
hauser -delete <name>
hauser -display [<name>]
hauser -list
hauser -help
]# uname -a
Linux <hostname>.<subdomain>.<domain>.com 2.6.32-279.14.1.el6.x86_64 #1 SMP Mon Oct 15 13:44:51 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
Is there another way?
John,
I think you are running a 'Secure VCS cluster'. Please confirm by checking cluster attribute SecureClus.
#haclus -value SecureClus
If the value is '1', then you are running secure cluster and the users will be authenticated with their OS /LDAP credentials.
The user passwords are not used from the main.cf. I think you have moved from non-secure cluster to secure cluster and had 'admin' as user earlier. Now in secure cluster, you will need an OS user 'admin' to work in same way. I would, instead advice the following:
from root shell, you can run following, where vcsadmin is an OS user on all the nodes of cluster.
# hauser -add vcsadmin -priv Administrator
Alternatively you can also do the following, assuming sys1.nebula.com is FQDN for one of the cluster node.
#hauser -add vcslocaladmin@sys1.nebula.com -priv Administrator.
Please let me know if you face some more problem.
Thanks and Warm Regards,
Amit Rangari
If this post helped you resolving the issue, please mark it as solution. _____________________________________________________________________________
any updates?
Thanks and Warm Regards,
Amit Rangari
If this post helped you resolving the issue, please mark it as solution. _____________________________________________________________________________
Amit,
I re-installed using the CPI (common platform installer) and changed the security. Apparently, the installer wizard for the Symantec High Availability plug-in within vCenter does not allow this option. Can an enhancement request be filed?
Thanks-
-John
John,
Please do report into Symantec Support so that concern teams can take a look at it.
Thanks and Warm Regards,
Amit Rangari
If this post helped you resolving the issue, please mark it as solution. _____________________________________________________________________________
Would you like to reply?
Login or Register to post your comment.