Fujitsu C120-E276-11ENZ0A User Manual

FUJITSU PCI Gigabit Ethernet

4.1 Update2 / 5.0 for Oracle Solaris

User's Guide

SPARC Enterprise

Solaris

C120-E276-11ENZ0(A)

October 2011

Preface

Purpose

This manual describes how to install the Gigabit Ethernet card into your SPARC Enterprise system, and configure the environmental settings for the interface.

Target Reader

This manual is intended for system administrators responsible for installing the Gigabit Ethernet card. To understand the concepts and procedures presented in this manual, you need a few years of experience in Oracle Solaris (in this manual,

abbreviated to Solaris) system administration and have a basic knowledge of networked systems.

Organization

This section describes how this manual is organized.

Chapter 1 Product Outline

Chapter 1 describes the distinctive features of the Gigabit Ethernet Card.

Chapter 2 Gigabit Ethernet Card Installation

Chapter 2 describes how to install the Gigabit Ethernet card.

Chapter 3 Setting Instructions

Chapter 3 provides an overview of the environment definition.

Chapter 4 LinkAggregation Feature

Chapter 4 describes how to use the LinkAggregation function.

Chapter 5 Troubleshooting

Chapter 5 provides information about how to troubleshoot and resolve problems you might encounter during installation.

Appendix A Messages

Appendix A explains the messages output by the driver software.

Appendix B Gigabit Ethernet Card LED Diagnosis

Appendix B explains details of the Gigabit Ethernet card LED diagnostics.

Appendix C Using FUJITSU PCI GigabitEthernet in a Cluster Environment

Appendix C describes notes when using the card in a Cluster System.

Appendix D Using FUJITSU PCI GigabitEthernet in Solaris Containers

Appendix D describes notes when using the card in Solaris Containers.

Appendix E Using FUJITSU PCI GigabitEthernet in Oracle VM Server for SPARC

Appendix E describes notes when using the card in Oracle VM Server for SPARC.

Appendix F Using FUJITSU PCI GigabitEthernet in Solaris 11 Network Virtualization

Appendix F describes notes when using the card in Solaris 11 Network Virtualization.

Appendix G PCI Slot Number and Device Name

Appendix G shows the PCI slot number and device name list for each SPARC Enterprise model.

Symbol

The following symbols are used in this manual:

- i -

Note

- This symbol indicates that important information is given.

Information

- This symbol indicates that useful information is given.

Handling of This Manual

This manual contains important information regarding the use and handling of this product. Read this manual thoroughly. Pay special attention to the section "Important Warnings". Use the product according to the instructions in this manual.

FUJITSU makes every effort to prevent users and bystanders from being injured or from suffering damages to their property. Use the product according to this manual.

Documents produced by FUJITSU may contain technology controlled under the Foreign Exchange and Foreign Trade Control Law of Japan. The document which contains such technology should not be exported from Japan or transferred to anyone other than residents of Japan without first obtaining license from the Ministry of International Trade and Industry of Japan in accordance with the above law.

TRADEMARK ACKNOWLEDGMENTS

- FUJITSU and the FUJITSU logo are trademarks of Fujitsu Limited.

- UNIX is a registered trademark of The Open Group in the United States and other countries.

- Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

All other product names and company names mentioned herein are trademarks or registered trademarks of their respective owners.

- The contents of this manual shall not be disclosed in any way or reproduced in any media without the express written permission of

Fujitsu Limited.

14th Edition: October 2011

Attention

- The contents of this manual may be revised without prior notice.

Revision History

Edition Date Details

01 2003-2-20 02 2003-5-1 PRIMEPOWER1/100 was supported

VLAN function was supported

03 2004-1-8

04 2004-10-28

Support switches was added Changed the Version 2.0 to 2.1 LinkAggregation function was supported

- ii -

Edition Date Details

Support switches was added Changed the Version 2.1 to 2.2

05 2005-11-11

06 2006-2-06

07 2007-1-20

08 2007-4-03 Changed the Version 3.0 to 3.0 Update1

09 2008-2-29

10 2008-8-29

11 2010-2-1

13 2010-12-17

Quad Gigabit Ethernet card(PW008QG1) was supported Changed the Version 2.2 to 2.3 RoHS compliant 1port Gigabit Ethernet Card(PW0G8GE1, PW0G8GE2) was supported Changed the Version 2.3 to 2.4 PCI Express Gigabit Ethernet Card(SE0X7GD1X, SE0X7GD2X, SE0X7CQ1X) was

supported Changed the Version 2.4 to 3.0

GLDv3(The LinkAggregation Feature of dladm(1M) command, Solaris Containers, Logical Domains) was supported

Changed the Version 3.0 Update1 to 3.0 Update2 / 4.0 PCI Express Gigabit Ethernet card(SE0X7GQ2X) was supported Changed the Version 3.0 Update2 / 4.0 to 3.0 Update3 / 4.0 Update1 Added the parameters and the setting method of new style to the operation mode setup Deleted the PRIMEPOWER and GP7000F family Changed the Version 3.0 Update3 / 4.0 Update1 to 3.0 Update3 / 4.1 Deleted the driver version 3.0 Update3. Changed the name of Solaris to Oracle Solaris. Changed the name of Logical Domains(LDoms) to Oracle VM Server for SPARC.

14 2011-10-25

Changed the Version 3.0 Update3 / 4.1 to 4.1 Update1. Solaris 11 Network Virtualization(Vanity Naming, Environment Setting with the

ipadm(1M) command, VLAN by dladm(1M) command, VNIC by dladm(1M) command, Operation Mode Setup by dladm(1M) command, Flow by flowadm(1M) command) was supported.

Added The SPARC T3 series. Changed Sun Microsystems Documentation to Oracle Documentation. Changed the Version 4.1 Update1 to 4.1 Update2 / 5.0.

- iii -

Chapter 1 Product Outline........................................................................................................................................................1

