| 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 |
Topic 1829 in the VMSNOTES_V11 conference discusses mount verification messages appearing with no apparent reason. Reply 11 says: > What worked for us was to downgrade the AlphaServer 2100 firmware. We > got a call from Dave Carlson (Sable engineering) who said they had seen > this caused by a bus arbitration problem associated with V4.1 and V4.2 > of the SRM console firware. We backed down to V4.0-3, set SCSCONNCNT > back to 15, and everything worked fine. A customer is facing probably the same problem in his mixed Alpha/VAX Cluster with two 2000 servers, one running with firmware version V4.0-3, the other one with V4.1-42, both using OpenVMS V6.2. One difference to topic 1829 is that they are using HSZ40s, not HSDs, but otherwise the symptoms are the same. Can anyone confirm that the problem in firmware versions 4.1/4.2 have been fixed in the latest version (4.7-143) ? I want to know whether I should recommend the customer to go back to (almost two years old) V4.0 or to upgrade to the latest and greatest. Thanks for your advice, Hans.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 97.1 | MVBLAB::SABLE | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Jan 28 1997 16:08 | 2 |
Check with the folks over in the Sable conference... | |||||
| 97.2 | UTRTSC::thecat.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Wed Jan 29 1997 02:18 | 5 | |
Are we talking about shadowsets? If so you can take a look at SPEZKO::CLUSTER note 4913.*. Jur. | |||||
| 97.3 | LNZALI::BACHNER | Mouse not found. Click OK to continue | Wed Jan 29 1997 04:05 | 19 | |
Re: .1 Thanks, I'll crosspost the question there. Re: .2 Thanks for the pointer, too. Been there, suggested the customer to install the patches. But 1829.11 in VMSNOTES_V11 mentions a firmware problem, and I'm not sure whether the driver patches can work around this. I'm grabbing any straw I can get - this cluster has been giving us problems for more than a year now (various crashes, some shadowing related, lots of CLUEXIT following a crash of one node in the cluster etc...), and the customer explicitely ordered a configuration for 24*365 operation... The mount verification messages are just one problem we need to get rid of - and hopefully a clean setup in this area will reduce the other problems, too. Thanks again, Hans. | |||||
| 97.4 | UTRTSC::thecow.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Wed Jan 29 1997 08:58 | 11 | |
>I'm grabbing any straw I can get - this cluster has been giving us problems for >more than a year now (various crashes, some shadowing related, lots of CLUEXIT >following a crash of one node in the cluster etc...), and the customer >explicitely ordered a configuration for 24*365 operation... The mount >verification messages are just one problem we need to get rid of - andhopefully >a clean setup in this area will reduce the other problems, too. Hmm, ever done a thorough site check (including all of the network of course)? Jur. | |||||