Exit Print View

Sun Dual 10GbE SPF+ PCIe 2.0 Low Profile Adapter User’s Guide

Get PDF Book Print View

Document Information

Using This Documentation

Related Documentation

Documentation, Support, and Training

Documentation Feedback

Understanding the Low Profile Adapter

Shipping Kit Contents

Product Description

Front Panel Connectors and LEDs

Physical Characteristics

Performance Specifications

Power and Environmental Requirements

Hardware and Software Requirements

OS Patches and Updates

Solaris Platform Installation Overview

Linux Platform Installation Overview

Microsoft Windows Platform Installation Overview

Installing the Driver

Verify the Driver Version on a Solaris Platform

Remove the Driver From a Solaris Platform

Download and Install the Driver on a Linux Platform

Remove the Driver From a Linux Platform

Download and Install the Driver on a Microsoft Windows Platform

Remove the Driver From a Microsoft Windows Platform

Installing the Low Profile Adapter

Install the SFP+ Transceivers

Install the Adapter in a System

Verify the Installation in a Solaris SPARC System

Verify the Installation in a Solaris x86 System

Verify the Installation in a Linux System

Verify the Installation in a Microsoft Windows System

Configuring the Network

Create /etc/hostname.ixgbe# Files

Configure the Network Host Files With the ifconfig Command

Boot Over the Network Using PXE

Boot Solaris x86 and Linux Systems Over a 10GbE Network

Install the Solaris OS Over a 10GbE Network on SPARC Systems

Configuring the Driver Parameters

Driver Parameters for the Solaris OS

Set ixgbe Driver Parameters in the Solaris OS

Solaris OS Performance Variables

Improve Performance in the Solaris OS

Driver Parameters for Linux

Set Driver Parameters in Linux

Configure Jumbo Frames in Solaris OS

Configure Jumbo Frames in Linux

Configuring Link Aggregation in a Solaris Environment

Link Aggregation Overview

Configure Link Aggregations

Display Information About Link Aggregations

Delete Link Aggregations

Configuring VLANs

VLAN Overview

VLAN Configuration

Configure Static VLANs in a Solaris Environment

VLAN Naming Format

Configure VLANs in a Linux Environment

Configure VLANs in a Microsoft Windows Environment

Configure Bonding for Multiple ixgbe Interfaces

Remove Bonding


VLAN Overview

With multiple VLANs on a card, a server with a single card can have a logical presence on multiple IP subnets. By default, you can define 128 VLANs for each VLAN-aware card on your server. However, you can increase this number 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.

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 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.

The following figure shows an example network that uses VLANs.

Illustration shows an 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.

The Main Server is a high-use server that must be accessed from all VLANs and IP subnets. The server has a Sun Dual 10GbE SFP+ PCIe 2.0 Low Profile Adapter installed. All three IP subnets are accessed by means of the single physical Ethernet 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 Ethernet adapter and the connected switch port have tagging turned on. Because of the tagging VLAN capabilities of both devices, the server is able to communicate on all three IP subnets in this network, but continues to maintain broadcast separation between all of those subnets. The following list describes the components of this network:

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 end-stations, such as servers or workstations with VLAN-aware Ethernet adapters.

Related Information