FreeBSD* Driver for the Intel® Ethernet 10 Gigabit Server Adapters
NOTES: This release includes the 10 gigabit ixgbe FreeBSD Base Driver
for Intel Ethernet 10 Gigabit PCI-Express Server Adapters. All 82599, 82598EB
and X540-based network connections
require the ixgbe driver. All other network connections require the
ixgb driver. The ixgb driver can be
downloaded at:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ixgb/.
First identify
your adapter. Then follow the appropriate steps for building,
installing, and configuring the appropriate driver.
Identifying Your Adapter
To verify that your Intel adapter is supported, find the board ID number on the
adapter. Look for a label that has a barcode and a number in the format of
123456-001 (six digits hyphen three digits).
For more information on how to identify your adapter, go to the Adapter &
Driver ID Guide at:
To verify that your Intel adapter is supported, find the board ID number on the
adapter. Look for a label that has a barcode and a number in the format of
123456-001 (six digits hyphen three digits).
For more information on how to identify your adapter, go to the Adapter &
Driver ID Guide at:
If your 82599-based Intel
Ethernet Network
Adapter came with Intel optics, or is an Intel® Ethernet Server
Adapter X520-2, then it only supports Intel optics and/or the
direct attach cables listed below.
When 82599-based
SFP+ devices are connected back to back, they should be set to
the same Speed setting via Ethtool. Results may vary if you mix
speed settings.
Supplier
Type
Part Numbers
SR Modules
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
FTLX8571D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDDZ-IN1
LR Modules
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
FTLX1471D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDDZ-IN1
The following is a list of 3rd party SFP+ modules and direct attach
cables that have received some testing. Not all modules are applicable to
all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
Finisar
DUAL RATE 1G/10G SFP+ SR (No Bail)
FTLX8571D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ SR (No Bail)
AFBR-703SDZ-IN1
Finisar
DUAL RATE 1G/10G SFP+ LR (No Bail)
FTLX1471D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ LR (No Bail)
AFCT-701SDZ-IN1
Finisar
1000BASE-T SFP
FCLF8522P2BTL
Avago
1000BASE-T SFP
ABCU-5710RZ
82599-based adapters support all passive and active limiting direct
attach cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4
specifications.
Laser turns off for SFP+ when ifconfig down
"ifconfig down" turns off the laser for 82599-based SFP+ fiber adapters. "ifconfig
up" turns on the later.
82598-BASED ADAPTERS
NOTES:
Intel Ethernet Network
Adapters that support removable optical modules only support their
original module type (i.e., the Intel 10 Gigabit SR Dual Port
Express Module only supports SR optical modules). If you plug in a
different type of module, the driver will not load.
Hot Swapping/hot plugging optical modules is not supported.
Only single speed, 10
gigabit modules are supported.
LAN on Motherboard
(LOMs) may support DA, SR, or LR modules. Other module types are not
supported. Please see your system documentation for details.
The following is a list of SFP+ modules and direct attach cables that
have received some testing. Not all modules are applicable to all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
82598-based adapters support all passive direct attach cables that comply
with SFF-8431 v4.1 and SFF-8472 v10.4 specifications. Active direct attach
cables are not supported.
THIRD PARTY
OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE LISTED ONLY FOR THE PURPOSE
OF HIGHLIGHTING THIRD PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY,
AND ARE NOT RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF ANY THIRD
PARTYS PRODUCT BY INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE
BY ANY THIRD PARTY AND THE THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE
INFORMATION REGARDING CERTAIN OPTIC MODULES AND CABLES WITH THE ABOVE
SPECIFICATIONS. THERE MAY BE OTHER MANUFACTURERS OR SUPPLIERS, PRODUCING OR
SUPPLYING OPTIC MODULES AND CABLES WITH SIMILAR OR MATCHING DESCRIPTIONS.
CUSTOMERS MUST USE THEIR OWN DISCRETION AND DILIGENCE TO PURCHASE OPTIC
MODULES AND CABLES FROM ANY THIRD PARTY OF THEIR CHOICE. CUSTOMERS ARE
SOLELY RESPONSIBLE FOR ASSESSING THE SUITABILITY OF THE PRODUCT AND/OR
DEVICES AND FOR THE SELECTION OF THE VENDOR FOR PURCHASING ANY PRODUCT. THE
OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY
EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR SELECTION OF VENDOR BY CUSTOMERS.
Building and Installation
NOTE: You must have kernel sources installed in order to compile the driver module.
In the instructions below, x.x.x is the driver version as indicated in the name of the driver
tar file.
ixgbe instructions
Move the base driver tar file to the directory of your choice. For
example, use /home/username/ixgbe or /usr/local/src/ixgbe.
Untar/unzip the archive:
tar xfz ixgbe-x.x.x.tar.gz
To install man page:
cd
ixgbe-x.x.x
gzip -c ixgbe.4 > /usr/share/man/man4/ixgbee.4.gz
To load the driver onto a running system:
cd ixgbe-x.x.x/src
make load
To assign an IP address to the interface, enter the following:
ifconfig ix<interface_num> <IP_address>
Verify that the interface works. Enter the following, where <IP_address> is
the IP address for another machine on the same subnet as the interface that is
being tested:
ping <IP_address>
If you want the driver to load automatically when the system is booted:
cd ixgbe-x.x.x/src make make install
Edit /boot/loader.conf, and add the following line:
ixgbe_load="YES"
OR
compile the driver into the kernel (see item 8).
Edit /etc/rc.conf, and create the appropriate ifconfig_ixgbe<interface_num>
entry:
Edit the kernel configuration file (i.e., GENERIC or MYKERNEL) in /usr/src/sys/i386/conf
(replace "i386" with the appropriate system architecture if necessary), and
ensure the following line is present:
device ixgbe
Compile and install the kernel. The system must be reboot for the kernel updates
to take affect. For additional information on compiling the kernel, consult the
FreeBSD operating system documentation.
Configuration
and Tuning
The driver supports Transmit/Receive Checksum Offload and Jumbo Frames on all
10GbE adapters.
Jumbo Frames
To enable Jumbo Frames, use the ifconfig utility to increase the MTU beyond
1500 bytes.
NOTES: The Jumbo Frames setting on the switch must be
set to at least 22 bytes larger than that of the MTU.
There are known performance issues with this driver when running UDP
traffic with Jumbo Frames.
The Jumbo Frames MTU range for Intel Adapters is 1500 to 16114. The default
MTU range is 1500. To modify the setting, enter the following:
ifconfig ix<interface_num> <hostname or IP address> mtu 9000
To confirm an interface's MTU value, use the ifconfig command. To confirm the
MTU used between two specific devices, use:
route get <destination_IP_address>
VLANs
To create a new VLAN interface:
ifconfig <vlan_name> create
To associate the VLAN interface with a physical interface and assign
an IP address, netmask, and VLAN ID:
In this example, all packets will be marked on egress with 802.1Q VLAN
tags, specifying a VLAN ID of 10.
To remove a VLAN interface:
ifconfig <vlan_name> destroy
Checksum Offload
Checksum offloading supports both TCP and UDP packets and is supported for
both transmit and receive.
Checksum offloading can be enabled or disabled using ifconfig. Both transmit and
receive offloading will be either enabled or disabled together. You cannot
enable/disable one without the other.
To enable checksum offloading:
ifconfig <interface_num> rxcsum
To disable checksum offloading:
ifconfig <interface_num> -rxcsum
To confirm the current setting:
ifconfig <interface_num>
TSO
TSO is enabled by default.
To disable:
ifconfig <interface_num> -tso
To re-enable:
ifconfig <interface_num> tso
LRO
Large Receive Offload is available in the driver; it is off by default.
LRO provides significant RX performance improvement. However it is incompatible
with packet-forwarding workloads. The administrator should carefully evaluate
the environment and enable when possible.
To enable:
ifconfig <interface_num> lro
It can be disabled by using:
ifconfig <interface_num> -lro
Important System Configuration Changes for ixgbe Driver
When there is a choice, run on a 64bit OS rather than 32, it makes a
significant difference in improvement.
The interface can generate high number of interrupts. To avoid running into the
limit set by the kernel, adjust hw.intr_storm_threshold setting using sysctl:
sysctl hw.intr_storm_threshold=9000 (the default is 1000)
For this change to take effect on boot, edit /etc/sysctl.conf and add the
line:
hw.intr_storm_threshold=9000
If you still see Interrupt Storm detected messages, increase the limit to a
higher number.
Best throughput results are seen with a large MTU; use 9000 if possible.
Known Limitations
Under small packets UDP stress test with the 10GbE driver, the FreeBSD system
will drop UDP packets, due to socket buffers being full. You may want to
change the driver's Flow Control variables to the minimum value for controlling
packet reception.
Attempting to configure larger MTUs with a large numbers of processors may
generate the error message "ix0:could not setup receive structures"
When using the ixgbe driver with RSS
autoconfigured based on the number of cores (the default setting) and that
number is larger than 4, increase the memory resources allocated for the mbuf
pool as follows:
Lower than expected performance on dual port 10GbE devices
Some PCI-E x8 slots are actually configured as x4 slots. These
slots have insufficient bandwidth for full 10Gbe line rate with dual port 10GbE
devices. The driver can detect this situation and will write the following
message in the system log: PCI-Express bandwidth available for this card is not
sufficient for optimal performance. For optimal performance a x8 PCI-Express
slot is required.
If this error occurs, moving your adapter to a true x8 slot
will resolve the issue.
Support
For general information and support, go to the support website
If an issue is identified, support is through email only at:
freebsd@intel.com
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.
NOTE: This release includes the following Linux* Base Drivers for
Intel® Ethernet Network Connection:
igb,
e1000e and igbvf.
igb driver supports all 82575-, 82576-, 82580-, I210-, and I211-, and I350-based gigabit
network connections.
The igbvf driver supports 82576-based virtual function devices that
can only be activated on kernels that support SR-IOV. SR-IOV requires
the correct platform and OS support.
e1000e driver supports all PCI Express gigabit network connections,
except those that are 82575-, 82576-, 82580-, and I350-based.
NOTE: As of July 2012, the e1000 legacy driver is no longer supported and is only maintained through the upstream kernel.
NOTE: The Intel(R) PRO/1000 P Dual Port Server Adapter
is supported by the e1000 driver, not the e1000e due to the
82546 part being used behind a PCI Express bridge.
First identify
your adapter. Then follow the appropriate steps for building,
installing, and configuring the driver.
UPGRADING: If you currently have the e1000 driver installed
and need to install e1000e, perform the following:
If your version of e1000 is 7.6.15.5 or less, upgrade to e1000
version 8.x.
Install the e1000e driver using the instructions in the
e1000e section.
Modify /etc/modprobe.conf to point your PCIe devices to use the new
e1000e driver using alias ethX e1000e, or use your distribution's
specific method for configuring network adapters like RedHat's
setup/system-config-network or SuSE's yast2.
Identifying Your Adapter
First identify your adapter. Then select the name of the specified base driver: igb or e1000e.
For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at:
The Linux base drivers
support the 2.4.x, 2.6.x, and 3.x kernels. These drivers includes support for Itanium®
2-based systems.
These drivers are only supported as a loadable module. Intel is not supplying
patches against the kernel source to allow for static linking of the drivers. For questions related
to hardware requirements, refer to the documentation supplied with your Intel
Gigabit adapter. All
hardware requirements listed apply to use with Linux.
The following features are now available in supported kernels:
Native VLANs
Channel Bonding (teaming)
SNMP
Channel Bonding documentation can be found in the Linux kernel source:
/documentation/networking/bonding.txt
The igb driver supports IEEE 1588 time stamping for kernels 2.6.30 and above.
The driver information previously displayed in the /proc file system is not
supported in this release. Alternatively, you can use ethtool (version 1.6 or
later), lspci, and ifconfig to obtain the same information. Instructions on
updating ethtool can be found in the section Additional
Configurations later in this document.
Building and Installation
To build a binary RPM* package of this driver, run 'rpmbuild -tb
igb.tar.gz'.
NOTES:
For the build to work properly, the currently running kernel
MUST match the version and configuration of the installed kernel sources. If you have just
recompiled the kernel reboot the system now.
RPM functionality has only
been tested in Red Hat distributions.
Move the base driver tar file to the directory of your
choice. For example, use '/home/username/igb' or '/usr/local/src/igb'.
Untar/unzip the archive, where <x.x.x> is the version number for the driver
tar file:
tar zxf igb-<x.x.x>.tar.gz
Change to the driver src directory, where <x.x.x> is the version number for the driver
tar:
The install location listed above is the default location.
This may differ for various Linux distributions.
Load the module using the modprobe
command:
modprobe igb
With 2.6 based kernels also make sure that older igb drivers are removed
from the kernel, before loading the new module:
rmmod igb; modprobe igb
Assign an IP address to the interface by entering the
following, where <x> is the interface number:
ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
TROUBLESHOOTING:Some systems have
trouble supporting MSI and/or MSI-X interrupts. If you believe your
system needs to disable this style of interrupt, the driver can be built
and installed with the command:
# make CFLAGS_EXTRA=-DDISABLE_PCI_MSI
install
Normally the driver will generate an interrupt
every two seconds, so if you can see that you're no longer getting
interrupts in cat /proc/interrupts for the ethX igb device, then this
workaround may be necessary.
To build igb driver with DCA:
If your kernel supports DCA, the driver will build by
default with DCA enabled.
Command Line Parameters
If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:
modprobe igb [<option>=<VAL1>,<VAL2>,...]
There needs to be a <VAL#> for each network port in the system supported by this driver. The values will be applied to each instance, in function order. For example:
modprobe igb InterruptThrottleRate=16000,16000
In this case, there are two network ports supported by igb in the system. The default value for each parameter is generally the recommended setting, unless otherwise noted.
NOTES:
For more information about the AutoNeg, Duplex, and Speed parameters, see the
Speed and Duplex
Configuration section in this document.
The driver can limit the amount of interrupts per second that the adapter
will generate for incoming packets. It does this by writing a value to
the adapter that is based on the maximum amount of interrupts that the
adapter will generate per second.
Setting InterruptThrottleRate to a value greater or equal to 100
will program the adapter to send out a maximum of that many interrupts
per second, even if more packets have come in. This reduces interrupt
load on the system and can lower CPU utilization under heavy load, but
will increase latency as packets are not processed as quickly.
The default behaviour of the driver previously assumed a static
InterruptThrottleRate
value of 8000, providing a good fallback value for all traffic types,
but lacking in small packet performance and latency. The hardware can
handle many more small packets per second however, and for this reason
an adaptive interrupt moderation algorithm was implemented.
The driver has two adaptive modes (setting 1 or 3) in which
it dynamically adjusts the InterruptThrottleRate value based on the traffic that it
receives. After determining the type of incoming traffic in the last
timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that
traffic.
The algorithm classifies the incoming traffic every interval into
classes. Once the class is determined, the InterruptThrottleRate value is adjusted to
suit that traffic type the best. There are three classes defined: "Bulk
traffic", for large amounts of packets of normal size; "Low latency",
for small amounts of traffic and/or a significant percentage of small
packets; and "Lowest latency", for almost completely small packets or
minimal traffic.
In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic
that falls in class "Bulk traffic". If traffic falls in the "Low
latency"
or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This
default mode is suitable for most applications.
For situations where low latency is vital such as cluster or grid
computing, the algorithm can reduce latency even more when
InterruptThrottleRate is set to mode 1. In this mode, which operates
the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for
traffic in class "Lowest latency".
Setting InterruptThrottleRate to 0 turns off any interrupt moderation
and may improve small packet latency, but is generally not suitable
for bulk throughput traffic
NOTE:
InterruptThrottleRate takes precedence over the TxAbsIntDelay and
RxAbsIntDelay parameters. In other words, minimizing the receive and/or
transmit absolute delays does not force the controller to generate more
interrupts than what the Interrupt Throttle Rate allows.
LLIPort
0-65535
0 (disabled)
LLI (Low Latency Interrupts): LLI allows for immediate generation of an
interrupt upon processing receive packets that match certain criteria as set
by the parameters described below. LLI parameters are not enabled when
Legacy interrupts are used. You must be using MSI or MSI-X (see cat
/proc/interrupts) to successfully use LLI.
LLI is configured with the LLIPort command-line parameter, which specifies
which TCP port should generate Low Latency Interrupts.
For example, using
LLIPort=80 would cause the board to generate an immediate interrupt upon
receipt of any packet sent to TCP port 80 on the local machine.
CAUTION:
Enabling LLI can result in an excessive number of interrupts/second that may
cause problems with the system and in some cases may cause a kernel panic.
LLIPush
0-1
0 (disabled)
LLIPush can be set to be enabled or disabled (default). It is most effective
in an environment with many small transactions.
NOTE: Enabling LLIPush may allow a denial of service attack.
LLISize
0-1500
0 (disabled)
LLISize causes an immediate interrupt if the board receives a packet smaller
than the specified size.
IntMode
0-2 (0 = Legacy Int, 1 = MSI and 2 = MSI-X)
2
IntMode controls allow load time control over the type of interrupt registered for by the driver. MSI-X is required for multiple queue support, and some kernels and combinations of kernel .config options will force a lower level of interrupt support. 'cat /proc/interrupts' will show different values for each type of interrupt.
RSS
0-8
1
0 - Assign up to whichever is less, number of CPUS or number of queues
X - Assign X queues where X is less than or equal to maximum number of
queues. The driver allows maximum supported queue value. For example,
I350-based adapters allow RSS=8 (where 8-queues is the maximum allowable
queues).
NOTE: For 82575-based adapters the maximum number of queues is 4; for 82576-based and newer adapters it is 8.
This parameter is also affected by the VMDq parameter in that it will limit
the queues more.
0 - 4 on 82575-based adapters; and 0 - 8 for 82576/82580-based adapters.
0 = disabled
1 = sets the netdev as pool 0
2+ = add additional queues but they currently are not used.
0
Supports enabling VMDq pools as this is needed to support SR-IOV.
This parameter is forced to 1 or more if the max_vfs module parameter is
used. In addition the number of queues available for RSS is limited if
this is set to 1 or greater.
NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering and VLAN tag stripping/insertion will remain enabled.
max_vfs
0-7
If the value is greater than 0 it will also force the VMDq parameter to be 1
or more.
0
This parameter adds support for SR-IOV. It causes the driver to spawn up to
max_vfs worth of virtual function.
QueuePairs
0-1
1 (TX and RX will be paired onto one
interrupt vector)
If set to 0, when MSI-X is enabled, the TX and RX will attempt to occupy
separate vectors.
This option can be overridden to 1 if there are not sufficient interrupts
available. This can occur if any combination of RSS, VMDQ, and max_vfs
results in more than 4 queues being used.
Node
0-n
0 - n: where n is the number of the NUMA node that
should be used to allocate memory for this adapter port.
-1: uses the
driver default of allocating memory on whichever processor is running modprobe.
-1 (off)
The Node parameter will allow you to pick which NUMA node you want to have the adapter allocate memory from. All driver structures, in-memory queues,
and receive buffers will be allocated on the node specified. This parameter is
only useful when interrupt affinity is specified, otherwise some portion of the
time the interrupt could run on a different core than the memory is allocated
on, causing slower memory access and impacting throughput, CPU, or both.
EEE
0-1
1 (enabled)
A link between two EEE-compliant devices will result in periodic bursts of data followed by periods where the link is in an idle state. This Low Power Idle (LPI) state is supported in both 1Gbps and 100Mbps link speeds.
Enables or disables DMA Coalescing feature. Values are
in usec�s and increase the internal DMA Coalescing feature�s internal timer. 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 adapter to collect packets before it initiates a DMA event. This may increase network latency but also increases the chances that the system will enter a lower power state.
Turning on DMA Coalescing may save energy with kernel 2.6.32 and later.
This will impart the greatest chance for your system to consume less power.
DMA Coalescing is effective in helping potentially saving the platform power
only when it is enabled across all active ports.
InterruptThrottleRate (ITR) should be set to dynamic. When ITR=0, DMA
Coalescing is automatically disabled.
A whitepaper containing information on how to best configure your platform is available on the Intel website.
MDD (Malicious Driver Detection)
Valid Range: 0, 1; 0 = Disable, 1 = Enable
Default Value: 1
This parameter is only relevant for I350 devices operating
in SR-IOV mode. When this parameter is set, the driver detects malicious VF
driver and disables its TX/RX queues until a VF driver reset occurs.
Additional Configurations
Configuring the Driver on Different Distributions
Configuring a network driver to load properly when the system is started
is distribution dependent. Typically, the configuration process involves
adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system
startup scripts and/or configuration files. Many popular Linux
distributions ship with tools to make these changes for you. To learn
the proper way to configure a network device for your system, refer to
your distribution documentation. If during this process you are asked
for the driver or module name, the name for the Linux Base Driver for the Gigabit
family of adapters
is e1000.
As an example, if you install the igb driver for two Gigabit adapters (eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI respectively, add the following to modules.conf or /etc/modprobe.conf:
alias eth0 igb
alias eth1 igb
options igb IntMode=2,1
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is restricting system messages.
In order to see network driver link
messages on your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved across reboots.
Jumbo Frames
Jumbo Frames support is enabled by changing the
Maximum Transmission Unit (MTU) to a value larger
than the default value of 1500. Use the ifconfig command to increase the MTU size. For
example:
ifconfig eth<x> mtu 9000 up
This setting is not saved across reboots. The
setting change can be made permanent by adding MTU=9000
to the file: /etc/sysconfig/network-scripts/ifcfg-eth<x> (Red
Hat
distributions). Other distributions may store this setting in a
different location.
NOTES:
To enable Jumbo Frames,
increase the MTU size on the interface beyond 1500.
The maximum MTU setting for Jumbo Frames is
9216. This value coincides with the maximum Jumbo Frames size of
9234.
Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.
ethtool
The driver utilizes the ethtool interface for driver configuration and
diagnostics, as well as displaying statistical information. ethtool version 3
or later is required for this functionality, although we strongly recommend
downloading the latest version at:
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 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.
Speed and Duplex are configured through the ethtool* utility. ethtool is
included with all versions of Red Hat after Red Hat 6.2. For other Linux
distributions, download and install ethtool from the following website: http://ftp.kernel.org/pub/software/network/ethtool/.
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.
Enabling Wake on LAN* (WoL)
WoL is configured through the ethtool* utility. ethtool is included with all
versions of Red Hat after Red Hat 7.2. For other Linux distributions,
download and install ethtool from the following website:
http://ftp.kernel.org/pub/software/network/ethtool/.
For instructions on enabling WoL with ethtool, refer to the website listed
above.
WoL will be enabled on the system during the next shut down or reboot. For this
driver version, in order to enable WoL, the driver must be
loaded prior to shutting down or suspending the system.
NOTES: Wake On LAN is only supported on port A of
multi-port devices.
Wake On LAN is not supported for the Intel® Gigabit
VT Quad Port Server Adapter.
Multiqueue
In this mode, a separate MSI-X vector is allocated for each queue and one for
"other" interrupts such as link status change and errors. All interrupts are
throttled via interrupt moderation. Interrupt moderation must be used to avoid
interrupt storms while the driver is processing one interrupt. The moderation
value should be at least as large as the expected time for the driver to process
an interrupt. Multiqueue is off by default.
Requirements: MSI-X support is required for Multiqueue. If MSI-X is not found, the system will
fallback to MSI or to Legacy interrupts. This driver supports multiqueue in kernel versions 2.6.24 and greater. This driver supports receive multiqueue on all kernels that support MSI-X.
NOTES: Do not use MSI-X with the 2.6.19 or 2.6.20
kernels.
On some kernels a reboot is
required to switch between a single queue mode and multiqueue modes, or
vice-versa.
LRO
Large Receive Offload (LRO) is a technique for increasing inbound throughput
of high-bandwidth network connections by reducing CPU overhead. It works by
aggregating multiple incoming packets from a single stream into a larger buffer
before they are passed higher up the networking stack, thus reducing the number
of packets that have to be processed. LRO combines multiple Ethernet frames into
a single receive in the stack, thereby potentially decreasing CPU utilization
for receives.
NOTE: LRO requires 2.4.22 or later kernel version.
IGB_LRO is a compile time flag. The user can enable it at compile time to
add support for LRO from the driver. The flag is used by adding
CFLAGS_EXTRA="-DIGB_LRO" to the make file when it's being compiled.
# make CFLAGS_EXTRA="-DIGB_LRO" install
You can verify that the driver is using LRO by looking at these counters in
ethtool:
lro_aggregated - count of total packets that were combined
lro_flushed - counts the number of packets flushed out of LRO
lro_recycled - reflects the number of buffers returned to the ring from
recycling
NOTE: IPv6 and UDP are not supported by LRO.
IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
Precision Time Protocol (PTP) is an implementation of the IEEE 1588
specification allowing network cards to synchronize their clocks over a
PTP-enabled network. It works through a series of synchronization and delay
notification transactions that allow a software daemon to implement a PID
controller to synchronize the network card clocks.
NOTE: PTP requires 3.0.0 or later kernel version that has PTP support
enabled in the kernel and a user-space software daemon.
IGB_PTP is a compile time flag. The user can enable it at compile time to add
support for PTP from the driver. The flag is used by adding
CFLAGS_EXTRA="-DIGB_PTP" to the make file when it's being compiled:
make CFLAGS_EXTRA="-DIGB_PTP" install
NOTE: The driver will fail to compile if your kernel does not
support PTP.
You can verify that the driver is using PTP by looking at the system log to
see whether a PHC was attempted to be registered or not. If you have a kernel
and version of ethtool with PTP support, you can check the PTP support in the
driver by executing:
ethtool -T ethX
MAC and VLAN anti-spoofing feature
When a malicious driver attempts to send a spoofed packet, it is dropped by
the hardware and not transmitted. An interrupt is sent to the PF driver
notifying it of the spoof attempt.
When a spoofed packet is detected the PF driver will send the following message
to the system log (displayed by the "dmesg" command):
Spoof event(s) detected on VF(n)
Where n = the VF that attempted to do the spoofing.
Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool
You can set a MAC address of a Virtual Function (VF), a default VLAN and the rate limit using the IProute2 tool. Download the latest version of the iproute2 tool from Sourceforge if your version does not have all the features you require.
Known Issues
NOTE: After installing the driver, if your Intel Ethernet Network
Connection is not working, verify that you have installed the correct
driver.
Using the igb driver on 2.4 or older 2.6 based kernels
Due to limited support for PCI-Express in 2.4 kernels and older 2.6 kernels,
the igb driver may run into interrupt related problems on some systems, such as
no link or hang when bringing up the device.
We recommend the newer 2.6 based kernels, as these kernels correctly
configure the PCI-Express configuration space of the adapter and all intervening
bridges. If you are required to use a 2.4 kernel, use a 2.4 kernel newer than
2.4.30. For 2.6 kernels we recommend using the 2.6.21 kernel or newer.
Alternatively, on 2.6 kernels you may disable MSI support in the kernel by
booting with the "pci=nomsi" option or permanently disable MSI support in your
kernel by configuring your kernel with CONFIG_PCI_MSI unset.
Intel® Active Management Technology 2.0, 2.1, 2.5 not
supported in conjunction with Linux driver
Detected Tx Unit Hang in Quad Port Adapters
In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit
Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 1
and 2 don't show any errors and will pass traffic.
This issue MAY be resolved by updating to the latest kernel and BIOS. The
user is encouraged to run an OS that fully supports MSI interrupts. You can
check your system's BIOS by downloading the Linux Firmware Developer Kit that
can be obtained at http://www.linuxfirmwarekit.org/
Compiling the Driver
When trying to compile the driver by running make install, the following
error may occur: "Linux kernel source not configured - missing
version.h"
To solve this issue, create the version.h file by going to the Linux source
tree and entering:
#
make include/linux/version.h
Performance Degradation with Jumbo Frames
Degradation in throughput performance may be observed in some Jumbo frames
environments. If this is observed, increasing the application's socket buffer
size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.
See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt
for more details.
Jumbo frames on Foundry BigIron 8000 switch
There is a known issue using Jumbo frames when connected to a Foundry BigIron
8000 switch. This is a 3rd party limitation. If you experience loss of packets,
lower the MTU size.
Multiple Interfaces on Same Ethernet Broadcast Network
Due to the default ARP behavior on Linux, it is not possible to have one
system on two IP networks in the same Ethernet broadcast domain
(non-partitioned switch) behave as expected. All Ethernet interfaces will
respond to IP traffic for any IP address assigned to the system.
This results in unbalanced receive traffic.
If you have multiple interfaces in a server, either turn on ARP filtering by
entering:
echo 1 >
/proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5)
NOTE: This setting is not saved across reboots. The
configuration change can be made permanent by adding the line:
net.ipv4.conf.all.arp_filter = 1
to the file /etc/sysctl.conf
or,
install the interfaces in separate broadcast domains (either in different
switches or in a switch partitioned to VLANs).
Disable rx flow control with ethtool
In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line.
For example:
ethtool -A
eth? autoneg off rx off
Unplugging network cable while ethtool -p is running
In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the
network cable while ethtool -p is running will cause the system to
become unresponsive to keyboard commands, except for control-alt-delete.
Restarting the system appears to be the only remedy.
Trouble passing traffic with on ports 1 and 2 using RHEL3
There is a known hardware compatibility issue on some systems with RHEL3
kernels. Traffic on ports 1 and 2 may be slower than expected and ping times
higher than expected.
This issue MAY be resolved by updating to the latest kernel and BIOS. You can
check your system's BIOS by downloading the Linux Firmware Developer Kit that
can be obtained at http://www.linuxfirmwarekit.org/
Do Not Use LRO When Routing Packets
Due to a known general compatibilty issue with LRO and routing, do not use
LRO when routing packets.
Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'
Some systems may experience build issues due to redefinition of irq_handler_t.
To resolve this issue build the driver (step 4 above) using the command:
# make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1 install
MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
Kernel panics and instability may be observed on any MSI-X hardware if you
use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are
encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.
Rx Page Allocation Errors
Page allocation failure. order:0 errors may occur under stress with kernels
2.6.25 and above. This is caused by the way the Linux kernel reports this
stressed condition.
Under Redhat 5.4-GA - System May Crash when Closing Guest OS Window after
Loading/Unloading Physical Function (PF) Driver
Do not remove the igb driver from Dom0 while Virtual Functions (VFs) are
assigned to guests. VFs must first use the xm "pci-detach" command to hot-plug
the VF device out of the VM it is assigned to or else shut down the
VM.
SLES10 SP3 random system panic when reloading driver
This is a known SLES-10 SP3 issue. After requesting interrupts for MSI-X
vectors, system may panic.
Currently the only known workaround is to build the drivers with CFLAGS_EXTRA=-DDISABLE_PCI_MSI
if the driver need to be loaded/unloaded. Otherwise the driver can be loaded
once and will be safe, but unloading it will lead to the issue.
Enabling SR-IOV in a 32-bit Microsoft* Windows* Server 2008 Guest OS using
Intel® 82576-based GbE or Intel® 82599-based 10GbE controller under KVM
KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
includes traditional PCIe devices, as well as SR-IOV-capable devices using Intel
82576-based and 82599-based controllers.
While direct assignment of a PCIe device or an SR-IOV Virtual Function (VF) to a
Linux-based VM running 2.6.32 or later kernel works fine, there is a known issue
with Microsoft Windows Server 2008 VM that results in a "yellow bang" error.
This problem is within the KVM VMM itself, not the Intel driver, or the SR-IOV
logic of the VMM, but rather that KVM emulates an older CPU model for the
guests, and this older CPU model does not support MSI-X interrupts, which is a
requirement for Intel SR-IOV.
If you wish to use the Intel 82576 or 82599-based controllers in SR-IOV mode
with KVM and a Microsoft Windows Server 2008 guest try the following workaround.
The workaround is to tell KVM to emulate a different model of CPU when using
qemu to create the KVM guest:
"-cpu qemu64,model=13"
Host May Reboot after Removing PF when VF is Active in Guest
Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing
this will cause your VFs to stop working until you reload the PF driver and may
cause a spontaneous reboot of your system.
The Linux base drivers
support the 2.4.x, 2.6.x, and 3.x kernels. These drivers includes support for Itanium®
2-based systems.
These drivers are only supported as a loadable module. Intel is not supplying
patches against the kernel source to allow for static linking of the drivers. For questions related
to hardware requirements, refer to the documentation supplied with your Intel
Gigabit adapter. All
hardware requirements listed apply to use with Linux.
The following features are now available in supported kernels:
Native VLANs
Channel Bonding (teaming)
SNMP
Channel Bonding documentation can be found in the Linux kernel source:
/documentation/networking/bonding.txt
The driver information previously displayed in the /proc file system is not
supported in this release. Alternatively, you can use ethtool (version 1.6 or
later), lspci, and ifconfig to obtain the same information. Instructions on
updating ethtool can be found in the section Additional
Configurations later in this document.
NOTE: The Intel®
82562v 10/100 Network Connection only
provides 10/100 support.
Building and Installation
To build a binary RPM* package of this driver, run 'rpmbuild -tb e1000e.tar.gz'.
NOTES:
For the build to work properly, the currently running kernel
MUST match the version and configuration of the installed kernel sources. If you have just
recompiled the kernel reboot the system now.
RPM functionality has only
been tested in Red Hat distributions.
Move the base driver tar file to the directory of your
choice. For example, use '/home/username/e1000e' or '/usr/local/src/e1000e'.
Untar/unzip the archive, where <x.x.x> is the version number for the driver
tar file:
tar zxf e1000e-<x.x.x>.tar.gz
Change to the driver src directory, where <x.x.x> is the version number for the driver
tar:
The install location listed above is the default location.
This may differ for various Linux distributions.
Load the module using the modprobe
command:
modprobe e1000e
With 2.6 based kernels also make sure that older e1000e drivers are removed
from the kernel, before loading the new module:
rmmod e1000e; modprobe
e1000e
Assign an IP address to the interface by entering the
following, where <x> is the interface number:
ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
TROUBLESHOOTING:Some systems have
trouble supporting MSI and/or MSI-X interrupts. If you believe your
system needs to disable this style of interrupt, the driver can be built
and installed with the command:
# make CFLAGS_EXTRA=-DDISABLE_PCI_MSI
install
Normally the driver will generate an interrupt
every two seconds, so if you can see that you're no longer getting
interrupts in cat /proc/interrupts for the ethX e1000e device, then this
workaround may be necessary.
Command Line Parameters
If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:
modprobe e1000e [<option>=<VAL1>,<VAL2>,...]
There needs to be a <VAL#> for each network port in the system supported by this driver. The values will be applied to each instance, in function order. For example:
modprobe e1000e InterruptThrottleRate=16000,16000
In this case, there are two network ports supported by e1000e in the system. The default value for each parameter is generally the recommended setting, unless otherwise noted.
The driver can limit the amount of interrupts per second that the adapter
will generate for incoming packets. It does this by writing a value to
the adapter that is based on the maximum amount of interrupts that the
adapter will generate per second.
Setting InterruptThrottleRate to a value greater or equal to 100
will program the adapter to send out a maximum of that many interrupts
per second, even if more packets have come in. This reduces interrupt
load on the system and can lower CPU utilization under heavy load, but
will increase latency as packets are not processed as quickly.
The default behavior of the driver previously assumed a static
InterruptThrottleRate value of 8000, providing a good fallback value for
all traffic types, but lacking in small packet performance and latency.
The driver has two adaptive modes (setting 1 or 3) in which
it dynamically adjusts the InterruptThrottleRate value based on the traffic that it
receives. After determining the type of incoming traffic in the last
timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that
traffic.
The algorithm classifies the incoming traffic every interval into
classes. Once the class is determined, the InterruptThrottleRate value is adjusted to
suit that traffic type the best. There are three classes defined: "Bulk
traffic", for large amounts of packets of normal size; "Low latency",
for small amounts of traffic and/or a significant percentage of small
packets; and "Lowest latency", for almost completely small packets or
minimal traffic.
In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic
that falls in class "Bulk traffic". If traffic falls in the "Low
latency"
or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This
default mode is suitable for most applications.
For situations where low latency is vital such as cluster or grid
computing, the algorithm can reduce latency even more when
InterruptThrottleRate is set to mode 1. In this mode, which operates
the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for
traffic in class "Lowest latency".
In simplified mode the
interrupt rate is based on the ratio of tx and rx traffic. If the bytes
per second rate is approximately equal, the
interrupt rate will drop as low as 2000 interrupts per second. If the
traffic is mostly transmit or mostly receive, the interrupt rate could
be as high as 8000.
Setting InterruptThrottleRate to 0 turns off any interrupt moderation
and may improve small packet latency, but is generally not suitable
for bulk throughput traffic
NOTE:
InterruptThrottleRate takes precedence over the TxAbsIntDelay and
RxAbsIntDelay parameters. In other words, minimizing the receive and/or
transmit absolute delays does not force the controller to generate more
interrupts than what the Interrupt Throttle Rate allows.
NOTE:
When e1000e is loaded with default settings and multiple adapters are in
use simultaneously, the CPU utilization may increase non-linearly. In
order to limit the CPU utilization without impacting
the overall throughput, we recommend that you load the driver as
follows:
This sets the InterruptThrottleRate to 3000 interrupts/sec for the first,
second, and third instances of the driver. The range of 2000 to 3000
interrupts per second works on a majority of systems and is a good
starting point, but the optimal value will be platform-specific. If CPU
utilization is not a concern, use RX_POLLING (NAPI) and default driver
settings.
RxIntDelay
0-65535 (0=off)
0
This value delays the generation of receive interrupts in units of
1.024 microseconds. Receive interrupt reduction can improve CPU
efficiency if properly tuned for specific network traffic.
Increasing this value adds extra latency to frame reception
and can end up decreasing the throughput of TCP traffic. If the system is
reporting dropped receives, this value may be set too high, causing the
driver to run out of available receive descriptors.
CAUTION: When setting RxIntDelay to a value other than 0,
adapters may
hang (stop transmitting) under certain network conditions. If
this occurs a NETDEV WATCHDOG message is logged in the system event log. In
addition, the controller is automatically reset, restoring the
network connection. To eliminate the potential for the hang
ensure that RxIntDelay is set to zero.
RxAbsIntDelay
0-65535 (0=off)
8
This value, in units of 1.024 microseconds, limits the delay in which a
receive interrupt is generated. Useful only if RxIntDelay is non-zero,
this value ensures that an interrupt is generated after the initial
packet is received within the set amount of time. Proper tuning,
along with RxIntDelay, may improve traffic throughput in specific
network conditions.
TxIntDelay
0-65535 (0=off)
8
This value delays the generation of transmit interrupts in units of 1.024
microseconds. Transmit interrupt reduction can improve CPU efficiency if
properly tuned for specific network traffic. If the system is reporting
dropped transmits, this value may be set too high causing the driver to run
out of available transmit descriptors.
TxAbsIntDelay
0-65535 (0=off)
32
This value, in units of 1.024 microseconds, limits the delay in which a transmit
interrupt is generated. Useful only if TxIntDelay is non-zero, this value
ensures that an interrupt is generated after the initial packet is sent on
the wire within the set amount of time. Proper tuning, along with TxIntDelay,
may improve traffic throughput in specific network conditions.
copybreak
0-xxxxxxx (0=off)
256
Usage: modprobe e1000e.ko copybreak=128
Driver copies all packets below or equaling this size to a fresh rx buffer
before handing it up the stack.
This parameter is different than other parameters, in that it is a single
(not 1,1,1 etc.) parameter applied to all driver instances and it is also
available during runtime at /sys/module/e1000e/parameters/copybreak
SmartPowerDownEnable
0-1
0 (disabled)
Allows Phy to turn off in lower power states. The user can turn off
this parameter in supported chipsets.
KumeranLockLoss
0-1
1 (enabled)
This workaround skips resetting the Phy at shutdown for the initial
silicon releases of ICH8 systems.
IntMode
0-2
(0=legacy, 1=MSI, 2=MSI-X)
2 (MSI-X)
Allows changing the interrupt mode at module load time, without requiring a
recompile. If the driver load fails to enable a specific interrupt mode, the
driver will try other interrupt modes, from least to most compatible. The
interrupt order is MSI-X, MSI, Legacy. If specifying MSI (IntMode=1)
interrupts, only MSI and Legacy will be attempted.
CrcStripping
0-1
1 (enabled)
Strip the CRC from received packets before sending up the network stack. If
you have a machine with a BMC enabled but cannot receive IPMI traffic after
loading or enabling the driver, try disabling this feature.
EEE
0-1
1 (enabled for parts supporting EEE)
This option allows for the ability of IEEE802.3az (a.k.a. Energy Efficient
Ethernet or EEE) to be advertised to the link partner on parts supporting
EEE. EEE saves energy by putting the device into a low-power state when the
link is idle, but only when the link partner also supports EEE and after the
feature has been enabled during link negotiation. It is not necessary to
disable the advertisement of EEE when connected with a link partner that
does not support EEE.
Node
0-n
0 - n: where n is the number of the NUMA node that
should be used to allocate memory for this adapter port.
-1: uses the
driver default of allocating memory on whichever processor is running modprobe.
-1 (off)
The Node parameter will allow you to pick which NUMA node you want to have the adapter allocate memory from. All driver structures, in-memory queues,
and receive buffers will be allocated on the node specified. This parameter is
only useful when interrupt affinity is specified, otherwise some portion of the
time the interrupt could run on a different core than the memory is allocated
on, causing slower memory access and impacting throughput, CPU, or both.
Additional Configurations
Configuring the Driver on Different Distributions
Configuring a network driver to load properly when the system is started
is distribution dependent. Typically, the configuration process involves
adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system
startup scripts and/or configuration files. Many popular Linux
distributions ship with tools to make these changes for you. To learn
the proper way to configure a network device for your system, refer to
your distribution documentation. If during this process you are asked
for the driver or module name, the name for the Linux Base Driver for the Gigabit
family of adapters
is e1000e.
As an example, if you install the e1000e driver for two Gigabit adapters
(eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI
respectively, add the following to modules.conf or /etc/modprobe.conf:
alias eth0 e1000e
alias eth1 e1000e
options e1000e IntMode=2,1
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is restricting system messages.
In order to see network driver link
messages on your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved across reboots.
Jumbo Frames
Jumbo Frames support is enabled by changing the
Maximum Transmission Unit (MTU) to a value larger
than the default value of 1500. Use the ifconfig command to increase the MTU size. For
example:
ifconfig eth<x> mtu 9000 up
This setting is not saved across reboots. The
setting change can be made permanent by adding MTU=9000
to the file: /etc/sysconfig/network-scripts/ifcfg-eth<x> (Red
Hat
distributions). Other distributions may store this setting in a
different location.
NOTES:
To enable Jumbo Frames,
increase the MTU size on the interface beyond 1500.
The maximum MTU setting for Jumbo Frames is 9216. This
value coincides with the maximum Jumbo Frames size of 9234 bytes.
Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.
The following adapters limit Jumbo Frames sized
packets to a maximum of 4088 bytes:
Intel® 82578DM Gigabit Network Connection
Intel® 82577LM Gigabit Network Connection
Jumbo Frames cannot be configured on an 82579-based
Network device, if MACSec is enabled on the system.
ethtool
The driver utilizes the ethtool interface for driver configuration and
diagnostics, as well as displaying statistical information. ethtool version 3
or later is required for this functionality, although we strongly recommend
downloading the latest version at:
NOTE:
When validating enable/disable tests on some parts (82578, for example) you need to add a few seconds between tests when working with ethtool.
Speed and Duplex Configuration
Speed and Duplex are configured through the ethtool* utility. ethtool is
included with all versions of Red Hat after Red Hat 7.2. For other Linux
distributions, download and install ethtool from the following website:
http://ftp.kernel.org/pub/software/network/ethtool/.
Enabling Wake on LAN* (WoL)
WoL is configured through the ethtool* utility. ethtool is included with all
versions of Red Hat after Red Hat 7.2. For other Linux distributions,
download and install ethtool from the following website:
http://ftp.kernel.org/pub/software/network/ethtool/.
For instructions on enabling WoL with ethtool, refer to the website listed
above.
WoL will be enabled on the system during the next shut down or reboot. For this
driver version, in order to enable WoL, the e1000e driver must be
loaded prior to shutting down or suspending the system.
NOTES: Wake On LAN is only supported on port A for the
following devices:
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® PRO/1000 PT Quad Port Server Adapter
Intel® Gigabit PT Quad Port Server ExpressModule
NAPI
NAPI (Rx polling mode) is supported in the e1000e driver. NAPI is enabled by
default.
To disable NAPI, compile the driver module, passing in a configuration
option:
NOTE: After installing the driver, if your Intel Network
Connection is not working, verify that you have installed the correct
driver.
Intel® Active Management Technology 2.0, 2.1, 2.5 not
supported in conjunction with Linux driver
Detected Tx Unit Hang in Quad Port Adapters
In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit
Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 1
and 2 don't show any errors and will pass traffic.
This issue MAY be resolved by updating to the latest kernel and BIOS. The
user is encouraged to run an OS that fully supports MSI interrupts. You can
check your system's BIOS by downloading the Linux Firmware Developer Kit that
can be obtained at http://www.linuxfirmwarekit.org/
Adapters with 4 ports behind a PCIe bridge
Adapters that have 4 ports behind a PCIe bridge may be incompatible with some
systems. The user should run the Linux firmware kit from http://www.linuxfirmwarekit.org/ to test their BIOS, if they have interrupt or "missing
interface" problems, especially with older kernels.
82573(V/L/E) TX Unit Hang Messages
Several adapters with the 82573 chipset display "TX unit
hang" messages during normal operation with the e1000e driver.
The issue appears both with TSO enabled and disabled, and is
caused by a power management function that is enabled in the
EEPROM. Early releases of the chipsets to vendors had the EEPROM
bit that enabled the feature. After the issue was discovered
newer adapters were released with the feature disabled in the
EEPROM.
If you encounter the problem in an adapter, and the chipset
is an 82573-based one, you can verify that your adapter needs
the fix by using ethtool:
The value at offset 0x001e (de) has bit 0 unset. This enables
the problematic power saving feature. In this case, the EEPROM
needs to read "df" at offset 0x001e.
A one-time EEPROM fix is available as a shell script. This
script will verify that the adapter is applicable to the fix and
if the fix is needed or not. If the fix is required, it applies
the change to the EEPROM and updates the checksum. The user must
reboot the system after applying the fix if changes were made to
the EEPROM.
Example output of the script:
# bash fixeep-82573-dspd.sh eth0
eth0: is a "82573E Gigabit Ethernet Controller"
This fixup is applicable to your hardware
executing command: ethtool -E eth0 magic 0x109a8086 offset 0x1e value 0xdf
Change made. You *MUST* reboot your machine before changes take effect!
Dropped Receive Packets on Half-duplex 10/100 Networks
If you have an Intel PCI Express adapter running at 10mbps or 100mbps,
half-duplex, you may observe occasional
dropped receive packets. There are no workarounds for this problem in this
network configuration. The network must be updated to operate in full-duplex,
and/or 1000mbps only.
Compiling the Driver
When trying to compile the driver by running make install, the following
error may occur: "Linux kernel source not configured - missing
version.h"
To solve this issue, create the version.h file by going to the Linux source
tree and entering:
#
make include/linux/version.h
Performance Degradation with Jumbo Frames
Degradation in throughput performance may be observed in some Jumbo frames
environments. If this is observed, increasing the application's socket buffer
size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.
See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt
for more details.
Jumbo frames on Foundry BigIron 8000 switch
There is a known issue using Jumbo frames when connected to a Foundry BigIron
8000 switch. This is a 3rd party limitation. If you experience loss of packets,
lower the MTU size.
Allocating Rx Buffers when Using Jumbo Frames
Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if
the available memory is heavily fragmented. This issue may be seen with PCI-X
adapters or with packet split disabled. This can be reduced or eliminated by
changing the amount of available memory for receive buffer allocation, by
increasing /proc/sys/vm/min_free_kbytes.
Multiple Interfaces on Same Ethernet Broadcast Network
Due to the default ARP behavior on Linux, it is not possible to have one
system on two IP networks in the same Ethernet broadcast domain
(non-partitioned switch) behave as expected. All Ethernet interfaces will
respond to IP traffic for any IP address assigned to the system.
This results in unbalanced receive traffic.
If you have multiple interfaces in a server, either turn on ARP filtering by
entering:
echo 1 >
/proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5)
NOTE: This setting is not saved across reboots. The
configuration change can be made permanent by adding the line:
net.ipv4.conf.all.arp_filter = 1
to the file /etc/sysctl.conf
or,
install the interfaces in separate broadcast domains (either in different
switches or in a switch partitioned to VLANs).
Disable rx flow control with ethtool
In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line.
For example:
ethtool -A
eth? autoneg off rx off
Unplugging network cable while ethtool -p is running
In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the
network cable while ethtool -p is running will cause the system to
become unresponsive to keyboard commands, except for control-alt-delete.
Restarting the system appears to be the only remedy.
MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
Kernel panics and instability may be observed on any MSI-X hardware if you
use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are
encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.
Rx Page Allocation Errors
Page allocation failure. order:0 errors may occur under stress with kernels
2.6.25 and above. This is caused by the way the Linux kernel reports this
stressed condition.
Network throughput degradation observed with Onboard video versus add-in
Video Card on 82579LM Gigabit Network Connection when used with some older
kernels.
This issue can be worked around by specifying "pci=nommconf" in the kernel
boot parameter or by using another kernel boot parameter
"memmap=128M$0x100000000" which marks 128 MB region at 4GB as reserved and
therefore OS won't use these RAM pages.
This issue is fixed in kernel version 2.6.21, where the kernel tries to
dynamically find out the mmconfig size by looking at the number of buses that
the mmconfig segment maps to.
This issue won't be seen on 32bit version of EL5, as in that case, the kernel
sees that RAM is located around the 256MB window and avoids using the mmconfig
space.
Activity LED blinks unexpectedly
If a system based on the 82577, 82578, or 82579 controller is connected to a
hub, the Activity LED will blink for all network traffic present on the hub.
Connecting the system to a switch or router will filter out most traffic not
addressed to the local port.
Link may take longer than expected
With some Phy and switch combinations, link can take longer than expected. This can be an issue on Linux distributions that timeout when checking for link prior to acquiring a DHCP address; however there is usually a way to work around this (e.g. set LINKDELAY in the interface configuration on RHEL).
Tx flow control is disabled by default on 82577 and 82578-based adapters
Possible performance degradation on certain 82566 and 82577 devices
Internal stress testing with jumbo frames shows the reliability on some 82566 and 82567 devices is improved in certain corner cases by disabling the Early Receive feature. Doing so can impact Tx performance. To reduce the impact, the packet buffer sizes and relevant flow control settings are modified accordingly.
The igbvf driver supports 82576-based virtual function devices that can only be
activated on kernels that support SR-IOV. SR-IOV requires the correct
platform and OS support.
The igbvf driver requires the igb driver, version 2.0 or later. The igbvf driver
supports virtual functions generated by the igb driver with a max_vfs value of 1
or greater. For more information on the max_vfs parameter refer to the section
on the the igb driver.
The guest OS loading the igbvf driver must support MSI-X interrupts.
This driver is only supported as a loadable module at this time. Intel is not
supplying patches against the kernel source to allow for static linking of the
driver. For questions related to hardware requirements, refer to the
documentation supplied with your Intel Gigabit adapter. All hardware
requirements listed apply to use with Linux.
Instructions on updating ethtool can be found in the section Additional
Configurations later in this document.
VLANs: There is a limit of a total of 32 shared VLANs to 1 or more VFs.
Building and Installation
To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'.
Replace <filename.tar.gz> with the specific filename of the driver.
NOTE: For the build to work
properly, the currently running kernel MUST match the version and
configuration of the installed kernel sources. If you have just recompiled
the kernel reboot the system now.
RPM functionality has only been tested in Red Hat distributions.
Move the base driver tar file to the directory of your
choice. For example, use ' /home/username/igbvf or /usr/local/src/igbvf.'.
The install location listed above is the default location.
This may differ for various Linux distributions.
Load the module using the modprobe
command:
modprobe igbvf
With 2.6 based kernels also make sure that older e1000e drivers are removed
from the kernel, before loading the new module:
rmmod igbvf; modprobe
igbvf
Assign an IP address to the interface by entering the
following, where <x> is the interface number:
ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
Troubleshooting: Some systems have trouble supporting
MSI and/or MSI-X interrupts. If you believe your system needs to disable
this style of interrupt, the driver can be built and installed with the
command:
make CFLAGS_EXTRA=-DDISABLE_PCI_MSI
install
Normally the driver will generate an interrupt every two seconds, so if you
can see that you're no longer getting interrupts in cat /proc/interrupts for the
ethX igbvf device, then this workaround may be necessary.
Command Line Parameters
If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:
modprobe igbvf [<option>=<VAL1>,<VAL2>,...]
There needs to be a <VAL#> for each network port in the system supported by this driver. The values will be applied to each instance, in function order. For example:
modprobe igbvf InterruptThrottleRate=16000,16000
In this case, there are two network ports supported by igbvf in the system. The default value for each parameter is generally the recommended setting, unless otherwise noted.
The driver can limit the amount of interrupts per second that the adapter
will generate for incoming packets. It does this by writing a value to
the adapter that is based on the maximum amount of interrupts that the
adapter will generate per second.
Setting InterruptThrottleRate to a value greater or equal to 100
will program the adapter to send out a maximum of that many interrupts
per second, even if more packets have come in. This reduces interrupt
load on the system and can lower CPU utilization under heavy load, but
will increase latency as packets are not processed as quickly.
The default behaviour of the driver previously assumed a static
InterruptThrottleRate
value of 8000, providing a good fallback value for all traffic types,
but lacking in small packet performance and latency. The hardware can
handle many more small packets per second however, and for this reason
an adaptive interrupt moderation algorithm was implemented.
The driver has two adaptive modes (setting 1 or 3) in which
it dynamically adjusts the InterruptThrottleRate value based on the traffic that it
receives. After determining the type of incoming traffic in the last
timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that
traffic.
The algorithm classifies the incoming traffic every interval into
classes. Once the class is determined, the InterruptThrottleRate value is adjusted to
suit that traffic type the best. There are three classes defined: "Bulk
traffic", for large amounts of packets of normal size; "Low latency",
for small amounts of traffic and/or a significant percentage of small
packets; and "Lowest latency", for almost completely small packets or
minimal traffic.
In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic
that falls in class "Bulk traffic". If traffic falls in the "Low
latency"
or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This
default mode is suitable for most applications.
For situations where low latency is vital such as cluster or grid
computing, the algorithm can reduce latency even more when
InterruptThrottleRate is set to mode 1. In this mode, which operates
the same as mode 3, the InterruptThrottleRate will be increased stepwise to 70000 for
traffic in class "Lowest latency".
Setting InterruptThrottleRate to 0 turns off any interrupt moderation
and may improve small packet latency, but is generally not suitable
for bulk throughput traffic
NOTE:
Dynamic interrupt throttling is only applicable to adapters
operating in MSI or Legacy interrupt mode, using a single
receive queue.
NOTE:
When igbvf is loaded with default settings and multiple adapters are in
use simultaneously, the CPU utilization may increase non-linearly. In
order to limit the CPU utilization without impacting
the overall throughput, we recommend that you load the driver as
follows:
This sets the InterruptThrottleRate to 3000 interrupts/sec for the first,
second, and third instances of the driver. The range of 2000 to 3000
interrupts per second works on a majority of systems and is a good
starting point, but the optimal value will be platform-specific. If CPU
utilization is not a concern, use default driver settings.
Additional Configurations
Configuring the Driver on Different Distributions
Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding an
alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other
system startup scripts and/or configuration files. Many popular Linux
distributions ship with tools to make these changes for you. To learn the proper
way to configure a network device for your system, refer to your distribution
documentation. If during this process you are asked for the driver or module
name, the name for the Linux Base Driver for the Gigabit Family of Adapters is
igbvf.
As an example, if you install the igbvf driver for two Gigabit adapters (eth0
and eth1) and want to set the interrupt mode to MSI-X and MSI respectively, add
the following to modules.conf or /etc/modprobe.conf:
alias eth0 igbvf
alias eth1 igbvf
options igbvf InterruptThrottleRate=3,1
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages on
your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved
across reboots.
Jumbo Frames
Jumbo Frames support is enabled by changing the MTU to a value larger than
the default of 1500. Use the ifconfig command to increase the MTU size.
For example:
ifconfig eth<x> mtu 9000 up
This setting is not saved across reboots. It can be made permanent if you add:
MTU=9000
to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This example applies
to the Red Hat distributions; other distributions may store this setting in a
different location.
NOTES:
To enable Jumbo Frames,
increase the MTU size on the interface beyond 1500.
The maximum MTU setting for Jumbo Frames is 9216. This
value coincides with the maximum Jumbo Frames size of 9234 bytes.
Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.
ethtool
The driver utilizes the ethtool interface for driver configuration and
diagnostics, as well as displaying statistical information. ethtool version 3.0
or later is required for this functionality, although we strongly recommend
downloading the latest version at:
NOTE: After installing the driver, if your Intel Network
Connection is not working, verify that you have installed the correct
driver.
Driver Compilation
When trying to compile the driver by running make install, the following
error may occur:
"Linux kernel source not configured - missing version.h"
To solve this issue, create the version.h file by going to the Linux source tree
and entering:
make include/linux/version.h.
Multiple Interfaces on Same Ethernet Broadcast Network
Due to the default ARP behavior on Linux, it is not possible to have one
system on two IP networks in the same Ethernet broadcast domain (non-partitioned
switch) behave as expected. All Ethernet interfaces will respond to IP traffic
for any IP address assigned to the system. This results in unbalanced receive
traffic.
If you have multiple interfaces in a server, either turn on ARP filtering by
entering:
echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5),
NOTE: This setting is not saved across reboots. The
configuration change can be made permanent by adding the line:
net.ipv4.conf.all.arp_filter = 1
to the file /etc/sysctl.conf or installing the interfaces in
separate broadcast domains (either in
different switches or in a switch partitioned to VLANs.
Do Not Use LRO When Routing Packets
Due to a known general compatibility issue with LRO and routing, do not use
LRO when routing packets.
Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'
Some systems may experience build issues due to redefinition of irq_handler_t.
To resolve this issue build the driver (step 4 above) using the command:
make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1
install
MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
Kernel panics and instability may be observed on any MSI-X hardware if you
use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are
encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.
Rx Page Allocation Errors
Page allocation failure. order:0 errors may occur under stress with kernels
2.6.25 and above. This is caused by the way the Linux kernel reports this
stressed condition.
Under Redhat 5.4 - System May Crash when Closing Guest OS Window after
Loading/Unloading Physical Function (PF) Driver
Do not remove the igbvf driver from Dom0 while Virtual Functions (VFs) are
assigned to guests. VFs must first use the xm "pci-detach" command to hot-plug
the VF device out of the VM it is assigned to or else shut down the VM.
Unloading Physical Function (PF) Driver Causes System Reboots When VM is
Running and VF is Loaded on the VM
Do not unload the PF driver (igb) while VFs are assigned to guests.
Host May Reboot after Removing PF when VF is Active in Guest
Using kernel versions earlier than 3.2, do not unload the PF driver with active VFs. Doing
this will cause your VFs to stop working until you reload the PF driver and may
cause a spontaneous reboot of your system.
Last modified on 11/03/11 4:12p Revision
DOCS/LINUX/index.htm 0000755 0000000 0000000 00000001063 11662474024 011225 0 ustar
Intel® Linux Base Driver for Intel Ethernet Adapters
/html>
DOCS/LINUX/ixgb.htm 0000755 0000000 0000000 00000232167 12126521014 011046 0 ustar
Linux Driver for Intel 10GbE Network Connections
Linux* Base Driver for 10 Gigabit Intel® Ethernet Network Connection
NOTES:
This release includes the ixgbe and ixgbevf Linux* Base Drivers for the IntelEthernet 10
Gigabit Family of Adapters.
All 82599, X540 and 82598-based 10 Gigabit network connections
require the ixgbe driver.
The ixgbevf driver supports 82599
and X540-based virtual function devices that
can only be activated on kernels that support SR-IOV. SR-IOV requires
the correct platform and OS support.
Warning: The ixgbe driver compiles by default with the LRO (Large Receive
Offload) feature enabled. This option offers the lowest CPU utilization for
receives, but is completely incompatible with *routing/ip forwarding* and
*bridging*. If enabling ip forwarding or bridging is a requirement, it is
necessary to disable LRO using compile time options as noted in the LRO section
later in this document. The result of not disabling LRO when combined with ip
forwarding or bridging can be low throughput or even a kernel panic.
Overview
The Linux* base driver supports the 2.6.x
and 3.x kernels, and includes support for any Linux supported system, including
Itanium(R)2, x86_64, i686, and PPC.
These drivers are only supported as a loadable module at this time. Intel is not
supplying patches against the kernel source to allow for static linking of the
driver. A version of the driver may already be included by your distribution
and/or the kernel.org kernel. For questions related to hardware requirements, refer to the
documentation supplied with your Intel adapter. All hardware
requirements listed apply to use with Linux.
The following features are now available in supported kernels:
Native VLANs
Channel Bonding (teaming)
SNMP
Generic Receive Offload
Data Center Bridging
Channel Bonding documentation can be found in the Linux kernel source:
/Documentation/networking/bonding.txt
The driver information previously displayed in the /proc file system is not
supported in this release. Alternatively, you can use ethtool (version 1.6 or
later), lspci, and ifconfig to obtain the same information. Instructions on
updating ethtool can be found in the section Additional
Configurations later in this document.
The driver in this release is compatible with 82598, 82599 and X540-based Intel
Ethernet Network Connections.
For more information on how to identify your adapter, go to the Adapter &
Driver ID Guide at:
If your 82599-based
Intel® Network Adapter came with Intel optics or is an Intel® Ethernet
Server Adapter X520-2, then it only supports Intel optics and/or the
direct attach cables listed below.
When 82599-based SFP+ devices are connected back to back, they
should be set to the same Speed setting via ethtool. Results may
vary if you mix speed settings.
Supplier
Type
Part Numbers
SR Modules
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
FTLX8571D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDDZ-IN1
LR Modules
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
FTLX1471D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDDZ-IN1
The following is a list of 3rd party SFP+ modules and direct attach cables
that have received some testing. Not all modules are applicable to all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
Finisar
DUAL RATE 1G/10G SFP+ SR (No Bail)
FTLX8571D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ SR (No Bail)
AFBR-703SDZ-IN1
Finisar
DUAL RATE 1G/10G SFP+ LR (No Bail)
FTLX1471D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ LR (No Bail)
AFCT-701SDZ-IN1
Finisar
1000BASE-T SFP
FCLF8522P2BTL
Avago
1000BASE-T SFP
ABCU-5710RZ
HP
1000BASE-SX SFP
453153-001
<<<<<<< ixgb.htm
82599-based adapters support all passive and active limiting direct attach
cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications.
Laser turns off for SFP+ when ifconfig ethX down
"ifconfig ethX down" turns off the laser for 82599-based SFP+ fiber adapters. "ifconfig
ethX
up" turns on the laser.
82598-BASED ADAPTERS
NOTES:
Intel Ethernet Network Adapters
that support removable optical modules only support their original
module type (i.e., the Intel 10 Gigabit SR Dual Port Express Module
only supports SR optical modules). If you plug in a different type of
module, the driver will not load.
Hot Swapping/hot plugging
optical modules is not supported.
Only single speed, 10
gigabit modules are supported.
LAN on Motherboard (LOMs)
may support DA, SR, or LR modules. Other module types are not supported.
Please see your system documentation for details.
The following is a list of SFP+ modules and direct attach cables that have
received some testing. Not all modules are applicable to all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
82598-based adapters support all passive direct attach cables that comply
with SFF-8431 v4.1 and SFF-8472 v10.4 specifications. Active direct attach
cables are not supported.
THIRD PARTY OPTIC
MODULES AND CABLES REFERRED TO ABOVE ARE LISTED ONLY FOR THE PURPOSE OF
HIGHLIGHTING THIRD PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY, AND ARE NOT
RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF ANY THIRD PARTYS PRODUCT BY
INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE BY ANY THIRD PARTY AND
THE THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE INFORMATION REGARDING
CERTAIN OPTIC MODULES AND CABLES WITH THE ABOVE SPECIFICATIONS. THERE MAY BE
OTHER MANUFACTURERS OR SUPPLIERS, PRODUCING OR SUPPLYING OPTIC MODULES AND
CABLES WITH SIMILAR OR MATCHING DESCRIPTIONS. CUSTOMERS MUST USE THEIR OWN
DISCRETION AND DILIGENCE TO PURCHASE OPTIC MODULES AND CABLES FROM ANY THIRD PARTY OF THEIR CHOICE. CUSTOMERS ARE SOLELY
RESPONSIBLE FOR ASSESSING THE SUITABILITY OF THE PRODUCT AND/OR DEVICES AND FOR
THE SELECTION OF THE VENDOR FOR PURCHASING ANY PRODUCT. THE OPTIC MODULES AND
CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES
NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR SELECTION OF VENDOR
BY CUSTOMERS.
Building and Installation
To build a binary RPM* package of this driver, run 'rpmbuild
-tb ixgbe.tar.gz'.
NOTE: For the build to work properly, the currently running kernel
MUST match the version and configuration of the installed kernel sources. If you have just
recompiled the kernel, reboot the system before building.
RPM functionality has only
been tested in Red Hat distributions.
To manually build this driver:
Move the base driver tar file to the directory of your
choice. For example, use '/home/username/ixgbe' or '/usr/local/src/ixgbe'.
The install location listed above is the default location.
This may differ for various Linux distributions.
Load the module:
For kernel 2.6.x, use the modprobe command -
modprobe
ixgbe <parameter>=<value>
With 2.6 based kernels also
make sure that older ixgbe drivers are removed from the kernel, before
loading the new module:
rmmod ixgbe; modprobe ixgbe
Assign an IP address to the interface by entering the
following, where x is the interface number:
ifconfig ethX <IP_address>
netmask <netmask>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address of another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
To build ixgbe driver with DCA
If your kernel supports DCA, the driver will build by default with DCA enabled.
Command Line Parameters
If the driver is built as a module, the following optional parameters are
used by entering them on the command line with the modprobe command using
this syntax:
modprobe ixgbe [<option>=<VAL1>,<VAL2>,...]
There needs to be a <VAL#> for each network port in the system supported
by this driver. The values will be applied to each instance, in function
order. For example:
modprobe ixgbe InterruptThrottleRate=16000,16000
In this case, there are two network ports supported by ixgbe in the system.
The default value for each parameter is generally the recommended setting,
unless otherwise noted.
NOTES:
For more information about the AutoNeg, Duplex, and Speed parameters,
see the Speed and Duplex Configuration section in this document.
For more information about the InterruptThrottleRate, parameter, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.
A descriptor describes a data buffer and attributes related to
the data buffer. This information is accessed by the hardware.
Parameter Name
Valid Range/Settings
Default
Description
RSS - Receive Side Scaling (or multiple queues for receives)
0 - 16
1
0 = Sets the descriptor queue count to whichever is less, number of CPUS or
16
1-16 = Sets the descriptor queue count to 1-16
Default Value: 0
RSS also effects the number of transmit queues allocated on 2.6.23 and
newer kernels with CONFIG_NETDEVICES_MULTIQUEUE set in the kernel .config
file.
CONFIG_NETDEVICES_MULTIQUEUE only exists from 2.6.23 to 2.6.26. Other
options enable multiqueue in 2.6.27 and newer kernels.
MQ - Multi Queue
0, 1
1
0 = Disables Multiple Queue support
1 = Enables Multiple Queue support (a prerequisite for RSS)
DCA - Direct Cache Access
0, 1
1 (when IXGBE_DCA is enabled)
0 = Disables DCA support in the driver
1 = Enables DCA support in the driver
See the above instructions for enabling DCA. If the driver is enabled for
DCA this parameter allows load-time control of the feature.
IntMode
0-2 (0 = Legacy Int, 1 = MSI and 2 = MSIX)
2
IntMode controls allow load time control over the type of interrupt
registered for by the driver. MSI-X is required for multiple queue support,
and some kernels and combinations of kernel .config options will force a
lower level of interrupt support. 'cat /proc/interrupts' will show
different values for each type of interrupt.
InterruptThrottleRate
956-488281 (0=off, 1=dynamic)
1
Interrupt Throttle Rate (interrupts/sec). The ITR parameter controls how
many interrupts each interrupt vector can generate per second. Increasing ITR lowers
latency at the cost of increased CPU utilization, though it may help
throughput in some circumstances.
1 = Dynamic mode attempts to moderate
interrupts per vector while maintaining very low latency. This can sometimes
cause extra CPU utilization. If planning on deploying ixgbe in a latency
sensitive environment please consider this parameter.
0 = Setting
InterruptThrottleRate to 0 turns off any interrupt moderation and may
improve small packet latency, but is generally not suitable for bulk
throughput traffic due to the increased cpu utilization of the higher
interrupt rate. Please note that on 82599 and X540-based adapters, disabling InterruptThrottleRate will also result in the driver disabling HW RSC. On
82598-based adapters, disabling InterruptThrottleRate will also result in
disabling LRO (Large Receive Offloads).
LLI (Low Latency Interrupts)
LLI allows for immediate generation of an interrupt upon processing receive
packets that match certain criteria as set by the parameters described
below.
LLI parameters are not enabled when Legacy interrupts are used. You must be
using MSI or MSI-X (see cat /proc/interrupts) to successfully use LLI.
LLIPort
0 - 65535
0 (disabled)
LLI is configured with the LLIPort command-line parameter, which specifies
which TCP port should generate Low Latency Interrupts.
For example, using LLIPort=80 would cause the hardware to generate an
immediate interrupt upon receipt of any packet sent to TCP port 80 on the
local machine.
CAUTION: Enabling LLI can result in an excessive
number of interrupts/second that may cause problems with the system and in
some cases may cause a kernel panic.
LLIPush
0-1
0 (disabled)
LLIPush can be set to be enabled or disabled (default). It is most effective
in an environment with many small transactions.
NOTE: Enabling LLIPush may allow a denial of service attack.
LLISize
0-1500
0 (disabled)
LLISize causes an immediate interrupt if the board receives a packet smaller
than the specified size.
LLIEType
0-x8fff
0 (disabled)
Low Latency Interrupt Ethernet Protocol Type.
LLIVLANP
0-7
0 (disabled)
Low Latency Interrupt on VLAN priority threshold.
Flow Control
Ethernet Flow Control (IEEE 802.3x) can be configured with ethtool to
enable receiving and transmitting pause frames for ixgbe. When tx is
enabled, PAUSE frames are generated when the receive packet buffer crosses a
predefined threshold. When rx is enabled, the transmit unit will halt for
the time delay specified when a PAUSE frame is received.
Flow Control is
enabled by default. If you want to disable a flow control capable link
partner,
use ethtool:
ethtool -A eth? autoneg off rx off tx off
NOTE:
For 82598 backplane cards entering 1 gig mode, flow control default behavior
is changed to off. Flow control in 1 gig mode on these devices can lead to
Tx hangs.
Intel® Ethernet Flow Director
NOTE: Flow director parameters are only supported
on kernel versions 2.6.30 or later.
Supports advanced filters that direct receive packets by their flows to
different queues. Enables tight control on routing a flow in the platform.
Matches flows and CPU cores for flow affinity. Supports multiple parameters
for flexible flow classification and load balancing.
Flow director is enabled only if the kernel is multiple TX queue capable.
An included script (set_irq_affinity) automates setting the IRQ to CPU
affinity.
You can verify that the driver is using Flow Director by looking at the
counter in ethtool: fdir_miss and fdir_match.
Perfect Filter: Perfect filter is an interface to load the filter
table that funnels all flow
into queue_0 unless an alternative queue is specified using "action". In
that
case, any flow that matches the filter criteria will be directed to the
appropriate queue.
Support for Virtual Function (VF) is via the user-data field. You must
update
to the version of ethtool built for the 2.6.40 kernel. Perfect Filter is
supported on all kernels 2.6.30 and later. Rules may be deleted from the
table
itself. This is done via "ethtool -U ethX delete N" where N is the rule
number
to be deleted.
NOTE: Flow Director Perfect
Filters can run in single queue mode, when SR-IOV is enabled, or
when DCB is enabled.
If the queue is defined as -1, filter will drop matching packets.
To account for filter matches and misses, there are two stats in ethtool:
fdir_match and fdir_miss. In addition, rx_queue_N_packets shows the number of
packets processed by the Nth queue.
NOTE: Receive Packet Steering
(RPS) and Receive Flow Steering (RFS) are not
compatible with Flow Director. IF Flow Director is enabled, these will be
disabled.
NOTE: For VLAN Masks only 4
masks are supported.
NOTE: Once a rule is defined,
you must supply the same fields and masks (if masks are specified).
Support for UDP RSS
This feature adds an ON/OFF switch for hashing over certain flow types. You
can't turn on anything other than UDP. The default setting is disabled. We
only support enabling/disabling hashing on ports for UDP over IPv4 (udp4) or
IPv6 (udp6).
NOTE: Fragmented packets may
arrive out of order when RSS UDP support is configured.
Supported Ethtool Commands and Options:
-n --show-nfc
Retrieves the receive network flow classification configurations.
rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
Retrieves the hash options for the specified network traffic type.
-N --config-nfc
Configures the receive network flow classification.
rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
m|v|t|s|d|f|n|r...
Configures the hash options for the specified network traffic type.
udp4 UDP over IPv4
udp6 UDP over IPv6
f Hash on bytes 0 and 1 of the Layer 4 header of the rx packet.
n Hash on bytes 2 and 3 of the Layer 4 header of the rx packet.
The following is an example using udp4 (UDP over IPv4):
To include UDP port numbers in RSS hashing run:
ethtool -N ethX rx-flow-hash udp4 sdfn
To exclude UDP port numbers from RSS hashing run:
ethtool -N ethX rx-flow-hash udp4 sd
To display UDP hashing current configuration run:
ethtool -n ethX rx-flow-hash udp4
The results of running that call will be the following, if UDP hashing is
enabled:
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA
L4 bytes 0 & 1 [TCP/UDP src port]
L4 bytes 2 & 3 [TCP/UDP dst port]
The results if UDP hashing is disabled would be:
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA
The following two parameters impact Flow Director:
FdirPballoc
1-3 (1=64k, 2=128k, 3=256k)
1 (64k)
Flow Director allocated packet buffer size.
AtrSampleRate
0-255
20
Software ATR Tx packet sample rate. For example, when set to 20, every 20th
packet looks to see if the packet will create a new flow. A value of 0
indicates that ATR should be disabled and no samples will be taken.
max_vfs
1-63
0
If the value is greater than 0 it will also force the VMDq parameter
to be 1 or more.
This parameter adds support for SR-IOV. It causes the driver to spawn up to
max_vfs worth of virtual function.
NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering and VLAN tag stripping/insertion will remain enabled.
The parameters for the driver are referenced by position. So, if you have a
dual port 82599 or X540-based adapter and you want N virtual functions per port, you
must specify a number for each port with each parameter separated by a
comma.
For example:
modprobe ixgbe max_vfs=63,63
NOTE:
If both 82598 and 82599 or X540-based adapters are installed on the same machine,
you must be careful in loading the driver with the parameters. Depending on
system configuration, number of slots, etc. its impossible to predict in
all cases where the positions would be on the command line and the user will
have to specify zero in those positions occupied by an 82598 port.
With kernel 3.6, the driver supports the simultaneous usage of max_vfs and DCB features, subject to the constraints described below.
Prior to kernel 3.6, the driver did not support the simultaneous operation of max_vfs > 0 and the DCB features (multiple traffic classes utilizing Priority Flow Control and Extended Transmission Selection).
When DCB is enabled, network traffic is transmitted and received through multiple traffic classes (packet buffers in the NIC).
The traffic is associated with a specific class based on priority, which has a value of 0 through 7 used in the VLAN tag.
When SR-IOV is not enabled, each traffic class is associated with a set of RX/TX descriptor queue pairs.
The number of queue pairs for a given traffic class depends on the hardware configuration.
When SR-IOV is enabled, the descriptor queue pairs are grouped into pools.
The Physical Function (PF) and each Virtual Function (VF) is allocated a pool of RX/TX descriptor queue pairs.
When multiple traffic classes are configured (for example, DCB is enabled), each pool contains a queue pair from each traffic class.
When a single traffic class is configured in the hardware, the pools contain multiple queue pairs from the single traffic class.
The number of VFs that can be allocated depends on the number of traffic classes that can be enabled.
The configurable number of traffic classes for each enabled VF is as follows:
0 - 15 VFs = Up to 8 traffic classes, depending on device support
16 - 31 VFs = Up to 4 traffic classes
32 - 63 = 1 traffic class
When VFs are configured, the PF is allocated one pool as well.
The PF supports the DCB features with the constraint that each traffic class will only use a single queue pair.
When zero VFs are configured, the PF can support multiple queue pairs per traffic class.
L2LBen
0 = disable, 1 = enable (default)
1 (enable)
This parameter controls the internal switch (L2 loopback between pf and vf). By default the switch is enabled.
LRO
0(off), 1(on)
1 (on)
Enable/disable Large Receive Offload.
Additional Configurations
Configuring the Driver on Different Distributions
Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding an
alias line to /etc/modules.conf or etc/modprobe.conf, as well as editing other system startup scripts
and/or configuration files. Many popular Linux distributions ship with tools to
make these changes for you. To learn the proper way to configure a network
device for your system, refer to your distribution documentation. If during this
process you are asked for the driver or module name, the name for the Linux Base
Driver for the 10 Gigabit Family of Adapters is ixgbe.
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages on
your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved across reboots.
Jumbo Frames
The driver supports Jumbo Frames for all adapters. Jumbo Frames support
is enabled by changing the MTU to a value larger than the default of 1500. The
maximum value for the MTU is 9710. Use the ifconfig command to increase the MTU size.
For example, enter the following where <x> is the interface number:
ifconfig ethX mtu 9000 up
The maximum MTU setting for Jumbo Frames is 9710. This value coincides with
the maximum Jumbo Frames size of 9728. This driver will attempt to
use multiple page sized buffers to receive each jumbo packet. This should help
to avoid buffer starvation issues when allocating receive packets.
For 82599-based network connections, if you are enabling jumbo frames in a
virtual function (VF), jumbo frames must first be enabled in the physical
function (PF). The VF MTU setting cannot be larger than the PF MTU.
ethtool
The driver utilizes the ethtool interface for driver configuration and
diagnostics, as well as displaying statistical information. The latest ethtool
version is required for this functionality.
Large Receive Offload (LRO) is a technique for increasing inbound throughput
of high-bandwidth network connections by reducing CPU overhead. It works by
aggregating multiple incoming packets from a single stream into a larger buffer
before they are passed higher up the networking stack, thus reducing the number
of packets that have to be processed. LRO combines multiple Ethernet frames into
a single receive in the stack, thereby potentially decreasing CPU utilization
for receives.
IXGBE_NO_LRO is a compile time flag. The user can enable it
at compile time to remove support for LRO from the driver. The flag is used by
adding
CFLAGS_EXTRA="-DIXGBE_NO_LRO" to the make file when it's being compiled.
make CFLAGS_EXTRA="-DIXGBE_NO_LRO"
install
You can verify that the driver is using LRO by looking at these counters in
ethtool:
lro_flushed - the total number of receives using LRO.
lro_aggregated - counts the total number of Ethernet packets that were
combined.
NOTE: IPv6 and UDP are not
supported by LRO.
HW RSC
82599 and X540-based adapters support HW based
receive side coalescing (RSC) which can merge multiple frames from the same IPv4
TCP/IP flow into a single structure that can span one or more descriptors. It
works similarly to SW Large receive offload technique. By default
HW RSC is enabled and SW LRO can not be used for 82599 and X540-based adapters unless HW RSC is disabled.
IXGBE_NO_HW_RSC is a compile time flag. The
user can enable it at compile time to remove support for HW RSC from the driver.
The flag is used by adding CFLAGS_EXTRA="-DIXGBE_NO_HW_RSC" to the make file
when it's being compiled.
make
CFLAGS_EXTRA="-DIXGBE_NO_HW_RSC" install
You can verify that the driver is using
HW RSC by looking at the counter in ethtool:
hw_rsc_count - counts the total number of Ethernet packets
that were being combined.
rx_dropped_backlog
When in a non-Napi (or Interrupt) mode, this counter indicates that the stack
is dropping packets. There is an adjustable parameter in the stack that allows
you to adjust the amount of backlog. We recommend increasing the
netdev_max_backlog if the counter goes up.
# sysctl -a |grep
netdev_max_backlog
net.core.netdev_max_backlog =
1000
# sysctl -e
net.core.netdev_max_backlog=10000
net.core.netdev_max_backlog =
10000
Flow Control
Flow control is enabled by default. If you want to disable a flow
control capable link partner, use ethtool:
ethtool -A eth? autoneg off rx off tx off
MAC and VLAN anti-spoofing feature
When a malicious driver attempts to send a spoofed packet, it is dropped
by the hardware and not transmitted. An interrupt is sent to the PF driver
notifying it of the spoof attempt.
When a spoofed packet is detected the PF driver will send the following
message to the system log (displayed by the "dmesg" command):
ixgbe ethX: ixgbe_spoof_check: n
spoofed packets detected
Where x=the PF interface# n=the VF that attempted to do the spoofing.
Note that this feature can be disabled for a specific Virtual Function (VF).
Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool
You can set a MAC address of a Virtual Function (VF), a default VLAN and the
rate limit using the IProute2 tool. Download the latest version of the iproute2
tool from Sourceforge if your version does not have all the features you
require.
(WoL) Wake on LAN Support
Some adapters do not support Wake on LAN. To determine if your adapter
supports Wake on LAN, run
ethtool ethX
IEEE 1588 PTP
Precision Time Protocol (PTP) is used to synchronize clocks in a computer network and is supported in the ixgbe driver.
The IXGBE_PTP is a compile time flag. The user may enable PTP at compile time by adding CFLAGS_EXTRA="-DIXGBE_PTP" to the make file when it is being compiled.
make CFLAGS_EXTRA="-DIXGBE_PTP" install
Performance Tuning
An excellent article on performance tuning can be found at:
NOTE: After installing the driver, if your Intel
Ethernet Network Connection is not working, verify that you have installed the
correct driver.
MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
Kernel panics and instability may be observed on any MSI-X hardware if you use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.
Driver Compilation
When trying to compile the driver by running make install, the following error may occur: "Linux kernel source not configured - missing version.h"
To solve this issue, create the version.h file by going to the Linux source tree and entering:
make include/linux/version.h
Do Not Use LRO When Routing or Bridging Packets
Due to a known general compatibility issue with LRO and routing, do not use
LRO and iSCSI Incompatibility
LRO is incompatible with iSCSI target or initiator traffic.
A panic may occur when iSCSI traffic is received through the ixgbe driver with LRO enabled.
To workaround this, the driver should be built and installed with:
# make CFLAGS_EXTRA=-DIXGBE_NO_LRO install
Performance Degradation with Jumbo Frames
Degradation in throughput performance may be observed in some Jumbo frames
environments. If this is observed, increasing the application's socket buffer
size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.
See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt .
Multiple Interfaces on Same Ethernet Broadcast Network
Due to the ARP behavior on Linux, it is not possible to have one system on
two IP networks in the same Ethernet broadcast domain (non-partitioned switch)
behave as expected. All Ethernet interfaces will respond to IP traffic for any
IP address assigned to the system. This results in unbalanced receive traffic.
If you have multiple interfaces in a server, either turn on ARP filtering by
entering:
echo 1 >
/proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5), or install
the interfaces in separate broadcast domains (either in different switches or in
a switch partitioned to VLANs).
UDP Stress Test Dropped Packet Issue
Under small packets UDP stress test with 10GbE driver, the Linux system may
drop UDP packets due to the fullness of socket buffers. You may want to change
the driver's Flow Control variables to the minimum value for controlling packet
reception.
Or you can increase the kernel's default buffer sizes for UDP by changing the
values in
/proc/sys/net/core/rmem_default
and rmem_max
Unplugging network cable while ethtool -p is running
In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the
network cable while ethtool -p is running will cause the system to become
unresponsive to keyboard commands, except for control-alt-delete. Restarting the
system appears to be the only remedy.
Cisco Catalyst 4948-10GE port resets may cause switch to shut
down ports
82598-based hardware can re-establish link quickly and when connected to some
switches, rapid resets within the driver may cause the switch port to become
isolated due to "link flap". This is typically indicated by a yellow instead of
a green link light. Several operations may cause this problem, such as
repeatedly running ethtool commands that cause a reset.
A potential workaround is to use the Cisco IOS command "no errdisable detect
cause all" from the Global Configuration prompt which enables the switch to keep
the interfaces up, regardless of errors.
Installing Red Hat Enterprise Linux 4.7, 5.1, or 5.2 with an Intel(R) 10 Gigabit AT Server
Adapter may cause kernel panic
A known issue may cause a kernel panic or hang after installing an
82598AT-based Intel(R) 10 Gigabit AT Server Adapter in a Red Hat Enterprise Linux
4.7, 5.1, or 5.2 system. The ixgbe driver for both the install kernel and the runtime kernel
can create this panic if the 82598AT adapter is installed. Red Hat may release a
security update that contains a fix for the panic that you can download using
RHN (Red Hat Network) or Intel recommends that you install the ixgbe-1.3.31.5
driver or newer BEFORE installing the hardware.
Rx Page Allocation Errors
Page allocation failure. order:0 errors may occur under stress with kernels
2.6.25 and above. This is caused by the way the Linux kernel reports this
stressed condition.
DCB: Generic segmentation offload on causes bandwidth allocation issues
In order for DCB to work correctly, GSO (Generic Segmentation Offload aka
software TSO) must be disabled using ethtool. By default since the hardware
supports TSO (hardware offload of segmentation) GSO will not be running. The GSO
state can be queried with ethtool using ethtool -k ethX.
When using 82598-based network connections, ixgbe driver only supports 16 queues
on a platform with more than 16 cores
Due to known hardware limitations, RSS can only filter in a maximum of 16
receive queues.
82599 and X540-based network connections support up to 64 queues.
Disable GRO when routing/bridging
Due to a known kernel issue, GRO must be turned off when routing/bridging.
GRO can be turned off via ethtool.
ethtool -K ethX gro off
where ethX is the ethernet interface you're trying to modify.
Lower than expected performance on dual port and quad port 10GbE devices
Some PCI-E x8 slots are actually configured as x4 slots.
These slots have insufficient bandwidth for full 10Gbe line rate with dual port and quad port 10GbE devices.
In addition, if you put a PCIe Gen 3-capable adapter into a PCIe Gen 2 slot, you can not get full bandwidth.
The driver can detect this situation and will write the following message in the system log:
PCI-Express bandwidth available for this card is not sufficient for optimal performance.
For optimal performance a x8 PCI-Express slot is required.
If this error occurs, moving your adapter to a true x8 slot will resolve the issue.
ethtool may incorrectly display SFP+ fiber module as Direct Attached cable
Due to kernel limitations, port type can only be correctly displayed on kernel 2.6.33 or greater.
Under Redhat 5.4 - System May Crash when Closing Guest OS Window after Loading/Unloading Physical Function (PF) Driver
Do not remove the ixgbe driver from Dom0 while Virtual Functions (VFs) are assigned to guests.
VFs must first use the xm "pci-detach" command to hot-plug the VF device out of the VM it is assigned to or else shut down the VM.
Unloading Physical Function (PF) Driver Causes System Reboots When VM is Running and VF is Loaded on the VM
On pre-3.2 Linux kernels unloading the Physical Function (PF) driver causes system reboots when the VM is running and VF is loaded on the VM.
Do not unload the PF driver (ixgbe) while VFs are assigned to guests.
Running ethtool -t ethX command causes break between PF and test client
When there are active VFs, "ethtool -t" will only run the link test.
The driver will also log in syslog that VFs should be shut down to run a full diags test.
SLES10 SP3 random system panic when reloading driver
This is a known SLES-10 SP3 issue. After requesting interrupts for MSI-X vectors, system may panic.
Currently the only known workaround is to build the drivers with CFLAGS_EXTRA=-DDISABLE_PCI_MSI if the driver need to be loaded/unloaded.
Otherwise the driver can be loaded once and will be safe, but unloading it will lead to the issue.
Enabling SR-IOV in a 32-bit or 64-bit Microsoft* Windows* Server 2008/R2 Guest OS using Intel® 82576-based GbE, Intel® 82599 or X540-based 10GbE controller under KVM
KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM.
This includes traditional PCIe devices, as well as SR-IOV-capable devices using Intel 82576-based and 82599 or X540-based controllers.
While direct assignment of a PCIe device or an SR-IOV Virtual Function (VF) to a Linux-based VM running 2.6.32 or later kernel works fine, there is a known issue with Microsoft Windows Server 2008/R2 VM that results in a "yellow bang" error.
This problem is within the KVM VMM itself, not the Intel driver, or the SR-IOV logic of the VMM, but rather that KVM emulates an older CPU model for the guests, and this older CPU model does not support MSI-X interrupts, which is a requirement for Intel SR-IOV.
If you wish to use the Intel 82576, 82599 or X540-based controllers in SR-IOV mode with KVM and a Microsoft Windows Server 2008/R2 guest try the following workaround.
The workaround is to tell KVM to emulate a different model of CPU when using qemu to create the KVM guest:
"-cpu qemu64,model=13"
Loading ixgbe driver in 3.2.x and above kernels displays kernel tainted message
Due to recent kernel changes, loading an out of tree driver will cause the kernel to be tainted.
Unable to obtain DHCP lease on boot with RedHat
For configurations where the auto-negotiation process takes more than 5 seconds, the boot script may fail with the following message:
ethX: failed. No link present. Check cable?
If this error appears even though the presence of a link can be confirmed using ethtool ethX, try setting
LINKDELAY=5 in /etc/sysconfig/network-scripts/ifcfg-ethX.
NOTE: Link time can take up to 30 seconds.
Adjust LINKDELAY value accordingly.
Host may Reboot after Removing PF when VF is Active in Guest
Using kernel versions earlier than 3.2, do not unload the PF driver with
active VFs. Doing this will cause your VFs to stop working until you reload the
PF driver and may cause a spontaneous reboot of your system.
Software bridging does not work with SR-IOV Virtual Functions
SR-IOV Virtual Functions are unable to send or receive traffic between VMs
using emulated connections on a Linux Software bridge and connections that use
SR-IOV VFs.
Support
For general information, go to the Intel support website at:
If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to the
issue to linux.nics@intel.com.
The ixgbevf driver supports 82599 and X540-based virtual function devices that can only be
activated on kernels that support SR-IOV. SR-IOV requires the correct
platform and OS support.
The ixgbevf driver requires the ixgbe driver, version 2.0 or later.
The ixgbevf driver supports virtual functions generated by the ixgbe driver with a max_vfs value of 1 or greater.
For more information on the max_vfs parameter refer to the section on the the ixgbe driver.
The guest OS loading the ixgbevf driver must support MSI-X interrupts.
This driver is only supported as a loadable module at this time.
Intel is not supplying patches against the kernel source to allow for static linking of the driver.
For questions related to hardware requirements, refer to the documentation supplied with your Intel Gigabit adapter.
All hardware requirements listed apply to use with Linux.
Instructions on updating ethtool can be found in the section Additional Configurations later in this document.
VLANs: There is a limit of a total of 64 shared VLANs to 1 or more VFs.
Building and Installation
To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'.
Replace <filename.tar.gz> with the specific filename of the driver.
NOTE: For the build to work
properly, the currently running kernel MUST match the version and
configuration of the installed kernel sources. If you have just recompiled
the kernel reboot the system now.
RPM functionality has only been tested in Red Hat distributions.
Move the base driver tar file to the directory of your
choice. For example, use ' /home/username/ ixgbevf or /usr/local/src/
ixgbevf.'.
The install location listed above is the default location.
This may differ for various Linux distributions.
Load the module using the modprobe
command:
modprobe ixgbevf
With 2.6 based kernels also make sure that older e1000e drivers are removed
from the kernel, before loading the new module:
rmmod ixgbevf; modprobe
ixgbevf
Assign an IP address to the interface by entering the
following, where <x> is the interface number:
ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
Command Line Parameters
If the driver is built as a module, the following optional parameters are
used by entering them on the command line with the modprobe command using
this syntax:
modprobe ixgbevf [<option>=<VAL1>,<VAL2>,...]
There needs to be a <VAL#> for each network port in the system supported
by this driver. The values will be applied to each instance, in function
order. For example:
In this case, there are two network ports supported by ixgbevf in the system.
The default value for each parameter is generally the recommended setting,
unless otherwise noted.
NOTES:
For more information about the AutoNeg, Duplex, and Speed parameters,
see the Speed and Duplex Configuration section in this document.
For more information about the InterruptThrottleRate, parameter, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm.
A descriptor describes a data buffer and attributes related to
the data buffer. This information is accessed by the hardware.
Parameter Name
Valid Range/Settings
Default
Description
InterruptThrottleRate
0,1,956-488281 (0=off, 1=dynamic)
8000
The driver can limit the amount of interrupts per second that the adapter
will generate for incoming packets. It does this by writing a value to
the adapter that is based on the maximum amount of interrupts that the
adapter will generate per second.
Setting InterruptThrottleRate to a value greater or equal to 100
will program the adapter to send out a maximum of that many interrupts
per second, even if more packets have come in. This reduces interrupt
load on the system and can lower CPU utilization under heavy load, but
will increase latency as packets are not processed as quickly.
The default behaviour of the driver previously assumed a static
InterruptThrottleRate
value of 8000, providing a good fallback value for all traffic types,
but lacking in small packet performance and latency. The hardware can
handle many more small packets per second however, and for this reason
an adaptive interrupt moderation algorithm was implemented.
The driver has one adaptive mode (setting 1) in which
it dynamically adjusts the InterruptThrottleRate value based on the traffic that it
receives. After determining the type of incoming traffic in the last
timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that
traffic.
The algorithm classifies the incoming traffic every interval into
classes. Once the class is determined, the InterruptThrottleRate value is adjusted to
suit that traffic type the best. There are three classes defined: "Bulk
traffic", for large amounts of packets of normal size; "Low latency",
for small amounts of traffic and/or a significant percentage of small
packets; and "Lowest latency", for almost completely small packets or
minimal traffic.
In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic
that falls in class "Bulk traffic". If traffic falls in the "Low
latency"
or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This
default mode is suitable for most applications.
For situations where low latency is vital such as cluster or grid
computing, the algorithm can reduce latency even more when
InterruptThrottleRate is set to mode 1. In this mode, the InterruptThrottleRate will be increased stepwise to 70000 for
traffic in class "Lowest latency".
Setting InterruptThrottleRate to 0 turns off any interrupt moderation
and may improve small packet latency, but is generally not suitable
for bulk throughput traffic
NOTE:
Dynamic interrupt throttling is only applicable to adapters
operating in MSI or Legacy interrupt mode, using a single
receive queue.
NOTE:
When ixgbevf is loaded with default settings and multiple adapters are in
use simultaneously, the CPU utilization may increase non-linearly. In
order to limit the CPU utilization without impacting
the overall throughput, we recommend that you load the driver as
follows:
This sets the InterruptThrottleRate to 3000 interrupts/sec for the first,
second, and third instances of the driver. The range of 2000 to 3000
interrupts per second works on a majority of systems and is a good
starting point, but the optimal value will be platform-specific. If CPU
utilization is not a concern, use default driver settings.
Additional Configurations
Configuring the Driver on Different Distribution
Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding an
alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other
system startup scripts and/or configuration files. Many popular Linux
distributions ship with tools to make these changes for you. To learn the proper
way to configure a network device for your system, refer to your distribution
documentation. If during this process you are asked for the driver or module
name, the name for the Linux Base Driver for the Gigabit Family of Adapters is
ixgbevf.
As an example, if you install the ixgbevf driver for two Gigabit adapters (eth0
and ethX) and want to set the interrupt mode to MSI-X and MSI respectively, add
the following to modules.conf or /etc/modprobe.conf:
alias eth0 ixgbevf
alias eth1 ixgbevf
options ixgbevf InterruptThrottleRate=3,1
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages on
your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved
across reboots.
ethtool
The driver utilizes the ethtool interface for driver configuration and
diagnostics, as well as displaying statistical information. ethtool version 3.0
or later is required for this functionality, although we strongly recommend
downloading the latest version at:
ixgbevf supports MACVLAN on those kernels that have the feature included. Kernel support for MACVLAN can be tested by checking if the MACVLAN driver is loaded. The user can run 'lsmod | grep macvlan' to see if the MACVLAN driver is loaded or run 'modprobe macvlan' to try to load the MACVLAN driver.
It may be necessary to update to a recent release of the iproute2 package to get support of MACVLAN via the 'ip' command.
Known Issues/Troubleshooting
NOTE: After installing the driver, if your Intel Network
Connection is not working, verify that you have installed the correct
driver.
Driver Compilation
When trying to compile the driver by running make install, the following
error may occur:
"Linux kernel source not configured - missing version.h"
To solve this issue, create the version.h file by going to the Linux source tree
and entering:
make include/linux/version.h.
Multiple Interfaces on Same Ethernet Broadcast Network
Due to the default ARP behavior on Linux, it is not possible to have one
system on two IP networks in the same Ethernet broadcast domain (non-partitioned
switch) behave as expected. All Ethernet interfaces will respond to IP traffic
for any IP address assigned to the system. This results in unbalanced receive
traffic.
If you have multiple interfaces in a server, either turn on ARP filtering by
entering:
echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
(this only works if your kernel's version is higher than 2.4.5)
NOTE: This setting is not saved across reboots. The
configuration change can be made permanent by adding the line:
net.ipv4.conf.all.arp_filter = 1
to the file /etc/sysctl.conf
or,
install the interfaces in separate broadcast domains (either in
different switches or in a switch partitioned to VLANs).
Build error with Asianux 3.0 - redefinition of typedef 'irq_handler_t'
Some systems may experience build issues due to redefinition of irq_handler_t.
To resolve this issue build the driver (step 4 above) using the command:
make CFLAGS_EXTRA=-DAX_RELEASE_CODE=1
install
MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
Kernel panics and instability may be observed on any MSI-X hardware if you
use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are
encountered, you may disable the irqbalance daemon or upgrade to a newer kernel.
Rx Page Allocation Errors
Page allocation failure. order:0 errors may occur under stress with kernels
2.6.25 and above. This is caused by the way the Linux kernel reports this
stressed condition.
Host may Reboot after Removing PF when VF is Active in Guest
Using kernel versions earlier than 3.2, do not unload the PF driver with
active VFs. Doing this will cause your VFs to stop working until you reload the
PF driver and may cause a spontaneous reboot of your system.
Support
For general information, go to the Intel support website at:
If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to the
issue to linux.nics@intel.com.
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA
Intel Corporation assumes no responsibility for errors or omissions in this document.
Nor does Intel make any commitment to update the information contained herein.
Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.
*Other names and brands may be claimed as the property of others.
Last modified on 1/25/11 10:21p Revision
DOCS/LINUX/license.htm 0000755 0000000 0000000 00000037564 11736273470 011563 0 ustar
Software License
INTEL SOFTWARE LICENSE AGREEMENT
IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.
By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement.
If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.
LICENSES:
Please Note:
If you are a network or system administrator, the “Site License” below shall apply to you.
If you are an end user, the “Single User License” shall apply to you.
If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.
SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute, or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
SINGLE USER LICENSE:
You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute, or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
OEM LICENSE:
You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
You may only distribute the Software to your customers pursuant to a written
license agreement. Such license agreement may be a "break-the-seal" license
agreement. At a minimum such license shall safeguard Intel's ownership rights to
the Software.
You may not distribute, sublicense or transfer the Source Code form of any
components of the Software and derivatives thereof to any third party without
the express written consent of Intel.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
LICENSE RESTRICTIONS.
You may NOT: (i) use or copy the Software except as provided in this Agreement;
(ii) rent or lease the Software to any third party; (iii) assign this Agreement
or transfer the Software without the express written consent of Intel; (iv)
modify, adapt, or translate the Software in whole or in part except as provided
in this Agreement; (v) reverse engineer, decompile, or disassemble the Software;
(vi) attempt to modify or tamper with the normal function of a license manager
that regulates usage of the Software; (vii) distribute, sublicense or transfer
the Source Code form of any components of the Software and derivatives thereof
to any third party without the express written consent of Intel; (viii) permit,
authorize, license or sublicense any third party to view or use the Source Code;
(ix) modify or distribute the Source Code or Software so that any part of it
becomes subject to an Excluded License. (An "Excluded License" is one that
requires, as a condition of use, modification, or distribution, that (a) the
code be disclosed or distributed in source code form; or (b) others have the
right to modify it.); (x) use or include the Source Code or Software in
deceptive, malicious or unlawful programs.
NO OTHER RIGHTS.
No rights or licenses are granted by Intel to you, expressly or by implication,
with respect to any proprietary information or patent, copyright, mask work,
trademark, trade secret, or other intellectual property right owned or
controlled by Intel, except as expressly provided in this Agreement. Except as
expressly provided herein, no license or right is granted to you directly or by
implication, inducement, estoppel, or otherwise. Specifically, Intel grants no
express or implied right to you under Intel patents, copyrights, trademarks, or
other intellectual property rights.
OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is
licensed, not sold. Title to all copies of the Software remains with Intel. The
Software is copyrighted and protected by the laws of the United States and other
countries and international treaty provisions. You may not remove any copyright
notices from the Software. You agree to prevent any unauthorized copying of the
Software. Intel may make changes to the Software, or to items referenced
therein, at any time without notice, but is not obligated to support or update
the Software.
ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the
Software you are installing or using under this Agreement is pre-commercial
release or is labeled or otherwise represented as alpha- or beta- versions
of the Software ("pre-release Software"), then the following terms apply. To the
extent that any provision in this Section conflicts with any other term(s) or
condition(s) in this Agreement with respect to pre-release Software, this
Section shall supersede the other term(s) or condition(s), but only to the
extent necessary to resolve the conflict. You understand and acknowledge that
the Software is pre-release Software, does not represent the final Software from
Intel, and may contain errors and other problems that could cause data loss,
system failures, or other errors. The pre-release Software is provided to you
"as-is" and Intel disclaims any warranty or liability to you for any damages
that arise out of the use of the pre-release Software. You acknowledge that
Intel has not promised that pre-release Software will be released in the future,
that Intel has no express or implied obligation to you to release the
pre-release Software and that Intel may not introduce Software that is
compatible with the pre-release Software. You acknowledge that the entirety of
any research or development you perform that is related to the pre-release
Software or to any product making use of or associated with the pre-release
Software is done at your own risk. If Intel has provided you with pre-release
Software pursuant to a separate written agreement, your use of the pre-release
Software is also governed by such agreement.
LIMITED MEDIA WARRANTY. If the Software has been
delivered by Intel on physical media, Intel warrants the media to be free from
material physical defects for a period of ninety days after delivery by Intel.
If such a defect is found, return the media to Intel for replacement or
alternate delivery of the Software as Intel may select.
EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE,
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY
KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A
PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for
the accuracy or completeness of any information, text, graphics, links, or other
items contained within the Software.
LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS
SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION,
LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE
OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION
OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO
THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS
THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use
the Software in conjunction with a virtual (emulated) device designed to
appear as an Intel component product, you acknowledge that Intel is neither the
author nor the creator of the virtual (emulated) device. You understand and
acknowledge that Intel makes no representations about the correct operation of
the Software when used with a virtual (emulated) device, that Intel did not
design the Software to operate in conjunction with the virtual (emulated)
device, and that the Software may not be capable of correct operation in
conjunction with the virtual (emulated) device. You agree to assume the risk
that the Software may not operate properly in conjunction with the virtual
(emulated) device. You agree to indemnify and hold Intel and its officers,
subsidiaries and affiliates harmless against all claims, costs, damages, and
expenses, and reasonable attorney fees arising out of, directly or indirectly,
any claim of product liability, personal injury or death associated with the use
of the Software in conjunction with the virtual (emulated) device, even if
such claim alleges that Intel was negligent regarding the design or manufacture
of the Software.
UNAUTHORIZED USE.THE SOFTWARE IS NOT DESIGNED,
INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH
THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR
DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS).
If you use the Software for any such unintended or unauthorized use, you shall
indemnify and hold Intel and its officers, subsidiaries and affiliates harmless
against all claims, costs, damages, and expenses, and reasonable attorney fees
arising out of, directly or indirectly, any claim of product liability, personal
injury or death associated with such unintended or unauthorized use, even if
such claim alleges that Intel was negligent regarding the design or manufacture
of the part.
TERMINATION OF THIS AGREEMENT.
Intel may terminate this Agreement at any time if you violate its terms.
Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.
APPLICABLE LAWS.
Claims arising under this Agreement shall be governed by the laws of the State
of California, without regard to principles of conflict of laws. You agree that
the terms of the United Nations Convention on Contracts for the Sale of Goods do
not apply to this Agreement. You may not export the Software in violation of
applicable export laws and regulations. Intel is not obligated under any other
agreements unless they are in writing and signed by an authorized representative
of Intel.
GOVERNMENT RESTRICTED RIGHTS.
The enclosed Software and documentation were developed at private expense, and
are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS
252.227-7013 et seq. or its successor. The use of this product by the Government
constitutes acknowledgement of Intels proprietary rights in the Software.
Contractor or Manufacturer is Intel.
LANGUAGE; TRANSLATIONS.
In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.
For general information and support, see the Support
page.
If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to the
issue to linux.nics@intel.com.
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.
DOCS/LINUX/test_ln.htm 0000755 0000000 0000000 00000010573 11660720040 011562 0 ustar
Test the Adapter
Adapter Testing Using Ethtool
Intel adapters have built-in self-test diagnostics, such as I/O conflicts,
memory faults, EEPROM operability, and basic transmit/receive operation. This
can help determine if there is a hardware fault due to the adapter or cable
connectivity. This testing capability is built into the adapter and is accessed
via the driver. Ethtool (version 1.6 or later) is used as the interface for the diagnostic tests and
results.
Ethtool is an open-source program that can be used as an interface to provide
driver configuration and diagnostics, as well as displaying statistical
information.
To invoke diagnostics from ethtool, enter this command:
ethtool -t <EthX>
where <EthX> is the name of the Ethernet device under test (e.g., "eth0").
Here is a sample of the diagnostics output:
The test result is PASS
Register test (offline).......... Passed
EEPROM test (offline).......... Passed
Interrupt test (offline).......... Passed
Loopback test (offline).......... Passed
Link test (on/offline).......... Passed
By default, the more comprehensive "offline" test set is invoked. This will
momentarily disrupt any active traffic on the device under test. The set of
available diagnostic tests is determined internally by the NIC. The tests that
are run are determined by the ethtool command line parameters.
The following tests are common to many Intel adapters:
Test Name
Description
Test Results
Register Test
Test patterns are written, read and verified through the adapter's
device registers to ensure proper functionality.
Test failure may indicate a faulty adapter.
FIFO Test
This utility will write test bit patterns to the adapter's FIFO
buffers, to make sure the FIFOs are working properly. Not all adapters
have FIFO buffers, so it may not appear in your test results.
Test failure may indicate a faulty adapter.
EEPROM Test
This test is run if the adapter is equipped with this type of
memory. It tests both the readability of the EEPROM and the integrity of
the data via checksum.
Test failure may indicate a faulty adapter.
Interrupt Test
This tests the adapter's ability to generate an interrupt. This test
sets the interrupt cause register and reads the interrupt set register,
verifying the adapter correctly registered an internal interrupt.
Test failure may indicate a faulty adapter.
Loopback Test
There are two internal loopback tests: MAC (media access controller)
Loopback and PHY (LAN controller) Loopback. Neither test requires an
external loopback connection or responder. These tests set the adapter
in the appropriate loopback mode and send packets back through the
adapter's receive circuitry and logic.
Test failure may indicate a faulty adapter.
Link Test
This checks to see whether or not the adapter has established link
with its link partner.
If this test fails, check the cable connection and the status of the
link partner.
Check for interrupt conflicts and sharing problems. Make sure the other adapter supports shared
interrupts. Also, make sure your operating system supports shared interrupts.
Unload all PCI device drivers, then reload all drivers.
Adapter unable to connect to switch at correct speed. Gigabit adapter connects
at 100 Mbps and 10 gigabit adapter connects at 1000 Mbps.
This is applicable only to copper-based connections.
Make sure the adapter and the link partner are set to auto-negotiate.
Verify that you are running the latest operating system
revision for your switch and that the switch is compliant with the proper IEEE
standard:
IEEE 802.3ad-compliant (gigabit over copper)
IEEE 802.3an-compliant (10 gigabit over copper)
The adapter stops working without apparent cause
Run the adapter and network tests described under
"Test
the Adapter".
The Link indicator light is off
Run the adapter and network tests described under
"Test
the Adapter".
Make sure the proper (and latest) driver is loaded.
Make sure that the link partner is configured to
auto-negotiate (or forced to match adapter)
Verify that the switch is IEEE 802.3ad-compliant.
The link light is on, but communications
are not properly established
Make sure the proper (and latest) driver is
loaded.
Both the adapter and its link partner must be set to either
auto-detect or manually
set to the same speed and duplex settings.
NOTE: The adapter's link indicator
light may be on even if
communications between the adapter and its link partner have not been
properly established. Technically, the link indicator
light
represents the presence of a carrier signal but not necessarily the
ability to properly communicate with a link partner. This is
expected behavior and is consistent with IEEE's specification for
physical layer operation.
RX or TX light is off
Network may be idle; try creating traffic while
monitoring the lights.
The diagnostic utility reports the adapter is
"Not enabled by BIOS"
When configuring a multi-adapter environment, you must upgrade all Intel
adapters in the computer to the latest software.
If the computer has trouble detecting all adapters, consider the following:
If you enable Wake on LAN* (WoL) on more than two
adapters, the Wake on LAN feature may overdraw your systems auxiliary power
supply, resulting in the inability to boot the system and other
unpredictable problems. For multiple desktop/management adapters, it is
recommended that you install one adapter at a time and use the IBAUtil
utility (ibautil.exe in \APPS\BOOTAGNT) to disable the WoL feature on adapters
that do not require WoL capabilities. On server adapters, the WoL
feature is disabled by default.
Adapters with Intel Boot Agent enabled will require a
portion of the limited start up memory for each adapter enabled. Disable the
service on adapters that do not need to boot Pre-Boot Execution Environment (PXE).
PCI / PCI-X / PCI Express Configuration
If the adapter is not recognized by your OS or if it does not
work you may need to change some BIOS settings. Try the following
only if you are having problems with the adapter and are familiar with BIOS
settings.
Check to see that the "Plug-and-Play" setting is
compatible with the operating system you are using.
Make sure the slot is enabled.
Install the
adapter in a bus-master slot.
Configure interrupts for level-triggering, as opposed to
edge-triggering.
Reserve interrupts and/or memory addresses. This prevents
multiple buses or bus slots from using the same interrupts. Check the BIOS
for IRQ options for PCI / PCI-X / PCIe.
Here are some examples of BIOS parameters:
PCI / PCI-X / PCIe slot #: Slot where the adapter is installed Master: ENABLED Slave: ENABLED Latency timer: 40 - 80 Interrupt: Choose any one of several that the BIOS provides. Edge-level: Level
The exact wording of the parameters varies with different computers.
Attaining the best speed requires that many components are operating at peak
efficiency. Among them are the following:
Cable quality and length - Do not exceed the maximum
recommended length for your cable type. Shorter lengths often provide better
results. Check for loose or damaged connectors. Check the cable for kinked
or damaged sections.
Bus speed and traffic - The PCI bus speed
accommodates the slowest PCI card installed. Check to see if you have a card
that is slowing down your system.
Processor and Memory - Check your performance
monitoring programs to see if traffic is being affected by your processor
speed, available memory or other processes.
Transmission frame size - Your network performance
may be enhanced by adjusting or maximizing the transmission frame size.
Operating systems, switches and adapters will impose varying limits on
maximum frame size. See the discussion on Jumbo Frames for your OS.
Operating System - Networking feature
implementation will vary by operating system version, such as offloading and multiprocessor threading.
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.
oOT[\]ݥΡBN~B~ΡBBB״_BaBw˩Τըld~CpGo{d~岫AIntel |ۦܧKOέ״_w鲣~AOHU]ߪp~AΪ̬OApGzѸӤd~Muh٧Ʊvv(Return Material Authorization) X (аѦҥHU) HʶRҩ (pG|U) zʶR~sө IntelAôѷ岫A]iHhٱzʶRBCpGzBeӤd~Ah]lοICz@wnϥέӪe]ά۵^äIBeOΡC
Installation des Intel® Ethernet 10-Gigabit-Server-Adapters
Einen Adapter installieren
Schalten Sie den Computer aus und ziehen Sie den Netzstecker aus der Steckdose. Wenn Sie eine Hot-Plug-Installation ausfhren, lesen Sie zuerst die Serverdokumentation.
Entfernen Sie die Computerabdeckung und die Blende des Adaptersteckplatzes, der fr Ihren Adapter passt. Sie knnen ohne negative Folgen einen Steckplatz benutzen, der lnger ist als der Anschluss Ihres Adapters; versuchen Sie jedoch nicht, den Adapter in einem Steckplatz zu installieren, der krzer ist als der PCI-Express-Anschluss.
Setzen Sie den Adapter fest in den Steckplatz ein und befestigen Sie die Halterung.
Bringen Sie die Computerabdeckung wieder an. Stecken Sie die Netzverbindung ein.
Eine Mezzanine-Erweiterungskarte installieren
Schalten Sie den Computer aus und ziehen Sie den Netzstecker aus der Steckdose.
Entfernen Sie die Computerabdeckung.
Richten Sie den PCIe-Anschluss der Mezzanine-Erweiterungskarte mit dem Anschluss und den vier Abstandhaltern aus Kunststoff am Mainboard aus.
Drcken Sie den Adapter in den Anschluss der Mezzanine-Karte, bis er fest sitzt und in den vier Abstandhaltern eingerastet ist.
Bringen Sie die Computerabdeckung wieder an. Stecken Sie die Netzverbindung ein.
Schlieen Sie das Netzwerkkabel an
Intel® Ethernet 10-Gigabit-Kupfer-Adapter: Verwenden Sie Ethernetkabel der Kategorie 6, 6a oder 7.
Intel® Ethernet 10-Gigabit-Server-Adapter mit anschliebarem SFP+-Optics-Modul: Installieren Sie das Modul und schlieen Sie das Kabel entsprechend den Herstelleranweisungen fr das Modul an.
Intel® Ethernet 10-Gigabit-Glasfaseradapter mit SC-Steckverbinder: Entfernen Sie die Abdeckung des Glasfaseranschlusses und bewahren Sie sie gut auf. Stecken Sie einen SC-Glasfaser-Steckverbinder in die TX/RX-Anschlsse der Adapterklammer.
Intel® Ethernet 10-Gigabit-Glasfaseradapter mit LC-Steckverbinder: Entfernen Sie die Abdeckung des Glasfaseranschlusses und bewahren Sie sie gut auf. Stecken Sie einen LC-Steckverbinder in den Adapter. Sie knnen Kabel anderer Verbindungstypen (wie SC) verwenden, wenn die Kabel den optischen Spezifikationen des Adapters, einschlielich der Lngenbegrenzung, entsprechen.
Intel® Ethernet 10-Gigabit-CX4-Adapter: Die Kabel mssen den Spezifikationen des IEEE-Standards 802.3ak, Klausel 54 entsprechen. Der erforderliche Kabelanschluss ist ein aufklappbarer MDI-Steckplatz wie in IEC 61076-3-113 definiert.
Starten Sie den Computer und folgen Sie nachfolgenden Anweisungen zur Treiberinstallation.
Treiber und Intel® PROSet Software installieren
Microsoft* Windows*-Betriebssysteme
HINWEISE:
Fr die Installation von Treibern sind Administratorrechte fr das Betriebssystem erforderlich.
Die untersttzten Betriebssysteme finden Sie auf der Seite "Systemanforderungen" im Intel 10GbE Adapter-Handbuch.
Beim Start von Windows wird der Adapter als neue Hardware erkannt. So installieren Sie den Treiber richtig:
Der Adapter wird erkannt, und Windows installiert entweder einen in Windows residenten Treiber oder startet den Assistent fr das Suchen neuer Hardware
.
Wenn der Assistent gestartet wird, folgen Sie den Aufforderungen, um den Treiber von der CD dieses Pakets zu installieren.
Wenn ein in Windows residenter Treiber installiert wird (Assistent wird nicht angezeigt), aktualisieren Sie den Treiber durch Einlegen der Intel CD. Klicken Sie auf die Schaltflche Treiber und Software installieren , wenn das Fenster Intel Netzwerkanschlsse
angezeigt wird.
Linux
Um ein binres RPM*-Paket dieses Treibers zu erstellen, fhren Sie 'rpmbuild -tb <dateiname.tar.gz>' aus. Ersetzen Sie <dateiname.tar.gz> mit dem Dateinamen des Treibers.
HINWEIS: Damit das erstellte Paket ordnungsgem funktioniert, MUSS der gegenwrtig ausgefhrte Kernel mit der Version und der Konfiguration der installierten Kernelquellen bereinstimmen. Wenn Sie den Kernel gerade neu kompiliert haben, fhren Sie jetzt einen Systemneustart aus.
Die RPM-Funktionalitt wurde bisher nur in Red Hat-Verteilungen getestet.
Verschieben Sie die Basistreiber-Tardatei in ein Verzeichnis Ihrer Wahl. Verwenden Sie beispielsweise '/home/username/ixgb' oder '/usr/local/src/ixgb'.
Entpacken/dekomprimieren Sie das Archiv, wobei <x.x.x> die Versionsnummer des Treibertars ist:
tar zxf ixgb-<x.x.x>.tar.gz
Wechseln Sie durch folgende Eingabe zum src-Verzeichnis des Treibers ber, wobei <x.x.x> die Versionsnummer des Treibertars ist:
Die oben aufgefhrten Installationsverzeichnisse sind die Standardverzeichnisse. Sie sind mglicherweise fr bestimmte Linux-Distributionen nicht richtig.
Installieren Sie das Modul:
modprobe ixgb <parameter>=<value>
Weisen Sie der Schnittstelle durch folgende Eingabe eine IP-Adresse zu, wobei <x> fr die Schnittstellennummer steht:
ifconfig eth<x> <IP_address>
Prfen Sie, ob die Schnittstelle funktioniert. Geben Sie Folgendes ein, wobei <IP_address> die IP-Adresse eines anderen Computers in dem Subnetz ist, in dem die Schnittstelle getestet wird:
ping <IP_address>
FreeBSD
Aufbau und Installation
Dieser Treiber wurde fr die Verwendung mit FreeBSD-Kernel Version 4.8 oder hher entwickelt.
HINWEIS: Sie mssen Kernelquellen installiert haben, damit Sie das Treibermodul kompilieren knnen.
Bei den untenstehenden Anleitungen ist x.x.x die Treiberversion, wie sie im Namen der Treibertardatei angegeben ist.
Verschieben Sie die Basistreiber-Tardatei in ein Verzeichnis Ihrer Wahl. Verwenden Sie beispielsweise /home/username/ixgb oder
/usr/local/src/ixgb.
Dekomprimieren Sie das Archiv:
tar xfz ixgb-x.x.x.tar.gz
Hierdurch wird das Verzeichnis ixgb-x.x.x erstellt.
So installieren Sie die man-Seite:
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
Um den Treiber in einem laufenden System zu laden, fhren Sie die folgenden Schritte aus:
cd ixgb-x.x.x
make
ODER
cd ixgb-x.x.x/src
make load
Um der Schnittstelle eine IP-Adresse zuzuweisen, geben Sie Folgendes ein:
ifconfig ixgb<Schnittstellennummer>
<IP-Adresse>
Prfen Sie, ob die Schnittstelle funktioniert. Geben Sie Folgendes ein, wobei <IP-Adresse> die IP-Adresse eines anderen Gertes auf demselben Subnet wie die Schnittstelle, die getestet wird, ist: ping <IP_address>
Wenn Sie mchten, dass der Treiber beim Hochfahren des Systems automatisch geladen wird, fhren Sie Folgendes aus:
cd ixgb-x.x.x/src make load cp if_ixgb.ko /modules
Bearbeiten Sie /boot/loader.conf und fgen Sie folgende Zeile hinzu:
if_ixgb_load="YES"
ODER
kompilieren Sie den Treiber in den Kernel (siehe Punkt 8).
Bearbeiten Sie /etc/rc.conf und erstellen Sie den geeigneten Eintrag fr ifconfig_ixgb<interface_num>:
Bearbeiten Sie die Kernelkonfigurationsdatei (GENERIC oder MYKERNEL) in /usr/src/sys/i386/conf und stellen Sie sicher, dass die folgende Zeile vorhanden ist:
device ixgb
Kompilieren Sie und installieren Sie den Kernel. Damit die Kernel-Aktualisierungen wirksam werden, ist ein Systemneustart erforderlich.
Weitere Informationen ber das Kompilieren des Kernels finden Sie in der Dokumentation ber das FreeBSD-Betriebssystem.
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA
Intel Corporation bernimmt keine Verantwortung fr Fehler oder Auslassungen
in diesem Dokument. Auerdem macht Intel keinerlei Zusagen, dessen Inhalt zu
aktualisieren.
Intel, Itanium und Pentium sind Marken der Intel Corporation in den USA und anderen Lndern.
*Andere Marken oder Produktnamen sind Eigentum der jeweiligen Inhaber.
WICHTIG BITTE LESEN SIE DIESE VEREINBARUNG VOR DEM KOPIEREN, INSTALLIEREN ODER VERWENDEN DER SOFTWARE.
Lesen Sie die folgenden Nutzungsbedingungen, bevor Sie diese Software oder zugehrige Ressourcen (gemeinsam als Software“ bezeichnet), die unter dieser Lizenzvereinbarung (Vereinbarung“) bereitgestellt werden, kopieren, installieren oder verwenden.
Durch Kopieren, Installieren oder anderweitigen Einsatz der Software erklren Sie sich mit den Bestimmungen dieser Vereinbarung einverstanden. Wenn Sie die Bedingungen dieser Vereinbarung nicht akzeptieren, drfen Sie die Software nicht kopieren, installieren oder einsetzen.
LIZENZEN:
Bitte beachten Sie:
Wenn Sie Netzwerk- oder Systemadministrator sind, trifft die unten stehende Standortlizenz auf Sie zu.
Wenn Sie Endbenutzer sind, trifft die Einzelbenutzerlizenz auf Sie zu.
Wenn Sie ein Originalgertehersteller oder OEM sind, gilt die OEM-Lizenz“.
STANDORTLIZENZ: Sie drfen die Software auf Computer Ihrer Organisation zum firmeninternen Gebrauch kopieren und von der Software unter folgenden Bedingungen eine angemessene Anzahl an Sicherungskopien erstellen:
Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz der Software.
Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
Die Software kann Bestandteile enthalten, die unter anderen Bedingungen als den hier erwhnten geliefert werden und deren Bedingungen in einer separaten Lizenz, die diesen Bestandteilen beiliegt, festgelegt sind.
EINZELBENUTZERLIZENZ:
Sie drfen die Software auf einen einzelnen Computer fr Ihren persnlichen Gebrauch kopieren und von der Software unter folgenden Bedingungen eine Sicherungskopie erstellen:
Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz der Software.
Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
Die Software kann Bestandteile enthalten, die unter anderen Bedingungen als den hier erwhnten geliefert werden und deren Bedingungen in einer separaten Lizenz, die diesen Bestandteilen beiliegt, festgelegt sind.
OEM-LIZENZ.
Die Software darf nur als wichtiger Bestandteil Ihres Produkts bzw. integriert in Ihr Produkt oder als Standalone-Softwareaktualisierung zur Wartung fr bestehende Endanwender Ihrer Produkte unter Ausschluss aller anderen Standalone-Produkte, oder als Komponente einer greren Softwareverteilung, einschlielich der Verteilung eines Installations-Images oder eines Gast-VM-Images, reproduziert und verteilt werden, und zwar unter Vorbehalt folgender Bedingungen:
Diese Software ist nur lizenziert fr den Gebrauch mit (a) physischen Intel Komponenten und (b) virtuellen (emulierten“) Gerten, die dafr konzipiert sind, dass sie von einem auf einer virtuellen Maschine ausgefhrten Gastbetriebssystem als Intel Komponente erkannt werden. Jeder anderweitige Gebrauch der Software, einschlielich Gebrauch mit nicht von Intel hergestellten Komponenten, fllt nicht unter diese Lizenzvereinbarung
Vorbehaltlich aller Bedingungen dieses Vertrags erteilt Ihnen die Intel Corporation (Intel“) eine einfache, nicht bertragbare Lizenz unter Einhaltung der Urheberrechte von Intel fr den Einsatz der Software.
Kein Teil der Software darf auer wie in dieser Vereinbarung festgelegt kopiert, modifiziert, vermietet, verkauft, verteilt oder bertragen werden, und Sie erklren sich damit einverstanden, ein unberechtigtes Kopieren dieser Software zu verhindern.
Sie drfen die Software nicht nachbauen, dekompilieren oder disassemblieren.
Sie drfen die Software nur in bereinstimmung mit einer schriftlichen Lizenzvereinbarung an Ihre Kunden vertreiben. Bei einer derartigen Lizenzvereinbarung kann es sich um eine Break the seal“ Lizenzvereinbarung handeln, d.h. um eine Lizenz, die mit ffnen der Verpackung oder CD-Hlle in Kraft tritt. Als Mindestvoraussetzung muss die Lizenz Intels Eigentumsrechte an der Software wahren.
Sie drfen das Quellcode-Format irgendwelcher Komponenten der Software und alle Ableitungen davon ohne vorherige schriftliche Genehmigung von Intel nicht an Dritte verteilen, in Unterlizenz vergeben oder bertragen.
Die Software kann Bestandteile enthalten, die unter anderen Bedingungen als den hier erwhnten geliefert werden und deren Bedingungen in einer separaten Lizenz, die diesen Bestandteilen beiliegt, festgelegt sind.
LIZENZEINSCHRNKUNGEN.
Sie drfen NICHT: (i) die Software auf andere Weise als in diesem Vertrag vereinbart einsetzen oder kopieren; (ii) die Software an eine beliebige Drittpartei vermieten oder verpachten; (iii) diesen Vertrag oder die Software ohne ausdrckliche schriftliche Genehmigung von Intel bertragen; (iv) die Software zur Gnze oder Teile davon verndern, bearbeiten oder bersetzen, auer wie in diesem Vertrag vorgesehen; (v) die Software zurckentwickeln, dekompilieren oder disassemblieren; (vi) versuchen, die normale Funktion eines Lizenzmanagers, der den Einsatz der Software steuert, abzundern oder zu manipulieren; (vii) das Quellcode-Format irgendwelcher Komponenten der Software und alle Ableitungen davon ohne vorherige schriftliche Genehmigung von Intel an Dritte verteilen, in Unterlizenz vergeben oder bertragen; (viii) einer Drittpartei die Erlaubnis, Autorisierung, Lizenz oder Sublizenz erteilen, den Quellcode einzusehen oder zu verwenden; (ix) den Quellcode oder die Software verndern oder verteilen, so dass ein beliebiger Teil davon einer ausgeschlossenen Lizenz (Excluded License“) unterliegen wrde. (Eine ausgeschlossene Lizenz“ erfordert als Bedingung der Nutzung, Vernderung oder Verteilung, dass (a) der Code im Quellcodeformat offen gelegt oder verteilt wird; oder (b) andere das Recht haben, ihn zu verndern.); (x) den Quellcode oder die Software in betrgerischen, bsartigen oder ungesetzlichen Programmen verwenden oder darin einschlieen.
KEINE ANDEREN RECHTE.
Es werden Ihnen von Intel keine anderen Rechte oder Lizenzen, sei es ausdrcklich oder konkludent, in Bezug auf die proprietren Informationen oder Patente, Urheberrechte, Topographien, Marken, Betriebsgeheimnisse oder andere Rechte an geistigem Eigentum erteilt, die Intel gehren oder von Intel kontrolliert werden, sofern dies nicht ausdrcklich in dieser Vereinbarung erwhnt ist. Soweit nicht ausdrcklich hier angegeben, werden Ihnen weder ausdrcklich noch konkludent Lizenzen oder Rechte gewhrt bzw. eingerumt. Intel gewhrt Ihnen keine ausdrcklichen oder konkludenten Rechte an Patenten, Urheberrechten und Marken von Intel oder andere Rechte an geistigem Eigentum.
EIGENTUM AN SOFTWARE UND URHEBERRECHTEN. Fr die Software wird eine Lizenz gewhrt; sie wird nicht verkauft. Das Eigentum aller Kopien der Software verbleibt bei Intel. Die Software ist urheberrechtlich und durch die Gesetze der Vereinigten Staaten von Amerika und anderer Lnder sowie durch internationale Abkommen geschtzt. Urheberrechtshinweise drfen nicht aus der Software entfernt werden. Sie erklren hiermit Ihr Einverstndnis, das unerlaubte Kopieren der Software zu verhindern. Intel kann die Software oder darin erwhnte Elemente jederzeit und ohne Vorankndigung ndern. Intel ist jedoch nicht dazu verpflichtet, die Software zu untersttzen oder zu aktualisieren.
ZUSTZLICHE BEDINGUNGEN FR PRE-RELEASE- SOFTWARE. Wenn die Software, die Sie unter dieser Vereinbarung installieren oder verwenden, eine nicht kommerziell vertriebene Pre-Release-Version ist oder als Alpha“- oder Beta“-Version der Software (Pre-Release-Software“) gekennzeichnet ist, gelten folgende Bedingungen. Sollte eine Bedingung in diesem Abschnitt in Bezug auf Pre-Release-Software in Widerspruch zu anderen Bedingungen dieser Vereinbarung stehen, so ersetzt dieser Abschnitt die anderen Bedingungen, aber nur in dem Ausma, wie es zur Vermeidung des Widerspruchs erforderlich ist. Sie verstehen und erkennen an, dass es sich bei dieser Software um Pre-Release-Software und nicht die endgltige Software von Intel handelt. Sie kann Fehler und andere Probleme aufweisen, die zu Datenverlust, Systemausfall oder anderen Fehlern fhren knnen. Die Pre-Release-Software wird wie besehen“ bereitgestellt und Intel schliet jegliche Garantie oder Haftung fr Schden, die aus dem Gebrauch der Pre-Release-Software entstehen knnen, aus. Sie erkennen an, dass Intel keine Zusage gemacht hat, in Zukunft Pre-Release-Software zu verffentlichen und dass Intel Ihnen gegenber keine ausdrckliche oder konkludente Verpflichtung zur Verffentlichung der Pre-Release-Software hat und dass Intel mglicherweise keine Software verffentlicht, die mit der Pre-Release-Software kompatibel ist. Sie stimmen zu, dass die Gesamtheit aller Forschungs- und Entwicklungsarbeiten, die Sie in Zusammenhang mit der Pre-Release-Software oder einem Produkt, das die Pre-Release-Software nutzt oder damit verknpft ist, durchfhren, auf Ihr eigenes Risiko erfolgt. Wenn Intel Ihnen entsprechend einer eigenen schriftlichen Vereinbarung Pre-Release-Software zur Verfgung gestellt hat, unterliegt Ihr Gebrauch der Pre-Release-Software ebenfalls dieser Vereinbarung.
BESCHRNKTE GARANTIE FR DATENTRGER. Wenn die Software von Intel auf einem Datentrger geliefert wurde, garantiert Intel fr einen Zeitraum von neunzig Tagen nach der Lieferung durch Intel, dass der Datentrger frei von Materialschden ist. Falls der Datentrger beschdigt ist, knnen Sie ihn an Intel zurckgeben. Intel entscheidet in diesem Fall, ob der Datentrger ersetzt oder ob die Software auf einem anderen Weg an Sie ausgeliefert wird.
AUSSCHLUSS ANDERER GARANTIEN. SOFERN OBEN NICHT ANDERWEITIG ANGEGEBEN WIRD DIE SOFTWARE IN DER VORLIEGENDEN FORM UND OHNE AUSDRCKLICHE ODER STILLSCHWEIGENDE GEWHR ANGEBOTEN. INTEL BERNIMMT KEINE GARANTIE FR DIE MARKTFHIGKEIT, RECHTSVERLETZUNGEN ODER DIE EIGNUNG FR EINEN BESTIMMTEN ZWECK. Intel bernimmt keine Garantie oder Verantwortung fr die Richtigkeit oder Vollstndigkeit der Informationen, des Texts, der Grafiken, Verknpfungen oder anderer Elemente, die in der Software enthalten sind.
HAFTUNGSBESCHRNKUNGEN. IN KEINEM FALL HAFTEN INTEL ODER INTELS LEISTUNGSERBRINGER FR SCHDEN JEGLICHER ART (EINSCHLIESSLICH, ABER NICHT BESCHRNKT AUF SCHDEN DURCH ENTGANGENE GEWINNE, GESCHFTSUNTERBRECHUNGEN ODER DATENVERLUST), DIE AUS DEM GEBRAUCH ODER NICHT MGLICHEN GEBRAUCH DER SOFTWARE ENTSTEHEN, SELBST WENN INTEL VON DER MGLICHKEIT DERARTIGER SCHDEN IN KENNTNIS GESETZT WURDE. IN EINIGEN GERICHTSBARKEITEN IST DER AUSSCHLUSS ODER DIE EINSCHRNKUNG DER HAFTUNG FR STILLSCHWEIGENDE GEWHRLEISTUNGEN ODER FR MITTELBARE BZW. BEILUFIG ENTSTANDENE SCHDEN NICHT ZULSSIG, SO DASS DIE OBEN AUFGEFHRTE EINSCHRNKUNG MGLICHERWEISE AUF SIE NICHT ZUTRIFFT. SIE HABEN UNTER UMSTNDEN NOCH ANDERE RECHTE, DIE JE NACH GERICHTSBARKEIT VARIIEREN KNNEN. Fr den Fall, dass Sie die Software in Verbindung mit einem virtuellen (emulierten“) Gert verwenden, das so konzipiert ist, dass es als Intel Komponente erkannt wird, erkennen Sie an, dass Intel weder der Urheber noch der Hersteller des virtuellen (emulierten“) Gerts ist. Sie verstehen und erkennen an, dass Intel keine Zusicherungen ber den korrekten Betrieb der Software macht, wenn diese mit einem virtuellen (emulierten“) Gert verwendet wird, dass Intel die Software nicht fr den Betrieb mit einem virtuellen (emulierten“) Gert entwickelt hat und dass die Software mglicherweise in Verbindung mit einem virtuellen (emulierten“) Gert nicht korrekt funktioniert. Sie stimmen zu, das Risiko zu bernehmen, dass die Software mglicherweise in Verbindung mit einem virtuellen (emulierten“) Gert nicht korrekt funktioniert. Sie stimmen zu, dass Sie Intel und seine Geschftsfhrer, Niederlassungen und verbundenen Unternehmen von allen Ansprchen, Kosten, Schden, Auslagen sowie Anwaltskosten freistellen, die sich direkt oder indirekt aus einem Anspruch auf Produkthaftung, Krperverletzung oder Tod ergeben und im Zusammenhang mit dem Gebrauch der Software in Verbindung mit einem virtuellen (emulierten“) Gert stehen, selbst dann, wenn im Anspruch vorgebracht wird, dass Intel im Design oder der Herstellung der Software fahrlssig handelte.
UNBEFUGTER GEBRAUCH.DIE SOFTWARE WURDE NICHT FR DEN EINSATZ IN SYSTEMEN ODER ANWENDUNGEN KONZIPIERT, IN DENEN DER AUSFALL DER SOFTWARE ZU PERSONENVERLETZUNG ODER LEBENSBEDROHLICHEN SITUATIONEN FHREN KNNTE (Z. B. IN MEDIZINISCHEN SYSTEMEN ODER LEBENSRETTUNGS- ODER LEBENSERHALTUNGSSYSTEMEN).
Sollten Sie die Software fr solche nicht vorgesehenen oder nicht genehmigten Zwecke einsetzen, stellen Sie Intel und seine Geschftsfhrer, Niederlassungen und verbundenen Unternehmen von allen Ansprchen, Kosten, Schden, Auslagen sowie Anwaltskosten frei, die sich direkt oder indirekt aus einem Anspruch auf Produkthaftung, Krperverletzung oder Tod ergeben und in Verbindung mit dem nicht vorgesehenen oder nicht genehmigten Einsatz stehen, selbst dann, wenn im Anspruch vorgebracht wird, dass Intel im Design oder der Herstellung dieses Teils fahrlssig handelte.
BEENDIGUNG DIESER VEREINBARUNG.
Diese Vereinbarung kann von Intel jederzeit beendet werden, wenn Sie die genannten Bestimmungen nicht einhalten. Wird die Vereinbarung beendet, sind Sie dazu verpflichtet, die Software entweder umgehend zu lschen oder alle Kopien der Software an Intel zurckzugeben.
ANWENDBARES RECHT.
Ansprche, die im Rahmen dieser Vereinbarung erhoben werden, unterliegen dem Recht des US-Bundesstaats Kalifornien, ungeachtet der Prinzipien zur Gesetzeskollision. Sie erklren sich damit einverstanden, dass das bereinkommen der Vereinten Nationen ber Vertrge ber den internationalen Warenkauf in Bezug auf diesen Vertrag nicht zutrifft. Sie drfen die Software nicht exportieren, wenn der Export gegen geltende Exportgesetze und -bestimmungen verstt. Intel ist an keine anderen Vereinbarungen gebunden, es sei denn, sie liegen in schriftlicher Form vor und wurden von einem autorisierten Reprsentanten von Intel unterzeichnet.
EINGESCHRNKTE RECHTE DER US-REGIERUNG.
Die im Lieferumfang enthaltene Software und Dokumentation wurden mit privaten finanziellen Mitteln entwickelt und werden mit EINGESCHRNKTEN RECHTEN“ bereitgestellt. Die Verwendung, Vervielfltigung oder Verffentlichung durch Regierungsbehrden unterliegt den Bestimmungen, die in FAR 52.227-14 und DFARS 252.227-7013 ff. oder einer entsprechenden Aktualisierung aufgefhrt sind. Die Verwendung dieses Produkts durch US-Regierungsbehrden erfolgt unter Anerkennung der diesbezglichen Eigentumsrechte von Intel. Auftraggeber oder Hersteller ist Intel.
SPRACHE; BERSETZUNGEN.
Sollte die englische Version dieses Vertrags zusammen mit einer in eine andere Sprache bersetzten Version ausgeliefert werden, dient diese bersetzte Version ausschlielich zu Informationszwecken; die englische Version ist die einzige rechtsgltige Version.
Intel garantiert dem ursprnglichen Eigentmer, dass das in diesem Paket gelieferte Adapterprodukt frei von Material- und Herstellungsfehlern ist. Das Adapterprodukt fllt nicht unter diese Garantie, wenn es whrend der Installation beschdigt oder unsachgem verwendet wurde.
DIE OBIGE GARANTIE ERSETZT ALLE ANDEREN AUSDRCKLICHEN, STILLSCHWEIGENDEN ODER GESETZLICHEN GARANTIEN, EINSCHLIESSLICH, ABER NICHT BESCHRNKT AUF IRGENDWELCHE GARANTIEN DER EINHALTUNG DER RECHTE DRITTER AN GEISTIGEM EIGENTUM, DER MARKTGNGIGEN QUALITT, DER EIGNUNG FR EINEN BESTIMMTEN ZWECK, DIE SICH AUS EINEM VORSCHLAG, EINER SPEZIFIKATION ODER EINEM BEISPIEL BZW. EINER PROBE ERGEBEN.
Diese Garantie gilt nicht fr den Austausch von Adapterprodukten, die durch Mutwilligkeit, Unfall, Zweckentfremdung, Nachlssigkeit, Reparaturen, Katastrophen, unsachgeme Installation oder unsachgemes Testen beschdigt wurden. Wird das Adapterprodukt als defekt eingestuft, wird Intel nach eigenem Ermessen das Hardwareprodukt wie unten erlutert kostenfrei ersetzen oder reparieren oder Ihnen den Kaufpreis zurckerstatten, vorausgesetzt, dass Sie das Adapterprodukt zusammen mit einer Return-Material-Authorization-(RMA-)Nummer (siehe unten) und einem Kaufnachweis (falls nicht registriert) an den Hndler, wo Sie es erworben haben, oder an Intel mit einer Beschreibung jeglichen Defekts zurckgeben. Wenn Sie das Adapterprodukt einschicken, bernehmen Sie das Risiko fr Schden am Produkt oder Verlust des Produkts whrend des Transports. Sie mssen die Originalverpackung (oder eine gleichwertige Verpackung) verwenden und das Porto bezahlen.
Intel kann das Adapterprodukt durch neue oder aufbereitete Teile ersetzen oder reparieren. Jedes von Intel ersetzte Adapterprodukt oder Teile davon gehen in das Eigentum von Intel ber. Reparierte oder ersetzte Adapterprodukte werden nach dem Ermessen von Intel mit derselben Revisionsstufe wie empfangen oder hher an Sie zurckgegeben. Intel behlt sich das Recht vor, eingestellte Adapterprodukte durch ein gleichwertiges Adapterprodukt der aktuellen Generation zu ersetzen.
Rckgabe eines defekten Produkts
Aus Nordamerika:
Wenden Sie sich vor der Rckgabe eines Adapterprodukts unter +1 916-377-7000 an den Kundensupport von Intel, um eine Return-Material-Authorization-(RMA-)Nummer anzufordern.
Wenn die Kundensupportgruppe den Defekt des Adapterprodukts besttigt, wird die RMA-Abteilung Ihnen eine RMA-Nummer ausstellen, die Sie an der Auenverpackung des Adapterprodukts anbringen. Intel akzeptiert nur Produkte mit einer RMA-Nummer auf der Verpackung.
Alle anderen Orte:
Geben Sie das Adapterprodukt fr eine Rckerstattung des Kaufpreises oder Ersatz an den Verkaufsort zurck.
Intel mchte, dass Sie mit dem gekauften Intel Adapterprodukt rundum zufrieden sind. Sie knnen in einem Zeitraum von neunzig (90) Tagen ab Kaufdatum Ihren Intel Adapter fr eine volle Rckerstattung des Kaufpreises durch den Hndler an den ursprnglichen Verkaufsort zurckgeben. Fachhndler und Distributoren, die Retouren akzeptieren und ihren Kunden Geld zurckerstatten, knnen Intel Adapter an den ursprnglichen Verkaufsort zurckgeben. Intel garantiert die Annahme von Retouren unter dieser Richtlinie und die Rckerstattung des ursprnglichen Kaufpreises an Kunden, die direkt von Intel kaufen.
Haftungsbeschrnkungen und Rechtsmittel
DIE EINZIGE HAFTUNG VON INTEL UNTER DIESER VEREINBARUNG IST BESCHRNKT AUF DIREKTE, OBJEKTIV MESSBARE SCHDEN. UNTER KEINEN UMSTNDEN HAFTET INTEL FR JEGLICHE INDIREKTEN ODER SPEKULATIVEN SCHDEN (EINSCHLIESSLICH, ABER OHNE EINSCHRNKUNG DES VORHERGEHENDEN, FOLGESCHDEN, NEBENSCHDEN ODER SONDERSCHDEN), EINSCHLIESSLICH, ABER NICHT BESCHRNKT AUF DIE EINHALTUNG DER RECHTE DRITTER AN GEISTIGEM EIGENTUM, KOSTEN DER NEUBESCHAFFUNG, UNBRAUCHBARKEIT, GESCHFTSAUSFLLEN, VERLUST DES GESCHFTSWERTS UND GEWINNVERLUSTEN, EGAL OB SICH SOLCHE SCHDEN AUS VERTRAGLICHER FAHRLSSIGKEIT, UNERLAUBTEM HANDELN ODER UNTER JEGLICHER GARANTIE ERGEBEN, UNGEACHTET DESSEN, OB INTEL VON DER MGLICHKEIT SOLCHER SCHDEN IM VORAUS KENNTNIS HATTE. UNGEACHTET DES VORHERGEHENDEN BERSTEIGT DIE GESAMTHAFTUNG VON INTEL FR ALLE ANSPRCHE UNTER DIESER VEREINBARUNG NICHT DEN FR DAS PRODUKT BEZAHLTEN PREIS. DIESE BESCHRNKUNGEN POTENZIELLER HAFTUNGSANSPRCHE TRUGEN WESENTLICH ZUR BESTIMMUNG DES PRODUKTPREISES BEI. INTEL BERNIMMT KEINE WEITEREN HAFTUNGEN UND AUTORISIERT NIEMANDEN, AN SEINER STELLE JEGLICHE WEITEREN HAFTUNGEN ZU BERNEHMEN.
In einigen Gerichtsbarkeiten ist der Ausschluss oder die Beschrnkung von Neben- oder Folgeschden nicht zulssig, sodass die oben ausgefhrten Beschrnkungen mglicherweise auf Sie nicht zutreffen.
Kritische Steuerungsanwendungen: Intel lehnt insbesondere die Haftung fr die Verwendung des Adapterprodukts in kritischen Steuerungsanwendungen (einschlielich, nur als Beispiel, Sicherheits- oder medizinische Steuerungssysteme, Kernenergie-Steuerungssysteme oder Luft- und Bodenverkehrs-Steuerungssysteme) durch den Lizenznehmer oder Unterlizenznehmer ab. Eine solche Verwendung geschieht einzig auf Risiko des Benutzers. Der Lizenznehmer willigt ein, Intel von allen Ansprchen, die sich aus der Verwendung des Adapterprodukts in solchen Anwendungen durch den Lizenznehmer oder Unterlizenznehmer ergeben, zu schtzen, freizustellen und schadlos zu
halten.
Software: Die mit dem Adapterprodukt gelieferte Software fllt nicht unter die oben ausgefhrte Hardwaregarantie. Einzelheiten zu eventuellen Softwaregarantien finden Sie in der zutreffenden Softwarelizenzvereinbarung im Lieferumfang des Adapterprodukts.
Hinweis: Wenn das "Australian Consumer Law" fr Sie als Konsument Anwendung findet, hat diese Garantie fr Sie keine Gltigkeit. Bitte besuchen Sie die Seite zur beschrnkten lebenslangen Hardwaregarantie fr Australien, um sich ber die fr australische Konsumenten gltige Garantie zu informieren.
Install the Intel® Ethernet 10 Gigabit Server Adapter
Install an Adapter
Turn off the computer and unplug the power cord.
If performing a "hot plug" install, see your server documentation first.
Remove the computer cover and the adapter slot cover from the slot that matches your adapter.
You may utilize a slot that is longer than your adapter’s connector with no harm, but do not attempt to install in a slot that is shorter than the PCI Express connector.
Firmly place the adapter into the slot and secure the bracket.
Replace the computer cover. Plug in the power cord.
Install a Mezzanine Card
Turn off the computer and unplug the power cord.
Remove the computer cover.
Align the PCIe connector on the mezzanine board with the connector and four plastic standoffs on the motherboard.
Press the adapter until it is fully inserted into the MB connector and snaps into the four standoffs.
Replace the computer cover. Plug in the power cord.
Attach the Network Cable
Intel® Ethernet 10 Gigabit copper adapters: Use Category 6, Category 6a, or Category 7 Ethernet cabling.
Intel® Ethernet 10 Gigabit Server Adapter with SFP+ pluggable optics: Install the module and attach the cable according to the module manufacturer’s directions
Intel® Ethernet 10 Gigabit fiber adapters with SC connector: Remove and save the fiber optic connector cover. Insert a SC fiber optic connector into the TX/RX ports on the adapter bracket.
Intel® Ethernet 10 Gigabit fiber adapters with LC connector: Remove and save the fiber optic connector cover. Insert an LC connector into the adapter. Conversion cables to other connector types (such as SC) may be used if the cabling matches the optical specifications of the adapter, including length limitations.
Intel® Ethernet 10 Gigabit CX4 adapters: Physical cabling must meet IEEE Std 802.3ak, Clause 54 specifications. The required cable connector is an MDI latch-type receptacle, as defined by IEC 61076-3-113.
Start your computer and follow the driver installation instructions below.
Install the Drivers and Intel® PROSet Software
Microsoft* Windows* Operating Systems
NOTES:
Installing drivers requires administrator rights to the operating
system.
See the System Requirements page in the Intel 10GbE Adapter
Guide for supported operating systems.
The adapter is detected as new hardware when Windows
starts. To install the
correct driver:
The adapter is detected and Windows either
installs a Windows resident driver or starts the Found New Hardware
wizard.
If the wizard starts, follow the prompts to
install the driver from the CD in this package.
If a Windows resident driver installs (wizard
does not appear), update the driver by inserting the Intel CD and clicking
the Install Drivers and Software button when the Intel Network Connections
autorun window appears.
Linux
To build a binary RPM* package of this driver, run 'rpmbuild -tb <filename.tar.gz>'.
Replace <filename.tar.gz> with the specific file name of the driver.
NOTE: For the build to work properly, the currently running kernel
MUST match the version and configuration of the installed kernel sources. If you have just
recompiled the kernel reboot the system now.
RPM functionality has only
been tested in Red Hat distributions.
Move the base driver tar file to the directory of your
choice. For example, use '/home/username/ixgb' or '/usr/local/src/ixgb'.
Untar/unzip the archive, where <x.x.x> is the version number for the driver
tar:
tar zxf ixgb-<x.x.x>.tar.gz
Change to the driver src directory, where <x.x.x> is the version number for the driver
tar:
The install locations listed above are the default
locations. They might not be correct for certain Linux distributions.
Install the module:
modprobe ixgb <parameter>=<value>
Assign an IP address to the interface by entering the
following, where <x> is the interface number:
ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where
<IP_address>
is the IP address of another machine on the same subnet as the interface
that is being tested:
ping <IP_address>
FreeBSD
Building and Installation
This driver has been developed for use with FreeBSD kernel, versions 4.8 and
later.
NOTE: You must have kernel sources installed in order to compile the driver module.
In the instructions below, x.x.x is the driver version as indicated in the name of the driver
tar file.
Move the base driver tar file to the directory of your choice. For
example, use /home/username/ixgb or
/usr/local/src/ixgb.
Untar/unzip the archive:
tar xfz ixgb-x.x.x.tar.gz
This will create an ixgb-x.x.x directory.
To install man page:
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
To load the driver onto a running system, perform the
following steps:
cd ixgb-x.x.x
make
OR
cd ixgb-x.x.x/src
make load
To assign an IP address to the interface, enter the following:
ifconfig ixgb<interface_num>
<IP_address>
Verify that the interface works. Enter the following, where <IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested: ping <IP_address>
If you want the driver to load automatically when the
system is booted:
cd ixgb-x.x.x/src make load cp if_ixgb.ko /modules
Edit /boot/loader.conf, and add the following line:
if_ixgb_load="YES"
OR
compile the driver into the kernel (see item 8).
Edit /etc/rc.conf, and create the appropriate ifconfig_ixgb<interface_num> entry:
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA
Intel Corporation assumes no responsibility for errors or omissions in this document.
Nor does Intel make any commitment to update the information contained herein.
Intel, Itanium, and Pentium are trademarks of Intel Corporation in the U.S. and other countries.
*Other names and brands may be claimed as the property of others.
IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
Do not copy, install, or use this software and any associated materials (collectively, the “Software”) provided under this license agreement (“Agreement”) until you have carefully read the following terms and conditions.
By copying, installing, or otherwise using the Software, you agree to be bound by the terms of this Agreement.
If you do not agree to the terms of this Agreement, do not copy, install, or use the Software.
LICENSES:
Please Note:
If you are a network or system administrator, the “Site License” below shall apply to you.
If you are an end user, the “Single User License” shall apply to you.
If you are an original equipment manufacturer (OEM), the “OEM License” shall apply to you.
SITE LICENSE: You may copy the Software onto your organization’s computers for your organization’s use, and you may make a reasonable number of back-up copies of the Software, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute, or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
SINGLE USER LICENSE:
You may copy the Software onto a single computer for your personal use, and you may make one back-up copy of the Software, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute, or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
OEM LICENSE:
You may reproduce and distribute the Software only as an integral part of or incorporated in your product, as a standalone Software maintenance update for existing end users of your products, excluding any other standalone products, or as a component of a larger Software distribution, including but not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these conditions:
This Software is licensed for use only in conjunction with (a) physical
Intel component products, and (b) virtual (emulated) devices designed to
appear as Intel component products to a Guest operating system running within
the context of a virtual machine. Any other use of the Software, including but
not limited to use with non-Intel component products, is not licensed hereunder.
Subject to all of the terms and conditions of this Agreement, Intel Corporation
("Intel") grants to you a non-exclusive, non-assignable, copyright license to
use the Software.
You may not copy, modify, rent, sell, distribute or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
You may not reverse engineer, decompile, or disassemble the Software.
You may only distribute the Software to your customers pursuant to a written
license agreement. Such license agreement may be a "break-the-seal" license
agreement. At a minimum such license shall safeguard Intel's ownership rights to
the Software.
You may not distribute, sublicense or transfer the Source Code form of any
components of the Software and derivatives thereof to any third party without
the express written consent of Intel.
The Software may include portions offered on terms differing from those set out
here, as set out in a license accompanying those portions.
LICENSE RESTRICTIONS.
You may NOT: (i) use or copy the Software except as provided in this Agreement;
(ii) rent or lease the Software to any third party; (iii) assign this Agreement
or transfer the Software without the express written consent of Intel; (iv)
modify, adapt, or translate the Software in whole or in part except as provided
in this Agreement; (v) reverse engineer, decompile, or disassemble the Software;
(vi) attempt to modify or tamper with the normal function of a license manager
that regulates usage of the Software; (vii) distribute, sublicense or transfer
the Source Code form of any components of the Software and derivatives thereof
to any third party without the express written consent of Intel; (viii) permit,
authorize, license or sublicense any third party to view or use the Source Code;
(ix) modify or distribute the Source Code or Software so that any part of it
becomes subject to an Excluded License. (An "Excluded License" is one that
requires, as a condition of use, modification, or distribution, that (a) the
code be disclosed or distributed in source code form; or (b) others have the
right to modify it.); (x) use or include the Source Code or Software in
deceptive, malicious or unlawful programs.
NO OTHER RIGHTS.
No rights or licenses are granted by Intel to you, expressly or by implication,
with respect to any proprietary information or patent, copyright, mask work,
trademark, trade secret, or other intellectual property right owned or
controlled by Intel, except as expressly provided in this Agreement. Except as
expressly provided herein, no license or right is granted to you directly or by
implication, inducement, estoppel, or otherwise. Specifically, Intel grants no
express or implied right to you under Intel patents, copyrights, trademarks, or
other intellectual property rights.
OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is
licensed, not sold. Title to all copies of the Software remains with Intel. The
Software is copyrighted and protected by the laws of the United States and other
countries and international treaty provisions. You may not remove any copyright
notices from the Software. You agree to prevent any unauthorized copying of the
Software. Intel may make changes to the Software, or to items referenced
therein, at any time without notice, but is not obligated to support or update
the Software.
ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the
Software you are installing or using under this Agreement is pre-commercial
release or is labeled or otherwise represented as alpha- or beta- versions
of the Software ("pre-release Software"), then the following terms apply. To the
extent that any provision in this Section conflicts with any other term(s) or
condition(s) in this Agreement with respect to pre-release Software, this
Section shall supersede the other term(s) or condition(s), but only to the
extent necessary to resolve the conflict. You understand and acknowledge that
the Software is pre-release Software, does not represent the final Software from
Intel, and may contain errors and other problems that could cause data loss,
system failures, or other errors. The pre-release Software is provided to you
"as-is" and Intel disclaims any warranty or liability to you for any damages
that arise out of the use of the pre-release Software. You acknowledge that
Intel has not promised that pre-release Software will be released in the future,
that Intel has no express or implied obligation to you to release the
pre-release Software and that Intel may not introduce Software that is
compatible with the pre-release Software. You acknowledge that the entirety of
any research or development you perform that is related to the pre-release
Software or to any product making use of or associated with the pre-release
Software is done at your own risk. If Intel has provided you with pre-release
Software pursuant to a separate written agreement, your use of the pre-release
Software is also governed by such agreement.
LIMITED MEDIA WARRANTY. If the Software has been
delivered by Intel on physical media, Intel warrants the media to be free from
material physical defects for a period of ninety days after delivery by Intel.
If such a defect is found, return the media to Intel for replacement or
alternate delivery of the Software as Intel may select.
EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE,
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY
KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A
PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for
the accuracy or completeness of any information, text, graphics, links, or other
items contained within the Software.
LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS
SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION,
LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE
OF OR INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION
OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO
THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS
THAT VARY FROM JURISDICTION TO JURISDICTION. In the event that you use
the Software in conjunction with a virtual (emulated) device designed to
appear as an Intel component product, you acknowledge that Intel is neither the
author nor the creator of the virtual (emulated) device. You understand and
acknowledge that Intel makes no representations about the correct operation of
the Software when used with a virtual (emulated) device, that Intel did not
design the Software to operate in conjunction with the virtual (emulated)
device, and that the Software may not be capable of correct operation in
conjunction with the virtual (emulated) device. You agree to assume the risk
that the Software may not operate properly in conjunction with the virtual
(emulated) device. You agree to indemnify and hold Intel and its officers,
subsidiaries and affiliates harmless against all claims, costs, damages, and
expenses, and reasonable attorney fees arising out of, directly or indirectly,
any claim of product liability, personal injury or death associated with the use
of the Software in conjunction with the virtual (emulated) device, even if
such claim alleges that Intel was negligent regarding the design or manufacture
of the Software.
UNAUTHORIZED USE.THE SOFTWARE IS NOT DESIGNED,
INTENDED, OR AUTHORIZED FOR USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH
THE FAILURE OF THE SOFTWARE COULD CREATE A SITUATION WHERE PERSONAL INJURY OR
DEATH MAY OCCUR (E.G MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS).
If you use the Software for any such unintended or unauthorized use, you shall
indemnify and hold Intel and its officers, subsidiaries and affiliates harmless
against all claims, costs, damages, and expenses, and reasonable attorney fees
arising out of, directly or indirectly, any claim of product liability, personal
injury or death associated with such unintended or unauthorized use, even if
such claim alleges that Intel was negligent regarding the design or manufacture
of the part.
TERMINATION OF THIS AGREEMENT.
Intel may terminate this Agreement at any time if you violate its terms.
Upon termination, you will immediately destroy the Software or return all copies of the Software to Intel.
APPLICABLE LAWS.
Claims arising under this Agreement shall be governed by the laws of the State
of California, without regard to principles of conflict of laws. You agree that
the terms of the United Nations Convention on Contracts for the Sale of Goods do
not apply to this Agreement. You may not export the Software in violation of
applicable export laws and regulations. Intel is not obligated under any other
agreements unless they are in writing and signed by an authorized representative
of Intel.
GOVERNMENT RESTRICTED RIGHTS.
The enclosed Software and documentation were developed at private expense, and
are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS
252.227-7013 et seq. or its successor. The use of this product by the Government
constitutes acknowledgement of Intels proprietary rights in the Software.
Contractor or Manufacturer is Intel.
LANGUAGE; TRANSLATIONS.
In the event that the English language version of this Agreement is accompanied by any other version translated into any other language, such translated version is provided for convenience purposes only and the English language version shall control.
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.
Last modified on 9/17/12 10:42a
DOCS/QUICK/ESN 0000755 0000000 0000000 00000000000 12233424121 007710 5 ustar DOCS/QUICK/ESN/10qi_esn.htm 0000755 0000000 0000000 00000030612 12140132664 012132 0 ustar
Gua rpida de instalacin de adaptadores de red Intel(R)
Instalacin de adaptadores de red Intel®
Instale el adaptador de Ethernet Intel® de 10 Gigabits para servidores
Instalar un adaptador
Apague su PC y desconecte el cable de energa. Si va a realizar una instalacin de "conexin en funcionamiento", consulte primero la documentacin de su servidor.
Quite la cubierta del sistema y la cubierta de la ranura del adaptador en la ranura que corresponde al adaptador. Puede utilizar una ranura ms larga que el conector del adaptador sin problemas, pero no intente realizar la instalacin en una ranura ms corta que el conector PCI Express.
Coloque de manera segura el adaptador en la ranura y asegure el soporte.
Vuelva a colocar la cubierta de su PC. Conecte el cable de energa.
Instalar una tarjeta Mezzanine
Apague su PC y desconecte el cable de energa.
Desmonte la cubierta de su PC.
Alinee el conector PCIe en la placa mezzanine con el conector y cuatro sujetadores en la placa base.
Presione el adaptador hasta que se haya insertado por completo en el conector MB y quede encajado en los cuatro sujetadores.
Vuelva a colocar la cubierta de su PC. Conecte el cable de energa.
Conexin del cable de red
Adaptadores de Ethernet Intel® de 10 Gigabits de cobre: Utilice cables Ethernet de Categora 6, Categora 6a o Categora 7.
Adaptador de Ethernet Intel® de 10 Gigabits con ptica acoplable SFP+: Instale el mdulo y conecte el cable segn las instrucciones del fabricante del mdulo
Adaptadores de Ethernet Intel® de 10 Gigabits de fibra con conector SC: Retire y guarde la cubierta del conector de fibra ptica. Introduzca un conector de fibra ptica SC en los puertos transmisin/recepcin del soporte del adaptador.
Adaptadores de Ethernet Intel® de 10 Gigabits de fibra con conector LC: Retire y guarde la cubierta del conector de fibra ptica. Inserte un conector LC en el adaptador. Puede utilizar cables de conversin a otros tipos de conector (como SC) si el cableado se ajusta a las especificaciones pticas del adaptador, incluyendo las limitaciones de longitud.
Adaptadores CX4 de Ethernet Intel® de 10 Gigabits: Las caractersticas fsicas del cable deben satisfacer las especificaciones IEEE Std 802.3ak, clusula 54. El conector de cable requerido es un receptculo tipo cierre MDI, tal como lo define IEC 61076-3-113.
Inicie su PC y siga las instrucciones de instalacin de los controladores que se ofrecen a continuacin.
Instalacin de los controladores y el software Intel® PROSet
Sistemas operativos Microsoft* Windows*
NOTAS:
La instalacin de los controladores requiere que se tengan derechos de administrador en el sistema operativo.
Consulte la pgina de requisitos de sistema del manual del adaptador Intel 10GbE para obtener informacin sobre los sistemas operativos compatibles.
El adaptador se detecta como hardware nuevo cuando Windows se inicia. Para instalar el controlador correcto:
El adaptador se detecta y Windows instala un controlador residente de Windows o inicia el asistente Nuevo hardware encontrado
.
Si se inicia el asistente, siga las indicaciones para instalar el controlador desde el CD que se suministra.
Si se instala un controlador residente de Windows (no aparece el asistente), inserte el CD de Intel y haga clic en el botn Instalar los controladores y el software para actualizar el controlador cuando la ventana de ejecucin automtica Conexiones de red Intel
aparece.
Linux
Para compilar un paquete RPM* binario de este controlador, ejecute 'rpmbuild -tb <nombre_de_archivo.tar.gz>'. Sustituya <nombrearchivo.tar.gz> por el nombre de archivo especfico del controlador.
NOTA: Para que la creacin funcione correctamente, el kernel en ejecucin DEBE coincidir con la versin y configuracin de las fuentes instaladas del kernel. Si acaba de recompilar el kernel, reinicie el sistema.
El funcionamiento de RPM slo se ha probado con las distribuciones Red Hat.
Mueva el archivo con la extensin tar del controlador base al directorio que seleccione. Por ejemplo, utilice '/home/username/ixgb' o '/usr/local/src/ixgb'.
Para descomprimir el archivo, escriba lo siguiente, donde <x.x.x> es el nmero de versin del archivo tar del controlador:
tar zxf ixgb-<x.x.x>.tar.gz
Vaya al directorio src del controlador. donde <x.x.x> es el nmero de versin del archivo tar del controlador:
Las ubicaciones de instalacin descritas anteriormente son las predeterminadas, y es posible que no sean correctas para determinadas distribuciones de Linux.
Instale el mdulo:
modprobe ixgb <parmetro>=<valor>
Asigne una direccin IP a la interfaz. Para ello, escriba lo siguiente, donde <x> es el nmero de interfaz:
ifconfig eth<x> <direccin_IP>
Compruebe que funcione la interfaz. Introduzca lo siguiente, donde <direccin_IP> es la direccin IP de otra mquina situada en la misma subred que la interfaz que se est probando:
ping <direccin_IP>
FreeBSD
Compilacin e instalacin
Este controlador ha sido desarrollado para utilizarse con las versiones 4.8 y posteriores del kernel FreeBSD.
NOTA: Debe contar con los recursos de kernel ya instalados para poder compilar el mdulo de controlador.
En las instrucciones a continuacin, x.x.x es la versin del controlador segn se indica en el nombre del archivo tar del controlador.
Mueva el archivo con la extensin tar del controlador base al directorio que seleccione. Por ejemplo, utilice /home/username/ixgb o
/usr/local/src/ixgb.
Descomprima el archivo tar o zip:
tar xfz ixgb-x.x.x.tar.gz
Esto crear un directorio ixgb-x.x.x.
Para instalar una pgina man:
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
Para cargar el controlador en un sistema en ejecucin, realice los pasos siguientes:
cd ixgb-x.x.x
make
O BIEN
cd ixgb-x.x.x/src
make load
Para asignar una direccin IP a la interfaz, escriba lo siguiente:
ifconfig ixgb<nm_interfaz>
<direccin_IP>
Compruebe que funcione la interfaz. Escriba lo siguiente, donde <direccin_IP> es la direccin IP de otra mquina en la misma subred donde se encuentra la interfaz que se est probando: ping <direccin_IP>
Si desea que el controlador se cargue automticamente cuando se inicie el sistema:
cd ixgb-x.x.x/src make load cp if_ixgb.ko /modules
Modifique /boot/loader.conf, y agregue la siguiente lnea:
if_ixgb_load="YES"
O BIEN
compile el controlador en el kernel (vea el punto 8).
Edite /etc/rc.conf y cree la entrada correspondiente de ifconfig_ixgb<nm_interfaz>:
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 EE.UU.
Intel Corporation no asume ninguna responsabilidad por los errores y omisiones en esta gua.
Del mismo modo, Intel no se compromete de ninguna forma a actualizar la informacin
aqu contenida.
Intel, Itanium y Pentium son marcas comerciales de Intel Corporation en los EE.UU. y en otros pases.
* Otros nombres y marcas pueden ser reclamados como propiedad de terceras partes.
IMPORTANTE: LASE ANTES DE COPIAR, INSTALAR O UTILIZAR.
No copie, instale ni utilice este software y cualquier material asociado (colectivamente, el “Software”) proporcionado con este contrato de licencia (“Contrato”) hasta que haya ledo atentamente los siguientes trminos y condiciones.
Al copiar, instalar o utilizar el Software de otro modo, acepta que estar sujeto por los trminos de este Contrato. Si no est de acuerdo con los trminos de este Contrato, no copie, instale ni utilice el Software.
LICENCIAS:
Tenga en cuenta que:
Si es usted un administrador de redes o de sistema, le corresponde la seccin “Licencia de sitio”.
Si es un usuario final, le corresponde la seccin "Licencia de usuario individual".
Si es usted un fabricante de equipo original (OEM), le corresponde la seccin "Licencia de OEM".
LICENCIA DE SITIO: Puede copiar el Software en los sistemas de su organizacin para el uso de sta, y podr efectuar un nmero prudente de copias de seguridad del Software, sujeto a las siguientes condiciones:
La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales (“emulados”) diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso del Software.
No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
El Software puede incluir partes ofrecidas en trminos que difieren de los establecidos aqu, y que se han proporcionado en una licencia que acompaa a dichas partes.
LICENCIA DE USUARIO NICO:
Puede copiar el Software en un nico sistema para su uso personal, no comercial, y realizar una copia de seguridad del Software con estas condiciones:
La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales (“emulados”) diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso del Software.
No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
El Software puede incluir partes ofrecidas en trminos que difieren de los establecidos aqu, y que se han proporcionado en una licencia que acompaa a dichas partes.
LICENCIA DE OEM:
Solo puede reproducir y distribuir el Software como parte integral de, o incorporado en su producto, como actualizacin independiente de mantenimiento del Software para usuarios finales existentes de sus productos, excluidos otros productos independientes, o como componente de una distribucin de Software mayor, incluyendo, aunque sin limitarse a ella, la distribucin de una imagen de instalacin o una imagen de mquina virtual invitada, con estas condiciones:
La licencia de este Software sirve para su uso solo junto con (a) productos de componentes de Intel fsicos, y (b) dispositivos virtuales (“emulados”) diseados para aparecer como productos de componentes de Intel en un sistema operativo invitado que funcione en el contexto de una mquina virtual. Cualquier otro uso del Software, incluido su uso con productos de componentes no de Intel, aunque sin limitarse a l, no est cubierto por esta licencia.
Intel Corporation ("Intel") le concede, con sujecin a todos los trminos y condiciones de este Contrato, una licencia de copyright no exclusiva y no asignable de uso del Software.
No puede copiar, modificar, alquilar, vender, distribuir ni transferir parte alguna del Software, excepto segn se especifique en este Contrato, y se aviene a impedir la copia no autorizada del Software.
No puede aplicar tcnicas de ingeniera inversa, descompilar ni desensamblar el Software.
Solamente podr distribuir el Software a sus clientes, conforme a un contrato de licencia por escrito. Ese contrato de licencia puede tener el carcter de contrato de licencia por "ruptura del sello". Al menos, esa licencia va a salvaguardar los derechos de propiedad sobre el Software de Intel.
No puede distribuir, sublicenciar ni transferir la forma de cdigo fuente de ningn componente del software y derivados del mismo a un tercero sin el consentimiento expreso por escrito de Intel.
El Software puede incluir partes ofrecidas en trminos que difieren de los establecidos aqu, y que se han proporcionado en una licencia que acompaa a dichas partes.
RESTRICCIONES DE LA LICENCIA.
Usted NO podr: (i) usar o copiar el Software excepto segn lo estipulado en este contrato; (ii) alquilar o arrendar el Software a un tercero; (iii) asignar este contrato o transferir el Software sin el consentimiento expreso por escrito de Intel; (iv) modificar, adaptar o traducir el Software, en todo o en parte, excepto segn lo estipulado en este contrato; (v) realizar operaciones de ingeniera inversa, descompilar o desensamblar el Software; (vi) intentar modificar o manipular el funcionamiento normal de un gestor de licencias que regule el uso del Software; (vii) distribuir, sublicenciar o transferir la forma de cdigo fuente de cualquier componente del Software y sus derivados a un tercero sin el consentimiento expreso por escrito de Intel; (viii) permitir, autorizar, licenciar o sublicenciar a un tercero a ver o utilizar el cdigo fuente; (ix) modificar o distribuir el cdigo fuente o el Software para que cualquier parte del mismo pase a estar sujeta a una licencia excluida. (Una "licencia excluida" es aqulla que requiere, como condicin de uso, modificacin o distribucin, que (a) el cdigo debe revelarse o distribuirse en la forma de cdigo fuente; o (b) otros tienen el derecho de modificarlo.); (x) utilizar o incluir el cdigo fuente o el software en programas engaosos, maliciosos o ilegales.
NO EXISTEN OTROS DERECHOS.
Intel no le concede otros derechos o licencias, de manera expresa o implcita, con respecto a cualquier informacin de titularidad o patente, copyright, topografa de circuito integrado, marca comercial, secretos comerciales, u otros derechos de titularidad de propiedad intelectual o controlados por Intel, a excepcin de lo que se establece expresamente en este Contrato. Salvo lo previsto expresamente en este documento, no se le concede ninguna licencia o derecho, de manera directa o implcita, incentivo, impedimento legal o de otra manera. Especficamente, Intel no le concede ningn derecho expreso o implcito bajo patentes, copyrights, marcas comerciales u otros derechos de propiedad intelectual de Intel.
PROPIEDAD DEL MATERIAL Y LOS "COPYRIGHTS". El Software se otorga con licencia, no se vende. Intel mantiene el ttulo de propiedad de todas las copias del Software. El Software dispone de sus correspondientes derechos de autor, y est amparado por la legislacin estadounidense y de otros pases, as como por disposiciones de tratados internacionales. No est permitido eliminar del Software ninguna nota sobre los derechos de autor. Acepta evitar cualquier copia no autorizada del Software. Intel puede introducir modificaciones en el Software, o en elementos a los que se hace referencia en el mismo, en cualquier momento y sin previo aviso, sin tener obligacin de prestar asistencia tcnica o actualizar el Software.
TRMINOS ADICIONALES PARA EL SOFTWARE PREVIO A LA VERSIN. Si el Software que est instalando o utilizando bajo este contrato es una versin previa a la comercializacin, o est etiquetada o representada de otra manera como versiones “alfa“ o “beta“ del Software ("Software previo a la versin"), se aplican los trminos siguientes. Hasta el extremo que cualquier disposicin de esta Seccin est en conflicto con otro(s) trmino(s) o condicin(es) de este Contrato respecto al Software previo a la versin, esta Seccin prevalecer sobre otro(s) trmino(s) o condicin(es), pero slo hasta el extremo necesario para resolver el conflicto. Entiende y reconoce que el Software es Software previo a la versin, no representa el Software final de Intel, y puede contener errores y otros problemas que podran causar la prdida de datos, fallos del sistema u otros errores. El Software previo a la versin se proporciona "como est" e Intel rechaza toda garanta o responsabilidad hacia usted por cualquier dao causado por el uso del Software previo a la versin. Reconoce que Intel no ha prometido que el Software previo a la versin se comercializar en el futuro, que Intel no tiene ninguna obligacin expresa o implcita hacia usted de comercializar el Software previo a la versin y que Intel puede presentar Software que no sea compatible con el Software previo a la versin. Reconoce que la totalidad de cualquier investigacin o desarrollo relacionado con el Software previo a la versin o con cualquier producto que utilice o est asociado con el Software previo a la versin se realizar por su cuenta y riesgo. Si Intel le ha proporcionado Software previo a la versin segn los trminos de un contrato escrito por separado, su uso del Software previo a la versin tambin est regido por dicho contrato.
GARANTA LIMITADA DE SOPORTES. Si Intel ha entregado el Software en un soporte fsico, Intel garantiza que dicho soporte est libre de defectos fsicos de material durante los noventa das despus de la entrega. Si encuentra algn defecto semejante, devuelva el soporte a Intel para reemplazarlo o para que Intel le entregue el Software de otro modo, a discrecin de Intel.
EXCLUSIN DE OTRAS GARANTAS. A EXCEPCIN DE LO ESTIPULADO ANTERIORMENTE, EL SOFTWARE SE FACILITA "TAL CUAL" SIN GARANTA EXPRESA O IMPLCITA DE NINGN TIPO, INCLUIDAS LAS GARANTAS DE COMERCIABILIDAD, NO INFRACCIN O ADECUACIN PARA UNA FINALIDAD CONCRETA. Intel no garantiza ni asume responsabilidad en cuanto a la exactitud o integridad de cualquier informacin, texto, grficos, enlaces u otros elementos contenidos en el Software.
LIMITACIN DE RESPONSABILIDAD. EN NINGN CASO NI INTEL NI SUS PROVEEDORES SERN RESPONSABLES POR DAO ALGUNO DERIVADO DEL USO DEL SOFTWARE, O DE NO PODER USARLO (INCLUSIVE, SIN LIMITACIN ALGUNA, POR LOS DAOS DERIVADOS DEL CESE DE LUCRO, DE LA INTERRUPCIN DE LA ACTIVIDAD O EL NEGOCIO, O DE LA PRDIDA DE DATOS O INFORMACIN), AUN SI INTEL HUBIERA SIDO ADVERTIDA DE DICHA POSIBILIDAD. EN CIERTAS JURISDICCIONES SE PROHBE LA EXCLUSIN O LIMITACIN DE RESPONSABILIDAD RESPECTO A GARANTAS IMPLCITAS O DAOS INDIRECTOS O CASUALES, POR LO QUE LAS LIMITACIONES MENCIONADAS PUEDEN NO SER APLICABLES EN SU CASO. ASIMISMO, ES POSIBLE QUE TENGA OTROS DERECHOS LEGALES QUE VAREN DE UNA JURISDICCIN A OTRA. En caso de que utilice el Software junto con un dispositivo virtual (“emulado”) diseado para aparecer como un producto de componente de Intel, reconoce que Intel no es el autor ni el creador del dispositivo virtual (“emulado”). Entiende y reconoce que Intel no hace ninguna declaracin sobre el funcionamiento correcto del Software cuando se utiliza con un dispositivo virtual (“emulado”), que Intel no dise el Software para que funcione conjuntamente con el dispositivo virtual (“emulado”) y que el Software puede no ser capaz de corregir el funcionamiento conjuntamente con el dispositivo virtual (“emulado”). Acepta asumir el riesgo de que el Software no funcione de forma correcta conjuntamente con el dispositivo virtual (“emulado”). Acepta indemnizar y mantener a Intel, sus directores, subsidiarias y afiliados libres de toda responsabilidad contra cualquier demanda, costo, dao y gasto y honorarios razonables de abogados que surjan de, directa o indirectamente, cualquier reclamo por productos defectuosos, daos personales o muerte relacionadas con el uso no previsto o no autorizado del Software conjuntamente con el dispositivo virtual (“emulado”), incluso si dicha accin se basa en que Intel fue negligente con respecto al diseo o fabricacin del Software.
USO NO AUTORIZADO.EL SOFTWARE NO EST DISEADO, PREVISTO O AUTORIZADO PARA SU USO EN CUALQUIER TIPO DE SISTEMA O APLICACIN EN LA QUE UN FALLO DE SOFTWARE PODRA CREAR UNA SITUACIN DONDE SE PRODUJERAN LESIONES PERSONALES O LA MUERTE (POR EJEMPLO, SISTEMAS MDICOS, DE SOPORTE VITAL O PARA SALVAR VIDAS).
Si utiliza el Software para cualquier uso no previsto o no autorizado, deber indemnizar y considerar sin responsabilidad a Intel y sus directores, subsidiarias y afiliados contra cualquier demanda, costo, dao y gasto y honorarios razonables de abogados que surjan de, directa o indirectamente, cualquier reclamo por productos defectuosos, daos personales o muerte relacionadas con dicho uso no previsto o no autorizado, incluso si dicha accin se basa en que Intel fue negligente con respecto al diseo o fabricacin del componente.
RESCISIN DE ESTE CONTRATO.
Si infringe los trminos de este Contrato, Intel puede rescindirlo en cualquier momento. Tras la rescisin, usted deber destruir inmediatamente el Software o devolver a Intel todas las copias del mismo.
LEGISLACIN APLICABLE.
Las reclamaciones que surjan bajo este Contrato estarn regidas por las leyes del estado de California, independientemente de los principios de conflicto de leyes. Acepta que los trminos de la Convencin sobre contratos para la venta internacional de bienes de las Naciones Unidas no se aplican a este Contrato. Se prohbe exportar el Software si dicho acto violara cualquier ley o reglamento aplicable sobre exportaciones. Intel no est obligada por ningn otro contrato, a menos que ste se haya realizado por escrito y est firmado por un representante autorizado de Intel.
DERECHOS RESTRINGIDOS DEL ESTADO.
El Software y la documentacin incluidos se desarrollaron a cargo de una iniciativa privada y se proporcionan con “DERECHOS LIMITADOS”. Su uso, reproduccin o divulgacin por el Gobierno est sujeto a las restricciones establecidas en FAR 52.227-14 y DFAR 252.227-7013 y siguientes o sus sucesoras. El uso de este producto por parte del Gobierno constituye el reconocimiento de los derechos de titularidad de Intel sobre el mismo. El contratista o fabricante es Intel.
IDIOMA; TRADUCCIONES.
En el caso de que la versin en ingls de este Contrato est acompaada por cualquier otra versin traducida a otro idioma, dicha versin traducida slo se ofrece a ttulo informativo y prevalecer la versin en ingls.
Intel garantiza al propietario original que el producto de adaptador proporcionado en este paquete no tendr defectos en el material o en la manufactura. Esta garanta no cubre el producto de adaptador si ste se daa durante el proceso de instalacin o si se utiliza de forma indebida.
LA GARANTA ANTERIOR TOMA EL LUGAR DE CUALQUIER OTRA GARANTA, YA SEA EXPLCITA, IMPLCITA O ESTABLECIDA POR LA LEY, INCLUSO SIN LIMITACIN CUALQUIER GARANTA DE FALTA DE CUMPLIMIENTO DE PROPIEDAD INTELECTUAL, COMERCIABILIDAD O IDONEIDAD PARA UN PROPSITO PARTICULAR QUE SURGIESE DE CUALQUIER PROPUESTA, ESPECIFICACIN O MUESTRA.
Esta garanta no cubre el reemplazo de productos de adaptador daados por abuso, accidente, uso indebido, negligencia, alteracin, reparacin, desastre, instalacin incorrecta o prueba inapropiada. Si se determina que el producto de adaptador est defectuoso, Intel, a su propia discrecin, reemplazar o reparar el producto de hardware sin ningn cargo con excepcin de lo estipulado ms adelante, o bien, reembolsar el precio de compra siempre y cuando usted entregue el producto de adaptador junto con un nmero de Autorizacin de devolucin de material (RMA) (vase ms adelante) y junto con la prueba de compra (si no se ha registrado), ya sea al distribuidor a travs del cual lo adquiri o a Intel, con una explicacin de cualquier deficiencia. Si enva el producto de adaptador, usted asume el riesgo de dao o prdida durante el transporte. Usted debe utilizar el contenedor original (o su equivalente) y pagar por el cargo de transporte.
Intel puede reemplazar o reparar el producto de adaptador ya sea con piezas nuevas o reacondicionadas, y cualquier producto de adaptador o pieza del mismo que Intel reemplace se convierte en propiedad de Intel. Los productos de adaptador reparados o reemplazados se devolvern a usted con el mismo nivel de revisin que se recibi o uno ms alto, a la discrecin de Intel. Intel se reserva el derecho de reemplazar los productos de adaptador descontinuados con un producto de adaptador de una generacin actual equivalente
Devolucin de productos defectuosos
En Amrica del Norte:
Antes de devolver cualquier producto de adaptador, comunquese con la Asistencia al cliente Intel y obtenga un nmero de Autorizacin de devolucin de material (RMA). Para ello, llame al +1 916-377-7000.
Si el grupo de asistencia al cliente verifica que el producto de adaptador est defectuoso, harn que el departamento de RMA emita un nmero RMA, el cual debe colocarse en la parte externa del paquete del producto de adaptador. Intel no aceptar ningn producto que no contenga un nmero RMA en el paquete.
Todas las dems ubicaciones:
Devuelva el producto de adaptador al punto de venta para obtener un reembolso o reemplazo.
Garanta de devolucin de dinero para adaptadores Intel (solamente en Amrica del Norte)
Intel desea su total satisfaccin con el producto de adaptador Intel que ha comprado. En cualquier momento dentro de los noventa (90) das a partir de la compra, usted puede devolver el adaptador Intel al punto de venta original para obtener el reembolso total del precio de compra a travs del distribuidor. Los vendedores y distribuidores, respectivamente, que acepten devoluciones y reembolsen dinero a sus clientes pueden devolver los adaptadores Intel a sus puntos de venta originales. Intel garantiza que aceptar las devoluciones bajo esta poltica y que reembolsar el precio de compra original a los clientes que compren directamente a travs de Intel.
Limitacin de responsabilidad y remedio
LA NICA RESPONSABILIDAD DE INTEL ESTIPULADA EN ESTE DOCUMENTO SE LIMITAR A LOS DAOS DIRECTOS QUE PUEDAN MEDIRSE DE FORMA OBJETIVA. BAJO NINGUNA CIRCUNSTANCIA INTEL TENDR NINGUNA RESPONSABILIDAD POR CUALQUIER DAO INDIRECTO O ESPECULATIVO (INCLUSO SIN LIMITACIN LOS DAOS PRECEDENTES, CONSIGUIENTES, FORTUITOS Y ESPECIALES) LO CUAL INCLUYE, SIN LIMITACIN, EL INCUMPLIMIENTO DE PROPIEDAD INTELECTUAL, LOS COSTOS DE READQUISICIN, LA PRDIDA DE USO, LAS INTERRUPCIONES COMERCIALES, LA PRDIDA DE REPUTACIN Y LA PRDIDA DE GANANCIAS, YA SEA QUE CUALQUIERA DE ESOS DAOS SURJAN POR NEGLIGENCIA CONTRACTUAL, RESPONSABILIDAD EXTRACONTRACTUAL O BAJO CUALQUIER GARANTA, INDEPENDIENTEMENTE DE SI INTEL RECIBE UN AVISO POR ANTICIPADO DE LA POSIBILIDAD DE CUALQUIERA DE ESTOS DAOS. A PESAR DE LO ANTERIORMENTE MENCIONADO, LA RESPONSABILIDAD TOTAL DE INTEL PARA CUALQUIER RECLAMO QUE SURJA BAJO ESTE CONTRATO NO EXCEDER EL PRECIO PAGADO POR EL PRODUCTO. ESTAS LIMITACIONES DE RESPONSABILIDADES POSIBLES CONSTITUYERON UN ELEMENTO ESENCIAL EN LA FIJACIN DEL PRECIO DEL PRODUCTO. INTEL NO ASUME NI AUTORIZA QUE NADIE ASUMA NINGUNA OTRA RESPONSABILIDAD EN SU NOMBRE.
Algunos estados no permiten la exclusin o limitacin de daos fortuitos o consiguientes, de modo que las limitaciones anteriores podran no aplicarse en su caso.
Aplicaciones de control crtico: Intel de forma especfica niega cualquier responsabilidad por el uso del producto de adaptador en aplicaciones de control crtico (incluso, solamente como ejemplo, los sistemas de control de atencin mdica, los sistemas de control de energa nuclear o los sistemas de control de trfico areo o terrestre) por los Titulares de licencia o los Titulares de sublicencia, y dicho uso se realiza bajo el riesgo total del usuario. El Titular de licencia acuerda defender, indemnizar y asumir responsabilidad ante Intel por cualquier reclamo que surgiese del uso del producto de adaptador en dichas aplicaciones del Titular de licencia o
Titulares de sublicencia.
Software: El software proporcionado con el producto de adaptador no est cubierto bajo la garanta de hardware descrita anteriormente. Consulte el contrato de licencia de software correspondiente, el cual acompaa al producto del adaptador, para obtener detalles sobre la garanta de software.
Nota: Si es un consumidor sometido a la Ley del consumidor de Australia, esta garanta no se aplicar en su caso. Visite Australian Limited Lifetime Hardware Warranty para ver la garanta limitada que se puede aplicar a los consumidores australianos.
Installer la carte rseau 10 Gigabit Ethernet Intel® pour serveurs
Installer une carte rseau
Mettez l'ordinateur hors tension et dbranchez le cordon d'alimentation. En cas d'installation sans arrt du serveur, reportez-vous tout d'abord la documentation du serveur.
Retirez le panneau de l'ordinateur et le panneau du connecteur de carte rseau correspondant votre carte rseau. Vous pouvez utiliser sans inconvnient un emplacement plus long que le connecteur de la carte rseau, mais n'essayez pas d'installer la carte rseau dans un emplacement plus court que le connecteur PCI Express.
Enfoncez fermement la carte rseau dans l'emplacement et fixez le support.
Remettez le panneau de l'ordinateur en place. Branchez le cordon d'alimentation.
Installer une carte Mezzanine
Mettez l'ordinateur hors tension et dbranchez le cordon d'alimentation.
Enlevez le panneau de l'ordinateur en place.
Alignez le connecteur PCIe csur la carte Mezzanine avec le connecteur et quatre entretoises en plastique sur la carte mre.
Insrez la carte rseau compltement dans le connecteur de la carte mre et enclenchez-la dans les quatre entretoises.
Remettez le panneau de l'ordinateur en place. Branchez le cordon d'alimentation.
Brancher le cble rseau
Cartes rseau 10 Gigabit Ethernet Intel® cuivre : Utilisez des cbles Ethernet de catgorie 6, 6a ou 7.
Carte rseau 10 Gigabit Ethernet Intel® pour serveurs avec fibre optique enfichable SFP+ : Installez le module et branchez le cble conformment aux instructions du fabricant du module.
Cartes rseau 10 Gigabit Ethernet Intel® fibre avec connecteur SC : Retirez le panneau du connecteur fibre optique et mettez-le de ct. Insrez un connecteur SC fibre optique dans les ports TX/RX du support de la carte rseau.
Cartes rseau 10 Gigabit Ethernet Intel® fibre avec connecteur LC : Retirez le panneau du connecteur fibre optique et mettez-le de ct. Insrez un connecteur LC dans la carte rseau. Les cbles de conversion pour d'autres types de connecteur (p. ex., un connecteur SC) peuvent tre utiliss si le cblage est conforme aux spcifications optiques de la carte rseau, y compris les limites de longueur.
Cartes rseau 10 Gigabit Ethernet Intel® CX4 : Le cblage physique doit tre conforme aux spcifications IEEE Std 802.3ak, clause 54. Le connecteur de cble requis est un connecteur verrou MDI, tel que dfini par IEC 61076-3-113.
Dmarrez votre ordinateur et suivez les instructions d'installation des pilotes ci-dessous.
Installer les pilotes et l'utilitaire Intel® PROSet
Systmes d'exploitation Microsoft* Windows*
REMARQUES :
L'installation des pilotes ncessite des droits d'administrateur sur le systme d'exploitation.
Reportez-vous la page relative la configuration requise dans le guide de la carte rseau Intel 10GbE pour une liste des systmes d'exploitation pris en charge.
La carte rseau est dtecte en tant que nouveau matriel lors de dmarrage de Windows. Pour installer le pilote correct :
La carte rseau est dtecte et Windows installe un pilote rsidant sous Windows ou dmarre l'Assistant Nouveau matriel dtect
.
Si l'assistant dmarre, suivez les invites pour installer le pilote depuis le CD fourni avec la carte rseau.
Si un pilote rsidant sous Windows s'installe (l'assistant ne dmarre pas), mettez jour le pilote en insrant le CD Intel et en cliquant sur le bouton Installer les pilotes lorsque la fentre d'excution automatique de Connexions rseau Intel
s'affiche.
Linux
Pour crer un paquage RPM* binaire de ce pilote, excutez "rpmbuild -tb <nom_de_fichier.tar.gz>". Remplacez <filename.tar.gz> par le nom de fichier spcifique du pilote.
REMARQUE : pour que la compilation fonctionne correctement, le noyau en cours d'excution DOIT correspondre la version et la configuration des sources de noyau installes. Si vous venez de recompiler le noyau, redmarrez l'ordinateur maintenant.
La fonctionnalit RPM a t teste uniquement sur les distributions Red Hat.
Placez le fichier tar du pilote de base dans le rpertoire de votre choix. Par exemple, utilisez "/home/username/ixgb" ou "/usr/local/src/ixgb".
Dballez/dcompressez l'archive en entrant la commande suivante, o <x.x.x> correspond au numro de version du paquetage du pilote :
tar zxf ixgb-<x.x.x>.tar.gz
Passez au rpertoire src du pilote en entrant la commande suivante, o <x.x.x> correspond au numro de version du paquetage du pilote :
cd ixgb-<x.x.x>/src/
Compilez le module du pilote :
make install
Les instructions binaires sont installes comme suit :
Les emplacements d'installation rpertoris ci-dessus sont les emplacements par dfaut. Il se peut qu'ils ne soient pas corrects sur certaines distributions Linux.
Installez le module :
insmod ixgb <paramtre>=<valeur>
Affectez une adresse IP l'interface en entrant la commande suivante, o <x> correspond au numro d'interface :
ifconfig eth<x> <adresse_IP>
Vrifiez que l'interface fonctionne. Entrez ce qui suit, o <adresse_IP> est l'adresse IP d'un autre ordinateur du mme sous-rseau que l'interface soumis au test :
ping <adresse_IP>
FreeBSD
Compilation et installation
Ce pilote a t dvelopp pour tre utilis avec le noyau FreeBSD, versions 4.8 et ultrieures.
REMARQUE : les sources du noyau doivent tre installes pour compiler le module du pilote.
Dans les instructions ci-dessous, x.x.x est la version du pilote telle qu'indique dans le nom du fichier tar du pilote.
Placez le fichier tar du pilote de base dans le rpertoire de votre choix. Par exemple, utilisez /home/nom de l'utilisateur/ixgb ou
/usr/local/src/ixgb.
Dcompressez l'archive :
tar xfz ixgb-x.x.x.tar.gz
Cela cre un rpertoire ixgb-x.x.x.
Pour installer man page :
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
Pour charger le pilote sur un ordinateur en marche, excutez les tapes suivantes :
cd ixgb-x.x.x
make
OU
cd ixgb-x.x.x/src
make load
Pour affecter une adresse IP l'interface, entrez ce qui suit :
ifconfig ixgb<num_interface>
<adresse_IP>
Vrifiez que l'interface fonctionne. Entrez la commande suivante, o <adresse_IP> correspond l'adresse IP d'un autre ordinateur du mme sous-rseau que celui sur lequel l'interface est teste : ping <adresse_IP>
Si vous voulez que le pilote se charge automatiquement lors de l'amorage de l'ordinateur :
cd ixgb-x.x.x/src make load cp if_ixgb.ko /modules
Modifiez le fichier /boot/loader.conf, puis ajoutez la ligne suivante :
if_ixgb_load="YES"
OU
compilez le pilote dans le noyau (voir lment 8).
ditez /etc/rc.conf et crez l’entre <n_interface>ifconfig_ixgb approprie :
Modifiez le fichier de configuration du noyau (c.--d. GENERIC ou MYKERNEL) dans /usr/src/sys/i386/conf, et assurez-vous que la ligne suivante existe :
device ixgb
Compilez et installez le noyau. Le systme doit tre redmarr pour que les mises jour du noyau soient prises en compte.
Pour obtenir des informations complmentaires sur la compilation du noyau, consultez la documentation du systme d'exploitation FreeBSD.
Informations complmentaires
Pour de plus amples informations, voir le Guide de l'utilisateur du CD Intel ou sur le site Web d'assistance Intel : http://www.intel.com/p/fr_FR/support/.
Intel Corporation dcline toute responsabilit pour toute erreur ou omission dans ce document. Intel ne s'engage aucunement mettre jour les informations contenues dans ce document.
Intel, Itanium et Pentium sont des marques de commerce d'Intel Corporation aux tats-Unis et dans d'autres pays.
* Les autres marques et noms de produits sont des marques commerciales appartenant leurs propritaires respectifs.
IMPORTANT - LIRE AVANT TOUTE TENTATIVE DE COPIE, D'INSTALLATION OU D'UTILISATION :
Ne copiez pas, n'installez pas et n'utilisez pas ce logiciel ni tout lment associ (appels collectivement le Logiciel ) fournis dans le cadre de ce contrat de licence ( Contrat ) tant que vous n'avez pas lu attentivement les conditions gnrales suivantes.
En copiant, installant ou autrement utilisant le Logiciel, vous acceptez d'tre li aux modalits de ce Contrat. Si vous n'acceptez pas les modalits de ce Contrat, ne copiez pas, n'installez pas et n'utilisez pas le Logiciel.
CONTRATS DE LICENCE.
Veuillez noter :
Si vous tes un administrateur rseau, reportez-vous la Licence de site ci-dessous.
Si vous tes un utilisateur final, reportez-vous la Licence utilisateur unique ci-dessous.
Si vous tes un fabricant OEM, reportez-vous la Licence OEM .
LICENCE DE SITE. Vous pouvez copier le Logiciel sur les ordinateurs de votre organisation afin qu'il soit utilis dans le cadre des activits de l'organisation et vous pouvez sauvegarder un nombre raisonnable de copies du Logiciel, conformment ces conditions :
Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser le Logiciel.
Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
Le Logiciel peut inclure des portions offertes sous des conditions autres que celles dcrites ici, telles que dfinies dans la licence accompagnant ces portions.
LICENCE UTILISATEUR UNIQUE.
Vous pouvez copier le Logiciel sur un seul ordinateur pour une utilisation personnelle, et vous pouvez effectuer une copie de sauvegarde du Logiciel, conformment ces conditions :
Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser le Logiciel.
Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
Le Logiciel peut inclure des portions offertes sous des conditions autres que celles dcrites ici, telles que dfinies dans la licence accompagnant ces portions.
LICENCE OEM.
Vous pouvez reproduire et distribuer le Logiciel uniquement s'il fait partie intgrante ou est incorpor votre produit, comme une mise jour de maintenance de Logiciel autonome pour les utilisateurs existants de vos produits, l'exclusion de tout autre produit autonome, ou en tant que composant d'une distribution plus tendue du Logiciel, y compris, mais sans s'y limiter, la distribution d'une image d'installation ou d'une image d'Ordinateur Virtuel Invit, sous rserve de ces conditions :
Ce Logiciel est accord sous licence pour une utilisation exclusive avec (a) des composants physiques Intel et (b) des priphriques virtuels ( mul ) conus pour apparatre comme des composants Intel dans un systme d'exploitation Invit excut dans le contexte d'un ordinateur virtuel. Toute autre utilisation du Logiciel, y compris, sans s'y limiter, toute utilisation avec des composants non Intel, n'est pas couverte par la licence ci-aprs.
Sous rserve des modalits de ce Contrat, Intel Corporation ( Intel ) vous accorde une licence non exclusive, non transfrable, d'utiliser le Logiciel.
Vous n’tes pas autoris copier, modifier, louer, vendre, distribuer, ni transfrer une partie quelconque du Logiciel, sauf dans la mesure prvue par le prsent Contrat, et vous vous engagez empcher toute copie non autorise du Logiciel.
Vous n'tes pas autoris reconstituer la logique du Logiciel, le dcompiler ou le dsassembler.
Vous tes autoris distribuer le Logiciel vos clients conformment un contrat de licence crit. L'ouverture de l'emballage scell entrane l'acceptation implicite des modalits du contrat de licence. Cette licence doit au minimum protger les droits de proprit du Logiciel d'Intel.
Vous n'tes pas autoris distribuer, cder en sous-licence ou transfrer le Code source des composants du Logiciel ou de ses drivatifs un tiers sans l'autorisation crite explicite d’Intel.
Le Logiciel peut inclure des portions offertes sous des conditions autres que celles dcrites ici, telles que dfinies dans la licence accompagnant ces portions.
RESTRICTIONS DE LA LICENCE.
Vous ne pouvez PAS : (i) utiliser ou copier le Logiciel, sauf selon les modalits prvues dans le prsent Contrat ; (iii) assigner le prsent Contrat ou transfrer le Logiciel sans l'autorisation crite explicite d’Intel ; (iv) modifier, adapter ou traduire tout ou partie du Logiciel, sauf selon les modalits prvues dans le prsent Contrat ; (v) effectuer d'ingnierie inverse, dcompiler ou dsassembler le Logiciel ; (vi) essayer de modifier ou d’altrer le fonctionnement normal du gestionnaire de licences qui rgit l’utilisation du Logiciel ; (vii) distribuer, cder en sous-licence ou transfrer le Code source des composants du Logiciel ou de ses drivatifs un tiers sans l'autorisation crite explicite d’Intel ; (viii) autoriser, licencier ou cder en sous-licence l'affichage ou l'utilisation du Code source un tiers ; (ix) modifier ou distribuer le Code source ou le Logiciel de sorte qu'une partie soit sujette une licence exclue. (Une licence exclue est une licence qui requiert, comme condition d'utilisation, de modification ou de distribution, (a) que le code soit divulgu ou distribu sous la forme de code source ; ou (b) que d'autres aient le droit de le modifier.); (x) utiliser ou inclure le Code source ou le Logiciel dans des programmes malveillants, illgaux ou trompeurs.
EXCLUSION DES AUTRES DROITS.
Aucun droit ou licence ne vous est accord par Intel, de manire explicite ou implicite, en ce qui concerne toute information ou tout brevet propritaire, droit d'auteur, moyen de masquage, marque commerciale, secret industriel ou tout autre droit de proprit intellectuelle contrl par Intel, sauf stipulation contraire dcrite dans ce Contrat. Sauf comme stipul dans la prsente, aucune licence et aucun droit ne vous est accord, directement ou implicitement, de faon induite, par prclusion, ou autre. Spcifiquement, Intel ne vous accorde aucun droit expresse ou induit concernant les brevets, droits d'auteur, marques de commerce ou droits de proprit intellectuelle d'Intel.
PROPRIT DU LOGICIEL ET COPYRIGHT (DROITS D'AUTEUR). Le Logiciel est offert sous licence, il n'est pas vendu. Intel demeure propritaire de toutes les copies du Logiciel. Le logiciel est protg par les lois sur les droits d'auteur, les lois en vigueur aux tats-Unis et dans d'autres pays, ainsi que par les dispositions de traits internationaux. Vous n'tes pas autoris retirer la mention de copyright du Logiciel. Vous acceptez de prvenir toute copie non autorise du Logiciel. Intel peut modifier le Logiciel ou des lments rfrencs dans ce document, tout moment et sans pravis, mais n'est pas dans l'obligation de mettre jour le Logiciel ni d'offrir une assistance.
MODALITS SUPPLMENTAIRES RELATIVES AU LOGICIEL PRLIMINAIRE. Si le Logiciel que vous installez ou utilisez dans le cadre de ce Contrat est une version de prcommercialisation, ou s'il est tiquet ou autrement reprsent comme une version alpha ou bta du Logiciel ( Logiciel prliminaire ), les modalits suivantes sont applicables. Dans l'ventualit ou des clauses de cette Section entreraient en conflit avec d'autres modalits de ce Contrat concernant le Logiciel prliminaire, cette Section remplacerait les autres modalits, mais uniquement dans la mesure ncessaire la rsolution du conflit. Vous comprenez et reconnaissez que le Logiciel est un Logiciel prliminaire, qu'il ne reprsente pas la version finale du Logiciel d'Intel, et qu'il peut contenir des erreurs et d'autres problmes pouvant entraner des pertes de donnes, des pannes de systme et d'autres erreurs. Le Logiciel prliminaire vous est fourni en l'tat et Intel n'met aucune garantie et rejette toute responsabilit votre gard concernant les dommages issus de l'utilisation du Logiciel prliminaire. Vous reconnaissez qu'Intel n'a pas promis que le Logiciel prliminaire serait commercialis l'avenir, qu'Intel n'a aucune obligation expresse ou induite envers vous concernant la commercialisation du Logiciel prliminaire et qu'il est possible qu'Intel n'introduise pas de Logiciel compatible avec le Logiciel prliminaire. Vous reconnaissez que les efforts de recherche et de dveloppement que vous consentez concernant le Logiciel prliminaire ou tout produit utilisant ou associ au Logiciel prliminaire le sont vos propres risques. Si Intel vous a fourni un Logiciel prliminaire dans le cadre d'un accord crit spar, votre utilisation du Logiciel prliminaire est galement rgie par l'accord en question.
GARANTIE LIMITE DU SUPPORT. Si le logiciel a t remis par Intel sur un support physique, Intel garantit que celui-ci est exempt de dfauts matriels pour une priode de quatre-vingt-dix jours compter de la date de livraison par Intel. Si un tel dfaut est dtect, renvoyez le support Intel qui pourra choisir de le remplacer ou d'employer une autre mthode de livraison.
EXCLUSION DE TOUTE AUTRE GARANTIE. LE LOGICIEL EST FOURNI TEL QUEL SANS GARANTIE EXPRESSE OU TACITE DE QUELQUE NATURE QUE CE SOIT, Y COMPRIS TOUTE GARANTIE DE QUALIT MARCHANDE, DE RESPECT DES DROITS DE PROPRIT INTELLECTUELLE OU D'ADQUATION UN USAGE PARTICULIER. Intel ne garantit pas la prcision ni l'exhaustivit des informations, des textes, des graphiques, des liens ou d'autres lments contenus dans le Logiciel et ne peut en tre tenu responsable.
RESPONSABILIT LIMITE. INTEL OU SES FOURNISSEURS NE SONT EN AUCUN CAS RESPONSABLES DE QUELQUE DOMMAGE QUE CE SOIT (Y COMPRIS, MAIS SANS QUE CETTE NUMRATION NE SOIT LIMITATIVE, DES PERTES DE BNFICE, DES INTERRUPTIONS D'ACTIVITS OU DES PERTES D'INFORMATIONS) DRIVANT DE L'UTILISATION DE CE PRODUIT OU DE L'INCAPACIT DE L'UTILISER, MME SI INTEL A T NOTIFI DE LA POSSIBILIT D'UN TEL DOMMAGE. CERTAINES JURIDICTIONS N'AUTORISENT PAS L'EXCLUSION OU LA LIMITATION DE RESPONSABILIT POUR LES GARANTIES IMPLICITES OU LES DOMMAGES INDIRECTS OU ACCESSOIRES, DE SORTE QUE LA LIMITATION CI-DESSUS PEUT NE PAS VOUS TRE APPLICABLE. VOUS POUVEZ GALEMENT DISPOSER D'AUTRES DROITS QUI VARIENT DE JURIDICTION EN JURIDICTION. Dans l'ventualit o vous utilisez le Logiciel conjointement avec un priphrique virtuel ( mul ) conu pour apparatre comme un composant Intel, vous reconnaissez qu'Intel n'est ni l'auteur ni le crateur du priphrique virtuel ( mul ). Vous comprenez et reconnaissez qu'Intel ne fait aucune reprsentation concernant le fonctionnement correct du Logiciel lorsqu'il est utilis avec un priphrique virtuel ( mul ), qu'Intel n'a pas conu le Logiciel pour qu'il fonctionne conjointement avec le priphrique virtuel ( mul ), et qu'il est possible que le Logiciel ne soit pas capable de fonctionner correctement conjointement avec le priphrique virtuel ( mul ). Vous acceptez d'assumer le risque que le Logiciel ne fonctionne pas correctement conjointement avec le priphrique virtuel ( mul ). Vous acceptez d'indemniser Intel et ses responsables et filiales et de les protger contre les plaintes, cots, dommages, dpenses et honoraires d'avocat ventuels issus, directement ou indirectement de toute plainte concernant la responsabilit du produit, des blessures ou la mort associes l'utilisation du Logiciel conjointement avec le priphrique virtuel ( mul ), mme si cette plainte prtend qu'Intel a t ngligent concernant la conception ou la fabrication du Logiciel.
UTILISATION NON AUTORISE.LE LOGICIEL N'EST PAS CONU, PRVU OU AUTORIS POUR UNE UTILISATION AVEC TOUT TYPE DE SYSTME OU D'APPLICATION DONT UNE DFAILLANCE LOGICIELLE POURRAIT ENTRANER DES BLESSURES OU LA MORT (PAR EX., SYSTMES MDICAUX, SYSTMES DE MAINTIEN DE LA VIE OU DE SURVIE).
Si vous utilisez le Logiciel dans un cadre non prvu ou non autoris, vous acceptez d'indemniser Intel et ses responsables et filiales et de les protger contre les plaintes, cots, dommages, dpenses et honoraires d'avocat ventuels issus, directement ou indirectement de toute plainte concernant la responsabilit du produit, des blessures ou la mort associes l'utilisation du Logiciel dans un cadre non prvu ou non autoris, mme si cette plainte prtend qu'Intel a t ngligent concernant la conception ou la fabrication de la pice.
RSILIATION DE CE CONTRAT.
Intel peut rsilier ce contrat tout moment si vous n'en respectez pas les termes. Dans ce cas, vous devez immdiatement dtruire le Logiciel et retourner toutes les copies dudit Logiciel Intel.
LOIS APPLICABLES.
Les plaintes dposes dans le cadre de ce Contrat seront rgies par les lois de l'tat de Californie, sans considration pour les principes de conflit de lois. Vous acceptez que les termes de la Convention des Nations Unies sur les contrats de vente internationale de marchandises ne s'appliquent pas ce Contrat. Vous n'tes pas autoris exporter le Logiciel en infraction des lois et des rgulations d'exportation applicables. Intel n'est contraint par aucun autre contrat moins que celui-ci ne soit tabli par crit et sign par un reprsentant autoris d'Intel.
LIMITATION DES DROITS DU GOUVERNEMENT.
Le Logiciel et la documentation inclus ont t dvelopps avec des fonds privs, et sont fournis avec des DROITS RESTREINTS . L'utilisation, la duplication ou la diffusion par le gouvernement est soumise des restrictions comme indiqu dans les clauses FAR.52.227-14 et DFAR.252.227-7013 et suivantes ou leurs successeurs. L'utilisation de ce produit par le Gouvernement constitue une reconnaissance des droits de proprit d'Intel sur le Logiciel. Le sous-traitant ou le fabricant est Intel.
LANGUE ; TRADUCTIONS.
Au cas o la version en langue anglaise de cet Accord est accompagne d’une autre version traduite dans une autre langue, la version traduite est fournie uniquement pour des raisons de commodit et seule la version anglaise fait foi.
Intel garantit au propritaire original que la carte livre dans ce coffret est dpourvue de tout dfaut de matriel ou de fabrication. Cette garantie ne couvre pas la carte si elle a t endommage au cours de l'installation ou utilise de faon incorrecte.
LA GARANTIE CI-DESSUS REMPLACE TOUTE AUTRE GARANTIE, EXPLICITE, IMPLICITE OU RGLEMENTAIRE, Y COMPRIS MAIS SANS S'Y LIMITER, LES GARANTIES DE QUALIT MARCHANDE, DE RESPECT DES DROITS DE PROPRIT INTELLECTUELLE OU DADAPTATION UN USAGE PARTICULIER QUI DCOULERAIT DUNE PROPOSITION, DUNE SPCIFICATION OU BIEN DUN CHANTILLON
Cette garantie ne couvre pas le remplacement des cartes endommages suite une utilisation non conforme aux instructions, un usage inappropri, la ngligence, un accident, un abus, une altration, une rparation, un dsastre, une installation incorrecte ou un test incorrect. Si la carte est dfectueuse, Intel pourra, sa discrtion, remplacer ou rparer gratuitement le matriel sauf dans les cas dcrits ci-dessous, ou rembourser le prix d'achat condition que vous retourniez la carte avec un numro d'autorisation de retour (RMA) [voir ci-dessous], une preuve d'achat (si votre produit n'a pas t enregistr), soit au fournisseur chez qui vous avez achet la carte, soit Intel, en incluant une description du problme. Les risques de dommage ou de perte associs l'envoi du produit sont votre responsabilit. Vous devez utiliser l'emballage original (ou un emballage similaire) et payer les frais d'envoi.
Intel peut remplacer ou rparer la carte en utilisant des pices nouvelles ou remises neuf, et toute carte ou pice de carte remplace par Intel deviendra la proprit d'Intel. Les cartes rpares ou remplaces vous seront retournes au mme niveau de rvision reu ou un niveau suprieur, la discrtion d'Intel. Intel se rserve le droit de remplacer les cartes abandonnes par une carte quivalente de la gnration actuelle.
Retourner un produit dfectueux
Depuis l'Amrique du Nord :
Avant de retourner une carte, contactez le support client d'Intel et obtenez un numro d'autorisation de retour (RMA) en appelant le +1 (916) 377-7000.
Aprs vrification par le groupe de support client que le produit est dfectueux, le groupe demandera au service RMA d'mettre un numro RMA que vous devrez apposer sur le carton d'envoi de la carte. Intel n'acceptera aucun produit sans numro RMA appos sur le colis.
Tous les autres pays :
retournez la carte au lieu d'achat pour obtenir un remboursement ou une carte de remplacement.
Remboursement garanti sur les cartes Intel (Amrique du Nord uniquement)
Votre entire satisfaction des cartes Intel que vous avez achetes est trs importante pour Intel. Pour une priode de quatre-vingt dix (90) jours compter de la date d'achat, vous pouvez retourner la carte Intel au lieu d'achat original pour obtenir un remboursement total. Les revendeurs et les distributeurs acceptant les retours et remboursant leurs clients, respectivement, peuvent retourner les cartes Intel au lieu d'achat original. En vertu de la prsente, Intel garantit que les retours seront accepts et que le prix d'achat original sera rembours aux clients qui ont achets leur produit directement auprs d'Intel.
Limitation de responsabilit et recours
SELON CETTE GARANTIE, LA RESPONSABILIT D'INTEL SERA LIMITE AUX DOMMAGES DIRECTS ET MESURABLES OBJECTIVEMENT. INTEL NE SERA EN AUCUN CAS RESPONSABLE DES DOMMAGES INDIRECTS OU SPCULATIFS (Y COMPRIS ET SANS LIMITATION, LES DOMMAGES CONSCUTIFS, ACCIDENTELS ET SPCIAUX), Y COMPRIS, MAIS SANS S'Y LIMITER, LE RESPECT DE LA PROPRIT INTELLECTUELLE, LES COTS DE RAPPROVISIONNEMENT, LA PERTE D'UTILISATION, LES INTERRUPTIONS DACTIVITS ET LA PERTE DE BNFICES, QUE CES DOMMAGES DCOULENT D'UNE NGLIGENCE CONTRACTUELLE, D'UNE FAUTE, OU DE TOUTE GARANTIE, MME SI INTEL A T NOTIFI DE LA POSSIBILIT DE TELS DOMMAGES. NONOBSTANT CE QUI PRCDE, LA RESPONSABILIT TOTALE D'INTEL EN CAS DE RECOURS LI AU PRSENT CONTRAT NE POURRA DPASSER LE PRIX D'ACHAT PAY POUR LE PRODUIT. CES LIMITATIONS DES RESPONSABILITS POTENTIELLES CONSTITUAIENT UN LMENT ESSENTIEL POUR LA DTERMINATION DU PRIX DU PRODUIT. INTEL N'ASSUME NI N'AUTORISE QUICONQUE ASSUMER TOUTES AUTRES RESPONSABILITS.
Certains pays n'autorisent pas l'exclusion ou la limitation des dommages accidentels ou conscutifs, auquel cas les limitations susmentionnes peuvent ne pas vous tre applicables.
Applications de contrle critiques : Intel dcline toute responsabilit en cas d'utilisation de la carte dans des applications de contrle critiques (comme par exemple, les systmes de contrle mdicaux, de la scurit, de l'nergie nuclaire ou du trafic arien) par le dtenteur de la licence ou les sous-licencis. Ceux-ci assument tous les risques lis une telle utilisation. Le dtenteur de la licence accepte de dfendre, d'indemniser et de protger Intel contre les rclamations dcoulant de l'utilisation de la carte dans de telles applications par le dtenteur de la licence ou les
sous-licencis.
Logiciel : Le logiciel fourni avec la carte n'est pas couvert par la garantie sur le matriel dcrite ci-dessus. Reportez-vous au contrat de licence logicielle appropri livr avec la carte pour plus d'informations sur les garanties logicielles.
Remarque : Si vous tes un consommateur soumis au droit rgissant les contrats la consommation en Australie, cette garantie ne s'applique pas vous. Visitez la page relative la garantie limite vie sur le matriel pour l'Australie pour consulter la garantie limite applicable aux consommateurs australiens.
Dernire modification le 17/09/12 10h42
DOCS/QUICK/ITA 0000755 0000000 0000000 00000000000 12233424124 007703 5 ustar DOCS/QUICK/ITA/10qi_ita.htm 0000755 0000000 0000000 00000030500 12142406770 012112 0 ustar
Guida rapida di installazione delle schede di rete Intel(R)
Installazione della scheda di rete Intel®
Installazione della scheda di rete Ethernet Intel® 10 Gigabit per server
Installazione di una scheda di rete
Spegnere il computer e disinserire il cavo di alimentazione. Se si sta eseguendo un'installazione "a caldo", consultare la documentazione del server prima di proseguire.
Rimuovere il coperchio del computer e la protezione dello slot della scheda. Si pu utilizzare uno slot pi lungo del connettore della scheda di rete senza che questo provochi alcun danno, mentre non bisogna tentare di installarla in uno slot pi corto del connettore PCI Express.
Inserire saldamente la scheda nello slot e fissare la staffa di supporto.
Chiudere il coperchio del computer. Inserire il cavo di alimentazione.
Installazione di una scheda mezzanine
Spegnere il computer e disinserire il cavo di alimentazione.
Rimuovere il coperchio del computer.
Allineare il connettore PCIe e la scheda mezzanine con il connettore e i quattro isolatori di plastica sulla scheda madre.
Premere la scheda di rete finch completamente inserita nel connettore della scheda madre e agganciata ai quattro isolatori.
Chiudere il coperchio del computer. Inserire il cavo di alimentazione.
Collegare il cavo di rete
Schede di rete Ethernet Intel® 10 Gigabit in rame: usare cavi Ethernet di categoria 6, 6a o 7.
Scheda di rete Ethernet Intel® 10 Gigabit per server con fibra ottica SFP+ collegabile: installare il modulo e collegare il cavo seguendo le istruzioni del produttore del modulo.
Schede di rete Ethernet Intel®10 Gigabit in fibra con connettore SC: rimuovere e riporre la copertura del connettore a fibre ottiche. Inserire un connettore SC a fibre ottiche nelle porte TX/RX della staffa di supporto della scheda di rete.
Schede di rete Ethernet Intel® 10 Gigabit in fibra con connettore LC: rimuovere e riporre la copertura del connettore a fibre ottiche. Inserire un connettore LC nella scheda di rete. possibile usare cavi per convertire altri tipi di connettori (come SC) se tali cavi soddisfano le specifiche ottiche della scheda, lunghezza inclusa.
Schede di rete Ethernet Intel®10 Gigabit CX4: i cavi devono essere conformi alle specifiche dello standard IEEE Std 802.3ak, articolo 54. Il connettore richiesto per il cavo deve essere una presa MDI con chiusura, conformemente a quanto indicato nello standard IEC 61076-3-113.
Avviare il computer e seguire le istruzioni per l'installazione del driver riportate di seguito.
Installazione dei driver e del software Intel® PROSet
Sistemi operativi Microsoft* Windows*
NOTE:
L'installazione dei driver richiede i diritti di amministratore relativamente al sistema operativo.
Per informazioni sui sistemi operativi supportati, vedere la pagina Requisiti di sistemi della Guida della scheda di rete Intel 10GbE.
La scheda viene rilevata come nuovo hardware all'avvio di Windows. Per installare il driver corretto:
La scheda viene rilevata e Windows installa un driver residente di Windows o avvia Installazione guidata nuovo hardware
.
Se viene eseguita la procedura guidata, seguire le richieste per installare il driver dal CD allegato al prodotto.
Se viene installato un driver residente di Windows (non viene eseguita l'installazione guidata), aggiornare il driver inserendo il CD di Intel e facendo clic sul pulsante Installa i driver e il software quando viene visualizzata la finestra Intel Network Connections
.
Linux
Per generare un package binario RPM* di questo driver, eseguire 'rpmbuild -tb <nomefile.tar.gz>'. Sostituire <nomefile.tar.gz> con il nome file specifico del driver.
NOTA: affinch il processo di build funzioni correttamente, il kernel al momento in esecuzione DEVE corrispondere alla versione dei sorgenti del kernel installati. Se stato appena ricompilato il kernel riavviare il sistema.
Le funzionalit RPM sono state testate soltanto con le distribuzioni Red Hat.
Spostare il file tar del driver di base in una directory di propria scelta. Ad esempio, usare '/home/nomeutente/ixgb' o '/usr/local/src/ixgb'.
Annullare l'archiviazione/compressione dell'archivio, dove <x.x.x> il numero di versione del file tar del driver:
tar zxf ixgb-<x.x.x>.tar.gz
Passare alla directory src del driver, dove <x.x.x> il numero di versione del file tar del driver:
Le posizioni di installazione elencate pi indietro sono le posizioni predefinite. Potrebbero non essere corrette per alcune distribuzioni di Linux.
Installare il modulo:
modprobe ixgb <parametro>=<valore>
Assegnare un indirizzo IP all'interfaccia inserendo l'istruzione seguente, dove <x> il numero di interfaccia:
ifconfig eth<x> <indirizzo_IP>
Verificare che l'interfaccia funzioni. Inserire la stringa seguente, in cui <indirizzo_IP> l'indirizzo IP di un altro sistema sulla stessa subnet dell'interfaccia da testare:
ping <indirizzo_IP>
FreeBSD
Build e installazione
Questo driver stato sviluppato per l'uso con il kernel FreeBSD, versioni 4.8 e successive.
NOTA: necessario disporre dei sorgenti del kernel installati per poter compilare il modulo del driver.
Nelle istruzioni seguenti, x.x.x la versione del driver come indicato nel nome del file tar del driver.
Spostare il file tar del driver di base in una directory di propria scelta. Ad esempio, usare /home/username/ixgb o
/usr/local/src/ixgb.
Scompattare l'archivio:
tar zxf ixgb-<x.x.x>.tar.gz
In questo modo verr creata una directory ixgb-x.x.x.
Per installare la pagina man:
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
Per caricare il driver in un sistema in esecuzione, eseguire i seguenti passi:
cd ixgb-x.x.x
make
O
cd ixgb-x.x.x/src
make load
Per assegnare un indirizzo IP all'interfaccia, inserire:
ifconfig ixgb<num_interfaccia>
<indirizzo_IP>
Verificare che l'interfaccia funzioni. Immettere l'istruzione seguente, dove <indirizzo_IP> l'indirizzo IP di un altro computer nella stessa sottorete in cui si trova l'interfaccia che si sta sottoponendo a test: ping <indirizzo_IP>
Se si desidera che il driver venga caricato automaticamente all'avvio del sistema:
cd ixgb-x.x.x/src make load cp if_ixgb.ko /modules
Modificare /boot/loader.conf e aggiungere la riga seguente:
if_ixgb_load="YES"
O
compilare il driver nel kernel (vedere il punto 8).
Modificare /etc/rc.conf e creare la voce opportuna ifconfig_ixgb<num_interfaccia>:
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA
Intel Corporation non si assume alcuna responsabilit per eventuali errori o omissioni presenti in questo documento. Inoltre, Intel non si assume alcun impegno di aggiornare le informazioni ivi contenute.
Intel, Itanium e Pentium sono marchi registrati di Intel Corporation negli Stati Uniti e in altri paesi.
*Gli altri marchi e nomi potrebbero essere propriet di terzi.
IMPORTANTE - LEGGERE PRIMA DI COPIARE, INSTALLARE O UTILIZZARE.
Non copiare, installare o usare questo software e l’eventuale materiale ad esso associato (definiti collettivamente con il termine “Software”) che sono forniti in base al presente Contratto di licenza (“Contratto”) senza avere prima letto attentamente i termini e le condizioni che seguono.
Copiando, installando o altrimenti utilizzando il Software, si accetta di essere vincolati dai termini di questo Contratto. Se non si accettano i termini di questo Contratto, non copiare, installare o usare il Software.
LICENZE:
Notare:
La "Licenza di sito" seguente si applica agli amministratori di rete o dei sistemi.
La "Licenza per utente singolo" si applica agli utenti finali.
La sezione “Licenza OEM” si applica ai produttori originali del computer (OEM).
LICENZA DI SITO: possibile copiare il Software sui computer di una azienda per un utilizzo interno all'azienda stessa ed possibile effettuare un numero ragionevole di copie di backup del Software, vincolate da queste condizioni:
Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali (“emulati”) destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare il Software.
Non possibile copiare, modificare, affittare, vendere, distribuire o trasferire alcuna parte del Software tranne quanto previsto nel presente Contratto e il Licenziatario concorda nell'impedire copie non autorizzate del Software.
Non permesso decodificare, decompilare o disassemblare il Software.
Il Software pu comprendere componenti soggetti a termini aggiuntivi a quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.
LICENZA PER UTENTE SINGOLO:
possibile copiare il Software su un singolo computer per uso personale ed possibile effettuare una copia di backup del Software, vincolata da queste condizioni:
Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali (“emulati”) destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare il Software.
Non possibile copiare, modificare, affittare, vendere, distribuire o trasferire alcuna parte del Software tranne quanto previsto nel presente Contratto e il Licenziatario concorda nell'impedire copie non autorizzate del Software.
Non permesso decodificare, decompilare o disassemblare il Software.
Il Software pu comprendere componenti soggetti a termini aggiuntivi a quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.
LICENZA OEM:
possibile riprodurre e distribuire il Software solo come parte integrante e incorporata del prodotto dell'OEM oppure come aggiornamento autonomo di manutenzione del Software per gli utenti esistenti dell'OEM, con l'esclusione degli altri prodotti autonomi o come componente di una distribuzione del Software pi ampia, compresa, ma non limitata a, la distribuzione di un'immagine di installazione o di una macchina virtuale guest, e rispettando queste condizioni:
Il presente Software viene concesso in licenza solo congiuntamente (a) ai componenti Intel e (b) ai dispositivi virtuali (“emulati”) destinati ad apparire come componenti Intel a un sistema operativo guest che viene eseguito nel contesto di una macchina virtuale. La licenza esclude qualsiasi altro utilizzo del Software compreso, ma non limitato a, l'uso con componenti non Intel.
In base ai termini e alle condizioni del presente Contratto, Intel Corporation ("Intel") concede al Licenziatario una licenza non esclusiva, non trasferibile, nell'ambito dei copyright Intel, per utilizzare il Software.
vietato copiare, modificare, noleggiare, vendere, distribuire o trasferire qualsiasi parte del Software, a eccezione di quanto specificato nel presente accordo, e l’utente acconsente a impedire di effettuare copie non autorizzate del Software.
Non permesso decodificare, decompilare o disassemblare il Software.
Il Software pu solo essere distribuito ai clienti conformemente a un contratto di licenza scritto. Tale contratto di licenza pu risultare un contratto “break-the-seal”. Per lo meno tale licenza deve salvaguardare i diritti di propriet di Intel sul Software.
Il Licenziatario non potr distribuire, concedere in sottolicenza o trasferire il Codice sorgente di alcun componente del Software e suoi derivati a terze parti senza il preventivo consenso scritto di Intel.
Il Software pu comprendere componenti soggetti a termini aggiuntivi a quelli qui definiti, che sono specificati nei contratti di licenza ad essi relativi.
LIMITAZIONI DELLA LICENZA.
Il Licenziatario NON potr: (i) utilizzare o copiare il Software tranne per quanto previsto da questo Contratto; (ii) affittare o noleggiare il Software a terze parti; (iii) assegnare questo Contratto o trasferire il Software senza espresso consenso scritto da parte di Intel; (iv) modificare, adattare o tradurre il Software in tutto o in parte tranne per quanto previsto dal presente Contratto; (v) decodificare, decompilare o disassemblare il Software; (vi) cercare di modificare o manomettere la normale funzione di un gestore delle licenze che regola l'utilizzo del Software; (vii) distribuire, concedere in sottolicenza o trasferire il Codice sorgente di alcun componente del Software e suoi derivati a terze parti senza il preventivo consenso scritto di Intel; (viii) permettere, autorizzare, concedere in licenza o sottolicenza a terze parti la visualizzazione o l'uso del Codice sorgente; (ix) modificare o distribuire il Codice sorgente o il Software cosicch parte di esso sia soggeto a una Licenza esclusa (la "Licenza esclusa" richiede, come condizione di utilizzo, la modifica o la distribuzione del codice nonch: (a) la divulgazione o la distribuzione del codice sotto forma di codice sorgente oppure (b) il diritto di terzi di apportarvi delle modifiche); (x) usare o includere il Codice sorgente o il Software in programmi ingannevoli, nocivi o illegali.
NESSUN ALTRO DIRITTO.
Intel non concede al Licenziatario altri diritti o licenze, sia in modo esplicito che implicito, in riferimento alle informazioni proprietarie o di brevetto, ai copyright, ai mask work, ai marchi di fabbrica, ai segreti commerciali e ad altri diritti di propriet intellettuale che sono di propriet o controllati da Intel, eccetto nei casi espressamente previsti dal presente Contratto. Fatto salvo per quanto esplicitamente previsto nel presente documento, al Licenziatario non sono concesse altre licenze o diritti diretti, impliciti, indotti, derivanti da dichiarazioni verbali non corrette o di altra natura. In particolare, Intel non garantisce alcun diritto esplicito o implicito su brevetti, copyright, marchi di fabbrica o altri diritti relativi alla propriet intellettuale.
PROPRIET DEL SOFTWARE E COPYRIGHT. Il Software viene concesso in licenza e non venduto. La titolarit di tutte le copie del Software appartiene a Intel. Il Software protetto da copyright, dalle leggi degli Stati Uniti e di altre nazioni oltre che dalle disposizioni previste dai trattati internazionali. Il Licenziatario non pu rimuovere alcun avviso di copyright dal Software. Il Licenziatario accetta di impedire qualsiasi copia non autorizzata del Software. Intel pu apportare modifiche al Software, o agli elementi che a esso fanno riferimento, in qualsiasi momento e senza preavviso, ma non obbligata a supportare o aggiornare il Software.
TERMINI AGGIUNTIVI PER IL SOFTWARE DI PRE-RELAEASE. Se il Software che si sta installando o utilizzando in base a questo Contratto una release preliminare o etichettato o altrimenti denominato versione "alfa" o "beta" del Software ("Software di pre-release"), si applicano i seguenti termini. Nel caso in cui una disposizione di questa Sezione sia in conflitto con altri termini o condizioni di questo Contratto in relazione al Software di pre-release, questa Sezione avr la priorit su tali termini e condizioni, ma solo nei limiti necessari per risolvere il conflitto. Il Licenziatario riconosce e accetta che il Software un Software di pre-release, non rappresenta il Software finale di Intel e potrebbe contenere errori e altri problemi che potrebbero causare la perdita di dati, il malfunzionamento del sistema o altri errori. Il Software di pre-release fornito "come tale" e Intel declina qualsiasi garanzia o responsabilit nei confronti del Licenziatario per gli eventuali danni causati dall'uso del Software di pre-release. Il Licenziatario riconosce che Intel non ha promesso il futuro rilascio del Software di pre-release, non ha alcun obbligo espresso o implicito di rilasciare al Licenziatario il Software di pre-release e che Intel potrebbe introdurre un Software non compatibile con il Software di pre-release. Il Licenziatario riconosce che tutte le attivit di ricerca o sviluppo che esegue, relative al Software di pre-release o a qualsiasi prodotto che fa uso o associato con il Software pre-release, sono eseguite a proprio rischio. Se Intel ha fornito al Licenziatario il Software di pre-release conformemente a un contratto scritto separato, l'uso del Software di pre-release regolamentato anche da tale contratto.
GARANZIA LIMITATA SUI SUPPORTI. Se il Software stato fornito da Intel su un supporto fisico, Intel garantisce che il supporto privo di difetti intrinseci e dei materiali per un periodo di novanta giorni dalla sua consegna da parte di Intel. Nel caso in cui siano rilevati difetti, restituire il supporto a Intel per ottenerne la sostituzione o per ricevere il Software in altro modo stabilito a discrezione di Intel.
ESCLUSIONE DI ALTRE GARANZIE. SALVO QUANTO QUI INDICATO, IL SOFTWARE VIENE FORNITO “COME TALE” SENZA GARANZIE ESPLICITE O IMPLICITE DI ALCUN TIPO, COMPRESE LE GARANZIE DI COMMERCIABILIT, DI NON VIOLAZIONE DI DIRITTI O DI IDONEIT PER UN USO SPECIFICO. Intel non garantisce n si assume alcuna responsabilit riguardo l'accuratezza o la completezza delle informazioni, del testo, delle immagini, dei collegamenti o di altri elementi contenuti nel Software.
LIMITAZIONE DI RESPONSABILIT. IN NESSUN CASO INTEL O I SUOI FORNITORI SARANNO RITENUTI RESPONSABILI PER QUALSIVOGLIA DANNO (INCLUSI, SENZA ALCUNA LIMITAZIONE, LA PERDITA DI PROFITTI, L'INTERRUZIONE DELL'ATTIVIT COMMERCIALE O LA PERDITA DI INFORMAZIONI) CHE POTREBBE DERIVARE DALL'UTILIZZO O DALL'INCAPACIT DI UTILIZZARE IL SOFTWARE, ANCHE SE INTEL STATA AVVERTITA DELLA POSSIBILIT DI TALI DANNI. ALCUNE GIURISDIZIONI PROIBISCONO L'ESCLUSIONE O LA LIMITAZIONE DELLA RESPONSABILIT RELATIVAMENTE ALLE GARANZIE IMPLICITE O AI DANNI CONSEQUENZIALI E ACCIDENTALI; DI CONSEGUENZA, LA SUDDETTA LIMITAZIONE POTREBBE NON ESSERE APPLICABILE A TUTTI I CASI. POTREBBERO INOLTRE ESSERE PREVISTI ALTRI DIRITTI LEGALI CHE VARIANO DA GIURISDIZIONE A GIURISDIZIONE. Nel caso in cui il Licenziatario usi il Software con un dispositivo virtuale (“emulato”) destinato ad apparire come un componente Intel, il Licenziatario riconosce che Intel non n l'autore n il creatore del dispositivo virtuale (“emulato”). Il Licenziatario riconosce e accetta che Intel non fornisce alcuna garanzia relativamente alla correttezza del funzionamento del Software quando usato con un dispositivo virtuale (“emulato”), che Intel non ha progettato il Software per il funzionamento con il dispositivo virtuale (“emulato”) e che il Software potrebbe non funzionare correttamente con il dispositivo virtuale (“emulato”). Il Licenziatario accetta di assumersi il rischio che il Software potrebbe non funzionare correttamente con il dispositivo virtuale (“emulato”). Il Licenziatario accetta di rimborsare e manlevare Intel e i suoi funzionari, le sue societ collegate o controllate, di qualsiasi rivendicazione, costo, danno, spesa, spesa legale derivanti, direttamente o indirettamente, da qualsiasi rivendicazione di responsabilit del prodotto, lesione personale o decesso associati all'uso del Software con il dispositivo virtuale (“emulato”), anche se tale rivendicazione sostiene che Intel abbia agito in modo negligente nella progettazione o costruzione del Software.
USO NON AUTORIZZATO.IL SOFTWARE NON PROGETTATO, PREVISTO O AUTORIZZATO PER ESSERE UTILIZZATO IN QUALSIASI SISTEMA O APPLICAZIONE IN CUI IL FALLIMENTO DEL SOFTWARE POTREBBE CREARE UNA SITUAZIONE DI LESIONE PERSONALE O DECESSO (AD ESEMPIO, SISTEMI MEDICALI, SALVAVITA O DI SOPRAVVIVENZA).
Se il Licenziatario utilizza il Software per qualsiasi uso non previsto o non autorizzato, il Licenziatario dovr rimborsare e manlevare Intel e i suoi funzionari, dipendenti, direttori, filiali, rappresentanti, affiliate e agenti nei confronti di qualsiasi rivendicazione, costo, danno, spesa, spesa legale e spese di vario tipo derivanti, direttamente o indirettamente, da qualsiasi rivendicazione di responsabilit del prodotto, lesione personale o decesso associati a tale uso non previsto o non autorizzato, anche se tale rivendicazione ritiene Intel negligente per quanto riguarda la progettazione o la costruzione della parte.
RESCISSIONE DI QUESTO CONTRATTO.
Intel pu rescindere il presente Contratto in qualsiasi momento, nel caso l'utente ne violi i termini. In seguito alla rescissione del contratto, il Licenziatario deve immediatamente distruggere tutte le copie del Software o restituirle a Intel.
LEGGI APPLICABILI.
Le rivendicazioni derivanti dal, o relative al, presente Contratto saranno regolamentate dalle leggi vigenti nello Stato della California, senza considerazione dei principi di conflitto della legge. Il Licenziatario accetta che la Convenzione delle Nazioni Unite sui Contratti per la vendita di beni non si applica al presente Contratto. Il Licenziatario non pu esportare il Software trasgredendo le leggi e i regolamenti sulle esportazioni attualmente in vigore. Intel non vincolata da alcun altro contratto che non sia per iscritto e firmato da un rappresentante autorizzato di Intel.
DIRITTI LIMITATI DEL GOVERNO.
Il Software e la documentazione forniti sono stati sviluppati privatamente e hanno “DIRITTI LIMITATI”. L'uso, la duplicazione o la divulgazione da parte del Governo sono soggetti alle limitazioni delle norme FAR 52.227-14 e DFAR 252.227-7013 et seq. o successive. L’uso di questo prodotto da parte del Governo equivale a riconoscere i diritti di propriet di Intel sul Software. Il contraente o il produttore Intel.
LINGUA; TRADUZIONI.
Qualora la versione in lingua inglese del presente Contratto venisse fornita insieme a una versione tradotta in un'altra lingua, a titolo di riferimento, far fede unicamente la versione in lingua inglese.
Intel garantisce al proprietario originario che la scheda di rete contenuta nella confezione non contiene difetti n dei materiali n di lavorazione. La presente garanzia non copre i danni del prodotto causati dall'installazione del prodotto stesso.
LA SUDDETTA GARANZIA SOSTITUISCE QUALSIASI ALTRA GARANZIA, ESPRESSA, IMPLICITA O OBBLIGATORIA, COMPRESA, MA NON LIMITATA A, QUALSIASI GARANZIA DI RISPETTO DELLA PROPRIET INTELLETTUALE, DI COMMERCIABILIT, DI IDONEIT AD UNO SCOPO PARTICOLARE, O QUALSIASI GARANZIA DERIVATA DA PROPOSTE, SPECIFICHE, CAMPIONI.
La presente garanzia non copre la sostituzione di schede di rete danneggiate in caso di abuso, incidente, uso improprio, negligenza, alterazione, riparazione, calamit, installazione errata o collaudo errato. Se la scheda di rete viene trovata altrimenti difettosa, Intel, a propria discrezione, la sostituir o riparer gratuitamente, eccetto che nei casi illustrati di seguito, purch la scheda di rete sia consegnata unitamente al codice di autorizzazione per la restituzione del materiale (RMA) (vedere pi avanti) all'azienda presso cui la si acquistata o a Intel, con copia della ricevuta di acquisto (se la scheda non stata registrata) e una descrizione del difetto riscontrato. In caso di spedizione del prodotto, l'utente si assume il rischio di danneggiamento o perdita durante il trasporto. Occorre usare il contenitore originale (o uno equivalente) e pagare le spese di spedizione.
Intel pu sostituire o riparare la scheda di rete con un prodotto o parti nuove o rigenerate, nel qual caso la scheda di rete o le parti restituite diventano propriet di Intel. Le schede di rete riparate o sostituite saranno restituite, a discrezione di Intel, con un livello di revisione pari o superiore al prodotto originale. Intel si riserva il diritto di sostituire la scheda di rete difettosa con un altro modello equivalente.
Restituzione di un prodotto difettoso
Dall'America del Nord
Prima di restituire una scheda di rete, necessario contattare il Servizio di assistenza clienti al numero +1 916-377-7000 e richiedere un codice di restituzione prodotto (RMA).
Se il Servizio di assistenza clienti determina che la scheda di rete effettivamente difettosa, chieder al reparto responsabile della restituzione dei prodotti di emettere un codice RMA da apporre sulla confezione del prodotto da restituire. La Intel non accetter prodotti sprovvisti del codice RMA sulla confezione.
Dagli altri paesi
Restituire la scheda di rete al rivenditore presso il quale stata acquistata per richiedere il rimborso o la sostituzione.
Garanzia di rimborso del prezzo pagato per la scheda di rete (valida solo per i clienti del Nord America)
Intel desidera che i suoi clienti siano pienamente soddisfatti della scheda di rete Intel che hanno acquistato. Pertanto, permette loro di restituire la scheda acquistata presso il rivenditore e di richiedere il rimborso dell'intero prezzo pagato entro novanta (90) giorni dalla data di acquisto. I rivenditori e i distributori che accettano i prodotti restituiti e rimborsano i clienti possono a loro volta restituire le schede di rete Intel al fornitore dal quale le hanno acquistate. Intel garantisce la possibilit di restituire il prodotto e di richiedere il rimborso dell'intero prezzo pagato anche ai clienti che hanno acquistato le loro schede direttamente dalla Intel.
Limitazione della responsabilit e rimedi
L'UNICA RESPONSABILIT DI INTEL DEFINITA DALLA PRESENTE GARANZIA LIMITATA AI DANNI DIRETTI E MISURABILI IN MODO OGGETTIVO. IN NESSUN CASO INTEL SAR CONSIDERATA RESPONSABILE PER DANNI INDIRETTI O IPOTETICI (INCLUSI, MA NON LIMITATI A, I DANNI PRECEDENTI, DERIVATI, INCIDENTALI E SPECIALI) INCLUSI, MA NON LIMITATI A, LA VIOLAZIONE DI PROPRIET INTELLETTUALE, I COSTI DI RIACQUISTO, LA PERDITA D'USO, L'INTERRUZIONE DELLE ATTIVIT COMMERCIALI, LA PERDITA DI AVVIAMENTO, LA PERDITA DI PROFITTI, INDIPENDENTEMENTE DAL FATTO CHE TALI DANNI SI VERIFICHINO SOTTO CONTRATTO, DA NEGLIGENZA, PER TORTO O SIANO COPERTI DA GARANZIA, E INDIPENDENTEMENTE DA EVENTUALI NOTIFICHE FATTE PERVENIRE ANTICIPATAMENTE A INTEL RELATIVAMENTE ALLA POSSIBILIT DEL VERIFICARSI DI TALI DANNI. NONOSTANTE QUANTO SOPRA RIPORTATO, LA RESPONSABILIT TOTALE DI INTEL PER TUTTI I RECLAMI REGOLATI IN BASE AL PRESENTE CONTRATTO NON PU SUPERARE IL PREZZO PAGATO PER IL PRODOTTO. TALI LIMITAZIONI DELLE RESPONSABILIT POTENZIALI HANNO RAPPRESENTATO UN ELEMENTO ESSENZIALE PER STABILIRE IL PREZZO DEL PRODOTTO. LA INTEL NON SI ASSUME N AUTORIZZA ALCUNO AD ASSUMERSI IN SUA VECE QUALUNQUE ALTRA RESPONSABILIT.
Alcuni stati non consentono l'esclusione o la limitazione dei danni incidentali o consequenziali, pertanto le suddette limitazioni potrebbero non essere applicabili all'utente.
Applicazioni di controllo critiche: la Intel disconosce specificamente la responsabilit per l'uso del prodotto hardware con applicazioni di comando fondamentali (compresi, solo a titolo di esempio, sistemi di comando per l'assistenza sanitaria, sistemi di comando per energia nucleare, o sistemi di comando per il traffico aereo o terrestre) da parte del Licenziatario o dei Sublicenziatari, e tale utilizzo totalmente a rischio e pericolo dell'utente. Il licenziatario concorda di sostenere, risarcire e ritenere Intel non responsabile di qualsivoglia reclamo derivato dall'uso del prodotto hardware in tali applicazioni da parte del Licenziatario o dei
Sublicenziatari.
Software: il software fornito con la scheda di rete non coperto dalla garanzia hardware descritta in precedenza. Per informazioni sulle eventuali garanzie software, consultare il Contratto di licenza del software fornito con la scheda di rete.
Nota: questa garanzia non si applica agli utenti soggetti alla legge sul consumo australiana (Australian Consumer Law). Visitare la pagina della Garanzia hardware limitata perpetua australiana per visualizzare la garanzia limitata applicabile ai consumatori australiani.
DOCS/QUICK/PTB 0000755 0000000 0000000 00000000000 12233424130 007710 5 ustar DOCS/QUICK/PTB/10qi_ptb.htm 0000755 0000000 0000000 00000027406 12142406770 012145 0 ustar
Guia de instalao rpida dos adaptadores de rede Intel(R)
Instalao do adaptador de rede Intel®
Instale o adaptador para servidor Intel® Ethernet 10 Gigabit
Instale o adaptador
Desligue o computador e desconecte o cabo de alimentao. Se estiver fazendo uma instalao "hot plug", consulte primeiro a documentao do servidor.
Remova a tampa do computador e a tampa do slot correspondente ao seu adaptador. Voc pode usar um slot mais comprido que o conector de seu adaptador, mas no tente instalar o adaptador em um slot mais curto que o conector PCI Express.
Insira firmemente o adaptador no slot e prenda a braadeira.
Recoloque a tampa do computador. Ligue o fio de eletricidade.
Instale uma placa mezanino
Desligue o computador e desconecte o cabo de alimentao.
Remova a tampa do computador.
Alinhe o conector PCIe da placa mezanino com o conector e os quatro pinos plsticos da motherboard.
Pressione o adaptador at que ele fique totalmente inserido no conector da motherboard e se encaixe nos quatro pinos.
Recoloque a tampa do computador. Ligue o fio de eletricidade.
Conectar o cabo de rede
Adaptadores de cobre Intel® Ethernet de 10 Gigabits Use cabos Ethernet categoria 6, categoria 6a ou categoria 7.
Adaptador para servidor Intel® Ethernet de 10 Gigabits com mdulos pticos plugveis SFP+: Instale o mdulo e conecte o cabo de acordo com as instrues do fabricante
Adaptadores de fibra Intel® Ethernet 10 Gigabit com conector SC: Remova e guarde a tampa do conector de fibra tica. Insira um conector de fibra ptica SC nas portas TX/RX da braadeira do adaptador.
Adaptadores de fibra Intel® Ethernet 10 Gigabit com conector LC: Remova e guarde a tampa do conector de fibra tica. Insira um conector LC no adaptador. Podem ser usados cabos de converso para outros tipos de conectores (como, por exemplo, SC) se o cabeamento corresponder s especificaes ticas do adaptador, inclusive as limitaes de comprimento.
Adaptadores CX4 Intel® Ethernet de 10 Gigabits Os cabos fsicos precisam atender norma IEEE 802.3ak, clusula 54. O conector de cabo necessrio um receptculo do tipo trava MDI, como definido pelo IEC 61076-3-113.
Ligue o computador e siga as instrues de instalao do driver conforme abaixo.
Instale os drivers e o software do Intel® PROSet
Sistemas operacionais Microsoft* Windows*
NOTAS:
instalar os drivers requer direitos de administrador no sistema operacional.
Consulte a pgina Requisitos do sistema no Guia do adaptador Intel 10GbE, para conhecer os sistemas operacionais suportados.
O adaptador detectado como novo hardware quando o Windows inicia. Para instalar o driver correto:
O adaptador detectado e o Windows instala um driver residente Windows ou inicia o assistente Novo hardware encontrado
.
Se o assistente iniciar, siga os avisos para instalar o driver a partir do CD contido neste pacote.
Se for instalado um driver residente do Windows (o assistente no aparece), atualize o driver inserindo o CD da Intel e clicando no boto Instalar drivers e software quando aparecer a janela de execuo automtica de Conexes de rede Intel
.
Linux
Para criar um pacote binrio RPM* desse driver, execute 'rpmbuild -tb <filename.tar.gz>'. Substitua <filename.tar.gz> com o nome do arquivo especfico do driver.
NOTA: Para o build funcionar corretamente, o kernel em execuo PRECISA corresponder verso e configurao da origem de kernel instalada. Se voc tiver recompilado o kernel, reinicialize agora o sistema.
A funcionalidade RPM foi testada somente nas distribuies do Red Hat.
Mova o arquivo tar do driver bsico para o diretrio de sua escolha. Por exemplo, use '/home/username/ixgb' ou '/usr/local/src/ixgb'.
Extraia (Untar/unzip) o arquivo digitando a seguinte opo abaixo, onde <x.x.x> representa o nmero da verso para o tar do driver:
tar zxf ixgb-<x.x.x>.tar.gz
Mude para o diretrio src, onde <x.x.x> representa o nmero da verso para o tar do driver:
Os locais da instalao listados acima so os locais padro. Eles no podem corrigir certas distribuies de Linux.
Instale o mdulo:
modprobe ixgb <parameter>=<value>
Atribua um endereo IP interface, digitando a seguinte informao, onde <x> representa o nmero da interface:
ifconfig eth<x> <IP_address>
Verifique se a interface funciona. Digite o seguinte, onde <IP_address> o endereo IP de uma outra mquina na mesma sub-rede da interface que est sendo testada:
ping <IP_address>
FreeBSD
Criao e instalao
Esse driver foi desenvolvido para ser usado com o kernel FreeBSD, verses 4.8 e posteriores.
NOTA: Voc deve ter as fontes do kernel instaladas a fim de compilar o mdulo do driver.
Nas instrues abaixo, x.x.x a verso do driver que est indicada no nome do arquivo .tar do driver.
Mova o arquivo tar do driver bsico para o diretrio de sua escolha. Por exemplo, use /home/username/ixgb ou
/usr/local/src/ixgb.
Descompacte o arquivo:
tar xfz ixgb-x.x.x.tar.gz
Essa ao criar um diretrio ixgb-x.x.x.
Para instalar a pgina man:
cd ixgb-x.x.x
gzip -c ixgb.4 > /usr/share/man/man4/ixgb.4.gz
Para carregar o driver em um sistema em funcionamento, execute os passos a seguir:
cd ixgb-x.x.x
make
OU
cd ixgb-<x.x.x>/src/
make load
Digite o seguinte para atribuir um endereo IP interface:
ifconfig ixgb<interface_num>
<endereo_IP>
Verifique se a interface funciona. Digite o seguinte, onde <IP_address> o endereo IP de uma outra mquina na mesma sub-rede da interface que est sendo testada: ping <IP_address>
Se quiser que o driver seja carregado automaticamente quando o sistema for inicializado:
cd ixgb-<x.x.x>/src/ make load cp if_ixgb.ko /modules
Edite o /boot/loader.conf e adicione a seguinte linha:
if_ixgb_load="YES"
OU
compile o driver no kernel (veja o item 8).
Edite o /etc/rc.conf e crie a entrada ifconfig_ixgb<interface_num> adequada:
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA
A Intel Corporation no assume nenhuma responsabilidade por erros ou omisses neste documento. A Intel tambm no assume nenhum compromisso de atualizar as informaes aqui contidas.
Intel, Itanium e Pentium so marcas comerciais da Intel Corporation nos Estados Unidos e em outros pases.
* Outras marcas e nomes podem ser propriedade de outras empresas.
IMPORTANTE LEIA ANTES DE COPIAR, INSTALAR OU USAR.
No copie, no instale nem use este software ou qualquer material associado (coletivamente o “Software”) fornecido sob este contrato de licena (“Contrato”) antes de ler cuidadosamente os termos e condies a seguir.
Ao copiar, instalar ou usar o Software, voc indica que concorda em se submeter aos termos deste Contrato. Se no concordar com os termos deste Contrato, no copie, no instale nem use o Software.
LICENAS:
Note o seguinte:
A “Licena de Site” a seguir aplica-se aos administradores de rede ou de sistema.
A “Licena para usurio nico” se aplica aos usurios finais.
A "Licena para fabricantes de equipamentos originais (OEM)" se aplica a tais fabricantes.
LICENA DE SITE. Voc poder copiar o Software nos computadores da sua empresa, para uso na sua empresa, e poder fazer um nmero razovel de cpias de backup do Software, de acordo com as seguintes condies:
Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar o Software.
Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
O Software pode conter partes oferecidas sob termos diferentes dos termos do presente Contrato, descritos em um contrato de licena que acompanha tais partes.
LICENA PARA USURIO NICO.
Voc poder fazer uma cpia do Software em um nico computador para o seu uso pessoal, e poder criar uma cpia de backup do Software, de acordo com as seguintes condies:
Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar o Software.
Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
O Software pode conter partes oferecidas sob termos diferentes dos termos do presente Contrato, descritos em um contrato de licena que acompanha tais partes.
LICENA PARA FABRICANTES DE EQUIPAMENTOS ORIGINAIS (OEM):
Voc pode reproduzir e distribuir o Software apenas como parte integrante ou na forma incorporada ao seu produto, como atualizao de manuteno do Software para usurios existentes dos seus produtos, excluindo-se quaisquer outros produtos individuais, ou como uma distribuio maior do Software, incluindo, mas no se limitando a, distribuio de uma imagem de instalao ou uma imagem de mquina virtual convidada (Guest), com estas condies:
Este Software licenciado para uso apenas em conjunto com (a) componentes fsicos Intel e (b) dispositivos virtuais (“emulados”) que aparecem como produtos Intel para sistemas operacionais Guests (convidados) que rodam em mquinas virtuais. Nenhum outro uso do Software, inclusive, mas sem se limitar a, o uso com produtos no Intel, licenciado sob este contrato.
Em conformidade com todos os termos e condies deste Contrato, a Intel Corporation ("Intel") concede a voc uma licena no exclusive e no transfervel de copyright para usar o Software.
Voc no pode copiar, modificar, alugar, vender, distribuir ou transferir qualquer parte do Software, exceto na forma expressa neste Contrato, e voc concorda em impedir a cpia no autorizada do Software.
Voc no pode fazer engenharia reversa, descompilao ou desmontagem do Software.
A distribuio do Software aos seus clientes s pode ser feita com um contrato de licena em forma escrita. Este contrato de licena pode ser do tipo "violao de lacre". No mnimo, tal contrato deve salvaguardar os direitos de propriedade da Intel sobre o Software.
Voc no pode distribuir, sublicenciar ou transferir o cdigo fonte de qualquer componente do Software, e de seus derivados, para terceiros sem a sem a permisso expressa e por escrito da Intel.
O Software pode conter partes oferecidas sob termos diferentes dos termos do presente Contrato, descritos em um contrato de licena que acompanha tais partes.
RESTRIES DA LICENA.
Voc NO pode: (i) usar ou copiar o Software, exceto na forma expressa neste Contrato; (ii) alugar ou arrendar o Software para terceiros; (iii) ceder este Contrato ou transferir o Software sem o consentimento expresso e por escrito da Intel; (iv) modificar, adaptar ou traduzir o Software, no todo ou em parte, exceto nas formas estabelecidas neste Contrato; (v) fazer engenharia reversa, descompilao ou desmontagem do Software; (vi) tentar modificar ou adulterar o funcionamento normal do gerenciador de licenas que regulamenta o uso do Software; (vii) distribuir, sublicenciar ou transferir o cdigo fonte de qualquer componente do Software, ou de seus derivados, para terceiros sem o consentimento expresso e por escrito da Intel; (viii) permitir, autorizar, licenciar ou sublicenciar terceiros a ver ou usar o cdigo fonte; (ix) modificar ou distribuir o cdigo fonte ou o Software de forma que parte ou partes dele fiquem sujeitas a uma Licena de Excluso. ("Licena de Excluso" a licena que exige, como condio de uso, uma modificao ou uma distribuio em que: (a) o cdigo seja revelado ou distribudo sob a forma de cdigo fonte ou (b) outros tenham o direito de modific-lo.); (x) usar ou inserir o cdigo fonte ou o Software em programas fraudulentos, maliciosos ou ilegais.
NENHUM OUTRO DIREITO.
A Intel no outorga a voc direitos nem licenas, implcitos ou explcitos, em relao a informaes de propriedade ou patentes, direitos autorais, trabalho de mscara, segredo comercial ou outro direito de propriedade intelectual de propriedade ou de controle da Intel, exceto nas formas expressamente estabelecidas neste Contrato. Exceto nas formas expressamente estabelecidas neste Contrato, no concedida a voc nenhuma licena ou direito, direto ou implcito, por induo, embargo ou outra forma. Especificamente, a Intel no concede nenhum direito expresso ou implcito a voc em relao a patentes, direitos autorais, marcas comerciais ou outros direitos de propriedade intelectual da Intel.
PROPRIEDADE DO SOFTWARE E DIREITOS AUTORAIS. O Software licenciado, no vendido. O ttulo de todas as cpias do Software permanece com a Intel. O Software contm direitos autorais e est protegido por leis dos Estados Unidos e de outros pases e por provises de tratados internacionais. Voc no pode remover nenhum aviso de direitos autorais do Software. Voc concorda em impedir qualquer cpia no autorizada do Software. A Intel pode fazer alteraes ao Software ou aos itens aqui citados a qualquer momento sem aviso prvio, mas no est obrigada a oferecer suporte ou a atualizar o Software.
TERMOS ADICIONAIS PARA SOFTWARE DE PRE-LANAMENTO.Se o Software que voc est instalando ou usando sob os termos deste Contrato for uma verso de pre-lanamento comercial, ou for uma verso “alfa“ ou “beta“ ("Software de pre-lanamento"), ento os termos a seguir se aplicaro. Se alguma clusula desta Seo entrar em conflito com qualquer termo ou condio deste Contrato em relao a Software de pre-lanamento, esta Seo ter precedncia sobre o(s) outro(s) termo(s) e condio(es), mas apenas at o ponto necessrio para resolver o conflito. Voc entende e reconhece que o Software um Software de pre-lanamento, no representa o Software final da Intel e pode conter erros e outros problemas que podem causar perda de dados, falhas de sistema ou outras falhas. O Software de pre-lanamento fornecido a voc "no estado em que se encontra" e a Intel se exime de fornecer garantias e no se responsabiliza por danos que possam ocorrer como consequncia do uso deste Software de pre-lanamento. Voc reconhece que a Intel no prometeu que o Software de pre-lanamento ser lanado no futuro, que a Intel no tem obrigao explcita ou implcita de lanar o Software de pre-lanamento e que a Intel pode no lanar nenhum Software que seja compatvel com o Software de pre-lanamento. Voc reconhece que a totalidade da pesquisa e desenvolvimento que voc fizer e que for relacionada ao Software de pre-lanamento ou a qualquer produto que use ou que esteja associado ao Software de pre-lanamento feita por sua conta e risco. Se a Intel forneceu a voc o Software de pre-lanamento sob um contrato escrito separado, o uso que voc fizer deste Software de pre-lanamento regido tambm por tal contrato.
GARANTIA LIMITADA DA MDIA. Se o Software foi entregue pela Intel na forma de mdia fsica, a Intel garante esta mdia contra defeitos fsicos, por um perodo de noventa dias aps a entrega. Se for detectado algum defeito fsico, devolva a mdia Intel para substituio ou remessa alternativa do Software, a critrio da Intel.
EXCLUSO DE OUTRAS GARANTIAS. COM EXCEO DO ACIMA DISPOSTO, O SOFTWARE FORNECIDO "NO ESTADO EM QUE SE ENCONTRA", SEM NENHUMA GARANTIA EXPRESSA OU IMPLCITA DE QUALQUER TIPO, INCLUINDO AS GARANTIAS DE NEGOCIABILIDADE, NO INFRAO OU ADEQUAO A UMA FINALIDADE ESPECFICA. A Intel no oferece garantia nem assume responsabilidade pela exatido ou pela integridade de quaisquer informaes, textos, grficos, links ou outros itens contidos no Software.
LIMITAO DE RESPONSABILIDADE. SOB NENHUMA CIRCUNSTNCIA A INTEL OU SEUS FORNECEDORES SERO RESPONSABILIZADOS POR QUALQUER DANO (INCLUSIVE, MAS NO SE LIMITANDO A, PERDA DE LUCROS, INTERRUPO DE NEGCIOS OU PERDA DE INFORMAES) PROVENIENTE DO USO OU DA INABILIDADE DE USO DO SOFTWARE, MESMO QUE A INTEL TENHA SIDO AVISADA DA POSSIBILIDADE DE TAIS DANOS. ALGUMAS JURISDIES PROBEM A EXCLUSO OU LIMITAO DA RESPONSABILIDADE PARA GARANTIAS IMPLCITAS OU PARA DANOS CONSEQENCIAIS OU INCIDENTAIS; PORTANTO, A LIMITAO ACIMA PODE NO SE APLICAR A VOC. VOC PODE TAMBM TER OUTROS DIREITOS LEGAIS QUE VARIAM DE JURISDIO PARA JURISDIO. Se voc usar o Software em conjunto com um dispositivo virtual (“emulado”) e destinado a aparecer como um produto Intel, voc reconhece que a Intel no a autora nem a criadora do dispositivo virtual (“emulado”). Voc entende e reconhece que a Intel no faz nenhuma afirmao sobre a correta operao do Software quando ele usado em um dispositivo virtual (“emulado”), que a Intel no projetou o Software para operar com o dispositivo virtual (“emulado”), e que o Software pode no ser capaz de funcionar corretamente com o dispositivo virtual (“emulado”). Voc concorda em assumir o risco de que o Software possa no funcionar corretamente em conjunto com o dispositivo virtual (“emulado”). Voc concorda em indenizar a Intel e manter a Intel e seus funcionrios, suas subsidirias e suas afiliadas isentos de responsabilidade contra todos os processos judiciais, custos, danos e despesas, alm de custos advocatcios razoveis, resultantes, direta ou indiretamente, de qualquer reclamao de obrigaes do produto, leses corporais ou morte associadas ao uso do Software em conjunto com o dispositivo virtual (“emulado”), mesmo sob a alegao de que a Intel foi negligente em relao ao design ou fabricao do Software.
USO NO AUTORIZADO.O SOFTWARE NO FOI PROJETADO NEM DESTINADO OU AUTORIZADO PARA USO EM QUALQUER TIPO DE SISTEMA OU APLICAO EM QUE A FALHA DO SOFTWARE PODE CAUSAR LESES CORPORAIS OU MORTE (POR EXEMPLO, SISTEMAS MDICOS, SISTEMAS DE SALVAMENTO OU DE MANUTENO DA VIDA).
Se usar o Software em qualquer destas aplicaes no autorizadas, voc ir indenizar a Intel e manter a Intel e seus funcionrios, suas subsidirias e suas afiliadas isentos de responsabilidade contra todos os processos judiciais, custos, danos e despesas, alm de custos advocatcios razoveis, resultantes, direta ou indiretamente, de qualquer reclamao de obrigaes do produto, leses corporais ou morte associadas a tal uso no autorizado, mesmo sob a alegao de que a Intel foi negligente em relao ao design ou fabricao do Software.
RESCISO DESSE CONTRATO.
A Intel pode rescindir este Contrato a qualquer momento no caso de violao dos seus termos. Com a resciso, voc destruir imediatamente o Software ou devolver todas as suas cpias Intel.
LEIS QUE SE APLICAM.
As aes judiciais oriundas deste Contrato sero governadas pelas leis do Estado da Califrnia, EUA, sem considerar conflitos com outras leis. Voc concorda que os termos da Conveno das Naes Unidas sobre Contratos de Venda de Bens no se aplica a este Contrato. Voc no poder exportar o Software em violao s leis e regulamentos aplicveis exportao. A Intel no est obrigada ao cumprimento de quaisquer outros contratos, a menos que se apresentem por escrito e estejam assinados por um representante autorizado da Intel.
DIREITOS RESTRITOS DO GOVERNO.
Este Software e esta documentao foram desenvolvidos com capital privado e so fornecidos com “DIREITOS RESTRITOS”. O uso, a duplicao ou a divulgao pelo Governo esto sujeitos s restries estabelecidas em FAR 52,227-14 e DFARS 252,227-7013 et seq. ou s suas clusulas substitutas ou s leis sucessoras. O uso deste produto pelo governo indica o reconhecimento dos direitos de propriedade da Intel sobre o Software. A Intel o fabricante ou o contratante.
IDIOMA; TRADUES.
Se a verso no idioma ingls deste Contrato for acompanhada por qualquer outra verso traduzida para qualquer outro idioma, essa verso traduzida ser fornecida somente a ttulo de convenincia e a verso gerada no idioma ingls ter prioridade de controle legal.
Mais recente modificao feita em: 02 de abril de 2012 s 22h56 Reviso
A Intel garante ao propriedade original que o produto adaptador entregue neste pacote no contm defeitos fsicos nem de fabricao. Esta garantia no cobre o produto adaptador, se ele for danificado no processo de instalao ou por uso inadequado.
A GARANTIA ACIMA SUBSTITUI QUALQUER OUTRA GARANTIA, QUER SEJA EXPRESSA, IMPLCITA OU ESTATUTRIA, INCLUSIVE, MAS NO LIMITADA A, QUALQUER GARANTIA DE NO-VIOLAO DE PROPRIEDADE INTELECTUAL, COMERCIALIZAO, ADEQUAO A UM PROPSITO ESPECFICO DECORRENTE DE QUALQUER PROPOSTA, ESPECIFICAO OU AMOSTRA.
Esta garantia no cobre a substituio de produtos adaptador danificados por uso indevido, acidente, uso incorreto, negligncia, alterao, reparo, desastre, instalao incorreta ou teste inadequado. Se o produto adaptador for considerado defeituoso, a Intel, se assim decidir, substituir ou consertar o produto de hardware gratuitamente, exceto conforme especificado a seguir, ou reembolsar o valor de aquisio, desde que o produto adaptador seja entregue com um nmero RMA (Return Material Authorization Autorizao de Material Devolvido ver abaixo), juntamente com um comprovante de compra (se no estiver registrado), ao negociante onde o produto foi comprado ou Intel, com uma explicao do problema em questo. Se voc enviar o produto adaptador, assumir o risco de dados ou perda durante o transporte. Use a embalagem original (ou equivalente) e pague o frete.
A Intel pode substituir ou consertar o produto adaptador com peas novas ou recondicionadas, e o produto adaptador ou a parte substituda pela Intel se tornar propriedade da Intel. Os produtos adaptador consertados ou substitudos sero devolvidos a voc, com o mesmo nvel de reviso recebido ou nvel superior, a critrio da Intel. A Intel se reserva o direito de substituir os produtos adaptador fora de linha por um produto adaptador de gerao atual equivalente.
Devoluo de um produto com defeito
Da Amrica do Norte:
Antes de devolver qualquer produto adaptador, entre em contato com o Suporte ao Cliente Intel e obtenha um Nmero RMA (Return Material Authorization Autorizao de Material Devolvido), ligando para +1 916-377-7000.
Se o Grupo do Suporte ao Cliente confirmar que o produto adaptador est com defeito, o departamento de RMA emitir um Nmero RMA para ser colocado na embalagem externa do produto adaptador. A Intel no pode aceitar qualquer produto sem um Nmero RMA na embalagem.
Todos os outros locais:
Devolva o produto adaptador ao local de compra para obter um reembolso ou uma troca.
Garantia de Devoluo do Dinheiro Pago pelo Adaptador Intel (somente na Amrica do Norte)
A Intel quer v-lo totalmente satisfeito com o adaptador Intel que voc comprou. A qualquer momento dentro do prazo de noventa (90) dias a partir da data de compra, voc pode devolver o adaptador Intel ao local original de compra, para obter de seu fornecedor o reembolso do valor de aquisio. Os integradores e distribuidores, respectivamente, que aceitarem devolues e reembolsarem seus clientes, podem devolver os adaptadores Intel ao local original de compra. A Intel garante que aceitar as devolues coberta por esta diretiva, e reembolsar o valor de aquisio inicial aos clientes que comprarem diretamente na Intel.
Limitao de Responsabilidade e Correes
A NICA RESPONSABILIDADE DA INTEL AQUI PREVISTA ESTAR LIMITADA AOS DANOS DIRETA E OBJETIVAMENTE AVALIVEIS. EM HIPTESE ALGUMA, A INTEL SE RESPONSABILIZAR POR QUAISQUER DANOS INDIRETOS OU ESPECULATIVOS (INCLUINDO, MAS NO LIMITADO A, OS DANOS CITADOS ANTERIORMENTE, CONSEQENTES, INCIDENTAIS E ESPECIAIS) INCLUSIVE, MAS NO LIMITADO A, VIOLAO DA PROPRIEDADE INTELECTUAL, CUSTOS DE REABASTECIMENTO, IMPOSSIBILIDADE DE USO, INTERRUPES DE NEGCIOS, PERDA DE REPUTAO E LUCROS CESSANTES, QUER ESSES DANOS SURJAM POR NEGLIGNCIA CONTRATUAL, RETALIAO OU SOB QUALQUER GARANTIA, A DESPEITO DE A INTEL TER SIDO AVISADA ANTECIPADAMENTE SOBRE A POSSIBILIDADE DESSES DANOS. INDEPENDENTEMENTE DO DISPOSTO ANTERIORMENTE, A RESPONSABILIDADE TOTAL DA INTEL POR TODAS AS REIVINDICAES PREVISTAS NESTE CONTRATO NO DEVER ULTRAPASSAR O PREO PAGO PELO PRODUTO. ESSAS LIMITAES SOBRE AS POSSVEIS RESPONSABILIDADE FORAM UM COMPONENTE FUNDAMENTAL AO ESTIPULAR O PREO DO PRODUTO. A INTEL NO ASSUME NEM AUTORIZA QUALQUER PESSOA A ASSUMIR QUAISQUER OUTRAS RESPONSABILIDADES EM SEU NOME.
Alguns estados no permitem a excluso ou limitao de danos incidental ou consequentes, de modo que as limitaes citadas anteriormente podem no ser aplicveis ao seu caso.
Aplicaes de controle crtico: A Intel se isenta especificamente da responsabilidade pelo uso do produto adaptador em aplicaes de controle crtico (incluindo, apenas para fins de exemplo, os sistemas de controle de segurana ou tratamento de sade, sistemas de controle de energia nuclear ou os sistemas de controle do trfego areo ou terrestre) por Licenciado ou Sublicenciados, e tal uso ser um risco total do usurio. O Licenciado concorda em defender, indenizar e isentar a Intel de e contra quaisquer e todas as aes legais decorrentes do uso do produto adaptador em tais aplicaes, pelos Licenciado ou
Sub-licenciados.
Software: O software fornecido com o produto adaptador no est coberto pela garantia de hardware descrita anteriormente. Consulte o contrato de licena do software aplicvel, que acompanha o produto adaptador, para obter detalhes sobre a garantia do software.
Nota: Se voc for usurio final e estiver sujeito s leis australianas de proteo ao consumidor, esta garantia no se aplica a voc. Visite o site da garantia vitalcia limitada de hardware para a Austrlia para ver a garantia limitada que aplicvel aos consumidores australianos.
Modificao mais recente: 17 de setembro de 2012 - 10h42
If your 82599-based Intel® Network Adapter came
with Intel optics, or is an Intel® Ethernet Server Adapter X520-2, then
it only supports Intel optics and/or the direct attach cables listed
below.
82599-Based adapters support all passive and active limiting direct attach
cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4
specifications.
Supplier
Type
Part Numbers
SR Modules
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
FTLX8571D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ SR (bailed)
AFBR-703SDDZ-IN1
LR Modules
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
FTLX1471D3BCV-IT
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDZ-IN2
Intel
DUAL RATE 1G/10G SFP+ LR (bailed)
AFCT-701SDDZ-IN1
The following is a list of 3rd party SFP+ modules that have received some testing. Not all modules are applicable to all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
Finisar
DUAL RATE 1G/10G SFP+ SR (No Bail)
FTLX8571D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ SR (No Bail)
AFBR-703SDZ-IN1
Finisar
DUAL RATE 1G/10G SFP+ LR (No Bail)
FTLX1471D3QCV-IT
Avago
DUAL RATE 1G/10G SFP+ LR (No Bail)
AFCT-701SDZ-IN1
Finisar
1000BASE-T SFP
FCLF8522P2BTL
Avago
1000BASE-T SFP
ABCU-5710RZ
HP
1000BASE-SX SFP
453153-001
82598-Based Adapters
NOTES:
Intel® Network Adapters that support removable
optical modules only support their original module type (i.e., the
Intel® 10 Gigabit SR Dual Port Express Module only supports SR optical
modules). If you plug in a different type of module, the driver will not
load.
82598-Based adapters support all passive direct
attach cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4
specifications. Active direct attach cables are not supported.
Hot Swapping/hot plugging optical modules is
not supported.
Only single speed, 10 gigabit modules are
supported.
LAN on Motherboard (LOMs)
may support DA, SR, or LR modules. Other module types are not supported.
Please see your system documentation for details.
The following is a list of SFP+ modules and direct attach cables that have
received some testing. Not all modules are applicable to all devices.
Supplier
Type
Part Numbers
Finisar
SFP+ SR bailed, 10g single rate
FTLX8571D3BCL
Avago
SFP+ SR bailed, 10g single rate
AFBR-700SDZ
Finisar
SFP+ LR bailed, 10g single rate
FTLX1471D3BCL
Molex
1m - Twin-ax cable
74752-1101
Molex
3m - Twin-ax cable
74752-2301
Molex
5m - Twin-ax cable
74752-3501
Molex
10m - Twin-ax cable
74752-9004
Tyco
1m - Twin-ax cable
2032237-2
Tyco
3m - Twin-ax cable
2032237-4
Tyco
5m - Twin-ax cable
2032237-6
Tyco
10m - Twin-ax cable
1-2032237-1
THIRD PARTY OPTIC
MODULES AND CABLES REFERRED TO ABOVE ARE LISTED ONLY FOR THE PURPOSE OF
HIGHLIGHTING THIRD PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY, AND ARE NOT
RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF ANY THIRD PARTY'S PRODUCT BY
INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE BY ANY THIRD PARTY AND
THE THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE INFORMATION REGARDING
CERTAIN OPTIC MODULES AND CABLES WITH THE ABOVE SPECIFICATIONS. THERE MAY BE
OTHER MANUFACTURERS OR SUPPLIERS, PRODUCING OR SUPPLYING OPTIC MODULES AND
CABLES WITH SIMILAR OR MATCHING DESCRIPTIONS. CUSTOMERS MUST USE THEIR OWN
DISCRETION AND DILIGENCE TO PURCHASE OPTIC MODULES AND CABLES FROM ANY THIRD PARTY OF THEIR CHOICE. CUSTOMERS ARE SOLELY
RESPONSIBLE FOR ASSESSING THE SUITABILITY OF THE PRODUCT AND/OR DEVICES AND FOR
THE SELECTION OF THE VENDOR FOR PURCHASING ANY PRODUCT. THE OPTIC MODULES AND
CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES
NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR SELECTION OF VENDOR
BY CUSTOMERS.
Connect a 10GbE Fiber Network Cable
CAUTION: This product uses a Class 1M laser module. Viewing the
laser output with certain optical instruments designed for use at a distance (for example, telescopes and binoculars) may pose an
eye hazard.
Remove and save the fiber optic connector cover. Insert a fiber optic
cable into the ports on the
network adapter bracket as shown.
Most connectors and ports are keyed for proper orientation. If the cable
you are using is not keyed, check to be
sure the connector is oriented properly (transmit port connected to
receive port on the link partner, and vice versa).
For Intel® 10GbE LR Server Adapters:
Laser wavelength: 1310 nanometer (not visible).
Cable type to use: Single-mode fiber with 9.0m core diameter
Connector type: LC.
Maximum cable length: 10 kilometers.
For Intel® 10GbE SR Server Adapters:
Laser wavelength: 850 nanometer (not visible).
Cable type to use: Multi-mode fiber with 62.5m or 50m core diameter
Connector type: LC or SC.
Maximum cable length: 300 meters.
The adapter must be connected to a compatible link partner, such as an IEEE
802.3ae-compliant 10-gigabit switch, which is operating at the same laser
wavelength as the adapter.
Conversion cables to other connector types (such as SC-to-LC) may be used
if the cabling matches the optical specifications of the adapter, including
length limitations.
