Network Shell requirements and support

This topic discusses the requirements of Network Shell (NSH) and the scope of its support.

Internationalization support for Network Shell commands

Most of the Network Shell commands support multibyte characters for internationalization (I18N). For a list of NSH commands that support multibyte characters, see Summarized-descriptions-of-Network-Shell-commands (as indicated in the I18N Support column).

I18N support depends on several locale category (LC_*) environment variables, specifically LC_ALL and LC_CTYPE. Ensure that these environment variables are set properly before starting Network Shell and the RSCD Agent.

Note

The applicability of these environment variables to Network Shell and the RSCD agent depends on the operating system where they are installed:

  • Network Shell uses these variables, whether hosted on a UNIX operating system or a Windows operating system.
  • The RSCD agent uses these variables only if installed on a UNIX operating system. On Windows, the RSCD agent uses the operating system's language settings.

Shared memory segments for Network Shell

On a server where multiple users run Network Shell, assure there is at least N * X shared memory segments available, where N is the number of simultaneous Network Shell login sessions and X is the number of times the chrole command is executed during the Network Shell session lifetime.

ZSH support

Network Shell supports both 4_0_4 and 4_3_4 versions of ZSH. By default, Network Shell calls the 4_3_4 version of ZSH. If you want to access the earlier version of ZSH, do the following:

Note

HP-UX platforms do not support ZSH 4.3.4. The default ZSH version on HP-UX remains 4.0.4.

The following functionality described in the NSH man page only applies to the default zsh 4.3.4 (zsh-4_3_4) based Network Shell executable. When using the earlier zsh 4.0.4 (zsh) based Network Shell executable, the following behavior is not present.

  • The ability to use fully qualified paths to specify execution of native commands when those commands have Network Shell equivalents.
  • The implicit nexec of a native command on a remote host.
  1. Cd to <BladeLogic install directory>\bin. By default, this is C:\Program Files\BMC Software\BladeLogic\NSH\bin on Windows and /opt/bmc/bladelogic/NSH/bin on UNIX.
  2. Do one of the following:
    • On UNIX, enter the following commands:
      mv nsh nsh-4_3_4
      ln -s zsh nsh
    • On Windows, do the following:
      1. Rename the existing nsh.exe executable to nsh-4_3_4.exe.
      2. Copy the zsh.exe executable to nsh.exe.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*