FILE NAME: ml110g3nic-8.51-1.zip TITLE : HP ProLiant ML110 G3 Embedded Gigabit Ethernet Driver for HP Proliant ML110 G3 Server DESCRIPTION: This .ZIP file contains Embedded Gigabit Ethernet Driver for HP Proliant ML110 G3 Server running Novell Netware 6.5 SBS. CATEGORY: Driver - Network VERSION: 8.51 SUPPORTED LANGUAGE(S): English SUPPORTED HARDWARE: HP ProLiant ML110 G3 Server. SUPPORTED OPERATING SYSTEM: Novell Netware 6.5 SBS. EXPECTED RELEASE DATE: 15 Aug 2005 PUBLIC NOTES: FIXES AND/OR ENHANCEMENTS: Initial Release PREREQUISITES: INSTALLATION INSTRUCTIONS: 1. Unzip the files to the location on the hard drive. 2. Load BASP.LAN just like a standard LAN driver with all necessary frame types for the team. BASP.LAN requires a special VSLOT parameter to specify the virtual slot. The virtual slot can be viewed as a team number and the valid range is from 1 to 4. e.g. LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 3. Load the network drivers for the NIC adapters that will be part of the team. The frame types loaded should be the same for all adapters in the team and same as those loaded for BASP.LAN in step 1. Do not bind protocols directly to these adapters. Be sure to load ODINEB.NLM (a Novell supplied NLM) before all network drivers. e.g. LOAD ODINEB.NLM LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 4. Bind BASP.LAN to the NIC adapters in the team by using a custom BASP BIND command at the console. e.g. BASP BIND BASP_1_EII B57_1_EII BASP BIND BASP_1_EII B57_2_EII Note that if there are multiple frame types loaded on the virtual and the physical adapters, it is only necessary to bind one frame type on the virtual adapter to the same frame type on the physical adapter. The other frame types will be automatically bound. Alternatively, BASP can be bound to NIC adapters like a protocol using the standard Netware BIND command. The protocol name for BASP is BASPn where n is the vslot number. e.g. BIND BASP1 B57_1_EII BIND BASP1 B57_2_EII Note that if there are multiple frame types loaded on the virtual and the physical adapters, it is only necessary to bind BASP to any one frame type on the physical adapter. The other frame types will be automatically bound. 5. Bind protocols to BASP.LAN. e.g. BIND IP BASP_1_EII ADDR=x.x.x.x MASK=x.x.x.x Note that the recommended sequence is to load BASP.LAN before the network drivers as outlined above. This allows BASP.LAN to determine the initial link state of the bound adapters without delay.