[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1207.0. "Send break to console via Telnet" by 54625::BANKEN () Thu Feb 22 1996 08:26

Hello,

Since customer switched from LAT to TELNET it is no more possible to get the console prompt.
I read note 642, but we run the DNAS software, so it should, as I understood, forward the break to the console.

Please find here below the terminal server and port characteristics.
Can someone tell me what is missing.

Network Access SW V1.5 for DS90M  BL95-32  ROM 4.1  Uptime:  27 08:10:53

Address:   08-00-2B-B0-48-F5   Name:   TSDMAD             Number:     0

Identification:

Circuit Timer:            80           Password Limit:            3
Console Port:              1           Prompt:              Local>
Inactivity Timer:         30           Queue Limit:             100
Keepalive Timer:          20           Retransmit Limit:          8
Multicast Timer:          30           Session Limit:            64
Node Limit:             None           Software:             MNENG2

Service Groups:   0


Enabled Characteristics:
Announcements,  Broadcast,  Dump,  Lock

Port  2: (Remote)                      Server: TSDMAD

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:                    PORT_2
Break:                Remote           Session Limit:                4
Forwards Switch:        None           Type:                      Ansi
Default Protocol:     Telnet           Default Menu:              None

Preferred Service: None

Authorized Groups:   0
(Current)  Groups:   0

Enabled Characteristics:
Input Flow Control,  Loss Notification,  Message Codes,
Output Flow Control,  Verification

Many thanks,

Alain.
      
T.RTitleUserPersonal
Name
DateLines
1207.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Feb 22 1996 15:2316
>Hello,

>Since customer switched from LAT to TELNET it is no more possible to get the 
    >console prompt.
>I read note 642, but we run the DNAS software, so it should, as I understood, forward the 
    >break to the console.
    
    When you attmept to send the break, does PCM disconnect the system and
    issue a message to the effect that the link has been lost to the
    remote system?
    
    If yes, then this is a known problem that has been fixed in ECO2
    which will be available shortly.

    REgards,
       Dan
1207.2Send break to console via Telnet54625::BANKENTue Mar 05 1996 09:3715
Hi Dan,

No, we don't loose the link, it just react as nothing has been send.

The node we want to 'halt' is a MVax 3100-90. For that machine, under PCM, ^P is defined to send a break.

I have really the impression that the break signal never gets through the Decserver, did you already succeed

to send a break via telnet ?

Many thanks and sorry for late answer,

Alain


1207.3CSC32::BUTTERWORTHGun Control is a steady hand.Tue Mar 05 1996 14:1326
>Hi Dan,

>No, we don't loose the link, it just react as nothing has been send.

>The node we want to 'halt' is a MVax 3100-90. For that machine, under PCM,
    > ^P is defined to send a break.

>I have really the impression that the break signal never gets through the 
    >Decserver, did you already succeed to send a break via telnet ?
    
    
    Yes, I have gotten a BREAK to be sent over a TELNET connection but I
    had to fix the code to get it to work. This was on an OpenVMS PCM
    engine though and you never stated what you PCM platform is. In short,
    if you have an OpenVMS PCM engine, trying to send a BREACK via TELNET
    doesn't work even in ECO 1. It has been fixed in ECO 2 which was kitted
    Monday and is currently being reviewed by SQM. 
    
    Regards,
       Dan

Many thanks and sorry for late answer,

Alain


1207.4Send break to console via Telnet54625::BANKENWed Mar 06 1996 04:0010
Dan,

Indeed this is an OpenVMS platform, thus we will wait the ECO2.

Maybe just one remark, I didn't find that problem in the CONSOLEECO2016.RELEASE_NOTES;10 located in the
PCMSVR::$1$dkb500:[eco.eco2] directory (not the last document version ?), just a customer question anticipation...

Regards,

Alain.
1207.542708::WATSONRLambs... so cute... but so tasty !Wed Mar 06 1996 09:5210
Hi,

    just to add an extra vote asking for the fix to the tcp/ip break transmit
problem. One of my customers was caught by this halfway through a VMS upgrade
he was doing from home. Ooops...

Thanks,
Ross

Ps. Can you also make sure that a matching OLB gets into the ECO kit ?  Ta.
1207.6CSC32::BUTTERWORTHGun Control is a steady hand.Wed Mar 06 1996 14:2311
    >Ps. Can you also make sure that a matching OLB gets into the ECO kit ? 
    
    Already done.
    
    >no mention in the release notes.
    
    Thats my fault as I found the problem a long time ago and fixed it but
    it never got IPMT'd.
    
    Regs,
      Dan
1207.7Problem solved54625::BANKENThu Mar 07 1996 10:5116
Hi,

Problem has been solved by the following Decserver command :

	LOCAL>	Change port n telnet server brk break

You may check it by the 'Show port n telnet server' command.

Dan, the fixe you spoke about is probably already included in PCM 1.6-127.

I didn't find this setting in the PCM manuals, if it is really missing, it should be added ...


Regards,

Alain.
1207.8CSC32::BUTTERWORTHGun Control is a steady hand.Fri Mar 08 1996 13:2114
    >Problem has been solved by the following Decserver command :
    
    >        LOCAL>  Change port n telnet server brk break
    
    >You may check it by the 'Show port n telnet server' command.
    
    Good work! That'll do it! I had one site that had somehow managed to
    set the server BRK characteristic to uppercase A... so he saw
    an A echoed... talk about baffling.....
    
    
    Regs,
       Dan
                                                                          
1207.9Does this work on DS300 ?42708::WATSONRLambs... so cute... but so tasty !Mon Mar 11 1996 09:178
� LOCAL>  Change port n telnet server brk break
    
Hi,

    does this work on a DECserver 300 ? If not (I can't see how you get 'break'
in there), is there an equivilent ?

Ross
1207.10CSC32::BUTTERWORTHGun Control is a steady hand.Mon Mar 11 1996 15:315
    It should. By default the setting is BREAK thus you don't need to
    worry about it unless someona has changed it.
    
    Regards,
       Dan
1207.1142708::WATSONRLambs... so cute... but so tasty !Tue Mar 12 1996 04:1919
� It should. By default the setting is BREAK thus you don't need to
� worry about it unless someone has changed it.
    
Dan,

    on my DS300 servers, the default (according to TSM) would be...

	DEFINE PORT ALL TELNET SERVER BRK None

    I tried "define port n telnet server brk ^p", which it seems to have
liked, but the user actually needs a break (typical!). If "none" is really
a break, I would assume that I'm back to square one, as that doesn't appear 
to work.

    With the imminent arrival of ECO2, I guess that this isn't a big problem, 
but I'm interested now.

Thanks,
Ross
1207.12CSC32::BUTTERWORTHGun Control is a steady hand.Tue Mar 12 1996 12:0440
    >>� It should. By default the setting is BREAK thus you don't need to
    >>� worry about it unless someone has changed it.
    
    >Dan,
    
    >    on my DS300 servers, the default (according to TSM) would be...
    
    >        DEFINE PORT ALL TELNET SERVER BRK None
    
    Thats interesting. I use a DS90TL (full DECServer command set unlike
    those "other" DS90's) and the ports are all set "Break" for the
    TELNET SERVER BREAK characteristic. I even "red-buttoned" this thing
    when I got it and set it up from scratch and I've not changed any of
    the ports. Must be a difference within the actual DS load image between
    the different servers. BTW, what version of the DS300 software are you
    running? I believe the Network Access SOftware is available for the
    300's on either OpenVMS CONDIST. Ya might want to see if your down-rev.
    
    My hat's off to you for your idea of setting the SERVER BRK to CTRL-P!
    Clever!! This would allow you to set a common break key for all systems
    and then set the port to send the proper character. This will be a moot
    point in the next release as the terminology will change. Users will
    define a HALT key (I really *HATE* the current "Break key" terminology)
    and they will specify what the halt key is and what character it sends
    on a per-node basis.
    
    Regs,
      Dan
    
        I tried "define port n telnet server brk ^p", which it seems to
    have
    liked, but the user actually needs a break (typical!). If "none" is
    really
    a break, I would assume that I'm back to square one, as that doesn't
    appear
    to work.
    
        With the imminent arrival of ECO2, I guess that this isn't a big
    problem,
    but I'm interested now.
1207.1342708::WATSONRLambs... so cute... but so tasty !Wed Mar 13 1996 05:489
� BTW, what version of the DS300 software are you running ?

    Well... I'm using 'V2.2a BL45-4', which appears to be the same as the
    version on the Dec'95 CD (well... same revision date anyway).

    I guess I'll just wait for the eco, but it would've been nice. Thanks for
    your comments.

Ross
1207.14Sending a Telnet Break over a Decserver 300 seems to be difficult...54625::BANKENWed Mar 13 1996 07:2842
Hi Ross,

This following info comes from the Polycenter Console Manager's SPD.
Please read carefully the note below the table.

Best regards,

Alain.


 Terminal Server Requirements                                                 
                                                                              
 The following terminal servers are supported for providing LAT and TELNET    
 PCM connections:                                                             
                                                                              
 ___________________________________________________________________          
 Terminal_Server__LAT________TELNET_________________________________          
                                                                              
 DECserver 200    X                                                           
 DECserver 300    X          X                                             
 DECserver 90L    X                                                           
 DECserver 90L+   X                                                           
 DECserver 90TL   X          X                                                
 DECserver 90M    X          X                                                
 DECserver 500    X                                                           
 DECserver 550    X                                                           
 DECserver 700    X          X                                                
 DECserver 900TM  X          X                                                
 LATprint_________X_________________________________________________          
                                                                              
 Note: TELNET Break functionality is only supported on the DECserver[TM]      
 90TL, DECserver 90M, DECserver 900 and the DECserver 700 with the Net-       
 work Access Software. If using TELNET the terminal server must sup-          
 port the Internet Working Group RFC 859 STATUS option in order to sup-       
 port Line Lost Notification.                                                  
                                                                              
                                                                   
                                                                              
                                                                              
                                                                              
                                                                              
                                                                      
1207.15Ah... ECO wont help ?42708::WATSONRLambs... so cute... but so tasty !Thu Mar 14 1996 11:159
Re. {last few}

    Hmmm... does this mean that, even armed with the much heralded ECO II,
    my little DS300 will not forward a break that it receives via a TCP/IP
    connection ? If this is indeed the case, then I'm still stuck.

Ta.

Ross
1207.16WOTVAX::WATSONRLambs... so cute... but so tasty !Wed Apr 10 1996 05:128
Re .-1
� ...does this mean that my little DS300 will not forward a break
� that it receives via a TCP/IP connection ?

    Can I just clarify this ? If so, I'll start sorting out a DS900.

Thanks,
Ross
1207.17CSC32::BUTTERWORTHGun Control is a steady hand.Wed Apr 10 1996 15:114
    Start moving to DS900.....
    
    Regs,
      dan