[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

1363.0. "Problem w/ CONSOLE CONNECT and OPA0 " by CHOWDA::GLICKMAN (writing from Newport,RI) Thu Aug 22 1996 09:07

    Hi,
    
    	Moving right along.  I have been able to make the connection to
    one of the node's in this VAXcluster but when I do a CONSOLE CONNECT
    the Username prompt came in as Us.  When I hit return I got ername
    and then Username.  I eventually had to type in my username and
    password without really know if I was at the right place.  Then
    the login messages from SYLOGIN and my own LOGIN came in but again
    at places would stop until I hit a return.  
    
    	When I put the cable back on the regular console monitor the 
    same thing it happening.  I have looked at the characteristics
    on that monitor and SHOW TERM OPA0: and made several changes but
    I still have this problem. When I looked at the OPA0: characteristics
    on the regular console monitor after I switched the cable the device
    was an LA36 and speed was 300.  Does POLYCENTER Console Manager change
    anything with OPA0's characteristics?
    
    	OPCOM messages print out fine.
    
    	Anyone have any ideas as to what is going on?  Would a re-boot
    of the system I am managing from PCM help?  But I was hoping to just be
    able to go back and forth from PCM to the regular console monitor while
    I'm testing as well as if there is a problem with PCM down the pike.
    
    	Appreciating any responses.
    
    	Thanks.
T.RTitleUserPersonal
Name
DateLines
1363.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Aug 22 1996 12:5214
    >Does POLYCENTER Console Manager change anything with OPA0's 
    >characteristics?
    
    No. There is no client-side to PCM. Terminal characteristics must be
    changed by a call to $QIO by a process running on the managed system
    and no part of PCM actually runs on the managed system.
    
    This sounds like a classic flow control problem. If you do a 
    SHO TERM OPA0, are Hostsync and TTSNC turned on? If you do a SHO DEV
    OPA0 is there a non-zero error count and is it incrementing? Post the
    results of a SHOW TERMINAL.
    
    Regards,
      Dan
1363.2re .1CHOWDA::GLICKMANwriting from Newport,RIFri Aug 23 1996 15:0011
    re .1
    
    	A re-boot of the managed system shook out the problem.  I had to do
    this so the machine could be shutdown this weekend for the installation 
    of a long awaited UPS.  Next week I will try again.  If I get the same
    thing happening I will post the SHOW TERMINAL.
    
    	I think HOSTSYNC was not turned on while TTSYNC was.  I did get
    a chance to do the SHOW DEV OPA0.
    
    	Thanks for the info.