1.1 Key Features........................................................................................................................................................................................1

1.2 Gigabit Ethernet Card Specifications..................................................................................................................................................2

1.2.1 Specifications................................................................................................................................................................................2

1.2.2 Part Names and Features of Hardware.........................................................................................................................................3

Chapter 2 Gigabit Ethernet Card Installation............................................................................................................................6

2.1 Installation of the Gigabit Ethernet Card.............................................................................................................................................6

2.2 Identifying the Gigabit Ethernet Card.................................................................................................................................................6

2.3 Cable Connection.................................................................................................................................................................................6

Chapter 3 Setting Instructions................................................................................................................................................11

3.1 Driver Software Installation...............................................................................................................................................................11

3.2 Identification of Interface Name........................................................................................................................................................11

3.3 Environment Setting..........................................................................................................................................................................12

3.3.1 Environment Setting of IPv4 Interfaces......................................................................................................................................12

3.3.2 Environment Setting of IPv6 Interfaces......................................................................................................................................14

3.4 Identification of the Gigabit Ethernet Card.......................................................................................................................................15

3.5 Operation Mode Setup.......................................................................................................................................................................17

3.5.1 Setting the fjgi.conf File.............................................................................................................................................................17

3.5.2 JumboFrame Setup.....................................................................................................................................................................26

3.5.3 Using the ndd(1M) command.....................................................................................................................................................28

3.5.4 Using the dladm(1M) command.................................................................................................................................................32

3.5.5 FCode Settings............................................................................................................................................................................35

3.6 Network Installation..........................................................................................................................................................................37

3.7 VLAN Interface Setup.......................................................................................................................................................................37

3.7.1 IEEE 802.1Q TagVLAN.............................................................................................................................................................37

3.7.2 Setting Up the VLAN Interface..................................................................................................................................................38

Chapter 4 LinkAggregation Feature.......................................................................................................................................40

4.1 About LinkAggregation Feature........................................................................................................................................................40

4.2 Configuration of the LinkAggregation Feature ................................................................................................................................42

4.2.1 Setting and Displaying the Configuration with the dladm(1M) Command................................................................................42

4.2.1.1 Create a LinkAggregation (dladm create-aggr)...................................................................................................................43

4.2.1.2 Delete a LinkAggregation (dladm delete-aggr)...................................................................................................................47

4.2.1.3 Modify a LinkAggregation (dladm modify-aggr)...............................................................................................................48

4.2.1.4 Add Interfaces to a LinkAggregation (dladm add-aggr).....................................................................................................50

4.2.1.5 Remove Interfaces from a LinkAggregation (dladm remove-aggr)....................................................................................51

4.2.1.6 Display LinkAggregation Statistics and Information (dladm show-aggr)...........................................................................53

4.3 Notes..................................................................................................................................................................................................56

Chapter 5 Troubleshooting.....................................................................................................................................................57

Appendix A Messages............................................................................................................................................................58

A.1 Console Messages from the Driver...................................................................................................................................................58

Appendix B Gigabit Ethernet Card LED Diagnosis.................................................................................................................62

B.1 Location and Meaning of the LEDs..................................................................................................................................................62

Appendix C Using FUJITSU PCI GigabitEthernet in a Cluster Environment..........................................................................66

C.1 Cluster Environment Support............................................................................................................................................................66

C.2 Cluster Environment Setup Procedure..............................................................................................................................................66

C.3 Notes.................................................................................................................................................................................................66

Appendix D Using FUJITSU PCI GigabitEthernet in Solaris Containers................................................................................67

D.1 Solaris Containers Support...............................................................................................................................................................67

D.2 Solaris Containers Setup Procedure..................................................................................................................................................67

- iv -

D.3 Notes.................................................................................................................................................................................................69

Appendix E Using FUJITSU PCI GigabitEthernet in Oracle VM Server for SPARC..............................................................73

E.1 Oracle VM Server for SPARC Support............................................................................................................................................73

E.2 Oracle VM Server for SPARC Setup Procedure...............................................................................................................................73

E.3 Notes..................................................................................................................................................................................................75

Appendix F Using FUJITSU PCI GigabitEthernet in Solaris 11 Network Virtualization..........................................................76

F.1 Solaris 11 Network Virtualization Support.......................................................................................................................................76

F.2 Solaris 11 Network Virtualization Setup Procedure..........................................................................................................................76

F.3 Notes..................................................................................................................................................................................................78

Appendix G PCI Slot Number and Device Name...................................................................................................................79

- v -

Chapter 1 Product Outline

This chapter describes the following topics.

- 1.1 Key Features

- 1.2 Gigabit Ethernet Card Specifications

1.1 Key Features

The Gigabit Ethernet cards covered in this manual are adapters designed for Solaris servers that are connected to a Gigabit Ethernet network. These cards provide the physical services and data link services defined by IEEE802.3, and are designed to work in a framework of the open system architecture used widely now. These cards are integrated under various network protocols (TCP/IP supported by a driver) by the installation of a host software driver (*1).

These cards are also available for use in FUJITSU PRIMECLUSTER and PRIMECLUSTER GLS environments (*2). The Gigabit Ethernet cards are available for use in SPARC Enterprise servers with operating system Solaris 10 8/07 or later. The key features of the Gigabit Ethernet cards are listed in "Table 1.1 Gigabit Ethernet Card Features".

*1: The name of the host software driver for Gigabit Ethernet cards is "fjgi". *2: The Multipath Function of PRIMECLUSTER GLS is not supported. Only the redundant line control of PRIMECLUSTER GLS

is only supported.

Table 1.1 Gigabit Ethernet Card Features

Key Features

