# Intel PRO/1000 Network Driver for UnixWare

Installation and Configuration

Advanced Network Services

Modifying a Team's Configuration

Example Topologies

Troubleshooting/Technical Notes

Contact Information

## Installation and Configuration

When installing and configuring network adapters, you may need to refer to SCO* UnixWare* documentation. Have this documentation available during the installation process.

To install the eeE8.pkg file you must be logged in as the root or super user.

To ensure predictable behavior when installing network adapters, remove the configuration settings for all adapters and reboot the system prior to configuring new adapters or reconfiguring installed adapters (see instructions below). For maximum system stability, it is recommended that all network adapters be configured with the same driver type.

### Recommendations

- Do not select "Cancel" when in the process of adding an adapter. To prevent the Network Configuration Manager from hanging and to avoid rebooting, continue installing the adapter. After it's installed, manually remove it.

- PCI Hot Plug*-enabled systems require the e1008g (DDI8) driver. And, if you are not using ANS, the adapters must only be configured using the Hot Plug utility. For example: scoadmin hot. PCI Hot Plug capabilities also require a Hot Plug Controller driver and the appropriate PCI Hot Plug ptfs. If you are using ANS, see the section Using Hot Plug and ANS for more information.

The Intel PRO/1000 adapter driver for SCO UnixWare is packaged in the e1008g.pkg file. To install the e1008g.pkg file and setup the e1008g (DDI8) driver for a network adapter, use the following steps:

1. Make sure no other users are logged on and all user applications are closed.

2. Start the Network Configuration Manager:

   > netcfg

3. Remove any adapters that are configured with the old drivers by selecting the Hardware menu -> Remove Network Device.

   Exit the Network Configuration Manager.

4. Verify that there is not an older version of the driver on the system:

   > pkginfo -l e1008g

   If there is, remove the driver:

   > pkgrm e1008g

   Reboot the system:

   > init 6

5. If you are installing the new driver from the CD, follow these steps. Otherwise, go to the next step.

   Mount the CDROM on the system. For example:

   > mkdir /<cdrom_mount_location>
   > mount -F cdfs -r /dev/cdrom/cdrom1 /<cdrom_mount_location>

   You can install the driver directly from the CDROM or spool the driver from the CDROM so the driver resides on the system. Example of installing the driver directly from the CD:

   > pkgadd –d /<cdrom_mount_location>/PRO1000/UNIXWARE/e1008g.pkg

   Example of spooling the driver from the CD to the system:

   > pkgadd -s spool –d /<cdrom_mount_location>/PRO1000/UNIXWARE/e1008g.pkg e1008g
   > pkgadd e1008g

6. If you are downloading the latest driver, save the package to a directory on your system; for example, the /tmp directory.

   You can install the driver from this directory or spool the driver from the directory so the driver resides on the system. Example of installing the driver from the directory:

   > pkgadd –d /<dir_location>/e1008g.pkg

   Example of spooling the driver from the directory to the system:

   > pkgadd -s spool –d /<dir_location>/e1008g.pkg e1008g
   > pkgadd e1008g

7. If you will be creating teams and/or VLANs, continue on with the instructions in Advanced Network Services below. Otherwise, use the Network Configuration Manager to configure the adapters.

## Advanced Network Services

Intel Advanced Network Services (ANS) for UnixWare includes teaming and VLANs. To use the ANS features install the driver on all adapters that will use ANS.

The latest Intel ANS package for UnixWare is available on the Intel website at http://downloadfinder.intel.com/scripts-df/File_Filter.asp?FileName=ians.pkg.

### Recommendations

- ANS should only be installed over Intel's e1008g (DDI8) driver. Add an ANS team as a protocol over Intel's DDI8 driver. Trying to add it over a different driver is possible in the Network Configuration Manager, but ANS will fail to work.

- Do not add a protocol to an adapter that already has ANS configured above it. After adding an ANS team as a protocol over an adapter, the Network Configuration Manager allows adding other protocols over that adapter. This should be avoided as unexpected results may occur; for example, the system will not know which of the two protocols to use.

