Sun™ GigaSwift Ethernet Adapter Installation and User’s Guide Sun Microsystems, Inc. www.sun.com Part No. 817-4341-10 August 2004, Revision A Submit comments about this document at: http://www.sun.
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Contents Preface 1. xix Sun GigaSwift Ethernet Adapter Overview Hardware Overview 1 Sun GigaSwift Ethernet MMF Adapter LED Displays on the MMF Adapter LED Displays on the UTP Adapter 3 Hardware and Software Requirements 4 Product Features 1 2 Sun GigaSwift Ethernet UTP Adapter Patch Requirements 1 2 4 5 Key Protocols and Interfaces Diagnostic Support 5 6 Support for Solaris 9 x86 Operating System 2.
Setting the local-mac-address? Variable Rebooting the System 14 Using the Installation Script ▼ 14 To Install the Software Using the Installation Script Verifying the Software Installation Network Configuration 15 21 Configuring the Network Host Files 3.
Setting Parameters Using the ce.conf File ▼ To Set Driver Parameters Using a ce.conf File Usability Enhancements to the Driver Reporting the Link Partner Capabilities Configuring VLANs 63 Overview of VLANs 63 Configuring VLANs 66 ▼ A. To Configure Static VLANs Installing the Software Manually B. 55 69 69 To Install the Driver Software Manually Verifying Patches 54 67 Installing the Driver Software Manually ▼ 51 52 GigaSwift Ethernet Driver Operating Statistics 5.
Configuring Driver Parameters Configuring VLANs C. Specifications Connectors 87 89 89 Performance Specifications Physical Characteristics Power Requirements D. 87 91 91 91 Diagnostic Software and Troubleshooting Issues SunVTS Diagnostic Software 93 Using the SunVTS netlbtest 94 To Use the netlbtest 94 ▼ Using the OpenBoot PROM FCode Self-Test ▼ 95 To Run the FCode Self-Test Diagnostic Troubleshooting Issues 93 95 98 Known Incompatibilities With Pre-IEEE 802.
Figures FIGURE 1-1 Sun GigaSwift Ethernet MMF Adapter 2 FIGURE 1-2 Sun GigaSwift Ethernet UTP Adapter 3 FIGURE 5-2 Ethernet Tag Header Format FIGURE C-1 Sun GigaSwift Ethernet MMF Adapter Connector 89 FIGURE C-2 Sun GigaSwift Ethernet UTP Adapter Connector 90 66 vii
viii Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
Tables TABLE 1-1 Front Panel Display LEDs for the MMF Adapter 2 TABLE 1-2 Front Panel Display LEDs for the UTP Adapter 3 TABLE 3-1 Device Link Parameters TABLE 3-2 link-clock Capabilities for Link Up TABLE 4-1 ce Driver Parameter, Status, and Descriptions TABLE 4-2 Operational Mode Parameters TABLE 4-3 Read-Write Flow Control Keyword Descriptions TABLE 4-4 Forced Mode Parameters TABLE 4-5 Parameters Defining enable_ipg0 and ipg0 TABLE 4-6 Read-Write Interpacket Gap Parameter Values and
TABLE C-1 SC Connector Link Characteristics (IEEE P802.
Declaration of Conformity Compliance Model Number: GCS Product Family Name: Sun GigaSwift Copper Ethernet PCI Adapter Card (X4050A) EMC USA - FCC Class A This equipment complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1) This equipment may not cause harmful interference. 2) This equipment must accept any interference that may cause undesired operation.
EN61000-4-6 3V EN61000-4-8 1 A/m EN61000-4-11 Pass EN61000-3-2 Pass EN61000-3-3 Pass Safety This equipment complies with the following requirements of Low Voltage Directive 73/23/EEC: EC Type Examination Certificates: EN 60950:2000, 3rd Edition TÜV Rheinland Certificate No. IEC 60950:2000, 3rd Edition, CB Scheme Certificate No. Evaluated to all CB Countries UL 60950, 3rd Edition, CSA C22.2 No. 60950-00 File: Vol. Sec.
Declaration of Conformity Compliance Model Number: GFS Product Family Name: Sun GigaSwift Fiber Ethernet PCI Adapter Card (X4051A) EMC USA - FCC Class A This equipment complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1) This equipment may not cause harmful interference. 2) This equipment must accept any interference that may cause undesired operation.
EN61000-4-11 Pass EN61000-3-2 Pass EN61000-3-3 Pass Safety This equipment complies with the following requirements of Low Voltage Directive 73/23/EEC: EC Type Examination Certificates: EN 60950:2000, 3rd Edition TÜV Rheinland Certificate No. IEC 60950:2000, 3rd Edition, CB Scheme Certificate No. Evaluated to all CB Countries UL 60950, 3rd Edition, CSA C22.2 No. 60950-00 File: Vol. Sec. Supplementary Information: This product was tested and complies with all the requirements for the CE Mark.
Regulatory Compliance Statements Your Sun product is marked to indicate its compliance class: • • • • Federal Communications Commission (FCC) — USA Industry Canada Equipment Standard for Digital Equipment (ICES-003) — Canada Voluntary Control Council for Interference (VCCI) — Japan Bureau of Standards Metrology and Inspection (BSMI) — Taiwan Please read the appropriate section that corresponds to the marking on your Sun product before attempting to install the product.
ICES-003 Class A Notice - Avis NMB-003, Classe A This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada. ICES-003 Class B Notice - Avis NMB-003, Classe B This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada. Graphic showing the Japanese VCCI-A regulatory statement. Graphic showing the Japanese VCCI-B regulatory statement.
BSMI Class A Notice The following statement is applicable to products shipped to Taiwan and marked as Class A on the product compliance label. Graphic showing the BSMI Class A Notice for products shipped to Taiwan. GOST-R Certification Mark Graphic showing the GOST-R Certification Mark.
x Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
Preface The Sun GigaSwift Ethernet Adapter Installation and User’s Guide provides installation instructions for both the Sun GigaSwift Ethernet UTP adapter and the Sun GigaSwift Ethernet MMF adapter. This manual also describes how to configure the driver software. These instructions are designed for enterprise system administrators with experience installing network hardware and software. How This Book Is Organized Chapter 1 provides a description of the adapter, including hardware and software.
Appendix C lists the specifications for the Sun GigaSwift Ethernet adapter. Appendix D provides an overview of the SunVTS diagnostic application and instructions for testing the adapter using the onboard FCode selftest. There is also a section outlining some common troubleshooting issues. Using UNIX Commands This document might not contain information on basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices.
Shell Prompts Shell Prompt C shell machine_name% C shell superuser machine_name# Bourne shell and Korn shell $ Bourne shell and Korn shell superuser # Related Documentation Application Title PCI Adapter Installation Your system installation or service manual Storage Device Installation Your storage device installation or service manual Dynamic Reconfiguration Installation Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Dynamic Reconfiguration User’s Guide Diagnostic Software SunVTS User
Third-Party Web Sites Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources.
CHAPTER 1 Sun GigaSwift Ethernet Adapter Overview This chapter provides a description of the Sun GigaSwift Ethernet UTP and MMF adapter hardware and software.
LINK FDX TX RX FIGURE 1-1 Sun GigaSwift Ethernet MMF Adapter LED Displays on the MMF Adapter Four LEDs are displayed on the front panel of Sun GigaSwift Ethernet MMF adapter. They are labeled on the front panel as shown in TABLE 1-1. TABLE 1-1 Front Panel Display LEDs for the MMF Adapter Label Meaning if Lit Color Source LINK Link is up. Green* MAC FDX Link is in full-duplex mode. Green MAC TX Link is transmitting. Green MAC RX Link is receiving.
1000/100/10 BASE - TX FIGURE 1-2 AC T Sun GigaSwift Ethernet UTP Adapter LED Displays on the UTP Adapter Two LEDs are displayed on the front panel of the Sun GigaSwift Ethernet UTP adapter. They are labeled on the front panel as shown in TABLE 1-2. TABLE 1-2 Front Panel Display LEDs for the UTP Adapter Label Meaning if On/Active Color Source LINK Gigabit link is up. Green PHY ACT Link is transmitting or receiving data.
Hardware and Software Requirements Before using the Sun GigaSwift Ethernet adapter, make sure your system meets the following hardware and software requirements: Hardware and Software Requirements Hardware Sun Ultra™ 60, 80 Sun Enterprise™ 280, 420, 3000/3500, 4000/4500, 5000/5500, 6000/6500/6800, 15000 Netra™ 20, 100 T1, 200 T1, 240, 1280 (lw8T8), 1405 Sun Fire™ 4900, 4800, 280R, v1280, v880, V480, v440, v240, v20Z* Sun Blade™ 1000, 100 OpenBoot PROM** Revision 4.
The Solaris 8 2/02 release includes Patch-ID Number 111883-05. Subsequent versions of the Solaris operating system may include the correct version.
■ ■ ■ ■ ■ ■ ■ ■ PCI Local Bus Rev 2.2-compliant (6.6-inch x 2.5-inch short card) IPv4 and IPv6 support Load balancing for RX packets among multiple CPUs Jumbo frames enables the Ethernet interfaces to send and receive packets of up to 9216 bytes IEEE 802.1Q VLAN IEEE 802.1P/802.
CHAPTER 2 Installing the Adapter This chapter describes how to install the adapter in your system and verify that it has been installed correctly. It then describes how to install the driver software using the automated script. Finally, this chapter describes how to edit the network host files after installing the adapter on your system.
Note – Dynamic reconfiguration (DR) is a system-specific feature. If you have a Sun Enterprise system that supports DR, refer to the Sun Enterprise Dynamic Reconfiguration User’s Guide and your system’s documentation for further information about DR. Installing the Adapter Without Dynamic Reconfiguration ▼ To Install the Adapter Note – The following instructions describe the basic tasks required to install the adapter.
Caution – Do not use excessive force when installing the adapter into the PCI slot. You might damage the adapter’s PCI connector. If the adapter does not seat properly when you apply even pressure, remove the adapter and carefully reinstall it. 9. Secure the adapter to the PCI slot using the screw you removed in Step 6. 10. Detach the wrist strap and close the system unit. 11. Connect the Ethernet cables. a. Connect one end of the Ethernet cable to the port on the card. b.
2. List the network devices on your system. ok show-nets You should see the full path name of the network devices, similar to the example below. In this example, the network@0 and the network@1 devices are the Sun GigaSwift Ethernet adapter, and the network@2 is the onboard Ethernet device.
4. View the .properties file for a list of device properties. The .properties command displays the specific information about the installed adapter. If you are using the Sun GigaSwift Ethernet MMF adapter, your output will be similar to the following. ok cd /pci@8,700000/network@2 ok .
If you are using the Sun GigaSwift Ethernet UTP adapter, your .properties output will be similar to the following. ok cd /pci@8,700000/network@3 ok .
Note – If you are going to set the local-mac-address? variable, note the local MAC address of your device at this time. See “Setting the local-mac-address? Variable” on page 13 for more information. 5. Type the following when you finish looking at the .properties values: ok device-end Setting the local-mac-address? Variable Note – Enabling the local-mac-address? variable is only required if you boot from the network.
1. List the network devices on your system. ok show-nets a) /pci@8,600000/network@1 b) /pci@8,700000/network@5,1 q) NO SELECTION Enter Selection, q to quit:q 2. Set the Sun GigaSwift Ethernet adapter device to be your default boot device. ok setenv boot-device /pci@8,600000/network@1 Note that the command shown in this example sets your boot device to be port 0 on the network portion of the card.
▼ To Install the Software Using the Installation Script 1. At the system console, become superuser (root). 2. Insert the Sun GigaSwift Ethernet Adapter CD into a CD-ROM drive that is connected to your system. ■ If your system is running Sun Enterprise Volume Manager, it should automatically mount the CD-ROM to the /cdrom/cdrom0 directory.
4. Execute the installation script: # ./install The script displays a menu of products: Product Installation 1 2 3 4 - Dual Gigabit Ethernet Dual SCSI/P Adapter GigaSwift Ethernet Adapter (copper/fiber) GigaSwift Ethernet Compact PCI Adapter Quad GigaSwift Ethernet Adapter Please select the product to install: 2 5. Select 2, the Sun GigaSwift Ethernet adapter, and answer the questions, if required, in the installation script.
CODE EXAMPLE 2-1 Script Output for SPARC Systems When Requirements Are Met *** Checking for correct version of GigaSwift Ethernet Driver Packages... *** Checking for correct version of GigaSwift Ethernet Driver Patches... *** Checking for correct version of VLAN Utility Driver Packages.. *** Checking for correct version of VLAN Utility Driver Patches... The CE/VLAN driver(s) installed on this system for: Dual GigaSwift Ethernet Adapter Driver meets or exceeds the required package or patch version.
CODE EXAMPLE 2-2 Script Output for x86 Systems When Requirements Are Met Dual GigaSwift Ethernet Adapter Driver meets or exceeds the required package or patch version. No changes to the system are required - exiting. Example 3: Updates Required The following is an example of an installation script output, if the packages are found and need updating by patching. Note – The following two examples are from a SPARC system.
CODE EXAMPLE 2-3 Script Output When Packages Require Patches (Continued) *** Installing patch 112817-16 for Solaris 9... Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 112817-16 has been successfully installed. See /var/sadm/patch/112817-16/log for details Patch packages installed: SUNWcea SUNWceax SUNWced SUNWcedu SUNWcedu *** Installing patch 114600-02 for Solaris 9... Checking installed patches...
Example 4: Packages Missing Following is an example of an installation script output if the package(s) are not found: CODE EXAMPLE 2-4 Script Output When Packages Are Not Found Product Installation 1 2 3 4 - Dual Gigabit Ethernet Dual SCSI/P Adapter GigaSwift Ethernet Adapter (copper/fiber) GigaSwift Ethernet Compact PCI Adapter Quad GigaSwift Ethernet Adapter Please select the product to install: 2 GigaSwift Ethernet Adapter Driver for sparc Installation. Copyright 2004 Sun Microsystems, Inc.
CODE EXAMPLE 2-4 Script Output When Packages Are Not Found (Continued) Installation of was successful. Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Installation of was successful. Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Installation of was successful. Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
● Use the modinfo command to verify that you have the current driver (v1.136 or later) installed. If you type grep CE, using uppercase letters, you will get only the specific driver information: # modinfo |grep CE 84 7821c000 4f9a6 75 1 ce (CE Ethernet Driver v1.136) If you type grep ce, using lowercase letters, you will still get the driver version information, but you will also get several lines of additional information. Your output will be similar to the following.
1. At the command line, use the grep command to search the /etc/path_to_inst file for ce interfaces. # grep ce /etc/path_to_inst "/pci@8,600000/network@1" 0 "ce" In the example above, the device instance is from a Sun GigaSwift Ethernet adapter. For clarity, the instance number is in bold italics. 2. Use the ifconfig command to set up the adapter’s ce interface. Use the ifconfig command to assign an IP address to the network interface.
3. Create an appropriate entry in the /etc/hosts file for each active ce interface. For example: # cat /etc/hosts # # Internet host table # 127.0.0.1 localhost 129.144.10.57 zardoz loghost 129.144.11.
CHAPTER 3 Network Configuration This chapter describes how to edit the network host files after the adapter has been installed on your system.
Use the ifconfig command to assign an IP address to the network interface. Type the following at the command line, replacing ip-address with the adapter’s IP address: # ifconfig ce0 plumb ip-address up Refer to the ifconfig(1M) man page and the Solaris documentation for more information. ■ If you want a setup that remains the same after you reboot, create an /etc/hostname.cenumber file, where number corresponds to the instance number of the ce interface you plan to use.
Setting Up a GigaSwift Ethernet Network on a Diskless Client System Before you can boot and operate a diskless client system across a gigabit Ethernet network, you must first install the GigaSwift Ethernet software packages into the root directory of the diskless client. You can find the GigaSwift Ethernet software packages on the Sun GigaSwift Ethernet Driver CD.
4. Eject the Sun GigaSwift Ethernet Driver CD from the CD-ROM drive. 5. Create a hostname.cenumber file in the diskless client’s root directory. You will need to create an /export/root/client-name/etc/hostname.cenumber file for the GigaSwift Ethernet interface. See “Configuring the Network Host Files” on page 25 for instructions. 6. Edit the hosts file in the diskless client’s root directory. Edit the /export/root/client-name/etc/hosts file to include the IP address of the GigaSwift Ethernet interface.
▼ To Install the Solaris Operating System Over a GigaSwift Ethernet Network 1. Prepare the install server and client system to install the Solaris Operating System over the network. The Solaris Advanced Installation Guide describes how to create the install server and set up the client systems. Note – If you want to install the client system over a network that is not part of the same subnet, you must also create a boot server.
4. On the install server, install the GigaSwift Ethernet software to the client’s root directory, as determined in Step 2. Replace root-directory with the location of the client’s root directory. # cd /cdrom/cdrom0/GigaSwiftEthernet/Packages # ls SUNWce* SUNWcea SUNWceax SUNWced SUNWcedu SUNWcem # pkgadd -R root-directory/Solaris_2.7/Tools/Boot -d .
8. At the ok prompt, boot the client system using the full device path of the Gigabit Ethernet device. The following examples show the options available: ■ Booting in autonegotiated mode: ok boot:link-param, -v ■ Booting in autonegotiated verbose mode at 1000 Mbps half-duplex: ok boot /pci@1f,4000/network@4:speed=1000,duplex=half,link-clock=auto Note – link-clock must be set to auto.
10. After installing the Solaris Operating System, install the Sun GigaSwift Ethernet software on the client system. The software installed in Step 4 was required to boot the client system over the GigaSwift Ethernet interface. You now need to install the software in order for the operating system to use the client’s GigaSwift Ethernet interfaces in normal operation. Before installing the Sun GigaSwift Ethernet software, make sure that the client system does not already have the software installed.
the device and its link partner. Attempting to link-up with autonegotiation disabled requires knowledge of the current capabilities at which both the device and its link partner are configured. The structure of the boot net command line that includes device parameters is as follows: ok boot device-path:speed=s,duplex=d,link-clock=c,promiscuous, Where: s = 1000, 100, 10, auto d = half, full, auto c = master, slave, auto Note – Refer to the IEEE 802.
TABLE 3-1 Device Link Parameters Device Parameters speed 100 duplex Device Link Capability link-clock autoneg 1000fdx 1000hdx 100fdx 100hdx 10fdx 10hdx 1 0 0 1 1 1 1 0 0 1 1 1 0 0 0 0 0 1 N/A auto 100 10 full N/A 0 10 half N/A 0 0 0 0 0 0 10 auto N/A 1 0 0 0 0 1 1 0 0 0 0 1 10 auto full 1 1 0 1 0 1 auto half 1 0 1 0 1 0 auto auto 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 auto auto auto TABLE 3-2 link-clock Capabil
Note – The link partner must be configured as link-clock slave. To attempt to autonegotiate the link while advertising 1000 Mbps full- and halfduplex, and link-clock auto capability to the link partner: # boot net:speed=1000,duplex=auto,link-clock=auto, Note – Link partner must autonegotiate in order to link-up at 1000 Mbps.
36 Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
CHAPTER 4 Configuring Driver Parameters This chapter describes how to configure the driver parameters used by the Sun GigaSwift Ethernet adapter.
GigaSwift Ethernet Driver Parameter Values and Definitions TABLE 4-1 describes the parameters and settings for the ce device driver.
TABLE 4-1 ce Driver Parameter, Status, and Descriptions (Continued) Parameter Status Description infinite-burst Read and write PCI interface parameter disable-64bit Read and write PCI interface parameter accept-jumbo Read and write Enable jumbo frames Operational Mode Parameters The following parameters determine the transmit and receive speed and duplex.
Note – If a parameter’s initial setting is 0, it cannot be changed. If you try to change the setting, it will revert back to 0. If all these parameters are set to 1, autonegotiation uses the highest speed possible. If all these parameters are set to 0, you receive the following error message: NOTICE: Last setting will leave ce0 with no link capabilities. WARNING: ce0: Restoring previous setting.
Gigabit Link Clock Mastership Controls The concept of link clock mastership was introduced with gigabit twisted-pair technology. One side of the link is the master that provides the link clock and the other side is the slave that uses the link clock. Once this relationship is established, the link is up, and data can be communicated. Two physical layer parameters control whether your side is the master or the slave, or whether mastership is negotiated with the link partner.
If enable_ipg0 is disabled, the value of ipg0 is ignored and no additional delay is set. Only the delays set by ipg1 and ipg2 will be used. Disable enable_ipg0 if other systems keep sending a large number of back-to-back packets. Systems that have enable_ipg0 set might not have enough time on the network. You can add the additional delay by setting the ipg0 parameter from 0 to 255, which is the media byte time delay. TABLE 4-5 defines the enable_ipg0 and ipg0 parameters.
Interrupt Parameters TABLE 4-7 describes the receive interrupt blanking values. TABLE 4-7 RX Blanking Register for Alias Read Field Name Values Description rx_intr_pkts 0 to 511 Interrupt after this number of packets have arrived since the last packet was serviced. A value of zero indicates no packet blanking. (Default=3) rx_intr_time 0 to 524287 Interrupt after 4.5 US ticks have elapsed since the last packet was serviced. A value of zero indicates no time blanking.
TABLE 4-8 RX Random Early Detecting 8-Bit Vectors Field Name Values Description red_dv6to8k 0 to 255 Random early detection and packet drop vectors for when FIFO threshold is greater than 6,144 bytes and fewer than 8,192 bytes. Probability of drop can be programmed on a 12.5 percent granularity. For example, if bit 8 is set, the first packet out of every eight will be dropped in this region.
TABLE 4-9 PCI Bus Interface Parameters Parameter Description rx_dma_weight Determines the multiplication factor for granting credit to the RX side during a weighted round robin arbitration. Values are 0 to 3. (Default=0) infinite_burst Enables the infinite burst capability to be utilized. When this is in effect and the system supports infinite burs, the adapter does not free the bus until complete packets are transferred across the bus. Values are 0 or 1.
Refer to the documentation that came with your switch for exact commands to configure jumbo frames support. Jumbo Frames With Trunking 1.3 When using jumbo frames with Trunking 1.3, you must explicitly enable jumbo frames on each link participating in the Trunk. ▼ To Configure Jumbo Frames Using ndd 1. Bring down and unplumb the interface. 2. Set the instance number: % ndd -set /dev/ce instance 0 In this example, the instance number set is 0. 3.
To set parameters so they remain in effect after you reboot the system, create a /platform/sun4u/kernel/drv/ce.conf file and add parameter values to this file when you need to set a particular parameter for a device in the system. Setting Parameters Using the ndd Utility Use the ndd utility to configure parameters that are valid until you reboot the system. The ndd utility supports any networking driver that implements the Data Link Provider Interface (DLPI).
In noninteractive mode, you invoke the utility to execute a specific command. Once the command is executed, you exit the utility. In interactive mode, you can use the utility to get or set more than one parameter value. Refer to the ndd(1M) man page for more information. ▼ To Use the ndd Utility in Noninteractive Mode This section describes how to modify and display parameter values. ● To modify a parameter value, use the -set option.
● To list all the parameters supported by the ce driver, type ?. See TABLE 4-1 through TABLE 4-12 for parameter descriptions.
▼ To Disable Autonegotiation Mode If your network equipment does not support autonegotiation, or if you want to specify your network speed, you can set autonegotiation to off on the ce device. Note – Disabling autonegotiation mode can cause collisions. 1.
Note – Configuring the parameters by putting ndd commands in rcX.d scripts is not supported. The man pages for prtconf(1M) and driver.conf(4) include additional details. The next procedure shows an example of setting parameters in a ce.conf file. ● To access any man page, type the man command plus the name of the man page. For example, to access man pages for prtconf(1M), type: % man prtconf ▼ To Set Driver Parameters Using a ce.conf File 1.
■ ■ The path name before the last component is the parent name. The number after the final @ character within quotes is the unit-address. To identify a PCI device unambiguously in the ce.conf file, use the name, parent name, and the unit-address for the device. Refer to the pci(4) man page for more information about the PCI device specification. In this example: parent = "/pci@8,600000" ■ unit-address = "1" ■ 2. Set the parameters for the above devices in the /platform/sun4u/kernel/drv/ce.conf file.
Then you had to get the link status: # ndd -get /dev/ce link_status 1 Starting in the Solaris 9 Operating System, this method of determining the link status is discouraged, and in some cases, it is removed completely as a driver feature. The new improved approach moves all read-only parameters from the ndd options into kstat. This simplifies getting link status information by allowing you to do it with one simple command.
GigaSwift Ethernet Driver Operating Statistics These statistics are part of the statistics presented by the netstat -k command. TABLE 4-11 describes the read-only Media Independent Interface (MII) capabilities. These parameters define the capabilities of the hardware. The Gigabit Media Independent Interface (GMII) supports all of the following capabilities.
TABLE 4-11 Read-Only ce Device Capabilities (Continued) Parameter Description (Local interface Capabilities) cap_10hdx Local interface half-duplex capability 0 = Not 10 Mbit/sec half-duplex capable 1 = 10 Mbit/sec half-duplex capable cap_asm_pause Local interface flow control capability 0 = Not asymmetric pause capable 1 = Asymmetric pause (from the local device) capable cap_pause Local interface flow control capability 0 = Not Symmetric pause capable 1 = Symmetric pause capable Reporting the Link
If the link partner is not capable of autonegotiation (when lp_autoneg_cap is 0), the remaining information described in TABLE 4-12 is not relevant and the parameter value = 0. If the link partner is capable of autonegotiation (when lp_autoneg_cap is 1), then the speed and mode information is displayed when you use autonegotiation and the link partner capabilities.
TABLE 4-13 Transmit and Receive Parameters (Continued) Parameter Description rx_split_pkts Number of packets that were split across two pages. rx_no_comp_wb Number of times the hardware cannot post completion entries for received data. rx_no_buf Number of times the hardware cannot receive data because there is no more receive buffer space. rx_new_pages Number of pages that got replaced during reception.
▼ To Check Link Partner Settings ● If you are running the Solaris 8 Operating System, type the netstat -k command as superuser: # netstat -k ce0 ce0: ipackets 0 ipackets64 0 ierrors 0 opackets 0 opackets64 0 oerrors 0 collisions 0 rbytes 0 rbytes64 0 obytes 0 obytes64 0 multircv 0 multixmt 0 brdcstrcv 0 brdcstxmt 0 norcvbuf 0 noxmtbuf 0 first_collision 0 excessive_collisions 0 late_collisions 0 peak_attempts 0 length_err 0 alignment_err 0 crc_err 0 code_violations 0 ifspeed 1000000000 promisc off rev_id 48
CODE EXAMPLE 4-1 Output from the kstat Command (Continued) # kstat ce:0 cap_1000hdx cap_100T4 cap_100fdx cap_100hdx cap_10fdx cap_10hdx cap_asmpause cap_autoneg cap_pause code_violations collisions crc_err crtime excessive_collisions first_collision ierrors ifspeed ipackets ipackets64 ipackets_cpu00 ipackets_cpu01 ipackets_cpu02 ipackets_cpu03 late_collisions lb_mode length_err link_T4 link_asmpause link_duplex link_pause link_speed link_up lp_cap_1000fdx lp_cap_1000hdx lp_cap_100T4 lp_cap_100fdx lp_cap_1
CODE EXAMPLE 4-1 Output from the kstat Command (Continued) # kstat ce:0 obytes obytes64 oerrors opackets opackets64 pci_bad_ack_err pci_dmarz_err pci_dmawz_err pci_drto_err pci_err pci_parity_err pci_rma_err pci_rta_err peak_attempts promisc qos_mode rbytes rbytes64 rev_id rx_allocb_fail rx_hdr_drops rx_hdr_pkts rx_inits rx_len_mm rx_msgdup_fail rx_mtu_drops rx_mtu_pkts rx_new_hdr_pgs rx_new_mtu_pgs rx_new_nxt_pgs rx_new_pages rx_no_buf rx_no_comp_wb rx_nocanput rx_nxt_drops rx_ov_flow rx_pkts_dropped rx_
CODE EXAMPLE 4-1 Output from the kstat Command (Continued) # kstat ce:0 tx_dma_hdr_bind_fail tx_dma_pld_bind_fail tx_dvma_pkts tx_hdr_pkts tx_inits tx_max_desc tx_max_pend tx_msgdup_fail tx_no_desc tx_nocanput tx_queue0 tx_queue1 tx_queue2 tx_queue3 tx_starts tx_uflo xcvr_addr xcvr_id xcvr_inits xcvr_inuse 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 1 2121809 1 1 ▼ To Discover Link Partner Capabilities ● Use the kstat command to discover link partner capabilities.
▼ To Discover Link Settings ● Use the kstat command to discover link settings. # kstat ce:0 | grep link link_T4 link_asmpause link_duplex link_pause link_speed link_up 0 0 2 0 1000 1 Configuration Checking The jumbo frame configuration checking occurs at Layer 2 or Layer 3, depending on the configuration method. Layer 2 Configuration Checking You can view the MTU configuration of a ce instance at any time using the kstat command.
CHAPTER 5 Configuring VLANs This chapter explains VLANs in detail and provides configuration instructions and examples. VLANs: Virtual Local Area Networks (VLANs) are commonly used to split up groups of network users into manageable broadcast domains, to create logical segmentation of workgroups, and to enforce security policies among each logical segment. With multiple VLANs on an adapter, a server with a single adapter can have a logical presence on multiple IP subnets.
VLANs are commonly used to separate groups of network users into manageable broadcast domains, to create logical segmentation of workgroups, and to enforce security policies among each logical segment. Each defined VLAN behaves as its own separate network, with its traffic and broadcasts isolated from the others, increasing the bandwidth efficiency within each logical group.
The physical LAN network consists of a switch, two servers, and five clients. The LAN is logically organized into three different VLANs, each representing a different IP subnet. ■ VLAN 1 is an IP subnet consisting of the Main Server, Client 3, and Client 5. This represents an engineering group. ■ VLAN 2 includes the Main Server, Clients 1 and 2 by means of a shared media segment, and Client 5. This is a software development group. ■ VLAN 3 includes the Main Server, the Accounting Server and Client 4.
Configuring VLANs VLANs can be created according to various criteria, but each VLAN must be assigned a VLAN tag or VLAN ID (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. For each network interface (ce0, ce1, ce2 and so on), 4094 possible VLAN IDs can be selected. Because IP subnets are commonly used, it is best to use IP subnets when setting up a VLAN network interface.
▼ To Configure Static VLANs 1. Create one hostname6.cenumber file for each VLAN that will be configured for each adapter on the server. Use the following naming format that includes both the VID and the physical point of attachment (PPA): VLAN logical PPA = 1000 * VID + Device PPA ce123000 = 1000*123 + ce This format limits the maximum number of PPAs (instances) you can configure to 1000 in the /etc/path_to_inst file.
68 Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
APPENDIX A Installing the Software Manually This appendix describes how to install the driver software manually. It contains the following sections: ■ ■ “Installing the Driver Software Manually” on page 69 “Verifying Patches” on page 74 Installing the Driver Software Manually The Sun GigaSwift Ethernet Adapter CD contains the driver software required to operate the adapter.
■ If your system is not running Volume Manager, mount the CD-ROM as follows: # mkdir /cdrom # mkdir /cdrom/cdrom0 # mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/cdrom0 You will see the following files and directories in the /cdrom/sun_gigaswift_ethernet_driver directory or the /cdrom/cdrom0 directory, depending on how you mounted the CD-ROM. TABLE A-1 Files and Directories on the CD-ROM File or Directory Contents Copyright U.S.
TABLE A-1 Files and Directories on the CD-ROM (Continued) File or Directory Contents (For Solaris 9 software only) The optional VLAN packages: • SUNWvld—VLAN utility routines • SUNWvldx—VLAN utility routines (64-bit) • SUNWvldu—VLAN utility headers For Solaris 9 x86 architecture GigaSwiftEthernet/Solaris_9 /i386/Packages/ Contains the Sun GigaSwift Ethernet software packages applicable to to the Solaris 9 x86 version of the software: • SUNWcea—32-bit adb macros • SUNWced—adapter driver • SUNWcedu—adapt
■ If nothing is reported back on SUNWced or SUNWcedx, then proceed to Step 4 and select SUNWcea, SUNWceax, SUNWced.u, SUNWcedx.u, SUNWcedu, and SUNWcem (if present). ■ If nothing is reported back for SUNWvld or SUNWvldx, then proceed to Step 4 and select SUNWvld, SUNWvldx, and SUNWvldu packages. ■ If nothing is reported back, then proceed to Step 4 and select "all" packages. 4.
■ If your system is running Solaris 9 x86 software type the following: # pkgadd -d /Solaris_9/i386/Packages/ A menu similar to the following displays: The following packages are available: 1 SUNWcea Sun GigaSwift Ethernet Adapter Driver 32 bit adb Macros (sparc) 1.0,REV=2001.05.04 2 SUNWceax Sun GigaSwift Ethernet Adapter Driver 64 bit adb Macros (sparc) 1.0,REV=2001.05.04 3 SUNWced.u Sun GigaSwift Ethernet Adapter (32-bit Driver) (sparc.sun4u) 1.0,REV=2001.05.
Verifying Patches Verify whether your system has the needed patches for your version of the Solaris Operating System to ensure that you do not need to add patches. Note – If patches meet the requirements, nothing needs to be installed on the install system. TABLE A-2 lists and describes the patch versions: TABLE A-2 Patch Versions Solaris Patch Version Description 7 112327-18 SunOS 2.7: Sun GigaSwift Ethernet 1.0 driver patch 8 111883-24 SunOS 5.8: Sun GigaSwift Ethernet 1.
■ To verify patches for the Solaris 8 Operating System, type the following: # showrev -p | grep 111883 The patch version should be -24 or greater. ■ To verify patches for the Solaris 9 SPARC Operating System, type the following: # showrev -p | grep 112817 The patch version should be -17 or greater. ■ To verify patches for the Solaris 9 x86 Operating System, type the following: # showrev -p | grep 117714 The patch version should be -01 or greater. 3.
■ If your system is running Solaris 9 x86 software type the following: # cd /cdrom/cdrom0 # patchadd GigaSwiftEthernet/Solaris_9/i386/Patches/117714-01 ▼ To Install a Sun VLAN Utility Patch Note – The VLAN Utility is only supported in Solaris 8 and Solaris 9 software. 1. Determine the version of the Solaris Operating System your system is running: % cat /etc/release Solaris 9 8/03 s9s_u4wos_08a SPARC Copyright 2003 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms.
4. If your system is running the Solaris 9 SPARC Operating System, type the following: # cd /cdrom/cdrom0 # patchadd GigaSwiftEthernet/Solaris_9/Sparc/Patches/114600-02 You will see output similar to the following Solaris 9 SPARC Operating System example: Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 114600-02 has been successfully installed.
78 Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
APPENDIX B Using the Sun GigaSwift Ethernet Driver in Solaris 9 x86 Operating Systems This appendix describes the features and limitations of using the Sun GigaSwift Ethernet driver software in the Solaris 9 x86 Operating System: ■ ■ ■ ■ ■ ■ ■ “Hardware and Software Requirements” on page 79 “Patch Requirements” on page 80 “Product Features” on page 80 “Features Not Currently Supported” on page 81 “Using the Installation Script” on page 81 “Installing the Software Manually” on page 84 “Configuring Driver
Patch Requirements The software driver package provided on the CD-ROM has current driver patch versions (at the time this document was created) preinstalled. ■ Patch-ID Number 117714-01 for Solaris 9 x86 Operating System Install the latest version of the Patch-ID number. For example, the Patch-ID number for the Solaris 9 x86 OS is 117714-01. The dash number -01 becomes higher with each new version of the patch. Updated versions of patches are available at the following web site: http://sunsolve.sun.
■ Energy Star® support Features Not Currently Supported The following features are not currently supported for the Sun GigaSwift Ethernet driver software in the Solaris 9 x86 Operating System.
2. Insert the Sun GigaSwift Ethernet Adapter CD into a CD-ROM drive that is connected to your system. ■ If your system is running Sun Enterprise Volume Manager, it should automatically mount the CD-ROM to the /cdrom/cdrom0 directory. ■ If your system is not running Sun Enterprise Volume Manager, mount the CDROM as follows: # mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/cdrom0 3.
Note – After the installation script runs, you see a summary of the software package or patch that was installed. You can also find a log of the installation in /var/tmp. The log file information is displayed when the installation completes unless the software meets or exceeds the required package or patch level.
Installing the Software Manually ▼ To Install the Software Manually 1. Become superuser. 2. Insert the Sun GigaSwift Ethernet Adapter CD into a CD-ROM drive that is connected to your system. ■ ■ If your system is running Sun Enterprise Volume Manager™, it should automatically mount the CD-ROM to the /cdrom/cdrom0 directory.
TABLE B-1 Files and Directories on the CD-ROM (Continued) File or Directory Contents (For Solaris 8 software only) The optional VLAN packages: • SUNWvld—VLAN utility routines • SUNWvldx—VLAN utility routines (64-bit) • SUNWvldu—VLAN utility headers For Solaris 9 SPARC architecture GigabitEthernet/Solaris_9/ sparc/Packages/ Contains the Sun GigaSwift Ethernet software packages applicable to to the Solaris 9 SPARC version of the software: • SUNWcea—32-bit adb macros • SUNWceax—64-bit adb macros • SUNWced
3. Determine if the ce and vlan drivers are installed on the system: #/usr/bin/pkginfo SUNWced SUNWvld system SUNWced Sun GigaSwift Ethernet Adapter system SUNWvld Sun GigaSwift Ethernet Adapter 4. Install the software packages by typing the following at the command line: # /usr/sbin/pkgadd -d /cdrom/cdrom0/GigaSwiftEthernet/Solaris_9/i386/Packages/ A menu similar to the following displays: The following packages are available: 1 SUNWcea Sun GigaSwift Ethernet Adapter Driver 32 bit adb Macros (i386) 1.
Verifying the Software Installation After you have run the automated installation script, check to be sure you have the current version of the driver installed. ● Use the modinfo command to verify that you have the current driver (v1.137 or later) installed. Type grep CE, using uppercase letters, to get only the specific driver information: # modinfo |grep CE 84 7821c000 4f9a6 75 1 ce (CE Ethernet Driver v1.
88 Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
C Specifications This appendix lists the specifications for the Sun GigaSwift Ethernet adapter. It contains the following sections: ■ ■ ■ ■ “Connectors” on page 89 “Performance Specifications” on page 91 “Physical Characteristics” on page 91 “Power Requirements” on page 91 Connectors FIGURE C-1 RX TX FDX FIGURE C-1 shows the connector for the Sun GigaSwift Ethernet MMF adapter.
1000/100/10 BSE-TX FIGURE C-2 ACT Sun GigaSwift Ethernet UTP Adapter Connector Table A-2 lists the characteristics of the Cat-5 connector used by the Sun GigaSwift Ethernet UTP adapter.
Performance Specifications TABLE C-3 Performance Sepcifications Feature Specification PCI clock 33/66 MHz max PCI data burst transfer rate up to 64-byte bursts PCI data/address width 32/64 -bit PCI modes Master/slave 1 GBit/s, 850 nm (MMF) 1000 Mbps (full-duplex) 1 GBit/s, 850 nm (UTP) 10/100/1000 Mbps (half-duplex or full-duplex) Physical Characteristics TABLE C-4 Physical Characteristics Dimension Measurement Length 6.600 inches (167.64 mm) Width 2.536 inches (64.
92 Sun GigaSwift Ethernet Adapter Installation and User’s Guide • August 2004
APPENDIX D Diagnostic Software and Troubleshooting Issues This appendix provides an overview of the SunVTS diagnostic application and instructions for testing the adapter using the onboard FCode self-test. There is also a section outlining some common troubleshooting issues.
Refer to the SunVTS documentation (listed in TABLE D-1) for instructions on how to run and monitor the nettest diagnostic. These SunVTS documents are available on the Solaris on Sun Hardware Collection, which is provided on the Solaris Supplement CD for the Solaris release on your system.
Using the OpenBoot PROM FCode SelfTest The Sun GigaSwift Ethernet adapter’s self-test verifies the correct operation of the adapter and identifies any hardware problems with the adapter. The self-test is a suite of tests that reside in the adapter’s FCode PROM. Note – The OpenBoot PROM FCode self-test is not available in the Solaris 9 x86 Operating System. You can only invoke the FCode self-test diagnostics using the OpenBoot PROM (OBP) test or test-all commands.
3. At the ok prompt, set the auto-boot? configuration variable to false. ok setenv auto-boot? false 4. Set the diag-switch? parameter to true in order to see the diagnostic power-on self-test (POST) messages. ok setenv diag-switch? true 5. Reset the system to activate these parameter changes. ok reset-all 6. Use the show-nets command to display the list of network devices on the system.
Note – The speed, duplex, and link-clock parameters are optional tests. See TABLE 3-1 for more information about these parameters. The following default tests are run when you execute the test command: ■ ■ ■ ■ MAC internal loopback 1000 Mbps PHY loopback 100 Mbps PHY loopback 10 Mbps PHY loopback Refer to the appropriate OpenBoot Command Reference Manual for more information about the test command.
8. After testing the adapter, type the following commands to return the OpenBoot PROM to the standard operating mode. ok setenv diag-switch? false 9. At the ok prompt, reset the auto-boot? configuration variable to true. ok setenv auto-boot? true 10. Reset and reboot the system. ok reset-all Refer to the system’s documentation for the correct procedures for bringing up the system. Troubleshooting Issues Known Incompatibilities With Pre-IEEE 802.
The following procedure describes how to turn autonegotiation off for one SunSwitch port. 1. Establish a connection to the switch using either a serial connection or a Telnet connection. Refer to the SunSwitch 1.1 Installation and Configuration Guide (805-3743-10) for more information. After connecting to the switch, the Main menu prompt (Main#) is displayed. 2. At the Main# prompt, type cfg to display the Configuration menu and prompt (Configuration#).
▼ To Set Autonegotiation to off for Other Noncompliant Network Equipment If your network equipment does not support autonegotiation, you can set autonegotiation to off on the GigaSwift Ethernet (ce) device. 1. Set the following GigaSwift Ethernet driver parameters to values according to the documentation that shipped with your switch: ■ ■ ■ ■ adv-1000fdx-cap adv-1000hdx-cap adv-ampause-cap adv-pause-cap 2. Set the adv-autoneg-cap parameter to 0.
Nonspecific Issues TABLE D-2 describes the problems you may encounter in using the GigaSwift Ethernet adapter as well as a solution for them: TABLE D-2 Troubleshooting the GigaSwift Ethernet Adapter Problem Description Solution prtdiag does not recognize the NIC in slot 0. If a PCI I/O board of an UltraSPARC III system is filled with network adapters with an internal bridge (for example, GigaSwift Ethernet or Quad FastEthernet), prtdiag displays the card on slot 0.
Problem With DR Attach on Sun Enterprise Platforms DR attach does not configure ce interfaces on Sun Enterprise 10000 platforms running the Solaris 2.6 Operating System. To add DR support for ce interfaces on such systems, make the following changes: 1. Add the following lines to the /etc/system file: set dr:detach_safe_list1="ce" set hswp:suspend_safe_list1="ce" 2. Reboot the system.
Index SYMBOLS E /etc/hostname.
M T MAC address, 13 mac-address property, 13 Media Access Control (MAC), 13 test diagnostic command, 95 to set, 13 V N ndd utility, 47 NVRAM configuration, 13 verify the installation, 9 virtual device, 67 VLAN ID, 66 VLAN naming format, 67 VLANs, 63 O OpenBoot PROM FCode self-test, 95 ok prompt, 95 test command, 97 operational mode parameters, 39 P parameter values how to modify and display, 48 parameters and settings, 38 R random early detection register, 43 receive interrupt blanking values, 38, 4
