To successfully install or uninstall the drivers or software, you must have
administrative privileges on the computer completing installation.
NOTES:
If you are using an Intel®
10GbE Server Adapter and an Intel Gigabit adapter in the same
machine, the driver for the Gigabit adapter must be running with the
Gigabit drivers found on this Intel software CD (or respective download
package).
If you are installing a driver in a
computer with existing Intel adapters, be sure to update all the adapters
(and additional adapter ports, if applicable) with the same Intel driver
and supplemental software. This ensures that all adapters
will function and interoperate correctly.
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.
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.
If the Found New Hardware Wizard screen is displayed, click
Cancel.
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.
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.
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.
If the Found New Hardware Wizard screen is displayed, click
Cancel.
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.
These instructions uninstall the drivers for all Intel network adapters in a
system.
From the Control Panel, double-click Add/Remove
Programs.
Select Intel(R) Network Connections Drivers.
Click Add/Remove.
When the confirmation dialog displays, click OK.
Last modified on 6/05/09 11:38a Revision
WINDOWS/dupwindm.htm 0000755 0000000 0000000 00000011565 12001223204 011434 0 ustar
Configuring Speed and Duplex in Windows*
Set Up Speed and Duplex
In addressing speed and duplex configuration issues, you need to distinguish between copper-based adapters and fiber-based adapters.
In the default mode, an Intel® Network Adapter using
copper-based 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. Your link partner must match the setting you choose.
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.
An Intel® Network Adapter using fiber-based connections, however, will not attempt auto-negotiate with its link partner since those 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.
Navigate to the Device Manager.
Open Properties on the adapter you would like to
configure.
Click the Link Speed tab.
Select the appropriate speed and duplex from the Speed and
Duplex pull down menu.
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:
10 Mbps or 100 Mbps Full duplex (requires a full
duplex capable link partner set to full duplex). The adapter can send and receive
packets at the same time. You must set this mode manually.
10 Mbps or 100 Mbps Half duplex (requires a link
partner set to half duplex). The adapter performs one operation at a time;
it either sends or receives. You must set this mode manually.
Auto-Negotiation 1000 Mbps. The adapter only
advertises gigabit speed at full duplex.
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:
10 Mbps or 100 Mbps Full duplex (requires a full
duplex capable link partner set to full duplex). The adapter can send and receive
packets at the same time. You must set this mode manually.
10 Mbps or 100 Mbps Half duplex (requires a link
partner set to half duplex). The adapter performs one operation at a time;
it either sends or receives. You must set this mode manually.
Last modified on 12/30/09 3:51p Revision
WINDOWS/hotwin.htm 0000755 0000000 0000000 00000003523 11656603624 011137 0 ustar
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.
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:
Jumbo frames are not supported in multi-vendor team
configurations.
Supported protocols are limited to IP (TCP, UDP).
Jumbo frames require compatible switch connections that
forward Jumbo Frames. Contact your switch vendor for more information.
When standard sized Ethernet frames (64 to 1518 bytes) are
used, there is no benefit to configuring Jumbo Frames.
The Jumbo Frames setting on the switch must be set to at least 8 bytes larger than the adapter
setting for Microsoft* Windows* operating systems, and at least 22 bytes larger for
all other operating systems.
The Intel® PRO/1000 PL Network Connection supports
jumbo frames in Microsoft* Windows* operating systems only when Intel® PROSet
for Windows Device Manager is installed.
The following devices do not support jumbo frames larger
than 4096 bytes:
Intel® 82577LM Gigabit Network Connection
Intel® 82578DM Gigabit Network Connection.
The following devices do not support jumbo frames:
NOTE: Jumbo frames are not
supported in multi-vendor team configurations.
Open Microsoft* Windows* Device Manager.
Open Properties on your adapter.
Click the Advanced tab.
Select Jumbo Frames from the list of advanced features.
Set your desired packet size (based on network capability).
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.
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
configured to Auto Detect speed and
connected to a link partner that can auto-negotiate speed
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.
Windows Vista*, Windows 7, 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.
Performance profiles allow you to quickly optimize the performance of your
Intel Ethernet Adapter. Selecting a performance profile will automatically
adjust some Advanced Settings to their optimum setting for the selected
application. For example, a standard server has optimal performance with only
two RSS (Receive-Side Scaling) queues, but a web server requires more RSS queues
for better scalability.
You must install Intel® PROSet for Windows Device Manager to use
Performance profiles. Profiles are selected on the Advanced tab of the adapter's
property sheet.
Profile Descriptions
Standard Server – This profile is optimized for typical servers.
Web Server – This profile is optimized for IIS and HTTP based web servers.
Virtualization Server – This profile is optimized for Microsoft’s Hyper-V virtualization environment. Selecting this profile will disable Data Center Bridging (DCB).
Storage Server – This profile is optimized for Fibre Channel over Ethernet
and iSCSI over DCB performance. Selecting this profile will disable SR-IOV and VMQ.
Storage + Virtualization – This profile is optimized for a combination of storage and virtualization requirements.
Low Latency – This profile is optimized to minimize network latency.
NOTES:
Not all profiles are available on all operating systems
or with all adapters.
If you have selected the Virtualization Server profile or the Storage + Virtualization profile, and you uninstall the Hyper-V role, you should select a new profile.
Supported Adapters
Performance Profiles are supported on Intel® 10GbE adapters.
Teaming Considerations
When you create a team with all members of the team supporting Performance
Profiles, you will be asked which profile to use at the time of team creation.
The profile will be synchronized across the team. If there is not a profile that
is supported by all team members then the only option will be Use Current
Settings. The team will be created normally. Adding an adapter to an existing
team works in much the same way.
If you attempt to team an adapter that supports performance
profiles with an adapter that doesn't, the profile on the
supporting adapter will be set to Custom Settings and the team will be created
normally.
Last modified on 8/11/10 7:48p Revision
WINDOWS/prosetdm.htm 0000755 0000000 0000000 00000004724 11714043510 011453 0 ustar
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
Intel® 82552 10/100 Network Connection
Intel® 82567V-3 Gigabit Network Connection
Last modified on 8/04/10 8:12p Revision
WINDOWS/pushinst.htm 0000755 0000000 0000000 00000002432 11744272404 011476 0 ustar
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.
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.
Last modified on 2/22/10 4:47p Revision
WINDOWS/qos10g.htm 0000755 0000000 0000000 00000003054 12135717420 010731 0 ustar
Quality of Service (QoS)
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.
To implement QoS, the adapter must be connected to a switch that
supports and is configured for 802.1p QoS.
Tagging is enabled and disabled using the "QoS Packet Tagging"
field in the Advanced tab in Intel® PROSet.
Once QoS is enabled in Intel PROSet, you can specify levels of priority based
on IEEE 802.1p/802.1Q frame tagging.
Microsoft* Windows* Server*
2008 has a utility for 802.1p packet prioritization. For more
information, see the Windows system help and Microsoft's knowledge base.
Last modified on 4/24/13.
WINDOWS/save_dm.htm 0000755 0000000 0000000 00000011027 12147427264 011243 0 ustar
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
USB drive) 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.
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.
Note: The static IP address and WINS configuration are saved to separate files (StaticIP.txt and WINS.txt). You cannot choose the path or names for these files. If you wish restore these settings, the files must be in the same directory as the SavResDX.vbs script.
/bdf
If you specify /bdf during a restore, the script attempts to restore the configuration based on the PCI Bus:Device:Function:Segment values of the saved configuration. If you removed, added, or moved a NIC to a different slot, this may result in the script applying the saved settings to a different device.
Notes:
If the restore system is not identical to the saved system, the script may not restore any settings when the /bdf option is specified.
Virtual Function devices do not support the /bdf option.
Examples
Save Example
To save the adapter settings to a file on a floppy diskette, do the
following.
Open a Windows Command Prompt.
Navigate to the directory where SavResDX.vbs is located
(generally c:\Program Files\Intel\DMIX).
Type the following:
cscript SavResDX.vbs save e:\settings.txt
Restore Example
To restore the adapter settings from a file on a floppy diskette, do the
following:
Open a Windows Command Prompt.
Navigate to the directory where SavResDX.vbs is located
(generally c:\Program Files\Intel\DMIX).
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
Before you install the Intel SNMP Agent on a computer, you must install SNMP on the computer. See your operating system documentation for more information.
To use the Intel SNMP Agent with an SNMP management application, you must first compile the Intel MIB
(Management Information Base) into the management application's database.
This allows the management application to recognize and support the adapter.
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.
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.
WINDOWS/vlan.gif 0000755 0000000 0000000 00000010663 11656603624 010547 0 ustar GIF89a *?*?*_ *_U*_*_* *U*** *U*** *U*** *U*ߪ** *U**U U UU U U U UU U U? U?UU?U?U_ U_UU_U_U UUUUU UUUUU UUUUU UUUߪUU UUUU U U ? ?U??_ _U__ U U U Uߪ U U U ? ?U??_ _U__ U U U Uߪ U U U ? ?U??_ _U__ Uԟ ԟUԟԟԿ ԿUԿԿ Uߪ U U U ? ?U??_ _U__ U U U UߪU3f U U U U ߪ U * * U* * * * U* * *? *?U𠠤 , H*\ȰÇ#JHŋ3jȱǏ C Iѐ3raʕZL!6q@C0=J`O$*]^Z %(^ V/k U,ٰP|ziE)@ 1Ĵ߿
hd jqW1
hbƐ% `\ 8XӅO
&#i^˞M`TWDVpdg|[\bAZ
]:"Wl]N6_}5bKOy]^ }6ހ_!Uyu ]Iu lE(H$`yTW1
&y= ҃NaS Ձ r+$ 7cH`0
S|)fe-$W # m
_Qs pUyB$h浟Ox+"˦2~_^ۖ " <0ho ` é{kllNgJ2CJ FQfPa )Ux O\ʰ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`>
0L h(ZPQDaEOըOрod#58C8)>2gxHB DT&$C:R##Iɿ<$%Ly S 8kq_dE-rW@y'U2I1^N+@ /i%L@e%B+Kd.Eiiq{ .v hc g.EI%Xh\^ЩNA4 Ж@ h+\sx"sZCRxG lq<%j XeD%QH8W:ֱYJG?{.Q>HZѩCЇ$C>Q&cai]F^JT:ҡD \fy*ŸMMMm,Y~zQi4?jXֱhfmb/í-Hǣf\Nİ
gV(&cؿN IcS.%ϡ2( l" \V!K2،M5y-B QWďnၘP7V֭n79c-ɴ.PY ;nKIIeJQt HBcנO?561I %[H0 ί@`
ωrxR;9Kʦօ+ d҂*7I:6O*u<ϥʕ!묒lxŷT"
bgaqUc&T:2R|XdϬy6Ao!6&9\]"xnW>
td7 zd0˸ 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:8 yd;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$:>seP FsĈ,= |w;"WOE3dN]ZE=7GRr L铻
QxLX,fmmO֙\J%N)$NK\\P][fxX8[O H#X:1C4%
Wo
AS]ahQ:6yN8y8xRؗqj!qY-+7pS:5$bD\pQed%E?VW5rCeΈK=Z!sLet<4MGt U?Cfux)6:|:_HOk&$g*xBZ刡{ JjfLX'b"kfg(d #Z AY'vi&9(OuV! کLQF 9)^w)tfK6 uPj]ez w[ӧbg@[x3av{[{} ; WINDOWS/vlwin10g.htm 0000755 0000000 0000000 00000012163 12015376214 011266 0 ustar
Virtual LAN under Windows
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 you do this,
the team must be defined first, then you can set up your VLAN.
You can set up only one untagged VLAN per network port 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.
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.
Notes:
A maximum of 64 VLANs per network port or team are supported by Intel PROSet.
If you change a setting under the Advanced tab for one VLAN, it changes the settings
for all VLANS using that port.
ANS VLANs are not supported on adpaters and teams that have VMQ enabled. However,
VLAN filtering with VMQ is supported via the Microsoft Hyper-V VLAN interface.
For more information see Microsoft Hyper-V virtual NICs on teams and VLANs.
You can have different VLAN tags on a child partition and its parent.
Those settings are separate from one another, and can be different or the same.
The only instance where the VLAN tag on the parent and child MUST be the same is if
you want the parent and child partitions to be able to communicate with each other
through that VLAN. For more information
see Microsoft Hyper-V virtual NICs on teams and VLANs.
Intel warrants to the original owner that the adapter product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in the process of being installed or improperly used.
THE ABOVE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.
This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as set forth below, or refund your purchase price provided that you deliver the adapter product along with a Return Material Authorization
(RMA) number (see below), along with proof of purchase (if not registered), either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge.
Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the right to replace discontinued adapter products with an equivalent current generation adapter product.
Returning a defective product
From North America:
Before returning any adapter product, contact Intel Customer Support and obtain a Return Material Authorization
(RMA) number by calling +1 916-377-7000.
If the Customer Support Group verifies that the adapter product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the adapter product. Intel cannot accept any product without an RMA number on the package.
All other locations:
Return the adapter product to the place of purchase for a refund or replacement.
Intel Adapter Money-back Guarantee (North America Only)
Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase. Intel guarantees that it will accept returns under this policy and refund the original purchase price to customers purchasing directly from Intel.
Limitation of Liability and Remedies
INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY, REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.
Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you.
Critical Control Applications: Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for example only, safety or health care control systems, nuclear energy control systems, or air or ground traffic control systems) by Licensee or
Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or
Sublicensees.
Software: Software provided with the adapter product is not covered under the hardware warranty described above. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.
Note: If you are a consumer under the Australian Consumer Law, this warranty does not apply to you. Please visit Australian Limited Lifetime Hardware Warranty to view the limited warranty which is applicable to Australian consumers.
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.
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.