IEEE802.3 compliant 1000Base-SX * 2ports(SE0X7GD2X), 10/100/1000 Base-T * 2ports(SE0X7GD1X), 10/100/1000 Base-T * 4ports(SE0X7GQ1X, SE0X7GQ2X) JumboFrame feature ndd(1M) command support (*1) VLAN (IEEE 802.1Q TagVLAN) LinkAggregation (*2) (IEEE 802.3) IPv4/IPv6 GLDv3 compliant (*3) Solaris 11 Network Virtualization (*4)

*1: ndd(1M) command is not supported by FUJITSU PCI GigabitEthernet 5.0 or later. *2: For more information about the LinkAggregation, please refer to "Chapter 4 LinkAggregation Feature". *3: The GLDv3 compliant driver works on the SPARC Enterprise whose operating system is Solaris 10 8/07 or later. *4: Solaris 11 Network Virtualization work with FUJITSU PCI GigabitEthernet 5.0 or later.

- JumboFrame Feature

Although the maximum frame size of one Ethernet packet is 1518 bytes, by using the JumboFrame feature it becomes possible to set the maximum frame size from 1518 bytes to 9018 bytes. When comparing the same size of transmitted data, the JumboFrame feature can decrease the CPU load and improve transmission speed by reducing the number of packets.

- Point to Point Connection

Direct connection between Gigabit Ethernet cards is forbidden, except when used in the private LAN of a CLUSTER system (PRIMECLUSTER).

- GLDv3 Architecture

New network stacks and a new device driver framework (called GLDv3) are introduced into Solaris 10. In addition, a new dladm(1M) command to manage the data links is provided.

- 1 -

The GLDv3 compliant driver works with the following features.

- The LinkAggregation (based on IEEE 802.3) by the dladm(1M) command.

- Solaris Containers (Exclusive-IP Non-Global Zones)

- Oracle VM Server for SPARC

The GLDv3 compliant driver does not work with the following features.

- SNA/FNA

- The Multipath Function of PRIMECLUSTER GLS.

The following feature was changed.

- Set instance number by ndd(1M) command.

Solaris 11 Network Virtualization

New features, Vanity Naming and Environment Setting by ipadm(1M) command, are introduced into Solaris 11. In addition, dladm(1M) command and Network Virtualization are extended and New flowadm(1M) command controlled network flow is provided. FUJITSU PCI GigabitEthernet 5.0 or later works with the following features.

- Vanity Naming.

- Environment Setting by ipadm(1M) command.

- VLAN by dladm(1M) command.

- VNIC by dladm(1M) command.

- Operation Mode Setup by dladm(1M) command.

- Flow by flowadm(1M) command.

The following feature was changed.

- Configuration of the LinkAggregation feature by the dladm(1M) command.

1.2 Gigabit Ethernet Card Specifications

The Gigabit Ethernet card is an adapter that is installed into a PCI Express slot.

1.2.1 Specifications

The specifications of the GigabitEthernet cards are listed in "Table 1.2 PCI Gigabit Ethernet Card Specification".

Table 1.2 PCI Gigabit Ethernet Card Specification

Item Hardware Specification

Host Bus Interface

Network Interface

PCI Express 1.0a (SE0X7GD1X, SE0X7GD2X) PCI Express 1.1 (SE0X7GQ1X, SE0X7GQ2X)

1000Base-SX * 2ports (SE0X7GD2X) 10/100/1000Base-T * 2ports (SE0X7GD1X) 10/100/1000Base-T * 4ports (SE0X7GQ1X, SE0X7GQ2X)

Host Data Transfer

Bus Type

SE0X7GD1X, SE0X7GD2X, SE0X7GQ2X: PCI Express 4lane Bus Mastering DMA Transfers SE0X7GQ1X: PCI Express 8lane Bus Mastering DMA Transfers

One PCI Express slot per card.

- 2 -

Item Hardware Specification

Power Requirements

Connections

Maximum: 9.1W (SE0X7GD1X), 9.2W (SE0X7GD2X),

15.0W (SE0X7GQ1X), 12.8W (SE0X7GQ2X) 1000Base-SX (SE0X7GD2X): Multi-mode Fibre LC-SC: 62.5/125 micron and 50/125

micron (Card side is LC. Used when connecting to a device with an SC connector.), LCLC: 62.5/125 micron and 50/125 micron 10/100/1000Base-T (SE0X7GD1X, SE0X7GQ1X, SE0X7GQ2X): CAT5e Cable (CAT5 cable can also be used for 10/100Mbps.)

Note

- SE0X7GD2X only support full duplex connection. Half-duplex connection is not supported.

- When using 1000Mbps transmission rate with SE0X7GD1X, SE0X7GQ1X and SE0X7GQ2X, "Auto-Negotiation" must be set to

"on".

1.2.2 Part Names and Features of Hardware

Figure 1.1 to 1.4 shows the appearance of the Gigabit Ethernet cards. The part names and features are listed as follows.

- Connection

The SE0X7GD2X allows optical fibre cable connection; the SE0X7GD1X, SE0X7GQ1X and SE0X7GQ2X allow twisted pair cable connection. See the section "Chapter 2 Gigabit Ethernet Card Installation" for detailed information.

- LEDs

The LEDs of the Gigabit Ethernet cards are listed in "Table 1.3 LEDs". See "Appendix B Gigabit Ethernet Card LED Diagnosis" for detailed information.

Table 1.3 LEDs

Gigabit Ethernet cards LEDs

SE0X7GD2X(1000BASE-SX) Two LEDs per port: LINK LED, ACT LED

SE0X7GD1X(10/100/1000BASE-T)

SE0X7GQ1X SE0X7GQ2X (10/100/1000BASE-T)

Three LEDs per port: 1000M LED, 100M LED, LINK/ACT LED

Two LEDs per port: LINK LED, ACT LED

- 3 -

Figure 1.1 1000Base-SX * 2ports (SE0X7GD2X)

Figure 1.2 10/100/1000Base-T * 2ports (SE0X7GD1X)

- 4 -

Figure 1.3 10/100/1000Base-T * 4ports (SE0X7GQ1X)

