Autoconfiguration does not seem to be working.
Make sure you choose Auto/Auto rather than assuming it as the default during configuration.
Autoconfiguration must be configured at both the adapter and the switch.
If the adapter is set to full duplex and the switch is set to autonegotiate, the adapter may default to half duplex.
ANS doesn't seem to work.
The protocol must be bound to a virtual adapter, not to a physical adapter. Only ANS should be bound to a physical adapter.
ANS should only be bound go a DDI8 driver. (eeE8)
To configure IPX:
Configure the VAdapter with the TCP/IP protocol (no need to enter an IP address).
Reboot to INITSTATE 3.
Add the SPX/IPX protocol to the VAdapter (TCP/IP can now be removed)
Note: If at boot-time, ANS fails when comitting the team or when adding the Virtual Adapter to the team, the system might hang because of a SCO issue (trying to add IPX/SPX to a non-existent adapter). Boot to initstate 1 to fix the failure.
A commit=later team disappears after reboot from netcfg:
This is expected behavior. Don't reboot the system if uncommitted teams exist in Netcfg. If the problem already occurred: typing "netcfg -s" restores the members, and the user can add them again in netcfg.
Hot -removing a member in FEC mode:
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 the same as the original primary (physical) adapter (chosen at installation). 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 _".
Do not add the removed adapter back into the NETWORK except in it's original role, until the system is rebooted.
Running /etc/nd stop on a member:
/etc/nd stop should NOT be executed on a member's net. (If run, it MUST be removed from the team
and then added back, or you must reboot to make it operational. 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!
"Error in handshake with adapter's driver: adapter wasn't opened" (at boot)
[FAILED]: anscfg cmd=add_lower team=... lower=... net=... low_attr=...
Cause: This is a known SCO bug, in which the adapter's driver isn't opened.
Possible workarounds: Reboot.
Possible Other Solutions: Try to add a different member and reboot
Try removing some members from netcfg and then adding other members and Reboot.
Try to remove everything from netcfg, reboot and reconfigure.
"Hot add of member ___ failed". (during hot add)
Check the system log for a legitimate reason (no server adapter in team). See Error in Handshake
Possible Cause: Going directly from initstate 1 to initstate 3 causes some adapters not to open when adding them to netcfg, and therefore hot-add failures might occur. (use int 6 followed by int 3)
"Error in handshake with adapter's driver: adapter wasn't opened" (in log)
Cause: known issue - also happens without ANS (adapter will be configured in netcfg but will not function).
Possible workarounds: Try to hot add the same member again (try several times). Try to hot add a different member.
Try removing some (or all) members from netcfg and then adding other members.
"Secondary adapter ___ deactivated / isolated from other team members."
"Secondary adapter ___ rejoined." (Note: messages of fail-overs might also appear)
Cause 1: Switch ports are not configured with VLAN Ids to match adapters. This causes ANS probes tto be dropped and then the adapters are deactivated.
Solution: 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.
Cause 2: High stress traffic. ANS probes are getting lost.
Possible workaround: Change the team's probe settings. In netcfg, choose team, protocol->Modify
protocol configuration, OK, Advanced options) and
Change "Max retry count" to 20 (causes more probe retries).
Change "Receive timeout" to 1 (less time between each retry).
Console is filled with [FAIL] messages describing the commands that ANS failed to run or
"[***] The last operation failed. Exited with status =..." and "Could not open ctrl device..." (ANS log)
Possible workaround: Remove everything from netcfg. Re-install the ANS package using "pkgadd -d" (no need to remove the package). Reboot.
Error messages concerning a "wrong state" of an adapter's driver, followed by
"OS Configuration error: message received on the wrong queue. Try to remove the network configuration and reconfigure."
Could also cause "Member is not ready for destruction" messages (very rare):
Symptoms: When booting the system, or when hot-adding a new member, "eeE8open: wrong state! "
The "problematic" member will not function correctly. Other system abnormalities might also occur.
If the user doesn't reconfigure the network, another problem might occur at shutdown or when removing the last virtual adapter from netcfg.
The system can enter an infinite loop, printing the message: "Member is not ready for destruction".
Cause: a known SCO bug preventing an adapter's driver to be opened correctly, causes problems in ANS.
Workaround: The user should remove the entire network configuration from netcfg and then reconfigure it .
If the user doesn't reconfigure netcfg and enters an infinite loop, he should do so after resetting the system.
This applies to: