Installation manual

Configuring Front-End Services
Configuring CIFS
11-16 CLI Storage-Management Guide
The volume and filers must be properly prepared before your CIFS service can offer
this subshare service. A subshare must have the same name, ACL, and position in the
directory tree (relative to the share root) on every filer behind the volume. To continue
the example, every filer share behind the “medarcv~/rcrds” volume must have
• a /2005 directory under its root,
• the same share name for it (“Y2005” in the above illustration), and
• the same ACL (“ACL3,” or its equivalent).
The managed-volume chapter discussed this preparation. Refer back to “Supporting
Subshares and their ACLs” on page 9-20, and “Replicating Subshares at all of the
Volume’s Filers” on page 9-23.
With the volume properly prepared, you can use the
filer-subshare flag in the export
command:
export namespace vol-path as subshare-name filer-subshare
[description description]
where
namespace and
vol-path are both described above.
subshare-name must match the subshare name used at all the back-end
filers.
filer-subshare specifies that clients should pass through to the back-end
subshare.
description description is also described above.
For example, the following command sequence adds the “Y2005” subshare to the
CIFS service at ac1.medarch.org:
bstnA6k(gbl)# cifs ac1.medarch.org
bstnA6k(gbl-cifs[ac1.medarch.org])# export medarcv /rcrds/2005 as Y2005 filer-subshare
bstnA6k(gbl-cifs[ac1.medarch.org])# ...