Explanation/Reference:
* Use the configuration element in the AI manifest for the client system to specify non-global zones.
Use the name attribute of the configuration element to specify the name of the zone.
Use the source attribute to specify the location of the config file for the zone.
The source location can be any http:// or file:// location that the client can access during installation.
* The following sample AI manifest specifies two Non-Global Zones: zone1 and zone2 You should replace the server_ip with the ip address of the NFS server.
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance>
<target>
<logical>
<zpool name="rpool" is_root="true">
<filesystem name="export" mountpoint="/export"/>
<filesystem name="export/home"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
<software type="IPS">
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
<software_data action="install">
<name>pkg:/entire@latest</name>
<name>pkg:/group/system/solaris-large-server</name>
</software_data>
</software>
<configuration type="zone" name="zone1" source="file:///net/server_ip/export/zone_config/zone1"/>
<configuration type="zone" name="zone2" source="file:///net/server_ip/export/zone_config/zone2"/>
</ai_instance>
</auto_install>
Reference: Automating Solaris 11 Zones Installation Using The Automated Install Server