HP3000-L Archives

March 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Eero Laurila <[log in to unmask]>
Reply To:
Eero Laurila <[log in to unmask]>
Date:
Thu, 9 Mar 1995 07:22:59 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Jeff Kell ([log in to unmask]) wrote:
 
: There's something special about the non-nailed default profile name too...
: seems like it must be a modem type profile (<?> not at work to check).
 
- I think the special is for DTC/telnet connections.  In order to have the
  ADCP/AFCP protocol to signal to telnet on the DTC that the TCP connection
  should be killed, ADCP drops the 'modem signals'.  With this piece of
  information the DTC telnet knows when the HP3000 host wants to close the
  TCP connection (i.e. BYE, ABORTJOB). I guess someone from termio will
  correct me if I'm wrong.
 
: Number of VT connections limited only by "max number of TCP connections" in
                                   ^^^^^^^
- Not quite.  There's also the NS services default "number of servers of
  each type" and total number of servers.  By default NS allows #300 vtservers
  on the system and this value can be adjusted up and down with
 
    NSCONTROL SERVER=VTSERVER,min,max
 
  command.  Max total number of servers is #1250.
 
: NMMGR (note that other things use TCP connections too).  Telnet sessions and
: non-nailed DTC sessions (sum of the two) limited by "max number of non-nailed
: ldevs".  Telnet sessions (from the DTC) do not count as a TCP connection.
 
- Right.  Telnet comes in as a DTC terminal using AFCP/ADCP protocol - no TCP.
 
:-)  Eero Laurila - HP CSY Networking lab.

ATOM RSS1 RSS2