- For additional information, see the ANS Usage Guidelines and Limitations in the Troubleshooting section below.

### Installing ANS and Configuring the Adapters

When using Intel ANS, the configuration process differs. Follow these instructions to load ANS onto the system and configure the adapters.

1. Copy the iANS.pkg file to any directory on the system, such as in the /tmp directory.

2. Install ANS:

   > pkgadd -d /tmp/iANS.pkg

3. Reboot the system:

   > init 6

4. If the base driver has not yet been installed, follow the instructions in Installation and Configuration to install the driver.

5. Start the Network Configuration Manger:

   > netcfg

6. Go to the Hardware menu and choose Add New LAN Adapter. The Network Configuration Manager presents the available adapters and drivers.

7. Select the first adapter to configure. If you have the DDI7 driver on your system, it appears as a configuration option. Make sure you only select an adapter displaying the e1008g (DDI8) driver. Select Continue.

8. The Network Driver Configuration window appears. If you are configuring an adapter that supports multiple speed settings, you may change the speed and duplex by selecting Advanced Options. The default is Auto_Auto. After choosing the speed and duplex, select OK.

   | NOTE: Adapters that use optical fiber media operate only at 1000 Mbps and full duplex.

9. The Add protocol window appears. Select the initial protocol for the adapter. For teaming or VLAN operation, select iANS team <team_id>. Select Add.

   | NOTE: You must select ANS before you select any other protocol in order to use this adapter as part of a virtual adapter. You can configure TCP/IP or IPX/SPX on the virtual adapter after you have successfully configured ANS on your adapters.

10. In the ANS configuration utility window, choose the priority of the member just added, then select OK. Priority determines the manner in which the different adapters handle traffic or errors.

11. The ANS configuration utility window prompts you to choose the role of the member in the team. The user determines the team configuration only once, during the addition of the first team member. For instructions on configuring the team, go to Teaming and VLANs below.

12. You may now configure a second adapter from the Hardware menu by selecting Add New LAN Adapter. Repeat steps 7-11.

13. Add the virtual adapter(s) created for the team(s). Select the same protocol for all adapters you add to a team. Instructions for adding a virtual adapter are included below.

###

### Teaming and VLANs

Creating a team with ANS in UnixWare is a two-step process. The first step involves adding members to the team, during which process the team's configuration is established. During the second step, you add one or more virtual adapters and choose the networking protocol you wish to use on them.

Virtual LANs are not compatible with the first generation PRO/1000 Gigabit Server Adapter.

1. After adding the first member to the team, the ANS configuration utility screen appears. Enter a unique team name.

2. If you want to include VLANs in your team, select VLAN mode on and enter the number of VLANs that will be added. If you choose VLAN mode off, no VLANs will be created; but, a virtual adapter will still be created (Ethernet-iANS Virtual Adapter without VLAN-PCI Slot 0 Bus 0) which needs to have a protocol installed over it. Instructions for adding a virtual adapter are included below.

3. Select the teaming mode for the team being configured (none, aft, alb, Static Link Aggregation).

   | NOTE: Adaptive Load Balancing (ALB) encompasses Adapter Fault Tolerance (AFT) as well. Static Link Aggregation includes Gigabit EtherChannel* (GEC) and IEEE 802.3ad static mode (3ad).

4. The following options may be changed by selecting the Advanced Options button. These settings are generally not changed unless necessary.

   > Option | Description
   > --- | ---
   > Probes mode (on/off) | Determines whether ANS probes are used or not
   > Probes addr mode (Broadcast / Multicast) | Determines whether ANS probes are sent as broadcast or multicast packets
   > Check timeout (ticks) | After sending a probe, n ticks expire before the system verifies that the probe was sent to the other members
   > Send time (ticks) | Interval time between probes
   > Max retry count | Number of probe retry bursts to transmit if the first probe was not received by team members
   > Receive timeout (ticks) | After sending a probe retry burst, n ticks expire before checking to see if the retry probe was transmitted to other team members
   > Rx back cycles | Number of probe back cycles to check (determines if probes from previous cycles are valid)
   > Burst size | Number of bits, bytes or characters grouped together for transmission
   > Balance interval (ticks) | Refresh time of load balancing tables (ALB, GEC)

