Active Route removed on Windows Server Failover Cluster

Article translations Article translations
Close Close
Article ID: 2161341 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When you add a static persistent route to a network adapter that is on a Windows Server 2008 Failover Cluster and take a clustered IP Address offline (or move it to another node), the “Active” route is removed and no connections can be made using this route even though it still shows as persistent when running the ROUTE PRINT command Once you bring the Clustered IP Address back online, the active route is returned. 

CAUSE

When a clustered IP Address goes offline, it takes the "active" route down that was added as a persistent route as well. This will only occur when both of the following are true:

1. Windows Server 2008 or Server 2008 R2 Failover Clustering is configured
2. Static Routes are being added with ROUTE.EXE

RESOLUTION

When using the ROUTE.EXE command, the most common command to add a persistent 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 to. Because it is not bound to a specific interface, it is removed as an active route. In the example above, the route being specified to the gateway is the same card (network) that a Clustered IP Address is on.

To keep the "active" route, you must also specify the interface 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


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2161341 - Last Review: September 11, 2010 - Revision: 1.1
APPLIES TO
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
Keywords: 
kbclustering KB2161341

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com