Figure 1.4 10/100/1000Base-T * 4ports (SE0X7GQ2X)

- 5 -

Chapter 2 Gigabit Ethernet Card Installation

This chapter describes the tasks necessary to install this card in your system. Install the hardware with the following procedures.

- 2.1 Installation of the Gigabit Ethernet Card

- 2.2 Identifying the Gigabit Ethernet Card

- 2.3 Cable Connection

2.1 Installation of the Gigabit Ethernet Card

Insert the card into a PCI Express slot on your server. Please refer to the User's Manual of your server for details about installing cards and specific PCI Express slot specifications.

Information

- Even when the system works, the device can be dynamically installed by the PCI hot plug feature of Solaris (*1) if the server is one

of the SPARC Enterprise M4000/M5000/M8000/M9000. The device can be dynamically composed by executing the cfgadm(1M) command or hotplug(1M) command(Solaris 10 9/10 or later). For more information, refer to the "Service Manual" of your server, System Administration Guide:Basic Administration" of the Oracle Documentation and the "man pages section 1M:System Administration Commands" of the Oracle Documentation.

*1:The PCI hot plug feature of Solaris is feature that can be physically installed, detached or exchange the device while the system is working.

2.2 Identifying the Gigabit Ethernet Card

The Gigabit Ethernet card can be identified by executing the "boot -r" command at the ok prompt after installing it into the server.

ok boot -r

Information

- Also, even when the system works, the device can be dynamically identified by the PCI hot plug feature of Solaris if the server is one

2.3 Cable Connection

Figure 2.1 to 2.4 shows how to connect a cable to the Gigabit Ethernet card. Connect a multimode optical fiber cable to the connector of the SE0X7GD2X Gigabit Ethernet card. Connect a CAT5e (Enhanced Category 5) twisted pair cable to the connector of the SE0X7GD1X, SE0X7GQ1X and SE0X7GQ2X Gigabit

Ethernet cards.

- 6 -

Figure 2.1 SE0X7GD2X (with Multimode Optical Fiber Cable)

- 7 -

Figure 2.2 SE0X7GD1X (with Twisted Pair CAT5e Cable)

- 8 -

Figure 2.3 SE0X7GQ1X (with Twisted Pair CAT5e Cable)

- 9 -

Figure 2.4 SE0X7GQ2X (with Twisted Pair CAT5e Cable)

- 10 -

Chapter 3 Setting Instructions

This chapter describes the summary of environment settings required after installing this product. Install the driver and configure environment settings using the following procedures.

- 3.1 Driver Software Installation

- 3.2 Identification of Interface Name

- 3.3 Environment Setting

- 3.5 Operation Mode Setup

- 3.6 Network Installation

- 3.7 VLAN Interface Setup

3.1 Driver Software Installation

It is necessary to install the driver software stored on the CD-ROM that ships with the card to use this product. See the document "Installation Guide FUJITSU PCI GigabitEthernet 4.1 Update2 / 5.0" for installation procedures.

3.2 Identification of Interface Name

In Solaris 11, The interface name is changed into the form of "net*" from the form of "fjgi*" by Vanity Naming. This section explains how to identify the interface name of fjgi interface.

*1: Please put a decimal number (instance number) in place of the asterisk (*). See section "3.3 Environment Setting" for detailed information about instance number.

Execute the commands shown in the following examples.

dladm show-phys | grep fjgi

example:

# dladm show-phys | grep fjgi net2 Ethernet unknown 1000 unknown fjgi0 net3 Ethernet unknown 1000 unknown fjgi1 net4 Ethernet unknown 1000 unknown fjgi2 net5 Ethernet unknown 1000 unknown fjgi3

The installed fjgi interface and the interface name are displayed.

The interface name (Vanity Name, the form of "net*") fjgi interface (the form of "fjgi*")

net2 fjgi0 net3 fjgi1 net4 fjgi2 net5 fjgi3

In the above example, it is displayed that net2 is fjgi0, net3 is fjgi1, and net5 is fjgi3. In addition, The interface name can be changed by dladm rename-link command. For more information about the dladm(1M) command,

please refer to the "System Administration Guide: IP Services" and the "man pages section 1M: System Administration Commands" of Oracle Documentation.

- 11 -

3.3 Environment Setting

This section explains how to edit the necessary files and use the commands(Solari 11 only) to configure the operating environment for each FUJITSU PCI GigabitEthernet interface.

For TCP/IP (IPv4 or IPv6), edit the following files and execute the following command(Solaris 11 only).

- Solaris 10 8/07 or later

- /etc/hostname.

fjgi*

(*1) file

- /etc/inet/hosts file or /etc/inet/ipnodes file

- /etc/inet/netmasks file

*1: Please put a decimal number (instance number) in place of the asterisk (*). See section "3.3 Environment Setting" for detailed information about instance number.

- Solaris 11

- ipadm(1M) command

- /etc/hosts file

*1: For more information about the ipadm(1M) command, please refer to the "System Administration Guide: IP Services" and the "man pages section 1M: System Administration Commands" of Oracle Documentation.

3.3.1 Environment Setting of IPv4 Interfaces

- Solaris 10 8/07 or later

1. Edit the /etc/hostname.

Assign an IP address or hostname to the fjgi interface by editing the /etc/hostname.fjgi* file (where name and instance number).

The relationship between IP address and netmask needs to be defined using the procedure described in "3. Edit the /etc/inet/ netmasks file".

fjgi*

file

fjgi*

represents the driver

Example of the /etc/hostname.fjgi* file: Define a unique hostname (example: giga-v4). (*1)

giga-v4

Or define an IP address (example: 192.168.150.1). (*2)

192.168.150.1

*1: See section "2. Edit the /etc/inet/hosts file" for detailed information about defining the hostname. *2: Please put neither a blank nor an empty line behind the hostname or IP address. If a blank or an empty line has been

entered, the fjgj driver will not be activated during OS boot.

