The cc_users domain cannot be selected in the VERITAS CommandCentral (tm) login screen. The result is that the user cannot log into the CommandCentral server using the default credentials.
| Article:TECH35332 | | | Created: 2008-01-26 | | | Updated: 2008-01-26 | | | Article URL http://www.symantec.com/docs/TECH35332 |
Problem
The cc_users domain cannot be selected in the VERITAS CommandCentral (tm) login screen. The result is that the user cannot log into the CommandCentral server using the default credentials.
Solution
The Issue: There have been incidents where,
after a fresh CommandCentral product installation has been completed, attempts
to connect to the CommandCentral server are not successful because the domain
entry in the login screen has no selection available for cc_users, or any other
domain in the drop down menu. An entry can also not be made by typing one
in.
Solution: The quickest solution to get CommandCentral to create the cc_user domain and others necessary to complete a successful login is to run the ccvssatsetup utility manually, available with all CommandCentral products. The following is the procedure:
Solution: The quickest solution to get CommandCentral to create the cc_user domain and others necessary to complete a successful login is to run the ccvssatsetup utility manually, available with all CommandCentral products. The following is the procedure:
I. Creating the private domains and principals
for CommandCentral manually
Solaris:
Solaris:
1. Log into the
CommandCentral Storage master server as root (super user)
2. Change to the directory
in the bin directory in the CommandCentral Shared Utilities for Solaris package
as follows:
# cd
/opt/VRTSccshd/bin
3. Launch the utility
ccvssatsetup as follows:
# ./ccvssatsetup
At this point, a series of
messages will be sent to the screen. The following major steps are
performed:
INITIALIZING:
CREATING PRIVATE
DOMAINS:
CREATING DOMAIN BROKER
MAPPINGS
CREATING PRINCIPALS
AUTHENTICATING
PRINCIPALS
The last line is as
follows:
"Closing connection to
authentication service"
Windows:
1. Log into the
CommandCentral Storage master server as administrator
2. Open a cmd
Window
3. Change to the folder in
CommandCentral as follows:
C:\>
cd \Program Files\VERITAS\Security\Authentication\bin
4. Launch the
utility ccvssatsetup as follows:
C:\> ccvssatsetup
At this point, a series of
messages will be sent to the screen. The following major steps are
performed:
INITIALIZING:
CREATING PRIVATE
DOMAINS:
CREATING DOMAIN BROKER
MAPPINGS
CREATING PRINCIPALS
AUTHENTICATING
PRINCIPALS
The last line is as
follows:
"Closing connection to
authentication service"
II. To verify that the
domains and principals exist and are recognized in CommandCentral:
Solaris:
1. Log into the
CommandCentral Storage master server as root (super user)
2. Change to the bin
directory for /opt/VRTSat
# cd
/opt/VRTSat/bin
3. Run the vssat utility
to extract the list of existing domains as follows:
#
./vssat showallbrokerdomains
This will show all the default
domains and principals that have been created.
Windows:
1. Log into the
CommandCentral Storage master server as administrator
2. Open a cmd
Window
3. Change to the folder in
CommandCentral as follows:
C:\>
cd \Program Files\VERITAS\Security\Authentication\bin
4. Run the vssat utility
to extract the list of existing domains as follows:
C:\>
vssat showallbrokerdomains
This will show all the default
domains and principals that have been created.
III. Try connecting to the server again with the
browser using default credentials
Solaris or Windows:
Solaris or Windows:
1. Open a new browser
session on a workstation
2. Use the URL
<http://<hostname>:8181>
Note: The hostname can be the
nickname or the IP address of the CommandCentral Storage master server.
3. From the VERITAS Web
Console, select the CommandCentral product to be connected to
4. For the connection
splash screen, use defaults as follows:
Start
In: = Storage (also Service or Availability)
User
Name: = admin
Password: = password
Domain: = cc_users@<domain>
5. Press "Login"
The following is typically what
it should look like:
|
|
Related Articles
Legacy ID
272798
Article URL http://www.symantec.com/docs/TECH35332
Terms of use for this information are found in Legal Notices
Thank you.