Download Print this page

Fujitsu PCI Gigabit Ethernet User Manual

4.1 update2 / 5.0 for oracle solaris.
Hide thumbs

Advertisement

FUJITSU PCI Gigabit Ethernet
4.1 Update2 / 5.0
for Oracle Solaris
User's Guide
Solaris
C120-E276-11ENZ0(A)
October 2011
SPARC Enterprise

Advertisement

   Related Manuals for Fujitsu PCI Gigabit Ethernet

   Summary of Contents for Fujitsu PCI Gigabit Ethernet

  • Page 1

    FUJITSU PCI Gigabit Ethernet 4.1 Update2 / 5.0 for Oracle Solaris User's Guide Solaris C120-E276-11ENZ0(A) October 2011 SPARC Enterprise...

  • Page 2

    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.

  • Page 3: Revision History

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

  • Page 4

    Edition Date Details Support switches was added Changed the Version 2.1 to 2.2 Quad Gigabit Ethernet card(PW008QG1) was supported 2005-11-11 Changed the Version 2.2 to 2.3 RoHS compliant 1port Gigabit Ethernet Card(PW0G8GE1, PW0G8GE2) was supported 2006-2-06 Changed the Version 2.3 to 2.4 PCI Express Gigabit Ethernet Card(SE0X7GD1X, SE0X7GD2X, SE0X7CQ1X) was supported 2007-1-20...

  • Page 5: Table Of Contents

    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 Notes.........................................66 Appendix D Using FUJITSU PCI GigabitEthernet in Solaris Containers................67...

  • Page 6

    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 Notes........................................75 Appendix F Using FUJITSU PCI GigabitEthernet in Solaris 11 Network Virtualization............76 F.1 Solaris 11 Network Virtualization...

  • Page 7: Chapter 1 Product Outline

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

  • Page 8: Gigabit Ethernet Card Specifications

    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.

  • Page 9: Part Names And Features Of Hardware

    Item Hardware Specification Maximum: 9.1W (SE0X7GD1X), 9.2W (SE0X7GD2X), Power Requirements 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.), LC- Connections LC: 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.)

  • Page 10

    Figure 1.1 1000Base-SX * 2ports (SE0X7GD2X) Figure 1.2 10/100/1000Base-T * 2ports (SE0X7GD1X) - 4 -...

  • Page 11

    Figure 1.3 10/100/1000Base-T * 4ports (SE0X7GQ1X) Figure 1.4 10/100/1000Base-T * 4ports (SE0X7GQ2X) - 5 -...

  • Page 12: Chapter 2 Gigabit Ethernet Card Installation

    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.

  • Page 13

    Figure 2.1 SE0X7GD2X (with Multimode Optical Fiber Cable) - 7 -...

  • Page 14

    Figure 2.2 SE0X7GD1X (with Twisted Pair CAT5e Cable) - 8 -...

  • Page 15

    Figure 2.3 SE0X7GQ1X (with Twisted Pair CAT5e Cable) - 9 -...

  • Page 16

    Figure 2.4 SE0X7GQ2X (with Twisted Pair CAT5e Cable) - 10 -...

  • Page 17: Chapter 3 Setting Instructions

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

  • Page 18: 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).

  • Page 19

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

  • Page 20: Environment Setting Of Ipv6 Interfaces

    3.3.2 Environment Setting of IPv6 Interfaces Solaris 10 8/07 or later fjgi* file 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 fjgi* 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).

  • Page 21: Identification Of The Gigabit Ethernet Card

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

  • Page 22

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

  • Page 23: Operation Mode Setup

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

  • Page 24

    Parameter Value Description Any connection speed of 1000, 100, or 10 Mbps is set based on negotiation with the Auto (default) remote device. (This is effective only when AutoNegotiation_A=On.) LinkSpeed_A (*1) 1000 Connect at 1000Mbps. Connect at 100Mbps. Connect at 10Mbps. Both Full-Duplex and Half-Duplex are Both (default) enabled.

  • Page 25

    Parameter Value Description The number of buffer descriptor to wait 1 to 500 (*3) TransmitMaxBD for an interrupt for transmitting is (default: 128) specified. (*5) <LinkSpeed_A> :<DuplexCapabilities_A> :<FlowControl_A> :<fjgi_mtu> Parameter setting values are specified for :<AutoNegotiation_A> every instance. fjgi* (*6) :<Role_A>...

  • Page 26

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

  • Page 27

    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::::";...

  • Page 28

    Parameter Value Description 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 LocSend allowed. Flow control from the remote device is not allowed. None Flow control is disabled.

  • Page 29

    From the above example, instance number and driver name for each interface can be determined. Device node of device tree Instance number Driver name /pci@1,700000/pci@0/FJSV,e4ta@4 fjgi /pci@1,700000/pci@0/FJSV,e4ta@4,1 fjgi /pci@1,700000/pci@0,1/FJSV,e4ta@6 fjgi /pci@1,700000/pci@0,1/FJSV,e4ta@6,1 fjgi /pci@2,600000/pci@0/FJSV,e2sa@4 fjgi /pci@2,600000/pci@0/FJSV,e2sa@4,1 fjgi /pci@3,700000/pci@0/FJSV,e2ta@4 fjgi /pci@3,700000/pci@0/FJSV,e2ta@4,1 fjgi /pci@4,600000/pci@0/FJSV,e4tb@4 fjgi /pci@4,600000/pci@0/FJSV,e4tb@4,1...

  • Page 30

    SE0X7GD1X name fjgi parent /pci@3,700000/pci@0 instance 6 is 4 unit-address instance 7 is 4,1 SE0X7GQ2X name fjgi parent /pci@4,600000/pci@0 /pci@4,600000/pci@0,1 instance 8 is 4 instance 10 is 6 unit-address instance 9 is 4,1 instance 11 is 6,1 The location of the fjgi.conf file depends on the model of the host system as described below: SPARC Enterprise Txxxx series and SPARC T3 series /platform/sun4v/kernel/drv/fjgi.conf SPARC Enterprise Mxxxx series...

  • Page 31

    Example 4: The parameters for all instances are 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 AutoNegotiation_A="Off", LinkSpeed_A="100", DuplexCapabilities_A="Half". The following is added to the fjgi.conf file: AutoNegotiation_A="Off";...

  • Page 32: Jumboframe Setup

    When "Method 1: Setting method of new style" and "Method 2: Setting method of old style" are specified at the same time, the driver gives priority to the "Method 1: Setting method of new style". And when "How to set a parameter to all instances" and "How to set a parameter to each instance"...

  • Page 33

    Reboot the system. - Method 3: Specify in dladm(1M) command This method can be used only by FUJITSU PCI GigabitEthernet 5.0 or later. When MTU settings must be individually set for each interface without reboot, please use this method. Refer to the "3.5.1 Setting the fjgi.conf...

  • Page 34: Using The Ndd(1m) Command

    This method is not supported by FUJITSU PCI GigabitEthernet 5.0 or later. Example You changed a remote device from one which supports Auto-Negotiation to another which does not support Auto-Negotiation or vice versa after system startup.

  • Page 35

    # ndd -set /dev/fjgi0 adv_1000fdx_cap 0 # ndd -set /dev/fjgi0 adv_1000hdx_cap 0 # ndd -set /dev/fjgi0 adv_autoneg_cap 0 # ndd -set /dev/fjgi0 adv_autoneg_cap 1 (Note) The last two commands above change the Auto-Negotiation setting, then change the setting back. This causes the Link Status to change, and is required to make the settings effective.

  • Page 36

    Parameter Status Meaning 10Mbps/FullDuplex Setting adv_10fdx_cap Read and write 0: Disabled 1: Enabled (default) 10Mbps/HalfDuplex Setting adv_10hdx_cap Read and write 0: Disabled 1: Enabled (default) 100Mbps/FullDuplex Setting adv_100fdx_cap Read and write 0: Disabled 1: Enabled (default) 100Mbps/HalfDuplex Setting adv_100hdx_cap Read and write 0: Disabled 1: Enabled (default) 1000Mbps/FullDuplex Setting...

  • Page 37

    Parameter Status Meaning Set link-partner to transmit pause frame by Auto-Negotiation. lp_pauseTX Read only 0: Disabled 1: Enabled Set link-partner to receive pause frame by Auto-Negotiation. lp_pauseRX Read only 0: Disabled 1: Enabled Set link-partner to Auto-Negotiate. lp_autoneg_cap Read only 0: Disabled 1: Enabled The current Role setting when operating at 1000Mbps.

  • Page 38: Using The Dladm(1m) Command

    This method can be used only by FUJITSU PCI GigabitEthernet 5.0 or later. Example: You changed a remote device from one which supports Auto-Negotiation to another which does not support Auto-Negotiation or vice versa after system startup.

  • Page 39

    Propertiy Status Meaning Auto-Negotiation Setting adv_autoneg_cap Read and write 0: Auto-Negotiation Off (Forced mode) 1: Auto-Negotiation On (default) MTU (byte) Setting mtu (*1) Read and write 1500 to 9000 (default: 1500) Flow_Control Setting no: None (flow_control disabled) tx: Local Send (Can transmit pause frame only) rx: Remote Send (Can receive pause frame only) flowctrl Read and write...

  • Page 40

    Propertiy Status Meaning 0: SX (SE0X7GD2X) _cardtype (*2) Read only 1: T (SE0X7GD1X/SE0X7GQ1X/SE0X7GQ2X) Role setting when operating at 1000Mbps. (used with SE0X7GD1X/ SE0X7GQ1X/SE0X7GQ2X only) _Role_A (*2) Read and write 0: Slave 1: Master 2: Auto (default) Time to wait for an interrupt for receiving is specified (micro seconds).

  • Page 41: Fcode Settings

    3.5.5 FCode Settings FCode settings must be changed when the remote device does not support Auto-Negotiation and the communication by FCode is needed (example: Network Installation). FCode changes are not required for Network Installation if the remote device supports Auto-Negotiation. Use the following procedure and examples to change FCode settings.

  • Page 42

    Execute the following command to set Half Duplex communication, 10Mbps. ok transfer-speed=10 ok half-duplex Execute the following command to display the current settings. ok .properties The following example shows the current settings of a SE0X7GD1X card installed in a SPARC Enterprise M9000. {6} ok cd /pci@4,600000/pci@0/FJSV,e2ta@4 {6} ok .properties duplex...

  • Page 43: Network Installation

    - How to Return to Default FCode Settings (Auto-Negotiation Mode): To return to default FCode settings, execute the following command from the ok prompt, or power cycle the system. ok reset-all 3.6 Network Installation Install Server Build Guide I/O Device Driver (SPARC Enterprise) " for the installation procedure. See the document "...

  • Page 44: Setting Up The Vlan Interface

    The FUJITSU PCI GigabitEthernet 4.1 or later drivers support: Supported VIDs 1 - 4094 Max number of VLAN interfaces 1024 3.7.2 Setting Up the VLAN Interface The VLAN interface is set up using the following procedures. By setting the interface number to 1000 or greater, it is possible to distinguish VLAN interfaces from physical interfaces.

  • Page 45

    To create a VLAN Interface of VID=231 for fjgi3 (this vanity name is net5), the following is used. Refer to "3.3 Environment Setting", and perform the procedure described. Use net231005 as the driver name. dladm create-vlan -l ether-link -v vid Example: # dladm create-vlan -l net5 -v 231 VLAN interfaces are displayed by the following command.

  • Page 46: Chapter 4 Linkaggregation Feature

    Chapter 4 LinkAggregation Feature This chapter outlines the LinkAggregation feature, and explains the settings required to use this feature. 4.1 About LinkAggregation Feature 4.2 Configuration of the LinkAggregation Feature 4.3 Notes 4.1 About LinkAggregation Feature This section explains the LinkAggregation feature. - LinkAggregation Feature Communication bandwidth and network redundancy (*1) can be improved by grouping two or more network interfaces as one virtual interface (*2).

  • Page 47

    LAN switch that supports the LinkAggregation (or equivalent) feature - Data Distribution Mode "Table 4.2 Data Distribution Mode" shows data distribution modes that FUJITSU Gigabit Ethernet 4.1 or later supports. Table 4.2 Data Distribution Mode The driver decides on the destination NIC based on the MAC (L2) header of sent data and sends the data to the destination.

  • Page 48: Configuration Of The Linkaggregation Feature

    This mode is used for re-configuring the LinkAggregation Group of the partner device automatically when the configuration of the LinkAggregation Group of the local device is changed. Also, the driver does not need to transmit the LACP for cases when the local device functions as a router, or the partner device does not implement LACP.

  • Page 49: Create A Linkaggregation (dladm Create-aggr)

    Note 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. 4.2.1.1 Create a LinkAggregation (dladm create-aggr) This section explains the dladm create-aggr command for activating LinkAggregation. - Synopsis Solaris 10 8/07 or later /usr/sbin/dladm create-aggr -d dev [-d dev] ...

  • Page 50

    Create the LinkAggregation Group Solaris 10 8/07 or later The following example shows how to create the LinkAggregation Group with the fjgi0, fjgi1 and fjgi2 interfaces and "key=1": # /usr/sbin/dladm create-aggr -d fjgi0 -d fjgi1 -d fjgi2 1 Solaris 11 The following example shows how to create the LinkAggregation Group with the fjgi0(this vanity name is net2), fjgi1(this vanity name is net3) and fjgi2(this vanity name is net4) interfaces and "aggr-link=aggr1": # /usr/sbin/dladm create-aggr -l net2 -l net3 -l net4 aggr1...

  • Page 51

    Describe the hostname in the /etc/hostname.aggr1 file. Example (Hostname is giga-lacp.): # cat /etc/hostname.aggr1 giga-lacp Define the relation between the IP address and the hostname in the /etc/inet/hosts file. Example (Hostname is giga-lacp and its IP address is 192.168.150.1): # cat /etc/inet/hosts 192.168.150.1 giga-lacp Reboot the system.

  • Page 52

    Define the relation between the IP address and the hostname in the /etc/inet/hosts file. Example (Hostname is giga-lacp and its IP address is 192.168.150.1): # cat /etc/hosts 192.168.150.1 giga-lacp Setup the hostname and prefix length to aggr1 by ipadm(1M) command. Example (Hostname is giga-lacp and prefix length is 24): # ipadm create-ip aggr1 # ipadm create-addr -T static -a giga-lacp/24 aggr1/v4static...

  • Page 53: Delete A Linkaggregation (dladm Delete-aggr)

    4.2.1.2 Delete a LinkAggregation (dladm delete-aggr) This section explains the dladm delete-aggr command for inactivating LinkAggregation. - Synopsis Solaris 10 8/07 or later /usr/sbin/dladm delete-aggr key key: Specify the key number to identify the LinkAggregation Group Specify a number ranging from 1 to 999. Solaris 11 /usr/sbin/dladm delete-aggr aggr-link aggr-link: The name of the representative interface.

  • Page 54: Modify A Linkaggregation (dladm Modify-aggr)

    Delete the LinkAggregation Group Solaris 10 8/07 or later The following example shows how to delete the "key=1" LinkAggregation Group (*3): # /usr/sbin/dladm delete-aggr 1 *3: Before deleting the LinkAggregation Group, please inactivate the LinkAggregation Group and stop the LinkAggregation. Solaris 11 The following example shows how to delete the "aggr-link=aggr1"...

  • Page 55

    passive: passive mode off: off mode -T time: Specify the LACP timer short: every one second long: every 30 seconds aggr-link: The name of the representative interface. - Description Modifies a LinkAggregation Group. - Exit Code 0: normal end. >0: abnormal end. - Example Processes to modify the policy of a LinkAggregation Group are shown below.

  • Page 56: Add Interfaces To A Linkaggregation (dladm Add-aggr)

    4.2.1.4 Add Interfaces to a LinkAggregation (dladm add-aggr) This section explains the dladm add-aggr command for adding interfaces to a LinkAggregation. - Synopsis Solaris 10 8/07 or later /usr/sbin/dladm add-aggr -d dev [-d dev] ... key -d dev: Specify the name of the physical interface (including instance number) to belong to a LinkAggregation Group You can specify devices belonging to the LinkAggregation Group until the number of them becomes 255.

  • Page 57: Remove Interfaces From A Linkaggregation (dladm Remove-aggr)

    Solaris 10 8/07 or later The following example shows how to add the interface "fjgi3" to the "key=1" LinkAggregation Group: # /usr/sbin/dladm add-aggr -d fjgi3 1 Solaris 11 The following example shows how to add the interface "fjgi3"(this vanity name is net5) to the "agg-link=aggr1" LinkAggregation Group: # /usr/sbin/dladm add-aggr -l net5 aggr1 Note...

  • Page 58

    - Synopsis Solaris 10 8/07 or later /usr/sbin/dladm remove-aggr -d dev [-d dev] ... key -d dev: Specify the name of the physical interface (including instance number) to belong to a LinkAggregation Group You can specify devices belonging to the LinkAggregation Group until the number of them becomes one.

  • Page 59: Display Linkaggregation Statistics And Information (dladm Show-aggr)

    Solaris 10 8/07 or later The following example shows how to remove the interface "fjgi2" from the "key=1" LinkAggregation Group: # /usr/sbin/dladm remove-aggr -d fjgi2 1 Solaris 11 The following example shows how to remove the interface "fjgi2"(this vanity name is net4) from the "aggr-link=aggr1" LinkAggregation Group: # /usr/sbin/dladm remove-aggr -l net4 aggr1 Note...

  • Page 60

    - Synopsis Solaris 10 8/07 or later /usr/sbin/dladm show-aggr [-s [-i interval]] [-L] [key] -s: Specify to display the statistics. -i interval: Specify the interval in seconds to report the statistics (Differences from the preceding screen are displayed when statistics are displayed multiple times.) Displays an accumulated value only once if the interval is omitted or 0 is specified.

  • Page 61

    The following example shows how to display the detailed LinkAggregation Information for the "key=1" LinkAggregation Group: # /usr/sbin/dladm show-aggr -L 1 key: 1 (0x0001) policy: L4 address: 0:0:77:9f:3c:d5 (auto) LACP mode: active LACP timer: short device activity timeout aggregatable sync coll dist defaulted expired fjgi1 active...

  • Page 62: Notes

    aggr1 net3 16.03K 18.82K aggr1 net4 15.62K 18.94K *: net2, net3, and net4 are the vanity name of fjgi0, fjgi1, and fjgi2, respectively. Note For more information about this command, please refer to the "man pages section 1M: System Administration Commands" of Oracle Documentation.

  • Page 63: Chapter 5 Troubleshooting

    CD-ROM attached to the Gigabit Ethernet card or downloading from the following URL. https://updatesite.jp.fujitsu.com/unix/en/download/driver/index.html Refer to the "Installation Guide FUJITSU PCI GigabitEthernet 4.1 Update2 or 5.0" manual for details. Does the system recognize the Gigabit Ethernet card? If the "prtconf -pv | grep FJSV"...

  • Page 64: Appendix A Messages

    This chapter explains messages displayed by the FUJITSU PCI GigabitEthernet driver. A.1 Console Messages from the Driver Messages from the FUJITSU PCI GigabitEthernet driver are listed in the following table. Table A.1 Console Messages(NOTICE) from the FUJITSU PCI GigabitEthernet Driver...

  • Page 65

    There is a possibility of driver (Other messages) internal bug or hardware Report the error to your service provider. failure. Table A.3 Console Messages from the FUJITSU PCI GigabitEthernet Driver Message Cause Workaround Check the cable connection and the network connection down Link is down switch configuration.

  • Page 66

    Message Cause Workaround Master: Communicating as Master Slave: Communicating as Slave An error was found with a Check whether the value is set correctly Illegal value for [ParameterName] parameter defined in the in the file. fjgi.conf file. Installed physical memory may be The driver could not allocate fail to ddi_dma_bind_handle insufficient.

  • Page 67

    Table A.4 Messages Reported by Machine Administration Message Meaning Workaround The version number of the driver may not support this hardware. Please apply any An error occurred during applicable patches described in the fjgi_device_check: fjgi_hw_deinit failed ! initialization of the adapter. Installation Guide.

  • Page 68: Appendix B Gigabit Ethernet Card Led Diagnosis

    Appendix B Gigabit Ethernet Card LED Diagnosis This appendix explains the LED diagnosis function of Gigabit Ethernet cards. B.1 Location and Meaning of the LEDs - Location of the LEDs (SE0X7GD2X) The following figure shows the location of the LEDs on SE0X7GD2X. Figure B.1 1000Base-SX * 2ports (SE0X7GD2X) - Meaning of the LEDs (SE0X7GD2X) The following tables show the meaning of each LED.

  • Page 69

    Figure B.2 10/100/1000Base-T * 2ports (SE0X7GD1X) - Meaning of the LEDs (SE0X7GD1X) The following tables show the meaning of each LED. 1000M LED indicates the following operation status. 1000M LED Description ON (Green) The card is connected to a 1000Mbps network and is ready to communicate. The card is not connected to a 1000Mbps network.

  • Page 70

    Figure B.3 10/100/1000Base-T * 4ports (SE0X7GQ1X) Figure B.4 10/100/1000Base-T * 4ports (SE0X7GQ2X) - Meaning of the LEDs (SE0X7GQ1X/SE0X7GQ2X) The following tables show the meaning of each LED. LINK LED (White LED in Figure B.3/B.4) indicates the following operation status. LINK LED Description ON (Amber) The card is connected to a 1000Mbps network and is ready to communicate.

  • Page 71

    ACT LED Description ON (Green) The card is transmitting or receiving network data. The card is not transmitting or receiving network data. - 65 -...

  • Page 72: Appendix C Using Fujitsu Pci Gigabitethernet In A Cluster Environment

    "PRIMECLUSTER 4.1 or later" is required when using the FUJITSU PCI GigabitEthernet driver. If an earlier version of cluster software is used, FUJITSU PCI GigabitEthernet driver cannot be used as the cluster interconnect or for IP address fail-over for an office LAN.

  • Page 73: Appendix D Using Fujitsu Pci Gigabitethernet In Solaris Containers

    PCI GigabitEthernet 5.0 or later interface when used in Solaris Containers. D.1 Solaris Containers Support The FUJITSU PCI GigabitEthernet 4.1 or later or the FUJITSU PCI GigabitEthernet 5.0 or later driver supports the following features in Solaris Containers. Global Zone Non-Global Zones(Shared-IP Non-Global Zones and Exclusive-IP Non-Global Zones) Note: Shared-IP Non-Global Zones are available in Solaris 10 3/05 or later.

  • Page 74

    zonecfg:zonename> add net (Begin adding network.) zonecfg:zonename:net> set address=IP-address/prefixlen (Specify IP address and prefix length.) zonecfg:zonename:net> set physical=Interface (Specify network interface.) zonecfg:zonename:net> end (Finish adding network.) zonecfg:zonename> exit (End of command.) Example: Adding fjgi0 to a Shared-IP Non-Global Zone (zone1). # zonecfg -z zone1 zonecfg:zone1>...

  • Page 75: Notes

    (Note 1) In Solaris 11, the vanity name (net4) is specified as fjgi2. (Note 2) Reboot the Exclusive-IP Non-Global Zone to make this setting effective. If the Exclusive-IP Non-Global Zone has not booted, execute the following command. # zoneadm -z zonename boot If the Exclusive-IP Non-Global Zone has booted, execute the following command.

  • Page 76

    zonecfg:zone1:net> set physical=net1002 zonecfg:zone1:net> end zonecfg:zone1> exit (Note 1) zonecfg create -b command must be executed to create a Shared-IP Non-Global Zone. (Note 2) net2 is the vanity name of fjgi0. (Note 3) Reboot the Shared-IP Non-Global Zone to make this setting effective. If the Shared-IP Non-Global Zone has not booted, execute the following command.

  • Page 77

    When a VLAN interface is used in Exclusive-IP Non-Global Zones, please add a VLAN interface of the fjgi interface to the Exclusive- IP Non-Global Zones in the Global Zone, and then make the VLAN interface active using the ifconfig(1M) command in the Exclusive- IP Non-Global Zones.

  • Page 78

    Execute the following commands in the Global Zone. # /usr/sbin/dladm create-aggr -d fjgi0 -d fjgi1 -d fjgi2 2 # zonecfg -z zone2 zonecfg:zone2> set ip-type=exclusive zonecfg:zone2> add net zonecfg:zone2:net> set physical=aggr2 zonecfg:zone2:net> end zonecfg:zone2> exit (Note) Reboot the Exclusive-IP Non-Global Zone to make this setting effective. If the Exclusive-IP Non-Global Zone has not booted, execute the following command.

  • Page 79: Appendix E Using Fujitsu Pci Gigabitethernet In Oracle Vm Server For Sparc

    PCI GigabitEthernet 5.0 or later interface when used in Oracle VM Server for SPARC. E.1 Oracle VM Server for SPARC Support The FUJITSU PCI GigabitEthernet 4.1 or later or the FUJITSU PCI GigabitEthernet 5.0 or later driver supports the following features in Oracle VM Server for SPARC.

  • Page 80

    The following example shows how to add a virtual switch (vsw) device (ldm add-vsw) /opt/SUNWldm/bin/ldm add-vsw net-dev=device vswitch_name ldom (device: network device vswitch_name: virtual switch device ldom: Logical Domain) Example: Adding primary-vsw0 of fjgi2 to the Control Domain (primary). # /opt/SUNWldm/bin/ldm add-vsw net-dev=fjgi2 primary-vsw0 primary (Note 1) In Solaris 11, the vanity name (net4) is specified as fjgi2.

  • Page 81: Notes

    # /opt/SUNWldm/bin/ldm list-domain -l ldg1 NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME ldg1 active -n--- 5000 0.5% 1h 17m SOFTSTATE Solaris running VCPU UTIL STRAND 0.5% 100% 0.2% 100% 0.4% 100% 0.7% 100% MEMORY SIZE 0x8000000 0x48000000 VARIABLES auto-boot?=true boot-device=vdisk1 keyboard-layout=Japanese DISK...

  • Page 82: Appendix F Using Fujitsu Pci Gigabitethernet In Solaris 11 Network Virtualization

    Appendix F Using FUJITSU PCI GigabitEthernet in Solaris 11 Network Virtualization This Appendix outlines the supported functions and setup procedure for the FUJITSU PCI GigabitEthernet 5.0 or later interface when used in Solaris 11 Network Virtualization. F.1 Solaris 11 Network Virtualization Support The FUJITSU PCI GigabitEthernet 5.0 or later driver support the following features in Solaris 11 Network Virtualization.

  • Page 83

    Example: Creating VNICs (vnic2_1 and vnic2_2) over fjgi0 (this vanity name is net2). # dladm create-vnic -l net2 vnic2_1 # dladm create-vnic -l net2 vnic2_2 The following example shows how to display VNICs (dladm show-vnic) dladm show-vnic [vnic-link] (vnic-link: link name of VNIC) Example: Displaying VNICs (vnic2_1 and vnic2_2).

  • Page 84: Notes

    # flowadm show-flow FLOW LINK IPADDR PROTO LPORT RPORT DSFLD vnic2_1_flow vnic2_1 vnic2_2_flow vnic2_2 The following example shows how to display properties of flows over VNICs (flowadm show-flowprop) flowadm show-flowprop [-p prop[,...]] [flow] (prop: property, flow: flow name) Example: Displaying properties(maximum bandwidth) of flows (vnic2_1_flow and vnic2_2_flow) over VNICs (vnic2_1 and vnic2_2). # flowadm show-flowprop -p maxbw FLOW PROPERTY...

  • Page 85: Appendix G Pci Slot Number And Device Name

    Appendix G PCI Slot Number and Device Name This appendix provides a cross-reference of PCI slot numbers and device names for the following SPARC Enterprise models. - SPARC Enterprise M3000 - SPARC Enterprise M4000/M5000 - SPARC Enterprise M8000/M9000 - SPARC Enterprise T1000 - SPARC Enterprise T2000 - SPARC Enterprise T5120 - SPARC Enterprise T5220...

  • Page 86

    Board Number Slot Number Device Name PCI#1-PCIE6 /pci@0,600000/pci@0/pci@9/pci@0/pci@9/pci@0/pci@9/****@0 Basic PCI PCI#2 /pci@1,700000/****@0 Slot PCI#2-PCIX1 /pci@1,700000/pci@0/pci@1/pci@0/****@4 PCI#2-PCIX2 /pci@1,700000/pci@0/pci@1/pci@0,1/****@4 PCI#2-PCIX5 /pci@1,700000/pci@0/pci@8/pci@0/****@4 PCI#2 IOBoat(X) PCI#2-PCIX6 /pci@1,700000/pci@0/pci@8/pci@0,1/****@4 PCI#2-PCIX3 /pci@1,700000/pci@0/pci@9/pci@0/****@4 PCI#2-PCIX4 /pci@1,700000/pci@0/pci@9/pci@0,1/****@4 PCI#2-PCIE1 /pci@1,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#2-PCIE2 /pci@1,700000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#2-PCIE3 /pci@1,700000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#2 IOBoat(Ex) PCI#2-PCIE4 /pci@1,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#2-PCIE5 /pci@1,700000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#2-PCIE6 /pci@1,700000/pci@0/pci@9/pci@0/pci@9/****@0 Basic PCI PCI#3...

  • Page 87

    Board Number Slot Number Device Name PCI#4-PCIE4 /pci@3,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#4-PCIE5 /pci@3,700000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#4-PCIE6 /pci@3,700000/pci@0/pci@9/pci@0/pci@9/****@0 PCI#0 /pci@10,600000/pci@0/pci@8/pci@0,1/****@1 Basic PCI Slot PCI#1 /pci@10,600000/pci@0/pci@9/****@0 PCI#1-PCIX1 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0/****@4 PCI#1-PCIX2 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0,1/****@4 PCI#1-PCIX5 /pci@10,600000/pci@0/pci@9/pci@0/pci@8/pci@0/****@4 PCI#1 IOBoat(X) PCI#1-PCIX6 /pci@10,600000/pci@0/pci@9/pci@0/pci@8/pci@0,1/****@4 PCI#1-PCIX3 /pci@10,600000/pci@0/pci@9/pci@0/pci@9/pci@0/****@4 PCI#1-PCIX4 /pci@10,600000/pci@0/pci@9/pci@0/pci@9/pci@0,1/****@4 PCI#1-PCIE1 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0/pci@0/****@0 PCI#1-PCIE2 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0/pci@1/****@0 PCI#1-PCIE3 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0/pci@9/****@0 PCI#1 IOBoat(Ex) PCI#1-PCIE4 /pci@10,600000/pci@0/pci@9/pci@0/pci@9/pci@0/pci@0/****@0...

  • Page 88

    Board Number Slot Number Device Name PCI#3-PCIE1 /pci@12,600000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#3-PCIE2 /pci@12,600000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#3-PCIE3 /pci@12,600000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#3 IOBoat(Ex) PCI#3-PCIE4 /pci@12,600000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#3-PCIE5 /pci@12,600000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#3-PCIE6 /pci@12,600000/pci@0/pci@9/pci@0/pci@9/****@0 Basic PCI PCI#4 /pci@13,700000/****@0 Slot PCI#4-PCIX1 /pci@13,700000/pci@0/pci@1/pci@0/****@4 PCI#4-PCIX2 /pci@13,700000/pci@0/pci@1/pci@0,1/****@4 PCI#4-PCIX5 /pci@13,700000/pci@0/pci@8/pci@0/****@4 PCI#4 IOBoat(X) PCI#4-PCIX6 /pci@13,700000/pci@0/pci@8/pci@0,1/****@4 PCI#4-PCIX3 /pci@13,700000/pci@0/pci@9/pci@0/****@4 PCI#4-PCIX4 /pci@13,700000/pci@0/pci@9/pci@0,1/****@4 PCI#4-PCIE1 /pci@13,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#4-PCIE2 /pci@13,700000/pci@0/pci@1/pci@0/pci@1/****@0...

  • Page 89

    Board Number Slot Number Device Name Basic PCI PCI#2 /pci@2,600000/****@0 Slot Basic PCI PCI#3 /pci@3,700000/****@0 Slot PCI#3-PCIX1 /pci@3,700000/pci@0/pci@1/pci@0/****@4 PCI#3-PCIX2 /pci@3,700000/pci@0/pci@1/pci@0,1/****@4 PCI#3-PCIX5 /pci@3,700000/pci@0/pci@8/pci@0/****@4 PCI#3 IOBoat(X) PCI#3-PCIX6 /pci@3,700000/pci@0/pci@8/pci@0,1/****@4 PCI#3-PCIX3 /pci@3,700000/pci@0/pci@9/pci@0/****@4 PCI#3-PCIX4 /pci@3,700000/pci@0/pci@9/pci@0,1/****@4 PCI#3-PCIE1 /pci@3,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#3-PCIE2 /pci@3,700000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#3-PCIE3 /pci@3,700000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#3 IOBoat(Ex) PCI#3-PCIE4 /pci@3,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#3-PCIE5 /pci@3,700000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#3-PCIE6...

  • Page 90

    Board Number Slot Number Device Name PCI#7-PCIX4 /pci@7,700000/pci@0/pci@9/pci@0,1/****@4 PCI#7-PCIE1 /pci@7,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#7-PCIE2 /pci@7,700000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#7-PCIE3 /pci@7,700000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#7 IOBoat(Ex) PCI#7-PCIE4 /pci@7,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#7-PCIE5 /pci@7,700000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#7-PCIE6 /pci@7,700000/pci@0/pci@9/pci@0/pci@9/****@0 Basic PCI PCI#0 /pci@10,600000/****@0 Slot Basic PCI PCI#1 /pci@11,700000/****@0 Slot PCI#1-PCIX1 /pci@11,700000/pci@0/pci@1/pci@0/****@4 PCI#1-PCIX2 /pci@11,700000/pci@0/pci@1/pci@0,1/****@4 PCI#1-PCIX5 /pci@11,700000/pci@0/pci@8/pci@0/****@4 PCI#1 IOBoat(X) PCI#1-PCIX6 /pci@11,700000/pci@0/pci@8/pci@0,1/****@4 PCI#1-PCIX3...

  • Page 91

    Board Number Slot Number Device Name Basic PCI PCI#5 /pci@15,700000/****@0 Slot PCI#5-PCIX1 /pci@15,700000/pci@0/pci@1/pci@0/****@4 PCI#5-PCIX2 /pci@15,700000/pci@0/pci@1/pci@0,1/****@4 PCI#5-PCIX5 /pci@15,700000/pci@0/pci@8/pci@0/****@4 PCI#5 IOBoat(X) PCI#5-PCIX6 /pci@15,700000/pci@0/pci@8/pci@0,1/****@4 PCI#5-PCIX3 /pci@15,700000/pci@0/pci@9/pci@0/****@4 PCI#5-PCIX4 /pci@15,700000/pci@0/pci@9/pci@0,1/****@4 PCI#5-PCIE1 /pci@15,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#5-PCIE2 /pci@15,700000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#5-PCIE3 /pci@15,700000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#5 IOBoat(Ex) PCI#5-PCIE4 /pci@15,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#5-PCIE5 /pci@15,700000/pci@0/pci@9/pci@0/pci@1/****@0 PCI#5-PCIE6 /pci@15,700000/pci@0/pci@9/pci@0/pci@9/****@0 Basic PCI PCI#6 /pci@16,600000/****@0 Slot...

  • Page 92

    - SPARC Enterprise T5120 Slot Number Device Name PCI-E#1 /pci@0/pci@0/pci@8/pci@0/pci@1/xxxxxxx@0 PCI-E#0 /pci@0/pci@0/pci@8/pci@0/pci@9/xxxxxxx@0 PCI-E#2 /pci@0/pci@0/pci@9/xxxxxxx@0 - SPARC Enterprise T5220 Slot Number Device Name PCI-E#1 /pci@0/pci@0/pci@8/pci@0/pci@1/xxxxxxx@0 PCI-E#4 /pci@0/pci@0/pci@8/pci@0/pci@2/xxxxxxx@0 PCI-E#5 /pci@0/pci@0/pci@8/pci@0/pci@8/xxxxxxx@0 PCI-E#0 /pci@0/pci@0/pci@8/pci@0/pci@9/xxxxxxx@0 PCI-E#3 /pci@0/pci@0/pci@8/pci@0/pci@a/xxxxxxx@0 PCI-E#2 /pci@0/pci@0/pci@9/xxxxxxx@0 - SPARC Enterprise T5140 Slot Number Device Name PCI-E#2 /pci@400/pci@0/pci@9...

  • Page 93

    - SPARC Enterprise T5440 (2CPU) Slot Number Device Name PCI-E#3 /pci@400/pci@0/pci@8/pci@0/pci@9 PCI-E#4 /pci@400/pci@0/pci@8/pci@0/pci@c PCI-E#1 /pci@400/pci@0/pci@c PCI-E#0 /pci@400/pci@0/pci@d PCI-E#7 /pci@500/pci@0/pci@8/pci@0/pci@9 PCI-E#6 /pci@500/pci@0/pci@8/pci@0/pci@c PCI-E#5 /pci@500/pci@0/pci@9 PCI-E#4 /pci@500/pci@0/pci@d SPARC T3-1 Slot Number Device Name PCI-E#0 /pci@400/pci@1/pci@0/pci@8 PCI-E#1 /pci@400/pci@2/pci@0/pci@8 PCI-E#2 /pci@400/pci@1/pci@0/pci@6 PCI-E#3 /pci@400/pci@2/pci@0/pci@c PCI-E#4 /pci@400/pci@1/pci@0/pci@0 PCI-E#5 /pci@400/pci@2/pci@0/pci@a...

Comments to this Manuals

Symbols: 0
Latest comments: