n/a
When a clustered IP Address goes offline, it takes the "active" route down that was added as a persistent route with the route.exe command.
Reference MS KB article:
When using the route.exe command, the most common command to add a persistent route would be this:
route -p add 10.51.0.0 mask 255.255.0.0 10.44.60.1
This command does not specify the specific interface to bind the persistent route to. Because the persistent route is not bound to a specific interface, the persistent route is removed as an active route when an IP address is unbound from a NIC. In the example above, the route being specified to the gateway is the same NIC (network) that a SFW-HA / VCS IP resource uses to bind the IP Address used for replication.
To keep the "active" route, the interface must be specified as part of the command. For example, if the network card interface is 18, the command would be:
route -p add 10.51.0.0 mask 255.255.0.0 10.44.60.1 if 18
More information:
In Windows 2008 and above, the supported method for adding a persistent route is to also include the network card interface. There are two methods to determine the interface number of the network card. When executing the ROUTE PRINT or NETSH command, it will give you the interfaces at the top first. Something similar to this:
C:\>route print
IPv4 Route Table
========================================
Interface List
23 ...00 15 5d 4a ac 06 ...... Local Gigabit Controller
19 ...00 15 5d 4a ac 01 ...... Local Gigabit Controller #2
18 ...00 15 5d 4a ac 00 ...... Local Gigabit Controller #3
========================================
-or-
C:\>netsh int ipv4 show int
Idx Met MTU State Name
--- --- ----- ----------- -------------------
18 50 4294967295 connected Local Gigabit Controller #3
19 5 1500 connected Local Gigabit Controller #2
23 5 1500 connected Local Gigabit Controller
Applies To
SFW-HA or VCS
Microsoft Windows Server 2008 or 2008 R2
Persistent routes added with route.exe command