2. Edit the /etc/inet/hosts file

Define an IP address by a unique name. Describe the relationship between the IP address and hostname in the /etc/inet/hosts file.

Example of the /etc/inet/hosts file: Describe the relationship between an IP address (example: 192.168.150.1) and a hostname (example: giga-v4).

# IP Address Hostname

192.168.150.1 giga-v4

- 12 -

3. Edit the /etc/inet/netmasks file

Describe the relationship between the network address and the netmask in the /etc/inet/netmasks file. Example of the /etc/inet/netmasks file: Describe the relationship between the network address (example: 192.168.150.0) and the netmask (example: 255.255.255.0).

# Network Address netmask

192.168.150.0 255.255.255.0

4. Reboot the system

Reboot the system after editing the above files.

Solaris 11

1. How to Use the ipadm(1M) Command

Assign an IP address or hostname and prefix length to the fjgi interface by ipadm(1M) command. Example: Setup a unique hostname (example: giga-v4) and prefix length (example: 24) to fjgi interface (example: fjgi0 (this vanity name

is net2)). (*1)

# ipadm create-ip net2 # ipadm create-addr -T static -a giga-v4/24 net2/v4static

Or setup an IP address (example: 192.168.150.1) and prefix length (example: 24) to fjgi interface (example: fjgi0 (this vanity name is net2)).

# ipadm create-ip net2 # ipadm create-addr -T static -a 192.168.150.1/24 net2/v4static

*1: When you use a hostname, please see section "2. Edit the /etc/hosts file" first.

Information

- The following examples shows how to display an IP address and prefix length that assigned the fjgi interface.

Example: When setting an IP address (example: 192.168.150.1) and prefix length (example: 24) to fjgi interface (example: fjgi0 (this

vanity name is net2)).

# ipadm show-addr net2/v4static ADDROBJ TYPE STATE ADDR net2/v4static static ok 192.168.150.1/24

2. Edit the /etc/hosts file

Define an IP address by a unique name. Describe the relationship between the IP address and hostname in the /etc/hosts file. Example of the /etc/inet/hosts file: Describe the relationship between an IP address (example: 192.168.150.1) and a hostname (example: giga-v4).

# IP Address Hostname

192.168.150.1 giga-v4

- 13 -

3.3.2 Environment Setting of IPv6 Interfaces

- Solaris 10 8/07 or later

1. Edit the /etc/hostname6.

Assign an IPv6 address or hostname and prefix length to the fjgi interface by editing the /etc/hostname6.fjgi* file (where represents the driver name and instance number).

Example of the /etc/hostname6.fjgi* file: Define a unique hostname (example: giga-v6) and prefix length (example: 120). (*1)

addif giga-v6/120 up

Or define an IPv6 address (example: fe80::2e0:ff:fea6:2222) and prefix length (example: 120).

addif fe80::2e0:ff:fea6:2222/120 up

*1: See section "2. Edit the /etc/inet/ipnodes file" when you define a hostname in the /etc/hostname6.fjgi* file.

fjgi*

file

2. Edit the /etc/inet/ipnodes file

Define an IPv6 address by a unique name. Describe the relationship between the IPv6 address and the hostname in the /etc/inet/ ipnodes file.

Example of the /etc/inet/ipnodes file: Describe the relationship between the IPv6 address (example: fe80::2e0:ff:fea6:2222) and the hostname (example: giga-v6).

# IP Address Hostname fe80::2e0:ff:fea6:2222 giga-v6

fjgi*

3. Reboot the system

Reboot the system after editing the above files.

- Solaris 11

1. How to Use the ipadm(1M) Command

Assign an IP address or hostname and prefix length to the fjgi interface by ipadm(1M) command. Example: Setup a unique hostname (example: giga-v6) and prefix length (example: 120) to fjgi interface (example: fjgi0 (this vanity name

is net2)). (*1)

# ipadm create-ip net2 # ipadm create-addr -T addrconf net2/v6addrconf # ipadm create-addr -T static -a giga-v6/24 net2/v4static

Or setup an IP address (example: fe80::2e0:ff:fea6:2222) and prefix length (example: 120) to fjgi interface (example: fjgi0 (this vanity name is net2)).

# ipadm create-ip net2 # ipadm create-addr -T addrconf net2/v6addrconf # ipadm create-addr -T static -a fe80::2e0:ff:fea6:2222/120 net2/v6static

*1: When you use a hostname, please see section "2. Edit the /etc/hosts file" first.

- 14 -

Information

- The following example shows how to display an IP address and prefix length that assigned the fjgi interface.

Example: When setting an IP address (example: 192.168.150.1) and prefix length (example: 24) to fjgi interface (example: fjgi0 (this

vanity name is net2)).

# ipadm show-addr net2/v4static ADDROBJ TYPE STATE ADDR net2/v6static static ok fe80::2e0:ff:fea6:2222/120

2. Edit the /etc/hosts file

Define an IPv6 address by a unique name. Describe the relationship between the IPv6 address and the hostname in the /etc/inet/ ipnodes file.

Example of the /etc/hosts file: Describe the relationship between the IPv6 address (example: fe80::2e0:ff:fea6:2222) and the hostname (example: giga-v6).

# IP Address Hostname fe80::2e0:ff:fea6:2222 giga-v6

Information

- In Solaris 10 8/07 or later, to delete the environment settings, please delete each of the settings made in the procedures described in

"3.3.1 Environment Setting of IPv4 Interfaces" and "3.3.2 Environment Setting of IPv6 Interfaces" from the files.

- In Solaris 11, to delete the environment settings, please execute the following ipadm(1M) commnad and delete each of the settings

made in the procedures described in "3.3.1 Environment Setting of IPv4 Interfaces" and "3.3.2 Environment Setting of IPv6

Interfaces" from the files.

Example:

# ipadm delete-ip net2

