Cluster Name Space
System Administration Manual
380
been created, create a single CIFS share and NFS export on the CNS root. Then, add a File
System Link for each physical file system under the root directory. In such a configuration, all of
the server’s storage resources will be accessible to network clients through a single share or
export, and each file system will be accessible through its own subdirectory.
Windows and Unix clients can take full advantage of the storage virtualization provided by CNS
because directories in the virtual name space can be shared and exported directly. However,
there is no support for creating FTP mount points or iSCSI Logical Units through the name
space. As a result, FTP clients and iSCSI Initiators communicate directly with individual EVS
and their associated file systems. This also means that if a file system containing FTP mount
points or iSCSI Logical Units is relocated to a different EVS, connectivity will need to be
reestablished through the new EVS.
Tip
: For the best results, FTP mount points and iSCSI Logical Units should
be added to file systems that are not part of a Cluster Name Space.
Note
: CNS is a licensed feature. To create a Cluster Name space, a CNS
license must be installed. To purchase a CNS license, please contact
BlueArc.
CNS Topology
The CNS has a tree-like directory structure, much like a real file system. The CNS can be viewed
through the CLI or the Web UI, and shows all of the configured directories and File System
Links.
To View an Existing Name Space
1.
Move to the SMU
Home
page.
2.
From the
File Services
heading, click on
CNS
to view the CNS page.
CNS Subdirectory
CNS Root Directory
CNS File System Link
Alert symbol indicates that the linked
file system also has shares or exports
outside of the CNS.
