General Issues

This section contains general issues about the IDN feature. Read this section before you attempt to configure an IDN.

Software Support

To use IDNs, the SSP must be running SSP version 3.2.

idn.conf(4) File

IDNs are initialized on the domain by using the idn.conf(4) file. Each domain must have an idn.conf(4) file to be a member of an IDN. This file is used to instantiate each instance of the driver and to initialize multiple parameters that can affect the performance and behavior of the IDN. You must ensure that the values of the parameters are within the allowed ranges of the values. Refer to the Sun Enterprise 10000 InterDomain Networks User Guide in the SSP 3.2 AnswerBook2^TM collection for more information about the idn.conf(4) parameters.

Values outside of the allowed range can result in panics occurring on the domain after the domain is rebooted. If the domain panics, the event detector daemon detects the panic and reboots the domain, causing the domain to panic again. Thus, the domain cannot be rebooted if the idn.conf(4) file contains an incorrect value. Sun Microsystems suggests that any /etc/hostname.idnX file be removed to prevent automatic loading of the IDN driver upon reboot.

OpenBoot^TM PROM

Be aware of the following issues with the idn-smr-size variable and with breaking to the OpenBoot PROM (OBP) prompt on the Sun Enterprise 10000 server.

idn-smr-size Variable

The OBP variable for the IDN feature, idn-smr-size, is present in Solaris 2.6. If Solaris 2.6 is installed on a domain, do not set the value to any other value other than zero (the default value). The IDN feature is not supported in the Solaris 2.6 operating environment.

OBP Environment

Before you break to the OBP prompt, unlink the domain from its IDN by using the domain_unlink(1M) command. Do not break to OBP while the domain is linked to an IDN.