Installation manual

Configuring Front-End Services
Configuring CIFS
11-22 CLI Storage-Management Guide
bstnA6k(gbl)# cifs ac1.medarch.org
bstnA6k(gbl-cifs[ac1.medarch.org])# no export medarcv /cifstest
bstnA6k(gbl-cifs[ac1.medarch.org])# ...
Allowing Clients to Use Windows Management (MMC)
As an alternative to managing the CIFS service from the CLI, Windows clients can
use Windows-management applications to manage the service from a remote PC. You
can use this feature instead of the
export command, above. Authorized clients can use
the Microsoft Management Console (MMC) and similar applications to export
volumes, list open files, close client sessions, and so on.
From gbl-cifs mode, use the
browsing command to enable Windows-management
browsing for the namespace behind this service:
browsing namespace
where namespace (1-30 characters) is the namespace that clients can access
through Windows-management applications like MMC. A CIFS service can only
export volumes from a single namespace, so if you have used the
export
command already, this must be the same namespace that you previously used.
Only authorized Windows clients can manage the CIFS service. You can configure a
group of CIFS clients with Windows-management access (recall “Authorizing
Windows-Management (MMC) Access” on page 3-28) and associate it with this
service’s namespace (also recall “Opening Windows-Management Access (optional,
MMC)” on page 7-18). These clients can use MMC and other remote-management
applications to fully manage the namespace.
For example, the following command sequence allows authorized clients of the
“ac1.medarch.org” service to use Windows management:
bstnA6k(gbl)# cifs ac1.medarch.org
bstnA6k(gbl-cifs[ac1.medarch.org])# browsing medarcv
bstnA6k(gbl-cifs[ac1.medarch.org])# ...