- To use VLAN interfaces, please refer first to "3.7.2 Setting Up the VLAN Interface" to define the interface name. Then, please carry

out the procedures described in "3.3.1 Environment Setting of IPv4 Interfaces" or "3.3.2 Environment Setting of IPv6 Interfaces".

3.4 Identification of the Gigabit Ethernet Card

This section explains how to identify a slot in which the Gigabit Ethernet card has been installed, on SPARC Enterprise. Execute the commands shown in the following examples.

- Identification of the Gigabit Ethernet Card Types and Instance Number

prtconf -D | grep fjgi

example:

# prtconf -D | grep fjgi FJSV,e4ta, instance #0 (driver name: fjgi) FJSV,e4ta, instance #1 (driver name: fjgi) FJSV,e4ta, instance #2 (driver name: fjgi) FJSV,e4ta, instance #3 (driver name: fjgi) FJSV,e2sa, instance #4 (driver name: fjgi) FJSV,e2sa, instance #5 (driver name: fjgi)

- 15 -

FJSV,e2ta, instance #6 (driver name: fjgi) FJSV,e2ta, instance #7 (driver name: fjgi) FJSV,e4tb, instance #8 (driver name: fjgi) FJSV,e4tb, instance #9 (driver name: fjgi) FJSV,e4tb, instance #10 (driver name: fjgi) FJSV,e4tb, instance #11 (driver name: fjgi)

The installed Gigabit Ethernet card types and instance numbers (shown in bold, above) are displayed.

Gigabit Ethernet card types:

FJSV,e4ta SE0X7GQ1X (10/100/1000Base-T * 4ports) card FJSV,e2sa SE0X7GD2X (1000BASE-SX * 2ports) card FJSV,e2ta SE0X7GD1X (10/100/1000BASE-T * 2ports) card FJSV,e4tb SE0X7GQ2X (10/100/1000BASE-T * 4ports) card

In this example, the following types of installed Gigabit Ethernet cards can be identified: e4ta (SE0X7GQ1X), e2sa (SE0X7GD2X), e2ta (SE0X7GD1X) and e4tb (SE0X7GQ2X).

Instance numbers: In this example, the following instance numbers of installed Gigabit Ethernet cards can be identified:

e4ta: 0, 1, 2, 3 e2sa: 4, 5 e2ta: 6, 7 e4tb: 8, 9, 10, 11

- Identification of Slots with Installed Gigabit Ethernet Cards

more /etc/path_to_inst | grep fjgi

example:

# more /etc/path_to_inst | grep fjgi "/pci@1,700000/pci@0/FJSV,e4ta@4" 0 "fjgi" "/pci@1,700000/pci@0/FJSV,e4ta@4,1" 1 "fjgi" "/pci@1,700000/pci@0,1/FJSV,e4ta@6" 2 "fjgi" "/pci@1,700000/pci@0,1/FJSV,e4ta@6,1" 3 "fjgi" "/pci@2,600000/pci@0/FJSV,e2sa@4" 4 "fjgi" "/pci@2,600000/pci@0/FJSV,e2sa@4,1" 5 "fjgi" "/pci@3,700000/pci@0/FJSV,e2ta@4" 6 "fjgi" "/pci@3,700000/pci@0/FJSV,e2ta@4,1" 7 "fjgi" "/pci@4,600000/pci@0/FJSV,e4tb@4" 8 "fjgi" "/pci@4,600000/pci@0/FJSV,e4tb@4,1" 9 "fjgi" "/pci@4,600000/pci@0,1/FJSV,e4tb@6" 10 "fjgi" "/pci@4,600000/pci@0,1/FJSV,e4tb@6,1" 11 "fjgi"

The installed logical bus addresses and the instance numbers (shown in bold, above) are displayed.

Identification of the logical bus addresses, instance numbers and driver name for each interface:

Logical bus address Instance number Driver name

"/pci@1,700000/pci@0/FJSV,e4ta@4" 0 fjgi "/pci@1,700000/pci@0/FJSV,e4ta@4,1" 1 fjgi "/pci@1,700000/pci@0,1/FJSV,e4ta@6" 2 fjgi

- 16 -

Logical bus address Instance number Driver name

"/pci@1,700000/pci@0,1/FJSV,e4ta@6,1" 3 fjgi "/pci@3,700000/pci@0/FJSV,e2sa@4" 4 fjgi "/pci@3,700000/pci@0/FJSV,e2sa@4,1" 5 fjgi "/pci@2,600000/pci@0/FJSV,e2ta@4" 6 fjgi "/pci@2,600000/pci@0/FJSV,e2ta@4,1" 7 fjgi "/pci@4,600000/pci@0/FJSV,e4tb@4" 8 fjgi "/pci@4,600000/pci@0/FJSV,e4tb@4,1" 9 fjgi "/pci@4,600000/pci@0,1/FJSV,e4tb@6" 10 fjgi "/pci@4,600000/pci@0,1/FJSV,e4tb@6,1" 11 fjgi

The relationship of logical bus addresses to physical slot numbers differs in each server. To determine the relationship, please refer to "Appendix G PCI Slot Number and Device Name".

3.5 Operation Mode Setup

This section explains how to edit the fjgi.conf configuration file or use the command line to change the operation mode of FUJITSU PCI GigabitEthernet interfaces. Setup of the following operation modes are described below.

- 3.5.1 Setting the fjgi.conf File

- 3.5.2 JumboFrame Setup

- 3.5.3 Using the ndd(1M) command

- 3.5.4 Using the dladm(1M) command

- 3.5.5 FCode Settings

3.5.1 Setting the fjgi.conf File

Usually, setup of the fjgi.conf file is unnecessary. Default settings are appropriate in most environments. The following examples show cases when the fjgi.conf file needs to be modified. Example:

- When the remote device does not support Auto-Negotiation.

In this case, please set the same mode of operation for the local and remote devices.

