|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management Oracle Solaris 11 Information Library|
The file-mac-profile property used to create read-only zones is not available.
The quota command documented in quota(1M) cannot be used to retrieve quota information for UFS file systems being used inside the solaris10 branded zone.
Automatic tunnels using the atun STREAMS module are not supported.
The following ndd tunable parameters are not supported in a solaris10 branded zone:
In a solaris10 branded zone with an exclusive-IP configuration, the following features are different from a physical Oracle Solaris 10 system:
Mobile IP is not available in the Oracle Solaris 11 release.
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 archived from a physical system running Oracle Solaris 10 9/10 or earlier update, /dev/net links, such as VNICs, are not supported by the Data Link Provider Interface library (libdlpi). These links are supported on Oracle Solaris 10 8/11. The library is described in thelibdlpi(3LIB) man page.
Applications that do not use either the libdlpi library in Oracle Solaris 10 8/11 or libpcap versions 1.0.0 or higher libraries will not be able to access /dev/net links, such as VNICs.
Because IP Network Multipathing (IPMP) in Oracle Solaris 10 Zones is based on the Oracle Solaris 11 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 220.127.116.11 and the underlying interfaces e1000g1 and e1000g2, with test addresses 18.104.22.168 and 22.214.171.124, respectively.
% ifconfig -a e1000g1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 8 inet 126.96.36.199 netmask ffffff00 broadcast 188.8.131.52 ether 0:11:22:45:40:a0 e1000g2: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 9 inet 184.108.40.206 netmask ffffff00 broadcast 220.127.116.11 ether 0:11:22:45:40:a1 ipmp0: flags=8011000803<UP,BROADCAST,MULTICAST,IPv4,FAILED,IPMP> mtu 68 index 10 inet 18.104.22.168 netmask ffffff00 broadcast 22.214.171.124 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 configuration succeeds, then the interface is given its own global address. In an Oracle Solaris 10 system, 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 a Oracle Solaris 10 Zones, 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.