Wins, Wins -3, Wins registration -3 – HP Storage Mirroring V5 Software User Manual

Page 125: Wins registration

Advertising
background image

16

-

3

WINS

When Storage Mirroring failover occurs, Windows initiates WINS registration with the target’s primary WINS server to
associate the source server’s name with the target’s primary IP address. In an environment with just one WINS server, no
additional processing is required. In an environment with more than one WINS server, WINS replication will distribute the
updated WINS registration to other WINS servers on the network. The length of time required for all WINS servers to obtain
the new registration depends on the number of WINS servers, the WINS replication architecture, and the WINS replication
interval. Clients will be unable to access the target until their WINS server has received the updated WINS information. You
can reduce the time required for the WINS updates, thereby decreasing the wait time for the end users, by scripting the WINS
updates in the Storage Mirroring failover scripts. You have two options for scripting the WINS updates.

‹

WINS registration

—This options registers a user-specified server with WINS. It requires less network overhead but

administrator group membership on all WINS servers.

‹

WINS replication

—This option forces WINS replication. It does not require any special privileges, but requires system

and network resources to complete WINS replication. The impact on the network will depend on the size and complexity
of the WINS architecture.

WINS registration

WINS regisration can be added to your failover and failback scripts by using the Windows NETSH command with the WINS
add name context. Add the following command to your failover and failback scripts for each additional WINS server in your
environment (excluding the target’s primary WINS server).

netsh wins server wins_server_IP_address add name Name=source_server_name RecType=1 IP={IP_address}

The variables used in the command are defined in the table below.

For example, suppose you had the following environment.

‹

Source name

—Alpha

‹

Source IP address

—192.168.1.108

‹

Target name

—Beta

‹

Target IP address

—116.123.2.47

‹

Target’s Primary WINS server

—116.123.2.50

‹

First secondary WINS server on the network

—192.168.1.110

‹

Second secondary WINS server on the network

—150.172.114.74

You would add the following to your failover script to register the source’s name with the target’s IP address on the two
secondary WINS servers.

Sample Post-Failover Script for WINS Registration

You would add the following to your failback script to register the source’s name back with the source’s original IP address
on the two secondary WINS servers.

Sample Post-Failback Script for WINS Registration

See your Windows documentation or the Microsoft web site for more details on the NETSH command.

Variable

Description

wins_server_IP_address

The IP address of the WINS server

source_server_name

The name of the source serve

IP_address

The IP address of the target that has taken over for the failed source (for the failover script) or
the IP address of the source that is reassuming its original identity (for the failback script)

netsh wins server 192.168.1.110 add name Name=Alpha RecType=1 IP={116.123.2.47}

netsh wins server 150.172.114.74 add name Name=Alpha RecType=1 IP={116.123.2.47}

netsh wins server 192.168.1.110 add name Name=Alpha RecType=1 IP={192.168.1.108}

netsh wins server 150.172.114.74 add name Name=Alpha RecType=1 IP={192.168.1.108}

Advertising
This manual is related to the following products: