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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

20.0. "Boot Node hangs off and on" by LEZAH::MCHIASSON () Thu Jan 26 1989 13:41

    I have a 2 node LAVC, (1 boot node and 1 satellite). Each is a VS_II
    with 13mb of memory. There is 1 user on the boot node, and 1 on
    the satellite. The LAVC is running VMS 5.1-T2 along with DECWINDOWS
    FT2. Just recently the user on the boot node complained that the
    sytsem was running very sluggishly. I checked the system, and if
    I log in thru a LAT, the systems seems ok, but every say 15 seconds
    or so, my screen freezes for a couple seconds, then continues. If
    I log in locally on the VS_II monitor thru DECWINDOWS, not only
    does it freeze, but the cursor stops completely for about 4 seconds,
    then continues. This happens constantly, but like I said, less
    frequently if I log in thru the LAT. The kicker is, if I log into
    the satellite, which is also a VS_II, thru the monitor, I have no
    problems whatsoever running DECWINDOWS or any other application.
    If I log into the satellite from the LAT, no problems at all. I
    have checked all parameters, set them accordingly from VPA reports
    I have generated, rebooted, and the same thing happens each time.
    I know from past experiences with LAVC's, that doing a check of
    the memory resources (IRP, SRP, LRP, NPAGEDYN) will help, but these
    are all set to what they should be, yet the system is still a dog.
    This all has happened in the past week, and the system has been
    running fine up until then...Any suggestions or clues are appreciated
    or if anyone has had similar problems, please let me know.
    
    Mark Chiasson
    297-5945

T.RTitleUserPersonal
Name
DateLines
20.1Receive errors on DECnet?CIMNET::MSMITHThu Jan 26 1989 13:4913
    If you have OPCOM running and look at the messages (using your favorite
    method), you might see a lot of DECnet RECEIVE ERRORS.  This will
    happen, for example, if your boot node is set up to serve 2 satelites
    and you've only booted one of them. (At least this is what happened
    to me last week.)  I may not have had my LAVC configured correctly,
    but when both satellites were booted, I didn't see the errors. 
    Also, the constant errors were causing both DECWINDOWS and DECNET
    to be very slow on the boot node.
    
    FWIW,
    
    Mike

20.2Sounds like DECserver "boot me's" may be the causeGOFER::HARLEYHe'd steal flies from a blind spider...Thu Jan 26 1989 14:507
I've seen the same thing happen if there's one (or more) systems like DECservers
requesting downline load service that no-one is satisfying; they'll just keep
on screaming "boot me" on the Ethernet until they either get booted, shut off,
or disconnected.

/Harley

20.3ALLOCLASS set to 1?? Maybe?GNUVAX::MCHIASSONThu Jan 26 1989 15:255
    How can I tell this? Is there a parameter (sysgen). I did notice
    that the parameter ALLOCLASS is set to 1, and all my other LAVC's
    are set to 0....Could this be the dirty rotten scoundrel?
    

20.4alloclass not the problemTRNING::BARFIELDThu Jan 26 1989 16:115
    Alloclass should not have anything to do with this situation. You're
    right, you don't need it, unless you're in a Mixed Interconnect
    or in a situation with two boot servers using dual-pathed disks.
    

20.5How to tell if "boot me's" are the culpritGOFER::HARLEYHe'd steal flies from a blind spider...Thu Jan 26 1989 21:2311
    Check the console of the boot node for DECnet event 0.7 messages (make
    sure they're enabled in NCP) and see if they occur when response
    goes down the drain. If they do, see if your Net Support group can
    help out. If they can't, I have a couple of routines that you can have
    your boot node throw at the offending systems to try to quiet them
    down.
    
    /Harley