test

Solaris 10 7/07 HW Release Notes

Networking Issues

The following networking bugs apply to the Solaris 10 release.

File libmd.so.1 Not Found (6541703)

The symbolic link between /lib/libmd.so and /lib/libmd.so.1 is missing.

The following error message is displayed:


libmd.so: not found

Workaround: Log in as a superuser. Type the following command on the command line to manually add the symbolic link:


ln -s /lib/libmd.so.1 /lib/libmd.so

Login Fails on iSCSI Target With Two Portals and One Bad Portal (6476060)

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.

System Domain of Interpretation Is Not Configurable (6314248)

The system Domain of Interpretation (DOI) is not configurable. When the SMC is used to create a new trusted network template, the SMC 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 SMC.

Memory Leaks with ECC and RSA Cipher Suites (6421471)

Memory leak in NSS with ECC and RSA cipher suites might cause a system hang or system panic. The out of memory error message is displayed.

Workaround: Install the following patches:

iSCSI Initiator Does Not Handle LUN Address Reporting Properly (6377485)

The Solaris iSCSI software initiator does not support logical units with a LUN greater than 255. No error message is displayed.

Workaround:

Change the logical unit numbers of the target device to less than 255.

Wrong MAC Address is Displayed When There is More Than One Ethernet Card (6316245)

When you register to a Solaris 10 7/07 HW OS for remote update management using the Sun Update Connection, your system information is displayed. If your system has more than one Ethernet card, the same MAC address is displayed for all the Ethernet cards. No error message is displayed.

Workaround: None.

SPARC: RTM_IFINFO Message Has Different Sizes on 32-bit and 64-bit Compilations

Sixty-four-bit programs that create PF_ROUTE sockets and parse the contents of RTM_IFINFO messages in the if_msghdr_t structure might work incorrectly unless they are recompiled.

IP Forwarding Disabled by Default in Solaris 10 OS

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.

For more information about IP forwarding, see the routeadm(1M) man page.

Generic LAN Driver Version 3 Fails to Set Field Length of Logical Link Control Frames (6350869)

The Generic LAN Driver Version 3 (GLDv3) incorrectly sets the field length of Logical Link Control (LLC) frames. Consequently, protocols such as AppleTalk that are dependent on LLC do not function correctly. No error message is displayed. The problem affects the following network interface controllers:

Workaround: None.

Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)

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.

Intermittent Errors Might Occur With the Use of DataDigests (5108515)

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.

ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)

During system boot, multiple instances might not connect to their LAN Emulation (LANE) instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level.

Workaround: To reinitialize your SunATM network, perform the following steps:

  1. Verify the problem by issuing a lanestat -a command.

    Instances that are not connected have Virtual Circuit Identifier (VCI) values of 0 to the LAN Emulation Server (LES) and Broadcast and Unknown Address Server (BUS).

  2. Stop and restart your SunATM network.


    # /etc/init.d/sunatm stop
# /etc/init.d/sunatm start

  3. Reset netmasks or any other network setup for the SunATM interfaces.

Configuring Multiple Tunnels Between Two IP Nodes With Filtering Enabled Might Result in Packet Loss (4152864)

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: