Performing the Initial Internal Zone Configuration

You must configure the zone using one of the following methods:

Log into the zone and configure it as described in Internal Zone Configuration.
Configure the zone using an /etc/sysidcfg file as described in How to Use an /etc/sysidcfg File to Perform the Initial Zone Configuration.

Tip - After you have performed the internal configuration, it is a good idea to make a copy of the non-global zone's configuration. You can use this backup to restore the zone in the future. As superuser or Primary Administrator, print the configuration for the zone my-zone to a file. This example uses a file named my-zone.config.

global# zonecfg -z my-zone export > my-zone.config

See How to Restore an Individual Non-Global Zone for more information.

How to Log In to the Zone Console to Perform the Internal Zone Configuration

You must be the global administrator in the global zone to perform this procedure.

Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see Using the Solaris Management Tools With RBAC (Task Map) in System Administration Guide: Basic Administration.
Use the zlogin command with the -C option and the name of the zone, my-zone in this procedure.
```
global# zlogin -C my-zone
```
From another terminal window, boot the zone.
```
global# zoneadm -z my-zone boot
```
You will see a display similar to the following in the zlogin window:
```
[NOTICE: Zone booting up]
```

The first time you log in to the console, you are prompted to answer a series of questions. Your screen will look similar to this:

SunOS Release 5.10 Version Generic 64-bit
Copyright 1983-2006 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: my-zone
Loading smf(5) service descriptions: 114/114
Select a Language
     1. English
     2. es
     2. fr

Please make a choice (1 - 3), or press h or ? for help:

Select a Locale

      1. English (C - 7-bit ASCII)
      2. Canada (English) (UTF-8)
      4. U.S.A. (UTF-8)
      5. U.S.A. (en_US.ISO8859-1)
      6. U.S.A. (en_US.ISO8859-15)
      7. Go Back to Previous Screen
      
Please make a choice (1 - 7), or press h or ? for help:

What type of terminal are you using?
      1) ANSI Standard CRT
      2) DEC VT52
      3) DEC VT100
      4) Heathkit 19
      5) Lear Siegler ADM31
      6) PC Console
      7) Sun Command Tool
      8) Sun Workstation
      9) Televideo 910
      10) Televideo 925
      11) Wyse Model 50
      12) X Terminal Emulator (xterms)
      13) CDE Terminal Emulator (dtterm)
      14) Other
Type the number of your choice and press Return:
13
.
.
.

For the complete list of questions you must answer, see Internal Zone Configuration.

(Optional) If you are not using two windows as described in step 3, you might have missed the initial prompt for configuration information. If you see the following system message at zone login instead of a prompt:
```
[connected to zone zonename console]
```
Press Return to display the prompt again.
If you enter an incorrect response and try to restart the configuration, you might experience difficulty when you attempt the process again. This occurs because the sysidtools can store your previous responses.
If this happens, use the following workaround from the global zone to restart the configuration process.
```
global# zlogin -S zonename /usr/sbin/sys-unconfig
```
For more information on the sys-unconfig command, see the sys-unconfig(1M) man page.

How to Use an `/etc/sysidcfg` File to Perform the Initial Zone Configuration

You must be the global administrator in the global zone to perform this procedure.

Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see Using the Solaris Management Tools With RBAC (Task Map) in System Administration Guide: Basic Administration.
From the global zone, change directories to the non-global zone's /etc directory:
```
global# cd /export/home/my-zone/root/etc
```

Create the sysidcfg file and place it in this directory.

The file will look similar to the following:

For a shared-IP zone:

system_locale=C
terminal=dtterm
network_interface=primary {
            hostname=my-zone
}
security_policy=NONE
name_service=NIS {
            domain_name=special.example.com
            name_server=bird(192.168.112.3)
}
timezone=US/Central
root_password=m4qtoWN

For an exclusive-IP zone with a static IP configuration:

system_locale=C
terminal=dtterm
network_interface=primary {
         hostname=my-zone
         default_route=10.10.10.1
         ip_address=10.10.10.13
         netmask=255.255.255.0
}
timezone=US/Central
root_password=m4qtoWN

For an exclusive-IP zone with DHCP and IPv6 option:

system_locale=C
terminal=dtterm
network_interface=primary {
            dhcp protocol_ipv6=yes
}
security_policy=NONE
name_service=DNS {
         domain_name=example.net
         name_server=192.168.224.11,192.168.224.33
}
timezone=US/Central
root_password=m4qtoWN

By default, a separate module will request the NFSv4 domain parameter used by the nfsmapid command. To complete a hands-off initial zone configuration, edit the file default/nfs, uncomment the NFSMAPID_DOMAIN parameter, and set the domain to the desired NFSv4 domain:
```
global# vi default/nfs
        .
        .
        .
        NFSMAPID_DOMAIN=domain
```
For more information on the NFSv4 domain parameter, see the nfsmapid(1M) man page.
Create the file .NFS4inst_state.domain in this directory to indicate that the NFSv4 domain has been set:
```
global# touch .NFS4inst_state.domain
```
Boot the zone.