Installation manual

Configuring Front-End Services
Configuring CIFS
CLI Storage-Management Guide 11-29
RFCs 1034 and 1035 define basic DNS, and RFC 3645 defines Microsoft-specific
authentication extensions to for dynamic DNS. The ARX implementation of dynamic
DNS adheres to all of these RFCs.
Before you use dynamic DNS, the name server(s) for this service’s Windows Domain
must be included in the AD forest. For instructions on setting up name servers for the
AD forest, recall “Identifying a Dynamic-DNS Server” on page 3-12. The Windows
Domain for this CIFS service is determined by the service’s global server; use
show
global server
to see the domain (recall “Showing One Global-Server” on page 10-13).
Use the
dynamic-dns command to choose a name for this service and register it with a
name server. This sends an “A” (Address) record that maps the virtual server’s VIP to
a host name:
dynamic-dns host-name
where host-name (1-255 characters) is a host name you choose for this CIFS
service. This is mapped to the virtual server’s VIP in the “A” record. If you enter
a host name without any domain (for example, “myservice”), the global server’s
Windows domain is appended to it. If you specify a domain (for example,
“myservice.myco.net”), the domain must match the Windows domain for the
global server.
You can repeat the command to enter additional aliases for this CIFS service. All of
these host names map to the CIFS service’s VIP; Windows clients can use any of
them to access the CIFS service.
For example, this command sequence registers two host names, “test” and “ac1,” for
the current CIFS service:
bstnA6k(gbl)# cifs ac1.medarch.org
bstnA6k(gbl-cifs[ac1.medarch.org])# dynamic-dns test
bstnA6k(gbl-cifs[ac1.medarch.org])# dynamic-dns ac1
bstnA6k(gbl-cifs[ac1.medarch.org])# ...
Replacing Back-End Services
Through DNS aliasing, you can transparently replace the CIFS services on existing
back-end filers. For example, suppose you had the following CIFS filers and shares
before the ARX was installed:
• \\fs1.medarch.org\xrays