Home

Fujitsu Update1 User's Manual

1. pciQa0 2000 1 pciQa0 4000 2 spite PCIS1A pciQal 2000 1 PCI 1B pciQal 4000 2 pciQa3 2000 PCI 3B pci a3 4000 2 PCIS0A pciQa4 2000 1 pciQa4 4000 2 spig PCIS1A 1 5 2000 1 5 4000 02 pci a7 2000 1 PCI 3B 4000 2 PCIS0A pci a8 2000 1 0 8 4000 02 apie pciQa9 2000 1 9 4000 02 pciQab 2000 1 PCI 3B pciQab 4000 2 PCIS0A pciQac 2000 1 pciQac 4000 2 SB LI PCIS1A pciQad 2000 1 PCI 1B pci ad 4000 2 PCI 3A pciQaf 2000 1 PCI 3B pciQaf 4000 2 PCIHOA pci b0 2000 01 PCISOB pci b0 4000 2 T PCI IA pci bl 2000 01 PCISIB pciObl 4000 2 pci b3 2000 1 PCI 3B pci b3 4000 2 PCIHOA pci b4 2000 01 pci b4 4000 02 SBHI3 PCI IA 5 2000 01 5 4000 02 pci b7 2000 0 PCI 3B pci b7 4000 2 PCIHOA pci b8 2000 01 PCISOB pci b8 4000 2 PCI IA pci b9 2000 0 pci b9 4000 02 PCIH3A pci bb 2000 01 PCI 3B pci bb 4000 2 PCIS0A pci bc 2000 1 pci bc 4000 02 SBHIS PCI IA 2000 1 pci bd 4000 02 pci bf 2000
2. ber Wwe et beh CBS 25 3 3 Operation Mode mls holt baad td dela pP DAN da bast esi d eb weed eae as 26 3 8 1 The tg et Cont Rid ote wile als iate bb dak ote pb bob iyd 26 3 3 2 JumboFrame Se blip iy ds doses dole chad Ma ees pA DE Pa bas tpe oe den Uno E healt 29 3 3 3 bale EET Qe bos Dope as wd sed dot neues 32 3 9 4 FECode SettihEgScs ded cadet ood Me das 36 3 4 Discernment Of the GigabitEthernet 39 3 4 1 Discernment Of the GigabitEthernet Interface PRIMEPOWER or GP7000 family 39 3 4 2 Discernment Of the GigabitEthernet Interface on SPARC 40 5 Network swore XU Ee qu LE IG teat dade 42 6 VLAN Inter tace iced epe me ban bibere IPLA Ie 45 6 1 802 10 M ER VERIOR IRSE 45 3 6 2 Setting Up the VLAN Interface ois onere eye eere 45 Chapter 4 LinkAgsrogdtion coms sn ce wad MER en cR D RD e 4T 4 1 About LinkAggresation Feature sso tet cece
3. Board Number Slot Number Device Name PCIZ3 PCIX6 013 700000 100 108 100 1 4 PCIS3 PCIX3 pci 13 700000 pci 0 pci 9 pci 0 O4 013 700000 100 109 100 1 4 PCI 3 PCIE1 pciQ13 700000 0 1 1 0 0 0 PCIS3 PCIE2 pciQ13 700000 pci 0 pci 1 pci 0 pci 1 0 PCI 3 PCIE3 pci 13 700000 1 0 1 1 1 0 1 9 0 pci 13 700000 1 0 1 9 1 0 1 0 0 PCIS3 PCIE5 pciQ13 700000 pci 0 pci 9 pci 0 pci 1 0 PCI 3 PCIE6 pciQ13 700000 1 0 1 9 1 0 1 9 0 Basic PCI 1014 600000 0 Slot 015 700000 00 Slot PCIS5 PCIXI pciQ15 700000 0 1 1 0 4 5 2 pci 15 700000 100 101 100 1 4 5 PCIS5 PCIX5 015 700000 1 0 1 8 1 0 4 IOBoat X PCIH5 PCIX6 15 700000 100 108 100 1 4 PCIS5 PCIX3 1 15 700000 pci 0 pci 9 pci 0 O4 PCI 5 PCIX4 pciQ15 700000 100 109 100 1 4 PCI 5 PCIE1 pciQ15 700000 pci 0 pci l pci 0 pci 0 0 PCI 5 PCIE2 pciQ15 700000 0 1 1 0 1 0 PCI 5 PCIE3 pci 15 700000 1 0 1 1 1 0 1 9 0 0 PCIR5 PCIEA
4. pci 80 2000 1 1080 2000 2 PCIZ2 1080 4000 3 1080 4000 04 PCI 4 pci 80 4000 5 PCI 5 1083 4000 3 75 Appendix D PCI Slot Number and Device Name 76 MEPOWER 250 20 rack mount Slot Number Device Name pci 83 2000 2 pci 83 4000 3 PCI 2 pci 83 4000 4 PRIMEPOWER 250 4U rack mount Slot Number Device Name 0 pci 80 2000 1 PCI 1 pci 80 2000 2 PCI 2 pci 80 4000 3 PCI 3 pci 80 4000 4 pci 80 4000 5 PCI 5 pci 83 4000 3 PRIMEPOWER 400 4U rackmount Slot Number Device Name 015 2000 1 PCI 2 015 4000 2 PCI 3 015 4000 4 PCI 4 017 2000 1 PCI 5 015 4000 5 6 017 4000 2 PRIMEPOWER 400 pedestal 100 rackmount Slot Number Device Name PCI 1 1016 4000 5 PCI 2 pci 16 4000 4 PCI 3 016 4000 2 PCI 4 015 2000 PCI 5 pci 16 2000 6 017 2000 PCI 7 015 4000 5 PCI 8 015 4000 4 PCI 9 015 4000 2 PCI 10 1017 4000 2 PRIMEPOWER 400 PPO40BR1U pedestal 100 rackmount Slot Number Device Name 00
5. Read only Display parameter list 33 Chapter 3 Setting Configuration Information parameter status meaning link_status Read only Link up 1000 1000Mbps link speed Read only 100 100Mbps 10 10Mbps 0 Half Duplex communication link_mode Read only 1 Full Duplex communication 0 Auto Negotiation is Off autonego Read only TE 1 Auto Negotiation is On 0 None flow control disabled 1 LocSend Can transmit pause frame only flow control Read only 2 Rem Can receive pause frame only 3 Sym Can receive and transmit pause frame 0 SX PWOO8GE4 PWOG8GE1 SEOX7GD2X 1 T PWOO8GE5 PWOG8GE2 SEOX7GD1X cardtype Read only PWOO8QG1 SEOX7GQ1X PRIMEPOWER250 450 secondary LAN port instance Read and write Instance Number 10Mbps FullDuplex Setting adv_l0fdx_cap Read and write 0 Invalid Valid Default OMbps HalfDuplex Setting adv lOhdx cap Read and write 0 Invalid Valid Default 00Mbps FullDuplex Setting adv 100fdx cap Read and write 0 Invalid Valid Default 100Mbps HalfDuplex Setting adv 100 cap Read and write 0 Invalid Valid Default 1000Mbps FullDuplex Setting adv 1000fdx cap Read and write 0 Invalid 1 Valid Default 1000Mbps HalfDuplex Setting adv 1000hdx Read and write 0 Invalid 1 Valid Default Transmit Pause Frame Setting adv pauseTX Re
6. Product Name Connection Available Function Name FUJITSU SH4322G OK LinkAggregation function 3Com Superstack 3 OK LinkAggregation function Hewlett Packard ProCurve 8000m OK Load Balancing function Extreme Networks Summit li 7i OK Load Sharing function CISCO Systems Catalyst3550 OK EtherChannel Function
7. pciQ3 700000 pci 0 pci 9 pci 0 pci 0 Q0 pciQ3 700000 pci 0 pci 9 pci 0 pci l 0 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name pciQ3 700000 1 0 1 9 1 0 1 9 0 Logical Basic PCI 10 10 600000 100 108 100 1 1 System Slot PCI 1 pci 10 600000 pci 0 pci 9 0 Board PCI 1 PCIX1 pci 10 600000 pci 0 pci 9 pci 0 pci 1 pci 0 e4 1 PCIR1 PCIX2 pci 10 600000 100 109 100 101 100 1 4 PCI 1 PCI 1 PCIX5 1010 600000 pci 0 pci 9 pci 0 pci 8 pci 0 O4 OBoat X PCIR1 PCIX6 pci 10 600000 pci 0 pci 9 pci 0 pci 8 pci 0 1 4 PCI 1 PCIX3 1010 600000 pci 0 pci 9 pci 0 pci 9 pci 0 O4 PCI 1 PCIX4 pci 10 600000 pci 0 pci 9 pci 0 pci 9 pci 0 1 4 pci 10 600000 pci 0 pci 9 pci 0 pci 1 pci 0 pci 0 0 PCI 1 PCIE2 pci 10 600000 pci 0 pci 9 pci 0 pci l pci 0 pci l 0 PCI 1 PCIE3 1010 600000 1 0 1 9 1 0 1 1 1 0 1 9 0 PCIH1 PCIE4 pci 10 6
8. 0 pciQ90 2000 1 pciQ90 4000 2 PCI 2 pciQ91 2000 1 d PCI 3 pci 91 4000 2 PCI 4 pci 91 4000 3 PCI 5 pci b2 2000 1 6 pci b2 4000 02 PCI 7 pci b2 4000 3 PCI 0 1044 2000 1 PCI 1 1044 4000 2 PCI 2 1044 4000 3 PCI 3 pciQd5 2000 1 PCI 4 5 4000 2 connected to SBH2 PCI 5 pciQd5 4000 3 6 pciQd5 4000 4 PCI 7 pciQf6 2000 1 8 pci f6 4000 02 PCI 9 pciQf6 4000 03 pci 98 2000 01 pci 98 4000 2 PCI 2 pciQ99 2000 1 pciQ99 4000 2 099 4000 03 PCI 5 pci ba 2000 01 PCI 6 pci ba 4000 2 PCI 7 pci ba 4000 3 PCI 0 pciQdc 2000 1 PCI 1 pciQdc 4000 2 PCI 2 pciQdc 4000 3 PCI 3 pciQdd 2000 1 PCI 4 pci dd 4000 2 connected to 5 3 5 pciQdd 4000 3 PCI 6 pciQdd 4000 4 pci fe 2000 1 PCI 8 0 4000 2 PCI 9 0 4000 03 85 Appendix D PCI Slot Number and Device Name 86 PRIMEPOWER 2000 GP7000F Mode12000 Board Number Slot Number Device Name PCIHOA 1080 2000 1 pci 80 4000 2 PCIS1A pciQ81 2000 1 PCISIB 081 4000 2 PCIH3A pc
9. Input distribution input packets distribution in a group 0pkt Output distribution output packets distribution in a group 55 Chapter 4 LinkAggregation Feature 4 3 Notes This section explains notes for using the LinkAggregation function 56 LACP dynamic LinkAggregation function is not supported nly TCP IP connection is supported o not run FJVTS when LinkAggregation is being used e satisfied 0 D If VLAN interface with LinkAggregation function enabled is used the following must b The number of VLAN interfaces the number of physical interfaces in group the number f groups lt 1024 If the above is not satisfied the system may not work correctly due to lack of memory resource Only superuser can execute the fjla command Re The link speed must be the same among the member interfaces in a LinkAggregation group and duplex mode must be set to full It is necessary to inactivate the corresponding LinkAggregation group with the fjla term command before DR Dynamic Reconfiguration or PCI Hot Plug is performed It is necessary to activate corresponding LinkAggregation group with the fjla init command after DR or PCI Hot Plug is completed In a cluster system takeover of LinkAggregation interfaces is not supported The VLAN interface cannot be specified directly It is necessary to use the VLAN interface with LinkAggregation that making the VLAN interface only for the
10. instance 5 is 3 instance 6 is 3 1 The location of the fjgi conf file depends on the model of the host system as described below PRIMEPOWER1 or PRIMEPOWER100 platform sun4u kernel drv f jgi conf PRIMEPOWER other than 1 or GP7000 family platform sundus kernel drv f jgi conf SPARC Enterprise T1000 or T2000 platform sun4v kernel drv f jgi conf 4 SPARC Enterprise M4000 M5000 M8000 or M9000 platform SUNW SPARC Enterpr i se kernel drv f jgi conf 28 3 3 Operation Mode Setup The example which sets a parameter to a fjgi conf file is shown example 1 the case where use the card of PWOO8GE5 10 100 1000BASE T and disable Auto Negotiation and connection speed is made into 100Mbps and Half Duplex name f jgi parent pci 15 2000 unit address 1 AutoNegotiation A Off LinkSpeed 100 DuplexCapabilities A Half example 2 the case where use the card of PWOO8GE4 1000BASE SX and Auto Negotiation is disabled name f jgi parent pciQ17 2000 unit address 1 AutoNegotiation A Off example 3 the case where use the port of the instance number 4 of PWOO8QG1 10 100 1000BASE T and enable Auto Negotiation and connection speed is made into 100Mbps and a Full Duplex name f jgi parent pci 83 4000 pci 3 unit address 1 1 Caution About AutoNegotiation A On LinkSpeed A 100 DuplexCapabilities A Full After m
11. 0 pci 13 700000 pci 0 pci 9 pci 0 pci 9 0 8000 9000 Board Number Slot Number Device Name Logical Basic PCI 100 600000 0 System Slot Board Basic PCI 4 pci 1 700000 0 0 Slot PCI 1 PCIX1 pciQ1 700000 1 0 1 1 1 0 4 PCI 1 PCIX2 pciQ1 700000 pci 0 pci l pci 0 1 4 PCI 1 PCI 1 PCIX5 pciQ1 700000 pci 0 pci 8 pci 0 4 IOBoat X PCI 1 PCIX6 pciQ1 700000 pci00 pciQ8 pci Q0 1 4 PCI 1 PCIX3 pciQ1 700000 1 0 1 9 1 0 4 PCI 1 PCIX4 pciQ1 700000 pci00 pciQ9 pci Q0 1 4 PCI 1 PCIE1 pciQ1 700000 pci 0 pci 1 pci 0 pci 0 e0 PCIS1 PCIE2 01 700000 pci00 pciQ1 pciQ0 pc i1 0 pciQ1 700000 100 101 100 109 00 TOBoat Ex 101 700000 100 109 100 100 00 5 pciQ1 700000 pci 0 pci 9 pci 0 pci l 0 01 700000 pci 0 pci 9 pci 0 pci 9 0 Basic PCI PCI 2 pci 2 600000 0 Slot Basic PCI PCI 3 pci 3 700000 0 Slot PCI 3 PCIX1 pci 3 700000 1 0 1 1 1 0 4 2 pci 3 700000 pci00 pciQ1 pciQ0 1 4 PCI 3 PCIX5 pci 3 700000 1 0 1 8 1 0 4 X PCI 3 PCIX6 pci 3 700000 pci 0
12. bind handle i DMA resources this error to your service provide Re activate the interface If this A error was found in message 7 fail to FragCount message is still fragmentation displayed report to your service provider Installed physical The driver could not allocate p 8 Could not allocate DMA handle memory may be DMA resources insufficient If this is not the cause report The driver could not allocate 9 Could not bind descriptor memory his error to your DMA resources service provide Re activate the interface If this A error was found in message 10 Multiple fragments in descriptor area message is still fragmentation displayed report to your service provider Installed physical memory may be A The driver could not allocate insufficient If this is 11 fjgiallocthings failed DMA resources not the cause report this error to your service provider Installed physical memory may be The driver could not allocate un no insufficient or hardware 12 pci config setup failed sufficient PCI configuration has failed Report this space error to your service provider 60 No Message Cause A 1 Console Messages Workaround apping of the adapter 3 Unable to map adapter registe
13. Requirements Table 4 1 1 shows requirements for the LinkAggregation feature PON a Three different NICs _ be made group by FUJITSU PCI GigabitEthernet is only a fjgi LinkAgeregation feature FRIMEPOWER caia i ri aru single virtual NIC MIC NI CZ Table 4 1 1 Requirements OS Solaris 8 OS or la With TCP IP connection LAN switch that suppor Solaris 9 05 120462 0 ter 64bit environment FJSVla package included in PRIMECLUSTER GLS 4 1 A30 or later Full duplex communicati on ts the LinkAggregation or equivalent feature For PRIMEPOWER patch 114536 07 or later for Solaris 8 05 114994 07 or later for 1 or later for Solaris 10 OS is required Note PRIMEPOWER250 450 secondary LAN port can also be used PRIMEPOWERIOO is not supported Data Distribution Mode Table 4 1 2 explains data distribution 4 1 About LinkAggregation Feature odes that FUJITSU PCI GigabitEthernet 3 0 supports Table 4 1 2 Data Distribution Mode Destination MAC address distribution The LinkAggregation function determines the transmission path to be used from the destination MAC address in the outgoing packet This reduces the likelihood of only specific transmission paths being used if the system mainly communicates with remote systems on the same network and improves transfer efficiency Destination IP address distribution The LinkAggregation
14. 1 pci 15 2000 1 00 2 017 2000 01 00 pci 15 4000 02 00 015 4000 4 00 5 015 4000 05 00 6 017 4000 02 01 2 pci 13 2000 1 01 PCI 3 011 4000 02 01 011 4000 4 Appendix D PCI Slot Number and Device Name Slot Number Device Name 01 5 pciQ11 4000 5 PRIMEPOWER 450 pedestal 7U rack mount Slot Number Device Name 1080 2000 PCI 1 pci 80 4000 3 PCI 2 pci 80 4000 4 PCI 3 pci 80 4000 5 PCI 4 pci 82 2000 PCI 5 pci 82 4000 3 PCI 6 pci 82 4000 4 PCI 7 pci 82 4000 5 8 1083 4000 3 PRIMEPOWER 450 4U rack mount Slot Number Device Name 0 pci 80 2000 1 PCI 1 pci 80 2000 2 2 1080 4000 3 PCI 3 pci 80 4000 4 pci 80 4000 5 PCI 5 pci 83 4000 3 PRIMEPOWER 600 pedestal rackmount Slot Number Device Name 00 1 pci 15 2000 1 00 2 pciQ17 2000 01 00 1015 4000 2 00 1015 4000 4 00 5 pci 15 4000 5 00 6 1017 4000 2 01 011 2000 01 01 2 pci 13 2000 01 01 pciQ11 4000 2 01 pciQ11 4000
15. Ubi ee ec eer a esee bite ta 48 4 2 Configuration of the LinkAggregation 50 4 2 1 Setting Up the etc opt FJSVla config 1 50 4 2 2 Using the etc opt FJSVla bin fjla 52 4 2 2 1 Activate a LinkAggregation Group fjla 1 11 52 4 2 2 2 Inactivate LinkAggregation Group fjla 53 4 2 2 3 Display Status and Statistics fjla 54 A SNOT OS re EE asa enr Mp RR 56 Chapter 5 Troubleshooting Dieu We ee ban ea ree tb ed Dee Beg ae es 57 Appendix A bila aces cus re ei ect e eie TOi add S Ue ala 59 A d5Gonsole Messages iio crates Seated cpu wae dew shine GE 59 Command Messages cases te SNR ed Sate tool ad Reus 63 Appendix B On Board DiagnOstics ond clue Re eee wena Gah Cd e e d bes hee e n 65 Contents Appendix C C 1 Cluster Enviro C 2 Cluster Enviro C 3 Notes Appendix D Appendix E vi Using GigabitEthernet in a Cluster 1 71 nent SUpport ose Decem aee a Tha eae ee RE Sank
16. hehe at eee 71 ment Setup Procedure cca dint ee ee VER Oni Rn pede a ee 71 M RE e eerte eius qe Sts bh saree une RS quo iei Ree RI 72 PCI Slot Number and Device 73 Available ae eee due EO TR WC Be 107 Chapter 1 Product Outline The following topics are described in this chapter Key Features GigabitEthernet card Specifications Chapter 1 Product Outline 1 1 Key Features The FUJITSU GigabitEthernet card is a adapter designed for Solaris OS servers that are connected to a GigabitEthernet network This card offers the physical services and data ink services defined by 802 3 Table 1 1 GigabitEthernet function Main Function IEEE802 3 compliant 1000Base SX PWOOSGE4 PWOGSGE1 1000Base SX 2ports SEOX7GD2X 10 100 1000Base T PWOO8GE5 PWOGSGE2 PRIMEPOWER250 450 secondary LAN 10 100 1000 Base T 2ports SEOX7GD1X 10 100 1000 Base T 4ports PWOO8QG1 SEOX7GQ1X JumboFrame function ndd 1M command provided by Solaris 05 VLAN IEEE 802 3 TagVLAN LinkAggregation IEEE 802 3 except dynamic LACP protocol IPv4 IPv6 SNA FNA JumboFrame VLAN and LinkAggregation functions are supported after Solaris 8 OS JumboFrame Functional ity Although the maximum frame size MTU of one Ethernet packet is 1514 bytes by using a JumboFrame function it becomes possible to set MTU from 151
17. with the remote device This can only be set when AutoNegotiation A On Master Communication by Master Slave Communication by Slave fjgi mtu 5 1500 to 9000 MTU size is specified When PWOO8GE5 or PWOG8GE2 is used it is possib e to set name FJSV pgtb When PWOO8GE4 or PWOGSGEl is used it is possible to set pgsb It becomes the same meaning as having specified name f jgi in both cases Parameter is supported on 10 100 1000Base T PWOO8GE5 PWOGSGE2 SEOX7GD1X PWOOSQGI SEOX7GQ1X adapters and PRI Parameter is effective only 10 100 1000 Base T it beco FlowControl A Rem EPOWER250 450 secondary LAN port when AutoNegotiation A On When AutoNegotiation A Off with mes FlowControl A None And with 1000 Base SX it becomes Parameter is supported on 10 100 1000Base T PWOO8GE5 PWOGSGE2 SEOX7GD1X PWOOSQGI SEOX7GQ1X adapters and PRI EPOWER250 450 secondary LAN port in 1000Mbps mode only Parameter is supported only in Solaris 9 or later and when the following patch for PRIMEPOWER is applied In the case of Solaris 9 OS In the case of Solaris 10 OS Parameter Setting The following shows how to set the parent and unit address parameter in the f jgi conf file 114994 13 or later 120462 06 or later Q Find the fjgi device tree device node and instance number in the etc path to inst 21 Chapter 3 Setting Config
18. 29 Chapter 3 Setting Configuration Information 3 3 2 JumboFrame Setup By using a JumboFrame the TCP IP MTU size can be expanded from 1500 to 9000 By expanding the single packet transmission size the number of packets processed can be reduced lowering the CPU load There are three kinds of following methods in the setting procedure of JumboFrame Method 1 How to specify by etc system and etc hostname f jgi recommendat ion It recommends setting up JumboFrame by this method This method can be used only in Solaris 9 or later or Solaris 8 patch 109900 01 or later is applied When you use JumboFrame in Solaris 2 6 or 7 please set up by the method 2 1 Add the following line to etc system file set fjgi fjgi_jumbo 1 2 The MTU size of TCP IP is set up by describing MTU size in etc hostname f jgi notes in the form of the following between 1500 and 9000 and rebooting When not specifying an MTU value as this file it is set as a default value except for a 9000Byte MAC header Note expresses an instance number Setting formal hostname mtu MTU size Example of setting when setting size of fjgiO to 8000 cat etc hostname f jgiO myhost mtu 8000 3 Reboot the system Method 2 How to specify by etc system and etc f jmtu fjgi Please use this method when you use JumboFrame in Solaris 2 6 or 7 This method is not supported when main part equipment is SPARC Enterprise Server series
19. 4 PCISI PCIX2 011 700000 100 101 100 1 4 5 pciQ11 700000 100 108 100 04 X PCI 1 PCIX6 pciQ11 700000 100 108 100 1 4 PCI 1 PCIX3 011 700000 pci 0 pci 9 pci 0 O4 011 700000 100 109 100 1 4 PCI 1 PCIE1 pciQ11 700000 pci 0 pci 1 pci 0 pci 0 0 pciQ11 700000 pci 0 pci 1 pci 0 pci 1 0 PCI 1 pciQ11 700000 1 0 1 1 1 0 1 9 0 0 PCIR1 PCIEA pciQ11 700000 pci 0 pci 9 pci 0 pci 0 0 5 pciQ11 700000 pci 0 pci 9 pci 0 pci 1 0 pciQ11 700000 1 0 1 9 1 0 1 9 0 Basic PCI PCI 2 pci 12 600000 0 Slot Basic PCI 1013 700000 0 Slot PCI 3 PCIS3 PCIXI pci 13 700000 pci 0 pci l pci 0 4 0 X PCI 3 PCIX2 pci 13 700000 pciQ0 pciQ1 pciQ0 1 4 PCIH3 PCIXS pci13 700000 100 108 100 04 105 Appendix D PCI Slot Number and Device Name
20. FUJITSU PCI GigabitEthernet 3 0 Update for Solaris Operating System User s Guide FUJITSU For Safe Operation 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 and information available in this manual FUJITSU makes every effort to prevent users and bystanders from being injured or from suffering from 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 isa registered trademark of The Open Group in the United States and other countries Sun Sun Microsystems the Sun Logo Solaris and all Solaris based marks and logos are trademarks or registered trademarks of Sun Microsystems Inc in the U S and other countries and are used under license All other product names mentioned herein are trademarks or registered tra
21. This section provides information about IEEE 802 IQ TagVLAN interfaces This section also provides instructions for setting up VLAN interfaces using the FUJITSU PCI GigabitEthernet interface 3 6 1 IEEE 802 10 TagVLAN Description The IEEE 802 10 TagVLAN function allows the use of two or more different networks with a single physical interface Each VLAN operates as its own separate network with its activity separated from other VLANs To accomplish this a virtual interface is created by assigning a VLAN ID VID to a physical interface Note that communication between different VID interfaces on the same physical interface is not allowed The following example shows a VLAN environment Ho Tag VLAN With PRIMEPOWER PRIMEPOWER 550 figi 551000 8212000 XX21 XX11 XX21 To Network To Network To Network netmask 255 255 255 0 Example 1 VLAN environment 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 The numbers FUJITSU PCI GigabitEthernet 3 0 adapter supports VID 1 4094 are available Max number of VLAN interfaces 1024 can be created 3 6 2 Setting Up the VLAN Interface By setting the VLAN interface number to a value greater than 1000 it is possible t
22. 3 PCI 3 pci bd 2000 1 PCI 4 pci bd 4000 2 connected to 7 PCI 5 pci bd 4000 3 6 pci bd 4000 04 PCI 7 pci be 2000 1 PCI 8 pci be 4000 2 PCI 9 pci be 4000 3 99 Appendix D PCI Slot Number and Device Name 100 Board Number Slot Number Device Name PCI O 1 0 2000 1 PCI 1 pci c0 4000 2 PCI 2 1 0 4000 3 PCI 3 0 1 2000 1 PCI 4 pci cl 4000 02 connected to 5 8 PCI 5 0 1 4000 3 PCI 6 0 1 4000 04 PCI 7 pciQc2 2000 1 PCI 8 pciQc2 4000 2 PCI 9 pci c2 4000 3 PCI O pci c8 2000 1 PCI 1 10 8 4000 2 PCI 2 10 8 4000 3 PCIZ3 pciQc9 2000 1 PCI 4 pci c9 4000 02 connected to 5 9 PCI 5 pciQc9 4000 3 PCIS6 pciQc9 4000 04 PCI 7 pci ca 2000 1 PCI 8 pci ca 4000 2 9 pci ca 4000 3 PCI 0 pciQd0 2000 1 PCI 1 1040 4000 2 PCI 2 pciQd0 4000 3 PCI 3 pci dl 2000 1 PCI 4 041 4000 2 connected to 5 PCI 5 pci dl 4000 3 PCIS6 pciQdl 4000 4 pciQd2 2000 1 8 pciQd2 4000 2 9 1042 4000 3 0 1048 2000 01 PCI 1 1048 4000 2 PCI 2 1048 4000 3 PCI 3 pciQd9 2000
23. PCI 4 1089 4000 02 connected to 5 PCI 5 1089 4000 3 6 1089 4000 04 PCI 7 pci 8a 2000 1 PCI 8 pci 8a 4000 2 PCI 9 pci 8a 4000 3 0 pci 8c 2000 1 108 4000 2 PCI 2 pci 8c 4000 3 PCI 3 pci 8d 2000 1 PCI BOX 1 PCI 4 pci 8d 4000 02 connected to 5 PCI 5 pci 8d 4000 3 PCIH6 084 4000 04 08 2000 01 8 08 4000 2 PCI 9 08 4000 03 90 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name 0 pci 90 2000 1 pciQ90 4000 2 PCIH2 pciQ90 4000 03 PCI 3 pciQ91 2000 1 PCI 4 091 4000 02 connected to 5 2 PCI 5 pci 91 4000 3 PCI 6 pciQ91 4000 4 PCI 7 pciQ92 2000 1 1092 4000 2 PCI 9 092 4000 3 pciQ94 2000 1 1094 4000 2 PCIH2 1094 4000 03 PCI 3 7 1095 2000 1 PCI BOX 1 PCI 4 095 4000 2 connected to 5 2 PCI 5 pciQ95 4000 3 6 pciQ95 4000 04 PCI 7 pciQ96 2000 1 8 1096 4000 2 PCI 9 pci 96 4000 3 PCI 0 pciQ98 2000 1 pciQ98 4000 02 PCIH2 7 098 4000 03 PCI 3 pciQ99 2000 1 PCI 4 0
24. PWOG8GE2 The following figures show the location of the LEDs Figure B 5 10 100 1000Base T PWOG8GE2 Meaning of the LEDs PWOG8GE2 1000M LED indicates the following operation status 1000M LED Description Amber lighting The adapter is connected to a 1000Mbps network and is in the state which can communicate Off The adapter is not connected to a 1000Mbps network 100M LED indicates the following operation status 100M LED Description Green lighting The adapter is connected to a 100Mbps network and is in the state which can communicate Off The adapter is not connected to a 100Mbps network 10M LED indicates the following operation status 10M LED Description Green lighting The adapter is connected to a 10Mbps network and is in the state which can communicate Off The adapter is not connected to a 10Mbps network ACT LED indicates the following operation status ACT LED Description Green lighting The adapter is transmitting or receiving network traffic Off There is no network traffic 67 Appendix B On Board Diagnostics Location of the LEDs SEOX7GD1X The following figures show the location of the LEDs Figure B 6 10 100 1000Base T 2ports SEOX7GD1X Meaning of the LEDs SEOX7GD1X 1000M LED indicates the following operation status 1000M LED Desc
25. aggregator interface by a usual VLAN interface making procedure ifconfig 1M or making etc hostname fjgi file Chapter 5 Troubleshooting The following should be checked first to troubleshoot a problem Is the driver software installed correctly Execute pkginfo 1 FJSVgid and pkginfo 1 FJSVgidx command to check the driver installation status If the driver package is not found or is not installed correctly install the driver packages using the driver CD ROM or downloads from the following URL http www fujitsu com global support comput ing server unix driver Refer to INSTALLATION GUIDE for details Does the system recognize the GigabitEthernet interface properly Execute prtconf grep FJSV command to check whether the system is recognizing the interface properly If FJSV pgsb PWOOSGEA4 PWOGSGE1 FJSV pgtb PWOOSGE5 PWOGSGE2 FJSV p4ta 008061 FJSV pwga PRIMEPOWER250 450 secondary LAN e2sa SEOX7GD2X FJSV e2ta SEOX7GD1X or FJSV e4ta SEOX7GQ1X is not found OBP Open Boot PROM on the system is not recognizing the GigabitEthernet interface properly Check whether the interface is properly installed on the system Are the LEDs on the GigabitEthernet card working properly Check the following items if the LEDs indicate the link status is abnormal See also Appendix B On Board Diagnostics for detailed information C
26. 1 4000 2 PCI 2 4000 3 PCI 3 pciQed 2000 1 PCI BOX 1 PCI 4 pci ed 4000 2 connected to 5 PCI 5 pci ed 4000 3 PCI 6 pci ed 4000 4 PCI 7 pciQee 2000 1 PCI 8 pci ee 4000 2 9 pci ee 4000 3 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name 0 pciQf0 2000 1 PCI 1 pci f0 4000 2 PCI 2 pci f0 4000 3 PCI 3 pciQfl 2000 1 PCI 4 pciQf1 4000 02 connected to 5 PCI 5 pciQfl 4000 3 PCI 6 pciQfl 4000 04 PCI 7 pciQf2 2000 1 PCI 8 pciQf2 4000 2 PCI 9 pciQf2 4000 03 pciQf4 2000 1 PCI 1 pci f4 4000 2 PCI 2 pciQf4 4000 3 PCIZ3 pciQf5 2000 1 PCI BOX 1 PCI 4 pci f5 4000 02 connected to 5 PCI 5 pciQf5 4000 3 PCI 6 pciQf5 4000 04 PCI 7 pciQf6 2000 1 PCI 8 pciQf6 4000 2 PCI 9 pciQf6 4000 3 PCI 0 pciQf8 2000 1 PCI 1 pciQf8 4000 2 PCI 2 pci f8 4000 3 PCI 3 pciQf9 2000 1 PCI 4 pciQf9 4000 02 connected to SBHf PCI 5 pciQf9 4000 3 PCI 6 pciQf9 4000 04 PCI 7 pciQfa 2000 1 8 pciQfa 4000 2 pci fa 1000 03 0 pciQfc 2000 1 PCI 1 pci fc 4000 2 PCI 2 pci fc 4000 3 PCI 3 0 200
27. 1 Add the following line to etc system file set fjgi fjgi_jumbo 1 30 3 3 Operation Mode Setup 2 The size of TCP IP is set up by creating etc fjmtu fjgi notes and describing MTU size in etc fjmtu fjgi in the form of the following between 1500 and 9000 and rebooting When not specifying an MTU value as this file it is set as a default value except for a 9000Byte MAC header Note expresses an instance number An instance number should set up the value the same as that of of etc hostname fjgi which surely corresponds Example of setting when setting size of fjgiO to 8000 cat etc f jmtu f jgiO 8000 3 Reboot the system Method 3 How to specify by conf When you set up MTU size separately by every interface and when application does not refer to etc hostname fjgi example CF of PRIMECLUSTER CIP function please use this method This method can be used only in Solaris 9 or later and when the following patch for PRIMEPOWER is applied In the case of Solaris 9 OS 114994 13 or later In the case of Solaris 10 OS 120462 06 or later 1 Add fjgi mtu parameter to fjgi conf file Specify the value like fjgi mtu 8000 instead of the character string like fjgi mtu 8000 Example of file description when setting MTU size of a specific interface to 8000 name FUSV pgtb parent pci 15 2000 unit address 1 f jgi_mtu 8000 2 Reboot the system C
28. 100 600000 pci 0 pci 9 pci 0 pci l pci 0 pci 1 Q0 PCI 1 PCI 1 PCIE3 pci 0 600000 pci 0 pci 9 pci 0 pci l pci 0 pci 9 0 Ex pci 0 600000 1 0 1 9 1 0 1 9 1 0 1 0 0 PCI 1 PCIE5 100 600000 pci 0 pci 9 pci 0 pci 9 pci 0 pci 1 0 PCI 1 PCIE6 100 600000 pci 0 pci 9 pci 0 pci 9 pci 0 pci 9 0 Baste PCI pot pci l 700000 0 Slot PCIS2 PCIXI pciQ1 700000 pci 0 pci 1 pci 0 e 4 PCIS2 PCIX2 pciQ1 700000 1 0 1 1 1 0 1 4 PCI 2 PCI 2 PCIX5 101 700000 pci 0 pci 8 pci 0 O4 IO0Boat X PCI 2 PCIX6 101 700000 100 108 100 1 4 PCI 2 PCIX3 101 700000 pci 0 pci 9 pci 0 O4 pciQ1 700000 100 109 100 1 4 PCI 2 PCIE1 pciQ1 700000 1 0 1 1 1 0 1 0 0 PCI 2 PCIE2 101 700000 0 10 1 0 1 1 0 PCI 2 PCI 2 PCIE3 101 700000 pci 0 pci l pci 0 pci 9 0 Ex PCI 2 PCIE4 1 1 700000 1 0 1 9 1 0 1 0 0 PCIS2 PCIE5 pciQ1 700000 pci 0 pci 9 pci 0 pci l 0 PCIS2 PCIE6 pciQ1 700000 1 0 1 9 1 0 1 9 0 Basic PCI pci 2 600000 0 Slot PCI 3 PCIX1 pci 2 600000 pci 0 pci l pci 0 O4 PCI 3 PCIX2 pci 2 600000 100 101 100 1 4 PCI 3 PCI 3 PCIX
29. 2 PCI 3A pciQdb 2000 1 PCI 3B 0 4000 2 PCIS0A pciQdc 2000 1 pciQdc 4000 2 688 pciQdd 2000 1 pci dd 4000 02 pciQdf 2000 1 PCI 3B pci df 4000 2 88 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name 1 0 2000 1 1 0 4000 2 SB 24 PCIS1A pciQel 2000 1 PCI 1B pciQel 4000 2 pciQe3 2000 PCI 3B pci e3 4000 2 PCIS0A pciQe4 2000 1 0 4 4000 2 spies PCIS1A 5 2000 1 pci ed 4000 02 pci e7 2000 1 PCI 3B pci e7 4000 2 PCIS0A pciQe8 2000 1 pci e8 4000 02 SB 26 pciQe9 2000 1 1 9 4000 02 pciQeb 2000 1 PCI 3B pciQeb 4000 2 PCIS0A 2000 1 4000 2 7 PCIS1A pciQed 2000 1 PCI 1B pciQed 4000 2 PCI 3A pciQef 2000 1 PCI 3B pciQef 4000 2 PCIS0A pciQf0 2000 1 PCISOB pci f0 4000 02 SBH28 pciQfl 2000 1 PCI IB 4000 02 PCI 3A pcif3 2000 01 PCI 3B pciQf3 4000 2 PCIS0A pciQf4 2000 1 pci f4 4000 02 PCI
30. 2 2 PCI Express GigabitEthernet Card Specification Item Compatibility Host Bus Inte face PCI Express 1 SEOX7GD1X SEOX7GD2X PCI Express 1 1 SEOX7GQIX Network Inter Lace 1000Base SX 2ports SEOX7GD2X 10 100 1000Base T 2ports SEOX7GD1X 10 100 1000Base T 4ports SEOX7GQ1X Host Data Tra nsfer SEOX7GD1X SEOX7GD2X PCI Express 4lane Bus Mastering DMA Transfers 5 0 7601 PCI Express 8lane Bus Mastering DMA Transfers Bus Type One PCI slot per card Power Requirements Maximum 9 1W SEOX7GD1X 9 2W SEOX7GD2X 15 OW SEOX7GQ1X 1000Base SX SEOX7GD2Y Multi mode Fibre LC SC 62 5 125 micron and 50 125 micron A card side is LC It is used when connection place partner Connections equipment is SC LC LC 62 5 125 micron and 50 125 micron 10 100 1000Base T SEOX7GDIX SEOX7GQIX Cat5e Cable Cat5 cable can also be used for 10 100Mbps Caution PWOO8GE4 PWOGSGEl and SEOX7GD2X only supports full duplex connection Half duplex Chapter 1 Product Outline connection is not supported When using 1000Mbps transfer rate with PWOO8GE5 PWOGSGE2 PRIMEPOWER250 450 secondary LAN port SEOX7GD1X PWOO8QG1 and SEOX7GQ1X only Auto Negotiation On can be used 1 2 2 Part Names and Features of Hardware Figure 1 1 to 1 8 shows the appearance of the FUJITSU PCI GigabitEthernet adapters The part names and features are listed as follows Conne
31. 4 01 5 pciQ11 4000 5 01 6 1013 4000 2 11 Appendix D PCI Slot Number and Device Name 78 PRIMEPOWER 650 rackmount Board Number Slot Number Device Name 1084 2000 1 PCI 1 1084 4000 1 PCIH2 1084 4000 2 PCIH3 1084 4000 3 PCI 4 1085 2000 1 PCI 5 1085 4000 1 PCIH6 1085 4000 2 PCI 7 085 4000 3 PCI 0 1080 2000 1 PCI I 7 1080 4000 01 PCI 2 080 4000 2 080 4000 03 PCI 4 pci 81 2000 1 ee 5 pci 81 4000 01 6 1081 4000 2 081 4000 03 8 1082 2000 1 9 1082 4000 1 10 082 4000 02 PCI 11 pci 82 4000 3 PRIMEPOWER 800 pedestal Board Number Slot Number Device Name 080 2000 1 080 4000 02 m PCI IA pci 81 2000 01 PCISIB 081 4000 2 PCIH3A 1083 2000 0 PCI 3B 083 4000 2 PCIHOA 7 1088 2000 1 PCISOB 088 4000 02 ae PCIHIA 1089 2000 0 PCISIB 1089 4000 2 PCIH3A 108 2000 01 PCI 3B pci 8b 4000 2 1 090 2000 1 090 4000 02 SBH PCIS1A pciQ91 2
32. FJSV p4ta 3 1 6 The logical bus address corresponds to a physical PCI slot number based on the Main Unit model number Refer to the Appendix D PCI slot number and device name to determine the slot number from the logical bus address 3 4 2 Discernment Of the GigabitEthernet Interface on SPARC 40 Enterprise This section explains how to distinguish the FUJITSU PCI GigabitEthernet interface instance number 1 fo interface type and which slot the card is installed in on SPARC Enterprise To determine the instance number execute the following command prtconf D grep example prtconf D grep FJSV e4ta instance 0 driver FJSV e4ta instance 1 driver FJSV e4ta instance 2 driver FJSV e4ta instance 3 driver FJSV e2sa instance 4 driver FJSV e2sa instance 5 driver FJSV e2ta instance 6 driver FJSV e2ta instance 7 driver The instance number is the number displayed in bold above The adapter type can also be determined from the prtconf command output FJSV e4ta SEOX7GQ1X 10 100 1000BASE T 4ports card FJSV e2sa SEOX7GD2X 1000BASE SX 2ports card FJSV e2ta SEOX7GD1X 10 100 1000BASE T 2ports card To determine the slot the GigabitEthernet PCI card is mounted in execute the lowing command 3 4 Discernment Of the GigabitEthernet Interface more etc path to inst grep example more
33. Hostname file Hostname Definition Netmask Value Definition 3 2 1 Configuring the Hostname File 1 use the GigabitEthernet interface as an IPv4 interface Allocate an IP address or hostname for the fjgi driver by editing the etc hostname fjgi file where is a numerical value About netmask value please see 3 2 3 Netmask Value Definition Example etc hostname fjgi file Define a unique hostname giga v4 Or define the IP address 192 168 150 1 Note 1 Please put a decimal number instance number into See section 3 4 Discernment Of the GigabitEthernet Interface for detailed information about instance number Note 2 See section 3 2 2 Hostname Definition for detailed information about defining the hostname Note 3 Please put in neither a blank nor a empty line behind an IP address If a blank or a empty line enter it will not be activated at the time of main part equipment starting To use the GigabitEthernet interface as an IPv6 interface Allocate an IP address and prefix for the fjgi driver by editing the etc hostname6 fjgi file where is a numerical value Example etc hostname6 fjgi file Define a unique hostname addif giga v6 120 up Note See section 3 2 2 Hostname Definition for detailed information about defining the hostname To use the GigabitEthernet interface as a VLAN interface See section 3 6 2 How to create the VLAN interface and
34. Name pciQ1f 2000 1 PCI 2 014 2000 1 pciQ1f 4000 02 4 pciQ1d 4000 2 PCI 5 pciQ1d 4000 4 PCI 6 pciQ1d 4000 5 73 Appendix D PCI Slot Number and Device Name GP7000F Model200R Slot Number Device Name 017 2000 01 PCI 2 pci 16 2000 1 PCI 3 017 4000 2 PCI 4 016 4000 2 PCI 5 016 4000 4 6 016 4000 5 GP7000F Model400A 400R Slot Number Device Name 00 PCI 1 017 2000 1 00 PCIZ2 pci 16 2000 1 00 PCIZ3 017 4000 2 00 PCI 4 pci 16 4000 2 00 PCI 5 016 4000 04 00 6 016 4000 5 01 015 2000 01 01 PCIZ2 pci 14 2000 01 01 PCIZ3 015 4000 2 01 PCI 4 014 4000 2 01 5 1 14 4000 04 01 6 014 4000 5 GP7000F Model400 Slot Number Device Name PCI 1 pciQ1f 2000 1 PCI 2 pciQ1e 4000 2 PCI 3 01 4000 3 PCI 4 pci le 4000 4 PCI 5 pci le 2000 1 6 pciQ1d 4000 2 PCI 7 pciQ1d 4000 3 PCI 8 pciQ1d 4000 4 PCI 9 1 14 2000 1 GP7000F Model600 Slot Number Device Name pciQ1f 2000 1 PCI 2 pci le 4000 2 P
35. PCI 3 pci 8d 2000 1 PCI 4 pci 8d 4000 2 connected to 5 PCI 5 pci 8d 4000 3 6 7 084 4000 04 PCI 7 08 2000 1 PCI 8 08 4000 2 PCI 9 08 4000 03 pci 90 2000 01 pciQ90 4000 02 PCI 2 pciQ91 2000 1 SBH PCI 3 pci 91 4000 2 PCI 4 091 4000 3 PCI 5 pciQ92 2000 1 PCIH6 1092 4000 02 PCI 7 092 4000 3 PCI 0 pciQ94 2000 1 1094 4000 02 PCIH2 1094 4000 PCI 3 pciQ95 2000 1 PCI 4 095 4000 02 connected to SB 2 5 pciQ95 4000 3 PCIH6 pci 95 4000 04 pci 96 2000 01 8 1096 4000 02 PCI 9 pci 96 4000 03 83 Appendix D PCI Slot Number and Device Name 84 Board Number Slot Number Device Name 7 1098 2000 1 PCI I 7 1098 4000 2 PCI 2 pciQ99 2000 1 PCIH3 1099 4000 2 PCIHA 7 1099 4000 03 PCI 5 pciQ9a 2000 1 PCI 6 pciQ9a 4000 2 PCI 7 pci 9a 4000 3 pciQ9c 2000 1 PCI 1 pci 9c 4000 2 PCI 2 pciQ9c 4000 3 pciQ9d 2000 1 PCI 4 pci 9d 4000 2 connected to 5 3 PCI 5 pci 9d 4000 3 6 pci 9d 4000 04 PCIZ7 pciQ9e 2000 1 8 pciQ9e 4000 2 PCI 9 pci 9e 4000 3 PRIMEPOWER 1500
36. PCI slot number and device name matrix for the following PRIMEPOWER GP7000F PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR SPA P7000 P7000 P7000 P7000 P7000 P7000 29 tutu SPA RC T 200 200R od 1j od od 1j 400 600 600R od ode T ode POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER POWER 900 POWER 900 POWER 1000 G POWER 1500 POWER 1500 POWER 2000 G POWER 2500 H 100 200 250 250 250 400 400 450 450 600 650 800 850 POWER 2500 400 PP04 AU ped ped models 400A 400R 1 0 rackmount pedestal pedestal rackmount pedestal 2U rack mount 4U rack mount 4 rackmount estal 10U rackmount OBRIU pedestal 100 rackmount estal 7U rack mount rack mount estal rackmount rackmount esta rackmount ysical Partitioning Extended Partitioning P7000F 11000 Physical Partitioning Extended Partitioning P7000F 12000 PC2500 Physical Partitioning Extended Partitioning 4000 M5000 8000 M9000 Table D 1 Slot Number and Device Name Matrix GP7000F Model200 Slot Number Device
37. ROM drive 6 Shutdown the OS on the client system and confirm that the OpenBoot ok prompt is displayed i shutdown 10 0 y example shutdown 0 g0 y 7 Search the device path for the FUJITSU PCI GigabitEthernet device with the show nets command from the ok prompt on the client system ok show nets example ok show nets a pciQ1f 4000 FJSV pgtbQ5 b pciQ1f 4000 FUSV pgsb 4 q NO SELECTION Enter Selection q to quit 8 From ok prompt boot the client system using the FUJITSU PCI GigabitEthernet device 43 Chapter 3 Setting Configuration Information ok boot pci 1f 4000 FJSV pgtb 5 9 Install the Solaris OS 10 After Solaris OS installation check whether the FUJITSU PCI GigabitEthernet software has already been installed using the following command pkginfo grep FJSVgid example pkginfo grep FJSVgid system FJSVgid Fujitsu Gigabit Interface Adapter system FJSVgidx Fujitsu Gigabit Interface Adapter 64 bit If the software has not been installed install the FUJITSU PCI GigabitEthernet software from the CD ROM that came with the adapter Refer to the nstallation Guide FUJITSU PCI GigabitEthernet 3 0 Updatel for more information about installation Caution When you install Solaris 2 6 OS via a network please be sure to set the value of the local mac address parameter of a client system as false 44 3 6 VLAN Interface Setup 3 6 VLAN Interface Setup
38. Twisted Pair Cat5E Cable Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2 3 5 SEOX7GD2X with Optical Fiber Cable 2 3 Cable Connection Figure 2 3 6 SEOX7GD1X with Twisted Pair Cat5E Cable Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2 3 7 PWOO8QG1 with Twisted Pair CatbE Cable 2 3 Cable Connection Figure 2 3 8 SEOX7GQ1X with Twisted Pair Cat5E Cable Chapter 3 Setting Configuration Information This chapter describes how to set configuration information after installing the FUJITSU PCI GigabitEthernet interface The following topics are covered in this chapter Driver Sof Environmen tware Installation t Setting Operation Mode Setup Discernment of the GigabitEthernet interface Network Installation VLAN Inter face Setup Chapter 3 Setting Configuration Information 3 1Driver Software Installation make use of the FUJITSU PCI GigabitEthernet interface Solaris 05 version specific driver packages must be installed from the attached CD ROM See the document Installation Guide FUJITSU PCI GigabitEthernet 3 0 Updatel for the installation procedure 22 3 2 Environment Setting 3 2 Environment Setting This section explains how to edit the necessary file to configure the operating environment of the FUJITSU PCI GigabitEthernet interface In TCP IP IPv4 or IPv6 protocol edit the following information must be setup Configuring the
39. after defining the VLAN name follow steps 1 or 2 above 3 2 2 Hostname Definition Define an IP address with a unique hostname 1 use the GigabitEthernet interface as IPv4 interface Add the IPv4 address and hostname to the etc hosts file Chapter 3 Setting Configuration Information Example etc hosts file IP Address Hostname 190 168 150 1 giga v4 24 3 2 Environment Setting 2 To use the GigabitEthernet interface as an IPv6 interface Add the IPv6 address and hostname to the etc inet ipnodes file Example etc inet ipnodes file IP Address Hostname fe80 2e0 ff fea6 2222 giga v6 3 2 3 Netmask Value Definition To use the GigabitEthernet interface as an IPv4 interface add the netmask value and IP address to the etc netmasks file Example etc netmasks file IP Address netmask 192 168 150 0 255 255 255 0 Chapter 3 Setting Configuration Information 3 3 Operation Mode Setup This section explains how to edit the fjgi conf configuration file or issue a command to change the operation mode of the FUJITSU PCI GigabitEthernet interface The operation mode can be changed with the following The fjgi conf file JumboFrame Setup The ndd Utility FCode Settings 3 3 1 The fjgi conf File About speed duplex flowcontrol it recommends carrying out default operation automatic setup by Auto Negotiation Usually a setup of a fjgi conf file is unnecessary It is a case a
40. ca 4000 2 9 pci ca 4000 3 0 pciQcc 2000 01 PCI 1 pciQcc 4000 2 PCI 2 pci cc 4000 3 PCI 3 pciQcd 2000 1 PCI BOX 1 PCI 4 pci cd 4000 2 connected to 9 PCI 5 pciQcd 4000 3 PCI 6 pciQcd 4000 04 PCI 7 pci ce 2000 1 PCI 8 pci ce 4000 2 9 pci ce 4000 3 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name 0 pciQd0 2000 1 pciQd0 4000 2 PCI 2 1040 4000 3 PCI 3 pci dl 2000 1 PCI 4 041 4000 2 connected to 5 PCI 5 pci dl 4000 3 PCI 6 pciQdl 4000 4 PCI 7 pciQd2 2000 1 PCI 8 pciQd2 4000 2 PCI 9 042 4000 3 1044 2000 1 PCI 1 1044 4000 2 PCI 2 1044 4000 3 PCIZ3 pciQd5 2000 1 PCI BOX 1 PCI 4 5 4000 2 connected to 5 PCI 5 pciQd5 4000 3 PCI 6 pciQd5 4000 4 PCI 7 pciQd6 2000 1 PCI 8 pciQd6 4000 2 PCI 9 046 4000 3 PCI 0 1048 2000 1 PCI 1 1048 4000 2 PCI 2 1048 4000 3 PCI 3 pciQd9 2000 1 PCI 4 049 4000 02 connected to 5 PCI 5 pciQd9 4000 3 PCI 6 pciQd9 4000 4 PCI 7 pciQda 2000 1 8 pciQda 4000 2 9 pci da 4000 3 0 pciQd
41. 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 a VLAN interface A VLAN interface uses approximately 700Kb of memory at MTU1514 or 900Kb of memory at MTU9014 in an idle state Therefore when using two or more VLAN interfaces a system slowdown may occur due to a shortage of resources depending on system configuration 46 Chapter 4 LinkAggregation Feature This chapter outlines the LinkAggregation feature and explains the settings required to use this feature About the LinkAggregation feature Configuration of the LinkAggregation feature Notes Chapter 4 LinkAggregation Feature 4 1 About LinkAggregation Feature This section explains the LinkAggregation feature 48 LinkAggregation feature The communication bandwidth and network reliability can be improved by bundling two or more network interfaces as one logical interface up to 8 physical interfaces can be bundled It is effective when handling a lot of data or when offering large scale customer service With this version only static aggregation is supported Dynamic Link Aggregation Control Protocol LACP specified by IEEE802 is not supported 1 As long as there is at least one transmission path available communication can be continued 2 The interface which ca interface Conventional method
42. from the logical bus address 41 Chapter 3 Setting Configuration Information 3 5 Network Installation This section explains how to perform a Solaris OS network installation using the FUJITSU PCI GigabitEthernet interface 1 Please refer to the Advanced Installation Guide for information on the setup of the server and clients for Solaris Jumpstart 2 On the installation server execute the following command and check the mini root directory for the client system The mini root directory for each client system is described in the etc bootparams file on the installation server grep CL ENT_NAME etc bootparams example grep CL ENT_NAME etc bootparams GL IENT root SERVER_NAME netinstall Solaris 8 Tools Boot instal In the above example the mini root directory is netinstall Solaris 8 Tools Boot on the installation server CLIENT NAME is the name of the client system SERVER NAME is the name of the installation server Information If the mini root directory name is not described in the etc bootparams file please refer to the Advanced Installation Guide 3 Insert the FUJITSU PCI GigabitEthernet 3 0 Updatel CD ROM into the CD ROM drive of the installation server 4 Install the FUJITSU PCI GigabitEthernet 3 0 Updatel software to the mini root directory as shown in the examples below 1 For PRIMEPOWER1 or PRIMEPOWER100 client systems cd cdrom cdrom0 FUSVgid_3 0 PRIMEPOWER
43. function determines the transmission path to be used from the destination IP address in the outgoing packet This reduces the likelihood of only specific transmission paths being used if the system mainly communicates with remote systems on different networks via a router and improves transfer efficiency Source Destination IP address distribution The LinkAggregation function determines source and d likelihood of o paths being used if communicates w different networks improves transfer e is more suitab the transmission path to be used from the the outgoing packet ith works as a rou estination IP address in nly specific transmission This reduces the the system mainly emote systems on via a router and e when the local system Ler fficiency Also this 49 Chapter 4 LinkAggregation Feature 4 2 Configuration of the LinkAggregation Feature The LinkAggregation feature can be configured with one of the following methods Setting Up the etc opt FJSVla config File Using the etc opt FJSVla bin fjla Command Caution PRIMECLUSTER GLS 4 1 A30 or later is required to use the LinkAggregation feature The FJSVla package contains the fjla command and a sample configuration file 4 2 1 Setting Up the etc opt FJSVla config File This section explains how to create and modify the etc opt FJSVla config file to use the LinkAggregation feature All Li
44. parameter values are valid ly when link_status 1 If link_status 0 these va ues are invalid The of 1 10 1000fdx 1000hdx cap parameter values valid only when Auto Negotiation communication is successfully lp lOhdx cap lp 100fdx cap lp pauseTX and 100 cap lp autoneg cap values lp pauseRX established The parameter values are invalid when Auto Negotiation is disabled or en Auto Negotiation communication fails e parameter values set by the ndd command become invalid after reboot e gt ndd command made to a physical interface that is related to IPv4 IPv6 interface d SNA FNA interface will apply to both the physical interface and the VLAN terface e 3 3 4 Settings By modifying FCode settings the adapter communication mode can be changed Changing the FCode settings is possible on PWOO8GE4 PWOG8GE1 SEOX7GD2X PWOO8GE5 PWOG8GE2 SEOX7GD1X PWOO8QG1 SEOX7GQ1X and the secondary LAN port of the PRIMEPOWER250 450 odifying FCode settings may be needed when Auto Negotiation is not used for speed duplex setting and flow control or when the link partner does not support Auto Negotiation FCode changes do not take effect after the OBP reset and netboot is completed FCode Setting Example The following example describes how to disable Auto Negotiation and set the communication speed of an fjgi interface by modifyi
45. pciQa9 4000 3 PCI 6 pciQa9 4000 4 PCI 7 pci aa 2000 1 8 pciQaa 4000 2 9 pci aa 4000 3 PCI 0 pciQac 2000 1 PCI 1 pciQac 4000 2 PCI 2 pciQac 4000 3 PCI 3 pci ad 2000 1 PCI BOX 1 PCI 4 pci ad 4000 2 connected to 5 5 PCI 5 pci ad 4000 3 PCI 6 pci ad 4000 4 PCI 7 pciQae 2000 1 PCI 8 pciQae 4000 2 9 pci ae 4000 3 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name 0 pci b0 2000 1 pci b0 4000 02 PCIH2 pci b0 4000 03 PCI 3 0 1 2000 1 PCI 4 0 1 4000 2 connected to 5 6 PCI 5 pci bl 4000 3 PCI 6 0 1 4000 4 PCI 7 2 2000 1 pci b2 4000 02 PCI 9 pci b2 4000 3 10 4 2000 1 pci b4 4000 02 PCIH2 pci b4 4000 03 PCI 3 pci b5 2000 01 PCI BOX 1 PCI 4 pci b5 4000 2 connected to SBH6 PCI 5 pciQb5 4000 3 6 7 5 4000 04 PCI 7 pciQb6 2000 1 8 pci b6 4000 02 PCI 9 pci b6 4000 3 PCI 0 pciQb8 2000 1 pci b8 4000 02 PCIH2 pci b8 4000 03 PCI 3 pciQb9 2000 1 PCI 4 pci b9 4000 02 connected to 7 PCI 5 10 9 4000 3 PCIH6 pci b9 4000 04 PC
46. support FJ LinkAggregation LinkAggregation feature the driver By setting up the physical interface to use fjla init vlan VLAN interface can 2 LinkAggregation the VLAN 4 interface cannot define FJ not be used for the terfaces associated with LinkAggregation LinkAggregation feature the physical interface lso use LinkAggregation The interface specified as Unplumb all member fjla init A member interface 5 LinkAggregation group interfaces except the has already been plumbed member is already plumbed aggregator interface interface specified The interface specified as 6 fjla init is not plumbed as aggregator interface interface aggregator interface is must be activated not activated viewable by ifconfig a The instance number is Do not specify the same are duplicated in the instance number in the fjla init Input member is HS 7 specified member list LinkAggregation member duplicated including list including aggregator interface aggregator interface 63 Appendix A Messages 64 interface name invalid No Message Cause Workaround 8 fjla init does not The interface does Specify interfaces that exist not exist exist on the system Specif
47. 0 1 PCI BOX 1 PCI 4 pci fd 4000 2 connected to SBHf PCI 5 pciQfd 4000 3 PCI 6 0 4000 04 PCI 7 pci fe 2000 1 PCI 8 0 4000 2 0 4000 03 97 Appendix D PCI Slot Number and Device Name 98 PRIMEPOWER 2500 Extended Parti tioning Board Number Slot Number Device Name 1084 2000 1 1084 4000 02 PCIH2 1084 4000 03 PCI 3 1085 2000 1 PCI 4 pci 85 4000 02 connected to SBHO PCI 5 1085 4000 3 PCIH6 1085 4000 04 PCI 7 pci 86 2000 1 PCI 8 1086 4000 02 PCI 9 pci 86 4000 3 0 108 2000 01 pci 8c 4000 2 PCI 2 108 4000 3 pci 8d 2000 01 PCI 4 pci 8d 4000 2 connected to 5 PCI 5 pci 8d 4000 3 6 7 084 4000 04 PCI 7 08 2000 1 PCI 8 08 4000 2 PCI 9 08 4000 03 0 1094 2000 01 1094 4000 02 PCIH2 1094 4000 03 PCI 3 pciQ95 2000 1 PCI 4 pci 95 4000 2 connected to 2 PCI 5 pciQ95 4000 3 PCIH6 pci 95 4000 04 PCI T pci 96 2000 01 PCI 8 096 4000 2 PCI 9 pci 96 4000 3 PCI O pci 9c 2000 1
48. 000 1 091 4000 02 PCIH3A pciQ93 2000 1 PCI 3B 093 4000 2 PCIHOA 7 1098 2000 1 PCISOB pci 98 4000 02 PCIHIA 7 1099 2000 01 PCISIB 099 4000 02 PCIH3A pci 9b 2000 01 PCI 3B pci 9b 4000 2 PRIMEPOWER 850 rackmount Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name PCI 0 1084 2000 1 PCI 1 pci 84 4000 1 PCIH2 1084 4000 2 PCIH3 1084 4000 03 PCI 4 1085 2000 1 PCI 5 pci 85 4000 1 PCIH6 1085 4000 2 PCI 7 085 4000 3 pci 80 2000 1 PCI I 1080 4000 01 PCIH2 1080 4000 2 080 4000 03 PCI 4 pci 81 2000 1 PCI BOX O PCI 5 pci 81 4000 1 PCI 6 pci 81 4000 2 PCI 7 pci 81 4000 3 PCI 8 1082 2000 1 9 1082 4000 01 PCI 10 082 4000 02 PCI 11 082 4000 3 PCI 0 pci 8c 2000 1 PCI 1 108 4000 1 PCI 2 108 4000 2 Sii PCI 3 108 4000 3 PCI 4 pci 8d 2000 1 PCIHS 1084 4000 1 6 pci 8d 4000 02 PCI 7 pci 8d 4000 3 PCI 0 pci 88 2000 1 PCI 1 1088 4000 1 PCIH2 7 1088 4000 2 PCIH3 7 1088 4000 3 PCI 4 1089 2000 1 POICH PCI 5 1089 4000 1
49. 00000 pciQ0 pci9 pciQ0 pciQ9 pci00 pc i0 eeekQ0 PCI 1 PCIE5 pci 10 600000 pci 0 pci 9 pci 0 pci 9 pci 0 pci l 0 PCI 1 PCIE6 pci 10 600000 pci 0 pci 9 pci 0 pci 9 pci 0 pci 9 0 Basic PCT 011 700000 setsieQ0 Slot PCI 2 PCIX1 1011 700000 pci 0 pci 1 pci 0 4 PCI 2 PCIX2 1011 700000 100 101 100 1 4 PCI 2 PCI 2 PCIX5 1011 700000 pci 0 pci 8 pci 0 4 OBoat X PCI 2 PCIX6 pci 11 700000 pci 0 pci 8 pci 0 1 xx 4 PCI 2 PCIX3 1011 700000 pci 0 pci 9 pci 0 O 4 2 1011 700000 100 109 100 1 4 PCI 2 PCIE1 1011 700000 pci 0 pci l pci 0 pci 0 0 PCI 2 PCIE2 pci 11 700000 pci 0 pci l pci 0 pci l 0 2 PCI 2 PCIE3 1011 700000 pci 0 pci l pci 0 pci 9 Q0 IOBoat PCI 2 PCIE4 1011 700000 100 109 100 100 00 2 5 1011 700000 pci 0 pci 9 pci 0 pci l 0 PCI 2 PCIE6 1011 700000 pci 0 pci 9 pci 0 pci 9 0 Basic PCI pora 012 600000 00 Slot PCI 3 PCIX1 pci 12 600000 pci 0 pci 1 pci 0 4 PCI 3 PCIX2 1012 600000 100 101 100 1 4 PCI 3 PCIX5 pci 12 600000 pci 0 pci 8 pci 0 4 TOBoat X PCI 3 PCIX6 1012 600000 100 108 100 1 O4 PCI 3 PCIX3 pci 12 600000 pci 0 pci 9 pci 0 O4 PCI 3 PCIX4 pci 12 600000 pci00 pci
50. 01 PCI 3B pci bf 4000 2 87 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name 1 0 2000 1 0 0 4000 2 PCIS1A 0 1 2000 1 PCI 1B 0 1 4000 2 pciQc3 2000 PCI 3B pci c3 4000 2 PCIS0A pciQc4 2000 1 pciQc4 4000 2 PCIS1A pciQc5 2000 1 pci c5 4000 02 pci c7 2000 1 PCI 3B pci c7 4000 2 PCIS0A 10 8 2000 1 pci c8 4000 02 apie pciQc9 2000 1 pci c9 4000 02 pciQcb 2000 1 PCI 3B pci cb 4000 2 PCIS0A pciQcc 2000 1 pciQcc 4000 2 PCIS1A pciQcd 2000 1 PCI 1B pciQcd 4000 2 PCI 3A pci cf 2000 1 PCI 3B pci cf 4000 2 PCIS0A pciQd0 2000 1 pciQd0 4000 2 SB 20 pci dl 2000 1 pci dl 4000 2 pciQd3 2000 1 PCI 3B pci d3 4000 2 PCIS0A pciQd4 2000 1 pci d4 4000 02 SB 21 pciQd5 2000 1 PCI 1B pciQd5 4000 2 0 7 2000 PCI 3B pci d7 4000 2 PCIS0A 1048 2000 1 1048 4000 2 PCIS1A pciQd9 2000 PCI 1B pciQd9 4000
51. 09 pci0 1 4 PCI 3 PCIE1 pci 12 600000 pci 0 pci l pci 0 pci 0 0 PCI 3 PCIE2 pci 12 600000 pci 0 pci l pci 0 pci 1 0 PCI 3 pci 12 600000 pci 0 pci l pci 0 pci 9 Q0 10Boat pci 12 600000 pci 0 pci 9 pci 0 pci 0 e0 5 pci 12 600000 pci 0 pci 9 pci 0 pci 1 0 PCI 3 PCIE6 pci 12 600000 pci 0 pci 9 pci 0 pci 9 Q0 Basic 013 700000 0 Slot PCI 4 PCIX1 pci 13 700000 pci 0 pci 1 pci 0 4 TOBoat X PCIS4 PCIX2 1013 700000 100 101 100 1 4 PCI 4 PCIX5 pci 13 700000 pci 0 pci 8 pci 0 4 PCI 4 PCIX6 1013 700000 100 108 100 1 4 103 Appendix D PCI Slot Number and Device Name 104 Board Number Slot Number Device Name PCIS4 PCIX3 pci 13 700000 1 0 1 9 1 0 4 pci 13 700000 100 109 100 1 e4 PCI 4 PCIE1 pci 13 700000 pci 0 pci l pci 0 pci 0 0 PCIS4 PCIE2 pci 13 700000 0 1 0 1 1 0 PCI 4 pci 13 700000 pci 0 pci l1 pci 0 pci 9 0 pci 13 700000 pci 0 pci 9 pci 0 pci 0 0 PCI 4 PCIE5 pci 13 700000 1 0 1 9 1 0 1 1
52. 1 PCI 4 049 4000 02 connected to 5 PCI 5 pciQd9 4000 3 PCI 6 pciQd9 4000 4 PCI 7 pciQda 2000 1 PCI 8 pciQda 4000 2 9 pci da 4000 3 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name 0 1 0 2000 1 1 0 4000 2 PCI 2 1 0 4000 3 PCI 3 pciQel 2000 1 PCI 4 pci el 4000 2 connected to 5 PCI 5 pciQel 4000 3 PCI 6 0 1 4000 4 PCI 7 pciQe2 2000 1 PCI 8 0 2 4000 2 PCI 9 pci e2 4000 3 pciQe8 2000 1 PCI 1 pci e8 4000 2 PCI 2 pci e8 4000 3 PCIZ3 pciQe9 2000 1 PCI 4 9 4000 2 connected to 5 PCI 5 pciQe9 4000 3 PCI 6 0 9 4000 04 PCI 7 pciQea 2000 1 PCI 8 pci ea 4000 2 9 pci ea 4000 3 PCI 0 pciQf0 2000 1 PCI 1 pci f0 4000 2 PCI 2 pci f0 4000 3 PCI 3 pciQfl 2000 1 PCI 4 pciQf1 4000 02 connected to 5 PCI 5 pciQfl 4000 3 PCI 6 pciQfl 4000 04 PCI 7 pciQf2 2000 1 PCI 8 pci f2 4000 02 PCI 9 pci f2 4000 3 0 pciQf8 2000 01 PCI 1 pciQf8 4000 2 PCT 2 pci amp f8 4000 3 PCI 3 pci
53. 10 Transmitting and eceiving data at lOMbps B yes Auto Negotiation is on no Auto Negotiation is off C full Transmitting and receiving data in full duplex mode half Transmitting and receiving data in half duplex mode D symmetric Send accept Flowcontrol request to from the remote system remote send Does not send Flowcontol request Only accept Flowcontrol request from the remote system local send Only send Flowcontrol request Does ot accept Flowcontrol equest from the remote system none Disabled Check the cable connection and the switch configuration There is no problem 59 Appendix A Messages No Message Cause Workaround E Master Communicating as Master Slave Communicating as Slave An error was found with a Check whether the value 3 Illegal value for ParameterName parameter defined in the is set correctly in the fjgi conf file file Installed physical memory may be Driver internal resources insufficient If this is 4 soft state alloc failed cannot be obtained not the cause report this error to your service provider 5 Allocation of descriptor memory The driver could not allocate Installed physical failed internal resources for DMA memory may be sufficient If this is The driver could not allocate not the cause report 6 fail to
54. 1_100 pkgadd R mini root directory d NOTE In this example the installation server is setup to install Solaris 8 OS on the client Substitute the appropriate Solaris level in the pkgadd command for other Solaris OS levels Information The package name may be displayed as FJSVgid 2 This is normal 2 For other PRIMEPOWER model client systems 42 3 5 Network Installation cd cdrom cdrom0 FUSVgid_3 0 lt So aris Level of client system Is FUSVgid FJSVgid us FJSVgidx us FJSVgidr us FuSVgidad us pkgadd R mini root directory d NOTE In this example the installation server is setup to install Solaris 8 OS on the client Substitute the appropriate Solaris level in the pkgadd command for other Solaris OS levels Caution When PWOO8QG1 is used please apply the following required patch to the install image in the install server Solaris 8 05 114536 11 or later Solaris 9 05 114994 11 or later Solaris 10 05 120462 04 or later When PWOG8GE1 or PWOGSGE2 is used please apply the following required patch to the install image in the install server Solaris 8 OS 114536 12 or later Solaris 9 OS 114994 12 or later Solaris 10 05 120462 05 or later cd cdrom cdrom0 FUSVgid_3 0 lt Solaris level of client system patchadd C mini root directory lt Patch ID gt cd 5 Eject the FUJITSU PCI GigabitEthernet 3 0 Updatel CD ROM from the CD
55. 4 bytes to 9014 bytes Use of JumboFrames can mitigate the CPU load and improve transmission speed Point to Point Connection Direct connection between FUJITSU PCI GigabitEthernet cards is forbidden except when used in the private LAN of a CLUSTER system 1 2 GigabitEthernet card Specifications 1 2 GigabitEthernet card Specifications The FUJITSU PCI GigabitEthernet card is an adapter that is installed into a PCI slot or a PCI Express slot 1 2 1 Specifications The specification of the FUJITSU PCI GigabitEthernet adapter is listed in Table 1 2 1 PCI GigabitEthernet Card Specification and Table 1 2 2 PCI Express GigabitEthernet Card Specification Table 1 2 1 PCI GigabitEthernet Card Specification Item Compatibility Host Bus Interface PCI Local Bus Revision 2 1 or later Network Interface 1000Base SX PWOO8GE4 PWOG8GE1 10 100 1000Base T PWOO8GE5 PWOG8GE2 PRIMEPOWER250 450 secondary LAN 10 100 1000Base T 4ports PW008QG1 Host Data Transfer 32 64 bit Bus Mastering DMA Transfers Bus Type One PCI slot per card Power Require ments Maximum 4 7W PWOO8GE4 5 PWOG8GE1 2 14 OW PWOO8QG1 1000Base SX PWOG8GE1 Multi mode Fibre 62 5 125 micron SC Duplex Connections 10 100 1000Base T PWOO8GE5 PWOGSGE2 PRIMEPOWER250 450 secondary LAN PWOO8QG1 Catbe Cable Cat5 cable can also be used for 10 100Mbps Table 1
56. 5 102 600000 pci 0 pci 8 pci 0 O4 IOBoat X 6 2 600000 100 108 100 1 4 PCI 3 PCIX3 pci 2 600000 pci 0 pci 9 pci 0 O4 pciQ2 600000 100 109 100 1 4 PCIS3 PCIEI pci 2 600000 1 0 1 1 1 0 1 0 0 PCIS3 PCIE2 pciQ2 600000 1 0 1 1 1 0 1 1 0 102 600000 0 10 1 0 10 9 00 IOBoat Ex 102 600000 pci 0 pci 9 pci 0 pci 0 O0 PCI 3 PCIE5 pciQ2 600000 1 0 1 9 1 0 1 1 0 PCIS3 PCIE6 pciQ2 600000 1 0 1 9 1 0 1 9 0 Basic PCI 03 700000 0 Slot pciQ3 700000 100 101 100 04 PCI 4 PCIX2 pci 3 700000 100 101 100 1 4 PCI 4 PCI 4 PCIX5 pci 3 700000 pci 0 pci 8 pci 0 O4 IOBoat X PCIS4 PCIX6 103 700000 pciQ0 pciQ8 pciQO 1 44404 PCI 4 PCIX3 pci 3 700000 pci 0 pci 9 pci 0 O4 pciQ3 700000 100 109 100 1 4 pci 3 700000 1 0 1 1 1 0 1 0 0 IOBoat Ex 2 pci 3 700000 1 0 1 1 1 0 1 1 0 pci 3 700000 1 0 1 1 1 0 1 9 0
57. 5 PCIE1 pci 5 700000 pci 0 pci 1 pci 0 pci 0 0 PCIS5 PCIE2 105 700000 pci 0 pci 1 pci 0 pci 1 0 PCI 5 PCI 5 PCIE3 105 700000 pci 0 pci 1 pci 0 pci 9 0 10Boat PCI 5 PCIE4 105 700000 pci 0 pci 9 pci 0 pci 0 0 PCI 5 PCIE5 pci 5 700000 pci 0 pci 9 pci 0 pci 1 0 5 6 105 700000 pci 0 pci 9 pci 0 pci 9 0 Basic PCI 06 600000 00 Slot Basic PCI PCIST 107 700000 0 Slot 0 700000 pci 0 pci l pci 0 4 PCI 7 PCIX2 107 700000 100 101 100 1 O4 5 107 700000 100 108 100 04 X 6 107 700000 100 108 100 1 O4 PCI 7 PCIX3 107 700000 pci 0 pci 9 pci 0 4 PCI 7 PCIX4 107 700000 100 109 100 1 O4 PCI 7 PCIE1 107 700000 pci 0 pci 1 pci 0 pci 0 0 PCIS7 PCIE2 pciQ7 700000 pci 0 pci 1 pci 0 pci 1 0 PCI 7 PCIE3 107 700000 pci 0 pci 1 pci 0 pci 9 0 TOBoat Ex PCI 7 PCIE4 pciQ7 700000 pci 0 pci 9 pci 0 pci 0 Q0 PCI 7 PCIE5 107 700000 pci 0 pci 9 pci 0 pci 1 0 0 700000 pci 0 pci 9 pci 0 pci 9 0 Logical Basic PCI PCI amp O pci 10 600000 0 System Slot Board Basic PCI 011 700000 0 1 Slot PCISI PCIXI pciQ11 700000 0 1 1 0
58. 8 4000 03 PRIMEPOWER 900 Extended rti tioning Board Number Slot Number Device Name SBHO 1080 2000 1 PCI 1 080 4000 02 PCI 2 pci 81 2000 1 PCI 3 pci 81 4000 2 PCI 4 pci 81 4000 3 PCI 5 pciQa2 2000 1 PCI 6 pciQa2 4000 2 PCI 7 0 2 4000 3 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name PCI O pciQc4 2000 1 PCI 1 pciQc4 4000 2 PCI 2 pciQc4 4000 3 PCI 3 0 5 2000 1 PCI 4 pci cd 4000 02 connected to SBHO PCI 5 5 4000 3 PCI 6 pciQc5 4000 04 PCI 7 pciQe6 2000 1 PCI 8 0 4000 2 PCI 9 pci e6 4000 3 7 1088 2000 1 PCI I 7 1088 4000 2 PCIH2 7 1089 2000 1 spi 089 4000 02 1089 4000 03 PCI 5 pci aa 2000 1 1 4000 2 pci aa 4000 3 PCI 0 pciQcc 2000 01 PCI 1 pci cc 4000 2 PCI 2 pciQcc 4000 3 PCI 3 pciQcd 2000 1 PCI 4 pci cd 4000 2 connected to 5 PCI 5 pci cd 4000 3 6 pciQcd 4000 04 PCI 7 pciQee 2000 1 8 pci ee 4000 2 PCI 9 pci ee 4000 3 PRIMEP
59. 99 4000 02 connected to 5 3 PCI 5 1099 4000 3 PCIH6 pciQ99 4000 04 PCI 7 pciQ9a 2000 1 8 pciQ9a 4000 2 PCI 9 pci 9a 4000 3 pciQ9c 2000 1 PCI 1 pci 9c 4000 2 PCI 2 pci 9c 4000 3 PCI 3 pciQ9d 2000 1 PCI BOX 1 PCI 4 pci 9d 4000 2 connected to 5 3 PCI 5 pci 9d 4000 3 6 7 094 1000 04 PCI 7 pciQ9e 2000 1 PCI 8 pci 9e 4000 2 PCI 9 09 4000 3 91 Appendix D PCI Slot Number and Device Name 92 Board Number Slot Number Device Name 0 pciQa0 2000 1 PCI 1 pciQa0 4000 2 PCI 2 pciQa0 4000 3 PCI 3 pciQal 2000 1 PCI 4 pci al 4000 2 connected to 5 4 PCI 5 pciQal 4000 3 PCI 6 0 1 4000 4 PCI 7 pciQa2 2000 1 PCI 8 pciQa2 4000 2 PCI 9 0 2 4000 3 pciQa4 2000 1 PCI 1 pciQa4 4000 2 PCI 2 pciQa4 4000 3 PCIZ3 1 5 2000 1 PCI BOX 1 PCI 4 5 4000 2 connected to 5 4 PCI 5 1 5 4000 3 PCI 6 pci ad 4000 04 PCI 7 pciQa6 2000 1 PCI 8 pciQa6 4000 2 PCI 9 4000 3 PCI 0 pci a8 2000 1 PCI 1 pci a8 4000 2 PCI 2 pci a8 4000 3 PCI 3 pciQa9 2000 1 PCI 4 9 4000 02 connected to 5 5 PCI 5
60. CI 3 01 4000 3 PCI 4 pci le 4000 4 PCI 5 pci le 2000 1 6 pciQ1d 4000 2 PCI 7 pciQ1d 4000 3 PCI 8 pciQ1d 4000 4 PCI 9 pci l1d 2000 1 PCI 10 pciQ1d 4000 2 PCI 11 pciQ1d 4000 3 Slot Number Device Name Appendix D PCI Slot Number and Device Name PCI 12 pciQ1c 4000 4 PCI 13 pciQ1c 2000 1 GP7000F Model600R Slot Number Device Name pciQ1f 4000 2 PCI 2 pciQ1f 2000 1 PCI 3 pciQ1c 4000 2 PCI 4 01 4000 2 PCI 5 01 4000 3 PCI 6 pci le 4000 4 PCI 7 pciQ1c 2000 1 PCI 8 pciQ1d 4000 2 PCI 9 pciQ1d 4000 3 PCI 10 pci ld 4000 04 PCI 11 pciQ1d 2000 1 PCI 12 pci le 2000 1 PRIMEPOWER 1 1U rackmount Slot Number Device Name pciQ1f 0 pci 1 2 PRIMEPOWER 100 pedestal Slot Number Device Name pciQ1f 0 pci 1 2 PCT 2 pciQlf 0 101 03 PCI 3 pciQ1f 0 pci l 1 04 PRIMEPOWER 200 pedestal rackmount Slot Number Device Name PCI 1 pci 17 2000 1 PCI 2 pci 16 2000 1 PCI 3 017 4000 2 PCI 4 pci 16 4000 2 PCI 5 016 4000 4 PCI 6 016 4000 5 PRIMEPOWER 250 pedestal Slot Number Device Name
61. E1 SEOX7GQ1X Chapter 2 Installing FUJITSU PCI GigabitEthernet Card This chapter describes the tasks necessary to install this card in the main unit Installation of the GigabitEthernet card Identifying the GigabitEthernet card Cable connection Chapter 2 Installing FUJITSU PCI GigabitEthernet Card 2 1 Installation of the GigabitEthernet Card Insert the card in a PCI slot or a PCI Express slot on the main unit Please refer to the main unit s User s Manual for details about installing cards and specific PCI slot or PCI Express slot specifications 2 2 Identifying the GigabitEthernet Card 2 2 Identifying the GigabitEthernet Card The GigabitEthernet card can be identified by executing the boot command at the OpenBoot prompt Chapter 2 Installing FUJITSU PCI GigabitEthernet Card 2 3 Cable Connection To connect the PWOO8GE4 PWOGSGEI and SEOX7GD2X GigabitEthernet card to the network use an optical fiber cable To connect the PWOO8GE5 PWOGSGE2 PRIMEPOWR250 450 secondary LAN PWOO8QG1 SEOX7GD1X and 5 0 7601 GigabitEthernet card to the network use a CAT5E twisted pair cable Enhanced Category 5 Figure 2 3 1 PWOO8GE4 with Optical Fiber Cable 12 2 3 Cable Connection Figure 2 3 2 PWOO8GE5 with Twisted Pair Cat5E Cable Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2 3 3 PWOG8GE1 with Optical Fiber Cable 2 3 Cable Connection Figure 2 3 4 PWOG8GE2 with
62. Extended Parti tioning Board Number Slot Number Device Name pci 80 2000 01 1080 4000 02 PCI 2 pci 81 2000 1 spo PCI 3 pci 81 4000 2 PCI 4 081 4000 3 PCI 5 0 2 2000 1 PCI 6 pciQa2 4000 2 PCI 7 0 2 4000 3 PCI 0 pciQc4 2000 1 PCI 1 pci c4 4000 2 PCI 2 pciQc4 4000 3 PCI 3 5 2000 1 PCI 4 1 5 4000 2 connected to SBHO 5 pciQc5 4000 3 PCI 6 pciQc5 4000 04 pciQe6 2000 1 PCI 8 0 4000 2 PCI 9 0 4000 3 pci 88 2000 01 1088 4000 02 PCI 2 1089 2000 1 PCIH3 1089 4000 02 1089 4000 03 PCI 5 pci aa 2000 1 PCI 6 pci aa 4000 2 PCI 7 pci aa 4000 3 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name pciQcc 2000 1 PCI 1 pciQcc 4000 2 PCI 2 pci cc 4000 3 PCI 3 pci cd 2000 1 PCI 4 pci cd 4000 2 connected to 5 PCI 5 pciQcd 4000 3 PCI 6 pciQcd 4000 4 PCI 7 pciQee 2000 1 PCI 8 pciQee 4000 2 PCI 9 pci ee 4000 3
63. I 7 pci ba 2000 01 8 pci ba 4000 2 PCI 9 pci ba 4000 3 0 pci bc 2000 01 PCI 1 pciebc 4000 2 PCI 2 pciebc 4000 3 PCI 3 pci bd 2000 1 PCI BOX 1 PCI 4 pci bd 4000 2 connected to 7 PCI 5 pci bd 4000 3 6 pci bd 4000 04 PCI 7 pci be 2000 1 PCI 8 pci be 4000 2 PCI 9 pci be 4000 3 93 Appendix D PCI Slot Number and Device Name 94 Board Number Slot Number Device Name 0 10 0 2000 1 pci c0 4000 2 PCI 2 1 0 4000 3 PCI 3 0 1 2000 1 PCI 4 pci cl 4000 02 connected to 5 8 PCI 5 0 1 4000 3 PCI 6 0 1 4000 04 PCI 7 pciQc2 2000 1 PCI 8 pciQc2 4000 2 PCI 9 pci c2 4000 03 pciQc4 2000 1 PCI 1 pciQc4 4000 2 PCI 2 10 4 4000 3 PCIZ3 pciQc5 2000 1 PCI BOX 1 PCI 4 5 4000 02 connected to 5 8 PCI 5 pciQc5 4000 3 PCI 6 pciQc5 4000 04 PCI 7 pci c6 2000 1 PCI 8 10 6 4000 2 PCI 9 pci c6 4000 3 PCI 0 pci c8 2000 1 PCI 1 10 8 4000 2 PCI 2 10 8 4000 3 PCI 3 pciQc9 2000 1 PCI 4 pci c9 4000 02 connected to 5 9 PCI 5 pciQc9 4000 3 PCI 6 pciQc9 4000 04 PCI 7 pci ca 2000 1 8 pci
64. IA pci f5 2000 01 pci f5 4000 02 pci f7 2000 0 PCI 3B pciQf7 4000 2 PCIS0A pciQf8 2000 1 PCISOB pciQf8 4000 02 SB 30 PCIS1A pciQf9 2000 pciQf9 4000 02 pciQfb 2000 1 PCI 3B pci fb 4000 2 PCIS0A pciQfc 2000 1 pci fc 4000 2 Jiu PCI IA pci fd 2000 01 pci fd 4000 02 pciQff 2000 1 PCI 3B pciQff 4000 2 89 Appendix D PCI Slot Number and Device Name PRIMEPOWER 2500 HPC2500 Physical Partitioning Board Number Slot Number Device Name PCI 0 1080 2000 1 PCI 1080 4000 2 PCIH2 1080 4000 3 PCI 3 pci 81 2000 1 PCI 4 081 4000 02 connected to SBHO PCI 5 pci 81 4000 3 PCI 6 pci 81 4000 4 1082 2000 01 PCIH8 1082 4000 2 PCI 9 082 4000 3 0 1084 2000 01 PCI 1 pci 84 4000 2 PCIH2 1084 4000 03 PCI 3 1085 2000 1 PCI BOX 1 PCI 4 085 4000 02 connected to 5 0 PCI 5 1085 4000 3 PCIH6 7 1085 4000 04 PCI 7 1086 2000 1 PCIH8 1086 4000 2 PCI 9 1086 4000 3 PCI 0 1088 2000 1 PCI I 7 1088 4000 2 PCI 2 1088 4000 03 PCI 3 1089 2000 1
65. OWER 1000 GP7000F 4 11000 Board Number Slot Number Device Name PCIHOA 1080 2000 0 PCISOB pci 80 4000 2 spo PCIS1A pciQ81 2000 1 081 4000 2 PCIH3A 7 1083 2000 1 PCI 3B pci 83 4000 2 PCIHOA 7 1088 2000 1 1088 4000 02 m PCI 1A pci 89 2000 01 PCI 1B 1089 4000 02 08 2000 01 PCI 3B pci 8b 4000 2 81 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name 090 2000 01 090 4000 02 SBH PCIS1A pciQ91 2000 1 PCISIB 091 4000 02 PCIH3A 1093 2000 PCI 3B 093 4000 2 PCIHOA 7 1098 2000 1 PCISOB pci 98 4000 02 ES PCIHIA 7 1099 2000 1 099 4000 02 pci 9b 2000 1 PCI 3B pci 9b 4000 2 PCIS0A pciQa0 2000 1 0 0 4000 02 spits pciQal 2000 1 PCI 1B pciQal 4000 2 pciQa3 2000 1 PCI 3B pci a3 4000 2 PCIS0A pci a8 2000 1 pci a8 4000 2 spits PCIS1A pciQa9 2000 1 PCI 1B pciQa9 4000 2 PCI 3A pci ab 2000 1 PCI 3B pciQab 4000 2 PCIHOA pei b0 2000 01 pci b0 4000 2 ha
66. PCI 1 pci 9c 4000 2 PCIZ2 pciQ9c 4000 3 PCI 3 pciQ9d 2000 1 PCI 4 pci 9d 4000 2 connected to 5 3 PCI 5 pci 9d 4000 3 6 7 094 1000 04 PCI 7 pciQ9e 2000 1 PCI 8 pciQ9e 4000 2 PCI 9 09 4000 03 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name 0 pciQa4 2000 1 PCI 1 pciQa4 4000 2 PCI 2 pciQa4 4000 3 PCI 3 1 5 2000 1 PCI 4 5 4000 2 connected to 5 4 PCI 5 1 5 4000 3 PCI 6 pci ad 4000 4 PCI 7 pciQa6 2000 1 PCI 8 pciQa6 4000 2 PCI 9 4000 3 pciQac 2000 1 PCI 1 pciQac 4000 2 PCI 2 pci ac 4000 3 PCIZ3 pci ad 2000 1 PCI 4 pci ad 4000 2 connected to 5 5 PCI 5 pci ad 4000 3 PCI 6 pci ad 4000 4 PCI 7 pciQae 2000 1 PCI 8 pci ae 4000 2 9 pci ae 4000 3 PCI 0 10 4 2000 1 pci b4 4000 02 PCIH2 pci b4 4000 03 PCI 3 pciQb5 2000 1 PCI 4 5 4000 2 connected to SBH6 PCI 5 pci b5 4000 3 PCIH6 pci b5 4000 04 PCI T pci b6 2000 01 PCI 8 pci b6 4000 2 PCI 9 pci b6 4000 3 0 pciebc 2000 01 PCI 1 pci bc 4000 2 PCI 2 pciebc 4000
67. PCIH6 1089 4000 2 PCIH7 1089 4000 3 PCI 8 pci 8a 2000 1 PCI 9 pci 8a 4000 1 PCI 10 pci 8a 4000 02 PCI 11 pci 8a 4000 3 79 Appendix D PCI Slot Number and Device Name PRIMEPOWER 900 Physical Parti 80 tioning Board Number Slot Number Device Name pci 80 2000 1 1080 4000 2 PCI 2 pci 81 2000 1 spo PCI 3 pci 81 4000 2 PCI 4 pci 81 4000 3 PCI 5 1082 2000 1 PCI 6 1082 4000 02 PCI 7 pci 82 4000 03 PCI 0 1084 2000 1 PCI 1 pci 84 4000 02 PCIH2 1084 4000 3 PCI 3 1085 2000 1 PCI 4 085 4000 2 connected to SBHO PCI 5 pci 85 4000 3 PCIH6 1085 4000 04 1086 2000 01 1086 4000 2 PCI 9 pci 86 4000 3 PCI 0 pci 88 2000 1 1088 4000 02 PCI 2 pci 89 2000 1 ES PCIH3 1089 4000 02 1089 4000 PCI 5 pci 8a 2000 1 6 pci 8a 4000 2 pci 8a 4000 03 PCI 0 pci 8c 2000 1 PCI 1 pci 8c 4000 2 PCI 2 108 4000 3 PCI 3 pci 8d 2000 1 PCI 4 pci 8d 4000 2 connected to 5 PCI 5 pci 8d 4000 3 6 08 4000 04 PCI 7 08 2000 1 PCI 8 08 4000 2 PCI 9 0
68. Qf9 2000 1 PCI 4 pciQf9 4000 02 connected to SBHf PCI 5 pciQf9 4000 3 PCI 6 pciQf9 4000 4 PCI 7 pciQfa 2000 1 PCI 8 0 4000 2 PCIH9 pci fa 4000 03 SPARC Enterprise M4000 M5000 Board Number Slot Number Device Name Logical Basic PCI pciQ0 600000 100 108 100 1 1 System Slot PCI 1 pciQ0 600000 0 i 09 0 Board PCI 1 PCIX1 100 600000 pci 0 pci 9 pci 0 pci l pci 0 O4 0 IOBoat X PCI 1 PCIX2 100 600000 pci 0 pci 9 pci 0 pci l pci 0 1 4 PCI 1 PCIX5 100 600000 100 109 100 108 100 0 6 100 600000 100 109 100 108 100 1 4 101 Appendix D PCI Slot Number and Device Name 102 Board Number Slot Number Device Name PCISI PCIX3 pciQ0 600000 0 9 0 1 9 0 4 pciQ0 600000 pci 0 pci 9 pci 0 pci 9 pci 0 1 4 PCI 1 PCIE1 100 600000 pci00 pci09 pci80 pciQ1 pci00 pci Q0 kQ0 PCI 1 PCIE2
69. ad and write 0 Invalid 1 Valid Default Receive Pause Frame Setting adv pauseRX Read and write 0 Invalid 1 Valid Default Auto Negotiation Setting adv autoneg cap Read and write 0 Auto Negotiation Off Fixed mode 1 Auto Negotiation On Default Role Setting Not valid for PWOOSGEA PWOGSGE1 SEOX7GD2X adv role cap Read and write 0 Slave 1 Master 2 Auto Default 34 3 3 Operation Mode Setup parameter status meaning The link partner has been set to 10Mbps FullDuplex by Auto Negotiation lp 10 cap Read only p y g 0 Invalid 1 Valid The link partner has been set to 10Mbps HalfDuplex by Auto Negotiation lp lOhdx cap Read only 4 PS 0 Invalid 1 Valid The link partner has been set to 100Mbps FullDuplex by Auto Negotiatio lp 100fdx cap Read only 0 Invalid 1 Valid The link partner has been set to 100Mbps HalfDuplex by Auto Negotiatio lp 100hdx cap Read only en 0 Invalid 1 Valid The link partner has been set to 1000Mbps FullDuplex by Auto Negotiation 1000fdx Read only 0 Invalid 1 Valid The link partner has been set to 1000Mbps HalfDuplex by Auto Negotiation lp 1000hdx cap Read only 0 Invalid 1 Valid The link partner has been set to transmit pause frame by Auto Negotiation lp pauseTX Read only 0 Invalid 1 Valid The link partner has been set to receive pause frame by Aut
70. aking changes to the fjgi conf file the system must be rebooted speed duplex flowcontrol it recommends carrying out default operation Auto Negotiation In that case connection partner equipment should also enable Auto Negotiation By doing so it is the optimal speed duplex flow control It is set up automatically When you use fjgi conf file and you change mode of operation please let mode of operation in agreement with self equipment and connection partner equipment When mode of operation is not in agreement with self equipment and connection partner equipment it may not become a value as a link up is not carried out or it cannot commu nicate even if it carries out a link up or mode of operation specified When an adapter is removed please remove the setting parameters of the applicable adap ter defined in the fjgi conf file If an adapter is removed and the setting parameters are left in the fjgi conf file panic may occur at the time of a system star Becau tup and it becomes impossible to start se the parameters are set in the fjgi conf file per physical interface when a VLAN interface is used individual interface used by the VLAN interface must be simi The p Recon after arly configured arameters set in the fjgi conf file may not become effective with DR Dynamic figuration function and Pci Hot Plug function The system must be rebooted the parameters are set
71. ample While Auto Negotiation had been enabled when changing 0 into 100Half Autonego 1 link sppd 100 link mode 0 from a default state Autonego 1 link speed 1000 link mode 1 ndd set dev fjgi instance 0 set dev fjgi 1000fdx cap set dev fjgi 1000hdx cap ndd set dev fjgi 100fdx cap ndd set dev fjgi autoneg cap ndd set dev fjgi autoneg cap Note Please perform change and sending back of Auto Negotiation at the end When setting change is reflected an Auto Negotiation value being subject to change set dev fjgi instance value Instance number value of an applicable interface is specified set dev fjgi parami value Change 1 of a setup ndd set dev fjgi param2 value Change 2 of a setup set dev fjgi adv autoneg Let Auto Negotiation be a different value from the present condition exapmle When f jgiO is changed into the state of 100 where Auto Negotiation was disabled from the state of 100Half Autonego 1 link sppd 100 ink_mode 0 where Auto Negotiation was enabled ndd set dev fjgi instance 0 set dev fjgi 100fdx cap 1 set dev fjgi autoneg cap 0 Note Please make change of Auto Negotiation at the end The following parameters can be used with the ndd command parameter status meaning
72. andle status information 5 not the cause report 28 status block can t bind handle esources this error to your fjgi board init mem Failed to The driver could not allocate 29 service provider dma_alloc DMA resources 30 statistic block can t alloced The driver could not allocate 31 hwmib block can t alloced handle statistic information 32 hwmib block can t bind handle esources 33 fjgi board init mem Failed to dma The driver could not allocate alloc2 DMA resources The value of LinkSpeed A in Set the correct value for 34 llegal value for LinkSpeed_A the configuration file is LinkSpeed A ncorrect 35 fjgi hw init Step 22 failed An error occurred during A hardware failure 36 fjgi hw init Step 23 failed initialization of the occurred Please contact 37 fjgi hw init Step 43 failed adapter your service provider 38 llegal combination of values AutoNeg Auto speed can not be used Set a value other than and Speed fixed mode Auto for LinkSpeed_A 61 Appendix A Messages No Message Cause Workaround Role setting is no supported with Remove Role_A parameter 39 Role not available for fiber adapters PWOO8GE4 PWOG8GE1 SEOX7GD2X in the fjgi conf file Check whether the system is supported Since there is possibility of TES The adapter type cannot be 2 40 Can t judge T or SX hard abnormalities when recognized the sys
73. aution If JumboFrame support is enabled the interface will be unable to transmit and receive data in IEEE802 3 format Q In the case of a method 1 or a method 2 if two or more interfaces VLAN interfaces are installed the JumboFrame setting applies to all interfaces When the file transfer protocol FTP is used set the MTU size to 8232 or less When using the JumboFrames function with the PWOO8GE5 PWOGSGE2 5 0 7601 PWOO8QG1 SEOX7GQ1X or the PRIMEPOWER250 450 secondary LAN port only use 1000Mbps mode 31 Chapter 3 Setting Configuration Information The parameters set in etc fjmtu fjgi and 1 conf file are not effective with DR Dynamic Reconfiguration function and Pci Hot Plug function To be effective this file the system must be rebooted 3 3 3 The ndd Utility By using the ndd command the interface communication mode can be changed dynamically Usually although it is not necessary to change the interface communication mode by the ndd command when shown in the following examples please change the interface communication mode by the ndd command Example It changed into the equipment which does not support Auto Negotiation from the equipment which supports Auto Negotiation for connection partner equipment after a system startup Or it changed into the equipment which supports Auto Negotiation from the equipment which does not support Auto Negotiation conversely The following examples show h
74. bbreviated to Solaris OS system administration and a basic knowledge of networked systems Organization This section describes the chapters in this document Chapter Product Outline Chapter 1 describes the distinctive features of the FUJITSU PCI GigabitEthernet Card Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Chapter 2 describes how to install the adapter Chapter 3 Setting Configuraton Information Chapter 3 provides an overview of the environment definition Chapter 4 LinkA ggregation Feature Chapter 4 describes how to use the LinkAggregation function Chapter 5 Troubleshooting Chapter 5 offers suggestions about how to troubleshoot and resolve problems you might encounter during installation Appendix A Messages Appendix A shows the messages output by the driver software Appendix B On Board Diagnostics Appendix B shows details of the adapter s on board diagnostics Appendix C Using GigabitEthernet in a Cluster Environment Appendix C describes notes when using the adapter in a Cluster System Appendix D PCI Slot Number and Device Name Appendix D shows the PCI slot number and device name list matrix for each PRIMEPOWER model Appendix E Available Switches Appendix E shows a list of the available and supported switches 8th Edition April 2007 Symbol The following conventions are used in this manual Caution Items that require attention are explained Information Useful information is given Atten
75. c 2000 1 PCI 1 pciQdc 4000 2 PCI 2 pciQdc 4000 3 PCI 3 pciQdd 2000 1 PCI BOX 1 PCI 4 pci dd 4000 2 connected to 5 PCI 5 pci dd 4000 3 PCI 6 pciQdd 4000 4 PCI 7 pciQde 2000 1 PCI 8 pciQde 4000 2 9 pci de 4000 3 95 Appendix D PCI Slot Number and Device Name 96 Board Number Slot Number Device Name 0 1 0 2000 1 1 0 4000 2 PCI 2 1 0 4000 3 PCI 3 pciQel 2000 1 PCI 4 pci el 4000 2 connected to 5 PCI 5 pciQel 4000 3 PCI 6 0 1 4000 4 PCI 7 pciQe2 2000 1 PCI 8 0 2 4000 2 PCI 9 pci e2 4000 3 pciQe4 2000 1 PCI 1 0 4 4000 2 PCI 2 0 4 4000 3 PCIZ3 1 5 2000 1 PCI BOX 1 PCI 4 pci ed 4000 2 connected to 5 PCI 5 1 5 4000 3 PCI 6 pciQe5 4000 4 PCI 7 pciQe6 2000 1 PCI 8 0 4000 2 PCI 9 0 4000 3 PCI 0 0 8 2000 1 PCI 1 pciQe8 4000 2 PCI 2 pci e8 4000 3 PCI 3 pciQe9 2000 1 PCI 4 1 9 4000 02 connected to 5 PCI 5 pciQe9 4000 3 PCI 6 pciQe9 4000 04 PCI 7 pciQea 2000 1 8 pci ea 4000 2 9 pci ea 4000 3 PCI 0 2000 1 PCI
76. connected to 100Mbps network and is in the state The adapter is connected to 10Mbps network and is in the state hich can communicate the adapter is not connected to network ACT LED Green LED i Figure B 7 8 indicates the following operation status ACT LED Description Green blinking The adapter is transmitting or receiving network traffic Off There is no network traffic 69 Appendix Using GigabitEthernet in a Cluster Environment This Appendix outlines the supported functions and setup procedure for the FUJITSU PCI GigabitEthernet 3 0 interface when used in a cluster environment C 1 Cluster Environment Support The FUJITSU PCI GigabitEthernet 3 0 adapter supports the following cluster features Operation standby mode l n operation standby mode Mutual standby mode TCP IP communication public LAN Use of a VLAN interface by SynfinityCluster private LAN or PRIMECLUSTER cluster interconnect cannot be performed A JumboFrame function can be used in SynfinityCluster private LAN or PRIMECLUSTER cluster interconnect When you change MTU size from a default value 9000 please set up by the fjgi conf file For details please refer to Method 3 How to specify by fjgi conf of 3 3 2 JumboFrame Setup The following table shows the supported failover mode with the FUJITSU PCI GigabitEthernet interfaces in a cluster system Synfini
77. ction LEDs PWOO8GE4 PWOG8GE1 SEOX7GD2X allow optical fibre cable connection PWOO8GE5 PWOGSGE2 PRIMEPOWER250 450 secondary LAN port SEOX7GD1X PWOO8QG1 and SEOX7GQ1X allow twisted pair cable connection See the section Chapter 2 Installing FUJITSU PCI GigabitEthernet Card for detailed information PWOO8GE4 1000BASE SX has two LEDs 1000 LED ACT LED indicating transmission rate and activity PWOG8GE1 and SEOX7GD2X 1000BASE SX has two LEDs LINK LED ACT LED indicating transmission rate and activity PWOO8GE5 and PWOGSGE2 10 100 1000BASE T have four LEDs 1000M LED 100M LED 10M LED ACT LED indicating 1000Mbps 100Mbps 10Mbps and activity SEOX7GD1X 10 100 1000BASE T have three LEDs 1000M LED 100M LED LINK ACT LED indicating 1000Mbps 100Mbps and activity PWOO8QG1 and SEOX7GQ1X 10 100 1000BASE T has two LEDs LINK LED ACT LED indicating transmission rate and activity See Appendix B On Board Diagnostics for detailed information 1 2 GigabitEthernet card Specifications Figure 1 1 1000Base SX Figure 1 2 10 100 1000Base T PWOOSGE4 0086 5 Figure 1 3 1000Base SX Figure 1 4 10 100 1000Base T PWOG8GE1 PWOG8GE2 Chapter 1 Product Outline Figure 1 5 1000Base SX 2ports Figure 1 6 10 100 1000Base T 2ports SEOX7GD2X SEOX7GD1X 1 2 GigabitEthernet card Specifications Figure 1 7 10 100 1000Base T 4ports Figure 1 8 10 100 1000Base T 4ports PWOG8G
78. demarks 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 Revision History Revised section 1 Edition Date Details Added Deleted Altered 01 2003 2 20 Appendix 1 100 is added 3 4 Change the procedure 02 2003 5 1 3 3 1 Some parameter explanations are added 35 Some procedures are added 3 6 VLAN information is added 03 2004 1 8 Change the Version 2 0 to 2 1 Appendix E VLAN tested switches are added Chapter 4 LinkAggregation function is added Change the Version 2 1 to 2 2 04 2004 10 28 Appendix Messages are added Appendix E Switches are added 05 2005 11 11 Change the Version 2 2 to 2 3 06 2006 02 06 Change the Version 2 3 to 2 4 07 2007 01 20 Change the Version 2 4 to 3 0 08 2007 04 03 Change the Version 3 0 to 3 0 Update Preface Purpose This manual describes how to install the FUJITSU PCI GigabitEthernet card in your PRIMEPOWER system and configure the environment setting of the interface Target Reader This book is intended for system administrators responsible for installing the FUJITSU PCI GigabitEthernet card To understand the concepts and procedures presented in this manual you need from one to two years of experience in the Solaris TM Operating System in this document a
79. e PCI IA pci bl 2000 01 PCISIB pciObl 4000 2 pci b3 2000 1 PCI 3B pci b3 4000 2 PCIHOA 7 1 8 2000 1 pci b8 4000 02 SBHT PCI IA pci b9 2000 1 pci b9 4000 02 PCIH3A pci bb 2000 PCI 3B pci bb 4000 2 PRIMEPOWER 1500 Physical Partitioning Board Number Slot Number Device Name 1080 2000 1 080 4000 02 PCI 2 pci 81 2000 1 spo PCI 3 pci 81 4000 2 PCI 4 1081 4000 3 PCI 5 1082 2000 1 PCIH6 1082 4000 2 PCI 7 1082 4000 3 82 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name 0 1084 2000 01 pci 84 4000 2 PCIH2 1084 4000 03 PCI 3 1085 2000 1 PCI 4 085 4000 2 connected to SBHO PCI 5 pci 85 4000 3 PCIH6 1085 4000 04 PCI 7 1086 2000 1 1086 4000 2 PCI 9 pci 86 4000 03 pci 88 2000 1 1088 4000 2 PCIH2 pci 89 2000 01 spi 089 4000 02 1089 4000 PCI 5 pci 8a 2000 1 PCI 6 pci 8a 4000 2 PCI 7 08 4000 3 PCI 0 pci 8c 2000 01 PCI 1 108 4000 2 PCI 2 pci 8c 4000 3
80. egotiation OK OK with SH4322G only SH4322G function of the switch CISCO Systems Catalyst5500 OK OK 6500 series Extreme Networks Summit series OK OK with i series only Extreme Networks BlackDiamond OK OK with i series only E series Table E 2 With FUJITSU PCI GigabitEthernet 3 0 PWOO8GE5 PWOG8GE2 SEOX7GD1X PWOO8QG1 SEOX7GQ1X and PRIMEPOWER250 450 secondary LAN port Gigabit Switches Product Name Connection JumboFrame Note FUJITSU 5 4000 5 43226 ae OK with SH4322G _ SH4124T only CISCO Systems Catalyst3550 OK with 6000 series _ 4000 6000 series only Extreme Networks Summit OK OK with i series series only 10 100Mbit Switches Product Name Connection Note FUJITSU SH1508 5 508 5 516 With SH4322G 100M Half SH1816 5 1816 5 1824 SH4124 OK connection is not supported SH4322G SH5124T LH8VC2 Repeater Router Product Name Connection Note FUJITSU NetShelter In 10 100M OK fix mode use cross cable Table E 3 802 14 TagVLAN capable switches Product Name Connection Note FUJITSU SH4124T SH4322G OK Superstack 3 OK Hewlett Packard ProCurve 8000m OK Extreme Networks Summit li 7i OK CISCO Systems Catalyst3550 OK 107 Appendix E Available Switches 108 Table 4 IEEE802 3 LinkAggregation capable switches
81. escription The adapter is connected to a 100Mbps network and is in the state Green lighting which can communicate Off The adapter is not connected to a 100Mbps network 10M LED indicates the following operation status PWOO8GE5 only 10M LED Description The adapter is connected to a 10Mbps network and is in the state Green lighting which can communicate Off The adapter is not connected to a 10Mbps network 65 Appendix B On Board Diagnostics 66 ACT LED indicates the following operation status ACT LED Description Green lighting The adapter is transmitting or receiving network traffic Off There is no network traffic Location of the LEDs PNOG8GE1 SEOX7GD2X The following figures show the location of the LEDs Figure B 3 1000Base SX PWOG8GE1 1000Base SX 2ports SEOX7GD2X Figure B 4 Meaning of the LEDs PWOG8GE1 SEOX7GD2X LINK LED indicates the following operation status LINK LED Description Green lighting The adapter is connected to a 1000Mbps network and is in the state which can communicate Off The adapter is not connected to a 1000Mbps network ACT LED indicates the following operation status ACT LED Description Green lighting The adapter is transmitting or receiving network traffic Off There is no network traffic Location of the LEDs
82. etc path to inst grep pciQ1 700000 pciQ0 FJSV e4ta04 0 pciQ1 700000 pci 0 FUSV e4ta04 1 1 pciQ1 700000 pci 0 1 FJSV e4ta 6 2 pciQ1 700000 pciQ0 1 FJSV e4ta06 1 3 pci 3 700000 pciQ0 FJSV e2sa04 4 pci 3 700000 pci 0 FUSV e2sa04 1 5 pci 2 600000 pci 0 FUSV e2ta04 6 pciQ2 600000 pci 0 FUSV 2 04 17 7 The logical bus address and the instance number shown in bold above are displayed The following table shows the logical bus address instance number and driver name for the example output above Logical bus address Instance number Driver name 101 700000 pci 0 FJSV e4ta 4 N 101 700000 pci 0 FJSV e4ta 4 1 N 101 700000 pci 0 1 FJSV e4ta 6 101 700000 pci 0 1 FJSV e4ta 6 1 8 103 700000 pci 0 FJSV e2sa 4 8 103 700000 pci 0 FJSV e2sa 4 1 RS ga oa 102 600000 pci 0 FJSV e2ta 4 J pci 2 600000 pci 0 FJSV e2ta 4 1 y fjgi The logical bus address corresponds to a physical PCI slot number based on the Main Unit model number Refer to the Appendix D PCI slot number and device name to determine the slot number
83. heck Item Recommended Action Optical fiber cable Replace the optical fiber cable Install the GigabitEthernet card to the PCI Adapter installation state slot of the system properly Adapter hardware Replace the GigabitEthernet card Cable connection to the GigabitEthernet Connect the cable to the devices firmly interface and the switch Power status of the GigabitEthernet switch Check the power of the switch Connection port of the switch Change the connection port of the switch Switch configuration Check the switch configuration Check the fjgi conf file or change the file fjgi conf file to default Re install the driver package from the driver Driver package installation status CD ROM or the FUJITSU download web site Appendix Messages A 1 This chapter explains messages from the FUJITSU PCI GigabitEthernet driver Console Messages Console messages from the FUJITSU PCI GigabitEthernet driver are listed in Table 1 1 Table 1 1 Console Messages of the FUJITSU PCI GigabitEthernet driver No Message Cause Workaround network connection down network connection up using portA speed A autonegotiation B duplex mode flowctrl D role E Link is down Link has become up A 1000 Transmitting and eceiving data at 1000Mbps 100 Transmitting and eceiving data at 100Mbps
84. i83 2000 PCI 3B 083 4000 2 PCIHOA 7 1084 2000 1 PCISOB 1084 4000 02 ae PCIHIA 1085 2000 01 085 4000 02 PCIH3A 1087 2000 01 PCI 3B 087 4000 2 PCIHOA 7 1088 2000 1 1088 4000 02 PCIHIA 7 1089 2000 1 PCISIB 1089 4000 2 pci 8b 2000 01 PCI 3B pci 8b 4000 2 PCIS0A pciQ8c 2000 1 108 4000 2 dus PCIHIA pei 8d 2000 1 PCISIB pci 8d 4000 2 PCIH3A 108 2000 01 PCI 3B pci 8f 4000 2 PCIHOA 1090 2000 01 PCISOB 090 4000 02 spits PCIS1A pciQ91 2000 1 PCISIB 091 4000 2 093 2000 1 pci 93 4000 2 094 2000 01 094 4000 02 SBHS PCI IA 095 2000 1 pci 95 4000 02 PCIH3A 1097 2000 0 PCI 3B pci 97 4000 2 PCIHOA 7 1098 2000 1 098 4000 02 kx PCIHIA 1099 2000 0 099 4000 02 PCIH3A 109 2000 01 PCI 3B pci 9b 4000 2 PCIS0A pciQ9c 2000 01 09 4000 02 PCIHIA 1094 2000 01 PCISIB pci 9d 4000 2 pciQ9f 2000 1 PCI 3B pciQ9f 4000 2 Board Number Appendix D PCI Slot Number and Device Name Slot Number Device Name
85. l not be able to communicate with remote device operating in fixed mode Auto Negotiation disabled When PWOO8GE5 PWOGSGE2 SEOX7GDIX PWOO8QG1 SEOX7GQIX or PRIMEPOWER250 450 secondary LAN port is used in 1000Mbps mode On default use this setting 26 3 4 5 Parameter Value 3 3 Operation Mode Setup Description Off Auto Negotiation is disabled Fixed mode LinkSpeed A 2 Auto default Connection speed of 1000 100 or 10 Mbps is set based on negotiation with the remote device This can only be set when AutoNegotiation A On 1000 Connect at 1000Mbps 100 Connect at 100Mbps 10 Connect at 10Mbps DuplexCapabilities A 2 Both default Indicating that both Full Duplex and Half Duplex are being supported This can only be set when utoNegotiation_A On Half alf Duplex operation is allowed Full FlowControl A 3 Auto default low control is performed according to a setup f partner equipment A H Full Duplex operation is allowed F 0 nly flow control from the remote machine is Rem allowed Flow control to the remote machine is not allowed Only flow control from the main unit is LocSend allowed Flow control from the remote machine is not allowed None Flow control is disabled Role 4 Auto default Master or Slave is set based on negotiation
86. mmunication 10Mbps example ok transfer speed 10 example ok half duplex Display the current settings example ok properties 1 Chapter 3 Setting Configuration Information The following example shows the current settings of a PWOO8GE5 card installed in a PRIMEPOWER600 6 ok pci 11 4000 FJSV pgtb 5 6 ok properties hal f lt 1 transfer speed 0000000 2 cabinet name Cab inet 0 board name Motherboard 1 assigned addresses 83002810 00000000 00100000 00000000 00010000 82002830 00000000 00110000 00000000 00010000 local mac address 00 0 00 c5 0c fjgiga rev 000000c2 product name FJSV pgtb device type network address bits 00000030 max frame size 00004000 reg 00002800 00000000 00000000 00000000 00000000 03002810 00000000 00000000 00000000 00010000 mode Broadcom BCM5703C compatible name FJSV pgtb media type 1000BASE T fcode rom offset 00000000 66mhz capable fast back to back devsel speed 00000001 class code 00020000 interrupts 00000001 latency 00000000 min grant 00000040 subsystem id 00001121 subsystem vendor i d 000010cf revision id 00000002 device id 00001141 vendor id 000010cf pcibus name PC I BUS G component name 01 5 fru PCI Slot PCI 5 at Motherboard 1 Displayed only when half duplex is set 2 Displayed only when transfer speed is set to a specific value 10Mbps 0xa 100Mbps 0x64 1000Mb
87. nce fjgi0 fjgi2 Distribution mode Source Destination IP address distribution PRIMEPCWER cca uu LAN Switch adapted LinkAggregation Im The etc opt FJSVla config file for this configuration should look similar to the following FJSVla FUJITSU LinkAggregation setup sample file attension Don t use the different link speed interfaces in same group and can t use half duplex interface in LinkAggregation member instance Input the number of interface The available members are max 7 Please t include the aggregator interface number 1 Mac Hash 2 Destination Address 3 Source and Destination Address format aggregator interface member_instance member_instance mode i example fjgid fjgi4 fjgil 0 2 3 51 Chapter 4 LinkAggregation Feature Caution The etc hostname fjgiXX XX instance number file is required for the aggregator interface only in the above example etc hostname fjgil is required The LinkAggregation group defined in the configuration file is activated by rebooting the system 4 2 2Using the etc opt FJSVla bin f jla Command The fjla command has the following functions Activate LinkAggregation Group fjla init Inactivate LinkAggregation Group fjla term Display status and statistics fjla stat 4 2 2 1 Activate LinkAggregation Group fjla init This section explains the fjla init comma
88. nce there is abnormalities when a problem still is not solved please replace the adapter 2 Command Messages Message Meaning Workaround There is a possibility of fjgi device check fjgi hw init n error occurred during hardware abnormalities failed initialization of the adapter Please replace the adapter There is a possibility of the resource shortage or he driver could not allocate an hardware abnormalities Uu pci config setup failed ufficient PCI configuration Please check the memory space usage and adapter installation status Check the transmission ey The Auto Negotiation of Autonegotiation_failed mode and the adapter 1000BASE SX failed hardware 2 Command Messages Messages from the etc opt FJSVla bin fjla command are listed in TableA 2 indicates user input value Table A 2 Command Message No Message Cause Workaround fjla init The number of More than 8 interfaces Specify less than or equal members including aes 1 were specified for to 8 interfaces including aggregator interface is max N A 8 aggregation group aggregator interface LinkAggregation has been 2 FJ LinkAggregation now start There is no problem started normally 275 The interface doesn t If the interface is fjgi fjla init does not 3 support the check the patch level of
89. nd for activating a LinkAggregation group Synopsis etc opt FJSVla bin fjla init ageregator interface member instance member instance 1 distr ibut ion mode aggregator interface Aggregator interface name including instance number member instance nstance numbers of member interfaces distribution mode Distribution mode used by the LinkAggregation group One of the following values must be specified 1 Destination MAC address distribution 2 Destination IP address distribution 3 Source Destination IP address distribution Description Configure and activate the LinkAggregation group All VLAN interfaces associated with the aggregator interface will be automatically configured in the group Exit code 0 normal end gt 0 error end Example Configure and activate the LinkAggregation group with the following Aggregator interface fjgi0 Member instance fjgil fjgi2 Distribution mode Source Destination IP address distribution 52 4 2 Configuration of the LinkAggregation Feature LinkAgere gation E ee ee Erg LAN Switch adapted to LinkAggregation etc opt FJSVla bin fjla init 0 1 2 2 0 FJ LinkAggregation now start Caution Before executing the command the aggregator interface must be already activated the interface can be displayed by ifconfig and the member instances must not be activated Q The aggregator interface must not be specified a
90. ng the FCode settings Q Search for the device path for the GigabitEthernet interface at the ok prompt Please refer to chapter 3 4 Discernment of the GigabitEthernet Interface example ok show nets a pciQ1f 4000 FJSV pgtb d b pciQ1f 4000 network61 1 q NO SELECTION Enter Selection q to quit In above example 01 4000 FJSV pgtb 5 represents PWOO8GE5 interface Select the device example ok pciQ1f 4000 FJSV pgtbQ5 Execute the following command to change the mode into Force mode speed fixed 36 3 3 Operation Mode Setup Auto Negotiation off from Auto Negotiation mode Setup to FCode is effective between OBP Open Boot Prom 1 The mode which can be set up on PWOO8GE4 PWOG8GE1 SEOX7GD2X 1000BASE SX is as follows Execute the following command to set Full Duplex communication 1000Mbps example ok transfer speed 1000 2 The mode which can be set up on PWOOSGE5 PWOGSGE2 SEOX7GD1X PWOOS8QG1 SEOX7GQ1X and PRIMEPOWER250 450 secondary LAN port is as follows Execute the following command to set Full Duplex communication 100Mbps example ok transfer speed 100 Execute the following command to set Half Duplex communication 100Mbps example ok transfer speed 100 example ok half duplex Execute the following command to set Full Duplex communication lObps example ok transfer speed 10 Execute the following command to set Half Duplex co
91. nkAggregation groups defined in the file will be automatically activated during the system boot In this case it is not necessary to run etc opt FJSVla bin fjla command manually 1 Create the etc opt FJSVla config file The etc opt FJSVla config sample file is provided by the FJSVla package Copy the sample file to create the config file cp etc opt FJSVla conf ig sample etc opt FJSVla conf ig 2 Modifying the etc opt FJSVla config file The following parameters must be specified in the etc opt FJSVla config file to use the LinkAggregation feature aggregator interface Specify the physical interface that represents the LinkAggregation group The froup is a unit that performs data distribution and aggregation and also provides redundancy member instance Specify the interfaces that belong to the LinkAggregation group by instance number except aggregator interface The valid number of members is 1 to 7 Multiple members can be specified by separating them with 7 7 distribution mode Specify the distribution mode used by the LinkAggregation group See 4 1 About LinkAggregation Feature for detailed information about each distribution mode Specify any one of the following values 1 Destination MAC address distribution 2 Destination IP address distribution 3 Source Destination IP address distribution Example Aggregator interface fjgil 50 4 2 Configuration of the LinkAggregation Feature Member insta
92. o distinguish between VLAN interfaces and physical interfaces The following naming format is used to create the VLAN interface number VLAN Interface Number 1000 VID Physical Instance Number VLAN Interface Setup Examples To create a VLAN Interface Number for an interface with a physical instance of 3 45 Chapter 3 Setting Configuration Information and belonging to VID 231 the following is used VLAN Interface Number 1000 VID Physical Instance Number f jgi231003 1000 231 3 Refer to 3 2 Environment Setting and create the interface name fjgi231003 Low 3 digits of VLAN interface number physical instance number Upper digits except low 3 digits of VLAN interface number VLAN ID 1 4094 VLAN interface number VLAN ID 1000 physical instance number Caution When connecting VLAN interfaces to a LAN switch the switch must support Tag VLAN Please refer to Appendix E Available Switches 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 protocol Do not use the VLAN interface with SNA FNA or OSI protocol SafeLINK and PRIMECLUSTER GLS 4 1A20 or earlier do not support the VLAN function PRIMECLUSTER GLS 4 1430 or later in fast switching NIC switching mode does support the VLAN function The VLAN function is supported with Solaris 8 OS or later Ina PRIMECLUSTER
93. o Negotiation lp pauseRX Read only 0 Invalid 1 Valid The link partner has been set to Auto Negotiate by Auto Negotiation lp autoneg cap Read only 0 Invalid 1 Valid The current Role setting when operating at 1000Mbps Not valid for role cap Read only PWOOSGEA PWOGSGE1 SEOX7GD2X 0 Slave 1 Master 0 JumboFrame support disabled jumbo Read only 1 JumboFrame support enabled Caution About speed duplex flowcontrol Auto Negotiation In that case connection partner equipment should also enable it recommends carrying out default operation Auto Negotiation By doing so it is the optimal speed duplex flow control It 35 Chapter 3 Setting Configuration Information is set up automatically When you use ndd command and you change mode of operation please let mode of operation in agreement with self equipment and connection partner equipment When mode of operation is not in agreement with self equipment and connection partner equipment it may not become a value as a link up is not carried out or it cannot communicate even if it carries out a link up or mode of operation specified for same driver at the same time ue to the ndd command specification if two or more processes execute the ndd command the resulting value will be invalid f the ndd command is issued repeatedly the fjgi driver s performance may decrease The link_speed link_mode autonego and flow_control
94. ow to display and set the parameters using the ndd command Setup of an instance number set dev fjgi instance value Instance number value of an applicable interface is specified example fjgi2 is specified ndd set dev fjgi instance Note carry out for referring to carry out for setting up it is necessary to specify the instance number of an applicable fjgi interface first To display get dev fjgi param param Each parameter example The state of the link of fjgi2 is referred to set dev fjgi instance 2 get dev fjgi link status To set set dev fjgi param value param each parameter and value Value example 1000Mbps FullDuplex of fjgi2 is disabled ndd set dev fjgi instance 2 set dev fjgi adv 1000fdx cap Note In this stage a setup is not reflected in hardware yet When setting change is reflected with no change of an Auto Negotiation value 32 3 3 Operation Mode Setup set dev fjgi instance value Instance number value of an applicable interface is specified set dev fjgi parami value Change 1 of a setup set dev fjgi param2 value Change 2 of a setup set dev f jgi autoneg Once let Auto Negotiation be a different value from the present condition set dev fjgi adv autoneg cap M Auto Negotiation is returned to the original value ex
95. pci 8 pci 0 1 4 PCI 3 PCIX3 pci 3 700000 1 0 1 9 1 0 4 PCI 3 PCIX4 pci 3 700000 pci00 pciQ9 pci Q0 1 4 PCI 3 PCIE1 pci 3 700000 pci 0 pci 1 pci 0 pci 0 0 PCI 3 PCIE2 pci 3 700000 1 0 1 0 1 1 0 PCI 3 PCIE3 pci 3 700000 pci 0 pci 1 pci 0 pci 9 0 PCI 3 PCIE4 pci 3 700000 1 0 1 9 1 0 1 0 0 PCIS3 PCIE5 pciQ3 700000 pci 0 pci 9 pci 0 pci 1 0 PCI 3 PCIE6 pci 3 700000 pci 0 pci 9 pci 0 pci 9 0 Basic PCI ease pci 4 600000 0 Basic PCI PCI 5 1 65 700000 0 Slot 5 PCI 5 PCIX1 105 700000 pci 0 pci l pci 0 4 IOBoat X pci 5 700000 100 101 100 1 Appendix D PCI Slot Number and Device Name Board Number Slot Number Device Name PCIS5 PCIX5 105 700000 pci 0 pci 8 pci 0 O4 PCIS5 PCIX6 105 700000 pci00 pci08 pciQ0 1 O4 PCIS5 PCIX3 105 700000 pci 0 pci 9 pci 0 O4 PCIS5 PCIX4 105 700000 pci00 pci09 pciQ0 1 O4 PCI
96. pciQ15 700000 0 1 9 0 0 0 PCIS5 PCIE5 pciQ15 700000 pci 0 pci 9 pci 0 pci 1 0 5 pciQ15 700000 1 0 1 9 1 0 1 9 0 Basic PCI PCI amp 6 pci 16 600000 0 Slot Basic PCI PCI 7 pciQ17 700000 0 Slot pciQ17 700000 0 1 1 0 4 PCI 7 PCIX2 pci 17 700000 100 101 100 1 4 PCI 7 PCIX5 pci 17 700000 pci 0 pci 8 pci 0 4 IOBoat X 6 017 700000 100 108 100 1 4 pciQ17 700000 0 1 9 0 4 PCI 7 PCIX4 pci 17 700000 100 109 100 1 4 PCI 7 PCIE1 pciQ17 700000 pci 0 pci l pci 0 pci 0 0 PCIS7 PCIE2 pciQ17 700000 pci 0 pci 1 pci 0 pci 1 0 PCI 7 PCIE3 pci 17 700000 pci 0 pci l pci 0 pci 9 0 IOBoat Ex PCIH 7 PCIE4 pciQ17 700000 pci 0 pci 9 pci 0 pci 0 0 PCI 7 PCIE5 pciQ17 700000 pci 0 pci 9 pci 0 pci 1 0 PCI 7 PCIE6 pciQ17 700000 1 0 1 9 1 0 1 9 0 106 Appendix E Available Switches This appendix shows switches tested with FUJITSU PCI GigabitEthernet 3 0 as of January 2007 Table E 1 With FUJITSU PCI GigabitEthernet 3 0 PWOO8GE4 PWOG8GE1 SEOX7GD2x Product Name Connection JumboFrame Note With SB7300 turn off FUJITSU SH4000 SB7300 SR8800 the Auton
97. ps 0x3e8 Note and 2 are not displayed in a default configuration Returning to Default FCode Settings Q To return to default FCode settings execute the following command from the ok prompt or power cycle the system ok reset all 38 3 4 D iscernment Of the GigabitEthernet Interface 3 4 Discernment Of the GigabitEthernet Interface This section explains how to distinguish the FUJITSU PCI GigabitEthernet interface instance number interface type and which slot the card is installed in Discernment Of the GigabitEthernet Interface on PRIMEPOWER or GP7000 family Discernment Of the GigabitEthernet Interface on SPARC Enterprise 3 4 1 Discernment Of the GigabitEthernet Interface on PRIMEPOWER or GP7000 family This section explains how to distinguish the FUJITSU PCI GigabitEthernet interface instance number interface type and which slot the card is installed in on PRIMEPOWER or GP7000 family 1 To determine the instance number prtconf D grep example prtconf D grep FJSV pwga instance 0 FJSV pgsb instance 1 FJSV pgtb instance 2 FJSV p4ta instance 3 FJSV p4ta instance 4 FJSV p4ta instance 5 FJSV p4ta instance 6 execute the following command driver driver driver driver driver driver driver The instance number is the number displayed in bold above The adapter type can also be determined from the prtconf command outp
98. ription Amber lighting The adapter is connected to a 1000Mbps network and is in the state which can communicate Off The adapter is not connected to a 1000Mbps network 100M LED indicates the following operation status 100M LED Description Green lighting The adapter is connected to a 100Mbps network and is in the state which can communicate Off The adapter is not connected to a 100Mbps network LINK ACT LED indicates the following operation status LINK ACT LED Description Green lighting The adapter is connected to a 1000Mbps 100Mbps or 10Mbps network and is in the state which can communicate Green Blinking The adapter is transmitting or receiving network traffic Off The adapter is not connected to a 1000Mbps 100Mbps or 10Mbps network and there is no network traffic 68 Location of the LEDs 008061 5 0 7001 The following figures show the location of the LEDs Figure B 7 Meaning of the LEDs LINK LED White LED Figure B 8 1000 4ports PWO08QG1 1000Base T 4ports SEOX7GQ1X PWOO8QG1 SEOX7GQ1X in Figure B 7 8 indicates the following operation status LINK LED Description Amber lighting he adapter is connected to a 1000Mbps network and is in the state hich can communicate Green lighting hich can communicate Off T The adapter is
99. rs egisters failed ddi get iblock cookie ERROR The driver could not allocate Installed physical Unable to install interrupt routine interrupt resources memory may be Creation of a device file insufficient If this is 6 ddi_create_minor_node failed failed not the cause report The driver was loaded to this error to your 7 ATTACH failed the kernel successfully service provider OPEN failed ENOMEM The driver could not allocate CLOSE stream NULL esources Re activate the interface If this A different protocol is being 20 bind to 802 2 failed 4 message is still used displayed report to your service provider With With PWOO8GE4 PWOG8GE1 SEOX7 51 Duplex are invalid Please change PWOOSGE4 PWOGSGEl SEOX7GD2X GD2X only full duplex is the partner s duplex Full the other end is using half available Change the duplex mode duplex mode of the other end to Full The adapter was not Check the mounting 22 DL DETACH REQ No board ptr ecognized status of the adapter The driver could not allocate 23 fjgi param register error esources for the ndd parameter nm The driver could not allocate 24 fjgi board alloc mem failed esources The driver could not allocate 25 Error filling TX ring Installed physical transmit resources b 26 status block t alloced The driver could not allocate ees insufficient If this is 27 status block can t alloced h
100. s a member instance Q Configuration by the fjla init command will become ineffective after system reboot Use the etc opt FJSVla config file for permanent configuration 4 2 2 2 Inactivate a LinkAggregation Group fjla term This section explains the fjla term command for inactivating a LinkAggregation group Synopsis etc opt FJSVla bin fjla term aggregator interface aggregator interface Aggregator interface name including instance number If aggregator interface is not specified all LinkAggregation group will be inactivated 53 Chapter 4 LinkAggregation Feature Description Inactivate the LinkAggregation group Exit code 0 normal end 20 error end Example Inactivate the LinkAggregation group with aggregator interface fjgi0 etc opt FJSVla bin fjla term f jgiO FJ LinkAggregation stop Caution When aggregator interface is inactivated unplumb it cannot perform that f jla term if not specify aggregator interface name In this case please specify aggregator interface name 4 2 2 3 Display Status and Statistics fjla stat This section explains the fjla stat command for displaying the LinkAggregation status and statistic Synopsis etc opt FJSVla bin fjla stat aggregator interface i interval 1 aggregator interface Aggregator interface name including instance number i interval s Specify the display interval in seconds maximum 4294967295 The command display
101. s shown in the following examples that a setup of a f jgi conf file is needed Example When connection partner equipment is not supporting Auto Negotiation In this case please let mode of operation in agreement with self equipment and connection place partner equipment Although Auto Negotiation is used when it is necessary to make only a specific setting value into a different value from a default value for example when you want to set speed as 100Mbps in order to press down the CPU load by the network low When JumboFrame is used It is also possible to set up except fjgi conf For details please refer to 3 3 2 JumboFrame Setup The following table provides descriptions of the parameters used in the fjgi conf file to configure the GigabitEthernet interface When editing the fjgi conf file please review the Caution items below Parameter List Parameter Value Description Name fjgi Used to specify the driver name Used to specify the location of the device Parent See below node in the device tree Used to specify the address within the device unit address See below node First connection is attempted with AutoNegotiation A On If this fails the ete onnection is retried with AutoNegotiation A Sense toNegotiation A Off automatically PWOGSGEI uto Negotiation is enabled The interface c A This setting can be used only with PWOOSGEA il
102. s the statistics during the specified period However the first report shows statistics accumulated since the group is activated If aggregator interface is not specified information for all LinkAggregation groups will be displayed If nterva is not specified or 0 is specified the command only shows the first report Description Display the status and statistics of specified aggregator interface Exit code 0 normal end gt 0 error end 54 4 2 Configuration of the LinkAggregation Feature Display Format The following example shows that the status and statistics for a LinkAggregation group aggregator interface is fjgi0 etc opt FJSVla bin fjla stat fjgiO i 5 Oct 05 17 20 14 2004 Aggregator fjgiO Mode DA Status Ipkts lerrs Opkts Oerrs 0pkt Total fjgi0 fjgil 1512 7658459 0 71932472 0 7658459 0 71932472 0 100 100 0 0 0 0 0 0 0 0 0 0 0 0 Oct 05 17 20 14 2004 date and time Aggregator aggregator interface name Mode Destination MAC address distribution DA Destination IP address distribution DSA Source Destination IP address distribution Name Interface name Status up The interface is up and communicating down The interface is down or Link is down Ipkts The number of input packets lerrs The number of input error packets Opkts The number of output packets Oerrs The number of output error packets
103. tem is supported please replace the adapter Perform DDI_DETACH after LinkAggregation member DDI_DETACH busy because fjla is terminating the 41 interfaces cannot be active LinkAggregation detached function Installed physical memory may be LinkAggregation setup for insufficient If this is 42 can t la attach fjgiX Me fjgiX failed not the cause report this error to your service provider The internal group table RN Abnormal response was fjgi la mlist pAC pVAC member is may be corrupt Please 43 returned to the fjla stat wrong report this error to your command service provider There is a possibility of Report the error to your 44 Other messages driver internal bug or hardware failure service provider 62 This appears only when PRIMEPOWER250 450 secondary LAN port PWOO8GE5 PWOG8GE2 SEOX7GD1X PWOO8QG1 SEOX7GQ1X is used 1000Mbps The Machine Administration function included in Enhanced Support Facility may report messages listed in Table A 1 2 Table 1 2 Machine Administration Reported Messages Message Meaning Workaround fjgi device check fjgi hw deinit failed An error occurred during initialization of the adapter A driver may be the number of versions which is not supporting this adapter Please apply the indispensable patch indicated to Installation Guide possibility of hard Si
104. tion The contents of this manual may be revised without prior notice Contents Chapter 1 cde euet eroe rata dte ete Se dv als 1 1 1 Key Re atune siete s e Nota Me ei EA NN de SM 2 1 2 GigabitEth rnet card Specitrcations s A uae Es 3 2951 opecLbicablolsu de Midas Rh Bin dixisti aedis oe 3 2 2 Part Names and Features of 4 Chapter 2 Installing FUJITSU PCI GigabitEthernet 9 2 1 Installation of the GigabitEthernet 10 2 2 Identifying the GigabitEthernet 1 11 2 9 Cable Connetti Onisa torir era RE pede b eus 12 Chapter 3 Setting Contrguratiom esee MER DARE dls ue er eb Upon E we ale 21 3 1 Driver software Installations Ru bte Fiere he ur od peeled Heb PLI need 22 9220 Bnvrronment Setting oesi iezsceca baad tnd dda aed p A a bas tesi por Id 23 3 2 1 Contiguring the Hosthame Ele cole rk wate deel bad pase dak deans 23 3 1222 Hostname Definition pedes EREA 23 3 2 3 Netnask Value Definition bale
105. tyCluster Failover Mode Support Status IP address Supported MAC address Supported IP address MAC address Supported version 2 0 1 and later PRIMECLUSTER Failover Mode Support Status IP address Supported MAC address Supported version 4 1 10 and later IP address MAC address Supported version 4 1 10 and later 0 2 Cluster Environment Setup Procedure Set up the cluster environment in the same way as for an Ethernet driver i e hme driver Follow Setting up the Network in the SynfinityCluster manual or PRIMECLUSTER manual Note that the GigabitEthernet driver resource name is fjgi 11 Appendix C Using GigabitEthernet in a Cluster Environment 0 3 Notes SynfinityCluster 2 0 or later or PRIMECLUSTER 4 1 or later is required when using the FUJITSU PCI GigabitEthernet interface If an earlier version of cluster software is used GigabitEthernet cannot be used as the private LAN or for IP address fail over on a public LAN When using a FUJITSU PCI GigabitEthernet interface as a SynfinityCluster private LAN or as the PRIMECLUSTER cluster interconnect execute the following command before setting up the cluster example fjgi0 ifconfig fjgiO plumb A FUJITSU PCI GigabitEthernet interface used as a VLAN interface cannot be used for the private LAN or the cluster interconnect Appendix D PCI Slot Number and Device Name The appendix provides the
106. uration Information file example grep fjgi etc path_to_inst pci 83 2000 FJSV pwga 1 0 fjgi PRIMEPOWER250 450 secondary LAN port pciQ15 2000 FJSV pgtb 1 1 PWOO8GE5 PWOGSGE2 pciQ17 2000 FJSV pgsb 1 2 PW008GE4 PWOG8GE1 pciQ83 4000 pci 3 FUSV p4taQ1 3 fjgi pciQ83 4000 pciQ3 FJSV p4taQ1 1 4 PWoo8QG1 pciQ83 4000 pciQ3 FJSV p4taQ3 5 pciQ83 4000 pciQ3 FJSV p4ta 3 1 6 In the above example device node of device tree instance number driver name 1083 2000 FJSV pwgaQ1 1015 2000 FJSV pgtb 1 i017 2000 FJSV pgsb 1 1083 4000 pci 3 FJSV p4taQ1 1083 4000 pci 3 FJSV p4taQ1 1 1083 4000 pci 3 FJSV p4ta 3 1083 4000 pci 3 FJSV p4ta 3 1 o o ga a aa oa o The unit address is the number to the right of FJSV pwga pgtb or pgsbQ The unit addresses from the example are shown below PRIMEPOWER250 450 PWOO8GE5 PWOO8GE4 secondary LAN port PWOGSGE2 PWOG8GE1 name fjgi fjgi fjgi parent 083 2000 pciQ15 2000 pciQ17 2000 unit address 1 1 1 80 1 name 1083 2000 3 instance 3 is 1 unit address
107. ut FJSV pwga PRIMEPOWER250 450 secondary LAN port FJSV pgsb PWOO8GE4 PWOG8GE1 1000BASE SX card FJSV pgtb PWOOSGE5 PWOGSGE2 10 100 1000BASE T card FJSV p4ta PWOO8QG1 10 100 1000BASE T 4ports card 2 To determine the slot the GigabitEthernet PCI card is mounted in execute the following command more etc path to inst grep example more etc path to inst grep 083 2000 FJSV pwga 1 0 pciQ1f 0 pci 1 FUSV pgsb 4 1 pciQ1f 0 pci 1 FUSV pgtb 1 2 pci 83 4000 pci 3 FUSV p4ta 7 1083 4000 pci 3 FuUSV p4ta 7 1083 4000 pci 3 FUSV p4ta pci 83 4000 3 FJSV p4ta The logical bus address and the instance 1 3 1 1 4 3 b 3 1 6 fjgi umber shown in bold above are displayed The following table shows the logical bus address instance number and driver name for the example output above 39 Chapter 3 Setting Configuration Information Logical bus address Instance number Driver name pci 83 2000 FJSV pwgaQ1 0 f jg pciQ1f 0 pci 1 FJSV pgsb 4 1 f jg pciQ1f 0 pci 1 FJSV pgtbQ1 2 f jg 1083 4000 pciQ3 FJSV p4taQ1 3 f jg pci 83 4000 pciQ3 FJSV p4taQ1 1 4 pci 83 4000 pciQ3 FJSV p4ta 3 5 1083 4000 pciQ3
108. y correct fjla init Invalid mode The distributed mode 9 Me NN distributed mode 1 2 or number XX is incorrect 3 Specified interface is already being used by Specify interfaces that bas af other LinkAggregation fjla init An input instance are not in the other group or it does exist 10 already used by fjla or does LinkAggregation group This message is also not exist Also specify interfaces displayed when the command that exist on the system is executed by general users LinkAggregation has been 11 LinkAggregation stop There is no problem stopped normally i Zu Enter the correct fjla term is invalid The interface name XX is 12 aggregator interface name Appendix B On Board Diagnostics This appendix explains the on board diagnostics function Location of the LEDs 0086 4 0086 5 The following figures show the location of the LEDs Figure B 1 Figure B 2 1000Base SX PWOO8GE4 10 100 1000Base T PWOO8GE5 Meaning of the LEDs PWOO8GE4 PWO08GE5 1000M LED indicates the following operation status 1000M LED Description The adapter is connected to a 1000Mbps network and is in the state Green lighting which can communicate Off The adapter is not connected to a 1000Mbps network 100M LED indicates the following operation status PWOO8GE5 only 100M LED D

Fujitsu Update1 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents