Home

Fujitsu C120-E276-11ENZ0(A) Network Card User Manual

1. LAN Switeh 13 The following example shows how to add a virtual switch vsw device Idm 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 f opt SUNWIdm bin ldm add vsw net de jgi2 primary vsw0 primary Note 1 In Solaris 11 the vanity name net4 is specified as fjgi2 Note 2 Reboot the Control Domain to make this setting effective Execute the following command from ok prompt ok boot r The following example shows how to display a virtual switch vsw device Idm list services opt SUNWldm bin ldm list services ldom Idom Logical Domain Example Displaying services of the Control Domain primary f opt SUNWldm bin ldm list services primary VDS NAME VOLUME OPTIONS DEVICE primary vdso NAME PORT RANGE primarv vcco 5000 5100 NAME MAC NET DEV DEVICE MODE primary vswO 00 15 17 13 81 8 fjgi2 switch 0 prog promisc Note In Solaris 11 the vanity name net4 is specified as fjgi2 The following example shows how to add a virtual network vnet device Idm add vsw opt SUNWldm bin ldm add vnet if name vswitch name ldom if name virtual network device vswitch name virtual switch device ldom Logical Domain Example Adding a virtual switch primary vsw0 of fjgi2 to the Guest Domain I
2. i Exclusive l a E The following example shows how to add an interface to a Shared IP Non Global Zone zonecfg add net zonecfg z zonename Specify Zone Name zonecfg zonename set ip type shared Specify Shared IP Non Global Zone 61 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 gt end Finish adding network zonecfg zonename gt exit End of command Example Adding fjgi0 to a Shared IP Non Global Zone zonel f zonecfg z zonel zonecfg zonel set ip type shared zonecfg zonel add net zonecfg zonel net set address 192 168 150 1 24 zonecfg zonel net set physical fjgiO zonecfg zonel net gt end zonecfg zonel gt exit Note 1 In Solaris ll zonecfg create b command must be executed to create a Shared IP Non Global Zone Note 2 In Solaris 11 the vanity name net2 is specified as 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 f zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot The following example shows how to remove an interface from a Shared IP
3. If LinkAggregation Group has been setup to be activated after rebooting the system please delete the descriptions in the etc hostname aggr instance number and etc inet hosts files defined in the activation of LinkAggregation Group section Solaris 11 The following example shows how to inactivate the aggr link aggr1 LinkAggregation Group and stop the LinkA ggregation 2 IP address of the representative interface agerl is deleted ifconfig aggrl unplumb 2 If LinkAggregation Group has been setup to be activated after rebooting the system please execute the following ipadm 1M command and delete the descriptions in the etc inet hosts files defined in the activation of LinkAggregation Group section f ipadm delete ip aggrl 47 2 Delete the LinkAggregation Group Solaris 10 8 07 or later The following example shows how to delete the key 1 LinkAggregation Group 3 4 usr sbin dladm delete aggr 1 3 Before deleting the LinkAggregation Group please inactivate the LinkA ggregation Group and stop the LinkA ggregation Solaris 11 The following example shows how to delete the aggr link aggr1 LinkAggregation Group 4 f usr sbin dladm delete aggr aggrl 4 Before deleting the LinkAggregation Group please inactivate the LinkA ggregation Group and stop the LinkA ggregation i Note 0606060000209090000009909029000009090990020000090909099099090900000090909900000090909090909000000909090
4. 17 Anv connection speed of 1000 100 or 10 Auto default Mbps is set based on negotiation with the uto defau remote device This is effective only when AutoNegotiation A On 1000 Connect at 1000Mbps Both Full Duplex and Half Duplex are Both default enabled This is effective only when AutoNegotiation A On Auto default Flow control is performed according to uto defau the setup of the remote device Only flow control from the remote device LinkSpeed A 1 DuplexCapabilities A 1 is allowed Flow control from the local FlowControl A 2 device is not allowed Only flow control from the local device is LocSend allowed Flow control from the remote device is not allowed 1500 default to 9000 3 MTU byte is specified Auto Negotiation is enabled The interface will not be able to communicate with remote device operating in fixed On default mode Auto Negotiation disabled AutoNegotiation A When SEOX7GDIX SEOX7GQIX SEOX7GQ2xX is used in 1000Mbps mode use this setting Auto Negotiation is disabled Forced Off mode Master or Slave is set based on Auto default negotiation with the remote device This uto defau is effective only when Role A 4 AutoNegotiation A On E 0 to 1000 3 Time to wait for an interrupt for receiving ReceiveTicks ia default 77 is specified micro seconds 5 0 to 1000 3 Time to wait for an interrupt for T itTick rans
5. 10 Chapter 3 Setting Instructions This chapter describes the summarv 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 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 Itis 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 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 unknown net3 Ethernet unknown unknown net4 Ethernet unknown unknown net5 Ethernet unknown unknown The installed fjgi interface and the interface name are displayed The interface name Vanity Name
6. 4ports SEOX7GQIX SE0X7GQ2X SEOX7GDIX SEOX7GD2X SE0X7GQ2X PCI Express 4lane Bus Mastering DMA Host Data Transfer Transfers SEOX7GQIX PCI Express 8lane Bus Mastering DMA Transfers M Maximum 9 1W SEOX7GDIX 9 2W SEOX7GD2X 3 15 0W SEOX7GQIX 12 8W SEOX7GQ2X 1000Base SX SEOX7GD2X 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 SEOX7GD1X SEOX7GQIX SE0X7GQ2X CAT5e Cable CATS cable can also be used for 10 100Mbps i Note SEOX7GD2X only support full duplex connection Half duplex connection is not supported When using 1000Mbps transmission rate with SEOX7GD1X SEOX7GQIX 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 SEOX7GD2X allows optical fibre cable connection the SEOX7GD1X SEOX7GQIX 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 SEOX7GD2X 1000BASE SX Two LEDs per port LINK LED
7. Appendix B Gigabit Ethernet Card LED Disgele sa a e Hel ki vb bebe Jani Evi peines 62 Bil L ti ii and Meaning of be EBD sienten tei tei pretesa menie r e dep es Pe bees PE pe Es si 62 Appendix C Using FUJITSU PCI GigabitEthernet in a Cluster Environment 66 EB ul c TEN ATR UTNE aN p a VE OR EI a ME 66 C2 Cluster Environment Setup Proeedime iai EA re HERE EO OTRO ETHER aii SPES ESEA EPS ESEE 66 BE e A M 66 Appendix D Using FUJITSU PCI GigabitEthernet in Solaris Containers nr nnnn 67 TE Satis do o a 00 ATE 67 D2 Soltis Containers Setup POGONE sise cesses e k pa obok DR EEG EE ERE CE DEI REDE EGRE ETHER b EORR osebi IEEE RET 67 iv BOMO A EE ne AEE eni EAE A EE ei Ces vase AA La aN Sica teed a aE 69 Appendix E Using FUJITSU PCI GigabitEthernet in Oracle VM Server for SPARC nn enen rent 73 E Oracle VM Server for SPARC SUpDOS uito coemiterio ree PPS aba REED ES E COP EE akad babe Ai eR 73 E 2 Oracle VM Server for SPARC Setup ProGedusg iue ane terree tiae ie e etre FR RE IUe eee iphone bei ii 73 E 3 Notes Appendix F Using FUJITSU PCI GigabitEthernet in Solaris 11 Network Virtualization nee 76 Fi Solanis 11 Network Virtualization Suppotrk n oret oer dri re t EDEPOL ED HERE ROIG HOUR Ee FAST 76 P2 Solaris 11 Network Virtualization Setup Pracedute od eee derer ie eH ee e SR bee e re eee 76 EID C JO 78 Appendix
8. DuplexCapabilities A FlowControl A fjgi mtu AutoNegotiation A Role A ReceiveTicks TransmitTicks ReceiveMaxBD or TransmitMaxBD parameters 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 lt Off LinkSpeed A 100 and DuplexCapabilities A lt 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 9 The parameter values need to be set by character strings like AutoNegotiation_A On LinkSpeed A 100 and DuplexCapabilities A lt Full The following is added to the fjgi conf file AutoNegotiation A On LinkSpeed A 100 DuplexCapabilities A Full Example 3 T
9. 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 fjgi file 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 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 See section 2 Edit the etc inet ipnodes file when you define a hostname in the etc hostname6 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 3 Reboot the system Rebo
10. micro seconds T tTick Read onl ransmitTicks ead only 0 to 1000 default 500 The number of buffer descriptor to wait for an interrupt for receiving l is specified R MaxBD Read onl eceiveMax ead only 1 to 500 default 10 The number of buffer descriptor to wait for an interrupt for transmitting is specified T tMaxBD Read onl ransmitMax ead only 1 to 500 default 128 Note Ce o 000000000 0 0000000 0 0 0 0 0 0 0000 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 8 0 0 0 0 8 0 2 0 0 0 0000 0 0 0 0 0 Using Auto Negotiation the default setting is recommended for speed duplex and flow control When Auto Negotiation is used the remote device should also be setup for Auto Negotiation Using Auto Negotiation on both local and remotes devicesallows the appropriate speed duplex and flow control to be set up automatically HalfDuplex modes are not supported with the SEOX7GD2X The SEOX7GD2X supports 1000Mbps operation only When you use the ndd 1M command to change the mode of operation please set the same mode of operation on local and remote devices When the mode of operation is not the same between local and remote devices link up may fail a communication error may occur even if link is up or the mode of operation may not be the same as specified Due to the ndd 1M command specification if two or more processes execute the ndd 1M command for the same driver a
11. please set the same mode of operation on local and remote devices When the mode of operation is not the same between local and remote devices link up may fail a communication error may occur even if link is up or the mode of operation may not be the same as specified The default values of the tuning parameter which provide higher throughput are recommended for the most systems Only when you need a smaller latency for a specific use change the values of the parameters You need to check if the specified parameters provide a suitable latency and throughput for your systems When the values of these parameters are set small the latency will be improved but the throughput will fall If the dladm 1M command is executed repeatedly the fjgi driver s performance may decrease The speed duplex autonego and flowctrl propertiese values are valid only when state 1 If state 0 these values are invalid After rebooting the system the value set by dladm 1M command remain effective Operation mode setting using the dladm 1M command becomes effective for each physical interface Therefore the operation modes of the VLAN interface and IPv4 IPv6 interface are changed at the same time 34 3 5 5 FCode Settings FCode settings must be changed when the remote device does not support Auto Negotiation and the communication bv FCode is needed example Network Installation FCode changes are not required for Network Installation if the remo
12. 0 PCI Express Gigabit Ethernet card SEOX7GQ2X was supported 10 2008 8 29 Changed the Version 3 0 Update2 4 0 to 3 0 Update3 4 0 Updatel iii Contents Chapter 1 Product Outline INE S d 01 CP E A A a L2 Gigabit Bther et Card SpeOITIGaHONE ae deett re ai Gi e dee e e Oei e eto iE nd ete bes ovest eggs 2 Exec orbc M O NJI 2 1 22 Pari Names iud Features vt Pay ai casas ccs cose oni itt rr RP BIRRA e HERREN PE PEEEEE EX a dje ER ORE EE ERE REFER FS 3 Chapter 2 Gigabit Ethernet Card Installation 2 1 Installation of the tnsabit Ethernet Card eene im petente tnb Pi eem ene o bete bb Deer taa 22 denni jip ne Eus abr ET ied Ub cn rem prote OE ob rer oe aea aee ette eb mre cet eet 6 2 2 Cable COMME UM 6 Chapter 3 Sawing INSTMO MONS E Mideast Bette iia leis ml Driver Solare Installation deine tace teretes va bid ied o at Sa dee et ire e tenes 2 2 Dieta IC AEN Doer dace OE asa a slip tota n trat rette et e rte a a ra Egan ni duis e NE EEA 3 3 Environment Seting of WP yt Int tfaees iu idet RANA ces eri ertea ttd lie ecelesie safra 3 52 Eine Seti of IPUO IMAGE coco n e e Ote teo eet Pus E eee ta 3 4 Identification of the Gigabit Ethernet Card 355 Operation Mode Se ooi tee te teme etie A retine te d ta ins eie oin teo ederet etie i
13. Auto Negotiation or vice versa after system startup You want to change setting JumboFrame without rebooting How to Use the dladm 1M Command The following examples show how to display and set a property using the dladm 1M command To display dladm show linkprop p prop link prop property name example The state of the link of fjgi2 this vanity name is net4 will be displayed f dladm show linkprop p state net4 LINK PROPERTY PERM VALUE DEFAULT POSSIBLE net4 state up up down To set dladm set linkprop p prop value link prop property name value value of property example 1000Mbps FullDuplex is disabled on interface fjgi2 this vanity name is net4 4 dladm set linkprop p en 1000fdx cap 0 net4 The dladm 1M Command Properties The following properties can be used with the dladm 1M command Properties 10 10Mbps speed Read only 100 100Mbps 1000 1000Mbps half Half Duplex dupl Read onl d Link d up Link up 32 Auto Negotiation Setting adv autoneg cap Read and write 0 Auto Negotiation Off Forced mode 1 Auto Negotiation On default MTU byte Setting tu 1 Read and writ Flow Control Setting no None flow control disabled tx Local Send Can transmit pause frame only flowctrl R d and wate ps Remote Send Can receive pause Home only bi Symmetric Can receive and transmit pause frame pfc Priority base Can receive and transmit pause frame includeing thr
14. Auto Negotiation to another which does not support Auto Negotiation or vice versa after system startup Note When using the ndd 1M command to change interface communication modes it is necessary to change or reset the Link Status after making the changes This causes the changes to be recognized by the hardware and dynamically take effect Using ndd 1M to change the adv autoneg cap parameter cause a Link Status change Please note in the To set examples below that the last step is always a change to the adv autoneg cap parameter How to Use the ndd 1M Command The following examples show how to display and set parameters using the ndd 1M command To display ndd get dev fjgi param Note Please put a decimal number instance number in place of the asterisk example The state of the link of fjgi2 will be displayed 4 ndd get dev fjgi2 link status jil To set ndd set dev fjgi param value Note Please put a decimal number instance number in place of the asterisk example 1000Mbps FullDuplex is disabled on interface fjgi2 f ndd set dev fjgi2 adv 1000fdx cap 0 Note In this stage the setting is not reflected in hardware yet When the setting change is reflected in hardware with no change of an Auto Negotiation value ndd set dev fjgi paraml value Change of setting 1 ndd set dev fjgi param2 value Change of setting 2 ndd set dev fjgi adv autoneg cap N Once let Auto
15. G PCI Slot Number and Device NamTie eue kaki kp ttti RE Rer euin te RARE ERR LM IRE annot tai 79 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 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 SEOX7GD2X 10 100 1000 Base T 2ports SEOX7GD1 X 10 100 1000 Base T 4ports SEOX7GQIX SE0X7GQ2
16. Global Zone f usr sbin dladm create aggr d fjgi0 d fjgil d fjgi2 2 f zonecfg z zone2 zonecfg zone2 set ip type exclusive zonecfg zone2 add net zonecfg zone2 net gt set physical aggr2 zonecfg zone2 net gt 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot 2 Execute the following command in the Exclusive IP Non Global Zone ifconfig aggr2 plumb 192 168 170 1 up Solaris 11 Example Adding aggr2 which is a LinkAggregation Group with fjgiO this vanity name is net2 fjgil this vanity name is net3 fjgi2 this vanity name is net4 to an Exclusive IP Non Global Zone zonel Execute the following commands in the Global Zone f usr sbin dladm create aggr 1 net2 1 net3 1 net4 aggr2 f zonecfg z zone2 zonecfg zone2 set ip type exclusive zonecfg zone2 add net zonecfg zone2 net set physical aggr2 zonecfg zone2 net gt 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm
17. LACP mode and the LACP timer are set to default values L4 distribution off mode and short To set parameters to non default values it is necessary to change the LinkA ggregation settings by using the dladm modify aggr command For more information about this command please refer to 4 2 1 3 Modify a LinkA ggregation dladm modify aggr After rebooting the system the LinkAggregation settings remain effective For more information about this command please refer to the man pages section 1M System Administration Commands of Oracle Documentation 46 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 Description Deletes a LinkAggregation Group Exit Code 0 normal end 20 abnormal end Example Processes to inactivate a LinkAggregation Group are shown below 1 Inactivate the LinkAggregation Group Solaris 10 8 07 or later The following example shows how to inactivate the key 1 LinkAggregation Group and stop the LinkAggregation 1 IP address of the representative interface aggr1 is deleted ifconfig aggrl unplumb
18. Negotiation have a different value from the current value ndd set dev fjgi adv autoneg cap M Auto Negotiation is returned to the original value Note Please put a decimal number instance number in place of the asterisk example When changing fjgi0 into 100Full autonego l link sppd 100 link mode 1 from a default state autonego 1 link speed 1000 link mode lt 1 while Auto Negotiation is enabled 28 ndd ndd ndd ndd set dev fjgi0 dev f jgi0 adv 1000fdx cap adv 1000hdx cap adv autoneg cap set set dev jgi0 dev jgi0 set adv autoneg cap Note The last two commands above change the Auto Negotiation setting setting back This causes the Link Status to change then change the and is required to make the settings effective When the setting change is reflected in hardware an Auto Negotiation value being subject to change ndd set dev fjgi paraml value Change of setting 1 ndd set dev fjgi param2 value Change of setting 2 ndd set dev fjgi adv autoneg cap N Let Auto Negotiation have a different value from the current value Note Please put a decimal number instance number in place of the asterisk example When changing fjgi0 into 100Full autonego 0 link sppd 100 link mode 1 from a default state autonego 1 link speed 1000 link mode lt 1 while Auto Negotiation had been disabled ndd set dev fjgi adv 1000fdx cap 0 ndd set dev fjgi adv 1000
19. R Ticks 2 Read and writ ReceiveTicks 2 ead and write 0 to 1000 default 77 Time to wait for an interrupt for transmitting is specified micro EN seconds T tTicks 2 Read and writ TransmitTicks 2 ead and write 0 to 1000 default 500 The number of buffer descriptor to wait for an interrupt for receiving i ified _ReceiveMaxBD 72 Read and write SEC 1 to 500 default 10 The number of buffer descriptor to wait for an interrupt for t ittingi ified TransmitMaxBD 72 Read and write COME nS 1 to 500 default 128 It is necessary to inactivate a corresponding interface with the ifconfig 1M command before JumboFrame has been enabled Then activate a corresponding interface with the ifconfig 1M command after enabled 2 cardtype Role A ReceiveTicks TransmitTicks ReceiveMaxBD TransmitMaxBD are extended properties These are not displayed by dladm show linkprop commend but can be set Note Using Auto Negotiation the default setting is recommended for speed duplex and flow control When Auto Negotiation is used the remote device should also be setup for Auto Negotiation Using Auto Negotiation on both local and remotes devicesallows the appropriate speed duplex and flow control to be set up automatically HalfDuplex modes are not supported with the SEOX7GD2X The SEOX7GD2X supports 1000Mbps operation only When you use the dladm 1M command to change the mode of operation
20. 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 A Information 06000029290900000002099292090000090909099090900000090090909090900000909990900000909092920900000000909909090000009099090000009090900000009999 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
21. devices key Specify the key number to identify the LinkAggregation Specify a number ranging from 1 to 999 The group means an aggregate unit of the interfaces to distribute to collect and to make mutually redundant Solaris 11 usr sbin dladm create aggr l ether link l l ether link aggr link l ether link Specify the name of the physical interface including instance number belonging to a LinkAggregation Group 2 You can specify one to 255 devices aggr link The name of the representative interface The name of the representative interface 2 The group means an aggregate unit of the interfaces to distribute to collect and to make mutually redundant Description Creates a LinkAggregation Group Exit Code 0 normal end 20 abnormal end Example Processes to create and activate a LinkAggregation Group are shown below 43 Svstem Image LinkA ssregation LAN Switch LinkAggregation enabled To other hosts 1 Create the LinkAggregation Group Solaris 10 8 07 or later The following example shows how to create the LinkAggregation Group with the fjgi0 fjgil and fjgi2 interfaces and key 1 4 usr sbin dladm create aggr d fjgi0 d fjgil d fjgi2 1 Solaris 11 The following example shows how to create the LinkAggregation Group with the fjgi0 this vanity name is net2 fjgil this vanity name is net3 and fjgi2 this vanity name is net4 int
22. for transmitting is specified 5 Parameter is supported on 10 100 1000Base T SEOX7GD1X SEOX7GQIX 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 SEOX7GD1X SEOX7GQIX SE0X7GQ2X adapters in 1000Mbps mode only 5 These ReceiveTicks TransmitTicks ReceiveMaxBD or TransmitMaxBD parameters are tuning parameters about the performance 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 21 grep fjgi etc path to inst fpcic1 700000 pcic0 F JSV e4ta 4 0 figi pci 1 700000 pci OFJSV e4ta 4 1 1 fjgi pci 1 700000 pci 0 1 FJSV e4ta 6 2 fjgi pci 1 7O0000 pci 0 1FJSV e4ta 6 1 3 fjgi 2 pcio2 600000 pci DO FJSV e2sa 4 4 ijgi Ipci 2 600000 pci 0 FISV e2sa 4 1 5 figi 0 0 0 0 0 l SEOX7GQ1X 0 0 Ipci 3 700000 pci 0 FUSV e2ta 4 6 figi 0 0 0 c eo SEOX7GD2X a SEOX7GD1X ipci 3 7O0000 pci O EUSV e2ta 4 1 7 fjgi ipci 4 B00000 pci 0 FUSV e4tb 4 8 fgi ipci 4 600000 pciQ O F JSV e4tb 4 1 9 figi Ipci 4 B00000 pci 0 1 F JSV e4tb s 10 figi pci 4 600000 pci 0 1 F JSV e4tb 6 1 11 figi eo SE
23. 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 4th Edition October 2011 Attention The contents of this manual may be revised without prior notice Copyright 2002 2011 FUJITSU LIMITED Revision History Ediion Details 2003 2 20 2003 5 1 PRIMEPOWER1 100 was supported VLAN function was supported 2004 1 8 Support switches was added Changed the Version 2 0 to 2 1 2004 10 28 LinkA ggregation function
24. interfaces Full duplex communication Same speed for all grouped interfaces TCP IP connection 40 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 When there are many L2 distribution remote systems which the local system sends to this method decreases the possibility that the network channel is monopolized by one remote system and improves transfer efficiency for other remote systems The driver decides on the destination NIC based on the IP L3 header of sent data and sends the data to the destination When there are many remote systems which the local system sends to this method decreases the possibility that the network channel is monopolized by one remote L3 distribution system and improves transfer efficiency for omer remote systems Even if a router is installed between systems sending data are distributed If one system used as a router sends data from multiple local systems to the same remote system this method decreases the possibility that the network channel is monopolized and improves transfer efficiency for other local systems The driver decides on the destination NIC based on the T
25. of the LEDs SEOX7GD2xX The following figure shows the location of the LEDs on SEOX7GD2X Figure B 1 1000Base SX 2ports SEOX7GD2X Meaning of the LEDs SEOX7GD2X The following tables show the meaning of each LED LINK LED indicates the following operation status ON Green The card is connected to a 1000Mbps network and is ready to communicate OFF The card is not connected to a 1000Mbps network ACT LED indicates the following operation status ON Green The card is transmitting or receiving network data OFF The card is not transmitting or receiving network data Location of the LEDs SEOX7GD1X The following figures show the location of the LEDs on SEOX7GDIX 62 Figure B 2 10 100 1000Base T 2ports SEOX7GD1X Meaning of the LEDs SEOX7GD1X The following tables show the meaning of each LED 1000M LED indicates the following operation status Description The card is connected to a 1000Mbps network and is ready to communicate The card is not connected to a 1000Mbps network 100M LED indicates the following operation status ON Green The card is connected to a 100Mbps network and is ready to communicate OFF The card is not connected to a 100Mbps network LINK ACT LED indicates the following operation status ON Green The card is connected to a 1000Mbps 100Mbps or 10Mbps network and is ready to communicate BLINKING 2m The card is transmitting or receiving network da
26. priority value not supported auto Auto mode is dynamically determined not supported 10Mbps FullDuplex Actual Setting adv_10fdx_cap Read only 0 Disabled 1 Enabled 10Mbps FullDuplex Setting en 10fdx cap Read and write 0 Disabled 1 Enabled default 10Mbps HalfDuplex Actual Setting adv 10hdx cap Read only 0 Disabled 1 Enabled 10Mbps HalfDuplex Setting en l0hdx cap Read and write 0 Disabled 1 Enabled default 100Mbps FullDuplex Actual Setting adv 100fdx cap Read only 0 Disabled 1 Enabled 100Mbps FullDuplex Setting en 100fdx cap Read and write 0 Disabled 1 Enabled default 100Mbps HalfDuplex Actual Setting adv 100hdx cap Read only 0 Disabled 1 Enabled 100Mbps HalfDuplex Setting en 100hdx cap Read and write 0 Disabled 1 Enabled default 1000Mbps FullDuplex Actual Setting adv 1000fdx cap Read only 0 Disabled 1 Enabled 1000Mbps FullDuplex Setting en 1000fdx cap Read and write 0 Disabled 1 Enabled default 1000Mbps HalfDuplex Actual Setting adv 1000hdx cap Read only 0 Disabled 1 Enabled 1000Mbps HalfDuplex Setting en 1000hdx cap Read and write 0 Disabled 1 Enabled default 33 cardtype 2 Read odi 0 SX SEOX7GD2X se i 1 T SEUX7GDIX SE0X7GQ1X SE0X7GQ2X Role setting when operating at 1000Mbps used with SEOX7GD1X SEOX7GQIX SEOX7GQ2X 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 l seconds
27. z zonename reboot 2 Execute the following command in the Exclusive IP Non Global Zone ifconfig aggr2 plumb 192 168 170 1 up For more information about Solaris Containers please refer to System Administration Guide Solaris Containers Resource Management and Solaris Zones of Oracle Documentation Par p Appendix E Using FUJITSU PCI GigabitEthernet in Oracle VM Server for SPARC This Appendix outlines the supported functions and setup procedure for the FUJITSU PCI GigabitEthernet 4 1 or later or the FUJITSU 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 Control Domain Service Domain Guest Domain Virtual Network virtual switch vsw devices and virtual network vnet devices E 2 Oracle VM Server for SPARC Setup Procedure Setup the Oracle VM Server for SPARC environment For more information about the Oracle VM Server for SPARC environment please refer to Oracle VM Server for SPARC Administration Guide of Oracle Documentation The examples below show the setting methods of virtual switch and virtual network devices System Image Control Domain primary Guest Domain ldgl figi VSWprimary vsw NIC
28. 0 1 24 zonecfg zonel net gt set phvsical aggrl zonecfg zonel net end zonecfg zonel gt exit Note 1 zonecfg create b command must be executed to create a Shared IP Non Global Zone Note 2 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 f zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot 70 Whena 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 Example Adding fjg11002 to an Exclusive IP Non Global Zone zone2 Solaris 10 8 07 or later Execute the following commands in the Global Zone f ifconfig fjgi1002 plumb f zonecfg z zone2 zonecfg zone2 set ip type exclusive zonecfg zone2 add net zonecfg zone2 net set physical fjgi1002 zonecfg zone2 net gt 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot 2 Execute the following c
29. 00010 class code 00020000 subsystem id 00000066 subsystem vendor id 00001374 revision id 000000a3 device id 00001678 vendor id 000014e4 Displayed only when half duplex is set 2 Displayed only when transfer speed is set to a specific value 10Mbps Oxa 100Mbps 0x64 1000Mbps 0x3e8 Note 1 and 2 are not displayed in the default configuration Note ooo 000000000 0000000000 00000000 0 0 0 0 0 00 800 0 0 0 0 0 0 0 8800 0 0 0 0 0 8 0 0 0 0 0 0 0 8 0 8 0 8 0 0 0 0 0 0 0 0 8 8 0 0 0 0 0 00000000 00 Changes to FCode settings are lost after executing the reset all command from the ok prompt See How to Return to Default FCode Settings Auto Negotiation Mode or after power cycling the system 36 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 See the document Install Server Build Guide I O Device Driver SPARC Enterprise for the installation procedure 3 7 VLAN Interface Setup This section provides information about the VLAN interface and setting up the VLAN interface 3 7 1 IEEE 802 1Q TagVLAN 3 7 2 Setting Up the VLAN Interface 3 7 1 IEEE 802 1Q TagVLAN The IEEE 802 1Q TagVLAN function is described in the following IEEE 802 1Q TagVLAN The TagVLAN function provides the ability to create two or more separat
30. 1 PCI 1 PCIE3 pci 20 600000 pci 0 pci Q 9 pci 0 pci 1 pci 0 pci 9 0 IOBoat Ex PCI 1 PCIE4 pci 0 600000 pci 0 pci 9 pci 0 pci 9 pci 0 pci 0 0 PCI 1 PCIES pci 0 600000 pci 0 pci 9 pci 0 pci 9 pci Q O pci Q 1 0 79 PCI 1 PCIE6 pci 0 600000 pci 0 pci Q 9 pci 0 pci 9 pci Q O pci 9 2 Basic PCI PCI Ipci 1 700000 0 o Basic PCI za i PCIH3 pci 2 600000 20 Basic PCI Slot i PE Ipci23 700000 20 rom pews 80 PCI 4 PCIE4 pci 3 700000 pci 0 pci 9 pci 0 pci 0 0 PCI 4 PCIES 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 Basic PCI PCHO pci 10 600000 pci amp 0 pci 8 pci 0 1 1 PCI 1 pci 2 10 600000 pci 0 pci 9 0 PCI 2 pci 11 700000 0 PCI 3 pci 12 600000 0 Basic PCI Slot Basic PCI Slot 81 Basic PCI SPARC Enterprise M8000 M9000 Basic PCI Slot ic PCI n C PCI 1 pci 1 700000 0 em o Board Number 82 ic PCI Sal z PCIH2 pci 2 600000 20 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 20 pci 1 pci 20 1 4 Basic PCI Slot PCI 4 pci 4 600000 0 ic PCI am e PCI S pci 5 700000 0 PCI 3 PCIX3 pci 3 700000 pci 9 0 pci 9 9 pci 0 4 I
31. 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot The following example shows how to remove an interface from an Exclusive IP Non Global Zone zonecfg remove net zonecfg z zonename Specify Zone Name zonecfg zonename remove net physical Interface Specify network interface zonecfg zonename exit End of command Example Removing fjgi2 from an Exclusive IP Non Global Zone zone2 f zonecfg z zone2 zonecfg zone2 remove net physical fjgi2 zonecfg zone2 exit Note 1 Note 2 In Solaris 11 the vanity name net4 is specified as fjgi2 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot D 3 Notes When a VLAN interface is used in Shared IP Non Global Zones please make the VLAN interface for the fjgi interface in the Global Zone with the VLAN interface creation procedure ifconfig 1M command or dladm 1M command Solaris 11 only etc Example Adding fjg11000 to a Shared IP Non Global Zone zone1 Solaris 10 8 07 or late
32. 8000 The following is added to the fjgi conf file fjgi0 lt Example 6 The MTU parameter for fjgil is set to 8000 The parameter value needs to be set by a character string like fjgil Auto Both Auto 8000 On Auto The following is added to the fjgi conf file fjgil lt 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 fjgiO is set to 8000 In this case the MTU of fjgiO is 8000 and the MTU of other instances is 1500 The following is added to the fjgi conf file fjgi mtu 1500 fjgi0 lt 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 Used to specify the location of the device parent See below node in the device tree dt ify the add ithin th VS See below Usg o specify the address within the device node Any connection speed of 1000 100 or 10 Auto default Mbps is set based on negotiation with the uto defau remote device This is effective only when AutoNegotiation A On 1000 Connect at 1000Mbps Both Full Duplex and Half Duplex are Both default enabled This is effective only wh
33. 909909000000990990909000000920990900000909299 After rebooting the system the LinkAggregation settings remain effective For more information about this command please refer to the man pages section 1M System Administration Commands of Oracle Documentation 4 2 1 3 Modify a LinkAggregation dladm modify aggr This section explains the dladm modify aggr command for modifying LinkAggregation Synopsis Solaris 10 8 07 or later usr sbin dladm modify aggr P policy l l model T time key P policy Specify the policy Data Distribution Mode Policies can be combined as needed L2 Distribution by MAC header L3 Distribution by IP header L4 Distribution by ULP TCP UDP etc header l mode Specify the LACP mode active active mode passive passive mode off off mode T time Specify the LACP timer short every one second long every 30 seconds key Specify the key number to identify the LinkAggregation Group Specify a number ranging from 1 to 999 Solaris 11 usr sbin dladm modify aggr P policy L mode T time aggr link P policy Specify the policy Data Distribution Mode Policies can be combined as needed L2 Distribution by MAC header L3 Distribution by IP header L4 Distribution by ULP TCP UDP etc header L mode Specify the LACP mode active active mode 48 passive passive mode off off mode T time Specifv the LACP timer short everv one second long everv 30 secon
34. ACT LED Three LEDs per port 1000M LED 100M LED LINK ACT LED SE0X7GQIX Two LED t LINK LED ACT LED SEOX7GD1X 10 100 1000BASE T Figure 1 1 1000Base SX 2ports SEOX7GD2X Figure 1 2 10 100 1000Base T 2ports SEOX7GD1X Figure 1 3 10 100 1000Base T 4ports SEOX7GQ1X Figure 1 4 10 100 1000Base T 4ports SEOX7GQ2X Porti Port2 Port3 Porti Chapter 2 Gigabit Ethernet Card Installation This chapter describes the tasks necessarv to install this card in vour svstem Install the hardware with the following procedures 2 1 Installation of the Gigabit Ethernet Card 22 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 A 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 Docume
35. AN interface for the aggregated interface by the usual VLAN interface creation procedure ifconfig 1M command or dladm 1M command Solaris 11 only etc to use the VLAN interface with LinkAggregation 56 Chapter 5 Troubleshooting The following should be checked first to troubleshoot a problem Is the driver software installed correctly If the pkginfo x FJSVgid command does not return output the driver package is not installed If this occurs install the driver package using the driver 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 command does not return any string having FJSV e2sa SEOX7GD2X FJSV e2ta SEOX7GDIX FJSV e4ta SEOX7GQ1X or FJSV e4tb SE0X7GQ2X OBP Open Boot PROM on the system is not recognizing the Gigabit Ethernet card properly Check whether the physical interface is properly installed on the system Do the LEDs on the Gigabit Ethernet card indicate proper operation status Check the following items if the LEDs indicate the link status is abnormal See also Appendix B Gigabit Ethernet Card LED Diagnosis for detailed information Check Item Recommended Action Cable Replace the cable m Affix the
36. CP UDP or other ULP L4 headers of sent data and sends the data to the destination If one system is directly connected to another system this method default distributes the sending data and improves transfer efficiency for the remote system L4 distribution These data distribution methods L2 distribution L3 distribution and L4 distribution can be used together arbitrarily LACP Mode Table 4 3 LACP Mode shows the LACP modes supported The LACP is a protocol to negotiate the configuration of the LinkAggregation Group between devices to group multiple network interfaces as one virtual interface By using LACP it is not necessary to inactivate the LinkAggregation Group when the configuration of the LinkAggregation Group is changed The driver can detect the configuration change of the LinkAggregation Group immediately and can re constitute a LinkAggregation Group automatically Table 4 3 LACP Mode The driver transmits the LACP periodically regardless of the LACP mode of the partner device It is necessary to set the LACP mode of the partner device to active or active mode passive This mode is used for re configuring the LinkAggregation Group of the local device automatically when the configuration of the LinkAggregation Group of the partner device is changed The driver does not transmit the LACP unless the LACP is transmitted passive mode by the partner device It is necessary to set the LACP mode of th
37. Gigabit Ethernet card to the PCI E lot of th t Gigabit Ethernet card installation state k 1 STU C eR APTES 070S IES LE securely Gigabit Ethernet card hardware Replace the Gigabit Ethernet card Cable connection to the Gigabit Ethernet card and the itch Connect the cable to the devices securely switc Replace the Gigabit Ethernet card Power status of the Gigabit Ethernet switch Connection port of the switch Check th ti de by dladm 1M d or ch th Operation mode by dladm 1M command ec e operation mode by a m 1M command or change the operation mode to default Solaris 11 only Re install the driver package from the driver CD ROM attached to the Dri kage installation stat R aca cee aac a a Gigabit Ethernet card or at the FUJITSU download web site 57 Appendix A Messages This chapter explains messages displaved bv 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 free send descriptor tailed detaili is of the descriptor to send deed report this error to your service ailed provider There is a possibility of driver Other messages internal bug or hardware Report the error to your service provider failure Table A 2 Console Messages WARNING from the FUJITSU PCI GigabitEthernet Driver nof O vesae ome elei I
38. GigabitEthernet interface used as a VLAN interface cannot be used as the cluster interconnect 66 Appendix D Using FUJITSU PCI GigabitEthernet in Solaris Containers This Appendix outlines the supported functions and setup procedure for the FUJITSU PCI GigabitEthernet 4 1 or later or the FUJITSU 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 Exclusive IP Non Global Zones are available in Solaris 10 8 07 or later D 2 Solaris Containers Setup Procedure Setup the Solaris Containers environment For more information about the Solaris Containers environment please refer to System Administration Guide Solaris Containers Resource Management and Solaris Zones of Oracle Documentation The examples below show the setting methods for Shared IP Non Global Zones and Exclusive IP Non Global Zones System Image OSetting Shared IP Non Global Zones OSetting Exclusive IP Non Global Zones Global Zone Non Global Zones Global Zone Non Global Zones Shared IP Exclusive IP 1 2 application zonel application zone application application
39. Non Global Zone zonecfg remove net zonecfg z zonename Specify Zone Name zonecfg zonename gt remove net address IP address Specify IP address zonecfg zonename gt exit End of command Example Removing fjgi0 from a Shared IP Non Global Zone zonel f zonecfg z zonel zonecfg zonel remove net address 192 168 150 1 zonecfg zonel exit Note 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 f zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot The following example shows how to add an interface to an Exclusive IP Non Global Zone zonecfg set ip type zonecfg add net zonecfg z zonename Specify Zone Name zonecfg zonename set ip type exclusive Specify Exclusive IP Non Global Zone zonecfg zonename add net Begin adding network zonecfg zonename net set physical Interface Specify network interface zonecfg zonename net gt end Finish adding network zonecfg zonename gt exit End of command Example Adding fjgi2 to an Exclusive IP Non Global Zone zone2 f zonecfg z zone2 zonecfg zone2 gt set ip type exclusive zonecfg zone2 gt add net zonecfg zone2 net gt set physical fjgi2 zonecfg zone2 net gt end zonecfg zone2 exit 68 Note 1 Note 2 In Solaris 11 the vanity name net4 is specified as fjgi
40. OBoat Ex PCI43 PCIE4 pci 3 700000 pci 0 pci 9 pci O pci 0 9 PCI 3 PCIE6 pci 3 700000 pci 0 pci 9 pci 0 pci 9 0 PCI 3 PCIES pci 3 700000 pci 0 pci 9 pci 9 0 pci 1 0 PCI 5 PCIE6 pci 5 700000 pci 9 0 pci 9 9 pci 0 pci 9 0 Basic PCI RN PCH6 pci26 600000 0 Slot ud PCE per pci 7 700000 0 o PCI 7 PCIX1 pci 7 700000 pci C0 pci 1 pci 90 4 PCI 7 PCIX2 pci 7 700000 pci amp O pci 1 pci 0 1 4 Po PCIH7 PCIX5 pci 7 700000 pci amp 0 pci 8 pci 9 0 Q4 IOBoat X PCIH7 PCIX6 pci 7 700000 pci 0 pci 8 pci 0 1 G4 PCIH7 PCIX3 pci 7 700000 pci 0 pci B9 pci 0 Q4 83 Logical Svstem Board 1 PCIZ7 PCIES pci 7 700000 pci 9 0 pci Q 9 pci 0 pci 1 0 PCI 7 PCIE6 pci 7 700000 pci 0 pci 9 pci 0 pci 9 a Basic PCI ers PCI O pci 10 600000 0 Slot i FT PCIHI pci 11 700000 00 Oo PCI 1 PCIX1 pci 11 700000 pci 0 pci 1 pci 0 4 PCHH PCIX2 pci 11 700000 pci 0 pci 1 pci 0 1 4 PCHH PCI 1 PCIX5 pci 11 700000 pci 0 pci 0 8 pci 0 4 IOBoat X PCHH PCIX6 pci11 700000 pci 0 pci 8 pci 9 0 1 4 ic PCI Basic PCI 2 pci 12 600000 0 Slot Basic PCI PCIA3 pciQ 13 700000 20 IOBoat X Ipci 13 700000 pci 0 pci 8 pci 0 1 Q4 PCI 1 PCIE1 pci 11 700000 pci 0 pci 1 pci 9 0 pci 0 0 PCI 1 PCIE2 pci 11 700000 pci 0 pci 1 pci 0 p
41. OX7GQ2X From the above example instance number and driver name for each interface can be determined pci 1 700000 pci 0 FISV c4ta 4 fost Ipci 1 700000 pci O FISV e4ta 4 1 pci 1 700000 pci 0 I FISV c4ta 6 Ipci 1 700000 pci 0 1 FISV e4ta 6 1 pci 2 600000 pci 0 FISV e2sa 4 Ipci 2 600000 pci 0 FISV e2sa 4 1 pci 3 700000 pci O FISV e2ta 4 I6 Jaa Ipci 3 700000 pci 0 FISV e2ta 4 1 ag Ipci 4 600000 pci 0 FISV c4tb 4 1 o st Ipci 4 600000 pci 0 FJSV e4tb 6 jie 0 7f IpciG4 GOO pci FIS SAD 6 r pci 4 600000 pci 0 FISV e4tb 4 The parent and unit addresses from the example are shown below The parent is the character string to the left of FJSV e4ta FJSV e2sa FJSV e2ta or FISV e4tb The unit address is the number to the right of FJSV e4ta FJSV e2sa FJSV e2ta or FISV e4tb Ipci 1 700000 pci 0 Ipci 1 700000 pci 0 1 instance 0 is 4 instance 2 is 6 unit address j instance 1 is 4 1 instance 3 is 6 1 instance 4 is 4 unit address instance 5 is 4 1 23 l instance 6 is 4 unit address 4 instance 7 is 4 1 SSS SEOX7GQ2X Ipci 4 600000 pci 0 Ipci 4 600000 pci 0 1 it add instance 8 is 4 instance 10 is 6 unit address 3 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 platfo
42. P transmissions is relatively few If the LACP timer value of the partner device is short the driver transmits the LACP every one second 4 2 Configuration of the LinkAggregation Feature The LinkA ggregation feature can be configured with the following method 4 2 1 Setting and Displaying the Configuration with the dladm 1M Command 4 2 1 Setting and Displaying the Configuration with the dladm 1M Command The dladm 1M command has the following six subcommands 4 2 1 1 Create a LinkAggregation dladm create aggr 4 2 1 2 Delete a LinkAggregation dladm delete aggr 4 2 1 3 Modify a LinkAggregation dladm modify aggr 4 1 4 Add Interfaces to a LinkAggregation dladm add aggr 4 2 1 5 Remove Interfaces from a LinkA ggregation dladm remove aggr 42 1 6 Display LinkAggregation Statistics and Information dladm show aggr 42 i 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 key d dev Specify the name of the physical interface including instance number belonging to a LinkAggregation Group 1 You can specify one to 255
43. TU parameter for fjgiO is set to 8000 26 2 Reboot the svstem Setting method of old style 1 Add the fjgi mtu parameter to the fjgi conf file The parameter value needs to be set by numerical value like fjgi mtu 8000 Example of file description The MTU parameter for fjgiO is set to 8000 name fjgi parent pci81 700000 pci80 unit address 4 fjgi mtu 8000 2 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 File for the setting procedures of JumboFrame Setup MTU by the following command dladm set linkprop p mtu value link Example when setting MTU of fjgi0 this vanity name is net2 to 8000 f dladm set linkprop p mtu 8000 net2 Settings are displayed by the following command dladm show linkprop p mtu link Example when setting MTU of fjgi this vanity name is net2 to 8000 f dladm show linkprop p mtu net2 LINK PROPERTY PERM VALUE DEFAULT POSSIBLE net2 mtu rw 8000 1500 1500 9000 i Note If JumboFrame feature is enabled the interface will be unable to transmit and receive data in IEEE802 3 format When JumboFrame has been enabled with Method 1 if two or more interfaces or VLAN interfaces are installed the JumboFrame setting applies to all interfac
44. UJITSU PCI GigabitEthernet 4 1 or later or the FUJITSU PCI GigabitEthernet 5 0 or later driver support the following cluster features Operation standby mode l n operation standby mode Mutual standby mode TCP IP communication public LAN A VLAN interface can not be used as a cluster interconnect The JumboFrame function can be used as a cluster interconnect When you change MTU from a default value 9000 please set up by the fjgi conf file or dladm 1M command Solaris 11 only For details please refer to Method 2 Specify in fjgi conf or Method 3 Specify in dladm 1M command Solaris 11 only of 3 5 2 JumboFrame Setup The following table shows the supported failover mode for an office LAN Failover Mode Support Status IP address Supported MAC address Supported 1 IP address MAC address Supported 1 Supported by PRIMECLUSTER 4 1A10 or later C 2 Cluster Environment Setup Procedure Set up the cluster environment in the same way as an Ethernet driver i e bge driver Follow Setting up the Network in the PRIMECLUSTER manual Note that the FUJITSU PCI GigabitEthernet driver resource name is fjgi C 3 Notes 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 A FUJITSU PCI
45. X 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 LinkA ggregation 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 The GLDv3 compliant driver works with the following features The LinkAggregation based on IEEE 802 3 by the dladm 1M command Solaris Contain
46. ace of VID 2 for a physical instance having instance number zero the following is used Refer to 3 3 Environment Setting and perform the procedure described Use fjgi2000 as the driver name Tocreate a VLAN Interface of VID 231 for a physical instance having instance number three the following is used Refer to 3 3 Environment Setting and perform the procedure described Use fjgi231003 as the driver name VLAN interfaces are displayed by the following command dladm show link grep fjgi Example dladm show link grep fjgi fjgiO type non vlan E device fjgi2000 type vlan 2 H device fjgil type non vlan i device fjgi2 type non vlan H device fjgi3 type non vlan device fjgi231003 type vlan 231 device In the above example the VLAN interfaces are displayed as fjgi1000 VID 1 and fjgi231003 VID 231 Solaris 11 Tocreate a VLAN Interface of VID 2 for fjgi0 this vanity name is net2 the following is used Refer to 3 3 Environment Setting and perform the procedure described Use net2002 as the driver name dladm create vlan l ether link v vid Example 4 dladm create vlan l net2 v 2 38 Tocreate 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 1 ether link v vid Example dladm create vlan 1 net5 v 231 VLAN i
47. ceiving data at 100Mbps 10 Transmitting and receiving data at 10Mbps network connection up using portA IC autonegotiation A symmetric Send accept Flowcontrol requests to from speed B the remote device There is no problem flowctrl C remote send Does not send Flowcontol request Only duplex mode D accept Flowcontrol requests role E 1 from the remote device local send Only send Flowcontrol requests Does not accept Flowcontrol requests from the remote device none Disabled D full Transmitting and receiving data in full duplex mode half Transmitting and receiving data in half duplex mode 59 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 B in the file fjgi conf file Installed physical memory may be l A The driver could not allocate e Pay ise St fail to ddi dma bind handle insufficient If this is not the cause report DMA resources O l this error to your service provider A Re activate the interface If this message An error was found in message fail to FragCount is still displayed report to your service fragmentation fei m The driver could not allocate i param register error JEEP zli resources for the ndd parameter tut The driver could not allocate cla qo E p e resources ei The dri
48. ci 1 0 IOBoat Ex PCI 7 PCIE4 pci 7 700000 pci 0 pci 9 pci O pci 0 0 PCI 1 PCIX3 pci 11 700000 pci 0 pci 9 pci 0 4 PCI 1 PCIX4 pci 11 700000 pci 0 pci 9 pci 9 0 1 4 PCIH3 PCIE1 pci 13 700000 pci 0 pci 1 pci O pci 0 00 PCI 3 PCIE2 pci 13 700000 pci 0 pci 1 pci O pci 1 00 PCI PCI 3 PCIE3 pci 13 700000 pci 0 pci 1 pci 9 0 pci 9 0 IOBoat Ex PCI43 PCIE4 pci 13 700000 pci 0 pci 9 pci 0 pci 0 0 PCI 3 PCIES pci 13 700000 pci 0 pci 9 pci 0 pci 1 0 Bi ii ix PCIH4 pci 14 600000 0 o PCI 3 PCIE6 pci 13 700000 pci 0 pci 9 pci O pci 9 GO 84 Basic PCI Basic PCI asic PCI 6 pci 16 600000 20 Slot m POL PCHI pci 17 700000 0 Oo PCIH7 pci 17 700000 pci 0 pci 1 pci O pci 9 0 SPARC Enterprise T1000 PCI E pci 780 xxxxxxx Q O y SPARC Enterprise T2000 PCI E 0 pci 780 pci 20 pci 9 8 xxxxxxx Q9 O y PCI E 1 pci 27c0 pci 9 0 pci 8 xxxxxxx 00 y PCI E 2 pci 27c0 pci 0 pci 9 9 xxxxxxx C0 y 85 SPARC Enterprise T5120 PCI E 1 pci 0 pci 0 pci 8 pci 0 pci 1 xxxxxxx 0 PCI E 0 pci 20 pci 20 pci 8 pci 0 pci 9 9 xxxxxxx 0 PCI E 2 pci 0 pci 0 pci 9 xxxxxxx 0 SPARC Enterprise T5220 SPARC Enterprise T5140 SPARC Enterprise T5240 SPARC Enterprise T5440 4CPU 86 SPARC En
49. ci82 600000 pciQ0 FJSV e2saQ4 4 fjgi pci82 600000 pci80 FJSV e2saQ04 1 5 fjgi pci 3 700000 pci 0 FISV e2ta 4 6 fjgi pci 3 700000 pci 0 FISV e2ta 4 1 7 fjgi pci84 600000 pciQ0 FJSV e4tbG4 8 fjgi pci 4 600000 pci 0 FISV e4tb 4 1 9 fjgi pci 4 600000 pci 0 1 FISV e4tb 6 10 fjgi pci 4 600000 pci 0 1 FISV 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 16 Logical bus address Instance number Driver name pci 1 700000 pci 90 L FJS V e4ta 26 1 pci 3 700000 pci 9 0 FJS V e2sa Q9 4 pci 3 700000 pci 9 0 FJSV e2sa Q4 1 pci 2 600000 pci 9 0 FJS V e2ta 24 pci 2 600000 pci 9 0 FJSV e2ta 4 pci 4 600000 pci Q 0 FJSV e4tb Q 4 pci 4 600000 pci Q 0 FJSV e4tb 24 1 pci 4 600000 pci 90 L FJS V e4tb 6 pci 4 600000 pci 90 L FJS V e4tb 9 6 1 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 p m Z Z lt m Z Z GigabitEthernet interfaces Setup of the following operation modes ar
50. co FUJITSU FUJITSU PCI Gigabit Ethernet 4 1 Update2 5 0 for Oracle Solaris User s Guide Solaris C120 E276 11ENZO A October 201 1 SPARC Enterprise Preface Purpose This manual describes how to install the Gigabit Ethernet card into vour SPARC Enterprise svstem and configure the environmental settings for the interface Target Reader This manual is intended for svstem administrators responsible for installing the Gigabit Ethernet card To understand the concepts and procedures presented in this manual vou need a few vears 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
51. dg1 f opt SUNWIdm bin ldm add vnet vnetO primary vsw0 ldgl Note Execute the following commands to make this setting effective If the Guest Domain has not started execute the following commands f opt SUNWIdm bin ldm bind domain ldgl 4 opt SUNWIdm bin ldm start domain ldgl If the Guest Domain has alreadv started execute the following commands 4 opt SUNWIdm bin ldm stop domain ldgl f opt SUNWIdm bin ldm unbind domain ldgl f opt SUNWIdm bin ldm bind domain ldgl 4 opt SUNWIdm bin ldm start domain ldgl The following example shows how to display a virtual network vnet device Idm list domain opt SUNWIdm bin ldm list domain l ldom ldom Logical Domain Example Displaying the status of the Guest Domain Idg1 74 f opt SUNWIdm bin ldm list domain l ldgl NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME ldgl active FIS 5000 4 1G 0 5 ih 17m SOFTSTATE Solaris running VCPU UTIL STRAND 0 5 100 0 2 100 0 4 100 0 7 100 MEMORY RA PA 0x8000000 0x48000000 VARIABLES auto boot true boot device vdiski kevboard lavout Japanese DISK NAME VOLUME TOUT DEVICE SERVER vdiskl voll primary vds0 disk80 primary VCONS NAME SERVICE PORT ldgi primary vccO8primary 5000 NETWORK NAME SERVICE DEVICE MAC vneto fjgi2 vswGprimary networkQ0O 00 14 4f f9 fa 5f Note In Solaris 11 the vanity name net4 is specified as fjgi2 E 3 Notes For more information about Oracle VM Server for SPARC please r
52. driver If this l l Enabling of the interrupt failed f message is still displaved report to vour ddi intr enable failed service provider Installed phvsical memorv mav be ATTACH failed detail Loading of the driver failed insufficient If this is not the cause report this error to your service provider Check whether the system is supported T Identify failed Identification of the interface If the system is supported there is a 58 Dw we ii me After disabling the driver re do the process disconnect in Dvnamic DETACH failed detail Unloading of the driver failed Reconfiguration etc If this message is still displayed report to your service provider l Allocating of the memory insufficient If this is not the cause report 17 ddi d lloc handle failed detail i v idma calloc handle failedtidetai Allocating ju the DMA this error to your service provider 18 ddi dma addr bind handle failed detail resource failed 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 ES Check the cable connection and the 1 network connection down Link is down l switch configuration Link has become up A yes Auto Negotiation is on no Auto Negotiation is off B 1000 Transmitting and receiving data at 1000Mbps 100 Transmitting and re
53. ds aggr link The name of the representative interface Description Modifies a LinkAggregation Group Exit Code 0 normal end 20 abnormal end Example Processes to modify the policy of a LinkAggregation Group are shown below Solaris 10 8 07 or later The following example shows how to change the key 1 LinkAggregation Group to policy L2 f usr sbin dladm modify aggr P L2 1 Solaris 11 The following example shows how to change the aggr link aggr1 LinkAggregation Group to policy L2 usr sbin dladm modify aggr P L2 aggrl Processes to modify the LACP mode and LACP timer of a LinkAggregation Group are shown below Solaris 10 8 07 or later The following example shows how to change the key 1 LinkAggregation Group to LACP mode active LACP timer short 4 usr sbin dladm modify aggr l active T short 1 Solaris 11 The following example shows how to change the aggr link lt aggrl LinkAggregation Group to LACP mode active LACP timer short f usr sbin dladm modify aggr L active T short aggrl Note It is not necessary to use this command if the desired policies are L4 distribution LACP mode off and LACP timer short LinkAggregation Groups are created with these default values After rebooting the system the LinkAggregation settings remain effective For more information about this command please refer to the man pages section 1M System Administration Comman
54. ds of Oracle Documentation sess 000000000 0 0 0 0 000000 0 0 0 0 0 0000 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 00000 00 00 49 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 LinkA ggregation Svnopsis 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 key Specify the key number to identify the LinkAggregation Group Specify a number ranging from 1 to 999 Solaris 11 usr sbin dladm add aggr l ether linkdev l l ether linkdev aggr link l ether linkdev 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 aggr link The name of the representative interface Description Adds interfaces to a LinkAggregation Group Exit Code 0 normal end 20 abnormal end Example Processes to add interfaces to a LinkAggregation Group are shown below 50 Svstem Image LinkAggregation LAN Switch LinkAggregation enabled To othe
55. e 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 A Information 0060600000099090000000992090000090909090900000090099099090990900009099900000090990900000000990909000000090990000000909000000909999 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 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 Touse 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 Ins
56. e MTU of other instances is 1500 The following is added to the fjgi conf file fjgi mtu 1500 name fjgi parent pci 61 700000 pciBO unit address 4 fjgi mtu 8000 Note After making changes to the fjgi conf file the system must be rebooted The settings become effective after rebooting Note nose ooooe 0000000000000 000000 0800600800000 000 8800000088000 0 0 00000000 0 0 0 0 0 0 8 8 0 0 0 00 0 08 08000000 0000000000 Using Auto Negotiation the default setting is recommended for speed duplex and flow control When Auto Negotiation is used the remote device should also be setup for Auto Negotiation Using Auto Negotiation on both local and remotes devices allows the appropriate speed duplex and flow control to be set up automatically When you use the fjgi conf file to change the mode of operation please set the same mode of operation on local and remote devices When the mode of operation is not the same between local and remote devices link up may fail a communication error may occur even if link is up or the mode of operation may not be the same as specified The default values of the tuning parameter which provide higher throughput are recommended for the most systems Only when you need a smaller latencv for a specific use change the values of the parameters You need to check if the specified parameters provide a suitable latency and throughput for your systems When the values of these parameters are set
57. e 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
58. e networks that share a single physical interface Virtual interfaces are created by assigning VLAN IDs VIDs to a physical interface Communication between different VID interfaces on the same host is not allowed The following example shows a comparison of the networks created without and with the TagVLAN feature Figure 3 1 Example of using VLAN No Tag VLAN With Tag VLAN fjgi0 fjgi3 fgi2000 fjgi281008 XX11 XX21 XX11 XX21 NIC NIC NIC Switch Switch To X X 1X To X X 2 X To X X 1X To X X 2 X Network Network Network Network netmask 255 255 255 0 By using a VLAN traffic management of two or more networks on a single physical interface can be done In order to create a VLAN environment a switch capable of supporting a VLAN setup VID and Tagged Untagged setting is required 39 The FUJITSU PCI GigabitEthernet 4 1 or later drivers support Supported VIDs 1 4094 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 The three lower digits of the VLAN interface number physical instance number The upper digits of the VLAN interface number VID 1 4094 VLAN interface number VID 1000 4 physical instance number VLAN Interface Setup Examples Solaris 10 8 07 or later Tocreate a VLAN Interf
59. e parameter value needs to be set by numerical value like fjgi mtu 8000 The following is added to the fjgi conf file name fjgi parent pci 4 600000 pci 0 unit address 4 1 fjgi mtu 8000 24 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 lt 100 DuplexCapabilities_A Half The following is added to the fjgi conf file AutoNegotiation A Off LinkSpeed A 100 DuplexCapabilities A Half Example 5 The parameters for all instances are 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 AutoNegotiation_A On LinkSpeed_A 100 DuplexCapabilities A lt Full The following is added to the fjgi conf file AutoNegotiation A On LinkSpeed A 100 DuplexCapabilities A Full Example 6 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 Example 7 The MTU parameter for all instances is set to 1500 and the MTU parameter for fjgiO the instance number 0 port of SEOX7GQIX 10 100 1000BASE T is set to 8000 In this case the MTU of fjgiO is 8000 and th
60. e partner device to active 41 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 The driver does not transmit the LACP regardless of the LACP mode of the partner device off mode It is necessary to set the LACP mode of the partner device to off default This mode has the effect of transmitting no LACP and is used when the configurations of the LinkAggregation Groups of both devices will not be changed LACP Timer Table 4 4 LACP Timer shows the LACP timer values supported Table 4 4 LACP Timer The driver transmits the LACP every one second With this timer value the number of LACP transmissions is higher but short there is the effect of detecting the configuration change of the LinkAggregation Group of the partner device immediately default If the LACP timer value of the partner device is long the driver transmits the LACP every 30 seconds When the LACP timer value of the partner device is unidentified this timer value is used The driver transmits the LACP every 30 seconds With this timer value LinkAggregation Group configuration changes of the partner device are detected within 30 seconds and the number of LAC
61. efer to the Oracle VM Server for SPARC Administration Guide of Oracle Documentation 575 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 VNIC by dladm 1M command Flow by flowadm 1M command F 2 Solaris 11 Network Virtualization Setup Procedure Setup Solaris 11 Network Virtualization For more information about Solaris 11 Network Virtualization please refer to System Administration Guide Network Interfaces and Network Virtualization and man pages section 1M System Administration Commands of Oracle Documentation The examples below show the setting methods of VNIC virtual network interface and flows System Image application application application upp transport TCP UDP UDP pr imax bandwidth IP ee IP vnic2 2 flow VNIC VNIC VNIC vnic2 1 vnic2 2 vnic2004 LAN Switch The following example shows how to create a VNIC dladm create vnic dladm create vnic l link vnic link link physical link vnic link link name of VNIC 2962 Examp
62. em 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 fjgiO 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 fjgiO this vanity name is net2 ipadm create ip net2 ipadm create addr T static a 192 168 150 1 24 net2 v4static When you use a hostname please see section 2 Edit the etc hosts file first a Information Pee reese 00000000 0000000000 0 0 0 0 0 8 8 8 00000000 0 0 0 0 0 0 0 0 0 00000 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 6 6 8 0 0 00000000 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 f ipadm show addr net2 vastatic ADDROBJ TYPE STATE ADDR net2 v4static static ok 192 168 150 1 24 Ce ooo 00 0 0 0 0 00000000 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 8 0 0 0 0 0 8 8 0 8 0 0 0 0 8 0 0 0 2 0 0 8 0 0 0 0 8 0 0 0 0 0 0 6 8 0 0 00000 0 0 0 0 Edit the
63. en AutoNegotiation A On Flow control is performed according to FlowControl_A 2 Auto default the setup of the remote device 21 LinkSpeed A 1 DuplexCapabilities A 1 Only flow control from the remote device Rem 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 1500 default to 9000 3 MTU byte is specified Auto Negotiation is enabled The interface will not be able to communicate with remote device operating in fixed On default mode Auto Negotiation disabled AutoNegotiation A When SEOX7GD1X SEOX7GQIX SE0X7GQ2X is used in 1000Mbps mode use this setting Auto Negotiation is disabled Forced mode Master or Slave is set based on Auto default negotiation with the remote device This uto defau is effective only when Role A 4 AutoNegotiation A On Master Communication by Master ReceiveTicks 0 to 1000 3 Time to wait for an interrupt for receiving default 77 is specified micro seconds 5 TransmitTicks 0 to 1000 3 Time to wait for an interrupt for default 500 transmitting is specified micro seconds 5 ReceiveMaxBD 1 to 500 3 The number of buffer descriptor to wait default 10 for an interrupt for receiving is specified 5 TransmitMaxBD 1 to 500 3 The number of buffer descriptor to wait default 128 for an interrupt
64. erface with the key 1 LinkAggregation Group for activation after rebooting the system IP address 192 168 151 1 is assigned to the VLAN interface aggr2001 of VID 2 1 Describe the hostname in the etc hostname aggr2001 file Example Hostname is giga vlan f cat etc hostname aggr2001 giga vlan 2 Define the relation between the IP address and the hostname in the etc inet hosts file Example Hostname is giga vlan and its IP address is 192 168 151 1 f cat etc inet hosts 192 168 151 1 giga vlan 3 Reboot the system shutdown y g0 i6 Solaris 11 The following example shows how to activate the aggr link aggr1 LinkAggregation Group and start the LinkAggregation 3 IP address 192 168 150 1 is assigned to the representative interface aggrl ifconfig aggrl plumb 192 168 150 1 up 3 After rebooting the system the representative interface aggrl is not activated The following example shows how to setup the aggr link lt aggrl LinkAggregation Group for activation after rebooting the system IP address 192 168 150 1 is assigned to the representative interface aggr1 45 1 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 f cat etc hosts 192 168 150 1 giga lacp 2 Setup the hostname and prefix length to aggrl by ipadm 1M command Example Hostname is giga lacp and p
65. erfaces and aggr link aggrl f usr sbin dladm create aggr 1 net2 1 net3 1 net4 aggrl 2 Activate the LinkAggregation Group Solaris 10 8 07 or later The following example shows how to activate the key 1 LinkAggregation Group and start the LinkA ggregation 1 IP address 192 168 150 1 is assigned to the representative interface aggr1 ifconfig aggrl plumb 192 168 150 1 up After rebooting the system the representative interface aggrl is not activated The following example shows how to setup the key 1 LinkAggregation Group for activation after rebooting the system IP address 192 168 150 1 is assigned to the representative interface aggr1 44 1 Describe the hostname in the etc hostname aggrl file Example Hostname is giga lacp f cat etc hostname aggrl giga lacp 2 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 f cat etc inet hosts 192 168 150 1 giga lacp 3 Reboot the system shutdown y g0 i6 The following example shows how to create a VLAN interface with the key 1 LinkAggregation Group 2 IP address 192 168 151 1 is assigned to the VLAN interface aggr2001 of VID 2 ifconfig aggr2001 plumb 192 168 151 1 up 2 After rebooting the system the VLAN interface aggr2001 is not activated The following example shows how to setup the VLAN int
66. ers 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 Setinstance 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 Host Bus Interface PCI Express 1 0a SEOX7GD1X SEOX7GD2X PCI Express 1 1 SEOX7GQIX SEOX7GQ2X 1000Base SX 2ports SEOX7GD2X Network Interface 10 100 1000Base T 2ports SEOX7GD1X 10 100 1000Base T
67. es It is necessary to inactivate a corresponding interface with the ifconfig 1M command before JumboFrame has been enabled with Method 3 Then activate a corresponding interface with the ifconfig 1M command after enabled When using the JumboFrames feature with the SEOX7GD1X SEOX7GQIX or SEOX7GQ2X use 1000Mbps mode The JumboFrame function setup in etc hostname fjgi or fjgi conf files after system started may not become effective after hot plug or installation with the DR Dynamic Reconfiguration and PCI Hot Plug functions Check the JumboFrame function with the ndd 1M command or dladm 1M command Solaris 11 only If the JumboFrame function is not correct reboot the system and the JumboFrame function will become effective When the interface is connected to a LAN switch it is necessary to enable the JumboFrame feature on the LAN switch For more information on the JumboFrame feature of the LAN switch please refer to the specifications of each LAN switch 27 3 5 3 Using the ndd 1M command By using the ndd 1M command the interface communication mode can be changed dynamically Usually it is not necessary to change the interface communication mode using the ndd 1M command but when you experience the following please change the interface communication mode using the ndd 1M command This method is not supported by FUJITSU PCI GigabitEthernet 5 0 or later Example Youchanged a remote device from one which supports
68. f packets processed can be reduced and lowering the CPU load is possible JumboFrame can be enabled using either of the following three procedures Method 1 Specify in etc system and etc hostname fjgi When MTU settings must be individually set for each interface or when the application uses etc hostname fjgi please use this method 1 Add the following line to the etc svstem file set fjgi fjgi jumbo 1 2 The MTU of TCP IP is set by defining an MTU size between 1500 and 9000 in etc hostname fjgi 1 in the following format and then rebooting the system When no MTU value is specified in this file the default value is set 9000bytes The asterisk expresses an instance number When IPv6 interface is used assign an IP address or hostname and an MTU size to the fjgi interface by editing the etc hostname6 fjgi file Setting format hostname mtu MTU Example of setting when setting MTU of fjgiO to 8000 f cat etc hostname fjgiO myhost mtu 8000 3 Reboot the system Method 2 Specify in fjgi conf File When MTU settings must be individually set for each interface or when the application does not use etc hostname fjgi example PRIMECLUSTER CF Cluster Foundation or CIP Cluster Interconnect Protocol function please use this method Refer to the 3 5 1 Setting the fjgi conf File for the setting procedures of JumboFrame Setting method of new style Recommended Example of file description The M
69. g 0 Auto Negotiation Off Forced mode 1 Auto Negotiation On default The Role setting when operating at 1000Mbps used with SEOX7GD1X SE0X7GQ1X SEOX7GQ2X only 0 Slave 1 Master 2 Auto default Set link partner to 1OMbps FullDuplex by Auto Negotiation 0 Disabled 1 Enabled Set link partner to 10Mbps HalfDuplex by Auto Negotiation 0 Disabled 1 Enabled Set link partner to 100Mbps FullDuplex by Auto Negotiation 0 Disabled 1 Enabled Set link partner to 100Mbps HalfDuplex by Auto Negotiation 0 Disabled 1 Enabled Set link partner to 1000Mbps FullDuplex by Auto Negotiation 0 Disabled 1 Enabled Set link partner to 1000Mbps HalfDuplex by Auto Negotiation 0 Disabled 1 Enabled 30 Set link partner to transmit pause frame bv Auto Negotiation Ip pauseTX Read only 0 Disabled 1 Enabled Set link partner to receive pause frame by Auto Negotiation Ip pauseRX Read only 0 Disabled 1 Enabled Set link partner to Auto Negotiate Ip autoneg cap Read only 0 Disabled 1 Enabled The current Role setting when operating at 1000Mbps used with SEOX7GD1X SE0X7G01X SE0X7G02X only role cap Read only 0 Slave 1 Master TA Read only 0 JumboFrame support disabled 1 JumboFrame support enabled Time to wait for an interrupt for receiving is specified micro seconds R Tick Read onl eceiveTicks ead only 0 to 1000 default 77 Time to wait for an interrupt for transmitting is specified
70. hdx cap 0 ndd set dev fjgi adv autoneg cap 0 Note Status to change The last command above changes the Auto Negotiation setting The ndd 1M Command Parameters This causes the Link and is required to make the settings effective The following parameters can be used with the ndd 1M command Parameters Read only Display parameter list link status link speed flow control Read only Read only Read only Read only Read only Read only 0 Link down 1 Link up 10 10Mbps 100 100Mbps 1000 1000Mbps Half Duplex Full Duplex Auto Negotiation is Off Auto Negotiation is On None flow control disabled LocSend Can transmit pause frame only Rem Can receive pause frame only Sym Can receive and transmit pause frame SX SEOX7GD2X T SEOX7GD1X SE0X7G01X SE0X7G02X 29 adv 1000fdx cap adv 1000hdx cap adv autoneg cap 10Mbps FullDuplex Setting 0 Disabled 1 Enabled default 10Mbps HalfDuplex Setting 0 Disabled 1 Enabled default 100Mbps FullDuplex Setting 0 Disabled 1 Enabled default 100Mbps HalfDuplex Setting 0 Disabled 1 Enabled default 1000Mbps FullDuplex Setting 0 Disabled 1 Enabled default 1000Mbps HalfDuplex Setting 0 Disabled 1 Enabled default Transmit Pause Frame Setting 0 Disabled 1 Enabled default Receive Pause Frame Setting 0 Disabled 1 Enabled default Auto Negotiation Settin
71. he 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 fjgiO is set to Auto Negotiation is disabled Connect at 100Mbps and Half Duplex operation is enabled Example 2 The parameters for fjgil 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 fjgil 100 Half Auto 1500 Off Auto The following is added to the fjgi conf file fjgil lt 100 Half Auto 1500 Off Auto Example 3 The parameters for fjgiO is set to Auto Negotiation is enabled Connect at 100Mbps and Full Duplex operation is enabled Example 4 The parameters for fjgil 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 fjgil 100 Full Auto 1500 On Auto The following is added to the fjgi conf file fjgil lt 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
72. ing on system configuration When using VLAN functionalitv provide sufficient memory resources to ensure optimal system performance 39 Chapter 4 LinkAggregation Feature This chapter outlines the LinkA ggregation 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 It is effective when handling large amounts of data or when providing large scale customer service As long as at least one transmission route available is available communication will continue 2 The maximum number of interfaces in a group is 255 OConventional method OLinkAggregation feature Three different IPs i l A single IP IPl IP2 IP3 IPl Three different NICs O A single virtual NIC NIC1 NIC2 NIC3 NICI NIC2 NICS SW SW SW SW LAN LAN LAN segmenti LAN segment 3 segment Server with Ex High speed segment 2 redundant large capacity transmission NFS server lines Requirements Table 4 1 Requirements show requirements for the LinkAggregation feature Table 4 1 Requirements OS Solaris 10 8 07 or later Server model SPARC Enterprise GLDv3
73. ion dladm show aggr This section explains the dladm show aggr command for displaying statistics and information for LinkAggregation Groups 53 Svnopsis Solaris 10 8 07 or later usr sbin dladm show aggr s l 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 L Specify to display detailed LinkAggregation Information key Specify the key number to identify the LinkAggregation Group Specify a number ranging from 1 to 999 Display the LinkA ggregation Information when all options are omitted Solaris 11 usr sbin dladm show aggr Lx aggr link L Specify to display detailed LinkAggregation Information x Specify to display extended LinkAggregation Information aggr link The name of the representative interface Display the LinkAggregation Information when all options are omitted Note CO 0008000000 00000008 80 0 0 0 00 80000 0 0 000000 0 0 0 0 0 0 0 8 8 00 0 0 0 0 0 0 0800 0 0 0 0 00 00000000 LinkA ggregation statistics can be displayed by dlstat 1M For more information about the dlstat 1M command please refer to the man pages section 1M System Administration Commands of Oracle Documentation Description Display statistics and i
74. ke the LinkAggregation Group for the fjgi interface in the Global Zone with the LinkAggregation creation procedure written in Chapter 4 LinkAggregation Feature Solaris 10 8 07 or later Example Adding aggrl which is a LinkAggregation Group with fjgi0 fjgil fjgi2 and key 1 to a Shared IP Non Global Zone zonel Execute the following commands in the Global Zone f usr sbin dladm create aggr d fjgi0 d fjgil d fjgi2 1 ifconfig aggrl plumb f zonecfg z zonel zonecfg zonel gt set ip type shared zonecfg zonel gt add net zonecfg zonel net gt set address 192 168 160 1 24 zonecfg zonel net gt set physical aggrl zonecfg zonel net gt end zonecfg zonel gt exit Note 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 4 zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command zoneadm z zonename reboot Solaris 11 Example Adding aggrl which is a LinkAggregation Group with fjgiO this vanity name is net2 fjgil this vanity name is net3 fjgi2 this vanity name is net4 to a Shared IP Non Global Zone zonel Execute the following commands in the Global Zone f usr sbin dladm create aggr 1 net2 1 net3 1 net4 aggri ifconfig aggri plumb ft zonecfg z zonel zonecfg zonel gt set ip type shared zonecfg zonel add net zonecfg zonel net set address 192 168 16
75. le Creating VNICs vnic2 1 and vnic2 2 over fjgiO 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 4 dladm show vnic LINK OVER SPEED MACADDRESS MACADDRTVPE vnic2 1 net2 1500 2 8 20 a5 f6 e4 random vnic2_2 net2 1500 2 8 20 82 b 7a random The following example shows how to create a VLAN interface over a VNIC dladm create vnic dladm create vnic l link v vlan id vnic link link physical link vnic id VID vnic link link name of VNIC Example Creating a VLAN interface over a VNIC vnic2004 of fjgi2 this vanity name is net4 f dladm create vnic l net4 v 2 vnic2004 The following example shows how to display VLAN interfaces on VNICs dladm show vnic dladm show vnic vnic link vnic link link name of VNIC Example Displaying a VLAN interface vnic2004 f dladm show vnic LINK OVER SPEED MACADDRESS MACADDRTVPE vnic2004 net4 1500 2 8 20 02 3 5 random The following example shows how to create a flow over a VNIC flowadm add flow flowadm add flow l link a attr value p prop value flow link physical link attr value attribute and value prop value property and value flow flow name Example Creating a flow vnic2 1flow with transport tcp as an at
76. m remove aggr l ether linkdev l l ether linkdev aggr link l ether linkdev 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 aggr link The name of the representative interface Description Removes interfaces from a LinkAggregation Group Exit Code 0 normal end 20 abnormal end Example Processes to remove interfaces from a LinkAggregation Group are shown below 52 Svstem Image aggrl figi0 fjgil fjgi2 LinkA ggregation LAN Switch LinkAggregation enabled To other hosts Solaris 10 8 07 or later The following example shows how to remove the interface fjgi2 from the key 1 LinkA ggregation Group f 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 aggri LinkAggregation Group f usr sbin dladm remove aggr 1 net4 aggrl i Note If the LACP mode is off do not use this command After rebooting the system the LinkAggregation settings remain effective For more information about this command please refer to the man pages section 1M System Administration Commands of Oracle Documentation 4 2 1 6 Display LinkAggregation Statistics and Informat
77. mit licks default 500 transmitting is specified micro seconds 5 1 to 500 3 The number of buffer descriptor to wait ReceiveMaxBD eceiveMax default 10 for an interrupt for receiving is specified 5 18 1 to 500 3 The number of buffer descriptor to wait T itMaxBD ransmitMax default 128 for an interrupt for transmitting is specified 5 LinkSpeed A DuplexCapabilities A lt FlowControl_A gt lt fjgi_mtu gt Parameter setting values are specified for lt AutoNegotiation_A gt every instance Foi jgi 6 lt Role_A gt Refer to the description of each parameter lt ReceiveTicks gt for the meaning of each value lt TransmitTicks gt lt ReceiveMaxBD gt lt TransmitMaxBD gt 7 Parameter is supported on 10 100 1000Base T SEOX7GD1X SEOX7GQ1X 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 SEOX7GD1X SEOX7GQIX 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
78. nformation for LinkAggregation Groups Exit Code 0 normal end 20 abnormal end Example Processes to display the statistics and LinkAggregation Information of LinkAggregation Groups are shown below Solaris 10 8 07 or later The following example shows how to display the LinkAggregation Information for the key 1 LinkAggregation Group f usr sbin dladm show aggr 1 key 1 0x0001 policy L4 address 0 0 77 9f 3e d5 auto device address speed duplex link state fjgil 0 0 77 9f 3e d5 1000 Mbps full up standbv fjgi2 0 0 77 9f 3e d6 1000 Mbps full up standby fjgi3 0 0 77 9f 3e d7 1000 Mbps full up standbv 54 The following example shows how to display the detailed LinkAggregation Information for the key 1 LinkAggregation Group f 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 fjgil active short ves ves yes yes no no fjgi2 active short yes yes yes yes no no fjgi3 active short yes yes yes yes no no The following example shows how to display the statistics for the key 1 LinkAggregation Group f usr sbin dladm show aggr s 1 key 1 ipackets rbvtes opackets obvtes Sipkts opkts Total 2474 245586 0 0 fjgal 1237 122793 0 0 50 0 fjgi2 1237 122793 0 0 50 0 fjgi3 0 0 0 0 0 0 Solaris 11 The following example shows how to display the LinkA ggregation Informa
79. nly when SEOX7GD1X SEOX7GQ1X SEOX7GQ2X are used in 1000Mbps environments Messages which are reported remotely by the Machine Administration function included in Enhanced Support Facility are listed in the following table 60 Table A 4 Messages Reported bv Machine Administration nof Meme tems veterane The version number of the driver mav not support this hardware Please applv anv a A Up An error occurred during applicable patches described in the figi d heck fjgi hw deinit failed aa pee initialization of the adapter Installation Guide If the problem persists there is a possibility of hardware abnormalities Please replace the adapter T l om m An error occurred during There is a possibility of hardware fjgi device check fjgi hw init failed l SM la ne initialization of the adapter abnormalities Please replace the adapter There is a possibility of a resource The driver could not allocate lior lied b liti shortage or hardware abnormalities pci_config_setup_failed sufficient PCI configuration i Please check the memory usage and space P adapter installation status 4 Aut tiation failed The Auto Negotiation of Check the transmission mode and the utonegotiation faile i 1000BASE SX failed adapter hardware 61 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
80. nstalled physical b Allocating of the memory DD CAPE QU d a he soft state alloc failed insufficient If this is not the cause report resource failed h l j this error to your service provider 2 oni f descript failed The driver could not allocate CU E a E We internal resources for DMA Installed physical memory may be insufficient If this is not the cause report ld not allocate DMA handl i The driver could not allocate this error to your service provider Could not bind descriptor memory DMA resources Re activate the interface If this message An error was found in message Multiple fragments in descriptor area is still displayed report to your service fragmentation Mappi f the adapt Unable to map adapter registers apping iE SEE registers failed ddi get iblock cookie ERROR The driver could not allocate nne physical Seon Ed be insufficient If this is not the cause report Unable to install interrupt routine Interrupt resources this error to your service provider ATTACH failed The driver was not loaded to the kernel successfully With SEOX7GD2X the remote With SEOX7GD2X only full duplex is provider Dupl invalid Pl h th T s aure die ani device is using half duplex available Change the duplex mode of the partner s duplex Full mode remote device to Full information failed possibility of hardware abnormalities Please replace the adapter ddi intr block enable failed Try re enabling the
81. ntation 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 a 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 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 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 SEOX7GD2X Gigabit Ethernet card Connect a CAT5e Enhanced Category 5 twisted pair cable to the connector of the SEOX7GD1X SEOX7GQ1X and SEOX7GQ2X Gigabit Ethernet cards Figure 2 1 SEOX7GD2X with Multimode Optical Fiber Cable Figure 2 2 SEOX7GD1X with Twisted Pair CAT5e Cable Figure 2 3 SEOX7GQIX with Twisted Pair CAT5e Cable Figure 2 4 SEOX7GQA2X with Twisted Pair CAT5e Cable
82. nterface by editing the etc hostname fjgi file where fgi represents the driver 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 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 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 s 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 syst
83. nterfaces are displayed by the following command dladm show link or dladm show vlan Example f dladm show link net2 net2002 net3 net4 net5 net231005 L 4 dladm show vlan net2002 net231005 In the above example the VLAN interfaces are displayed as net2002 VID 2 and net231005 VID 231 Please refer to 3 2 Identification of Interface Name for details about the relationship of fjgi to net where represents an instance number To delete VLAN interfaces the following is used It is necessary to inactivate a corresponding interface with the ifconfig 1M command before executing the following command dladm delete vlan vlan link Example dladm delete vlan net2002 dladm delete vlan net231005 Note When connecting VLAN interfaces to a LAN switch the switch must support Tag VLAN On the switch set VLAN tagging and VLAN ports appropriately based on the VLANS setup on the server Use the VLAN interface only with the TCP IP In a PRIMECLUSTER environment when using a VLAN interface check that the SMAWdtcp package has not been installed If SMAWdtcp is installed remove the package before setting up the VLAN interface or do not use the VLAN interface A VLAN interface uses approximately 700Kb of memory when MTU is 1500 or 900Kb of memory when MTU is 9000 in an idle state Therefore when using two or more VLAN interfaces a system slowdown may occur due to a shortage of resources depend
84. ommand in the Exclusive IP Non Global Zone ifconfig fjgil002 plumb 192 168 170 1 up Solaris 11 Execute the following commands in the Global Zone dladm create vlan 1 net4 v 1 f zonecfg z zone2 zonecfg zone2 set ip type exclusive zonecfg zone2 add net zonecfg zone2 net set physical net1004 zonecfg zone2 net gt end zonecfg zone2 exit Notel net4 is the vanity name of fjgi2 Note2 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 f zoneadm z zonename boot If the Exclusive IP Non Global Zone has booted execute the following command f zoneadm z zonename reboot 2 Execute the following command in the Exclusive IP Non Global Zone ifconfig net1004 plumb 192 168 170 1 up When a LinkA ggregation is used in Exclusive IP Non Global Zones please make the LinkAggregation Group in the Global Zone with the creation procedure in Chapter 4 LinkAggregation Feature Also add the representative LinkAggregation interface to the Exclusive IP Non Global Zones and then make the representative LinkA ggregation interface active using the ifconfig 1M command in the Exclusive IP Non Global Zones Solaris 10 8 07 or later Example Adding aggr2 which is a LinkAggregation Group with fjgi0 fjgil fjgi2 and key 2 to an Exclusive IP Non Global Zone zone2 71 1 Execute the following commands in the
85. ormation about this command please refer to the man pages section 1M System Administration Commands of Oracle Documentation 4 3 Notes This section explains notes for using the LinkAggregation function Only TCP IP connection is supported If a VLAN interface is made with the LinkA ggregation feature the following must be satisfied The number of VLAN interfaces the number of physical interfaces in group the number of groups 1024 If this is not satisfied the system may not work correctly due to lack of memory resource The link speed must be the same among the member interfaces in a LinkAggregation Group and duplex mode must be set to full In a cluster system fail over of LinkAggregation interfaces on a public LAN is not supported When the interfaces are connected to a LAN switch it is necessary to enable the LinkAggregation function on the LAN switch For more information about the LAN switch and the LinkAggregation function please refer to the specifications of each LAN switch It is necessary to inactivate corresponding LinkAggregation Groups with the ifconfig 1M command before DR Dynamic Reconfiguration or PCI Hot Plug is performed It is necessary to activate corresponding LinkAggregation Groups with the ifconfig 1M command after DR or PCI Hot Plug is completed VLAN interfaces can not be specified directly as interfaces belonging to the LinkAggregation Group It is necessary to create the VL
86. ot 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 fjgiO this vanity name is net2 1 ipadm create ip net2 f 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 fjgiO this vanity name is net2 ipadm create ip net2 f ipadm create addr T addrconf net2 v6addrconf f ipadm create addr T static a fe80 2e0 ff fea6 2222 120 net2 v6static When you use a hostname please see section 2 Edit the etc hosts file first 14 a 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 f 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 th
87. peed 100 Execute the following command to set Half Duplex communication 100Mbps ok transfer speed 100 ok half duplex Execute the following command to set Full Duplex communication 10bps ok transfer speed 10 35 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 SEOX7GDIX card installed in a SPARC Enterprise M9000 6 ok cd pci 4 600000 pci 0 FISV e2ta 4 6 ok properties duplex half xc Way transfer speed 0000000a lt 2 status okay assigned addresses 82032010 00000000 00100000 00000000 00010000 82032018 00000000 00110000 00000000 00010000 82032030 00000000 00120000 00000000 00010000 local mac address 00 e0 ed 12 a8 3c fjgiga rev 000000c3 product name FJSV e2ta device type network address bits 00000030 max frame size 00004000 reg 00032000 00000000 00000000 00000000 00000000 03032010 00000000 00000000 00000000 00010000 03032018 00000000 00000000 00000000 00010000 02032030 00000000 00000000 00000000 00010000 model Broadcom BCM5715C compatible fjgi name FJSV e2ta media type 1000BASE T version 1 0 fcode rom offset 00000000 66mhz capable fast back to back devsel speed 00000001 latency timer 00000040 max latency 00000000 min grant 00000040 interrupts 00000001 cache line size 000
88. r Execute the following commands in the Global Zone ifconfig fjgil000 plumb ft zonecfg z zonel zonecfg zonecfg zonecfg zonecfg zonecfg zonecfg Note Solaris 11 zonel set ip type shared zonel gt add net zonel net gt set address 192 168 160 1 24 zonel net set physical fjgil000 zonel net end zonel exit 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 f zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command zoneadm z zonename reboot Execute the following commands in the Global Zone dladm create vlan 1 net2 v 1 zonecfg z zonel zonecfg zonel set ip type shared zonecfg zonel add net zonecfg zonel net gt set address 192 168 160 1 24 69 zonecfg zonel net set physical net1002 zonecfg zonel net end zonecfg zonel 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 fjgiO 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 zoneadm z zonename boot If the Shared IP Non Global Zone has booted execute the following command ft zoneadm z zonename reboot When a LinkAggregation is used in Shared IP Non Global Zones please ma
89. r hosts Solaris 10 8 07 or later The following example shows how to add the interface fjgi3 to the key 1 LinkAggregation Group f 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 lt aggrl LinkAggregation Group f usr sbin dladm add aggr 1 net5 aggrl Note Ifthe LACP mode is off do not use this command After rebooting the system the LinkAggregation settings remain effective For more information about this command please refer to the man pages section 1M System Administration Commands of Oracle Documentation Ce ooo 00000000 0000000 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 80 0 0 0 0 0 0 0 0 0 8 8 8 0 0 0 0 0 0 8 8 0 0 0 0 0 0 0 0 8 8 0 8 8 0 0 8 0 8 0 0 8 0 0 0 0 8 0 0 00000 00 00 4 2 1 5 Remove Interfaces from a LinkAggregation dladm remove aggr This section explains the dladm remove aggr command for removing interfaces from a LinkA ggregation 51 Svnopsis 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 key Specify the key number to identify the LinkAggregation Group Specify a number ranging from 1 to 999 Solaris 11 usr sbin dlad
90. refix length is 24 ipadm create ip aggrl ipadm create addr T static a giga lacp 24 aggrl v4static The following example shows how to create a VLAN interface with the aggr link lt aggrl LinkAggregation Group 4 IP address 192 168 151 1 is assigned to the VLAN interface aggr2001 of VID 2 4 dladm create vlan l aggrl v 2 ifconfig aggr2001 plumb 192 168 151 1 up 4 After rebooting the system the VLAN interface aggr2001 is not activated The following example shows how to setup the VLAN interface with the aggr link aggr1 LinkAggregation Group for activation after rebooting the system IP address 192 168 151 1 is assigned to the VLAN interface aggr2001 of VID 2 1 Create the VLAN interface by dladm 1M command 2 Example the VLAN interface aggr2001 of VID 2 4 dladm create vlan l aggrl v 2 3 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 f cat etc hosts 192 168 151 1 giga vlan 4 Setup the hostname and prefix length to aggr2001 by ipadm 1M command Example Hostname is giga lacp and prefix length is 24 ipadm create ip aggr2001 ipadm create addr T static a giga vlan 24 aggr2001 v4static Before creating a LinkA ggregation Group all interfaces to be assigned to the group must be in an inactive state By using the dladm create aggr command the policy the
91. rm sun4v kernel drv fjgi conf 2 SPARC Enterprise Mxxxx series platform SUNW SPARC Enterprise kernel drv fjgi conf Examples of setting parameters in the fjgi conf file are shown below Example 1 The parameters for fjgi0 the instance number 0 port of SEOX7GQIX 10 100 1000BASE T is set to Auto Negotiation is disabled Connect at 100Mbps and Half Duplex operation is enabled The parameter values need to be set by a character string like name fjgi parent pci 1 700000 pci 0 unit address 4 AutoNegotiation_A Off LinkSpeed_A 100 DuplexCapabilities A Half The following is added to the fjgi conf file name fjgi parent pci l 700000 pci 0 unit address 4 AutoNegotiation A Off LinkSpeed_A 100 DuplexCapabilities A Half Example 2 The parameters for fjgi4 the instance number 4 port of SEOX7GD2X 1000BASE SX is set to Auto Negotiation is enabled Connect at 100Mbps and Full Duplex operation is enabled The parameter values need to be set by a character string like name fjgi parent pci 2 600000 pci 0 unit address 4 AutoNegotiation_A On LinkSpeed A 100 DuplexCapabilities A Full The following is added to the fjgi conf file name fjgi parent pci 2 600000 pci 0 unit address 4 AutoNegotiation A On LinkSpeed A 100 DuplexCapabilities A Full Example 3 The MTU parameter for fjgi9 the instance number 9 port of SEOX7GQ2X 10 100 1000BASE T is set to 8000 Th
92. small the latency will be improved but the throughput will fall 25 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 are specified at the same time the driver gives priority to the How to set a parameter to each instance When a Gigabit Ethernet card is removed please remove the setting parameters of the applicable adapter defined in the fjgi conf file If an adapter is removed and the setting parameters are left in the fjgi conf file a panic may occur at system boot causing boot failure Because the parameters are set in the fjgi conf file per physical interface when a VLAN interface is used individual interfaces used by the VLAN interface must be similarly configured The operation mode setup in the fjgi conf file after system boot may not become effective after installation with DR Dynamic Reconfiguration or PCI Hot Plug functions Check the operation mode with the ndd 1M command or dladm 1M command Solaris 11 only If the operation mode is not correct reboot the system and the desired operation mode will become effective 3 5 2 JumboFrame Setup By using a JumboFrame the TCP IP MTU can be expanded from 1500 to 9000 By expanding the single packet transmission size the number o
93. t the same time the resulting value will be invalid If the ndd 1M command is executed repeatedly the fjgi driver s performance may decrease The link speed link mode autonego and flow control parameter values are valid only when link status 1 If link status 0 these values are invalid 31 The values of Ip 10fdx cap lp 10hdx cap Ip 100fdx cap Ip 100hdx cap lp 1000fdx cap lp 1000hdx cap lp pauseTX lp pauseRX and Ip autoneg cap parameters are valid only when Auto Negotiation is successfully established These parameter values are invalid when Auto Negotiation is disabled or when Auto Negotiation fails The parameter values set by the ndd 1M command become invalid after rebooting the system Operation mode setting using the ndd 1M command becomes effective for each physical interface Therefore the operation modes of the VLAN interface and IPv4 IPv6 interface are changed at the same time 3 5 4 Using the dladm 1M command By using the dladm 1M command the interface communication mode can be changed dynamically Usually it is not necessary to change the interface communication mode using the dladm 1M command but when you experience the following please change the interface communication mode using the dladm 1M command This method can be used only by FUJITSU PCI GigabitEthernet 5 0 or later Example Youchanged a remote device from one which supports Auto Negotiation to another which does not support
94. ta Green OFF The card is not connected to a 1000Mbps 100Mbps or 10Mbps network and the card is not transmitting or receiving network data Location of the LEDs SE0X7GQ1X SE0X7GQ2X The following figures show the location of the LEDs on SEOX7GQIX and SEOX7GQ2X 63 Figure B 3 10 100 1000Base T 4ports SEOX7GQ1X LNK ACT Figure B 4 10 100 1000Base T 4ports SEOX7GQ2x Port 1 Port2 Port3 Porta 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 ON Amber The card is connected to a 1000Mbps network and is ready to communicate ON Green The card is connected to a 100Mbps network and is ready to communicate The card is connected to a 10Mbps network and is ready to communicate or the card is not connected to a network ACT LED Green LED in Figure B 3 B 4 indicates the following operation status 64 ON Green The card is transmitting or receiving network data The card is not transmitting or receiving network data 65 Appendix C Using FUJITSU PCI GigabitEthernet in a Cluster Environment This Appendix outlines the supported functions and setup procedure for the FUJITSU PCI GigabitEthernet 4 1 or later or the FUJITSU PCI GigabitEthernet 5 0 or later interface when used in a cluster environment PRIMECLUSTER C 1 Cluster Environment Support The F
95. tance Number prtconf D grep fjgi example f prtconf D grep fjgi FJSV e4ta instance 0 FJSV e4ta instance 1 FJSV e4ta instance 2 FJSV e4ta instance 43 FJSV e2sa instance 4 FJSV e2sa instance 45 driver name fjgi driver name fjgi driver name fjgi driver name fjgi driver name fjgi driver name fjgi 15 FJSV e2ta instance 6 FJSV e2ta instance 47 FJSV e4tb instance 8 FJSV e4tb instance 49 FJSV e4tb instance 10 driver name fjgi driver name fjgi driver name fjgi driver name fjgi 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 In this example the following types of installed Gigabit Ethernet cards can be identified e4ta SEOX7GQIX e2sa SEOX7GD2X e2ta SEOX7GD1X and e4tb SEOX7GQ2X 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 f more etc path to inst grep fjgi pci81 700000 pci80 FJSV e4taQ4 0 fjgi pci81 700000 pci80 FJSV e4ta84 1 1 fjgi pci81 700000 pciQ0 1 FJSV e4taG6 2 fjgi pci81 700000 pci80 1 FJSV e4ta86 1 3 fjgi p
96. te device supports Auto Negotiation Use the following procedure and examples to change FCode settings Changing the FCode settings is possible on SEOX7GD2X SEOX7GD1X SEOX7GQ1X SEOX7GQ2X How to Set FCode Force Mode Fixed Speed Disabled Auto Negotiation Search for the device path for the Gigabit Ethernet card at the ok prompt after the system was stopped by a command like shutdown i0 g0 y Please refer to chapter 3 4 Identification of the Gigabit Ethernet Card example show nets pci81 700000 pciQ0 FJSV e2taQ4 1 pci 1 700000 pci 0 FISV e2tae4 pci 0 600000 pci 0 1 network 1 1 pci 0 600000 pci 0 1 network l NO SELECTION Enter Selection q to quit In above example a pci 1 700000 pci 0 FISV e2ta 4 1 and b pci 1 700000 pci O FIS V e2ta 9 4 represent an SEOX7GDIX card Select the device as follows example ok cd pci81 700000 pciQ0 FJSV e2taQ4 Execute the following command to change the mode to Force mode speed fixed Auto Negotiation off from Auto Negotiation mode FCode settings are effective only during OBP Open Boot Prom 1 The only mode which can be set on SEOX7GD2X 1000BASE SX is as follows Execute the following command to set Full Duplex communication 1000Mbps ok transfer speed 1000 2 The available modes which can be set on SEOX7GD1X SE0X7G01X SE0X7G02X are as follows Execute the following command to set Full Duplex communication 100Mbps ok transfer s
97. te li eve ERN anii ipid T 33 2 JumboFrame a E EZAERAOAZ OPSET px dg tlie mad EM ami EM 3 5 4 Using the dladm 1M command e a TAN O DE c0id nrilriro EN FE VEAN Mion O A O O O RE RO KOT RON TI A LIEBE REUS TO Tas VE RIN pe a p ete i pe et PE UE EE TO RE ea PE L PE ENS aAA Je NI IER Chapter 4 LinkAggregation Features E b ensued 40 2 1 About LES ee A NAN CRIN sa A rer d tni ROTER tam a Qa at 40 4 2 Configuration of the Link Agere pation Feature eee ionis rrt ntn RH EE FEAR DET EE Eee ERE eei PEE ER Fe 42 4 2 1 Setting and Displaying the Configuration with the dladm 1M Command nena 42 4 2 1 1 Create a LinkAggregation dladm create aggr 4 2 1 2 Delete a LinkAggregation dladm delete aggr 4 2 1 3 Modify a LinkA sere ration dladm modif y AEBE eret rte rnnt torri ear hire ae 48 4 214 Add Interfaces to LinkAgeregation dladm addesgar aesti terret reet ree rg nb pe reina 50 4 2 1 5 Remove Interfaces from a LinkAggregation dladm remove aggr eese eene 51 4 2 1 6 Display LinkAggregation Statistics and Information dladm show aggr eene 53 o 56 NE Meo cli wn pa RPM 57 eoa pq o o MM A 1 Console Messages from the Driver
98. terprise T5440 2CPU SPARC T3 1 SPARC T3 2 87
99. the form of net fjgi interface the form of fjgi In the above example it is displayed that net2 is fjgiO net3 is fjgil 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 letc inet hosts file or etc inet ipnodes file letc inet netmasks file 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 7gi file Assign an IP address or hostname to the fjgi i
100. tion for the aggr link aggr1 LinkA ggregation Group dladm show aggr aggrl LINK POLICY ADDRPOLICY LACPACTIVITY LACPTIMER FLAGS aggrl L4 auto active The following example shows how to display the detailed LinkAggregation Information for the aggr link aggri LinkA ggregation Group 4 dladm show aggr L aggrl LINK PORT AGGREGATABLE SYNC DIST DEFAULTED EXPIRED aggrl net2 yes yes yes no no net3 yes yes yes no no net4 yes yes yes no no net2 net3 and net4 are the vanity name of fjgi0 fjgil and fjgi2 respectively The following example shows how to display the extended LinkAggregation Information for the aggr link aggri LinkAggregation Group f dladm show aggr x aggrl LINK PORT SPEED DUPLEX STATE ADDRESS PORTSTATE aggrl 1000Mb full up OFO sors net2 1000Mb full up SOs 772988 H attached net3 1000Mb full up 0 77 9 3e attached net4 1000Mb full up Fs Ora aa ALS bie attached net2 net3 and net4 are the vanity name of fjgi0 fjgil and fjgi2 respectively a Information The following example shows how to display the statistics for the aggr link lt aggrl LinkAggregation Group f dlstat show aggr aggrl LINK PORT IPKTS RBYTES OPKTS OBYTES aggrl Sala 47 73K 447 56 96K aggrl net2 125 16 09K 152 19 20K 55 aggrl net3 124 16 03K 147 18 82K aggrl net4 122 15 62K 148 18 94K net2 net3 and net4 are the vanity name of fjgiO fjgil and fjgi2 respectively sse For more inf
101. tribute maxbw 50 as a property over a VNIC vnic2 1 ft flowadm add flow 1 vnic2 1 a transport tcp p maxbw 50 vnic2 1flow Example Creating a flow vnic2 2flow with transport udp as an attribute maxbw 50 as a property over a VNIC vnic2 2 f flowadm add flow 1 vnic2 2 a transport udp p maxbw 50 vnic2 2flow The following example shows how to display flows over VNICs flowadm show flow flowadm show flow flow flow flow name Example Displaying flows vnic2 1 flow and vnic2 2 flow over VNICs vnic2 1 and vnic2 2 T flowadm show flow FLOW LINK IPADDR PROTO LPORT RPORT DSFLD vnic2 1 flow vnic2 1 tcp s vnic2 2 flow vnic2 2 m 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 VALUE DEFAULT POSSIBLE vnic2 1 flow maxbw 50 vnic2 2 flow maxbw 50 F 3 Notes For more information about Solaris 11 Network Virtualization please refer to System Administration Guide Network Interfaces and Network Virtualization and man pages section IM System Administration Commands of Oracle Documentation 78 Appendix G PCI Slot Number and Device Name This appendix provides a cross reference of PCI slot n
102. umbers 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 SPARC Enterprise T5140 SPARC Enterprise T5240 SPARC Enterprise T5440 4CPU SPARC Enterprise T5440 2CPU SPARC T3 1 SPARC T3 2 SPARC Enterprise M3000 PCIHO pci 0 600000 pci 0 pci 28 00 Logical Basic PCI PCHH pci 1 700000 pci 0 pci O 0 System Board 0 Slot PCI 2 pciQ 1 700000 pci 0 pci 8 0 PCI 3 pciQ 1 700000 pci 0 pci 9 0 SPARC Enterprise M4000 M5000 Basic PCI PCIHO pci 0 600000 pci O pci 8 pci 0 1 1 Slot PCIHI pci 0 600000 pci O pci 9 20 PCI 1 PCIX1 pci 0 600000 pci O pci 9 pci 0 pci I pci 0 4 PCHH PCIX2 pci 0 600000 pci 0 pci 9 pci O pci I pci 90 1 G4 PCIH1 PCHEH PCIX5 pci 20 600000 pci Q 0 pci Q 9 pci 0 pci 8 pci 0 9 4 IOBoat X PCI 1 PCIX6 pci 0 600000 pci 0 pci 9 pci 0 pci 8 pci 90 1 24 Logical System PCI 1 PCIX3 pci 20 600000 pci 0 pci 9 pci 0 pci 9 pci 0 4 Board 0 PCI I PCIX4 pci 0 600000 pci 00 pci 9 pci 0 pci 9 pci 0 1 4 PCI I PCIE1 pci 0 600000 pci 0 pci 9 pci 0 pci L pci 0 pci 0 0 PCI I PCIE2 pci 0 600000 pci 0 pci 9 pci 0 pci 1 pci 0 pci 1 0 PCI
103. ver could not allocate Error filling TX ring transmit resources provider a 10 status block can t alloced handle The de d could not allocate Installed physical memory may be status information resources f so fe insufficient If this is not the cause report status block can t bind handlel A this error to your service provider D fjgi board init mem Failed to The driver could not allocate dma alloc DMA resources statistic block can t alloced The dri ld not allocati hwmib block can t alloced handle A e dad a Mdb statistic information resources hwmib block can t bind handle fjgi board init mem Failed to dma The driver could not allocate alloc2 DMA resources The value of LinkSpeed A in Illegal value for LinkSpeed A the configuration file is Set the correct value for LinkSpeed A 8 fjgi hw init Step 22 failed 19 Bei he init Step 23 failed sa S occurred during A hardware tanus occ rred Please initialization of the adapter contact your service provider 20 fjgi hw init Step 43 failed Can t judge T or SX status block can t alloced n 13 14 15 incorrect Check whether the server is supported If The adapter type cannot be the system is supported there is a recognized possibility of hardware abnormalities Please replace the adapter There is a possibility of driver Other messages internal bug or hardware Report the error to your service provider failure N This appears o
104. was supported li Support switches was added o Changed the Version 2 1 to 2 2 ET Quad Gigabit Ethernet card PW008QG1 was supported 2005 11 11 Changed the Version 2 2 to 2 3 RoHS compliant 1 port Gigabit Ethernet Card PWOG8GE1 PWOG8GE2 was supported Changed the Version 2 3 to 2 4 PCI Express Gigabit Ethernet Card SEOX7GD1X SEOX7GD2X SEOX7CQ1X was 2007 1 20 supported Changed the Version 2 4 to 3 0 2007 4 03 Changed the Version 3 0 to 3 0 Updatel GLDv3 The LinkA ggregation Feature of dladm 1M command Solaris Containers 2008 2 29 Logical Domains was supported Changed the Version 3 0 Updatel to 3 0 Update2 4 0 Added the parameters and the setting method of new style to the operation mode setup 2010 2 1 Deleted the PRIMEPOWER and GP7000F family Changed the Version 3 0 Update3 4 0 Updatel to 3 0 Update3 4 1 Deleted the driver version 3 0 Update3 Changed the name of Solaris to Oracle Solaris 2010 12 17 Changed the name of Logical Domains LDoms to Oracle VM Server for SPARC Changed the Version 3 0 Update3 4 1 to 4 1 Updatel 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 2011 10 25 BE Added The SPARC T3 series Changed Sun Microsystems Documentation to Oracle Documentation Changed the Version 4 1 Updatel to 4 1 Update2 5

Fujitsu C120-E276-11ENZ0(A) Network Card User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents