Test private network failures
Updated: January 21, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To test private network failures
Open Cluster Administrator.
Verify that there are at least two networks set up for internal cluster communication and determine which network has the highest priority for internal cluster communications.
For more information, see "To change network priority for communication between nodes" in Related Topics. When you follow that procedure, Cluster Administrator will only list those networks that support internal cluster communication.
If there are two or more internal networks, continue to step 4, otherwise stop here and do not continue.
On one node, unplug the cable for the highest priority network identified above.
In the console tree, click the cluster node and verify that the state of the node is still Up (that is, actively participating in all cluster operations).
To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.
To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools, and then double-click Cluster Administrator.
Information about functional differences
Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.