HP StorageWorks Scalable File Share - Manual (Page 150)

Verifying, diagnosing, and maintaining the system 6–20
6.1.6 Verifying the management network
To verify that the servers are correctly connected to the management network, perform the following steps
for each server in turn:
1. Enter the command shown in the following example. Note that, to address the management network,
you must append
-adm
to the server name:
# ssh south3-adm hostname
south3.my.domain.com
2. Verify that the host name returned by the command is correct for the server.
Repeat these steps for each server.
6.1.7 Verifying the operation of supplementary groups
To verify that supplementary groups are configured correctly and working correctly, perform the following
steps:
1. Verify the operation of the
ssh
connection (see Section 6.1.7.1).
2. Verify access for supplementary groups (see Section 6.1.7.2).
6.1.7.1 Verifying the operation of the ssh connection
Verify that the
ssh
connection is operating correctly, as follows:
1. Log in to the administration server.
2. Invoke the
hpls_getgroups
command on the group server as shown in the following example,
where
100
is a user UID:
# ssh [email protected] /usr/sbin/hpls_getgroups 100
uid=100 gid=30 gids=31,32,33,44,46,50
Ensure that the primary group (
gid=
) and the supplementary groups (
gids=
) fields shown by the
command are correct.
Repeat the verification steps on the MDS server.
6.1.7.2 Verifying access for supplementary groups
To allow you to verify that access for supplementary groups is being provided correctly, you must have the
following in place:
• A client node that has mounted a file system from the HP SFS system
• Two user accounts that are members of a common group other than their primary group
• A directory in the file system where one user has write and execute permissions on the directory and
the second user has execute permission.
To verify that access for supplementary groups is being provided correctly, perform the following steps:
1. Log in to the client node as user1.
2. Create a file and then use the
chmod
(1) command to allow read and write access for groups and
deny all access for others on the file (for example,
g=rw,o-rwx
).
3. Use the
chgrp
(1) command to change group ownership of the file to the common, non-primary,
group.
4. Log in to the client node as user 2.
5. Use the
touch
(1) or
cat
(1) commands to access the file; you should be allowed to access the file.