| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1492.1 | check network reachability | ALEPPO::BOWKER | Joe Bowker, KB1GP | Fri Feb 28 1997 12:10 | 12 |
| If the console port is using LAT, can you connect to the terminal
server using NCP (Connect via xxx-0 phys addr 08-00-2b-.....)
You can also check port status using LATCP.
or if TELNET try TELNETing to (or pinging) the terminal server.
In other words check the network path to the terminal server to see if
you can reach it.
Joe
|
| 1492.2 | Some answers | CHOWDA::GLICKMAN | writing from Newport,RI | Fri Feb 28 1997 12:53 | 9 |
| I did connect to the DECserver and found the port was idle.
I also created a test LAT port and was able to do the SET HOST/DTE and
connected up just fine.
I also have done a CONSOLE MONITOR SHOW SYSTEM and found this node
to have a Console Line Status of Unknown.
|
| 1492.3 | Licenses = number of nodes you can connect | CHOWDA::GLICKMAN | writing from Newport,RI | Sat Mar 01 1997 09:05 | 6 |
| Figured it out. I was testing connecting to an HSJ and forgotten that
I only had 6 licenses. When the HSJ was added I had 7 connections
hence I was over the limit. Once I removed the HSJ description out of
the configuration I was back in business. The customer is in the
process of buying the additional licenses.
|
| 1492.4 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon Mar 03 1997 11:17 | 11 |
| Whenever you have this problem the first thing to do is
CONSOLE STATUS/CONTINUOUS/ALL
Check the State field. The last letter in the State field is the
connection status. One of it's possible values is "P" which means there
is no PAK. To see all possible values for the State field enter "?" or
"H" for help.
Regs,
Dan
|