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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

496.0. "SYS$EWDRIVER problems on OVMS 6.2" by BACHUS::ROELANDTS (Wa d'es ma da ve ne stuut) Mon Apr 21 1997 05:50

    Hello,

  *Note was posted in DECNET-OSI_FOR_VMS but I was told to post it here

  A customer reported the following problem :

  He has an Alpha with VMS 6.2, with a DE500 board installed, due to some
  other problems he was asked to install some patch kits ( ALPBOOT06_062.A +
  ALPCLUSIO01_062.A + ALPLAN04_062.A). After the installation, his DE500 could
  not operate at 100 Mb anymore, he did re-install the old SYS$EWDRIVER.EXE
  again and the DE500 started operating again. Unfortunately, I asked him to
  check with LANCP for the EWA0 controller but he couldn't because the old
  driver was re-installed, the image file build identification of the one
  that is working is : X61Q-SSB-1300 and from the one that is not :
  X61Q-SSB-L600.

  Has anyone seen this ? What could have caused this ?

  A second question is : what is the usage of the SYS$EWBTDRIVER with regards
                         to the SYS$EWDRIVER ?

  Thank you for any info.

       Regards,

            Guy



T.RTitleUserPersonal
Name
DateLines
496.1EWA0_MODE?EVMS::JSTICKNEYJay Stickney, OpenVMS LAN Eng., 381-2020, ZK3-4/T12Mon Apr 21 1997 09:1618
    The ALPLAN04_062 kit has a few bug fixes, adds support for the
    DE500-AA, and adds support for using the EWA0_MODE console environment
    variable to configure the operating mode of the EW device. Do you 
    know what the customer has EWA0_MODE set to?  The release notes
    describe how to use the variable. 
    
    The SYS$EWBTDRIVER driver allows you to network boot your system 
    over EW devices.  Like booting a satellite into a cluster.  The
    ALPBOOT06_062 kit provides a new version that supports the DE500-AA.
    
    I assume that your customer has a DE500-XA since it was supported
    under V6.2.  This device was tested with the ALPLAN04_062 and
    ALPBOOT06_062 kits and is up and running without problems at
    other customer sites.
    
    Jay Stickney
    OpenVMS LAN Engineering 
                           
496.2VMSSG::FRIEDRICHSAsk me about Young EaglesMon Apr 21 1997 10:079
    ALPCLUSIO01_062 contains SYS$EWBTDRIVER.  I will have to go verify 
    whether ALPCLUSIO01_062 or ALPBOOT06_062 have the newer one.  
    
    I suspect that whatever order they installed the kits is the opposite
    of what it should be..
    
    Cheers,
    jeff
    
496.3installation orderBACHUS::ROELANDTSWa d'es ma da ve ne stuutMon Apr 21 1997 10:3819
    
    
    Hello dear .1 and .2 repliers,
    
    I'm getting somehow confused. If I use a stand-alone system, I think
    I'm using the sys$ewdriver for the DE500, isn't it ? It is only if I
    need to boot my system over the LAN that I use the sys$ewbtdriver then.
    
    In this case the sys$ewbtdriver does not play, but is there still an
    installation order ?

     I checked and it apperas that ALPBOOT06_062.A contains a sys$ewbtdriver
     from 24-Dec-1996, that ALPCLUSIO01_062.A contains a sys$ewbtdriver from
     11-Feb-1997 and ALPLAN04_062.A doesn't contain one, so I think the order
     should be ALPBOOT then ALPLAN then ALPCLUSIO.
    
    Regards,
    
          Guy
496.4EVMS::JSTICKNEYJay Stickney, OpenVMS LAN Eng., 381-2020, ZK3-4/T12Tue Apr 22 1997 09:4511
    Guy,
    
    You are correct, you are not using sys$ewbtdriver.  I'm not familiar
    with the ALPCLUSIO01_062 kit but I would hope that it has the latest
    sys$ewbtdriver bits since it has a more recent date which would make
    sense that your installation order is correct.  
    
    Your DE500-AA should work correctly with sys$ewdriver from ALPLAN04_062.  
    Did you find out what the customer has EWx0_MODE set to at the console?
    
    Jay.
496.5will test with a DE500-AABACHUS::ROELANDTSWa d'es ma da ve ne stuutMon Apr 28 1997 04:3228
    
    
    Jay,
    
    I asked the customer to check the following things :
    
    1. Kind of DE500 : they use DE500-XA modules
    
    2. Installation order : they did it in the correct order, but in the
    release notes of ALPBOOT06_062 I found the following :
    
    The ALPBOOT06_062 kit CANNOT be installed if the ALPCLUSIO01_062 Cluster
    Compatiblity Kit for mixed V6.2 and V7.1 systems was previously installed.
    
    So I don't know what this can do to the system
    
    3. Checked the console firmware : v3.8
    
    4. The EWx0_mode was not correct initialy, corrected it : same problem
       (I asked to put it at Fast)
    
    I will test now with a DE500-AA, to see if this changes something.
    
    Rgds,
    
         Guy
    
    
496.6STAR::STOCKDALEMon Apr 28 1997 08:127
If EWn0_MODE was set correctly and the correct driver was installed,
both the DE500-XA and -AA should work.  It sounds like one of these two
is incorrect.  Can you post the output from the console 'show config'
and 'show ew' commands?  And the console output from the boot?  And
the output from SHOW LAN/FULL in SDA once the system is booted.

- Dick