WINDOWS/caution.gif0000755000000000000000000000130411651733270011235 0ustar GIF89a)!19)!k91J9RZBRBJcRJB{fJcsZRRckJRfZJJ{{{{{s{{ksss{sJfffZZZRRRJJJJJ9BBB333)))!!!!,(,,00 -( 40 4(0 6($99 'A/ COO; 74 ͣB0  @7.C)!5.=ҏ# %"p8JB@1xJdbT`$cG(0c R`pP#B@̜=T`#IAT@!Nm; (QƄ:J05 (;98FCG fC >xA['!0!`> BH"F$D\N4yB$;WINDOWS/dmacoal.htm0000755000000000000000000000314211656574604011231 0ustar DMA Coalescing

Direct Memory Access (DMA) Coalescing

DMA (Direct Memory Access) allows the network device to move packet data directly to the system's memory, reducing CPU utilization. However, the frequency and random intervals at which packets arrive do not allow the system to enter a lower power state. DMA Coalescing allows the NIC to collect packets before it initiates a DMA event. This may increase network latency but also increases the chances that the system will consume less energy. Adapters and network devices based on the Intel® Ethernet Controller I350 (and later controllers) support DMA Coalescing.

Higher DMA Coalescing values result in more energy saved but may increase your system's network latency. If you enable DMA Coalescing, you should also set the Interrupt Moderation Rate to 'Minimal'. This minimizes the latency impact imposed by DMA Coalescing and results in better peak network throughput performance. You must enable DMA Coalescing on all active ports in the system. You may not gain any energy savings if it is enabled only on some of the ports in your system. There are also several BIOS, platform, and application settings that will affect your potential energy savings. A white paper containing information on how to best configure your platform is available on the Intel website.

WINDOWS/drivers.htm0000755000000000000000000000613111710273344011274 0ustar Install the Drivers

Intel Network Drivers for Microsoft* Windows* Operating Systems


Install the Drivers in Microsoft Windows

NOTE: This will update the drivers for all supported Intel® network adapters in your system.

Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network cable. When Windows discovers the new adapter, it attempts to find an acceptable Windows driver already installed with the operating system. 

If found, the driver is installed without any user intervention. If Windows cannot find the driver, the Found New Hardware Wizard window is displayed.

Regardless of whether or not Windows finds the driver, it is recommended that you follow the procedure below to install the driver. Drivers for all Intel adapters supported by this software release are installed.

  1. If you are installing drivers from the Product CD, insert the CD. If you do not have the Product CD, download drivers from the support website and transfer them to the system.

  2. If the Found New Hardware Wizard screen is displayed, click Cancel.

  3. Start the autorun located on the CD. If you downloaded the software package from the support website, the autorun automatically runs after you have extracted the files.

  4. Click Install Drivers and Software.

  5. Follow the instructions in the install wizard.


Uninstalling the Driver

These instructions uninstall the drivers for all Intel network adapters in a system.

  1. From the Control Panel, double-click Add/Remove Programs

  2. Select Intel(R) Network Connections Drivers.

  3. Click Add/Remove

  4. When the confirmation dialog displays, click OK


Last modified on 6/05/09 11:38a Revision

WINDOWS/dupwindm.htm0000755000000000000000000001103211656741062011447 0ustar Configuring Speed and Duplex in Windows*

Set Up Speed and Duplex

In the default mode, an Intel® Network Adapter using copper connections will attempt to auto-negotiate with its link partner to determine the best setting. If the adapter cannot establish link with the link partner using auto-negotiation, you may need to manually configure the adapter and link partner to identical settings to establish link and pass packets. This should only be needed when attempting to link with an older switch that does not support auto-negotiation or one that has been forced to a specific speed or duplex mode.

CAUTION: Only experienced network administrators should force speed and duplex manually. The settings at the switch must always match the adapter settings. Adapter performance may suffer or your adapter may not operate if you configure the adapter differently from your switch.

Your link partner must match the setting you choose.

Fiber-based adapters operate only in full duplex, and only at their native speed.

Configuring Speed and Duplex in Microsoft* Windows*

By default, auto-negotiation is enabled. Change this setting only to match your link partner.

  1. Navigate to the Device Manager.
  2. Open Properties on the adapter you would like to configure.
  3. Click the Link Speed tab.
  4. Select the appropriate speed and duplex from the Speed and Duplex pull down menu.
  5. Click OK.

Intel® Gigabit Network Adapter Considerations

Per the IEEE specification, gigabit speed is available only in full-duplex.

The settings available when auto-negotiation is disabled are:

Intel® 10 Gigabit Network Adapter Considerations

Intel® 10 Gigabit adapters that support 1 gigabit speed allow you to configure the Speed setting. If this option is not present, your adapter only runs at its native speed.

If the adapter cannot establish link with the gigabit link partner using auto-negotiation, set the adapter to 1 Gbps Full duplex.

Intel 10 gigabit fiber-based adapters and SFP direct-attach devices operate only in full duplex, and only at their native speed. Multi-speed 10 gigabit SFP+ fiber modules support full duplex at 10 Gbps and 1 Gbps.

Intel® PRO/100 Network Adapter Considerations

The settings available when auto-negotiation is disabled are:


Last modified on 12/30/09 3:51p Revision WINDOWS/hotwin.htm0000755000000000000000000000352311656574604011144 0ustar PCI Hot Plug Support for Microsoft Windows

PCI Hot Plug Support for Microsoft* Windows* Operating Systems

Intel® network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and running Microsoft* Windows* operating systems. For more information on setting up and using PCI Hot Plug support in your server, see your hardware and/or Hot Plug support documentation for details. PCI Hot Plug only works when you hot plug an identical Intel network adapter.

 

NOTES:
  • The MAC address and driver from the removed adapter will be used by the replacement adapter unless you remove the adapter from the team and add it back in. If you do not remove and restore the replacement adapter from the team, and the original adapter is used elsewhere on your network, a MAC address conflict will occur.
  • For SLA teams, ensure that the replacement NIC is a member of the team before connecting it to the switch.

 


Last modified on 9/03/07 4:49p Revision

WINDOWS/jumbo_dm.htm0000755000000000000000000001363011656574604011430 0ustar Jumbo Frames

Jumbo Frames

Jumbo frames are Ethernet frames that are larger than 1518 bytes. You can use Jumbo Frames to reduce server CPU utilization and increase throughput. However, additional latency may be introduced. 

NOTES:
  • Jumbo Frames are supported at 1000 Mbps and 10Gbps. Using Jumbo Frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

  • End-to-end network hardware must support this capability; otherwise, packets will be dropped.

Jumbo Frames can be implemented simultaneously with VLANs and teaming.

To configure Jumbo Frames at the switch, consult your network administrator or switch user's guide.

Restrictions:

Setting Up Jumbo Frames in Microsoft* Windows*

NOTE: Jumbo frames are not supported in multi-vendor team configurations.
  1. Open Microsoft* Windows* Device Manager.

  2. Open Properties on your adapter.

  3. Click the Advanced tab.

  4. Select Jumbo Frames from the list of advanced features.

  5. Set your desired packet size (based on network capability).

  6. Click OK to apply the changes. 

All equipment on the network must also support the larger frame size. When setting up Jumbo Frames on other network devices, be aware that different network devices calculate Jumbo Frame size differently. Some devices include the header information in the frame size while others do not. Intel adapters do not include header information in the frame size. When configuring Jumbo Frames on a switch, set the frame size four bytes higher for CRC, plus four bytes if you are using VLANs or QoS packet tagging.


Last modified on 8/01/11 3:59p Revision

WINDOWS/mang_win.htm0000755000000000000000000001754011734015456011427 0ustar Power Management

Power Management

The Intel® PROSet Power Management tab replaces the standard Microsoft* Windows* Power Management tab in Device Manager. It includes the Power Saver and Wake on LAN* (WoL*) options that were previously included on the Advanced tab. The standard Windows power management functionality is incorporated on the Intel PROSet tab.

NOTES:
  • The options available on the Power Management tab are adapter and system dependant. Not all adapters will display all options.
  • The following adapters support WoL only on Port A:
    • Intel® Ethernet Server Adapter I350-T2
    • Intel® Ethernet Server Adapter I350-T4
    • Intel® Ethernet Server Adapter I340-T2
    • Intel® Ethernet Server Adapter I340-T4
    • Intel® Ethernet Server Adapter I340-F4
    • Intel® Gigabit ET2 Quad Port Server Adapter
    • Intel® PRO/1000 PF Quad Port Server Adapter
    • Intel® PRO/1000 PT Quad Port LP Server Adapter
    • Intel® PRO/1000 PT Quad Port Server Adapter
    • Intel® PRO/1000 PT Dual Port Network Connection
    • Intel® PRO/1000 PT Dual Port Server Connection
    • Intel® PRO/1000 PT Dual Port Server Adapter
    • Intel® PRO/1000 PF Dual Port Server Adapter
    • Intel® Gigabit PT Quad Port Server ExpressModule
  • The following adapters do not support WoL:
    • Intel® PRO/1000 MT Quad Port Server adapter
    • Intel® Gigabit VT Quad Port Server Adapter
    • Intel® Ethernet Server Adapter X520-2
    • Intel® Ethernet Server Adapter X520-1
    • Intel® Ethernet Server Adapter X540-T1
    • Intel® Ethernet Converged Network Adapter X540-T2
    • Intel® Ethernet Converged Network Adapter X540-T1

NOTE: If your system has a Manageability Engine, the Link LED may stay lit even if WoL is disabled.

Power Options

The Intel PROSet Power Management tab includes several settings that control the adapter's power consumption. For example, you can set the adapter to reduce its power consumption if the cable is disconnected.

If Reduce speed during standby is enabled,  then Wake on Magic Packet and/or Wake on directed packet must be enabled. If both of these options are disabled, power is removed from the adapter during standby. Wake on Magic Packet from power off state has no effect on this option.

Energy Efficient Ethernet

The Energy Efficient Ethernet (EEE) feature allows a capable device to enter Low Power Idle between bursts of network traffic. Both ends of a link must have EEE enabled for any power to be saved. Both ends of the link will resume full power when data needs to be transmitted. This transition may introduce a small amount of network latency.

NOTES:

  • Both ends of the EEE link must automatically negotiate link speed.
  • EEE is not supported at 10Mbps.

 

Intel® Auto Connect Battery Saver

The Intel® Auto Connect Battery Saver (ACBS) feature turns off the adapter when link is down or the network cable is disconnected. After a timeout period, the adapter will power off. When the network cable is reconnected and link is restored, the NIC powers up and functionality is fully restored.

ACBS only functions when the system is on battery power. If the power cable is connected, ACBS will be automatically disabled. If ACBS is active, the adapter will appear to be powered off. If you have Intel® PROSet installed, on the Link Speed tab, the Link Status will indicate Speed: Not connected. Power off.

NOTE: ACBS will not function on an adapter if the adapter has forced speed or duplex settings. ACBS will only function if the adapter is set to auto-detect or auto-negotiate.

Intel® System Idle Power Saver

The Intel® System Idle Power Saver feature sets the adapter to negotiate the lowest possible speed setting when the system and network are idle. When the system activity is detected, the link will be negotiated to a higher speed.

To support this feature, the adapter must be

Remote Wake-Up and Wake on LAN*

The ability to remotely wake computers is an important development in computer management. This feature has evolved over the last few years from a simple remote power-on capability to a complex system interacting with a variety of device and operating system power states. More details are available here.

Microsoft Windows XP, Windows Vista*, Windows 7, Windows Server* 2003, Windows Server 2008, and Windows Server 2008 R2 are ACPI-capable. These operating systems do not support wake from a power-off (S5) state, only from standby (S3) or hibernate (S4). When shutting down the system, they shutdown ACPI devices, including Intel adapters. This disarms the adapters remote wake up capability. However, in some ACPI-capable computers, the BIOS may have a setting that allows you to override the operating system and wake from an S5 state anyway. If there is no support for wake from S5 state in your BIOS settings, you are limited to Wake From Standby when using these operating systems in ACPI computers.

For some adapters, the Power Management tab in Intel PROSet includes a setting called Wake on Magic Packet from power off state. Enable this setting to explicitly allow wake up with a Magic Packet* from shutdown under APM power management mode.

In ACPI-capable versions of Windows, the Intel PROSet Power Management tab includes Wake on Magic Packet and Wake on directed packet settings. These controls the type of packets that wake up the system from standby.

Wake on Intel® Ready Access

Intel® Ready Access keeps your network connection active when the rest of your system is in sleep or standby mode, so that content on your system is readily accessible. Requests from other computers will wake up your computer.


Last modified on 7/12/11 11:49p Revision

WINDOWS/note.gif0000755000000000000000000000073211651733270010544 0ustar GIF89a!1J!Z)c1sRR{{{{Z{9sssBBssR99JJfffZZZ))ZZ9ZZ)RRRRRBJJJBBB333)))!!!!,@pH,  f!:(3z<H\! E@S$bQ/G2~C $.$G(c%Gz',sE!rrC $M*L ( +UMG&MBCN#L}G ,ȻB+KB)Yt(E # B*$#һ+s-N#m@@465֘ 09!.(*@ 1A ;WINDOWS/prosetdm.htm0000755000000000000000000000472411714034554011463 0ustar Using PROSet

Intel® PROSet for Windows* Device Manager

Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager.

NOTE:  You must have administrator rights to install or use Intel PROSet for Windows Device Manager.

Installing Intel PROSet for Windows Device Manager

Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You can select Intel PROSet for Windows Device Manager and Advanced Network Services from the Install Options dialog.

Removing Intel PROSet for Windows Device Manager

Use Add/Remove programs from the Control Panel to uninstall Intel PROSet for Windows Device Manager.

Changing Intel PROSet Settings Under Windows Server Core

You can use the command line utility prosetcl.exe to change most Intel PROSet settings under Windows Server Core. Please refer to the help file prosetcl.txt located in the \Program Files\Intel\DMIX\CL directory. For iSCSI Crash Dump cofiguration, use the CrashDmp.exe utility and refer to the CrashDmp.txt help file.

Compatibility Notes

The following devices do not support Intel PROSet for Windows Device Manager


Last modified on 8/04/10 8:12p Revision WINDOWS/pushinst.htm0000755000000000000000000000354711735070116011502 0ustar Microsoft* Windows* Push Install Instructions

Microsoft* Windows* Push Install Instructions

A "Push," or unattended, installation provides a means for network administrators to easily install the drivers on systems that have similar equipment. The following document provides instructions for a basic unattended installation of Microsoft* Windows* that includes the installation of drivers for Intel® Network Adapters.

For 32-bit Microsoft Windows operating systems, see the Push32.txt file in the Apps\Setup\Push\Win32 directory on the Product CD or in the download directory. This file applies to the following operating systems:

 

For x64 Microsoft Windows operating systems, see the Pushx64.txt file in the APPS\SETUP\PUSH\WINX64 directory on the Product CD or in the download directory. This file applies to the following operating systems:


Last modified on 2/22/10 4:47p Revision

WINDOWS/qos.htm0000755000000000000000000000422711735070116010423 0ustar Quality of Service (QoS)

Quality of Service

Quality of Service (QoS) allows the adapter to send and receive IEEE 802.3ac tagged frames. 802.3ac tagged frames include 802.1p priority-tagged frames and 802.1Q VLAN-tagged frames. In order to implement QoS, the adapter must be connected to a switch that supports and is configured for QoS. Priority-tagged frames allow programs that deal with real-time events to make the most efficient use of network bandwidth. High priority packets are processed before lower priority packets.

Under Windows XP and Windows Server 2003, tagging is enabled and disabled using the "QoS Packet Tagging" setting in the Advanced tab in Intel® PROSet. Under Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, tagging is enabled using the "Priority/VLAN Tagging" setting on the Advanced tab.

Once QoS is enabled in Intel PROSet, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.

The supported operating systems have a utility for 802.1p packet prioritization. For more information, see the Windows system help and Microsoft's knowledge base.

NOTE: The first generation Intel® PRO/1000 Gigabit Server Adapter (PWLA 8490) does not support QoS frame tagging.

 


Last modified on 4/22/09 10:46p Revision

WINDOWS/save_dm.htm0000755000000000000000000000712211656574604011251 0ustar Save and Restore

Saving and Restoring an Adapter's Configuration Settings

The Save and Restore Command Line Tool is a VBScript (SavResDX.vbs) that allows you to copy the current adapter and team settings into a standalone file (such as on a floppy disk) as a backup measure. In the event of a hard drive failure, you can reinstate most of your former settings.

The system on which you restore network configuration settings must have the same configuration as the one on which the save was performed.

NOTES:
  • You must have Administration privileges to run scripts. If you do not have Administration privileges, you will not receive an error, the script just will not run.
  • Only adapter settings are saved (these include ANS teaming and VLANs). The adapter's driver is not saved.
  • Restore using the script only once. Restoring multiple times may result in unstable configuration.
  • The Restore operation requires the same OS as when the configuration was Saved.

Command Line Syntax

cscript SavResDX.vbs save|restore [filename]

SavResDX.vbs has the following command line options:

save Saves adapter and team settings that have been changed from the default settings.  When you restore with the resulting file, any settings not contained in the file are assumed to be the default.
restore Restores the settings.
filename The file to save settings to or restore settings from.  If no filename is specified, the script default to WmiConf.txt.

Examples

Save Example

To save the adapter settings to a file on a floppy diskette, do the following.

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:
  4. cscript SavResDX.vbs save a:\settings.txt

Restore Example

To restore the adapter settings from a file on a floppy diskette, do the following:

  1. Open a Windows Command Prompt.
  2. Navigate to the directory where SavResDX.vbs is located (generally c:\Program Files\Intel\DMIX).
  3. Type the following:
  4. cscript SavResDX.vbs restore a:\settings.txt


Last modified on 2/10/10 3:18p Revision

WINDOWS/snmpwin.htm0000755000000000000000000000441211656574604011325 0ustar Simple Network Management Protocol (SNMP)

Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is a network protocol used to manage TCP/IP networks. SNMP-compliant devices (agents) communicate with management applications (consoles) to send alerts and updates and allow configuration changes.

The Intel® SNMP Agent translates event notices from the adapter and sends them to specified SNMP management stations. The SNMP agent provides information on Intel® network adapters as well as information about advanced features, such as teaming and VLANs.

Using the Intel SNMP Agent

Installing the SNMP Agent on Microsoft* Windows* Operating Systems

This utility should only be employed by experienced network administrators. Additional software/services must be installed on your network prior to installing the Intel® SNMP Agent.

To install the SNMP Agent, start the autorun menu from the Product CD or download directory and click Install Drivers and Software. Follow the instructions on the screen.


Last modified on 9/03/07 4:49p Revision

WINDOWS/style.css0000755000000000000000000000450511651733270010764 0ustar .legaldis { font-family: Helvetica; font-size: 7pt; color: #555555; align: justify; } BODY { BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; COLOR: black } .nav {background-color: #ddeeFF} a:link {color:#001060} a:visited {color:#800080} a:hover {color:#800000} H1 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 18pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H2 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 14pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H3 { MARGIN-TOP:14;MARGIN-BOTTOM:0; FONT-SIZE: 12pt; FONT-WEIGHT: bold; COLOR:#0860A8 } H4 { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } H5 { MARGIN-LEFT:14; MARGIN-TOP:2; MARGIN-BOTTOM:0; font-size:10pt; FONT-WEIGHT: bold } P { MARGIN-TOP:10;MARGIN-BOTTOM:0; } blockquote { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } ol { MARGIN-TOP:10;MARGIN-BOTTOM:0; } ul { MARGIN-TOP:0;MARGIN-BOTTOM:0; } li { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; margin-top: 6px; } TH { COLOR: black; FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt; FONT-WEIGHT: bold } TD { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 10pt } .top {MARGIN-LEFT:12;} .contents { FONT-SIZE: 10pt; MARGIN-BOTTOM: 6px; MARGIN-LEFT: 20px; MARGIN-TOP: 6px; TEXT-INDENT: -20px } .gui { FONT-SIZE: 9pt; FONT-WEIGHT: bold } .inentry { MARGIN-BOTTOM: 3px; MARGIN-TOP: 0px; WORD-SPACING: 0px } .monospace { FONT-FAMILY: Courier New, Courier; FONT-SIZE: 10pt } .numlst { LIST-STYLE: decimal; MARGIN-BOTTOM: 8px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; TEXT-ALIGN: left; TEXT-INDENT: 0px; WORD-SPACING: 0px } .r { font-size: 11pt } .small { FONT-FAMILY: Arial, sans-serif; FONT-SIZE: 7pt; color:#505050} .warning { FONT-STYLE: italic; FONT-WEIGHT: bold } .toc_head { FONT-SIZE: 10pt; FONT-WEIGHT: bold; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 0px; MARGIN-TOP: 6px; TEXT-INDENT: 0px; } .toc_level1 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 15px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } .toc_level2 { FONT-SIZE: 9pt; MARGIN-BOTTOM: 1px; MARGIN-LEFT: 30px; MARGIN-TOP: 1px; TEXT-INDENT: -10px } WINDOWS/support.gif0000755000000000000000000003157611651733270011325 0ustar GIF89a]h!"9)$9J,Z B R)j)R% X& e)(s!4k#2x1 k1&X1JMwuC6~9;f37j.\8%׶}$).fdӫ_m: ҅qըqaI[1ĖlpG uQW!Qd9ކvEt #81TL37Hae1`)(IroP"YBT!υT"qI}(TVOiH"3McΙᆋ¶]2833h&cv!b r$1%<3 $nxY'eqFRZ)餔VF<3Hc9|ƘllLؗ1fl3_v9z>L*c1KBxdi6lP.Ęrnaa9}y+T0b .z91IvgGU C!zJK4H"ta / w4RSx8-(Q98 3Ċ;>#hAe0H8#nA 7 .;#OH>[ҸUDBHUa-?%Agdx HJ T-pxcG#(#Aژ"btАQ]]E IH"8$@3džhLh!;Z<A01pƸx 㨑8UI˼Qxm(1 2 R&7)ǒ@Wb&H\!"yxȥ8!orH-,8 '$"X21zEcb$ -9F[Ӝ,dQ =z扅z^WpB 8Els IN3lB*:TF5a?BbG;T?@A ^TJqkt#P:uh!p!2|wѻ eHMOAO8(6a5zB`!` +)́l HH9z (3"01Jͫ^iFBK5!AT3ƍi@ʉdyq9Y`C+H8e{MjibH8Wqts Ad@("C;p+QqF `_p`` ؀ؐȉِ Jv/(ِ2P܀[8 TDE7yq P Ҩ `bu0vxqp % e |73Yxhȉ(+h  yѐ 2   ^]0}!-HLX @ bi0] `m@}FP#V `0&g (v0q\gs  p! e +A6p1\@ȏ P*9  *` *p **\) 0%لM8 Q:P[PHG R$PGP yPfsv^h'~XuG} 1H Op.-=0 ` p؉ Xz`  򀙹\KnlQ$Ii0xw E<@lp@ 0l09I8 xS&v(@qōۘi)DEpV $ gj` ЏzI_vZ  yTw+׈ x;50Awb Ds mPXx'&ʁF\˵qyv5GUGEBV'WtEpIi0'ŰxYmڦP}YsJuJ}^ K(Jp`p7fC7 P iBH^jJ&ʆ`*W` `Y|H QZ/fphpӯ PP gq1p *Jvtژ i]!]0iMyIr,°BFɑѭW[9 Y\Kf9 T@Q |{-隡p1:@'ߡC~1^Ph5i&=ڰ ԉ.q* P `@g_ eлfr`qq@p#[/o46{*iK0!YHp D盾]*J! L @Z++^k]wZ) < )`o; ,+jI*'p9pbp% l020po` p^P[&ć uXK!Q|C @Tt _g9|kAX̠&V)Ipʂ|aL`pk+AHQ2K㰿 Ȍȑ! 09;P  L+PH|Ѱ ]Q*P2p3 2I0PgpdEQL,$li|ibƅ:|_л[ Ǜ 0j Q؄oJ)xz,PzpȐ2aɊʈl7`ɞi;p{** Cl-\,؛ -m <iȘ]r,$ғ^@Ƭ̺b.Ps0ZhE9 i}Pt& K, <[  1 GQ9RS epq\okk*+q ݊NHа9lVIK M ҋEʩ} \{|ÜQL1MV0TKL!9];Gƭ2ZJLJR}+΀m5:aE Ac1 0 0 %N(paPP9\gz H_ wglўfjh,ċ݊IΩKɽ-9$i:] Y={l4^( ˾'"WXa5>ioj0#A kD$^bTp  \9(\\46m wvؤ Yg2_Puջg0'rp;dm' mℙꙹٳ O]3a+K`f&ik,:NjʎZN|0j)IpZ2m" t$ sP}҂0 zV>R3~r0 :wǻo`rot tl"WŚМ] ۮ"L4Na*  )hG4HOG/d;̠i2@Jx?Uk-7vI(tķAp8ˆ[)y_tr(%{T f,xȁ!CbF +"W;q}|-p}1HhJ1V]nP2\`nBcK31BU \*qRЁXA,A Јxp׻?ftWD')91kht2!ǘ2V-pp3!B1A2F dpMr/a XplcŔ ipE8,ssc(bÆ[ސ'!Wh%CcgZ7 3$(X3x̸41|׼0}p4!pӸ| cgx,@`l|c[; FQxiKo$pɸ? {ZzmuHޅS4_^4':!FE.<O7Ip9:\5)V@׮j4| d  #U<;%S3܀5Qp 73uG3#HM>LSo=^W`z5w{ hO1!C}Dp tXȺ [> 䳇哇OS tzx (=; zXp rC;B 7s`2g`6hM9),zch%@# a r xhyv6> =L  @cx'O+I$ 1c"t@A8pp M893bz/tM9]tT18; );Jkės8hVxh ck?p?50 E, 3?+%MgHx9/?8512 gZHЅJ49-Xm<R=RUxՅMIeԑnX7&$I KRTsHpWY=SuR؇T^V%<̺Ľ % ЙP>Xo4nxӱy K{>eU&jmhy+L6@L!-""X3!@ȧ}9@6`1hE-!rӱ#X- AN]T&?}XxHA -1J\ H\NAsG},թ\{\C }=Y\ܣ٨Ľ- pBwQR JsK+їr)^H7-!E̲[q!W|[+"83CXChOש}^b=!85\ \Mm\:j܅A)TlCӗ``a%#QXٟ]NXYTF`~tU0EUPϜE8Yħm^9^%VJF گ="%[M[%*^"8!ai:?7 7,}X_:Sԭ:mؑITxܘXO=T TVm\څ,X1:G7T]ʥa%G&T Ƈ B|Ty&dZ|b͈EK- RU!+cI`Cޱ+,k56o5HȋB5(x/˂/}:@X3t,c=~vYGgo\`@d}4:(:ۅ%Go}w]U:uȈPf`$LhQH0ɬsIiLIEϖi"蟞Bc%;!>yvcbyNjfzDg]xF/ #l^b-Ɓ 6X9]H*ȁG.C5"f7,M} 癨p:bޤĆ#$M*t xl] <p8{`Nlfj ATClˉav^,x04iHfjv%W-pXBq.O)32xcEFljj m#򮐛"X˦my,=fՌCގM;V~@bf? H.6i1-yx@ތ=mq&)8nӡ"vw0555KVfh.pRqk ߴ 610 Ca('H4#H4K÷r/O>1䕾Z" s%SQ3&ssqCЍ&`.I =M6)q7I/tLDF^f^FJc=8QSg%[G#AdiWcJkM?vd>V!f^n2bfw0Tߟ˔hn]dt*\\vISDMvye!N8뱺-(7Eb`'xWxbHׅC-pE @`#B+dy@^óSzy/AFV7x->35 G??. ЀH+}dryz,yJym!p&5Wj]8>upB8zݔ4fgZz{zE,"b~3rs9?cxf̲?{ȟF5x3$8J̸{?pz,v[goqvT/@{/yHI(5`Uͤw6v~W,_'| >1t^Ǐ;F9AxJxIc45 Y,h „ 2l!Ĉ'RH^={7jc= a$Ɣ3ڋ'0u=4(1E*ib)l\ =ŬZ꒰K.ZQEjײm-ܸrureǒOQ]ѣČÆMlhC&ĦJ {ңIXͥ"aٱ M6ܺw[};I)%x2@>$ǐ!7(MpUXӂuCӯo>~=N2U 7.8=ƆQ4\$ ZJV<0 L,"@]4NSV'.E4 HtAxD#œKKYŕWx->fbXR@"'(j\ Yc"fl}oJ5qQ<2ua]CC(p)\p#`*).D H^AѨM=`1c4("Lϐ90K,K*cd80qriK A-Z{c*2Pr^sjf{/guJ,bD/@FD1DFxZ0sN` K8*vmKU}6ib?b$4]>L 0@ZK9oPrl3t|j1ߵԬԉ|]"@<'Fd2ġCu#hu(zuCcU4*"Nc(:NٌX {8EHfBǕ(څLlGRt&ArN 6L}*T*թRV*Vխr^*X*ֱf=+X/qMLuЄTrQ Vjj_:Vj]JվO(d#+Y)qI,[TrOeٵ-jSڸL)!.Z;WINDOWS/support.htm0000755000000000000000000000206611651733270011340 0ustar Intel Customer Support

Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information.

Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

 


Last modified on 5/12/10 3:26p Revision

WINDOWS/thermal.htm0000755000000000000000000000405211727655656011274 0ustar Thermal Monitoring

Thermal Monitoring

Adapters and network controllers based on the Intel® Ethernet Controller I350 (and later controllers) can display temperature data and automatically reduce the link speed if the controller temperature gets too hot.

NOTE: This feature is enabled and configured by the equipment manufacturer. It is not available on all adapters and network controllers. There are no user configurable settings.

Monitoring and Reporting

Temperature information is displayed on the Link tab in Intel® PROSet for Windows* Device Manger. There are three possible conditions:

  • Temperature: Normal
    Indicates normal operation.
  • Temperature: Overheated, Link Reduced
    Indicates that the device has reduced link speed to lower power consumption and heat.

    NOTE: Devices based on the Intel® X540 Ethernet Controller and Intel® 82599 10 Gigabit Ethernet Controller do not support link speed reduction.

  • Temperature: Overheated, Adapter Stopped
    Indicates that the device is too hot and has stopped passing traffic so it is not damaged.

If either of the overheated events occurs, the device driver writes a message to the system event log.

WINDOWS/vlan.gif0000755000000000000000000001066311656574604010554 0ustar GIF89a*?*?*_*_U*_*_**U****U****U****U*ߪ***U**UUUUUUUUUUU?U?UU?U?U_U_UU_U_UUUUUUUUUUUUUUUUUUUߪUUUUUUUU??U??__U__UUUUߪUUU??U??__U__UUUUߪUUU??U??__U__UԟԟUԟԟԿԿUԿԿUߪUUU??U??__U__UUUUߪU3fUUUUߪU**U****U***?*?U𠠤, H*\ȰÇ#JHŋ3jȱǏ CIѐ3raʕZL!6q@C0=J`O$*]^Z %(^ V/kU,ٰP|ziE)@ 1Ĵ߿ hd jqW1 hbƐ% `\ 8XӅO &#i^˞M`TWDVpdg|[\bAZ ]:"Wl]N6_}5bKOy]^}6ހ_!Uyu ]IulE(H$`yTW1 &y=҃NaS Ձ r+$7cH`0 S|)fe-$W#m _Qs pUyB$h浟Ox+"˦2~_^ۖ "<0ho `é{kllNgJ2CJFQfPa )UxO\ʰa t%:d]`0S֭d]HxD @]ԡM¯'4ROu5لA >dp(6PɵBAt6Ʈm k6Xgh{ᵭ!GWf^gu^ieWYN,暧˂}ItIؠ͞lrמ6Jm'|r><$WogO:Ο }R/r/ /#o_|s_'0TKwv # Ab@*C`>Mp# 23%A"-ta(C pG50?Pȑ~s`> 0Lh(ZPQDaEOըOрod#58C8)>2gxHB DT&$C:R##Iɿ<$%LyS 8kq_d񢧔E-rW@y'U2I1^N+@ /i%L@e%B+Kd.Eiiq{ .vhc g.EI%Xh\^ЩNA4Ж@h+\sx"sZCRxG lq<%jXeD%QH8W:ֱYJG?{.Q>HZѩCЇ$C>Q&cai]F^JT:ҡD\fy*ŸMMMm,Y~zQi4?jXֱhfmb/í-Hǣf\Nİ gV(&cؿNIcS.%ϡ2( l" \V!K2،M‚5y-B QWďnၘP7V֭n79c-ɴ.PY;nKIIeJQtHBcנO?561I%[H0 ί@` ωrxR;9Kʦօ+d҂*7I:6O*u<ϥʕ!묒lxŷT" bgaqUc&T:2R|XdϬy׸6Ao!6&9\]"xnW> td7zd0˸ 9%R7&5 LPK6 iK;8J z61푫 D,<dRm좗b qi[a#x.q P~/>xxכ=u]KȖKhNtڔ^4dN.xE6k9p崰YV )fׄD;ڮwg]{w*ؒkNu棧ܲES7͙/lP:8yd;1A},}D xWvl]T.ZG|)nwDaұjm[P*_о,[ⰖyOLÊI ;Oֶ; ]ѷL8NPPAy3w^,UJj 1PMQdX.% g :m7h\(cH*ߓL4M$M啈.Zx(WbZ%_Q2`O"bgz}(IbRQfR"R\vK|]6QARJeTңSaU6mW{7r%V9ar(QqfhVHz׀k=@9^rvxKw ;b/&(8؊9ItD.XȊ3Z j=SՑlQUV,Hc< IA"I$:>sePFsĈ,=|w;"WOE3dN]ZE=7GRr L铻 QxLX,fmmO֙\J%N)$NK\\P][fxX8[OH#X:1C4% Wo AS]ahQ:6yN8y8xRؗqj!qY-+7pS:5$bD\pQed%E?VW5rCeΈK=Z!sLet<4MGtU?Cfux)6:|:_HOk&$g*xBZ刡{JjfLX'b"kfg(d#ZAY'vi&9(OuV!کLQF9)^w)tfK6uPj]ezw[ӧbg@[x3av{[{};WINDOWS/vlwin.htm0000755000000000000000000001140111711606312010745 0ustar Join a Virtual LAN under Windows OS

Virtual LANs

The term VLAN (Virtual Local Area Network) refers to a collection of devices that communicate as if they were on the same physical LAN. Any set of ports (including all ports on the switch) can be considered a VLAN. LAN segments are not restricted by the hardware that physically connects them.

VLANs offer the ability to group computers together into logical workgroups. This can simplify network administration when connecting clients to servers that are geographically dispersed across the building, campus, or enterprise network.

Typically, VLANs consist of co-workers within the same department but in different locations, groups of users running the same network protocol, or a cross-functional team working on a joint project. 

 

By using VLANs on your network, you can:

  • Improve network performance

  • Limit broadcast storms

  • Improve LAN configuration updates (adds, moves, and changes)

  • Minimize security problems

  • Ease your management task

Other Considerations

  • To set up IEEE VLAN membership (multiple VLANs), the adapter must be attached to a switch with IEEE 802.1Q VLAN capability.

  • A maximum of 64 VLANs per network port or team are supported by Intel software.

  • VLANs can co-exist with teaming (if the adapter supports both). If you do this, the team must be defined first, then you can set up your VLAN.

  • The Intel PRO/100 VE and VM Desktop Adapters and Network Connections can be used in a switch based VLAN but do not support IEEE Tagging.

  • You can set up only one untagged VLAN per adapter or team. You must have at least one tagged VLAN before you can set up an untagged VLAN.

CAUTION: When using IEEE 802 VLANs, settings must match between the switch and those adapters using the VLANs.

Microsoft* Load Balancing and Failover (LBFO) teams

Intel ANS VLANs are not compatible with Microsoft's LBFO teams. Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team, as this may cause system instability.

 

Configuring VLANs in Microsoft* Windows*

In Microsoft* Windows*, you must use Intel® PROSet to set up and configure VLANs. For more information, select Intel PROSet in the Table of Contents (left pane) of this window.

Note: If you change a setting under the Advanced tab for one VLAN, it changes the settings for all VLANS using that port.

In most environments, a maximum of 64 VLANs per network port or team are supported by Intel PROSet.

Configuration notes for Microsoft Hyper-V*

If you want to have VLANs on the parent partition and on any child partitions, each child partition's VLAN must have the same VLAN ID as a VLAN on the parent partition.


Last modified on 6/17/09 9:47p Revision

WINDOWS/warranty.htm0000755000000000000000000001324011651733270011467 0ustar Limited Lifetime Hardware Warranty

Limited Lifetime Hardware Warranty

Returning a defective product

From North America:

All other locations:

Intel Adapter Money-back Guarantee (North America Only)

Limitation of Liability and Remedies


Last modified on 7/23/02 10:42a Revision

WINDOWS/wminicdm.htm0000755000000000000000000000763511656574604011453 0ustar WMI NIC Provider

Intel® Network Adapters WMI Provider


Overview

The Intel® Network Adapters Windows Management Instrumentation (WMI) Provider enables WMI-based management applications such as Intel® PROSet for Windows Device Manager to monitor and configure the status of PCI network adapters. Intel Network Adapters WMI Provider uses WMI, a user-level instrumentation technology for the Microsoft Windows* platform.

WMI is a middleware layer that allows measurement and instrumentation information to be collected from kernel mode data providers. This information can then be provided to local or remote user-mode data consumers through the use of a common set of interfaces (Web-based Enterprise Management called WBEM). WMI is a data-independent pipeline between the data consumer and the data provider that makes no assumptions about the format of the data.

A guide is available on this distribution, which contains detailed information on the Intel Network Adapters WMI Provider, also referred to as Network Configuration Services (NCS2) WMI Providers. This guide is located in \APPS\WMI\DOCS. The technical reference paper describes the external view of NCS2 WMI providers so WMI-based management applications could use it to manage the network configuration for the Intel adapters.


System Requirements

  • Any Intel® PRO/100, Intel® Gigabit Network Adapter, or Intel® 10GbE Network Adapter

  • related driver software

  • a supported Microsoft* Windows* operating system. Please refer to the System Requirements page for a list of supported operating systems.

The Intel Network Adapters WMI Provider supports all Intel PRO/100, Gigabit, and 10GbE network adapters.


Installation

The Intel Network Adapters WMI Provider are installed as part of Intel® PROSet for Windows Device Manager software installation. See the Installing Intel PROSet for Windows Device Manager section for more information on how to install Intel PROSet for Windows Device Manager.

Intel PROSet for Windows Device Manager Typical Setup Type registers the Intel Network Adapters WMI Provider into the root\IntelNCS2 namespace.


Supported Standards

The Intel Network Adapters WMI Provider supports the standards based CIM 2.6 specification.


Known Issues

DMI-SNMP Instrumentation

This Intel Network Adapters WMI Provider cannot jointly operate with the Intel® DMI-SNMP instrumentation.

Missing Instances under Microsoft Windows Vista*

You must elevate (i.e., embed a manifest file) in your application in order to access all of the Intel WMI classes.


Last modified on 6/05/09 11:26a Revision