The following networking bugs apply to the Solaris 10 release.
The Broadcom NetXtreme II 5709 (BCM5709) chipset is not supported in the Solaris 10 10/08 release.
Workaround: Download the bnx driver from the http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php web site.
Existing chipsets might experience performance regression issues when the downloaded driver is installed.
Connection errors might occur between an NFS server and client that are using Remote Direct Memory Access (RDMA). Because of these errors, the buffer pool resources are exhausted and the system panics. The following error message is displayed:
rpcib: WARNING: rib_rbuf_alloc: No free buffers!
Workaround: Choose one of the following workarounds:
Configure the NFS server to enable TCP. In the /etc/default/nfs file, change (NFSD_PROTOCOL=tcp).
Mount the NFS file system from the client side with the proto=tcp mount option.
If an iSCSI target or an array returns more than one IP address as part of its send target response, the initiator takes into account only the last address in the list and not the first one, as it used to prior to this release. As a result, if the last IP address is bad or invalid, the connection to this target fails.
Workaround: Return the different target portal group tags (TPGT) for each entry in its send target response. The initiator tries to establish a connection to all the IP addresses so that the connection succeeds.
The system Domain of Interpretation (DOI) is not configurable. When the Solaris Management Console is used to create a new trusted network template, the Solaris Management Console sets the DOI to 0 and Solaris Trusted Extensions does not function correctly. Various error messages are displayed.
Workaround: Set the DOI to 1 using the Solaris Management Console.
In this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps.
Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.
To enable IPv4 forwarding, type routeadm -e ipv4-forwarding .
To enable IPv6 forwarding, type routeadm -e ipv6-forwarding .
To apply the enabled IP-forwarding configuration to the currently running system, type routeadm -u.
For more information about IP forwarding, see the routeadm(1M) man page.
A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Shared-IP Non-Global Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group.
The following example illustrates the result if you attempt to boot the zone.
# zoneadm -z my-zone boot zoneadm: zone 'my-zone': bge0:1: could not set default interface for multicast: Invalid argument zoneadm: zone 'my-zone': call to zoneadmd failed
Workaround: Repair at least one network interface in the group.
Internet SCSI (iSCSI) targets might report cyclic redundancy check (CRC) errors if DataDigests are enabled. User applications that update input/output buffers after transmitting to the iSCSI initiator might cause a miscalculation of the CRC. When the target responds with a CRC error, the iSCSI Initiator retransmits the data with the correct DataDigest CRC. Data integrity is maintained. However, data transfer performance is affected. No error message is displayed.
Workaround: Do not use the DataDigest option.
If you configure multiple IP tunnels between two IP nodes, and enable ip_strict_dst_multihoming or other IP filters, packet loss might result.
Workaround: Choose one of the following:
First, configure a single tunnel between the two IP nodes. Add addresses to the tunnel by using the ifconfig command with the addif option.
Do not enable ip_strict_dst_multihoming on tunnels between two IP nodes.