- When Auto-Negotiation is used, but it is desirable to use a specific setting value, different from the default value (for example, when

you want to set the speed to 100Mbps in order to keep the CPU load by the network low).

- When JumboFrame is used.

For details, please refer to "3.5.2 JumboFrame Setup". Using Auto-Negotiation (the default settings) is recommended for speed, duplex, and flow control. To change the operation mode, there are two methods; "Method 1: Setting method of new style" and "Method 2: Setting method of old

style". When there is a mistake in parent and unit-address setting by the "Method 2", warning messages may be displayed repeatedly. Therefore the "Method 1: Setting method of new style" is recommended.

When editing the fjgi.conf file, please review the [Cautions] in the following sections.

- Method 1: Setting method of new style (Recommended) [Parameter List]

- 17 -

Parameter Value Description

LinkSpeed_A (*1)

DuplexCapabilities_A (*1)

Any connection speed of 1000, 100, or 10

Auto (default)

1000 100 Connect at 100Mbps. 10 Connect at 10Mbps.

Both (default)

Half Full Full-Duplex operation is enabled.

Mbps is set based on negotiation with the remote device. (This is effective only when AutoNegotiation_A=On.)

Connect at 1000Mbps.

Both Full-Duplex and Half-Duplex are enabled. (This is effective only when AutoNegotiation_A=On.)

Half-Duplex operation is enabled.

Auto (default)

Rem

FlowControl_A (*2)

LocSend

None

fjgi_mtu 1500 (default) to 9000 (*3) MTU (byte) is specified.

On (default)

AutoNegotiation_A

Off

Auto (default)

Role_A (*4)

Flow control is performed according to the setup of the remote device.

Only flow control from the remote device is allowed. Flow control from the local device is not allowed.

Only flow control from the local device is allowed. Flow control from the remote device is not allowed.

Flow control is disabled.

Auto-Negotiation is enabled. The interface will not be able to communicate with remote device operating in fixed mode (Auto-Negotiation disabled). When SE0X7GD1X, SE0X7GQ1X, SE0X7GQ2X is used in 1000Mbps mode, use this setting.

Auto-Negotiation is disabled. (Forced mode)

Master or Slave is set based on negotiation with the remote device. (This is effective only when AutoNegotiation_A= On.)

ReceiveTicks

TransmitTicks

ReceiveMaxBD

Master Slave Communication by Slave. 0 to 1000 (*3)

(default: 77)

0 to 1000 (*3) (default: 500)

1 to 500 (*3) (default: 10)

- 18 -

Communication by Master.

Time to wait for an interrupt for receiving is specified (micro seconds). (*5)

Time to wait for an interrupt for transmitting is specified (micro seconds). (*5)

The number of buffer descriptor to wait for an interrupt for receiving is specified. (*5)

Parameter Value Description

TransmitMaxBD

fjgi* (*6)

