Non-ASCII objects created using the N1 System Manager display random characters if you start N1 System Manager in following ways:
Running the /etc/init.d/n1sminit command in a non-UTF8 locale
Rebooting the management server in a non-UTF8 locale
Workaround: Use either of the two following methods.
Temporary solution: set the LANG environment variable to the UTF8 locale on the management server and restart the N1 System Manager. For example:
# export LANG en_US.UTF-8 # /etc/init.d/n1sminit stop # /etc/init.d/n1sminit start |
Permanent solution:
On a Solaris based management server:
Edit the file /etc/default/init and change the LANG value to en_US.UTF-8.
On a Linux based management server:
Edit the file /etc/sysconfig/i18n and change the LANG value to en_US.UTF-8.
The load server command fails to install ALOM firmware if the firmware name is non-ASCII.
Workaround: Change the firmware name to ASCII using the set firmware command.
The Python version (2.3) on a default Solaris management server does not provide adequate internationalization support for the n1sh command.
Workaround: Install Python 2.4 or later on the Solaris management server. The Python executable must be /usr/bin/python2.4.
If you deploy Solaris 10 with an OS profile that has a particular installation language set, the installation is performed in interactive mode and you must select a language when prompted. The deploy OS job will eventually time out if you do not make the language selection. The following languages create this behavior:
ja_JP.eucJP
no_NO.ISO8859-1
th_TH.TIS620
ko_KR.UTF-8
sh_BA.ISO8859-2
zh_CN.EUC
zh_CN.UTF-8
Workaround: Because the installation is no longer automated, you must monitor the deployment through the server's serial console and make the language selection. You can choose Serial Console from the Actions menu in the browser interface or use the connect server command.
This problem occurs if an ALOM-based, Solaris provisionable server is running Non–English locale and you power on and off the server using the stop and start commands, respectively.
Workaround: Use the reset server command on the server.
If a Solaris SPARC provisioning server is running a non-English locale, the package information does not display in the server details output.
Workaround: Edit the file /etc/default/init on the provisionable server, change the LANG value to en_US.UTF-8, and reboot the server.
When adding OS monitoring agents to a provisionable server, there are two situations that fail because the server is running a non-English locale.
Issue 1: "Either invalid credentials were used or ssh key in known_hosts file has changed" error message.
Issue 2: "Driver not found for the specified device" error message for Solaris 10 HW2 provisionable servers.
Workaround:
Issue 1: Delete the provisionable server's SSH credentials in the management server's known_hosts file: /.ssh/known_hosts file for a Solaris management server and /root/.ssh/known_hosts for a Red Hat management server. Then, try to add the OS monitoring agents again.
Issue 2: There is no workaround for a non-English locale. You must run the management server in the en_US.UTF-8 locale and reinstall Solaris 10 HW2 with the en_US.UTF-8 locale on the provisionable server. Then, try to add the OS monitoring agents again.