FUJITSU PCI GigabitEthernet 3.
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.
Revision History Edition 01 02 03 ii Date 2003-2-20 2003-5-1 2004-1-8 Revised section (*1) (Added/Deleted/Altered) Details - - Appendix D PRIMEPOWER1/100 is added 3.4 Change the procedure 3.3.1 Some parameter explanations are added 3.5 Some procedures are added 3.6 VLAN information is added - 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.
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, abbreviated to Solaris OS.
iv
Contents Chapter 1 Product Outline ....................................................................... 1 1.1 Key Features ................................................................................. 2 1.2 GigabitEthernet card Specifications .......................................................... 3 1.2.1 Specifications ........................................................................... 3 1.2.2 Part Names and Features of Hardware ......................................................
Contents Appendix C Using GigabitEthernet in a Cluster Environment ....................................... 71 C.1 Cluster Environment Support................................................................. 71 C.2 Cluster Environment Setup Procedure......................................................... 71 C.3 Notes....................................................................................... 72 Appendix D PCI Slot Number and Device Name ......................................................
Chapter 1 Product Outline The following topics are described in this chapter.
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 link services defined by IEEE802.3. Table 1.1 GigabitEthernet function Main Function IEEE802.
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.
Chapter 1 Product Outline connection is not supported. ● When using 1000Mbps transfer rate with PW008GE5, PW0G8GE2, PRIMEPOWER250/450 secondary LAN port, SE0X7GD1X, PW008QG1 and SE0X7GQ1X, 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.
1.2 GigabitEthernet card Specifications Figure 1.1 1000Base-SX (PW008GE4) Figure 1.2 10/100/1000Base-T (PW008GE5) Figure 1.3 1000Base-SX (PW0G8GE1) Figure 1.
Chapter 1 Product Outline Figure 1.5 1000Base-SX * 2ports (SE0X7GD2X) 6 Figure 1.
1.2 GigabitEthernet card Specifications Figure 1.7 10/100/1000Base-T * 4ports (PW0G8GE1) Figure 1.
Chapter 2 Installing FUJITSU PCI GigabitEthernet Card This chapter describes the tasks necessary to install this card in the main unit.
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 -r" command at the OpenBoot prompt.
Chapter 2 Installing FUJITSU PCI GigabitEthernet Card 2.3 Cable Connection To connect the PW008GE4, PW0G8GE1 and SE0X7GD2X GigabitEthernet card to the network, use an optical fiber cable. To connect the PW008GE5, PW0G8GE2, PRIMEPOWR250/450 secondary LAN, PW008QG1, SE0X7GD1X and SE0x7GQ1X GigabitEthernet card to the network, use a CAT5E twisted pair cable (Enhanced Category 5). Figure 2.3.
2.3 Cable Connection Figure 2.3.
Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2.3.
2.3 Cable Connection Figure 2.3.
Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2.3.
2.3 Cable Connection Figure 2.3.
Chapter 2 Installing FUJITSU PCI GigabitEthernet Card Figure 2.3.
2.3 Cable Connection Figure 2.3.
Chapter 3 Setting Configuration Information This chapter describes how to set configuration information after installing the FUJITSU PCI GigabitEthernet interface.
Chapter 3 Setting Configuration Information 3.1 Driver Software Installation To make use of the FUJITSU PCI GigabitEthernet interface, Solaris OS version-specific driver packages must be installed from the attached CD-ROM. See the document "Installation Guide FUJITSU PCI GigabitEthernet 3.0 Update1" for the installation procedure.
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 Hostname file ● Hostname Definition ● Netmask Value Definition 3.2.1 Configuring the Hostname File 1.
Chapter 3 Setting Configuration Information Example /etc/hosts file: # IP Address 190.168.150.
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.
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).
3.3 Operation Mode Setup Parameter LinkSpeed_A FlowControl_A 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. Both (default) Indicating that both Full-Duplex and Half-Duplex are being supported. (This can only be set when AutoNegotiation_A=On.) Half Half-Duplex operation is allowed.
Chapter 3 Setting Configuration Information file.
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 PW008GE5 (10/100-/1000BASE-T), and disable Auto-Negotiation and connection speed is made into 100Mbps and Half-Duplex name="fjgi" parent="/pci@15,2000" unit-address="1" AutoNegotiation_A="Off" LinkSpeed_A="100" DuplexCapabilities_A="Half" ; example 2.
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.fjgi* (recommendation)] It recommends setting up JumboFrame by this method.
3.3 Operation Mode Setup 2. The MTU 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.
Chapter 3 Setting Configuration Information ● The parameters set in /etc/fjmtu.fjgi* and fjgi.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.
3.3 Operation Mode Setup ndd -set /dev/fjgi 'instance' value ndd ndd -set /dev/fjgi 'param1' -set /dev/fjgi 'param2' : ndd -set /dev/fjgi 'adv_autoneg_cap' ndd -set /dev/fjgi 'adv_autoneg_cap' value value (Instance number "value" of an applicable interface is specified.) (Change 1 of a setup) (Change 2 of a setup) : N (Once let Auto-Negotiation be a different value from the present condition.) M (Auto-Negotiation is returned to the original value.
Chapter 3 Setting Configuration Information parameter meaning Read only 0 : Link down 1 : Link up link_speed Read only 1000 : 1000Mbps 100 : 100Mbps 10 : 10Mbps link_mode Read only 0 : Half Duplex communication 1 : Full Duplex communication autonego Read only 0 : Auto-Negotiation is Off. 1 : Auto-Negotiation is On.
3.3 Operation Mode Setup parameter status meaning to Read only The link-partner has been set 10Mbps/FullDuplex by Auto-Negotiation. 0 : Invalid 1 : Valid to Read only The link-partner has been set 10Mbps/HalfDuplex by Auto-Negotiation. 0 : Invalid 1 : Valid Read only The link-partner has been set to 100Mbps/FullDuplex by Auto-Negotiation. 0 : Invalid 1 : Valid Read only The link-partner has been set to 100Mbps/HalfDuplex by Auto-Negotiation.
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.
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 PW008GE4/PW0G8GE1/SE0X7GD2X (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 PW008GE5/PW0G8GE2/SE0X7GD1X/PW008QG1/SE0X7GQ1X and PRIMEPOWER250/450 secondary LAN port is as follows.
Chapter 3 Setting Configuration Information The following example shows the current settings of a PW008GE5 card installed in a PRIMEPOWER600. {6} ok cd /pci@11,4000/FJSV,pgtb@5 {6} ok .
3.4 Discernment 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.
Chapter 3 Setting Configuration Information Logical bus address Instance number Driver name "/pci@83,2000/FJSV,pwga@1" 0 fjgi "/pci@1f,0/pci@1/FJSV,pgsb@4" 1 fjgi "/pci@1f,0/pci@1/FJSV,pgtb@1" 2 fjgi "/pci@83,4000/pci@3/FJSV,p4ta@1" 3 fjgi "/pci@83,4000/pci@3/FJSV,p4ta@1,1" 4 fjgi "/pci@83,4000/pci@3/FJSV,p4ta@3 5 fjgi "/pci@83,4000/pci@3/FJSV,p4ta@3,1 6 fjgi The logical bus address corresponds to a physical PCI slot number based on the Main Unit model number.
3.
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.
3.5 Network Installation # cd /cdrom/cdrom0/FJSVgid_3.0/ # ls FJSVgid* FJSVgid.us FJSVgidx.us FJSVgidr.us FJSVgidad.us # pkgadd -R mini_root_directory -d . # cd / 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. ● When PW008QG1 is used, please apply the following required patch to the install image in the install server.
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.
3.6 VLAN Interface Setup 3.6 VLAN Interface Setup This section provides information about IEEE 802.1Q TagVLAN interfaces. This section also provides instructions for setting up VLAN interfaces using the FUJITSU PCI GigabitEthernet interface. 3.6.1 IEEE 802.1Q TagVLAN Description The IEEE 802.1Q 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.
Chapter 3 Setting Configuration Information and belonging to VID 231, the following is used: VLAN Interface Number = (1000 * VID) + Physical Instance Number fjgi231003 = (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).
Chapter 4 LinkAggregation Feature This chapter outlines the LinkAggregation feature, and explains the settings required to use this feature.
Chapter 4 LinkAggregation Feature 4.1 About LinkAggregation Feature This section explains the LinkAggregation feature. - 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.
4.1 About LinkAggregation Feature - Data Distribution Mode: Table 4.1.2 explains data distribution modes 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.
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 ● 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.
4.2 Configuration of the LinkAggregation Feature Member-instance: fjgi0, fjgi2 Distribution mode: Source/Destination IP address distribution 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.
Chapter 4 LinkAggregation Feature ● The /etc/hostname.fjgiXX (XX: instance number) file is required for the aggregator-interface only (in the above example, /etc/hostname.fjgi1 is required). The LinkAggregation group defined in the configuration file is activated by rebooting the system. 4.2.2 Using the /etc/opt/FJSVla/bin/fjla Command The fjla command has the following functions.
4.2 Configuration of the LinkAggregation Feature # /etc/opt/FJSVla/bin/fjla init fjgi0 1:2 2 # fjgi0 FJ LinkAggregation now start. ● Before executing the command, the aggregator-interface must be already activated (the interface can be displayed by ifconfig -a), and the member instances must not be activated. ● The aggregator-interface must not be specified as a member instance. ● Configuration by the fjla init command will become ineffective after system reboot.
Chapter 4 LinkAggregation Feature - Description Inactivate the LinkAggregation group. - Exit code 0 : normal end. >0 : error end. - Example Inactivate the LinkAggregation group with aggregator-interface = fjgi0. # /etc/opt/FJSVla/bin/fjla term fjgi0 # FJ LinkAggregation stop. ● When aggregator-interface is inactivated (unplumb), it cannot perform that fjla term if not specify aggregator-interface name. In this case, please specify aggregator-interface name. 4.2.2.
4.
Chapter 4 LinkAggregation Feature 4.3 Notes This section explains notes for using the LinkAggregation function. ● LACP (dynamic LinkAggregation function) is not supported. ● Only TCP/IP connection is supported. ● Do not run FJVTS when LinkAggregation is being used. ● If VLAN interface with LinkAggregation function enabled is used, the following must be satisfied.
Chapter 5 Troubleshooting The following should be checked first to troubleshoot a problem. Is the driver software installed correctly? Execute "pkginfo -l FJSVgid" and “pkginfo –l 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/computing/server/unix/driver/ Refer to INSTALLATION GUIDE for details.
Appendix A Messages This chapter explains messages from the FUJITSU PCI GigabitEthernet driver A.1 Console Messages Console messages from the FUJITSU PCI GigabitEthernet driver are listed in Table A.1.1. Table A.1.1 Console Messages of the FUJITSU PCI GigabitEthernet driver No Message Cause Workaround 1 network connection down Link is down Check the cable connection and the switch configuration.
Appendix A Messages No Message Cause Workaround [E] Master: Communicating as Master Slave: Communicating as Slave 3 Illegal value for [ParameterName]. An error was found with a parameter defined in the fjgi.conf file. Check whether the value is set correctly in the file. Installed physical memory may be insufficient. If this is not the cause, report this error to your service provider. 4 soft state alloc failed. Driver internal resources cannot be obtained.
A.1 Console Messages No Message Cause Workaround Mapping of the adapter registers failed. 13 Unable to map adapter registers. 14 ddi_get_iblock_cookie-ERROR 15 Unable to install interrupt routine. 16 ddi_create_minor_node failed Creation of a device file failed. 17 ATTACH failed The driver was not loaded to the kernel successfully. 18 OPEN failed: ENOMEM 19 CLOSE: stream==NULL The driver could not allocate interrupt resources. Installed physical memory may be insufficient.
Appendix A Messages No 39 Message Cause Workaround Role not available for fiber adapters Role setting is no supported with PW008GE4/PW0G8GE1/SE0X7GD2X . Remove Role_A parameter in the fjgi.conf file. 40 Can't judge T or SX !! The adapter type cannot be recognized. Check whether the system is supported. Since there is possibility of hard abnormalities when the system is supported, please replace the adapter.
A.2 Command Messages Message Meaning Workaround An error occurred during initialization of the adapter. There is a possibility of hardware abnormalities. Please replace the adapter. pci_config_setup_failed The driver could not allocate sufficient PCI configuration space. There is a possibility of the resource shortage or hardware abnormalities. Please check the memory usage and adapter installation status. Autonegotiation_failed The Auto-Negotiation of 1000BASE-SX failed.
Appendix A Messages No 64 Message Cause Workaround 8 fjla init: "XX" does not exist. The interface "XX" does not exist. Specify interfaces that exist on the system. 9 fjla init: Invalid mode number ("XX"). The distributed mode "XX" is incorrect. Specify correct distributed mode (1, 2 or 3). 10 fjla init: An input instance already used by fjla or does not exist. Specified interface is already being used by other LinkAggregation group or it does not exist.
Appendix B On-Board Diagnostics This appendix explains the on-board diagnostics function. - Location of the LEDs(PW008GE4/PW008GE5) The following figures show the location of the LEDs. Figure B.1 1000Base-SX (PW008GE4) Figure B.2 10/100/1000Base-T (PW008GE5) - Meaning of the LEDs(PW008GE4/PW008GE5) 1000M LED indicates the following operation status. 1000M LED Description Green lighting The adapter is connected to a 1000Mbps network and is in the state which can communicate.
Appendix B On-Board Diagnostics 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(PW0G8GE1/SE0X7GD2X) The following figures show the location of the LEDs. Figure B.3 1000Base-SX (PW0G8GE1) Figure B.4 1000Base-SX * 2ports (SE0X7GD2X) - Meaning of the LEDs(PW0G8GE1/SE0X7GD2X) LINK LED indicates the following operation status.
- Location of the LEDs(PW0G8GE2) The following figures show the location of the LEDs. Figure B.5 10/100/1000Base-T (PW0G8GE2) - Meaning of the LEDs(PW0G8GE2) 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.
Appendix B On-Board Diagnostics - Location of the LEDs(SE0X7GD1X) The following figures show the location of the LEDs. Figure B.6 10/100/1000Base-T * 2ports (SE0X7GD1X) - Meaning of the LEDs(SE0X7GD1X) 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.
- Location of the LEDs(PW008QG1/SE0X7GQ1X) The following figures show the location of the LEDs. Figure B.7 1000Base-T * 4ports (PW008QG1) Figure B.8 1000Base-T * 4ports (SE0X7GQ1X) - Meaning of the LEDs(PW008QG1/SE0X7GQ1X) LINK LED(White LED in Figure B.7/8) indicates the following operation status. LINK LED Description Amber lighting The adapter is connected to a 1000Mbps network and is in the state which can communicate.
Appendix C 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.
Appendix C Using GigabitEthernet in a Cluster Environment C.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.
Appendix D PCI Slot Number and Device Name The appendix provides the PCI slot number and device name matrix for the following PRIMEPOWER/GP7000F models.
Appendix D PCI Slot Number and Device Name ● GP7000F Model200R Slot Number Device Name PCI#1 /pci@17,2000/*@1 PCI#2 /pci@16,2000/*@1 PCI#3 /pci@17,4000/*@2 PCI#4 /pci@16,4000/*@2 PCI#5 /pci@16,4000/*@4 PCI#6 /pci@16,4000/*@5 ● GP7000F Model400A/400R Slot Number Device Name 00-PCI#1 /pci@17,2000/*@1 00-PCI#2 /pci@16,2000/*@1 00-PCI#3 /pci@17,4000/*@2 00-PCI#4 /pci@16,4000/*@2 00-PCI#5 /pci@16,4000/*@4 00-PCI#6 /pci@16,4000/*@5 01-PCI#1 /pci@15,2000/*@1 01-PCI#2 /pci@14,2000/*@
Appendix D PCI Slot Number and Device Name Slot Number Device Name PCI#12 /pci@1c,4000/*@4 PCI#13 /pci@1c,2000/*@1 ● GP7000F Model600R Slot Number Device Name PCI#1 /pci@1f,4000/*@2 PCI#2 /pci@1f,2000/*@1 PCI#3 /pci@1c,4000/*@2 PCI#4 /pci@1e,4000/*@2 PCI#5 /pci@1e,4000/*@3 PCI#6 /pci@1e,4000/*@4 PCI#7 /pci@1c,2000/*@1 PCI#8 /pci@1d,4000/*@2 PCI#9 /pci@1d,4000/*@3 PCI#10 /pci@1d,4000/*@4 PCI#11 /pci@1d,2000/*@1 PCI#12 /pci@1e,2000/*@1 ● PRIMEPOWER 1 (1U rackmount) Slot Number
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 250 (2U rack-mount) Slot Number Device Name PCI#0 /pci@83,2000/*@2 PCI#1 /pci@83,4000/*@3 PCI#2 /pci@83,4000/*@4 ● PRIMEPOWER 250 (4U rack-mount) Slot Number Device Name PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,2000/*@2 PCI#2 /pci@80,4000/*@3 PCI#3 /pci@80,4000/*@4 PCI#4 /pci@80,4000/*@5 PCI#5 /pci@83,4000/*@3 ● PRIMEPOWER 400 (4U rackmount) Slot Number Device Name PCI#1 /pci@15,2000/*@1 PCI#2 /pci@15,4000/*@2 PCI#3 /pci@15,40
Appendix D PCI Slot Number and Device Name Slot Number 01-PCI#5 Device Name /pci@11,4000/*@5 ● PRIMEPOWER 450 (pedestal, 7U rack-mount) Slot Number Device Name PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,4000/*@3 PCI#2 /pci@80,4000/*@4 PCI#3 /pci@80,4000/*@5 PCI#4 /pci@82,2000/*@1 PCI#5 /pci@82,4000/*@3 PCI#6 /pci@82,4000/*@4 PCI#7 /pci@82,4000/*@5 PCI#8 /pci@83,4000/*@3 ● PRIMEPOWER 450 (4U rack-mount) Slot Number Device Name PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,2000/*@2 PCI#2 /pci@8
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 650 (rackmount) Board Number SB#0 PCI-BOX#0 Slot Number Device Name PCI#0 /pci@84,2000/*@1 PCI#1 /pci@84,4000/*@1 PCI#2 /pci@84,4000/*@2 PCI#3 /pci@84,4000/*@3 PCI#4 /pci@85,2000/*@1 PCI#5 /pci@85,4000/*@1 PCI#6 /pci@85,4000/*@2 PCI#7 /pci@85,4000/*@3 PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,4000/*@1 PCI#2 /pci@80,4000/*@2 PCI#3 /pci@80,4000/*@3 PCI#4 /pci@81,2000/*@1 PCI#5 /pci@81,4000/*@1 PCI#6 /pci@81,4000/*@2 PCI#7
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 850 (rackmount) Board Number SB#0 PCI-BOX#0 SB#1 PCI-BOX#1 Slot Number Device Name PCI#0 /pci@84,2000/*@1 PCI#1 /pci@84,4000/*@1 PCI#2 /pci@84,4000/*@2 PCI#3 /pci@84,4000/*@3 PCI#4 /pci@85,2000/*@1 PCI#5 /pci@85,4000/*@1 PCI#6 /pci@85,4000/*@2 PCI#7 /pci@85,4000/*@3 PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,4000/*@1 PCI#2 /pci@80,4000/*@2 PCI#3 /pci@80,4000/*@3 PCI#4 /pci@81,2000/*@1 PCI#5 /pci@81,4000/*@1 PCI#6 /pci@81,
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 900 (Physical Partitioning) Board Number; SB#0 PCI-BOX#0 (connected to SB#0) SB#1 PCI-BOX#0 (connected to SB#1) Slot Number Device Name PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,4000/*@2 PCI#2 /pci@81,2000/*@1 PCI#3 /pci@81,4000/*@2 PCI#4 /pci@81,4000/*@3 PCI#5 /pci@82,2000/*@1 PCI#6 /pci@82,4000/*@2 PCI#7 /pci@82,4000/*@3 PCI#0 /pci@84,2000/*@1 PCI#1 /pci@84,4000/*@2 PCI#2 /pci@84,4000/*@3 PCI#3 /pci@85,2000/*@1 PCI#4 /pci@
Appendix D PCI Slot Number and Device Name Board Number; PCI-BOX#0 (connected to SB#0) SB#1 PCI-BOX#0 (connected to SB#1) Slot Number Device Name PCI#0 /pci@c4,2000/*@1 PCI#1 /pci@c4,4000/*@2 PCI#2 /pci@c4,4000/*@3 PCI#3 /pci@c5,2000/*@1 PCI#4 /pci@c5,4000/*@2 PCI#5 /pci@c5,4000/*@3 PCI#6 /pci@c5,4000/*@4 PCI#7 /pci@e6,2000/*@1 PCI#8 /pci@e6,4000/*@2 PCI#9 /pci@e6,4000/*@3 PCI#0 /pci@88,2000/*@1 PCI#1 /pci@88,4000/*@2 PCI#2 /pci@89,2000/*@1 PCI#3 /pci@89,4000/*@2 PCI#4 /p
Appendix D PCI Slot Number and Device Name Board Number SB#2 SB#3 SB#4 SB#5 SB#6 SB#7 Slot Number Device Name PCI#0A /pci@90,2000/*@1 PCI#0B /pci@90,4000/*@2 PCI#1A /pci@91,2000/*@1 PCI#1B /pci@91,4000/*@2 PCI#3A /pci@93,2000/*@1 PCI#3B /pci@93,4000/*@2 PCI#0A /pci@98,2000/*@1 PCI#0B /pci@98,4000/*@2 PCI#1A /pci@99,2000/*@1 PCI#1B /pci@99,4000/*@2 PCI#3A /pci@9b,2000/*@1 PCI#3B /pci@9b,4000/*@2 PCI#0A /pci@a0,2000/*@1 PCI#0B /pci@a0,4000/*@2 PCI#1A /pci@a1,2000/*@1 PC
Appendix D PCI Slot Number and Device Name Board Number; PCI-BOX#0 (connected to SB#0) SB#1 PCI-BOX#0 (connected to SB#1) SB#2 PCI-BOX#0 (connected to SB#2) Slot Number Device Name PCI#0 /pci@84,2000/*@1 PCI#1 /pci@84,4000/*@2 PCI#2 /pci@84,4000/*@3 PCI#3 /pci@85,2000/*@1 PCI#4 /pci@85,4000/*@2 PCI#5 /pci@85,4000/*@3 PCI#6 /pci@85,4000/*@4 PCI#7 /pci@86,2000/*@1 PCI#8 /pci@86,4000/*@2 PCI#9 /pci@86,4000/*@3 PCI#0 /pci@88,2000/*@1 PCI#1 /pci@88,4000/*@2 PCI#2 /pci@89,2000/*@
Appendix D PCI Slot Number and Device Name Board Number; SB#3 PCI-BOX#0 (connected to SB#3) Slot Number Device Name PCI#0 /pci@98,2000/*@1 PCI#1 /pci@98,4000/*@2 PCI#2 /pci@99,2000/*@1 PCI#3 /pci@99,4000/*@2 PCI#4 /pci@99,4000/*@3 PCI#5 /pci@9a,2000/*@1 PCI#6 /pci@9a,4000/*@2 PCI#7 /pci@9a,4000/*@3 PCI#0 /pci@9c,2000/*@1 PCI#1 /pci@9c,4000/*@2 PCI#2 /pci@9c,4000/*@3 PCI#3 /pci@9d,2000/*@1 PCI#4 /pci@9d,4000/*@2 PCI#5 /pci@9d,4000/*@3 PCI#6 /pci@9d,4000/*@4 PCI#7 /pci@9e,
Appendix D PCI Slot Number and Device Name Board Number; PCI-BOX#0 (connected to SB#1) SB#2 PCI-BOX#0 (connected to SB#2) SB#3 PCI-BOX#0 (connected to SB#3) Slot Number Device Name PCI#0 /pci@cc,2000/*@1 PCI#1 /pci@cc,4000/*@2 PCI#2 /pci@cc,4000/*@3 PCI#3 /pci@cd,2000/*@1 PCI#4 /pci@cd,4000/*@2 PCI#5 /pci@cd,4000/*@3 PCI#6 /pci@cd,4000/*@4 PCI#7 /pci@ee,2000/*@1 PCI#8 /pci@ee,4000/*@2 PCI#9 /pci@ee,4000/*@3 PCI#0 /pci@90,2000/*@1 PCI#1 /pci@90,4000/*@2 PCI#2 /pci@91,2000/*@
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 2000,GP7000F Model2000 Board Number SB#0 SB#1 SB#2 SB#3 SB#4 SB#5 SB#6 SB#7 86 Slot Number Device Name PCI#0A /pci@80,2000/*@1 PCI#0B /pci@80,4000/*@2 PCI#1A /pci@81,2000/*@1 PCI#1B /pci@81,4000/*@2 PCI#3A /pci@83,2000/*@1 PCI#3B /pci@83,4000/*@2 PCI#0A /pci@84,2000/*@1 PCI#0B /pci@84,4000/*@2 PCI#1A /pci@85,2000/*@1 PCI#1B /pci@85,4000/*@2 PCI#3A /pci@87,2000/*@1 PCI#3B /pci@87,4000/*@2 PCI#0A /pci@88,2000/*@1 PC
Appendix D PCI Slot Number and Device Name Board Number SB#8 SB#9 SB#10 SB#11 SB#12 SB#13 SB#14 SB#15 Slot Number Device Name PCI#0A /pci@a0,2000/*@1 PCI#0B /pci@a0,4000/*@2 PCI#1A /pci@a1,2000/*@1 PCI#1B /pci@a1,4000/*@2 PCI#3A /pci@a3,2000/*@1 PCI#3B /pci@a3,4000/*@2 PCI#0A /pci@a4,2000/*@1 PCI#0B /pci@a4,4000/*@2 PCI#1A /pci@a5,2000/*@1 PCI#1B /pci@a5,4000/*@2 PCI#3A /pci@a7,2000/*@1 PCI#3B /pci@a7,4000/*@2 PCI#0A /pci@a8,2000/*@1 PCI#0B /pci@a8,4000/*@2 PCI#1A /p
Appendix D PCI Slot Number and Device Name Board Number SB#16 SB#17 SB#18 SB#19 SB#20 SB#21 SB#22 SB#23 88 Slot Number Device Name PCI#0A /pci@c0,2000/*@1 PCI#0B /pci@c0,4000/*@2 PCI#1A /pci@c1,2000/*@1 PCI#1B /pci@c1,4000/*@2 PCI#3A /pci@c3,2000/*@1 PCI#3B /pci@c3,4000/*@2 PCI#0A /pci@c4,2000/*@1 PCI#0B /pci@c4,4000/*@2 PCI#1A /pci@c5,2000/*@1 PCI#1B /pci@c5,4000/*@2 PCI#3A /pci@c7,2000/*@1 PCI#3B /pci@c7,4000/*@2 PCI#0A /pci@c8,2000/*@1 PCI#0B /pci@c8,4000/*@2 PCI#
Appendix D PCI Slot Number and Device Name Board Number SB#24 SB#25 SB#26 SB#27 SB#28 SB#29 SB#30 SB#31 Slot Number Device Name PCI#0A /pci@e0,2000/*@1 PCI#0B /pci@e0,4000/*@2 PCI#1A /pci@e1,2000/*@1 PCI#1B /pci@e1,4000/*@2 PCI#3A /pci@e3,2000/*@1 PCI#3B /pci@e3,4000/*@2 PCI#0A /pci@e4,2000/*@1 PCI#0B /pci@e4,4000/*@2 PCI#1A /pci@e5,2000/*@1 PCI#1B /pci@e5,4000/*@2 PCI#3A /pci@e7,2000/*@1 PCI#3B /pci@e7,4000/*@2 PCI#0A /pci@e8,2000/*@1 PCI#0B /pci@e8,4000/*@2 PCI#1A
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 2500/HPC2500 (Physical Partitioning) Board Number PCI-BOX#0 (connected to SB#0) PCI-BOX#1 (connected to SB#0) PCI-BOX#0 (connected to SB#1) PCI-BOX#1 (connected to SB#1) 90 Slot Number Device Name PCI#0 /pci@80,2000/*@1 PCI#1 /pci@80,4000/*@2 PCI#2 /pci@80,4000/*@3 PCI#3 /pci@81,2000/*@1 PCI#4 /pci@81,4000/*@2 PCI#5 /pci@81,4000/*@3 PCI#6 /pci@81,4000/*@4 PCI#7 /pci@82,2000/*@1 PCI#8 /pci@82,4000/*@2 PCI#9 /pci@82,4000/*@3
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#2) PCI-BOX#1 (connected to SB#2) PCI-BOX#0 (connected to SB#3) PCI-BOX#1 (connected to SB#3) Slot Number Device Name PCI#0 /pci@90,2000/*@1 PCI#1 /pci@90,4000/*@2 PCI#2 /pci@90,4000/*@3 PCI#3 /pci@91,2000/*@1 PCI#4 /pci@91,4000/*@2 PCI#5 /pci@91,4000/*@3 PCI#6 /pci@91,4000/*@4 PCI#7 /pci@92,2000/*@1 PCI#8 /pci@92,4000/*@2 PCI#9 /pci@92,4000/*@3 PCI#0 /pci@94,2000/*@1 PCI#1 /pci@94,4000/*@2 PCI#
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#4) PCI-BOX#1 (connected to SB#4) PCI-BOX#0 (connected to SB#5) PCI-BOX#1 (connected to SB#5) 92 Slot Number Device Name PCI#0 /pci@a0,2000/*@1 PCI#1 /pci@a0,4000/*@2 PCI#2 /pci@a0,4000/*@3 PCI#3 /pci@a1,2000/*@1 PCI#4 /pci@a1,4000/*@2 PCI#5 /pci@a1,4000/*@3 PCI#6 /pci@a1,4000/*@4 PCI#7 /pci@a2,2000/*@1 PCI#8 /pci@a2,4000/*@2 PCI#9 /pci@a2,4000/*@3 PCI#0 /pci@a4,2000/*@1 PCI#1 /pci@a4,4000/*@2
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#6) PCI-BOX#1 (connected to SB#6) PCI-BOX#0 (connected to SB#7) PCI-BOX#1 (connected to SB#7) Slot Number Device Name PCI#0 /pci@b0,2000/*@1 PCI#1 /pci@b0,4000/*@2 PCI#2 /pci@b0,4000/*@3 PCI#3 /pci@b1,2000/*@1 PCI#4 /pci@b1,4000/*@2 PCI#5 /pci@b1,4000/*@3 PCI#6 /pci@b1,4000/*@4 PCI#7 /pci@b2,2000/*@1 PCI#8 /pci@b2,4000/*@2 PCI#9 /pci@b2,4000/*@3 PCI#0 /pci@b4,2000/*@1 PCI#1 /pci@b4,4000/*@2 PCI#
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#8) PCI-BOX#1 (connected to SB#8) PCI-BOX#0 (connected to SB#9) PCI-BOX#1 (connected to SB#9) 94 Slot Number Device Name PCI#0 /pci@c0,2000/*@1 PCI#1 /pci@c0,4000/*@2 PCI#2 /pci@c0,4000/*@3 PCI#3 /pci@c1,2000/*@1 PCI#4 /pci@c1,4000/*@2 PCI#5 /pci@c1,4000/*@3 PCI#6 /pci@c1,4000/*@4 PCI#7 /pci@c2,2000/*@1 PCI#8 /pci@c2,4000/*@2 PCI#9 /pci@c2,4000/*@3 PCI#0 /pci@c4,2000/*@1 PCI#1 /pci@c4,4000/*@2
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#a) PCI-BOX#1 (connected to SB#a) PCI-BOX#0 (connected to SB#b) PCI-BOX#1 (connected to SB#b) Slot Number Device Name PCI#0 /pci@d0,2000/*@1 PCI#1 /pci@d0,4000/*@2 PCI#2 /pci@d0,4000/*@3 PCI#3 /pci@d1,2000/*@1 PCI#4 /pci@d1,4000/*@2 PCI#5 /pci@d1,4000/*@3 PCI#6 /pci@d1,4000/*@4 PCI#7 /pci@d2,2000/*@1 PCI#8 /pci@d2,4000/*@2 PCI#9 /pci@d2,4000/*@3 PCI#0 /pci@d4,2000/*@1 PCI#1 /pci@d4,4000/*@2 PCI#
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#c) PCI-BOX#1 (connected to SB#c) PCI-BOX#0 (connected to SB#d) PCI-BOX#1 (connected to SB#d) 96 Slot Number Device Name PCI#0 /pci@e0,2000/*@1 PCI#1 /pci@e0,4000/*@2 PCI#2 /pci@e0,4000/*@3 PCI#3 /pci@e1,2000/*@1 PCI#4 /pci@e1,4000/*@2 PCI#5 /pci@e1,4000/*@3 PCI#6 /pci@e1,4000/*@4 PCI#7 /pci@e2,2000/*@1 PCI#8 /pci@e2,4000/*@2 PCI#9 /pci@e2,4000/*@3 PCI#0 /pci@e4,2000/*@1 PCI#1 /pci@e4,4000/*@2
Appendix D PCI Slot Number and Device Name Board Number PCI-BOX#0 (connected to SB#e) PCI-BOX#1 (connected to SB#e) PCI-BOX#0 (connected to SB#f) PCI-BOX#1 (connected to SB#f) Slot Number Device Name PCI#0 /pci@f0,2000/*@1 PCI#1 /pci@f0,4000/*@2 PCI#2 /pci@f0,4000/*@3 PCI#3 /pci@f1,2000/*@1 PCI#4 /pci@f1,4000/*@2 PCI#5 /pci@f1,4000/*@3 PCI#6 /pci@f1,4000/*@4 PCI#7 /pci@f2,2000/*@1 PCI#8 /pci@f2,4000/*@2 PCI#9 /pci@f2,4000/*@3 PCI#0 /pci@f4,2000/*@1 PCI#1 /pci@f4,4000/*@2 PCI#
Appendix D PCI Slot Number and Device Name ● PRIMEPOWER 2500 (Extended Partitioning) Board Number; PCI-BOX#0 (connected to SB#0) PCI-BOX#0 (connected to SB#1) PCI-BOX#0 (connected to SB#2) PCI-BOX#0 (connected to SB#3) 98 Slot Number Device Name PCI#0 /pci@84,2000/*@1 PCI#1 /pci@84,4000/*@2 PCI#2 /pci@84,4000/*@3 PCI#3 /pci@85,2000/*@1 PCI#4 /pci@85,4000/*@2 PCI#5 /pci@85,4000/*@3 PCI#6 /pci@85,4000/*@4 PCI#7 /pci@86,2000/*@1 PCI#8 /pci@86,4000/*@2 PCI#9 /pci@86,4000/*@3 PCI#0
Appendix D PCI Slot Number and Device Name Board Number; PCI-BOX#0 (connected to SB#4) PCI-BOX#0 (connected to SB#5) PCI-BOX#0 (connected to SB#6) PCI-BOX#0 (connected to SB#7) Slot Number Device Name PCI#0 /pci@a4,2000/*@1 PCI#1 /pci@a4,4000/*@2 PCI#2 /pci@a4,4000/*@3 PCI#3 /pci@a5,2000/*@1 PCI#4 /pci@a5,4000/*@2 PCI#5 /pci@a5,4000/*@3 PCI#6 /pci@a5,4000/*@4 PCI#7 /pci@a6,2000/*@1 PCI#8 /pci@a6,4000/*@2 PCI#9 /pci@a6,4000/*@3 PCI#0 /pci@ac,2000/*@1 PCI#1 /pci@ac,4000/*@2 PCI
Appendix D PCI Slot Number and Device Name Board Number; PCI-BOX#0 (connected to SB#8) PCI-BOX#0 (connected to SB#9) PCI-BOX#0 (connected to SB#a) PCI-BOX#0 (connected to SB#b) 100 Slot Number Device Name PCI#0 /pci@c0,2000/*@1 PCI#1 /pci@c0,4000/*@2 PCI#2 /pci@c0,4000/*@3 PCI#3 /pci@c1,2000/*@1 PCI#4 /pci@c1,4000/*@2 PCI#5 /pci@c1,4000/*@3 PCI#6 /pci@c1,4000/*@4 PCI#7 /pci@c2,2000/*@1 PCI#8 /pci@c2,4000/*@2 PCI#9 /pci@c2,4000/*@3 PCI#0 /pci@c8,2000/*@1 PCI#1 /pci@c8,4000/*@2
Appendix D PCI Slot Number and Device Name Board Number; Slot Number PCI-BOX#0 (connected to SB#c) PCI-BOX#0 (connected to SB#d) PCI-BOX#0 (connected to SB#e) PCI-BOX#0 (connected to SB#f) Device Name PCI#0 /pci@e0,2000/*@1 PCI#1 /pci@e0,4000/*@2 PCI#2 /pci@e0,4000/*@3 PCI#3 /pci@e1,2000/*@1 PCI#4 /pci@e1,4000/*@2 PCI#5 /pci@e1,4000/*@3 PCI#6 /pci@e1,4000/*@4 PCI#7 /pci@e2,2000/*@1 PCI#8 /pci@e2,4000/*@2 PCI#9 /pci@e2,4000/*@3 PCI#0 /pci@e8,2000/*@1 PCI#1 /pci@e8,4000/*@2 PCI
Appendix D PCI Slot Number and Device Name Board Number Slot Number PCI#1 IOBoat(Ex) Basic Slot PCI PCI#2 IOBoat(X) PCI#2 IOBoat(Ex) Basic Slot PCI PCI#3 IOBoat(X) PCI#3 IOBoat(Ex) Basic Slot PCI PCI#4 IOBoat(X) PCI#4 IOBoat(Ex) 102 Device Name PCI#1-PCIX3 /pci@0,600000/pci@0/pci@9/pci@0/pci@9/pci@0/****@4 PCI#1-PCIX4 /pci@0,600000/pci@0/pci@9/pci@0/pci@9/pci@0,1/****@4 PCI#1-PCIE1 /pci@0,600000/pci@0/pci@9/pci@0/pci@1/pci@0/pci@0/****@0 PCI#1-PCIE2 /pci@0,600000/pci@0/pci@9/pci@0/p
Appendix D PCI Slot Number and Device Name Board Number Logical System Board #1 Basic Slot Slot Number PCI PCI#1 IOBoat(X) PCI#1 IOBoat(Ex) Basic Slot PCI PCI#2 IOBoat(X) PCI#2 IOBoat(Ex) Basic Slot PCI PCI#3 IOBoat(X) PCI#3 IOBoat(Ex) Basic Slot PCI PCI#4 IOBoat(X) Device Name PCI#4-PCIE6 /pci@3,700000/pci@0/pci@9/pci@0/pci@9/****@0 PCI#0 /pci@10,600000/pci@0/pci@8/pci@0,1/****@1 PCI#1 /pci@10,600000/pci@0/pci@9/****@0 PCI#1-PCIX1 /pci@10,600000/pci@0/pci@9/pci@0/pci@1/pci@0/****@4
Appendix D PCI Slot Number and Device Name Board Number Slot Number PCI#4 IOBoat(Ex) Device Name PCI#4-PCIX3 /pci@13,700000/pci@0/pci@9/pci@0/****@4 PCI#4-PCIX4 /pci@13,700000/pci@0/pci@9/pci@0,1/****@4 PCI#4-PCIE1 /pci@13,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#4-PCIE2 /pci@13,700000/pci@0/pci@1/pci@0/pci@1/****@0 PCI#4-PCIE3 /pci@13,700000/pci@0/pci@1/pci@0/pci@9/****@0 PCI#4-PCIE4 /pci@13,700000/pci@0/pci@9/pci@0/pci@0/****@0 PCI#4-PCIE5 /pci@13,700000/pci@0/pci@9/pci@0/pci@1/****@0
Appendix D PCI Slot Number and Device Name Board Number Slot Number PCI#5 IOBoat(Ex) Basic Slot PCI Basic Slot PCI PCI#7 IOBoat(X) PCI#7 IOBoat(Ex) Logical System Board #1 Basic Slot PCI Basic Slot PCI PCI#1 IOBoat(X) PCI#1 IOBoat(Ex) Basic Slot PCI Basic Slot PCI PCI#3 IOBoat(X) Device Name PCI#5-PCIX5 /pci@5,700000/pci@0/pci@8/pci@0/****@4 PCI#5-PCIX6 /pci@5,700000/pci@0/pci@8/pci@0,1/****@4 PCI#5-PCIX3 /pci@5,700000/pci@0/pci@9/pci@0/****@4 PCI#5-PCIX4 /pci@5,700000/pci@0/pc
Appendix D PCI Slot Number and Device Name Board Number Slot Number PCI#3 IOBoat(Ex) Basic Slot PCI Basic Slot PCI PCI#5 IOBoat(X) PCI#5 IOBoat(Ex) Basic Slot PCI Basic Slot PCI PCI#7 IOBoat(X) PCI#7 IOBoat(Ex) 106 Device Name PCI#3-PCIX6 /pci@13,700000/pci@0/pci@8/pci@0,1/****@4 PCI#3-PCIX3 /pci@13,700000/pci@0/pci@9/pci@0/****@4 PCI#3-PCIX4 /pci@13,700000/pci@0/pci@9/pci@0,1/****@4 PCI#3-PCIE1 /pci@13,700000/pci@0/pci@1/pci@0/pci@0/****@0 PCI#3-PCIE2 /pci@13,700000/pci@0/pci@1/p
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 (PW008GE4/PW0G8GE1/SE0X7GD2X) Product Name Connection JumboFrame Note FUJITSU SH4000, SB7300, SR8800, SH4322G OK OK with SH4322G only With SB7300, turn off the Autonegotiation function of the switch.
Appendix E Available Switches Table E.4 IEEE802.