5. Select OK to complete the configuration.

To view a team's configuration, choose Protocol -> View protocol configuration from the Network Configuration Manager.

To modify a team's configuration choose Protocol -> Modify protocol configuration from the Network Configuration Manager.

### Adding Virtual Adapters

When creating a VLAN, you must add the adapters in the VLAN as virtual adapters. To add a virtual adapter for each adapter in the VLAN:

1. Start the Network Configuration Manager:

   > netcfg

2. Select Add New LAN Adapter from the Hardware menu.

3. Select the virtual adapter to add to the VLAN. For example:

> Ethernet-iANS Virtual Adapter with VLAN - PCI Slot 0 Bus 1

If several virtual adapters were added in the previous installation stage, they appear with sequential bus numbers. Additionally, if a virtual adapter is on a different team, its slot number increases.

4. Choose the networking protocol to be installed on the virtual adapter. Although ANS is presented by the Network Configuration Manager as an available protocol, ANS cannot be installed and configured over itself on a virtual adapter.

5. Repeat these steps for the remaining adapters in the VLAN.

To view a virtual adapter's configuration, choose Hardware -> View hardware configuration from the Network Configuration Manager.

To modify a virtual adapter's configuration, choose Hardware -> Modify hardware configuration from the Network Configuration Manager. This allows you to change the virtual adapter's VLAN ID.

## Modifying a Team's Configuration

Most changes to an active team can be accomplished dynamically, without rebooting after the change. Other topology changes require a reboot. View the following lists to determine whether your system requires a reboot in order for the changes to take effect.

Changes that do not require reboot:

- Create a new team

- Add or remove a member to an existing team ("Hot Add")

- Add a virtual adapter to an existing team

- Remove a virtual adapter from an existing team

- Replace a member in an existing team

- Change VLAN ID

- Probe settings (on/off, or other probe parameters)

- Balance interval (in ticks)

Changes that do require reboot:

- Change teaming mode (none, aft, alb, gec/3ad)

- Probe address mode (broadcast/multicast)

## Example Topologies

These examples summarize the actions needed to build two typical topologies:

For a team without VLAN and with several members:

1. Add the first member using Add New LAN Adapter.

2. Choose teaming modes as desired, and set VLAN mode to off.

3. Add all the other members in the same manner.

4. Add the virtual adapter using Add New LAN Adapter.

For a team with VLAN and with several members:

1. Add the first member using Add New LAN Adapter.

2. Choose teaming modes as desired, and set VLAN mode to on.

3. Enter the number of VLAN IDs you will use.

4. Add all the other members in the same manner.

5. Add the virtual adapters using Add New LAN Adapter from the Hardware menu. For each adapter added you will be prompted for the virtual adapter's VLAN ID. Do not give two virtual adapters in the same team the same VLAN ID.

## Troubleshooting

### Known Issues

