VNX for file character shows common problems and solutions

Failure phenomenon:

The article is reproduced from the EMC Chinese Support forum.

The VNX for file default character encoding is ASCII, which often uses Unicode language character criteria to store, search, and interchange text in any language in a uniform manner. After the system initial installation and platform migration, because the newly installed VNX does not start Unicode character encoding, often causing a normal file name on a computer to become garbled on another computer, this article will explain the solution to this type of problem.

Solution:

VNX for file uses the language character standard specified in Unicode Consortium, which covers the world's leading written languages, including 24 languages: Latin European, Slavic, Arabic, Hebrew, Chinese, Korean, and Japanese. EMC strongly recommends that Unicode be enabled on newly installed VNX, and that if the data mover is in ASCII mode, non-ASCII text and directory names will be saved as-is without any transformations, which will result in other computers accessing these filenames and directories as garbled.

On the new VNX device, the default ASCII character encoding and directory/nas/site/locale are created on the control station, and you need to configure the international character set to display non-ASCII text names and directory names by following these steps:

Step one: Check for common file system and transformation subdirectories, and create the subdirectory if needed. Normally/nas/site/locale and/.ETC_COMMON/XLT directories exist, and directories typically include files xlt.cfg, Unidata2.txt, 8859-1.txt, Cp437.txt, 8859-15.txt, Big5.txt, Sjis.txt and Eucjp1.txt.

[nasadmin@ns480]$/nas/sbin/uc_config–setup "shows normal status as follows"

Common Unicode translation subdirectory already exists.

Step two: Depending on the language type to determine the client protocol and transformation requirements, please refer to the documentation "Using international character sets on VNX for file", Simplified Chinese character translation file does not need to be modified.

Step three: Edit the/nas/site/locale/xlt.cfg file for new character conversion requirements.

Step four: Copy edit file to directory/.etc_common/xlt.

Example: #/nas/sbin/uc_config–update big5.txt–mover server_2 (copy Chinese character conversion file)

If you do not specify a filename later, all files under the directory/nas/sbin/uc_config are copied to the/.etc_common/xlt directory.

Step Five: Authentication configuration file.

#/nas/sbin/uc_config–verify IP_Address | hostname | -mover server_2

The client IP address or host name configured by the corresponding data mover

Step Six: Verify that the conversion was successful.

#/nas/sbin/uc_config–setup

Step Seven: Open the international character set.

#/nas/sbin/uc_config–on–mover server_2

The above steps apply to the newly installed VNX device to turn on international character set support, which is different for the device operation already in use. Because the old device has already saved part of the document, the old document needs a character conversion to display correctly. Character conversions need to be done on the basis of the first five actions above.

Step One: Start the conversion, the command format is as follows:

#/nas/sbin/uc_config–convert Start Big5.txt–mover server_2 (convert server2)

#/nas/sbin/uc_config–convert Start Big5.txt–mover All (convert all)

File conversions occur only in the file system or directory that is accessed, and a large amount of system resources are consumed during the conversion, and it is recommended that you manually convert all file systems and directories immediately by using the "find" command during resource free time.

Step two: After the character conversion completes, turn off the conversion function.

#/nas/sbin/uc_config–convert Stop Big5.txt–mover server_2