| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 131.1 | and get stuck after a while | HERON::LAFORGUE | It works better if you plug it! | Wed Nov 17 1993 15:46 | 9 |
| I forgot to add something to the previous description:
If you let the DECterm in this state for a while (several minutes)
then even the Ctrl/D (or Ctrl/E for console -c) does not work)
I had to kill the csh process.
This does not seem to be related to LAT.
Regards,
/Bernard
|
| 131.2 | A few bits and pieces | OPG::SIMON | | Wed Nov 17 1993 15:55 | 64 |
| Bernard,
lets look at what you are doing:
mine is:
/usr/sbin/latcp -E te0
/usr/sbin/latcp -e te1
/usr/sbin/latcp -g 254 -a UNIDAD
> /usr/sbin/latcp -A -p tty04 -H TAGFS5 -R PORT_1
> /usr/sbin/latcp -A -p tty07 -H TAGFS5 -R PORT_2
These tow lines are not necessary.
When you define your system in the Database you should put the device name
serminal server name and port name in the system record. When CM starts the
daemon then does the necessary LAT assignments.
/usr/sbin/latcp -s
Is it OK?
(I used the -E te0 and -e te1 because I use both interfaces,
te0 for IP and DECnet and te1 for the LAT to the consoles on a separate
segment)
using console -e I defined the node DEION with /dev/tty04
and I tried to connect by
console -c DEION or console -C3 and the menu on the icon DEION.
In both case I got the same result:
a blank window with at the last two lines:
Connected to remote console (DEION)
Type CTRL/D to exit or CTRL/@ to escape to monitor
But I cannot type anything. The the Ctrl/D and Ctrl/G work but I do not
see the login prompt and it does not react to <Return> key.
Is anything wrong in my LAT setup? What should I check?
First check that CM thinks there is a connection to the remote machine
console -d -c
This will bring up the front screen of the status display.
The active systems count shows how many systems have active connections.
For further info on your system type "S"
It will prompt for your system name
"t" returns to the front screen and "q" will quit.
If the connection is not there and you think your database is correct i.e.
system record is as stated above then:
Check LAT group codes for server and port
Check the port on the server is access remote
If the connection is good then check:
Check that the port speed on the server matches the system console speed.
That's a few of the basics. If still no joy get back to me.
Cheers Simon.....
|
| 131.3 | Re .1 | OPG::SIMON | | Wed Nov 17 1993 15:57 | 4 |
| The getting stuck is probably a bug. We have a couple of timer funnies we are
ironing out at the moment. This may be a side effect of them.
Cheers SImon...
|
| 131.4 | One answer | KETJE::SYBERTZ | Marc Sybertz@BRO - 856/7572 | Wed Nov 17 1993 16:12 | 26 |
| Hi Bernard,
You don't have to change your /sbin/init.d/lat file ...
Console Manager will start the correct lat command for the concerned ports you
are using.
The only thing to do is of course to run latsetup and configure enough lat
devices.
You can use the latcp -d -P to have a look to what console has been done :
# latcp -d -P
Local Port Name = tty04 <application>
Specified Remote Node Name = DECT07
Specified Remote Port Name = DS5500
Specified Remote Service Name = DS5500
Actual Remote Node Name = DECT07
Actual Remote Port Name = DS5500
...
Marc.
|
| 131.5 | got it working, but still hanging after a while | HERON::LAFORGUE | It works better if you plug it! | Thu Nov 18 1993 10:15 | 8 |
| Thanks to Simon and Marc, I got it working.
My main problem was that the port numbers I had were obsolete.
With the correct values I got it working, I managed to connect, type
commands and get the display.
BUT I still have the hang problem after a while doing nothing on the
console.
/Bernard
|