If you start a system from iSCSI, the gateway specified in the iSCSI Boot solution will always be used by Windows to communicate with the iSCSI Target

Article translations Article translations
Close Close
Article ID: 960104 - View products that this article applies to.
Expand all | Collapse all
Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom

If you start a Windows Server 2003 or Windows Server 2008 system using iSCSI Boot with the Microsoft iSCSI Boot Initiator, the gateway settings specified in the iSCSI Boot solution will always be used by Windows to reach the iSCSI Target hosting the boot drive, even if the iSCSI Target is directly reachable (on-link) and is not on a network disjoint from the iSCSI Boot NIC.

Cause



While starting, the Microsoft iSCSI Boot Initiator creates a static route to the iSCSI Target which contains the gateway specified in the iSCSI Boot solution.  This route is a system-critical route that cannot be removed.

Because the gateway from the iSCSI Boot solution is specified in the route, the gateway will always be used in communication with the iSCSI Target, even if the iSCSI Target is directly reachable (on-link) and a gateway is not required to communicate with the iSCSI Target.

Resolution



In an iSCSI Boot environment, the optimal configuration is to have a NIC dedicated to iSCSI traffic and a separate NIC or NICs used for network communication with other servers or workstations.  In an iSCSI Boot environment, the iSCSI Boot NIC being used to communicate with the iSCSI Target should only be used for communication with the iSCSI Target.

The NIC being used to communicate with the iSCSI Target should be configured to communicate with the iSCSI Target using the most efficient network route possible.  For example, if a gateway is not needed to reach the iSCSI Target, then one should not be specified in the iSCSI Boot solution.  This will prevent network traffic to the iSCSI Target from being unnecessarily routed through a gateway.

The Default Gateway specified in the TCP/IP settings for the iSCSI Boot NIC is separate from the gateway specified in the static route created by the Microsoft iSCSI Boot Initiator.  The Default Gateway is used to communicate with devices on disjoint networks.  The gateway specified in the static route created by the Microsoft iSCSI Boot Initiator will take precedence over any Default Gateway specified in the TCP/IP settings for the iSCSI Boot NIC.  For more information Default Gateways, please review the following KB article:

157025  Default Gateway Configuration for Multihomed Computers

Multiple Default Gateways should not be specified on a system, as you may experience connectivity problems.  For more information regarding multiple Default Gateways, please review the following KB article:

159168  Multiple Default Gateways Can Cause Connectivity Problems

More Information



The static route is created by the Microsoft iSCSI Boot Initiator to ensure communication with the iSCSI Target is maintained at all times, as the iSCSI Target contains files critical to the operation of Windows.

The gateway settings for the static route are passed from the iSCSI Boot solution to the Microsoft iSCSI Boot Initiator by way of the iSCSI Boot Firmware Table (iBFT).  For more information on the function and purpose of the iBFT, please review the following KB article:

953528  You may experience unpredictable results in Windows Server 2003 when you start the operating system from iSCSI

To view the active routes on a system, including the system-critical route established when using iSCSI Boot, use the 'route print' command from the Command Prompt.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Properties

Article ID: 960104 - Last Review: November 14, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Windows Server 2008 Standard
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter
Keywords: 
kbnomt kbrapidpub KB960104

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