| No they aren't stupid questions:
In a nutshell you setup the serverport about the same as you would for
a LAT printer port. Here is an example from a DS90TL:
Port 2: (Remote) Server: LLANO
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Disabled
Stop Bits: Dynamic
Access: Remote Local Switch: None
Backwards Switch: None Name: PCM02
Break: Remote Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: Telnet Default Menu: None
Preferred Service: None
Authorized Groups: 63
(Current) Groups: 63
Enabled Characteristics:
Input Flow Control, Loss Notification, Message Codes,
Output Flow Control, Verification
Regards,
Dan
|
| [PLY_CM] LAT Connection Setup and Troubleshooting for PCM
COPYRIGHT (c) 1988, 1993 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.
Copyright (c) Digital Equipment Corporation 1994. All rights reserved.
PRODUCT: POLYCENTER Console Manager (PCM) Versions 1.1, 1.5
OP/SYS: OpenVMS VAX
OpenVMS AXP
SOURCE: Digital Equipment Corporation
OVERVIEW:
POLYCENTER Console Manager supports connections to service systems
using a terminal server with either LAT or TELNET protocol. This
article provides information on setting up and troubleshooting LAT
connections, and is divided into the following sections:
Background
Terminal Server Setup
Troubleshooting LAT Connections
BACKGROUND:
The LAT connection consists of a host system connected to the same
Ethernet network as the terminal servers which are connected to PCM
serviced systems. The terminal servers are configured with the
characteristics of a printer connection. The LTA devices are mapped
automatically at PCM startup using information supplied in the PCM
database for server name and port name. For more information on
configuring PCM for LAT, see "POLYCENTER Console Manager Users' Guide",
May 1994, (AA-PRENB-TE), Chapter 2.
TERMINAL SERVER SETUP:
1. Method to log onto the terminal server:
$ MCR LATCP SHOW CONNECTION
o The column "Remote Node' lists the terminal server name
with the Ethernet address to the right. Record the address.
Note: The server may not be present in the list if no
connections have been made. If this is the case, the
Ethernet address may be obtained from the back of the
terminal server. You may also login directly via a
server console.
$ MCR NCP SHOW KNOWN CIRCUITS
o Record the circuit name xxx-0. If no circuits are listed,
DECNET is not started. Either start DECNET or log
directly into the terminal server.
$ MCR NCP CONNECT VIA xxx-0 PHYSICAL ADDRESS -
_$ xx-xx-xx-xx-xx-xx (Ethernet address of the terminal server)
o You are prompted for the password of the terminal server.
LOCAL> SET PRIV
o To enable privileged access, you will be prompted for
the terminal server System password.
LOCAL> SHOW SERVER
o To confirm the terminal server name.
2. Perform the following steps for each terminal server port being
used for PCM host-initiated LAT connections:
LOCAL> DEFINE PORT n NAME port_name
o Where 'n' is the physical port number and 'port_name'
is the name i.e. PCM01.
LOCAL> DEFINE PORT n SPEED baud
o The 'baud' must be the setting of the actual console
port of the PCM service node.
LOCAL> DEFINE PORT n ACCESS REMOTE
LOCAL> DEFINE PORT n BREAK REMOTE
LOCAL> DEFINE PORT n AUTOBAUD DISABLE
LOCAL> DEFINE PORT n AUTOPROMPT DISABLE
LOCAL> DEFINE PORT n BROADCAST DISABLE
LOCAL> DEFINE PORT n AUTHORIZED GROUP 0 DISABLE
LOCAL> DEFINE PORT n AUTHORIZED GROUP group ENABLE
o Enable a unique LAT group number so that only the PCM
host controls this port.
o Define the same group number for all ports of the
same terminal server.
LOCAL> SHOW PORT n
o To confirm the above settings especially the port names.
If necessary, redefine the settings.
LOCAL> LOGOUT PORT n
o Repeat for each port to implement the above settings.
LOCAL> LOG
<CRTL/D> (Not needed if you are using a terminal directly
attached to the terminal server.)
TROUBLESHOOTING LAT CONNECTIONS:
Basic information is required for some of the troubleshooting steps
below. That information may be found in preceding steps. We would
advise you to proceed through the steps in order.
The troubleshooting strategy used in this section proceeds as follows:
What messages are provided from PCM?
What information is provided in the PCM Console Editor?
Is LAT started and are Connections Enabled?
Are the terminal server characteristics appropriate?
Are the port characteristics appropriate?
Generating additional errors
Creating and testing an LTA device
Hardware notes
1. Check the PCM Status of the Console line.
$ CONSOLE MONITOR
Command: SHOW SYSTEM
System User Connected Console Line Status
------ -------------- -------------------
node_name OK
node_name Port Open Failed
Check the C3 node icon for information by using MB3 and select
from the popup menu "System Status". The System Status
information is found in the top left corner under the icon box.
2. Review system information in the Console Editor for the type
of Connection, Terminal Server, Server Port, and the Console Line
to confirm that it is Enabled.
-----------------------------------------------------------------
$ CONSOLE EDIT /INTERFACE=CHARACTER_CELL SHOW SYSTEM HILIFE
System Name = HILIFE
Information = 1
>> Connection = LAT (terminal server)
>> Terminal Server = SSTDS1
>> Server Port = PCM06
Scan Profile = MVII
Icon filename = Q3_MICROVAX_II.XBM
>> Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
----------------------------------------------------------------
3. Confirm that the LAT transport is active by checking if the
Incoming and Outgoing Connections are Enabled.
$ MCR LATCP SHOW CHARACTERISTICS
Fix: $ @SYS$MANAGER:LAT$SYSTARTUP.COM
4. Check terminal server characteristics. See TERMINAL SERVER
SETUP above for more information.
-----------------------------------------------------------------
Local> SHOW SERVER
DECserver 200 V3.0 BL33 LAT V5.1 ROM BL20 Uptime:1 17:14:29
Address: 08-00-2B-07-27-4D >> Name: SSTDS1 Number: 0
Identification:
Circuit Timer: 80 Password Limit: 3
Console Port: 1 Prompt: Local>
Inactivity Timer: 30 Queue Limit: 24
Keepalive Timer: 80 Retransmit Limit: 8
Multicast Timer: 30 Session Limit: 32
Node Limit: 100 Software: PR0801ENG
>> Service Groups: 0, 63
Enabled Characteristics:
Announcements, Broadcast, Dump, Lock
-----------------------------------------------------------------
Does the Server Name match the reference in the Console Editor
i.e. SSTDS1?
Fix: Change the field when prompted for "Terminal Server"
$ CONSOLE EDIT /INTERFACE=CHARACTER_CELL
PCM Edit> MODIFY SYSTEM HILIFE
5. Check the port characteristics on the terminal server.
-----------------------------------------------------------------
Local> SHOW PORT 6
Port 6: (Remote) Server: SSTDS1
Character Size: 8 >> Input Speed: 9600
Flow Control: XON >> Output Speed: 9600
Parity: None Modem Control: Disabled
Access: Remote Local Switch: None
Backwards Switch: None >> Name: PCM06
Break: Remote Session Limit: 4
Forwards Switch: None Type: Soft
Preferred Service: None
>> Authorized Groups: 63
(Current) Groups: 63
Enabled Characteristics:
Input Flow Control, Output Flow Control, Verification
-----------------------------------------------------------------
A. Does the port name match the reference in the Console Editor
i.e. PCM06? Use the Fix below that is most appropriate.
Fix 1: LOCAL> DEFINE PORT n NAME port_name
Fix 2: PCM Edit > MODIFY SYSTEM HILIFE
! Modify when prompted for "Terminal server port"
B. Does "Authorized Groups" match one of the terminal server
"Enabled Groups"?
Fix: LOCAL> DEFINE PORT n AUTHORIZED GROUP group ENABLE
C. Does the "Input/Output Speed" match the actual baud rate
of the PCM service node console port? Note: Do not use
the INPUT RATE from a SHOW TERM OPA0 on a VAX service node
since it is considered a template display. The template
display value may indicate 300 baud which is default for an
LA36. Instead, check the actual printer or VT for speed
setting.
Fix: LOCAL> DEFINE PORT n SPEED baud
6. If the problem has still not been identified, additional errors
can be generated by shutting down PCM and running the image below.
$ CONSOLE SHUTDOWN/NOCONFIRM
$ RUN CONSOLE$IMAGE:CONSOLE$DAEMON
7. It is sometimes useful to confirm a problem by creating an LTA
device, then attempting to make a connection to that device.
A. Create a test LTA device on the PCM terminal server.
$ MCR LATCP
LATCP> CREATE PORT /APPLICATION LTAxxx
LATCP> SET PORT /NODE=server_name /PORT=port_name /NOQUEUE LTAxxx
LATCP> SHOW PORT LTAxxx !Confirm device creation
LATCP> EXIT
B. Establish appropriate terminal settings, and attempt a
connection. A carriage-return should display a "Username:"
prompt if the connection is successful. An error message
could be useful in additional troubleshooting.
$ ALLOCATE LTAxxx:
$ SET TERM /TYPEAHEAD /HOST /TTSYNCH LTAxxx:
$ SET HOST /DTE LTAxxx:
<CR>
8. Hardware notes:
A. If present, check the DISABLE switch on the console cable to
make sure that it is in the PCM position.
B. The Emulex Performance 400 terminal server does not support
NonQueued Application ports. Another terminal server will
be needed since PCM requires the NonQueued port feature.
|