HP StorageWorks Storage Mirroring application notes Guidelines for networking and failover (T2558-96063, February 2008)

Storage Mirroring Guidelines for networking and failover application notes 7
• WINS scripting is not required when the target and all clients have the same primary WINS server
(regardless of whether clients and target are in a LAN or WAN environment), the target server and all
clients are Windows 2000 or later versions and the IP address is failed over, or the “replace” failover
option is used.
Since Windows 2000/2003 clients can use SMB/IP with any IP address on a Windows 2000/2003
server, it does not matter if they resolve the source name to the source IP address or the target IP address.
Both will work as long as the source IP address is failed over to the target. However, if the source IP
address is not failed over (typically because the source and target are on different subnets), WINS servers
must be updated at failover so that clients will resolve the source name to the target IP address.
Management of Windows NT 4.0 WINS servers can only be scripted with WINSCL, which includes two
different methods of registration. The first way is to import an LMHOSTS file that is located on the WINS
server. This method requires less scripting, but more files to manage since a separate LMHOSTS file must
be maintained on each WINS server for each source server. If there are ten source servers and ten WINS
servers, 100 LMHOSTS files, ten on each WINS server, will be required.
The second method is to script each registration individually. Although this requires only one script per
source and does not require any files to be stored on the WINS servers, the scripts are much longer since
a complete WINS registration for a member server actually has three registrations: SERVER[0x0],
SERVER[0x3], and SERVER[0x20]. See Microsoft Knowledge Base article 119495 for descriptions of names
registered with the WINS service. (The SERVER[0x3] entry is a registration for the Messenger service and
can typically be omitted unless there is an application dependency.) See ”Creating WINSCL scripts” on
page 7 for sample WINSCL scripts.
Windows 2000/2003 WINS servers can be managed with the WINSCL utility or the Windows 2000
NETSH command, which supports numerous Windows 2000 IP management functions. NETSH can be
used interactively or in scripts. The “add name” command in the WINS context will register SERVER[0x0],
SERVER[0x3], and SERVER[0x20] with the specified WINS server. See Microsoft Knowledge Base article
233375 for more information on adding WINS registrations with the NETSH command. Following is an
example that adds a dynamic (RecType=1) registration for a server named EUROPA with an IP address of
172.16.137.5 to a WINS server with an IP address of 172.16.137.1.
netsh wins server 172.16.137.1 add name Name=EUROPA RecType=1 IP={172.16.137.5}
Using the NETSH command is the preferable method in Windows 2000/2003 environments since each
registration is simply a one-line command. Additionally, the NETSH command can be used to initiate
WINS replication on Windows 2000 WINS servers if that is the method selected to propagate the WINS
changes after failover.
netsh wins server [ip address of WINS server] set replicateflag 1
Creating WINSCL scripts
Updating WINS servers with WINSCL scripts will require two LMHOSTS files on each WINS server that
need to be updated, as well as text files containing the WINSCL commands that will be executed at
failover and failback. An LMHOSTS file (TARGET_HOST) mapping the source's name to the target's IP
address will be imported into the WINS database at failover, and another file (SOURCE_HOST) mapping
the source's name to the source's IP address will be imported into the WINS database at failback.
The following sample LMHOSTS files use a source computer named PRODSVR with an IP address of
10.5.0.2, while the target server's IP address is 10.4.0.4. As you can see, the SOURCE_HOST file
associates PRODSVR with its own 10.5.0.2 IP address, while the TARGET_HOST associates PRODSVR with
the target's IP address of 10.4.0.4
NOTE: The sample scripts provided are only examples. Because no two environments or configurations
are exactly the same, you MUST modify the sample scripts in order to make the solution work in your
environment.
SAMPLE_SOURCE_HOST
10.5.0.2 PRODSVR