Installation manual

Configuring a Global Server
Adding a Global Server
10-4 CLI Storage-Management Guide
windows-domain name (up to 15 characters, converted to uppercase). For most
installations, this is sufficient. For sites that do not conform to this naming
convention, you can use the
pre-win2k-name option to use a different short-domain
name:
windows-domain domain pre-win2k-name short-name
where short-name (optional) can be up to 15 characters long. The CLI converts
all letters to uppercase. As with the domain, the namespace behind this global
server must have an NTLM-authentication server for the short-name domain,
too. This is a separate NTLM-server configuration that points to the same server
but supports the shortened Windows domain.
For example, the following command sequence sets the short name to “NTNET” for
the global server at “ac1.medarch.org:”
bstnA6k(gbl)# global server ac1.medarch.org
bstnA6k(gbl-gs[ac1.medarch.org])# windows-domain MEDARCH.ORG pre-win2k-name NTNET
bstnA6k(gbl-gs[ac1.medarch.org])# ...
Removing the Windows Domain
Use no windows-domain to remove the Windows domain from the global server:
no windows-domain
For example:
bstnA6k(gbl)# global server www.nfs-only.com
bstnA6k(gbl-gs[www.nfs-only.com])# no windows-domain
bstnA6k(gbl-gs[www.nfs-only.com])# ...
Adding a Virtual Server
The next step in setting up a global server is creating one or more virtual servers. The
virtual server listens at its VIP address for client requests; when one is received, the
switch invokes one of the global server’s front-end services (NFS or CIFS) to answer
the client request. A global server requires one virtual server to run its front-end
services.