*1: Parameter is supported on 10/100/1000Base-T (SE0X7GD1X, SE0X7GQ1X, SE0X7GQ2X) adapters only. *2: Parameter is effective only when AutoNegotiation_A=On. When AutoNegotiation_A=Off, it becomes FlowControl_A=None. *3: Specify the value as a decimal figure. *4: Parameter is supported on 10/100/1000Base-T (SE0X7GD1X, SE0X7GQ1X, SE0X7GQ2X) adapters in 1000Mbps mode only. *5: These ReceiveTicks, TransmitTicks, ReceiveMaxBD or TransmitMaxBD parameters are tuning parameters about the performance. *6: Please put a decimal number (instance number) in place of the asterisk (

The fjgi* parameter is used prior to parameters to all instances if the fjgi parameter is specified with LinkSpeed_A, DuplexCapabilities_A, FlowControl_A, fjgi_mtu, AutoNegotiation_A, Role_A, ReceiveTicks, TransmitTicks, ReceiveMaxBD or TransmitMaxBD parameters.

1 to 500 (*3) (default: 128)

<LinkSpeed_A> :<DuplexCapabilities_A> :<FlowControl_A> :<fjgi_mtu> :<AutoNegotiation_A> :<Role_A> :<ReceiveTicks> :<TransmitTicks> :<ReceiveMaxBD> :<TransmitMaxBD> (*7)

The number of buffer descriptor to wait for an interrupt for transmitting is specified. (*5)

Parameter setting values are specified for every instance. Refer to the description of each parameter for the meaning of each value.

*7: The default values are used when setting values are omitted.

[Parameter Setting]

The following examples show how to set the fjgi.conf file.

- The location of the fjgi.conf file depends on the model of the host system as described below:

1. SPARC Enterprise Txxxx series and SPARC T3 series

/platform/sun4v/kernel/drv/fjgi.conf

2. SPARC Enterprise Mxxxx series

/platform/SUNW,SPARC-Enterprise/kernel/drv/fjgi.conf

- How to set a parameter to all instances

Example 1: The parameters for all instances are set to "Auto-Negotiation is disabled", "Connect at 100Mbps" and "Half-Duplex

operation is enabled".

The parameter values need to be set by character strings like AutoNegotiation_A="Off", LinkSpeed_A="100" and

DuplexCapabilities_A="Half".

The following is added to the fjgi.conf file:

AutoNegotiation_A="Off"

LinkSpeed_A="100"

DuplexCapabilities_A="Half";

Example 2: The parameters for all instances are set to "Auto-Negotiation is enabled", "Connect at 100Mbps" and "Full-Duplex

operation is enabled".

- 19 -

The parameter values need to be set by character strings like AutoNegotiation_A="On", LinkSpeed_A="100" and

DuplexCapabilities_A="Full".

The following is added to the fjgi.conf file:

AutoNegotiation_A="On"

LinkSpeed_A="100"

DuplexCapabilities_A="Full";

Example 3: The MTU parameter for all instances is set to 8000.

The parameter value needs to be set by numerical value like fjgi_mtu=8000.

The following is added to the fjgi.conf file:

fjgi_mtu=8000;

Note: After making changes to the fjgi.conf file, the system must be rebooted. The settings become effective after rebooting.

- How to set a parameter to each instance

Example 1: The parameters for fjgi0 is set to "Auto-Negotiation is disabled", "Connect at 100Mbps" and "Half-Duplex operation is

enabled".

The parameter value needs to be set by a character string like fjgi0="100:Half:::Off:::::".

The following is added to the fjgi.conf file:

fjgi0="100:Half:::Off:::::";

Example 2: The parameters for fjgi1 is set to "Auto-Negotiation is disabled", "Connect at 100Mbps" and "Half-Duplex operation is

enabled".

The parameter value needs to be set by a character string like fjgi1="100:Half:Auto:1500:Off:Auto::::".

The following is added to the fjgi.conf file:

fjgi1="100:Half:Auto:1500:Off:Auto::::";

Example 3: The parameters for fjgi0 is set to "Auto-Negotiation is enabled", "Connect at 100Mbps" and "Full-Duplex operation is

enabled".

The parameter value needs to be set by a character string like fjgi0="100:Full:::On:::::".

The following is added to the fjgi.conf file:

fjgi0="100:Full:::On:::::";

Example 4: The parameters for fjgi1 is set to "Auto-Negotiation is enabled", "Connect at 100Mbps" and "Full-Duplex operation is

enabled".

The parameter value needs to be set by a character string like fjgi1="100:Full:Auto:1500:On:Auto::::".

The following is added to the fjgi.conf file:

fjgi1="100:Full:Auto:1500:On:Auto::::";

Example 5: The MTU parameter for fjgi0 is set to 8000.

- 20 -

The parameter value needs to be set by a character string like fjgi0=":::8000::::::".

The following is added to the fjgi.conf file:

fjgi0=":::8000::::::";

Example 6: The MTU parameter for fjgi1 is set to 8000.

The parameter value needs to be set by a character string like fjgi1="Auto:Both:Auto:8000:On:Auto::::".

The following is added to the fjgi.conf file:

fjgi1="Auto:Both:Auto:8000:On:Auto::::";

Note: After making changes to the fjgi.conf file, the system must be rebooted. The settings become effective after rebooting.

- How to set parameters to all instances and to each instance

Example 1: The MTU parameter for all instances is set to 1500 and the MTU parameter for fjgi0 is set to 8000.

In this case, the MTU of fjgi0 is 8000, and the MTU of other instances is 1500.

The following is added to the fjgi.conf file:

fjgi_mtu=1500;

fjgi0=":::8000::::::";

Note: After making changes to the fjgi.conf file, the system must be rebooted. The settings become effective after rebooting.

- Method 2: Setting method of old style [Parameter List]

Parameter Value Description

name fjgi Used to specify the driver name.

parent See below

unit-address See below

Auto (default)

LinkSpeed_A (*1)

1000 100 Connect at 100Mbps. 10 Connect at 10Mbps.

Both (default)

DuplexCapabilities_A (*1)

Half

Used to specify the location of the device node in the device tree.

Used to specify the address within the device node.

Any connection speed of 1000, 100, or 10 Mbps is set based on negotiation with the remote device. (This is effective only when AutoNegotiation_A=On.)

Connect at 1000Mbps.

Both Full-Duplex and Half-Duplex are enabled. (This is effective only when AutoNegotiation_A=On.)

Half-Duplex operation is enabled.

FlowControl_A (*2)

Full Full-Duplex operation is enabled.

Auto (default)

- 21 -

Flow control is performed according to the setup of the remote device.

Parameter Value Description

Only flow control from the remote device

Rem

LocSend

is allowed. Flow control from the local device is not allowed.

Only flow control from the local device is allowed. Flow control from the remote device is not allowed.

None

fjgi_mtu 1500 (default) to 9000 (*3) MTU (byte) is specified.

On (default)

AutoNegotiation_A

Off

Auto (default)

Role_A (*4)

Master Slave Communication by Slave.

ReceiveTicks 0 to 1000 (*3)

(default: 77)

TransmitTicks 0 to 1000 (*3)

(default: 500)

Flow control is disabled.

Auto-Negotiation is disabled. (Forced mode)

Master or Slave is set based on negotiation with the remote device. (This is effective only when AutoNegotiation_A= On.)

Communication by Master.

Time to wait for an interrupt for receiving is specified (micro seconds). (*5)

Time to wait for an interrupt for transmitting is specified (micro seconds). (*5)

ReceiveMaxBD 1 to 500 (*3)

(default: 10)

TransmitMaxBD 1 to 500 (*3)

(default: 128)

The number of buffer descriptor to wait for an interrupt for receiving is specified. (*5)

The number of buffer descriptor to wait for an interrupt for transmitting is specified. (*5)

[Parameter Setting]

The following shows how to set the parent and unit-address parameters in the fjgi.conf file.

- Find the fjgi device tree, device node and instance number in the /etc/path_to_inst file.

Example:

- 22 -

+ 65 hidden pages

Fujitsu C120-E276-11ENZ0A User Manual

Preface

Revision History

Contents

Chapter 1 Product Outline

1.1 Key Features

1.2 Gigabit Ethernet Card Specifications

1.2.1 Specifications

1.2.2 Part Names and Features of Hardware

Chapter 2 Gigabit Ethernet Card Installation

2.1 Installation of the Gigabit Ethernet Card

2.2 Identifying the Gigabit Ethernet Card

2.3 Cable Connection

Chapter 3 Setting Instructions

3.1 Driver Software Installation

3.2 Identification of Interface Name

3.3 Environment Setting

3.3.1 Environment Setting of IPv4 Interfaces

3.3.2 Environment Setting of IPv6 Interfaces

3.4 Identification of the Gigabit Ethernet Card

3.5 Operation Mode Setup

3.5.1 Setting the fjgi.conf File