intellectual propertylaws. Exceptas expressly permitted in your license agreementor allowedby law, you may not use, copy,reproduce, translate,
broadcast, modify,license, transmit,distribute, exhibit,perform, publish,or displayany part,in anyform, orby anymeans. Reverseengineering,
disassembly, or decompilation of this software,unless required bylaw forinteroperability, isprohibited.
The informationcontained hereinis subjectto changewithout noticeand isnot warrantedto beerror-free.If youfind anyerrors, pleasereport them to us
in writing.
If thisis softwareor related softwaredocumentation thatis deliveredto theU.S. Governmentor anyonelicensing iton behalfof theU.S. Government,the
following noticeis applicable:
U.S. GOVERNMENTRIGHTS. Programs,software, databases, and related documentation and technical data deliveredto U.S.Government customers
are "commercial computer software" or"commercial technicaldata" pursuantto theapplicable FederalAcquisition Regulationand agency-specific
supplemental regulations.As such,the use,duplication, disclosure, modification, and adaptation shall be subject to the restrictionsand licenseterms set
forth inthe applicableGovernment contract,and, tothe extentapplicable bythe termsof theGovernment contract,the additionalrights setforth inFAR
52.227-19, CommercialComputer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This softwareor hardware isdeveloped forgeneral use in a varietyof informationmanagement applications.It isnot developed or intended for use inany
inherently dangerous applications, including applications which may create arisk ofpersonal injury.If youuse thissoftware orhardware in dangerous
applications, thenyou shallbe responsibleto takeall appropriate fail-safe, backup, redundancy,and othermeasures toensure the safe use. Oracle
Corporation andits affiliatesdisclaim anyliability forany damagescaused byuse ofthis software or hardware indangerous applications.
Oracle andJava areregistered trademarks of Oracle and/or its affiliates.Other namesmay betrademarks oftheir respectiveowners.
AMD, Opteron,the AMDlogo, andthe AMDOpteron logo are trademarks or registered trademarksof AdvancedMicro Devices. Intel and Intel Xeon are
trademarks orregistered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registeredtrademarks of
SPARCInternational, Inc.UNIX is a registered trademarklicensed throughX/Open Company,Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services.
restrictions d’utilisationet dedivulgation. Saufdisposition devotre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire,
diffuser,modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher lelogiciel, mêmepartiellement, sousquelque formeet par
quelque procédéque cesoit. Parailleurs, ilest interdit de procéder àtoute ingénierieinverse dulogiciel, dele désassemblerou dele décompiler, exceptéà
des finsd’interopérabilité avecdes logicielstiers outel queprescrit par la loi.
Les informationsfournies dansce documentsont susceptiblesde modificationsans préavis.Par ailleurs,Oracle Corporationne garantitpas qu’elles
soient exemptesd’erreurs etvous invite,le caséchéant, àlui enfaire part par écrit.
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government
contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
Ce logicielou matériela étédéveloppé pourun usagegénéral dansle cadred’applications degestion desinformations. Celogiciel oumatériel n’estpas
conçu nin’est destinéà êtreutilisé dansdes applicationsà risque,notamment dansdes applicationspouvant causerdes dommagescorporels. Si vous
utilisez celogiciel oumatériel dansle cadred’applications dangereuses, il est de votre responsabilitéde prendre toutesles mesuresde secours,de
sauvegarde, deredondance et autres mesures nécessairesà sonutilisation dansdes conditionsoptimales desécurité. OracleCorporation etses affiliés
déclinent touteresponsabilité quantaux dommagescausés parl’utilisation dece logicielou matérielpour cetype d’applications.
Oracle etJava sontdes marquesdéposées d’OracleCorporation et/oude sesaffiliés.Tout autre nom mentionné peut correspondre àdes marques
appartenant àd’autres propriétaires qu’Oracle.
AMD, Opteron,le logoAMD etle logoAMD Opteron sont des marquesou desmarques déposéesd’Advanced Micro Devices. Intel et Intel Xeon sont des
marques oudes marques déposées d’Intel Corporation. Toutesles marques SPARC sontutilisées souslicence etsont desmarques ou des marques
déposées deSPARCInternational, Inc.UNIX est une marque déposée concédée sous licence par X/Open Company, Ltd.
Please
Recycle
Contents
Using This Documentationvii
1.Product Overview1
Components1
Product Description1
Hardware and Software Requirements3
Features3
Declaration of Conformity5
2.Installing and Setting Up the Driver7
Downloading and Installing the Driver on a Solaris SPARC or x86 Platform7
▼To Download the Driver on a Solaris Platform7
▼To Remove the Driver from a Solaris Platform9
Downloading and Installing the Driver on a Linux Platform10
▼To Remove the Driver From a Linux Platform12
3.Installing the Adapter13
Installing the Adapter13
▼To Install the Adapter14
Installing an Optical Transceiver17
▼To Install an Optical Transceiver18
iii
Verifying the Hardware Installation20
▼To Verify the Hardware Installation20
Rebooting the System22
4.Network Configuration23
Configuring the Network Host Files23
Setting Up a 10-Gigabit Ethernet Network on a Diskless Client System25
▼To Set Up a 10-Gigabit Ethernet Port on a Diskless Client26
Installing the Solaris Operating System Over a 10-Gigabit Ethernet Network27
▼To Install the Solaris Operating System Over a 10-Gigabit Ethernet
Network27
Booting Over the 10-Gigabit Ethernet Network for Solaris x86 and Linux
Systems30
▼To Boot Over the Network on Solaris x86 and Linux Systems30
5.Configuring the nxge Device Driver Parameters33
nxge Hardware and Software Overview33
Setting nxge Driver Parameters on a Solaris Platform34
Setting Parameters Using the ndd Utility34
Noninteractive and Interactive Modes34
▼To Specify Device Instances for the ndd Utility35
▼To Specify Parameter Values Using the ndd Utility35
▼To Use the ndd Utility in Interactive Mode35
Setting Parameters Using the nxge.conf File36
▼To Set Driver Parameters Using an nxge.conf File37
Tuning for Maximum Performance on a Solaris Platform41
▼To Improve Performance on an UltraSPARC CPU Based Sun Platform41
▼To Improve Performance on an AMD CPU Based Sun Platform42
▼To Obtain Higher Throughput Using the Generic Tunables for the Solaris
This guide provides instructions for installing both the hardware and software for
the Sun Dual 10GbE XFP PCI Express card from Oracle. This manual also describes
how to configure the nxge driver, which controls the card.
These instructions are designed for enterprise system administrators with experience
installing network hardware and software.
Note – In this document the term x86 refers to 64-bit and 32-bit systems
manufactured using processors compatible with the AMD64 or Intel Xeon/Pentium
product families. For supported systems, see the Solaris Hardware Compatibility Guide.
Using UNIX Commands
This document might not contain information about basic UNIX commands and
procedures such as shutting down the system, booting the system, and configuring
devices. Refer to the following for this information:
■ Software documentation that you received with your system
■ Solaris Operating System documentation, which is at:
The Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter is a low
profile x8 lane PCI-Express 10 gigabit Ethernet card utilizing the Sun ASIC with
XFP-based 10-gigabit Ethernet optics. The Sun x8 Express Dual 10 Gigabit Ethernet
Fiber XFP Low Profile Adapter requires an optical transceiver.
TABLE 1-1 lists the supported hardware and software.
Features
The Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
provides the following features:
■ Two full-duplex 10 gigabit Ethernet interface that use a 10 gigabit Ethernet small
form factor pluggable (XFP), optical transceiver with duplex LC fiber connector
■ IEEE 802.3ae 2002 compliant
■ Uses Sun’s own ASIC and software for innovative throughput networking design
■ Networking I/O virtualization supporting Solaris LDOM 1.0. (VMware support
planned for mid 07)
■ Hardware-based flow classification for extending parallelism and virtualization to
networking
■ Up to 16 Receive DMA channels and up to 24 Transmit DMA channels, multiple
receive and transmit Descriptor Rings and dedicated networking hardware
resources (DMA, interrupts, buffer, and more) for each thread or strand
■ CPU/thread affinity and CPU load balancing at L1,L2,L3 and L4
■ Dynamic Reconfiguration (DR)
■ Jumbo frame support (up to 9KBytes)
■ IPv4/IPv6 and IPMP support
■ TCP/UDP/IP checksum and CRC32C support
■ IEEE 802.1Q VLAN support
Chapter 1 Product Overview3
Declaration of Conformity
Compliance Model Number:ATLS2XGF
Product Family Name:Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
EMC
USA—FCC Class A
This equipment complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
1. This equipment may not cause harmful interference.
2. This equipment must accept any interference that may cause undesired operation.
European Union
This equipment complies with the following requirements of the EMC Directive 89/336/EEC:
As Information Technology Equipment (ITE) Class A per (as applicable):
EN 55022:1994 +A1:1995 +A2:1997 Class A
EN 61000-3-2:2000Pass
EN 61000-3-3:1995 +A1:2000Pass
EN 55024:1998 +A1:2001 +A2:2003 Required Limits:
IEC 61000-4-24 kV (Direct), 8kV (Air)
IEC 61000-4-33 V/m
IEC 61000-4-41 kV AC Power Lines, 0.5 kV Signal and DC Power Lines
IEC 61000-4-51 kV AC Line-Line and Outdoor Signal Lines, 2 kV AC Line-Gnd, 0.5 kV DC Power
IEC 61000-4-63 V
IEC 61000-4-81 A/m
IEC 61000-4-11Pass
Lines
Safety
This equipment complies with the following requirements of the Low Voltage Directive 73/23/EEC:
EC Type Examination Certificates:
EN 60950-1:2001, 1st Edition
IEC 60950-1:2001, 1st EditionCB Scheme Certificate No.
Evaluated to all CB Countries
UL and cUL/CSA 60950-1:2001, CSA C22.2 No. 60950-00 File:E138989-A82Vol. 54
FDA DHHS Accession Number (Monitors Only)
Supplementary Information
This equipment was tested and complies with all the requirements for the CE Mark.
This equipment complies with the Restriction of Hazardous Substances (RoHS) directive 2002/95/EC.
Worldwide Compliance Engineering
Sun Microsystems, Inc.
4150 Network Circle, MPK15-102
Santa Clara, CA 95054 U.S.A.
Tel: 650-786-3255
Fax: 650-786-3723
Donald Cameron
Program Manager/Customer Quality
Sun Microsystems Scotland, Limited
Blackness Road, Phase I, Main Bldg.
Springfield, EH49 7LR
Scotland, United Kingdom
Tel: +44 1 506 672 539Fax: +44 1 506 670 011
This chapter explains how to download and install the nxge driver. The nxge gigabit
Ethernet driver (nxge(7D)) is a multi-threaded, loadable, clonable, GLD-based
STREAMS driver. The nxge driver is managed by the dladm(1M) command line
utility, which allows VLANs to be defined on top of nxge instances and for nxge
instances to be aggregated. See the dladm(1M) man page for more details on
configuring the data-link interfaces and link aggregations.
This chapter contains the following sections:
■ “Downloading and Installing the Driver on a Solaris SPARC or x86 Platform” on
page 7
■ “Downloading and Installing the Driver on a Linux Platform” on page 10
Downloading and Installing the Driver
on a Solaris SPARC or x86 Platform
If your system uses the Solaris SPARC or x86 operating system you will need to
download and install the nxge device driver for Solaris platforms.
▼ To Download the Driver on a Solaris Platform
1. Locate and download the nxge device driver software at the following web
■ Press Return or type all to accept the default and install all packages.
■ Type the specific numbers, separated by a space, if you prefer not to install any
optional packages.
7. Verify that the nxge driver is installed on the system:
Sun PCI-E 10G/1G Ethernet Adapter Driver(i386)
1.0,REV=2006.12.05.10.0 Copyright 2006 Sun Microsystems,
Inc. All rights reserved. Use is subject to license terms.
## Executing checkinstall script. Using as the package base
directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs. This package contains
scripts which will be executed with super-user permission
during the process of installing this package.
Do you want to continue with the installation of [y,n,?] y
Installing Sun PCI-E 10G/1G Ethernet Adapter Driver as
## Installing part 1 of 1.
/kernel/drv/amd64/nxge [ verifying class ]
# Executing postinstall script.
# Installation of was successful.
▼ To Remove the Driver from a Solaris Platform
1. To discover the driver packages run the pkginfo command:
3. Discover the network interfaces before adding the package by using the
ifconfig -a command:
# ifconfig -a |grep eth
eth0 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DC
eth1 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DD
eth2 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DE
eth3 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DF
4. Use the rpm tool to install the driver on SuSe and RedHat Linux.
Note – In RHEL5.0 and later releases, the driver is packaged in the kmod driver
binary package format. This packaging allows forward and backward driver binary
compatibility within the same flavors of RHEL5 releases. Driver packages nxge
version 2.0.0 and later are not compatible with the earlier nxge-1.x-x releases. To
upgrade from 1.x-x to 2.x.x rpm package, it is necessary to remove nxge-1.x-x package before installing the 2.x.x package.
The RHEL5 nxge 2.x.x kmod package contains two separate packages: One for
the driver and another one for applications like nxge_config. You must install
both of the following packages:
To ensure that the driver is loaded after the rpm installation, enter the following:
# modprobe nxge
5. Verify the new network interface instances corresponding to the Sun x8 Express
Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter:
# ifconfig -a |grep eth
eth0 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DC
eth1 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DD
eth2 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DE
eth3 Link encap:Ethernet HWaddr 00:14:4F:20:F1:DF
eth4 Link encap:Ethernet HWaddr 00:14:4F:6C:78:E8
eth5 Link encap:Ethernet HWaddr 00:14:4F:6C:78:E9
The Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
instances, eth4 and eth5, are shown in
bold italics.
6. Add the nxge interfaces to the /etc/modules.conf file to automatically load
the driver after system reboot:
alias eth4 nxge
alias eth5 nxge
Chapter 2 Installing and Setting Up the Driver11
7. Use the ethtool command to check the parameter configurations that apply to
the nxge driver.
This chapter describes how to install the Sun x8 Express Dual 10 Gigabit Ethernet
Fiber XFP Low Profile Adapter in your system and verify that it has been installed
correctly.
This chapter contains the following section:
■ “Installing the Adapter” on page 13
■ “Installing an Optical Transceiver” on page 17
■ “Verifying the Hardware Installation” on page 20
Note – If you are installing the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP
Low Profile Adapter in a machine running either the Solaris x86 Operating System
or the Linux x86 Operating System, Dynamic Reconfiguration (DR) is not supported.
Installing the Adapter
If you are installing the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low
Profile Adapter into a machine running Solaris 10, you must install the software
before you install the hardware.
The following instructions describe the basic tasks required to install the adapter.
Refer to your system installation or service manual for detailed PCI-Express adapter
installation instructions, specifically you must check which bracket your server
requires (low profile or standard height), and install the standard height bracket if
required.
mechanical fit limitations:
Do not install the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile
Adapter in slot-2 of a Sun Fire T2000 system. The SATA cables from the adjacent
card slot prevent the proper installation of an Sun x8 Express Dual 10 Gigabit
Ethernet Fiber XFP Low Profile Adapter in this slot. (Note that this issue does not
exist for Sun Fire T2000 that is RoHS compliant.)
Caution – Do not install the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP
Low Profile Adapter in slot-5 of a Sun Fire X4600 system because the heatsink on the
adapter will sit against the daughter card of the Sun Fire X4600 system.
Note – When you install the adapter, ensure that the optical transceiver has not been
installed. The optical transceiver must be installed into the adapter when it is in
place.
This section contains the following topics:
■ “To Install the Adapter” on page 14
■ “Installing an Optical Transceiver” on page 17
■ “Verifying the Hardware Installation” on page 20
▼ To Install the Adapter
1. Halt and power off your system.
2. Power off all of the peripherals connected to your system.
3. Open the system unit.
4. Attach the adhesive copper strip of the antistatic wrist strap to the metal casing
of the power supply. Wrap the other end twice around your wrist, with the
adhesive side against your skin.
5. Remove the filler panel from the PCI-E opening.
Note – These illustrations show the Sun x8 Express Dual 10 Gigabit Ethernet Fiber
XFP Low Profile Adapter being installed into a Sun Fire T2000, which requires a
standard height bracket for the low profile adapter.
6. Open the retaining clip at the edge of the PCI-E opening.
7. Holding the adapter by the edges, align the adapter edge connector with the
PCI-E slot. Slide the adapter face plate into the small slot at the end of the PCIE opening.
8. Applying even pressure at both corners of the adapter, push the PCI-Express
adapter until it is firmly seated in the slot.
Chapter 3 Installing the Adapter15
9. Secure the retaining clip
Caution – Do not use excessive force when installing the adapter into the PCI-E
slot. You might damage the adapter ’s PCI connector. If the adapter does not seat
properly when you apply even pressure, remove the adapter and carefully reinstall
it.
10. Detach the wrist strap and close the system unit.
Note – Illustrations for installing the adapter and installing the optical transceiver
show different systems. This difference in systems provides the maximum clarity for
installing the optical transceiver and shows the most complicated adapter
installation.
Installing an Optical Transceiver
The Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
requires an optical transceiver in each port to create and Ethernet connection. The
short-range optical transceiver Part Number: 135-1172-01 and the long-range optical
transceiver Part Number: 375-3495-01 are both available from Sun Microsystems.
Chapter 3 Installing the Adapter17
▼ To Install an Optical Transceiver
1. Pull the white locking handle into the full horizontal position.
You will feel the handle click into position when it is fully opened.
Note – If you are installing an optical transceiver in a Sun Fire T1000, ensure that
the label and the edge connector is visible to you.
2. Holding the optical transceiver by the edges, align the transceiver with the slot
in the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
and slide it into the opening.
3. Applying even pressure at both corners of the transceiver, push the transceiver
until it is firmly seated in the slot.
4. Push the handle closed to lock the optical transceiver in place.
5. Repeat Step 1 through Step 4 to install the second optical transceiver
6. Detach the wrist strap.
Caution – If you pull the locking handle down when the optical transceiver is
installed, remove the optical transceiver entirely and reinstall it. The handle operates
an internal lock. Pulling the handle down can disconnect the optical transceiver,
even though it might appear to be connected.
Chapter 3 Installing the Adapter19
7. Connect the Ethernet cables.
Verifying the Hardware Installation
After you have installed the Sun 10-Gigabit Ethernet adapter, but before you boot
your system, perform the following tasks to verify the installation. Refer to the your
Solaris documentation for the detailed instructions.
Note – Verification is not required if your system supports dynamic reconfiguration
(DR). Verification is not supported if your system is running Solaris x86 software.
▼ To Verify the Hardware Installation
1. Power on the system, and when the banner appears, press the Stop-A key
sequence to interrupt the boot process and display the OpenBoot (ok) prompt.
2. List the network devices on your system.
ok show-nets
a) /pci@7c0/pci@0/pci@8/network@0,1
b) /pci@7c0/pci@0/pci@8/network@0
c) /pci@7c0/pci@0/pci@2/network@0,1
d) /pci@7c0/pci@0/pci@2/network@0
e) /pci@780/pci@0/pci@1/network@0,1
f) /pci@780/pci@0/pci@1/network@0
q) NO SELECTION from the above list
Checking the .properties output for each device is the surest way to identify
the device. Usually /pci@7c0/pci@0/pci@8 or /pci@7c0/pci@0/pci@9
correspond to PCIe slots, so look at those devices first.
a) /pci@7c0/pci@0/pci@8/network@0,1
b) /pci@7c0/pci@0/pci@8/network@0
Note – If you do not see the device listed, check that the adapter is properly seated.
4. Use the .properties command to display a list of device properties.
The .properties command displays the specific information about the device. If
you are using the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile
Adapter, your output will be similar to the following:
This chapter describes how to edit the network host files after the adapter has been
installed on your system. This chapter contains the following sections:
■ “Configuring the Network Host Files” on page 23
■ “Setting Up a 10-Gigabit Ethernet Network on a Diskless Client System” on
page 25
■ “Installing the Solaris Operating System Over a 10-Gigabit Ethernet Network” on
page 27
■ “Booting Over the 10-Gigabit Ethernet Network for Solaris x86 and Linux
Systems” on page 30
Configuring the Network Host Files
After installing the driver software, you must create a hostname.nxgenumber file
for the adapter’s Ethernet interface. You must also create both an IP address and a
host name for its Ethernet interface in the /etc/hosts file.
23
1. At the command line, use the grep command to search the
/etc/path_to_inst file for nxge interfaces.
In this example, the device instance is from a Sun x8 Express Dual 10 Gigabit
Ethernet Fiber XFP Low Profile Adapter installed in slot 1.
Be sure to write down your device path and instance, which in the example is
"/pci@7c0/pci@0/pci@9/network@0" 0. Your device path and instance will be
similar. You need this information to make changes to the nxge.conf file. See
“Setting Parameters Using the nxge.conf File” on page 36.
2. Use the ifconfig command to set up the adapter’s nxge interface.
Use the ifconfig command to assign an IP address to the network interface.
Type the following at the command line, replacing ip-address with the adapter’s IP
address:
# ifconfig nxge0 plumb ip-address up
Refer to the ifconfig(1M) man page and the Solaris documentation for more
information.
■ If you want a setup that remains the same after you reboot, create an
/etc/hostname.nxgenumber file, where number is the instance number of the
nxge interface you plan to use.
To use the adapter’s nxge interface in the Step 1 example, create an
/etc/hostname.nxge0 file, where 0 is the number of the nxge interface. If the
instance number were 1, the filename would be
/etc/hostname.nxge1.
■ Do not create an /etc/hostname.nxgenumber file for a Sun x8 Express Dual 10
Gigabit Ethernet Fiber XFP Low Profile Adapter interface you plan to leave
unused.
■ The /etc/hostname.nxgenumber file must contain the host name for the
appropriate nxge interface.
■ The host name must have an IP address listed in the /etc/hosts file.
■ The host name must be different from any other host name of any other interface,
for example: /etc/hostname.nxge0 and /etc/hostname.nxge1 cannot share
the same host name.
The following example shows the /etc/hostname.nxgenumber file required for
a system called zardoz that has a Sun x4 PCI-Express Gigabit Ethernet driver
(zardoz-11).
3. Create an appropriate entry in the /etc/hosts file for each active nxge
interface.
For example:
# cat /etc/hosts
#
# Internet host table
#
127.0.0.1 localhost
129.144.10.57 zardoz loghost
129.144.11.83 zardoz-11
Setting Up a 10-Gigabit Ethernet
Network on a Diskless Client System
Before you can boot and operate a diskless client system across a 10-Gigabit Ethernet
network, you must first install the 10-Gigabit Ethernet software packages into the
root directory of the diskless client. You can find the 10-Gigabit Ethernet software
packages at the following web site:
Refer to the Solaris Advanced Installation Guide and the System Administration Guide
for more information about installing and administering diskless client systems.
Note – The Solaris x86 version of the operating system do not support diskless
clients.
Chapter 4 Network Configuration25
▼ To Set Up a 10-Gigabit Ethernet Port on a
Diskless Client
1. Locate the root directory of the diskless client on the host server.
The root directory of diskless client system is commonly installed in the host
server’s /export/root/client-name directory, where client_name is the diskless
client’s host name. In this procedure, the root directory is:
/export/root/client-name
2. Download the software for Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP
Low Profile Adapter onto the server’s drive.
3. Use the pkgadd -R command to install the software packages to the diskless
client’s root directory on the server.
Install the software packages to the client’s root directory.
4. Create a hostname.nxgenumber file in the diskless client’s root directory.
Create an /export/root/client-name/etc/hostname.nxgenumber file for the
10-Gigabit Ethernet interface. See “Configuring the Network Host Files” on
page 23 for instructions.
5. Edit the hosts file in the diskless client’s root directory.
Edit the /export/root/client-name/etc/hosts file to include the IP address of
the 10-Gigabit Ethernet interface. See “Configuring the Network Host Files” on
page 23 for instructions.
6. Set the MAC address on the server side and rebuild the device tree if you want
to boot from the 10-Gigabit Ethernet port.
7. To boot the diskless client from the 10-Gigabit Ethernet port, type the
following boot command:
Installing the Solaris Operating System
Over a 10-Gigabit Ethernet Network
The Solaris Advanced Installation Guide describes the full procedure for installing the
Solaris Operating System over the network. The following procedure assumes that
you have created an install server, which contains the image of the Solaris CD, and
that you have set up the client system to be installed over the network.
Before you can install the Solaris Operating System on a client system with a 10Gigabit Ethernet adapter, you must first add the 10-Gigabit Ethernet software
packages to the install server. These software packages are on Sun 10-Gigabit
Ethernet Driver CD.
Note – Refer to the Solaris Advanced Installation Guide for more information about
installing the Solaris Operating System over the network.
▼ To Install the Solaris Operating System Over a
10-Gigabit Ethernet Network
1. Prepare the install server and client system to install the Solaris Operating
System over the network.
The Solaris Advanced Installation Guide describes how to create the install server
and set up the client systems.
Note – If you want to install the client system over a network that is not part of the
same subnet, you must also create a boot server. The Solaris Advanced Installation
Guide describes how to create a boot server.
Chapter 4 Network Configuration27
2. Find the root directory of the client system.
The client system’s root directory can be found in the install server’s
/etc/bootparams file. Use the grep command to search this file for the root
directory.
6. At the ok prompt, use the show-nets command to find the device path of the
10-Gigabit Ethernet device.
The show-nets command lists the system devices. You should see the full paths
and names of the network devices, similar to the example below.
ok show-nets
a) /pci@7c0/pci@0/pci@8/network@0,1
b) /pci@7c0/pci@0/pci@8/network@0
c) /pci@7c0/pci@0/pci@2/network@0,1
d) /pci@7c0/pci@0/pci@2/network@0
e) /pci@780/pci@0/pci@1/network@0,1
f) /pci@780/pci@0/pci@1/network@0
q) NO SELECTION from the above list
7. At the ok prompt, boot the client system using the full device path of the 10-
Gigabit Ethernet device, for example:
ok boot /pci@7c0/pci@0/pci@8/network@0
8. Proceed with the Solaris Operating System installation.
Refer to the Solaris Advanced Installation Guide for more information about
installing the Solaris Operating System over the network.
9. After installing the Solaris Operating System, install the Sun x8 Dual 10
Gigabit Ethernet software on the client system.
The software installed in Step 4 is required to boot the client system over the 10Gigabit Ethernet interface. You now need to install the software in order for the
operating system to use the client’s 10-Gigabit Ethernet interfaces in normal
operation.
Before installing the Sun 10-Gigabit Ethernet driver, ensure that the client system
does not already have the driver installed. Use the pkginfo command to see if
the Sun 10-Gigabit Ethernet software packages are installed on the client system.
# pkginfo | grep SUNWnxge
Chapter 4 Network Configuration29
■ If the software is installed, the previous command will return the package name
you typed in. In that case, skip to Step 10.
■ If the software is not installed, install the software from the download center.
See Chapter 2 for instructions on installing the required software packages.
10. Confirm that the network host files have been configured correctly during the
Solaris installation.
Although the Solaris software installation creates the client’s network
configuration files, you may need to edit these files to match your specific
networking environment. See “Configuring the Network Host Files” on page 23
for more information about editing these files.
11. Use the dladm show-dev command to show configuration information for
all data-links or the specified data-link. By default, the system is configured to
have one data-link for each known network device.
# dladm show-dev
e1000g0link: upspeed: 1000 Mbpsduplex: full
e1000g1link: downspeed: 0Mbpsduplex: half
e1000g2link: downspeed: 0Mbpsduplex: half
e1000g3link: downspeed: 0Mbpsduplex: half
nxge0link: upspeed: 10000 Mbpsduplex: full
nxge1link: upspeed: 10000 Mbpsduplex: full
Booting Over the 10-Gigabit Ethernet
Network for Solaris x86 and Linux
Systems
▼ To Boot Over the Network on Solaris x86 and
Linux Systems
1. Obtain the MAC address from the target Sun x8 Express Dual 10 Gigabit
Ethernet Fiber XFP Low Profile Adapter.
2. Set up the PXE boot server with the MAC addresses .
3. Choose one of the adapter ports as the boot interface.
6. Press the F2 key or the Control/E keys to go to the BIOS.
7. Check and make sure that the boot order of Hard Drive is higher than network
devices.
8. Refer the boot-device-order image.
The reconfiguration boot attaches the driver to the adapter. You can now
configure the driver parameters for your Sun x8 Express Dual 10 Gigabit Ethernet
Fiber XFP Low Profile Adapter.
9. Press the F10 key to save the boot configuration changes and exit.
System should reboot after saving the boot configuration.
Chapter 4 Network Configuration31
10. Press the F12 key to install the OS from the network.
If the cable is connected to the right port, you should see the MAC address that
you assigned to your PXE server displayed by BIOS.
image : pxe-mac-addr
PXE-E61: Media test failure, check cable
PXE-MOF: Exiting Intel Boot Agent.
The nxge device driver controls the Sun x8 Express Dual 10 Gigabit Ethernet
interfaces. You can manually set the nxge driver parameters to customize each
device in your system.
This chapter lists the available device driver parameters and describes how you can
set these parameters.
■ “nxge Hardware and Software Overview” on page 33
■ “Setting nxge Driver Parameters on a Solaris Platform” on page 34
■ “Setting Parameters Using the ndd Utility” on page 34
■ “Setting Parameters Using the nxge.conf File” on page 36
■ “Setting Parameters on a Linux Platform” on page 44
nxge Hardware and Software Overview
The Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter
provides two 10-Gigabit Full Duplex networking interfaces. The device driver
automatically sets the link speed to 10000 Mbit/sec and conforms to the IEEE 802.3
Ethernet standard. Each interface has 8 Receive DMA Channels and 12 Transmit
DMA Channels to allow for parallel processing of the packets. The Sun x8 Express
Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter extends CPU and OS
parallelism to networking with its support for hardware-based flow classification
and multiple DMAs. Using CPU thread affinity to bind a given flow to a specific
CPU thread, it enables a one-to-one correlation of Rx and Tx packets across the same
TCP connection. This can help avoid cross-calls and context switching to deliver
greater performance while reducing the need for CPU resources to support I/O
33
processing. The Sun 10-Gigabit Ethernet Adapter utilizes Sun’s own innovative
MAC Controller to map the 10-Gigabit XAUI interface onto the PCI Express form
factor. It supports 10 Gb/sec bandwidth using eight transmit and eight receive lanes.
Setting nxge Driver Parameters on a
Solaris Platform
You can set the nxge device driver parameters in two ways:
■ Using the ndd utility
■ Using the nxge.conf file
If you use the ndd utility, the parameters are valid only until you reboot the system.
This method is good for testing parameter settings.
To set parameters so they remain in effect after you reboot the system, create a
/platform/sun4u/kernel/drv/nxge.conf file and add parameter values to this
file when you need to set a particular parameter for a device in the system.
Setting Parameters Using the ndd Utility
Use the ndd utility to configure parameters that are valid until you reboot the
system.
The following sections describe how you can use the nxge driver and the ndd utility
to modify (with the -set option) or display (without the -set option) the
parameters for each nxge device.
Noninteractive and Interactive Modes
You can use the ndd utility in two modes:
■ Noninteractive
■ Interactive
In noninteractive mode, you invoke the utility to execute a specific command. Once
the command is executed, you exit the utility. In interactive mode, you can use the
utility to get or set more than one parameter value. Refer to the ndd(1M) man page
for more information.
This section describes how to modify and display parameter values.
1. To modify a parameter value, use the -set option.
If you invoke the ndd utility with the -set option, the utility passes value, which
must be specified, down to the named /dev/nxgedriver_instance, and assigns the
value to the parameter:
# ndd -set /dev/nxgeX parameter-value
Where X is the driver instance, for example /dev/nxge0, /dev/nxge1.
2. To display the value of a parameter, specify the parameter name and omit the
value.
When you omit the -set option, the utility queries the named driver instance,
retrieves the value associated with the specified parameter, and prints it:
# ndd /dev/nxgeX parameter
▼ To Use the ndd Utility in Interactive Mode
1. To modify a parameter value in interactive mode, specify ndd /dev/nxgeX:
# ndd /dev/nxge0
name to get/set? (Enter the parameter name or ? to view all
parameters)
Chapter 5 Configuring the nxge Device Driver Parameters35
After you enter the parameter name, the ndd utility prompts you for the parameter
value.
2. To list all the parameters supported by the nxge driver, type ?.
# ndd /dev/nxge1 name to get/set ?
? (read only)
function_number (read only)
adv_autoneg_cap (read and write)
adv_10gfdx_cap (read and write)
adv_1000fdx_cap (read and write)
adv_100fdx_cap (read and write)
adv_10fdx_cap (read and write)
adv_pause_cap (read and write)
accept_jumbo (read and write)
rxdma_intr_time (read and write)
rxdma_intr_pkts (read and write)
class_opt_ipv4_tcp (read and write)
class_opt_ipv4_udp (read and write)
class_opt_ipv4_ah (read and write)
class_opt_ipv4_sctp (read and write)
class_opt_ipv6_tcp (read and write)
class_opt_ipv6_udp (read and write)
class_opt_ipv6_ah (read and write)
class_opt_ipv6_sctp (read and write)
Setting Parameters Using the
nxge.conf File
Specify the driver parameter properties for each device by creating a nxge.conf file
in the /kernel/drv directory. Use a nxge.conf file when you need to set a
particular parameter for a device in the system.
The man pages for prtconf(1M) and driver.conf(4) include additional details.
The next procedure shows an example of setting parameters in a nxge.conf file.
● To access any man page, type the man command plus the name of the man
page.
For example, to access man pages for prtconf(1M), type:
■ The first part within the double quotes specifies the hardware node name in
the device tree.
■ The number not enclosed in quotes is the instance number (shown in bold
italics
■ The last part in double quotes is the driver name.
for emphasis).
To identify a PCI-E device unambiguously in the nxge.conf file, use the name,
parent name, and the unit-address for the device. Refer to the pci(4) man page for
more information about the PCI-E device specification.
In this example:
■ name = "pciex108e,abcd"
■ parent = "/pci@780/pci@0/pci@8/network@0"
■ unit-address = "0"
2. Set the parameters for the nxge devices in the
/platform/sun4u/kernel/drv/nxge.conf file.
a. The following parameters can be set using the
/platform/sun4u/kernel/drv/nxge.conf file.
#
#---------------Link Configuration ---------------------# The link parameters depend on the type of the card
# and the port.
Chapter 5 Configuring the nxge Device Driver Parameters37
# 10 gigabit related parameters ( i.e adv_10gfdx_cap)
# apply only to 10gigabit ports.
# Half duplex is not supported on any NIU card.
#
# adv-autoneg-cap
# Advertise auto-negotiation capability.
# default is 1
# adv-autoneg-cap = 1;
#
# adv_10gfdx_cap
# Advertise 10gbps Full duplex capability.
# default is 1
# adv_10gfdx_cap = 1;
#
# adv_1000fdx_cap
# Advertise 1gbps Full duplex capability.
# default is 1
# adv_1000fdx_cap = 1;
#
# adv_100fdx_cap
# Advertise 100mbps Full duplex capability.
# default is 1
# adv_100fdx_cap = 1;
#
# adv_10fdx_cap
# Advertise 10mbps Full duplex capability.
# default is 1
# adv_10fdx_cap = 1;
#
# adv_asmpause_cap
# Advertise Asymmetric pause capability.
# default is 0
# adv_asmpause_cap = 0;
#
# adv_pause_cap
# Advertise pause capability.
# default is 1
# adv_pause_cap = 1;
#
#
#------- Jumbo frame support --------------------------------# To enable jumbo support for all nxge interfaces,
# accept_jumbo = 1;
#
# To disable jumbo support for all nxge interfaces,
# accept_jumbo = 0;
#
# Default is 0. See the example at the end of this file for
# enabling or disabling jumbo for a particular nxge interface.
#
#
#------- Receive DMA Configuration ---------------------------#
# rxdma-intr-time
# Interrupts after this number of NIU hardware ticks have
# elapsed since the last packet was received.
# A value of zero means no time blanking (Default = 8).
#
# rxdma-intr-pkts
# Interrupt after this number of packets have arrived since
# the last packet was serviced. A value of zero indicates
# no packet blanking (Default = 20).
#
# Default Interrupt Blanking parameters.
#
# rxdma-intr-time = 8;
# rxdma-intr-pkts = 20;
#
#
#------- Classification and Load Distribution Configuration -----#
# class-opt-****-***
# These variables define how each IP class is configured.
# Configuration options range from whether TCAM lookup ie
# is enabled to flow hash generation.
# This parameters also control how the flow template is
# constructed and how packet is distributed within RDC
# groups.
#
# supported classes:
# class-opt-ipv4-tcp class-opt-ipv4-udp class-opt-ipv4-sctp
# class-opt-ipv4-ah class-opt-ipv6-tcp class-opt-ipv6-udp
# class-opt-ipv6-sctp class-opt-ipv6-ah
#
# Configuration bits (The following bits will be decoded
# by the driver as hex format).
#
# 0010: use MAC Port (for flow key)
# 0020: use L2DA (for flow key)
# 0040: use VLAN (for flow key)
# 0080: use proto (for flow key)
# 0100: use IP src addr (for flow key)
# 0200: use IP dest addr (for flow key)
# 0400: use Src Port (for flow key)
# 0800: use Dest Port (for flow key)
#
# class-opt-ipv4-tcp = fe0;
#
Chapter 5 Configuring the nxge Device Driver Parameters39
b. The following parameters operate on a per port basis and can be set using
the /platform/sun4u/kernel/drv/nxge.conf file.
#
# ------- How to set parameters for a particular interface -------# The example below shows how to locate the device path and set a
# parameter for a particular nxge interface. (Using jumbo support as
# an example)
#
# Use the following command to find out the device paths for nxge,
# more /etc/path_to_inst | grep nxge
#
# For example, if you see,
# "/pci@7c0/pci@0/pci@8/network@0" 0 "nxge"
# "/pci@7c0/pci@0/pci@8/network@0,1" 1 "nxge"
# "/pci@7c0/pci@0/pci@8/network@0,2" 2 "nxge"
# "/pci@7c0/pci@0/pci@8/network@0,3" 3 "nxge"
#
# then you can enable jumbo for ports 0 and 1 and disable jumbo for ports 2
# and 3 as follows,
#
# name = "pciex108e,abcd" parent = "/pci@7c0/pci@0/pci@8/" unit-address
= "0"
# accept_jumbo = 1;
# name = "pciex108e,abcd" parent = "/pci@7c0/pci@0/pci@8/" unit-address
= "0,1"
# accept_jumbo = 1;
# name = "pciex108e,abcd" parent = "/pci@7c0/pci@0/pci@8/" unit-address
= "0,2"
# accept_jumbo = 0;
# name = "pciex108e,abcd" parent = "/pci@7c0/pci@0/pci@8/" unit-address
= "0,3"
# accept_jumbo = 0;
c. In the following example, the ports of all the Sun x8 Express Dual 10 Gigabit
Ethernet Fiber XFP Low Profile Adapter are being set for load balancing Rx
traffic based on IP source address. The default value is F80 indicating Rx
load balancing based on IP 5-tuple. Notice the semi-colon at the end of the
last parameter.
Tuning for Maximum Performance on a
Solaris Platform
Tuning for maximum performance in a Solaris platform depends on whether you
are using an UltraSPARC CPU based platform or an AMD CPU based platform.
▼ To Improve Performance on an UltraSPARC
CPU Based Sun Platform
1. Improve performance by adding the following /etc/system file:
# set ddi_msix_alloc_limit=4
Increasing the MSI improves the Rx performance. The default value for MSI is 2,
but changing it to 4 improves performance (8 can be used for UltraSparc-T1 based
systems).
2. Reboot the system:
# reboot -r
Chapter 5 Configuring the nxge Device Driver Parameters41
3. Add the following to a startup script, or use ndd before plumbing the interface:
# ndd -set /dev/ip ip_soft_rings_cnt 8
Utilizing more soft-rings provided by the Solaris TCP/IP stack significantly
improves bulk throughput for Rx. The default number of soft-rings is 2, but
changing it to 8 improves performance. (You can increase the number to 16 in
UltraSparc-T1 based systems).
▼ To Improve Performance on an AMD CPU Based
Sun Platform
1. Enable soft-rings and change to a higher value than the default of 2 by adding
the following to the /etc/system file:
set ip:ip_squeue_fanout=1
set ip_squeue_soft_ring=1
Bulk throughput for Rx can be significantly improved by utilizing more soft-rings
provided by the Solaris TCP/IP stack. Soft-rings are disabled by default in
previous and current releases of the Solaris-x86 Operating System.
2. Reboot the system:
# reboot -r
3. Set the MSI to 1 on AMD platforms by adding following to the /etc/system
rx-usecs and rx-frames control the RX interrupt rate per RX DMA channel. RX
interrupt will be generated after rx-frames have been received or after rx-usecs
time interval if fewer than rx-frames have been received within the interval. For
low latency applications, it is recommended to set rx-usecs to smaller value. For
bulk traffic, it is recommended to use larger values of rx-usecs and control the
rate with rx-frames.
rx-frames-irq controls the maximum number of rx packets processed with a single
RX interrupt.
3. To get status of L4 HW checksumming, use the ethtool -k command:
# ethtool -k eth4
Offload parameters for eth4:
Cannot get device tcp segmentation offload settings: Operation not
supported
rx-checksumming: on
tx-checksumming: on
scatter-gather: off
tcp segmentation offload: off
Chapter 5 Configuring the nxge Device Driver Parameters47
▼ To Set Parameters Using the Bundled
configtool Utility
1. To get a list of tunable parameters, use the nxge_config if_name get
command:
# /usr/local/bin/nxge_config eth4 get
The tunable parameters exported by this device are:
These classification variables define how each IP class is configured. This
parameter also controls how the flow template is constructed and how packets are
distributed within RDC groups.
Configuration bits:
0x0010: use MAC Port (for flow key)
0x0020: use L2DA (for flow key)
0x0040: use VLAN (for flow key)
0x0080: use proto (for flow key)
0x0100: use IP src addr (for flow key)
0x0200: use IP dest addr (for flow key)
0x0400: use Src Port (for flow key)
0x0800: use Dest Port (for flow key)
Note – The classification variables are modified on an adapter basis, that is, if any of
these variables is modified for one port, the change carries over to all other ports of
that adapter.
2. To get a particular variable use the nxge_config if_name get param_name:
# /usr/local/bin/nxge_config eth4 get class_opt_ipv4_udp
class_opt_ipv4_udp 0xfe3
3. To set a particular variable, use the /usr/local/bin/nxge_config if_name
set param_name value:
# /usr/local/bin/nxge_config eth4 set class_opt_ipv4_tcp 0xfe0
Tuning for Maximum Performance on a
Linux Platform
The following tunings will improve the performance of the Sun x8 Express Dual 10
Gigabit Ethernet device driver on a system running the Linux operating system.
1. Create the conf file (for example, sysctl_nxge.conf) that will be called by
the sysctl utility.
### IPV4 specific settings
# turns TCP timestamp support off, default 1, reduces CPU use
net.ipv4.tcp_timestamps = 0
# turn SACK support off, default on systems with a VERY fast bus ->
# memory interface this is the big gainer
This chapter describes how to configure the Jumbo Frames feature. It contains the
following sections:
■ “Jumbo Frames Overview” on page 51
■ “Checking Jumbo Frames Configurations” on page 51
■ “Enabling Jumbo Frames in a Solaris Environment” on page 53
■ “Enabling Jumbo Frames in a Linux Environment” on page 54
Jumbo Frames Overview
Configuring Jumbo Frames enables the Ethernet interfaces to send and receive
packets larger than the standard 1500 bytes. However, the actual transfer size
depends on the switch capability and the ethernet adapter driver capability.
Note – Refer to the documentation that came with your switch for exact commands
to configure Jumbo Frames support.
Checking Jumbo Frames Configurations
The jumbo frame configuration checking occurs at Layer 2 or Layer 3, depending on
the configuration method.
51
▼ To Show the Driver Statistics in a Solaris
Environment
1. Use the kstat command to display driver statistics, for example:
The previous example displays the receive packet counts on all of the eight
Receive DMA channels on interface 1. Using the kstat nxge:1 shows all the
statistics that the driver supports for that interface.
2. Use the kstat command to display driver statistics of a VLAN interface, for
example:.
This section describes how to enable jumbo frames in both a SPARC and an x86
environment.
▼ To Enable Jumbo Frames in a Solaris
Environment Using nxge.conf
1. Enable Jumbo Frames for a port using the nxge.conf file. For example,
name = "pciex108e,abcd" parent = "/pci@780/pci@0/pci@8/network@0"
unit-address = "0"
accept-jumbo=1;
2. Reboot the system:
% boot -r
3. Set the maximum MTU for maximum performance:
# ifconfig nxge mtu 9194
▼ To Check Layer 2 Configuration
● View the maximum transmission unit (MTU) configuration of an nxge instance
at any time with the kstat command.
# kstat nxge:0 | grep mac_mtu
The kstat mac_mtu variable represents the complete size of the Ethernet frame,
which includes the Ethernet header, maximum payload, and crc. This value
should be equal to or less than the MTU configured on the switch.
Chapter 6 Configuring the Jumbo Frames Feature53
▼ To Check Layer 3 Configuration
● Check the Layer 3 configuration by using the dladm command with the show-
This chapter describes how to configure link aggregation. It contains the following
sections:
■ “Overview of Link Aggregation” on page 57
■ “Configuring Link Aggregation in a Linux Environment” on page 60
Overview of Link Aggregation
Link Aggregation allows one or more network links to be aggregated together to
form a link aggregation group. This link aggregation group appears to MAC clients
as a regular link. Link aggregation is defined by IEEE 802.2ad and it provides the
following benefits:
■ Increased bandwidth
■ Linearly incremental bandwidth
■ Load sharing
■ Automatic configuration
■ Rapid configuration and reconfiguration
■ Deterministic behavior
■ Low risk of duplication or mis-ordering
■ Support of existing IEEE 802.3 MAC clients
57
Configuring Link Aggregation in a
Solaris Environment
This section explains how to configure link aggregation in a Solaris environment.
▼ To Configure Link Aggregation in a Solaris
Environment
1. Aggregate nxge0 and nxge1 to form an aggregation and a random number 33 as
key.
a. Unplumb the interfaces to be aggregated:
# ifconfig down unplumb nxge0
# ifconfig down unplumb nxge1
b. Create a link-aggregation group with key 33 without specifying mode:
# dladm create-aggr -d nxge0 -d nxge1 33
As the command returns, one line appears in /etc/aggregation.conf file and
indicates that the default mode is off, as shown in the following example:
# tail -1 /etc/aggregation.conf
33 L4 2 nxge0/0,nxge1/0 auto off short
# dladm show-aggr
key: 33 (0x0021) policy: L4 address: 0:3:ba:d8:9d:e8 (auto)
device address speed duplex link state
nxge0 0:3:ba:d8:9d:e8 10000 Mbps full up standby
nxge1 0:3:ba:d8:9d:e9 10000 Mbps full up standby
5. Use the dladm show-aggr -L command to display LACP specific
information:
# dladm show-aggr -L
key: 33 (0x0021) policy: L4 address: 0:3:ba:d8:9d:e8 (auto)
LACP mode: off LACP timer: short
device activity timeout aggregatable sync coll dist defaulted expired
nxge0 passive short yes no no no no no
nxge1 passive short yes no no no no no
For more information refer to the man pages for dladm, man dladm.
Chapter 7 Configuring Link Aggregation59
Configuring Link Aggregation in a
Linux Environment
This section explains how to configure link aggregation in a Linux environment.
▼ To Configure Bonding for Multiple nxge
Interfaces
1. Modify the /etc/modprobe.conf file for 2.6 kernels file by adding these
lines:
alias bond0 bonding
options bonding max_bonds=2 mode=4 miimon=1000
where:
■ bond0 is the bonding device.
■ max_bonds is the number of bond interfaces to be created.
■ mode specifies the bonding policies.
■ miimon is the frequency in milliseconds that MII link monitoring will occur.
Refer to Linux documentation for more information.
2. Load the bonding driver:
# modprobe bonding
3. Configure bond0 interface.
In this example, bond0 is the master of the two interfaces eth4 and eth5.
# ip addr add 192.12.38.64/24 brd + dev bond0
# ip link set dev bond0 up
# ifenslave bond0 eth4 eth5
This chapter explains Virtual Local Area Networks (VLANs) in detail and provides
configuration instructions and examples. It contains the following sections:
■ “Overview of VLANs” on page 61
■ “Configuring VLANs in a Solaris Environment” on page 63
■ “Configuring VLANs in a Linux Environment” on page 65
With multiple VLANs on an adapter, a server with a single adapter can have a
logical presence on multiple IP subnets. By default, 128 VLANs can be defined for
each VLAN-aware adapter on your server. However, this number can be increased
by changing the system parameters.
If your network does not require multiple VLANs, you can use the default
configuration, in which case no further configuration is necessary.
Overview of VLANs
VLANs enable you to split your physical LAN into logical subparts, providing an
essential tool for increasing the efficiency and flexibility of your network.
VLANs are commonly used to separate groups of network users into manageable
broadcast domains, to create logical segmentation of workgroups, and to enforce
security policies among each logical segment. Each defined VLAN behaves as its
own separate network, with its traffic and broadcasts isolated from the others,
increasing the bandwidth efficiency within each logical group.
Although VLANs are commonly used to create individual broadcast domains
and/or separate IP subnets, it can be useful for a server to have a presence on more
than one VLAN simultaneously. Several Sun products support multiple VLANs on a
per port or per interface basis, allowing very flexible network configurations.
61
FIGURE 8-1 shows an example network that uses VLANs.
FIGURE 8-1 Example of Servers Supporting Multiple VLANs With Tagging Adapters
The example network has the following features:
The physical LAN network consists of a switch, two servers, and five clients. The
LAN is logically organized into three different VLANs, each representing a different
IP subnet.
■ VLAN 1 is an IP subnet consisting of the Main Server, Client 3, and Client 5. This
represents an engineering group.
■ VLAN 2 includes the Main Server, Clients 1 and 2 by means of a shared media
segment, and Client 5. This is a software development group.
■ VLAN 3 includes the Main Server, the Accounting Server and Client 4. This is an
accounting group.
The Main Server is a heavily used server that needs to be accessed from all VLANs
and IP subnets. The server has a Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP
Low Profile Adapter installed. All three IP subnets are accessed by means of the
single physical adapter interface. The server is attached to one of the switch’s
Gigabit Ethernet ports, which is configured for VLANs 1, 2, and 3. Both the adapter
and the connected switch port have tagging turned on. The tagging VLAN
capabilities of both devices enable the sever to communicate on all three IP subnets
in this network, yet continue to maintain broadcast separation among the three
subnets. The following list describes the components of this network:
■ The Accounting Server is available to VLAN 3 only. It is isolated from all traffic
on VLANs 1 and 2. The switch port connected to the server has tagging turned
off.
■ Clients 1 and 2 are attached to a shared media hub that is then connected to the
switch. They belong to VLAN 2 only, and are logically in the same IP subnet as
the Main Server and Client 5. The switch port connected to this segment has
tagging turned off.
■ Client 3 is a member of VLAN 1, and can communicate only with the Main Server
and Client 5. Tagging is not enabled on Client 3’s switch port.
■ Client 4 is a member of VLAN 3, and can communicate only with the servers.
Tagging is not enabled on Client 4’s switch port.
■ Client 5 is a member of both VLANs 1 and 2, and has a Sun x8 Express Dual 10
Gigabit Ethernet Fiber XFP Low Profile Adapter installed. It is connected to
switch port 10. Both the adapter and the switch port are configured for VLANs 1
and 2 and have tagging enabled.
VLAN tagging is only required to be enabled on switch ports that create trunk links
to other VLAN-aware Ethernet switches, or on ports connected to tag-capable endstations, such as servers or workstations with VLAN-aware adapters.
Configuring VLANs in a Solaris
Environment
VLANs can be created according to various criteria, but each VLAN must be
assigned a VLAN tag or VLAN ID (VID). The VID is a 12-bit identifier between 1
and 4094 that identifies a unique VLAN. For each network interface (nxge0 andnxge1), 4094 possible VLAN IDs can be selected. Only 512 unique IDs can be used
simultaneously. Because IP subnets are commonly used, it is best to use IP subnets
when setting up a VLAN network interface. This means that each VID assigned to a
VLAN interface of a physical network interface will belong to different subnets.
Tagging an Ethernet frame requires the addition of a tag header to the frame. The
header is inserted immediately following the destination MAC address and the
Source MAC address. The tag header consists of two bytes of Ethernet Tag Protocol
identifier (TPID, 0x8100) and two bytes of Tag Control Information (TCI).
shows the Ethernet Tag Header format.
Chapter 8 Configuring VLANs63
FIGURE 8-2
FIGURE 8-2 Ethernet Tag Header Format
TPID (0x8100
3 bits
bit
1
12 bytes
Octet
1
2
3
4
User_priority
CFI
VID
By default, a single VLAN is configured for every port. This groups all ports into the
same broadcast domain, just as if there were no VLANs at all, VLAN tagging for the
switch port is turned off.
Note – If you configure a VLAN virtual device for an adapter, all traffic sent or
received by that adapter must be in VLAN-tagged format.
▼ To Configure Static VLANs
1. Create one hostname.nxgenumber file for each VLAN that will be configured
for each adapter on the server.
Use the following naming format, which includes both the VID and the physical
point of attachment (PPA):
VLAN logical PPA = 1000 * VID + Device PPA
nxge123000 = 1000*123 + nxge
This format limits the maximum number of PPAs (instances) you can configure to
1000 in the /etc/path_to_inst file.
For example, on a server with the Sun x8 Express Dual 10 Gigabit Ethernet Fiber
XFP Low Profile Adapter having an instance of 0, belonging to a member of two
VLANs, with VID 123 and 224, you would use nxge123000 and nxge224000,
respectively, as the two VLAN PPAs.
This appendix lists the specifications for the Sun x8 Express Dual 10 Gigabit Ethernet Fiber
XFP Low Profile Adapter. It contains the following sections:
■ “Connectors” on page 67
■ “Performance Specifications” on page 68
■ “Physical Characteristics” on page 69
■ “Power Requirements” on page 69
Connectors
FIGURE A-1 shows the connector for the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP
This appendix provides an overview of the SunVTS diagnostic application and
instructions for updating the SunVTS software to recognize the adapter. This
appendix contains the following sections:
■ “SunVTS Diagnostic Software” on page 71
■ “Updating SunVTS to Recognize the Adapter” on page 72
■ “Using the SunVTS netlbtest” on page 73
SunVTS Diagnostic Software
The SunVTS software executes multiple diagnostic hardware tests from a single user
interface and is used to verify the configuration and functionality of most hardware
controllers and devices. The SunVTS software operates primarily from a graphical
user interface, enabling test parameters to be set quickly and easily while a
diagnostic test operation is being performed.
Note – SunVTS diagnostic software is not currently available for Solaris x86
Operating Systems.
The SunVTS nettest diagnostic can be used to test all of the networking interfaces
on the system, including the interfaces on the adapter.
To use the nettest diagnostic, you must have the SunVTS software installed on
your system. Refer to your Solaris documentation for installation instructions.
Refer to the SunVTS documentation (listed in
run and monitor the nettest diagnostic. These SunVTS documents are available
online at the following URL:
You must have the Ethernet card and the device driver installed, a loopback
connector in place, and Intervention mode enabled before running netlbtest.netlbtest cannot run if the network interface is connected to a live network, and
requires that the Ethernet device be configured offline before running the test. Use
the ifconfig(1M) command to bring the Ethernet device down before running
netlbtest.
▼ To Use the netlbtest
1. Ensure that the SunVTS software and the nxge driver are installed on your
system.
2. Plug in a loopback cable.
3. Unplumb the interface from the system, using the ifconfig command:
# ifconfig nxgeinstance down
# ifconfig nxgeinstance unplumb
Where
Refer to SunVTS documentation for instructions on how to run netlbtest.