User Guide Gigabit Server Network Interface Cards 3C996B-T and 3C996-SX http://www.3com.com/ http://support.3com.com/registration/frontpg.pl Published November 2001 User guide version 1.0.
3Com Corporation ■ 5400 Bayfront Plaza ■ Santa Clara, California ■ 95052-8145 ■ U.S.A. Copyright © 2001 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.
Contents 1 Introduction Contents 1 Advanced Server Features Overview 1 Load Balance 2 Advanced Server Features for Windows 2000 2 Advanced Server Features for Windows NT 3 Advanced Server Features for Novell NetWare 3 Advanced Server Features for Linux 4 3Com Management Programs 4 Creating a Driver Disk 5 2 Installing and Connecting the NIC System Requirements 7 Windows XP (64-bit) 7 Windows XP (32-bit) 7 Windows 2000 7 Windows NT 7 NetWare 8 Linux 8 UNIX 8 Solaris 8 Safety Precautions 9 Pre-Installation
Contents 4 Windows 2000 Driver Setup Installing the Driver Software 25 Verifying Successful Installation 27 Modifying Configuration Parameters 27 Removing the Driver Software 29 Installing Advanced Server Features 30 Uninstalling Advanced Server Features 30 Configuring Advanced Server Features 30 Configuring Teaming 30 Configuring VLANs 32 Advanced Server Control Suite 34 Updating Mini-port (Core) Drivers 34 5 Windows NT Driver Setup Installing the Driver Software 37 Modifying Configuration Parameters 3
Contents 7 Linux Driver Setup Installation Overview 65 Installing the Source RPM Package 65 Building the Driver From a TAR File 65 Patching PCI Files (Optional) 66 Unloading and Removing the Driver 66 Optional Parameters 66 Advanced Server Features 67 Installing Advanced Server Features 68 Configuring Teams 69 8 UNIX and SCO OpenServer Driver Setup UnixWare 7 Driver 75 Package Creation 75 Driver Installation 75 MAC Address 76 Jumbo MTU Size 76 SCO OpenServer Release 5 Driver 76 Installation Diskette 76
Contents 10 3Com Management Programs Overview 85 Installing the Management Programs 85 Removing the Management Programs 86 Initializing the Management Programs 86 Vital Sign 86 Diagnostics 87 Cable Analysis 88 Load Balance/Virtual LANs 89 Saving the Configuration 91 Restoring the Configuration 91 Load Balance/Virtual LAN Statistics 91 11 Troubleshooting Hardware Diagnostics 93 Checking Port LEDs 93 Troubleshooting Checklist 94 Checking if Proper Drivers are Loaded Windows 94 NetWare 95 Linux 95 Running
Contents B Installing and Using the Managed PC Boot Agent Booting From the Network 105 Using the Boot ROM on the NIC to Boot from the Network Enabling or Disabling the Boot ROM Setting 106 C Specifications 10/100/1000 BASE-T Cable Specifications Performance Specifications 107 Physical Characteristics 107 Power Requirements 107 Environmental Specifications 108 D Technical Support Online Technical Services 109 World Wide Web Site 109 3Com KnowledgeBase Services 109 3Com FTP Site 109 Support from Your Ne
1 Introduction This guide describes how to install and configure the 3Com® Gigabit Server NICs in Windows XP, Windows 2000, Windows NT, Novell NetWare, Linux, UNIX, and, Solaris operating system environments. Contents ■ ■ ■ 3Com Gigabit Server NIC Keep the NIC in its package until ready for installation. 3Com Installation CD with Gigabit Server driver software and online user guide. Quick start guide. Inform your network supplier of any missing or damaged items.
1 Introduction Load Balance Load balance is a protocol-specific scheme. The levels of support for IP, IPX, and other protocols are listed below. Protocol Load Balancing Failover IP Yes Yes IPX Yes* Yes** Other protocols No Yes** *Only outbound load-balancing for IPX (on NetWare only). **For 3Com NICs. Load balance mode works with all Ethernet switches without configuring the switch ports to any special trunking mode.
Advanced Server Features Overview Advanced Server Features for Windows NT The following options are supported under Windows NT Server operating systems (Server and Enterprise Server). See “Windows NT Driver Setup” on page 37 for additional information. Failover and Load Balance ■ Adapter teaming for failover (heterogeneous support for 3Com 10/100 server NICs, released Alteon AceNIC, Intel 82559 LAN on Motherboard (LOM), released Intel 10/100 server NICs, and released Intel 1000BaseSX server NICs).
1 Introduction Virtual LAN (VLANs) ■ Up to 64 VLANs per NIC using IEEE 802.1Q-1988 tagging (64 is the maximum configurable, although 32 is the maximum operable). Offloading ■ IP, TCP/UDP checksum—NetWare 5.0 or greater only PCI Hot-Plug ■ Contact your OEM for more information. Advanced Server Features for Linux The Gigabit Ethernet NIC supports the Linux driver. See “Linux Driver Setup” on page 65 for additional information.
Creating a Driver Disk Creating a Driver Disk Create driver disks using the MakeDisk utility (setup.exe file).
2 Installing and Connecting the NIC System Requirements Before installing the Gigabit Ethernet NIC, be sure your system meets the requirements listed for your operating system. Windows XP (64-bit) ■ ■ ■ ■ ■ ■ Itanium-based computer that meets Windows XP software requirements One open 32-bit or 64-bit PCI slot PCI v2.2 33/66 MHz or PCI-x v1.
2 Installing and Connecting the NIC NetWare ■ ■ ■ ■ ■ ■ Pentium-based computer that meets Novell NetWare 4.2/5.x/6.x software requirements One open 32-bit or 64-bit PCI slot PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz 128 MB RAM (minimum) One of the following versions of Novell NetWare: ■ Novell NetWare 5.0 or higher, with Support Pack 3 or the most recent NetWare 5 Support Pack ■ Novell NetWare 4.2 with Support Pack 7 or the most recent Support Pack, including the optional ODI v3.
Safety Precautions Safety Precautions Observe the following safety precautions. WARNING: The NIC is being installed in a system that operates with voltages that can be lethal. Before you remove the cover of your system, you must observe the following precautions to protect yourself and to prevent damage to the system components. ■ Remove any metallic objects or jewelry from your hands and wrists. ■ Use only insulated or nonconducting tools.
2 Installing and Connecting the NIC Installing and Connecting the NIC This manual covers two types of Gigabit Server NICs: server Ethernet NIC (3C996B-T): and server fiber NIC (3C996-SX): The procedure for installing a NIC in a system is identical for both NICs. Connecting the network cables is different for Ethernet and fiber NICs (see “Connecting the Network Cables” on page 12”). Installing the NIC 1 Review the precautions and pre-installation instructions.
Installing and Connecting the NIC NOTE: For optimal performance, select a PCI-X slot. For second best performance, select a 64-bit PCI slot. 3 Remove the blank cover plate from the slot that you selected (see item 1 in the figure, below). 4 Holding the PCI card by the edges, align the NIC’s connector edge with the PCI connector dock. NOTE: The connector dock in a 32-bit PCI slot is shorter than in a 64-bit PCI slot.
2 Installing and Connecting the NIC Connecting the Network Cables Choose your type of NIC (Ethernet or fiber) and follow the procedure. Ethernet NICs Gigabit Ethernet NICs have one RJ-45 connector for attaching the system to an Ethernet copper-wire segment. When automatic link negotiation is disabled, the port can be configured for 10 Mbps or 100 Mbps signaling and either half-duplex or full-duplex operation. To configure the port for 1000 Mbps, both link partners must be configured for autonegotiation.
Installing and Using the 3Com Connection Assistant Fiber NIC 1 If you have not already done so, remove the optical dust cap from the NIC port. 2 Connect the NIC to the network using 62.5/125 µm or 50/125 µm mulitmode fiberoptic cable with SC duplex connectors. Installing and Using the 3Com Connection Assistant The 3Com Connection Assistant is an optional Web-based software component that allows users access to a variety of interactive technical support services.
3 Windows XP Driver Setup Installing the Driver Software Before you begin software installation: ■ Make sure that all software installation requirements are met. See “System Requirements” on page 7. ■ Install the hardware. For instructions, see “Installing and Connecting the NIC” on page 7. NOTE: Before beginning this procedure, verify that Windows XP has been upgraded to the latest version with the latest service pack applied.
3 Windows XP Driver Setup Windows XP 64-bit Use the following procedure to install the driver for the first time in a computer running Windows XP 64-bit version. 1 Start Windows and log in. You must have Network Administrator privileges to install the driver software 2 Insert the 3Com Installation CD in the CD-ROM drive. 3 The main menu appears. Select NIC Software. 4 From the list on the left, select NIC Drivers. 5 Click Install NIC Drivers. 6 Click Install Win XP 64 NIC Drivers.
Verifying Successful Installation Verifying Successful Installation 1 Right-click My Network Places and select Properties from the menu. 2 Check connections in the LAN or High-Speed Internet window. Modifying Configuration Parameters Although the default values should be appropriate in most cases, you may change any of the available options to meet the requirements of your specific system.
3 Windows XP Driver Setup The following options are available: ■ 802.
Removing the Driver Software 7 When all desired configuration is complete, click OK to accept the settings. 8 Reloading your driver is recommended. To do so, right-click My Network Places. 9 Right-click the NIC and select Disable. You have unloaded the driver. 10 Right-click the NIC and select Enable. You have reloaded the driver. 11 Verify that the NIC port LEDs operate as described in the table in “Installing and Connecting the NIC” on page 7.
3 Windows XP Driver Setup 7 Double-click baspi64i.exe to install Advanced Server Features. This will install the Advanced Server Features software and display a window. From this menu, you can create a team. See “Creating a Team and Assigning NICs” on page 21, or click OK to complete installation. Uninstalling Advanced Server Features 1 Start Windows XP I64 Server Edition and log in. You must have Network Administrator privileges to uninstall the driver software.
Configuring Advanced Server Features Accessing the Advanced Server Features Driver Interface Use this procedure to access the NIC properties for teaming configuration: 1 Click the Start menu, and then select Settings/Control Panel. 2 Select Network and Dial-up Connections, right-click 3Com Virtual NIC, and then select Broadcom Advanced Server Program Driver. The Advanced Server Features window appears.
3 Windows XP Driver Setup 4 If a team has no NICs assigned, you will be prompted to add a NIC or delete the team. Click OK. When team has been correctly configured, one Virtual Team NIC driver will be created for each configured team and will appear along with the other NICs in the Local Area Connection Properties window. Click OK. 5 Configure the team IP address if necessary. Configure the IP address and any other necessary TCP/IP configuration for the team. Click OK when finished.
Configuring Advanced Server Features Accessing the Adapter VLAN Configuration Interface Use this procedure to access the NIC properties for VLAN Configuration: 1 Click the Start menu, and then select Settings, Control Panel. 2 Double-click the Gigabit Ethernet NIC icon. The Advanced Server Features configuration window is displayed. If you do not see the Gigabit Ethernet NIC icon, you must install the 3Com Management Programs. For more information, see “3Com Management Programs” on page 85.
4 Windows 2000 Driver Setup Installing the Driver Software Before you begin software installation: ■ Make sure that all software installation requirements are met. See “System Requirements” on page 7. ■ Install the hardware. For instructions, see “Installing and Connecting the NIC” on page 7. NOTE: Before beginning this procedure, verify that Windows 2000 has been upgraded to the latest version with the latest service pack applied.
4 Windows 2000 Driver Setup 9 Follow the steps in the Completing NIC installation with Windows 2000 screen. Click Done. . 10 Click Exit. 11 Make sure the 3Com Installation CD is still in the CD-ROM drive. 12 In the Found New Hardware Wizard screen, click Next. 13 The Install Hardware Device Drivers window appears. Click Search for a suitable driver for my device, and then click Next. 14 The Locate Driver Files screen appears. Select the CD-ROM drives checkbox, and then click Next.
Verifying Successful Installation Verifying Successful Installation 1 Right-click My Network Places and select Properties from the menu. 2 Check connections in the Network and Dial-up Connections window. Modifying Configuration Parameters Although the default values should be appropriate in most cases, you may change any of the available options to meet the requirements of your specific system.
4 Windows 2000 Driver Setup The following options are available: ■ 802.
Removing the Driver Software 7 When all desired configuration is complete, click OK to accept the settings. 8 Reloading your driver is recommended. To do so, right-click My Network Places. 9 Right-click the NIC and select Disable. You have unloaded the driver. 10 Right-click the NIC and select Enable. You have reloaded the driver. 11 Verify that the NIC port LEDs operate as described in the table in “Installing and Connecting the NIC” on page 7.
4 Windows 2000 Driver Setup Installing Advanced Server Features NOTE: Advanced Server Features will only install in a system running a Windows 2000 Server operating system (Server, Advanced Server, or Datacenter Server). 1 Start Windows 2000 Server and log in. You must have Network Administrator privileges to install the driver software. 2 Insert the 3Com Installation CD into the CD-ROM drive. 3 If the main menu appears, click Exit. 4 Double-click My Computer icon.
Configuring Advanced Server Features The Standby Member field is used to permit the selection of one team member to handle traffic, if all other members in the Load Balance Member list fail (failover). The selected Standby Member will not handle any traffic unless all Load Balance Members fail. When one load balance member (or more) is restored (fail-back), traffic will then be resumed by the restored team member(s). Teaming configuration is optional.
4 Windows 2000 Driver Setup NOTE: All other NICs added to the team are reconfigured automatically to match the team configuration. When the basic configuration properties of a team are changed, this changes the configuration of all NICs in the team. However, when a NIC is removed from any failover teams, it will operate according to the parameters set for it before becoming a member of a failover team. 3 Add a NIC to the team.
Configuring Advanced Server Features NOTE: NICs that are members of a team can also be configured to support VLANs; however, VLANs cannot be configured with foreign NICs. When configuring VLANs for team NICs, note that any NIC or LOM that is a member of a team inherits the configuration of the primary NIC. When a NIC or LOM is removed from the team, however, its original configuration parameters are used. By default, Ethernet NICs are configured with VLAN support disabled.
4 Windows 2000 Driver Setup Deleting a VLAN To delete a configured VLAN, follow these steps: 1 From the Advanced Server Features window, select the team from which you want to delete the VLAN, and then click Delete VLAN. The selected VLAN will be deleted from the VLAN list window. 2 When you have finished deleting VLANs, click OK to accept the changes. 3 Click OK at the Local Area Connection Properties window.
Updating Mini-port (Core) Drivers 20 Open the Advanced Server Features driver properties. 21 Click Restore. 22 Type the filename you used during the save. Click OK. 23 Click OK twice to make the changes. 24 The virtual NIC appears in the Network and Dialup Connections window. Open the properties for the virtual NIC. 25 Reset the IP address for the virtual NIC, and then click OK twice to bring up the team.
5 Windows NT Driver Setup Installing the Driver Software Before you begin software installation: ■ Make sure that all installation requirements are met. See “System Requirements” on page 7. ■ Install the hardware. See “Installing and Connecting the NIC” on page 7. NOTE: Make sure that the correct BIOS and Firmware are installed to ensure the system works correctly. NOTE: Verify that your Windows NT system is upgraded with Service Pack 5 (or the latest service pack).
5 Windows NT Driver Setup 11 Click Exit, and then perform the steps outlined in Completing NIC installation with Windows NT screen. 12 When prompted to restart your computer, click Yes. The system restarts, using the new configuration settings. 13 When the system returns to normal operation, verify that the NIC port LEDs operate as described in “Installing and Connecting the NIC” on page 7.
Modifying Configuration Parameters 3 Select the desired NIC from the Network Adapters window and click Properties. The Gigabit Ethernet Controller window opens.
5 Windows NT Driver Setup Updating the Driver Software To replace version 4.0 NIC driver software with newer versions as they become available: 1 Start your Windows NT system and log in. You must have Network Administrator privileges to install the driver software. 2 Insert the 3Com Installation CD in the CD-ROM drive. 3 From the Welcome screen, select NIC Software. 4 Click Update NIC Driver. 5 And Update screen appears. Click OK. 6 The Update NIC Drivers screen appears. Click Done. 7 Click Exit.
Installing Advanced Server Features Installing Advanced Server Features These features are only available for Windows NT Server and Enterprise Server operating systems. NOTE: If you have problems installing the Advanced Server Features, uninstall the Microsoft Loopback Adapter before installing the Advanced Server Features. If needed, you can reinstall the Microsoft Loopback Adapter afterwards. For more information see “Installing the Microsoft Loopback Adapter Driver” on page 46.
5 Windows NT Driver Setup Configuring Teaming Teaming configuration is optional. Before configuring Failover Teaming, see “NIC Teaming” on page 101. Configuring Teaming consists of the following tasks: ■ Accessing the Advanced Server Features Driver Properties ■ Creating teams ■ Adding NICs to the teams ■ Assigning an IP address to the teams ■ Rebooting the system Each of these tasks is described below, along with how to delete NICs from a failover team and how to delete a team.
Uninstalling Advanced Server Features NOTE: All other NICs added to the team are reconfigured automatically to match the team configuration. When a basic team configuration properties are changed, this changes the configuration of all NICs in the team. However, after an NIC has been removed from any team, it will operate according to the parameters set for it before becoming a member of a team. 3 Add a NIC to the team.
5 Windows NT Driver Setup Configuring VLANs VLAN configuration is optional. Before configuring VLANs, see the “VLANs Overview” on page 102. NOTE: NICs that are members of a team can also be configured to support VLANs. VLANs, however, cannot be configured for an Intel stand-alone LAN on Motherboard (LOM) or a team that includes a LOM. When configuring VLANs for team NICs, note that any NIC or LAN-onmotherboard (LOM) that is a member of a team inherits the configuration of the primary NIC.
Uninstalling Advanced Server Features 5 The TCP/IP Properties window appears. Select the VLAN and configure TCP/IP settings. Click Apply. You must configure TCP/IP settings for each VLAN you created. When finished, click OK. 6 When prompted to restart the system, click Yes. A new virtual NIC will be created for each VLAN. NOTE: To maintain optimal NIC performance, your system should have 64 MB of system memory for each eight VLANs created.
5 Windows NT Driver Setup Installing the Microsoft Loopback Adapter Driver When you do a fresh installation of Windows NT 4.0, Microsoft recommends that you install the Microsoft Loopback Adapter driver, and then verify that networking is operating normally before installing any NICs. The Loopback Adapter driver enables the computer to connect to local network resources that then allow alerter and messenger services to start on a stand-alone system.
Performing a Fresh Installation of Windows NT on a Backup Domain Controller CAUTION: If performed incorrectly, this procedure can destroy the primary domain controller security database. Use the rdisk /s command to make emergency repair diskettes to backup the server security databases on the two servers before attempting this procedure. 1 Install Windows NT 4.0 with service pack 6a on two servers set up as primary domain controllers.
5 Windows NT Driver Setup Stopping the Net Logon Service on SERVER 1 1 Double-click the Control Panel. 2 Double-click Services. 3 In the Services dialog box, select Net Logon. 4 Click Stop. 5 Click Yes to stop the net logon service. This unlocks the security database. 6 Close the Services dialog box. Stopping the Net Logon Service on SERVER 2 7 Double-click the Control Panel. 8 Double-click Services. 9 In the Services dialog box, select Net Logon. 10 Click Stop.
Updating Mini-port (Core) Drivers 18 On SERVER-1, refresh the Server Manager dialog box. From the View menu, select Refresh. The Server Manager dialog box now shows SERVER-2 as PRIMARY and SERVER-1 as BACKUP. 19 Select SERVER-2. 20 From the Computer menu, select Synchronize with Primary Domain Controller. 21 Click Yes to start synchronization. 22 Click OK. 23 Restart SERVER-1. 24 Restart SERVER-2. 25 Verify that services are starting correctly.
5 Windows NT Driver Setup 15 Open the Advanced Server Features driver properties. 16 Click Restore. 17 Type the filename you used during the save, and then click OK. 18 Click OK again to make the changes. 19 Click Close to reset the IP address on the virtual NIC. 20 When the machine prompts you to restart, click Yes.
6 Novell NetWare Driver Setup Pre-Installation Requirements ■ ■ The NIC must be installed in the server. Install the latest support pack files. The NetWare support pack or patch file(s) needed for your server operating system are indicated below: NetWare OS NetWare 5.1 NetWare 4.2 Support Pack or Patch NetWare 5.1 Support Pack (or latest support pack) Files to be Installed The latest support packs can be found at: http://support.novell.com/misc/patlst.htm Support Pack 8.0 or later NOTE: NetWare 5.
6 Novell NetWare Driver Setup 8 Repeat steps 6 through 8 for additional NICs. 9 After you are finished configuring the NICs, select Continue Installation. NOTE: You may want to change the autoexec.ncf file to add or delete keywords. The startup.ncf and autoexec.ncf files can be edited by invoking NWCONFIG from the NetWare 5.x server console, and by invoking LOAD INSTALL from the NetWare 4.x server console. Example of a typical autoexec.
Installing Novell NetWare Server 4.2 Parameter Options Description TxDescriptors = Default = 120 Min = 100 Max = 400 Pre-allocates ECB resources on the adapter for transmitting packets. RxFlow = Default = ON Selections are: ON, OFF Allows enabling/disabling of RxFlow control. TxFlow = Default = ON Selections are: ON, OFF Allows enabling/disabling of TxFlow control. Slot = n Identifies the slot number for the specific BCM5700 adapter currently being configured.
6 Novell NetWare Driver Setup Installing Novell NetWare Server 5.1 Be sure that the server has the latest support pack available installed. The latest support packs can be found at: http://support.novell.com/misc/patlst.htm. You may want to create an archive disk by copying all the files from the CDROM\NetWare\Driver directory onto a floppy disk. If you choose to use the CD directly, ensure that the CDROM.NLM is loaded and that you are aware of the NetWare Volume name for the CD that you just installed.
Removing Drivers from Autoexec.ncf # WARNING! # If you change the name of this server, you must update # all the licenses that are assigned to this server. Using # NWAdmin, double-click a license object and click # Certificate Assignments. If the old name of # this server appears, you must delete it and then add the # new server name. Do this for all license objects. ServerID 1C8EE2C LOAD ODINEB.NLM LOAD TCPIP LOAD B57 SLOT=2 FRAME=Ethernet_802.
6 Novell NetWare Driver Setup Installing Advanced Server Features 1 Load BASP.LAN just like a standard LAN driver with the same frame types loaded for the NIC in the team. BASP.LAN requires a special VSLOT parameter to specify the virtual slot. The virtual slot can be viewed as a team number. Example: LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 2 After BASP.LAN is successfully loaded, a new screen appears. This screen displays all virtual NIC settings and statistics.
Uninstalling Advanced Server Features Load Balance and Trunk Mode Selection Use “MODE=SLB” for Load Balance mode or “MODE=TRUNK” for Generic Trunking mode. The default is load balance mode. Example: LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 MODE=TRUNK NOTE: Load Balance occurs only on the Tx send side with IPX protocol. It will not Load Balance on the receive side when running NetWare Advanced Server Features.
6 Novell NetWare Driver Setup 3 Bind BASP.LAN to the NIC in the team for each protocol. Example: BASP BIND BASP_1_V2_EII B57_1_EII BASP BIND BASP_1_V2_EII B57_2_EII Note that if there are multiple VLANs (each with one or more frame types) loaded on the virtual NIC, it is necessary to bind only one frame type on one VLAN on the virtual NIC to the same frame type on the physical NIC. The other VLANs will be bound automatically. 4 Bind protocols to BASP.LAN. Example: BIND IP BASP_1_V2_EII ADDR=x.x.x.
Uninstalling Advanced Server Features Additional Command Line Keywords CHECKSUM=ON This enables BASP.LAN to offload TCP/UDP and IP checksums to the bound NIC if supported. This will improve performance if some or all NIC in the team support hardware checksums. Example: A team of two BCM5700 NICs with hardware checksums enabled. LOAD BASP.LAN FRAME=ETHERNET_II NAME=B57_1_EII CHECKSUM=ON VSLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII CHECKSUM=ON SLOT=1 LOAD B57.
6 Novell NetWare Driver Setup # Note: The Time zone information mentioned above # should always precede the SERVER name. Set Bindery Context = 3Com file server name GOBRCM ipx internal net 1234ABCD load conlog maximum=100 ; Network driver LOADs and BINDs are initiated via ; INITSYS.NCF. The actual LOAD and BIND commands ; are contained in INITSYS.NCF and NETINFO.CFG. ; These files are in SYS:ETC. #sys:etc\initsys.
Uninstalling Advanced Server Features VLAN=3 LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V4_EII VSLOT=1 VLAN=4 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_V_EII SLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_V_EII SLOT=2 # Bind BASP.LAN to the NIC adapters in the team for each protocol # Note: BASP BIND is only used for the first VLAN all other VLANs are automatically # bound to the virtual adapter (VSLOT=1). BASP BIND BASP_1_V2_EII B57_1_V_EII BASP BIND BASP_1_V2_EII B57_2_V_EII #Bind protocols to BASP.
6 Novell NetWare Driver Setup NOTE: Bind B57_1_EII to BASP_1_E82 is also bound to BASP_1_E82. VLSOT range is from 1 to 4 (only four TEAMS can be configured.) Example of VLAN with Advanced Server Features: LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=100 LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=200 LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=300 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 LOAD B57.
Installing Advanced Server Features on Novell NetWare Server 4.2 and 5.1 Installing Advanced Server Features on Novell NetWare Server 4.2 and 5.1 Use the following procedure to install Advanced Server Features on Novell NetWare Server 4.2 and 5.1: 1 Load BASP.LAN just like a standard LAN driver with the same frame types loaded for the NIC in the team. BASP.LAN requires a special VSLOT parameter to specify the virtual slot. The virtual slot can be viewed as a team number. Example: LOAD BASP.
6 Novell NetWare Driver Setup NIC Driver Configuration Parameters for Novell NetWare Parameter Options Description CheckSum = Default = ON Selections are: ON, OFF, Tx, Rx Enables or disables the transmit and receive checksum off-loading feature. Note that checksum is supported under NetWare 5.x only. Frame = type Valid types are: Ethernet_802.2 Ethernet_802.3 Ethernet_II Ethernet_SNAP Defines the frame type being used by this load instance. Ethernet_802.2 and Ethernet_II are the default values.
7 Linux Driver Setup Installation Overview The driver is distributed in three packaging formats: binary RPM, source RPM, and compressed tar archive. The binary RPM includes precompiled driver modules for kernels 2.2.14-6.1.1 (Red Hat 6.2) and 2.2.16-22 (Red Hat 7.0), and is the preferred installation method for systems running these kernel versions. The source RPM is suitable for use on any system that has the RPM utility installed and a properly configured kernel source tree.
7 Linux Driver Setup Patching PCI Files (Optional) To use Red Hat’s kudzu hardware detection utility, a number of files containing PCI vendor and device information need to be patched with information on the BCM5700 chip. A patch file (pci.patch) is included for Red Hat 7. Apply the patch by typing the following: patch -N -pl -d /usr < pci.
Advanced Server Features ■ ■ ■ ■ rx_flow_control Enables or disables receiving flow control (pause) frames. This parameter is used together with auto_flow_control. The valid values are: 0 pause receive disabled (default) 1 pause receive enabled if auto_flow_control is set to 0, or pause receive advertised if auto_flow_control is set to 1 tx_flow_control Enables or disables transmitting flow control (pause) frames. This parameter is used together with auto_flow_control.
7 Linux Driver Setup Installing Advanced Server Features The driver is released in two packaging formats, source RPM and compressed tar archive. The file names for the two packages are bcm5700-.src.rpm and bcm5700.tar.gz respectively. Identical files to build the driver are included in both packages. Installing the TAR Archive NOTE: Before installing the tar archive, copy the tar archive from the CD to a temp directory on your PC.
Advanced Server Features 5 See “Configuring Teams” on page 69 to set up the teams. Makefile makefile baspcfg precompiled configuration utility bcmtype.h commonly use type header file blf.c Advanced Server Features module entry points blf.h ioctl interface blfcore.h core interface blfcore.o precompiled core object blfopt.h automatically generated header file from Make blfver.h version header file nicext.h NICE header file pal.c platform abstraction implementation pal.
7 Linux Driver Setup NOTE: Forming multiple teams is possible by copying the sample files into “/etc/ basp/” and modifying this file as described in the sample file. The files must have unique filenames. Name the files “team-xxx” where “xxx” is a unique identifier for the team. NOTE: To create more that one virtual interface (VLAN) for each team, refer to the respective description section in the sample files.
Advanced Server Features Startup Scripts 1 basp This script is intended to be installed in /etc/rc.d/init.d directory. After copying the script, run “chkconfig --add basp”. This script will be executed at runlevel 2, 3, 4 and 5. When basp runs, it will search the /etc/basp directory to list all the files with “team” prefix, and then it will invoke the “baspteam” script to add or delete the teams. It is normal, for each “team-*” file in /etc/basp, to represent 1 team.
7 Linux Driver Setup Configuration Scripts Both team-sample and team-gec are configuration scripts that follow the same syntax, as follows: ■ TEAM_ID: this number uniquely identifies a team. ■ TEAM_TYPE: 0 = SLB, 1 = Generic Trunking/GEC/FEC ■ TEAM_NAME: ascii name of the team ■ TEAM_PAx_NAME: ASCII name of the physical interface x, where x can be 0 to 7. ■ TEAM_PAx_ROLE: role of the physical interface x 0 = Primary, 1 = Hot-standby. This field must be 0 for Generic Trunking/GEC/FEC team.
Advanced Server Features Removing the Driver and Team Configuration To remove the RPM package, type: rpm -e basplnx-{version}.386.
8 UNIX and SCO OpenServer Driver Setup UnixWare 7 Driver This procedure describes the installation procedure for the UnixWare 7 driver. The driver is released as a TAR file containing the set of object, configuration, and script files used to create the driver add-on package. Package Creation To create a package: 1 On a UnixWare system, create a directory for the package and copy the files on the installation CD to it. 2 Untar the TAR file using: tar xvf bcme-.tar.
8 UNIX and SCO OpenServer Driver Setup Line Speed FullDuplex1000* * 1000 Mbps (1 Gbps) full duplex fixed speed is only valid for fiber connections. For copper twisted-pair connections, 1 Gbps can only be set through autonegotiation with a 1 Gbps partner. Flow Control Off (default) AutoNegotiate (Symmetric Pause advertised)* RxPause TxPause RxPause/TxPause *Autonegotiation of Flow Control is only valid when the Line Speed is set to AutoNegotiate.
SCO OpenServer Release 5 Driver Driver Installation To install the driver: 1 Install the SCO OpenServer driver from the media image or installation diskette using either: custom or scoadmin. 2 Add the new network adapter using: netconfig. 3 Modify the hardware configuration in Advanced Options to change the Line Speed and Flow Control, if desired. The settings for these parameters are listed in step 3 of “Driver Installation” on page 75.
9 Solaris Driver Setup The Solaris Release 8 driver is released in two formats: 1 BRCMbcme.pkg (datastream format) 2 BRCMbcme.tar.Z (compressed and TAR file system format) Driver Installation To install the Solaris driver: 1 Change to the directory in which BRCMbcme.pkg resides. 2 Perform one of the following two substeps: a pkgadd -d BRCMbcme.pkg or b Copy BRCMbcme.tar.Z to /tmp cd /tmp uncompress BRCMbcme.tar pkgadd -d /tmp 3 Execute prtconf to determine the instance number of the NIC.
9 Solaris Driver Setup Customizing the Driver Configuration To customize the driver, edit /kernel/drv/bcme.conf and update the respective parameters in this file. These parameters are described below. ForceSpeedDuplex ForceSpeedDuplex configures the link (or instance) to a certain speed and duplex mode. By default, all instances are set to AutoNegotiate (0).
Customizing the Driver Configuration MaxJumboFrameSize MaxJumboFrameSize configures the Jumbo Frame feature of a link. The valid range of values for this parameter is 0 to 9000. If the value configured is less than 1500, the Jumbo Frame feature is disabled. Once this is configured, the ifconfig command is used to configure the desired MTU size.
9 Solaris Driver Setup TxMaxCoalescedFrames TxMaxCoalescedFrames configures the number of Tx Maximum Coalesced Frames parameters. This determines upper boundary of the maximum number of Tx buffer descriptors that the device processes before it will generate an interrupt. The default value is 10: TxMaxCoalescedFrames=10; RxCoalescingTicksDuringInt RxCoalescingTicksDuringInt configures the number of Rx Host Coalescing Ticks in microseconds during an interrupt.
Customizing the Driver Configuration ndd Command Driver configurations can also be temporarily changed with the ndd command. Any changes made with this command are temporary and will be lost when you reboot the system. To make permanent configuration changes, modify bcme.conf instead. NOTE: Refer to the parameter descriptions as required in “Customizing the Driver Configuration” on page 80.
10 3Com Management Programs Overview The 3Com Management Programs are an integrated graphical user interface application that provides status reports for all LAN NICs/controllers in your system (“Vital Sign”); a comprehensive diagnostics tool for Gigabit Ethernet controllers (“Diagnostics”); an in-depth analysis of physical cable transceiver conditions (“Cable Analysis”); an easy way to configure the load balance and failover by grouping multiple NICs/controllers (“Load Balance/Virtual LAN”); and detailed
10 3Com Management Programs Removing the Management Programs To remove the 3Com Management Programs software, do the following: 1 Select Start/Control Panel, then double-click Add/Remove Programs. 2 Select Management Programs and click Change/Remove. 3 Select Remove from the Modify, Repair, Remove menu and follow the prompts. Initializing the Management Programs To initialize the 3Com Management Programs software, do the following: 1 Click Start, Settings, and then click Control Panel.
Initializing the Management Programs ■ ■ ■ Memory Address: Indicates the memory mapped address that is assigned to the selected NIC. This value can never be zero. PCI Bus Mode: Indicates the type and mode of PCI bus slot that is occupied by the selected NIC.
10 3Com Management Programs ■ page 97 for information about using the DOS Diagnostic program B57DIAG.exe to run the PHY Loopback Test.) Test LED: Verifies that the NIC LED is working properly. Cable Analysis From the Cable Analysis screen, the user can monitor conditions of an Ethernet CAT5 cable connection within a cable plant in an Ethernet network.
Initializing the Management Programs Load Balance/Virtual LANs The Load Balance/Virtual LANs screen allows you to configure advanced features. Any available NIC can be configured as part of a team. Teaming is a method of grouping multiple NICs to a virtual NIC (bundling multiple NICs to appear as a single NIC). The benefit of this approach is load balancing. By selecting each of the available NICs, and moving it to the Load Balance Members column, this appears as one NIC.
10 3Com Management Programs 4 Click OK. When a team has been correctly configured, one Virtual Team NIC driver will be created for each configured team. When you create a generic trunking team, you cannot select a Standby Member. Standby Members work only with Load Balance and Failover Teams. 5 Configure the Team IP address if necessary. If other NICs in your system use TCP/IP bindings, the TCP/IP Properties window will open.
Initializing the Management Programs Saving the Configuration 1 With the Team and VLAN configuration loaded, click Save As at the Load Balance/ Virtual Lan tab. 2 At the Save As screen, enter the path and filename of the new configuration file. A “bcg” extension will be placed on the filename. Click Save. 3 A configuration file will be placed in the directory. This new configuration file is a text file and can be viewed by any text editor. The file contains both adapter and team configuration information.
10 3Com Management Programs ■ Broadcast Frames Rx—Count of frames that are successfully received and are directed to the broadcast group address. This does not include frames received with frametoo-long, FCS, length or alignment errors, or frames lost due to internal MAC sublayer error. This counter is incremented as indicated by the receiveOK status, and the value in the Destination field. IEEE 802.3 Interface components of the Statistics/IEEE 802.
11 Troubleshooting Hardware Diagnostics Loopback diagnostic tests are available for testing the NIC hardware under Windows. These tests provide access to NIC internal/external diagnostics, where packet information is transmitted across the physical link. See “Diagnostics” on page 87. Checking Port LEDs The NIC has four LEDs, one for each port speed option (10 Mbps, 100 Mbps, and 1 Gbps), and one for Data Transfer.
11 Troubleshooting Troubleshooting Checklist WARNING: Before removing or inserting the NIC, please review all precautions outlined under “Safety Precautions” on page 9. The following checklist provides recommended actions to take to resolve problems installing the Gigabit Ethernet NIC or running it in your system. ■ ■ ■ ■ ■ ■ ■ ■ Inspect all cables and connections. Verify that the cable connections at the Gigabit Ethernet NIC and the switch are attached properly.
Running Cable Analysis NetWare From the command line, type config then press Enter. The following status information is displayed: 3Com Gigabit Ethernet NIC Version: Hardware Setting: Mode Address: Frame Type: Board Name: Lan Protocol: ARP (see note) Lan Protocol: IP Addr: (see note) NOTE: The LAN protocol status appears after assigning an IP address to the adapter (that is, bind). Linux To verify that the bcm5700.
11 Troubleshooting Length The Length sub tab allows you to verify cable length and determine whether your configuration has the appropriate cable, which are calculated by cable loss and return loss algorithms. This utility allows you to determine whether the problem is with the adapter or in the cable plant. 1 From the Cable Analysis/Length screen, select the NIC to be tested. 2 Click Initialize, and then click Test to display the status of the selected adapter.
DOS Diagnostic Failures Linux To verify that the Ethernet interface is up and running, run ifconfig to check the status of the Ethernet interface. To check the statistics on the Ethernet interface, you can also use netstat -i. Consult manual pages for more information on ifconfig and netstat. DOS Diagnostic Failures Running the DOS diagnostic B57DIAG.exe can result in false failures under the following circumstances: ■ The DOS diagnostic B57DIAG.exe will fail if EMM386.exe is loaded in low memory.
11 Troubleshooting Problem Solution Team configuration is not retained when user goes back to edit. In configuring Advanced Server Features teams, the actual changes of the configuration is not committed until the user click “OK” in “Network Properties” window. If a user chooses not click OK and instead goes back to the Advanced Server Features team configuration window, all the previous uncommitted changes will be lost and the user will need to re-enter the configurations.
A Key Protocols and Interfaces CIM The Common Information Model (CIM) is an industry standard defined by the Distributed Management Task Force (DMTF). Microsoft implements CIM on Windows platforms such as Windows 2000. 3Com will support CIM on the Windows 2000 platform. The 3Com implementation of CIM will provide various classes to provide information to users through CIM client applications.
A Key Protocols and Interfaces DMI The DMI PCI Hot-Plug service operates in conjunction with the DMI Service Provider software component. It provides hot-swap/ hot-add functionality for the NIC in Windows 2000 and Windows NT 4.0 hot plug systems. You should consult the system documentation to determine the supported Hot-Plug capabilities. The hot-swap feature allows the user to replace a NIC without bringing down the system.
NIC Teaming NIC Teaming Teaming provides traffic load balancing and redundant NIC operation in the event that a network connection fails. When multiple Gigabit Ethernet NICs are installed in the same server, they can be grouped into teams. Each team, with up to 8 ports or 8 NICs, can be configured on the server.
A Key Protocols and Interfaces Failover Teaming Failover Teaming provides redundant NIC operation in the event that a network connection fails. When multiple Gigabit Ethernet NICs are installed in the same server, they can be grouped into teams. Each team must have at least one NIC, but can support up to eight NICs. The number of teams is limited by the number of NICs that are installed.
VLANs Overview 32-bit or 64-bit PCI Bus Master The PCI Interface on the Gigabit Ethernet NIC complies with PCI Local Bus Rev 2.2, is compatible with both 32-bit and 64-bit PCI buses. As a bus master, the NIC requests access to the PCI bus, instead of waiting to be polled. ASIC with Embedded RISC Processor The core control for the Gigabit Ethernet NIC resides in a tightly integrated, highperformance ASIC. The ASIC includes dual RISC processors.
B Installing and Using the Managed PC Boot Agent Booting From the Network This section explains how to use the Managed PC Boot Agent (MBA) to boot from the network. NOTE: For detailed information on using, configuring, and troubleshooting the MBA, see the Managed PC Boot Agent User Guide, located with the MBA software on the 3Com Installation CD. MBA allows the PC to boot from the server rather than from its local hard drive.
B Installing and Using the Managed PC Boot Agent Non-BBS BIOS-Compatible PCs To enable a non-BBS BIOS-compatible PC to boot from the network using the MBA boot ROM: 1 Make sure that the NIC boot ROM setting is Enabled. See “” on page 106 for instructions. 2 Change the MBA default boot setting from Local to Network.
C Specifications 10/100/1000 BASE-T Cable Specifications Port Type Connector Media Maximum Distance 10BASE-T RJ-45 Cat. 3, 4, or 5 UTP 100 meters (325 ft) 100/1000BASE-T RJ-45 Cat. 5 UTP 100 meters (325 ft) NOTE: 1000BASE-T signaling requires four twisted pairs of Category 5 balanced cabling, as specified in ISO/IEC 11801:1995 and ANSI/EIA/TIA-568-A (1995) and tested for additional performance using testing procedures defined in TIA/EIA TSB95.
C Specifications Environmental Specifications 108 Condition Operating Specification Storage Specification Temperature 0°C to 55°C (+32°F to +131°F) –40°C to +85°C (–40°F to +185°F) Relative humidity 5% to 85% (non-condensing) 40°C, 16 hour dwells at extremes 5% to 95% (non-condensing) 10°C/hour Altitude Up to 10,000 ft. Up to 35,000 ft. Shock 10g, 1/2 sine wave, 11 msec 60g, 1/2 sine wave, 11 msec Vibration, peak to peak displacement 0.005 in. max (5 to 32 Hz) 0.1 in.
D Technical Support 3Com provides easy access to technical support information through a variety of services. This appendix describes these services. Information contained in this appendix is correct at time of publication. For the very latest, 3Com recommends that you access the 3Com Corporation World Wide Web site.
D Technical Support Support from Your Network Supplier If additional assistance is required, contact your network supplier. Many suppliers are authorized 3Com service partners who are qualified to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services.
Returning Products for Repair Country Telephone Number From the following countries, you may use the toll-free numbers: Austria Belgium Denmark Finland France Germany Hungary Ireland Israel Italy Luxembourg Netherlands Norway Poland Portugal South Africa Spain Sweden Switzerland U.K.
D Technical Support Country Austria Belgium Denmark Finland France Germany Hungary Ireland Israel Italy Netherlands Norway Poland Portugal South Africa Spain Sweden Switzerland U.K. 112 Telephone Number 0800 297468 0800 71429 800 17309 0800 113153 0800 917959 0800 1821502 00800 12813 1800553117 1800 9453794 1678 79489 0800 0227788 800 11376 00800 3111206 0800 831416 0800 995014 900 983125 020 795482 0800 55 3072 0800 966197 Latin America 1 408 326 2927 U.S.A.
Regulatory Information FCC Class A Verification Statement WARNING: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules, and the Canadian Department of Communications Equipment Standards entitled, “Digital Apparatus,” ICES-003. These limits are designed to provide reasonable protection against harmful interference in a commercial installation.
Regulatory Information FCC Declaration of Conformity We declare under our sole responsibility that the Model: Description: 3C996B-T Gigabit Server NIC (Ethernet) 3C996-SX Gigabit Server NIC (Fiber) to which this declaration relates, are in conformity with the following standards or other normative documents: ■ ANSI C63.4-1992 Methods of Measurement Federal Communications Commission 47 CFR Part 15, subpart B 3Com Corporation, 5400 Bayfront Plaza, P.O.
Index Numerics 10 LED 93 100 LED 93 1000 LED 93 1000BASE-T signaling requirements 12 32-bit PCI bus master 103 3Com 10/100 server NICs 2, 3 3Com Connection Assistant 13 3Com Management Programs 4, 23, 26, 30, 34, 38, 45, 85 to 92 Cable Analysis 88 Diagnostics 87 initialization 86 installation 85 removing 86 Vital Sign 86 64-bit PCI bus master 103 802.
Index 82559 LAN on Motherboard (LOM) 2, 3 stand-alone LAN on Motherboard (LOM) 44 Internal Memory Test 87 Internet Explorer 13 Interrupt 86 Interrupt Test 87 IP Address 86 IPX protocol 57 ISO/IEC 11801:1995 12 J jumbo frames 2, 3 jumbo MTU 17, 18, 27, 28, 38, 39, 76, 77 margin 96 Master Navigator 5, 16 MaxJumboFrameSize 81 Memory Address 87 Microsoft Exchange 46 Microsoft Java Virtual Machine 13 Microsoft Loopback Adapter 37, 41, 46 MII Register Test 87 mini-port (core) drivers Windows 2000 34 Windows NT
Index Test LED 88 TIA/EIA TSB95 12 troubleshooting 93 checklist 94 MBA boot ROM 105 trunking 101 Tx.
