Set up the Environment › Identifying and Solving Connection Problems › Possible Solutions

Possible Solutions

If the connection is not working correctly, check the following:

• The LAT status is correct by using the LATCP utility.
• The DECconnect adapter is seated correctly.
• The DECconnect cable ends are connected correctly.
• The baud rates of the devices at each end of the cable are the same.
• The host system and terminal or console servers are using the same LAT group codes.
• The TELNET listeners on the terminal or console server are correctly configured.
• The port and server names in the configuration database match those set up on the terminal or console server (this includes case sensitivity of names).
• The terminal device assigned is of the appropriate type for the connection method being used.
• The PING utility, supplied as part of the TCP/IP Services for OpenVMS software shows that the TELNET terminal or console server is available on the network.
• The terminal server port is set up for remote access.
• The terminal server ports are correctly configured for XON/XOFF flow control.
• Before attempting to connect to a console with Console Manager using SSH, first validate the SSH configuration from DCL.
  • Be sure the TCP/IP stack commands are initialized. Execute one of the following commands:

    TCPIP Services

    @sys$manager:tcpip$define_commands
    

    TCPware

    $ @TCPware:TCPWARE_COMMANDS
    

    MultiNet

    $ SET COMMAND MULTINET:USER.CLD
    

    For best results, run this command in system-wide login procedure SYLOGIN.COM.

  • Validate the SSH connection to your terminal/console server:

    $ ssh <username>@<terminal/console-server>#<port number>
    

• Security settings external to the Console Manager database were changed. One example: the contents of an identity file used by CM for SSH connections. In this case, you need to shut down and then restart Console Manager in order to use the new settings for all affected connections.
  • Examine your SYS$STARTUP:SYLOGIN.COM for any command that might interfere with the SSH connection. Typically, terminal setup commands such as SET TERMINAL/INQUIRE or terminal output commands such as WRITE SYS$OUTPUT can cause these processes to abort shortly after their creation, before pseudo terminal characteristics are finalized. To avoid this, insert the following instructions at the top of the SYLOGIN.COM file:

    $ if f$locate(“ssh “,f$getjpi(“”,”prcnam”)) .eq. 0 then exit 1
    

  • When connecting to the MP/iLO of an HP Integrity server, you need to execute the necessary commands on the MP/iLO in order to interface with the operating system console. For example, enter the “CO” command at the MP/iLO command prompt after executing the CONSOLE CONNECT command to interface with it. Execute the necessary commands to access the OS console at least once after:
    1. startup of Console Manager
    2. executing the RECONFIGURE command

For more troubleshooting information, see the DECconnect System Planning and Configuration Guide.