Symptom | Description
--- | ---
Limitations with the Network Configuration Manager cause some PRO/1000 adapter names that are not installed in the system to appear in the list of adapters. | The Intel® PRO/1000 MT Dual Port Network Connection Adapter is also shown as an Intel® PRO/1000 MF Server Adapter. The Intel® PRO/1000 MT Network Connection Adapter is also shown as an Intel® PRO/1000 F Server Adapter. The Intel® PRO/1000 MT Server Adapter is also shown as an Intel PRO/1000 MT Network Connection Adapter. The e1008g driver may identify certain PRO/100 adapters as PRO/1000 adapters. Workarounds: Install and configure all Intel PRO/100 adapters prior to installing PRO/1000 adapters. If you are installing a MT Dual Port Network Connection Adapter, ignore the entry for the MF Server Adapter when you select Add New LAN Adapter. If you are installing a MT Network Connection Adapter, ignore the entry for the F Server Adapter when you select Add New LAN Adapter. If you are installing a MT Server Adapter, ignore the entry for the MT Network Connection Adapter when you select Add New LAN Adapter.
At boot time, a member fails to be added to a team, and the following error messages are seen on the screen: "Error in handshake with adapter's driver: adapter wasn't opened." and "[FAILED]: anscfg cmd=add_lower team=... lower=... net=... low_attr=...". | This is a known SCO bug in which the adapter's driver is not opened. Possible workarounds: The problem usually disappears after a reboot. If it does not you can try the following: Add a different member and reboot if necessary. Remove some members from the Network Configuration Manager and then adding other members. Reboot if necessary. If none of the above helps, try to remove everything from the Network Configuration Manager, reboot and reconfigure everything. NOTE: This error message might also be seen when hot adding a member.
Hot adding a member to a team fails. The member will not be configured in the Network Configuration Manager and the user will see the following message: "Hot add of member ___ failed". | It is possible that the hot-add failed because of a legitimate reason (no server adapter in team, adapter that doesn't support VLAN in a VLAN-team, etc). In such cases, a relevant error message will be seen in the system log. If there is no message in the log, or if the following message is seen: "Error in handshake with adapter's driver: adapter wasn't opened", then this is an anomaly which is a known issue. It also happens without ANS (in that case, the adapter will be configured in the Network Configuration Manager but will not function). Possible workarounds: Hot add the same member again (try several times). Hot add a different member. Remove some members from the Network Configuration Manager and then add other members. Reboot. If none of the above helps, try to remove everything from the Network Configuration Manager, reboot and reconfigure everything.
The following messages are printed to the system log repeatedly while in VLAN mode: "Secondary adapter ___ deactivated / isolated from other team members." and "Secondary adapter ___ rejoined.". | VLAN IDs are configured in an ANS team, but some of these IDs are not configured in the switch ports to which the team's members are connected. This causes ANS probes transmitted on these VLAN IDs to be lost, which causes adapters to be deactivated. Possible workaround: Configure all the switch ports to which the team's members are connected to be 802.3ac/802.1Q VLAN tagged, with all the VLAN IDs corresponding to the ones configured in the team. NOTE: Messages of fail-overs might also appear.
The following messages are printed to the system log from time to time when transmitting/receiving high-stress traffic: "Secondary adapter ___ deactivated / isolated from other team members." and "Secondary adapter ___ rejoined." | These message appear when ANS probes are lost. Possible workaround: Changing the team's probe-settings may solve the problem or at least limit it. In the Network Configuration Manager, modify the team's advanced options: Choose the team. Select protocol -> Modify protocol configuration, OK, Advanced options. Change "Max retry count" to 20 (causes more probe retries). Change "Receive timeout" to 1 (less time between each retry). NOTE: Messages of fail-overs might also appear.
At boot time, ANS fails to be configured. The console is filled with [FAIL] messages describing the commands that ANS failed to run. In the ANS log (etc/*ans/data/log), the following messages are also printed: "[***] The last operation failed. Exited with status =..." and "Could not open ctrl device..." | Possible workaround: Remove everything from the Network Configuration Manager. Re-install the ANS package using "pkgadd –d". You do not need to remove the package. Reboot the system.

###

### ANS Usage Guidelines and Limitations

Recommendation/Limitation | #### Description
--- | ---
Tunable Parameters | When the ANS package is installed, two system tunable parameters are altered. This is needed in order to support the maximum number of VLANs that can be configured in ANS (64 VLANs).
Parameter | Default value | Value set when ANS is installed
FMOD_RESERVE | 50 | 114
SFNOLIM | 64 | 172
After removing the ANS package, these parameters retain the values set by ANS. This should not affect the user, but the parameters can nevertheless be restored to their default values or to any other value using the SCOAdmin System Tuner or using the 'idtune' command. For more information refer to the idtune man page.
Switching init states: | When the system is in init state 1, do not go directly to init state 3 (using 'init 3'). Instead reboot (using 'init 6') and bring the system up to init state 3. Going directly from init state 1 to init state 3 causes some adapters not to open when adding them to the Network Configuration Manager, and therefore hot-add failures might occur.
Throughput limitations: | There is a SCO limitation regarding the maximum TCP/IP throughput of an adapter. Therefore, when using ALB or GEC mode for TCP/IP traffic, we recommend configuring no more than four members in a team PER virtual adapter. This is because the virtual adapter's throughput will not exceed the mentioned SCO limitation so more members will not improve the total throughput. If the configuration has more than one virtual adapter in a team (in VLAN mode), the throughput of each virtual adapter varies according to the distribution of the traffic between the virtual adapters. As a rule of thumb, traffic that is equally distributed between all virtual adapters allows better average throughput per virtual adapter. Examples: If you configure a non-VLAN ALB/GEC team with one virtual adapter, the team should have a maximum of four members. If you configure an ALB/GEC team with two virtual adapters, a maximum of eight members should be configured. The utilization depends on the distribution of traffic between the virtual adapters.
Hot-remove in GEC mode: | When hot-removing a member in GEC mode, you should also disconnect the member's link from the switch. If you fail to do this, the switch will keep transmitting to that port (the switch isn't aware of the member's removal from the team).
Hot-removing a team's original primary adapter: | A team's MAC address is taken from the MAC address of its original primary physical adapter (the adapter that was chosen as primary at boot-time). If this adapter is hot-removed from the team, both the team and the adapter will have the same MAC address and the following warning will be printed to the system log: "WARNING: the MAC Address ------ is still in use by Team _". In such a case, the removed adapter should not be used anywhere in the network until the system is rebooted, or unexpected results may occur.
Running /etc/nd stop on a member: | /etc/nd stop should NOT be executed on a member's net. If it is executed, the member will become non-operational and you will have to remove it from the team and add it back, or reboot, for the member to become operational again. The following warning will be printed to the system log in this case: "WARNING: Closed member [PCI Slot -, (---)] which is still attached to a team! It must be removed to become operational again."

###

### Using PCI Hot Plug and ANS

#### Requirements

You need a PCI Hot Plug controller driver, such as intelhpcd for the Intel Hot Plug Controller, and the latest UnixWare Hot Plug patch. (For 7.1.1, use ptf7604e, and for 7.1.0, use ptf7428d or later).

If you already have the above packages installed, remove them before installing the new drivers.

1. Install the necessary drivers (DDI8 drivers for adapters and ANS).

2. Reboot the system.

3. Configure your initial network configuration.

4. Install the Hot Plug controller driver and the UnixWare Hot Plug patch.

5. Reboot to rebuild the kernel.

#### Using Hot Plug with ANS Team Members

- Set normal team configurations using the Network Configuration Manager.

- To replace a member adapter: remove it from the team using the Network Configuration Manager, power off the slot using the SCOAdmin Hot Plug manager, remove the adapter, insert the new adapter, power on the slot using the SCOAdmin Hot Plug manager, and add the adapter to the team using the Network Configuration Manager.

#### Limitations of Dynamic Configurations in Hot Plug Computers

When ANS is used on a computer in which Hot Plug is enabled, the following limitations apply (due to the way the Network Configuration Manager works in these cases):

- Building a team and adding virtual adapters require a reboot of the computer.

- In order to configure the IPX/SPX protocol over a virtual adapter, the user should first configure TCP/IP over it, reboot the system, and only then add the IPX/SPX protocol (the TCP/IP protocol can then be removed).

These limitations can be avoided by temporarily disabling Hot Plug before doing anything that will create virtual adapter resources in the Network Configuration Manager (i.e. creating a new team or adding VLANs when modifying a team). Hot Plug can be temporarily disabled using 'modadmin -U <HPCD_MODULE>' where HPCD_MODULE is hpcd/intelhpcd or any other module name used for your Hot Plug Controller Driver. Hot Plug can be enabled again after configuring all virtual adapters by using 'modadmin -l <HPCD_MODULE>'.

## Contact Information (for base driver support)

For information on Intel adapters and drivers:

1. Select Support -> Knowledge Center -> Advanced Search.

2. Enter Intel gigabit in the search box.

3. Select the AND keywords option.

4. Click the Search button.

For Intel Advanced Networking Services (teaming/VLAN) support email unixteam.nic@intel.com.

`Last modified on 5/10/04 4:20p Revision 7`