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 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 Create OS Profile wizard incorrectly shows ja_JP.EUC_JP as a selection. If ja_JP.EUC_JP is selected, then the load OS process will fail.
Workaround:
Specify ja_JP.UTF-8 when creating the OS profile: and deploy it to the provisionable server, for example:
N1-ok> set osprofile osprofile_name language=ja_JP.UTF-8
Deploy the profile using the load server command or the Load OS wizard in the browser interface.
Log in to the provisionable server as root, and open the /etc/default/init file for edit.
Replace the text ja_JP.UTF-8 with ja_JP.eucJP, then save and close the /etc/default/init file.
Clicking the Help button in a localized environment causes all text in the browser interface Command Line pane to display in English, except for tab completion text.
Workaround: Refresh the browser interface by clicking the browser Reload button.
If you specify a OS Distribution name with non-ASCII characters during the create os command, the OS distribution name will not display properly with the show os command.
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.