Chapter 16 - Operating the Server from a Remote Console
A remote server console connection allows you to operate a server from a workstation. The workstation acting as a remote server console duplicates the functions of a server console in every way. When you use the remote server console, your terminal becomes the server console. You can access all of the menus and screens of the server console. The commands you enter and the screens that appear on the remote server console simultaneously appear on the server console. The remote server console and the server console share one screen.
The remote server console feature is most appropriate for networks where a limited number of people use this feature, or where it is possible to control who can gain access to the actual server console. You can use ARLs (Access Rights Lists) to restrict who can use the remote server console. For more information on ARLs, refer to the Managing VINES Services.
This chapter explains how to set up the asynchronous terminal emulation connection you need to establish a remote console session.
Before you establish the connection, assign a line on your network serial communications card (such as the ICA card) to serve as an asynchronous terminal emulation connection. Refer to Managing Communications and the Asynchronous Terminal Emulation Guide for more information on assigning asynchronous connections.
Adding a Remote Server Console Connection
To establish a remote server console connection, you need to create an asynchronous terminal emulation service. The service needs to be running before you can configure the connection.
To Add an Asynchronous Terminal Emulation Service
1. Run MSERVICE. The Manage Services menu appears.
2. Choose ADD a server-based service. The Add a Service screen appears.
3. Enter a StreetTalk name for the service and a description of the service. For example:
StreetTalk Name: VT@Admin1@Servers
Description: Remote Console connection for Admin1The Select a Server screen appears.
4. Select a server from the list of available servers. The Select Type of Service screen appears.
5. Choose Asynchronous terminal emulation service. You are prompted to start the service immediately after creating it.
6. Choose Y. The Service Added screen appears and confirms that the service has been created and added.
7. Press ESC. The Manage a Service Menu appears. You are now ready to configure the service.
To Add a Connection to an Asynchronous Service
1. After you add the asynchronous service, choose CONTROL the service from the Manage a Service Menu. The Control A Service menu appears.
2. Choose CONFIGURE service. The Configure Asynchronous Connections screen appears.
3. Choose ADD a connection. The Name a Connection screen appears. You are now ready to name the new connection.
When you first create a new service, there are no connections defined. Defining a connection requires you to supply the following information:
Connection name - The name by which users identify the server connection. It appears on the Select a Connection menu and must be unique within the service. The name can be up to 19 characters in length and can contain letters, numbers, spaces, and punctuation marks.
Alternate name - Another name for the connection. The alternate name appears along with the connection name on the Select a Connection menu. The alternate name can be up to 19 characters in length. This entry is optional.
Description - The description line is optional. Use this field to enter information about how you configured the connection. You can enter up to 40 characters, including spaces.
1. Enter a name for the connection. For example, call the connection Remote or RemoteConsole. Use the backspace, insert, delete, and arrow keys to make corrections as needed.
Note: The remote console connection does not need to be called RemoteConsole. However, if you give the connection a name that contains the words "remote console," it will be easier to tell which connection is the remote connection when using the HOSTS command.
2. Enter an alternate name if desired.
3. Enter a description if desired, or press F10.
After you press F10 on the description line, the Select a Terminal Type screen appears. You have identified the connection. You are now ready to identify the terminal type.
1. From the Select a Terminal Type screen, choose VT100. The terminal emulates this type of connection by default. The Associate a Script File screen appears.
2. Press ENTER. Do not associate a script file with this connection. The Select Connection Type screen appears.
3. Choose Server Console. You are prompted to specify the access rights for the connection.
4. Do one of the following:
- Choose YES to define specific access rights for the connection. The Enter ARL Screen appears. You are prompted to enter a new ARL. Continue with step 5.
- Choose NO to accept the default access rights. The default access rights allow members of the following list access to the connection:
AdminList@servername@Servers
where servername is the name of the server on which the service is running. The Confirmation to Add screen appears. You are asked to confirm that you want to add this connection. Skip to step 6.
5. To define specific access rights for the connection, enter the StreetTalk name, list, or pattern that identifies the users to whom you want to provide access.
6. Do one of the following:
- Choose YES to add the new connection. The connection is added.
- Choose NO if you do not want to add the new connection. The connection is not added and the information you entered is discarded.
The Configure Asynchronous Connections screen appears.
7. Exit from MSERVICE. You are now ready to begin using the remote console.
Establishing a Remote Console Session
After you add an asynchronous service and define a connection, you are ready to begin using the remote console.
To Establish a Remote Console Connection from a Workstation
1. Enter one of the following:
- AYSNCH /S:servicename /C:connection
or
- HOSTS /A:servicename
where servicename is the StreetTalk name of the asynchronous terminal emulation service defined for the server and connection is the name of the connection defined for the service.
One of the following occurs:
- A server console menu or screen appears. You established a connection to the server. Operate the console menus as you would when using the local console.
- A blank screen appears. The console may be in use or you may need to refresh the screen.
- The Action Menu appears, informing you that the connection is busy or cannot be found. Verify that you entered the connection properly and try again.
2. Refresh the screen by pressing ESC or ENTER. The key that you press acts on whatever screen currently appears on the local console.
3. One of the following occurs:
- The following message appears:
Invalid Input. Try again.
and then the console screen appears. You established a connection to the server. Operate the console menus as you would when using the local console
- A blank screen appears. The Service Monitor may be the current screen on the server console.
- The following prompt appears:
User>
This is the UNIX prompt that appears on a server configured for Enhanced UNIX Access.
4. Enter 1 to refresh the screen on the Service Monitor. The Service Monitor appears. Operate the console menus as you would when using the local console.
Note: If you use the remote console to access UNIX on your server, exit UNIX and return to any console menu before you end the remote session. If you end a session while at a UNIX prompt, the remote console may not properly reset the terminal type.
The ATE software automatically sets the server console terminal type to VT100 for the duration of the remote server console session. If you end a remote console session anywhere except at the Operator Menu, the remote console terminal type remains set to VT100 until you return to the Operator Menu. To reset the workstation to the original terminal type, press ESC until you return to the Operator Menu.
Example Connecting to a Remote Server Console Connection Called RemoteConsole on the Server UKLON115
The following sample command line uses the ASYNCH command to connect to a remote server console connection called RemoteConsole on the server UKLON115:
asynch /c:RemoteConsole /s:vt@UKLON115@Servers
The following sample command line uses the HOSTS command to reach a list of connections for the same server:
hosts /a:vt@UKLON115@Servers
After you issue the HOSTS command, the Select a Connection menu appears. Select the remote console connection.
Exiting from a Remote Console Session
Exit from the remote console to end the connection between your workstation and the server.
To End a Remote Console Session
1. Finish the current operation and return the console to the Operator Menu.
2. Press HOME. The Action Menu appears.
3. Choose End this connection. The following message appears:
Session ended. Press ESC to exit this screen.
4. Press ESC. The DOS prompt appears.
Using the Remote Server Console
Although using the remote console is nearly identical to using the local server console, some differences exist. This section includes tips and precautions for using the remote console and explains errors you might receive while attempting to establish a remote console connection.
To prevent a user at a remote server console from inadvertently executing a command left at the server console, never leave the server console in a state in which pressing ENTER at a remote server console will execute a command that you do not want executed.
For example, if entering 4 on the current menu on the server console shuts down the system, do not leave the console after typing a 4. Someone using the remote server console might press ENTER to get a response. That action will execute your command and shut down the server.
Do not use the remote server console feature while someone else is actively using the server console. If you are using the remote server console and someone else is using the server console, your commands can conflict.
Set ARLs to restrict the number of users who have access to the remote server console. The greater the access to the remote console, the greater the possibility that a conflict will occur between commands issued from remote server console and commands issued at the same time by a user at the server console.
Keyboard Mappings on the Remote Server Console
When you access the server from a remote server console, your workstation is emulating a VT100 terminal. Occasionally, the keystroke you enter may not work as expected. Differences in key mappings require you to use different keys or key sequences to mimic the function of the keys on the local console. For example, on many menus the server console requires you to press a function key to obtain help or complete an operation (for example F1 - HELP or F10 - Continue). From the remote console you enter the same command by pressing three keys: CTRL + F + 1.
Example To Obtain Help from a Remote Console Screen - <CTRL-F>1
1. Enter CTRL-F.
2. Release the keys.
3. Enter 1. The appropriate Help screen appears.
Also, you may not be able to use the arrow keys to choose menu items. Choose menu items by entering the corresponding menu number.
Shutting Down the Server or Services
Be careful when using the remote server console feature to shut down the server. After you shut down the server, you lose your connection and the ability to issue further commands until the server is running once again.
If you shut down the server and have the server reboot automatically, you will be able to renew a connection following the reboot. However, if the server does not reboot automatically, you cannot restart it from the remote console. You must go to the server when you want to restart it.
Remote Console Terminal Settings
The remote server console feature requires that you choose VT100 as the terminal type. You must use VT100 as the terminal type for both the remote server console and the server console.
If the server console does not normally use VT100 as the terminal type, the screen display on the server console can appear garbled. This does not cause any problems for you at your workstation, but anyone looking at the server console while it is acting as a remote server console will see a garbled screen.
After you exit the remote server console connection, the server console might be left in an unusual state: the colors may be different, the text may appear in reverse video when it should not, and wavy lines may appear on the screen. To return the server console to its normal state, run any menu-driven utility, such as the Network and Systems Management utility (NSM).
Only one remote server console for each ATE service can be active at one time. If you try to connect a second remote server console, you will receive the following error message:
All of the connections are in use.
You will not be able to use the connection. Even if you configure two remote server consoles for the same service, you can use only one at a time.