About Oracle Solaris 10 Zones in This Release

Operating Limitations

A /dev/sound device cannot be configured into the solaris10 branded zone.

Debugging Tools and System Call Traps

Debugging tools can be used to debug single processes inside an Oracle Solaris 10 Container.

Administrators must use the truss command, mdb command, and other debugging tools that can observe system call traps, such as the dbx debugging tool, from the Oracle Solaris 11 global zone if the commands will follow child processes.

Debugging commands and tools that can observe system call traps do not properly follow child processes forked from controlled processes when the commands are executed within solaris10 branded zones. For example:

truss -f -p PID

does not follow the children of the process identified by PID. Attempting to follow child processes with these tools within Oracle Solaris 10 Zones can result in undefined behavior.

Additionally, the Oracle Solaris 10 truss, mdb, and other debugging commands will not observe the following syscall traps and their 64-bit equivalents because the traps were eliminated, re-implemented, or renumbered in Oracle Solaris 11 Express:

• access

• chmod

• chown

• creat

• dup

• fchmod

• fchown

• forkall

• fork1

• fsat

• fstat

• fxstat

• lchown

• link

• lstat

• lwp_mutex_lock

• lwp_sema_wait

• lxstat

• mkdir

• mknod

• poll

• readlink

• rename

• rmdir

• stat

• symlink

• umount

• unlink

• utime

• utimes

• xmknod

• xstat

For more information, see mdb(1) and truss(1).

Networking in Oracle Solaris 10 Zones

The following sections identify Oracle Solaris 10 networking features that are either not available in Oracle Solaris 10 Zones or are different in Oracle Solaris 10 Zones.

Networking Features That Are not Supported

• Mobile IP is not supported. This feature is not available in Oracle Solaris 11 Express.

• Automatic tunnels using the atun STREAMS module are not supported.

• The following ndd tunable parameters are not supported in a solaris10 branded zone:

  • ip_squeue_fanout

  • ip_soft_rings_cnt

  • ip_ire_pathmtu_interval

  • tcp_mdt_max_pbufs

Networking Features That Are Different

In a solaris10 branded zone with an exclusive-IP configuration, the following features are different from a physical Oracle Solaris 10 system:

• In a solaris10 branded zone, an autopush configuration will be ignored when the tcp, udp, or icmp sockets are open. These sockets are mapped to modules instead of STREAMS devices by default. To use autopush, explicitly map these sockets to STREAMS-based devices by using the soconfig and sock2path.d utilities described in the soconfig(1M) and sock2path.d(4) man pages.

• In a solaris10 branded zone, you must install the patch to support /dev/net links in the Data Link Provider Interface (DLPI) library, which is described in thelibdlpi(3LIB) man page.

  • 145923-01 or later version (SPARC)

  • 145924-01 or later version (x86/x64)

  Contact your support provider for information regarding patches.

  Applications that do not use either the patched libdlpi or libpcap versions 1.0.0 or higher libraries will not be able to access /dev/net links.

• Because IP Network Multipathing (IPMP) in Oracle Solaris 10 Zones is based on the Oracle Solaris 11 Express release, there are differences in the output of the ifconfig command when compared to the command output in the Oracle Solaris 10 operating system. However, the documented features of the ifconfig command and IPMP have not changed. Therefore, Oracle Solaris 10 applications that use the documented interfaces will continue to work in Oracle Solaris 10 Zones without modification.

  The following example shows ifconfig command output in a solaris10 branded zone for an IPMP group ipmp0 with data address 198.162.1.3 and the underlying interfaces e1000g1 and e1000g2, with test addresses 198.162.1.1 and 198.162.1.2, respectively.

  % ifconfig -a
  e1000g1: 
  flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> 
  mtu 1500 index 8
          inet 198.162.1.1 netmask ffffff00 broadcast 198.162.1.255
          ether 0:11:22:45:40:a0
  e1000g2: 
  flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> 
  mtu 1500 index 9
          inet 198.162.1.2 netmask ffffff00 broadcast 198.162.1.255
          ether 0:11:22:45:40:a1
  ipmp0: flags=8011000803<UP,BROADCAST,MULTICAST,IPv4,FAILED,IPMP> mtu 68 
  index 10
          inet 198.162.1.3 netmask ffffff00 broadcast 198.162.1.255
          groupname ipmp0

  • Unlike the display produced on an Oracle Solaris 10 system, the ifconfig command in an Oracle Solaris 10 Container does not show the binding of the underlying interfaces to IP addresses. This information can be obtained by using the arp command with the -an options.

  • If an interface is plumbed for IPv6 and address autoconfiguration succeeds, then the interface is given its own global address. In Oracle Solaris 10, each physical interface in an IPMP group will have its own global address, and the IPMP group will have as many global addresses as there are interfaces. In an Oracle Solaris 10 Container, only the IPMP interface will have its own global address. The underlying interfaces will not have their own global addresses.

  • Unlike the Oracle Solaris 10 operating system, if there is only one interface in an IPMP group, then its test address and its data address cannot be the same.

  See the arp(1M) and ifconfig(1M) man pages, and IP Network Multipathing in Exclusive-IP Zones.