Creating a turnkey system

Creating a turnkey system

This section describes what turnkey systems are and how they are created.

The system may be set up so users only get a D3 logon message, not a UNIX login message. This type of system is called turnkey.

Turnkey systems should allocate no more than 85% of the total physical memory to shared memory. Non-turnkey systems should allocate no more than 50% of the total physical memory to shared memory. As the number of users reaches 100 or more, a 50/50 memory split is recommended for best performance.

Before creating a turnkey system, decide which devices will be UNIX terminals and which devices will be D3 terminals. Both serial tty connections and network Telnet connections can be reserved for D3 ports.

Various methods to create a turnkey system are discussed below. Review these sections to determine the method that best fits your needs.

  1. Using increased functionality
    Setting up the turnkey system using either of these two methods provides increased Telnet functionality, but does not maintain compatibility with other D3 platforms and releases. The following methods are the recommended methods for setting up a turnkey system.
  2. Configuring blocks of Telnet ports on D3
    The auto-xinet command is used to configure one or more blocks of telnet ports on D3.
  3. Maintaining compatibility
    These sections discuss creating a turnkey system while maintaining consistency and compatibility with other D3 platforms and releases.
  4. Changing inittab
    When the serial port is not in use, a single D3 turnkey respawn can be disabled. Comment out the inittab entry with the # sign, as in:
  5. SSH and Enterprise licensing
    In order to use Enterprise licensing through a SSH connection, the sshd_config file must be updated by adding the line below: