Technical data

Workaround: Set the DOI to 1 using the Solaris Management Console.
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 congurations. 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
conguration steps.
Workaround: The command routeadm enables IP forwarding. The conguration 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 conguration to the currently running system, type
routeadm -u.
For more information about IP forwarding, see the
routeadm(1M) man page.
Zone Not Booting When IP Address Belongs to a Failed
IP Network Multipathing Group (6184000)
A zone can be congured so that the zone's IP address becomes part of an IP Network
Multipathing (IPMP) group. The conguration process is documented in
“How to Extend IP
Network Multipathing Functionality to Shared-IP Non-Global Zones” in System
Administration Guide: Oracle Solaris Containers-Resource Management and Oracle 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.
Networking Issues
Chapter 2 • Solaris Runtime Issues 83