[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

1487.0. "Connected nodes connection lost after data storm" by NEMAIL::GLICKMAN () Thu Feb 13 1997 08:48

    Twice now when there are network data storms at this customer the
    connections to the machines that POLYCENTER Console Manager is
    managing (via LAT through a DECserver 700) seem to go away when
    the operator tries to connect back after the data storm.
    
    The first time the ports on the DECserver had to be logged out and
    then they worked ok.  The second time, I tried that and it didn't 
    work,  then I tried downloading the DECserver software again and
    that didn't work either.  Finally I rebootd the AlphaStation that
    POLYCENTER Console Manager is running on and the connections came
    back.
    
    Are other sites finding this situation as well?  What are they
    doing -- following what I did?
    
    Appreciating any responses.
T.RTitleUserPersonal
Name		DateLines
1487.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Feb 13 1997 11:4620
    What version of PCM are you running? Do a CONS STATUS and tell me the
    version number shown to the right of the "CM Pid" field.
    
    By reloading the DECServer there's no question that you cleared the
    connections on the server end. Logging out each port does the same
    thing. Even if the LTA devices stayed around after PCM deassigned it's
    channels it would have been able to create new ones and reestablish
    the connections. A question:
    
    When you tried to do a CONSOLE CONNECT to one of the managed systems,
    did you receive an error to the effect of "system was disabled or
    unavailable"? If not, then did the connect interface simply not respond
    after your got the bit about "use ctrl-G to exit?
    If  you did get an error then I'd say that the LAT software on the PCM
    engine was ina wierd state and you cleared it via the reboot. If you
    simply got no response then PCM did not realize the connection went
    away. A PCM restart should have cleared it up.
    
    Regs,
     Dan
1487.2Some answers to questions in .1CHOWDA::GLICKMANwriting from Newport,RIThu Feb 13 1997 14:5118
    >>> What version of PCM are you running?
    
    CM version is V1.6-201.
    
    >>> When you tried to do a CONSOLE CONNECT to one of the managed
    systems, did you receive an error?
    
    No messages whatsoever.  Just a blinking cursor when we got to a
    connected node window.  I don't think I even got the "use ctrl-G to
    exit".
    
   >>> If you simply got no response then PCM did not realize the connection 
   >>> went away. A PCM restart should have cleared it up.                
    
    New to this whole thing and restarting the PCM hadn't occurred to me.
    I certainly can try that the next time it occurs.
1487.3CSC32::BUTTERWORTHGun Control is a steady hand.Fri Feb 14 1997 10:2922
    Okay, the first thing to do is get this site up to rev. There are
    numerous fixes in ECO 3 and above. You didn't menion if your on OpenVMS
    or DUNIX. If you on OpenVMS then grab the following from
    CSC32::PCM$KITS:
    
    CONSOLEECO3016.A
    CONSOLEECO3016.C  
    ALPH312.BCK
    
    Since you have an Alpha you do *not* need the CONSOLEECO3016.B as
    that has OpenVMS VAX images.
    
    The CONSOLEECO3016 kit is vmsinstal'able. The ALPH312.BCK is simply a 
    savset. Restore it to a temp directory and follow the instructions in
    the README file. You must install the CONSOLEECO3016 first.
    
    Regs,
      Dan